Skip to content
This repository was archived by the owner on Jul 21, 2021. It is now read-only.

MVP

Jump to bottom
Harald Kirschner edited this page Oct 1, 2015 · 11 revisions

Summary

The platform feature status board is a highly visible offline-first reference app that serves Web Developers as a hub to look up the status of proposed to implemented web features. The data will be maintained on Github by the Platform and WebAPI team.

Users

Web developers: Learn about Mozilla's platform roadmap and standardization efforts.

Platform/WebAPI team: Maintain standards and roadmap status in one place.

Themes/Use Cases

Browse: About users informing themselves about the platform status.

Participate: How the roadmap drives participation, build community and feature adoption.

Maintain: Covers Mozillians keeping the roadmap updated.

Epics/User Stories

Offline-first (Browse): As a user I want to access the feature list even when I am offline.

Mobile-first (Browse): As a user I want to access the board on my various devices to look up status (Responsive for mobile/tablet/desktop display, mouse/keyboard/touch input).

Searchable (Browse): As a user I want to search specific features.

Linkable (Browse): As a user I want to share a link to a specific feature.

Read more (Browse): As a user I want to read more about a feature with links to the spec, announcements and documentation.

Compatibility (Browse): As a user I want to see the standardization involvement/opinion and implementation status for other browsers/platforms.

Follow progress (Browse/Participate): As a user I want links to bug trackers and mailing lists to follow/participate in the discussion and development.

TBD …

Dependencies

  • Mozilla's WebAPI and Platform team & community will need to update the data as features evolve.
  • TBD: Define process to maintain this with constantly moving standards, bugs and implementation
    • Update data in sync with Release Notes
    • Are We Tracking It Yet (Health Check)
      • Verify/Sync roadmap data against
        • Sync with Trello's Platform tracking
        • Tracking bug
        • MDN compatibility tables
        • Microsoft/Chrome/Safari data

TBDiscussed

Roadmap data

Each feature is defined by

  • References/Links
    • Proposal/Spec
    • Tracking bug
    • MDN
    • Announcement/Hacks blog
    • Standards Mailing list
    • Mozilla Developer Mailing list
    • Preffed off
  • Status
    • Standardization: No Public Discussion, Working Draft, Editor's Draft, Established Standard
    • Implementation (per platform/browser): No Public Signals, Not Currently Planned, Under Consideration, In Development, Shipped since X (Un-prefixed since Y, Un-preffed since Z)

TBDiscussed: Data storage options

  • JSON
    • Example: MicrosoftEdge/Status
    • Hard to maintain without an additional tool
    • No good history of commits per feature
  • Markdown with YAML Front Matter for meta data
    • One file per feature can be categorized in folders
    • File might end up containing more meta data than content (title, summary)

References

Prior Art

[1]:

Clone this wiki locally