Update co-create contacts and email

| Program | Overview | Website |  Email Address | DRI

|-----------|-----------|-----------|-----------|-----

| Co-Create| [Handbook](/handbook/marketing/developer-relations/programs/cocreate/) | [Website](https://about.gitlab.com/community/co-create/)  | `contributors@gitlab.com` | [@ashleysezer](https://gitlab.com/ashleysezer)

| Co-Create| [Handbook](/handbook/marketing/developer-relations/programs/cocreate/) | [Website](https://about.gitlab.com/community/co-create/)  | `co-create@gitlab.com` | [@ihuerga](https://gitlab.com/ihuerga)

|Notable Contributors|  | [Website](https://contributors.gitlab.com/docs/notable-contributors) | `contributors@gitlab.com` | [@ihuerga](https://gitlab.com/ihuerga)

## Non Developer Relations programs

1. **Technical Enablement Workshop**: Interactive session to help customers set up GitLab Development Kit (GDK) and understand GitLab's architecture

1. **On-Site Engineering Support**: One GitLab engineer co-located for one week to kick off co-creation through pair programming, with the goal of completing at least one merge request

1. **Legal Support**: Assistance with Corporate Contributor Agreements and open source policies

1. **Ongoing Mentorship**: Dedicated support from the Contributor Success team for long-term contribution success

1. **Ongoing Mentorship**: Dedicated support from the Co-Create and Community Engineering team for long-term contribution success

## Program goals

## Roles & Responsibilities

### Co-Create Program Manager

### Co-Create Strategy Lead

1. End-to-end program coordination and execution

1. Customer communication and expectation management

1. Continuous program improvement

1. Issue resolution and escalation management

**DRI**: Wesley De Vrient @wdevrient-ext

**DRI**: Isa Huerga @ihuerga

### Account Team (AE/SA/CSM/As)

1. Identify opportunities for expanded Co-Create participation (additional teams, follow-on contributions)

1. Identify business expansion opportunities (additional use cases, feature adoption, seat growth)

### Contributor Success

### Co-Create and Community Engineering

1. Conduct technical enablement workshops (GDK setup, architecture overview)

1. Ongoing mentorship for contributors

1. [Customer-Facing Doc](https://docs.google.com/document/d/1-abN7qF2Gd_XX9oaigNbFlEvvua1_YdZCXdrJ_6RFcM)

1. [Program Training Recording](https://gitlab.zoom.us/rec/share/300tNBVE4R72losqQjoPAReWF5jc2NGLK_p2AswfmxHprPqdWqdY3WR4ywYsyYWl.s3Gw-ExF4sMa5EZa?startTime=1738092078000&pwd=kqmKPNHsLP5k4TB2FeQK3ReIY6ybyD1l) (Internal only)

1. [Internal Training Deck](https://docs.google.com/presentation/d/13x7xZA_3L7EVpMb5t3hwdr1090mnBIOP5zhHUNSexEg/edit#slide=id.g273d5139f36_0_0) (Internal only)

1. Slack: `#devrel-cocreate-program`

1. Slack: `#co-create-and-community-engineering`

### For Customers

**For program-related questions and GitLab internal inquiries:**

- **Slack**: `#devrel-cocreate-program` - General channel for program questions, candidate identification, and internal coordination

- **Slack**: `#co-create-and-community-engineering` - General channel for program questions, candidate identification, and internal coordination

**For active customer engagements:**

- **Dedicated Slack Channel**: Created for each engagement with format `#cocreate-initiative-CUSTOMERNAME`

- **Dedicated Slack Channel**: Created for each engagement with format `#cocreate-CUSTOMERNAME`

- Includes: Customer team, Account team (CSM, SA, AE), Program Manager, Technical Lead, and GitLab Engineer

**For customers and community:**

- **Email**: contributors@gitlab.com

- **Email**: co-create@gitlab.com

- **Community**: [GitLab Community Discord](https://discord.gg/gitlab)

#### Team Contacts

1. **Program Manager**: Ashley Sezer - @asezer

1. **Co-Create Strategy Lead**: Isa Huerga Ayza - @ihuerga

1. **Technical Lead**: Raimund Hook - @stingrayza

1. **Manager, Developer Relations Programs**: Isa Huerga Ayza - @ihuerga

1. **Director, Contributor Success**: Nick Veenhof - @nick_vh

1. **Engineering Coordinator**: Shekhar Patnaik - @shekharpatnaik

1. **General Inquiries**: contributors@gitlab.com

1. **Demand Generation and Advocacy**: Rachel Lurie - @rlurie

1. **Field Lead**: Jess Perry - @jperry

1. **General Inquiries**: co-create@gitlab.com

## Playbook

##### Post-Engagement

1. Schedule testimonial interview within 2 weeks

1. Connect customer to Contributor Success for ongoing support

1. Connect customer to Co-Create and Community Engineering for ongoing support

1. Work with Product Marketing on case study

1. Document lessons learned

1. Plan quarterly follow-up

##### Running the Update Pipeline

1. Navigate to [Contributor Success Toolbox Pipelines](https://gitlab.com/gitlab-org/developer-relations/contributor-success/toolbox/-/pipelines/new)

1. Navigate to [DevRel Engineering Toolbox Pipelines](https://gitlab.com/gitlab-org/developer-relations/contributor-success/toolbox/-/pipelines/new)

1. Click "Run pipeline"

1. Add the following variables:

   - `CO_CREATE_TRACKER = 1`

- Check the issue labels for stage/group hints (e.g., `~devops::package`, `~group::pipeline authoring`)

- Ask in `#product` Slack channel

- Reach out to Contributor Success team for guidance

- Reach out to Co-Create and Community Engineering team for guidance

##### Step 2: Assess Issue Readiness

| Situation | Channel |

| --------- | ------- |

| Customer-specific channel already exists | `#cocreate-initiative-[customer]` - tag the PM there |

| No customer channel yet | `#cocreate-initiative` - start the conversation there |

| Customer-specific channel already exists | `#cocreate-[customer]` - tag the PM there |

| No customer channel yet | `#co-create-and-community-engineering` - start the conversation there |

This keeps context visible to the account team and avoids fragmented conversations.

1. **First**: Reach out to the relevant Engineering Manager for the group

2. **Second**: Contact the Group Product Manager (PM's manager)

3. **Third**: Raise in `#cocreate-initiative` for Contributor Success leadership guidance

3. **Third**: Raise in `#co-create-and-community-engineering` for Co-Create and Community Engineering leadership guidance

**When NOT to Escalate**

#### Step 3: Facilitate Connection

1. Direct customer to [application form](https://about.gitlab.com/community/co-create/#form)

1. Create Slack channel: `#cocreate-initiative-CUSTOMERNAME`

1. Invite: CSM, SA, AE, @wdevrient-ext, @stingrayza

1. Create Slack channel: `#cocreate-CUSTOMERNAME`

1. Invite: CSM, SA, AE, @ihuerga, @stingrayza

1. Schedule discovery call with customer stakeholders

### For Engineering: On-Site Best Practices

**Q: What exactly does Co-Create involve?**

A: GitLab sends one engineer to your site for one week to pair-program with your team on a contribution to GitLab. Before that, we run a virtual workshop to set up the [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit) and walk through the architecture. Afterward, the Contributor Success team provides ongoing mentorship as your merge requests move through review.

A: GitLab sends one engineer to your site for one week to pair-program with your team on a contribution to GitLab. Before that, we run a virtual workshop to set up the [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit) and walk through the architecture. Afterward, the Co-Create and Community Engineering team provides ongoing mentorship as your merge requests move through review.

**Q: Is this a consulting engagement? Do we pay for it?**

**Q: What happens after the week is over?**

A: Merge requests go through GitLab's standard review process. The Contributor Success team provides ongoing support through that cycle. Many customers continue contributing independently afterward. We also connect your team to the [GitLab Community Discord](https://discord.gg/gitlab) for broader community support.

A: Merge requests go through GitLab's standard review process. The Co-Create and Community Engineering team provides ongoing support through that cycle. Many customers continue contributing independently afterward. We also connect your team to the [GitLab Community Discord](https://discord.gg/gitlab) for broader community support.

**Q: Who maintains what we build?**

**Q: What if the customer wants to continue contributing after the on-site week?**

A: Excellent! Connect them with Contributor Success team for ongoing mentorship. Many customers become long-term contributors.

A: Excellent! Connect them with Co-Create and Community Engineering team for ongoing mentorship. Many customers become long-term contributors.