├── LICENSE.md ├── README.md ├── code-of-conduct.md ├── governance.md ├── people.md ├── projectlicense.md └── teams.md /LICENSE.md: -------------------------------------------------------------------------------- 1 | # Creative Commons CC0 License 2 | 3 | ## Statement of Purpose 4 | The laws of most jurisdictions throughout the world 5 | automatically confer exclusive Copyright and Related Rights 6 | (defined below) upon the creator and subsequent owner(s) (each 7 | and all, an "owner") of an original work of authorship and/or 8 | a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights 11 | to a Work for the purpose of contributing to a commons of 12 | creative, cultural and scientific works ("Commons") that the 13 | public can reliably and without fear of later claims of 14 | infringement build upon, modify, incorporate in other works, 15 | reuse and redistribute as freely as possible in any form 16 | whatsoever and for any purposes, including without limitation 17 | commercial purposes. These owners may contribute to the 18 | Commons to promote the ideal of a free culture and the further 19 | production of creative, cultural and scientific works, or to 20 | gain reputation or greater distribution for their Work in part 21 | through the use and efforts of others. 22 | 23 | For these and/or other purposes and motivations, and 24 | without any expectation of additional consideration or 25 | compensation, the person associating CC0 with a Work (the 26 | "Affirmer"), to the extent that he or she is an owner of 27 | Copyright and Related Rights in the Work, voluntarily elects 28 | to apply CC0 to the Work and publicly distribute the Work 29 | under its terms, with knowledge of his or her Copyright and 30 | Related Rights in the Work and the meaning and intended legal 31 | effect of CC0 on those rights. 32 | 33 | **1. Copyright and Related Rights.** 34 | A Work made available under CC0 may be protected by 35 | copyright and related or neighboring rights ("Copyright and 36 | Related Rights"). Copyright and Related Rights include, but 37 | are not limited to, the following: 38 | 39 | 40 | 1. the right to reproduce, adapt, distribute, perform, 41 | display, communicate, and translate a Work; 42 | 2. moral rights retained by the original author(s) and/or 43 | performer(s); 44 | 3. publicity and privacy rights pertaining to a person's 45 | image or likeness depicted in a Work; 46 | 4. rights protecting against unfair competition in regards 47 | to a Work, subject to the limitations in paragraph 4(a), 48 | below; 49 | 5. rights protecting the extraction, dissemination, use and 50 | reuse of data in a Work; 51 | 6. database rights (such as those arising under Directive 52 | 96/9/EC of the European Parliament and of the Council of 11 53 | March 1996 on the legal protection of databases, and under 54 | any national implementation thereof, including any amended 55 | or successor version of such directive); and 56 | 7. other similar, equivalent or corresponding rights 57 | throughout the world based on applicable law or treaty, and 58 | any national implementations thereof. 59 | 60 | **2. Waiver.** To the greatest extent 61 | permitted by, but not in contravention of, applicable law, 62 | Affirmer hereby overtly, fully, permanently, irrevocably and 63 | unconditionally waives, abandons, and surrenders all of 64 | Affirmer's Copyright and Related Rights and associated claims 65 | and causes of action, whether now known or unknown (including 66 | existing as well as future claims and causes of action), in 67 | the Work (i) in all territories worldwide, (ii) for the 68 | maximum duration provided by applicable law or treaty 69 | (including future time extensions), (iii) in any current or 70 | future medium and for any number of copies, and (iv) for any 71 | purpose whatsoever, including without limitation commercial, 72 | advertising or promotional purposes (the "Waiver"). Affirmer 73 | makes the Waiver for the benefit of each member of the public 74 | at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be 76 | subject to revocation, rescission, cancellation, termination, 77 | or any other legal or equitable action to disrupt the quiet 78 | enjoyment of the Work by the public as contemplated by 79 | Affirmer's express Statement of Purpose. 80 | 81 | **3. Public License Fallback.** Should any 82 | part of the Waiver for any reason be judged legally invalid or 83 | ineffective under applicable law, then the Waiver shall be 84 | preserved to the maximum extent permitted taking into account 85 | Affirmer's express Statement of Purpose. In addition, to the 86 | extent the Waiver is so judged Affirmer hereby grants to each 87 | affected person a royalty-free, non transferable, non 88 | sublicensable, non exclusive, irrevocable and unconditional 89 | license to exercise Affirmer's Copyright and Related Rights 90 | in the Work (i) in all territories worldwide, (ii) for the 91 | maximum duration provided by applicable law or treaty 92 | (including future time extensions), (iii) in any current or 93 | future medium and for any number of copies, and (iv) for any 94 | purpose whatsoever, including without limitation commercial, 95 | advertising or promotional purposes (the "License"). The 96 | License shall be deemed effective as of the date CC0 was 97 | applied by Affirmer to the Work. Should any part of the 98 | License for any reason be judged legally invalid or 99 | ineffective under applicable law, such partial invalidity or 100 | ineffectiveness shall not invalidate the remainder of the 101 | License, and in such case Affirmer hereby affirms that he or 102 | she will not (i) exercise any of his or her remaining 103 | Copyright and Related Rights in the Work or (ii) assert any 104 | associated claims and causes of action with respect to the 105 | Work, in either case contrary to Affirmer's express Statement 106 | of Purpose. 107 | 108 | **4. Limitations and Disclaimers.** 109 | 110 | 1. No trademark or patent rights held by Affirmer are 111 | waived, abandoned, surrendered, licensed or otherwise 112 | affected by this document. 113 | 2. Affirmer offers the Work as-is and makes no 114 | representations or warranties of any kind concerning the 115 | Work, express, implied, statutory or otherwise, including 116 | without limitation warranties of title, merchantability, 117 | fitness for a particular purpose, non infringement, or the 118 | absence of latent or other defects, accuracy, or the present 119 | or absence of errors, whether or not discoverable, all to 120 | the greatest extent permissible under applicable law. 121 | 3. Affirmer disclaims responsibility for clearing rights of 122 | other persons that may apply to the Work or any use thereof, 123 | including without limitation any person's Copyright and 124 | Related Rights in the Work. Further, Affirmer disclaims 125 | responsibility for obtaining any necessary consents, 126 | permissions or other rights required for any use of the 127 | Work. 128 | 4. Affirmer understands and acknowledges that Creative 129 | Commons is not a party to this document and has no duty or 130 | obligation with respect to this CC0 or use of the Work. 131 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # pandas Project Governance 2 | 3 | The purpose of this repository is to formalize the governance process that the 4 | pandas project has used informally since its inception in 2008. This document 5 | clarifies how decisions are made and how the various elements of our community 6 | interact, including the relationship between open source collaborative 7 | development and work that may be funded by for-profit or non-profit entities. 8 | 9 | ## Table of Contents 10 | 11 | * [Main Governance Document](governance.md) 12 | * [Current People](people.md) 13 | - [Code of Conduct](code-of-conduct.md) 14 | 15 | ## License of Governance Documents 16 | 17 | To the extent possible under law, pandas Project has waived all copyright and 18 | related or neighboring rights to the pandas Project Governance documents, in 19 | accordance with the Creative Commons [CC0 20 | license](http://creativecommons.org/publicdomain/zero/1.0/). This work is 21 | published from the United States. See the LICENSE.md file in this repository 22 | for details. 23 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Contributor Code of Conduct 2 | 3 | As contributors and maintainers of this project, and in the interest of 4 | fostering an open and welcoming community, we pledge to respect all people who 5 | contribute through reporting issues, posting feature requests, updating 6 | documentation, submitting pull requests or patches, and other activities. 7 | 8 | We are committed to making participation in this project a harassment-free 9 | experience for everyone, regardless of level of experience, gender, gender 10 | identity and expression, sexual orientation, disability, personal appearance, 11 | body size, race, ethnicity, age, religion, or nationality. 12 | 13 | Examples of unacceptable behavior by participants include: 14 | 15 | * The use of sexualized language or imagery 16 | * Personal attacks 17 | * Trolling or insulting/derogatory comments 18 | * Public or private harassment 19 | * Publishing other's private information, such as physical or electronic 20 | addresses, without explicit permission 21 | * Other unethical or unprofessional conduct 22 | 23 | Project maintainers have the right and responsibility to remove, edit, or 24 | reject comments, commits, code, wiki edits, issues, and other contributions 25 | that are not aligned to this Code of Conduct, or to ban temporarily or 26 | permanently any contributor for other behaviors that they deem inappropriate, 27 | threatening, offensive, or harmful. 28 | 29 | By adopting this Code of Conduct, project maintainers commit themselves to 30 | fairly and consistently applying these principles to every aspect of managing 31 | this project. Project maintainers who do not follow or enforce the Code of 32 | Conduct may be permanently removed from the project team. 33 | 34 | This Code of Conduct applies both within project spaces and in public spaces 35 | when an individual is representing the project or its community. 36 | 37 | A working group of community members is committed to promptly addressing any 38 | reported issues. The working group is made up of pandas contributors and users. 39 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 40 | reported by contacting the working group by e-mail (pandas-coc@googlegroups.com). 41 | Messages sent to this e-mail address will not be publicly visible but only to 42 | the working group members. The working group currently includes 43 | 44 | - Safia Abdalla 45 | - Tom Augspurger 46 | - Joris Van den Bossche 47 | - Camille Scott 48 | - Nathaniel Smith 49 | 50 | All complaints will be reviewed and investigated and will result in a response 51 | that is deemed necessary and appropriate to the circumstances. Maintainers are 52 | obligated to maintain confidentiality with regard to the reporter of an 53 | incident. 54 | 55 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 56 | version 1.3.0, available at 57 | [http://contributor-covenant.org/version/1/3/0/][version], 58 | and the [Swift Code of Conduct][swift]. 59 | 60 | [homepage]: http://contributor-covenant.org 61 | [version]: http://contributor-covenant.org/version/1/3/0/ 62 | [swift]: https://swift.org/community/#code-of-conduct 63 | 64 | -------------------------------------------------------------------------------- /governance.md: -------------------------------------------------------------------------------- 1 | # _pandas_ Project Governance and Decision-Making 2 | 3 | The purpose of this document is to formalize the governance process used by the pandas 4 | project in both ordinary and extraordinary situations, and to clarify how decisions are 5 | made and how the various elements of our community interact, including the relationship 6 | between open source collaborative development and work that may be funded by for-profit 7 | or non-profit entities. 8 | 9 | 10 | The official version of this document, along with a list of 11 | individuals and institutions in the roles defined in the governance 12 | section below, is contained in The Project Governance Repository at: 13 | 14 | [https://github.com/pandas-dev/pandas-governance](https://github.com/pandas-dev/pandas-governance) 15 | 16 | ## Summary 17 | 18 | _pandas_ is a community-owned and community-run project. Major technical changes to the 19 | project are managed by the PDEP (pandas enhancement proposal) process, described in 20 | PDEP-1 at https://pandas.pydata.org/pdeps/0001-purpose-and-guidelines.html . Because of 21 | the large scope of the project, the project is managed by a number of different Teams, 22 | who each have responsibilities for different aspects of the project. A Steering 23 | Committee, elected on an annual basis, coordinates the activities of the different 24 | Teams. 25 | 26 | ## The Project 27 | 28 | The pandas Project (The Project) is an open source software project sponsored 29 | by the 501(c)3 NumFOCUS Foundation. NumFOCUS provides pandas with fiscal, legal, and 30 | administrative support to help ensure the health and sustainability of the project. 31 | The goal of The Project is to develop open 32 | source software that is the fundamental high-level building block for doing practical, 33 | real world data analysis in Python. Additionally, it has the broader goal of becoming 34 | the most powerful and flexible open source data analysis / manipulation tool available 35 | in any language. The Software developed by 36 | The Project is released under the BSD (or similar) open source license, 37 | developed openly and hosted on public GitHub repositories under the [`pandas-dev` 38 | GitHub organization](https://github.com/pandas-dev). Examples of Project Software 39 | include the main pandas code repository, pandas website, and the pandas-stubs library. 40 | 41 | The Project is developed by a team of distributed developers, called 42 | Contributors. Contributors are individuals who have contributed code, 43 | documentation, designs or other work to one or more Project repositories. 44 | Anyone can be a Contributor. Contributors can be affiliated with any legal 45 | entity or none. Contributors participate in the project by submitting, 46 | reviewing and discussing GitHub Pull Requests and Issues and participating in 47 | open and public Project discussions on GitHub, mailing lists, and 48 | other channels. The foundation of Project participation is openness and 49 | transparency. 50 | 51 | The Project Community consists of all Contributors and Users of the Project. 52 | Contributors work on behalf of and are responsible to the larger Project 53 | Community and we strive to keep the barrier between Contributors and Users as 54 | low as possible. 55 | 56 | The Project is formally affiliated with the 501(c)3 NumFOCUS Foundation 57 | ([https://numfocus.org](https://numfocus.org)), which serves as its fiscal 58 | sponsor, may hold project trademarks and other intellectual property, helps 59 | manage project donations and acts as a parent legal entity. NumFOCUS is the 60 | only legal entity that has a formal relationship with the project (see 61 | Institutional Partners section below). 62 | 63 | ## Governance 64 | 65 | This section describes the governance and leadership model of The Project. 66 | 67 | The foundations of Project governance are: 68 | 69 | - Openness & Transparency 70 | - Active Contribution 71 | - Institutional Neutrality 72 | 73 | To manage the project, there are different Teams that each have responsibility for 74 | specific aspects of the project. Collectively, the members of all Teams are referred to 75 | as _Stewards_ of the project. Individuals may be members of more than one Team. 76 | 77 | ## Steering Committee 78 | 79 | The role of the _pandas_ Steering Committee is to coordinate the activities of the 80 | different Teams and to ensure that different policies and procedures are carried out in 81 | a consistent manner. The Steering Committee has no routine decision-making authority, 82 | except as detailed herein, although in exceptional circumstances it may be called upon 83 | from time to time to make decisions that are in the best interest of The Project as a 84 | whole. The Steering Committee will itself decide when a circumstance is exceptional. 85 | The Steering Committee may not override a PDEP. When the Steering Committee meets to 86 | discuss an issue, the members of the Steering Committee are responsible for soliciting 87 | input from members of the relevant Teams. 88 | 89 | The Steering Committee may create a working group to consider changes to the governance 90 | model described in this document, including the creation of new Teams that support the 91 | goals of The Project. Changes to the governance model will require a voting process and 92 | approval equivalent to the process described in PDEP-1, with the exception that all 93 | Stewards are eligible to vote. 94 | 95 | The Steering Committee may appoint temporary working groups to work on issues, such as 96 | governance, that fall outside the scope of responsibilities for the existing Teams. 97 | 98 | The ideal composition of the Steering Committee consists of 5 people. The Steering 99 | Committee will be chosen via an approval voting process from a slate of nominees, 100 | meaning that each person who is eligible to vote may vote for more than one candidate 101 | from the slate. All members of each Team, except the Code of Conduct Team, are 102 | eligible to vote. 103 | 104 | ### Initial Election 105 | 106 | The initial slate for the Steering Committee election will consist of 5 or more 107 | candidates who volunteer to be on the slate of candidates for the initial Steering 108 | Committee. For the initial election, the members of the previous _pandas_ core team 109 | will vote via an approval voting process. The top 5 candidates receiving votes 110 | will then become members of the initial Steering Committee. 111 | 112 | ### Subsequent Elections 113 | 114 | Subsequent changes to the membership of the Steering Committee will occur towards the 115 | end of each calendar year. By October 31 of each year, each member of the Steering 116 | Committee will be asked if they would like to continue in that role. If any member 117 | decides to step down from the Steering Committee, new volunteers will be solicited from 118 | the group of stewards by the Steering Committee. Those new volunteers, along with any 119 | current Steering Committee members who wish to remain on the Steering Committee, 120 | will then be on a 121 | slate for an election that will occur by November 15 of that year. For each year after 122 | the initial election, the current Steering Committee members plus any new volunteers on 123 | the slate will be elected via approval voting, with the top 5 candidates elected as 124 | Steering Committee members for the subsequent year. 125 | 126 | The terms of each member of the Steering Committee are from January 127 | 1 to December 31 of each calendar year, and Steering Committee members may serve for 128 | any number of multiple terms, provided that they are re-elected in each annual election. 129 | 130 | 131 | ## Teams 132 | 133 | Each Team has defined responsibilities for different aspects of the project. As a 134 | general rule, an Individual Contributor can be nominated by a member of a Team to become 135 | a member of that Team, and the Team must agree to admitting that person to 136 | the Team, since every Team member becomes a Steward of the Project. If a member of a 137 | Team is inactive for more than one year, the active members of the Team 138 | may decide to remove that 139 | person from the Team. 140 | Decisions about admittance or removal of Team members should be made by the Team as a 141 | whole, as long as there are no objections from active Team members. 142 | 143 | Each Team will maintain its own private mailing list if the Team 144 | deems it to be necessary. There will also be a mailing list consisting of all Stewards 145 | of all Teams. 146 | 147 | Each Team has specific responsibilities as well as authorities over permissions, as 148 | defined below. In addition, specific criteria are used by Team Members to guide 149 | decisions on adding new Members to the Team. 150 | 151 | The Steering Committee has the authority to change the responsibilities of individual 152 | Teams, remove or consolidate Teams. 153 | 154 | The description of each Team can be found in https://github.com/pandas-dev/pandas-governance/teams.md . 155 | 156 | ### Conflict of interest 157 | 158 | It is expected that all Stewards will be employed at a wide 159 | range of companies, universities and non-profit organizations. Because of this, 160 | it is possible that Stewards will have conflict of interests. Such conflict of 161 | interests include, but are not limited to: 162 | 163 | - Financial interests, such as investments, employment or contracting work, 164 | outside of The Project that may influence their work on The Project. 165 | - Access to proprietary information of their employer that could potentially 166 | leak into their work with the Project. 167 | 168 | All Stewards shall disclose to the Steering Committee 169 | any conflict of interest they may have. Stewards with a conflict of 170 | interest in a particular issue may participate in Team discussions on that 171 | issue, but must recuse themselves from voting on the issue, if such 172 | a vote is necessary. If a conflict of interest is not disclosed and later uncovered, 173 | it will be left to the Steering Committee to decide how to handle the lack of disclosure 174 | on a case-by-case basis 175 | 176 | ### Private communications of the Steering Committee 177 | 178 | To the maximum extent possible, Team discussions and activities will be 179 | public and done in collaboration and discussion with the Project Contributors 180 | and Community. The Steering Committee will have a private mailing list that will be used 181 | sparingly and only when a specific matter requires privacy. When private 182 | communications and decisions are needed, the Steering Committee will do its best to 183 | summarize those to the Community after eliding personal/private/sensitive 184 | information that should not be posted to the public internet. 185 | 186 | ## Institutional Partners and Funding 187 | 188 | The Stewards are the primary leaders of the project. No outside 189 | institution, individual or legal entity has the ability to own, control, usurp 190 | or influence the project other than by participating in the Project as 191 | Contributors and Stewards. However, because institutions can be an important 192 | funding mechanism for the project, it is important to formally acknowledge 193 | institutional participation in the project. These are Institutional Partners. 194 | An Institutional Contributor is any individual Project Contributor who 195 | contributes to the project as part of their official duties at an Institutional 196 | Partner. Likewise, an Institutional Steward is any Steward 197 | who contributes to the project as part of their official duties at an 198 | Institutional Partner. 199 | With these definitions, an Institutional Partner is any recognized legal entity 200 | in the United States or elsewhere that employs at least one Institutional 201 | Contributor or Institutional Steward. Institutional Partners can be 202 | for-profit or non-profit entities. 203 | Institutions become eligible to become an Institutional Partner by employing 204 | individuals who actively contribute to The Project as part of their official 205 | duties. To state this another way, the only way for an Institutional Partner to 206 | influence the project is by actively contributing to the open development of 207 | the project, on equal terms with any other member of the community of 208 | Contributors and Stewards. Merely using Project Software in 209 | an institutional context does not allow an entity to become an Institutional 210 | Partner. Financial gifts, which are recognized on the _pandas_ web site, 211 | do not enable an entity to become an Institutional 212 | Partner. Once an institution becomes eligible for Institutional Partnership, 213 | the Steering Committee must nominate and approve the Partnership, after soliciting 214 | input from the Stewards. 215 | If at some point an existing Institutional Partner stops having any contributing 216 | employees, then a one year grace period commences. If at the end of this one year period 217 | they continue to not have any contributing employees, then their Institutional 218 | Partnership will lapse, and resuming it will require going through the normal process 219 | for new Partnerships. 220 | 221 | An Institutional Partner is free to pursue funding for their work on The 222 | Project through any legal means. This could involve a non-profit organization 223 | raising money from private foundations and donors or a for-profit company 224 | building proprietary products and services that leverage Project Software and 225 | Services. Funding acquired by Institutional Partners to work on The Project is 226 | called Institutional Funding. However, no funding obtained by an Institutional 227 | Partner can override the Steering Committee. If a Partner has funding 228 | to do pandas work and the Steering Committee decides to not pursue that work as a 229 | project, the Partner is free to pursue it on their own. However in this 230 | situation, that part of the Partner’s work will not be under the pandas 231 | umbrella and cannot use the Project trademarks in a way that suggests a formal 232 | relationship. 233 | 234 | Institutional Partner benefits are: 235 | 236 | - Acknowledged on the _pandas_ website, in talks and T-shirts. 237 | - Ability to acknowledge their own funding sources on the _pandas_ websites, in 238 | talks and T-shirts. 239 | - Ability to influence the project through the participation of their Steward. 240 | 241 | A list of current Institutional Partners is maintained at the page 242 | https://pandas.pydata.org/about/sponsors.html . 243 | 244 | 245 | ## Document History 246 | 247 | Original Version: February 15, 2016 248 | Complete Revision: ???, 2024 249 | 250 | ## Acknowledgments 251 | 252 | Portions of this document were adapted from the [NumPy governance document](https://numpy.org/doc/stable/dev/governance/governance.html). 253 | 254 | ## License 255 | 256 | To the extent possible under law, the authors have waived all copyright and related or 257 | neighboring rights to the pandas project governance and decision-making document, 258 | as per the [CC-0 public domain dedication / license](https://creativecommons.org/publicdomain/zero/1.0/). 259 | 260 | -------------------------------------------------------------------------------- /people.md: -------------------------------------------------------------------------------- 1 | # pandas People 2 | 3 | ## Benevolent Dictator for Life 4 | 5 | Wes McKinney is the Benevolent Dictator for Life (BDFL). 6 | 7 | ## Project Core Team 8 | 9 | - Tom Augspurger 10 | - William Ayd 11 | - Chris Bartak 12 | - Pietro Battiston 13 | - Phillip Cloud 14 | - Marc Garcia 15 | - Andy Hayden 16 | - Masaaki Horikoshi (@sinhrks) 17 | - Simon Hawkins 18 | - Stephan Hoyer 19 | - Wes McKinney 20 | - Brock Mendel 21 | - Terji Petersen 22 | - Jeff Reback 23 | - Matthew Roeschke 24 | - Jeremy Schendel 25 | - Chang She 26 | - Joris Van den Bossche 27 | - G. Young 28 | 29 | ## Project NumFOCUS Subcommittee 30 | 31 | - Phillip Cloud 32 | - Stephan Hoyer 33 | - Wes McKinney 34 | - Jeff Reback 35 | - Joris Van den Bossche 36 | - Tom Augspurger 37 | 38 | ## Code of Conduct Committee 39 | 40 | - Safia Abdalla 41 | - Tom Augspurger 42 | - Joris Van den Bossche 43 | - Camille Scott 44 | - Nathaniel Smith 45 | 46 | ## Institutional Partners 47 | 48 | ### Tier 1 49 | 50 | - [Two Sigma](https://www.twosigma.com/) (Jeff Reback) 51 | - [Ursa Labs](https://ursalabs.org) (Wes McKinney, Joris Van den Bossche) 52 | - [Gousto](https://www.gousto.co.uk/) (Marco Gorelli) 53 | - [d-fine GmbH](https://www.d-fine.com/en/) (Patrick Hoefler) 54 | 55 | ## Past Core Team Members 56 | 57 | - Wouter Overmeire 58 | - Skipper Seabold 59 | - Jeff Tratner 60 | 61 | ## Past Institutional Partners 62 | 63 | - [Paris-Saclay Center for Data Science](https://www.datascience-paris-saclay.fr/) 64 | - [Anaconda, Inc.](https://www.anaconda.com/) 65 | - [RStudio](https://www.rstudio.com) 66 | -------------------------------------------------------------------------------- /projectlicense.md: -------------------------------------------------------------------------------- 1 | ======= 2 | License 3 | ======= 4 | 5 | pandas is distributed under a 3-clause ("Simplified" or "New") BSD license. 6 | 7 | pandas license 8 | ============== 9 | 10 | Copyright (c) 2012-2016, pandas Development Team. 11 | All rights reserved. 12 | 13 | Copyright (c) 2011-2012, Lambda Foundry, Inc. and pandas Development Team. 14 | All rights reserved. 15 | 16 | Copyright (c) 2008-2011 AQR Capital Management, LLC. 17 | All rights reserved. 18 | 19 | Redistribution and use in source and binary forms, with or without 20 | modification, are permitted provided that the following conditions are 21 | met: 22 | 23 | * Redistributions of source code must retain the above copyright 24 | notice, this list of conditions and the following disclaimer. 25 | 26 | * Redistributions in binary form must reproduce the above 27 | copyright notice, this list of conditions and the following 28 | disclaimer in the documentation and/or other materials provided 29 | with the distribution. 30 | 31 | * Neither the name of the copyright holder nor the names of any 32 | contributors may be used to endorse or promote products derived 33 | from this software without specific prior written permission. 34 | 35 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS 36 | "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 37 | LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 38 | A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 39 | OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 40 | SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 41 | LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 42 | DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 43 | THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 44 | (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 45 | OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 46 | 47 | About the Copyright Holders 48 | =========================== 49 | 50 | AQR Capital Management began pandas development in 2008. Development was 51 | led by Wes McKinney. AQR released the source under this license in 2009. 52 | Wes is now an employee of Lambda Foundry, and remains the pandas project 53 | lead. 54 | 55 | The pandas Development Team is the collection of developers of the pandas 56 | project. This includes all of the pandas sub-projects, including pandas 57 | itself. 58 | 59 | Full credits for pandas contributors can be found in the documentation. 60 | 61 | Our Copyright Policy 62 | ==================== 63 | 64 | pandas uses a shared copyright model. Each contributor maintains copyright 65 | over their contributions to pandas. However, it is important to note that 66 | these contributions are typically only changes to the repositories. Thus, 67 | the pandas source code, in its entirety, is not the copyright of any single 68 | person or institution. Instead, it is the collective copyright of the 69 | entire pandas Development Team. If individual contributors want to maintain 70 | a record of what changes/contributions they have specific copyright on, 71 | they should indicate their copyright in the commit message of the change 72 | when they commit the change to one of the pandas repositories. 73 | 74 | With this in mind, the following banner should be used in any source code 75 | file to indicate the copyright and license terms: 76 | 77 | # Copyright (c) pandas Development Team. 78 | # Distributed under the terms of the Simplified BSD License. 79 | 80 | Other licenses can be found in the LICENSES directory of the main pandas 81 | repository http://github.com/pydata/pandas. -------------------------------------------------------------------------------- /teams.md: -------------------------------------------------------------------------------- 1 | # Teams 2 | 3 | This document describes the responsibilities, permissions and criteria for membership 4 | for each of the Teams associated with the _pandas_ project. The Teams are: 5 | 6 | - Core library Team 7 | - pandas-stubs Team 8 | - Finance Team 9 | - Infrastructure Team 10 | - Documentation Team 11 | - Code of Conduct Team 12 | - Triage Team 13 | - Contributor Community Team 14 | - Website Team 15 | - Outreach Team 16 | 17 | Individuals may be on more than one Team. If it is difficult to find enough people 18 | for any particular Team, the Steering Committee may assign the responsibilities of that 19 | underserved Team to another Team. 20 | 21 | ### Core Library Team 22 | 23 | #### Responsibilities 24 | 25 | * Maintain and develop the _pandas_ library (the 26 | [https://github.com/pandas-dev/pandas/](https://github.com/pandas-dev/pandas/) 27 | repository) 28 | * Review and Approve or Reject Pull Requests 29 | * Current guidelines on merging PRs: 30 | [https://pandas.pydata.org/docs/dev/development/maintaining.html#merging-pull-requests](https://pandas.pydata.org/docs/dev/development/maintaining.html#merging-pull-requests) 31 | * Finalizes Releases of the _pandas_ library 32 | 33 | #### Permissions 34 | 35 | * Has permission to merge anything to the main branch of the _pandas_ repository 36 | * Only Team with PDEP voting rights 37 | 38 | #### Criteria for Membership 39 | 40 | * New Members are nominated after a period of sustained and qualitative contributions 41 | * Joining heuristic: "is there some aspect of _pandas_ where we trust this person to 42 | get something in without anyone's help?". 43 | * An existing Member of the Team proposes to promote a new member 44 | * [https://pandas.pydata.org/docs/dev/development/maintaining.html#becoming-a-pandas-maintainer](https://pandas.pydata.org/docs/dev/development/maintaining.html#becoming-a-pandas-maintainer) 45 | 46 | ### pandas-stubs Team 47 | 48 | #### Responsibilities 49 | 50 | * Maintenance of `pandas-stubs` repository 51 | ([https://github.com/pandas-dev/pandas-stubs](https://github.com/pandas-dev/pandas-stubs)) 52 | * Triage of issues 53 | * Reviews of pull requests 54 | * Merges 55 | * Releases 56 | * Delegated to 2 or 3 members 57 | 58 | #### Permissions 59 | 60 | * Only Team with permission to merge to the main branch of the _pandas-stubs_ repository 61 | 62 | #### Criteria for Membership 63 | 64 | * New Members are nominated after a period of sustained and qualitative contributions 65 | * Joining heuristic: "is there some aspect of _pandas-stubs _where we trust this 66 | person to get something in without anyone's help?". 67 | * An existing Member of the Team proposes to promote a new member 68 | 69 | ### Finance Team 70 | 71 | #### Responsibilities 72 | 73 | * Manage Applications for Grant Proposals for Funding 74 | * Approve Project Expenses 75 | * Ensure that finances are effectively used 76 | * Find funding opportunities from appropriate, ethical sources 77 | 78 | #### Permissions 79 | 80 | * No specific technical permissions 81 | * Permissions to make all financial decisions on behalf of the Project 82 | * Determines rates for any paid contributors 83 | 84 | #### Criteria for Membership 85 | 86 | * Member of one Team for at least three years 87 | * Unanimous Approval of Steering Committee 88 | * Limited to 5 Members 89 | 90 | ### Infrastructure Team 91 | 92 | #### Responsibilities 93 | 94 | * Keep the pandas infrastructure up and working, including the servers for the website, 95 | benchmarks, CI and others as needed. 96 | * Build and Distribute Releases of the _pandas_ library 97 | * Decisions on platform support 98 | * Manage the 1Password repository 99 | 100 | #### Permissions 101 | 102 | * Usernames and Passwords for various servers 103 | 104 | #### Criteria for Membership 105 | 106 | * New Members are nominated after a period of sustained and qualitative contributions 107 | * Joining heuristic: "is there some aspect of the infrastructure where we trust this 108 | person to manage that part of the infrastructure without assistance?". 109 | * An existing Member of the Team proposes to promote a new member 110 | 111 | ### Documentation Team 112 | 113 | #### Responsibilities 114 | 115 | * Maintain the pandas documentation and its (building, e.g. Sphinx) infrastructure 116 | 117 | #### Permissions 118 | 119 | * Permission to merge to the main branch of the _pandas_ repository, with the criteria 120 | that it is a DOC only PR. 121 | 122 | #### Criteria for Membership 123 | 124 | * New Members are nominated after a period of sustained and qualitative contributions to 125 | the documentation 126 | 127 | ### Code of Conduct Team 128 | 129 | #### Responsibilities 130 | 131 | * Make sure the _pandas_ community is a welcoming and inclusive community. 132 | * Keeping the Code of Conduct 133 | ([https://pandas.pydata.org/community/coc.html](https://pandas.pydata.org/community/coc.html)) 134 | updated 135 | * Addressing reports of violations of the Code of Conduct 136 | 137 | #### Permissions 138 | 139 | * Administering the Code of Conduct 140 | 141 | #### Criteria for Membership 142 | 143 | * At most one Member of another Team can be on the Code of Conduct Team 144 | * Volunteers from the Community are welcome 145 | * Approval by the Steering Committee 146 | 147 | ### Triage Team 148 | 149 | #### Responsibilities 150 | 151 | * Help triage issues on the _pandas_ repository (respond to new issues, verify 152 | reproducibility and ensure a clear description, …) 153 | 154 | #### Permissions 155 | 156 | * “Triage” permissions for the _pandas_ repository (ability to manage issues without 157 | write access) 158 | 159 | #### Criteria for Membership 160 | 161 | * New Members are nominated by a Core Library Team member after a period of sustained 162 | and qualitative contributions 163 | 164 | ### Contributor Community Team 165 | 166 | #### Responsibilities 167 | 168 | * Support and enable Individual Contributors to make contributions to the Project 169 | * Encourage continued contributions from Individual Contributors so that they become 170 | future members of Teams 171 | * Lead Biweekly New Contributor Meetings 172 | * Organize sprints 173 | 174 | #### Permissions 175 | 176 | * No special permissions exist for this team 177 | 178 | #### Criteria for Membership 179 | 180 | * At least 2 members of the Core Library Team should be on this team 181 | * Appointed by the Core Library Team 182 | 183 | ### Website Team 184 | 185 | #### Responsibilities 186 | 187 | * Maintain the website; in particular: 188 | * The active maintainers 189 | * The institutional partners and sponsors of the project 190 | * The advertised books 191 | * Design and technical implementation 192 | 193 | #### Criteria for Membership 194 | 195 | * At least two Stewards should be on this team. 196 | * Joining heuristic: Would you trust this person to make decisions about the pandas 197 | website? 198 | 199 | #### Permissions 200 | 201 | * Permission to merge to the main branch of the _pandas_ repository, with the criteria 202 | that it is a WEBSITE only PR. 203 | * Login credentials for the web server 204 | 205 | ### Outreach Team 206 | 207 | #### Responsibilities 208 | 209 | * Announce new _pandas_ releases on social channels 210 | * Announce other pandas-related news, such as: 211 | * Recurring meetings 212 | * Events (such as sprints) 213 | * Blog posts (related to _pandas_) by _pandas_ members 214 | * Keep communication on-topic. It doesn’t all have to be completely serious, but it 215 | should be on-topic - let’s not use the social accounts for political soapboxing 216 | * Be respectful of other projects: open source, closed source, etc…they all have real 217 | humans behind them 218 | 219 | #### Permissions 220 | 221 | * Usernames and Passwords for various social accounts 222 | * Twitter/X account 223 | * Mastodon account 224 | * LinkedIn group management 225 | --------------------------------------------------------------------------------