On May 31, 2011, at 6:29 AM, Marvin Humphrey wrote: > On Mon, May 30, 2011 at 09:41:10PM -0700, Mattmann, Chris A (388J) wrote: >> I'll wait for the "go ahead" for release announcements, but that shouldn't >> block me pushing out the bits to the mirrors, which I'll do. As the RM for >> the release though I'd like to send the announcement to [email protected], >> and [email protected], which is pretty std practice. > > -0 > > I trust your judgment, so please do what you think is best. > > Nevertheless, here's my rationale: other people who are already involved with > Apache are Lucy's most valuable potential recruits. Of all the possible > candidates out there, existing Apache community members will cost the least to > integrate and will be most likely to stick around. I think it should be our > top recruiting priority to present a good impression to the people in this > demographic and give them the maximum possible chance to click on a link, get > interested and get involved.
Hmm, we're debating the download link here, right? So, why not cruft the announcement to specify that the link will be available within X days? > While our Apache internal announcements may > serve administrative purposes, we have only so much contact with the rest of > the foundation and we should make the most of our limited opportunities. There's nothing limiting our contact with the rest of the foundation -- if we release every 72 hours which is theoretically possible (or 72+N hours), we could send a release announcement that frequently. Also, realize I'm looking at this from a checkbox perspective, which is what the RM should -- I'm looking to check the box and move onto the next task. You are welcome to look at it from a consumer perspective too. > > If my reasoning is faulty, it would be helpful to me to understand why, though > again, please do as you see fit. Here's what I'm proposing, concretely, not necessarily in order: 1. push Lucy tarball bits and KEYS/CHANGES to the mirrors today (since release VOTE has now passed on [email protected]). Joe I need your help with this, right, to do that magic initially for releases to sync to the mirrors from www/www.apache.org/incubator/dist/lucy? 2. send ANNOUNCE emails to [email protected] and lucy-{dev|user}@incubator.a.o with your wording, but maybe with something like the below added to it: Initially the download link won't be available while we are updating the Lucy website. But the release should still be available from http://www.apache.org/dyn/closer.cgi... I'm OK with waiting on 2 until the Lucy website is updated, but like I said, I don't think it's a blocker to sending the emails. The consumers are interested in the Lucy product, aka the software bits. If the website is out of sync, that shouldn't block pushing the VOTEd on, accepted bits to the mirrors. > > Sorry, I meant to get more done this weekend so that your work as RM could > conclude smoothly, but surprise family visits and and then collaborating with > Joe consumed my time. No worries -- Apache is about fun, not about schedules/deadlines! :-) Family time is more important, that's for sure! Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
