canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Features/Lifecycle of a feature: Difference between revisions
m
→Team List (required)
| Line 48: | Line 48: | ||
* '''Security''': Contact the Security team so they can evaluate your feature and decide whether it will need a security review. If it does, add the Security team contact person's name here. | * '''Security''': Contact the Security team so they can evaluate your feature and decide whether it will need a security review. If it does, add the Security team contact person's name here. | ||
* '''Privacy''': Contact the Privacy team so they can evaluate your feature and decide whether it will need a privacy review. If it does, add the Privacy team contact person's name here. | * '''Privacy''': Contact the Privacy team so they can evaluate your feature and decide whether it will need a privacy review. If it does, add the Privacy team contact person's name here. | ||
=== Use Cases (required) === | |||
Both user-facing and developer-facing features need to have use cases defined prior to a Feature being submitted to the Inbox. This is how the Product Team knows what a feature is about and how they figure out how to prioritize it. Without uses cases, your feature will be bounced back to you until those are defined. | |||
=== The other stuff (not required, but useful!) === | === The other stuff (not required, but useful!) === | ||