Yes, we have it...developer.ja-sig.org/source/ -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
On Tue, Oct 21, 2008 at 10:29 AM, David Whitehurst <[EMAIL PROTECTED]>wrote: > Do we have Crucible? > > > David > > On 10/21/08, Scott Battaglia <[EMAIL PROTECTED]> wrote: > > David, > > > > I would focus your efforts on creating guidelines that help with the > > following items: > > 1. Ensuring code quality > > 2. Ensuring transparency within the project > > 3. Ensuring that at the end of the development lifecycle we're adequately > > documented so that people can start using it. > > > > Examples of each: > > 1. We should have regular distributed code reviews of various portions of > > the project (using a tool such as Crucible). Also, in our wiki we should > > have some documentation on our existing philosophies including the usage > of > > the final keyword, template methods/extension points, etc. > > 2. All commits should have the JIRA issue attached (unless its something > > minor like updating a POM). This way anyone looking in JIRA can see what > > changes were made > > 3. All non-setter/getter methods should be appropriately documented > > > > Right now I wouldn't worry about the management of people. The CAS > project > > doesn't have resources dedicated to it explicitly and thus we're much > more > > fluid and must be responsive to local needs of the developer's > > organizations. We really need #1-3 for when less junior developers and > new > > people join the project to help out. > > > > Thanks > > -Scott > > > > -Scott Battaglia > > PGP Public Key Id: 0x383733AA > > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > > > > > > On Tue, Oct 21, 2008 at 9:40 AM, David Whitehurst < > [EMAIL PROTECTED]> > > wrote: > > > > > > Hi. We're putting together documentation for the development of CAS4. > > > And, as CAS is an open source project we get help from many sources. > > > This help comes from Universities, CAS Users, Companies, and many > > > individuals. And, while CAS may be built by the hands of a few, it's > > > intellectual property is the evolution of many thoughts and ideas from > > > all over the globe. > > > > > > We ask you to share your response to the following question: > > > > > > If you could have anything at all to help you create a better CAS what > > > would that be? Do you work best under a firm hand? Do you need to > > > understand the requirements better? Do you want to be given specific > > > tasks? Or, do you like to pick and choose what you volunteer for? > > > > > > We're preparing documentation in the CAS wiki and these words really > > > fall under group authorship. Help us help you. We may not copy your > > > words or text verbatim, but we are concerned that we create the > > > documentation that best assists you the developer. > > > > > > Thanks > > > > > > David > > > _______________________________________________ > > > cas-dev mailing list > > > cas-dev@tp.its.yale.edu > > > http://tp.its.yale.edu/mailman/listinfo/cas-dev > > > > > > > > > _______________________________________________ > > cas-dev mailing list > > cas-dev@tp.its.yale.edu > > http://tp.its.yale.edu/mailman/listinfo/cas-dev > > > > > _______________________________________________ > cas-dev mailing list > cas-dev@tp.its.yale.edu > http://tp.its.yale.edu/mailman/listinfo/cas-dev >
_______________________________________________ cas-dev mailing list cas-dev@tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas-dev
