Incomplete Todo list of stuff that needs to be done and/or figured out before www.gnome.org can switch to wordpress:

Mandatory

• Upgrade to wordpress 3.1.1

• Copy /css/ and /img/ folder from gnomeweb-wml to gnomeweb-wp
  ovitters: Is this really the solution?

• Migrate Friends of GNOME (and ruler) to gnomeweb-wp repo
  ovitters: Is this really the solution?

• Split of projects.gnome.org and people.gnome.org from gnomeweb-wml
• Figure out what to do with /start/stable and /start/unstable links
• Audit all gnome.org sites for CSS links to www.gnome.org and ensure local copy is
• www.gnome.org/friends/ has javascript which is directly included from various sites

• http://www.gnome.org/img/ has images which are used for directory index on anjuta.org, projects.gnome.org, people.gnome.org, tracker-project.org

• i18n.gnome.org redirects to www.gnome.org/i18n/
  vuntz: Redirect to http://live.gnome.org/TranslationProject/ or http://www.gnome.org/teams/

• torrent.gnome.org redirects to www.gnome.org/start/
  vuntz: Redirect to www.gnome.org/getting-gnome/

• implement redirects (below)

Recommended

• One have one wordpress installation for blogs.gnome.org, gnomejournal.org and www.gnome.org
  So what is the difference between blogs.gnome.org and wptest.gnome.org?
  Shared installation is not going to be possible without a bunch of overhaul.

• Put wordpress installation into Puppet?
  I don't see a need for this. The only dynamic content (themes, plugins) can be handled as git modules. WP installation is tracked via wordpress.org svn checkout.

After the launch

• Fix security issues in wppo plugin (since we won't use it right now)
• Audit all custom plugins for security issues

Comments

• for /start/stable and /start/unstable just do the same as now? ie. redirect to library and wiki.
  ovitters: HOW?

• torrent.gnome.org - http://wptest.gnome.org/start/

• i18n.gnome.org looks old, the info on the team workspace looks more up to date https://live.gnome.org/TranslationProject/

Redirects:

# ignore:
# /support
# /contest
# /faqs/
# /about
# /learn  (used to redirect to library.go)
# /contact
# /mobile/
# /images

RedirectPermanent /press/releases/ /press/
RedirectPermanent /community/ /get-involved/
RedirectPermanent /tour/ /
RedirectPermanent /resources/ /
RedirectPermanent /softwaremap/ /
RedirectPermanent /i18n/ http://live.gnome.org/TranslationProject#

Redirect /css/ http://www-old.gnome.org/css/
Redirect /fonts/ http://www-old.gnome.org/fonts/
Redirect /img/ http://www-old.gnome.org/img/
Redirect /friends/ http://www-old.gnome.org/friends/

# release-team stuff
Redirect /start/stable                   http://library.gnome.org/misc/release-notes/3.0
Redirect /start/unstable/schedule.ics    http://www-old.gnome.org/start/schedule-unstable.ics
Redirect /start/unstable                 http://live.gnome.org/TwoPointNinetyone
RedirectMatch ^/start/([0-9]+\.[0-9]*[02468])     http://library.gnome.org/misc/release-notes/$1
RedirectMatch ^/start/([0-9]+\.[0-9]*[13579])     /start/unstable

# old and in use redirects:
Redirect /projects/ http://projects.gnome.org/
Redirect /projects http://projects.gnome.org/
Redirect /start/getstable.html http://www-old.gnome.org/~davyd/footware.shtml
Redirect /rt3-stats http://www-old.gnome.org/rt3-stats
Redirect /updatelogs http://www-old.gnome.org/updatelogs

# TODO:
#  RewriteEngine On
#  RewriteRule ^/application_crashed.shtml(.*) http://bugzilla.gnome.org/simple-bug-guide.cgi?from_gnome_segv=1
#
#  # Yelp 2.16.x likely use this to redirect questions to gnomesupport. Removing this line breaks
#  # Yelp 2.16.x!
#  RewriteRule ^/yelp$ http://gnomesupport.org/forums/search.php?search_cat=1&search_keywords=%{QUERY_STRING} [R=303,L]
#
#  RewriteRule   ^/~(.+)  http://people.gnome.org/~$1  [R=301,L]