Most Apache projects are already mirrored on GitHub so I'm not sure mirroring on yet another service would make sense. It might confuse people even more. Maybe.
Gary On Tue, Oct 22, 2024, 2:46 PM Delany <delany.middle...@gmail.com> wrote: > Maybe its me but I never got the hang of JQL so JIRA always been difficult > to find stuff, not to mention it's dog slow. > > There was mention of GitHub's terms of service. Its not the only game in > town though - what about Gitlab or even Gitea? > I'm sure they'd appreciate being able to host project code like Maven. Just > a thought. > > Delany > > On Tue, 22 Oct 2024 at 19:11, Matt Nelson <thefla...@gmail.com> wrote: > > > I think the user experience for everyone but the most active members may > > regress by moving issues to GH. Maven has a lot of repositories(100+) and > > almost as many jira projects. I'm never quite sure if I'm logging an > issue > > to the correct jira project. And I suspect that federating out into 100+ > > different places may exacerbate issues being logged to the "wrong" repo. > > But when creating an issue on jira, there is a project drop down that can > > guide in the correct direction and see if another project is more > relevant. > > > > Today I can search jira and find issues across all the maven projects. I > > can then use JQL to slice and dice on many facets. Even without the > > category filter, the results are almost always relevant and point me to > the > > "correct" project to further dig into. > > > > > https://issues.apache.org/jira/issues/?jql=description%20!~%20doxia%20and%20category%20%3D%20Maven > > > > A similar search across the entire Apache GH org is quite different. This > > could be mitigated by putting some automation in place to add labels to > > every issue. > > https://github.com/search?q=org%3Aapache+stacktrace&type=issues > > > > I think some of this could be an education gap on how to best leverage GH > > issues, but there are likely also feature gaps from jira to GH as well. > > > > > > On Tue, Oct 22, 2024 at 9:54 AM Guillaume Nodet <gno...@apache.org> > wrote: > > > > > I'd like to start discussing opening (and eventually slowly switching) > > from > > > JIRA to GitHub issues. > > > > > > JIRA is a bit of a pain to use, even though we have some automatic > links > > > done with PRs and such. Accounts need to be authorized to maintain the > > > number of external accounts low enough within the ASF, whereas this > would > > > only require a GitHub account. > > > Release notes can be published on GitHub very easily, so the only thing > > is > > > that we have the whole history and list of opened issues, but I just > see > > > new issues being created on GitHub and handling both sources for some > > time, > > > gradually moving to GitHub issues only. > > > > > > I also think we could benefit from GitHub discussions. Those can be > > backed > > > by the mailing list very easily (just by configuration) and that would > be > > > easier to link to issues, PRs and more integrated into GitHub, with > > > markdown support, etc.... See > > > https://github.com/apache/opendal/discussions/5211 for example. > > > > > > Thoughts ? > > > -- > > > ------------------------ > > > Guillaume Nodet > > > > > >
