GitHub issues could be a good replacement for jira IMO.
Mailing lists do not have an issue with spam because there are human
moderators doing most of the filtering. ;-)
There are several moderation messages every day, some of them even directly
land in my spam folder and I won't bother finding
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.
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 2 issue tracking system sounds like a pain... :-(
Gary
On Sun, Oct 23, 2022, 16:34 Ralph Goers 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 al
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
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
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 provid
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. Wo
