Received from NLnet today (not attaching the MoU as it contains private data, it will be redacted and published when final).
Hi Loïc,
Thanks still for the answers.
I cast your plan into our format (molding it a bit as we lack sub-subheadings etc.), and forged an MoU for you.
It is implied (in the ‘compliance testing’ task description), but not explicit, that you make each tooling feature work for (at least) Gitea/Forgejo and Gitlab. Correct? I added this line in the intro about tooling (which moved into the plan intro):
Each feature of the F3 tooling will work with Gitea, Forgejo, and Gitlab (to the extent each has the required features).In the code and documentation it will probably be helpful to be explicit about which versions of which forges the tool works with.
I also added descriptions to the tasks about down/uploading using internals, basing on your explanation. With internals, do you mean reading directly from the database, or using a (command-line) data export tool provided by the forge? (asking just for curiosity; it’s similar enough, and fine to leave it open in the task description.)
Please check if everything looks right, and if so add (a scan of) your signature. Then we’ll do the same and we are (officially) started.
(but also feel free to come back with further questions/suggestions)
Sent the following reply:
Hi,
Hi Loïc,
Thanks still for the answers.
I cast your plan into our format (molding it a bit as we lack sub-subheadings etc.), and forged an MoU for you.
It is implied (in the ‘compliance testing’ task description), but not explicit, that you make each tooling feature work for (at least) Gitea/Forgejo and Gitlab. Correct? I added this line in the intro about tooling (which moved into the plan intro):
Each feature of the F3 tooling will work with Gitea, Forgejo, and Gitlab (to the extent each has the required features).This is correct, thanks for adding this.
In the code and documentation it will probably be helpful to be explicit about which versions of which forges the tool works with.
The test pipelines will be pinned to specific versions of forges.
I also added descriptions to the tasks about down/uploading using internals, basing on your explanation. With internals, do you mean reading directly from the database, or using a (command-line) data export tool provided by the forge? (asking just for curiosity; it’s similar enough, and fine to leave it open in the task description.)
It could be reading directly from the database, but it is unlikely to be the case. The more general case is using function calls that are in the forge codebase but which are not exposed via a publicly available API. Either because the API endpoint is missing entirely. Or because the API endpoint does not accept some parameters (such as forcing the creation date of something).Please check if everything looks right, and if so add (a scan of) your signature. Then we’ll do the same and we are (officially) started.
Everything is correct. I’m grateful for the effort you made to format this into the MoU: it is a tedious task.I fixed a few minor typos and attached the modified document with revisions shown so you can quickly verify them.
I attach the signed MoU and I look forward to getting started as soon as possible.
Cheers