Hi Ignasi, Thanks a lot for getting a start on this. Here are some comments.
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. 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. 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? 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. We have the wiki for developer documentation (this guide definitely falls into that category) and we have the main site for user documentation. Once we are happy with this guide, we need to *delete* the contributing-to-jclouds page. Regards, Everett [1] https://gist.github.com/adriancole/5592785 On Jun 18, 2013, at 3:37 AM, Ignasi wrote: Hi! I've created a page in the wiki [1] explaining the new procedure to contribute code to jclouds. Its purpose it to provide a standard way to proceed, although steps like opening a JIRA, etc, can be ignored when it applies, as we already discussed it in the ML. Please, hava a look at it and feel free to comment/add/change anything (fixing my English would be highly appreciated :)). 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, since it is out of date (at least regarding the ICLAs). [1] https://wiki.apache.org/jclouds/How%20to%20contribute [2] http://jclouds.incubator.apache.org/documentation/devguides/contributing-to-jclouds/
