What could be done to improve the OM development process?
oberger at ouvaton.org
Wed Aug 13 14:09:16 CEST 2008
Holger Freyther <zecke at openmoko.org> writes:
> On Wednesday 13 August 2008 00:05:14 Jeffery Davis wrote:
>> 2. Better communication between the development community and the end
>> user community. I have yet to see anyone say they're pleased
>> as punch with the keyboard. When almost everyone is unhappy, closing
>> bugs as 'working as intended' is pigheaded.
> as this action is misunderstood a couple of small words. What is the
> bugtracker for? The way we have used docs.openmoko.org so far is to make it
> an engineering tool. The assigned/owned tickets tells/informs engineers what
> to work on, when to get it done (milestone) and how important that is.
Whereas us users have been assuming that it was an open bugtracker for
Maybe there would be a need for some other Bug-tracking tool, which
would clearly support the separation between support-oriented
bugtracker (external) and engineering-oriented one (internal maybe) ?
I don't think trac's is powerful enough to play both roles without
much frustration from either side (but I may be wrong).
In any case, a policy should be drafted and announced widely. And
mailing-lists for users vs bugtracker for engineering is not
satisfactory for any open project, of course.
Also, maybe you would need to rely on an organisational tool like a
todo manager to assign work to people, whereas bugtrackers may only be
there as a repository of knowledge and a communication tool ?
My 2 cents.
More information about the community