MDN/Archives/Projects/Development/CompatibilityTables: Difference between revisions

From MozillaWiki
< MDN‎ | Archives
Jump to navigation Jump to search
 
(32 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Web compatibility tables (WCT) are one of the key feature of MDN. It allows users to know more about the reliability of any web standard features and to ease the use of web technologies. Currently, the data are gather and maintain "by hand". Thanks to our awesome community we have some good data. However, this is hardly sustainable as the number of technologies is growing as well a the complexity of the implementation. We start to face some difficulties to stay up to date and to provide and improved content around those data.
Web compatibility tables (WCT) are one of the key features of MDN. They allow users to know more about the reliability of any web standard feature and to ease the use of web technologies. Currently, the data is gathered and maintained "by hand". Thanks to our awesome community we have some good data. However, this is hardly sustainable, as the number of technologies is growing as well as the complexity of the implementations. We start to face some difficulties to stay up to date and to provide and improve content regarding this data.


= Goals =
= Goals =


Goals and how we see the project is elaborated in the [https://wiki.mozilla.org/MDN/Projects/Development/CompatibilityTables/Vision '''Vision Document''']
Long terms goals and how we see the project is elaborated in the '''[[MDN/Projects/Development/CompatibilityTables/Vision|Vision Document]]'''


'''NOTE''': Initial goal elaboration is commented in this page.
== 2016 Planning ==


<!--
An actionable breakdown is available in the [[MDN/Projects/Development/CompatibilityTables/Milestones|project milestones page]].
This project intend to cover the following goals:


* Improving the quality and display of data
End of year goals:
** Avoid misleading users with inaccurate data.
*** '''NOTE:''' ''This is our primary concern as misleading users is the worst thing we could do on MDN (as a bad side effect it could induce distrust of Mozilla).''
** Make sure our data are coherent all across MDN.
*** '''NOTE:''' ''This is our secondary most important concern for the same reason as the first one (even if the side effect could only affect MDN rather than Mozilla).''
** Allow compatibility data to scale technically with a proper data schema
** Allow simple and complex compatibility data to be properly display in a responsive environment
* Easing data contribution
** Allow (and automate) massive data contribution
** Allow easier single in-site contribution
*** '''NOTE:''' ''This is our third most important concern as it impacts contributors right now. By easing the contribution we ensure to improve both the quality and quantity of data, but we also pleased our contributors which ultimately contribute to the good reputation of both MDN and Mozilla.''
* Easing access to data
** Provide a way to allow third party tools or web sites to use our data
** Allow importation of data from third party resources
* Allowing the reuse of data within MDN
** Make data reachable through KumaScript
** Make data usable for filtering research


* At the end of the year, browsercompat.org must
** be a standalone data service with its own set of contributors
** have an agile, continuous delivery process
** provide compatibility data both in read and write mode
** have MDN to be its first client
* At the end of the year, MDN must:
** Display better and more reliable browser compatibility data
** Display browser compatibility data in different and more contextual ways
** Display more compatibility data about new browsers/environments
** Provide a smooth contribution pathway to browsercompat.org


'''NOTE:''' ''This project is action driven rather than time driven. It means that we do whatever is needed to reach our goals, whatever the time it requires. However, in order to not to be swamped into an endless project, we try to cut into small actionable steps that allows to measure progress as often as possible.''
= Current stats =


-->
Current milestone: [[MDN/Projects/Development/CompatibilityTables/Milestones/Bicycle|Bicycle]] (frozen)
Achievement: '''46%'''
 
* [https://docs.google.com/presentation/d/1Ly5B705D4CkMJjQgVGUndBSAPJ7ktbkLZwdr5EaQlGk/edit?usp=sharing Project assessment]
* [https://docs.google.com/spreadsheets/d/1YgUVcvXxY0ocdThTdKzFTwR83OEiP1wF-uet7UjB9dQ/edit?usp=sharing Project dashboard]
* [[MDN/Projects/Development/CompatibilityTables/Milestones|Full milestones breakdown]]
* [[MDN/Development/CompatibilityTables/Infrastructure|Infrastructure]] (target)
 
Deprecated (to be archived):
* Temporary [https://docs.google.com/document/d/1J8Ip8NjXTcnMcsOg4OWtvWvT1vCgQnMU3_Ug7HB9m64/edit short term plan]
* Next release spec.: [https://docs.google.com/document/d/1J8Ip8NjXTcnMcsOg4OWtvWvT1vCgQnMU3_Ug7HB9m64 BC Skateboard]
 
== Meeting minutes ==
Public project meeting occurs every two weeks on Tuesday at [http://arewemeetingyet.com/UTC/2016-01-19/18:00/b/Browser%20Compat%20Project%20Meeting 18:00 UTC] in the [https://v.mozilla.com/flex.html?roomdirect.html&key=gMM1xZxpQgqiQFNkUR3eBuHgxg MDN Vidyo room].
 
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-03-15|03/15/2016]]
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-03-01|03/01/2016]]
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-02-26|02/16/2016]]
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-02-02|02/02/2016]]
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-01-19|01/19/2016]]
* [[MDN/Projects/Development/CompatibilityTables/Project_meetings/2016-01-03|01/03/2016]]
 
