GitLab for Open Source Program Verification

1. You are here:
2. Handbook
3. Marketing
4. Developer Relations
5. Community Programs
6. Community Programs Applications Automated Workflows
7. GitLab for Open Source Program Verification

Maintained by:

On this page

• Overview
• Program application form
• Verifying applicants
• Verification limit

Overview

This page contains details regarding the process of verifying applications for GitLab for Open Source Program. Because the GitLab for Open Source Program is part of GitLab's Community Programs, team members verify applications by using the seven-step Community Programs Automation Workflow. See the handbook page on that workflow for details that pertain to all GitLab community programs.

Program application form

GitLab engages a third party, SheerID, to assist with processing program applications and verifying that applicants meet program requirements. Applicants must complete a SheerID form to apply for the GitLab for Open Source Program:

• Program application form

This SheerID form contains the following fields:

• First Name
• Last Name
• Email Address
• Country (drop down list)*
• Institution Name (drop down list)
• Open Source Organization or Project Name
• Project Description
• Publicly Visible Project on GitLab
• OSI Approved License
• Not Seeking Profile (checkbox)
• Marketing email opt-in (checkbox)

(*) Note: US Embargoed countries are not on the list. SheerID is not able to separate out the two different regions in Ukraine, so we have asked them to remove Ukraine entirely from the list of countries. Applicants from Ukraine will need to contact the team directly at opensource@gitlab.com, and team members determine whether they qualify based on their region of origin.

The SheerID form also includes the following statement, added with help from GitLab's legal team:

By submitting this form, you understand that your information will be shared with GitLab by SheerID and used for verification purposes.

`For more information please see the [GitLab's Privacy Policy](/privacy/).`

If you are accepted into the GitLab for Open Source Program, you will be subject to [GitLab's terms and conditions](/handbook/legal/opensource-agreement/). All use of GitLab products must comply with United States export control and economic sanction laws.

Verifying applicants

Eligibility requirements for the GitLab for Open Source Program are listed in the program's handbook page. SheerID assists GitLab with reviewing program applications and ensuring applicants meet these program requirements.

SheerID is not able to completely automate the Verification phase of the application workflow for the GitLab for Open Source Program. This means the program manager and team members must verify applications with some amount of manual effort. However, while unable to fully automate the Verification phase, SheerID is able to make the reviewing process easier by doing the following:

• Requesting screenshots to verify the project's publicly visible status and application of OSI-approved licenses
• Asking the applicant to check a box to certify they are not seeking profit with their project

When applicants submit forms to the GitLab for Open Source Program, those forms enter a review queue. Note that:

• Applications in the queue expire after 20 days
• The queue displays only the 20 most recently submitted applications; when processed, older applications become visible

Verification for the GitLab for Open Source Program will require an application processing team until further automation is implemented. The team plans to explore ways to more fully automate the application process of the program in the future.

Applicants have three attempts to upload a documentation verifying their eligibility for the GitLab for Open Source Program. Upon a third unsuccessful attempt, applicant will be rejected.

Members of GitLab's Community Programs team have trained to use SheerID to review these documents via the SheerID Review Portal according to the following process:

1. Login to MySheerID. Go to the "Document review" section.
2. Click "Begin" or click on any open application to view.
3. Verify license type: Make sure that an OSI approved license is being used by checking the screenshot against this OSI license list. If you find a match, check the box on the right about license type.
4. Verify public settings: make sure there is a screenshot showing that the project is publicly visible. If it is, click on the checkbox saying you've verified this.
5. Visit the applying namespace on GitLab to verify that all remaining projects in the namespace meet program requirements.
6. If all requested screenshots are present (see instructions for screenshots here), Approve the application. Click Hold if you need more time to decide, or Reject if they do not meet the criteria.

Reviewers should be sure to check different views in the "Review Documents" section. A drop-down field takes reveals applications "On Hold" and "Escalated."

Successfully verified applicants receive a welcome email containing a coupon code and instructions for activating their subscriptions. See the Community Applications Workflow for additional details on what follows.

If the GitLab review team is unable to determine the eligibility based on the screenshots that the applicant provided via the SheerID Review Portal, the GitLab review team will send a rejection email. The applicant can then choose to reach out to opensource@gitlab.com if they believe the rejection was sent in error, or if they have additional questions about eligibility.

To view the welcome and rejection emails that applicants receive, please see the Verification Simulation section below.

Verification limit

Any individual can apply through the form and attempt verification up to five times per 365-day period. This limit provides room for error and allows a single individual to apply for licenses on behalf of multiple open source projects. This limit is determined by GitLab and set by SheerID. It can be changed at any time.