Hi, In step (1) you may want to have a pointer to the github documentation on how-to fork a project there say something along the lines of " For additional details on forking a project using github see the following <url> ".
You may also want in step (14) to point to the page for any requirements that a patch needs to meet to be accepted (unit tests..) within the project (assuming someone may land on this page via a google search). *Vince Ford* GemFire Sustenance Engineering Beaverton, OR USA 503-533-3726 (office) http://www.pivotal.io Open Source Project Geode https://geode.incubator.apache.org/ <https://network.pivotal.io/products/project-geode> On Thu, May 28, 2015 at 5:09 PM, William Markito <[email protected]> wrote: > Hey folks, > > Here is the draft page for our code contributions process, which current > just covers GitHub but soon will have steps on using only JIRA ticket + > patch. > > This is based on our recent discussions here on the list. > > Please visit/play with the process and fix it if needed... > > It covers things like GitHub PR submission, Accepting/Rejecting PRs, and > such, following git-flow + JIRA as we have discussed. > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=57903992 > > Thanks, > -- > William Markito Oliveira > -- For questions about Apache Geode, please write to > *[email protected] > <[email protected]>* >
