Adapting contributing guide - License mismatch #17
Replies: 2 comments 8 replies
-
This repo has a GNU General Public License v3.0 https://github.com/Club-40/TOP-Club-40-Group-Project/blob/e6626ae4735f89e689f0574fb7013f7fd4902baa/LICENSE. I believe in order to use the TOP contributing guide or a derivative, we'd need to follow their licensing. I could be wrong. |
Beta Was this translation helpful? Give feedback.
-
Do we need to follow TOP's contributing guide as a derivative? I like GPL-v3's straightforward, strict copyleft policy and I think allowing that for this project would be cool enough. If you want an example, here's a contributing guide for another GPL-v3 project. |
Beta Was this translation helpful? Give feedback.
-
I believe that TOP's contributing guide (is their License a part of the curriculum?) falls under a different license than is currently shown in the license.md for this group project.
From TOP's curriculum repo license.md:
https://github.com/TheOdinProject/curriculum/blob/main/license.md
In order to create a derivative work from the TOP contributing guide, it sounds like we'd need to adopt that license for our guide. Now, I think we'd be fine having the whole project under that license, but I think another path is to have just the guide under that specific license.
What are the team's thoughts on adopting the same license that TOP uses for their curriculum?
Beta Was this translation helpful? Give feedback.
All reactions