The Open Source Supporters awesome list highlights companies that offer their tools and services for free to Open Source and public projects. It is important to note that some companies offer standard free tiers (such as Slack, for example), however this list focuses specifically on companies that have made an overt commitment to the Open Source community.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:
Include a short description about the project/theme of the list. It should not describe the list itself. Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.
The list I'm submitting complies with these requirements:
Has been around for at least 30 days. That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme.(Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.
The file should be named contributing.md. Casing is up to you.
Has consistent formatting and proper spelling/grammar.
Each link description starts with an uppercase character and ends with a period. Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/1028
**Author:** [@zachflower](https://github.com/zachflower)
**Created:** 8/19/2017
**Status:** ✅ Merged
**Merged:** 10/11/2017
**Merged by:** [@sindresorhus](https://github.com/sindresorhus)
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (6)
- [`38e8212`](https://github.com/sindresorhus/awesome/commit/38e8212125cf16f39fee5cdebcf0158be6ceb7cf) Add Free for Open Source
- [`1b1c9dc`](https://github.com/sindresorhus/awesome/commit/1b1c9dcbdeaa4eed6424dadc423c1e6629911e01) Make copy more clear
- [`1fe0211`](https://github.com/sindresorhus/awesome/commit/1fe021194ef948b44bce11998d4bc947c6f35a77) Merge branch 'master' into patch-1
- [`3f50363`](https://github.com/sindresorhus/awesome/commit/3f50363242d07408802db385cc8ebb69b870a40c) Change list name to reduce ambiguity
- [`c29d8bd`](https://github.com/sindresorhus/awesome/commit/c29d8bd388fc39a632556433980ffc292765d007) Merge branch 'master' into patch-1
- [`ffde32c`](https://github.com/sindresorhus/awesome/commit/ffde32ca316ef946258f7fde5110fe860c47ad78) Merge branch 'master' into patch-1
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
<!-- Congrats on creating an Awesome list! 🎉 -->
<!-- Please fill in the below placeholders -->
https://github.com/zachflower/awesome-open-source-supporters
The Open Source Supporters awesome list highlights companies that offer their tools and services for free to Open Source and public projects. It is important to note that some companies offer standard free tiers (such as Slack, for example), however this list focuses _specifically_ on companies that have made an overt commitment to the Open Source community.
# By submitting this pull request I confirm I've read and complied with the below requirements.
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
- I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md).
- This pull request has a descriptive title.<br>For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`.
- The entry in the Awesome list should:
- Include a short description about the project/theme of the list. **It should not describe the list itself.**<br>Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`.
- Be added at the bottom of the appropriate category.
- The list I'm submitting complies with these requirements:
- **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
- It's the result of hard work and the best I could possibly produce.
- Non-generated Markdown file in a GitHub repo.
- **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
- The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics.
- Not a duplicate.
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Includes a project logo/illustration whenever possible.
- Placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron)
- The image should link to the project website or any relevant website.
- The image should be high-DPI. Set it to maximum half the width of the original image.
- Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
- Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge).
- Should be placed on the right side of the readme heading.
- Should link back to this list.
- Has a Table of Contents section.
- Should be named `Contents`, not `Table of Contents`.
- Should be the first section in the list.
- Should only have one level of sub-lists, preferably none.
- Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license).
- That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.**
- If you use a license badge, it should be SVG, not PNG.
- Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines).
- The file should be named `contributing.md`. Casing is up to you.
- Has consistent formatting and proper spelling/grammar.
- Each link description starts with an uppercase character and ends with a period.<br>Example: `- [AVA](…) - JavaScript test runner.`
- Drop all the `A` / `An` prefixes in the descriptions.
- Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`.
- Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
- Go to the top and read it again.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/1028
Author: @zachflower
Created: 8/19/2017
Status: ✅ Merged
Merged: 10/11/2017
Merged by: @sindresorhus
Base:
master← Head:patch-1📝 Commits (6)
38e8212Add Free for Open Source1b1c9dcMake copy more clear1fe0211Merge branch 'master' into patch-13f50363Change list name to reduce ambiguityc29d8bdMerge branch 'master' into patch-1ffde32cMerge branch 'master' into patch-1📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
https://github.com/zachflower/awesome-open-source-supporters
The Open Source Supporters awesome list highlights companies that offer their tools and services for free to Open Source and public projects. It is important to note that some companies offer standard free tiers (such as Slack, for example), however this list focuses specifically on companies that have made an overt commitment to the Open Source community.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
For example,
Add Name of List, notUpdate readme.mdorAdd awesome list.Example:
- [Fish](…) - User-friendly shell., not- [Fish](…) - Resources for Fish..That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-list&awesomeas GitHub topics. I encourage you to add more relevant topics.Contents, notTable of Contents.contributing.md. Casing is up to you.Example:
- [AVA](…) - JavaScript test runner.A/Anprefixes in the descriptions.Node.js, notNodeJSornode.js.You can still use Travis for list linting, but the badge has no value in the readme.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.