CruiseControl and Sourceforge Features
Although SourceForge(SF) currently hosts the CruiseControl open-source project, some of the features provided by SF are not going to be used.
Bugs should not be entered into the Bug Tracking System provided by SF, but rather should be emailed to either the User or Developer mailing list.
Feature Requests should not be entered into the Feature Tracking System provided by SF, but rather should be emailed to either the User or Developer mailing list. See the decision making document for more information on Feature Requests.
Patches to the CruiseControl source written by Developers should not be entered into the Patch Manager System provided by SF, but rather should be emailed to either to the Developer mailing list.
Basically ALL project communication should occur on the mailing lists.
Why not use the features provided by SourceForge?
- Working Offline:
- Many of the CruiseControl contributors require the ability to work offline, i.e. behind strange firewalls or on the plane. Email is easy to replicate locally, but websites are not. Having all project communication occur in one place makes it simpler to work offline.
- Tight Coupling to SourceForge:
- CruiseControl may move to a different host. Remaining host agnostic makes the transition simpler. The tasks presented are easily accomplished without the use of these features, so there is no need to tightly couple the project process to the host.
- Push versus Pull:
- Using features on a website requires Committers and Administrators to monitor the website, as well as their email. Monitoring email already occurs, whereas monitoring a website represents an added burden.