Skip to content

WEB: Updating links of the governance page #47679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 12, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 19 additions & 28 deletions web/pandas/about/governance.md
Original file line number Diff line number Diff line change
@@ -1,23 +1,21 @@
# Main Governance Document
# Project governance

The official version of this document, along with a list of
individuals and institutions in the roles defined in the governance
section below, is contained in The Project Governance Repository at:
section below, is contained in the
[Project governance](https://pandas.pydata.org/about/governance.html)
page of the pandas website.

[https://github.com/pydata/pandas-governance](https://github.com/pydata/pandas-governance)

The Project
===========
## The Project

The pandas Project (The Project) is an open source software project affiliated
with the 501(c)3 NumFOCUS Foundation. The goal of The Project is to develop open
source software for data ingest, data preparation, data analysis, and data
visualization for the Python programming language. The Software developed by
The Project is released under the BSD (or similar) open source license,
developed openly and hosted in public GitHub repositories under the [PyData
GitHub organization](https://github.com/pydata). Examples of Project Software
include the main pandas code repository, pandas-website, and the
pandas-datareader add-on library.
developed openly and hosted in public GitHub repositories under the [pandas
GitHub organization](https://github.com/pandas-dev). Examples of Project Software
include the main pandas code repository and the pandas-stubs library.

Through its affiliation with NumFOCUS, The Project has the right to receive
tax-deductible donations in the United States of America.
Expand All @@ -34,7 +32,7 @@ transparency.

Here is a list of the current Contributors to the main pandas repository:

[https://github.com/pydata/pandas/graphs/contributors](https://github.com/pydata/pandas/graphs/contributors)
[https://github.com/pandas-dev/pandas/graphs/contributors](https://github.com/pandas-dev/pandas/graphs/contributors)

There are also many other Contributors listed in the logs of other repositories of
the pandas project.
Expand All @@ -45,14 +43,13 @@ Community and we strive to keep the barrier between Contributors and Users as
low as possible.

The Project is formally affiliated with the 501(c)3 NumFOCUS Foundation
([http://numfocus.org](http://numfocus.org)), which serves as its fiscal
([https://numfocus.org](https://numfocus.org)), which serves as its fiscal
sponsor, may hold project trademarks and other intellectual property, helps
manage project donations and acts as a parent legal entity. NumFOCUS is the
only legal entity that has a formal relationship with the project (see
Institutional Partners section below).

Governance
==========
## Governance

This section describes the governance and leadership model of The Project.

Expand All @@ -76,8 +73,7 @@ need for a more formal governance model. Moving forward The Project leadership
will consist of a BDFL and Core Team. We view this governance model as the
formalization of what we are already doing, rather than a change in direction.

BDFL
----
### BDFL

The Project will have a BDFL (Benevolent Dictator for Life), who is currently
Wes McKinney. As Dictator, the BDFL has the authority to make all final
Expand All @@ -103,8 +99,7 @@ vote. If no BDFL candidate receives 2/3 of the votes of the Core Team, the Core
Team members shall propose the BDFL candidates to the Main NumFOCUS board, who
will then make the final decision.

Core Team
---------
### Core Team

The Project's Core Team will consist of Project Contributors who have produced
contributions that are substantial in quality and quantity, and sustained over
Expand Down Expand Up @@ -238,8 +233,7 @@ interactions with NumFOCUS.
employment or contracting work (including the reportee, i.e. the reportee + 1
is the max). This avoids effective majorities resting on one person.

Institutional Partners and Funding
==================================
## Institutional Partners and Funding

The BDFL and Core Team are the primary leadership for the project. No outside
institution, individual or legal entity has the ability to own, control, usurp
Expand Down Expand Up @@ -300,23 +294,20 @@ Institutional Partners, with associated benefits:

**Tier 2** = an institution with at least one Institutional Contributor

Breach
======
## Breach

Non-compliance with the terms of the governance documents shall be reported to
the Core Team either through public or private channels as deemed appropriate.

Changing the Governance Documents
=================================
## Changing the Governance

Changes to the governance documents are submitted via a GitHub pull request to
The Project's governance documents GitHub repository at
[https://github.com/pydata/pandas-governance](https://github.com/pydata/pandas-governance).
Changes to the governance are submitted via a GitHub pull request to The Project's
[governance page](https://github.com/pandas-dev/pandas/blob/main/web/pandas/about/governance.md).
The pull request is then refined in response to public comment and review, with
the goal being consensus in the community. After this open period, a Core Team
Member proposes to the Core Team that the changes be ratified and the pull
request merged (accepting the proposed changes) or proposes that the pull
request be closed without merging (rejecting the proposed changes). The Member
request be closed without merging (rejecting the proposed changes). The Member
should state the final commit hash in the pull request being proposed for
acceptance or rejection and briefly summarize the pull request. A minimum of
80% of the Core Team must vote and at least 2/3 of the votes must be positive
Expand Down