Mr. Craft, I think you've hit one of the most important points in favor of the GNOME Innovation Project, and I thank you for that. It is indeed a quest for the user to file a bug report. The system is not very friendly with people who use their computer for simple tasks such as email, web browsing and music. Now, it is true that people who use linux tend to have more knowledge on computers than the average windows user, or mac user even, but is this a reason for turning down a project which will attempt to create a more comfortable environment for the proposal of ideas and projects? But also remember not to lose track--this project does not attempt to replace bugzilla; the project is intended to route the end-user's creativity to a channel GNOME can access. Now, I understand that tangible limits have to be created in order to decide what should be filed as an enhancement bug, and what should be filed as an idea. - Best regards, Wolter Hellmund On Thu, 2009-10-01 at 20:20 -0400, Jud Craft wrote: > There is one good reason why this is a good idea: GNOME's support > system is too compartmentalized. > > This shows up all the time in bug reports. People have no idea which > component to file against (for particularly tricky situations, even > developers have to do some investigation before they arrive at the > root cause of the problem). > > Detective work is not bad; but "a priori" detective work, of > debugger-caliber, before the user can even flag an end-user issue, is > not conducive to enabling user feedback. > > Under such a system, I could file what seems to me a general issue > about keyboard accessibility in GNOME, for example -- without having > the slightest clue what part of GNOME is actually responsible for > keyboard accessibility (and no, I don't have a clue). > > The management of such a system (how to link ideas and issues to their > components?) is definitely important, but the end-goal would be: > easier for the end-user to give feedback on a system he uses, but has > not helped build. > > How do other commercial projects (MSDN - Windows beta testing, Apple, > etc) allow user feedback? Do they expect users to discover what > component of Explorer is malfunctioning, or what plugin in Windows > Media Player they'd like to suggest a change to? Or does the system > aid them in automating as much of this homework as possible? > > > On Thu, Oct 1, 2009 at 5:06 AM, Rodrigo Moya <rodrigo gnome-db org> wrote: > > On Wed, 2009-09-30 at 11:37 -0700, Sandy Armstrong wrote: > >> On Wed, Sep 30, 2009 at 11:20 AM, Wolter Hellmund <wolterh6 gmail com> wrote: > >> > The project is intended to use a Brainstorm System, which is already provided by > >> > IdeaTorrent. It is already implemented in successful projects such as Ubuntu > >> > Brainstorm, SourceForge.net and others. > >> > >> Is there any data indicating that Ubuntu Brainstorm works better than > >> filing enhancement bugs? Are there any statistics about how many > >> Ubuntu Brainstorm ideas are actually implemented, and how many are > >> implemented largely due to feedback from Brainstorm? > >> > > AFAIK, brainstorm.ubuntu.com is used as the base (one of them, the other > > being bug reports and already existing feature enhancement requests in > > the bug tracker) for development of new Ubuntu releases. Popular ideas > > are converted to blueprints (bugs in the GNOME case I guess), then > > discussed during the UDS (Ubuntu Developer Summit) and assigned for the > > next cycle. > > > > _______________________________________________ > > desktop-devel-list mailing list > > desktop-devel-list gnome org > > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list gnome org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Attachment:
signature.asc
Description: This is a digitally signed message part