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

Find a good deploy mechanism #29

Open
Damian-Oswald opened this issue Feb 27, 2025 · 2 comments
Open

Find a good deploy mechanism #29

Damian-Oswald opened this issue Feb 27, 2025 · 2 comments
Labels
question Further information is requested

Comments

@Damian-Oswald
Copy link
Member

Possible ides: Posit Workbench. @GuySchnidrig we'll probably need your help here ;)

@Damian-Oswald Damian-Oswald added the question Further information is requested label Feb 27, 2025
@Damian-Oswald
Copy link
Member Author

Think about repo split

@AFoletti
Copy link
Member

AFoletti commented Mar 3, 2025

Last week we were blocked in the repo split by a semantic issue about naming.
I think we shoud KISS:

  1. Keep the code and schemas in this repo, without changing the name, ad give it the https://creativecommons.org/licenses/by/4.0/ license
  2. Create a second repo with the data itself, name it "foag-metadata" or similar and give it the https://creativecommons.org/licenses/by-nd/4.0/ license

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

No branches or pull requests

2 participants