veyepar: Understanding Copyleft

Author(s):	Simon Hornbachner
Location	F0.02
Date	apr Thu 28	Days Raw Files
Start	11:00	First Raw Start	error-in-template
Duration	01:00:00	Offset	None
End	12:00	Last Raw End
Chapters
Total cuts_time	None min.

370
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Understanding_Copyleft.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

More and more code is licensed under FLOSS licenses and more companies than ever are starting to incorporate FLOSS into their business and projects. Yet there is a lot of confusion about the different licenses, especially when it comes to copyleft licenses such as the GNU GPL family.
This talk will start with a very concise introduction to different FLOSS licenses in general and then go into more detail of what copyleft means and what different copyleft licenses require developers to do.
The presenter will specifically address common misconceptions about copyleft licenses - the most prevailing one being that all modifications of copylefted code need to be "made public" or "given back to the community" - and try to explain when and how certain copyleft provisions are triggered and what needs to be shared with whom and when.
In the end, a case for copyleft still being relevant these days (maybe even more so) will be made and different reasons for developers and businesses to release their code under a copyleft license will be given.

Comment:

production notes