Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
serialseb.github.com/_posts/2009/2009-10-30-derivative-work-for-speakers-or-guide.html
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
12 lines (11 sloc)
1.56 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- | |
layout: post | |
title: Derivative work for speakers, or a guide on how to use my content | |
date: '2009-10-30T13:06:00.001Z' | |
tags: [conferences] | |
modified_time: '2009-10-30T13:06:33.583Z' | |
blogger_id: tag:blogger.com,1999:blog-4015568221071268916.post-5038945662721975583 | |
comments: true | |
blogger_orig_url: http://serialseb.blogspot.com/2009/10/derivative-work-for-speakers-or-guide.html | |
--- | |
<p>I realize I’ve never clarified what you can or cannot do with my slides and my talks. So here’s a clarification for anyone that wishes to inspire themselves from my work (aka derivative works) or reuse them.</p> <p>I do not release my presentations, the videos or the content / slides under any kind of open-source license. Not even creative commons. Presentations take a while to build, structure and mature, and this cost me money. If you’re going to use them, you’re effectively using my work.</p> <p>Now, I’m not anal about how you use the content, it’s written to benefit the community. However, ff you want to create a derivative work, or even re-present my presentations, I’m happy for you to do so provided the following conditions are met:</p> <ul> <li>The original work author is to be named (that’s me), together with my company name (that’s Caffeine IT).</li> <li>It would be terribly appreciated to link to the original content, or my blog, or both.</li> <li>You notify me that you’re going to use the content, or created a derivative work.</li> </ul> <p>If you have any issue with any of that, don’t hesitate to send me an email we can chat about it.</p> |