Should we move aospy repository to its own 'aospy' organization?

spencerahill / aospy

Python package for automated analysis and management of gridded climate data

Apache License 2.0

83 stars 12 forks source link

Should we move aospy repository to its own 'aospy' organization? #330

Open spencerahill opened 5 years ago

spencerahill commented 5 years ago

I created one: https://github.com/aospy

Maybe that looks more professional than having it just on my account?

Also, maybe this matters now that we're switching to Azure and the CI jobs are run in parallel, BUT: whenever I push to a PR, the CI would get called twice, once on the PR and once on the branch (or something like that). Moving the repo to the aospy organization would resolve that. (It's still happening on Azure it's just less important.)

spencerkclark commented 5 years ago

Sure! I see no problem with doing that. I agree with both of your points in favor of it.

spencerahill commented 5 years ago

OK, I'm leaning towards going ahead with this then. Here are some potential cons:

Headache of making the transition (one-time but still)
100% selfishly, it not being directly associated with my Github profile (not really a compelling reason to not switch)

I think it makes sense to do this as part of a release, so that we can announce it/publicize it/make people aware of the switch.

So most likely will do this as part of our next release, which I think is still a ways away.