Slashdot Mirror


What to Protect in Open Source Software

eldavojohn writes "I found a brief blog by Marc Fleury on something that seems to almost be an oxymoron — what you need to legally protect in Open Source Software. The short of it is that you should trademark your name and brand it. Which might explain Xen's stance on the use of the brand 'Xen'. Another short blog notes that you should also maintain control of your distribution channels. Fleury also states this interesting tidbit on protecting intellectual property in OSS, 'Short of filing patents, there isn't much you can do in OSS. Let's face it the IP is there for everyone to see. If you are in a mode where a lot of the value is the code itself then open sourcing under GPL or equivalent reciprocal license may be a good choice for you. At least you will make sure that ISV's that re-use your license get in contact with you and many of them will pursue dual-licensing, a strategy that is known to work to monetize an OSS user base (mySQL).' Is there anything else you should take measures to protect in open source software? Is it possible to maintain control of a project under the GPL or are you constantly faced with forks?"

2 of 96 comments (clear)

  1. Duh, by pb · · Score: 4, Interesting

    Didn't Red Hat already demonstrate this principle, years ago? Hopefully for his sake, they didn't trademark it too, pfft...

    --
    pb Reply or e-mail; don't vaguely moderate.
  2. no protection against forks except excellence by markhahn · · Score: 4, Interesting

    being GPL means, most of all, that there is no protection against forks. after all, GPL _is_ the ability to fork (ignore RMS's politics and all the other noise.)

    how do you avoid forks? by being on the right side - everyone pulls in slightly different directions, and any project would be a mess if it accepted all of them. it's also not just a matter of choosing - ideally, if a fork is threatened, the mainstream would trump the fork. that is, instead of some little feature X, develop a bigger, more general thing that is a superset of X. turn the fork into a trivial an unappealing, limited special case. I'm not advocating hyper-featurism, but to embrace big-picture generalizations.