Skip to content
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

skyhookify #1

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
# governance
Governance Documents for Pangeo
Governance Documents for SkyhookDM
42 changes: 22 additions & 20 deletions conduct/code_of_conduct.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Pangeo Code of Conduct
# SkyhookDM Code of Conduct

Pangeo values the safety and security of all of our members and,
SkyhookDM values the safety and security of all of our members and,
because of that, we will not tolerate any form of harassment or
discrimination. To this end in this page we:

Expand All @@ -11,18 +11,18 @@ discrimination. To this end in this page we:
* Commit to a periodic review of the code of conduct


## Statement of Intent of the Pangeo Community
## Statement of Intent of the SkyhookDM Community

Pangeo is an engaged and respectful community made up of people
SkyhookDM is an engaged and respectful community made up of people
from all over the world. Your involvement helps us to further our
mission and to create an open platform that serves a broad range of
communities, from research and education, to journalism, industry and
beyond.

Pangeo is dedicated to providing a respectful, harassment-free community for everyone.
SkyhookDM is dedicated to providing a respectful, harassment-free community for everyone.
We do not tolerate harassment or bullying of any community member in any form.
This applies equally to founders, developers, mentors and new community members,
in all spaces managed by Pangeo. This includes the mailing lists,
in all spaces managed by SkyhookDM. This includes the mailing lists,
our GitHub organizations, our chat rooms, in-person events, and any other
forums created by the project team. In addition, violations of this code
outside these spaces may affect a person's ability to participate within them.
Expand Down Expand Up @@ -55,7 +55,7 @@ outside these spaces may affect a person's ability to participate within them.

* **3. Consider Impact vs. Intent**.
Disagreements, both social and
technical, happen all the time and Pangeo is no exception.
technical, happen all the time and SkyhookDM is no exception.
People perceive their own behaviors very differently than others perceive them.
What motivates one person may cause stress for another.
A few steps worth remembering include the following:
Expand All @@ -82,10 +82,9 @@ Rather than considering this code an exhaustive list
of things that you *can’t* do, take it in the spirit it is intended - a guide to
make it easier to enrich all of us and the communities in which we participate.
By embracing the following principles, guidelines and actions to follow or
avoid, you will help us make Pangeo a welcoming and productive community. Feel
avoid, you will help us make SkyhookDM a welcoming and productive community. Feel
free to contact the Code of Conduct Committee at
[[email protected]](mailto:[email protected]) with any questions.

[[email protected]](mailto:[email protected]) with any questions.

## Forms of harrassment

Expand All @@ -111,11 +110,11 @@ Forms of harrassment include, but is not limited to:

If a member of the community at large engages in behavior which is harassing
or discriminatory in any way, once the incident is reported,
the [Code of Conduct Committee](mailto:pangeo-conduct@googlegroups.com) may take any action they deem
the [Code of Conduct Committee](mailto:skyhookdm-conduct[email protected]) may take any action they deem
appropriate listed in the [*Enforcement Manual*](enforcement.md).
These actions include, but are not limited to, issuing a warning,
requiring an apology, or a permanent or temporary ban from some
or all Pangeo spaces (mailing lists, gitter.im, etc.).
or all SkyhookDM spaces (mailing lists, gitter.im, etc.).


## How to Report Harassment and Discrimination
Expand All @@ -125,8 +124,8 @@ a timely manner. Code of conduct violations reduce the value of the community
for everyone and we take them seriously.

You can file a report by emailing
[pangeo-conduct@googlegroups.com](mailto:pangeo-conduct@googlegroups.com) or by filing out
[this form](https://forms.gle/jDmUokAtzwxwkKQq7). The online form gives you the option to
[skyhookdm-conduct[email protected]](mailto:skyhookdm-conduct[email protected]) or by filing out
[this form](https://forms.gle/qaszuCWz2pYXjvad9). The online form gives you the option to
keep your report anonymous or request that we follow up with you directly. While we cannot
follow up on an anonymous report, we will take appropriate action.

Expand All @@ -138,17 +137,20 @@ Manual*](enforcement.md).

## Periodic Review

Pangeo strives to create a positive and inclusive environment.
As such, the Pangeo Steering Council commits to an annual review
SkyhookDM strives to create a positive and inclusive environment.
As such, the SkyhookDM Steering Council commits to an annual review
of the Code of Conduct to ensure that it continues to align with
this goal and address the needs of our community.
Pangeo welcomes feedback from its members.
Feedback can be submitted to: [[email protected]](mailto:[email protected]) and to this github repository.
SkyhookDM welcomes feedback from its members.
Feedback can be submitted to: [email protected]](mailto:[email protected]) and to this github repository.


