> To contribute code: > -find/file the JIRA ticket for that topic > -fork the code from the github Apache repo > -clone the fork, create a new branch, push commits to the branch > -create a pull request and add it to the jira ticket > -a committer will look at it and integrate it in the code /or not
I'm not a git expert but many projects use "one commit per pull request" policy for efficient management of master branch. Patch file also. On Tue, Nov 17, 2015 at 2:26 AM, Adina Crainiceanu <[email protected]> wrote: > Hi all, > > We need to figure out how people can contribute to Rya, and what the > workflow should be. I looked at other projects (Accumulo, Spark) and the > workflow seems to be something like: > > To report a bug/propose work: > -create a JIRA ticket for the issue, using the Apache JIRA system: > https://issues.apache.org/jira/browse/RYA (new users need to create a user > account) > > To contribute code: > -find/file the JIRA ticket for that topic > -fork the code from the github Apache repo > -clone the fork, create a new branch, push commits to the branch > -create a pull request and add it to the jira ticket > -a committer will look at it and integrate it in the code /or not > > > Here are the detailed instructions from Spark: > https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingCodeChanges > Maybe we can create something similar. > > I think the committers should follow the same process. > > What do you think? Can someone try this workflow to see how it works? > > Thanks, > Adina > > > > -- > Dr. Adina Crainiceanu > http://www.usna.edu/Users/cs/adina/ -- Best Regards, Edward J. Yoon
