I propose to add@BaseMax as collaborator, to help with bug triage and project management.
Max is a very prolific Open Source contributor and have helped many projects (seehis profile).

Note: To prevent misunderstandings, "contributor" is not the same thing as "committer" and IMHO this PR does not require a PMC vote.

Add Max Base as collaborator

19c83d7

I propose to add@BaseMax as collaborator, to help with bug triage andproject management.Max is a very prolific Open Source contributor and have helped manyprojects (see [his profile](https://github.com/basemax)).**Note**: To prevent misunderstandings, "contributor" is not the samething as "committer" and IMHO this PR does not require a PMC vote.

github-project-automationbot added this toLog4j bug tracker

May 9, 2025

github-project-automationbot moved this toTo triage inLog4j bug tracker

May 9, 2025

ppkarwasz requested a review fromvy

May 9, 2025 18:56

Copy link

Member

vy commentedMay 13, 2025

@ppkarwasz, thanks so much for helping with sourcing contributors.

Given@BaseMax has no track record of contributing to any of the Apache Logging Services projects, I'm inclined to first see his contributions, preferably, for a certain period of time. AFAICT, he/anyone should not need special privileges/rights to help with triaging and/or prioritization. If there are any blockers for him from carrying out this work, please share them explicitly.

Regarding adding labels to issues and making updates to the Log4j bug tracker, he can just ping us in comments, and we can do the clicking for him.

Relaxx422 approved these changes

May 13, 2025

View reviewed changes

Copy link

ContributorAuthor

ppkarwasz commentedMay 16, 2025

The triaging role in GitHub is so limited, that I don't think we should set the bar too high to assign it.

However, since triagerscan not do many simple things like creating labels, we should probably first sit down and add some order to the labels we are using, before wasting time assigning labels that will be removed.

If we want to use GitHub Projects and the new GitHub features:

labels that indicate the type of issue report (bug,enhancement) can be replaced with GitHub issue types.
labels that indicate the affected Log4j component, can be replaced with a custom field in GitHub Projects.
labels that indicate the state of the PR or issue report can be replaced with fields in GitHub Projects.

We should probably start by specifying the set of all possible states for an issue report and a PR. I'll try to make a draft state diagram and then we'll schedule a call with@BaseMax for some feedback.