Timeline for License Requirements for Including Dual-Licensed Open-Source Software
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2013 at 14:59 | answer | added | hakre | timeline score: 2 | |
| Jun 20, 2013 at 0:21 | comment | added | RunnerRick | @apsillers That's kind of what I thought too, but--being a programmer--I thought there might be a pattern that others have used. Thanks for your feedback. | |
| Jun 19, 2013 at 23:57 | comment | added | apsillers | Since you already have a perfectly fine understanding of how dual-licensing works, your question seems narrowly focused on a legally-airtight wording/approach, which you're unlikely to find here. I'd say simply to remove any references to the dual or GPL licensing throughout your fork of the project, and you will have made it as clear as possible that your project is BSD-only. If you want better advice than that, I'm afraid you'll need to talk to a lawyer. | |
| Jun 19, 2013 at 22:14 | history | edited | RunnerRick | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Jun 19, 2013 at 22:13 | history | undeleted | RunnerRick | ||
| Jun 18, 2013 at 22:18 | history | deleted | RunnerRick | ||
| Jun 18, 2013 at 22:14 | history | asked | RunnerRick | CC BY-SA 3.0 |