Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Have the licensing talk early to maximize impact

942 views

Published on

Lightning talk presented at OER15 in Cardiff.

The outputs of many collaborative projects often see limited use in the long term because neither partner is quite sure what is permitted. Frequently, the people involved in the creation of content have left their institutions and futher use and distribution of the developed works is in doubt.

Yet, in most projects, the talk about rights and licensing is left till close to the end or is omitted all together. People talk about the value of intellectual property but they never explore the limits unclarities about licensing impose on the potential impact of outputs. It is therefore essential that the licensing discussion is introduced early on in the development of the project.

This talk will present key talking points that have been used in three projects that have led to partners agreeing to licensing some or all of the work developed under the project using open licences. Often resistance to open licenses stems from ignorance and making a clear case for it as well as clearly outlining the options can prevent barriers from ever being formed in the first place.

Published in: Education
  • Be the first to comment

Have the licensing talk early to maximize impact

  1. 1. Have the licensing talk early to maximize impact: Experiences from three collaborative projects Dominik Lukes @TechCzech - Researchity.net
  2. 2. Attribution-ShareAlike
  3. 3. Questions / comments @TechCzech
  4. 4. Presentation on j.mp/licensing-talk
  5. 5. Three projects: iLearnRW, Load2Learn, LDD Navigator
  6. 6. Alt title: How I found out I’m a licensing geek!
  7. 7. Typed up in a few hours
  8. 8. Why?
  9. 9. People have inflated expectations of the value of their IP
  10. 10. People are ignorant of copyright law implications
  11. 11. Content everyone wants shared cannot be reused due to unclear copyright ownership
  12. 12. Solution?
  13. 13. Have the licensing talk early!
  14. 14. Licensing talking points
  15. 15. Value of IP
  16. 16. How are we leveraging the value of our IP?
  17. 17. Who sees our IP and would we benefit more if it was out in the open being used by people?
  18. 18. Do we have any IP locked away in documents that have not been used by anyone but may have impact if shared openly?
  19. 19. Lack of clarity in a collaborative project
  20. 20. Who owns the copyright? Are all people working on a collaborative project under the same contract with their institution?
  21. 21. How about copyright ownership under different jurisdictions? May not always be enforceable by contract?
  22. 22. What are specific conditions of use once all principals involved in creation and collaboration leave?
  23. 23. Reality of Open Licensing
  24. 24. You still OWN copyright of openly licensed materials!
  25. 25. Open licences can offer more realistic protection of your IP by securing attribution.
  26. 26. Many materials in education with permission to copy already effectively BY NC SA.
  27. 27. Open licences give explicit permission and remove incorrect assumptions about ownership.
  28. 28. Open Licensing avoids awkward conversations…
  29. 29. “I thought we owned that.” “We can only use this internally because we’re not sure if we own it.” “We need to get a permission from X who left 2 year ago before we can use this.”
  30. 30. Open Licensing business models
  31. 31. You can still sell openly licensed materials (printed versions, special formats, content subscriptions, …).
  32. 32. Openly Licensed materials can be doing the work of advertising other services.
  33. 33. Openly Licensed materials can directly support a charitable mission.
  34. 34. Other sources of funding / crowdsourcing can be available for the development and maintenance of openly licensed content.
  35. 35. Recommendations
  36. 36. Content CC BY or CC BY SA Code Modified BSD or (a)GPL
  37. 37. Results
  38. 38. All three projects where this was proposed accepted the idea in principle.
  39. 39. 1. Accepted with more restrictive license (added NC). 2. Accepted with more liberal license (BY instead of BY SA) 3. Accepted as proposed (BY SA)
  40. 40. It takes more work to get from agreement to actual implementation, but…
  41. 41. Load2Learn.org.uk/training/cuecards
  42. 42. OER Videos on YouTube.com/Load2Learn
  43. 43. iLearnRW will release code and content
  44. 44. bit.ly/cc-teachers
  45. 45. Image credits
  46. 46. Rainbow Bee-eater, food transfer by David and Dorothy Jenkins CC BY NC SA https://www.flickr.com/photos/78742710@N08/16174327408
  47. 47. Thank you @TechCzech

×