• 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?)

At least a script to get a list of tickets ordered by last modification date.
And maybe the possibility to filter based on tags.

I think a monthly check in for 3 months; then finding a second interval that works (i.e every 3 months after) would be amazing.

• 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?)

At least a script to get a list of tickets ordered by last modification date.
And maybe the possibility to filter based on tags.

So I may be totally incorrect but I do believe we used to have at least some useful scripts related to this. Let me go see if I can find them.

Aha! Found them! https://pagure.io/fedora-join/Fedora-Join/blob/master/f/scripts

• 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?)

At least a script to get a list of tickets ordered by last modification date.
And maybe the possibility to filter based on tags.

Didn't see a utility with the functionality you wanted so I'm currently writing a python script for it.

How does this look so far?

It's a nice idea, and I see something that you can do.

I just went through 35 tickets manually, and got a 10% reply rate.

I think I got that reply rate because I responded to the interests and skills described in the new users introduction and comments.

It would be useful to automate notifications, but I think understanding the new user is key to recruitment.

So what I've written doesn't automate a reply, it just makes it easier to see everything. When you select a ticket it shows you the original ticket content along with any current comments on the ticket. It then gives you the option to comment.

I made a small video to demo it. Do note that It's still a WIP and I'm having some issues with pulling comment content.

@markrosenbaum

Hi! and thx for your time, effort and commiment, but I've got a sujection:

Instead of creating the ghost ticket in the Welcome repo, it is better to create it in the JOIN-sig repo so only members of the join-sig can see it and once the script is finished, change it to the Welcome repo, because in this way we avoid confusing newcomers with spam in the welcome repo.

P.D: we don't want create excesive noise in welcome repo

Regards.,

So what I've written doesn't automate a reply, it just makes it easier to see everything. When you select a ticket it shows you the original ticket content along with any current comments on the ticket. It then gives you the option to comment.

Cheers, Mark. I was hoping I was not dissuasive of a great idea. What would be really good is if, say, after 5 weeks, an automated reply could be sent. Better that than nothing.
I note Justin said in Matrix that it might be better to get your Python going in the new Forgejo system.

Best regards,
Mat

Thanks for working on this @markrosenbaum . That'll really make it easier for me to go through the various tickets. Going through the web interface is quite slow for me, and I forget what tickets I've already used.

Would it be possible to:

• move a ticket to a "processed" queue after we've commented on it etc., just to make it easier for us to know that we've already processed it?
• give us an option to update tags so we can mark them with the "status check" tags? (this is probably more complex, and perhaps not necessary at the moment..)

For anyone looking to use it, a preliminary version of the ticket tool can be found at https://markrosenbaum.fedorapeople.org/Fedora%20Join/ and future more polished versions will be added to the scripts repo in git.