diff --git a/swh/web/templates/add_forge_now/create-request.html b/swh/web/templates/add_forge_now/create-request.html index 659e8e11..81a360b2 100644 --- a/swh/web/templates/add_forge_now/create-request.html +++ b/swh/web/templates/add_forge_now/create-request.html @@ -1,234 +1,256 @@ {% extends "../layout.html" %} {% comment %} Copyright (C) 2022 The Software Heritage developers See the AUTHORS file at the top-level directory of this distribution License: GNU Affero General Public License version 3, or any later version See top-level LICENSE file for more information {% endcomment %} {% load render_bundle from webpack_loader %} {% load static %} {% block header %} {% render_bundle 'add_forge' %} {% endblock %} {% block title %} Add forge now – Software Heritage archive {% endblock %} {% block navbar-content %}

Request the addition of a forge into the archive

{% endblock %} {% block content %}

“Add forge now” provides a service for Software Heritage users to save a complete forge in the Software Heritage archive by requesting the addition of the forge URL into the list of regularly visited forges. {% if not user.is_authenticated %}

You can submit an “Add forge now” request only when you are authenticated, please login to submit the request.

{% endif %}

{% if not user.is_authenticated %}

You must be logged in to submit an add forge request. Please log in

{% else %}
{% csrf_token %}
Supported forge types in software archive.
Remote URL of the forge to list.
Name of the Forge administrator.
Email of the forge administrator. The given email address will not be used for any purpose outside the “add forge now” process.
Optionally, leave a comment to the moderator regarding your request.

-
-
- -
-
-

- 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). +

{% endif %}
Submission date Forge type Forge URL Status
+
+

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.
    • +
+
-
{% endblock %}