Page History
- 2020-Apr-21 06:50 tim
- 2014-Sep-16 11:58 tannenba
- 2014-Aug-11 11:32 tannenba
- 2014-Jun-10 16:20 tannenba
- 2014-Jun-10 16:19 tannenba
- 2014-Jun-10 16:19 tannenba
- 2013-Oct-16 11:55 matyas
- 2013-May-21 15:36 tannenba
- 2012-Dec-15 12:21 matt
- 2012-Nov-13 16:20 adesmet
- 2012-Oct-23 13:12 tannenba
- 2012-Oct-11 12:14 adesmet
- 2011-Nov-30 11:27 jfrey
- 2010-Jun-09 07:31 tannenba
- 2010-Jun-05 10:33 tannenba
- 2010-Jun-04 14:42 matt
- 2009-Jul-15 10:19 jfrey
- 2009-Jan-29 18:34 matt
- 2009-Jan-29 18:33 matt
First, make sure you have a signed Contributor License Agreement (CLA) on file with UW-Madison. Print out a copy, review and sign it to indicate your agreement, then get it back to us. The easiest way to get it to us is to scan it into a PDF and email it to cppa[at]cs.wisc.edu with a Subject of "Contributor License Agreement". When your CLA is received, a gittrac account will be created for you, if you don't already have one.
For documentation contributions,
- Contact an administrator to get a wiki account with edit privileges. You can find them on the condor-devel mailing list mailing list.
For code contributions,
- Grab the source code
- Open a 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). - Send an email to the condor-devel mailing list announcing your ticket to find a committer to help you
- Make sure: you work with a committer, your code compiles on all platforms, your code meets guidelines, you include test a procedure
- 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.
- State which version of the Condor source your patch is relative to.
- When generating your patch, use one of the diff formats that provides context (i.e.
diff -cordiff -u). - When modifying existing source files, try to match the formatting style of the surrounding code.