Support/Goals/2011Q3/Identity Documentation): Difference between revisions

Latest revision as of 15:35, 30 June 2011

Feature	Status	ETA	Owner
Identity SUMO Content Creation	Working on initial concept	2011-09-30	Ibai Garcia

Summary

A set of articles and templates that explains the processes and potential issues of using Identity/Browser ID. The goal is to have an initial set ready with the Beta launch of the Service in Q3.

Team

Who's working on this?

Goal Manager: Ibai Garcia
Lead Developer:
Product Manager: Dan Mills
UX:

Team list should make it clear who to ask about what, and who to ping when they're needed.

Goals

To draft, write and review SUMO articles to cover the "expected" most popular uses cases of Browser ID.
Set up an easy access to the content (i.e. link) so the beta users can find the information after the launch.

Project Plan

Initial topic selection by Product and SuMo
Propose list of topics and discuss with the Community
Draft of the articles
Finalize and review articles
Decide with Product and UX how drive user with issues to support.
Implement support path.

Non-Goals

The goal for this quarter doesn't involve the full localization of the content.
This project doesn't aim to cover every possible issue but to have an initial collection of articles before the official launch.

Additional Documentation

Identity Roadmap

Legend (remove if you like)

	Healthy: feature is progressing as expected.
	Blocked: feature is currently blocked.
	At Risk: feature is at risk of missing its targeted release.
ETA	Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.

@@ Line 9: / Line 9: @@
 | [[Identity SUMO Content Creation]]
 | {{StatusHealthy|status=Working on initial concept}}
-| YYYY-MM-DD
+| 2011-09-30
 | Ibai Garcia
 <section end="status" />
@@ Line 16: / Line 16: @@
 == Summary ==
-A set of articles and templates that explains the processes and potential issues of using Identity/Browser ID. The goal is to have an initial set ready with the Beta launch in Q3.
+A set of articles and templates that explains the processes and potential issues of using Identity/Browser ID. The goal is to have an initial set ready with the Beta launch of the Service in Q3.
 == Team ==
@@ Line 24: / Line 24: @@
 * '''Lead Developer''':
 * '''Product Manager''': Dan Mills
-* '''QA''':
 * '''UX''':
-* '''Security''':
-* Etc.
-Team list should make it clear who to ask about what, and who to ping when they're needed.  If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.  Contact info for each person would also be handy.
+Team list should make it clear who to ask about what, and who to ping when they're needed.
-== Release Requirements ==
+== Goals ==
-Complete checklist of items that need to be satisfied before we can call this feature "done".
+* To draft, write and review SUMO articles to cover the "expected" most popular uses cases of Browser ID.
+* Set up an easy access to the content (i.e. link) so the beta users can find the information after the launch.
-== Next Steps ==
+== Project Plan ==
-Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
+# Initial topic selection by Product and SuMo
+# Propose list of topics and discuss with the Community
+# Draft of the articles
+# Finalize and review articles
+# Decide with Product and UX how drive user with issues to support.
+# Implement support path.
-== Open Issues ==
+== Non-Goals ==
-Unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.
+* The goal for this quarter doesn't involve the full localization of the content.
+* This project doesn't aim to cover every possible issue but to have an initial collection of articles before the official launch.
-== Related Bugs & Dependencies ==
-Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
-== Designs ==
-N/A
-== Use Cases ==
-Everyone loves use cases, so you should provide them if you can (and where it makes sense).  The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.
-== Test Plans ==
+== Additional Documentation  ==
-Any and all test plans and strategies.  Either inline or linked to.
-== Goals ==
+*[[Identity]] Roadmap
-The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
-== Non-Goals ==
-Things we are specifically not doing or building as part of this feature.
-== Other Documentation ==
-Can include things like:
-* Competitive landscape
-* Research & references
-* Whatever else is useful to the project.
 == Legend (remove if you like) ==
@@ Line 81: / Line 65: @@
 __NOTOC__
-Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 [[Category:Features]]
 [[Category:Firefox]]
-[[Category:Platform]]
 [[Category:Services]]
-[[Category:Mobile]]
-[[Category:Other]]