Agreed.
Some things on JIRA which you might also want to setup/consider:
* Add some components -
https://issues.apache.org/jira/plugins/servlet/project-config/RYA/components
* Figure out what the first release version will be -
https://issues.apache.org/jira/plugins/servlet/project-config/RYA/versions
* Consider using a different workflow. It's nice to have the ability for
users to note when they have some code ready for committers to review.
The current workflow does not have this step -
https://issues.apache.org/jira/plugins/servlet/project-config/RYA/workflows
If you want to go pull-request based, there may be some additional hooks
you can request INFRA to set up. Making it clear how you _want_ new
users to contribute to the codebase is very important. This is also
relevant for existing committers (e.g. can committers commit their own
code w/o review? is there a required review period? minimum reviewer(s)?
etc.) Focusing on how you expect committers and contributors to interact
with the codebase is important to write down (as you let it evolve later).
Seetharam Venkatesh wrote:
Makes sense - please document it in the wiki.
On Mon, Nov 16, 2015 at 9:27 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/
