Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incubate #2242

Open
sindresorhus opened this issue Apr 20, 2022 · 149 comments
Open

Incubate #2242

sindresorhus opened this issue Apr 20, 2022 · 149 comments

Comments

@sindresorhus
Copy link
Owner

If you just starting working on a list, you can post it here to indicate that you are working on it (prevents duplicates) and to gather feedback.

One comment per list draft. Open an issue on the list to provide feedback. Not here.
@sindresorhus sindresorhus pinned this issue Apr 20, 2022
@sindresorhus sindresorhus mentioned this issue Apr 20, 2022
Closed
@cnpryer
Copy link
Contributor

cnpryer commented Apr 20, 2022

Started awesome-polars.

cnpryer added a commit to cnpryer/awesome that referenced this issue Apr 20, 2022
@cnpryer
add reference to sindresorhus#2242 in pull_request_template.md
50fe207
cnpryer added a commit to cnpryer/awesome that referenced this issue Apr 20, 2022
@cnpryer
add reference to sindresorhus#2242 in pull_request_template.md
1406f44
@ericyangpan ericyangpan mentioned this issue Apr 26, 2022
Merged
@Ki-er
Copy link
Contributor

Ki-er commented Apr 26, 2022

Started awesome-discord-tools

@crutchcorn
Copy link

I actually started this a bit ago, but I started awesome-plop

@villesundell
Copy link
Contributor

We have been working on awesome-move for a while now (Move is a smart contract programming language initially started by Facebook). Polishing is still underway: currently adding more descriptions for items, and making the list pass the awesome-lint. We have an open issue on awesome compliance here: MystenLabs/awesome-move#9.

@elasticdotventures
Copy link

Started awesome-discord-tools

omg, I needed this!

@elasticdotventures
Copy link

I submitted a pull request but it got rejected I think because it was misformatted.

https://github.com/elasticdotventures/awesome-openscad/

Here is the commit:
612a987

@Ki-er
Copy link
Contributor

Ki-er commented May 3, 2022

Yeah, your main list doesnt meet the guidelines of how to create a list found here.

@inoue0426 inoue0426 mentioned this issue May 9, 2022
Merged
32 tasks
Dharmik48 added a commit to Dharmik48/awesome that referenced this issue May 15, 2022
@Dharmik48
Add SmollCSS
67b58f2 
<!-- Congrats on creating an Awesome list! 🎉 -->

<!-- Please fill in the below placeholders -->

**[Insert URL to the list here]**

**[Explain what this list is about and why it should be included here]**

### 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.**

## Requirements for your pull request

- **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).**
	Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **Just commenting “looks good” or simply marking the pull request as approved does not count!** You have to actually point out mistakes or improvement suggestions.
- You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- This pull request has a title in the format `Add Name of List`.
	- ✅ `Add Swift`
	- ✅ `Add Software Architecture`
	- ❌ `Update readme.md`
	- ❌ `Add Awesome Swift`
	- ❌ `Add swift`
	- ❌ `add Swift`
	- ❌ `Adding Swift`
	- ❌ `Added Swift`
- Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
	- ✅ `- [iOS](…) - Mobile operating system for Apple phones and tablets.`
	- ✅ `- [Framer](…) - Prototyping interactive UI designs.`
	- ❌ `- [iOS](…) - Resources and tools for iOS development.`
	- ❌ `- [Framer](…)`
	- ❌ `- [Framer](…) - prototyping interactive UI designs`
- Your entry should be added at the bottom of the appropriate category.
- The title of your entry should be title-cased and the URL to your list should end in `#readme`.
	- Example: `- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.`
- The suggested Awesome list complies with the below requirements.

## Requirements for your Awesome list

- **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.
- Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [sindresorhus#2242](sindresorhus#2242) for incubation visibility**.
- Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new).
- The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/).
- **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
	- ✅ `Mobile operating system for Apple phones and tablets.`
	- ✅ `Prototyping interactive UI designs.`
	- ❌ `Resources and tools for iOS development.`
	- ❌ `Awesome Framer packages and tools.`
- It's the result of hard work and the best I could possibly produce.
	**If you have not put in considerable effort into your list, your pull request will be immediately closed.**
- The repo name of your list should be in lowercase slug format: `awesome-name-of-list`.
	- ✅ `awesome-swift`
	- ✅ `awesome-web-typography`
	- ❌ `awesome-Swift`
	- ❌ `AwesomeWebTypography`
- The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`.
	- ✅ `# Awesome Swift`
	- ✅ `# Awesome Web Typography`
	- ❌ `# awesome-swift`
	- ❌ `# AwesomeSwift`
