[awards-program] [Fwd: Re: [Fwd: Re: Preamble draft and my brainstorm rules]]

[Jesse Silver]

-------- Original Message --------
Subject: 	Re: [Fwd: Re: [awards-program] Preamble draft and my 
brainstorm rules]
Date: 	Fri, 21 Dec 2007 11:20:51 +1300
From: 	Glynn Foster <Glynn.Foster at Sun.COM>
To: 	Jesse Silver <Jesse.Silver at Sun.COM>
CC: 	Team Indiana <teamindiana at sun.com>
References: 	<476ADEBF.4010104 at sun.com>



Hey,

So as per our phone call earlier, here's my comments - most of them are
specifically due to this first paragraph comes across.

> 1.BRIEF DESCRIPTION OF THE CONTEST:
> 
> The [OpenSolaris Community Innovation Awards Contest] is designed to ...
> 
>   " ...recognize and award outstanding Technical Submissions which
>   demonstrate new, enabling, innovative and/or high-performance
>   uses of Open Solaris.  Participants in this Contest will
>   begin by declaring a problem statement and proposing a solution.
>   Proposals must  be framed within the context of a business proposition.
>   and can be either for profit or altruistic motives.  Participants,
>   must then submit a technical implementation of their solution whose
>   software component(s) must execute on the OpenSolaris(TM) Operating
>   Environment...."

I think this is both too formal, too focused on technology (or cutting code),
and too 'business' focused. We need to encourage the community feel, that we're
all part of a global mesh of cultures, all excited in working on OpenSolaris as
a set of technologies, and see that success grow. I can see why you'd want to
mention that business proposals are acceptable, but really this is a community
program, and we should encouraging all shapes and sizes, all colours, and all
languages.

I think the idea of submitting a problem statement is a great way to express an
interest in the program (and I think everyone should do that right at the
start), and then follow it up with a solution - whether that's a set of code, a
bunch of documents, or whatever.

In terms of actual code, we probably need to figure out whether success is
judged on actually integrating that code, or just providing it as part of the
'solution'. The rules may want to address that in some way. Is request-sponsor a
requisite for example?


Glynn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/awards-program/attachments/20071220/7879851c/attachment.html