The most recent email notification I got from an issue in that repository was today at 10:00 CDT.

https://pagure.io/fedora-join/Welcome-to-Fedora/issue/358

I'm assuming at the time that link worked, but it's been a 404 since at least 17:00 CDT.

Hrm, yeh, the project has completely disappeared!

https://pagure.io/projects/fedora-join/%2A

I'm assuming this is some sort of infra glitch (unless someone deleted the repo (?!)).

Filed: https://pagure.io/fedora-infrastructure/issue/11983

So, someone has deleted the repo:

https://pagure.io/fedora-infrastructure/issue/11983

I assume they were trying to stop getting notifications and have ended up deleting it. It's clearly an edge case, so I don't know if we need to tweak things:

• at the moment, we add all new comers to the fedora-join pagure group, giving them admin rights on all our repos
• the idea was that they should be able to work with tickets and make changes to the repos and so on, since everything is transparent and can be easily undone
• deleting a repo, however, is not easily undone---I'm not sure if we'll be able to get this repo back for example (I've asked in the infra ticket).

So (and I'd rather not, but), do we need to create a new group for newcomers that has fewer permissions to avoid such honest mistakes?

(I've removed the account that deleted the repo from our group for the moment)

Thoughts?

I think we should make a group with an appropriate balance of permissions so that people can manage their tickets. We want people to feel included, but we also have a legitimate need to protect things like the projects themselves so that we can avoid situations like this one.

In my mind it's not a whole lot different than how the infra folks run things. I'm new here, so they have me set up with a fairly basic set of read-only permissions and access to a limited scope of systems while I'm in the fi-apprentice group. Later as I learn more and folks get comfortable with me they might give me broader permissions as they need to. (Or they might decide something completely different, and I'd respect their decision.)

I don't feel like that makes us exclusive or unwelcoming, but rather it shows that we're trying to take reasonable measures to be good stewards of our resources.

Yeh, I agree. So:

• I've created a new group called fedora-join-admins which will have admin permissions on our repos
• the current fedora-join group will have commit permissions (which means folks can do everything but modify the settings of the repo)

We're waiting to see if the repo/project can be recovered. I do have a fork, probably outdated, but forks don't have copies of tickets :(

That's really weird=2E Maybe it was a mistake but all these organizations =
have sabotage and vandalism attacks, GDG Google developers group is no diff=
erent=20

On June 13, 2024 9:07:15 AM EDT, Paul Maconi pagure@pagure=2Eio wrote:

aggraxis added a new comment to an issue you are following:
``
I think we should make a group with an appropriate balance of permissions=
so that people can manage their tickets=2E We want people to feel included=
, but we also have a legitimate need to protect things like the projects th=
emselves so that we can avoid situations like this one=2E=20

In my mind it's not a whole lot different than how the infra folks run th=
ings=2E I'm new here, so they have me set up with a fairly basic set of rea=
d-only permissions and access to a limited scope of systems while I'm in th=
e fi-apprentice group=2E Later as I learn more and folks get comfortable wi=
th me they might give me broader permissions as they need to=2E (Or they mi=
ght decide something completely different, and I'd respect their decision=
=2E)

I don't feel like that makes us exclusive or unwelcoming, but rather it s=
hows that we're trying to take reasonable measures to be good stewards of o=
ur resources=2E
``

To reply, visit the link below or just reply to this email
https://pagure=2Eio/fedora-join/Fedora-Join/issue/293

Yeh, this was clearly an honest mistake. Stuff happens :)

Anyway, here's what I think we should do to get our process back on track:

• create a new repo, populate it with information from our forks, re-start ticketing
• if the old repo can be recovered, we'll migrate tickets from the new one back to the old one

How does that sound?

A new repo is here now:

https://pagure.io/fedora-join/WelcomeToFedora

Let's open new tickets!

@ankursinha With everything seemingly back in order I think we can mark this issue as resolved right? Just doing a bit of yard work/cleaning up a little.

Yeh, closing this. We'll use the new repo and if the old one is restored at some point, we'll see how to proceed.

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/join/Fedora-Join//issues/293