I sent this message out to the Click people this weekend to encourage
them to discuss possible incubation at the ASF. I offered to be Champion
and I'd say that Velocity will be the sponsoring PMC. There is notion
that Click will go to top-level but it might as well end up as part of
Velocity.
This is basically a FYI, until the Click community decided where to go,
there is not much to do for us (I think) to encourage them and be
helpful if questions arise.
Best regards
Henning
-------- Forwarded Message --------
> From: Henning Schmiedehausen <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: Malcolm Edgar <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Incubation of the Click Project at the Apache Software
> Foundation
> Date: Sat, 24 Mar 2007 17:36:51 +0100
>
> Hi,
>
> this message goes out to the Apache Velocity PMC and the Click
> Development list. For those of you who do not know anything about me
> (probably most Click developers not directly involved with Velocity), I
> am the current chair of the project management committee (PMC) of the
> Apache Velocity project.
>
> End of last year, we discussed with Malcolm Edgar about opportunities to
> bring Click to the Apache Software Foundation in general and
> specifically to the Velocity project.
>
> I would like to review this now and if we agree that this is a good
> thing, prepare to start the incubation process.
>
> Personally, I'm very much in favor of doing this.
>
> What must be understood however, before we kick off the process to bring
> Click in, is that the ASF is interested in communities more than code.
>
> Which means, that the most important thing for us is to get acceptance
> and embrace from the people who currently *are* the Click community. The
> ASF is not a big vacuum cleaner that sucks in code and slaps an ASF logo
> and the feather brand on top of it.
>
> What we (the "Apache people") request from "you" (the "Click people")
> now, is that you form consensus. I reviewed your mailing lists and there
> was mixed discussion about this move and I found no consensus. So this
> would be needed first before any of the incubation process could start.
>
> I did read some points about bureaucracy. The following list is a
> personal compilation and should not be seen as canonical:
>
> * Yes, the ASF has some of that. We are not just an open source
> project. There is some legalese involved and we do offer a
> legal protection umbrella for our projects. This also means, that
> there are some rules for dependencies and releases that we are
> quite adamant about.
>
> * No, the foundation does not play into your project. If you run
> your project fast and loose, we let you do so most of the time.
>
> * No, as a developer / committer, the bureaucracy does not touch
> you most of the times. It is the job of the people serving on the
> entities of the foundation (like the PMC) to provide oversight and
> guidance to any project. Joining a PMC is a voluntary act and while
> most developers choose to do so at some point, there are some that
> say no.
>
> * Yes, as a developer, there are harder rules to e.g. dependencies
> inside the ASF than outside. You do have to play by the rules, there
> are no exceptions. The rules sometimes change, though. As a part
> of the foundation you *can* influence these changes.
>
> * Yes, as a developer / committer, you *must* sign a formal CLA before
> you can work on a project. Even if you already have commit rights to
> the project. This is a formal requirement and part of the incubation
> process and also an one-step thing (you fill out a form, fax it in).
>
> * Yes and no, incubation can be a drag. It is a formal process and it
> works as well as the people involved. If a project drags incubation,
> this is not the fault of the foundation. We had projects whiz through
> it in a few (1-3) months, we have projects in there for years.
> If Click joins the ASF, I intend to do the former, not the latter.
> Please understand, that every incubation is different. Experiences
> from another project are no indication for the next project. YMMV.
>
> For those of you interested in the incubation process, there is a
> summary on
> http://incubator.apache.org/incubation/Incubation_Policy.html
>
> There is a lot of boring stuff in there, but then again, this is more a
> formal process than anything else and this process is normally done by
> the mentors and a few selected members of the project development
> community. It does not touch or influence any users and developers that
> do not want to be involved in incubation.
>
> Interesting might be the flow chart of the incubation steps.
> Click ATM would be "pre-candidate" state.
>
> As current PMC chair of Velocity, I'd volunteer as your "Incubation
> champion" and the Velocity project would be the sponsoring project for
> Click. Whether at the end of incubation it will join Velocity or become
> a top-level project in its own right is yet to be determined.
>
> Once you have formed consent (we do not require you to hold any formal
> vote here, though it probably helps :-) ), I'd like to point you at the
> proposal guide at http://incubator.apache.org/guides/proposal.html and
> the recent proposals located at http://wiki.apache.org/incubator/ . If
> you feel ready to go, we (me as the Champion and probably one or two
> members of the Velocity PMC that will act as mentors) want to help you
> formulating your proposal and move Click to candidate and then podling
> status.
>
> So please: Start discussing. Especially if you are a developer of the
> Click framework. Voice your opinion, discuss, form consensus. I
> subscribed to the dev list and I will sit on the sidelines listening to
> you. If you have any direct questions about this process, feel free to
> send mail to me or the Velocity PMC ([EMAIL PROTECTED]).
>
> Best regards
> Henning
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
|gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
