On Wed, 31 Jan 2007, Ian Collins wrote:
Shawn Walker wrote:
I think the barriers to contribution are currently the biggest discouragement.
Integration of even the smallest changes can take a very long time.
That's put me off as well, it adds cost (from the developer's
perspective). It will all come down to quality. Most opensource
projects have a number of developers with commit rights and at some
point, community developers on OpenSolaris will have to be trusted. But
in order to be trusted, they have to be able to contribute, which kind
of looks like a nasty chicken and egg situation.
That's why I favour robust unit tests where passing the tests gates the
putback.
I'm with you all the way there, but then even internally at Sun it doesn't
work this way. We just _love_ review processes. Sometimes so much that
it's daunting and discouraging to go through them....
The code integration "process" isn't very streamlined. We have no "Google
Mondrian" to track development code from inception to integration and
automatically pull for / remind of review needs. Every group uses slightly
different ways of performing/requesting reviews or testing changes before
allowing commit, and none of them automated. Yes, it'd be absolutely great
to have something that neither incurs delays nor creates the feeling of
"not really wanted" with anyone. OpenSolaris _is_ already making this
better (from my point of view - inside the fence), but it's still quite a
way to go.
FrankH.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
