Re: Adding to Logging KEYS file

2024-10-11 Thread Robert Middleton
The source code is the same for all platforms, so we only need to run it on one builder. I took a brief look earlier, but I'm busy this weekend so I can take a closer look next week. -Robert Middleton On Fri, Oct 11, 2024 at 2:10 PM Piotr P. Karwasz wrote: > > Hi Stephen, > > On Wed, 9 Oct 2024

Re: Feature proposal for a new Filter result: Throw

2024-10-11 Thread Gary Gregory
On Thu, Oct 10, 2024 at 4:09 AM Piotr P. Karwasz wrote: > Hi Gary, > > On Wed, 9 Oct 2024 at 16:34, Gary D. Gregory wrote: > > My proposal is to allow a user to _not_ define any custom filters by > reusing a new Result enum value called “Throw”. When a filter returns > “Throw”, then Log4j throws

Re: Successor to mailing lists

2024-10-11 Thread Gary Gregory
On Fri, Oct 11, 2024 at 2:08 PM Christian Grobmeier wrote: > > > On Fri, Oct 11, 2024, at 19:35, Gary Gregory wrote: > > I'm not crazy about having to bounce around sections of various repos in > > addition to monitoring emails, which has to be done anyway. It's > _another_ > > thing to lose trac

Re: Adding to Logging KEYS file

2024-10-11 Thread Piotr P. Karwasz
Hi Stephen, On Wed, 9 Oct 2024 at 08:36, Stephen Webb wrote: > > That would be much simpler. I was not aware that option was available. Is > there an example I can copy? I added a prototype as PR #414[1]: * I added a `package.sh` script that can be used to generate the source archives in a repr

Re: Successor to mailing lists

2024-10-11 Thread Christian Grobmeier
On Fri, Oct 11, 2024, at 19:35, Gary Gregory wrote: > I'm not crazy about having to bounce around sections of various repos in > addition to monitoring emails, which has to be done anyway. It's _another_ > thing to lose track of :-( Having a repo just to use the discussion feature > feels like a

Re: Successor to mailing lists

2024-10-11 Thread Gary Gregory
I'm not crazy about having to bounce around sections of various repos in addition to monitoring emails, which has to be done anyway. It's _another_ thing to lose track of :-( Having a repo just to use the discussion feature feels like a hack. I wish I could find the thread about new reddit-like FO

Re: Successor to mailing lists

2024-10-11 Thread Jan Friedrich
Hi Volkan, I would prefer option 1.3, because most of the users will look for discussions in the most relevant Github repo (for them). I'm not a fan of Discourse (another app to install and no integration with Github). Let's try and find out whether it works for us. We need to decide, whether

Re: Successor to mailing lists

2024-10-11 Thread Volkan Yazıcı
That is something we can decide together: 1. Have project-specific discussion repositories (i.e., Log4j users will use `logging-log4j2`, LogNet users will use `logging-log4net`, and so on) 2. Have a shared discussion repository (e.g., we can create `logging-discuss` repository and crea