Re: identifying low-hanging fruit tasks for the community

[John Wagenleitner]

I think that's a great idea.  The Contribute page [1] on groovy-lang.org
currently links to the 'contrib' label for "..possible easy contributions
that could get you started on your journey to become a Groovy committer."
 I used that link when I first started looking for ways to contribute.  I
think any label name is good as long as it's used consistently and some
efforts are made to provide pointers in the comments.

[1] http://www.groovy-lang.org/contribute.html#code

Just a few suggested tickets to add to the list

https://issues.apache.org/jira/browse/GROOVY-8170
https://issues.apache.org/jira/browse/GROOVY-8042
https://issues.apache.org/jira/browse/GROOVY-7979


On Tue, May 2, 2017 at 6:36 AM, Paul King  wrote:

>
> Hi everyone,
>
> I was asked again recently to identify some potential tasks for various
> keen members of the community who want to help. We have done this to some
> degree in the past using various labels on jira tickets but I think perhaps
> we could look at potential improvements to how we identify and advertise
> such tasks.
>
> There were two things I was going to try. Firstly, some better consistency
> in our labels: we currently use these labels (at least - maybe more):
> beginner, easyfix, contrib, newbie, and help-requested. I was going to try
> to shrink that list. Secondly, I was thinking we could perhaps use Apache's
> helpwanted app/page: https://helpwanted.apache.org/.
> I don't know how popular or widely known it is but it seems worth a try.
>
> Thoughts or suggested tickets are welcome.
>
> My initial goal will just be to get a small backlog of such tasks
> available using a consistent label scheme and fed into the helpwanted app.
> I am happy to get the ball rolling and advertise what naming scheme I end
> up selecting (and adding that to the docs) but it will work best if a few
> folks chime in and get their favourite tasks added to the list(s). We don't
> need an extensive list of tasks, just ones that are easy for contributors
> to identify and for us to identify too so that we can ensure they remain up
> to date and contain the needed info for contributors to get started
> relatively easily.
>
> For anyone interested, the search I used:
>
> https://issues.apache.org/jira/browse/GROOVY-8044?jql=
> project%20%3D%20GROOVY%20AND%20status%20in%20(Open%2C%20%
> 22In%20Progress%22%2C%20Reopened)%20AND%20labels%
> 20in%20(beginner%2C%20easyfix%2C%20contrib%2C%20newbie%2C%
> 20help-requested)
>
> Cheers, Paul.
>
>

Some trivial tickets

[Yazad Khambata]

Hi,

I have been looking around to see if there some simple items I can
pick up to make some initial contributions. I see 3 trivial tickets
that I can work on if that's ok,

GROOVY-7388
DefaultGroovyMethods class's plus(T[] left,  right) have ambiguous errors

In this ticket I see Paul has requested a test case and has not
received a response, I could look at providing a test case and a fix
for this. Note I see that there also a duplicate filed but that is
closed without any work-log or comments.

GROOVY-5227
AbstractHttpServlet should extend GenericServlet directly instead of HttpServlet

Looks like this is one of the tickets where I may be able to provide
some analysis and suggestions and based on that a decision can be made
to either close it or implement it.

Both tickets have had some comments in 2016 but don't seem to have an
owner. Please let me know if I can pick them up. Thank you.

Regards,
Yazad Khambata