search

UMM-CSci / senior-seminar

Public materials for senior seminar, including assignments, past papers/slides, templates, etc.
https://umm-csci.github.io/senior-seminar/
9 stars 10 forks source link

Add LICENSE #45

Open floogulinc opened 3 years ago

floogulinc commented 3 years ago

This repo doesn't have any license set for it. We should probably set one up. I would be ok licensing the code I have written that builds the site under the MIT license but we should probably also specify that the papers themselves are not under the same license as the code that builds the site.

elenam commented 3 years ago

Right - the papers clearly have their own license. Slides may need a clarification.

On Sun, Apr 4, 2021 at 5:21 PM Paul Friederichsen @.***> wrote:

This repo doesn't have any license set for it. We should probably set one up. I would be ok licensing the code I have written that builds the site under the MIT license but we should probably also specify that the papers themselves are not under the same license as the code that builds the site.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/UMM-CSci/senior-seminar/issues/45, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAERJYMEH4QJY7GDZCPEUN3THDQ5BANCNFSM42L3AVIA .

-- Dr. Elena Machkasova Associate Professor of Computer Science Division of Science and Mathematics University of Minnesota, Morris Office: Sci 2325 (320) 589-6308 http://cda.morris.umn.edu/~elenam/ Pronouns: she/her/hers or any other

floogulinc commented 3 years ago

Yeah and I suppose you may want to license all the text in the Resources section under something else like a CC license.

elenam commented 3 years ago

I feel like maybe this should be an item for the next Discipline meeting - April 15th.

On Sun, Apr 4, 2021 at 5:29 PM Paul Friederichsen @.***> wrote:

Yeah and I suppose you may want to license all the text in the Resources section under something else like a CC license.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/UMM-CSci/senior-seminar/issues/45#issuecomment-813108915, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAERJYKQZ262MHK37VD4WHDTHDR5DANCNFSM42L3AVIA .

-- Dr. Elena Machkasova Associate Professor of Computer Science Division of Science and Mathematics University of Minnesota, Morris Office: Sci 2325 (320) 589-6308 http://cda.morris.umn.edu/~elenam/ Pronouns: she/her/hers or any other

elenam commented 3 years ago

@NicMcPhee

floogulinc commented 3 years ago

One more thing, I think the right thing to do when adding a license like this is to ask permission from everyone who has contributed to the affected code. I think for the Jekyll template code that amounts to just @emmahsax and I. There are more contributors for other parts like the Resources text and individual seminar data.

emmahsax commented 3 years ago

@floogulinc and @elenam: I'm fine with licensing all Jekyll code I've written for this project under the MIT license, but another one I've been liking lately is the BSD 3-Clause license. But it's all your choice, I'm happy with whatever you go with 😄

emmahsax commented 3 years ago

@floogulinc One other thing we could do is have two "licenses", one which is a content license. AKA any content (seminars, papers, slides, etc) is ours only, as if there was no license file at all, so essentially there's no permissions for anyone else. But the Jekyll code (non-content) would be licensed under MIT.