+1 as well. As I use GitHub at work it'd be easier to track issues and changes in sis there as well.
On Wed, 12 Nov 2025, 09:14 Alexis Manin, <[email protected]> wrote: > +1 for Github issue tracker. > > Apart from gaining visibility, it also allow for better integration > between source code and issues (referencing commits or PRs in issue > tracker, pointing to a specific code location, etc.). > > Regards, > > Le mer. 12 nov. 2025 à 08:50, Johann Sorel > <[email protected]> a écrit : > > > > Yes for the github issue tracker. > > > > I guess /every/ developer worldwide has a github account, this would > > help making SIS more friendly. > > > > Johann > > > > Le 10/11/2025 à 11:34, Martin Desruisseaux a écrit : > > > Hello all > > > > > > Apache SIS currently uses JIRA for issues tracking [1]. But it may not > > > have as much visibility as GitHub issues. Would it help users and > > > potential contributors if we migrate issues from JIRA to GitHub? The > > > ASF mentions this possibility in [2]. > > > > > > Note: it would require that we copy the existing JIRA issues to GitHub > > > first. The Maven project went through this process [3], so maybe we > > > could leverage their experience. But it will require some effort in > > > any case. > > > > > > Martin > > > > > > [1]https://issues.apache.org/jira/browse/SIS/ > > > [2]https://infra.apache.org/request-bug-tracker.html > > > [3] > https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching > > > > > > >
