We used to do this before but stopped at some point. The idea was to go through (manually) the recently filed Welcome to Fedora tickets to see how folks were doing, and drop a comment asking if there was anything we could do to help.
newcomers: would you find this useful?
everyone in the join-sig : would you be able to help with this if we restart it?
Another, but a second order question:
would it be possible to automate this in some way using the Pagure API (or coming up with a script that helps us doing it in a command line app or something rather than having to go through tickets manually?)
I am wondering if it might be more helpful to first plan how we will adapt our workflow to Forgejo, as far as training new Join SIG contributors goes? I know this is not immediately ready, but there is a public sandbox instance online. Maybe we could get a headstart on figuring out how to retool the workflow for a new platform?
It’s not very difficult to do monthly status checks, so we could still use the help checking in on people from next week to next month.
In the ‘Welcome to Fedora’ readme I am just about to finish updating, it says ‘every two weeks’. Should I change that to ‘every month for three months’
I prefer monthly, two weeks goes by very fast.
Lets have a play in the new sandbox too!
EDIT: I cannot sign in with either the ‘sign in’ or with the ‘sign in with FAS’ options at Forgejo
The only change I expect is that we’ll open tickets at Forgejo instead of Pagure, and the script that Mark wrote will need to be tweaked for it. We’ll create the same fedora-join/fedora-join-admin groups on Forgejo too to manage permissions. (We really don’t use the forge for anything else). There’s no other tooling—it’s all just us using tickets, and at the moment is done manually.
This is sort of why I don’t consider moving to Forgejo an urgent task. I’d rather that other folks move to it and we ensure that it’s stable—because we do not want newcomers to have a negative experience if there are initial teething issues. I also expect that once people begin to migrate to Foregejo, perhaps the community will come up with scripts etc. that enable moving of issues from Pagure to Forgejo and so on—I don’t think the Join SIG has the bandwidth to spearhead these, and we’d like to not lose our current tickets if at all possible.