adding license for the hardware itself and the documentation

BeeHive-org / BeeHive

BeeHive: a flexible open hardware platform for behavioural experiments

MIT License

10 stars 6 forks source link

adding license for the hardware itself and the documentation #7

Closed amchagas closed 1 year ago

amchagas commented 4 years ago

Hardware projects need more than one license. Specifically, they need:

a license for the software (Which is MIT)
a license for documentation and designs
a license for the hardware itself once it gets built.

This is a bit of a long topic to put on the issue, and it is not super pressing at this stage... So I would suggest for us to take a look at this material and circle back with suggestions for licenses soon.

isobianin commented 4 years ago

Hi @amchagas ! Regarding CERN or TAPR choice, it was hard to spot differences . In addition to the article you have mentioned, I read rationale of CERN and looked up TAPR. There is an another good comparison article and in the end I think that CERN is the way to go. But do we need to register BeeHive as CERN-W or CERN-S? I think CERN-W as it has more licensing margin for software used.

amchagas commented 4 years ago

Agreed!