- Once submitted, your "add forge" request can either be: -

- Pending: - the request was submitted and is waiting for a moderator - to check its validity. -
- Waiting for feedback: - the request was processed by a moderator - and the forge was contacted, the request is waiting for feedback from the - forge. -
- Feedback to handle: - the forge has responded to the request and - there is feedback to handle for the request.
- Accepted: - the request has been accepted and waiting to be - scheduled. -
- Scheduled: - the request has been scheduled is considered - done. -
- First listing done: - The first listing of the forge is - completed. -
- First origin loaded: - The first origin or repository processed by - loader and archived (using a search query). -
Rejected: the request is not a valid request and is rejected by a - Software Heritage moderator.
Denied: the forge has requested not to archive the forge.
Suspended: the request is for a forge with a non supported - VCS.

- Once a add request has been submitted, you can follow its current status in - the - submitted requests list - . This process is depending on human interactions and might take a few days to be - handled (it primarily depends on the response time of the forge). -

+ Once a add request has been submitted, you can follow its current status in + the + submitted requests list. This process is depending on human interactions + and might take a few days to be handled (it primarily depends on the response + time of the forge). +

@@ -223,9 +161,93 @@

Prior to submit an "Add forge now" request, we ask + you to fill in the following parameters:

Forge type: the type of supported forge the software archive is able to list. + Currently, the supported types are: +
- cgit, for cgit forges
- gitea, for gitea forges
- gitlab, for gitlab forges
- heptapod, for heptapod forges
+
Forge url: the url of the selected forge. This must be unique. +
Forge contact name: Contact name of the forge administrator we + intend to ingest. +
Forge contact email: Contact email of the forge administrator so an + email can be send to the forge. The intent is to notify the forge prior to + actually start the ingestion. +
Consent checkbox: This checkbox's purpose is to know whether we can + explicitly mention the user's login within the email sent to the forge. If + not checked, the user's name won't be mentioned in the email at all. +
Comment: (Optionally) For the user to mention something more about + their request to the add-forge-now moderator. +

Once submitted, your "add forge" request can either be: +

+ Pending: + the request was submitted and is waiting for a moderator + to check its validity. +
+ Waiting for feedback: + the request was processed by a moderator + and the forge was contacted, the request is waiting for feedback from the + forge. +
+ Feedback to handle: + the forge has responded to the request and + there is feedback to handle for the request.
+ Accepted: + the request has been accepted and waiting to be + scheduled. +
+ Scheduled: + the request has been scheduled is considered + done. +
+ First listing done: + The first listing of the forge is + completed. +
+ First origin loaded: + The first origin or repository processed by + loader and archived (using a search query). +
Rejected: the request is not a valid request and is rejected by a + Software Heritage moderator.
Denied: the forge has requested not to archive the forge.
Suspended: the request is for a forge with a non supported + VCS.