Author SHA1 Message Date
heldev 42ff4209b7 Leave only *GPL license tags 2019-07-19 12:44:42 -04:00
heldev 0cc14ccc20 Resolve 697: Add crawled repositories and licenses 2019-07-15 19:00:09 -04:00
3 changed files with 412 additions and 499 deletions
-2
View File
@@ -1,4 +1,3 @@
<!--
Please read the CONTRIBUTING.md first. The most important parts regarding the actual entry:
- Write about it's unique selling point compared to other projects.
@@ -7,4 +6,3 @@ Please read the CONTRIBUTING.md first. The most important parts regarding the ac
- Do not use a description like "A library/project/tool/framework for JSON processing in Java" since all of this is implied.
- Finish the description with a dot.
- Try to order it alphabetically.
-->
+15 -15
View File
@@ -12,11 +12,11 @@ Unfortunately, not every library/tool/framework can be considered. This list aim
Suggested software must also be developer-friendly, which means it meets the following criteria:
(i) If an open source _application_, it is licensed under one of the open source licenses listed on https://opensource.org/licenses.
(i) If an open source *application*, it is licensed under one of the open source licenses listed on https://opensource.org/licenses.
(ii) If an open source _library_, it is licensed under one of the open source licenses listed on https://opensource.org/licenses, with the exception of GPL and AGPL (due to their viral nature).
(ii) If an open source *library*, it is licensed under one of the open source licenses listed on https://opensource.org/licenses, with the exception of GPL and AGPL (due to their viral nature).
(iii) If commercial, it has clear pricing and at least one free tier.
(iii) If commercial, it has clear pricing.
(iv) It has a documentation in the English language.
@@ -26,11 +26,11 @@ There are two required criteria for a pull request:
1. If an entry has a similar scope as other entries in the same category, the description must state the unique features that distinguishes it from the other entries.
2. If an entry does not meet conditions _(a)_ to _(d)_ there has to be an explanation either in the description or the pull request why it should be added to the list.
2. If an entry does not meet conditions *(a)* to *(d)* there has to be an explanation either in the description or the pull request why it should be added to the list.
3. If an entry doesn't fit any of the pre-existing specialized sections, it should go under Miscellaneous.
3. If an entry doesn't fit any of the pre-existing specialised sections, it should go under Miscellaneous.
4. If two or more entries in Miscellaneous are in the same domain, then they can be moved to a new specialized section.
4. If two or more entries in Miscellaneous are in the same domain, then they can be moved to a new specialised section.
Self-promotion is frowned upon and viewed critically, but your suggestion will of course be approved if the criteria match.
@@ -38,14 +38,14 @@ If your entry isn't accepted, please check the [Issues](https://github.com/akull
Furthermore, please ensure your pull request follows the following guidelines:
- Please search previous suggestions before making a new one, as yours may be a duplicate.
- Please make an individual pull request for each suggestion.
- Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
- Entries should be sorted in ascending alphabetical order, i.e. a to z.
- New categories or improvements to the existing categorization are welcome.
- Keep descriptions short, simple and unbiased.
- End all descriptions with a full stop/period.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.
* Please search previous suggestions before making a new one, as yours may be a duplicate.
* Please make an individual pull request for each suggestion.
* Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
* Entries should be sorted in ascending alphabetical order, i.e. a to z.
* New categories or improvements to the existing categorization are welcome.
* Keep descriptions short, simple and unbiased.
* End all descriptions with a full stop/period.
* Check your spelling and grammar.
* Make sure your text editor is set to remove trailing whitespace.
Thank you for your suggestions!
+392 -477
View File
File diff suppressed because it is too large Load Diff