├── SECURITY.md ├── SUPPORT.md ├── FUNDING.yml ├── ISSUE_TEMPLATE ├── content_request.yaml └── bug_report.yaml ├── CHANGELOG.md ├── README.md ├── PULL_REQUEST_TEMPLATE ├── clojure_code_contribution.md └── practicalli_book_contribution.md ├── profile └── readme.md ├── CONTRIBUTING.md ├── GOVERNANCE.md ├── CODE_OF_CONDUCT.md └── LICENSE.md /SECURITY.md: -------------------------------------------------------------------------------- 1 | Security reports should be raised as issues against the respective Practicalli repository, stating the details of the issue and tooling used to indentify the issue. 2 | 3 | Repeatable issues will be resolved much faster than those that require manual investigation and testing. 4 | 5 | [Securing your repository: GitHub Docs](https://docs.github.com/en/code-security/getting-started/securing-your-repository) 6 | 7 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | Request support for content and projects provides by Practicalli via one of the following methods: 2 | 3 | - Post a message in the `#practicalli` channel of the [Clojurians Slack Community](https://clojurians.slack.com/) - [sign up](http://clojurians.net/) 4 | - Raise an issue via the [Practicalli issue board](https://github.com/orgs/practicalli/projects/2) 5 | - Contact Engineering at Practical.li with questions 6 | 7 | -------------------------------------------------------------------------------- /FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: [practicalli-johnny] 4 | # patreon: # Replace with a single Patreon username 5 | # open_collective: # Replace with a single Open Collective username 6 | # ko_fi: # Replace with a single Ko-fi username 7 | # tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel 8 | # community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry 9 | # liberapay: # Replace with a single Liberapay username 10 | # issuehunt: # Replace with a single IssueHunt username 11 | # otechie: # Replace with a single Otechie username 12 | # custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] 13 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE/content_request.yaml: -------------------------------------------------------------------------------- 1 | name: ✨Idea Request 2 | description: Request a new content or enhancement 3 | labels: ["enhancement"] 4 | title: "Idea: " 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | Please make sure this request hasn't been already submitted by someone by looking through other open/closed issues 10 | 11 | - type: textarea 12 | id: description 13 | attributes: 14 | label: Description 15 | description: Give us a brief description of the idea or enhancement you would like 16 | validations: 17 | required: true 18 | 19 | - type: textarea 20 | id: additional-information 21 | attributes: 22 | label: Additional Information 23 | description: Give us some additional information on the feature request like proposed solutions, links, screenshots, etc. 24 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | 3 | All notable changes to this project will be documented in this file. 4 | The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) 5 | 6 | * **Added** for new features 7 | * **Changed** for changes in existing functionality 8 | * **Deprecated** for soon-to-be removed features 9 | * **Resolved** resolved issue 10 | * **Security** vulnerability related change 11 | 12 | ## [Unreleased] 13 | 14 | ### Added 15 | - add changelog 16 | - health: add governance description 17 | 18 | ### Changed 19 | - health: update funding account to practicalli-johnny 20 | - health: rename to CONTRIBUTING.md standard naming of file 21 | - health: add link to GitHub health files 22 | - health: general support approach for practicalli projects 23 | - health: general security approach for practicalli projects 24 | - health: updated pull request code contribution template 25 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Practicalli .github 2 | 3 | Organisation profile and [GitHub community health files](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) across the Practicalli organisation. 4 | 5 | A `.github` repository provides defaults for all of user and organisation repositories which don't contain their own `.github` directory. 6 | 7 | A `.github` directory in a repository can contain documents about the project and configuration to mange that project. 8 | 9 | - Continuous Integration workflows 10 | - issue and pull request templates 11 | - funding information 12 | - code of conduct 13 | 14 | 15 | ## Licence 16 | 17 |
18 | Creative Commons License 19 | This work is licensed under a Creative Commons Attribution 4.0 ShareAlike License (including images & stylesheets). 20 |
21 | 22 | 23 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE/bug_report.yaml: -------------------------------------------------------------------------------- 1 | name: 🐛Bug Report 2 | description: File a bug report here 3 | title: "[BUG]: " 4 | labels: ["bug"] 5 | assignees: ["practicalli-johnny"] 6 | body: 7 | - type: markdown 8 | attributes: 9 | value: | 10 | Thanks for taking the time to fill out this bug report 🤗 11 | Make sure there aren't any open/closed issues for this topic 😃 12 | 13 | - type: textarea 14 | id: bug-description 15 | attributes: 16 | label: Description of the bug 17 | description: Give us a brief description of what happened and what should have happened 18 | validations: 19 | required: true 20 | 21 | - type: textarea 22 | id: steps-to-reproduce 23 | attributes: 24 | label: Steps To Reproduce 25 | description: Steps to reproduce the behavior. 26 | placeholder: | 27 | 1. Go to '...' 28 | 2. Click on '...' 29 | 3. Scroll down to '...' 30 | 4. See error 31 | validations: 32 | required: true 33 | - type: textarea 34 | id: additional-information 35 | attributes: 36 | label: Additional Information 37 | description: | 38 | Provide any additional information such as logs, screenshots, likes, scenarios in which the bug occurs so that it facilitates resolving the issue. 39 | -------------------------------------------------------------------------------- /PULL_REQUEST_TEMPLATE/clojure_code_contribution.md: -------------------------------------------------------------------------------- 1 | 2 | #### Description :memo: 3 | 4 | 5 | 6 | Resolve # 7 | Refer # 8 | 9 | #### Type of change :octocat: 10 | 11 | 12 | 13 | - [ ] Bug fix (non-breaking change resolving an issue) 14 | - [ ] New feature (non-breaking change adding functionality) 15 | - [ ] Breaking change (fix or feature that breaks an API or contract between services) 16 | - [ ] Documentation update 17 | - [ ] Development workflow enhancement 18 | 19 | #### How Has This Been Tested? :beetle: 20 | 21 | 22 | - [ ] Test A 23 | - [ ] Test B 24 | - [ ] Unit tests run with `clojure -X:test:runner` 25 | - [x] GitHub Action checkers 26 | 27 | 28 | 29 | #### Checklist :eyes: 30 | 31 | - [ ] Code follows the [Practicalli style guides](https://practical.li/clojure/coding-guidelines/) 32 | - [ ] Add / update doc-strings where relevant 33 | - [ ] Changelog entry describing all notable changes & GitHub ticket (add `Skip-Changelog` label to PR if entry not required) 34 | - [ ] Unit tests to cover code changes and integration tests run successfully 35 | - [ ] Request one or more of the team review the PR 36 | -------------------------------------------------------------------------------- /PULL_REQUEST_TEMPLATE/practicalli_book_contribution.md: -------------------------------------------------------------------------------- 1 | > WARNING: Practicalli Books are currently being migrated to MkDocs which also presents an opportunity to refact the content and navigation of each book. 2 | > Submitting pull requests for broken links may not resolve the issue as the page layouts may change. 3 | > Please raise an issue before spending time working on the book as that work may become redundant by the migration to MkDocs and subsequent changes 4 | 5 | 6 | #### Description :memo: 7 | 8 | _Please include a summary of the change and link to any relevant Jira tickets._ 9 | 10 | Resolve # 11 | Refer # 12 | 13 | #### Type of change :octocat: 14 | 15 | _Please delete options that are not relevant_ 16 | 17 | - [ ] Content addition (non-breaking change, resolving an issue) 18 | - [ ] New page or section that also updates the navigation (non-breaking change) 19 | - [ ] Breaking change (changes in-page or overall navigation ) 20 | - [ ] README update 21 | - [ ] Development workflow enhancement 22 | 23 | #### Tested? :beetle: 24 | 25 | _Confirm that the change is correct and the website can still be built_ 26 | 27 | - [ ] `make docs` was run and the website published at [localhost:7777/](http://localhost:7777) 28 | - [] GitHub Action checkers - MegaLinter has no errors 29 | 30 | 31 | #### Checklist :eyes: 32 | 33 | - [x] Contribution follows the [Practicalli Contribution guidelines](https://practical.li/clojure/contributing/) 34 | - [x] Contribution becomes copyright of Practicalli and is made available under Creative Commons Licence indefinately 35 | - [ ] Request practicalli-join reviews the PR 36 | -------------------------------------------------------------------------------- /profile/readme.md: -------------------------------------------------------------------------------- 1 | # Practicalli 2 | 3 | Practical guides to programming in Clojure and tools that support an effective Clojure REPL workflow (Repl Driven Development). 4 | 5 | [Practicalli Engineering Playbook](https://practical.li/engineering-playbook/) contains guides to a wider range of tools and practices within Engineering and Technical Management. 6 | 7 | [Practicalli website](https://practical.li) provides a range of books to learn Clojure programming and detailed editor guides to support an effective workflow. 8 | 9 | - [Practicalli Clojure](https://practical.li/clojure) | [Practicalli Clojure Web Services](https://practical.li/clojure-web-services) | [Practicalli ClojureScript](https://practical.li/clojurescript) 10 | - [Practicalli Neovim](https://practical.li/neovim) | [Practicalli Spacemacs](https://practical.li/spacemacs) | [Practicalli VSpaceCode](https://practical.li/vspacecode) 11 | - [Practicalli Project Templates](https://practical.li/clojure/clojure-cli/projects/templates/practicalli/) 12 | - [Practicalli Engineering Playbook](https://practical.li/engineering-playbook) 13 | 14 | [Practicalli YouTube channel](https://youtube.com/practicalli) has over 100 hours of live coding in Clojure to demonstrate how to think in functional programming and apply Clojure to sovling challenges. 15 | 16 | ![Clojure repl driven development using Clojure aware editor](https://raw.githubusercontent.com/practicalli/graphic-design/live/clojure/clojure-repl-workflow-concept.png) 17 | 18 | 19 | ## Sponsor Practicalli 20 | 21 | [![Sponsor practicalli-john](https://raw.githubusercontent.com/practicalli/graphic-design/live/buttons/practicalli-github-sponsors-button.png)](https://github.com/sponsors/practicalli-johnny/) 22 | 23 | The majority of my work is now focused on the [Practicalli series of books and videos](https://practical.li/) and an advisory role with several communities 24 | 25 | Thank you to [Cognitect](https://www.cognitect.com/), [Nubank](https://nubank.com.br/) and a wide range of other [sponsors](https://github.com/sponsors/practicalli-john#sponsors) from the Clojure community for your continued support 26 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Practicall 2 | 3 | Practicalli content is written in markdown and uses MkDocs to generate the website via a GitHub action. 4 | 5 | Practicalli code is written in Clojure and configuration in Edn, Yaml and ELisp. Languages and configuration should be checked via MegaLinter or a specific lint tool. 6 | 7 | By submitting content ideas and corrections you are agreeing they can be used in this workshop under the [Creative Commons Attribution ShareAlike 4.0 International license](https://creativecommons.org/licenses/by-sa/4.0/){target=_blank}. Attribution will be detailed via [GitHub contributors](https://github.com/practicalli/clojure/graphs/contributors){target=_blank}. 8 | 9 | All content and interaction with any persons or systems must be done so with respect and within the Practicalli Code of Conduct. 10 | 11 | 12 | ### Submit an issue or idea 13 | 14 | If something doesnt seem quite right or something is missing from the book, please raise an issue via the GitHub repository of the project. 15 | 16 | 17 | ### Considering a Pull request? 18 | 19 | Before investing any time in a pull request, please raise an issue explaining the situation. This can save you and the maintainer time and avoid rejected pull requests. 20 | 21 | Please keep pull requests small and focused, as they are much quicker to review and easier to accept. Ideally PR's should be for a specific page or at most a section. 22 | 23 | A PR with a list of changes across different sections will not be merged, it will be reviewed eventually though. 24 | 25 | 26 | ## Thank you to everyone that has contributed 27 | 28 | A huge thank you to Rich Hickey and the team at Cognitect for creating and continually guiding the Clojure language. Special thank you to Alex Miller who has provided excellent advice on working with Clojure and the CLI tooling. 29 | 30 | The Clojure community has been highly supportive of everyone using Clojure and I'd like to thank everyone for the feedback and contributions. I would also like to thank everyone that has joined in with the [London Clojurins community](https://www.meetup.com/London-Clojurians/){target=_blank}, [ClojureBridgeLondon](https://clojurebridgelondon.github.io/){target=_blank}, [Clojurians Slack community](http://clojurians.net/){target=_blank}, [Clojurians Zulip](https://clojurians.zulipchat.com/){target=_blank} community and [Clojureverse community](https://clojureverse.org/){target=_blank}. 31 | 32 | Thank you to everyone who sponsors the Practicalli websites and videos and for the [Clojurists Together sponsorship](https://www.clojuriststogether.org/){target=_blank}, it helps me continue the work at a much faster pace. 33 | 34 | Special thanks to [Bruce Durling](https://twitter.com/otfrom){target=_blank} for getting me into Cloure in the first place. 35 | 36 | -------------------------------------------------------------------------------- /GOVERNANCE.md: -------------------------------------------------------------------------------- 1 | # Main Governance Document 2 | 3 | 4 | A GOVERNANCE file lets people know about how your project is governed. For example, it might discuss project roles and how decisions are made. 5 | 6 | 7 | 8 | Governance 9 | ========== 10 | 11 | This section describes the governance and leadership model of The Project. 12 | 13 | The foundations of Project governance are: 14 | 15 | - Openness & Transparency 16 | - Active Contribution 17 | - Institutional Neutrality 18 | 19 | Traditionally, Project leadership was provided by a BDFL (Wes McKinney) and 20 | subset of Contributors, called the Core Team, whose active and consistent 21 | contributions have been recognized by their receiving “commit rights” to the 22 | Project GitHub repositories. In general all Project decisions are made through 23 | consensus among the Core Team with input from the Community. The BDFL can, but 24 | rarely chooses to, override the Core Team and make a final decision on a 25 | matter. 26 | 27 | While this approach has served us well, as the Project grows and faces more 28 | legal and financial decisions and interacts with other institutions, we see a 29 | need for a more formal governance model. Moving forward The Project leadership 30 | will consist of a BDFL and Core Team. We view this governance model as the 31 | formalization of what we are already doing, rather than a change in direction. 32 | 33 | BDFL 34 | ---- 35 | 36 | The Project will have a BDFL (Benevolent Dictator for Life), who is currently 37 | Johnny Stevenson. As Dictator, the BDFL has the authority to make all final 38 | decisions for The Project. As Benevolent, the BDFL, in practice chooses to 39 | defer that authority to the consensus of the community discussion channels and 40 | the Core Team. It is expected, and in the past has been the case, that the BDFL 41 | will only rarely assert his/her final authority. Because it is rarely used, we 42 | refer to BDFL’s final authority as a “special” or “overriding” vote. When it 43 | does occur, the BDFL override typically happens in situations where there is a 44 | deadlock in the Core Team or if the Core Team ask the BDFL to make a decision 45 | on a specific matter. To ensure the benevolence of the BDFL, The Project 46 | encourages others to fork the project if they disagree with the overall 47 | direction the BDFL is taking. The BDFL is chair of the Core Team (see below) 48 | and may delegate his/her authority on a particular decision or set of decisions 49 | to any other Core Team Member at his/her discretion. 50 | 51 | The BDFL can appoint his/her successor, but it is expected that the Core Team 52 | would be consulted on this decision. If the BDFL is unable to appoint a 53 | successor (e.g. due to death or illness), the Core Team will choose a successor 54 | by voting with at least 2/3 of the Core Team members voting in favor of the 55 | chosen successor. At least 80% of the Core Team must participate in the 56 | vote. If no BDFL candidate receives 2/3 of the votes of the Core Team, the Core 57 | Team members shall propose the BDFL candidates to the Main NumFOCUS board, who 58 | will then make the final decision. 59 | 60 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | contribute@practical.li. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | Creative Commons Attribution ShareAlike 4.0 2 | 3 | CC-BY-SA-4.0 4 | 5 | [https://creativecommons.org/licenses/by-sa/4.0/legalcode.en](https://creativecommons.org/licenses/by-sa/4.0/legalcode.en) 6 | 7 | Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible. 8 | 9 | 10 | ## Attribution-ShareAlike 4.0 International 11 | 12 | By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. 13 | 14 | 15 | ## Section 1 – Definitions 16 | 17 | a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. 18 | 19 | b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. 20 | 21 | c. BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses , approved by Creative Commons as essentially the equivalent of this Public License. 22 | 23 | d. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. 24 | 25 | e. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. 26 | 27 | f. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. 28 | 29 | g. License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike. 30 | Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License. 31 | 32 | h. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. 33 | 34 | i. Licensor means the individual(s) or entity(ies) granting rights under this Public License. 35 | 36 | k. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. 37 | 38 | l. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. 39 | 40 | m. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. 41 | 42 | 43 | ## Section 2 – Scope 44 | 45 | a. License grant 46 | 47 | 1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: 48 | 49 | A. reproduce and Share the Licensed Material, in whole or in part; and 50 | 51 | B. produce, reproduce, and Share Adapted Material. 52 | 53 | 2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. 54 | 55 | 3. Term. The term of this Public License is specified in Section 6(a). 56 | 57 | 4. Media and formats; technical modifications allowed . The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material. 58 | 59 | 5. Downstream recipients. 60 | A. Offer from the Licensor – Licensed Material . Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. 61 | 62 | B. Additional offer from the Licensor – Adapted Material . Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply. 63 | 64 | C. No downstream restrictions . You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. 65 | 66 | 6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). 67 | 68 | b. Other rights. 69 | 70 | 1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. 71 | 72 | 2. Patent and trademark rights are not licensed under this Public License. 73 | 74 | 3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties. 75 | 76 | 77 | ## Section 3 – License Conditions. 78 | 79 | Your exercise of the Licensed Rights is expressly made subject to the following conditions. 80 | 81 | a. Attribution. 82 | 1. If You Share the Licensed Material (including in modified form), You must: 83 | 84 | A. retain the following if it is supplied by the Licensor with the Licensed Material: 85 | 86 | i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); 87 | 88 | ii. a copyright notice; 89 | 90 | ii. a notice that refers to this Public License; 91 | 92 | iv. a notice that refers to the disclaimer of warranties; 93 | 94 | v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; 95 | 96 | B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and 97 | 98 | C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. 99 | 100 | 2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. 101 | 102 | 3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. 103 | 104 | 105 | b. ShareAlike. 106 | 107 | In addition to the conditions in Section 3(a) , if You Share Adapted Material You produce, the following conditions also apply. 108 | 109 | 1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License. 110 | 111 | 2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material. 112 | 113 | 3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply. 114 | 115 | 116 | ## Section 4 – Sui Generis Database Rights 117 | 118 | Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: 119 | 120 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database; 121 | 122 | b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b) ; and 123 | 124 | c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. 125 | 126 | For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. 127 | 128 | 129 | ## Section 5 – Disclaimer of Warranties and Limitation of Liability 130 | 131 | a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You. 132 | 133 | b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You. 134 | 135 | c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. 136 | 137 | 138 | ## Section 6 – Term and Termination 139 | 140 | a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. 141 | 142 | b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: 143 | 144 | 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or 145 | 146 | 2. upon express reinstatement by the Licensor. 147 | 148 | For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. 149 | 150 | c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. 151 | 152 | d. Sections 1 , 5 , 6 , 7 , and 8 survive termination of this Public License. 153 | 154 | ## Section 7 – Other Terms and Conditions 155 | 156 | a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. 157 | 158 | b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. 159 | 160 | 161 | ## Section 8 – Interpretation 162 | 163 | a . For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. 164 | 165 | b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. 166 | 167 | c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. 168 | 169 | d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. 170 | 171 | --------------------------------------------------------------------------------