diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 67a4701..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,4 +0,0 @@ -# Code of Conduct - -The code of conduct for this repository is the -[PlasmaPy code of conduct](https://github.com/PlasmaPy/PlasmaPy/blob/master/CODE_OF_CONDUCT.md). diff --git a/CODE_OF_CONDUCT.rst b/CODE_OF_CONDUCT.rst new file mode 100644 index 0000000..487d6f5 --- /dev/null +++ b/CODE_OF_CONDUCT.rst @@ -0,0 +1,5 @@ +Code of Conduct +=============== + +The code of conduct for this repository is the `PlasmaPy code of +conduct `__. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 9e4779f..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,4 +0,0 @@ -# Contributing Guidelines - -Please see [Contributing to PlasmaPy](https://github.com/PlasmaPy/PlasmaPy/blob/master/CONTRIBUTING.md) -for guidelines on how to contribute. diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst new file mode 100644 index 0000000..fc24dd5 --- /dev/null +++ b/CONTRIBUTING.rst @@ -0,0 +1,6 @@ +Contributing Guidelines +======================= + +Please see `Contributing to PlasmaPy +`__ for guidelines on +how to contribute. diff --git a/LICENSE.md b/LICENSE.md deleted file mode 100644 index 3fe6c87..0000000 --- a/LICENSE.md +++ /dev/null @@ -1,9 +0,0 @@ -# Licenses - -Copyright (c) 2017-2018, PlasmaPy Developers. - -Except as otherwise noted, content in this repository is licensed -under a [Creative Commons Attribution 4.0 International (CC BY 4.0) -license](https://creativecommons.org/licenses/by/4.0/). - -[![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/) diff --git a/LICENSE.rst b/LICENSE.rst new file mode 100644 index 0000000..ab190d6 --- /dev/null +++ b/LICENSE.rst @@ -0,0 +1,10 @@ +Licenses +======== + +Copyright (c) 2017-2018, PlasmaPy Developers. + +Except as otherwise noted, content in this repository is licensed under +a `Creative Commons Attribution 4.0 International (CC BY 4.0) +license `__. + +`License: CC BY 4.0 `__ diff --git a/PLEP-0000.md b/PLEP-0000.md deleted file mode 100644 index a77906b..0000000 --- a/PLEP-0000.md +++ /dev/null @@ -1,47 +0,0 @@ -# PLEP-0000 - Index of PlasmaPy Enhancement Proposals - -| PLEP | 0 | -|-------------------|--------------------------| -| title | PLEP Index | -| author(s) | Nick Murphy | -| contact email | namurphy@cfa.harvard.edu | -| date created | 2017-09-28 | -| date last revised | 2017-11-14 | -| type | informational | - -This PLEP is an index of all PlasmaPy Enhancement Proposals, known as -PLEPs (to avoid confusion with Python Enhancement Proposals, or PEPs). - -## Informational PLEPs - -| number | title | author(s) | type | -|--------|-------|-----------|------| -| 0 | [Index of PLEPs](./PLEP-0000.md) | Nick Murphy | informational | -| 3 | [Members of Coordinating Committee](./PLEP-0003.md) | Nick Murphy | informational | - -## Accepted PLEPs - -| number | title | author(s) | type | -|--------|-------|-----------|------| -| | | | | - -## Declined PLEPs - -| number | title | author(s) | type | -|--------|-------|-----------|------| -| | | | | - -## PLEPs in preparation or under consideration - -| number | title | author(s) | type | -|--------|-------|-----------|------| -| 1 | [Purpose and Guidelines of PLEPs](./PLEP-0001.md) | Nick Murphy | process | -| 4 | [Licensing of PlasmaPy Repositories](./PLEP-0004) | Nick Murphy | process | -| 5 | [Versioning and Releases](./PLEP-0005.md) | Nick Murphy, Stuart Mumford| process | - -## Reserved PLEPs - -| number | title | author(s) | type | -|--------|-------|-----------|------| -| 2 | [PlasmaPy Organizational Structure](./PLEP-0002.md)| | process | -| 6 | [Data Structures](./PLEP-0006.md) | | standard | diff --git a/PLEP-0000.rst b/PLEP-0000.rst new file mode 100644 index 0000000..c7ca91f --- /dev/null +++ b/PLEP-0000.rst @@ -0,0 +1,85 @@ +PLEP-0000 - Index of PlasmaPy Enhancement Proposals +=================================================== + ++-------------------+--------------------------------------------------+ +| PLEP | 0 | ++===================+==================================================+ +| title | PLEP Index | ++-------------------+--------------------------------------------------+ +| author(s) | Nick Murphy | ++-------------------+--------------------------------------------------+ +| contact email | namurphy@cfa.harvard.edu | ++-------------------+--------------------------------------------------+ +| date created | 2017-09-28 | ++-------------------+--------------------------------------------------+ +| date last revised | 2018-05-22 | ++-------------------+--------------------------------------------------+ +| type | informational | ++-------------------+--------------------------------------------------+ + +This PLEP is an index of all PlasmaPy Enhancement Proposals, known as +PLEPs (to avoid confusion with Python Enhancement Proposals, or PEPs). + +Informational PLEPs +------------------- + ++--------+--------------------------+------------------+---------------+ +| number | title | author(s) | type | ++========+==========================+==================+===============+ +| 0 | `Index of PLEPs | Nick Murphy | informational | +| | <./PLEP-0000.rst>`__ | | | ++--------+--------------------------+------------------+---------------+ +| 3 | `Members of Coordinating | Nick Murphy | informational | +| | Committee | | | +| | <./PLEP-0003.rst>`__ | | | ++--------+--------------------------+------------------+---------------+ + +Accepted PLEPs +-------------- + ++--------+--------------------------+------------------+---------------+ +| number | title | author(s) | type | ++========+==========================+==================+===============+ +| | | | | ++--------+--------------------------+------------------+---------------+ + + +Declined PLEPs +-------------- + ++--------+--------------------------+------------------+---------------+ +| number | title | author(s) | type | ++========+==========================+==================+===============+ +| | | | | ++--------+--------------------------+------------------+---------------+ + +PLEPs in preparation or under consideration +------------------------------------------- + ++--------+--------------------------+------------------+---------------+ +| number | title | author(s) | type | ++========+==========================+==================+===============+ +| 1 | `Purpose and Guidelines | Nick Murphy | process | +| | of PLEPs | | | +| | <./PLEP-0001.rst>`__ | | | ++--------+--------------------------+------------------+---------------+ +| 4 | `Licensing of PlasmaPy | Nick Murphy | process | +| | Repositories | | | +| | <./PLEP-0004>`__ | | | ++--------+--------------------------+------------------+---------------+ +| 5 | `Versioning and Releases | Nick Murphy, | process | +| | <./PLEP-0005.rst>`__ | Stuart Mumford | | ++--------+--------------------------+------------------+---------------+ + +Reserved PLEPs +-------------- + ++--------+--------------------------+------------------+---------------+ +| number | title | author(s) | type | ++========+==========================+==================+===============+ +| 2 | `PlasmaPy Governance | | process | +| | <./PLEP-0002.rst>`__ | | | ++--------+--------------------------+------------------+---------------+ +| 6 | `Data Structures | | standard | +| | <./PLEP-0006.rst>`__ | | | ++--------+--------------------------+------------------+---------------+ diff --git a/PLEP-0001.rst b/PLEP-0001.rst new file mode 100644 index 0000000..478839b --- /dev/null +++ b/PLEP-0001.rst @@ -0,0 +1,228 @@ +PLEP-0001 – Purpose and Guidelines for PlasmaPy Enhancement Proposals +===================================================================== + ++-----------------------------------+-----------------------------------+ +| PLEP | 1 | ++===================================+===================================+ +| title | Purpose and Guidelines for | +| | PlasmaPy Enhancement Proposals | ++-----------------------------------+-----------------------------------+ +| author(s) | Nick Murphy | ++-----------------------------------+-----------------------------------+ +| contact email | namurphy@cfa.harvard.edu | ++-----------------------------------+-----------------------------------+ +| date created | 2017-11-13 | ++-----------------------------------+-----------------------------------+ +| date last revised | 2018-09-18 | ++-----------------------------------+-----------------------------------+ +| type | process | ++-----------------------------------+-----------------------------------+ +| status | in preparation | ++-----------------------------------+-----------------------------------+ + +Introduction +------------ + +**Pl**\ asmaPy **E**\ nhancement **P**\ roposals (PLEPs) are design +documents that provide information to the PlasmaPy community, describe +decision-making processes, or propose major changes or enhancements to +the code. PLEPs are intended to be the primary mechanism for proposing +major changes to the direction of PlasmaPy, collecting community +feedback, and documenting the reasoning behind major decisions. + +Types of PLEPs +-------------- + +There are three primary types of PLEPs: + +- A **standard PLEP** introduces and describes a major change to the + PlasmaPy code base. Standard PLEPs may describe a new feature or + subpackage, major changes to an existing package, or a backwards + incompatible change to the application programming interface (API). A + standard PLEP will start out as a proposal and eventually evolve into + a design document if accepted. + +- A **process PLEP** describes a new process or change to an existing + process in the management and coordination of PlasmaPy. Examples + include changes to PlasmaPy decision-making processes or management + structure, guidelines, or procedures. A process PLEP will start out + as a proposal and eventually evolve into a document on the governance + of PlasmaPy. + +- An **informational PLEP** provides information and does not describe + any changes. + +PLEP workflow +------------- + +A PLEP may come about when a contributor has an idea for how to improve +PlasmaPy, or when a Coordinating Committee member or subpackage +maintainer requests a PLEP to be written before a pull request is +accepted. The following subsections describe the procedure for PLEPs to +be created, submitted, decided upon, amended, and implemented. Anyone +who abides by the code of conduct may submit a PLEP. + +Creating a PLEP +~~~~~~~~~~~~~~~ + +Before writing a PLEP, it is generally advisable to bring up your idea +on the PlasmaPy +`Matrix `__/`Gitter `__ +channel and with the Coordinating Committee and/or subpackage +maintainers to get initial feedback. PLEPs are not necessary to +propose minor changes, which are often best `submitted as +issues `__ on the +`PlasmaPy GitHub repository `__. + +Each PLEP should contain a clear, concise, and well-organized description +of a new idea or proposal. PLEPs should generally focus on a single +topic. PLEPs should be written to be understandable to general members +of the PlasmaPy community rather than just core contributors and +Coordinating Committee members. However, technical details about the +implementation of a proposed change should be included when needed. + +Standard PLEPs are generally only needed for major improvements to the +code base such as significant restructuring of the code base or adoption +of a new standard. PLEPs are more likely to be needed for changes that +break backward compatibility, especially for stable subpackages in +development releases and after the release of version ``1.0.0``. PLEPs +are not needed for minor changes. + +All new PLEPs should begin with a copy of the PLEP template contained +within the PlasmaPy/PlasmaPy-PLEPs repository. This copy should be +renamed to ``PLEP-nnnn.rst`` where ``nnnn`` should be the lowest PLEP +number preceded by zeros that has not been tentatively or permanently +assigned by the Coordinating Committee. The template contains a +suggested outline that is most appropriate for a standard PLEP. Not +all sections included in the template are required for every PLEP, and +sometimes it is appropriate to create different sections. PLEPs are +written in the `reStructuredText +`__. +format. + + +Amending or superseding a PLEP +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +PLEPs may be amended or superseded as PlasmaPy grows and changes. + +If a topic is already covered by an existing PLEP, then it is often +appropriate to propose an amendment to that PLEP instead of writing a +new PLEP. Amendments should not substantially change the spirit of the +PLEP. Proposed amendments should update the “date last revised” category +in the header. Amendments to PLEPs go through the same process as newly +proposed PLEPs. + +When major changes to a PLEP are desired, then it is most appropriate to +propose a new PLEP to supersede the old PLEP. The pull request to +supersede a PLEP should change the “status” category in the header of +the old PLEP to “superseded by PLEP N” where N is the number of the new +PLEP not preceded by zeros. + +When PLEPs are amended or superseded, it is generally helpful to request +reviews from the authors of the original PLEP. + +Minor changes to a PLEP that do not affect its meaning or intent (e.g., +formatting changes, fixes to typos, updates to links, minor rewording to +improve clarity, and reversing cosmic ray bit flips) do not need to go +through the full review process, but do require approval by the +Coordinating Committee. + +Submitting a PLEP +~~~~~~~~~~~~~~~~~ + +All new PLEPs and amendments to PLEPs should be submitted as pull +requests into the PlasmaPy-PLEP repository. The pull request should be +created while the PLEP is being written to allow for greater +transparency and community input during the writing process. In this +case, the sponsor should comment on the pull request and inform the +Coordinating Committee when the proposed PLEP is ready for review. + +Review process +~~~~~~~~~~~~~~ + +When a new PLEP or an amendment to a PLEP is submitted, the Coordinating +Committee should appoint one of its members to be the PLEP’s editor. The +editor is responsible for aiding the sponsor by making sure that the +PLEP follows the accepted standard and facilitating communication +between the sponsor and the Coordinating Committee. The editor and +sponsor may be the same person. + +When the sponsor and editor decide that the proposal is ready for +broader discussion, then they should email the PlasmaPy list to +introduce the PLEP and request community feedback. The status of the +PLEP should be changed to “Discussion” at this time. Community +discussion should take place through normal communication channels +such as the Matrix/Gitter channel, on the pull request on GitHub, and +community meetings. Concerns that are raised should be constructive +and made in accordance with the PlasmaPy code of conduct. Important +points and relevant meeting minutes should be recorded as comments on +the GitHub pull request so that the community discussion may be +archived. During the discussion phase, the sponsor should revise the +PLEP in order to address concerns raised by the community. Others may +propose changes as well. The discussion should continue until a +general consensus among the PlasmaPy community has been reached. + +The Coordinating Committee is tasked with making the final decision on +the PLEP. A PLEP shall be accepted when at least two-thirds of the +Coordinating Committee votes in favor of the PLEP. The vote may be +taken in the discussion of the pull request on GitHub, over email, or +at a Coordinating Committee meeting where voting is recorded in the +minutes. + +PLEP status +~~~~~~~~~~~ + +The status of a standard or process PLEP may be any of the following: + +- **In preparation**: The PLEP is currently being written. Community + input is welcome during this phase so that concerns may be addressed + earlier rather than later. + +- **Discussion**: The PLEP is currently being considered and getting + community feedback before a decision has been made. This is the + default status for informational PLEPs that have been completed. + +- **Accepted**: The PLEP has been accepted and it will be assigned a + number and merged into the PlasmaPy/PlasmaPy-PLEPs repository. A + decision rationale for standard PLEPs should be drafted and added + to the PLEP by the sponsor of the PLEP or by someone appointed by + the Coordinating Committee. Features proposed in standard PLEPs may + now be implemented. Process PLEPs come into effect when accepted. + +- **Implemented**: The feature discussed in a standard PLEP has been + fully implemented and merged into the main repository. At least half + of the Coordinating Committee must agree that the implementation + (including documentation and tests) is complete. A summary of the + implementation process should be added to the PLEP when this status + is reached. This summary should include links to the issues and pull + requests associated with this PLEP that were created after the PLEP + was accepted. + +- **Declined**: The community and Coordinating Committee decided + against a proposed PLEP. A decision rationale should be provided by + the sponsor, editor, and/or Coordinating Committee. The PLEP should + still be assigned a number and merged into the main repository. A + future PLEP may supersede this decision. + +- **Superseded**: THe PLEP is no longer in effect and has been replaced + by another PLEP. + +Informational PLEPs that are being written should have a status of **in +preparation**, and **informational** when it is sufficiently complete. +Informational PLEPs may also have a status of **outdated** when the some +of the information is out-of-date and needs updating, or **obsolete** +when the PLEP is no longer relevant. + +Archiving PLEPs +~~~~~~~~~~~~~~~ + +When a PLEP has been decided upon and merged into the repository, the +Coordinating Committee will upload the PLEP to `Zenodo +`__ for permanent archiving and so that the PLEP +may get a Digital Object Identifier (DOI) and therefore be +citable. The PLEP should be included as part of the `PlasmaPy +Community on Zenodo `__. The +title should be of the form “PlasmaPy Enhancement Proposal *number*: +*title*”. All PLEPs on Zenodo should be versioned to allow for +eventual amendments and revisions. diff --git a/PLEP-0003.md b/PLEP-0003.md deleted file mode 100644 index f11108a..0000000 --- a/PLEP-0003.md +++ /dev/null @@ -1,30 +0,0 @@ -# PLEP-0003 -- Members of Coordinating Committee - -| PLEP | 3 | -|-------------------|------------------------------------------| -| title | Members of Coordinating Committee | -| author(s) | Nick Murphy | -| contact email | namurphy@cfa.harvard.edu | -| date created | 2017-09-29 | -| date last revised | 2017-11-13 | -| type | informational | -| status | discussion | - -## Abstract - -This document lists the membership of the PlasmaPy Coordinating -Committee. - -## Coordinating Committee Membership - -The PlasmaPy Coordinating Committee includes the following members: - -| Name | Institution | -|-------------------|---------------------------------------------| -| Drew Leonard | Aperio Software | -| Nick Murphy | Harvard-Smithsonian Center for Astrophysics | -| Tulasi Parashar | University of Delaware | -| Dominik Stańczak | Warsaw University of Technology | - -The institutions of Coordinating Committee members are included for -identification purposes only. diff --git a/PLEP-0003.rst b/PLEP-0003.rst new file mode 100644 index 0000000..c35a83e --- /dev/null +++ b/PLEP-0003.rst @@ -0,0 +1,47 @@ + +PLEP-0003 – Members of Coordinating Committee +============================================= + ++-------------------+-----------------------------------+ +| PLEP | 3 | ++===================+===================================+ +| title | Members of Coordinating Committee | ++-------------------+-----------------------------------+ +| author(s) | Nick Murphy | ++-------------------+-----------------------------------+ +| contact email | namurphy@cfa.harvard.edu | ++-------------------+-----------------------------------+ +| date created | 2017-09-29 | ++-------------------+-----------------------------------+ +| date last revised | 2017-11-13 | ++-------------------+-----------------------------------+ +| type | informational | ++-------------------+-----------------------------------+ +| status | discussion | ++-------------------+-----------------------------------+ + +Abstract +-------- + +This document lists the membership of the PlasmaPy Coordinating +Committee. + +Coordinating Committee Membership +--------------------------------- + +The PlasmaPy Coordinating Committee includes the following members: + ++------------------+---------------------------------------------+------------------+ +| Name | Institution | GitHub nickname | ++==================+=============================================+==================+ +| Drew Leonard | Aperio Software | @SolarDrew | ++------------------+---------------------------------------------+------------------+ +| Nick Murphy | Harvard-Smithsonian Center for Astrophysics | @namurphy | ++------------------+---------------------------------------------+------------------+ +| Tulasi Parashar | University of Delaware | @tulasinandan | ++------------------+---------------------------------------------+------------------+ +| Dominik Stańczak | Warsaw University of Technology | @StanczakDominik | ++------------------+---------------------------------------------+------------------+ + +The institutions of Coordinating Committee members are included for +identification purposes only. diff --git a/PLEP-template.md b/PLEP-template.md deleted file mode 100644 index 1ba1dad..0000000 --- a/PLEP-template.md +++ /dev/null @@ -1,53 +0,0 @@ -# PLEP-*number* -- *PLEP title* - -| PLEP | number | -|---------------|------------------------------| -| title | PLEP Title | -| author(s) | | -| contact email | me@myemail.org | -| date created | YYYY-MM-DD | -| date last revised | YYYY-MM-DD | -| type | process, standard, informational | -| status | discussion, accepted, declined | - -# Abstract - -*Briefly describe this PLEP in a paragraph, including a statement of -the problem that this PLEP addresses.* - -# Detailed Description - -*Provide an extended description of the problem and the proposed -changes, including usage examples when needed.* - -# Implementation - -*Describe the steps necessary to implement this PLEP, if necessary.* - -# Issues, Pull Requests, and Branches - -*Provide repository links related to this PLEP, and include -descriptions.* - -# Backward Compatibility - -*State whether or not this PLEP will maintain backward compatibility -and describe the proposed changes, if necessary. Backward -compatibility does not need to be maintained between development -releases (with a major version number of zero). Starting with version -1.0, backward incompatible changes can only happen when the major -version number is incremented.* - -# Alternatives - -*Summarize alternative possibilities to address (or not address) the -problem described in this PLEP, if necessary.* - -# Decision Rationale - -*Summarize the discussion on this PLEP and describe the reasoning -behind the decision, if necessary.* - -*Not all PLEPs require all of these sections, and occasionally -additional sections may be necessary. Emphasized text should be -deleted.* diff --git a/PLEP-template.rst b/PLEP-template.rst new file mode 100644 index 0000000..a179338 --- /dev/null +++ b/PLEP-template.rst @@ -0,0 +1,69 @@ +PLEP-\ *number* – *PLEP title* +============================== + ++-------------------+----------------------------------+ +| PLEP | number | ++===================+==================================+ +| title | PLEP Title | ++-------------------+----------------------------------+ +| author(s) | | ++-------------------+----------------------------------+ +| contact email | me@myemail.org | ++-------------------+----------------------------------+ +| date created | YYYY-MM-DD | ++-------------------+----------------------------------+ +| date last revised | YYYY-MM-DD | ++-------------------+----------------------------------+ +| type | process, standard, informational | ++-------------------+----------------------------------+ +| status | discussion, accepted, declined | ++-------------------+----------------------------------+ + +Abstract +======== + +*Briefly describe this PLEP in a paragraph, including a statement of the +problem that this PLEP addresses.* + +Detailed Description +==================== + +*Provide an extended description of the problem and the proposed +changes, including usage examples when needed.* + +Implementation +============== + +*Describe the steps necessary to implement this PLEP, if necessary.* + +Issues, Pull Requests, and Branches +=================================== + +*Provide repository links related to this PLEP, and include +descriptions.* + +Backward Compatibility +====================== + +*State whether or not this PLEP will maintain backward compatibility and +describe the proposed changes, if necessary. Backward compatibility does +not need to be maintained between development releases (with a major +version number of zero). Starting with version 1.0, backward +incompatible changes can only happen when the major version number is +incremented.* + +Alternatives +============ + +*Summarize alternative possibilities to address (or not address) the +problem described in this PLEP, if necessary.* + +Decision Rationale +================== + +*Summarize the discussion on this PLEP and describe the reasoning behind +the decision, if necessary.* + +*Not all PLEPs require all of these sections, and occasionally +additional sections may be necessary. Emphasized text should be +deleted.* diff --git a/README.md b/README.md deleted file mode 100644 index fa35aec..0000000 --- a/README.md +++ /dev/null @@ -1,6 +0,0 @@ -# PlasmaPy Enhancement Proposals - -[![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/) - -This repository contains PlasmaPy Enhancement Proposals (PLEPs). -[PLEP 0](PLEP-0000.md) contains an index of PLEPs. diff --git a/README.rst b/README.rst new file mode 100644 index 0000000..06c1b9a --- /dev/null +++ b/README.rst @@ -0,0 +1,7 @@ +PlasmaPy Enhancement Proposals +============================== + +`License: CC BY 4.0 `__ + +This repository contains PlasmaPy Enhancement Proposals (PLEPs). `PLEP +0 `__ contains an index of PLEPs. diff --git a/licenses/SunPy_SPE_license.md b/licenses/SunPy_SPE_license.md new file mode 100644 index 0000000..78bb1a9 --- /dev/null +++ b/licenses/SunPy_SPE_license.md @@ -0,0 +1,165 @@ +# SunPy Proposals for Enhancement + +Unless otherwise noted all the material in this repository is copyright the +SunPy developers and is distributed subject to the terms of the Creative Commons +Attribution 4.0 International Public License which is reproduced +below. + + +# Attribution 4.0 International + +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. + +### Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses. + +* __Considerations for licensors:__ Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. [More considerations for licensors](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensors). + +* __Considerations for the public:__ By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. [More considerations for the public](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensees). + +## Creative Commons Attribution 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution 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. + +### Section 1 – Definitions. + +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. + +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. + +c. __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. + +d. __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. + +e. __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. + +f. __Licensed Material__ means the artistic or literary work, database, or other material to which the Licensor applied this Public License. + +g. __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. + +h. __Licensor__ means the individual(s) or entity(ies) granting rights under this Public License. + +i. __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. + +j. __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. + +k. __You__ means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. + +### Section 2 – Scope. + +a. ___License grant.___ + + 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: + + A. reproduce and Share the Licensed Material, in whole or in part; and + + B. produce, reproduce, and Share Adapted Material. + + 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. + + 3. __Term.__ The term of this Public License is specified in Section 6(a). + + 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. + + 5. __Downstream recipients.__ + + 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. + + B. __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. + + 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). + +b. ___Other rights.___ + + 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. + + 2. Patent and trademark rights are not licensed under this Public License. + + 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. + +### Section 3 – License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the following conditions. + +a. ___Attribution.___ + + 1. If You Share the Licensed Material (including in modified form), You must: + + A. retain the following if it is supplied by the Licensor with the Licensed Material: + + 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); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of warranties; + + v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; + + B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and + + 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. + + 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. + + 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. + + 4. If You Share Adapted Material You produce, the Adapter's License You apply must not prevent recipients of the Adapted Material from complying with this Public License. + +### Section 4 – Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: + +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; + +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; and + +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. + +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. + +### Section 5 – Disclaimer of Warranties and Limitation of Liability. + +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.__ + +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.__ + +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. + +### Section 6 – Term and Termination. + +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. + +b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or + + 2. upon express reinstatement by the Licensor. + + 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. + +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. + +d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License. + +### Section 7 – Other Terms and Conditions. + +a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. + +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. + +### Section 8 – Interpretation. + +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. + +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. + +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. + +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. + +> Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at [creativecommons.org/policies](http://creativecommons.org/policies), Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses. +> +> Creative Commons may be contacted at creativecommons.org \ No newline at end of file