The hive project decided to use a dedicated mailing list for requiring a jira account.
https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-JIRA And maybe we could enable github issues to let users ask questions and report bugs there first, if we decided it is a true problem that needs to be fixed, we could create a jira account for the user who reported the problem. I think if there are communications then it will be easier to let the users fill some sort of forms. Thanks. Andrew Purtell <andrew.purt...@gmail.com> 于2022年10月23日周日 00:50写道： > > The Yetus tools invoked by create-release use JIRA as source of truth for > changelog and release notes and there is not an alternative that I am aware > of, although perhaps there is one. So, we can to look at that: Can Yetus, or > create-release, be modified to generate changelogs and release notes from > GitHub issues instead? If so we could abandon Apache JIRA and avoid this new > burden, although that would make referring to anything historical on current > issues inconvenient, so is not ideal, in my opinion, but would return us to a > low touch process. > > Let me observe that once a contributor is onboarded to JIRA by one of us > using this “self service” tool, how that user interacts with the project is > the same as now. The one change here is the GitHub user cannot sign up for > the JIRA account on their own. It might not be too bad. Perhaps there is a > way to pre fill our GitHub issues and PRs with template text that requests > the user’s JIRA ID. We would document this new JIRA signup process in the > template so users can proactively determine if they require onboarding to > JIRA or not. Then one of us (PMC) has to do it, one time for each unique > contributor. This is burdensome. It would delay our response that first time > from the perspective of the new contributor while the JIRA onboarding is > pending. But if it’s the new policy it is not avoidable. > > Like today, if the GitHub user does not want to onboard to JIRA we ignore the > issue or PR. That doesn’t represent a change of policy. > > I have a feeling there will be changes to this announced policy. Only those > projects where commercial entities have their employees on the PMC getting > paid to do user onboarding administrivia will not see some sort of impact. > The long tail of everyone else will see declines that will be reflected in > statistics that Whimsy generates for the Board reports. > > > > On Oct 21, 2022, at 7:58 PM, 张铎 <palomino...@gmail.com> wrote: > > > > Because of spam users, the infra team plans to shutdown self > > registration of jira account and suggests ASF projects to make use of > > github issuesfor tracking customer facing questions/bugs. > > > > What should we do? > > > > ---------- Forwarded message --------- > > 发件人： fluxo <c...@apache.org> > > Date: 2022年10月22日周六 09:02 > > Subject: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira) > > To: <annou...@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
