Question related to Sagemath permission on Github

[Juan Grados]

I have a question about how you deal with deletion policies in Sagemath. Specifically, I plan to create a repository with many people involved. This repo MUST have several admins (who can potentially delete the repo). To protect the repo from arbitrary deletion, I need to know if Github allows adding a rule to avoid a repository being deleted by a single person. In other words, I need to know if there is a way to add a rule where others must agree each time one wants to delete a repo. Do you know that? or have you had the same question in Sagemath? If so, how do you solve it?

Thanks in advance for your time.

---------------------------------------------------------------------
D.Sc. Juan del Carmen Grados Vásquez
Laboratório Nacional de Computação Científica 
Tel: +55 21 97633 3228

(http://www.lncc.br/)
http://juaninf.blogspot.com
---------------------------------------------------------------------

[Dima Pasechnik]

On 21 January 2024 12:25:23 GMT, Juan Grados <jua...@gmail.com> wrote:
>I have a question about how you deal with deletion policies in Sagemath.
>Specifically, I plan to create a repository with many people involved. This
>repo MUST have several admins (who can potentially delete the repo). To
>protect the repo from arbitrary deletion, I need to know if Github allows
>adding a rule to avoid a repository being deleted by a single person. In
>other words, I need to know if there is a way to add a rule where others
>must agree each time one wants to delete a repo. Do you know that? or have
>you had the same question in Sagemath? If so, how do you solve it?

I don't know for sure (I would be surprised if they had this feature), but you can just
have a mirror for this repository (which is a good idea regardless).

HTH
Dima

[Nils Bruin]

On Sunday 21 January 2024 at 04:25:42 UTC-8 Juan Grados wrote:

To protect the repo from arbitrary deletion, I need to know if Github allows adding a rule to avoid a repository being deleted by a single person.

If you encourage a workflow with forks and pull requests then everybody will have their own copy anyway. Then the question is more: is there a way to reinstate a repo after it is deleted? Then it will be recovering from an admin mistake, just as any misjudged commit will be (if you have to worry about your admins inadvertently deleting your repo then you'll have to worry about wrong merges even more). And if you expect that your admins are prone to making mistakes, people will probably be much happier living mainly in their own repo and only interacting with the central one if they have to (for pull requests). It of course does add a level of indirection to staying up-to-date, but I think the sage github documentation has some tips on minimizing the pain in that (and otherwise other projects will).

[Jan Groenewald]

https://docs.github.com/en/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories

--
You received this message because you are subscribed to the Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/0663f1c7-fc7b-4252-8bb9-07b3f48de6fcn%40googlegroups.com.