Technology / Open Source @ Creative Commons (CC Salon SF, August 2009)

2,911 views

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,911
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Technology / Open Source @ Creative Commons (CC Salon SF, August 2009)

  1. 1. [pithy title here]
  2. 4. <a href=” http://creativecommons.org/licenses/by/3.0/ ” rel=”license”> Attribution 3.0 Unported </a>
  3. 5. Why do we care? Programs should be able to answer simple questions about licensed works. <ul><li>What is the work's license?
  4. 6. Allows commercial use?
  5. 7. Are derivative works allowed?
  6. 8. How do we attribute the work? </li></ul>
  7. 9. CC Rights Expression Language
  8. 13. Integrating CC
  9. 14. Integrating License Selection <ul><li>Partner Interface
  10. 15. Simple Chooser
  11. 16. Web Services </li></ul>
  12. 17. Partner Interface <ul><li>Pop-up or iframe for web applications
  13. 18. Utilizes the same license selection rules as license engine
  14. 19. Returns a license URL, name to your application via HTTP GET </li></ul>
  15. 20. Simple Chooser <ul><li>Drop-down license selector
  16. 21. Optionally exclude licenses by attribute code </li><ul><li>ie, ?exclude=nd </li></ul></ul><script type=&quot;text/javascript&quot; src=&quot;http://api.creativecommons.org/rest/dev/simple/chooser.js&quot; > </script>
  17. 22. Simple Chooser
  18. 23. Web Services <ul><li>Provide access to the full licensing dataset
  19. 24. Localized “questions” for implementing your own version of cc.org/license
  20. 25. HTTP interface; take as little or as much as you need
  21. 26. But... requires more work to use.
  22. 27. http://api.creativecommons.org/docs </li></ul>
  23. 28. Open Source at CC
  24. 29. CC is built on open source <ul><li>“LAMPP” – Linux / Apache / MySQL / PHP / Python
  25. 30. BB Press
  26. 31. WordPress
  27. 32. Zope 3
  28. 33. Django
  29. 34. CiviCRM
  30. 35. Etc </li></ul>
  31. 36. Finding Our Code <ul><li>Git and Subversion repositories </li><ul><li>http://code.creativecommons.org/ </li></ul><li>Roundup for bug tracking
  32. 37. BSD/GPL/AGPL license </li></ul>
  33. 38. Talking About our Code <ul><li>cc-devel mailing list </li><ul><li>http://lists.ibiblio.org/mailman/listinfo/cc-devel </li></ul><li>#cc on IRC (irc.freenode.net) </li><ul><li>nathany, nkinkade, Bovinity, JED3, paroneayea are all CC Staff
  34. 39. currybot can tell you what's for lunch (when online) </li></ul></ul>
  35. 40. You Can Help! <ul><li>OOo Add-in
  36. 41. MozCC: The Next Generation
  37. 42. CMS Integration
  38. 43. Copy and Paste tools
  39. 44. Bugs! http://code.creativecommons.org/issues </li></ul>
  40. 45. Nathan R. Yergler Chief Technology Officer Creative Commons [email_address] @nyergler [identi.ca] nathany [irc.freenode.org]

×