Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add all active team members as developers #351

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ppkarwasz
Copy link
Contributor

This change modifies the POM file and adds all the active Apache Logging Services team members as developers in the order:

  • PMC Chair
  • PMC Member
  • Committer

Since jobs come and go and people forget to update the POM file, when they change affiliation, all the entries:

  • Use the @apache.org e-mail.
  • Use https://github.com/sponsors/<userId> as URL, which is redirected automatically to https://github.com/<userId>/ if the user does not have a GitHub Sponsors profile.
  • Use The Apache Software Foundation as organization.

This change modifies the POM file and adds all the active Apache Logging Services team members as developers in the order:

- PMC Chair
- PMC Member
- Committer

Since jobs come and go and people forget to update the POM file, when they change affiliation, all the entries:

- Use the `@apache.org` e-mail.
- Use `https://github.com/sponsors/<userId>` as URL, which is redirected automatically to `https://github.com/<userId>/` if the user does not have a GitHub Sponsors profile.
- Use `The Apache Software Foundation` as organization.
In Apache addresses you can use `-<anything>` aliases.
Copy link
Member

@vy vy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ppkarwasz, I am against this change:

  1. Roles come and go. Why do we follow a role-based ordering? (Want to appear at the top?)
  2. My organization is not ASF and I don't want to use my @apache.org email address either. (WTF?)
  3. I want to point to my personal home page, not some ASF/GitHub facade.
  4. adds all the active Apache Logging Services team members Why? This is "a subproject of ALS", not "the ALS project". Why do we need to list here the name of individuals who never ever done anything for logging-parent and/or Log4j?

I am fine with removing temporal organization, roles, timezone entries – this will pretty much ensure sustainability. Though I prefer to respect to author's choice of id, name, email, and url.

@ppkarwasz
Copy link
Contributor Author

@vy,

I was planning to start a thread on dev@logging and point to this PR, but I forgot the former. 😉
Your remarks are all valid and I will address them after I post on the mailing list.

@ppkarwasz
Copy link
Contributor Author

ppkarwasz commented Mar 21, 2025

I started a thread on dev@logging.

  1. Roles come and go. Why do we follow a role-based ordering? (Want to appear at the top?)

I see the <developers> section as a prioritized contact list. The person to contact for the latest release is the PMC Chair, when his term is up, someone else takes his place.

I don't have any evidence that the <developers> section was ever used to contact a developer or any other purpose, so this is pure speculation.

  1. My organization is not ASF and I don't want to use my @apache.org email address either. (WTF?)
  2. I want to point to my personal home page, not some ASF/GitHub facade.

We probably should remove the organization everywhere.

One of the reasons this is a draft, is to allow team members to recheck and update the data they provide. The e-mail and URL are "safe" default with a -pom suffix to the Apache e-mail to help identifying the source of the data.

BTW: This PR must not be entirely futile, since it drove your attention to the fact logging-parent is already using your @apache.org e-mail.

  1. adds all the active Apache Logging Services team members Why? This is "a subproject of ALS", not "the ALS project". Why do we need to list here the name of individuals who never ever done anything for logging-parent and/or Log4j?

If we list the people "responsible" for our artifacts, that list includes also Log4cxx and Log4net developers. Some Log4j releases were validated thanks to their votes.

I think that this should not be a list of copyright holders or maintainers that are also copyright holders. We could retrieve such a list from Git, but it might be inaccurate.

I am fine with removing temporal organization, roles, timezone entries – this will pretty much ensure sustainability. Though I prefer to respect to author's choice of id, name, email, and url.

I completely agree with you. This is a draft and it will not be merged unless people agree on their data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants