+1. I say go ahead with the plans you post. If others see problems, then they should speak up. I've found there is often deafening silence, and only when there's an objection are you likely to get a lot of responses. Seems the old "do it now, ask for forgiveness later" applies, with the process being you post what you plan to do, allow a (reasonalbly short) time for repsonses, and then go, go, go.
Maybe a very quick approach is to do a ReleaseCandidate within the next couple days/weeks, purely to get the process going. With an RC floating about, people can then dive into discussions on content, process, etc. (Release early and often...) This way, no matter what the problems with the RC, it's still just an RC, so nothing it contains binds us in the future. Dan -----Original Message----- From: Sam Chance [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 7:50 PM To: [email protected] Subject: Re: shifting up a gear... Jim, A hearty "Amen!" from the evangelicals in the crowd. My "campaign" would benefit from your recommendations. Sam On 8/22/07, Jim Hurley <[EMAIL PROTECTED]> wrote: > > We've had a few discussions on potential project plans, > including: > <http://mail-archives.apache.org/mod_mbox/incubator-river-dev/ > 200705.mbox/[EMAIL PROTECTED]> > I'd like to get us back to it and get agreement on a short term plan > to get us accomplishing things and gaining momentum as a project. > Let's shift it up a gear (or two ;-)). > > As I've said in the past, I think working to get out a first release > from the project soon would help the Community (by having a release > available from the project), as well as help us understand what it > takes to get out a release. It would be great if we could shoot for a > late September timeframe for a release. I also think we need to get > our project (web) pages updated with some content (so the place looks > like the lights are on). > > Once we have a good handle on this first release, I think we should > then focus on another short term release (say, November/December > timeframe), and start discussing what that release should look like > (for example, which issues to commit to it). > > Following that we have a more difficult and significant discussion to > have on the future focus and efforts of the River project (more > 'infrastructure work? work on services? other?). If you'll bear with > me, though... > I'd like > to wait on diving into that until we get some success and things going > in the River project. > > I'll follow up immediately with another email detailing some things > around a first release. > > I'm not trying to force this plan through -- so if someone else would > lead us through discussing an alternative plan -- please do. > > thanks -Jim > > > > > -------------------------------------------------- This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. --------------------------------------------------
