2009/12/16 Alex Parker <parker.alex.e_at_gmail.com>:
>
>
> 2009/12/16 Alex Bennee <kernel-hacker_at_bennee.com>
>>
>> Well if the Rockbox project wants to be serious about soliciting
>> contributions from outside the core team it is a problem. The current
>> method of sitting in IRC and badgering developers
>> and hoping you'll get lucky in getting a review/commit is obviously
>> not sustainable.
>>
>> I suspect it's not something that will be resolved in the current
>> release cycle though!
>>
>
> We are well aware of how frustrating this is - but what would you do to
> improve it?  There are limited people that know the code well for each
> particular area, and ultimately with a 100% volunteer spare time project you
> can't force people to review code.  Do you have any suggestions as to what
> we could do?

Well one suggestion would be to have nominate a person responsible for each
Flyspray Category area so at least there is a first port of call to
contact. At the
moment queries in IRC often lead to "I dunno the code" answers and leave the
contributor none the wiser who to approach.

Is it possible to get Flyspray to list all open tasks from a
particular category?
The search functionality seems to want some sort of text to search (obviously).

At the moment all I have is the main RSS feed which I keep an eye on
for relevant
new tasks when they come up. I'd happily take responsibility for
triaging the Playlist
category if I could see a list of all outstanding bugs, patches and
feature requests for it.

Of course I would still need a core team member to review and commit,
but at least
I could weed out stale stuff and review what is currently there.

> Incidently, whilst this is far from perfect it has been like this for years,
> and the project seems to do not too badly :)

Don't get me wrong, Rockbox is a great project and has achieved a lot.
However past
success shouldn't be an impediment to making it even better in the future :-)

-- 
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk