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

Transfer repository ownership to SciTools #167

Open
bjlittle opened this issue Feb 15, 2023 · 10 comments
Open

Transfer repository ownership to SciTools #167

bjlittle opened this issue Feb 15, 2023 · 10 comments
Assignees

Comments

@bjlittle
Copy link
Owner

📰 Custom Issue

It's early days for geovista, which has just been born 🥳

The current plan is to bootstrap geovista here with an minimal stable core under ownership of https://github.com/bjlittle, before then transferring ownership of the repository to the https://github.com/SciTools organisation.

At the moment SciTools is slowly undergoing re-licensing from LGPL to BSD 3-Clause, and a refresh of its CLA. After this work is completed, and when geovista is "ready" it will be migrated to SciTools to live alongside its more mature and well-behaved sister cartopy.

More importantly, once geovista is under SciTools ownership, it can then be maintained by its awesome team of core developers 😄

@bjlittle bjlittle added the new: issue Highlight a new community raised "generic" issue label Feb 15, 2023
@bjlittle bjlittle self-assigned this Feb 15, 2023
@bjlittle bjlittle pinned this issue Feb 15, 2023
@bjlittle bjlittle removed the new: issue Highlight a new community raised "generic" issue label Feb 18, 2023
@trexfeathers
Copy link
Collaborator

Looking forward to this! Do you think we could have a checklist in the main issue body of what would make GeoVista "ready"? Should make it easier for us to hold ourselves to account.

@bjlittle
Copy link
Owner Author

Looking forward to this! Do you think we could have a checklist in the main issue body of what would make GeoVista "ready"? Should make it easier for us to hold ourselves to account.

@trexfeathers Totally agree.

I've have a ponder, and try to figure out the MVP for "readiness" to migrate. Fleshing that out to add realy clarity will give us something concrete to aim for, which is always a winner.

Thanks!

@trexfeathers
Copy link
Collaborator

Bump

@bjlittle
Copy link
Owner Author

bjlittle commented Mar 13, 2023

@trexfeathers Thinking on this, I'm not going to create an exhaustive list here. I feel that would be a bit counter-productive. Also, at the moment the line in the sand is quite fluid, and I'm totally okay with that (for now).

However, I am using the image label in the this GH project to capture my current thinking on what I want to deliver.

Also, I don't see the point in transferring ownership too soon, otherwise I can't be as nimble, reactive and productive as I am at the moment. Dunno, tough call.

Ultimately, I think I'm relying on the fact that the decision of "when" will eventually become "clear", and I'm in no particular rush to force that decision along atm.

@bjlittle
Copy link
Owner Author

@trexfeathers However, do keep nudging me. That should keep things healthy 😉

It's important that the migration happens 👍

@trexfeathers
Copy link
Collaborator

This is probably a "perfect is the enemy of the good" situation. We have to make sure we recognise when GeoVista has passed the "good" threshold, and resist waiting for "perfect".

@github-actions
Copy link
Contributor

In order to maintain a backlog of relevant issues, we automatically label them as stale after 180 days of inactivity.

If this issue is still important to you, then please comment on this issue and the stale label will be removed.

Otherwise this issue will be automatically closed in 28 days time.

@github-actions github-actions bot added the stale A stale issue/pull-request label Sep 10, 2023
@tkoyama010
Copy link
Collaborator

This issue is still important.

@github-actions github-actions bot removed the stale A stale issue/pull-request label Sep 11, 2023
@bjlittle bjlittle removed their assignment Nov 23, 2023
Copy link
Contributor

In order to maintain a backlog of relevant issues, we automatically label them as stale after 180 days of inactivity.

If this issue is still important to you, then please comment on this issue and the stale label will be removed.

Otherwise this issue will be automatically closed in 28 days time.

@github-actions github-actions bot added the stale A stale issue/pull-request label May 22, 2024
@tkoyama010
Copy link
Collaborator

This issue is still important.

@github-actions github-actions bot removed the stale A stale issue/pull-request label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 Candidate
Development

No branches or pull requests

3 participants