Hi JB, Before I come to any conclusion, I would really like to understand what kind of issue/problem you would like to solve with this, which is easier to solve under an apache umbrella.
thanks, Achim Am Do., 24. Feb. 2022 um 15:04 Uhr schrieb Jean-Baptiste Onofré < j...@nanthrax.net>: > Hi guys, > > Some of you already pinged me to share concerns about PAX projects > governance. I think it's my duty to share these concerns and discuss > possible actions. > > Apache Karaf is one of the biggest consumers of PAX projects. > > However, PAX projects use a "self own" designed governance: > - for contribution/IP > - for release > - for CVE/Security > - ... > > And it could be seen as a major concern for Apache Karaf users, as PAX > projects are not necessarily "aligned" with Apache Foundation rules. > > I would like to start a discussion on both Karaf and OPS4J communities > to "move" PAX projects as Karaf subproject (like karaf-pax). > Concretely, it would mean that: > 1. Karaf PAX projects would use org.apache.karaf.pax namespace > 2. Karaf PAX releases will have to follow the Apache release process > (binding votes, 3 days vote period, ...) > 3. Any active contributor on PAX projects would be invited as Karaf > committer > > Thoughts ? > > Regards > JB > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
