Confirmed users
503
edits
DevMo Project Plan Notes: Difference between revisions
m
Reverted edit of Oiyzytrk, changed back to last version by RyanJones
No edit summary |
m (Reverted edit of Oiyzytrk, changed back to last version by RyanJones) |
||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 7: | Line 7: | ||
The Mozilla Developer Network is an organized and carefully maintained collection of resources for the international community of Web Developers, Mozilla ISVs, and Mozilla Contributors. | The Mozilla Developer Network is an organized and carefully maintained collection of resources for the international community of Web Developers, Mozilla ISVs, and Mozilla Contributors. | ||
=== Resources to Include === | |||
* Documentation | * Documentation | ||
* Training and Educational Materials | * Training and Educational Materials | ||
| Line 14: | Line 14: | ||
* Community support infrastructure, including forums, mailing lists, weblog hosting, and/or whatever else could be useful | * Community support infrastructure, including forums, mailing lists, weblog hosting, and/or whatever else could be useful | ||
The guiding principles for the Network are that it be: | === Guiding Principles === | ||
The guiding principles for the Mozilla Developer Network are that it be: | |||
* Usable | * Usable | ||
* Practical | * Practical | ||
| Line 36: | Line 37: | ||
== Strategies == | == Strategies == | ||
Taken as a whole, this project is entirely too large to tackle at once. The project needs to be broken up into manageable components, each of which will be developed independently | Taken as a whole, this project is entirely too large to tackle at once. The project needs to be broken up into manageable components, each of which will be developed independently and later integrated into the greater whole. | ||
Each of the | Each of the “Components�? discussed below should be thought of as independent projects. Sorting out which to work on first will be a matter of prioritization. | ||
Keys to this | Keys to this project’s long term success: | ||
* Components need to support and reflect open standards as much as possible, if not completely. | * Components need to support and reflect open standards as much as possible, if not completely. | ||
| Line 65: | Line 66: | ||
# Mozilla Contributors subsite front end | # Mozilla Contributors subsite front end | ||
=== Mozilla Documentation Library === | === Mozilla Developer Documentation Library === | ||
Single repository of all Mozilla-created and hosted developer documentation, including: | Single repository of all Mozilla-created and hosted developer documentation, including: | ||
* Product and Reference documentation | * Product and Reference documentation | ||
| Line 71: | Line 72: | ||
* Task specific procedural documentation ("Cookbook"-style) | * Task specific procedural documentation ("Cookbook"-style) | ||
* FAQs | * FAQs | ||
* Knowledge Base | * Developer Knowledge Base | ||
* Annotated sample code and other examples | * Annotated sample code and other examples | ||
* Whitepapers | * Whitepapers | ||
| Line 86: | Line 87: | ||
Single repository of all Mozilla-created and hosted developer tools, including sidebars, Venkman, validators, Bugzilla, Bonsai, Tinderbox, etc, including links to Documentation Library resources for each tool (docs, education center resources, FAQs/Knowledge Base, etc.) | Single repository of all Mozilla-created and hosted developer tools, including sidebars, Venkman, validators, Bugzilla, Bonsai, Tinderbox, etc, including links to Documentation Library resources for each tool (docs, education center resources, FAQs/Knowledge Base, etc.) | ||
=== Mozilla | === Mozilla Contributor’s Dashboard === | ||
This is | This is Chase’s idea – create a system that allows us to display the current status of bugzilla, tinderboxen, bonsai, etc on the front page of the Mozilla Contributor’s subsite. | ||
=== Mozilla Community Commons === | === Mozilla Community Commons === | ||
| Line 107: | Line 108: | ||
# Sort through the existing documentation and other relevant content we have and figure out what state it's in. This has been started at [[Links to Existing Content]]. | # Sort through the existing documentation and other relevant content we have and figure out what state it's in. This has been started at [[Links to Existing Content]]. | ||
# Start moving still-valuable content into the wiki within the basic structure. | # Start moving still-valuable content into the wiki within the basic structure. | ||
# Start promoting the wiki within the existing developer community. Hopefully | # Start promoting the wiki within the existing developer community. Hopefully they will take the time to update, edit, and add new content where they see errors, problems, or holes. | ||
they will take the time to update, edit, and add new content where they | |||
see errors, problems, or holes. | |||
# Finish branding and layout modifications for the wiki. Create and brand an initial portal/news-weblog system, then launch to a wider audience. At that point, if we've done things properly, it will start to take on a life of its own (with some serious care and feeding in the background). | # Finish branding and layout modifications for the wiki. Create and brand an initial portal/news-weblog system, then launch to a wider audience. At that point, if we've done things properly, it will start to take on a life of its own (with some serious care and feeding in the background). | ||
=== Medium Term === | === Medium and Long Term === | ||
Once we have the short term goals taken care of and an initial site launched, we'll have a better grasp of where to go from there. At that point we'll evaluate possible options and formulate a new set of short and medium term goals. | |||
== Other Notes and Ideas == | == Other Notes and Ideas == | ||
Moved to [[Other DevMo Notes and Ideas]]. | Moved to [[Other DevMo Notes and Ideas]]. | ||