We have some cases, where we have external repositories for systems (e.g. PRESS for the historic systems). For the active systems there are mostly external repositories, sometimes even on departmental servers.
I would generally like to have a fork in the theoremprover-museum organization and keep that up to date automatically. Then we have a safety measure (KISS) when these repositories go away. There may even be a way to update from other (i.e. non-git) repository types (but this is a longer-term problem we can address when we need to).
We have some cases, where we have external repositories for systems (e.g. PRESS for the historic systems). For the active systems there are mostly external repositories, sometimes even on departmental servers.
I would generally like to have a fork in the theoremprover-museum organization and keep that up to date automatically. Then we have a safety measure (KISS) when these repositories go away. There may even be a way to update from other (i.e. non-git) repository types (but this is a longer-term problem we can address when we need to).