On Tue, Oct 25, 2005 at 12:24:37PM -0500, David Robinson wrote:
> So the new third category are people willing to do all the
> grunt work of builds and tests that consumes all the time.
> This is the same thing we expect out of any Solaris
> developer so potentially the pool is anyone who has
> suc
In response to multiple requests to provide viewable data on
opensolaris.org about sponsor requests and submitted bugs,
http://opensolaris.org/os/bug_reports has been transformed.
The PDF files are gone (let us know if you really want the archived ones
back for some reason - we're anticipating tha
David Robinson wrote:
> Being a sponsor is not just about typing putback,
> but it is actually moderately heavyweight in that
> the sponsor is expected to build, test (maybe DIY test?),
> and validate the changes. Frankly, in many cases that
> may take more time than the actual code change.
>
> T
Bonnie Corwin wrote:
> In response to multiple requests to provide viewable data on
> opensolaris.org about sponsor requests and submitted bugs,
> http://opensolaris.org/os/bug_reports has been transformed.
>
> The PDF files are gone (let us know if you really want the archived ones
> back for som
If I can summarize to make sure I understand this.
Being a sponsor is not just about typing putback,
but it is actually moderately heavyweight in that
the sponsor is expected to build, test (maybe DIY test?),
and validate the changes. Frankly, in many cases that
may take more time than the actual
Apologies for not being clear last week - let's try again.
Until we can allow external contributors to integrate directly to the
O/N gate, Sun developers (sponsors) are pairing with external developers
to follow the O/N code integration processes.
The original concept of sponsoring included two t
