Notes from websites task force meeting on 6/30/11
present: chrissie, cmore, liz, davidwboswell, alex, rsnyder, rafael
- Domain Name Changes
The big news since the last meeting is that the Thunderbird site has
moved from mozillamessaging.com to mozilla.org/thunderbird. There are
a few other public-facing sites using the mozillamessaging.com domain
but these will also be migrated off that domain or retired so that the
Mozilla Messaging domain will no longer be in use.
Chrissie also discussed plans for the upcoming move of the Firefox
pages on mozilla.com to mozilla.org/firefox and that will be happening
Liz brought up the issue about domains redirecting to sites that are
being moved and this highlights a general concern with the mess of
redirects covering all of our sites. David also gave an example of
some redirects he has seen the send some Thunderbird links through 4
hops (from mozilla.org > mozilla.com > messaging.com > mozilla.org).
It might be a good idea for someone to create a redirect sanity check
task force proposal just so people are aware that this is a general
concern to watch out for -- for instance, web QA may want to add
redirect issues to their testing checklist.
- Documenting Website Ownership
Chris is continuing to work on this and is looking to make searching
for and documenting sites into a regular process.
As of now he has identified around 260 production sites and the goal
is to have this number go down as we continue to retire abandoned
sites. Liz asked if abandoned sites that collect personal information
had priority for being archived. Chris said that they hadn't so far
but he would look into it.
- Universal Tab and Fonts
No update here, but the Universal Tab is scheduled for the Creative
team's Q3 goals.
- Universal Subtitles
Dean, who had discussed this proposal at an earlier meeting, wasn't on
the call but David had talked with him recently and this is still
something he is interested in. The goal is still for PCF to address
the technical issues and then we can set up an instance of this on a
Mozilla site to use as a case study before rolling it out more