Introduction
"Kuma" is a project to redevelop the MDN website. We will leverage the Kitsune codebase that the new SUMO is built on and plan to customize it to fit our needs. The Kitsune knowledge base (KB) will replace the current Deki wiki, and we will be integrating the Kitsune support forums and discussion forums as needed. Kuma will also benefit from Kitsune l10n, administration, and social interaction features.
Goals
- Improve the MDN experience for developers, demo authors, and documentation contributors.
- Make it easier for planning, writing, and maintaining docs
- Make it discoverable to help developers find what they need
- Make it faster and more stable for visitors and contributors
- Make it extensible to allow rapid development of new features
- Create a more robust system for l10n contributors
- Better tracking and diffs so they know when we create new docs, update existing docs, or do anything for en-US
- Dashboard for l10n progress and monitoring so locales can better manage their work
Strategy and Planning
We plan to develop the initial functionality and test internally through a series of MDN 1.x releases, and will launch Kuma officially as MDN 2.0 when it's ready (tentatively Q42011).
Team Resources
The Kuma team uses various tools to manage their work, hold discussions, and track progress. These tools, and the differences between them, are outlined here.
Kuma Wiki
- Address: https://wiki.mozilla.org/MDN/Kuma
- Purpose: Track overall progress, share and collaborate on high-level details and (occasionally) lower-level details. An "outbound communication channel" that anyone can contribute to.
Basecamp
- Address: https://mozilla.basecamphq.com
- Purpose: Share assets (mockups, wireframes, etc.), provide feedback on those assets, and hold lengthy discussions
Bugzilla
- Address: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=Kuma&list_id=334028
- Purpose: Assign tasks and track resolutions. Much of the discussion that happens between assignment and resolution takes place on Basecamp.
Features
Feedback to consider
- UserVoice: Feedback on the current MDN website.
- Localization: We need to review and see what is possible based on the requests of localizers around the world.
Miscellaneous References
- Kuma related requirements/notes
- Wiki docs TOC - docs team is organizing content under a consistent hierarchy.
- etherpad from Luke+Jay+James meeting
- Other stuff
- MDN programs and projects - home for everything related to the Mozilla Developer Network
- MDN requirements - initial set of features and functionality we need for a good developer and documentation experience on MDN (more stuff will be added over time and a final PRD will be drafted soon)
- Kitsune roadmap and requirements - home for everything related to the next version of SUMO
- Overlap doc - early draft of the features that are shared between SUMO and MDN (more details will be added and unique features/tweaks for each application will be noted)
New MDN IA
MDN 1.0 PRD
A draft of the MDN 1.0 PRD lists most of the features that are needed to start the migration away from Deki. The document includes a list of features and their priorities.
Kitsune and overlap with SUMO
The documents below outline requirement overlap in SUMO and the MDN. We will collaborate with the SUMO development team to understand what is available in the Kitsune codebase and work through our requirements to build a solid foundation for the MDN website based on the Django framework.
Development
Comprehensive Feature List
A comprehensive list of features is provided below. Each feature has its own Wiki page that provides more detail and, in some cases, specific tasks that must be completed.
This list is a compilation and formalization of existing feature lists (including the feature EtherPad, the MDN 1.0 PRD, and the MDN / SUMO Shared Components PRD), and as such is fairly comprehensive.
Scrum
The Kuma team will be using Scrum to manage development. Please see the Scrum page and Scrum Guide for more information about the framework.
The team decided that it would be easiest to manage Scrum user stories with Bugzilla, and has written a guide for doing so. However, the team is interested in building a Scrum dashboard to make this process easier. Please see Jay's mockups, which provide our current vision for this dashboard.
Milestones
Artifacts and Progress
- Product backlog (all remaining features)
- Kuma 0.9.8
- Goal: "Polish MDN features and regain Kuma momentum."
- Sprint backlog (By assignee: Luke, Les, Craig, Jay, Unassigned)