What license shall we pick for this JSR?

[Mark Struberg]

I'd be pretty happy if we could use Apache License v2.0 (ALv2 [1]) as done with quite a few new specs those days:

* CDI

* BeanValidation

* JBatch

It's really open and we don't have to fight battles with neither Oracle, nor OSS projects nor commercial projects.

Any opinions?

LieGrue,

strub

[1] http://www.apache.org/licenses/LICENSE-2.0

[Antonio Goncalves]

And what about the TCK ? The TCK also is under Apache License ?

--
You received this message because you are subscribed to the Google Groups "java-config" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-config...@googlegroups.com.
Visit this group at http://groups.google.com/group/java-config.
To view this discussion on the web visit https://groups.google.com/d/msgid/java-config/0a560fc8-76fa-4758-83e1-339fd6207dc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Antonio Goncalves
Software architect, Java Champion and Pluralsight author

Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France

[Oliver B. Fischer]

+1 to use ALv2 for the spec as well as the TCK and RI.

Oliver

Am 02.06.14 10:29, schrieb Antonio Goncalves:

To view this discussion on the web visit https://groups.google.com/d/msgid/java-config/CA%2BZZq9_YfMh_mbUnNV%2Bujqh8ndJBSLVBGM6vdaeT3GRtsg0avQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

-- 
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538 
E o.b.f...@swe-blog.net 
S oliver.b.fischer
J oliver.b...@jabber.org

[Antonio Goncalves]

Hum... looks like Oracle wants to move to UPL : http://h30499.www3.hp.com/t5/HP-Software-Solutions-Blog/Use-Oracle-s-UPL-Abandon-Your-Intellectual-Property/ba-p/6485626#.U4zMDZR_tZe

To view this discussion on the web visit https://groups.google.com/d/msgid/java-config/538C6118.3020405%40swe-blog.net.

For more options, visit https://groups.google.com/d/optout.

[Kevin Sutter]

According to the referenced article, it doesn't look like everybody is in favor of this UPL license.  I'd prefer that we stick with Mark's original suggestion of using Apache v2 License.

Kevin

[Antoine Sabot-Durand]

Regarding CDI and Bean validation we have a dual licensing : ASL v2.0 on Red Hat side and CCDL on Oracle side. I'm not expert enough in IP to understand how that can be sorted out in case of conflict, but perhaps that couldbe solution for Java config too ?

[Mark Struberg]

Hi Antoine!

Please re-check.

Afaik the Spec wording [1] is dual licensed as ALv2 + Java Community Process License [2] (the click-through stuff for the Oracle page). Btw this got changed without noticing or asking the contributing people. So it might not be fully kosher as well. It might be covered by the JSPA though, Idc.

But the Spec API [3] and  Weld itself is licensed as ALv2 only. At least according to all java files I looked at [4]

There is no CDDL mentioned anywhere.

LieGrue,

strub

[1] https://github.com/cdi-spec/cdi/tree/master/spec

[2] https://jcp.org/ja/resources/license_reference

[3] https://github.com/cdi-spec/cdi/tree/master/api 
[4] https://github.com/weld/core/tree/master/impl