[drupal-docs] Handbook 2

[Anisa]

Mind boggling over having to offer a reverse bounty for upgrades to a 
core module in an open source project aside, to get this done you need to:

1) Write up technical specs for the specific things you want done.  Are 
you limiting this to the items that were posted into the issues?  Aiming 
for 4.7?
2) Come up with an amount of $ for the bounty.
3) Figure out technical details, like, what if multiple developers want 
to work on this?  Do you pass it off to just anyone who says 'Ooo, me, 
me!' or just to 'experienced drupal developers'
4) Establish a reasonable timeline.

I think that's it...  As far as managing the developer who works on it, 
sou ne...  Ideally one of the three people who can make commits to the 
core should take a look at the code from time to time, under the 
presumation that they would know best about what is 'Drupalish'.

But...  of course you all knew that, right?  ;p

Anisa.
There's a reason why it's called Golden Week!

Dries Buytaert wrote:

>
> On 16 Apr 2005, at 19:44, Boris Mann wrote:
>
>>> Most of the features have been asked for 1-2 years ago so I wouldn't
>>> assume anyone is going to work on them, unless they are getting paid
>>> to. Maybe this makes for a good "reverse bounty" (see Boris' post at
>>> http://drupal.org/node/20301).
>>
>>
>> Dries, would you be willing to use Drupal.org money to do this? Are
>> there other things desired for Drupal.org that could be funded? Just
>> thinking out loud here...
>
>
> Sure.  I can help promote/organize it too, but can only commit to 
> doing part of the work it takes.
>
> -- 
> Dries Buytaert  ::  http://www.buytaert.net/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://drupal3.drupal.org/pipermail/documentation/attachments/20050420/56d00603/attachment.htm