help wanted!

[rabernat]

This issue is just to make it clear that I am explicitly looking for volunteers to take on responsibility for versioning (#101), packaging (#100), documentation, and overall administration of xgcm. I just don't have time to tackle these things any time soon, but they are important for the long-term sustainability of this project.

For example, @jbusecke, @raphaeldussin, @willirath, @maikejulie, @jetesdal or anyone else who wants to learn more about how that stuff works, this is an opportunity to do so...

[raphaeldussin]

count me in!

[jbusecke]

Yup I would be interested!

…

Sent from my iPhone

On Jun 13, 2018, at 8:45 PM, Ryan Abernathey ***@***.***> wrote: This issue is just to make it clear that I am explicitly looking for volunteers to take on responsibility for versioning (#101), packaging (#100), documentation, and overall administration of xgcm. I just don't have time to tackle these things any time soon, but they are important for the long-term sustainability of this project. For example, @jbusecke, @raphaeldussin, @willirath, @maikejulie, @jetesdal or anyone else who wants to learn more about how that stuff works, this is an opportunity to do so... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[rabernat]

Great, thanks! I have given you both write access, so you can commit / merge PRs. (I would strongly prefer that all changes continue to come through PRs.) I probably also have to give you permissions on pypi--I'll try to sort that out asap.

So basically just start doing it. I recommend starting by copying xarray's "how to release" instructions / adapting them for xgcm:
https://github.com/pydata/xarray/blob/master/HOW_TO_RELEASE

[rabernat]

In order to get permissions to publish on pypi, you need to make accounts there and then tell me your usernames. I will add you to the xgcm project: https://pypi.org/project/xgcm/

[willirath]

I'm happy to join and look into #100. (But I'll be quite busy the next few days.) Am 14. Juni 2018 02:45:07 schrieb Ryan Abernathey <notifications@github.com>:

…

This issue is just to make it clear that I am explicitly looking for volunteers to take on responsibility for versioning (#101), packaging (#100), documentation, and overall administration of xgcm. I just don't have time to tackle these things any time soon, but they are important for the long-term sustainability of this project. For example, @jbusecke, @raphaeldussin, @willirath, @maikejulie, @jetesdal or anyone else who wants to learn more about how that stuff works, this is an opportunity to do so... -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #104

[rabernat]

Just to be clear, the near-term goal is to release xgcm v 0.2.0 via pip and conda-forge.

[jbusecke]

Do we have concrete milestones for 0.2.0 (e.g. working metrics module and perhaps vector calculus?)

[jbusecke]

Joined PyPI (username: jbusecke)

[raphaeldussin]

same (username: raphaeldussin)

[rabernat]

Ok you are both added as maintainers.

Let's make 0.2.0 just the current state of the project. No need to wait for those hard things to get done. We have not had a release in a long time, and there are already many improvements that we need to get out there.

We can discuss milestones for 0.3.0 in a separate issue.

[raphaeldussin]

from the pypi and conda docs, it seems that the way to go is to start with creating the pypi package
then the conda recipe. I can start testing it next week if that's ok with everybody.

[maikejulie]

Happy to be involved, but a bit busy out June sorry!

[jbusecke]

Sounds great. I have started a todo list (#105), where we can discuss what is still missing for a clean release of v0.2.0. Perhaps its only the things that I have to do...then this might have been a bit overkill.

Either way let me know if there are things (particularly in the documentation) that are still needed.

[rabernat]

from the pypi and conda docs, it seems that the way to go is to start with creating the pypi package
then the conda recipe. I can start testing it next week if that's ok with everybody.

Note that @ocefpaf has already created a conda-forge package for us (https://github.com/conda-forge/xgcm-feedstock), but it needs some attention (see discussion here: conda-forge/staged-recipes#6056 (comment)). He would be a great person to ask if you have questions about releasing.

As for the overall release procedure, I highly recommend you follow the procedure described in the xarray HOW_TO_RELEASE document:
https://github.com/pydata/xarray/blob/master/HOW_TO_RELEASE

[jbusecke]

Now that we have a more active development team should we close this? If we still want to highlight this issue, can we pin it somehow to the top? Otherwise it will not be seen I am afraid.

[jbusecke]

Ah there it is. I pinned this to the top.

[ocefpaf]

He would be a great person to ask if you have questions about releasing.

I usually recommend people to take a look at https://github.com/ioos/ioos-python-package-skeleton

As for the overall release procedure, I highly recommend you follow the procedure described in the xarray HOW_TO_RELEASE document:
pydata/xarray@master/HOW_TO_RELEASE

Got a broken link in that but xarray is a bigger project and needs more human intervention for a release. This project is in good shape and I would recommend something simpler and automated:

• dropping versioneer, which is deprecated, and adopting setuptools_scm;
• adding some sdist tarball/wheels tests (see link above);
• use a GH action to release every new tag.

I can send PRs to implent those if you want to adopt that wokflow.

[github-actions]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

[github-actions]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

[jbusecke]

I would like to keep this open, since it is a general announcement?