Skip to content

Define and document workflow for "save requests" for tarballs

Currently, team members and ambassadors have access to the save code now functionality for tarballs. When a user asks SWH for saving tarballs, we need to dispatch this request to ambassadors in a traceable manner.

To this end, a proposal is to create a "save requests collection" or "rescue mission" project in the forge (here and migrate to gitlab) and create tickets under the project with the following template:

Title: [save request] submit <name> tarball link to save code now
Description: 

Here is the link to source code page where code needs rescuing:
<link> / <list of links>

visit page and download content from direct link.

Please verify that the tarballs are source code and submit the direct link in:
save.softwareheritage.org

The ticket should be labeled (tagged) also Ambassadors.

This project can also be a holder of forges that needs to be rescued, similarly as the https://wiki.softwareheritage.org/wiki/Suggestion_box:_source_code_to_add


Migrated from T3673 (view on Phabricator)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information