The mission of Software Heritage is to collect, preserve and share all
the publicly available source code: https://www.softwareheritage.org
We have received a request to add the forge hosted at the URL below
to the list of software origins that are archived, and it is our
understanding that you are or know the contact person for this forge.
In order to archive the forge contents, we will have to periodically
pull the public repositories it contains and clone them into the
Software Heritage archive. FAQs for our processes are available:
Please let us know if there are any issues to consider before
we launch the archival of the public repositories hosted on your
infrastructure. Please use « Reply all » to ensure our system will
process your answer properly.
In the absence of an answer to this message, we will start to archive
your forge in the coming weeks. Only the publicly accessible
repositories will be archived.
Could you tell us who have made the request or is it a anonymous process ?
From what i’ve read in your FAQ, the process should not overload our forge, nice. One question: will you clone all the forge or only a specific organization ? FTR, our forge contains more than a thousand repos, maybe you should archive only the repos containing SPIP code and not its plugins. SPIP code is located in this org spip · GitLab
Could you tell us who have made the request or is it a anonymous process ?
Add Forge Now submission requires a login, but the requester for git.spip.net did not consent to share their identity with you.
From what i’ve read in your FAQ, the process should not overload our
forge, nice. One question: will you clone all the forge or only a
specific organization ? FTR, our forge contains more than a thousand
repos, maybe you should archive only the repos containing SPIP code
and not its plugins. SPIP code is located in this org spip · GitLab
We generally clone all repos, but for GitLab it is possible to restrict
the scope if that is wanted. Personally I would suggest to archive the
plugins and other code as well, unless there is a reason other than
load. After the first ingestion, we do full clones of new repos,
incremental clones of updated repos and ignore the unchanged repos.
