It has been decided that the code should go through an automatic reformatting to ensure that everything matches the project's coding standards.
Prior to this, we need to review the coding standards and confirm that they are what we want to use.
The current coding standards for the project are referenced here: http://pki.fedoraproject.org/wiki/PKI_C_Coding_Style http://pki.fedoraproject.org/wiki/PKI_Java_Coding_Style
Some alternative styles: http://freeipa.org/page/Coding_Style (C) http://www.oracle.com/technetwork/java/codeconvtoc-136057.html (java, sun conventions)
We should focus on the java coding style first, followed by C. The perl code is mostly going away most likely, so no need to focus on that.
IPA has a style guide for python, which, unless we have another compelling reason, we should probably use:
http://freeipa.org/page/Python_Coding_Style
Metadata Update from @vakwetu: - Issue assigned to vakwetu - Issue set to the milestone: m1
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/616
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.