See here:
https://github.com/cobbler/cobbler/wiki/Patch-process
(It could probably use some updating to include a little better
guidance for people newer to github, contributions welcome.)
Basics -- everyone should get a
github.com account, fork the project,
and create a new branch for each feature, and use pull requests to ask
that their code get merged back in.
An upside to this is that it makes it possible to watch features
better as everyone works on them. Also, having a lot of forks of
cobbler on github is hopefully good for spreading interest, since
github is quasi-social.
It also allows folks to collaborate together on a large feature before
merging it into master -- we might even have officially hosted
integration branches should we take on some really big things, who
knows.
Emailing this list with the pull request + an explanation is still
encouraged and is something everyone should do, that way others can
see what's going on and talk about it. Though we may ask a few
questions on the pull request
itself in github before something gets committed as well. Explaining
how something has been tested in the pull request is a very good idea
too.
Also "following" the cobbler project on github probably can't hurt either.
--Michael