add NOTICE.LLNS, MAINTAINERS, CONTRIBUTING#58
add NOTICE.LLNS, MAINTAINERS, CONTRIBUTING#58wihobbs wants to merge 1 commit intoflux-framework:masterfrom
Conversation
|
@wihobbs the tutorial content does not need to be under the less permissive GNU license. We want people to take it and modify. My preference would be to have MIT here, or MIT/Apache 2. Of course I'm sure this would need to be a Flux meeting item, so let's hold on merging and can bring up at a future meeting. |
wihobbs
changed the title
Problem: RFC 2 and RFC 48 set out guidelines for flux-framework repositories, and the Tutorials repository is currently lacking some of the things it mandates or recommends. Add a LLNS notice, and update the README and other files.
vsoch
left a comment
vsoch
left a comment
There was a problem hiding this comment.
Let's do a structure that places "community" files in .github and license (and similar) files in the root. E.g.,:
.github/
CONTRIBUTING.md
MAINTAINERS.md
NOTICE.LLNS|  | ||
|
|
||
| #### Release | ||
|
|
There was a problem hiding this comment.
I think you forgot to remove this, or update to the release code.
I will note that when I make new tutorial content, I typically do another release (for LLNL-PRES) so I don't know if it makes sense to put any single one here. I would generally not, but we can see what others think.
There was a problem hiding this comment.
We had some discussion in the coffee call about this and I asked Meg, who said that presentations released for external unlimited distribution can use the Creative Commons (with Attribution) license. I've now come full circle with you and wonder if it's necessary to have a license at all...I'm not clear on what the implied permission scope is if you have no license in a repo.
There was a problem hiding this comment.
Some information on if you have no license in a repo is in the GitHub docs.
There was a problem hiding this comment.
No license means "all rights reserved," which we probably do not want. Creative commons is not typically for code, and there is more of that than presentation here. We likely want a license that is more akin to MIT or Apache 2, which is in line with other projects we have. I would bring it up at a future Flux meeting and we can choose from the set of 3 that the other projects have.
2 participants
Problem: RFC 2 and RFC 48 set out guidelines for flux-framework repositories, and the Tutorials repository is currently lacking some of the things it mandates or recommends.
Add a LICENSE, LLNS notice, and update the README and other files.