Thank you for your feedback. Now I finally know how to make contribution to the community. Actually I not only wanna to contribute to the Apache community but also have a highly interest in participating in Google Summer of Code next year. I want to start earlier than others from now on. If there's any advice for me about how to prepare for Apache's GSoC next year? And how could I become the commiter of a project? Is there any tips for it?
Best regards, Jack Tsai Woonsan Ko <woon...@apache.org> 於 2018年8月30日 週四 下午10:33寫道： > Hi Jack, > > On Thu, Aug 30, 2018 at 5:55 AM Jack Tsai <jack1998870...@gmail.com> > wrote: > > > > Dear Sir/Madam, > > > > Thanks for the feedback. Double check again, so if there's an issue which > > shows the "open" tag, I could just comment on it and show that I am > > researching it first. Then I can make the pull request regarding to this > > issue. Is that OK for pulling request to the issue which has not > > distributed or already assigning to somebody? Is it because I am not the > > "developer group" member or I am a newcomer so that I cannot see the > > "Assign to me" button on JIRA? How should I do to dig deeper in a > community > > or a project? Could you please give me some instructions? > > In most projects from my experiences, only committers, who earned the > committerships based on their past contributions, are able to assign, > resolve and close JIRA tickets. You now have a good chance to start > contributions. ;-) See [1] for detail. > When you find somethings to contribute from JIRA or the Help Wanted > [2], I'd recommend you to start discussions in the developer mailing > list as well as commenting in the JIRA tickets. Sometimes committers > do not have enough time to read all the JIRA ticket comments, but the > developer mailing list is the single source of truth all the time in > our community. > Let me give an example: > - Suppose you find a JIRA ticket you can contribute for. > - I'd post a message in the developer mailing list to express your > interest to help with and a plan (e.g, PR provision), and possibly ask > if anyone else is already working on (especially if the JIRA ticket > was already assigned to a committer). Perhaps you can get responses > from people in the mailing list in some days. > - Once you get a response, you can submit a pull request and wait. It > could take some time for committers to take a review. > - If there's no response, you might want to post the message again. > Sometimes the initial message was not clear to others, from my > experience. Keep belief and patience. ;-) > > If anything is not going so well, let us know. > > Regards, > > Woonsan > > [1] https://www.apache.org/foundation/getinvolved.html > [2] https://helpwanted.apache.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
