Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-27 Thread Karl Heinz Marbaise
Hi, +1 from that... also Github Discussions is a good point... because otherwise the discussions often end up in JIRA Issues... Kind regards Karl Heinz Marbaise On 22.10.24 16:52, Guillaume Nodet wrote: I'd like to start discussing opening (and eventually slowly switching) from JIRA to GitHub i

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-27 Thread Timothy Stone
On 10/24/24 11:10 AM, Giovanni van der Schelde wrote: ...snip... 0 / -1 While I'm not most familiar with ticket management on bigger open source projects on GitHub, I can imagine it might be a bit more tricky to relate issues like you can with tools like Jira. Features like 'related to', 'dupli

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-27 Thread Timothy Stone
On 10/22/24 2:44 PM, Delany wrote: 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. +1 I'm a HUGE fan of GitLab (and "Notable Hero" havi

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-24 Thread Giovanni van der Schelde
Hi, +1 Switching from Jira to GitHub brings the benefit of reducing the hurdle for people to start contributing. I don't have statistics but I can imagine that quite some people (who would like to commit) don't even know we are using Jira and the mailing list. And if they do, it is still an extra

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-23 Thread Mirko Friedenhagen
> Am 22.10.2024 um 16:52 schrieb Guillaume Nodet : > > 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 ma

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Guillaume Nodet
Le mar. 22 oct. 2024 à 19:13, Matt Nelson a écrit : > 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

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Gary Gregory
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 wrote: > Maybe its me but I never got the hang of JQL so JIRA always been difficult > to fin

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Delany
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

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Ralph Goers
GitHub can be a pain with all the email it generates. However, I would think Maven would be the perfect project to use discussions and issues. Every maven plugin would have its discussions in its repo so following along with areas one is interested in could be much easier. This list would still

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Matt Nelson
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+ diff

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Romain Manni-Bucau
+1 while it stays forwarded to the list (dev@ only I guess) and we close jira projects to avoid 2 sources of truth (side effect being to update sites to reflect that project by project) Romain Manni-Bucau @rmannibucau | Blog |

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Tamás Cservenák
+1 for moving to GH issues On Tue, Oct 22, 2024 at 4:53 PM Guillaume Nodet 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. Account

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Matthias Bünger
+1 (nb) I like Github Issues more then the JIRA ones as esp. the formatting is far much more comfortable than in JIRA. I could also imagine that the project recieves more issues (I only hope for useful ones, but well there might be more useless too), due the fact that many people have an Github

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Slawomir Jaranowski
On Tue, 22 Oct 2024 at 17:02, Michael Osipov wrote: > > Am 2024-10-22 um 16:52 schrieb Guillaume Nodet: > > 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 > > do

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Slawomir Jaranowski
+1 We can start step by step from projects with a little number of open issues, e.g. all shared components. We already have done it for parents poms. On Tue, 22 Oct 2024 at 16:54, Guillaume Nodet wrote: > > I'd like to start discussing opening (and eventually slowly switching) from > JIRA to Gi

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Michael Osipov
Am 2024-10-22 um 16:52 schrieb Guillaume Nodet: 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 numbe

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Amess Xeno
+1 for killing jira From: Guillaume Nodet Sent: Tuesday, October 22, 2024 10:52:56 PM To: Maven Developers List Subject: [DISCUSS] Enable GitHub issues and GitHub discussions I'd like to start discussing opening (and eventually slowly switching) from JI

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Guillaume Nodet
Really, support for Markdown in issues would be a pain healer. I did spend 15 minutes trying to format an issue correctly because whenever you switch between "Visual" and "Text" mode, your {{ }} are mixed up ... That's really painful. Le mar. 22 oct. 2024 à 16:52, Guillaume Nodet a écrit : >

[DISCUSS] Enable GitHub issues and GitHub discussions

2024-10-22 Thread Guillaume Nodet
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,