Comment 65 for bug 1049082

Bug reporting is like folding paper,

Origami can demonstrate it very well.

the 'shell of a bug report that i like to see is a envelope that has Classification 1 to 10 '
A good Bug reporting site has also 10 specific testimonials in form of what to report.
A brief note to developers from the <operator>( UI )-' in this section is where installation type or migraiting type bug's can make the Operator have difficulties . Many dependent variables make problems depending on hardware the end user has or if multisystem OS of hda etc. < End user / operator > will flag developers depending where or what he thinks caused chaos. That is where a good bug report ( UI ) will make developers or admin take a look at it. Bug reporting is like folding paper like origami to sort out so the end user or the operator will have what the aim was. I think we can use a lots from this as ( UI ) where each report is folded in the end to satisfy the end user. Classing the Bug's in sections depending on what is causing problems.

Makes bug reporting dynamic when we have enough information from the end user. Which we have to ask in the report so we can do a good assessment so the end user has origami which developers created the Ubuntu to be.

https://help.ubuntu.com/community/FoldingAtHome/origami#Ubuntu_PPA_.28.deb.29

We can use this as a engine since i looked at this and i think the principle is same for the model that Alberto Salvia Novella is wanting bug reporting that is like a recycle.

Let me know if i can help out better.

With all my respect,