== Bugzilla raw backlog ==
 
List of all open bugs for the project. The objective is to reach 0 ''major'' and ''normal'' bugs for milestones other than ''TARDIS''
 
Main tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=compat-data
<bugzilla>
{
  "whiteboard": "[bc:",
  "f1" : "bug_status",
  "n1" : 1,
  "o1" : "equals",
  "v1" : "RESOLVED",
  "f2" : "bug_status",
  "n2" : 1,
  "o2" : "equals",
  "v2" : "VERIFIED",
  "include_fields": "id, summary, status, severity, whiteboard"
}
</bugzilla>


= Get Involved =
= Get Involved =
Line 37: Line 70:


==Who's in charge?==
==Who's in charge?==
[[User:Jeremie_Patonnier|Jeremie Patonnier]] is the resource leading that project, feel free to contact him for any question. He's available, on IRC under the nickname '''Jeremie''' and follows typical work hours within the Central European time-zone.


Responsibilities for the project are define through the following RASCI matrix:
Responsibilities for the project are define through the following RASCI matrix:
* [[Media:MDN_-_RACI_-_Compat_Data.pdf | MDN — RACI — Compat Data (PDF)]]
* [[Media:MDN_-_RACI_-_Compat_Data.pdf | MDN — RACI — Compat Data (PDF)]]
The main contact points are the following:
* Project Management: [https://mozillians.org/fr/u/Jeremie/ Jeremie Patonnier] (Europe [http://www.timeanddate.com/time/zones/cet CET])
* Dev lead: [https://mozillians.org/fr/u/jwhitlock/ John Whitlock] (US [http://www.timeanddate.com/time/zones/cst CST])
* UX/Front-end lead: [https://mozillians.org/fr/u/stephaniehobson/ Stephanie Hobson] (Canada [http://www.timeanddate.com/time/zones/pst PST])
* Data and MDN content management: [https://developer.mozilla.org/en-US/profiles/Teoli Jean-Yves Perrier] (Europe [http://www.timeanddate.com/time/zones/gmt GMT])
== Join the discussion and meet the team ==
A public project meeting occurs every two weeks on Tuesday at [http://arewemeetingyet.com/UTC/2016-01-19/18:00/b/Browser%20Compat%20Project%20Meeting 18:00 UTC] in the [https://v.mozilla.com/flex.html?roomdirect.html&key=gMM1xZxpQgqiQFNkUR3eBuHgxg MDN Vidyo room]. Everybody is welcome to attend.
Beside the project meeting, everything is discussed on mailing lists:
* [https://lists.mozilla.org/listinfo/dev-mdc dev-mdc]: Functional discussion (Features prioritization, data, content, UX)
* [https://lists.mozilla.org/listinfo/dev-mdn dev-mdn]: Technical discussion (Architecture, QA, Dev work)
* [https://lists.mozilla.org/listinfo/mdn mdn]: Project management discussion (Prioritization, status, decision)
On a daily basis, the team members are available for discussion during their respective working hours on [[IRC]]:
* on the #mdn channel (functional).
* on the #mdndev channel (technical).


==How to help?==
==How to help?==


Depending on your skills, this project offer many contribution opportunities:
Depending on your skills, this project offers many contribution opportunities:
 
===Development===
 
The data repository is a full Django application, so if you know Python, Django and HTML/CSS/JS you're welcome to help.
 
* [https://github.com/mdn/browsercompat Source code on GitHub]
* [https://browsercompat.readthedocs.org/en/latest/ Browser Compat API documentation]


===Developpement===
===UX & Design===
===UX & Design===
Displaying and contributing data in a way that makes it understandable and usable by everyone is quite challenging. If you are skilled in design and UX, your help is more than welcome.
===Data Management===
===Data Management===
Our data is currently hosted on MDN itself and we need some help to clean and normalize it and do the transition to our new data repository. If you want us to move faster, this is where your help is needed and it doesn't required any particular skills. :)


* [[MDN/Development/CompatibilityTables/Importer|Learn about importer errors]]
* [[MDN/Development/CompatibilityTables/Importer|Learn about importer errors]]
Line 56: Line 117:
== Tracking tools ==
== Tracking tools ==


* [https://trello.com/b/whnNVWBA/compatibility-data-project Project Trello board]
* [http://mzl.la/1P0n4b5 Bugzilla]
 
* [https://docs.google.com/spreadsheets/d/1YgUVcvXxY0ocdThTdKzFTwR83OEiP1wF-uet7UjB9dQ/edit?usp=sharing Project dashboard]
= Current progress =
* [https://trello.com/b/whnNVWBA/compatibility-data-project Project Trello board] (outdated & unmaintained)
Project meeting to be schedule.
 
== Bugzilla status ==
Main tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=compat-data
<bugzilla>
    {
        "blocks":"989448",
        "bug_status":"RESOLVED",
        "bug_status_type":"not_equals",
        "include_fields": "id, summary, status, assigned_to"
    }
</bugzilla>


= Archive =
= Archive =


The project is now two years long then we have some outdated document that we keep for information purpose but be aware that they are no longer canonical for the project.
The project is now two years old and we have some outdated documents that we keep for information purposes, but be aware that they are no longer canonical for the project.


* [[MDN/Projects/Development/CompatibilityTables/Useful ressources|Useful ressources]]
* [[MDN/Projects/Development/CompatibilityTables/Useful ressources|Useful ressources]]
* [[MDN/Projects/Development/CompatibilityTables/Project status|Project Status for 2014/2015]]
* [[MDN/Projects/Development/CompatibilityTables/Project status|Project Status for 2014/2015]]

Latest revision as of 19:47, 19 June 2017

Web compatibility tables (WCT) are one of the key features of MDN. They allow users to know more about the reliability of any web standard feature and to ease the use of web technologies. Currently, the data is gathered and maintained "by hand". Thanks to our awesome community we have some good data. However, this is hardly sustainable, as the number of technologies is growing as well as the complexity of the implementations. We start to face some difficulties to stay up to date and to provide and improve content regarding this data.

Goals

Long terms goals and how we see the project is elaborated in the Vision Document

2016 Planning

An actionable breakdown is available in the project milestones page.

End of year goals:

  • At the end of the year, browsercompat.org must
    • be a standalone data service with its own set of contributors
    • have an agile, continuous delivery process
    • provide compatibility data both in read and write mode
    • have MDN to be its first client
  • At the end of the year, MDN must:
    • Display better and more reliable browser compatibility data
    • Display browser compatibility data in different and more contextual ways
    • Display more compatibility data about new browsers/environments
    • Provide a smooth contribution pathway to browsercompat.org

Current stats

Current milestone: Bicycle (frozen) Achievement: 46%

Deprecated (to be archived):

Meeting minutes

Public project meeting occurs every two weeks on Tuesday at 18:00 UTC in the MDN Vidyo room.

Bugzilla raw backlog

List of all open bugs for the project. The objective is to reach 0 major and normal bugs for milestones other than TARDIS

Main tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=compat-data

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Get Involved

Any one who wish to get involved with this project is welcome. This page will provide information about the project and its progress. Everything is discuss directly on the dev-mdn mailing list. Schedule and progress are summarized on the the mdn mailing list.

Who's in charge?

Responsibilities for the project are define through the following RASCI matrix:

The main contact points are the following:

Join the discussion and meet the team

A public project meeting occurs every two weeks on Tuesday at 18:00 UTC in the MDN Vidyo room. Everybody is welcome to attend.

Beside the project meeting, everything is discussed on mailing lists:

  • dev-mdc: Functional discussion (Features prioritization, data, content, UX)
  • dev-mdn: Technical discussion (Architecture, QA, Dev work)
  • mdn: Project management discussion (Prioritization, status, decision)

On a daily basis, the team members are available for discussion during their respective working hours on IRC:

  • on the #mdn channel (functional).
  • on the #mdndev channel (technical).

How to help?

Depending on your skills, this project offers many contribution opportunities:

Development

The data repository is a full Django application, so if you know Python, Django and HTML/CSS/JS you're welcome to help.

UX & Design

Displaying and contributing data in a way that makes it understandable and usable by everyone is quite challenging. If you are skilled in design and UX, your help is more than welcome.

Data Management

Our data is currently hosted on MDN itself and we need some help to clean and normalize it and do the transition to our new data repository. If you want us to move faster, this is where your help is needed and it doesn't required any particular skills. :)

Tracking tools

Archive

The project is now two years old and we have some outdated documents that we keep for information purposes, but be aware that they are no longer canonical for the project.