I don't know... I can't tell if it's any slower than using Planet or writing blog posts on m.o.

Tim

I feel like I'm speaking Martian lately.

IMO all enhancement requests should only go to Brainstorm. This will increase the likely hood that what is reported in Bugzilla can be acted upon efficiently by the resources available.

As zerojay has pointed out, new users can be intimidated by Bugzilla, and as qgil pointed out Brainstorm is more user friendly.

If this is the case, bug vs. enhancement request descriptor errors will more likely be made by new users in Brainstorm.
It also appears that it easier for general membership to comment in Brainstorm and this may provide more friendly guidance and training to new users to help reduce future errors.

Still not a decision and still Andre thinks that Bugzilla is the right default place for "specific" enhancement requests & gathering votes.

http://talk.maemo.org/showthread.php...926#post335926

Do as you wish but please decide something.

If we can point Maemo product managers to only one place instead of 2, great. But whatever the community prefers.

After using Brainstorm myself...

Brainstorm does seem to lend itself more to having a broad general desire and hashing out the best way of making that desire happen whereas an enhancement request sort of denotes that the user knows precisely what needs to be done and how. It feels much more targetted, whereas Brainstorm feels like "let's ask the collective what is the best way to go about this goal".

In this sense, I feel both have a place. Perhaps once a consensus is formed in Brainstorm, an enhancement bug should be filed pointing to the Brainstorming session.

Just an idea.

Ok, let me rationalize this a bit more.

If someone files a bug that happen to be changes as enhancement but the maintainers or the bugsquad, is so clear cut that a developer alone can consider it without involving product manager or change in the development plans, if it doesn't require votes or much discussion and perhaps even a patch can be attached... then there is no question that bugzilla is the place.

If someone has a proposal that he can't fix himself with a patch, or can't even describe accurate solutions, would need further discussion, perhaps votes and support, and anyway Nokia developers wold need to accommodate plans and discuss with product managers... then this is clearly something for the Brainstorm.

In practice I think it's easy to detect what proposals go where.

And in practice we could

- document this
- resolve new proposals landing in bugzilla as Invalid pointing to Brainstorm
- do the same for current enhancement requests that fall in the second category and are not in the plans currently
- keep in bugzilla the take-or-leave specific enhancement requests plus those that can be resolved soon based on current plans

One idea might be to allow people to post "issues" to Bugzilla whether they are bugs or enhancements. Then, if an easy fix or patch isn't available at the time of posting, link the bug report to Brainstorm, where people can hash out ideas and Solutions. Then, when a certain Soultion has garnered enough support, it can be copy/pasted to the original bug report, with a link back to the popular solution.

Tim

qgil's last post sounds good to me, except for:
In my experience with other projects (e.g. MythTV) people don't like their bugs marked as invalid - it gives off a rather 'rude' feeling. (Note that this is probably largely just a problem with the terminology used in Bugzilla). Instead, if someone could actually turn the bug report into a brainstorm idea for the user, rather than make the user do it themselves, that might be better.

Sounds like something the community council should weigh in on. *hint, hint*

Would DUPLICATE with the URL field pointing to the brainstorm page be a better resolution? We could create a dummy bug to dup all brainstormed enhancements.