One Hundred Papercuts will make Ubuntu shine

Bug #1049082 reported by Chris Wilson
80
This bug affects 14 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Fix Released
Critical
Alberto Salvia Novella

Bug Description

The Ubuntu experience is limited by plenty of small bugs. We are redesigning the "One Hundred Papercuts" project to make Ubuntu delightful by reducing them (https://blueprints.launchpad.net/hundredpapercuts/+spec/other-design-p-papercuts-shine).

This time we're trying the other way:
- Instead of planning so hardly, designing to deliver improvements continuously.
- Instead of working so hardly, warranting that every piece of work seizes useful.
- Instead of creating an impressive infrastructure, to make it simple and visual.
- Instead of marketing the project, to make it easy to recognize and to find.
- Instead of working in many aspects, to put all the workforce in the most important one now.

Although we will rather be working than commenting, your comments are very valuable and we will carefully look at them.

Thank you ♡

Changed in hundredpapercuts:
milestone: none → quantal-0-meta
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Chris Wilson (notgary)
Revision history for this message
Timothy Arceri (t-fridey) wrote :

- Did you know about the existence of the papercuts project before now?
Yes

- If so, how did you find out about it?
Various Linux news websites like omg ubuntu.

- What, from your point of view, are the weaknesses and limitation of the papercuts project?
Most of the 250 odd bugs currently in the papercuts project simply cannot easily be fixed (even though they do qualify as papercuts). There are many different reasons for this including:

 upstream not agreeing on the suggested change see: https://bugs.launchpad.net/hundredpapercuts/+bug/681872
fixes existing in GTK3 but not GTK2 (therefore not worth effort backporting) see: https://bugs.launchpad.net/hundredpapercuts/+bug/219385
uncertainty about who decides if a change should be made see: https://bugs.launchpad.net/hundredpapercuts/+bug/411964 and https://bugs.launchpad.net/hundredpapercuts/+bug/540826
slow repackaging of inherited debian packages see: https://bugs.launchpad.net/hundredpapercuts/+bug/498705 also search for description and you will find many others

Now if you continue to look though the current 250 odd bugs you will see many match the state of the above bugs. The *REAL* weakness of the papercuts project is that many of these bugs have been sitting there for years in order to fix 100 bugs per release there needs to be probably at least 200-300 new papercut bugs reported each release as probably half will either not qualify, be duplicates, or just as hard to fix as the above bugs. So in order to be able to fix 100 bugs we simply need a larger number of bugs tagged as papercuts.

- Why do you contribute to the papercuts project?

I'm a developer that likes fixing the odd bug bug dont have a large amount of time to contribute. I find papercuts maximise what I can give back in that short amount of time, also I like being able to easily contribute to multiple projects.

- Are you satisfied with the current state of the papercuts project

No, As I said above there needs to be more bugs tagged as papercuts I would like papercuts to expand to easyhacks (see LibreOffice easy hacks http://wiki.documentfoundation.org/Development/Easy_Hacks) bugs that can be fixed easily by developers not just user interface stuff like is currently targeted by papercuts.

- Do you think you will continue to contribute?

I would love to but I find it hard to target easy things to work on in my limited spare time.

I hope this insight is useful and I'm happy to answer any questions.

Revision history for this message
Jack Leigh (leighman) wrote :

Agreed, it seemed to start off more like easy hacks but more recently it became more constrained/bureaucratic which resulted in otherwise good bugs being discarded from the project.

description: updated
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Jack and Timothy, thanks a lot for your feedback. It is both valuable and insightful. It seems to me that the problems you describe stem from my particular interpretation of the definition of a papercut, since I've been the one most actively invalidating bugs in the papercuts backlog.

In the blueprint this bug links to, a few suggestions were raised regarding the definition of a papercuts, and whether or not it should remain as is. One suggestion was to expand the definition to cover popular apps from the archives, and another is to expand the project to cover all minor bugs on the CD, effectively replacing the 'Affects hunders papercuts' action with the 'bitssize' tag.

What do the two of you think of this, and do you have any other suggestions of your own?

Revision history for this message
Jack Leigh (leighman) wrote :

I think a wider range of minor bugs or an expansion of the bitesize scope seems like the way to go (as someone who was looking for bitesize bugs to get involved with recently).
The problem I would see with choosing by popularity is that perhaps those programs are popular because they have less of these small issues or they are more attentively dealt with by upstream.

Revision history for this message
Timothy Arceri (t-fridey) wrote :

"effectively replacing the 'Affects hunders papercuts' action with the 'bitesize' tag"

I personally dont like the idea of just having a tag. I like the hundred papercuts project because its a Project. Its easier to change a bugs status, milestone, etc, under hundred papercuts for example generally you cant change a bug to triaged in other projects unless you have permissions to that project which makes updating random bugs difficult.
 I also like that fact that the hundred papercuts project has a home page that shows contributing members this allows me to add this to my resume when applying for jobs (contributing to open source needs to be rewarding).

So anyway I like the idea of expanding the hundred papercuts scope but I would like it to remain a project rather than just reverting to being a tag added to bugs.

Changed in hundredpapercuts:
status: Confirmed → In Progress
Revision history for this message
U.W.D.Dhananjaya (dedunumax) wrote :

Now two days im struggling to start to contribute ubuntu. I didn't find a one to help yet :( everything here i can't start, I don't know why

Revision history for this message
Ricky Menne (menner-u) wrote :

I would really like to start contributing as much as I can as well. I'm a senior level Software engineering student and this is my first real day looking into how I can contribute to the open source community. I know this might be going in the wrong place, but if anyone can help point me in a direction to where I can get some starting material to work on that would be great. What I'd really like and once again I doubt this is the right place is if someone can hook me up with a mentor or someone who will take a little bit of time to help me get started. An IRC chat would be even better!

Thanks in advance!

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Ricky, you will find useful these teams:

- https://launchpad.net/~bugsquad
- https://launchpad.net/~papercuts-ninja

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

*********************
 SUGGESTED ACTIONS
*********************

1. Suggest the "hundredpapercuts" project in the "bugsquad" page as a possibility (https://launchpad.net/~bugsquad).

2. Suggest the "hundredpapercuts" project (again) in the "bugsquad" mail-list for those new members in the BugSquad (<email address hidden>).

3. Just let Ubuntu get a bit more of momentum, and the "hundredpapercuts" will get it too. The main problem, although Ubuntu is the most popular libre operating system, is it represents a minority; mainly because is a bit buggy for general adoption. So making our best debugging it is what we can do; and what in the medium term it will attract more users and computer professional to its bug fixing, and eventually to this project.

4. Ask yourself these questions:

- What I want Ubuntu to became, in detail.
- What kind of thoughts has someone who will get it.
- In which moments I feel I'm getting more closer to it.
- What I do different under these circumstances.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Excuse grammar: happens because of writing late at night!

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Now we have new branding.

Changed in hundredpapercuts:
assignee: Chris Wilson (notgary) → Papercutters (papercutters)
milestone: quantal-0-meta → none
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

The One Hundred Paper Cuts project logo, from the Ubuntu project.

© 2013 Alberto Salvia Novella (es20490446e)
© 2013 Canonical Ltd.

This logo is published under the CC-BY-SA 3.0 license from creativecommons.org, and it's part of the Ubuntu trademark property of Canonical Ltd.

The source vector graphic can be found at "http://www.safecreative.org/user/Alberto+Salvia+Novella".

summary: - The hundred papercuts project has lost contributors and direction
+ The hundred papercuts project needs serious planning
summary: - The hundred papercuts project needs serious planning
+ The hundred papercuts project needs to redefine its goals and planning
description: updated
summary: - The hundred papercuts project needs to redefine its goals and planning
+ The "hundredpapercuts" project needs to redefine its goals and planning
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote : Re: The "hundredpapercuts" project needs to redefine its goals and planning

My suggestion for fixing this bug is:

- To throw less at the problem.
- To cut objectives down.
- To cross-reference teams involved in debugging.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

I have edited the "hundredpapercuts" project description, so it can be more clean and focused. Observations are welcomed.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Ubuntu QA agreed to include a reference to the project in the wiki.

Revision history for this message
Dario Ruellan (druellan) wrote :

Hi Alberto. Thanks for all the work. I like the new logo, but I'm not so sure about the new description. Sadly, English is not my first language and it is difficult for me achieve a concise and clean redaction, but I believe something like this could be more concise and clear:

"Papercuts are small bugs that appear relatively easy to fix but have a noticeable impact on the user experience.
"Our goal is to improve Ubuntu's usability, fixing small annoyances and bugs that an average user could find on a default installation of Ubuntu Desktop"

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Thank you.

I would like to say that don't take any change I'm doing now too seriously, because it's mostly prototyping.

I find any comment like the one you just did of being valuable to figure out how things could be combined together. On the other hand, at this time and because I know myself, I will be changing my mind day to day in plenty of things.

So YES, I thing the project description could be improved; but perhaps, although I agree with the point of view and take it into account, I will perhaps be not doing it till I grow my understanding of how the project can be improved globally. But I promise that in the end One Hundred Papercuts will be a reflection of how all of us equally understand it.

Por otra parte, supongo que imaginarás que mi lengua nativa también es el Español; pero es lo que tiene haber dado clase durante doce años con un profesor nativo, negro y contestatario, al cuál le tengo mucho cariño.

Regards to all.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Ah, to say that Chris asked me to take on the leadership of this project. So my first and last instruction is not to call me project leader, but project coordinator.

Now I'm going to bed, expecting to dream with papercuts ☾

Revision history for this message
Dario Ruellan (druellan) wrote :

Oh, I figured out that could be the case, but since my Papercuts Ninja suscription expired (on porpuse, since I give up trying to catch some time for coding) and my papercutters re-apply is still waiting approval, I'm a bit off the loop.

About the description, I still believe we must start with a clear description about what a papercut is, and the scope of the proyect (Unity desktop only or other flavors, default apps or apps installed from the default repo, etc), and move on from there.

The idea of Papercuts Proyect as a nexus for cross-reference other teams is something that was discussed before and I still believe is a good idea, specially contacting upstream teams. The Rhythmbox experience contacting the upstream dev was wonderful, for example, an many bugs where fixed.

description: updated
description: updated
description: updated
description: updated
summary: - The "hundredpapercuts" project needs to redefine its goals and planning
+ The "hundredpapercuts" project shall redefine its goals and planning
summary: - The "hundredpapercuts" project shall redefine its goals and planning
+ The "hundredpapercuts" project shall make the Ubuntu experience to glaze
summary: - The "hundredpapercuts" project shall make the Ubuntu experience to glaze
+ The "hundredpapercuts" project shall make the Ubuntu desktop to glaze
summary: - The "hundredpapercuts" project shall make the Ubuntu desktop to glaze
+ The "hundredpapercuts" project shall make the Ubuntu experience to glaze
summary: - The "hundredpapercuts" project shall make the Ubuntu experience to glaze
+ The "hundredpapercuts" project will make the Ubuntu experience to glaze
description: updated
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote : Re: The "hundredpapercuts" project will make the Ubuntu experience to glaze
Revision history for this message
Teo (teo1978) wrote :

> The Ubuntu experience is limited by plenty of small bugs.

That's not quite correct. The ubuntu experience right now is made absolutely unbearable by a bunch (or even plenty) of HUGE critical bugs, such as:
- inability to properly hibernate
- unreliable suspend/resume
- random x.org crashes
- random complete freezing of the whole system, the only way out being hard power off
- bluetooth randomly starting to systematically reject all incoming transfer (workaround being to switch bluetooth hardware of and on, but only works on some machines)
- usb pendrives randomly remounting as readonly at any moment
- ntfs filesystems are unreliable (crash at random times)
- broadband mobile modems don't work out-of-the-box
- broadband mobile modems (even once configured properly) "die" randomly meaning you have to unplug and replug them

There are only the ones that come right to my mind now; I've reported (or found to have already been reported) all of them.

I guess there is a list somewhere where we can contribute links to the most urgent bugs to be fixed? Or am I missing what this report is about?

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@matteo:

I have to agree.

And speaking of getting bug list, is just about figuring how to use the advance search feature for the kind of activity you want to develop. For example, I learned how to use this very well for finding bugs prone to be triaged:

Status 'Confirmed', because someone else tested it is a real bug.
Importance 'Undecided', because it should mean no one with the ability to set bug priority has put an eye on it.
With the 'Saucy' tag, so it is a warrant it is affecting more users and it has not got End Of Life.

And latter, I organized result in heat order; so I know usual the bug is.

But if you want to develop a task that isn't bug triaging, you shall use your imagination.

Regard.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@matteo:

Also I wanted to ask you what you think should be done about the fact of having so many bugs.

Revision history for this message
Teo (teo1978) wrote :
Download full text (4.0 KiB)

I am just a user, the only thing I can do is contribute my own humble list of bugs I know of that are so critical that (a) It's beyond me that they haven't got enough attention yet and (b) I don't even see the point in having new major releases of ubuntu without having them fixed. Which only makes sense if it is joined with lists provided by other users, of course.

May I suggest to PLEASE forget the "bug has the 'confirmed' status" criteria when selecting important bugs to take action on!?
Now that you mention it, that mostly explains how some tremendously critical bugs have remained unfixed across several major releases (which is really frustrating and disappointing). There are kinds of bugs that shouldn't require any confirmation whatsoever to be looked at, or that should be picked by developers (or anybody with the skills to do that) for the very purpose of checking whether they can reproduce them, and hence confirm them.

Consider crashes. If somebody reports a crash of, e.g., xorg, that should be enough to take that bug report seriously and investigate whether there is enough information in it to take some action. If you're going to wait for someone to confirm that, you're almost certainly going to wait forever. Unless you think users may actually be inventing bugs, or thinking a program has crashed when it hasn't. And a bug report generated by ubuntu-bug should contain enough information to discard that hypothesis.
Xorg is just an example, of course. When something as basic as xorg, ntfs.whatever, network-manager and the like, crashes, even if one single person has reported one single crash, it should be enough to trigger developers' attention to it to do whatever can be done to figure out what caused the crash. The only case when a bug report should be "forgotten" until new information is available, is if some developer has actually checked that there's not enough information to do anything about it. Where "anything" does not necessarily mean "start working at fixing it" but also "try to figure out what _may_ reproduce it", etc.
The most disastrous crashes of the most vital components of the OS are usually hardly reproducible, so if you wait for confirmation or for a set of steps to reproduce the issue, you're going to leave the most critical bugs unsolved, exactly those that most need to be fixed.
Basically, crashes should be treated as confirmed by default (that would mean e.g. encouraging people to confirm their own bug reports if they are crashes, or even have some bot confirm bugs when they contain the word "crash/crashes").

Another thing that frustrates me beyond telling is when I report some critical bug, then I get an automated response that tells me to test the upstream kernel, and the bug report is put into the "incomplete" status, and then it expires. I never going to test the upstream, period. Does that mean that I shouldn't report the bug? Oh well, then you're never going to discover the bugs that "real users" face (where by "real users" I mean any people outside the cyrcle of those actively developing parts of Ubuntu).
That the particular person who reported a bug cannot or is not willing to do additional testing, is...

Read more...

summary: - The "hundredpapercuts" project will make the Ubuntu experience to glaze
+ The "hundredpapercuts" project will make the Ubuntu experience blaze
+ gloriously like the sun!
Revision history for this message
Anthony Harrington (linuxchemist) wrote : Re: The "hundredpapercuts" project will make the Ubuntu experience blaze gloriously like the sun!

I hope you don't mind my tweaking the name of this bug slightly so that it makes sense and reflects your intention ;)

I have a few thoughts people might agree with.

It seems to me that the issue over the years has become something like this: Those who created a program in question themselves or actively code for the programs that make up the infrastructure of ubuntu have got their hands full adding features and fixing major bugs etc

Comparatively smaller bugs and smaller changes which the general userbase point out should be changed tend to slip through the cracks a bit and become the focus of groups like the 100 papercuts. However overall, i think it's accurate to say that there is perhaps a difference in programming expertise between the creators and those hoping to fix a small bug here and there, and certainly a difference in familiarity of the procedures for helping out as well.

It seems to result in a situation where major release versions of programs are churned out, complete with new features and no/almost no show-stopping bugs, but so many possible userbase-inspired additions have missed their chance because noone knew how to contribute or it was too complicated to do so. Then there are users who will report a bug but have no clue how to gather useful data about it - and can suddenly be met with comments as short as "can you bisect it?" referring to 'git bisect' to see which commit caused the problem. Let's assume the average user is not going to want to build the program from source to see what the problem is exactly; they want to be helpful and report something that's not so good but rarely want to/are able to go through the hassle of making the change themself, so they must wait until someone is free to look at it. (This step is understandably slow and for good reason - there are other things to be done first!)

Ubuntu brainstorming was popular a while back and served a purpose because a lot of cool new USERBASE DESIRED features and changes were thought up, but as many said later, the ideas were generally ignored and left just as ideas. (Perhaps people didn't know how they would go about implementing one of these ideas?)

Generally, there are a few really talented programmers in the linux world but they've really got their hands full focusing on what they enjoy most/what they feel is most important and it's slow going for a beginner to reach their level of expertise.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Anthony, I think the title you just proposed reflects much better the spirit.

However, on the other hand, what I wanted is:

- People to be willing to read it every time we enter this report... and fifteen word is a very long title to do so!
- This to be, not only a source of motivation, but mainly a formal commitment. So rather than adjectives and exclamations, verbs and affirmations. Then, instead of moving motion, motion is moved itself.

But is seems good changing glaze (from a glazed lemon and orange pound cake) to blaze (of a summer blazing rising sun) 😅

summary: - The "hundredpapercuts" project will make the Ubuntu experience blaze
- gloriously like the sun!
+ The "hundredpapercuts" project will make the Ubuntu experience to blaze
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote : Re: The "hundredpapercuts" project will make the Ubuntu experience to blaze

Or perhaps changing:

1. To burn fiercely.
2. To shine brightly.
3. (often followed by "up") to become stirred, as with anger or excitement.
4. (usually followed by "away") to shoot continuously.

in favour of:

1. To emit a steady even light without flames.
2. To shine intensely, as if from great heat.
3. To be exuberant or high-spirited, as from excellent health or intense emotion.
4. To experience a feeling of wellbeing or satisfaction: to glow with pride.
5. (esp of the complexion) to show a strong bright colour, esp a shade of red.
6. to be very hot.

summary: - The "hundredpapercuts" project will make the Ubuntu experience to blaze
+ The "hundredpapercuts" project will make the Ubuntu experience to glow
summary: - The "hundredpapercuts" project will make the Ubuntu experience to glow
+ The "hundredpapercuts" project will make the Ubuntu experience a glow
Revision history for this message
Dario Ruellan (druellan) wrote : Re: The "hundredpapercuts" project will make the Ubuntu experience a glow

I agree with many of the comments, but I believe that bring in bugs related to hardware or a particular installation is a bad idea.

First of all, those bugs are supposedly reported by oops-daisy, and there is already a backend to handle them. I agree that many of them are never fixed, but is not an easy task to reproduce, fix, and retest everything (you can break many things at this level); far from the scope of the project.

Besides, I agree with @Matteo. They are a problem to the UX.

I believe the focus of the project was not to fix critical bugs, but to provide some refinement on the product, fixing annoyances that are never discussed just because they are so minimal.

Even more, if you ask me, we should be working on LTS only. This version is often left behind (last year I get tired trying to backport several papercuts), but has the most professional user base (Amazon, Google), and because is not a moving target like other releases, you can take your time to try polish it, even with hardware-related problems.

IMHO.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

- I feel that Understanding the general context is what will make this project to be in context right now.
- I had never got my software updated only every two years when I used (the piece of junk of) Windows, back in the 90s.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote : Re: The "hundredpapercuts" project will make the Ubuntu experience to shine

Target description updated in the related blueprint (https://blueprints.launchpad.net/hundredpapercuts/+spec/other-design-p-papercuts-shine).

Please, review it.

And regards.

summary: - The "hundredpapercuts" project will make the Ubuntu experience a glow
+ The "hundredpapercuts" project will make the Ubuntu experience to shine
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

What is you opinion about point 3 (Rebrand the One Hundred Papercuts project as Ubuntu Desktop Bitesize) in "https://wiki.ubuntu.com/FutureOfThePapercutsProject"?

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Blueprint updated to include the hole process to make this a reality 😲

Please, give your points of view!

Since long list never get done, I have written remaining actions as small lists; what is not an option in the "work items" section. So we get achievements sooner, and we will discard or simplify processes easily as needed.

Also; after reading (all) the previous discussions, documentation and user's surveys (for days since my mind literally blew up); I decided to take some radical actions, as seen in the blueprint. Always thinking that decisions are just temporal guesses.

Thank you.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This is just a backup.

Jack Leigh (leighman)
summary: - The "hundredpapercuts" project will make the Ubuntu experience to shine
+ The "hundredpapercuts" project will make the Ubuntu experience shine
Changed in hundredpapercuts:
assignee: Papercutters (papercutters) → Papercuts Ninja (papercuts-ninja)
summary: - The "hundredpapercuts" project will make the Ubuntu experience shine
+ Hundred Papercuts will make the Ubuntu experience to shine
summary: - Hundred Papercuts will make the Ubuntu experience to shine
+ Hundred Papercuts will make Ubuntu to shine
summary: - Hundred Papercuts will make Ubuntu to shine
+ Hundred Papercuts will make Ubuntu shine
summary: - Hundred Papercuts will make Ubuntu shine
+ One Hundred Papercuts will make Ubuntu shine
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This is just a backup.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
description: updated
description: updated
Revision history for this message
Dario Ruellan (druellan) wrote :

Some things that come to my mind just reading the blueprint:

HOW WE WANT IT TO BE LIKE, IN DETAIL
* Feel that someone actually cares about the details.
* Feel that the Ubuntu desktop usage experience is complete and well thought.

IN WHICH MOMENTS WE APPROACH MORE THAN USUAL TO WHAT WE WANT
* When its clear why we are here.
* When we all act for a common objective.
* When documentation in wiki is simple and straighforward.

WHAT WE DO DIFFERENT UNDER THESE CIRCUMSTANCES
* We quickly identify problems landing on the scope of the proyect.
* We know what to do or how to forward the problem to the right people.

WHAT WE THINK THAT MAKES US TO ACT THIS WAY
* We care about those problems.
* When we can experience the results on the real life.

WHAT ELSE THINKS WHO IS SUCCESSFUL HERE
* You're not only improving you own experience, but others.

WE REDEFINE WHAT A PAPERCUT IS
(sorry to insist but :p)
[o] I expand the definition of papercut to include LTS releases.

WE EDIT OUR WIKI
[o] I include how to easy backport papercuts.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

When focusing the project in regular releases, Dario, I do because I want to see if it's possible every version to be a pleasure by the very first day after it's released.

This is because the most probable thing is a great part of people; from the 96% of users who use Windows; is not deciding to jump to Ubuntu only because small details, and when this details have been improved we could be seeing a massive migration to the OS. In this scenario, having set the appropriate infrastructure for those users to help improving their computing easily will make a great difference.

This is not for the present; but for catalysing a chain reaction that can happen at any time, and perhaps not too far. In case we don't reach this goal, life is simple; and we can continue having the good Ubuntu we have (but I'm not feeling like giving up at any time).

For the rest of the given thoughts, I have accommodated them in the project's plan.

So thank Yu.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Oh, I don't know if this is causality; but I was just resting a bit watching videos on YouTube and, from a one of a very different nature, I was suggested with the following one. I started viewing it at random time position, and got this:

http://youtu.be/loQhufxiorM?t=4m19s

Magic! (or perhaps Google's AI).

Revision history for this message
Dario Ruellan (druellan) wrote :

Oh, I was not implying left behind the current releases, but to keep in scope the last LTS, but I don't want to keep discussing that point since the next LTS is around the corner, and anything we can do now will impact that release.

BTW, we need to decide if the scope includes beta versions. Could be interesting to have a "call for arms" when the first beta is released.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Note that when a release is more buggy is at the time it's launched; so this is another reason why I think at the moment it will be better to focus in releases that are more buggy, rather in one launched a year ago and it's pretty stable.

On the other hand, notifying that beta has been released to the "Papercut Ninjas" team seems practical for it; although I think rather than an asking for help it shall be just informative.

Regards.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Just a backup.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Just a backup.

Revision history for this message
James Ramsay (f-jack) wrote : Re: [Papercuts-ninja] [Bug 1049082] Re: One Hundred Papercuts will make Ubuntu shine

How would I tell what ubuntu version the bug affects

On Fri, Nov 8, 2013 at 12:07 PM, Alberto Salvia Novella
<email address hidden> wrote:
> Just a backup.
>
> ** Attachment added: "papercutters description.back.txt"
>
> https://bugs.launchpad.net/hundredpapercuts/+bug/1049082/+attachment/3903400/+files/papercutters%20description.back.txt
>
> --
> You received this bug notification because you are a member of
> Papercuts
> Ninjas, which is a bug assignee.
> https://bugs.launchpad.net/bugs/1049082
>
> Title:
> One Hundred Papercuts will make Ubuntu shine
>
> Status in One Hundred Papercuts:
> In Progress
>
> Bug description:
> The Ubuntu experience is limited by plenty of small bugs. We are
> redesigning the "One Hundred Papercuts" project to make Ubuntu
> delightful by reducing them.
>
> This time we're trying the other way:
> - Instead of planning so hardly, working.
> - Instead of creating an impressive infrastructure, to create an
> agile one.
> - Instead of working in many aspect, to polish the very important
> things.
> - Instead of marketing the project; to make it recognizable, and to
> properly tie it.
> - Instead of setting great goals; to set a great mission, and to
> define goals for sure we will get.
>
> If you want this kind of bugs, as us, to be fixed; you may want to:
> - Subscribe to this report and give your points of view in it.
> Although we will rather be working than commenting, we will carefully
> look at them.
> - Know or contribute to its implementation
> (https://wiki.ubuntu.com/One%20Hundred%20Papercuts/One%20Hundred%20Papercuts%20will%20make%20Ubuntu%20shine).
>
> Thank you ♡
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1049082/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~papercuts-ninja
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~papercuts-ninja
> More help : https://help.launchpad.net/ListHelp
>

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Under the bug description there's a tag list. It shall contain the names of the releases (https://wiki.ubuntu.com/Releases) which are known to be affected by the bug.

Sometimes, specially for older releases, it happens it isn't told. In these cases:
- It shall be mentioned somewhere in the report.
- Or shall be assumed is affecting the release that was current at the time the report had been written.

So it's a good practice to tag untagged reports.

If you need support at some time, you can ask the Papercuts Ninjas (mailto:Ubuntu - Papercuts Ninja <email address hidden>).

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Sorry:

mailto:<email address hidden>

Revision history for this message
Dario Ruellan (druellan) wrote :

"Note that when a release is more buggy is at the time it's launched; so this is another reason why I think at the moment it will be better to focus in releases that are more buggy, rather in one launched a year ago and it's pretty stable."

Yeah, and I agree (again, work done here will land on the next LTS, sooner or later), but that's also part of the problem. LTS is by no means perfect. It is stable, meaning that has little critical flaws, but it has many small annoyances that are left there for over two years just because it has no community traction and the packages are old; and thats a shame because it is the most important release for Canonical, the one people are willing to pay for support.
But, again, I don't want to keep pushing on it. I'm out of Ubuntu until my Linux main machine come back from repair (over 2 months now!), so, keep the good work!

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

I have attached icons to https://wiki.ubuntu.com/IconsPage.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

A summary of the development summit can be found at:

- Of the notes: <http://pad.ubuntu.com/ep/pad/view/uds-1311-community-1311-quality-papercuts/latest>.
- Of the hangout: <https://www.youtube.com/watch?v=zp6p3Pivw3U>.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This document shows why Debian users prefer his community over Ubuntu's, and helps to identify priorities for Ubuntu.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Suggestions of experienced triagers on how to find proper bugs to work in Launchpad.

Changed in hundredpapercuts:
assignee: Papercuts Ninjas (papercuts-ninja) → Alberto Salvia Novella (es20490446e)
description: updated
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This is a Value Stream Map (http://en.wikipedia.org/wiki/Value_stream_map) of work-flow in Launchpad.

Changed in hundredpapercuts:
assignee: Alberto Salvia Novella (es20490446e) → Iosu Sacristan Etxabe (iosusacristan)
Changed in hundredpapercuts:
assignee: Iosu Sacristan Etxabe (iosusacristan) → Alberto Salvia Novella (es20490446e)
Revision history for this message
xreuze (xreuze) wrote :

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,

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

I read your message many times, but I think I don't really understand what you mean :o

Please:
- Have a quick look at <http://tinyurl.com/okhevtb>.
- Imagine yourself saying what you wrote aloud.

and try again!

Revision history for this message
Andrew (am-public-o) wrote :

I just found out about this project from the link on this bug: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1531184

I am glad that 12.04LTS seemed to be a great release, but since then, I'm disappointed that the 14.04 and 16.04 releases seem to be plagued with bugs that are making it difficult to use a Desktop Ubuntu computer. Just now, I'm having to reboot a few times per day due to weird issues. None that a newbie to Ubuntu would care to put up with.

Changed in hundredpapercuts:
status: In Progress → Fix Released
To post a comment you must log in.