Building Safety Into Our Work

[David Callé]

On ven., 2011-05-20 at 23:04 +0200, Octavian Damiean wrote:
> On 2011-05-20 22:58, Jono Bacon wrote:
> > On Fri, 2011-05-20 at 14:55 -0600, Mike Basinger wrote:
> >> I think this need to be a key foundations of the power user community.
> >> Giving people the tools and info to tweak their system , but in a way
> >> that does not damage their installs or makes it difficult for the
> >> kernel/bug team to help people with bug reports.
> >>
> >> We have enough sites inside/outside of Ubuntu that say "hey install this
> >> deb/ppa/file" it awesome and then 10 minute later the person has an
> >> usable system.
> > It seems one simple approach is just throwing warning notices everywhere
> > before someone pulls the trigger, but I also wonder if there a better
> > way of categorizing different options into different levels of risk.
> >
> > This could arguably be performed within a tool such as Ubuntu Tweak.
> >

What about adding a visual difficulty/risk hint to our
tutorials/wikipages?
One wrench icon, two wrench icons, etc.

We could provide guidelines to determine the difficulty/risks of tasks:
* if it involves root access: 1 wrench
* if it involves more than two TTY: 2 wrenches
* if it involves root editing a conf file in Emacs before compiling a
customized kernel from a Mercurial branch: 4 wrenches
* if it involves looking more than five minutes at the Bugzilla
interface: 5 wrenches
You get the idea...