lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: [lucy-dev] 0.1.0 release prep
Date Sat, 21 May 2011 01:19:03 GMT
Hi Guys,

On May 20, 2011, at 4:13 PM, Joe Schaefer wrote:

> Sure, but it is counter to the goals of an Apache project to allow
> *anything* to block progress other than a technical veto.  It is
> "bad form" for anyone to take a lock on RMing the codebase, just
> as it is "bad policy" to instill code freezes on trunk.  Find another
> way.

Yep, I don't need to stand in the way, +1 to that. And I've never favored code freezes either.
It didn't affect me b/c I don't really have my hands in the Lucy code other than to help release
it when I'm needed, but in general I'm not in favor of it.

> I'm yelling at Chris today, but tomorrow I may be yelling at Marvin
> for being too much of a coordination hub for this project.  

+1 to that -- Marvin and I have had that discussion before and I think he is open to seeing
others step up. Right, Marvin? ^_^

> We need
> to start documenting the common goals that we all can agree on, but
> at the same time ensure that every committer has equal say in the
> control and direction of the project.


>   Kinda hard to do that right
> now as so much of this codebase was authored by Marvin, but over
> time if enough of us scribble on it we can all share the same goals.

Agreed! I'm best used to do release management since I do most of that on my other projects,
besides periodic patches and development. If I do it enough on Lucy, I'm definitely +1 for
having a say in the direction of how releases get pushed through and I hope everyone is open
to that.


Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

View raw message