Migrate the Defensive Coding Guide to Forge #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Defensive Coding Guide is published at https://docs.fedoraproject.org/en-US/defensive-coding/ and the repository is currently still in Pagure at https://pagure.io/defensive-coding-guide.
I discussed the repo earlier with the main contributor, @huzaifas, and he essentially said that he wanted to continue to maintain it, and agreed that putting it here under security would probably be best. However, despite the pagure deadline being only a few days away, it still isn't migrated. That isn't a huge problem, since after the end of the month pagure should remain available read-only, which means the repo can still be published, but making any changes will require it to be migrated first.
I think this is more or less a "sub issue" of #14 in which the defensive-coding guide is already listed.
@py0xc3 could you do the Forge import please, I don’t have enough permissions to do it on the Security group.
I think this makes sense to leave as a standalone repo.
Yes, makes sense. I can do the import tomorrow or later today, we'll see. I'll put it still in the matrix chat, just to have others getting the chance to add their thoughts before it gets closed, just in case someone wants to have a discussion about us taking over responsibility for this or so. But I can do the import as its revertible anyway.
If we do that, merge privileges and such will be limited to Security SIG members I think (I can do exceptions within repos but I think they are only for within the Security SIG group). I can have another look tomorrow about this, or maybe someone knows off the cuff.
Migrated: https://forge.fedoraproject.org/security/defensive-coding-guide
If I shall add it to the agenda of the next meeting or so, let me know or add the meeting label.
Otherwise, it's now migrated to the security SIG space, with the default security SIG privileges.
Supplement: it seems I can add individual collaborators, but I would prefer to have it discussed/approved in advance before I would add external contributors with privileges to any security SIG repos. They can open PR anyway.
@py0xc3 wrote in #19 (comment):
Awesome, thanks! I updated our site config so the docs will build from the new location. I also pushed a commit to the old repo that wipes everything but the README and leaves a link to the new location - we've done the same for a bunch of other previously, too.
I think this issue can be closed now; reopen if you still need it for something.