Cameron McCormack: > Ivan and Jasleen, the two Google Summer of Code students working on > Batik, are starting to write some code now. I’m wondering what the best > way of integrating their work would be. Ideally (in my mind), they > would each have a branch to commit code to, as that would give them more > experience working directly with the project, rather than having their > own, separate checkout of the code that they work on. Is that possible? > If not, what’s the best way to keep abreast of their contributions?
After some discsusion, I think it’s best if we start off just by having you guys submit patches. You should create an entry in Bugzilla each for your work, and periodically attach a new patch to the bug. This is the way regular contributions to Apache projects are accepted (starting off with patches, then after proven good work, an invitation to become a committer would be extended). To include your code in the Batik codebase though, you’ll have to sign and submit an Individual Contributor License Agreement: http://www.apache.org/licenses/icla.pdf You may as well submit this now, so there isn’t any hassle later on when we come to incorporate your code. Thanks, Cameron -- Cameron McCormack, http://mcc.id.au/ xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
