From a90737eb91368b3be912d1759f9573203ef9e70d Mon Sep 17 00:00:00 2001
From: Sindre Sorhus kMTr)T-F=r=9U4?HulfY@Tv(Y2u
z@sgJ2JK}dZB$xeL367h7cTRcGKm4Pm&^8nI$(!=H(Cd1+X%}wk#Q*i;sO$&w!OT0Q
z(2{{|)gTFzhQP8#53BqR9^dE7C5=!#T79g4Xjz#@-F>S6m~f{5m{{!NURRA!LYe=1
z$Nlt=wKUK;wUPbT&J2b8KyQRds4_hsET)8vXur7gb@n(JPK%6ndY+m|$_y{mvxR)<
zzUxB21)YuF90`89gnRfnBgM(yf*iWDUpQ?0eN(7q__!L0l1h6QfhWiU2I+@La(T6$
zVdw9~vGn(0lg{P8=#wG(@Ss{0hVfI$>@-FtAiu=Q%?(s*bjZS3`e7S;Jd2WuhsAi1
z(h6%u?}%nNWa;FI`Ln1pa=mi^^qr@(3t-99v4$*4Zkf9qZ$n>D`P?H?ovw%`5&ASZ
zJQ{{Bwemelbu4lBdK~F-uOCGw)#k=W;+A<~ZRuR{Whti0FYpoF`eJGC)dV;E8Pi(>
zo7#nVN&?y%`k6r8cNy#r2E`hf;HR|*6ZE*03Z3wkunjTBE080=^8ZwF-O+G$>l
- A project of mine is on Product Hunt and could use some feedback 🙌
- speed-test-cli - Test your download speed on the command-line
-
From 709366479bfa78a748ad1b9a05e8c34944e6ef3d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tobias=20B=C3=BCschel?=
What is an awesome list?
Contribution guide
@@ -44,6 +34,13 @@
Just type
+
+
+
+
-
-
-
-
-
-
-
-
----
-
awesome.re
to go here. Check out my blog and follow me on Twitter.
+
+
- - - -
+ + + ## Contents From 003cf83af80816418196029fe59483ebd8dba34b Mon Sep 17 00:00:00 2001 From: platy11
Just type
Just type
Just type
From 6aa449700d3c9999e4470647aee5408b866937f1 Mon Sep 17 00:00:00 2001
From: Julio Cesar dos Santos
From 50710cdaf51e0fe6fd6eef0026b2a56a065eb368 Mon Sep 17 00:00:00 2001
From: Sindre Sorhus
From eca040f5978ba73a0c8cb7e5fe12936ecb261315 Mon Sep 17 00:00:00 2001
From: Jay Sherby awesome.re
to go here. Check out my blog and follow me on Twitter.
From 34afc20537b34b57b75c3bb319894f5e87efc4fa Mon Sep 17 00:00:00 2001
From: Sindre Sorhus
-
-
-My free macOS app HEIC Converter is on Product Hunt. Could use some feedback.
-
awesome.re
to go here. Check out my blog and follow me on Twitter.
-
-
-
-
## Contents
From 2aa290e928d692a334adf608e54471e2c7da9734 Mon Sep 17 00:00:00 2001
From: Sergey Bronnikov
+
+
+My free macOS app Black Out is on Product Hunt.
+
It makes it easy to hide sensitive parts of an image.
awesome.re
to go here. Check out my blog and follow me on Twitter.
From e97541a22e86a38c41464bdbdeff019b57197827 Mon Sep 17 00:00:00 2001
From: Shuaib Yunus
-->
-My free macOS app Black Out is on Product Hunt.
+
It makes it easy to hide sensitive parts of an image.Support my work with the Awesome project and open source in general
From f40e4e0f040f2cc0daba7d004dc96847ca1668c2 Mon Sep 17 00:00:00 2001
From: Sindre Sorhus
+
+Support my work with the Awesome project and open source in general
+
-->
-Support my work with the Awesome project and open source in general
+🐦
Improve your Twitter experience with this browser extension I made
-->
-🐦
+
Improve your Twitter experience with this browser extension I made🌈
Convert videos to high-quality GIFs with this free & open source Mac app I made
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)](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.
- - Either fullwidth or 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.**
- - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses.
- - 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.
- - The link and description are separated by a dash.
Example: `- [AVA](…) - JavaScript test runner.`
- - The description starts with an uppercase character and ends with a period.
- - 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.
+
+
+## Requirements for your Awesome list
+
+- **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)](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.
+ - Either fullwidth or 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.**
+ - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses.
+ - 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.
+ - The link and description are separated by a dash.
Example: `- [AVA](…) - JavaScript test runner.`
+ - The description starts with an uppercase character and ends with a period.
+ - 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.