[
https://issues.apache.org/jira/browse/LOG4J2-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-3285:
--------------------------------
Attachment: image-2021-12-24-09-45-20-341.png
> JIRA tickets should be able to be assigned to Contributors and not just
> Committers
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-3285
> URL: https://issues.apache.org/jira/browse/LOG4J2-3285
> Project: Log4j 2
> Issue Type: Request
> Reporter: Michael Vorburger
> Priority: Major
> Attachments: image-2021-12-24-09-45-20-341.png
>
>
> New issue to follow up re. this from LOG4J2-3284, this is not about code but
> tooling configuration and process for community management:
> bq. I don't believe this Jira configuration allows us to assign tickets to
> folks who aren't committers.
> This is strange. It's definitely possible to fix this at the ASF. FYI I often
> do this myself in another JIRA project at the ASF - the FINERACT one. Myself
> or other committers of Apache Fineract such as [~awasum] or
> [[email protected]] ([~ptuomola]) traditionally "promote" anyone who
> has succssfully contributed a PR or two by adding them to a group in JIRA so
> that they can assign assign to themselves that they want to work on. (Long
> before we invite such people to become committers in our ASF community.)
> May I suggest that this gets fixed for the Log4j JIRA project? I believe this
> is important for a healthy community and to encourage active contributors
> from folks who are not committers. Note that on GitHub issues this is the
> default. I volunteer to help fix this for LOG4J2, if you would like to make
> me a JIRA Admin for this project. [~ckozak] if you are not a JIRA Admin for
> LOG4J2 yourself, who is?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
