launchpad development|
Size: 1455
Comment:
|
Size: 2549
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from LEP/OpinionStatus | |
| Line 3: | Line 4: |
| ''There should be a way to decline working on bugs without closing down discussions in the bug report.'' | ''There should be a way to close bugs without closing down discussions in the bug report.'' |
| Line 5: | Line 6: |
| '''As a ''' $PERSON<<BR>> '''I want ''' $FEATURE<<BR>> '''so that ''' $BENEFIT<<BR>> ''Consider clarifying the feature by describing what it is not?'' ''Link this from [[LEP]]'' |
'''As a ''' bug supervisor for a project<<BR>> '''I want ''' a way to reject bugs without shutting down continued conversation<<BR>> '''so that ''' bug lists only have relevant bugs for me but community members can continue discussing issues.<<BR>> |
| Line 15: | Line 12: |
| ''Why are we doing this now?'' | === Why do this now? === |
| Line 17: | Line 14: |
| ''What value does this give our users? Which users?'' | Bugs continue to be filed against Launchpad that experience status toggling wars as developers seek to remove bugs from Launchpad workflows but users want them re-opened for discussion. === What value does a new approach provide? === If we had a way to remove bugs from bug lists on Launchpad while leaving discussion open, both developers and users would be happy. |
| Line 21: | Line 22: |
| ''Who really cares about this feature? When did you last talk to them?'' | * Mark Shuttleworth * Any bug supervisor for a project |
| Line 25: | Line 27: |
| ''What MUST the new behaviour provide?'' ''What MUST it not do?'' == Subfeatures == ''Other LaunchpadEnhancementProposal``s that form a part of this one.'' |
* Keep the number of statuses to a minimum * Developers must not be confused by the choices offered in the status menu * Marking a bug in this way must not have the social impact of closing the discussion * Marking a bug in this way must remove the bug from developer bug lists * It must be easy to review bugs marked in this way |
| Line 35: | Line 35: |
| ''What are the workflows for this feature?'' ''Provide mockups for each workflow.'' |
Current suggestions have been to add a status called OPINION. The new status would behave exactly as WONTFIX and INVALID behave now. |
| Line 38: | Line 37: |
| '''''You do not have to get the mockups and workflows right at this point. In fact, it is better to have several alternatives, delaying deciding on the final set of workflows until the last responsible moment.''''' | XXX: What about ACLs? |
| Line 42: | Line 41: |
| ''How will we know when we are done?'' | We will know we have been successful when discussions continue independent of the state of the bug and without cause bug status to toggle needlessly. |
| Line 44: | Line 43: |
| ''How will we measure how well we have done?'' | XXX: Actual stats/metrics still to be added to this LEP. |
| Line 48: | Line 47: |
| ''This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the first part of our release change log. It is mandatory.'' | Bug Supervisors can make use of a new status, OPINION, which will mark a bug closed but is meant to indicate discussions are free to continue in the bug. |
| Line 52: | Line 51: |
| ''Put everything else here. Better out than in.'' | There has been some email discussion between Deryck, Jono L., and Mark about the name of the status. OPINION seems the best anyone can come up with but is still problematic due to the fact that it's purpose is not that clear. Status names that were discussed and rejected include: * POLICY * DESIGN * MOOT * DELIBERATE * INTENDED * STYLISTIC * FEATURE * OUTOFSCOPE * CONFAB * RAPSESSION * DIGRESSION Status names that have been proposed and are still being considered include: * DISCUSSION * DISPUTED * ONGOING * INDISCUSSION * COMMENTING * CONVERSATION * DIALOG * DEBATE * TALK |
Close Bugs, while Leaving Discussions Open
There should be a way to close bugs without closing down discussions in the bug report.
As a bug supervisor for a project
I want a way to reject bugs without shutting down continued conversation
so that bug lists only have relevant bugs for me but community members can continue discussing issues.
Rationale
Why do this now?
Bugs continue to be filed against Launchpad that experience status toggling wars as developers seek to remove bugs from Launchpad workflows but users want them re-opened for discussion.
What value does a new approach provide?
If we had a way to remove bugs from bug lists on Launchpad while leaving discussion open, both developers and users would be happy.
Stakeholders
- Mark Shuttleworth
- Any bug supervisor for a project
Constraints
- Keep the number of statuses to a minimum
- Developers must not be confused by the choices offered in the status menu
- Marking a bug in this way must not have the social impact of closing the discussion
- Marking a bug in this way must remove the bug from developer bug lists
- It must be easy to review bugs marked in this way
Workflows
Current suggestions have been to add a status called OPINION. The new status would behave exactly as WONTFIX and INVALID behave now.
XXX: What about ACLs?
Success
We will know we have been successful when discussions continue independent of the state of the bug and without cause bug status to toggle needlessly.
XXX: Actual stats/metrics still to be added to this LEP.
Release Note
Bug Supervisors can make use of a new status, OPINION, which will mark a bug closed but is meant to indicate discussions are free to continue in the bug.
Thoughts?
There has been some email discussion between Deryck, Jono L., and Mark about the name of the status. OPINION seems the best anyone can come up with but is still problematic due to the fact that it's purpose is not that clear.
Status names that were discussed and rejected include:
- POLICY
- DESIGN
- MOOT
- DELIBERATE
- INTENDED
- STYLISTIC
- FEATURE
- OUTOFSCOPE
- CONFAB
- RAPSESSION
- DIGRESSION
Status names that have been proposed and are still being considered include:
- DISCUSSION
- DISPUTED
- ONGOING
- INDISCUSSION
- COMMENTING
- CONVERSATION
- DIALOG
- DEBATE
- TALK
