Slashdot Mirror


Trademarks Considered Harmful To Open Source

An anonymous reader touts a blog posting up at PC World titled "Trademarks: The Hidden Menace." Keir Thomas asks why open source advocates are keen to suggest patent and copyright reform, yet completely ignore the issue of trademarks, which can be just as corrosive to the freedom that open source projects strive to embody. "Even within the Linux community, trademarking can be used as obstructively as copyright and patenting to further business ends. ... Is this how open source is supposed to work? Restricted redistribution? Tight control on who can compile software and still be able to call it by its proper name? ... Trademarking is almost totally incompatible with the essential freedom offered by open source. Trademarking is a way of severely limiting all activity on a particular product to that which you approve of. ... If an open source company embraces trademarks then it embraces this philosophy. On the one hand it advocates freedom, and [on] the other it takes it away."

9 of 226 comments (clear)

  1. Trademarks helps some of OSS best organisations by levell · · Score: 5, Insightful

    I disagree with the whole underlying point of the article. I think Mozilla should be able to stop someone taking their source, adding a whole bunch of unstable "improvements" as patches and calling it Firefox. It would damage a brand that is one of the best brands that FOSS currently has. It doesn't stop people getting the browser, if they don't Mozilla's restrictions they could call it, say, EarthHorse.

    The article throws around terms like "restricted distribution" and "severely limiting all activity" but gives examples like CentOS where CentOS and Red Hat exist happily together but with Red Hat still able to build up a brand with some protections.

    The article ends "just like patents and traditional copyright, it's totally incompatible with the spirit and ethos of open source software.". People here may not like the length that copyright lasts for but the GPL relies on the fundamental idea of copyright. Similarly there may be some issues with trademarks but if so they need patching not a whole sale revolution as this article seems to suggest.

    --
    Struggling to find a day everyone can make? WhenShallWe.com
    1. Re:Trademarks helps some of OSS best organisations by wisty · · Score: 5, Insightful

      Trademarks do seem a little harmful to open source. It's a bit of a pain to explain why Firefox is the same thing as Ice Weasel. Inconsistent terminology can hurt a field - just look what happened to postmodernism.

      But "Considered Harmful" is a bloody big call. That's comparing trademarks to "gotos". Ouch. Open source has other worries - like web applications (online data processing), proprietary devices (iPhones), companies turning GPL programs into XML wrapped libraries, the .net framework, walled garden communitites (facebook), and proprietary file / stream formats.

      Trademarks? Big deal.

    2. Re:Trademarks helps some of OSS best organisations by Daengbo · · Score: 5, Insightful

      CentOS does the same thing with the whole of Red Hat. They just strip out the RH trademarks. Should they be allowed to call it Red Hat? No. Does removing the trademarks restrict their freedoms in any way? Also no.

    3. Re:Trademarks helps some of OSS best organisations by shutdown+-p+now · · Score: 5, Insightful

      Trademarks do seem a little harmful to open source. It's a bit of a pain to explain why Firefox is the same thing as Ice Weasel.

      Would you prefer having to explain why some random IE-based China-made shareware/adware browser that's called "Firefox Pro" isn't really Firefox at all?

      Because that's pretty much where we'd be if it wasn't trademarked.

    4. Re:Trademarks helps some of OSS best organisations by blowdart · · Score: 5, Interesting

      Except ... Rails. Rails is a trademark, so in theory we now need to write Rails(tm). Now I can understand the Ruby on Rails(tm) logo being trademarked, if you don't want it appropriated, but Hansson has gone a bit further.

      On the use of the logo he's said

      So I only grant promotional use for products I'm directly involved with. Such as books that I've been part of the development process for or conferences where I have a say in the execution.

      This steps out of protection and into control, he's been refusing to allow books to use the logo on their covers. He's even trademarked "Ruby on Rails", taking the name of something he didn't invent or write and using that as part of his mark;

      "Rails", "Ruby on Rails", and the Rails logo are trademarks of David Heinemeier Hansson.

      Want to have a Ruby on Rails(tm) conference? Better not include the name of the platform in your conference name then, that would be violating Hansson's trade mark. Even more "interesting" is the Ruby on Rails(tm) logo was a community effort (although the wiki pages for that are now gone. The original logo was even open source. The money to register the trademarks came from the community, but the marks are in the hands of Hansson alone.

      It's not trademarks that are the problem, it's the person who controls them. If, for example, the Rails(tm) marks were overseen by a committee (made up, as a starting point, of everyone that helped pay for them) then that would be more acceptable than the current situation.

    5. Re:Trademarks helps some of OSS best organisations by Daengbo · · Score: 5, Funny

      I live in Asia so I'll just have a "Luby on Lails" conference, and no one will be confused at all.

  2. It's not about Freedom by GameGod0 · · Score: 5, Insightful

    It's about protecting your users, and protecting your project.

    Take a large, reputable open source project like Audacity. If some scammer comes along and bundles their own version of Audacity with some spyware and tries to distribute it under the Audacity name, this is damaging to both users and the reputation of the software. Audacity's defense against people like this is their trademark. Nobody will confuse real "Audacity" with any ripoff, because nobody else can use the name.

    This also protects the developers, who have worked hard to produce great software, and who deserve to have it recognized as something special on their resumes/CVs. Preserving the reputation (ie. name) of your software project helps ensure their contributions to the project aren't devalued.

    Lastly, the Mozilla example in the article can easily be countered by the infamous OpenSSL/Debian fiasco, where a Debian packager incorrectly patched OpenSSL and created a vulnerability. This was certainly damaging for OpenSSL's reputation, even though it wasn't their fault. If Ubuntu decides to patch Firefox and introduces bugs, it's Firefox (NOT Ubuntu) who looks bad to users. IMO this is good justification for exercising ownership of your trademark.

  3. Open source is about SOURCE by SuperKendall · · Score: 5, Insightful

    Just because source is open does not give you the right to hijack the work of a team and call something by the same name.

    It does give you the right to take the source and make something else with it, and that is great. But because so much of the reward of open source is working on something that many people get to use an enjoy, diminishing the power of trademark removes a strong element of motivation by allowing names to mean less through dilution.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  4. Your Mark by OnlyHalfEvil · · Score: 5, Insightful
    I take it all back, I think this is a dumb idea.
    Signed,
    Keir Thomas

    What?
    If trademarks are a restriction of freedom, then me using Keir's name to endorse my own ideas sounds like exactly the type of freedom he's arguing for. So what if it breeds confusion and implies an endorsement that doesn't actually exist?