Thanks for checking! > 1. I think we can safely remove the legacy-jclouds row from the Git repositories table. It doesn't have any impact at all on contributing.
It was there just to show which repos exist right now. Existing forks previous to the move to the ASF will point to the legacy* in github, so I just added it to the table to help people know what those repos are. I agree to remove it, btw :) > > 2. Under the review process, I was still under the impression that we required an explicit +1 for non-committers at the end of the review to make it clear that the PR is completely finished review and ready to be merged. Will add this step too. > > 3. For Commiting the changes to the ASF repo, I have been using the process that Adrian outlined in this gist [1] early on. It's been working really well for me. Is there a particular reason to use patches? Is this just a matter of personal preference? Just because it is what I used :) I see it a bit easier and also generates the patch for the Jira issue, so I think it could be a good way to proceed. Does anyone have any preference? > > 4. Below you mention, "Once we are happy with it, we should update the "how to contribute guide" in the main site [2] with the contents in the wiki". > > Please no!!! This was my biggest concern when we decided to start using a wiki. Documentation needs to be DRY too. We must not duplicate our docs. Totally agree!
