Features/Inbox: Difference between revisions

No edit summary
(the person meets inbox first, then meets "was: inbox, is: landed")
 
(29 intermediate revisions by the same user not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
{{ForceRefreshButton}}
{{ForceRefreshButton}}
Ubuntu has bite size bugs, that is, easy to patch bugs. Also, you had to implement a feature to show a window's parents in the window like Preferences -> Advanced -> General, but there was not enough time, because the feature was too hard to implement. Also, if two features are equally important, you should implement the easy one first, then the hard one last, because you'll start working in the unmentioned medium ones faster. So there should be a column with Difficulty (easy, medium or hard) and Length (short, medium or long) in the Inbox feature tables, then the "By Associate Project" feature tables, then finally the hard and long, but extremely tasty "By Team" feature tables.
== Feature Inbox ==
== Feature Inbox ==
=== How to propose a new feature ===
=== How to propose a new feature ===
Line 10: Line 9:
<tr>
<tr>
<td class="header" style="width: 30%;">Feature</td>
<td class="header" style="width: 30%;">Feature</td>
<td class="header" style="width: 13%;">Feature list</td>
<td class="header" style="width: 23%;">Feature list</td>
<td class="header" style="width: 39%;">Status</td>
<td class="header" style="width: 29%;">Status</td>
<td class="header" style="width: 18%;">Last modified</td>
<td class="header" style="width: 18%;">Last modified</td>
</tr>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature stage::Feature Inbox]]
{{#ask: [[Category:Feature Page]] [[Feature stage::Feature Inbox]]
Line 20: Line 20:
| ?Feature status note#
| ?Feature status note#
| ?Modification date
| ?Modification date
| mainlabel=-
| mainlabel=-
| sort=Feature list
| sort=Feature list
Line 26: Line 27:
}}
}}
</table>
</table>
<h2> Was: Inbox, Is: Landed </h2>
<p>[https://wiki.mozilla.org/What%27s_new%3F Exception to Silent: What's new?]
</p>


== Unprioritized: Need attention ==
== Unprioritized: Need attention ==
Line 31: Line 36:
<table class="querytable sortable">
<table class="querytable sortable">
<tr>
<tr>
<td class="header" style="width: 30%;">Feature</td>
<td class="header" style="width: 20%;">Feature</td>
<td class="header" style="width: 10%;">List</td>
<td class="header" style="width: 10%;">List</td>
<td class="header" style="width: 15%;">Stage</td>
<td class="header" style="width: 15%;">Stage</td>
Line 37: Line 42:
<td class="header" style="width: 15%;">Feature manager</td>
<td class="header" style="width: 15%;">Feature manager</td>
<td class="header" style="width: 15%;">Lead engineer</td>
<td class="header" style="width: 15%;">Lead engineer</td>
</tr>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature priority::Unprioritized]] [[Feature stage::!Draft]] [[Feature stage::!Feature Inbox]] [[Feature stage::!On hold]]
{{#ask: [[Category:Feature Page]] [[Feature priority::Unprioritized]] [[Feature stage::!Draft]] [[Feature stage::!Feature Inbox]] [[Feature stage::!On hold]]
Line 46: Line 52:
| ?Feature feature manager#
| ?Feature feature manager#
| ?Feature lead engineer#
| ?Feature lead engineer#
| mainlabel=-
| mainlabel=-
| sort=Feature list
| sort=Feature list
Line 58: Line 65:
<table class="querytable sortable">
<table class="querytable sortable">
<tr>
<tr>
<td class="header" style="width: 30%;">Feature</td>
<td class="header" style="width: 20%;">Feature</td>
<td class="header" style="width: 13%;">Feature list</td>
<td class="header" style="width: 23%;">Feature list</td>
<td class="header" style="width: 39%;">Status</td>
<td class="header" style="width: 39%;">Status</td>
<td class="header" style="width: 18%;">Last modified</td>
<td class="header" style="width: 18%;">Last modified</td>
</tr>
</tr>
{{#ask: [[Category:Feature Page]] [[Feature stage::On hold]]
{{#ask: [[Category:Feature Page]] [[Feature stage::On hold]]
Line 69: Line 77:
| ?Feature status note#
| ?Feature status note#
| ?Modification date
| ?Modification date
| mainlabel=-
| mainlabel=-
| sort=Feature list
| sort=Feature list

Latest revision as of 20:47, 27 July 2012

Feature Inbox

How to propose a new feature

To propose a new feature for any of our products, you must first create a feature page for it, here: Create a new feature page. When you change your feature's "Stage" to "Feature Inbox" it will magically appear on this list. The Product team goes through this list regularly, evaluating and prioritizing each item.

Inbox

{{#ask: Feature stage::Feature Inbox | ?# | ?Feature name# | ?Feature list# | ?Feature status note# | ?Modification date | mainlabel=- | sort=Feature list | format=template | template=4ColTable }}
Feature Feature list Status Last modified

Was: Inbox, Is: Landed

Exception to Silent: What's new?

Unprioritized: Need attention

These are items that have somehow skipped the Inbox and are not yet prioritized.

{{#ask: Feature priority::UnprioritizedFeature stage::!DraftFeature stage::!Feature InboxFeature stage::!On hold | ?# | ?Feature name# | ?Feature list# | ?Feature stage# | ?Feature product manager# | ?Feature feature manager# | ?Feature lead engineer# | mainlabel=- | sort=Feature list | format=template | template=6ColTable | limit=500 }}
Feature List Stage Product manager Feature manager Lead engineer

On hold

Items here are usually "on hold" until we get more information or details.

{{#ask: Feature stage::On hold | ?# | ?Feature name# | ?Feature list# | ?Feature status note# | ?Modification date | mainlabel=- | sort=Feature list | format=template | template=4ColTable }}
Feature Feature list Status Last modified

Needs feature page

Roadmap Team Feature Status Proposed by
Layout Layout Pretty Borders Needs a feature page or a feature page to live on. fantasai / Anil
UX, Security (many) Application Reputation for downloaded executables Needs feature page, Deb has pinged Lucas & Sid. Jesse Ruderman