Next steps restoring hosted loco team websites (meeting summary)

[Matthew Nuzum]

Hello everyone, here is a quick summary of the meeting today regarding
the canonical sponsored loco team web hosting.

Since you're subscribed to this list, you've probably already seen
this e-mail, but you may want to read over it again, since it is still
pertinent <https://lists.ubuntu.com/archives/loco-contacts/2007-August/001510.html>

In a nutshell, if you are using one of the "approved" webapps listed
in that e-mail, you are welcome to use the hosting provided by the
Canonical sysadmin team in the London based Canonical data center
(CDC).

If you are not using an approved application and don't feel migration
to a supported application is possible, the US based servers will
still be maintained, but not allocated the same administrative
resources that the CDC hosted sites will receive.

All of the above means, "don't worry, everything is going to be OK." ;-)

Sites that had PHP, CGI or other executable code need to make
arrangements to have that code replaced, since it could be
compromised.

Also, each site will need to make arrangements for getting their site
set up in the proper place.

To do this, follow these steps:
 * Log into #canonical-sysadmin on freenode and ask for help migrating
your existing loco site. The first available sysadmin will contact you
to make proper arrangements. As always, be patient. Loco teams far
outnumber sysadmins.
 * Contact us to make sure we can make DNS changes for your site by
filing a bug against the loco-webhosting project in launchpad
<https://launchpad.net/loco-webhosting>. This process is not
instantaneous unfortunately.

If you do not yet have Canonical sponsored hosting but would *like* to
have hosting, please understand that there will be a slightly longer
than usual delay, then follow the existing instructions at
<https://wiki.ubuntu.com/LoCoHosting>

Thanks for your cooperation as we work through this event.
-- 
Matthew Nuzum
newz2000 on freenode