Draft: Add question about what to do when there are major changes at a forge

Asked-in: https://archive.softwareheritage.org/admin/add-forge/request/155/

Jenkins job DDOC/builds #463 succeeded .
See Console Output and Coverage Report for more details.

approved this merge request

@ardumont @bchauvet this is not ready yet, because I noticed that resubmitting a forge using the same URL and a different forge type is blocked with Request for forge already exists (id 240) when the forge was already added via Add Forge Now. So this MR will need to wait for a fix for that issue, or the process for submitting forge updates will need to be rethought.

Ok.

It's probably a unicity constraint check solely put on the (forge) url and not the (forge) url and the (forge) type. But yes, that'd need to be thought over whether we want that or not.

Indeed we will have to bring more flexibility to the add forge now moderator dashnoard for this kind of use cases. By the time we design and implement efficient changes, we will change the origin url for afn #240, setting it to https://git.exim.org/swh-amended. @guillaume is working on it. I'll add a comment to explain this in the request dashboard when it's done

assigned to @guillaume

unassigned @guillaume

Done.

swh-web=*> select * from add_forge_request where id = 240;
-[ RECORD 1 ]--------------+-------------------------------------------------------------------------
id                         | 240
status                     | REJECTED
submission_date            | 2023-10-23 13:28:51.648041+00
submitter_name             | pabs
submitter_email            | pabs3@bonedaddy.net
forge_type                 | bitbucket
forge_url                  | https://git.exim.org/swh-amended
forge_contact_email        | hs@schlittermann.de
forge_contact_name         | Heiko Schlittermann (HS12-RIPE)
forge_contact_comment      | Full contact list: Heiko Schlittermann (HS12-RIPE) <hs@schlittermann.de>
submitter_forward_username | f
last_moderator             | pabs
last_modified_date         | 2023-10-24 00:09:09.833753+00

@pabs you can recreate the request with the right forge type.

Jenkins job DDOC/builds #464 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #465 succeeded .
See Console Output and Coverage Report for more details.

what is the status of this MR?

My take is that it should be merged, hence why i accepted it.

Has the website been fixed to allow (instead of reject) what the proposed FAQ item suggests?

added 25 commits

• af5342f8...5b452862 - 24 commits from branch swh/devel:master
• 8d3aac44 - Add question about what to do when there are major changes at a forge

Compare with previous version

Jenkins job DDOC/builds #541 succeeded .
See Console Output and Coverage Report for more details.

added 3 commits

• 8d3aac44...f8891cb9 - 2 commits from branch swh/devel:master
• b358c3d2 - Add question about what to do when there are major changes at a forge

Compare with previous version

Jenkins job DDOC/builds #545 succeeded .
See Console Output and Coverage Report for more details.

merged

@lunar I don't think this was ready to merge, because the nessecary changes in the SWH web app haven't been made yet.

I was trying to clean up lingering MRs. Please tag requests that are not ready as drafts next time. I'll revert this.

marked this merge request as draft