Publishing code reviews

Tim O'Brien tobrien at
Thu Oct 11 18:04:38 UTC 2007

If you have a process that's working well internally, don't change it.
Clone what works internally and move it out into the open.   I'm sure that
once people see it, you'll end up with a bunch of contributors from outside
of Sun coming up with various unsolicited improvements.  (I'd be surprised
if you don't end up with something similar to Mondrian in short order).

Maybe just create another mailing list and adopt the sort of standard you
see in projects like Jakarta Commons or Codehaus Mojo where email subjects
are prefixed with a string like [REVIEW-2324].   If it the email list is
public, people will have the choice to view it in something like Nabble or
subscribe directly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the discuss mailing list