Proposal: create partner-specific groups, for extension forks or WIP extensions
Context:
- We want to encourage using
/extensions
as the canonical space for official CiviCRM extensions (either by automatic mirroring, or if folks use that as their main repo). - Some people want to be able to fork those extensions, so that they can later send a merge-request (if the extensions is managed on gitlab).
- Currently, people can fork to their personal space, but for most organizations, it would be more practical to have an organization space, so that they do not need to add all their team members/staff for each fork.
Proposition:
- Partners/members can request an org-space under
/partners/your-org
. - The canonical space for extensions should always be
/extensions
. Meaning that if an extension is in a partner-specific space, it is consider a work in progress (WIP), and cannot be considered for automatic release.
Conditions:
- Repositories hosted under
/partners
would have to be public repositories- Having private projects would push the boundaries of the 0$ Gitlab Ultimate license for Open Source projects, which is not for companies (who can afford to run their own Gitlab instance).
- We want to avoid having to host client-specific projects on lab.civicrm.org, which would increase the maintenance costs on the CiviCRM infrastructure.
Based on a discussion with Luciano/Vangelis (iXiam) and @MikeyMJCO