Clytie Siddall, 11-01-2007 09:11:
On 11/01/2007, at 1:09 AM, Kirill S. Palagin wrote:
First of all, I am not talking about monetary bonus here

Drat. :D

- strictly
project-related bonus.

I am talking about granting the right to get particular issue fixed in
exchange for certain amount of work. Specifically, for confirming, say,
20 issues, volunteer can choose issue and it will be fixed in reasonable
timeframe.
I understand that some issues will require non-trivial resources and
developers can deny some issues (but as exception and with some
explanation).

Taking into account the number of issues raised per day, the number of developers and the ammount of time to fix non trivial issues or to add a feature, I think the developers wouldn't have enough resources and time.
We would end up with a lot of credits without founds ;).

The reason to ask for such a benefit is very simple - some issues exist
for years and nothing is being done about them, so somebody (even
non-developer type!) can do something to fix important issue (besides
campaigning for votes).

I think the need to encourage more participation is something we do need to discuss. A great deal of work is being done by very few people, in at least some cases (mac-porting and vi are two of which I know personally‚, and we all know how much more we could get done if we had a bit more help.

I support Kirill's idea. I know some people, at least, are very frustrated with the length of time it takes to resolve some issues, so this would not only raise participation, but help get rid of some of these outstanding issues. Even if they aren't fixed, at least they can be resolved, and stop cluttering up the tracker.

I went to log an issue reported by a user today, only to find it had already been reported ... which is fine, but for version 2.0.2? And still completely unresolved?

Well... what about an issue reported for 1.1, with more than 100 votes?
<http://www.openoffice.org/issues/show_bug.cgi?id=24969>

It's no wonder some people become frustrated by such a situation. OTOH, we have equally frustrated project members badly needing participation. Maybe we _can_ scratch each other's back on this.

Where would we start? :)


If there is some issue someone thinks that it is much important to fix, even if it's not a stopper (as a highly requested new feature which its lack makes users have to use MS Office), we could buy attention to this, asking on the [EMAIL PROTECTED] list or on the respective project list.

The issue is that we need more developers resources (what about to raise an issue for this ;D?).

QA users choosing some issues wouldn't be either cosmethical to the outside world. The community would still complaining about old bugs or lack of highly requested features.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to