I followed the migration of the Apache Beam project from JIRA to GitHub issues and that worked fine. As such I'm in favor of doing that migration to GitHub.
Perhaps we can check with the Apache Beam devs to see if they have a plan or script that they followed? Cheers, Matt On Mon, Oct 24, 2022 at 5:06 PM Hans Van Akelyen <[email protected]> wrote: > Hi Ricardo, > > The ASF Infra team offers us a wide variety of services, list of available > services can be found here: https://infra.apache.org/services.html > There is actually not a single mandatory service. There are a couple of > mandatory concepts. > > 1) code must be public > 2) discussion (aka mailinglist) must be available and public > > If you want to set-up your own mailinglist you are free to do so (you would > be insane to not use this service, but it is an option) > > So there are no standards, there are projects using Jira, Bugzilla, GH > Issues, their own Jira, fill in the blank…. > > Currently we are using the Jira hosted/managed by the ASF Infra team. > > Cheers, > Hans > > > > On 24 October 2022 at 16:50:32, Ricardo Gouvea ([email protected]) > wrote: > > Just understanding the possibilities. Does being outside the Apache > standard bring us any problem or ease? > > Any idea how other Apache communities are handling this? > > Cheers, > > Em seg., 24 de out. de 2022 às 11:36, Hans Van Akelyen < > [email protected]> escreveu: > > > Hi Ricardo, > > > > The issue is not the spam itself we can delete issues and comments in our > > Jira project too. But we have to report them to the ASF Infra team to > > delete the user. This is putting quite a lot of strain on their team in > the > > past year over 10.000 accounts have been created on the Jira server. As > > they want to migrate to Jira cloud (and will have to pay per user) the > only > > solution they see is restricting user creation. > > > > So this part of the discussion is final and can’t be changed this means > > users can no longer create their own account in the near future. > > > > This means we will have to adjust our workflow…. I think we have 2 > options, > > accept this (extra burden?) and create a ticket when we get a mail, or > > create an account for that user. This however might increase the > threshold > > for people wanting to submit an issue…. > > > > Or we move to a platform where public account creation is active Github > > Issues, our own Jira, or random platform X…. > > > > Cheers, > > Hans > > > > > > > > On 24 October 2022 at 16:18:40, Ricardo Gouvea ([email protected]) > > wrote: > > > > I understand the situation Hans, but even migrating to GH, wouldn't we > have > > the same Spam problems? > > > > Cheers, > > > > Em seg., 24 de out. de 2022 às 11:06, Hans Van Akelyen < > > [email protected]> escreveu: > > > > > 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 > > > > > > > > > -- br/> < > > > > > > <https://www.openin.com.br> > > > > Patrocinadora Oficial do > > > > Pentaho Day 2019 > > > > Ricardo Gouvêa > > > > CEO > > > > [email protected] > > > > Mobile: +55 11 9 9638-9238 > > > > > > Openin - Your Partner in Data > > > > www.openin.com.br > > > > [image: Openin no Linkedin] [image: Openin no Facebook] > > <https://www.facebook.com/Openinbr/> [image: Openin no Instagram] > > <https://www.instagram.com/openinbr/> [image: Openin no Twitter] > > <https://twitter.com/OpeninBigData> [image: Openin no Youtube] > > <https://www.youtube.com/openinbigdata> > > > > > -- br/> < > > > <https://www.openin.com.br> > > Patrocinadora Oficial do > > Pentaho Day 2019 > > Ricardo Gouvêa > > CEO > > [email protected] > > Mobile: +55 11 9 9638-9238 > > > Openin - Your Partner in Data > > www.openin.com.br > > [image: Openin no Linkedin] [image: Openin no Facebook] > <https://www.facebook.com/Openinbr/> [image: Openin no Instagram] > <https://www.instagram.com/openinbr/> [image: Openin no Twitter] > <https://twitter.com/OpeninBigData> [image: Openin no Youtube] > <https://www.youtube.com/openinbigdata> > -- Neo4j Chief Solutions Architect *✉ *[email protected]
