Trent W. Buck
trentbuck at gmail.com
Wed Feb 4 00:42:50 UTC 2009
Eric Kow <kowey at darcs.net> writes:
> (d) increase the availability of the darcs developers
> (e.g. 20% time, see below)
As I see it, this is two sub-points:
1. paying Fred to work on Darcs one day a week (salaried); or
2. paying Fred a fixed sum to implement a single feature (contract).
The second case has the same kind of fixed goal as a sprint, but is
appropriate for tasks that can't be achieved in a couple of days.
I think it also corresponds to "Google Summer of Code" and the
"Blueprints" concept in Launchpad (Ubuntu/Canonical).
Having a concrete goal means that the steering committee (with input
from the community) can work out up-front what the conditions are to
satisfy the task (i.e. a requirements document), and from that can
solicit contractors to provide a list of sub-tasks with time estimates,
and from *that* can work out how much the contract is actually worth (in
terms of cash).
> - Hiring developers: if we manage to raise lots of money, could
> we find a way to get some paid darcs hacking done?
> - Bounties: I doubt that bounties work, but maybe in the right
> contexts, and with some creative twists, we can make them work
These are other terms for (1) and (2), I think.
More information about the darcs-users