Contributor forteller on the Quality category
353
votes
384
35
31
266
votes
278
21
12
Solution #2:
Work on "AppCenter"
Written by
Rodrigo the 7 Aug 09 at 16:34.
Looking at the ideas of the past days I came across one that pointed me towards this:
https://wiki.ubuntu.com/AppCenter
please have a look.
I think is a great idea.
38
votes
68
18
30
Solution #3:
Group related updates together
Most users don't need to know the names of all the packages that are being upgraded. It might make things look less scary if, say, all the security-related updates were lumped together into one item in the Update Manager. And not just group those updates together -- I mean *completely hide* the names of all the security-related upgrades, so the user only sees *one* security-related item in the list.
Power users should still be able to get a list of what each update contains. But regular users shouldn't be overwhelmed with 50 different package names, when all they need to know is that there's 37 MB of system upgrades, 2 MB of security patches, and a new version of Firefox.
Most users don't need to know the names of all the packages that are being upgraded. It might make things look less scary if, say, all the security-related updates were lumped together into one item in the Update Manager. And not just group those updates together -- I mean *completely hide* the names of all the security-related upgrades, so the user only sees *one* security-related item in the list.
Power users should still be able to get a list of what each update contains. But regular users shouldn't be overwhelmed with 50 different package names, when all they need to know is that there's 37 MB of system upgrades, 2 MB of security patches, and a new version of Firefox.
-33
votes
6
17
39
Solution #4:
Organize related things better
When you go to install programs or updates, they are not in order, which could cause someone to possibly install the wrong upgrade or application that may cause problems in the future. I propose that categories should be made organize data so you can find exactly what you're looking for.
When you go to install programs or updates, they are not in order, which could cause someone to possibly install the wrong upgrade or application that may cause problems in the future. I propose that categories should be made organize data so you can find exactly what you're looking for.
-49
votes
28
6
77
Solution #5:
Update on Shutdown Option
AppCenter is quite a neat idea, they should work on an option for that to update just before the computer shuts down rather than slowing your computer down while you're using it. This option should be disabled by default.
AppCenter is quite a neat idea, they should work on an option for that to update just before the computer shuts down rather than slowing your computer down while you're using it. This option should be disabled by default.
-12
votes
3
7
15
Solution #6:
Only group packages with same changes text
(Similar but not equal to #3!)
The Update Manager lists updatable packages. Below the list you can unfold a text field that describes what changed in the currently selected package.
I propose to group together all packages that have the very same text of changes! Each package should still be un/checkable for updating individually. But only a whole group should be selectable. Further the context menu in the list could also show "Check Group" and "Uncheck Group".
In contrast to #3 no info is hidden! I even miss the total number of updatable packages that Gutsy or Feisty once had shown.
(Similar but not equal to #3!)
The Update Manager lists updatable packages. Below the list you can unfold a text field that describes what changed in the currently selected package.
I propose to group together all packages that have the very same text of changes! Each package should still be un/checkable for updating individually. But only a whole group should be selectable. Further the context menu in the list could also show "Check Group" and "Uncheck Group".
In contrast to #3 no info is hidden! I even miss the total number of updatable packages that Gutsy or Feisty once had shown.
-11
votes
10
6
21
Solution #7:
Fine as it is
It is currently simple, straightforward, and concise.
It is currently simple, straightforward, and concise.
-6
votes
8
4
14
Solution #8:
No more code-rot please!
I agree that the existing system is quite poor.
I should not see so much mess in the app list. Searching for a specific app to install also should never return Beta or Source unless I've chosen to see those.
I'm 100% against AppCenter!
One of the most irritating things about Linux is all of the abandoned/orphaned/code-rot apps. How many different apps like this do we need and must we have installed?
Please do not release a different app to manage this, the source exists for the other apps, just take the best one and update it to a new version that has the required features.
There should never be multiple/duplicate/abandoned apps for the base OS... EVER!
I agree that the existing system is quite poor.
I should not see so much mess in the app list. Searching for a specific app to install also should never return Beta or Source unless I've chosen to see those.
I'm 100% against AppCenter!
One of the most irritating things about Linux is all of the abandoned/orphaned/code-rot apps. How many different apps like this do we need and must we have installed?
Please do not release a different app to manage this, the source exists for the other apps, just take the best one and update it to a new version that has the required features.
There should never be multiple/duplicate/abandoned apps for the base OS... EVER!
Including Vote Counting for Problem Statement
Written by adamknox the 21 Dec 09 at 08:57.
Related project: brainstorm.ubuntu.com .
Category: Others.
New
We are currently allowed to vote on solutions to problems (as many solutions as we want), but not to the importance of the problem itself.
If a solution is voted upon multiple times the problem is deemed more important! This is a mistake in design.
Viewers have no way of recognising a problem without supporting a solution. This means that if they agree with the problem statement, but not with the solutions they can't voice the importance of the problem.
Solution #1:
Add another vote box next to the problem statement
Written by
adamknox the 21 Dec 09 at 08:57.
This vote box ought to be visually different from the solution vote boxes.
The statistics from this box ought to have a direct impact on a sorting field for ideas labelled "community importance"
This vote box ought to be visually different from the solution vote boxes.
The statistics from this box ought to have a direct impact on a sorting field for ideas labelled "community importance"
Solution #2:
There is ALWAYS a solution
Every "problem" should have the automatic solution "Other Solution/I Do Not agree with the proposed solutions/None of the Above"
Then, assuming (as we are in the question!!) that you cannot be bothered/cannot think of a solution that solves the issues you have with the current solutions, you could be automatically notified if another solution is proposed to the problem in question.
Thusly, one is registering interest about the problem whilst simultaneously providing a mechanism to promote a killer instinct hill climb to a workable solution.
For example, a large number of people voting for the "make another solution" solution would indicate a high whuffy for solving the problem satisfactorily and this provide the stimulus necessary to do so.
The only issue I can think with this, is what to do with the vote cast to the "None of the Above" solution... It would be most useful to remove it if the user votes on any other existing solution, in terms of statistics. It is perfectly possible to analyse this into the statistics in the back end. I just wonder about doing it immedittelly in the javascript.
Every "problem" should have the automatic solution "Other Solution/I Do Not agree with the proposed solutions/None of the Above"
Then, assuming (as we are in the question!!) that you cannot be bothered/cannot think of a solution that solves the issues you have with the current solutions, you could be automatically notified if another solution is proposed to the problem in question.
Thusly, one is registering interest about the problem whilst simultaneously providing a mechanism to promote a killer instinct hill climb to a workable solution.
For example, a large number of people voting for the "make another solution" solution would indicate a high whuffy for solving the problem satisfactorily and this provide the stimulus necessary to do so.
The only issue I can think with this, is what to do with the vote cast to the "None of the Above" solution... It would be most useful to remove it if the user votes on any other existing solution, in terms of statistics. It is perfectly possible to analyse this into the statistics in the back end. I just wonder about doing it immedittelly in the javascript.
Solution #4:
Rating The Problem
Written by
adamknox the 30 Jan 10 at 02:32.
Instead of just "voting" that the problem is important there could be a starring system. 1 star denotes that the problem is not very pressing to the voter, 5 stars denotes very important.
Instead of just "voting" that the problem is important there could be a starring system. 1 star denotes that the problem is not very pressing to the voter, 5 stars denotes very important.
Get more developers reading Brainstorm!
Written by DanteAshton the 19 Dec 09 at 15:42.
Related project: ubuntu.com .
Category: Developer feedback.
New
In a recent official document, this was stated;
I have yet to find anything interesting on Brainstorm. -
â—¦ Yes brainstorm is useless, the user doesn't know that though, so he posts
stuff or votes there and wonders why we never do anything
It's not exactly pleasant to hear of this in a document, and communication to the community would have been helpful.
Solution #1:
Get more developers using Brainstorm.
I admit, not all of Brainstorm's ideas may be helpful, or even usable. However, it is the primary location for a user to suggest new things and improvements.
I admit, not all of Brainstorm's ideas may be helpful, or even usable. However, it is the primary location for a user to suggest new things and improvements.
Solution #2:
Automate the transfer of Brainstorm ideas into feature-requests on bugtracker.
To make it easier on the devs, I beleive Brainstorm should serve as a way for the users to vote upon ideas, until a mod/automated program comes along and dumps popular ideas into the feature-request list of Bugtracker.
This would mean, in the long run, a remake of Brainstorm, turning it into a sort of wrapper for feature requests and improvments, rather then a seperate site.
To make it easier on the devs, I beleive Brainstorm should serve as a way for the users to vote upon ideas, until a mod/automated program comes along and dumps popular ideas into the feature-request list of Bugtracker.
This would mean, in the long run, a remake of Brainstorm, turning it into a sort of wrapper for feature requests and improvments, rather then a seperate site.
Solution #3:
Make summary of ideas
Written by
DrG the 20 Dec 09 at 05:55.
Ubuntu Developers periodically reads BrainStorm ideas and posts 'Developer comments' .
Some solutions are too long and contains good as well as bad ideas .
Make a group of 'Briefers' (Like '
Moderators ') and display a brief summary of the relevant solution . This will be comfortable .
Make small icons besides each block of idea to vote for the user , who proposed that solution .
Also see -
Better BrainStorming
Ubuntu Developers periodically reads BrainStorm ideas and posts 'Developer comments' .
Some solutions are too long and contains good as well as bad ideas .
Make a group of 'Briefers' (Like '<a class="undecoredlink" href="https://launchpad.net/~brainstorm-moderators">Moderators</a>') and display a brief summary of the relevant solution . This will be comfortable .
Make small icons besides each block of idea to vote for the user , who proposed that solution .
Also see - <a class="undecoredlink" href="http://brainstorm.ubuntu.com/idea/23056">Better BrainStorming</a>
Solution #4:
Highlighting techniques.
Written by
DrG the 20 Dec 09 at 16:33.
Use more HTML capabilities in Brinstorm, which to represent ideas better.
1.Table
2.Flowcharts / Mind Maps
3.Text format - Text highlighting , bold , different font etc.
4.Animations / audio & presentations -( Should be limited - considering narrow band users )
These will help others to understand the idea better with ease and in minimal time.
Also see -
Better BrainStorming
Use more HTML capabilities in Brinstorm, which to represent ideas better.
1.Table
2.Flowcharts / Mind Maps
3.Text format - Text highlighting , bold , different font etc.
4.Animations / audio & presentations -( Should be limited - considering narrow band users )
These will help others to understand the idea better with ease and in minimal time.
Also see - <a class="undecoredlink" href="http://brainstorm.ubuntu.com/idea/23056">Better BrainStorming</a>
Solution #5:
Cross-reference Brainstorm ideas with project roadmaps
Users want to see when their proposals might be implemented, and developers have to address dependency complexity in order to implement features that everyone wants. A beautiful crossroads here is the project roadmap, since it can be used to lay out dependencies and rough timelines.
Users want to see when their proposals might be implemented, and developers have to address dependency complexity in order to implement features that everyone wants. A beautiful crossroads here is the project roadmap, since it can be used to lay out dependencies and rough timelines.
Solution #6:
Send Alerts To The Launchpad Projects
Written by
eld1e6o the 21 Dec 09 at 07:25.
Add the hability to interact with launchpad, when the user put the name of any related project in the brainstorm wich is hosted in launchpad (optionally, if is popular) send an alert to launchpad.
Add the hability to interact with launchpad, when the user put the name of any related project in the brainstorm wich is hosted in launchpad (optionally, if is popular) send an alert to launchpad.
Solution #7:
Better and faster search capabilities
Written by
stoffel the 21 Dec 09 at 21:24.
It should be easier for developers to find all ideas related to a *very* *specific* subject.
It also should be possible to (automatically) embed these *very* specific search results to blueprints, bug entries, forum entries, and so forth. Maybe there even can be an IRC bot that can suggest relevant brainstorm ideas during an ongoing discussion.
It should be easier for developers to find all ideas related to a *very* *specific* subject.
It also should be possible to (automatically) embed these *very* specific search results to blueprints, bug entries, forum entries, and so forth. Maybe there even can be an IRC bot that can suggest relevant brainstorm ideas during an ongoing discussion.
Solution #8:
Integrate instant messaging
Written by
stoffel the 21 Dec 09 at 21:42.
Integrate real-time communication capabilities using XMPP to make it easier for developers to get additional instant feedback from idea contributors.
Integrate real-time communication capabilities using XMPP to make it easier for developers to get additional instant feedback from idea contributors.
Solution #9:
Include a session devoted to the brainstorm ideas in the Ubuntu summits
Many new features that are to be included in Ubuntu are discussed in the Ubuntu summits, so it would be logical to include a session to offer an overview of the most important ideas to both developers and planners at the summit.
Many new features that are to be included in Ubuntu are discussed in the Ubuntu summits, so it would be logical to include a session to offer an overview of the most important ideas to both developers and planners at the summit.
Solution #10:
Involve non english speaking people
Creating brainstorm.es, .fr, .de to involve more people in brainstorming
Creating brainstorm.es, .fr, .de to involve more people in brainstorming
Solution #11:
Make Brainstorm multilingual
Written by
retimer the 30 Dec 09 at 17:37.
According to "The Ubuntu promise" to "provide the best translations and accessibility features that the free software community has to offer" there should be multilingual Brainstorm-sites to collect ideas from all the world. I suppose Canonical can afford it.
According to "The Ubuntu promise" to "provide the best translations and accessibility features that the free software community has to offer" there should be multilingual Brainstorm-sites to collect ideas from all the world. I suppose Canonical can afford it.
Solution #12:
Ask software development sites to display a message
My solution is to ask open-source development sites like SourceForge.net and our own Launchpad.net to display a message (not an ad) to get developers to come over here. This would be a great way to attract many developers this way and notify people about Ubuntu Brainstorm and Ubuntu in general.
My solution is to ask open-source development sites like SourceForge.net and our own Launchpad.net to display a message (not an ad) to get developers to come over here. This would be a great way to attract many developers this way and notify people about Ubuntu Brainstorm and Ubuntu in general.
Solution #14:
publicity
Written by
bergginu the 8 Jan 10 at 00:27.
It's simple to solve:
You only accurate to a more direct channel to invite users and developers, most of them do not have this system.
You can for example, insert the call message, which appears during the final part of the installation and the pages that refer to the links to download the Ubuntu LiveCD's.
It's simple to solve:
You only accurate to a more direct channel to invite users and developers, most of them do not have this system.
You can for example, insert the call message, which appears during the final part of the installation and the pages that refer to the links to download the Ubuntu LiveCD's.
Solution #15:
Make Brainstorm More significant .
Written by
DrG the 13 Jan 10 at 06:24.
Ubuntu members may get more privilege than normal users in development process of Ubuntu .
But now Brinstorm ideas are not considered when choosing ubuntu members but participation in any of the forum will get .
-
That much inferior is Brinstorm in the eyes of ubuntu ( You can contact the members and verify ) . As per 'lifeless' ( Ubuntu Member ) (
https://launchpad.net/~lifeless ) - "we don't currently really recognise brainstorm activity - both gardening and idea generation - as a significant contribution. " -12/jan/2010 (04:02:38 PM) in IRC #ubuntu-meeting .
-
So
1. Make developers or similar personnel to check brainstorm Ideas at least once in a month
2. Take Brainstorm Ideas when considering for Ubuntu Membership .
Ubuntu members may get more privilege than normal users in development process of Ubuntu .
But now Brinstorm ideas are not considered when choosing ubuntu members but participation in any of the forum will get .
-
That much inferior is Brinstorm in the eyes of ubuntu ( You can contact the members and verify ) . As per 'lifeless' ( Ubuntu Member ) ( https://launchpad.net/~lifeless ) - "we don't currently really recognise brainstorm activity - both gardening and idea generation - as a significant contribution. " -12/jan/2010 (04:02:38 PM) in IRC #ubuntu-meeting .
-
So
1. Make developers or similar personnel to check brainstorm Ideas at least once in a month
2. Take Brainstorm Ideas when considering for Ubuntu Membership .
Solution #16:
Link ideas to bug reports
Written by
philip the 13 Jan 10 at 20:40.
For some ideas, there are already related bug reports at their respective projects. Brainstorm should include an extra category of ideas, "bug reported" or something similar, in addition to the "in development", etc., and include links to the related bug reports. Users can then join the discussion at the bug report and alert the developers to the discussion on Brainstorm.
For some ideas, there are already related bug reports at their respective projects. Brainstorm should include an extra category of ideas, "bug reported" or something similar, in addition to the "in development", etc., and include links to the related bug reports. Users can then join the discussion at the bug report and alert the developers to the discussion on Brainstorm.
Solution #17:
Integrate Brainstorm into Launchpad
In my oppinion it would be much easier if there would be only one plattform for developers, so adding an "Ideas-Section" or something like this wouldn't be bad in Launchpad
In my oppinion it would be much easier if there would be only one plattform for developers, so adding an "Ideas-Section" or something like this wouldn't be bad in Launchpad
Solution #18:
More involvement into Brainstorm
Make more Ubuntu users involve in Brainstorm to vote/propose ideeas. So many Ubuntu users are not involved in this project... and there are very few new ideeas proposed every week...
Make more Ubuntu users involve in Brainstorm to vote/propose ideeas. So many Ubuntu users are not involved in this project... and there are very few new ideeas proposed every week...
Ubuntu Crash Reporting Service
Written by noblex the 23 Jun 09 at 22:58.
Global category: Quality.
New
This has been discussed before (see LP bug #174195 and
the comments on this old Apport spec ), but isn't on here yet...
Right now, Apport only allows you to file a full bug report if you hit a crash (which requires you to sign up for Launchpad--so that devs can contact the reporter later). That's why Apport's only available on beta versions by default: it's disabled on final releases. Otherwise Launchpad'd be flooded with duplicates.
There should be a general crash reporter for end-users, not devs and testers: one with a low barrier for use that only requires a few clicks to submit a core dump. This'll let Launchpad compile statistics for what the most frequent crashers are out in the wild. Of course, this'll require a whole new service running on the Launchpad servers.
Fedora 11 already has
ABRT - Automatic Bug Reporting Tool .
Solution #1:
Give Apport an easy crash-report mode by default
Written by
noblex the 23 Jun 09 at 22:58.
Or at least, toggle this mode on in the stable releases' /etc/default/apport if you want to force alpha/beta testers to file bugs.
End-User Apport should work a lot like Firefox's use of Breakpad -- Ask the user what they were doing, and ask to provide an e-mail address where they can be reached by the QA team. Both fields would have to be optional. If the user enters an email address, it should be "remembered" for next time on a per-user basis (maybe in ~/.apport/?).
To keep current functionality, after submission, have an 'Advanced...' button or just a 'File a new bug...' button to go into the current "file a LP bug" mode.
Or at least, toggle this mode on in the stable releases' /etc/default/apport if you want to force alpha/beta testers to file bugs.
End-User Apport should work a lot like Firefox's use of Breakpad -- Ask the user what they were doing, and ask to provide an e-mail address where they can be reached by the QA team. Both fields would have to be optional. If the user enters an email address, it should be "remembered" for next time on a per-user basis (maybe in ~/.apport/?).
To keep current functionality, after submission, have an 'Advanced...' button or just a 'File a new bug...' button to go into the current "file a LP bug" mode.
Solution #2:
Apport should not require Sign-in and shoul search a database of proposed fixes,
This is the way apport should function.
Application Y crashes
Apport catches the crash and error dumps and compiles them into a report.
Apport displays two options:
1: Send report
2: Check for Fixes
If user chooses option 1:
Apport opens a window with comment field for additional details to be included in report user clicks submit, and apport closes.
If user chooses option 2:
Apport searches the launchpad database, finds proposed solutions to the bug and displays those solutions in a list for the user.
If a solution is found in database:
User clicks a solution and tries it, if it doesnt work continues to next solution
If a given solution works:
User clicks a button that says "This Solution worked"
If none of the solutions work:
User is presented with a "none of these solutions worked for me" button.
If no solution is found in database:
Apport opens a window with comment field for additional details to be included in report user clicks submit, and apport closes.
This is the way apport should function.
Application Y crashes
Apport catches the crash and error dumps and compiles them into a report.
Apport displays two options:
1: Send report
2: Check for Fixes
If user chooses option 1:
Apport opens a window with comment field for additional details to be included in report user clicks submit, and apport closes.
If user chooses option 2:
Apport searches the launchpad database, finds proposed solutions to the bug and displays those solutions in a list for the user.
If a solution is found in database:
User clicks a solution and tries it, if it doesnt work continues to next solution
If a given solution works:
User clicks a button that says "This Solution worked"
If none of the solutions work:
User is presented with a "none of these solutions worked for me" button.
If no solution is found in database:
Apport opens a window with comment field for additional details to be included in report user clicks submit, and apport closes.
Solution #3:
Apport shouldn't force the user to search for duplicates
Crashes look alike, and the user may never know the cause. Is this issue a duplicate of that one or maybe it just looks the same? There is a system on Launchpad which checks for duplicates automatically; moreover, freshly reported bugs are only seen by that system until it checks them. So why force the user to go through this process?
Crashes look alike, and the user may never know the cause. Is this issue a duplicate of that one or maybe it just looks the same? There is a system on Launchpad which checks for duplicates automatically; moreover, freshly reported bugs are only seen by that system until it checks them. So why force the user to go through this process?
Solution #4:
Apport should use optional username and password to connect to Launchpad
Written by
ki4jgt the 4 Aug 09 at 23:41.
This would allow the computer to automatically generate a report and send it without the user signing in all the time.
This would allow the computer to automatically generate a report and send it without the user signing in all the time.