groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pascal Schumacher <pascalschumac...@gmx.net>
Subject Re: Disable auto-assignment of jira issues?
Date Sat, 16 Jan 2016 12:17:02 GMT
http://www.groovy-lang.org/contribute.html

Am 16.01.2016 um 09:19 schrieb jim northrop:
> Do we have an up-to-date guidebook on how to contribute to Apache 
> Groovy or is the process unclear ?
> thx
>
> On 16 January 2016 at 06:06, Guillaume Laforge <glaforge@gmail.com 
> <mailto:glaforge@gmail.com>> wrote:
>
>     I've moved forward and removed all component leads, and set back the
>     default assignment to the "default project assignment" which is... "no
>     assignment". So we're good now on that front.
>
>     Perhaps the next step would be to do a pass on all currently assigned
>     issues and remove all assignments?
>     The problem with that though is that doing it large and wide might
>     remove assignments that are indeed really being worked on...
>     What do you think?
>
>     Guillaume
>
>     On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
>     <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>> wrote:
>     > Hello everybody,
>     >
>     > I think should disable auto-assignment of jira issues. Dozen of
>     issues are
>     > assigned to people who do not currently work on them. I believe
>     this stops
>     > people from contributing, because they think somebody is already
>     working on
>     > the issue. It also mislead users to expect that the issue will
>     be fixed
>     > soon.
>     >
>     > What do you think?
>     >
>     > Cheers,
>     > Pascal
>
>
>
>     --
>     Guillaume Laforge
>     Apache Groovy committer & PMC member
>     Product Ninja & Advocate at Restlet
>
>     Blog: http://glaforge.appspot.com/
>     Social: @glaforge / Google+
>
>


Mime
View raw message