Commit b86ef246 authored by Nick Veenhof's avatar Nick Veenhof 💬
Browse files

Update Developer Relations strategy-programs references to programs (sales section)

parent 783bad20
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -25,7 +25,7 @@ description: "Operations, Procedures, Documentation"
- `#it_help`
- `#marketing_programs`
- `#marketing`
- `#community-programs`
- `#developer-relations-programs`

## Glossary

+4 −4
Original line number Diff line number Diff line
@@ -557,17 +557,17 @@ For assistance with a Subscription Transfer Agreement please open a Legal Reques

### Open Source, Education, and Startup Application Opportunities

GitLab provides free licenses to qualifying entities through the [Strategy Programs](/handbook/marketing/developer-relations/strategy-programs/): [GitLab for Education Program](https://about.gitlab.com/solutions/education/) and [GitLab for Open Source Program](https://about.gitlab.com/solutions/open-source/), as well as through the [GitLab for Startups Program](https://about.gitlab.com/solutions/startups/). All applications to these programs are routed through the [Strategy Programs applications automated workflows](/handbook/marketing/developer-relations/strategy-programs/program-resources/#automated-application-workflow). **Only Developer Relations team members** should handle these applications and opportunities because the team verifies program requirements before issuing/renewing licenses and these opportunities are handled differently since the opportunities are free.
GitLab provides free licenses to qualifying entities through the [Developer Relations Programs](/handbook/marketing/developer-relations/programs/): [GitLab for Education Program](https://about.gitlab.com/solutions/education/) and [GitLab for Open Source Program](https://about.gitlab.com/solutions/open-source/), as well as through the [GitLab for Startups Program](https://about.gitlab.com/solutions/startups/). All applications to these programs are routed through the [Developer Relations Programs applications automated workflows](/handbook/marketing/developer-relations/programs/program-resources/#automated-application-workflow). **Only Developer Relations team members** should handle these applications and opportunities because the team verifies program requirements before issuing/renewing licenses and these opportunities are handled differently since the opportunities are free.

#### Inquiry and Application Process (Leads or Contacts)

1. If an existing contact or new lead is interested in applying to one of the programs, use the resources in the [Strategy Programs](/handbook/marketing/developer-relations/strategy-programs/#active-programs) to guide them apropriately. If the lead has specific questions, direct them to send an email to `education@gitlab.com`, `startups@gitlab.com`, or `opensource@gitlab.com`. Then reassign the lead to the appropriate program manager (DRI).
1. If an existing contact or new lead is interested in applying to one of the programs, use the resources in the [Developer Relations Programs](/handbook/marketing/developer-relations/programs/#active-programs) to guide them apropriately. If the lead has specific questions, direct them to send an email to `education@gitlab.com`, `startups@gitlab.com`, or `opensource@gitlab.com`. Then reassign the lead to the appropriate program manager (DRI).
1. In the situation that you need direct assistance with the lead/contact, chatter the 'Community Program Owner' in Salesforce with a note about the requested action.

#### Assigning Opportunities and Renewal Opportunities

1. All opportunities related to a program should be owned by the Program Manager of the corresponding program as indicated in the [Strategy Programs](/handbook/marketing/developer-relations/strategy-programs/#active-programs) handbook.
1. If you need to assign an opportunity or a renewal opportunity please reach out to the #strategy-programs Slack channel.
1. All opportunities related to a program should be owned by the Program Manager of the corresponding program as indicated in the [Developer Relations Programs](/handbook/marketing/developer-relations/programs/#active-programs) handbook.
1. If you need to assign an opportunity or a renewal opportunity please reach out to the #developer-relations-programs Slack channel.

### **How to Submit a Quote for Discount and Payment Term Approval**

+1 −1
Original line number Diff line number Diff line
@@ -232,7 +232,7 @@ As it relates to retirement of quota, we will refer to the Closed Won date as we
| [Renewals Process Guide](/handbook/sales/sales-renewal-process/) | Field Operations | Handbook page outlining renewal process and policies |
| [Customer Renewal Tracking](/handbook/customer-success/csm/renewals/) | Technical Account Management |  Resource that outlines process for managing renewals as a part of the larger account team (with SAEs, CSMs, Customer Success) |
| [ISR Renewal Management](https://drive.google.com/drive/u/0/search?q=%22Renewal%20Oppty%20Management%22) | Shared doc | A shared document outlining the renewal management process for ISRs |
| [Community Education / EDU Program](/handbook/marketing/developer-relations/strategy-programs/education-program/) | Developer Relations | Resource that outlines The GitLab for Education Program which provides GitLab for free to students and faculty at educational institutions around the globe |
| [Community Education / EDU Program](/handbook/marketing/developer-relations/programs/education-program/) | Developer Relations | Resource that outlines The GitLab for Education Program which provides GitLab for free to students and faculty at educational institutions around the globe |

#### ISR Manager Resources

+14 −14
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ title: Collaborating with Community Programs
---

{{% alert title="Note" color="warning" %}}
The Community Programs team is now Strategy Programs. The information from the original session has been preserved but links have been updated.
The Community Programs team is now Developer Relations Programs. The information from the original session has been preserved but links have been updated.
{{% /alert %}}

## 🌎 Overview
@@ -27,7 +27,7 @@ A [recording of this session](https://youtu.be/B75IPB5L4yI) is available for on-

## 👋 Introduction

The Community Programs team supports communities that align with GitLab's CREDIT values by executing specific programs that help these communities grow and thrive. Our mission is to help these communities experience GitLab's vision of a world where everyone can contribute. Learn more about [Community Programs in the GitLab handbook](/handbook/marketing/developer-relations/strategy-programs).
The Community Programs team supports communities that align with GitLab's CREDIT values by executing specific programs that help these communities grow and thrive. Our mission is to help these communities experience GitLab's vision of a world where everyone can contribute. Learn more about [Community Programs in the GitLab handbook](/handbook/marketing/developer-relations/programs).

## ❓ What is a community program?

@@ -41,7 +41,7 @@ Through these programs, we seek to raise awareness of GitLab in specific markets

## 🔎 Meet the programs

Learn more about GitLab's community programs and their respective DRIs in the [Community Programs handbook pages](/handbook/marketing/developer-relations/strategy-programs/#active-programs).
Learn more about GitLab's community programs and their respective DRIs in the [Community Programs handbook pages](/handbook/marketing/developer-relations/programs/#active-programs).

## 📃 Rules of engagement

@@ -53,7 +53,7 @@ Please note that even if there is not a sales related opportunity on an account,

### Lead routing

If you are routed a lead that has contacted GitLab about a Strategy program (GitLab for Education or GitLab for Open Source), please reply directly to the lead to connect them with the appropriate program team. To know what email address customers can use to contact us, check the [Active Programs](/handbook/marketing/developer-relations/strategy-programs/#active-programs) information. Replying directly provides the optimal experience for the customer and the most efficient path for everyone.
If you are routed a lead that has contacted GitLab about a Strategy program (GitLab for Education or GitLab for Open Source), please reply directly to the lead to connect them with the appropriate program team. To know what email address customers can use to contact us, check the [Active Programs](/handbook/marketing/developer-relations/programs/#active-programs) information. Replying directly provides the optimal experience for the customer and the most efficient path for everyone.

Please do not forward leads or emails from individual program members to GitLab team members' individual email addresses. If you have any questions, please reach out to the "Community Program Owner" for that Salesforce account.

@@ -61,11 +61,11 @@ Please do not forward leads or emails from individual program members to GitLab

In Q3FY23, Community Programs launched an automated system which allows wider community members to apply, receive verification, and obtain new or renewed subscriptions directly through a specific portal on `gitlab.customers.com`. After successful verification, applicants will receive a coupon code to use in the Community Self-Checkout Portal.

Below are details on the application process most pertinent to Sales team members. To learn about the application and renewal process in its entirety, please see the [Community Programs Applications Automated Workflow](/handbook/marketing/developer-relations/strategy-programs/program-resources/#automated-application-workflow) handbook page.
Below are details on the application process most pertinent to Sales team members. To learn about the application and renewal process in its entirety, please see the [Community Programs Applications Automated Workflow](/handbook/marketing/developer-relations/programs/program-resources/#automated-application-workflow) handbook page.

### Application

The Community Programs team uses a third party vendor, [Proxi.id](https://www.proxi.id/), to host the application forms for its programs. More details are in the [Application](/handbook/marketing/developer-relations/strategy-programs/program-resources/#application) section of the Community Programs handbook page.
The Community Programs team uses a third party vendor, [Proxi.id](https://www.proxi.id/), to host the application forms for its programs. More details are in the [Application](/handbook/marketing/developer-relations/programs/program-resources/#application) section of the Community Programs handbook page.

NOTE:

@@ -73,21 +73,21 @@ If a customer applying to the GitLab for Education Program is having problems be

### Verification

Proxi.id provides automated verification for applications to the GitLab for Education Program. The Strategy Programs team reviews applications for the GitLab for Education and GitLab for Open Source programs. Additional details are in the [Verification](/handbook/marketing/developer-relations/strategy-programs/program-resources/#verification) section of the Strategy Programs handbook page.
Proxi.id provides automated verification for applications to the GitLab for Education Program. The Developer Relations Programs team reviews applications for the GitLab for Education and GitLab for Open Source programs. Additional details are in the [Verification](/handbook/marketing/developer-relations/programs/program-resources/#verification) section of the Developer Relations Programs handbook page.

Important points:

- For applications to the education program, the Community Programs team does not require proof of use case nor do we enforce it. The applying entity agrees to our legal terms—use case included—as described in the Education Program Agreement [Purpose section](/handbook/legal/education-agreement/#2-purpose).

- For applications to the open source program, the Community Programs team requires proof of use case at the time of application (new and renewing) in the form of a screenshot. The applying entity agrees to our legal terms—use case included—as described in the Open Source Program Agreement [2.Purpose & Eligibility Section](/handbook/legal/opensource-agreement/#2-purpose--eligibility). If a SAE/AE has concerns regarding potential violation of the use case, please contact our team in the #strategy-programs channel and provide the SFDC opportunity in question.
- For applications to the open source program, the Community Programs team requires proof of use case at the time of application (new and renewing) in the form of a screenshot. The applying entity agrees to our legal terms—use case included—as described in the Open Source Program Agreement [2.Purpose & Eligibility Section](/handbook/legal/opensource-agreement/#2-purpose--eligibility). If a SAE/AE has concerns regarding potential violation of the use case, please contact our team in the #developer-relations-programs channel and provide the SFDC opportunity in question.

- In the case that a community program member no longer meets the program requirements, the Community Programs team works with the sales team to identify a path forward to transition from free to paid.

### Booking

After successful verification, program members receive a coupon code, which members then use in the Community Programs self-checkout portal on CustomerDOT to obtain their subscription license or renew. Additional details are in the [Booking](/handbook/marketing/developer-relations/strategy-programs/program-resources/#booking) section of the Community Programs handbook page.
After successful verification, program members receive a coupon code, which members then use in the Community Programs self-checkout portal on CustomerDOT to obtain their subscription license or renew. Additional details are in the [Booking](/handbook/marketing/developer-relations/programs/program-resources/#booking) section of the Community Programs handbook page.

Add-ons or license-type changes cannot be made on through self-service. Program members need to [email the corresponding program](/handbook/marketing/developer-relations/strategy-programs/#active-programs) with the request.
Add-ons or license-type changes cannot be made on through self-service. Program members need to [email the corresponding program](/handbook/marketing/developer-relations/programs/#active-programs) with the request.

### Provisioning

@@ -101,7 +101,7 @@ Sales Support and Billing Ops handle compliance. This phase results in granting

Community program members need to renew their subscriptions annually.

Self-checkout renewal functionality on CustomerDOT launched in 2022-09. Program members use the same form for both new and renewing subscriptions. For renewal instructions please see the programs' respective [marketing pages](/handbook/marketing/developer-relations/strategy-programs/#active-programs). Additional details on the renewal process are in the [Renewal](/handbook/marketing/developer-relations/strategy-programs/program-resources/#renewal) section of the Community Programs handbook page.
Self-checkout renewal functionality on CustomerDOT launched in 2022-09. Program members use the same form for both new and renewing subscriptions. For renewal instructions please see the programs' respective [marketing pages](/handbook/marketing/developer-relations/programs/#active-programs). Additional details on the renewal process are in the [Renewal](/handbook/marketing/developer-relations/programs/program-resources/#renewal) section of the Community Programs handbook page.

Important points:

@@ -113,19 +113,19 @@ Important points:

### Support

Details on the Support workflow for Community Programs are in the [Support](/handbook/marketing/developer-relations/strategy-programs/program-resources/#common-issues) section of the Community Programs handbook page.
Details on the Support workflow for Community Programs are in the [Support](/handbook/marketing/developer-relations/programs/program-resources/#common-issues) section of the Community Programs handbook page.

Important points:

- Program members do not receive Ultimate support with subscriptions granted through community programs. They are able to open a support ticket via the [GitLab Support Portal](https://about.gitlab.com/support/#issues-with-billing-purchasing-subscriptions-or-licenses) with errors involving the Community Self-checkout Portal on CustomersDOT or any errors relating to their subscription.

- If GitLab for Education applicants are having issues during the application or verification stages, they should contact the corresponding team as indicated in the [Common Issues](/handbook/marketing/developer-relations/strategy-programs/program-resources/#common-issues) section.
- If GitLab for Education applicants are having issues during the application or verification stages, they should contact the corresponding team as indicated in the [Common Issues](/handbook/marketing/developer-relations/programs/program-resources/#common-issues) section.

## 🤝 Engaging with the Community Programs team

You can engage with our team asynchronously by:

- Using our Slack channel, `#strategy-programs`
- Using our Slack channel, `#developer-relations-programs`
- Tagging us in account-related conversations on Salesforce
- Using our Slack channel, `#gitlab-for-campuses` for questions regarding the [GitLab for Campuses](/handbook/sales/public-sector#gitlab-for-campuses) paid offering.