@@ -101,7 +101,7 @@ GitLab EE requires an active license key.
GitLab team members can follow [these instructions](/handbook/support/internal-support/#gitlab-plan-or-license-for-team-members) to acquire or renew a license.
Wider community members should contact the [Contributor Success team](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows#contributing-to-the-gitlab-enterprise-edition-ee).
Wider community members should contact the [Developer Relations Engineering team](/handbook/marketing/developer-relations/engineering/community-contributors-workflows#contributing-to-the-gitlab-enterprise-edition-ee).
### Ruby Gems
@@ -111,13 +111,13 @@ Follow the [development guidelines for Ruby gems](https://docs.gitlab.com/ee/dev
- Become a [Merge Request Coach](/job-families/expert/merge-request-coach/)
- Join the [Community Discord](https://discord.gg/gitlab)
- Encourage teams to host [Community Office Hours](/handbook/marketing/developer-relations/contributor-success/#community-office-hours)
- Reach out to the [Contributor Success team](/handbook/marketing/developer-relations/contributor-success) on Slack in `#contributor-success`
- Encourage teams to host [Community Office Hours](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#community-office-hours)
- Reach out to the [Developer Relations Engineering team](/handbook/marketing/developer-relations/engineering) on Slack in `#developer-relations-engineering`
- Involve the community in things you do
- Have conversations in public
- Triage team issues and label with `quick win` where applicable, especially in advance of [Hackathons](https://about.gitlab.com/community/hackathon/)
- Use the [Community Forks](https://gitlab.com/gitlab-community)
- Consider [live streaming](/handbook/marketing/marketing-operations/youtube/#public-or-private-streaming) and [pairing sessions](/handbook/marketing/developer-relations/contributor-success/community-pairing-sessions/), with team members and/or the community
- Consider [live streaming](/handbook/marketing/marketing-operations/youtube/#public-or-private-streaming) and [pairing sessions](/handbook/marketing/developer-relations/engineering/community-pairing-sessions/), with team members and/or the community
- Record meetings for the [GitLab Unfiltered](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) YouTube channel (handbook info [here](/handbook/marketing/marketing-operations/youtube/))
- Champion requests from community members and raise concerns internally
- Reach out offline to connect with community members on channels like X/Twitter or LinkedIn
@@ -51,4 +51,4 @@ Because we have a wide range of domains to cover, it requires a lot of different
At GitLab our goal is that [everyone can contribute](/handbook/company/mission/#contribute-to-gitlab-application). This applies to GitLab team members and the wider community through community contributions. We welcome contributions to any and all features, but recognize that first time contributors may prefer to start with smaller features. To support this we maintain a list of `quick wins` that may be more suitable for first time contributors, and contributors new to the domains in Software Supply Chain Security.
If the contributor needs an EE license, we can point towards the [Contributing to the GitLab Enterprise Edition (EE)](/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributing-to-the-gitlab-enterprise-edition-ee) section on the Community contributors workflows page.
If the contributor needs an EE license, we can point towards the [Contributing to the GitLab Enterprise Edition (EE)](/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#contributing-to-the-gitlab-enterprise-edition-ee) section on the Community contributors workflows page.