- Non-generated Markdown file in a GitHub repo.
- 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. Please search for existing submissions.
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
- Includes a project logo/illustration whenever possible.
	- Either centered, 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/main/awesome.md#awesome-badge).
	- Should be placed on the right side of the readme heading.
		- Can be placed centered if the list has a centered graphics header.
	- 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 [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none.
	- Must not feature `Contributing` or `Footnotes` sections.
- Has an appropriate license.
	- **We strongly recommend the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), but any [Creative Commons license](https://creativecommons.org/choose/) will work.**
		- Tip: You can quickly add it to your repo by going to this URL: `https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0` (replace `<user>` and `<repo>` accordingly).
	- A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and [Unlicense](https://unlicense.org).
	- Place a file named `license` or `LICENSE` in the repo root with the license text.
	- **Do not** add the license name, text, or a `Licence` section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
	- To verify that you've read all the guidelines, please comment on your pull request with just the word `unicorn`.
- Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines).
	- The file should be named `contributing.md`. Casing is up to you.
	- It can optionally be linked from the readme in a dedicated section titled `Contributing`, positioned at the top or bottom of the main content.
	- The section should not appear in the Table of Contents.
- All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a `Footnotes` section at the bottom of the readme. The section should not be present in the Table of Contents.
- Has consistent formatting and proper spelling/grammar.
	- The link and description are separated by a dash. <br>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 use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap).
- Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
- Doesn't include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough.

**Go to the top and read it again.**
@Dharmik48 Dharmik48 mentioned this issue May 15, 2022
Closed
@rzashakeri rzashakeri mentioned this issue May 16, 2022
Closed
@BlackSquirrelz BlackSquirrelz mentioned this issue May 17, 2022
Closed
32 tasks
@Delft-Open-Hardware Delft-Open-Hardware mentioned this issue May 20, 2022
Merged
@kgolubic
Copy link

I've started working on the Memgraph awesome list.

@pbauer pbauer mentioned this issue May 20, 2022
Merged
brootware added a commit to brootware/awesome that referenced this issue May 22, 2022
@brootware
Add Cyber security university
6f220de 
<!-- Congrats on creating an Awesome list! 🎉 -->

<!-- Please fill in the below placeholders -->

**https://github.com/brootware/Cyber-Security-University**

**Cyber Security University is A curated list of awesome and free educational resources that focuses on learn by doing.**

### 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.**

## Requirements for your pull request

- **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive.
- **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).**
	Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **Just commenting “looks good” or simply marking the pull request as approved does not count!** You have to actually point out mistakes or improvement suggestions.
- You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md).
- This pull request has a title in the format `Add Name of List`.
	- ✅ `Add Swift`
	- ✅ `Add Software Architecture`
	- ❌ `Update readme.md`
	- ❌ `Add Awesome Swift`
	- ❌ `Add swift`
	- ❌ `add Swift`
	- ❌ `Adding Swift`
	- ❌ `Added Swift`
- Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
	- ✅ `- [iOS](…) - Mobile operating system for Apple phones and tablets.`
	- ✅ `- [Framer](…) - Prototyping interactive UI designs.`
	- ❌ `- [iOS](…) - Resources and tools for iOS development.`
	- ❌ `- [Framer](…)`
	- ❌ `- [Framer](…) - prototyping interactive UI designs`
- Your entry should be added at the bottom of the appropriate category.
- The title of your entry should be title-cased and the URL to your list should end in `#readme`.
	- Example: `- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.`
- The suggested Awesome list complies with the below requirements.

## Requirements for your Awesome list

- **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.
- Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [sindresorhus#2242](sindresorhus#2242) for incubation visibility**.
- Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new).
- The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/).
- **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
	- ✅ `Mobile operating system for Apple phones and tablets.`
	- ✅ `Prototyping interactive UI designs.`
	- ❌ `Resources and tools for iOS development.`
	- ❌ `Awesome Framer packages and tools.`
- It's the result of hard work and the best I could possibly produce.
	**If you have not put in considerable effort into your list, your pull request will be immediately closed.**
- The repo name of your list should be in lowercase slug format: `awesome-name-of-list`.
	- ✅ `awesome-swift`
	- ✅ `awesome-web-typography`
	- ❌ `awesome-Swift`
	- ❌ `AwesomeWebTypography`
- The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`.
	- ✅ `# Awesome Swift`
	- ✅ `# Awesome Web Typography`
	- ❌ `# awesome-swift`
	- ❌ `# AwesomeSwift`
