Conversation
|
Let's discuss at the bi-weekly meeting next week |
keewis
left a comment
There was a problem hiding this comment.
I've got some comments, but not necessarily answers
| label: What do you want to do | ||
| options: | ||
| - label: Address reported issues and feature requests | ||
| - label: Update a **Archived** repository to make it work on the latest JupyterLab version |
|
|
||
| ### 1. Open source license | ||
|
|
||
| The project must bee Licensed under an [OSI approved license](https://opensource.org/licenses) |
There was a problem hiding this comment.
| The project must bee Licensed under an [OSI approved license](https://opensource.org/licenses) | |
| The project must be Licensed under an [OSI approved license](https://opensource.org/licenses) |
|
|
||
| **conda-forge** | ||
|
|
||
| If there is a conda-forge package then an xarray-contrib core team member must be added as an owner of the package (TODO: is there an easier way?) |
There was a problem hiding this comment.
I don't think there's an easier way, but on conda-forge rights management is already much easier than on PyPI
|
|
||
| #### Documentation | ||
|
|
||
| Any documentation hosting (e.g. `readthedocs`) must also be shared with `xarray-contrib` |
There was a problem hiding this comment.
how would we do that? If we ask for it, we should provide a suggestion.
There was a problem hiding this comment.
for now i m writing just adding someone. but i think having an xarray-contrib account on common platforms like readthedocs might also be helpful.
|
@shoyer after discussing with @keewis we think we would like to create a pypi organization to test out the concept of using that to maintain access to pypi publishing even if original maintainers drop off. You are the natural person to apply for creating such an account (but can easily add other owners/managers later). Would you be willing to do the application process (https://docs.pypi.org/organization-accounts/actions/org-actions/#create-an-organization) for an xarray-contrib org so we can try it out to see if it is a good solution? |
|
I think any of the owners of
|
|
what do you think about:
Once we figured that out, one of us (ideally someone who is also a maintainer of the xarray project on PyPI) would request the organization. |
|
That all seems good to me with the possible exception of
I suspect if this is successful it will grow beyond that presuming anyone working on a specific package needs to become a member. but that's not a huge deal
Agreed. |
I guess this depends on the way organizations work, but I was thinking this was the number of people performing admin tasks in that organization (i.e. us who are supposed to transfer ownership in case maintainers stop responding). Maybe that's not how organization model works (the form explicitly says "NOT the number of people in your organization"), so I'll have to investigate this further. |
|
I filed the request on PyPI to make a new "xarray-contrib" organization. I'll add all of you as maintainers once it's approved! |
|
a pypi org now exists! thank you @shoyer! given this does anyone have thoughts on codifying this policy? |
|
I like the policy and support starting with requiring it and adapting if needed when someone complains. |
|
Ok i have updated the site to finish filliing out |
Follow up to #15
This creates a new static website with more information and makes a new issue template for requests to help maintain. This is modeled on https://jupyterlab-contrib.github.io/
A key change is that I added an explicit requirement to provide the "keys to castle" to any projects added here. So that if the original authors stop responding the xarray-contrib org has the power to allow access to anyone who wants to volunteer to work on the project. This should require some discussion the right way to transfer these permissions (e.g. should we have a pypi organization?)