├── .github └── FUNDING.yml ├── CONTRIBUTING.md ├── LICENSE └── README.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | github: Correia-jpv -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to lists 2 | 3 | Thank you for your interest in this project! Before making a contribution, please take a minute to read these guidelines. 4 | 5 | If you have any questions about the project or these guidelines, [open an issue](https://github.com/jnv/lists/issues). 6 | 7 | Most importantly, **have fun!** Don’t take this project _too_ seriously. While it is (hopefully) useful, there are better things in life than some arbitrary hoard of links. 8 | 9 | ## What Is Accepted 10 | 11 | If you wish to add some project to this list, make sure it meets the following criteria: 12 | 13 | * The project’s primary purpose is to be a list; it can be a list of recipes, favorite places in some city, learning resources… The subject doesn’t matter. 14 | * The project should contain the list of resources in some form; i.e., if the resources are stored in some database and the project contains only a backend code, it won’t be accepted. 15 | * The project should be open to contributions; it doesn’t have to be hosted on GitHub, but anyone should be able to send a pull request or its equivalent. 16 | * The project can be forked, cloned and maintained without reliance on the original source. 17 | * Non-English lists and lists about non-technical subjects are very welcome! 18 | 19 | ## Adding a List 20 | 21 | Lists are alphabetically sorted, so find a proper place to put your list in and an item in the following format: 22 | 23 | ```md 24 | * [repository-name](https://github.com/author/repository-name) – Optional short description. 25 | ``` 26 | 27 | In your commit message, write: 28 | 29 | ``` 30 | Add repository-name 31 | ``` 32 | 33 | Keep one list to one commit and make separate pull requests for every list. 34 | 35 | In your pull request, please put the list’s URL into the description, it is easier to review it. 36 | 37 | Link’s description (`repository-name` in the example above) should be the original repository name. For example, given the repository `author/my-awesome-list-of-pancakes`, use `my-awesome-list-of-pancakes` for link’s description, not `My Awesome List of Pancakes` or even `Pancakes`. 38 | 39 | Add a short description if the repository name is not obvious enough or to improve searchability. For example, `awesome-php` is most likely about PHP, while `cscs` is not obvious, so it is explained in the description (_Coding Style Conventions and Standards._). 40 | 41 | Avoid using _List of…_ or _A curated list of…_ and similar in the description. It is redundant. 42 | 43 | You can use the description for linking or describing a less known subject of the list. For example, `awesome-sarl` is about a rather less known SARL programming language, so the description states: _Resources for [SARL](http://www.sarl.io/) Agent-Oriented Programming Language._ 44 | 45 | If the list is not in English, state its language. The list’s description can also be in the list’s language. For example: 46 | 47 | * [awesome-awesomeness-zh_CN](https://github.com/justjavac/awesome-awesomeness-zh_CN) _In Chinese_ – 中文版awesome list 系列文章` 48 | 49 | If there are multiple lists with the same name by different authors, add the author’s username after the link, e.g., `recipes by @csswizardy`. 50 | 51 | If there is a website for the list, add a link into the sub-item. For example, `awesome-ruby` has an official presentation at [awesome-ruby.com](http://awesome-ruby.com/), so in the list there is: 52 | 53 | * [awesome-ruby](https://github.com/markets/awesome-ruby) by @markets 54 | - http://awesome-ruby.com/ 55 | 56 | ### Technical and Non-technical Lists 57 | 58 | Is your list related to software, programming, video games, or development activities? Then it is probably Technical. If the project’s name starts with `awesome`, put it into the [awesome-*](https://github.com/jnv/lists#awesome-) section. 59 | 60 | If your list is related to cooking, fiction books, pictures, people or pretty much anything a non-programmer can relate to, then your project is likely Non-Technical and should be sorted as such. 61 | 62 | When in doubt, [just ask](https://github.com/jnv/lists/issues). Or just send a pull request, we’ll sort it out. 63 | 64 | ## Removing Lists 65 | 66 | You are welcome to propose a removal or change of an existing entry if: 67 | 68 | * The project is not available anymore (e.g., the repository was deleted, or the user account was closed), 69 | * the project has been moved to a new URL (e.g., project was moved under an organization). 70 | 71 | Lack of activity in the project or duplication with other projects are not reasons for removal. 72 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | --------------------------------------------------------------------------------