ppkarwasz commented on PR #3657: URL: https://github.com/apache/logging-log4j2/pull/3657#issuecomment-2886091203
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 triagers [can not do many simple things like creating labels](https://github.com/orgs/community/discussions/5773), 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
