Mozillians/Releases/1.3/March 6 2012
From MozillaWiki
< Mozillians | Releases | 1.3
Tuesday Mar 6th 10:30am PDT.
- Vidyo: 370; Conf 9370.
Agenda
- Responsive Design (tallOwen)
- Search Results UX (bram)
- Admin Panel (tofumatt)
- Locations (tofumatt)
- Taskboard Update (timw)
- Releasing? (tofumatt/aakashd/all)
- Vouching (aakashd)
Notes
Responsive Design
- Nearing completion;
- the tests pass and its not ideal; itd be good to put on master
- mbrandt is sync'd up on the possible areas of concern to test
Search Results UX Here are some things to be discussed in terms of search:
- We talked about searching by groups as opposed to other keywords. To clarify that groups are not people’s name (or other kinds of information), can we mark groups in the search box? Essentially, we want it so that, when a user type a group name, he will see a list of possible groups and be able to select from it. Very similar to our group adding feature.
- There are some “red herring” search terms that a lot of people will search for. We need to tailor our search result page (SRP) for each:
- “Firefox” – in the SRP, put “Did you mean Firefox for Desktop, Firefox for Mobile, Firefox Home?”
- “Mozilla” – in the SRP, put “Did you mean Mozilla Foundation, or the team that works on various Mozilla products”
- Any product name by itself (Firefox, Thunderbird) – in the SRP, in addition to displaying people, we should display related tags. “People work in many departments within Firefox, like <group>, <group>, <group>”
- Commonly misidentified group – Websites > WebDev, Mozillians > Engagement, Support > SUMO, Feedbacks > Input, extension, theme > Addons, Marketplace
- Name change – when people type BrowserID, we should display both BrowserID and Mozilla Persona, because it’s the same thing. AMO and Marketplace is also another case.
- General keywords like “Help”, “Contribute” – in the SRP, put “Which area within Mozilla would you like to contribute to? <group>, <group>, <group>”
- Rewords:
- Consider clarifying “groups” into something that’s more descriptive, like “what I’m working on”? Or put this on the description field. Avoid just calling it Groups.
- “Skills” could be “things I can do and programs and languages I know”
- I can review design changes from tallOwen
Admin Panel
- code's ready to go and on dev
- need IT to serve up the media
- Aakash will take a look at it to check against the reqs
Taskboard Update
Releasing?
- Look at Wednesday/Thursday code changes and determine day to release
- Migrations aren't working for user profile
- The Matt's will follow-up on changes made and qa time
- Milos will need to give us a heads up on timing
- Post-release
Vouching
