|
| 1 | +# GitHub Sponsorship Program |
| 2 | + |
| 3 | +Thank you for your contributions to the OWASP Nest project! This document outlines how to set up GitHub Sponsors on your personal account as the first step toward participating in our Sponsorship Program. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## Phase 1 — Set Up GitHub Sponsors on Your Personal Account |
| 8 | + |
| 9 | +> [!NOTE] |
| 10 | +> **Official Docs:** [Setting up GitHub Sponsors for your personal account](https://docs.github.com/en/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account) |
| 11 | +
|
| 12 | +This is a one-time setup. GitHub needs to verify your identity and set up your payout method before your profile goes live. |
| 13 | + |
| 14 | +--- |
| 15 | + |
| 16 | +### Step 1 — Check Your Eligibility & Region |
| 17 | + |
| 18 | +Contributors to open source - including mentorship - may be eligible, subject to GitHub Sponsors eligibility criteria. Check if your country is supported: |
| 19 | + |
| 20 | +- [Supported regions for GitHub Sponsors](https://docs.github.com/en/sponsors/receiving-sponsorships-through-github-sponsors/supported-regions-for-github-sponsors) |
| 21 | + |
| 22 | +If your region isn't listed yet, you can join the waitlist on the same page. |
| 23 | + |
| 24 | +--- |
| 25 | + |
| 26 | +### Step 2 — Enable Two-Factor Authentication (2FA) |
| 27 | + |
| 28 | +GitHub requires 2FA before you can become a sponsored developer. If you haven't enabled it yet, go to **Settings → Password and authentication**. |
| 29 | + |
| 30 | +- [Configuring two-factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +### Step 3 — Apply for GitHub Sponsors |
| 35 | + |
| 36 | +Go to [github.com/sponsors](https://github.com/sponsors) → click **Get sponsored** → follow the prompts to complete your contact information. You will choose your payout method at this step (see Step 4). |
| 37 | + |
| 38 | +Once submitted, GitHub will review your application — this typically takes a few days, though it can take longer. If your application seems stuck, contact [GitHub Support](https://support.github.com) directly. |
| 39 | + |
| 40 | +--- |
| 41 | + |
| 42 | +### Step 4 — Choose Your Payout Method |
| 43 | + |
| 44 | +> [!NOTE] |
| 45 | +> ⚠️ This must be decided at sign-up — it is difficult to change later. |
| 46 | +
|
| 47 | +GitHub offers two options: |
| 48 | + |
| 49 | +#### Option A — Stripe Connect (bank account) |
| 50 | + |
| 51 | +Most common. Your bank account region must match your country of residence. Check the official GitHub Sponsors payout documentation and supported regions for full details. |
| 52 | + |
| 53 | +- [Stripe Connect cross-border payouts — supported countries](https://stripe.com/docs/connect/cross-border-payouts) |
| 54 | +- Double-check your identity info (name, date of birth) before submitting — it is difficult to update after the fact. |
| 55 | + |
| 56 | +#### Option B — Fiscal Host |
| 57 | + |
| 58 | +Best if Stripe isn't available in your country, or if you prefer not to connect a personal bank account. A fiscal host is an organization that receives funds on your behalf and pays you out through their system. |
| 59 | + |
| 60 | +You will need to register with your chosen fiscal host first, then select **"Use a fiscal host"** during GitHub Sponsors sign-up and provide your profile URL from that platform. |
| 61 | + |
| 62 | +GitHub currently supports these fiscal hosts: |
| 63 | + |
| 64 | +- [Open Source Collective](https://opencollective.com/opensource) *(most commonly used)* |
| 65 | +- [Hack Club](https://hackclub.com/fiscal-sponsorship/) |
| 66 | +- [NumFOCUS](https://numfocus.org/programs/fiscal-sponsorship) |
| 67 | +- [Open Collective Europe](https://opencollective.com/europe) |
| 68 | +- [Python Software Foundation](https://www.python.org/psf/) |
| 69 | +- [Radiant Earth](https://radiant.earth/) |
| 70 | +- [Software in the Public Interest](https://www.spi-inc.org/) |
| 71 | +- [Software Underground](https://softwareunderground.org/) |
| 72 | + |
| 73 | +> [!NOTE] |
| 74 | +> **Official Docs:** [Using a fiscal host to receive GitHub Sponsors payouts](https://docs.github.com/en/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts) |
| 75 | +
|
| 76 | +--- |
| 77 | + |
| 78 | +### Step 5 — Submit Your Tax Information |
| 79 | + |
| 80 | +After connecting your payout method, complete a tax form from your Sponsors dashboard: |
| 81 | + |
| 82 | +- **US residents:** Form W-9 |
| 83 | +- **Non-US residents:** Form W-8BEN |
| 84 | + |
| 85 | +- [Tax information for GitHub Sponsors](https://docs.github.com/en/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors) |
| 86 | + |
| 87 | +--- |
| 88 | + |
| 89 | +### Step 6 — Submit for GitHub Review |
| 90 | + |
| 91 | +Click **Request approval** from your Sponsors dashboard. Once approved, your profile goes live at: |
| 92 | + |
| 93 | +```text |
| 94 | +https://github.com/sponsors/YOUR-USERNAME |
| 95 | +``` |
| 96 | + |
| 97 | +--- |
| 98 | + |
| 99 | +### Step 7 — Complete Your Sponsors Profile |
| 100 | + |
| 101 | +After approval, go to **your profile picture → Your sponsors → Dashboard → Profile details** and fill in the following: |
| 102 | + |
| 103 | +- **Short bio** — a brief description of who you are. |
| 104 | +- **Introduction** — describe your open source work. For example: |
| 105 | + |
| 106 | + > *"I'm an OWASP Nest mentor with the Google Summer of Code, helping the next generation of open source security engineers build real-world skills."* |
| 107 | +
|
| 108 | +--- |
| 109 | + |
| 110 | +Once you have completed Phase 1 and your GitHub Sponsors profile is live, you are ready to proceed to the next steps in the OWASP Nest Sponsorship Program. |
| 111 | + |
| 112 | +If you have questions or run into any issues, feel free to open a discussion or reach out to the maintainers. |
0 commit comments