Rename Contributor Success and Strategy Programs team names in marketing pages

### Monday through Tuesday of release week

- **Contributor Success** team:

- **Developer Relations Engineering** team:

  - Adds the [Notable Contributor](#notable-contributor)

  - Verifies the [contributions total](https://10az.online.tableau.com/#/site/gitlab/views/WiderCommunityPIsPart1/MergedMRsperMilestonebasedondate) in the wider community thank you note

- **Release Post Manager and Technical Writer** perform final reviews

### Notable Contributor

The Contributor Success team owns the process for nominating, selecting and adding the GitLab Notable Contributor (formerly MVP) for the release post. See the Contributor Success [GitLab Notable Contributor Selection Process](/handbook/marketing/developer-relations/engineering/notable-contributor-process/).

The Developer Relations Engineering team owns the process for nominating, selecting and adding the GitLab Notable Contributor (formerly MVP) for the release post. See the Developer Relations Engineering [GitLab Notable Contributor Selection Process](/handbook/marketing/developer-relations/engineering/notable-contributor-process/).

The Release Post Manager no longer has any Notable Contributor related tasks.

#### Process

Once an issue with a community bonus label is closed, it appears on [a triage report](https://gitlab.com/gitlab-org/developer-relations/contributor-success/team-task/-/issues/960). A Contributor Success team member will:

Once an issue with a community bonus label is closed, it appears on [a triage report](https://gitlab.com/gitlab-org/developer-relations/contributor-success/team-task/-/issues/960). A Developer Relations Engineering team member will:

##### Verify the contribution

- **Adapt your teaching style**: Some learn best by doing, others by explanation - be flexible

- **Regular check-ins**: Ensure everyone feels included and that progress is on track

- **Plan for future contributions**: Schedule a discussion about continued contribution plans on the second-to-last day of the on-site

- **Build personal connections**: Consider opportunities for informal interaction outside of work hours, such as team dinners or local activities, which can strengthen relationships and collaboration (these can be expensed - check with the Contributor Success team)

- **Build personal connections**: Consider opportunities for informal interaction outside of work hours, such as team dinners or local activities, which can strengthen relationships and collaboration (these can be expensed - check with the Developer Relations Engineering team)

## Managing Common Challenges

- **Co-Create Project Manager**: Available for process questions, scheduling, and escalations

- **Product Managers**: For feature alignment and roadmap questions

- **Engineering Managers**: For technical architecture and code review guidance

- **Contributor Success Team**: For community and ongoing support questions

- **Developer Relations Engineering Team**: For community and ongoing support questions

### For Customers

### Program health metrics (KPIs)

The Strategy Programs team tracks the health of the GitLab for Education program through these metrics:

The Developer Relations Programs team tracks the health of the GitLab for Education program through these metrics:

1. Monthly active education institutions (active = 1 active user)

1. Monthly active education users (active = ping received)

### Team

Strategy Programs team lead: [@ihuerga](https://gitlab.com/ihuerga)

Developer Relations Programs team lead: [@ihuerga](https://gitlab.com/ihuerga)

GitLab for Education program DRI: [@rburns](https://gitlab.com/rodburns-gitlab)

* Promote awareness and expand reach with outreach campaigns

* Nurture program members through onboarding, engagement, and feedback collection

* Direct sales-assisted inquiries

* Pipeline members into other Strategy Programs

* Pipeline members into other Developer Relations Programs

* Create compelling case studies with universities and GitLab advocates

* Collaborate cross-functionally with GitLab teams and dependencies to ensure program operations and growth efforts

* Program operations

* Email: `education@gitlab.com`

  * Automatically opens a new confidential issue in GitLab Service Desk

  * Issues are triaged by the Strategy Programs team

  * Issues are triaged by the Developer Relations Programs team

  * Response time SLO: 3 business days

**For technical support** (license activation, setup, platform issues):

### Support

The Strategy Programs team uses GitLab issues and labels to manage all education programs support:

The Developer Relations Programs team uses GitLab issues and labels to manage all education programs support:

* Issues are [triaged on GitLab](https://gitlab.com/gitlab-com/marketing/developer-relations/meta/-/issues/61) using GLQL views

* All GitLab for Education Program issues are labeled and tracked with new inquiries and updated replies

We typically allocate this budget for local and regional community-driven events that GitLab's corporate events and field marketing teams have not already agreed to sponsor and staff.

We prefer to sponsor events at which multiple open source projects and communities are present.

The open source program team tracks event participation in the [Strategy Programs project on GitLab](https://gitlab.com/groups/gitlab-org/developer-relations/strategy-programs/-/epic_boards/2073660?label_name[]=Events&label_name[]=Strategy%20Programs%3A%3AGitLab%20for%20Open%20Source).

The open source program team tracks event participation in the [Developer Relations Programs project on GitLab](https://gitlab.com/groups/gitlab-org/developer-relations/strategy-programs/-/epic_boards/2073660?label_name[]=Events&label_name[]=Strategy%20Programs%3A%3AGitLab%20for%20Open%20Source).

To suggest an open source event sponsorship, open an issue in this project and use the `event` issue template to file your request.

Event organizers and consortium leads working with GitLab will find GitLab's brand-related assets (such as logo files, press release boilerplate, and trademark information) in [GitLab's press kit](https://about.gitlab.com/press/press-kit/).