You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Yasser Zamani <ya...@live.com> on 2017/02/01 16:06:43 UTC

How to select which issue to work on?

Hi there,

I have some time and energy which I love to spend on helping Struts.

I know it's possible by answering user questions, documentation, examples, unit tests and providing patch for issues.

All of them are clear enough for me but some things about issues.

How to avoid parallel duplicate work on an issue? e.g. does 'unassigned' mean no one already work on it?

After that, how to select which issue to work on? e.g. is it better to solve old reported one or newer ones? or between issues with same priority, which things can make help to select better one to work on?

Or any further recommendations please?

Thanks in advance!

Re: How to select which issue to work on?

Posted by Lukasz Lenart <lu...@apache.org>.
Hi,

As others already said, pick unassigned issue, post a comment that you
will be working on it, and prepare a PR which references the issue -
just use issue's key in PR's title.


Thank you & Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2017-02-01 17:06 GMT+01:00 Yasser Zamani <ya...@live.com>:
> Hi there,
>
> I have some time and energy which I love to spend on helping Struts.
>
> I know it's possible by answering user questions, documentation, examples, unit tests and providing patch for issues.
>
> All of them are clear enough for me but some things about issues.
>
> How to avoid parallel duplicate work on an issue? e.g. does 'unassigned' mean no one already work on it?
>
> After that, how to select which issue to work on? e.g. is it better to solve old reported one or newer ones? or between issues with same priority, which things can make help to select better one to work on?
>
> Or any further recommendations please?
>
> Thanks in advance!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: How to select which issue to work on?

Posted by Konstantin Priblouda <kp...@yahoo.com.INVALID>.
Usually  it would be an unassigned issue.  Any ou can always ask aktive developers directly onm the list, whether somebody is working on it. ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- JTec quality components: http://www.pribluda.de/projects/ 

    On Wednesday, February 1, 2017 5:06 PM, Yasser Zamani <ya...@live.com> wrote:
 

 Hi there,

I have some time and energy which I love to spend on helping Struts.

I know it's possible by answering user questions, documentation, examples, unit tests and providing patch for issues.

All of them are clear enough for me but some things about issues.

How to avoid parallel duplicate work on an issue? e.g. does 'unassigned' mean no one already work on it?

After that, how to select which issue to work on? e.g. is it better to solve old reported one or newer ones? or between issues with same priority, which things can make help to select better one to work on?

Or any further recommendations please?

Thanks in advance!