license

[heisters]

By default, all github content is fully copyrighted, all rights reserved. I'd love to build on top of your code, but without an explicit MIT-compatible license, I can't. If you're interested in others contributing code to your repo, I'd suggest adding an MIT license to the repo.

Thanks!

[lichtfaktor]

Hi Ian,

I will sometime later. I don't know how that works or better what it means. But if you could help me a little with this I could set it up next week Thursday once I am back from holiday.

Best, Jens

LICHTFAKTOR GmbH Zülpicher Strasse 28 50674 Cologne / Germany

www.lichtfaktor.com

T +49 221 - 80 15 80 85 F +49 221 - 80 15 80 87 M +49 172 - 24 74 148

Am 27.09.2013 um 18:49 schrieb Ian Smith-Heisters notifications@github.com:

By default, all github content is fully copyrighted, all rights reserved. I'd love to build on top of your code, but without an explicit MIT-compatible license, I can't. If you're interested in others contributing code to your repo, I'd suggest adding an MIT license to the repo.

Thanks!

— Reply to this email directly or view it on GitHub.

[heisters]

Awesome, thanks very much. Usually I just add a file called "LICENSE" in the root of the repo, next to the README. Here's an example MIT license:

The MIT License (MIT)

Copyright (c) 2013 LICHTFAKTOR GmbH

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Basically, it just says that people can do whatever they want with your code, as long as they include the license with your name and copyright.

If you want an example, you can take a look at my MDDS repo. If you want to read up more about the MIT license before committing to it, the wikipedia article is a good start. You might also consider a FreeBSD license or something else entirely, depending on your and your company's positions regarding intellectual property. I just recommend MIT because it's what I use, many of my clients use, and seems to be pretty standard these days because it allows unencumbered use in commercial applications.

Hope that helps! Let me know if you have any questions. Really looking forward to playing with your code--just as soon as I can find a mini HDMI to HDMI adapter :P Enjoy the rest of your vacation!

[lichtfaktor]

Hi Ian,

thanks for your email.

Reading you're looking for a mini Hdmi Adapter I was wondering if you plan to record canon or go pro? Let me know if that's what you're planning. I am a little experienced with these ones. E.g. we first had trouble to capture canon mark ii as we were using a bad Hdmi cable (it was new and not broken)

Best, Jens

LICHTFAKTOR GmbH Zülpicher Strasse 28 50674 Cologne / Germany

www.lichtfaktor.com

T +49 221 - 80 15 80 85 F +49 221 - 80 15 80 87 M +49 172 - 24 74 148

Am 27.09.2013 um 19:45 schrieb Ian Smith-Heisters notifications@github.com:

Awesome, thanks very much. Usually I just add a file called "LICENSE" in the root of the repo, next to the README. Here's an example MIT license:

The MIT License (MIT)

Copyright (c) 2013 LICHTFAKTOR GmbH

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Basically, it just says that people can do whatever they want with your code, as long as they include the license with your name and copyright.

If you want an example, you can take a look at my MDDS repo. If you want to read up more about the MIT license before committing to it, the wikipedia article is a good start. You might also consider a FreeBSD license or something else entirely, depending on your and your company's positions regarding intellectual property. I just recommend MIT because it's what I use, many of my clients use, and seems to be pretty standard these days because it allows unencumbered use in commercial applications.

Hope that helps! Let me know if you have any questions. Really looking forward to playing with your code--just as soon as I can find a mini HDMI to HDMI adapter :P Enjoy the rest of your vacation!

— Reply to this email directly or view it on GitHub.