No worries about the review of the PR. As stated in the GitHub repo, your PR doesn't need to be merged — that can take time and we don't rush that process.
When we'll go through the submissions for a project, we'll take a look at your proposal and PR and will review them to rank everybody applying for the same project.
So you just need to focus on writing a good proposal and PR. Start with something small and react to feedback. If that one worked well, you can continue with another one if you want. One good, small PR is better than opening multiple half baked ones or tackling a big problem and getting stuck.
I have a bit of a backlog of proposals to work through, but I'll do my best to get it done tomorrow, so everybody has a chance to make changes over the weekend / early next week.
If there are general questions, please ask them here, so we don't have to answer them multiple times.
Filter out proposals, which are not related to any project or don't have a PR against one of our projects
The remaining ones are evaluated based on:
Does the proposal make sense — you understood the problem, you have a complete and more or less reasonable timeline.
How good is the PR. Is it a one line fix or is it something more complicated.
How did the interaction work out — both on Discuss and for the PR.
Find the best proposal for every project.
Rank the strength of the projects and decide which ones we feel comfortable doing.
Admittedly we had to be rather strict, since the number of slots is limited and we only want to pursue projects where we think that they have a good chance of succeeding.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.