Process Definition - Creation of external Big Bang contribution process
Is your feature request related to a problem? Please describe.
Process definition requested by @nicolaschaillan.
There is currently no process (or ability on repo1) for external contributions to Big Bang repos. Only Platform One developers have ability to contribute to Big Bang projects.
As an external Platform One user of Big Bang, what is the workflow for contributing back to Big Bang repos?
- External developers should not have
developer
permissions on the repos - Creation of an SLA on response time by the Big Bang team and expectations on resolving feedback by external contributors
Describe the solution you'd like
An ideal solution would be ...
- External developer confirms with @joshwolf / @runyontr or the BB Package owner that the change is value added. External contributions should be attached to an gitlab issue.
- Repo1 admins updates external user's account to allow 3 personal projects (these are needed for a fork/merge process).
- An external contributor would fork the BB repo to their personal namespace, apply updates, and create an MR back to the upstream project.
- BB team reviews within one week.
- External review has one week to resolve issues.
Describe alternatives you've considered
- Grant those who want to contribute
developer
on the repo, but this is a security issue. - Process of forking and merging on github, but that seems overly complex merging between Repo1 and GitHub.
Additional context
A couple blockers right now.
- External users don't have ability to fork repos
- Big Bang CI would need to be updated for a subset of testing. Any pipelines on a fork will fail because regular and protected variables aren't available.