Websites/Mozillians.org/Meetings/June 2nd 2011

From MozillaWiki
Jump to: navigation, search

Mozillians.org Project Status Agenda

Backchannel: #mozillians

Following Up

Last week's TODOs...

  • Aakash - Clarify public, pending, mozillian throughout PRD
  • ozten, cshields - Create system architecture diagrams for mcoates and rforbes amusement
  • ozten - Follow up with Corey Shields on estimates
    • Add Raymond Forbes to roster
    • Ask legal for point person and if they want to attend meetings
      • Alex and Liz added to team roster, June 9th will be privacy/legal focused
    • Build Critical path and In Parallel timeline

Next Meeting June 9th

New Topics

  • Matej with copy update
    • See Next Actions
  • David or Monique with the design update
    • Due to amount of feedback, Mockups will be delivered incrementally and final will be June 10th instead of June 6th. David to coordinate end date estimates.
  • ozten with a LDAP Directory consultant update
    • Approval from HR, Operations budget
    • Waiting for Approval from Engagement budget
  • ozten Security Diagram update

Q:Did morgamic say we should re-evaluate LDAP?

No, he needed more context around why we hadn't contracted a resource yet. We documented the LDAP design decision. Timeline below documents where we are at with contract (75% done). Full steam ahead.

Development is scheduled during Open Source Bridge, which is a conference and webdev all-hands, so not much progress will be made that week (realistically).

Timelines

Mozilllians June2ndGantt.png

See the Timeline and Gantt chart spreadsheet for details.

Corey Shields notes that Infrasec bandwidth is tighter now and over the coming weeks, may become a risk for timeline.

Notes

Critical Path: If a task misses it's deadline by a day, then it slips the ship date by a day.

In Parallel: Tasks that aren't currently in the critical path.

Some dates in spreadsheet are 'fuzzy' and not updated by hand. They don't accurately account for weekends, but instead add 2 days to a 5 day estimate, etc.

Next Steps

[] ozten: Invite Legal to next meeting

[] David: Continue coordinating Copy with Matej (mockups, David and Aakash to write first cut at copy).