Background
Now that @ry has acquired a “Gold” license for MergeTB’s hosted GitLab, we need to revisit our approach to leveraging GitLab for MergeTB.
While we did get the gold license for free because we are open source and “educational”, it does have membership quotas:
- Only 20 non-guest members are allowed with our current license agreement
- Guest members are not metered
Note in this context, the following terms apply:
Term | Meaning |
---|---|
member |
A logged in user who has been added as a team or project member for a team or project within the “MergeTB” GitLab team. |
guest member |
A member who has been added to a MergeTB team or project as in a GitLab guest role |
non-guest member |
A member who has been added to a MergeTB team or project in a role with higher permissions than guest , e.g. developer etc. |
Further background reading:
Agenda
Things to figure out.
This is a living document, so feel free to add to this wishlist.
Git workflow choices
Do we stick with the current workflow, which is essentially a “Feature branch workflow” ?
Or do we move to a “Forking workflow (aka fork&pull)” ?
Aside from questions of how to handle our own “source” material, we should also consider the concerns raised in the Keeping up with upstream projects topic.
Git pipeline choices
Multi-project pipelining
One of the reasons that the gold license was requested, was to get better support for mulit-project ci/cd pipelines.
Are there any existing projects which could benefit from this?
Merge trains
Are there any existing projects which could benefit from this?
Project management
Group or team level issues
Currently issues are only maintained at individual project levels.
There is a need for cross-project issues for concerns that cross individual project scopes.
Are there any gitlab features in gold that would help with this? And how do we want to use them?