I'm all for that, James. I've done everything in my power to make my changes easy to digest: No new key functionality, just making what's there working. No changed interfaces for total backwards compatibility.
I'm hard at work on some new documentation and javadocs, and I'm dying to get some feedback as to how it's working for existing users of JCS. What else, besides submitting my changes in the form of a CVS diff, can I do to expedite the process? -Travis Savo -----Original Message----- From: James Taylor [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 3:27 PM To: Turbine JCS Users List Subject: Re: JCS fixes/branch > The discussions in the last 24 hours indicate that there is interest > in reviving JCS Yeah, this is excellent! Seems like it would be logical to move JCS up a level to a jakarta subproject and get Travis hooked up with commit access. So, how can we make this happen while avoiding get bogged down in endless pointless discussion and polls and votes and such? -- jt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
