I'm somewhat annoyed that the spam in jira is not able to be automatically filtered out. The mailing lists don't seem to have an issue with spam.
Jira is definitely more powerful(and better in some regards) but the github issues and projects do seem to have more of a feature parity with Jira now. I will plan on enabling the Github issues for Log4cxx sometime in the next few days unless somebody strongly disagrees. -Robert Middleton On Sun, Oct 23, 2022 at 7:30 PM Matt Sicker <m...@musigma.org> wrote: > > Jira support is left in place for anyone who heavily relies on it already. > I’d prefer not to maintain two issue repositories, so I’d lean toward > switching to GH Issues. Would be nice if we could copy existing issues over > or have some sort of redirect URLs. > > A nice advantage to uses GHI would be using other actions to help maintain a > changelog file based on issues and PRs. That sort of thing integrates nicely > with Dependabot, too! > > — > Matt Sicker > > > On Oct 23, 2022, at 15:40, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > Using 2 issue tracking system sounds like a pain... :-( > > > > Gary > > > >> On Sun, Oct 23, 2022, 16:34 Ralph Goers <ralph.go...@dslextreme.com> wrote: > >> > >> Yup, I somehow missed that sentence. > >> > >> So they are suggesting that development continue to use Jira but users > >> report issues via GitHub. I would expect if we do that then we would also > >> create corresponding Jira issues for any of the GitHub issues we choose to > >> work on. > >> > >> Ralph > >> > >>>> On Oct 23, 2022, at 12:57 PM, Volkan Yazıcı <vol...@yazi.ci> wrote: > >>> > >>> Users will need to create a JIRA account, which needs to be supervised by > >>> the PMC, so that they can submit a bug report or ask a question. I cannot > >>> think of a more cumbersome method for a F/OSS project to accept issues. > >> Put > >>> another way, practically no public users will go this route. > >>> > >>> Please search for "GitHub Issues" in the original email, in particular, > >>> this statement: *"We suggest projects consider using GitHub Issues for > >>> customer-facing questions/bug reports/etc."* > >>> > >>> > >>> On Sun, Oct 23, 2022 at 9:48 PM Ralph Goers <ralph.go...@dslextreme.com> > >>> wrote: > >>> > >>>> I actually don’t know where this idea of switching to GitHub issues is > >>>> coming from. > >>>> The email from infra talks about how Jira will no longer allow random > >>>> users to sign > >>>> up and the tool they provided to allow the PMC to register users. I > >> would > >>>> guess the > >>>> expectation would be that we would provide some process for our users to > >>>> requests > >>>> ids from the PMC. > >>>> > >>>> What does any of this have to do with GitHub issues. I see no mention of > >>>> that in > >>>> the email from infra. > >>>> > >>>> Ralph > >>>> > >>>>> On Oct 23, 2022, at 12:10 PM, Volkan Yazıcı <vol...@yazi.ci> wrote: > >>>>> > >>>>> I personally think this is great news in the long run. I already had > >>>>> pitched the idea of moving to GitHub Issues earlier, but it was back > >> then > >>>>> rejected due to various reasons; GitHub is proprietary, JIRA also plays > >>>> an > >>>>> archive role due to its age, `changes.xml` sort-of requires JIRA > >> tickets, > >>>>> etc. World spam organizations solved the discussion for everyone. 😜 > >>>>> > >>>>> We were already receiving bug reports via Issues, nothing has changed > >> in > >>>>> this regard. Yet we need to reflect the official switch to Issues in > >> our > >>>>> documentation, which right now points users to JIRA > >>>>> <https://logging.apache.org/log4j/2.x/support.html>, too. I also > >> expect > >>>>> more questions funneled via StackOverflow, since several people were > >>>> using > >>>>> JIRA for asking questions too. Last but not least, maybe this would > >>>> create > >>>>> sufficient leverage to replace `changes.xml` with something else. > >>>>> > >>>>> On Sat, Oct 22, 2022 at 4:53 AM Matt Sicker <m...@musigma.org> wrote: > >>>>> > >>>>>> 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 > >>>>>>> > >>>>>> > >>>> > >>>> > >> > >>