### Acknowledgements

### References
This Code of Conduct has been adapted from the [*Pangeo*](https://github.com/skyhookdm/governance/blob/master/conduct/code_of_conduct.md) Project, licensed under a [*Creative Commons
Attribution 4.0 International (CC BY 4.0)*](http://creativecommons.org/licenses/by/4.0/) license.

This Code of Conduct has been adapted from:
The Pangeo Code of Conduct has been adapted from:
* the [*Jupyter*](http://jupyter.org/conduct/) Project, licensed under a [*Creative Commons
Attribution*](http://creativecommons.org/licenses/by/3.0/) license.
* the [*WWCode*](https://www.womenwhocode.com/codeofconduct) Network.
Expand Down
30 changes: 15 additions & 15 deletions governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,23 +4,23 @@ 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:

https://github.com/pangeo-data/governance
https://github.com/skyhookdm/governance

## The Project

The Pangeo Project (The Project) is an open source software project. The goal
of The Project is to develop open source software and related technology for the
analysis of large scientific datasets. The Project endeavors to extend the
broader scientific software ecosystem. 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 Pangeo-data GitHub organization.
The Skyhook Data Management Project (The Project) is an open source software project. The goal
of The Project is to develop open source software and related technology for
the computational I/O stack. The Project endeavors to extend the
broader software ecosystem of storage systems, networking, and data science.
The Software developed by The Project is
released under a variety of open source software licenses that are both approved by the Open Source Initiative (OSI)
and recognized as free by the Free Software Foundation (FSF), is developed openly, and
hosted in public GitHub repositories under the skyhookdm GitHub organization.
Examples of Project Software include the tools and configurations related to the
deployment of computational infrastructure. The Services run by The Project
consist of public websites and web-services that are hosted under the pangeo.io
or pangeo-data.org domains. Examples of Project Services include the Pangeo
website (https://pangeo-data.org and https://pangeo.io), Pangeo-JupyterHub
deployments (https://pangeo.pydata.org and https://pangeo.informaticslab.co.uk),
and the Pangeo-Binder (https://binder.pangeo.io).
website (https://skyhookdm.github.io) and ...

The Project is developed by a team of distributed developers, called
Contributors. Contributors are individuals who have contributed to code, code
Expand All @@ -35,10 +35,10 @@ participation is openness and transparency.

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

https://github.com/pangeo-data/pangeo/graphs/contributors
https://github.com/skyhookdm/skyhookdm.github.io/graphs/contributors

There are also many other Contributors listed in the logs of other repositories
of the Pangeo Project.
of the SkyhookDM Project.

The collection of all Contributors to The Project and stakeholders in The
Project, including Users and Funders, is called The Community. Contributors
Expand Down Expand Up @@ -84,7 +84,7 @@ In particular, the Council may:
Outcomes and decisions should be clearly communicated to the Community. This can
take three different forms:

* New challenges for Pangeo will be detailed as a GitHub issue for the Community
* New challenges for SkyhookDM will be detailed as a GitHub issue for the Community
to discuss.
* Resolved technical deadlocks will result in an explanation on the relevant
issue and/or closure of the relevant pull request.
Expand Down Expand Up @@ -119,7 +119,7 @@ Council:
Council.
2. If a Council Member becomes inactive in The Project for a period of one year,
they will be considered for removal from the Council. Before removal, an
inactive Member will be approached by the a Council Member to see if they plan
inactive Member will be approached by a Council Member to see if they plan
on returning to active participation. If not they will be removed immediately
upon a Council vote. If they plan on returning to active participation soon,
they will be given a grace period of one year. If they don’t return to active
Expand Down Expand Up @@ -208,7 +208,7 @@ umbrella.

Changes to the governance documents are submitted via a GitHub pull request to
The Project's governance documents GitHub repository at
https://github.com/pangeo-data/governance. The pull request is then refined in
https://github.com/skyhookdm/governance. The pull request is then refined in
response to public comment and review, with the goal being consensus in the
community. The period for open comment will last in proportional to the
complexity of the changes; major changes will be open for comment for no less
Expand Down