Update dependancies_and_licenses.md

This commit is contained in:
langolierz
2018-05-02 11:15:52 +12:00
committed by GitHub
parent 7536f9e4dc
commit e4d48bdaa1

View File

@@ -1,28 +1,39 @@
# license info
the more features i add to recur the more dependancies on other software i create. i want to add a license for my work on recur and acknowledge the software it uses , and the license they use. ## software
also need to decide whether my design needs a license outside of the software. i have chosen to [license] r_e_c_u_r's software under [GPL-3.0] for the following reasons:
from wikipedia on [gpl]: - i agree with the copy-left philosophy and want to empower the users, ensuring it remains (as intended) an open community project.
`the licensing depends only on the used libraries and software components and not on the underlying platform` - although i have not modified any existing open-source projects to create r_e_c_u_r , it does run on top of many dependencies, some of which have GPL licenses (omxplayer in particluar). i wish to respect the sentiment of these developers, even if not required legally.
- for low-level utility tools with numerous, varied uses, a permissive open-source licence like MIT can empower other developers to create and license without restrictions. however r_e_c_u_r is an embedded top level application that is unlikely to be useful in any other context
this licence only applies to the code in this repo. see below for a list of external programs that r_e_c_u_r uses and their respective repos/sites for more infomation.
dependancy | use | license ## hardware
besides the application code licensed above , i would like all original hardware designs licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License]. this includes the enclosure design , custom key stickers and assembly. it does __not__ apply to, and i am __not__ the copyright holder for _Raspberry Pi 3 Model B_ , _3.5 Inch TFT LCD Module For Raspberry Pi_ , _Generic Wireless USB Numeric Keypad_ or any other third party extension / accessory.
# program dependencies
dependency | use | licence
--- | --- | --- --- | --- | ---
rasbian | the os on pi | based on debian , made up of different licensed programs rasbian | the os on pi | based on debian , made up of different licensed programs
python | lanuage | open-source , gpl-compatible python | lanuage | open-source , gpl-compatible
omxplayer | the media player | GPL-2.0 omxplayer | the media player | GPL-2.0
omx python wrapper | for controlling omxplayer | LGPL omx python wrapper | for controlling omxplayer | LGPL
dbus-python | dependacy for omx wrapper | permissive, non-copyleft dbus-python | dependacy for omx wrapper | permissive, non-copyleft
tkinter | the tui display | bsd tkinter | the ui display | BSD
picamera | interface with capture | bsd picamera | interface with capture | BSD
mido | interface with midi | mit mido | interface with midi | MIT
python-rt-midi | midi backend | mit / modified mit python-rt-midi | midi backend | MIT / modified MIT
gpac (mp4box) | creating mp4 file | lgpl gpac (mp4box) | creating mp4 file | LGPL
mscorefonts | the current display font (may need to change this) | freeware under a [proprietary license] mscorefonts | the current display font (may need to change this) | freeware under a [proprietary license]
git | used to install and update | GPL-2.0 git | used to install and update | GPL-2.0
besides the fonts which are a special case (and some low level black box chips on raspi), all other software is open source. ## some research / thoughts about how licences work and interact.
it will be best to replace the mscorefonts with something open...
i have not modified any of the programs that are used in recur. they are all being used either under a permissive license or as part of the operating system. i can license my program however i choose, i can not license (for example) an img that contained gpl-2.0 programs with a non gpl compatable license. i have not modified any of the programs that are used in recur. they are all being used either under a permissive license or as part of the operating system. i can license my program however i choose, i can not license (for example) an img that contained gpl-2.0 programs with a non gpl compatable license.
@@ -34,9 +45,9 @@ some [interesting discussion] around difference between modifying a gpl program
there is no restrictions to permissive installer scripts downloading gpl licensed programs (or even the freeware fonts it seems) there is no restrictions to permissive installer scripts downloading gpl licensed programs (or even the freeware fonts it seems)
for the non-software side of recur (the case etc) it can be licensed under cc , with apropriate [markings] for third party content (ie screen , usb keypad , raspberry pi) [license] : ../LICENSE.md
[GPL-3.0]: https://www.gnu.org/licenses/gpl-3.0.en.html
[gpl]: https://en.wikipedia.org/wiki/GNU_General_Public_License#Use_of_licensed_software
[proprietary license]: https://en.wikipedia.org/wiki/Core_fonts_for_the_Web [proprietary license]: https://en.wikipedia.org/wiki/Core_fonts_for_the_Web
[markings]: https://wiki.creativecommons.org/wiki/Marking/Creators/Marking_third_party_content [markings]: https://wiki.creativecommons.org/wiki/Marking/Creators/Marking_third_party_content
[interesting discussion]: https://softwareengineering.stackexchange.com/questions/289785/can-i-distribute-a-gpl-executable-not-a-library-in-a-closed-source-application [interesting discussion]: https://softwareengineering.stackexchange.com/questions/289785/can-i-distribute-a-gpl-executable-not-a-library-in-a-closed-source-application
[Creative Commons Attribution-ShareAlike 4.0 International License]: https://creativecommons.org/licenses/by-sa/4.0/