There are many ways to contribute to the project without commit. And it is best to start from no expectation of commit bits rather than trying to earn them.
When I started contributing to Solr, I did not ever expect to become a committer. So, I worked on things around it. Blogging, commenting on JIRA, creating my own website listing information derived from - but hard to find in - the actual project (http://www.solr-start.com/), running a mini-newsletter. You control all of that and can be the best you are in it. And specifically on documenting as a beginner. You are in the best position actually. Read the latest releases/issues, find out the best way to do the simplest thing, publish it on your own blog and/or offer to contribute to the official documentation. You have the eyes and sense of need that others - used to the project at its earlier version - do not. Often, those contributions are very valued. Similarly, tracking and resharing other people's writing on the web about that project are often valuable. Feel free to reach out to me directly if you would like to take that onboarding role within your chosen project. I would be happy to give some ideas based on my own journey with Solr. Again, the important mindset is NOT to expect the commit bits. Regards, Alex. On Mon, 16 Sep 2019 at 03:32, Ray Ma <d...@rayma.me> wrote: > > Hi ComDev, > > [Meta] > > I was going to private mail someone, since I wasn't really comfortable > talking about this question in a public list, but I want to start > trusting Apache people as an inclusive group. So... here goes nothing. > (Also, really sorry if this sounded like an over-dramatic fictional > piece.) > > [Actual Question Starts Here] > > I have just found an Apache project (I don't want to call anyone out), > and I just really want to contribute to it. The idea seems really > good! But there're a bunch of outstanding issues on Jira that's > preventing newcomers from contributing. I really want to deal with > these, but I'm not a committer, and I in no way want to "bypass" > whatever committership requirements the project may have. But seeing > the list of 20-or-so issues that I'm powerless to resolve... It's just > this sense of frustration and powerlessness. > > What can I do to help? I love the goals of the project, but it's hard > to get started without crucial information or even working development > instruction. Apologies for the genericness, it's just I don't want to > seem rude towards that project. > > Thanks, > Ray > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
