On 4 April 2014 00:38, Brian Wolff <bawolff(a)gmail.com> wrote:
what about directing new volunteers there, asking
them to submit their
code
revisions. For a patch that has been waiting in
silence for over a year,
any feedback will be better than no feedback.
You sure about that? I would imagine that having no one look at your code
for months, then having someone who doesn't have the authority to approve
it
nit pick it a little, followed by another couple months of waiting, to be
more frustrating then no feedback at all.
This is also completely the wrong way to go about open-source development.
The work priorities of volunteers are the thing that you, as manager of
paid staff, *can't* control, as opposed to the work priorities of paid
staff, which you very much can. If reviewing these old patches was in any
way interesting/exciting/fulfilling, volunteers would probably already have
*made* some contributions. Being occasionally tasked with
uninteresting/unexciting/unfulfilling tasks that Just Need Doing is one of
the things that paid developers *get *paid *for*.
--HM