Written by AndrewLuecke the 7 May 09 at 03:17.

If it wasn't clear when I said that the old ideas shouldn't be imported months ago, it certainly is now.

I'd say, move them into their own category "needs revising", and slowly integrate them into brainstorm. As they are added into proper rationales.

They need to be filtered from the rest of brainstorm though, as barely any have been properly rewritten (I posted probably hundreds of old ideas as "Auzy", and I will not be revising them).

This may make brainstorm more manageable and cleaner

If it wasn't clear when I said that the old ideas shouldn't be imported months ago, it certainly is now. I'd say, move them into their own category "needs revising", and slowly integrate them into brainstorm. As they are added into proper rationales. They need to be filtered from the rest of brainstorm though, as barely any have been properly rewritten (I posted probably hundreds of old ideas as "Auzy", and I will not be revising them). This may make brainstorm more manageable and cleaner

Written by AndrewLuecke the 7 May 09 at 03:22.

Before a moderator approves an idea it should be:
1) Checked as it is now
2) Checked to identify if it is a dupe (a very large percentage of ideas are not being properly checked, whilst being obvious dupes)
3) Checked for accuracy. All mods should test the problem themselves to identify if it exists in cases where appropriate. None seem to be..

Before a moderator approves an idea it should be: 1) Checked as it is now 2) Checked to identify if it is a dupe (a very large percentage of ideas are not being properly checked, whilst being obvious dupes) 3) Checked for accuracy. All mods should test the problem themselves to identify if it exists in cases where appropriate. None seem to be..

Written by AndrewLuecke the 7 May 09 at 03:28.

It seems idea reviewers who don't think an idea should be approved can only rate 0, but they should be able to vote as -1.

Ideas at -2 in the sandbox (with at least 2 mods disapproving it for various reasons), should be automatically rejected. This prevents ideas sitting in the sandbox for weeks until it inevitably gets accidentally approved.

It seems idea reviewers who don't think an idea should be approved can only rate 0, but they should be able to vote as -1. Ideas at -2 in the sandbox (with at least 2 mods disapproving it for various reasons), should be automatically rejected. This prevents ideas sitting in the sandbox for weeks until it inevitably gets accidentally approved.

Written by AndrewLuecke the 7 May 09 at 03:34.

Problems which are actually non-existant are getting approved. In fact, ideas and solutions are getting approved that make a claim, yet have no evidence attached.

I could pretty much post an idea that claims that compiz consumes a large amount of GPU, and it would get approved, without ever provided any proof.

Therefore, it should be required to test all problems before approval, and ideas which aren't obvious and are lacking evidence should require more evidence first.

Problems which are actually non-existant are getting approved. In fact, ideas and solutions are getting approved that make a claim, yet have no evidence attached. I could pretty much post an idea that claims that compiz consumes a large amount of GPU, and it would get approved, without ever provided any proof. Therefore, it should be required to test all problems before approval, and ideas which aren't obvious and are lacking evidence should require more evidence first.

Written by AndrewLuecke the 7 May 09 at 03:52.

Whilst multiple problems can possess the same solution, there is no way to represent this on Brainstorm. So people end up voting 15x for the same solution, over 15 different problems. The votes aren't collated, so none stand out.

We need a way to link solutions to one another and merge the votes, when they are the same solution, so that solutions can stand out, and users aren't voting twice for the same idea.

An example that demonstrates this is the following problems:
- Users have difficulty determining which driver to install from the repos, as their don't know their chipset
- Drivers are too difficult to install

The solution for both may be:
- Maintain a driver repository which can install valid drivers for your specific hardware automagically.

This will help make brainstorm infinitely more usable, and more useful to developers.

Whilst multiple problems can possess the same solution, there is no way to represent this on Brainstorm. So people end up voting 15x for the same solution, over 15 different problems. The votes aren't collated, so none stand out. We need a way to link solutions to one another and merge the votes, when they are the same solution, so that solutions can stand out, and users aren't voting twice for the same idea. An example that demonstrates this is the following problems: - Users have difficulty determining which driver to install from the repos, as their don't know their chipset - Drivers are too difficult to install The solution for both may be: - Maintain a driver repository which can install valid drivers for your specific hardware automagically. This will help make brainstorm infinitely more usable, and more useful to developers.

Written by Darwin Survivor the 7 May 09 at 17:59.

If we implement negative voting, more moderators should be added so that moderators have more time to properly review each submission.

I think part of the problem is that there are WAY more suggestions than there are mods, so instead of each suggestion getting a good 2-4 minutes of checking (especially for duplicates), the mods only have time to check if it is marginally feasible and completely outlandish.

If we implement negative voting, more moderators should be added so that moderators have more time to properly review each submission. I think part of the problem is that there are WAY more suggestions than there are mods, so instead of each suggestion getting a good 2-4 minutes of checking (especially for duplicates), the mods only have time to check if it is marginally feasible and completely outlandish.

Written by lavinog the 2 Jun 09 at 06:33.

Ideas and solutions should be considered professional proposals.
If a user doesn't want to take the time to clearly present their idea or solution, then the idea must not be that important to them.
Ideas should be written without focus on personal opinions.
Ideas should use proper capitalization, and punctuation so that they can be read clearly.
They should avoid slang, slander, or signs of personal frustration.
Moderators can make small corrections to ideas, but the responsibility should fall on the poster.
A moderator should leave a comment if the quality is in question, and leave it up to the poster to correct any issues.
If the poster does not work to comply with the standards, then the idea will not be approved.

Ideas and solutions should be considered professional proposals. If a user doesn't want to take the time to clearly present their idea or solution, then the idea must not be that important to them. Ideas should be written without focus on personal opinions. Ideas should use proper capitalization, and punctuation so that they can be read clearly. They should avoid slang, slander, or signs of personal frustration. Moderators can make small corrections to ideas, but the responsibility should fall on the poster. A moderator should leave a comment if the quality is in question, and leave it up to the poster to correct any issues. If the poster does not work to comply with the standards, then the idea will not be approved.

Written by vexorian the 2 Jun 09 at 15:16.

Unlike what most people seem to think the intended use for marking something as duplicate is not to stop every single new idea from ever getting added. It is to stop an idea that was already made before from getting added.

It seems right now that mods are doing some very rushed pattern matching before deciding whether something is a duplicate or not:
Wrong way to enforce the duplicate rule:
There is already an idea ("Add a bicycle icon to pidgin emoticons") that contains the words "cycle" and "icon" therefore the idea ["A new install ubuntu icon for each release cycle"] is a duplicate.

Right way to enforce the duplicate rule:
Idea A and idea B mean almost exactly the same, therefore B is a duplicate.

Unlike what most people seem to think the intended use for marking something as duplicate is not to stop every single new idea from ever getting added. It is to stop an idea that was already made before from getting added. It seems right now that mods are doing some very rushed pattern matching before deciding whether something is a duplicate or not: <b>Wrong way to enforce the duplicate rule:</b> There is already an idea ("Add a bicycle icon to pidgin emoticons") that contains the words "cycle" and "icon" therefore the idea ["A new install ubuntu icon for each release cycle"] is a duplicate. <b>Right way to enforce the duplicate rule:</b> Idea A and idea B mean almost exactly the same, therefore B is a duplicate.