Resolving Package and Plan Name Collisions
We have a challenge today where our package names (and repositories) align with the SKU's/plans that we sell. For example our open source package is Community Edition
and our free plan is also Community Edition
. This has worked in the past, but now we want most enterprises to use our open core Enterprise Edition
package even if they use the free license. This can cause confusion.
We have three main options:
- Leave everything as is, and simply attempt to document the behavior and steer people to EE package even if they want the CE plan.
- Rename the packages away from the editions, perhaps
gitlab
andgitlab-ce
but that still includes room for confusion. - Rename the pricing plans, and remove the Community/Enterprise delineation and instead focus on a single word for good/better/best. Perhaps: CE => Essentials, EES => Starter, EEP => Premium
Edited by Joshua Lambert