Hello
I made a proposal for how we could handle this tricky
issue on
http://meta.wikimedia.org/wiki/Developer_payment.
I invite you to read it and to comment if you wish :-)
My belief is that it is a decent compromise between
all the wishes expressed (well, at least I hope).
I remind you that this is a trial, not a permanent
decision.
The plain idea is
* that the opportunity is taken to clean up and
organise better a couple of pages (such as
http://meta.wikimedia.org/wiki/Development_tasks)
* to avoid bureaucracy.
**If an editor or the foundation wishes for a task to
be done, just ask
**If a developer is ready to take care of a matter,
just mentions it on development task. If he would be
interested by getting in contract, please mentions it
on [[development payment proposal]] (or any title you
think best)
*to always ensure that this task is welcome by the
entire community (please discuss it before on mailing
lists or meta)
*to ensure that this task makes consensus amongst the
developers (hence the involvment of the developer
committee - no task will be paid for, which will go
against the general direction set by the developers,
or is technically nonsensical)
*to ensure that this task is interesting the
foundation (hence, the decision to pay or not for a
task will be made by the board)
Refining the proposal is welcome. Otherwise,
basically, this is in your hands now. The basic
structure is there, use it or do not use it :-)
ant
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
I made a proposal for how we could handle this tricky
issue on
http://meta.wikimedia.org/wiki/Developer_payment.
I invite you to read it and to comment if you wish :-)
My belief is that it is a decent compromise between
all the wishes expressed (well, at least I hope).
I remind you that this is a trial, not a permanent
decision.
The plain idea is
* that the opportunity is taken to clean up and
organise better a couple of pages (such as
http://meta.wikimedia.org/wiki/Development_tasks)
* to avoid bureaucracy.
**If an editor or the foundation wishes for a task to
be done, just ask
**If a developer is ready to take care of a matter,
just mentions it on development task. If he would be
interested by getting in contract, please mentions it
on [[development payment proposal]] (or any title you
think best)
*to always ensure that this task is welcome by the
entire community (please discuss it before on mailing
lists or meta)
*to ensure that this task makes consensus amongst the
developers (hence the involvment of the developer
committee - no task will be paid for, which will go
against the general direction set by the developers,
or is technically nonsensical)
*to ensure that this task is interesting the
foundation (hence, the decision to pay or not for a
task will be made by the board)
Refining the proposal is welcome. Otherwise,
basically, this is in your hands now. The basic
structure is there, use it or do not use it :-)
ant
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail