Thursday May 26th 3pm

3O - ORLY

x361

Agenda

Background

David and Aakash to talk about product vision.

Project idea has been around for years. Seth B pitched it on David's first day ;)

Many projects needed this key missing part - a Community phonebook. These projects would then snowball through feature creep into these overwhelming projects.

This might be the 4th attempt, but it's an organized and limited scope attempt. It is the basis for the Contributor Engagement group's future work.

There is a real need for this phonebook.

Stormy anecdote about trying to organize a speaker for an event, but the community was just too big and without a phonebook it seemed impossible.

After 1.0 there are many ideas for how to integrate Mozillians.org loosely with related Mozilla properties.

Project Minutia

The wiki page describing this project: https://wiki.mozilla.org/Websites/Mozillians.org

PRD https://wiki.mozilla.org/Mozillians/Releases/1.0

The tracking bug for this project: https://bugzilla.mozilla.org/show_bug.cgi?id=658621

ozten - A few words about our LDAP Directory plan. This is tentative, but:

Phase I - (during 1.0) consultant builds simple DIT, ACL, and tests

Phase II - Training for Ops and Webdev

Phase III - During a 1.x 'data privacy' feature release, consultant and this team working together on advanced ACL, DIT and test additions

thanks to Gerv for LDAP expert reference.

Q & A

Q: What will happen to the old phonebook?

Please join the discussion! https://intranet.mozilla.org/Websites/Mozillians/MoCo_Phonebook

Q: What kinds of users are their?

also

Q: What data will be shown?

Profile info in PRD.

Q: With two week sprints (after 1.0) will security review every release?

• functionality pieces
• unit testing, test security properties reduces time needed
• Major releases - longer reviews
• Smaller releases and good communication = organic security

Schedule

Rough Estimated Launch Date: TBD

Team by team, let's talk about rough estimates based on the 1.0 PRD.

• Copy/Design - Copy TBD, Monique shooting for June 6th for final mockups
• Development - tofumatt - 3 weeks assuming 2 people working with Gerv's Domesday, which gives us a big head start
  • These developers are commited to an Input release first. Then some snippets work, during Mozillians.org, which adds risk to the estimate
• LDAP Directory Consultant - TBD - 5 days (Phase I)
• L10n - stas - Usually 2 weekends, ozten to follow up
• Legal - TBD, usually locked into Copy cycle
• Operations - cshields (See TODO)
• QA - retornam 7-8 days of testing once staging is setup
• Security - mcoates
  • Project is high potential risk
  • 1st - review architecture, planned design diagrams (meeting, 1 week)
  • 2nd - security pass (2 weeks), couple days after QA

Future Meetings

Does this time, 30 min work for everyone?

 Word

Most will be marked optional, only attend in phases you want to participate in.

Works for me. (I was wrong before; timezone fail) -- tofumatt

Next Steps

[] Aakash - Clarify public, pending, mozillian throughout PRD

[] Aakash - Make chart of login states

[started] ozten, cshields - Create system architecture diagrams for mcoates and rforbes amusement

[x] ozten - Follow up with Corey Shields on estimates

[X] ozten - Add Raymond Forbes to roster

[X] ozten - Ask legal for point person and if they want to attend meetings

[X] ozten - Build Critical path and In Parallel timeline

Next Meeting

June 2nd