search

veikman / dactyl-keyboard

Programmatic keyboard CAD
GNU Affero General Public License v3.0
268 stars 30 forks source link

licence #8

Open hsgw opened 5 years ago

hsgw commented 5 years ago

Hi, original dactyl keyboard is licensed under CC BY-SA now. https://github.com/adereth/dactyl-keyboard/issues/29

But DMOTE is under CC BY-NC-SA. Would you change this?

Note: https://github.com/tshort/dactyl-keyboard/issues/17

veikman commented 5 years ago

I was not aware of Adereth changing his license. Thank you for bringing it to my attention.

I hope to merge the DMOTE back upstream to Short, eventually. If he’s changed his license by then, or still wants to change it afterward, I would not object. I certainly have nothing against people group-buying their parts to build a DMOTE. I would object to people selling my work for private profit without involving me, but I don’t know what a reasonable compromise to prevent that would look like.

「浦川」と書いてるんでしょうか？日本語でも、ライセンスでも、上手ではありません、僕は。

hsgw commented 5 years ago

Thank you very much for accepting my proposal.

I would like to make dmote to my friend and get a little bit of extra spending money without license violation.

"浦川" is my family name. But where is that written? Sorry to confuse you.

veikman commented 5 years ago

CC NC allows you to make a keyboard for a friend and charge money for it. You can charge for your materials, for wear and tear on equipment, perhaps even for your time, but you cannot do the job for the money’s sake. NC forbids uses that are “primarily intended for or directed towards commercial advantage or monetary compensation”*. It is your intention that matters.

I’ll stick with NC for now.

友達に優しくしてね、浦川さん。

dangerzone commented 4 years ago

What's the rational for keeping the NC? Are you planning on making & selling this yourself?

veikman commented 4 years ago

I have not done so yet and I have no such plan at the moment.

bluekeys commented 4 years ago

My understanding of what I've read is that although the code is GPL, there is an additional license which restricts my freedom to use the software to produce keyboards for commercial purposes. That can't be right, can it?

Can you please clarify where the NC restrictions are intended to apply? Is it the use of some specific models you have created and included in the repo?

veikman commented 4 years ago

For questions of intent, I refer you to the upstream, where the decision to have a dual license was made, and—for the Dactyl—reverted.