Notes from www.mozilla.org planning meeting on 9/3
davidwboswell
Present: david, reed, sam, kairo
- P1 Bugs
The bug about 404 errors for Firefox users is the only p1 open right
now. This continues to be a problem and we have had three duplicate
bugs filed about this already this week. Reed assigned the bug to
himself and will take a look at it soon.
https://bugzilla.mozilla.org/show_bug.cgi?id=491731
- New Design
The new design was deployed a couple of weeks ago. The only bug
remaining from the relaunch is related to the Community Ticker, but we
decided it is working well enough that we can fix this issue as part
of post-launch site polish (the ticker wasn't updating at all
initially and now it's just about an hour out of date). It also looks
like mozilla.com is going to have a sprint about a community ticker
coming up soon, so we could reuse some of that code if it's
appropriate for our needs.
In terms of triaging the remaining launch related tweaks, we're open
to suggestions about the best way to do that. If anyone interested in
QA wants to help, let us know. Our concern here is making sure we do
things in a standard way that will let people from other parts of the
community easily get up to speed with issues on the site.
We've had some requests to document how to get a version of the site
running locally (which is how edits to the previous build-system
version of the site were staged). Reed said he'd send out some basic
documentation soon and cleaning this up and making it more user-
friendly could be a good project for a new volunteer.
Gettng Bespin set up as the editor for the site looks like it will be
a week or two out. Reed said that he could get Kubla set up as a stop-
gap, but we didn't think this was necessary. People have been able to
edit the site (although there have been reports of problems with using
SSH+SVN) and we think waiting a short while won't be a problem. If it
looks like Bespin will take longer than a couple more weeks, we'll
revisit the Kubla option.
We're starting to see other sites start to adopt the new design. Are
we able to help people by providing templates that work with other
tools and also designs that are similar but not exactly like the
existing site? We don't really have any answers right now or the
ability to do any short-term designs projects about this, so we
decided just to monitor things.
- Archiving, Migrating and Updating Content
Now that the design is done and has provided the site with a new
global theme, our focus is on page-level work. The community group
has identified many projects it is interested in, but we need to
prioritize things. David has a page on the wiki with a list of
projects we've discussed and will post to the newsgroup to get people
to help fill in any holes and arrange things by priority.
https://wiki.mozilla.org/Mozilla.org/Content_priorities
We should also figure out what we can address ourselves and what we
need outside resources for -- for instance, for a project to design a
community dashboard do we have community members intererested in
design projects or do we need to work with a design agency?
For archiving and migrating, there's still more to do after the
relaunch and we'll need to figure out how to keep momentum here since
it's a low priority and low interest sort of project for most people.
- Localization
Now that we have the site on Subversion, we can start interacting with
the web l10n community, although we still need to sort out the
technical system we want to use on the site and identify the pages we
want to localize (since many pages are likely to change based on the
content priorities mentioned above this may only be a small number of
pages for now).
There was discussion about how busy the web l10n community is right
now, so we should be aware of this. Even if the localizers are busy,
we should at least start the process of engaging with them but keep
our expectations realistic.
- Testing
If anyone is interested in getting involved with site testing, this is
an area that has a lot of opportunities. For instance, Reed mentioned
how useful it would be to have an automated link checker set up. If
you'd like to get involved with this, let us know.
- Promo Spots
There have been a couple of requests to set up promos on the new site
since the relaunch and we decided for now just to handle things on an
ad hoc basic (file a bug and then get at least one owner or peer to
sign off). This would cover any promos on the home page or section
main pages. If we get a lot more requests we can come up with a more
formal process.
- Stats
MoCo is getting tools in place to help sites more easily do
optimization testing, so we should consider what we'd like to test.
For instance, can we test something related to rotating a different
message in on the home page?
- Search
Reed asked if we'd like to use the mozilla.com search infrastructure?
Sam mentioned we couldn't if it didn't search across many Mozilla
sites the way current search does. Instead we'll look into how we
could rebrand the existing Google-based search. Reed will set Sam and
David up with access to the Google search account and look into
contact information so we can follow up with any questions.