Create community program section in docs

doc/subscriptions/index.md

@@ -12,8 +12,8 @@ have access to. Subscriptions are valid for 12 months.
 
 GitLab provides special subscriptions to participants in:
 
-- [Education](#gitlab-for-education-subscriptions)
-- [Open Source](#gitlab-for-open-source-subscriptions)
+- [Education](#gitlab-for-education)
+- [Open Source](#gitlab-for-open-source)
 
 ## Choose a GitLab subscription
 
@@ -68,7 +68,7 @@ click D "./gitlab_com/index.html#view-your-gitlabcom-subscription"
 click E "./self_managed/index.html#view-your-subscription"
 ```
 
-## Customers portal
+## Customers Portal
 
 With the [Customers Portal](https://customers.gitlab.com/) you can:
 
@@ -165,20 +165,102 @@ To change the password for this customers portal account:
 1. Make the required changes to the **Your password** section.
 1. Click **Save changes**.
 
-## GitLab for Education subscriptions
+## Community program subscriptions 
 
-The GitLab Education license can only be used for instructional-use or
+### GitLab for Education
+
+For qualifying non-profit educational institutions, the [GitLab for Education](https://about.gitlab.com/solutions/education/) program provides 
+the top GitLab tier, plus 50,000 CI minutes per month. 
+
+The GitLab for Education license can only be used for instructional-use or
 non-commercial academic research.
 
-Find more information how to apply and renew at
+Find more information on how to apply and renew at
 [GitLab for Education](https://about.gitlab.com/solutions/education/).
 
-## GitLab for Open Source subscriptions
+### GitLab for Open Source
+
+For qualifying open source projects, the [GitLab for Open Source](https://about.gitlab.com/solutions/open-source/) program provides 
+the top GitLab tier, plus 50,000 CI minutes per month. 
+
+You can find more information about the [program requirements](https://about.gitlab.com/solutions/open-source/join/#requirements),
+[renewals](https://about.gitlab.com/solutions/open-source/join/$renewals),
+and benefits on the [GitLab for Open Source application page](https://about.gitlab.com/solutions/open-source/join/).
 
-All [GitLab for Open Source](https://about.gitlab.com/solutions/open-source/)
-requests, including subscription renewals, must be made by using the application process.
 If you have any questions, send an email to `opensource@gitlab.com` for assistance.
 
+#### Verification for Open Source program
+
+As part of the [application verification process](https://about.gitlab.com/solutions/open-source/join/), you must upload three screenshots.
+These screenshots are needed to qualify you for the GitLab for Open Source program.
+
+- [OSI-approved license overview](#license-overview)
+- [OSI-approved license file](#license-file)
+- [Publicly visible settings](#publicly-visible-settings)
+
+##### OSI-approved license
+
+You must apply an [OSI-approved license](https://opensource.org/licenses/) to each project in your group before you can be verified.
+
+Add the license to the LICENSE file so that it shows up in the overview section of the project. This allows contributors to see it at a glance.
+
+It's best to copy and paste the entire license into the file in its original form. GitLab defaults to **All rights reserved** if no license file is mentioned.
+You must ensure that you add the correct license to each project within your group.
+
+After you ensure that you are using OSI-approved licenses for your projects, you can take your screenshots.
+
+###### License overview
+
+Go to **Project Overview > Details**. Take a screenshot that includes a view of the license you've chosen for your project.
+
+![License overview](img/license-overview.png)
+
+###### License file
+
+Navigate to one of the license files that you uploaded. You can usually find the license file by selecting **Project Overview > Details** and scanning the page for the license.
+Make sure the screenshot includes the title of the license.
+
+![License file](img/license-file.png)
+
+##### Publicly visible settings
+
+The goal of the GitLab for Open Source program is to enable collaboration on open source projects.
+As a pre-condition to collaboration, people must be able to view the open source project.
+As a result, we ask that all projects under this license are publicly visible.
+
+Follow these instructions to take a screenshot of the publicly visible settings:
+
+ 1. Go to your project and select **Settings**. 
+ 1. Expand **Visibility, project features, permissions**.
+ 1. Set **Project Visibility** to **Public**.
+ 1. Ensure others can request access by selecting the **Users can request access** checkbox.
+ 1. Take the screenshot. Include as much of the publicly visible settings as possible. Make sure to include your project's name in the
+    upper-left of the screenshot.
+
+![Publicly visible setting](img/publicly-visible.png)
+
+NOTE:
+From time to time, GitLab allows exceptions. One or two projects within a group can be private if there is a legitimate need for it, for example,
+if a project holds sensitive data. Email `opensource@gitlab.com` with details of your use case to request written permission for exceptions. 
+
+### GitLab for Startups
+
+For qualifying startups, the [GitLab for Startups](https://about.gitlab.com/solutions/startups/) program provides 
+the top GitLab tier, plus 50,000 CI minutes per month for 12 months. 
+
+For more information, including program requirements, see the [Startup program's landing page](https://about.gitlab.com/solutions/startups/). 
+
+Send all questions and requests related to the GitLab for Startups program to `startups@gitlab.com`.
+
+### Support for Community Programs
+
+Because these Community Programs are free of cost, regular Priority Support is not included. However, it can be purchased at a 95% discount in some cases.
+If interested, email the relevant community program team: `education@gitlab.com`, `opensource@gitlab.com`, or `startups@gitlab.com`.
+
+As a community member, you can follow this diagram to find support: 
+
+![Support diagram](img/support-diagram.png)
+
 ## Contact Support
 
 Learn more about: