diff --git a/swh/web/templates/add_forge_now/create-request.html b/swh/web/templates/add_forge_now/create-request.html
--- a/swh/web/templates/add_forge_now/create-request.html
+++ b/swh/web/templates/add_forge_now/create-request.html
@@ -85,7 +85,7 @@
- Remote URL of the forge to list.
+ Remote URL of the forge.
@@ -95,7 +95,7 @@
- Name of the Forge administrator.
+ Name of the forge administrator.
@@ -146,11 +146,11 @@
- Once a add request has been submitted, you can follow its current status in
+ Once an add-forge-request is submitted, its status can be viewed 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).
+ submitted requests list. This process involves a moderator approval and
+ might take a few days to handle (it primarily depends on the response
+ time from the forge).
{% endif %}
@@ -168,11 +168,12 @@
-
Prior to submit an "Add forge now" request, we ask
- you to fill in the following parameters:
+
+ For submitting an "Add forge now" request", you have to provide the following details:
+
-
Forge type: the type of supported forge the software archive is able to list.
- Currently, the supported types are:
+
Forge type:Type of the forge you would like to add.
+ Supported forge types in software heritage currently are:
Forge url: the url of the selected forge. This must be unique.
+
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 name:Contact name of the forge administrator
-
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.
+
Forge contact email:Contact email of the forge administrator. An email
+ will be sent to the given address to notify about the request.
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
@@ -198,57 +197,55 @@
their request to the add-forge-now moderator.
-
Once submitted, your "add forge" request can either be:
+
Once submitted, your "add forge" request can be in one
+ of the following states
Pending:
- the request was submitted and is waiting for a moderator
- to check its validity.
+ The request was submitted and is waiting for a moderator
+ to validate
Waiting for feedback:
- the request was processed by a moderator
- and the forge was contacted, the request is waiting for feedback from the
+ The request was processed by a moderator
+ and the forge was contacted, the request is waiting for the feedback from the
forge.
Feedback to handle:
- the forge has responded to the request and
- there is feedback to handle for the request.
-
+ 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
+ The request has been accepted and is waiting to be
scheduled.
Scheduled:
- the request has been scheduled is considered
- done.
+ The requested forge has been scheduled to ingest data
First listing done:
- The first listing of the forge is
- completed.
+ The first listing of the requested forge has been completed
First origin loaded:
- The first origin or repository processed by
- loader and archived (using a search query).
+ The first origin or repository from the requested forge has been loaded and archived (using a search query).
-
Rejected: the request is not a valid request and is rejected by a
+
Rejected:the request is not a valid one and is rejected by a
Software Heritage moderator.
-
Denied: the forge has requested not to archive the forge.
+
Denied:the forge has requested not to archive it.
-
Suspended: the request is for a forge with a non supported
+
Suspended:the request is for a forge with a non supported
VCS.