MDN/Archives/Projects/Development/CompatibilityTables/Project meetings/2016-01-19
From MozillaWiki
< MDN | Archives | Projects/Development/CompatibilityTables | Project meetings(Redirected from MDN/Projects/Development/CompatibilityTables/Project meetings/2016-01-19)
Contents
Browser Compat Project Meeting: 01/19/2016
Discussion topics
Project Kick Off
- People in charge
- End of year goal:
- Having browsercompat.org
- being a standalone data service with its own set of contributors
- having an agile, continuous delivery process
- providing compatibility data both in read and write mode
- with MDN being its first client
- Having MDN:
- Displaying better and more reliable browser compatibility data
- Displaying browser compatibility data in different and more contextual ways
- Displaying more compatibility data about new browser/environment
- Providing a smooth contribution pathway to browsercompat.org
- Having browsercompat.org
- Methodology: we intend to be agile, but at that point we won't rely on a formal methodology like scrum.
- A central point of information
- Everything being discussed publicly on:
- the MDN mailing list for things related to project management and highlevel priorities
- the DEV-MDN mailing list for things related to project development
- the https://lists.mozilla.org/listinfo/dev-mdc DEV-MDC mailing list] for all things related to MDN content and MDN integration
- ALL those mailing lists to be informed about the key events of the project.
- Bugzilla as the canonical source of information for the day-to-day implementation work of everything. An operational dashboard will be built on top of it.
- A Bi-weekly meetings to review the deliverables and to discus the priorities.
Project milestones
- Skateboard (Proof of concept) This is our current state
- Having some compat. tables on MDN display with BC data for beta users
- Data being scraped manually from MDN with the BC importer
- Bicycle We need to get into details to check the exact feasibility
- Having a contribution interface for admins -> needed first to make maintenance simpler and fix some basic importer issues
- Scooter We need to get into details to check the exact feasibility
- Having data being scraped automatically from MDN with the BC importer
- Motorbike (Production ready) We need to get into details to check the exact feasibility
- Having all compat. tables on MDN display with BC data for beta users
WARNING: This means going from 20 converted pages to about 4300 converted pages, about 1400 of which have data issues
- Having all compat. tables on MDN display with BC data for beta users
- Car (1st official public release)
- Having all compat. tables on MDN display with BC data for all users (including l10n)
- Having an authentication mechanism able to handle different levels of privileges to access the BC API/UI
- Having the continuous deployment infrastructure up and ready for deploying new code/features for BC with at least two target environments (staging/prod)
- Plane (1st stabilisation release)
WARNING: we need to make sure the time between Car and Plane is short to avoid too much burden for data contributors, therefor we need to know the velocity of change to estimate what time is "acceptable"- Having all compat data removed from MDN content
- Having a fully working contribution UI usable by any contributor.
- Kill the data importer
- Space ship (1st improvement release)
- Having compat data display in more contextual ways on MDN
- Enable SSO between MDN and BC
- T.A.R.D.I.S (To Infinity And Beyond, or… http://bit.ly/1ZGUEuT )
- ? API V3 based n user feedback
- ? Independent product management
- ? Third party clients other than MDN
IMPORTANT: The current status of the project does not allow to provide any formal deadline on any of the milestone. We wish to reach the Plane milestone by end of year, but at that point it's only a wish.
Decision made
- Everybody agreed with the suggested methodology for the project… we'll see how it goes
- Everybody is okay with the goals for the year, but they need a formal agreement from Ali and Lonnen.
- A first draft of highlevel milestones has been define. It appears that the overall complexity seems very high so further discussion are needed to make sure it is broken into doable pieces.
Action taken
- Jeremie: Get a formal approval for project goals
- Jeremie: Push forward the discussion about the expected milestones