Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Achim Nierbeck
Hi, I'm sorry to be a PITA :) What I've read so far has been feelings, one concern of perception by "big" customers. I would really like to know, which problem we are trying to solve by moving the pax projects under the umbrella of Karaf. Or what I personally would favor under their own tlp of

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Eric Lilja
Personally, I would love to see this change and the other people in my organization liked the proposal as well. - Eric L On Thu, Feb 24, 2022 at 3:04 PM Jean-Baptiste Onofré wrote: > Hi guys, > > Some of you already pinged me to share concerns about PAX projects > governance. I think it's my

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Robert Varga
On 24/02/2022 16:48, Jean-Baptiste Onofré wrote: Hi Achim Just wanted to share concerns I received. Basically, PAX projects are "free fields", without strong guarantee in the release (not formal staging/vote/review). It doesn't mean we don't do that, it's just not strongly enforced;) Hello,

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Łukasz Dywicki
Hi Jean, hello ops4j participants. Given recent rush hours with log4j issues I can understand some of the concerns. However, looking at practical aspects, these issues were handled as good as they would be at the ASF. Time it took Grzegorz to release updated pax-logging was pretty short. If

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Jean-Baptiste Onofré
Hi Achim Just wanted to share concerns I received. Basically, PAX projects are "free fields", without strong guarantee in the release (not formal staging/vote/review). It doesn't mean we don't do that, it's just not strongly enforced ;) I don't mean we *have to* do it, I'm just sharing comments

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Achim Nierbeck
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

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Łukasz Dywicki
I am not sure if concerns about PAX projects are fully justified, simply because they are being released and still worked on. While team of people working on it have shrunk over time, I haven't had any troubles with them for long time. The contribution regulation is not an issue. It does work

[DISCUSSION] Move PAX projects to Apache Karaf ?

2022-02-24 Thread Jean-Baptiste Onofré
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

[ANN] Pax Logging 2.1.1, 2.0.16, 1.12.1 and 1.11.15 released (4 versions)

2022-02-24 Thread Grzegorz Grzybek
Hello I'd like to announce the release of 4 Pax Logging versions with two version updates: - SLF4J 1.7.36 (not much affecting Pax Logging - just a version update) - Reload4J 1.2.19 (aligning to latest upstream version) in 1.11.15 and 2.0.16 (the 1.12.x and 2.1.x branches do not contain