WebAPI/Docs schedule: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(20 intermediate revisions by one other user not shown)
Line 18: Line 18:
|TCP Socket API||April 18||[https://developer.mozilla.org/en-US/docs/WebAPI/TCP_Socket Done]
|TCP Socket API||April 18||[https://developer.mozilla.org/en-US/docs/WebAPI/TCP_Socket Done]
|-
|-
|Contacts API||April 19||
|Contacts API||April 19||[https://developer.mozilla.org/en-US/docs/WebAPI/Contacts Done]
|-
|-
|Settings API||April 19||
|Settings API||April 19||[https://developer.mozilla.org/en-US/docs/WebAPI/Settings Done]
|-
|-
|Idle API||April 24||Everything is already done except the intro/guide article.
|Idle API||April 24||[https://developer.mozilla.org/en-US/docs/WebAPI/Idle Done] ([https://developer.mozilla.org/en-US/docs/tag/Idle complete])
|-
|-
|Web Bluetooth||April 27||Assuming the API is stable enough, which it should be. ''Planning to work on this during the Vancouver doc sprint.''
|Web Bluetooth||April 27||Assuming the API is stable enough, which it should be. ''Planning to work on this during the Vancouver doc sprint.''
|-
|-
|Permissions API||April 27||''Planning to work on this during the Vancouver doc sprint.''
|Permissions API||April 27||[https://developer.mozilla.org/en-US/docs/WebAPI/Permissions Done]
|-
|-
|Mobile Connection API||April 27||''Planning to work on this during the Vancouver doc sprint.''
|Mobile Connection API||April 27||[https://developer.mozilla.org/en-US/docs/WebAPI/Mobile_Connection Done]
|-
|-
|Power Management API||April 27||Everything is already done except the intro/guide. ''Planning to work on this during the Vancouver doc sprint.''
|Power Management API||April 27||[https://developer.mozilla.org/en-US/docs/WebAPI/Power_Management Done] ([https://developer.mozilla.org/en-US/docs/tag/Power%20Management complete])
|-
|-
|Network Stats API||April 27||''Planning to work on this during the Vancouver doc sprint.''
|Network Stats API||April 27||[https://developer.mozilla.org/en-US/docs/WebAPI/Network_Stats Done]
|-
|-
|WiFi Information API||???||''Depends on the implementation status, which is not currently known.''
|WiFi Information API||???||''Depends on the implementation status, which is not currently known.''
Line 45: Line 45:
!API!!Estimated completion date!!Notes
!API!!Estimated completion date!!Notes
|-
|-
|Ambient Light Events||April 27||Nearly finished already. ''Planning to work on this during the Vancouver doc sprint.''
|Ambient Light Events||April 27||[https://developer.mozilla.org/en-US/docs/tag/Ambient%20Light Done]
|-
|-
|Proximity Events||May 15/16||[https://developer.mozilla.org/en-US/docs/tag/Proximity Done], actually a lot sooner than expected.
|Proximity Events||May 15/16||[https://developer.mozilla.org/en-US/docs/tag/Proximity Done]
|-
|-
|Screen Orientation||May 22/23||
|Screen Orientation||May 22/23||Both [https://developer.mozilla.org/en-US/docs/tag/Screen%20Orientation Screen Orientation] and [https://developer.mozilla.org/en-US/docs/tag/Device%20Orientation Device Orientation]
|-
|-
|Battery Status||May 23/24||Nearly finished already.
|Battery Status||May 23/24||[https://developer.mozilla.org/en-US/docs/tag/Battery Done].
|-
|-
|Alarm API||May 24||Nearly finished already.
|Alarm API||May 24||[https://developer.mozilla.org/en-US/docs/tag/alarm Done].
|-
|-
|Time/Clock API||May 29/30||
|Time/Clock API||May 29/30||[https://developer.mozilla.org/en-US/docs/tag/Time Done]
|-
|-
|WebFM API||May 30/31||
|WebFM API||May 30/31||[https://developer.mozilla.org/en-US/docs/tag/WebFM Done]
|}
|}


Line 66: Line 66:
!API!!Estimated completion date!!Notes
!API!!Estimated completion date!!Notes
|-
|-
|Device Storage API||June 5/6||
|Device Storage API||June 5/6||[https://developer.mozilla.org/en-US/docs/tag/Device%20Storage Done] but we need to document some related API such as FileHandle.
|-
|-
|TCP Socket API||June 6/7||
|TCP Socket API||June 6/7||[https://developer.mozilla.org/en-US/docs/tag/TCP%20Socket Done]
|-
|-
|Browser API||June 12/14||
|Browser API||June 12/14||[https://developer.mozilla.org/en-US/docs/tag/Browser Done]
|-
|-
|Contacts API||June 19/21||
|Contacts API||June 19/21||[https://developer.mozilla.org/en-US/docs/tag/Contact Done]
|-
|-
|WebSMS||June 26||We have fairly good documentation here, so this will be a clean up and enhancement round.
|WebSMS||June 26||[https://developer.mozilla.org/en-US/docs/tag/WebSMS Done] (''There are still things missing but the API is far from stable, so not sure it worth the effort to go deeper'')
|-
|-
|WebTelephony||June 26||We have fairly good documentation here, so this will be a clean up and enhancement round.
|WebTelephony||June 26||[https://developer.mozilla.org/en-US/docs/tag/Telephony Done]
|-
|-
|Settings API||June 26||
|Settings API||June 26||[https://developer.mozilla.org/en-US/docs/tag/Settings Done]
|-
|-
|Web Bluetooth API||June 27/28||
|Web Bluetooth API||June 27/28||
Line 90: Line 90:


However, we do not currently have resources allocated for this work. That said, we hope to hire a writer in time to have them do this work.
However, we do not currently have resources allocated for this work. That said, we hope to hire a writer in time to have them do this work.
[[Category:Web APIs]]

Latest revision as of 23:52, 1 October 2014

After our April 12 WebAPI meeting, the following schedule was prepared, estimating when various APIs will be documented.

We are documenting these APIs in phases as described below.

Phase 1: Basic Coverage for All APIs

The first phase involves having basic content with a brief summary for each API, as well as complete reference material for all of the APIs not already documented. This phase should be completed by the end of April. Outline of the order in which writing will be done, and estimates for completion dates per API.

API Estimated completion date Notes
Proximity API April 17 Done
Time/Clock API April 17 Done
WebFM API April 18 Done
TCP Socket API April 18 Done
Contacts API April 19 Done
Settings API April 19 Done
Idle API April 24 Done (complete)
Web Bluetooth April 27 Assuming the API is stable enough, which it should be. Planning to work on this during the Vancouver doc sprint.
Permissions API April 27 Done
Mobile Connection API April 27 Done
Power Management API April 27 Done (complete)
Network Stats API April 27 Done
WiFi Information API ??? Depends on the implementation status, which is not currently known.

Phase 2: Full documentation for all content-accessible APIs

The next phase is to fully-document all APIs accessible from unprivileged apps. This means having complete how-to documentation, as well as examples. These should be finished by the end of May.

Note: The contractor doing the majority of the writing is on PTO from April 29 to May 13.

API Estimated completion date Notes
Ambient Light Events April 27 Done
Proximity Events May 15/16 Done
Screen Orientation May 22/23 Both Screen Orientation and Device Orientation
Battery Status May 23/24 Done.
Alarm API May 24 Done.
Time/Clock API May 29/30 Done
WebFM API May 30/31 Done

Phase 3: Full documentation for all Certified APIs

By the end of June, we should have complete documentation for all stable certified APIs.

API Estimated completion date Notes
Device Storage API June 5/6 Done but we need to document some related API such as FileHandle.
TCP Socket API June 6/7 Done
Browser API June 12/14 Done
Contacts API June 19/21 Done
WebSMS June 26 Done (There are still things missing but the API is far from stable, so not sure it worth the effort to go deeper)
WebTelephony June 26 Done
Settings API June 26 Done
Web Bluetooth API June 27/28

At this point, our contractor's contract will expire, and what happens from there out is theoretical, but we are in good shape if we hold to this schedule.

Phase 4: In-depth tutorials

Once basic documentation is complete by the end of June, we would like to proceed to write more in-depth tutorials for the most important APIs, as well as to show better how to use them together, as well as in concert with Firefox OS UX building blocks as appropriate.

However, we do not currently have resources allocated for this work. That said, we hope to hire a writer in time to have them do this work.