Notes from mozilla.org planning meeting on 1/7
davidwboswell
present: fantasai, davidwboswell, reed
- p1 bugs
Staging site -- Reed is almost finished with this but still needs to
sort out how to handle merging conflicts.
Truncated pages -- We've fixed the truncated pages we've found out
about but we're not sure how extensive this may be so it's worth
trying to scan for other truncated pages. Reed wants to take a look
at the conversion script used in the relaunch and can see if there are
bugs. fantasai also suggested just diffing between the end of current
files and files on archive site.
- Content
We discussed how we should prioritize content updates -- we could go
by which pages get the most traffic or which pages have the most
important content. The first option includes product related pages
like the Mozilla Suite start page and the second option includes the
top-level section pages.
We felt that giving priority to the pages that are getting the most
traffic made sense, but these pages are in relatively good shape. We
decided to focus on improving the pages with important content and in
general want to start with the About section, move to the Community
section and then work on the Causes section.
One thing to keep in mind while we go through things is that as we
update pages, we can look into removing overlap with similar content
on mozilla.com. For instance, now that we've updated the Get Involved
page, there's a bug open to remove the Get Involved page on
mozilla.com and link people to the mozilla.org version instead. Other
pages where this could apply include the mozilla.com Many Faces page
and Contact pages. To help us think through more about this, David
will post a wiki page with a list of overlapping content.
- Design
We discussed moving forward with cleaning up site wide design issues,
specifically media queries and the overflow problem with clipped
pages. Fixing these could either be something that group does or it
could be something we contract out and review (this goes back to the
discussion at the last meeting about the group transitioning from an
execution to planning/reviewing role). David and fantasai to meet and
review open CSS bugs to figure out next steps.
- Localization
Reed will look into the issue with the environment variable that
fantasai needs to set up the localization system on the site after he
finishes the staging changes. Once there's an estimate about when the
staging and environment variable issues will be fixed, David will talk
to Pascal and Seth about their schedules for web localization this
year.
- Back-end
Reed mentioned a fix for the recent security issue with home page feed
(bug 537659). This was fixed quickly, but highlights the need for us
to be reviewing the activity of a wider group of contributors and
contractors. David and Reed to talk soon about best way to deal with
this.
We discussed how to move forward with Bespin work. Similar to the
media queries project, this could be something we as a group do or we
could look into bringing someone in to help us make this happen.
David and Reed to discuss more about this as well.
Chris Ilias
> Notes from mozilla.org planning meeting on 1/7
Oh jeez, I totally forgot about the meeting, even though I saw your
reminder. Sorry. :-(
I had a couple of questions I wanted to bring up:
1. Regarding the discussion about support.mozilla.org, is there a way to
find out how much traffic on www.mozilla.org/support/ is coming from
support.mozilla.org? Out of that traffic, what action are those visitors
taking (are they all clicking on the Firefox support link?). I think
that info would help decide what to do with that domain.
2. Is there any way to find out if support.css is still being used?
davidwboswell
Urchin? If not, I'm happy to look into it for you or help you get
access to Urchin to look things up.
David
> I had a couple of questions I wanted to bring up:
>
> 1. Regarding the discussion about support.mozilla.org, is there a way to
> find out how much traffic onwww.mozilla.org/support/is coming from
Chris Ilias
Not since SUMO moved to Omniture. Thanks.
davidwboswell
I just filed a bug to get you Urchin access.
https://bugzilla.mozilla.org/show_bug.cgi?id=538764
I also looked at the stats and support.css is still being used but it
looks like it's declining. I didn't see how to tell what traffic is
coming from support.mozilla.org but I might not have dug far enough.
Probably other ways beyond Urchin we could use too.
David