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

MVP

Jump to bottom
overholt edited this page Nov 2, 2015 · 11 revisions

Introduction: https://github.com/mozilla/platatus/blob/master/README.md

Users

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

  • Casual browser that just want to see cross-browser status
  • Experienced developers that want more details

Platform 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

v1

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).

Find a single feature (Browse): As a user I want to search specific features.

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

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

v2

Hot Features (Browse): As a user I want see which features are hot.

Linkable (Browse): As a user I want to share a link to a specific feature and find it in a search engine.

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

v3

Health Check (Maintain): As a maintainer I want to see which features need attention (see Health Check).

Browse by release (Browse): As a user I want see new features by browser version.

Dependencies

  • Mozilla's Platform team & community will need to update the data as features evolve.

Health Check

Define process to maintain this with constantly moving standards, bugs and implementation

  • Update data in sync with Release Notes
  • Sources, verify/Sync roadmap data against:
    • Sync with Trello's Platform tracking
    • Tracking bug
    • MDN compatibility tables
    • CanIUse
    • Microsoft/Chrome/Safari data

Roadmap data

Each feature is defined by

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

Depth: 1-level depth (features can have another feature as parent feature, ES6 > [Classes, …] Example Webkit)

  • Tree allows splitting up complex specs like ServiceWorker
  • Chrome's guidelines for adding a new feature (doesn't track the parent relationship):

    Would this feature ship in isolation from the other features in the spec? Would we mention this feature in isolation in a Chromium blog post feature update post (eg the posts for 26, 25, 24)?

Decided: Data storage

  • 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

See Also/Prior Art

Clone this wiki locally