This is relevant to potentially switching to GitHub issues.
Begin forwarded message: > From: fluxo <c...@apache.org> > Date: October 21, 2022 at 20:02:01 CDT > To: annou...@infra.apache.org > Subject: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira) > Reply-To: us...@infra.apache.org > > Hello PMC members, > > As I'm sure most of you are aware, the spam issues on Jira are getting worse. > We are seeing spam user creation of over 10,000 accounts per year, and > receive many requests per month from project members for help addressing spam > complaints. Infra is taking steps to disable public Jira signups. > > Infra has developed a self-service tool by which folks on a PMC can request a > Jira account for non-ASF contributors: > > > https://selfserve.apache.org/ > > > Click "Create a Jira user account" to go to: > > > https://selfserve.apache.org/jira-acct.html > > > You need to enter a username for the new Jira account. We will reject the > request if there is an existing account with that username. If this person > may ultimately become a committer, Infra recommends that they choose a > username that they can also use for their LDAP username. > > Next, the tool asks you to enter their Display Name. This is the "public > name" which will appear on all their Jira posts and comments. > > Last, the tool asks you to enter the user's email address. We expect the PMC > to exercise due diligence in making sure the contributor's email works. If it > does not, they will not get the password reset mail. > > > Infra knows this process change places an increasing burden on PMC members > for managing contributors, and makes it harder for people to contribute bug > reports. We suggest projects consider using GitHub Issues for customer-facing > questions/bug reports/etc., while maintaining development issues on Jira. You > can enable GitHub Issues for your repository via > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Repositoryfeatures > > > Infra has targeted 6 November for the date we switch off public signups for > issues.apache.org/jira . Please let us know if this will place any > significant burden on your teams. We are following an aggressive timeline > because of the serious impact spam users have on the safety and stability of > our infrastructure. > > As always, if you have any questions or comments about this, please let us > know! > > -Chris (fluxo) > > -- > @fluxo > Chris Lambertus > ASF Infrastructure >
