Slashdot Mirror


Small OSS Library Project Battles US Corporation

New submitter abesottedphoenix writes "The rural library responsible for the first open source library catalogue is under attack from defence contractor PTFS. More than a decade after rolling out Koha (which we've discussed in the past), they now find themselves in a battle to keep a generic Maori term within the public domain. The story is also covered at Radio NZ. "

118 comments

  1. FFS by Anonymous Coward · · Score: 0

    I for one note the correct spelling of the word 'Maori' and find this site grinding at my roots up to my boots in incompetence!!

    1. Re:FFS by NZKiwi · · Score: 2

      I for one note the correct spelling of the word 'Maori' and find this site grinding at my roots up to my boots in incompetence!!

      I don't think he misspelled Maori deliberately - I've submitted one of the dupes to this story - the Slashdot editing/preview ate the a-macron in Maori and displays it as Mori instead; so I expect abesottedphoenix did the same thing.

    2. Re:FFS by Anonymous Coward · · Score: 0

      +1 for rhyme? I find it funny spelling can be overseen by admins and thought the hurt I felt should be achknowledged

  2. generic Mori? by CrimsonAvenger · · Score: 1, Informative

    Am I confused today, or did you mispell Maori?

    That said, Trademark only applies in a specific field. If whoever it is has a Trademark for anything other than a library, his trademark in no way impacts the small library in question...

    --

    "I do not agree with what you say, but I will defend to the death your right to say it"
    1. Re:generic Mori? by Anonymous Coward · · Score: 3, Insightful

      I know it is pointless to say - but RTFA. PTFS wants the trademark for their fork of the library software.

    2. Re:generic Mori? by Anonymous Coward · · Score: 0

      Maybe RTFA yourself; it says no such thing.

    3. Re:generic Mori? by MrHanky · · Score: 3, Informative

      No?

      However, the trust says an American company named LibLime has hijacked the system and wants to use it for its own private client base.

      The company has also been granted provisional rights to the name Koha by the Ministry of Economic Development.

      "We did something really good and we gave it away to the world and it's been a glorious thing globally for 12 years," the trust's head of libraries, Joann Ransom, told Radio New Zealand.

      "And now this American corporate wants to take it."

    4. Re:generic Mori? by avgjoe62 · · Score: 2, Funny

      They would have spelled the term correctly, but to do so violates someones trademark on the term "M-a-o-r-i"

      --

      How come Slashdot never gets Slashdotted?

    5. Re:generic Mori? by polymeris · · Score: 2

      Not even "Māori" displays correctly. How come slashdot still doesn't support non ASCII characters? At this point it is probably more of a tradition thing than difficulty of implementation, right?

    6. Re:generic Mori? by DMFNR · · Score: 1

      Posting to cancel wrong moderation.

    7. Re:generic Mori? by Anonymous Coward · · Score: 0

      Well maybe PTFS should get the fuck off and find their own name instead of trying to be the big fat assed foul smelling bullys all it boils down to is the original name is already a known name so they want to hijac it to save them the job of publicity freakin tossers

    8. Re:generic Mori? by Anonymous Coward · · Score: 0

      There are about three codepoints in Unicode that, if allowed to enter page text, can mess up display on certain browsers in a way that could potentially be used to make it look like a comment has a higher score than it really has.

      Apparently this is a huge deal, and blacklisting a handful of non-printing characters using the convenient classifications already provided in the Unicode standard is somehow too difficult, so we're stuck with plain ASCII on Slashdot in 2011.

  3. Mori? by ratguy · · Score: 4, Insightful

    I think you mean Maori, the indigenous people of New Zealand.

    1. Re:Mori? by Anonymous Coward · · Score: 1

      Of course there are no Maoris on slashdot.

    2. Re:Mori? by jd · · Score: 4, Interesting

      There may well be Maoris on Slashdot. You can't see tattoos over the Internet. Now, there are probably no Moa on Slashdot and I hope there are no Keas (they're terrorists, I tell you!), but that's ok, there are enough bird-brains as it is. I have great respect for the Maori and it is intensely sad that I lost all of my mementos from my year in New Zealand after a storage place fire.

      Back to the issue at hand. It is completely reprehensible that a "common word" (because it IS a common word in New Zealand) can be trademarked at all. That is not acceptable, in and of itself. It is a flagrant abuse of the system, relying on the fact that Americans are not very up on foreign cultures. I am increasingly of the opinion that words should not be trademarkable at all. A "trademark" is, after all, first and foremost a mark. From the Sumerians to the Victorian English, this has been a stamp, a unique symbol that denotes the origin and guarantees authenticity. Arguably, the seals produced by stamps and signet rings serve the same function.

      You can always make a new symbol. Creativity is endless. But you can't create a new language every time foreigners decide to trademark words from it.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:Mori? by GoodNewsJimDotCom · · Score: 4, Funny

      Maybe he means Moria, the abandoned home of the Dwarves.

    4. Re:Mori? by masternerdguy · · Score: 1

      He might have been referencing Father Ted with that line (Of course there are no Maoris on Craggy Island).

      --
      To offset political mods, replace Flamebait with Insightful.
    5. Re:Mori? by Anonymous Coward · · Score: 1

      No No, he means Mario that Italian plumber that jumps on turtles.

    6. Re:Mori? by currently_awake · · Score: 3, Insightful

      Apple is a common word, in the USA. Apparently you CAN trademark common words.

    7. Re:Mori? by jd · · Score: 1

      Which, IMHO, is utterly wrong, completely in violation of the spirit of what a trademark is and probably in technical violation of the written law but IANAL.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    8. Re:Mori? by Rogerborg · · Score: 0

      It's spelled "Mario". The indigenous peoples of New Zealand are a proud race with a noble history of cannibalism and plumbing.

      --
      If you were blocking sigs, you wouldn't have to read this.
    9. Re:Mori? by Talderas · · Score: 1

      No no... he means Boatmurdered where the dwarves were obsessed with cheese, talking with dwarves, and the killing of dwarves by pachyderms.

      --
      "Lack of speed can be overcome. In the worst case by patience." --Znork
    10. Re:Mori? by Anonymous Coward · · Score: 0

      No, it's not. But don't worry, it's pretty danged clear that you're not informed about the purpose of trademarks, much less actually a lawyer.

    11. Re:Mori? by Kalriath · · Score: 1

      Not in New Zealand you can't. Although apparently that only applies to little people.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    12. Re:Mori? by Anonymous Coward · · Score: 0

      Of course there are no Maoris on slashdot.

      Pkokohua!

  4. thank you, summary makes no sense by richlv · · Score: 2, Interesting

    ok. usually i can understand /. summary immediately. sometimes i have to read the article. sometimes i have to do some extra research.

    but this summary just does it - it makes so much "no sense" that i have no fucking idea what is it about and i'm just going to skip the topic.

    --
    Rich
    1. Re:thank you, summary makes no sense by Anonymous Coward · · Score: 0

      Thanks for letting us know. It was the top concern on our minds.

    2. Re:thank you, summary makes no sense by nadaou · · Score: 5, Informative

      > but this summary just does it - it makes so much "no sense" that
      > i have no fucking idea what is it about and i'm just going to skip
      > the topic.

      which is real a shame, because what is happening is nasty, evil, theft (in the correct IP usage of the term) from a long established volunteer community by newly arrived greedy corporate. Or just take a moment to listen to the linked 2 minute mp3?

      here is the real project's "about" page: http://koha-community.org/about/

      "Koha" is a Maori word meaning gift (often in a quid quo pro sense). Note that Wikipedia lists it as a custom. It is a truly wonderful name for a GPL'd project for the public good.
      http://en.wikipedia.org/wiki/Koha_(custom)

      read the mailing list plea from the librarian here:
      http://lists.nzoss.org.nz/pipermail/openchat/2011-November/008940.html

      a blog post:
      http://news.tangatawhenua.com/archives/14545

      and the thread that follows.
      http://lists.nzoss.org.nz/pipermail/openchat/2011-November/thread.html#8943

      favourite quote from the ensuing thread:

      Oh, and that you can't win a Wikipedia fight against librarians.

      listen to more audio from NZ public radio than what's in the /. submission here:
      (Scroll down to the Ogg @ 9:44 am)
      http://www.radionz.co.nz/national/programmes/ninetonoon

      The project was founded by a small country town library in 1999 when the Y2K bug was taking out their existing solution and they couldn't afford to buy another one. Since then it has grown to be a large and wonderful FOSS success story. Until last year, when an associated company that held the domain name and provided commercial support got bought out by a big corporate bully, who took ownership of the DNS and domain name, taken over the home page, obfuscated links to and existence of the community (which has had to rush out and register http://koha-community.org/ instead of their original koha dot org site), and now are trying to block the community from being able to use their own name, on their own turf. It seems that Liblime has grabbed the trademark already in the US; the original koha-community.org group after they got over their shock was able to get in first in the EU, but not Liblime (a US company) has moved in to grab it in the community's home country of New Zealand.

      PTFS/Liblime's actions here are truly despicable, and if I were a customer I'd have to wonder if they are willing to screw over the people who built up the project from nothing, what is stopping them from screwing me over too?

      Please visit the Koha-community.org site, read the plea: http://koha-community.org/plea-horowhenua-library-trust/

      and help out their non-existent legal fund with a small donation:
      https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FQ6JH3L48LV5Y
      (your dollar goes far here; they are a registered legal non-profit, paypal's freezing of funds typically happens to unregistered projects who are basically ignoring tax laws, so they should be safe from that)

      written article here:
      http://www.radionz.co.nz/news/national/91830/lawyer-labels-overseas-trademark-of-'koha'-offensive

      --
      ~.~
      I'm a peripheral visionary.
    3. Re:thank you, summary makes no sense by bhagwad · · Score: 1

      Wow - there has to be an easier way to explain this. A two three sentence summary perhaps? Like what the problem was before, what great thing was conceived of and what the threat currently is...

    4. Re:thank you, summary makes no sense by Anonymous Coward · · Score: 0

      oi

    5. Re:thank you, summary makes no sense by theVarangian · · Score: 5, Informative

      Wow - there has to be an easier way to explain this. A two three sentence summary perhaps? Like what the problem was before, what great thing was conceived of and what the threat currently is...

      Hmmm... simple... let me try.

      1. 1) Once upon a time a small rural library could not afford to upgrade their library management software due to a nasty bug.
      2. 2) The small rural library then got the bright idea to set up a FOSS project aimed at creating a free alternative library management software system and named it Koha.
      3. 3) The Koha library management software project became a big FOSS success.
      4. 4) Due to a variety of reasons the homepage and domains of the Koha project were taken over by a bunch of US American corporate weasels called PTFS.
      5. 5) The US corporate weasels then started a campaign aimed at convincing the world that they have taken over the Koha project and are the only legitimate source of Koha software and support. Basically they are trying to hijack the Koha project.
      6. 6) This campaign by PTFS has now gone so far that they have trademarked the word Koha. in New Zealand for no other reason than to deny it's use to the Koha foundation.
    6. Re:thank you, summary makes no sense by bhagwad · · Score: 1

      Thank you! Now I understand.

    7. Re:thank you, summary makes no sense by Anonymous Coward · · Score: 0

      No company "gets bought out" by a "corporate bully". Their directors decided to sell to PTFS out of their own greed.

      No sympathy for the Koha "community". Fork and rename.

    8. Re:thank you, summary makes no sense by bluefoxlucid · · Score: 1

      So... PTFS and Liblime need their Wikipedia pages updated with something coherent that documents this mess. That way the Google test will always reveal such actions that reflect poorly on the company (i.e. they deal falsely and unfairly, thus their reputation is damaged by their actions--make this public and clear to enforce that damage).

    9. Re:thank you, summary makes no sense by richlv · · Score: 1

      thank you, slashdot, for reviving some old comment of mine and attaching to this article. for the record, this comment was originally to some other article where summary indeed didn't make sense (this one actually does).\

      it was a bit of a surprise, though. started reading the comment. thoughts go like this :
      "hey, what's this guy (there are no girls on /.) having a problem understanding, this was a pretty clear summary... hmm, i think i have seen this somewhere before... OMGWTF"

      --
      Rich
    10. Re:thank you, summary makes no sense by HeckRuler · · Score: 1

      +1 ThisGuyNeedsToBeAnEditor

    11. Re:thank you, summary makes no sense by Obelos · · Score: 1

      4) The actual story is not particularly weasely. HTL contracted Katipo Communications to write Koha in 1999. Katipo sold all of its Koha-related assets (including all its Koha copyrights and the koha.org domain) to LibLime in 2007. With the blessing of the community, LibLime also reserved the US trademark in 2008. The community split in 2008/2009. LibLime then sold its assets to PTFS in 2010, just after submitting the application for NZ trademark. 5) PTFS/LibLime does not try to convince anyone that theirs is the only Koha distribution. Conversely, HLT's community cannot seem to shut up about theirs being "real Koha". 6 ) Why the NZ app was filed is a mystery known only by the former LibLime owners. PTFS intends to hold the NZ TM for non-exclusive use, just as it has held the US TM for non-exclusive use for several years now, having never contested anyone else's use of the name.

    12. Re:thank you, summary makes no sense by Red+Flayer · · Score: 1
      Mistake in your description of events.

      5) PTFS/LibLime does not try to convince anyone that theirs is the only Koha distribution.

      Horsepoop. By asserting their trademark, they are *in fact* asserting that they are the only Koha distribution. That's what a trademark does.

      --
      "Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
  5. MAORI by Anonymous Coward · · Score: 0

    Not Mori.

  6. Maori definitely misspelt by Anonymous Coward · · Score: 5, Informative

    Kia ora from Wellington NZ
    Maori was definitely misspelt
    link to wikipedia article on the Maori term Koha
    http://en.wikipedia.org/wiki/Koha_(custom)

    1. Re:Maori definitely misspelt by Eythian · · Score: 1

      The real spelling can't be written on slashdot. If I write it correctly, it comes out "Mori." Or, in LaTeX: M\-{a}ori (IIRC.) It seems plausible that the editing process swallowed a macron.

  7. Summary by karit · · Score: 5, Insightful

    Basically a company who has extended and NOT given back to the community is now wanting the trademark the name of the Open Source product.

    --
    http://blog.karit.geek.nz/
    1. Re:Summary by kevin_j_morse · · Score: 2

      That's what I got out of it...

      Not sure what the hell the defense contractor has to do with anything? LibLime appears to be the guilty party here.

    2. Re:Summary by Anonymous Coward · · Score: 3, Informative

      That's what I got out of it...

      Not sure what the hell the defense contractor has to do with anything? LibLime appears to be the guilty party here.

      Liblime sold themselves to PTFS (a defense contractor) in 2010

      'LibLime was founded in 2005, as part of Metavore Inc.[2] and purchased by Progressive Technology Federal Systems, Inc. (PTFS) in 2010.'
      http://en.wikipedia.org/wiki/Liblime

    3. Re:Summary by Anonymous Coward · · Score: 0

      There is probably no better example of how completely fucked up IP law is internationally than this.

      If someone has an example, please provide.

      I feel for this project. It's totally fucking ridiculous.

    4. Re:Summary by Anonymous Coward · · Score: 0

      The fact that's a defense contractor isn't important. Maybe it's about trying to get more sympathy by suggesting the DoD is comming after them. In this case it would be more appropriate to mention liblime is also a WIPO contractor, maybe that's where they got their idea from...

    5. Re:Summary by Obelos · · Score: 1

      This is patently false. LibLime's Koha git repo is available on Github: https://github.com/liblime/LibLime-Koha. HLT community members have even submitted pull requests to our project.

    6. Re:Summary by Jonner · · Score: 1

      Basically a company who has extended and NOT given back to the community is now wanting the trademark the name of the Open Source product.

      If LibLime has distributed Koha binaries, but not source, they have violated its Copyleft license, which is much more serious than a trademark dispute. Is there any evidence they've done so? LibLime's FAQ says

      Q. LibLime Koha is open-source software; doesn’t that mean it’s free?
      A. Yes, LibLime Koha is open source and so LibLime Koha is free, in fact you can download it yourself from a number of sites, including here. LibLime is an open source support company and we were established in 2005 to work with libraries that wish to run LibLime Koha but do not have the internal resources to manage a system.
      LibLime offers the following services:
      -Professional project management for your LibLime Koha implementation
      -Set up and implementation of your LibLime Koha instance
      -LibLime Koha Training
      -Migration of legacy data
      -Hosting and support (help desk and online ticketing system)

    7. Re:Summary by Obelos · · Score: 2

      Koha is written in Perl. There's no (practical) way to distribute a binary. We make our code freely available through Github.

    8. Re:Summary by Kalriath · · Score: 1

      Oh, so you ARE an employee of LibLime then. I figured you were, since you're the only person defending this shitty behaviour.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    9. Re:Summary by Eythian · · Score: 1
    10. Re:Summary by Obelos · · Score: 1

      There were others, but I turned them down because they were poor code.

    11. Re:Summary by Eythian · · Score: 1

      Also, the last update to that codebase was in July. Your developers can't be very busy then.

  8. Crazy by Anonymous Coward · · Score: 0

    An obscure contractor without vowels should be unable to complain, let alone annunciate.

    1. Re:Crazy by interval1066 · · Score: 1

      Why? We now need a law to keep people from saying stupid things? Let 'em fumble.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
  9. Better summary by Anonymous Coward · · Score: 5, Informative

    A commercial company that has been reselling an open-source product now wants to claim ownership of the product itself. Because the current owners are not well funded, there is a prospect that they will be able to do so.

    The current owners, being incredibly naive, claim to have been under the impression that foreigners couldn't trademark Maori words. (Possibly they've never heard of Coca-Cola. Even now, they're only trying to fight the trademark application in New Zealand, so I'm not sure what (if any) effect that would have internationally.

    1. Re:Better summary by Old+Wolf · · Score: 2

      'Poor' is a better word than 'naive'. They're just a small library, they cannot afford things like legal fees. Hopefully the EFF will step in here.

    2. Re:Better summary by Anonymous Coward · · Score: 0

      Your understanding of the word 'naive' is 'poor'.

    3. Re:Better summary by Anonymous Coward · · Score: 0

      claim to have been under the impression that foreigners couldn't trademark Maori words.

      That isn't even close. Did you read the article or is this just a gut reaction? If this was a fully formed opinion you may want to take stock of your mental state. Twisting a situation to this degree is fairly clear evidence of a thought disorder.

    4. Re:Better summary by Anonymous Coward · · Score: 0

      It has been well publicized that some people are pathological liars and will invent whatever stories will get them what they want on the spot. (This is a general point, I'm not claiming the GP poster is one.) However, it seems to me that the same mechanism is there in all neurotypical people, only they employ it to a far lesser degree. Very few people are careful to stick to 100 % facts in a discussion.

  10. The history by Anonymous Coward · · Score: 5, Informative

    Short version: PTFS ended up owning the community domain name and a trademark for Koha due to some weird stuff that has happened over the past 12 years. PTFS is not well regarded by the general community due to how they try to confuse users into thinking theirs is the only version, their practices which (from what I can tell) make versioning a nightmare, and their lack of regard for the community. The community does not want them to gain any more ground.

    1. Re:The history by Anonymous Coward · · Score: 0

      To clarify - they bought a domain name, but no trademark as no trademark has ever existed.

    2. Re:The history by Anonymous Coward · · Score: 2, Informative

      I believe they already have a US trademark for Koha (3619202).

    3. Re:The history by Obelos · · Score: 1

      This is probably the fairest assessment I've seen, save that PTFS doesn't "confuse users into thinking theirs is the only version" any more than the HLT community does.

  11. Defense contractor? by Anonymous Coward · · Score: 2, Informative

    Sure, PTFS counts some DoD entities among its clients, but it's odd to refer to a company that has clients like the Holocaust Museum and the National Library of Medicine as a defense contractor.

    That being said, it's super shady for a company that got started solely to provide end-user support for an OSS system to try and trademark that system's name.

  12. Licensing? by cuncator · · Score: 2

    Can someone explain to me how this isn't a violation of the copyleft GPL Koha is distributed under?

    1. Re:Licensing? by Anonymous Coward · · Score: 0

      The problem is the copyright holder doesn't have the money required to "lawyer up" and take it to court.

    2. Re:Licensing? by Anonymous Coward · · Score: 0

      Can someone explain to me how this isn't a violation of the copyleft GPL Koha is distributed under?

      this is a trademark issue. PTFS/Liblime are attempting a trademark claim for the word 'KOHA' in New Zealand

      this is *not* a copyright issue, the GPL does not apply here, (afaik, ianal)

    3. Re:Licensing? by Shompol · · Score: 1
      From TFA comments:

      ... It could be argued that trying to seize a trademark in connection with a work is tantamount to claiming ownership of that work, which is copyright infringement.

    4. Re:Licensing? by Anonymous Coward · · Score: 0

      It's the Affero loop hole. They provide Koha as SaaS, hence their modifications don't leave there servers and no open sourcing is required. Should have used AGPL...

    5. Re:Licensing? by Anonymous Coward · · Score: 0

      That makes absolutely no sense.

      Just because someone writes something on the internet doesn't make it true.

    6. Re:Licensing? by Anonymous Coward · · Score: 0

      While GPL certainly would allow for this situation, LibLime still distributes their code as OSS: https://github.com/liblime/LibLime-Koha

    7. Re:Licensing? by Jonner · · Score: 1

      The dispute has nothing to do with copyright (and therefore Copyleft) AFAICT. I don't see any claim that LibLime is distributing proprietary derivatives of Koha. This is only a trademark dispute. If LibLime is trying to gain trademark protection for a term they adopted from the already existing project, that is an attempt to mislead at best and commit fraud at worst, but it has nothing to do with the GPL.

  13. The following parts don't make sense... by Anonymous Coward · · Score: 1

    1. rural library responsible for the first open source library catalogue
    2. defence contractor PTFS
    3. More than a decade after rolling out Koha
    4. in a battle to keep a generic Mori term within the public domain

    Is Koha a generic Mori (Maori) term? What is a library catalog? Like a public library catalog of the books in the library? Who is PTFS?

    As far as the TM goes, If I make up a word called Azkio but it turns out to be a generic term in a language that less than .0002% of the people in the world would recognize does that mean a TM is invalidated?

    1. Re:The following parts don't make sense... by Anonymous Coward · · Score: 0

      >>a generic term in a language
      Link "Windows" ?

    2. Re:The following parts don't make sense... by Anonymous Coward · · Score: 0

      Maori is taught to every student in every school in New Zealand
      Koha means gift
      The trademark application in in New Zealand.
      Its like trying to trademark "Gift"

      Trademarking "Gift" isn't a problem as far as I'm aware though. I would object to it however, if it was the trademark for a product that isn't owned by the trademark owner.

      That, and the product seems to be in violation of gpl. Not a trade mark issue but would be fun to see them sued for copyright infringement. I'm sure the library could do with a few million in damages. They could buy a lot of books

    3. Re:The following parts don't make sense... by NZKiwi · · Score: 2

      Is Koha a generic Mori (Maori) term? What is a library catalog? Like a public library catalog of the books in the library? Who is PTFS?

      As far as the TM goes, If I make up a word called Azkio but it turns out to be a generic term in a language that less than .0002% of the people in the world would recognize does that mean a TM is invalidated?

      Koha is the Maori word for "gift" - It's about as generic as the english word "gift". An example in the New Zealand context would be Te Papa Tongarewa (translates as "container of treasures" - the National Museum of New Zealand) having a box by the door labelled "Koha" in the hope you'll put some money in it to help support the museum and to show your appreciation for the place.

      If you ask almost any New Zealander what Koha is (that's approximately 4 million people) they'd nearly all say it means gift or donation.

    4. Re:The following parts don't make sense... by Anonymous Coward · · Score: 0

      - Is Koha a generic Mori (Maori) term?
      yep, but PTFS/Liblime are attempting to claim trademark in NZ **specifically** in the classification of
      '9/9 computer software, namely, an integrated library system for use in searching a collection of records, circulating materials, purchase of new materials and creation of metadata records for materials held'

        - What is a library catalog?
      its another name for an 'Integrated library system' (ILS)
      'http://en.wikipedia.org/wiki/Integrated_library_system'

        - Who is PTFS?
      a recent player Koha community, and the recent purchaser of a company called Liblime, thats all
      http://en.wikipedia.org/wiki/Liblime

      the Koha wiki page has the backstory
      http://en.wikipedia.org/wiki/Koha_(software)

    5. Re:The following parts don't make sense... by kiwi_james · · Score: 2

      a language that less than .0002% of the people in the world would recognize does that mean a TM is invalidated?

      By my rough calculation our 4 million people gives us 0.057% of the world's population recognising the phrase :-)

      The basic fact is that this is an extremely arrogant move. A company is taking a "common word", which ironically means gift, and using it for commercial gain for open source software that was created in the very country they're applying their trademark in.

      The Maori meaning of "koha" is more complex than Gift - and if you start to understand the moral obligation that underpins true "koha" - you really feel that these guys are a bunch of knob-ends.

      That said, our intellectual property office recently let a large brewery trademark the term "Radler" - http://www.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=10738427 - so unfortunately they might be needing their legal fund to try and get Koha back out of corporate hands.

    6. Re:The following parts don't make sense... by Kalriath · · Score: 1

      If I make up a word called Azkio but it turns out to be a generic term in a language that less than .0002% of the people in the world would recognize does that mean a TM is invalidated?

      In the country whose native language it's a generic term in, I would imagine so, yes.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  14. and, some comments from PTFS/Liblime... by Anonymous Coward · · Score: 1

    here's a very interesting recent discussion about this - with comments from PTFS/Liblime

    http://diligentroom.wordpress.com/2011/11/22/the-exemplar-of-stupid-koha-vs-liblime-trademark/

  15. "Microsoft Jailbreaks OSS Bitcoin MAFFIA " by westlake · · Score: 1

    but this summary just does it - it makes so much "no sense" that i have no fucking idea what is it about

    Like Google News, Slashdot doesn't have an editor. You wand your submission accepted, all you need to do is hit ther geek's hot buttons in your headline.

  16. Evildoers abound? by Gravis+Zero · · Score: 1

    sounds like a job for Anonymous. ;)

    --
    Anons need not reply. Questions end with a question mark.
  17. It is possible to trademark generic terms by bdwoolman · · Score: 2

    IANAL But the Tabasco story is a famous and an interesting trademark case .

    Since Tabasco is a state in Mexico and a name for a pepper, McIllhenny understandably had a hard time cementing its claim. Right or wrong, McIllhenny vigorously defends this hard-won mark to this day.

    --
    "No fear. No envy. No meanness." Liam Clancy
    1. Re:It is possible to trademark generic terms by Anonymous Coward · · Score: 0

      So just because Daddy-Pepperbucks steamrolled a trademark for Tabasco a century ago, it makes it RIGHT for another USA-ian outfit to hijack "Koha"?

  18. This is why the world hates America by Anonymous Coward · · Score: 0

    For all the great things about this country, they are completely overshadowed by things that are just plain and simply evil.

  19. Hate to say it but... by Anonymous Coward · · Score: 0

    The group would be better of using the money to advertise whatever new name they choose. Sure they could fight the court battle win or lose the lawyers get the money. They might win with a little publicity. They might lose with a little publicity. Or they could use the money they get to take out ads in multiple papers and magazines and establish their new name as a powerful brand.

  20. I find something is wrong with this approach by initialE · · Score: 1

    Instead of spending their own resources to dispute the trademark, they ought to consider if the trademark covers their own domain of application - similarly to how Apple Inc and Apple corps are both trademarks built on a single English word, but technically don't cover the same area - one is a trademark on an IT brand, the other is a trademark on a music store, and one should not be able to confuse one for the other (although they have fought over the name, needlessly really). Is LibLime asking them to C&D the use of the name? Can they coexist without confusing their client base over each other's existence? Are they fretting over the problem unnecessarily?

    --
    Starbucks, Harbuckle of Breath.
    1. Re:I find something is wrong with this approach by ColaMan · · Score: 2

      I am unable to adequately express my dismay regarding your sheer ignorance of the situation at hand.

      So, if you could just punch yourself in the face, just as hard as you can, that'd be great. Well, it wouldn't be great for *you*, but I'd feel a whole lot better knowing it had been done.

      Thanks.

      --

      You are in a twisty maze of processor lines, all alike.
      There is a lot of hype here.
    2. Re:I find something is wrong with this approach by andydread · · Score: 1

      The trademark was originated by the project that invented the software at the poor library in NZ. Because the software can be distributed for free anyone can download it and re-distribute the software. So what Liblime did was downloaded the software and because the poor owner of the software failed to register the trademark worldwide Liblime registered the trademarks. And they are now marketing the trademark as theirs totally hijacking the real project's trademark.

    3. Re:I find something is wrong with this approach by gl4ss · · Score: 1

      they're the same product. they can't co-exist.

      it's like ubuntu going and trademarking "debian" to fight loosing downloads to debian-mint.

      --
      world was created 5 seconds before this post as it is.
    4. Re:I find something is wrong with this approach by Jonner · · Score: 1

      I'm pretty sure LibLime's application for trademark was the first (and probably only) one. It seems that the originators of the project didn't apply for a trademark because they didn't think the generic word "Koha" could be trademarked. Horowhenua Library Trust is not saying they should hold the "real" trademark but that the trademark shouldn't exist at all.

    5. Re:I find something is wrong with this approach by Jonner · · Score: 1

      "Debian" was trademarked in 1999, long before Canonical came along anyway. While Canonical and Mint must use the term "Debian" in compliance with the Debian licensing policy, Canonical gets to determine Ubuntu trademark policy. Whether "Koha" can be trademarked seems a similar question to whether "Ubuntu" can, since it's also a generic word in several languages.

    6. Re:I find something is wrong with this approach by steveg · · Score: 1

      How do you loose a download?

      If it's extraordinarily tight, perhaps you mean loosen?

      --
      Ignorance killed the cat. Curiosity was framed.
  21. get used to it by jjbarrows · · Score: 1

    I'm from Tasmania, where our most recognisably tasmanian icon the Tasmanian Devil(TM) (since we killed the Tigers) is trademarked by a US company
    http://en.wikipedia.org/wiki/Tasmanian_Devil_(Looney_Tunes)

    1. Re:get used to it by Anonymous Coward · · Score: 0

      There are some hundred Swedish products, some of them patented, that have been stolen by US companies, usually both the name and invention, usually by some previous US reseller of the product.

      US IP-protection only applies to US based companies. It seem to be constructed to help US based companies to steal inventions as well as trade marks.

  22. Do something by Anonymous Coward · · Score: 0

    I chipped in $50, I feel better. Try it!

  23. Certainly not right in my opinion by bdwoolman · · Score: 2

    Just legally possible, although not morally defensible. The law, we all know well, does not always equate to justice. And that is especially true of IP law, of course.

    By referencing this case I was pointing out that the NZ library has every reason to be worried. Since this rather creepy little company going after the Maori trademark has plenty of creepy company. I had no intention of defending them.

    Personally I am outraged by Daddy Pepperbucks century of non-stop litigious bullying. They even went after a punk rocker who used a "Tabasco" moniker. Was it Annie Tabasco..? or Suzy Tabasco...? or... Someone help me here. The early 80s are a bit.... fuzzy.

    --
    "No fear. No envy. No meanness." Liam Clancy
    1. Re:Certainly not right in my opinion by Jonner · · Score: 1

      I certainly agree that the TABASCO trademark should never have been granted and the company has defended it with reprehensible tactics. I've often enjoyed their products since I was young, though ironically I prefer their jalapeño sauces to the original. I will now more likely buy competitors' products.

  24. The sad truth. by madhi19 · · Score: 1

    Let face it if you start any kind of business, blog or public project you now need to get it trademarked from day one to prevent the vultures from circling you a decade later in the unlikely event that you are even a little successful. $275 per class for a TEAS Plus application that meets the requirements of 37 C.F.R. 2.22 and 2.23 $325 per class for an application filed electronically using the Trademark Electronic Application System (TEAS) $375 per class for an application filed on paper That only for filling trademark I did not mention alternate domain suffix like .org .ca .fr .xxx and patent... It not higher tax that killing the economy it all the damn parasite lawyers.

    1. Re:The sad truth. by unitron · · Score: 1

      Are you sure it's not the "businesses" that hire those lawyers who are really to blame?

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

  25. Maybe in the US its ok by vik · · Score: 2

    but this kind of behaviour is not OK in New Zealand. What if someone from NZ snuck over and trademarked "Honour" (or "Honor" on your side of the pond)?

    Frankly, I'm fed up with corporations behaving like this then bleating that they are only doing it to secure their profits which justifies anything as you know. Time they got taken down a peg or two.

  26. Let's hope ... by Anonymous Coward · · Score: 0

    Let's hope that the Liblime company jumps all over http://koha.com/, the Kalamazoo Optimist Hockey Association as well.
    I mean, they're infringing the trademark/copyright whatever it is too, aren't they?

    If they don't, then they fck themselves for not pursuing protection of "their" assets, no ?

  27. American Corp. by Anonymous Coward · · Score: 0

    They are all shit none of them can compete fairly.
    They all make and sell everything as cheap as they can.
    Source something on the cheap then sell it to you the same price as if it were from America.

    Look at my company we can only do business if I do a full on ringing endorsement of communism or American prison labor.
    This is not capitalism it is legal theft of the consumer and exploitation of labor.
    Greed.

  28. How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 1

    This summary and the ensuing discussion are so full of dumb and FUD, it's hard to know where to start. I'll list a few bullets:

    1) If managing one of the Navy's library catalogs makes PTFS/LibLime a "defense contractor," that's a serious diffusion of the term.
    2) PTFS/LibLime has held the same trademark continuously in the US for several years without any attempts to limit its use. The same applies to this trademark.
    3) PTFS/LibLime's project is also OSS: https://github.com/liblime/LibLime-Koha
    4) The LibLime component of PTFS is composed of fewer than a dozen people. PTFS as a whole is under 50... smaller than a lot of libraries.

    The real issue here is that there is an unresolved project fork with an ugly, circuitous history. A conflict erupted over project direction and management, the "ownership" of the project was diffuse, and now both sides claim that they have rights to the name. Ironically, HLT is the side that claims that LibLime does not have rights to use the name. However, LibLime does not contend the converse, recognizing that plain fact that the name ownership is not clearly resolvable.

    Everyone loves little neighborhood libraries, and everyone hates "big, evil defense contractors," so you can see who receives the benefit of the narrative frame. HLT is doing their best to work this framing, facts be damned. Meanwhile, they can't even take the issue seriously enough to stop their own trademark application from being abandoned from inattention.

    1. Re:How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 0
      So, ptfs/liblime are finally on the defensive and working on damage control. This spin on the events seems to be something only a loyal ptfs/liblime employee could come up with.

      This summary and the ensuing discussion are so full of dumb and FUD, it's hard to know where to start. I'll list a few bullets:

      1) If managing one of the Navy's library catalogs makes PTFS/LibLime a "defense contractor," that's a serious diffusion of the term.

      From the PTFS website: "PTFS’s Professional Support Services department specializes in staffing for Intelligence Agencies. "

      2) PTFS/LibLime has held the same trademark continuously in the US for several years without any attempts to limit its use. The same applies to this trademark.

      Considering the behavior of ptfs/liblime up to now, why would any reasonable person trust ptfs/liblime as a steward of the koha trademark?

      3) PTFS/LibLime's project is also OSS: https://github.com/liblime/LibLime-Koha

      Thank you for not referring to the ptfs/liblime fork as "koha".
      By saying that "...PTFS/LibLime's project is also OSS," you seem to be acknowledging that it is separate from koha, so why not call it by a different name?

      4) The LibLime component of PTFS is composed of fewer than a dozen people. PTFS as a whole is under 50... smaller than a lot of libraries.

      Is the small size of ptfs/liblime supposed to excuse its abhorrent behavior and lack of moral compass?

      The real issue here is that there is an unresolved project fork with an ugly, circuitous history. A conflict erupted over project direction and management, the "ownership" of the project was diffuse, and now both sides claim that they have rights to the name. Ironically, HLT is the side that claims that LibLime does not have rights to use the name.

      False. HLT is the side that claims that LibLime should not be permitted to trademark the name "koha".

      However, LibLime does not contend the converse, recognizing that plain fact that the name ownership is not clearly resolvable.

      Everyone loves little neighborhood libraries, and everyone hates "big, evil defense contractors," so you can see who receives the benefit of the narrative frame. HLT is doing their best to work this framing, facts be damned. Meanwhile, they can't even take the issue seriously enough to stop their own trademark application from being abandoned from inattention.

      So, are you saying that HLT is to blame for not taking "...the issue seriously enough to stop their own trademark..." from being acquired by ptfs/liblime? In other words, ptfs/liblime is not responsible for what it is doing, but HLT is to blame for allowing ptfs/liblime to to do it?? Wow, you folks at ptfs/liblime really have no moral compass at all.

    2. Re:How about some actual facts from a LibLimer? by Obelos · · Score: 1

      Considering the behavior of ptfs/liblime up to now, why would any reasonable person trust ptfs/liblime as a steward of the koha trademark?

      Yes, your divisive and herd-ish community is a real trust broker.

      Thank you for not referring to the ptfs/liblime fork as "koha". By saying that "...PTFS/LibLime's project is also OSS," you seem to be acknowledging that it is separate from koha, so why not call it by a different name?

      Why not call HLT's project a different name?

      Is the small size of ptfs/liblime supposed to excuse its abhorrent behavior and lack of moral compass?

      One of HLT's tactics is to spin us as some mega-corp bully.

      False. HLT is the side that claims that LibLime should not be permitted to trademark the name "koha".

      Please spend 30 seconds on the HLT mailing lists or IRC after mentioning LibLime's name. All of the following commentary will predictably be along the lines of "that's not *real* Koha" or "they have no right to use that name." Please cite one, just one, instance where PTFS/LibLime has said that about HLT. Just one.

      So, are you saying that HLT is to blame for not taking "...the issue seriously enough to stop their own trademark..." from being acquired by ptfs/liblime? In other words, ptfs/liblime is not responsible for what it is doing, but HLT is to blame for allowing ptfs/liblime to to do it?? Wow, you folks at ptfs/liblime really have no moral compass at all.

      No, I'm saying that in addition to their hostility and divisiveness (which is what has prevented PTFS from simply canceling the app when we found out about its existence), HLT is also incompetent. They let their own application fall to rot. If they had not done so, they could have (probably successfully) contested PTFS' claim. But this way it sure is useful for garnering attention and donations.

    3. Re:How about some actual facts from a LibLimer? by Kalriath · · Score: 1

      Thank you for not referring to the ptfs/liblime fork as "koha".
      By saying that "...PTFS/LibLime's project is also OSS," you seem to be acknowledging that it is separate from koha, so why not call it by a different name?

      Why not call HLT's project a different name?

      Um, because they were the ones that created the project? Duh.

      Is the small size of ptfs/liblime supposed to excuse its abhorrent behavior and lack of moral compass?

      One of HLT's tactics is to spin us as some mega-corp bully.

      Which your posts here are doing a damn fine job of reinforcing.

      So, are you saying that HLT is to blame for not taking "...the issue seriously enough to stop their own trademark..." from being acquired by ptfs/liblime? In other words, ptfs/liblime is not responsible for what it is doing, but HLT is to blame for allowing ptfs/liblime to to do it?? Wow, you folks at ptfs/liblime really have no moral compass at all.

      No, I'm saying that in addition to their hostility and divisiveness (which is what has prevented PTFS from simply canceling the app when we found out about its existence), HLT is also incompetent. They let their own application fall to rot. If they had not done so, they could have (probably successfully) contested PTFS' claim. But this way it sure is useful for garnering attention and donations.

      Which still doesn't explain why FTFS feels it has to trademark the name at all. The only reason you need one is if you actually feel you have to protect the brand from dilution (i.e. Ubuntu, Red Hat, Debian, Firefox) - many OSS projects get along just fine without one.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    4. Re:How about some actual facts from a LibLimer? by Obelos · · Score: 1

      You obviously know dangerously little about the history of this project, the principals involved, and business in general. That's more than I'm willing to correct.

    5. Re:How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 0

      I love the repeated use of the 'divisive' criticism. People's Republic of China much.
      Also, if everybody on the forum says you have no right to trademark the name (I doubt they say you have no right to use it, just to own it), it is not actually a defense of your position.
      Um, trying to trademark the name in NZ is a very, very, very strong way of saying HLT has no _right_ to use the name. You may let them, but they have no right.

    6. Re:How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 0

      Wow... an open source community that is 'divisive'?

      Take a step back. Is LibLime part of the community? Sure looks like it to me. Either that or you're a megacorp bully trying to play foul 'cos your victims noticed that you were trying to fleece them. Which is it?

      Try this resolution: send HLT an MOU or (gasp!) contract that guarantees that the OSS community will still have free access. Alternatively, stop assuming that people should conform to your business methodology... Academics have their own and they resent your shuttered belief that yours is the only way to do things. They hear it a lot when it's clearly not true.

    7. Re:How about some actual facts from a LibLimer? by Obelos · · Score: 1

      Actually, we want the reverse that; we want to transfer the TM to a non-profit trust (potentially HLT) that will grant us license to continue to use the name in perpetuity. The official press release is at http://www.liblime.com/ptfsliblime-granted-provisional-use-of-koha-trademark-in-new-zealand.

    8. Re:How about some actual facts from a LibLimer? by Kalriath · · Score: 1

      And you obviously work for LibLime, so noone cares what you have to say anyway.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    9. Re:How about some actual facts from a LibLimer? by unitron · · Score: 1

      Is it possible that you had a noble and worthy goal and went about achieving it in, shall we say, a less than optimal manner?

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

    10. Re:How about some actual facts from a LibLimer? by Obelos · · Score: 1

      Our goal was self-preservation, to ensure our ability to retain use of the name in the face of the HLT community's aggressive efforts to exclude us and establish itself as "the real Koha". I don't think that goal readily qualifies one way or the other on the "noble and worthy" scale, but it should not surprise anyone that we would pursue actions to keep using a name that we have rights to.

    11. Re:How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 0

      Seems like a spectacularly incompetent effort to do so, by taking on a library, when your customers are libraries.

      Even if you do succeed with your trademark grab, how will that in anyway stop people staying you forked Koha and do your own development? The only thing you can do with it is to try to stop others using the name Koha. Becoming the thing you are pretending you are fighting against.

      Surely the better course is to actually participate, you know like everyone else seems to manage to do.

    12. Re:How about some actual facts from a LibLimer? by Obelos · · Score: 1

      I see the average reading comprehension level on /. has decreased significantly since I last read it a decade ago.

    13. Re:How about some actual facts from a LibLimer? by Anonymous Coward · · Score: 0

      Self-preservation? Oh, please.

      A lot of companies try to preserve themselves by making sure their customers are happy. That's a much sounder business plan.

      I know that within the consortium that signed up with LibLime under its notorious former owner, there is tremendous discontent about the quality and reliability of the program and the ridiculously high cost of the development project. The software development project within PTFS/Liblime is, what, 3 years behind schedule now?

      The Liblime version of Koha is not open source, and it's also not anywhere close to the quality of the other proprietary systems available. And the support is nothing to write home about, either. Bugs remain unfixed for months and years.

      You don't currently contribute much code to the real, free version of Koha. You didn't start the project initially. You really have no right to own the trademark in New Zealand, and by trying to grab it, you manage to look both ruthless and foolish.

      If you want to work on "self-preservation" why don't you hire some more staff to fix the many serious bugs and deficiencies in the software you're providing to your customers. Leave the trademark for Koha in New Zealand alone - it just makes you look like greedy opportunists.