Actually 116 with the re-opened ones, or in progress. On Sat, Jan 16, 2016 at 6:11 AM, Guillaume Laforge <[email protected]> wrote: > There's about 113 issues currently assigned (if I performed the right > JIRA query) > > On Sat, Jan 16, 2016 at 6:06 AM, Guillaume Laforge <[email protected]> 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 >> <[email protected]> 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+ > > > > -- > Guillaume Laforge > Apache Groovy committer & PMC member > Product Ninja & Advocate at Restlet > > Blog: http://glaforge.appspot.com/ > Social: @glaforge / Google+
-- Guillaume Laforge Apache Groovy committer & PMC member Product Ninja & Advocate at Restlet Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+
