savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-help-public] [sr #107497] "Request for Inclusion" is too vague


From: Chris Bryant
Subject: [Savannah-help-public] [sr #107497] "Request for Inclusion" is too vague
Date: Mon, 18 Oct 2010 18:24:14 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

Follow-up Comment #2, sr #107497 (project administration):

I've thought about this as well, having been a requester on many occasions. 
However, as a maintainer it takes on a whole new level of consideration.  The
easiest solution working within the existing framework might be to have a
selection requirement, where one requesting "inclusion" must select the
squad(s) they are interested in, thus identifying their desired role(s), such
as Technical Writers, Developers, Managers, Maintainers, etcetera.  This
places responsibility on the Maintainers, however, to approach their projects
in a formal way, exercising due diligence in creating logical squads for their
members.  Alternatively, one could be required to select an unassigned task or
bug they wish to work on; again, if no bugs or tasks exist...  It all comes
down to work-flow and giving the Maintainer the most information up-front
about a volunteer and what their intent is.  Will this person be of use to the
project - that is the question :)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?107497>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]