There are absolutely no guidelines at the moment on what makes a good idea. And theres many reasons we need them!
- People keep saying that we are barking up the wrong tree with coding ideas, because "Canonical doesn't do coding" or "canonical shouldn't be inventing new standards".
- We need to know if you want new project ideas, or just enchancement ideas.
- What are you expecting us to write in an idea. You should present examples of ideas, and the format you want us to write them in. And example format may be:
Title: Clear and concise. Mention affected programs if any
Description: Summary/idea, what happens now in the program, benefits of implementation, disadvantages of implementation, etc.
- Without an example, what are you expecting? We need a few examples! So that we know the best ways of doing things
- Should we be targetting certain programs only, do you want us to suggest new protocols, or are they outside the scope of brainstorm? Do you want us to suggest new standards? Without a clear specification of what the ubuntu team actually does, and what they dont do, we cant optimise the process.
- Are ideas posted upstream?
-Help us, help you by explaining why some ideas are particularly good
- Its Software Engineering 101, we are expected to submit random ideas, but we don't know enough about the ubuntu development teams to submit the best choices
- Outline coders strengths in the team. If you have many coders who are good with image processing, let us know, we will place an emphasis on image processing ideas
Tags:
(none)