...
- Use our project and provide feedback.
- Ask and answer questions on the dev@rya.incubator.apache.org users list
- Contribute javadocs, documentation.
- Provide us with use-cases.
- Report bugs and submit patches.
- Contribute code.
- Contribute to the Rya website
- Help spread the word about the project
- Review pull requests
- Verify releases
- Anything else that contributes to health of the Rya project and community
...
-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 issues in JIRA and find one that you'd like to work on.
-Create a JIRA account for yourself and email dev@rya.incubator.apache.org your username and ask to be added to the contributors list for JIRA
-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 the issue to yourself, and mark the issue as "In Progress"
-Feel free to email dev@rya.incubator.apache.org for help or advice
To contribute code:
...
Step 0: Clone and Update your local copy of Apache Rya -Incubator repository
Step 1: Add a remote to the fork referenced in the PR and fetch the branch in the PR.
...
Step 0.1: Clone the Apache Rya -Incubator repository
git clone https://gitbox.apache.org/repos/asf/incubator-rya.git incubator- rya-apache
Step 0.2: Update your repository
...
git remote add jej2003
https://github.com/jej2003/incubator-rya.git
git fetch jej2003 input_format_fix
git checkout input_format_fix
...
The repository for Apache Rya website is at https://gitbox.apache.org/repos/asf/incubator-rya-site.git.
- master branch is the source in markdown for the Jekyll tool.
- asf-site branch is the compiled HTML that is deployed to the webserver.
Part 1 (merging into master): Follow the steps above, but using the incubator-rya-site repository to merge the changes from the PR made against the master branch of the incubator- rya-site repository into the incubator- rya-site master branch
Part 2 (merging into asf-site): If a corresponsing corresponding PR was made against the asf-site branch, and that PR corresponds to the changes made to master, you can follow the steps similar with Part 1 to merge into asf-site. Be sure that the asf-site matches content in master. It might be safer to ignore the asf-site pull request and compile the modifications from master as below:
...
Step 2.3 Build the website, test the changes, and compare the result with the current website. Note that different versions of jekyll will generate different structures for the website. If the new website has a different structure than the old, and that was not the intention (for example if a download.html file is created instead of download/index.html), update your version of jeckyll
cd content/
bundle exec jekyll serve
Step 2.3 Move the content/target folder out of the way, you will commit this separately.
mv content/target/ ../
Step 2.4 Checkout asf/site, create a new branch, remove old content
git checkout --force origin/asf-site
git checkout -b another_new_branch_name_here
rm -r content
Step 2.5 Now copy the folder formally named target/ into the project, renaming it to content/.
mv ../target/ ./content
Step 2.6 Use git status to observe changes. The css and other template files are probably not changed. If they are flagged as modified, investigate CRLF or other trival differences. See .gitattributes. Try git diff *css. The file permissions might be different: chmod -R 755 *
Step 2.7 When satisfied that all looks OK, commit changes
git add [new and modified files]
...
git checkout asf-site
git merge
another_new_branch_name_here
Step 2.9 If there was a PR against the asf-site branch, amend the commit message so that it closes the PR (Github Info here). After running the command below, add the append the following line to the commit "Closes #123 from usrname/branchname
". Note theat "#123" refers to the PR number in GitHub
...
Step 2.11: Delete PR branch.
git branch -D
another_new_branch_name_here
Closing Stale Issues on Github
...