Feature Page Structure: Difference between revisions

Feature Page Structure (view source)

442 bytes removed , 31 March 2011

m

no edit summary

canmove, Confirmed users, Bureaucrats and Sysops emeriti

6,906

edits

@@ Line 16: / Line 16: @@
 == Summary ==
-One or two paragraphs outlining what we're building and why.  Should be enough so that uninvolved readers will know whether or not they want to learn more about the project.
+Very succinct (one or two line) summary of what this feature is all about.
+== Team ==
+Who's working on this?
+* '''Lead Developer''':
+* '''Product Manager''':
+* '''QA''':
+* '''UX''':
+* '''Security''':
+* Etc.
+Team list should make it clear who to ask about what, and who to ping when they're needed.
 == Release Requirements ==
@@ Line 26: / Line 38: @@
 == 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.
-== Team ==
-Should start with a short intro explaining that this is the current set of team leads, but anyone is welcome to dive in and help out.
-Team list should make it clear who to ask about what, and who to ping when they're needed.  Not all team members will be actively involved with the project at all times, but we should have an idea of who will be the touchpoint for each involved group (PM, marketing, devs, UX, graphic design, services, webdev, QA, etc etc)
-Team info should include notes about where they hang out in IRC, if there's a mailing list, etc.
 == Designs ==