Your SlideShare is downloading. ×
ROI in a GPL World
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ROI in a GPL World

3,976
views

Published on

ROI in a GPL World (or, From Code to Cash) -- originally presented at the Chicago CMS Expo. See http://cmsexpo.net for additional details. …

ROI in a GPL World (or, From Code to Cash) -- originally presented at the Chicago CMS Expo. See http://cmsexpo.net for additional details.

The session covered the implications of using GPL'd software like Joomla! and Drupal, how to build sustainable (and legal) businesses around GPL'd products, and how to spot hippies in the wild.

Published in: Technology, Business

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,976
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
129
Comments
0
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • If you’re here, you’re probably using GPL.
    Topic: How businesses can build on GPL tools and profit.
    Emphasis is on code, that’s the trickiest.
  • The GPL is a software license. Explains what you can and can’t do.
    Mirror image of most licenses -- intended to ensure that:
    You CAN copy it.
    Anyone using it CAN customize it.
  • Richard Stallman, creator of the GPL.
    Dirty, Smelly Hippie. The GPL is political. Deal with it.
    Made by programmers (with help from lawyers) for programmers.
  • Free as in beer, not free as in speech.
    Programmers are free to do whatever they need to to make it work for them.Programmers are free to pass on their improvements to anyone else.
    “Zero-cost” programs and code may not be “free” in this sense
  • If you have a GPL program, you have the right to the source code (at no extra charge)
    You have the right to modify that source code.
    You have the right to distribute it to others.
    You have the right to sell it.
    You have the right to print it, roll it up, and smoke it.
  • If you have a GPL program, you have the right to the source code (at no extra charge)
    You have the right to modify that source code.
    You have the right to distribute it to others.
    You have the right to sell it.
    You have the right to print it, roll it up, and smoke it.
  • If you have a GPL program, you have the right to the source code (at no extra charge)
    You have the right to modify that source code.
    You have the right to distribute it to others.
    You have the right to sell it.
    You have the right to print it, roll it up, and smoke it.
  • If you have a GPL program, you have the right to the source code (at no extra charge)
    You have the right to modify that source code.
    You have the right to distribute it to others.
    You have the right to sell it.
    You have the right to print it, roll it up, and smoke it.
  • If you have a GPL program, you have the right to the source code (at no extra charge)
    You have the right to modify that source code.
    You have the right to distribute it to others.
    You have the right to sell it.
    You have the right to print it, roll it up, and smoke it.
  • If you DO distribute it, though, it has to be GPL’d
    You can’t restrict what others do with it (they get it under the GPL)
    You can’t add restrictions (that would be a pseudo-GPL license)
    You can’t combine it with things that aren’t GPL’d
    DERIVATIVE WORKS have to be GPL.
  • If you DO distribute it, though, it has to be GPL’d
    You can’t restrict what others do with it (they get it under the GPL)
    You can’t add restrictions (that would be a pseudo-GPL license)
    You can’t combine it with things that aren’t GPL’d
    DERIVATIVE WORKS have to be GPL.
  • Eggs = GPL, Toast must be GPL, too.
    Otherwise, “Toast And Eggs” can’t be GPL, and license is violated.
    Skillet doesn’t have to be. Either does the Orange juice.
    The Full text of the license, and the GPL FAQ, explains the details.
  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • If you’re a developer, why build on top of GPL?
    Lots of ideological reasons, but short answer: Everyone’s doing it.
    If you are willing to work with the GPL, you benefit from the network effect.

  • But what if I write code for money? If I share it, my ROI drops to zero.
    That’s definitely a problem. But it’s already happening around you.
    “Keep it to yourself” means “Someone else will build it.”

    Story of the union consultant whose “competitive advantage” code was cloned by community that needed it
  • Transcript

    • 1. from code to cash doing business with the GPL http://www.flickr.com/photos/nathangibbs/1360099367/
    • 2. http://www.flickr.com/photos/popilop/331357312/
    • 3. http://www.flickr.com/photos/gisleh/3306564460
    • 4. dirty smelly hippies http://www.flickr.com/photos/gisleh/3306564460
    • 5. http://www.flickr.com/photos/23912576@N05/3010067161/
    • 6. free as in freedom http://www.flickr.com/photos/23912576@N05/3010067161/
    • 7. http://www.flickr.com/photos/myeye/458096701/
    • 8. customization code sales silly hats distribution http://www.flickr.com/photos/myeye/458096701/
    • 9. http://www.flickr.com/photos/photohop/2913211897/
    • 10. your additions must be GPL. http://www.flickr.com/photos/photohop/2913211897/
    • 11. your additions must be GPL. (plugins, too) http://www.flickr.com/photos/photohop/2913211897/
    • 12. derivawhat? http://www.flickr.com/photos/cv47al/140523348
    • 13. http://www.flickr.com/photos/emagic/56206868/
    • 14. http://www.flickr.com/photos/emagic/56206868/
    • 15. what about my code? http://www.flickr.com/photos/lunadirimmel/2886049368/
    • 16. http://www.flickr.com/photos/vubui/47617247/
    • 17. code: is it what you do… http://www.flickr.com/photos/vubui/47617247/
    • 18. code: is it what you do… …or what you have when you’re done? http://www.flickr.com/photos/vubui/47617247/
    • 19. build to spec http://www.flickr.com/photos/pnuno/3289057516/
    • 20. hosted services http://www.flickr.com/photos/dotbenjamin/2575372856/
    • 21. support
    • 22. Consulting http://www.flickr.com/photos/theaftershock/2982078586
    • 23. Teaching & Training http://www.flickr.com/photos/benrussell/1477899923
    • 24. http://www.flickr.com/photos/thomashawk/2681744739
    • 25. gpl breeds gpl http://www.flickr.com/photos/thomashawk/2681744739
    • 26. gpl breeds gpl if you distribute, others can. http://www.flickr.com/photos/thomashawk/2681744739
    • 27. gpl breeds gpl if you distribute, others can. code: product or tool? http://www.flickr.com/photos/thomashawk/2681744739
    • 28. gpl breeds gpl if you distribute, others can. code: product or tool? sell your brain. http://www.flickr.com/photos/thomashawk/2681744739