Meowdy! See your PR preview:
🔍 Git commit SHA: ff2bde5
✅ Deployment Preview URL: https://NCAR.github.io/geocat-applications/_preview/61

Another option could be leaving emails off.

It seems like this might be more of the norm.

Oh! I hadn't considered that, that's a good idea!

This looks great!

It did remind me that we might want to add something like a CC-BY license for non-code content similar to Project Pythia. The Turing Way has a nice example of how to include info on this in a repo.

I only mention this here since the license is included in the citation file and if we do want to add this it's probably easier sooner than later.

Or maybe we just remove the license info for now and decouple these issues?

I'm not opposed to sorting this out in theory, but I think using CC-BY may necessitate asking legal first according to our select a license guide.

I can remove the license here for now, though, if that's an acceptable solution to unblock us here?

I'm not opposed to sorting this out in theory, but I think using CC-BY may necessitate asking legal first according to our select a license guide.

This guide is for software citation / licensing specifically and I've seen a good bit of usage beyond Project Pythia. We could certainly get clarification though.

I'm not opposed to sorting this out in theory, but I think using CC-BY may necessitate asking legal first according to our select a license guide.

This guide is for software citation / licensing specifically and I've seen a good bit of usage beyond Project Pythia. We could certainly get clarification though.

@jukent do you know anything about how Pythia handled this? Did y'all need to get permission or guidance?

I don't remember much of a conversation about it. I think that was either just the standard (so not much of a decision) or a decision that was made between just the PIs.