Propose "Jini" to the ASF

Diving into some details...

 >Based on these and other factors, we're embarking on a four
 >step plan, outlined below. There are a lot of details and
 >questions to discuss around each of these, so in the interest
 >of some brevity, I'll provide a top level overview, and then
 >follow-up with separate emails on each to clarify and begin
 >discussion of the details.
 >
 >1) Propose "Jini" to the Apache Software Foundation (apache.org)
 >    - we feel that "Jini" would make a compelling top level
 >      project at Apache, and plan to make contacts there in
 >      hopes of successfully proposing "Jini" as a project.


* Some Background:
    {Note: I am just coming up to speed on the details of
    Apache and the processes, and am not trying to represent
    being an expert of any kind on this. Just trying to share
    some information as background to help us all get to a
    common starting place.}

    For those not familiar, the Apache Software Foundation (ASF)
    provides support for the Apache community of open-source
    software projects. Some examples of the projects include:
    Apache HTTP Server project, Tomcat, Ant, Maven, etc.  It
    has a well formed structure for management of the Foundation
    (Board of directors, etc) as well as project management
    governance and philosophy. A good read on some background,
    structure, roles, etc. is at:
      <http://apache.org/foundation/how-it-works.html>

    Apache has a defined process for accepting new projects, with
    the primary entry path being through their "incubator" project.
    See: <http://incubator.apache.org>. The incubation period for
    new projects gives them time to demonstrate that they have adopted
    the 'Apache way' :-) of open communication, establishment of
    roles and responsibilities (for example, project management
    committee, committers, etc), following the decision making process,
    clearing any legal hurdles, etc.

    Prior to submitting a project to Apache, a project must have
    a "Champion", an Apache Member or Officer who believes in the
    project and will support it for incubation.

    Another background piece of information that's important to
    know is about committers. Committers are individuals who have
    been given access rights to write the source. See:
    <http://www.apache.org/dev/new-committers-guide.html> for details.
    As part of a project proposal for incubation, a project must
    include an initial set of Committers, and then can add (or
    subtract) from it over time.


* To be clear on where we are in the process... we are early
   on, having only had informal discussions thus far with some
   members of Apache. The discussions have been positive, and
   we are very hopeful that we'll find a Champion and make a
   successful proposal to the ASF.


* Dan Creswell
     Before we'd seriously consider this approach (proposing
     Jini to Apache), I knew we needed to identify some strong
     technical leadership to come from outside the Sun engineering
     team. Yes, Sun engineers would be committers on the project,
     but Apache projects require a diversity of committers
     (not just commits from a single individual or company).

     I immediately looked to Dan Creswell, as his technical
     knowledge of Jini and leadership and support for the
     Community is well known (see:
     <http://www.jini.org/Contrib_Award/index.html> ).

     Dan enthusiastically jumped at the chance to help lead
     and participate in this effort, so look for him to be
     vocal and visible as we move forward here. (We couldn't
     be more pleased - thanks Dan :-)).

     Again, the project will need a diversity of committers,
     and we hope that many others will want to get involved.
     This is a Community with a wealth of software development
     talent, so we look for broader involvement to develop
     now and over time.


* Considerations
     If you have opinions or input on these, please share
     with the lists.

     - You may not have noticed, but when I wrote 'Propose
       "Jini" to the...', "Jini" was in quotes. The reason
       being -- what to exactly propose to Apache?

         o should it be "The Jini Technology Starter Kit"
           in it's exact form?

         o are there pieces of the starter kit that would
           be worth removing (potentially, some of the less
           used utility services)?

         o would it be valuable to add the Service UI API
           to the Proposal (we have talked to Bill Venners
           at artima about this - and he's supportive)

     - What happens to the Jini Community Decision Process (JDP)?
       Is it still needed? Are separate Standards fundamental?
       How should the specifications fit in?


* Some next steps...
    - Continue to understand more about the Apache structure

    - Decide on positions on the questions above (and other
      questions raised)

    - Continue to engage Apache members for advice and counsel

    - Write a draft Proposal of the project


thanks -Jim

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html