Propose your solution
Attachments
No attachments.
Duplicates
Comments
Biornus
(Idea reviewer)
wrote on the 3 Oct 08 at 18:35
|
|
|
|
Leaving a silly comment doesn't insure that its being considered, if your idea was about improving communication between Brainstorm and developers it was a completely different matter.
|
|
|
|
Of course some feedback saying that the team will or will not consider an idea is no guarantee for that it will happen, but it can be an indicator nevertheless.
|
|
cheesehead
(Brainstorm admin)
wrote on the 4 Oct 08 at 03:08
|
|
|
Do feel free to ask nicely in the appropriate IRC channel or mailing list. The Brainstorn moderators don't need to do everything for us - most of us are ostensibly adults.
Asking nicely for a feedback quote from the appropriate project(s) or team(s) is a good idea.
Expecting one based on Brainstorm votes is rude...why should they follow the voting here?
|
|
|
What is the freaking point of Brainstorm if the only way to get any response from developers is to talk to them directly on a mailing list or IRC? If I was in contact with the developers of a given project via the mailing list or IRC I would not be bothering with brainstorm would I.
Sorry, I know you mean well, but the developers can't stick to this attitude that "We are too busy coding to speak to regular people, if you arent on the mailing list then tough".
There needs to be an attitude shift that it is polite and proper that developers give some feedback on suggestions here if they have proven to be very popular. It's not like you need to comment on every single thing, only the very popular. There might be one suggestion relating to your project in any given month. It's not asking much.
|
|
Craig73
wrote on the 5 Oct 08 at 20:13
|
|
|
|
Are you looking for response from Canonical? or from the Ubuntu Community Developers?
|
|
|
I would say feedback from canonical, or from community developers, or even upstream developers, if they happen by, create brainstorm accounts, and gets registered as developers of a certain project or subproject (if it indeed is possible to register as such. If it isn't, it should be.)
Cheesehead, I don't know if you are a developer yourself or not, but I can sympathize with the stance of not wanting to put any extra strain on already busy developers.
However, I think its in the developers own best interest to pay attention to this here brainstorm site. Many of the ideas here are excellent, and I believe implementing them will increase the usefulness and popularity of the projects in question.
Big companies pay good money for focus-groups and other groups of people to beta test things, or just say what they think about various products (be it software, cars, mp3-players, etc). Brainstorm can provide similar or even better information about open source projects for free!
Then we of course have the kind of developers who work on projects to scratch their own itches only. These developers would probably not care about ideas here. Nothing wrong with that, and I'm not proposing Canonical hire a bunch of thugs to pay these devs a visit.
Just saying that it might be nice for people who spend considerable time trying to come up with nice and do:able improvement ideas for projects to get some feedback on them if the rest of the community likes them, that's all.
|
|
|
+1 it's a good idea to close the feedback loop-time between isea/brainstorm-vode to dev/team feedback.
One might even have a tab on the user dashboard: idea I voted for that has received dev feedback...
|
|
Hobbsee
(Ubuntu developer)
wrote on the 6 Oct 08 at 13:23
|
|
|
This might be nice.
But I can imagine most things getting answered with a "this is feasible" or "this is not feasible" and marked as such. That says nothing about any action being taken on the particular wish, by the person commenting.
If you want to require that action *is* taken by whoever comments, then I think even fewer people would comment.
|
|
Hobbsee
(Ubuntu developer)
wrote on the 6 Oct 08 at 13:55
|
|
|
Having thought about this a little more, I'd like to point out that there are various mails to the development mailing list requesting that people look at brainstorm, and comment on ideas.
So, I don't think it's a problem of developers not knowing about them.
I think it's a problem of them being too busy, or having other reasons for not looking at them.
I'm not sure of the best resolution - but i'm sure it's not to try to shove your things in front of their nose (I'm sure they'll come here if they're looking for something to implement).
Mandating that the paid developers spend X hours a week on brainstorm (such as they do with the sponsorship queue) will get less things in Ubuntu get done - and the community developers won't follow that mandate anyway (unless they want to, of course). Whether that's a worthwhile thing to do is up for interpretation.
|
|
|
I'm sure the developers pay attention to the most popular ideas. However, I do agree that good ideas here should be made more visible to the community. One possible way of accomplishing that, which should also be relatively easy to implement, was if once an idea hit 500 votes, it would be sent out to ubuntu-desktop@lists.ubuntu.com. This would attract alot more attention to it, resulting in more votes one way or the other.
+1
|
|
Jimbo99
wrote on the 6 Oct 08 at 19:19
|
|
|
If you are asking that once a certain number of votes are cast in favor of a brainstorming comment is reached then a developer should comment, I see no problem with that suggestion. It simply puts the onus on the developers to respond to solid ideas so that the participants of this site don't feel jilted.
I would also suggest allowing the participants of the site to vote up or down on how acceptable the developer's response is so that we can learn who those developers are that don't really see value in this site nor are willing to participate with the people voting on ideas.
|
|
Craig73
wrote on the 6 Oct 08 at 20:19
|
|
|
Right now though it is probably in their best interest to NOT respond. I would hope they are heavily focused on coding/fixing the up coming release.
The benefit of the internet and brainstorm is ideas are captured every few seconds... but that is the drawback as well. If they are here providing feedback, they aren't getting the precious coding done :-)
While it doesn't provide any satisfaction to the latest creative burst... the ideas will likely get seen during the next planning/requirements cycle.
|
Post your comment
|
