|
|
|
Cool,
Since I did not receive a reply for a long time. I went ahead and created a separate project on sourceforge (http://jcctray.sf.net) I don't mind merging jcctray with cruisecontrol, provided that I get credit for this contribution. Let me know. Everyone that contributes to the CruiseControl project is credited for their contribution in the RELEASENOTES that accompany the releases.
As far as merging with the Cruise project... You may want to maintain your own project if you expect the code to change frequently. A separate project gives you the flexibility to modify it as you see fit, without having to contribute patches through CC's JIRA for one of the committers to apply. This is the model that Allan Wick uses for cc-config. On the other hand, if you think that the code is pretty much stabilized and unlikely to change, it might be easier to include in Cruise's contrib directory. Your call. If you want to maintain the separate project, then I'll close this issue. Otherwise, you can provide a zip that would be appropriate for Cruise's contrib dir. Thanks for building this either way! I believe that the code is going to change for quite some time, until things stabilize, after which I do not expect much to change.
Your idea of adding jcctray in Cruise's /contrib directory is a good one, and I go with it. I can provide a zip for Cruise's contrib directory. That also means that there needs to be some sort of mechanism for me know that there's going to be a cruise release, so that I can plan my releases accordingly. | |||||||||||||||||||||||||||||||||||||||||||||||||||
Would you like to contribute it?