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
For documentation contributions,
- Send a request to the condor-devel mailing list mailing list, and an administrator will help you
For code contributions,
- Grab the source code! Also helpful to refer to BuildingHtcondorOnUnix and/or BuildingHtcondorOnWindows
- Open a ticket for discussing your contribution (either enhancement or bug fix); you can read about our ticket process here or by clicking [Help] at the top of the new ticket page. 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 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 htcondor-devel mailing list. - Send an email to the htcondor-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
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 HTCondor source code.
- State which version of the HTCondor 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.