Hi Paul. Thanks for your answer. Indeed, I know all the effor Canonical puts on delivering the best Ubuntu ( I'll use U from here) distribution and so for all the people like us that helps to improve it. I've been using the K/X/Ubuntu distibutions since 6.06 and is still my favorite and only OS in most of mi PCs. I know well (sometimes not enough) the process behind Ubuntu development and research. My point here is as follows: I'm aware of all the importance that Unity and all the upcoming changes in U has for the benefit off the users, I'm quiet impacient to have them all in my desktop and play with them and enjoy them because that's what I do with every new release. BUT I think we must desing an optional workflow for the developers and all the people involved which let us attack those old bugs and not leave them behind unsolved.
In my experience, sometimes it's a little dissapointing for some users and for me when they want me to install Ubuntu and I have to say "uhmm well not now, not the 10.10 that you liked because it's gonna have an issue with battery status, so let's wait untill April of 2011". I know we all want to minimze this kind of situations. And If I can help to avoid it I will be glad to do it. I don'tt know is there's a mechanism that reminds the developers about the antiquity of the bugs or their importance, but such a nice implementation would be excellent. Even one where they can "bookmark" one bug and create some warning every 3 days that there has not been any changes or fixes. I think this is a great idea (if it has not been implemented yet) and maybe the old bugs can be fixed with a 20% of their main working time or maybe less but just aiming to the high,critical bugs. I'm not asking them to fix it for me, I apologize if it was missunderstood, I just want to optimize the way we process bugs because that's our goal. I'm sorry if this was taken as a "flame" but I wanted to call your attention so we can see if there's something we all can improve to solve those old bugs. Thanks so much for your answer Paul. 2011/1/14 Paul Sladen <[email protected]> > Jonas: In Ubuntu there is no "us" and "them", there is only "we", ...and > that includes yourself as an equal to anyone else (by taking the time to > participate in Ubuntu, to file this bug report you are as much a part of > Ubuntu as anyone else). There are a finite number of a people and a > finite amount of time, so there is not always time to do everything at > once. > > We (which includes you as much as I) also need to remember that for many > people Ubuntu is a hobby, something done in their spare time and for > free, for fun and because it is satisfying. > > If you particularly want to help Ubuntu (which includes you as much as > I) to make something happen, then the best way is to get involved with > helping to debug the situation or issue; perhaps trying to to find the > right people that can give advice, asking them for assistance or for > their help in discovering a solution or cause. > > It is often worth bribing people too; if you can find somebody offering > them a drink is a good way to focus their attentio ... but for other > people the motivation might be different, it might be interrail tickets > and the time to use them, or cupcakes, or some form of consultancy > income. On a large scale if that you *need* doing for a company, or for > yourself, it might be worth buying a support contract from one of the > companies that are familiar with Ubuntu and/or the component in > question; Canonical is such a company but there are others. Putting > your energy (time or money) behind something demonstrates to others that > it is important, or worthy of doing above everything else that there is > to do. This would help not just yourself, but everyone using Ubuntu, > everyone using Debian and everyone using one of the other distributions > that ship the same base software > > I've marked this report as "invalid", and is not something that can be > fixed with a patch or code (even if that might be nice). For the actual > issue of bug #531190, that is still maked Confirmed, so lets keep all > the discussion in one place and start debugging it on the bug report! > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/702736 > > Title: > Is developers really paying attention to the Maverick bugs?... > > Status in “unity” package in Ubuntu: > Invalid > > Bug description: > Binary package hint: unity > > Is developers really paying attention to the Maverick bugs?... I've > seen a bug ie bug #531190 and it is about a year old and has not been > fixed yet. I'm sorry, I know this is not the right place but I needed > to call your attention. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/702736/+subscribe > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702736 Title: Is developers really paying attention to the Maverick bugs?... -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
