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 -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/CAB8EV3R5FCXaWMkhCYLGcEC8eeeJ079WL8-4ct1DXBS7kavtsw%40mail.gmail.com.
