Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Should this repo be archived? #12

Open
dblodgett-usgs opened this issue Jul 17, 2019 · 6 comments
Open

Should this repo be archived? #12

dblodgett-usgs opened this issue Jul 17, 2019 · 6 comments

Comments

@dblodgett-usgs
Copy link
Contributor

If this notification makes it to anyone that objects -- please object. Otherwise, I will archive next time I decide to clean up github stuff.

@MTG-Formats
Copy link

Are the CF-2 issuse now discussed under cf-convention/cf-conventions? Some of the issues here are still open and still relevant to the CF convention evolution - like the use of the new user types. Should these be moved or re-opened as cf-conventions issues?

@dblodgett-usgs
Copy link
Contributor Author

I think that would make sense. The one I'm responsible for is done. Maybe we just comment on each one @thepersonwhostartedit and tell them to move it to cf-conventions if it's still relevant?

@MTG-Formats
Copy link

How can the issue be moved to cf-conventions? Is there an option to do this or shall I just open it again under cf-conventions with a link back here for the previous discussion?

@ghost
Copy link

ghost commented Jul 22, 2019 via email

@dblodgett-usgs
Copy link
Contributor Author

I see the "Transfer Issue" button. How about I transfer the ones that seem to still be relevant and comment at the person who started the ones that aren't obvious?

@MTG-Formats
Copy link

Sounds like a good idea.

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

No branches or pull requests

2 participants