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

Governance and affiliation #400

Closed
alimanfoo opened this issue Feb 8, 2019 · 3 comments
Closed

Governance and affiliation #400

alimanfoo opened this issue Feb 8, 2019 · 3 comments

Comments

@alimanfoo
Copy link
Member

Following on from #291, I'm raising this issue as a focus for discussing a governance process and model, and associated issues like affiliation and legal protection.

Given that Zarr is closely aligned with the PyData ecosystem, the default approach is probably to follow the examples of other prominent projects within the ecosystem, e.g., NumPy, Jupyter, or pandas.

A key commonality for all of the above projects is that they are formally affiliated with NumFOCUS, 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".

For comparison, there are other options for governance and affiliation of open source projects, such as the Apache Software Foundation, which runs the Apache Incubator as the entry path for new projects.

One possible difference with the above projects is that the Zarr project includes development of both specifications and implementations of those specifications. A point for consideration is whether the same process can apply to both specs and code, or whether specs need a different process.

There are various organisations involved in standardisation of technical specifications, which have processes and structures that we might draw on.

@jakirkham
Copy link
Member

Are we ok to create an empty governance repo to start?

cc @zarr-developers/core-devs

@jakirkham
Copy link
Member

jakirkham commented Feb 14, 2019

Have created the governance repo. Am not attached to the name if we need to rename it to zarr-governance for instance. ( zarr-developers/governance#1 )

Should we close this and start adding issues over there?

@alimanfoo
Copy link
Member Author

alimanfoo commented Mar 1, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants