We welcome contributions to the Va11yS Project in many forms, and there's always plenty to do!
First things first, please review the Va11yS Project's Code of Conduct before participating. It is important that we keep things civil.
If you are looking for something to work on, need some expert assistance in debugging a problem or working out a fix to an issue, our community is always eager to help. We hang out on Slack; look for the #open_a11y channel. To join, visit the IBM developerWorks Slackin page.
If you are a user and you find a bug, please submit an issue. Please try to provide sufficient information for someone else to reproduce the issue. One of the project's maintainers should respond to your issue within 24 hours. If not, please bump the issue and request that it be reviewed.
Review the issues list. and find something that interests you. You could also check the "help wanted" list. It is wise to start with something relatively straight forward and achievable. Usually there will be a comment in the issue that indicates whether someone has already self-assigned the issue. If no one has already taken it, then add a comment assigning the issue to yourself, eg.: I'll work on this issue.. Please be considerate and rescind the offer in comments if you cannot finish in a reasonable time, or add a comment saying that you are still actively working the issue if you need a little more time.
We are using the GitHub Flow process to manage code contributions. If you are unfamiliar, please review that link before proceeding.
To work on something, whether a new feature or a bugfix:
-
Create a fork (if you haven't already)
-
Clone it locally
git clone https://github.com/yourid/REPO.git
- Add the upstream repository as a remote
git remote add upstream https://github.com/ORG/REPO.git
- Create a branch
Create a descriptively-named branch off of your cloned fork (more detail here)
cd fabric
git checkout -b issue-nnnn
- Commit your code
Commit to that branch locally, and regularly push your work to the same branch on the server.
- Commit messages
Commit messages must have a short description no longer than 50 characters followed by a blank line and a longer, more descriptive message that includes reference to issue(s) being addressed so that they will be automatically closed on a merge e.g. Closes #1234 or Fixes #1234.
- Pull Request (PR)
When you need feedback or help, or you think the branch is ready for merging, open a pull request (make sure you have first successfully built and tested your changes.
Note: if your PR does not merge cleanly, use git rebase master in your feature branch to update your pull request rather than using git merge master.
- Any code changes that affect documentation should be accompanied by corresponding changes (or additions) to the documentation and tests. This will ensure that if the merged PR is reversed, all traces of the change will be reversed as well.
After your Pull Request (PR) has been reviewed and signed off, a maintainer will merge it into the master branch.
We have tried to make it as easy as possible to make contributions. This applies to how we handle the legal aspects of an original contribution. We use the same approach—the Developer's Certificate of Origin 1.1 (DCO)—that the Linux® Kernel community uses to manage code contributions. We simply ask that when submitting a pull request, the developer must include a sign-off statement in the pull request description.
Here is an example Signed-off-by line, which indicates that the submitter accepts the DCO:
Signed-off-by: John Doe <[email protected]>
If the contribution was derived from a WCAG Technique, please instead add the following sign-off line:
Signed-off-by: Jane Doe <[email protected]>. This contribution was derived by samples provided by WCAG techniques.
Please see Notice of copyright and disclaimers applied.