Planet MySQL at a new URL

Did anybody notice that http://planetmysql.org now redirects to http://planet.mysql.com?

Curious to know the reason why, perhaps an official MySQL person can give us some details.
Also it’s a 302 redirect, not a 301 redirect, interesting?

 wget http://planetmysql.org
--2009-02-26 14:40:09--  http://planetmysql.org/
Resolving planetmysql.org... 213.136.52.29
Connecting to planetmysql.org|213.136.52.29|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.planetmysql.org/ [following]
--2009-02-26 14:40:10--  http://www.planetmysql.org/
Resolving www.planetmysql.org... 213.136.52.29
Connecting to www.planetmysql.org|213.136.52.29|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://planet.mysql.com/ [following]
--2009-02-26 14:40:10--  http://planet.mysql.com/
Resolving planet.mysql.com... 213.136.52.29
Connecting to planet.mysql.com|213.136.52.29|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

3 Responses to “Planet MySQL at a new URL”

  1. Dups says:

    Hey Ronald, nothing very serious, blog post coming soon, maybe today, maybe tomorrow, just some reconfiguration and code changes and allow us to use mysql.com logins more seamlessly etc.

    Cheers
    Dups

  2. Arjen Lentz says:

    Yea I figured it’d be for login purposes.
    Still, the nice thing about planetmysql.org was that it was a community thing, not aimed at getting leads for MySQL or whatever.
    With logins, that changes. Not sure that’s a good idea.

  3. Adam Donnison says:

    “the nice thing about planetmysql.org was that it was a community thing, not aimed at getting leads for MySQL or whatever.
    With logins, that changes.”

    Why? How does a login (that is not mandatory) change it from a “community thing” (whatever that means) into something else?

    Planet.mysql.com is a community resource and always will be. It lives on the same infrastructure as the other .mysql.com sites (as it has for the last 3 years), and was, until this change, a separate codebase that required separate maintenance, and if we wanted to do combined stuff was a pain. Should I mention “Sakila Points” at this point? With this change we now use the same codebase as the main sites, with a lot better capability to provide the integration that you sought a few years back.