Yes, I disagree for a few reasons: 1. Not all the people listed in the logging services team page contribute to each project. While it is probably OK for Log4j because most Logging Services members are contributing to Log4j the same would not be true for Log4cxx and Log4Net. 2. We are not going to add contributors to the Logging Services Team page so individuals who have made contributions but are not a committer or PMC member are not going to be acknowledged.
The main issue as I see it is that the developer list in the pom.xml is not being maintained. That is probably because we have never discussed it. The answer to that is pretty simple - we just need an agreement on when contributors to the project should be added and how long they should stay, as well as keeping the list of PMC members and committers accurate. Ralph On 2023/02/22 08:26:20 Volkan Yazıcı wrote: > I propose redirecting all "Team" links in Log4j, log4cxx, etc. to the > Logging Services Team page <https://logging.apache.org/team-list.html>. > > I know Ralph disagrees with me[, hence this email]. He wants the Log4j > project to have its own "Team" page where its content is populated from > `pom.xml`. I strongly disagree with this. `pom.xml` only contains people > who happen to care about having their names there: some PMC members, > committers, random contributors. It didn't even contain the entire Log4j > PMC – this I fixed myself while doing the recent site work. I don't know > what it represents, but that thing is certainly not _the team_. Having one > central place, the Logging Services Team page, is not only convenient, but > accurate; those people are the official maintainers. > > maven-site-plugin is dead > <https://cwiki.apache.org/confluence/display/MAVEN/Quo+Vadis+Maven+Site> > for a reason. > > Long story short, I would appreciate your input for a tie breaker. >
