We welcome all contributions to JSS and thank you in advance for them! Below are a few ways of contributing to JSS.
If you're using JSS as shipped by a distribution, we recommend filing an issue downstream first. In the case of a RHCS, RHEL, or Fedora release, the correct bugtracker is the Red Hat Bugzilla instance.
If you don't hear a response at the appropriate downstream tracker or if you think the issue exists upstream as well, feel free to file an upstream issue.
Most of the Dogtag software (the new home of JSS) uses Fedora's pagure.io for bug tracking; JSS's issue tracker can be found there as well. Note that this requires a Fedora account to create bugs. If this isn't of interest to you, feel free to file an issue on GitHub instead; it will still get read and responded to.
If you'd like to contribute code to JSS, feel free to open a pull request against JSS. We'd recommend filing an issue (see above) if you'd like to introduce major change to JSS. This gives us a place to discuss the changes before they are proposed.
Please fork the repository and make your changes in a new branch; before
proposing the pull request, rebase your branch against upstream master.
To test JSS locally, follow the build instructions.
Additionally, it is possible to run the CI container instances locally;
follow directions in the CI Overview. We'd suggest making
sure a Fedora build passes (e.g., fedora_28) and the stylecheck
image passes as well. Then, feel free to open a PR.
If you're looking for more information, we suggest reading about the GitHub Flow and reaching out to the developers if you need any assistance.
If you wish to discuss contributing to JSS or an issue, there are a few forums of discussion:
- The pki-devel mailing list.
- The
#dogtag-pkiIRC channel on Freenode.
Thanks!