Hi Dominik, I can allocate some time to help setting up the builds for Log4Net. Let me know what tasks I can start with. I would suggest https://dev.azure.com as a replacement for NAnt. The azure pipeline is free for GitHub projects and have support to the latest frameworks.
Regards, Kabilan On Sun, Sep 22, 2019 at 7:54 AM Dominik Psenner <dpsen...@gmail.com> wrote: > Streamlining the architectures across the different log4* implementations > has been discussed earlier. It would make sense to split log4net into > several libraries (api, configuration, several appender.xxx, etc). Further > make these assemblies all available over nuget. I could imagine this to > become part of a not yet existing 3.0 milestone if the community is willing > to contribute. I see also more important things to flesh out (getting a > release out of the door, reimplement the rolling file appender, replace > nant to improve builds and their automation, automate deployments to nuget, > ..). > > On Tue, 17 Sep 2019 at 17:31, Matt Sicker <boa...@gmail.com> wrote: > > > SLF4J is an earlier alternative to log4j-api, but it's not a > > replacement. If the other log4* projects adopt similar architectures > > to log4j2, they can all have API/implementation separation and > > potentially compatible config files, though that's not really planned > > by anyone that I know of. > > > > On Mon, 16 Sep 2019 at 23:15, Brown, Michael A <m...@purdue.edu> wrote: > > > > > > Any action on slf* as log4* replacement? > > > > > > I don’t have any issues with log4* or know a great deal about slf* but > > some of what I read indicates some developers moving in that direction. > > > > > > Any comments? > > > > > > Mike > > > > > > Get Outlook for iOS<https://aka.ms/o0ukef> > > > ________________________________ > > > From: Dominik Psenner <dpsen...@gmail.com> > > > Sent: Monday, September 16, 2019 5:10:50 PM > > > To: dev@logging.apache.org <dev@logging.apache.org> > > > Subject: Re: Is Log4Net project abandoned? > > > > > > I had this message in draft for quite some time now and just now I > > decided > > > to send it in a slightly modified version. > > > > > > While log4net has been around for a while it may have come the point in > > > time when it has reached end of life. A good indicator to me is the > > number > > > of active contributors. This means that the decision is obviously > > community > > > driven. So long people step up and get involved the project is healthy. > > Me > > > being the only one to do releases, review and apply PR, etc does not > > scale. > > > Any contribution is welcome! > > > > > > Best regards > > > -- > > > Dominik Psenner > > > > > > On Sat, Jun 29, 2019, 20:00 Kabilan VK <kabilan...@gmail.com> wrote: > > > > > > > The last commit was on 2017 so, its becoming a less favor to new > > startup > > > > projects. I tried to contribute by adding latest .net framework > > support so, > > > > at least need a PR review support to get this on track. > > > > Thanks for understanding. > > > > > > > > Regards, > > > > Kabilan > > > > > > > > On Sat, 29 Jun, 2019, 4:31 AM Jochen Wiedmann, < > > jochen.wiedm...@gmail.com> > > > > wrote: > > > > > > > > > On Sat, Jun 29, 2019 at 1:21 PM Dominik Psenner < > dpsen...@gmail.com> > > > > > wrote: > > > > > > We could also push log4net back to incubation. What do you think? > > > > > > > > > > If availability of people is an issue, then this would be an > > excellent > > > > > way of exhausting those even more. > > > > > > > > > > Jochen > > > > > > > > > > > > > > > > > > > > > -- > > Matt Sicker <boa...@gmail.com> > > > > > -- > Dominik Psenner > -- ================= Thanks and Regards Kabilan.vk
