THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Note: This page is work in progress.
This workflow page is modeled after Spark Spark Contributing to Spark and Beam Become a Committer
There are many ways to contribute to Rya. All contributions, code or not code, are important.
Contributions:
There are many actions other than coding that build the trust we place in a committer - code review, design discussion, user support, community outreach, improving infrastructure, documentation, project management, etc. Here are some types of contributions. Any positive contribution to the project is welcome:
...
-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 find bugs/issues to work on:
-Browse browse issues in in JIRA and find one that you'd like to work on.
-Create create a JIRA account for yourself and email email dev@rya.apache.org your username and ask to be added to the contributors list for JIRA
-If if you're new to Rya, and you'd like to get your feet wet with a simple issue, search for issues labeled "beginner"
-Assign assign the issue to yourself, and mark the issue as "In Progress"
-Feel feel free to email email dev@rya.apache.org for help or advice
To contribute code:
-find/file the JIRA ticket for that topic
-fork the code from the Github Apache repository https://github.com/apache/rya-others can review the pull request and possibly suggest changes
-a committer will look review at it the pull request and integrate it in the code /or not
What does it mean to be a committer:
An Apache Rya committer has write access to the repository for merging pull requests, but you don’t have to be a code contributor to become a committer. Becoming a committer means that you have the project’s trust. Read the ASF documentation for more about being a committer in the Apache Software Foundation.
How to become a committer:
...