DRAFT Community Awards Rules

[Andrew John Hughes]

On 15/01/2008, Rich Sands <Richard.Sands at sun.com> wrote:
> Here's a draft set of rules for the contest we've been discussing.
> Please read and comment. Deadline for doing anything with comments is
> probably this coming Sunday, Jan 20. We can't promise we'll incorporate
> all suggestions but we really appreciate and value your ideas.
>
> Thanks,
>
>       --  rms
>

Thanks for all the hard work that's gone into this and for offering
such an opportunity in the first place.  Most of it seems fine, with a
lot being boilerplate legalese that is required for this sort of
thing.   I've highlighted specific sections and made comments below.

snip...

> Sun Campus Ambassadors are eligible to participate.

For my own sake, I hope this line is approved ;)

snip...
>
>             (i) Develops and implements new APIs, language features,
>             tools, or implementation methodologies that extend the
>             applicability or use of the Java SE platform into new
>             markets, simplifies the development process and use of the
>             platform, improves performance, scalability, security, or
>             other implementation characteristics, or improves the
>             end-user experience. These ideas need not be formally
>             proposed as JSRs.
>

Does this also include existing JSRs?  If so, will some guidance be
made available as to current JSRs applicable to the current OpenJDK
code base?  The biggest issue I see with implementing a current JSR
however is access to the specification, which required accepting a
license last time I tried.  Proposed JSRs would be much more exciting
and hopefully a great way of getting new blood into the JDK! :)

>             (ii) Implements a compatible, free software alternative to
>             a remaining bit of encumbered code or improves the quality
>             or performance of the free software alternatives that have
>             already been incorporated as part of the OpenJDK code base
>             to clear encumbrances.
>

Similar issue to the last; this would need some guidance as to what
are the remaining encumbrances and the progress on them within Sun.

snip...

>          e. It must specifically call out any dependence on Sun
>             involvement/participation for success. For fairness,
>             Entries may have only limited dependence on Sun
>             involvement/participation and may not require a commitment
>             by Sun for significant time/effort for success. Dependence
>             on Sun includes required effort on the part of Sun
>             engineering in order to deliver code, information, or
>             assistance to an Entrant in order to successfully complete
>             a Proposal.
>

For this to work in practice, it would help if the current state of
the OpenJDK was made as clear as possible (e.g. encumbrances, current
development work inside Sun, etc.)

snip...

>          b. Proposals that are lewd, obscene, sexually explicit,
>             pornographic, disparaging, defamatory, libelous, obscene,
>             or otherwise contain any inappropriate content or
>             objectionable material may be disqualified at any time in
>             the sole and unfettered discretion of the judges and/or the
>             Sponsor.
>

I dread to think what a pornographic OpenJDK project proposal would look like...

snip...

>          e. All work on Proposals, including without limitation
>             communications among team members, and any source code or
>             information repositories associated with the Proposal must
>             be accessible to all developers visiting the OpenJDK
>             Project website, and must be done in the open.
>

Couldn't agree more with this, especially with regards open
development processes.  Is it worth putting anything in about the
license to be adopted for the code?  You could simplistic assume it
will be GPL+Classpath exception like the majority of the OpenJDK code
base, but the above doesn't make this explicit.  The source code could
be accessible to developers of the OpenJDK community but under a
restrictive license, as I read this.

snip...

> 6. THE PROJECT STAGE:
>     The Project Stage of the Contest will begin on March 18, 2008 at
>     12:00AM PST, and end on August 4, 2008 at 11:59PM PST (the
>     "Project Stage). During the Project Stage the selected Finalists
>     will be asked to and construct their Proposal (the
>     "Project") according to the specification of completeness
>     that is a part of the accepted Proposal. Completed Projects must be
>     submitted no later than August 4, 2008 at 11:59 PM PST by submitting
>     an email to the [EMAIL] alias of the OpenJDK Community with the words
>     "FINAL PROJECT" in the subject line. This email must
>     provide specific instructions for how to access code or other project
>     materials from source code repositories or websites, constituting the
>     entire Project implementation of a particular Finalist Proposal.  Each
>     Project must use only open source and free software tools and
>     libraries with the exception of any non-free, encumbered binaries that
>     are a part of the OpenJDK code base. Each Project must also comply
>     with the requirements set forth herein applicable to the Proposal.
>     Projects must be completed and fully operational, as determined within
>     the sole discretion of the judges..
>

This seems very 'hands off', but then the prize is only awarded at the
end :) Google's Summer of Code is much more heavy handed but then they
award money throughout the process.  Is there any possibility of
projects having a mentor, an explicit contact point within the OpenJDK
community?  This might reduce the chance of projects just getting
lost.  The same comments with respect to licensing apply here I guess.

snip...

Thanks,
-- 
Andrew :-)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net