CR Merge Requests for guest contributors
Step 2 of the current draft guidance gives the following:
Contributor creates and submits a merge request in the appropriate project on ETSI Forge
The submitted Merge Request shall include the changes uploaded to a branch in the repository with a given temporary name (the branch will be deleted after the merge)
This is a sensible process. But is it the case that people making CRs against published specifications generally won't have permissions to create new branches in the project that contains the specification?
Possible resolutions:
-
(My preferred) Amend the process description to include having the CR author forking the repo into their own private namespace and then submit an MR from that - I don't know if there are there any issues with permissions or visibility from this, and it also may mean that any CI/CD pipelines in the project aren't available to the contributor.
-
Enforce that CR contributors request access to the repository before making a CR - this could introduce an unintended barrier to contributions, and result in many people being members of the specification's project
Can we learn anything from the working practices of any of the existing projects on the Forge?