- Non-generated Markdown file in a GitHub repo.
- 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. Please search for existing submissions.
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
- Includes a project logo/illustration whenever possible.
	- Either centered, 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/main/awesome.md#awesome-badge).
	- Should be placed on the right side of the readme heading.
		- Can be placed centered if the list has a centered graphics header.
	- 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 [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none.
	- Must not feature `Contributing` or `Footnotes` sections.
- Has an appropriate license.
	- **We strongly recommend the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), but any [Creative Commons license](https://creativecommons.org/choose/) will work.**
		- Tip: You can quickly add it to your repo by going to this URL: `https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0` (replace `<user>` and `<repo>` accordingly).
	- A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and [Unlicense](https://unlicense.org).
	- Place a file named `license` or `LICENSE` in the repo root with the license text.
	- **Do not** add the license name, text, or a `Licence` section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
	- To verify that you've read all the guidelines, please comment on your pull request with just the word `unicorn`.
- Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines).
	- The file should be named `contributing.md`. Casing is up to you.
	- It can optionally be linked from the readme in a dedicated section titled `Contributing`, positioned at the top or bottom of the main content.
	- The section should not appear in the Table of Contents.
- All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a `Footnotes` section at the bottom of the readme. The section should not be present in the Table of Contents.
- Has consistent formatting and proper spelling/grammar.
	- The link and description are separated by a dash. <br>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 use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap).
- Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
- Doesn't include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough.

**Go to the top and read it again.**
@brootware brootware mentioned this issue May 22, 2022
Merged
3 tasks
@theeMahmud theeMahmud mentioned this issue May 26, 2022
Closed
@Cy-clon3 Cy-clon3 mentioned this issue May 30, 2022
Closed
@atkirtland atkirtland mentioned this issue Jun 1, 2022
Merged
@LuozhuZhang LuozhuZhang mentioned this issue Jun 7, 2022
Closed
@walido0z walido0z mentioned this issue Jun 14, 2022
Open
@teamssix teamssix mentioned this issue Jun 16, 2022
Closed
@gpotter2 gpotter2 mentioned this issue Jun 19, 2022
Merged
@kgolubic kgolubic mentioned this issue Jun 20, 2022
Closed
@itsmeadarsh2008
Copy link
Contributor

Started awesome-reflex

@dirandoboss
Copy link

started

@AbdelrahmanBayoumi AbdelrahmanBayoumi mentioned this issue Sep 28, 2024
Closed
33 tasks
@Tacacian
Copy link

Anyone interested in non-destructive testing?

@powhapki powhapki mentioned this issue Sep 30, 2024
Closed
33 tasks
@0PandaDEV 0PandaDEV mentioned this issue Sep 30, 2024
Merged
33 tasks
@itsmeadarsh2008 itsmeadarsh2008 mentioned this issue Sep 30, 2024
Merged
33 tasks
@AnirudhG07 AnirudhG07 mentioned this issue Oct 3, 2024
Open
33 tasks
@michaelbrusegard michaelbrusegard mentioned this issue Oct 3, 2024
Open
33 tasks
@amitmittal amitmittal mentioned this issue Oct 11, 2024
Merged
33 tasks
@lnxpy lnxpy mentioned this issue Oct 21, 2024
Closed
33 tasks
@sellisd
Copy link
Contributor

sellisd commented Oct 27, 2024

I started a fun list: https://github.com/sellisd/awesome-nothing links to empty or nonsensical resources that make you laugh and think

@Axorax
Copy link

Axorax commented Oct 28, 2024

Started awesome-free-apps

@hardBSDk hardBSDk mentioned this issue Nov 1, 2024
Open
33 tasks
@ForNeVeR ForNeVeR mentioned this issue Nov 4, 2024
Open
33 tasks
@idematos
Copy link

idematos commented Nov 7, 2024

Started awesome-permacomputing

@felladrin
Copy link

Started working on awesome-ai-web-search, focusing on software that allows searching the web with the assistance of AI. In general, it includes the following types of software:

  • Web Search with LLM summarization and follow-up questions (Example: MiniSearch)
  • LLM chat with Web Search support (Example: Open WebUI)
  • Agent-driven research done by LLM collecting info via Web Search (Example: GPT Researcher)

@fynks
Copy link

fynks commented Nov 13, 2024

I have been working on awesome-android-root for quite some time, it focuses on:

  • A basic intro to Android rooting and various methods of rooting
  • A catalogue of Apps that use android permission to run or depend on rooted device for extended functionality

@Wizzyboypondec
Copy link

Wizzyboypondec commented Nov 13, 2024 via email

@EinGuterWaran
Copy link

Started awesome-opensource-boilerplates

@Wizzyboypondec
Copy link

Wizzyboypondec commented Nov 14, 2024 via email

@Bruno-366
Copy link

Started Awesome-Property-Testing :)

@Bruno-366 Bruno-366 mentioned this issue Nov 15, 2024
Open
33 tasks
@yanganto yanganto mentioned this issue Nov 16, 2024
Open
33 tasks
@ssvjugg ssvjugg mentioned this issue Nov 19, 2024
Closed
33 tasks
@zhjwpku zhjwpku mentioned this issue Nov 23, 2024
Open
33 tasks
@bozaci bozaci mentioned this issue Nov 25, 2024
Open
33 tasks
@Kitarah Kitarah mentioned this issue Nov 30, 2024
Merged
33 tasks
@yijun-lee
Copy link

Started awesome-pspd :)

@yijun-lee
Copy link

Started awesome-ebm :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests