Hi All, I think GitHub Issue is a more basic issue tracking system than Jira. But as we have only one repository and not a strong need in terms of planning and work measurement, the Github solution can be very well suited. Another argument Pros: the mobile version of Github works much better than the hosted version of Jira. I'm in favor of this migration to GitHub.
Cheers, Nicolas Le lun. 24 oct. 2022 à 16:06, Hans Van Akelyen <[email protected]> a écrit : > Hi All, > > This mail is related to a mail that is going around in the users@infra > mailinglist [1] (log-in is required to view this mail). > > TL;DR: > The Apache infra team is planning to disable public sign-up to Jira, there > will be a self-service tool for PMC members to create accounts for people > that would like to have an account. There has been an ongoing fight with > spam users creating accounts and tickets/comments on our Jira server, they > are also planning to move to Jira cloud and this would also restrict us to > a maximum number of accounts on Foundation level. > > These changes would mean that users will only be able to create tickets > after contacting us to create an account or describe issues via the public > mailing list. > > Here are a couple of things that come to mind and would really love to have > input, on how you all feel about this. I will list my ideas, feel free to > write down everything that comes to mind. I will not yet formulate my final > preference as it might bias things. > > 1) We could keep everything as-is, this would mean that when a user > approaches us with an issue we either create an account for this user, or > create the issue ourselves. > Pros: > - All issues will be logged on the mailinglist > - We can ask/add additional information before a ticket is created > - We can add a user to Jira when he plans on creating multiple issues and > do the follow-up > Cons: > - More work on our side to create tickets/users > - Users will have to find their way to the mailing lists > - Users will not get notifications if their issue is being worked on (if > created by us) > > 2) Move to another issue platform (Github Issues) > Pros: > - Users can create their own tickets again (more inclusive) > - Tighter coupling with our source code (issue linking does work better in > GH) > - Everything on one platform > Cons: > - Migration of our current issues > - Triage work on the issues > - More work short term to change all our docs/references/... > > > Cheers, > Hans > > [1] https://lists.apache.org/thread/jx9d7sp690ro660pjpttwtg209w3m39w >
