*Contributions*, either *code* patches or *documentation*, are welcomed from the community.
-*First*, make sure you have a signed {link: http://www.cs.wisc.edu/condor/licenses/CLA-PUBLIC.pdf Contributor License Agreement (CLA)} on file with UW-Madison [NEED: Contact/Fax info]. When your CLA is received, a gittrac account will be created for you.
+*First*, make sure you have a signed {link: http://www.cs.wisc.edu/condor/licenses/CLA-PUBLIC.pdf Contributor License Agreement (CLA)} on file with UW-Madison by sending it to cppa[at]cs.wisc.edu. When your CLA is received, a gittrac account will be created for you.
-For *documentation* contributions, [NEED: Procedure, maybe...]
+For *documentation* contributions,
-1: Contact an {link: userlist administrator} to get a wiki account with edit privileges
+1: Contact an {link: userlist administrator} to get a wiki account with edit privileges. You can find them on the {link: https://lists.cs.wisc.edu/mailman/listinfo/condor-devel condor-devel mailing list} mailing list.
-For *code* contributions, [NEED: Procedure, maybe...]
+For *code* contributions,
1: Open a {link: tktnew ticket} for discussing your contribution (either enhancement or bug fix)
-1: Send an email to the {link: https://lists.cs.wisc.edu/mailman/listinfo/condor-devel condor-devel mailing list} announcing your ticket
-1: [Make sure you: work with committer, code compiles on all platforms, code guidelines, include test procedure, ...]
+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.
