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

License - How do we want to license this repo? #1

Open
serbinsh opened this issue Sep 19, 2019 · 3 comments
Open

License - How do we want to license this repo? #1

serbinsh opened this issue Sep 19, 2019 · 3 comments
Assignees

Comments

@serbinsh
Copy link
Collaborator

@rgknox @glemieux

This is the first NGT repo for FATES docker. This is labeled as a "tutorial" but may expand to a repo for building versions of FATES for the testbed or testing. Or perhaps we have this basic tutorial repo and eventually create another "working" repo for dev/testbed release of Docker fates? In which case the license may be different?

@serbinsh
Copy link
Collaborator Author

BSD, GNU3, the FATES license?

@glemieux
Copy link
Collaborator

glemieux commented Sep 19, 2019

Good question about the license and the variation based on audience; I'm not sure. Maybe we can clarify during the FATES call today.

Yes, I was thinking along the lines of what you laid out @serbinsh regarding having a very basic tutorial repo and create separate fates docker development repo once we have success with the tutorial. My main rationale is that we perhaps avoid worrying about the input data interface for the tutorial by simply including the necessary data in the tutorial container? The docker-fates-development repo would address that issue (and others).

@serbinsh
Copy link
Collaborator Author

@glemieux yeah lets ask on the call if that seems to make sense. As for "shipping" the required files for a demo/tutorial, I do have an example of that for CTSM here: https://github.com/serbinsh/ctsm_containers/wiki/Example-CTSM-(CLM5)-run:-US-NR1-(Niwot-Ridge,-Colorado) .

We could do the same exact thing for fates. We just need to identify a site and met drivers we can share in the docker container, and then build the single point surface files. I will work on that and assume BCI is a good first site?

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

No branches or pull requests

2 participants