Re: Moving towards a proposed vote

Angela Cymbalak wrote:
> Roland - What about being a Mentor?

I'll consider it. It's the first time I'm engaging in
a podling, so I would prefer not to start as a mentor.
On the other hand, I'm used to get training on the job.


Regarding the proposal, I have made some updates.
But I'm still not happy with the sections on
"Initial Goals"/"High Level Design" and "Relationships
with Other Apache Products". This has to do with all
the open design questions in the proposal. It is important
to document such questions and the decisions, but that
does not belong into the proposal. The proposal should
give the Incubator folks the information needed to
decide whether the project should become a podling.
It should not bury them with irrelevant technical
detail. My suggestion is as follows:

1. Drop all the questions. Instead, describe the
    preliminary high-level design that seems to be
    the current consensus:

    * JCR/Jackrabbit backend
    * Web service interface
    * Sling frontend (not using the WS interface)

2. Define a roadmap for the "Inital Goals" section:

    * define a repository layout
    * create a prototype based on the Tuscany SCA sample
      by replacing the filesystem backend with the
      newly defined JCR backend
    * Sling frontend to follow later

3. Update the "Relationships" section:

    * Jackrabbit for the backend
    * Tuscany SCA for the WS interface
    * Sanselan for metadata extraction
    * Sling for the frontend
    * maybe JSecurity for authorization

    Apache Tomcat, Apache Directory Server or Apache Derby
    (if we need a relational DB) are just implementations
    of standard APIs. We can mention them, but should
    indicate that they are replaceable middleware components.
    Though to me, that would create the impression that we
    are trying to artificially inflate our relationships.

The reason why I'm not jumping ahead with this is
that I am not sure yet whether my understanding of
the high level design is the current consensus.


> Committers -
>    Angela
>    Noel
>    Luciano
>    Carston (???-because of his Sling code that we aren't waiting for but 
> might be useful)
>    Martin (???-flex front end [1])

Initial committers should list themselves. It's not good
to put people on the list that later don't invest time.
Carsten probably intends to contribute his code to Sling
(that's what I assumed when editing the proposal). We
could take it from there. Or, if he contributes it to
the new project, he can be voted in as a committer when
the time comes.

cheers,
   Roland