incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <>
Subject Re: [PROPOSAL] Incubate Wicket
Date Sun, 30 Jul 2006 18:54:35 GMT
On Monday 31 July 2006 00:58, Justin Erenkrantz wrote:

> Legally, you may not call it Apache Wicket

It is known as Wicket and will remain to be known as Wicket.

> (if that's the name you decide on), and as a matter of policy, 
> I'd frown upon such 'backporting' behavior.

Not sure what part you are frowning upon. Considering the strong legacy of 
compatibility in Apache Web Server, still supporting 1.3, I strongly doubt 
that you frown upon leaving existing users in the dry.

Possible scenario; PersonA contributes some patch to Wicket 2.0. A wicket team 
member takes that patch and also applies it to Wicket 1.2.2 at with 
the proper attributions. Now, are you saying that this is unacceptable 
behavior?? It is definitely not against the license. Is it against 
the 'spirit of incubation', or some other guideline, rule or principle?

> The problem that Roller did was that they took code that was in our
> SVN repository, removed the license blocks and relicensed it to LGPL
> (I think) and posted it to  In two words, "Uh, no."

Yep. Wicket OTOH is already under ALv2, so that particular aspect is not a 

> - Keep their existing 'branch' wherever it is (i.e. - do not
> ever backport anything that is in the Apache SVN repository.  Treat
> them as a chinese wall - nothing should mix except for the initial
> code grant.  Code can only go into both repositories IF the
> contributor explicitly says that it can do so or commits them into
> both trees themselves.  

Sounds a bit harsher than it really is, no?

Nevertheless, AFAIU the 2.0 already exist as a separate branch, and is so 
different that automated backporting is not possible.
So, the team is already working off two branches, and if one of those moves to 
Apache, it shouldn't change much of the work flow.

I think the Wicket team have no problem complying with this. (but see 
the 'scenario' above)

> At no time, does a 1.2.x release *ever* get 
> cut from our repositories.

Of course.

> - No releases can be cut from the Incubator until the CLAs and
> software grants are on file.  (All other disclosure requirements must
> be met too.)

Of course.

> - All new development comes to the Incubator.  We expect no more
> 'major' releases to be made outside of the ASF.  

The change to 2.0 is happening because of a lot of experience in the 1.x life 
span, that they want to apply. It is a convenient point in time to enter 
Apache Incubator, as it otherwise would also constitute another incompatible 

> - Development lists for the next release move to the Incubator lists
> here, while development discussions around previous versions need to
> stay where they are now.  (i.e. no discussions around cutting 1.2.x
> releases on our lists.)

Hear ya!

> - User-focused lists can move to the Incubator lists now - they can
> get support or whatever for older versions; but again, no development
> discussions on older releases happen here.

Perhaps the user list stays where it is, and the user list for 2.0 is 
established closer to the release of 2.0. Makes more sense to me.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message