For *code* contributions,
1: {wiki: DownloadingSource Grab the source code}
-1: Open a {link: tktnew ticket} for discussing your contribution (either enhancement or bug fix). If your contribution is a relatively small patch, you could simply attach a patch file directly to the ticket page (at the top of the ticket page, select =Attach=).
+1: Open a {link: tktnew ticket} for discussing your contribution (either enhancement or bug fix). If your contribution is a small/trivial patch or bugfix, you could simply attach a patch file directly to the ticket page (at the top of the ticket page, select =Attach=). If your change is an enhancement (new feature) or large bug fix, you will need to author and attach a {wiki: DesignDoc design document} to the ticket page for architecture review and get it approved before code contributions will be accepted. It is appreciated if you openly discuss design with committers via the condor-devel mailing list.
1: Send an email to the {link: https://lists.cs.wisc.edu/mailman/listinfo/condor-devel condor-devel mailing list} announcing your ticket to find a committer to help you
1: Make sure: you work with a committer, your code compiles on all platforms, your code meets guidelines, you include test a procedure
1: Assign your ticket to the committer and change its status to review
-*Note:* If your change is an enhancement (new feature) or large bug fix, it is appreciated if you openly discuss design with committers via the condor-devel mailing list.
-
Your code contributions will be much more happily received if you observe the following guidelines:
*: Submit your contribution as a patch to most recent version of the Condor source code.
