As PMC member I voted to make the source code available in a git repository. The git repository and the mailing list are all the tools needed to prepare contributions and fixes. It allows for easy forking and contributions to prosper. I would love to see this cause the community to grow. It would be awesome to see more committers and add additional PMC members.
As of now, log4j1 is still EOL. By examining future contributions we can have a discussion about the EOL status in the future. Lets take one step at a time! To me it is premature to open a public issue tracker or accepting pull requests from the public. Someone would have to review them and we would allow allocation of resources in favor of loosing other opportunities. As said, I voted +1 to provide the tools needed to let contributors work on contributions. I encourage you to end the discussions now and to start working on contributions instead. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Fri, Dec 24, 2021, 13:51 Vladimir Sitnikov <sitnikov.vladi...@gmail.com> wrote: > Dominik, > > Are you willing to add committers and PMC members to the log4j 1.x > community? > > If you forbid issues and pull requests, then it goes against the idea of > adding new commuters and PMC members for 1.x. > > How do you expect to nominate committers and PMC members if you > forbid pull requests, forbid non-CVE changes, and so on? > > How do you expect to nominate committers and PMC members if you > want to mention EOL all over the place? > > I would rather use "log4j 1.x is feature complete, so no new features are > expected to appear" > On the other hand, it should be perfectly fine to add new tests, fix > security issues, > fix other issues (e.g. NPEs). > > Vladimir >
