Written by grofaty the 14 Dec 09 at 16:27.

I suggest to add karma points for forum contributions. There was some months ago button on forum to set "thank you" post. The number of "thank you" from other users could add some karma points to Launchpad. There are a lot of users that are contributing to FLOSS to help other users in forum. I think they deserve some "thank you" word.

I suggest to add karma points for forum contributions. There was some months ago button on forum to set "thank you" post. The number of "thank you" from other users could add some karma points to Launchpad. There are a lot of users that are contributing to FLOSS to help other users in forum. I think they deserve some "thank you" word.

Written by Rodrigo the 14 Dec 09 at 23:17.

Maybe based on the ideas, or on the votes an idea gets (I don't know what formula to actually use) you could be given Karma. After all you are helping the KARMA!!!

Maybe based on the ideas, or on the votes an idea gets (I don't know what formula to actually use) you could be given Karma. After all you are helping the KARMA!!!

Written by qense the 1 Mar 08 at 14:15.

Allow people to submit ideas to projects and vote on them, like people can now do on Brainstorm.

This would be integrated in as another tab (like answers and bugs). Once an idea has been marked as in development it would become/link to a blueprint.

This would improve the brainstorm interface, as launchpad has a clean user interface that works with small screens.

It would also improve developer interaction, as developers would be automatically able to control and interact with there projects brainstorm.

brainstorm.ubuntu.com would remain as an interface to the collective of brainstorms existing on launchpad connected with the ubuntu project.

Allow people to submit ideas to projects and vote on them, like people can now do on Brainstorm. This would be integrated in as another tab (like answers and bugs). Once an idea has been marked as in development it would become/link to a blueprint. This would improve the brainstorm interface, as launchpad has a clean user interface that works with small screens. It would also improve developer interaction, as developers would be automatically able to control and interact with there projects brainstorm. brainstorm.ubuntu.com would remain as an interface to the collective of brainstorms existing on launchpad connected with the ubuntu project.

Written by Kev the 13 Jul 09 at 22:38.

I've already an launchpad account. Why do I need to create a new account here to vote for a brainstorm idea? Making brainstorm using OpenID could be a first step to integrate brainstorm with launchpad. This would help people retain ownership of ideas as they move across.

I've already an launchpad account. Why do I need to create a new account here to vote for a brainstorm idea? Making brainstorm using OpenID could be a first step to integrate brainstorm with launchpad. This would help people retain ownership of ideas as they move across.

Written by Warbo the 1 Jul 08 at 18:23.

Wishlist bugs on Launchpad should spawn an appropriate idea on Brainstorm. Use a duplicate matching algorithm to prevent too many duplicates. The ideas would, of course, have the Launchpad bug attached.

Wishlist bugs on Launchpad should spawn an appropriate idea on Brainstorm. Use a duplicate matching algorithm to prevent too many duplicates. The ideas would, of course, have the Launchpad bug attached.

Written by Jarige the 30 Apr 10 at 11:37.

Instead, show the normal bug e-mail address as sender, which is unique to that bug report (445852@bugs.launchpad.net for instance). Those e-mail addresses already exist, the only thing that needs to be done is removing the private e-mail adresses from the notification mail.

Instead, show the normal bug e-mail address as sender, which is unique to that bug report (445852@bugs.launchpad.net for instance). Those e-mail addresses already exist, the only thing that needs to be done is removing the private e-mail adresses from the notification mail.

Written by der_vegi the 10 Mar 09 at 10:21.

Add the option to tag a bug as "my most annoying bug" in Launchpad. Only one bug per user can be marked like this at the same time.

Yes, there is already the "This bug does(n't) affect me" feature in Launchpad, but the ability of the average user to set a priority could give the devs some enhanced feedback.

Add the option to tag a bug as "my most annoying bug" in Launchpad. Only one bug per user can be marked like this at the same time. Yes, there is already the "This bug does(n't) affect me" feature in Launchpad, but the ability of the average user to set a priority could give the devs some enhanced feedback.

Written by rafalcieslak the 19 Mar 09 at 07:19.

I think users should be able to select if it is a really annoying bug, or not, instead of just flagging it as 'affecting me'.

I think users should be able to select if it is a really annoying bug, or not, instead of just flagging it as 'affecting me'.

Written by Craig73 the 21 Mar 09 at 17:11.

Your number one might not be very common, but your number two might be very common and have significant impact if fixed. A top 10 list might give a better picture of the key issues.

Your number one might not be very common, but your number two might be very common and have significant impact if fixed. A top 10 list might give a better picture of the key issues.

Written by jamesisin the 7 Apr 09 at 17:20.

Just a thought...

Just a thought...

Written by grofaty the 6 Mar 09 at 09:10.

There are probably some packages that hundreds of people would like to have in repository and there are probably some packages that only few people need them. It would be nice if some kind of voting would be possible something like brainstorm is for voting ideas there could be some kind of system to vote for new package to get accepted into official Ubuntu repository.

There are probably some packages that hundreds of people would like to have in repository and there are probably some packages that only few people need them. It would be nice if some kind of voting would be possible something like brainstorm is for voting ideas there could be some kind of system to vote for new package to get accepted into official Ubuntu repository.

Written by grofaty the 6 Mar 09 at 09:17.

It should be better collaboration with Debian project. When new request for package to get acceptance in official Ubuntu repository is requested, it should be some kind of process of synchronization between Ubuntu and Debian. If package would be accepted into Debian, Ubuntu would get that package automatically at next freeze. It would be also benefiting that any distribution based on Debian would also get new packages in there repository.

It should be better collaboration with Debian project. When new request for package to get acceptance in official Ubuntu repository is requested, it should be some kind of process of synchronization between Ubuntu and Debian. If package would be accepted into Debian, Ubuntu would get that package automatically at next freeze. It would be also benefiting that any distribution based on Debian would also get new packages in there repository.

Written by cheesehead the 6 Mar 09 at 12:35.

Join today! Always need more volunteers to help package, backport, maintain/upstream liason, submit to Debian, etc.
No voting or managing or prioritizing. Just pitch in on the packages you want.

Join today! Always need more volunteers to help package, backport, maintain/upstream liason, submit to Debian, etc. No voting or managing or prioritizing. Just pitch in on the packages you want.

Written by cyberix the 13 Jul 09 at 16:51.

Provide one page for each hardware component. Allow users to link bugs to pieces of hardware. Having an overview page for a piece of hardware is useful for multiple interest groups. Some of these include: developers working on related bugs, users experiencing the bugs, and consumers choosing hardware to buy. Companies manufacturing the devices may also have an interest in pages related to their products.

Provide one page for each hardware component. Allow users to link bugs to pieces of hardware. Having an overview page for a piece of hardware is useful for multiple interest groups. Some of these include: developers working on related bugs, users experiencing the bugs, and consumers choosing hardware to buy. Companies manufacturing the devices may also have an interest in pages related to their products.

Written by omegamormegil the 13 Aug 09 at 19:32.

Create a system where ordinary users can create Problem Reports documenting the SYMPTOMS of problems they are experiencing. After a Problem Report is created, it is added to a page on the user's Launchpad profile, giving them a place to keep track of the problems they have reported and any progress made on identifying the underlying bug and progress on fixing that bug. Users can comment and discuss their problems on their Problem Reports just like users like to comment and discuss their problems on bug reports right now. Commenting on bug reports should be kept to comments relating to fixing the bug.

Reported Problems could be indexed and compared, with more frequently reported user problems floating to the surface, giving the developers a good idea of what problems users are experiencing. Similar Problem Reports could be grouped together as it becomes apparent that various users have reported the same problem/symptoms, similar to duplicating bug reports, but keeping the original Problem Report of the reporter intact. Bug Triagers could tag clumps of Problem Reports with the bug suspected to be causing the problem, or Users could tag Problem Reports with bugs they think likely to be causing the problem. When the patch for a bug is in -proposed, the Problem Reports could be notified and invited to test the new version of the package to see if it fixes their problem.

A friendly support widget could be created to help users create problem reports. Perhaps functionality could also be added to direct users reporting common problems to documentation or other help resources to correct their problem.

Create a system where ordinary users can create Problem Reports documenting the SYMPTOMS of problems they are experiencing. After a Problem Report is created, it is added to a page on the user's Launchpad profile, giving them a place to keep track of the problems they have reported and any progress made on identifying the underlying bug and progress on fixing that bug. Users can comment and discuss their problems on their Problem Reports just like users like to comment and discuss their problems on bug reports right now. Commenting on bug reports should be kept to comments relating to fixing the bug. Reported Problems could be indexed and compared, with more frequently reported user problems floating to the surface, giving the developers a good idea of what problems users are experiencing. Similar Problem Reports could be grouped together as it becomes apparent that various users have reported the same problem/symptoms, similar to duplicating bug reports, but keeping the original Problem Report of the reporter intact. Bug Triagers could tag clumps of Problem Reports with the bug suspected to be causing the problem, or Users could tag Problem Reports with bugs they think likely to be causing the problem. When the patch for a bug is in -proposed, the Problem Reports could be notified and invited to test the new version of the package to see if it fixes their problem. A friendly support widget could be created to help users create problem reports. Perhaps functionality could also be added to direct users reporting common problems to documentation or other help resources to correct their problem. Advantages of implementing something like this: -Less bugs reported which makes actual bugs stand out more in Launchpad -Users are more satisfied with the experience of reporting their problems, without having to get technical -Users that might otherwise be intimidated by Launchpad will be reporting problems they experience in a less noisy way for developers -Users can keep track of their problems on Launchpad, and can check the progress of any bugs causing their problems -Users could be directed to help in fixing problems which aren't bugs, without going through the trouble and frustration of documenting their "bug" only to have a friendly Triager tell them it isn't a bug months later. -Trying to triage bugs becomes less like drinking from a firehose.

Written by hunteke the 3 Sep 09 at 06:56.

Perhaps we should be evangelizing answers.ubuntu.com instead then. If it's a bug, the answers site will likely quickly be able to discern it, and have it "upgraded." In the meantime, by not immediately jumping to "please report the bug", we avoid many false-positives.

Perhaps we should be evangelizing answers.ubuntu.com instead then. If it's a bug, the answers site will likely quickly be able to discern it, and have it "upgraded." In the meantime, by not immediately jumping to "please report the bug", we avoid many false-positives.

Written by hendi the 28 Feb 08 at 18:24.

Ubuntu Brainstorm was updated in January 2009. Since the idea #125 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #125 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by unimatrix the 14 Apr 08 at 12:33.

Ubuntu Brainstorm was updated in January 2009. Since the idea #6986 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #6986 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by Shnatsel the 20 Dec 09 at 20:11.

The title says it all.

The title says it all.

Written by Shnatsel the 20 Dec 09 at 20:15.

Make PPAs an alternative way of distributing release packages, so developers could be able to post only the source code to releases and link packages from PPAs to the release to make them easy to download and save Launchpad's disk space.

Make PPAs an alternative way of distributing release packages, so developers could be able to post only the source code to releases and link packages from PPAs to the release to make them easy to download and save Launchpad's disk space.

Written by _khAttAm_ the 21 Dec 09 at 10:28.

In Repo options in Synaptic, add a new tab which will allow searching for PPAs by package name.

In Repo options in Synaptic, add a new tab which will allow searching for PPAs by package name.

Written by MetalHellsAngel the 26 Dec 09 at 10:32.

I propose making it simple to add the PPA's on launchpad by making authentication keys clickable for import similar to apturl. as well as click import for the PPA address.

I propose making it simple to add the PPA's on launchpad by making authentication keys clickable for import similar to apturl. as well as click import for the PPA address.

Written by tommis the 7 Jan 10 at 01:18.

When you paint url in any program and click rigth mouse putton there should be a "add to the reposities" putton.

When you paint url in any program and click rigth mouse putton there should be a "add to the reposities" putton.