Hi Team Emacsen! Which of the following approaches do you think is the best way to enable new contributors to update a package's upstream version on salsa? 1. New contributor files MR using gbp+pristine-tar style. Existing team member reviews the MR, but also has to manually add the remote from the personal namespace of the contributor in order to gain access to the upstream/$version tag (created by gbp import-orig), which is then manually pushed to salsa. 2. New contributor adds upstream-vcs remote, merges upstream-created tag, files MR. Existing team member also adds upstream-vcs remote, using info from d/control, grabs the tag from there, and manually pushes it. 3. Give new contributor per-project full access (early) for specific repos. 4. Is there a class of permissions that allows contributors to push tags, but where existing branches remain "protected". If this exists, is it the best option? 5. The MR is just a site for discussion. After resolving any outstanding issues the contributor uploads the source package to mentors, an existing team member sponsors from mentors, and then uses "gbp import-dsc" or the dgit equivalent to integrate the updates into the git repo. I may have missed other options... Thank you in advance for taking the time to consider this, Regards, Nicholas
Attachment:
signature.asc
Description: PGP signature