clearly communicate features destination for gitlab.com plan levels

Description

Community needs more clear understanding of how CE/EES/EEP licensing relates to gitlab.com licensing levels. Clearly many users, myself included, are evaluating how all of the recent licensing changes affect them, their teams, and their future development tooling and it's hard to pin-point what will land in which gitlab.com plan where it's very clear which Product version features are headed. Example #928 (closed) - I'm still not clear on which plan this will be associated to and will weigh heavily on my decision to stay with gitlab or not.

Proposal

Either have a clear association between CE/EES/EEP and Free/Bronze/Silver/Gold gitlab.com plans or add explicit labels to features for which plan a feature will be associated to.

There is a direct mapping between versions, but I agree we can do a better job communicating that @jamemackson.

• EES => Bronze
• EEP => Silver
• EEU (future) => Gold

We're discussing other ways of making this more clear.

added Product work label

removed Product work label

@mydigitalself : is there some ongoing marketing work to address this? I was wondering why this page doesn't list CE/EES/EEP: https://about.gitlab.com/gitlab-com/

@victorwu because not ALL features of EEP are available on GitLab.com, because you don't have server/admin access.

Exactly what @JobV said. There's a conceptual difference between running your own instance and using GitLab.com - you don't have access to some of the server-wide admin capabilities or settings this includes some features, for instance, the ability to connect the server to an LDAP server.

All of the .com features are listed on https://about.gitlab.com/gitlab-com/ including a comparison of the features in the table below the plans.

We initially had listed the plans mapping to CE/EES/EEP, but that caused confusion because of the fact that there are some features not available as per my comment above.

@mydigitalself : If you think communicating the mapping is confusing / not helpful, I don't think we should use it ourselves either. So when communicating with the community, should we simply link to https://about.gitlab.com/gitlab-com/ ?

And as for at least our own internal planning, or on the about.gitlab.com website, should we have a table somewhere that basically extracts from features.yml, and it would be something like:

Feature	Self-hosted Versions (CE/EES/EEP)	GitLab.com Plans
One issue board per project	CE, EES, EEP	Free, Bronze, Silver, Gold
Group issue boards	EEP	Silver, Gold
Related issues	EES, EEP	Bronze, Silver, Gold
...	...	...

For non-admin features, the mapping would be implicit, and then you can easily call out the admin features as not following the mapping.