275088ea75
* Stripped trailing whitespace, added OSS badge to Chromium, added Tor Browser * Added Lockdown under Security Tools * Added htop to Command Line section, fixed Chromium and TorBrowser links, added open-source link to Firefox * Added MalwareBytes to Security Tools * Added CLion * Added Signal for Desktop and Riot * Alphebetized Text Editors * Alphebetized IDEs * Alphebetized Development Tools * Alphebetized Regex Editors * Alphebetized Test Tools * Alphebetized CLI tools and removed duplicate Hyper entry * Alphebetized Version Control GUIs * Alphebetized Version Control Managers * Alphebetized Remote Login Software, System Related Tools, Qual of Life, Databases * Alphebetized Communication and VMs * Alphebetized email and Data Recovery Tools * Alphebetized Frameworks, FTP, Ebooks * Alphebetize Online Storage and Download Management Tools * Alphebetized Browsers, Translation tools, Security tools * Assorted alphebetization * Alphabetize Third Party Markets, WM, Productivity, General Tools * More alphabetization * Added Contributing.md * Added CC0 License * Removed all leading [A/An]s and rephrased some descriptions. Added icons where needed and removed a duplicate * Update from master * Removed leading [A/An]s, rephrased decsriptions, added badges, added a CLI tool * Phrasing * phrasing
3.3 KiB
Contribution Guidelines
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
The pull request should have a useful title. Pull requests with Update readme.md as title will be closed right away because I'm so tired of nobody reading this document. Please carefully read everything in Adding to this list.
Table of Contents
- Adding to this list
- Creating your own awesome list
- Adding something to an awesome list
- Updating your Pull Request
Adding to this list
Please ensure your pull request adheres to the following guidelines:
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description.
- Make an individual pull request for each suggestion.
- Use title-casing (AP style).
- Use the following format:
[List Name](link) - Link additions should be added to the bottom of the relevant category.
- New categories or improvements to the existing categorization are welcome.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
- The pull request and commit should have a useful title.
- The body of your commit message should contain a link to the repository.
Thank you for your suggestions!
Creating your own awesome list
To create your own list, check out the instructions.
Adding something to an awesome list
If you have something awesome to contribute to an awesome list, this is how you do it.
You'll need a GitHub account!
- Access the awesome list's GitHub page. For example: https://github.com/sindresorhus/awesome
- Click on the
readme.mdfile:
- Now click on the edit icon.
- You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use GitHub Flavored Markdown.
- Say why you're proposing the changes, and then click on "Propose file change".
- Submit the pull request!
Updating your Pull Request
Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines.
Here is a write up on how to change a Pull Request, and the different ways you can do that.