-
-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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.
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
Incubate #2242
Comments
Started awesome-polars. |
Started awesome-discord-tools |
I actually started this a bit ago, but I started |
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 |
omg, I needed this! |
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: |
Yeah, your main list doesnt meet the guidelines of how to create a list found here. |
<!-- 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.**
I've started working on the Memgraph awesome list. |
<!-- 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.**
Started awesome-permacomputing |
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:
|
I have been working on awesome-android-root for quite some time, it focuses on:
|
Nice bro 👍
…On Wed, Nov 13, 2024, 7:14 AM Fynks ***@***.***> wrote:
I have been working on awesome-android-root
<https://github.com/fynks/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
—
Reply to this email directly, view it on GitHub
<#2242 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLABDP74ZYYLZZYFU5PERBD2ALU4JAVCNFSM5T3R5IIKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENBXGI2TCNBQG4YQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Started awesome-opensource-boilerplates |
Thanks for the tip! Am interested chat me up on Whatsapp let me inform my
team+2348164961457
…On Thu, Nov 14, 2024, 12:07 AM Janu Lingeswaran ***@***.***> wrote:
Started awesome-opensource-boilerplates
<https://github.com/EinGuterWaran/awesome-opensource-boilerplates/>
—
Reply to this email directly, view it on GitHub
<#2242 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLABDP4J7US2K36PDB234LD2APLUNAVCNFSM5T3R5IIKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENBXGUYDANJWGA2Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Started Awesome-Property-Testing :) |
Started awesome-pspd :) |
Started awesome-ebm :) |
@yijun-lee Why announce it when there is no content yet? |
I just uploaded the initial format to get started on the project today! Should I add more content before posting? If I’ve misunderstood anything, I’ll delete the comment and upload it later. |
There's no hard requirements for posting here, but the goal is to get user engagement and feedback. Announcing empty lists wont get you much of that. |
Ah, I see! Thank you for the feedback. I actually thought the main reason was to write down what I'm working on in the issue to avoid overlapping. I’ll organize my existing work and upload it today! |
started working on awesome-ao |
started awesome-world-model-games – awesome list for games run on interactive video models :) |
started working on awesome-standards |
Working on an awesome-backstage list - for the backstage developer portal. |
Looking for feedback on awesome-aoip. (AudiooverIP) |
thanks , my coins /?????
…On Thu, 19 Dec 2024 at 12:05, Mo_ ***@***.***> wrote:
Looking for feedback on awesome-aoip
<https://github.com/Mo-way/awesome-aoip>. (*A*udio*o*ver*IP*)
—
Reply to this email directly, view it on GitHub
<#2242 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKDPQKEKBYCNFGAWC3ZCEUD2GJSKZAVCNFSM5T3R5IIKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJVGI4DSMBVGE4A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: