ubuntu-bugcontrol team mailing list archive
-
ubuntu-bugcontrol team
-
Mailing list archive
-
Message #03991
Re: Work-flow prototype
Work-flow illustrates *both *pile importance and typical bug flow:
* Bug *flow* begins with step 1, and ends with step 5.
* But pile *importance* is the opposite: the highest importance is for
step 5, and the lowest is for step 1.
Although people can *freely choose* where to contribute:
* They're *clearly shown* where help is more needed.
* They're *asked to stop* working when next step is congested.
*So* work-flow:
* First *liberates congestion* at the end of the flow, so previous
steps begin to move too.
* Is *visual* how work is flowing, so it's also easy to improve it and
choose where to work.
* Creates value *constantly* to the Ubuntu OS, so also constant
improvements in users' satisfaction and constant returns to the project.
* Takes advantage of *every piece of work* done, and makes work much
more *easier to understand*. So users will be much more prone to help.
* Changes the need to check for errors in the hole report to checking
only if previous step was okay, making the process zero-defects
and*mistake resistant*.
* Since errors in bug handling are not discovered in latter steps, but
immediately in next step, this also makes the management to
*accelerate*.
And for *warranting* this work-flow will respond well to any situation,
I designed it testing over the "Ubuntu" project, not the "One Hundred
Papercuts" project only. So only step 1 is specific to papercuts management.
On the other hand, it's very probable I'll *divide* step 4 (fix a
papercut) into more steps. So please subscribe
<https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Work-flow?action=subscribe>
to the page and you'll receive notifications when work-flow is changed.
Thank you 😊
El 23/01/14 19:51, Dario Ruellan escribió:
Loved it!
Then, looking again to your 5 steps workflow, you're illustrating the
preferred "priority" for each bug-pile. NOT the actual bug workflow,
but the preferred workflow as a Papercutter, right?
On Thu, Jan 23, 2014 at 10:20 AM, Alberto Salvia Novella
<es20490446e@xxxxxxxxx <mailto:es20490446e@xxxxxxxxx>> wrote:
Here it is the explanation: the Bug Stream Map
<https://bugs.launchpad.net/hundredpapercuts/+bug/1049082/+attachment/3955080/+files/Bug%20Stream%20Map.pdf>.
On the other hand, I expect the One Hundred Papercuts work-flow
<https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Work-flow> to
change over time since, rather than details, what's relevant here
is the main concept.
If you *wanted to help* improving this prototype work-flow but
without leaving working in your projects, you can easily reuse the
work-flow in your desired project and give feedback.
Just open one of the lists
<https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Work-flow> and
change, in your web-browser's *direction*, "hundredpapercuts" by
the desired project's short name (for example, "ubuntu").
https://bugs.launchpad.net/*hundredpapercuts*/+bugs?field.searchtext=...
Good day 🌞 <http://youtu.be/bS6B8zC2CNI>
El 20/01/14 16:35, Dario Ruellan wrote:
Really like the idea. The links to the launchpad lists alone are
insanely handy.
I'm also wondering about the order. Waiting to read the proper
explanation.
On Jan 19, 2014 7:36 AM, "Alberto Salvia Novella"
<es20490446e@xxxxxxxxx <mailto:es20490446e@xxxxxxxxx>> wrote:
Can you make me a *favour*?
*Next time* you wanted to manage some bugs, please give this
little baby
<https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Workflow>
a *try*; and then some (picky) *feedback*.
Have a nice day 🎏
--
Ubuntu-quality mailing list
Ubuntu-quality@xxxxxxxxxxxxxxxx
<mailto:Ubuntu-quality@xxxxxxxxxxxxxxxx>
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
--
Darío Ruellan Google Profile
<http://www.google.com/profiles/dario.ruellan> Linkedin
<http://www.linkedin.com/in/darioruellan> Twitter
<http://www.twitter.com/druellan>
Information Technology Professional
17CC 5A20 2F75 610F BB0F
57A2 9D7F 54F3 5705 DDD3
References
