Search

ROI in a GPL World

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    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

    Favorites, Groups & Events

    ROI in a GPL World - Presentation 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

    + Jeff EatonJeff Eaton, 6 months ago

    custom

    314 views, 0 favs, 0 embeds more stats

    ROI in a GPL World (or, From Code to Cash) -- origi more

    More info about this document

    CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

    Go to text version

    • Total Views 314
      • 314 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 2
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    -->
    Search
    RSS Feed
    What's new?

    © 2009 SlideShare Inc. All Rights Reserved