Slashdot Mirror


GPL Wins In French Court Case

viralMeme writes "An appeals court in Paris has upheld the ruling from a lower court, which found that the French firm Edu4 had violated the GNU General Public License (GPL). The plaintiff was the French Organisation Association francaise pour la Formation Professionnelle des Adultes (AFPA), an umbrella organization for adult education." The basic charge was the removal of copyrights and such from VNC source code, and not distributing it.

266 comments

  1. Why? by Daryen · · Score: 0, Troll

    It sucks to see the GPL being used to shut down an organization that dedicates itself to something noble like adult education. Then again, what did they have to gain by NOT publishing their changes and removing the copyright info?

    1. Re:Why? by Noryungi · · Score: 4, Informative

      Read the article: AFPA - the education agency - sued edu4 - a company working for this agency - because edu4 did not release the source code to its modified VNC software.

      The court essentially said that AFPA was correct, that the GPL should have been upheld by edu4, and that the source code should be released by edu4 to its client, the AFPA.

      Essentially, this is good news: as far as France is concerned, the GPL has been challenged, and upheld in court. Modifications done by a private company to a GPL software should therefore be available for all.

      --
      The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    2. Re:Why? by Anonymous Coward · · Score: 0

      AFPA was the plaintiff, not the defendant.

    3. Re:Why? by flyingfsck · · Score: 2, Informative

      "should therefore be available for all"

      No, not to all, only to their clients. What their clients do with it in turn is up to them.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    4. Re:Why? by MoralHazard · · Score: 1

      ...and those who can't be bothered to RTFA, while rushing madly to post first, are doomed to look like morons (or trolls, at best).

    5. Re:Why? by Chris+Burke · · Score: 1, Informative

      No, not to all, only to their clients.

      Not according to the GPL. If you distribute GPL software to anyone, then you must extend the offer of source code to all third parties.

      --

      The enemies of Democracy are
    6. Re:Why? by noundi · · Score: 4, Funny

      It sucks to see the GPL being used to shut down an organization that dedicates itself to something noble like adult education. Then again, what did they have to gain by NOT publishing their changes and removing the copyright info?

      You're the kind of guy who sees a good and innocent side of genocide, aren't you?

      --
      I am the lawn!
    7. Re:Why? by someone1234 · · Score: 1

      Were you just as eager when M$ sued russian schools about their pirated Windows versions?
      In THAT case, the one sued was a real education institution.
      In THIS case, the one sued is a for profit company.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    8. Re:Why? by noundi · · Score: 1, Insightful

      No, not to all, only to their clients.

      Not according to the GPL. If you distribute GPL software to anyone, then you must extend the offer of source code to all third parties.

      Wrong. Look people it's fucking simple, if you distribute GPL, you bring along the source. You have no obligation to distribute it to anybody else than those you distributed the software to. Meaning if A buys software from B, B must give source to A, C has no way of demanding the source from either. How is this difficult?

      --
      I am the lawn!
    9. Re:Why? by Nadaka · · Score: 1

      how exactly are they shutting the organizaton down? The GPL was violated, and the AFPA refused reconciliation. BTW, even Microsoft didn't let its GPL violation go to court, it instead released the violating code after some negotiation.

    10. Re:Why? by Gudeldar · · Score: 3, Insightful

      Presumably they are only going to distribute the binaries (and therefore the source) to their clients. There is nothing stopping the clients from then giving the source code away for free but unless one of them does then the only way to get it is to buy their product.

    11. Re:Why? by Saint+Ego · · Score: 3, Informative

      Propagation of this misinformation, specifically, is the reason the GPL is so misunderstood: too many people out there that think GPL is the same thing as public domain and derive a sense of entitlement from it.

      General Public License != Public Domain

      --
      Reality is prettier inside my head...
    12. Re:Why? by morgan_greywolf · · Score: 5, Informative

      You're both almost right.

      3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

              a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
              b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
      (rest of section 3 omitted since it's irrelevant here)

      Empahsis mine.

      Basically, edu4 could have either distribute the source with the binaries or accompany the binaries with a written offer to distribute the source to any third parties. (I suppose they technically could have done both and still be in compliance, but that seems rather redundant)

    13. Re:Why? by Nadaka · · Score: 1

      note: some of my assertions are incorrect, based on the summary and posted before I read the article. oops.

    14. Re:Why? by nedlohs · · Score: 2, Informative

      It's difficult because it depends how you "give source".

      If you go for the written offer to provide source rather than just providing the source upfront then you do in fact have an obligation to provide the source to all third parties.

    15. Re:Why? by BrokenHalo · · Score: 1

      Well, it seems the judge was equally ambivalent, given the derisory payment demanded from the offender of 8,000 (which for those who count in US dollars amounts to about $11,616) plus court costs. I'd say that was pretty much a slap on the wrist.

    16. Re:Why? by Anonymous Coward · · Score: 1, Insightful

      No it doesn't. The GPL says if you provide a binary to someone you must offer them a way to get the source code, and if they redistribute the binary to someone else you must also honor your offer of source code to that third party (ad infinitum). If someone doesn't have your binary, they don't have any claim to your code.

    17. Re:Why? by dlapine · · Score: 3, Informative

      mod parent up. The original post on this thread was just plain FUD.

      You must:
      1) give the modified GPL source code as well as the binaries to the person who is your client.
      You have the option to
      2) give the modified GPL source code to your client, and everybody else if you choose to.
      The second option is not mandatory.

      --
      The Internet has no garbage collection
    18. Re:Why? by Chris+Burke · · Score: 1

      Nothing I said would apply to software in the public domain.

      --

      The enemies of Democracy are
    19. Re:Why? by Chris+Burke · · Score: 1

      Ah yes, thanks, I forgot about the "one of" clause.

      I really don't see how that makes my post 'FUD' as all these others are claiming, especially since a link to a website containing the source -- even if it isn't your website, it just contains your modifications -- is sufficient.

      --

      The enemies of Democracy are
    20. Re:Why? by AlecC · · Score: 2, Insightful

      Not sure I understand you. The Adult Education organisation was the plaintiff, the winner, in this case, complaining that the IT company they hired to set something up for them, used and modified GPL code (VNC) but did not, as required by the GPL, give them the modified sources. Presumably, the IT company was wanting to keep the AE organisation beholden to them for maintenance rather than, as the GPL hopes, being able to do it themselves or find someone else to do it if the wanted to. I.e. the GPL wanted to help the organisation you support, and the courts have just backed it up.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    21. Re:Why? by SanguineV · · Score: 1

      You're the kind of guy who sees a good and innocent side of genocide, aren't you?

      Seems like a good start to solving our human overpopulation problems!

    22. Re:Why? by Lord+Bitman · · Score: 1

      Except that most people don't distribute source code along with the binary distribution. It's not "give the modified source code as well as the binaries", it's "give the modified sourcecode along with the binaries".
      Now it's arguable that "A URL to a page with a tar.bz2" is a medium customary to software interchange, but it is also arguable that a URL is simply "a written offer to provide" sourcecode (which fits b, not a).

      There is no option to provide a written offer which is valid only to those who have received binaries from you, so it's "give at the same time" or "give to everyone".

      --
      -- 'The' Lord and Master Bitman On High, Master Of All
    23. Re:Why? by digitig · · Score: 2, Informative

      AFPA were permitted to unilaterally terminate the contract (which is what the appeal was about) and so not pay EDU4 for the work. That looks like over a million euro -- hardly just "a slap on the wrist".

      --
      Quidnam Latine loqui modo coepi?
    24. Re:Why? by Anonymous Coward · · Score: 0

      Yeah! We only equate GPL with public domain when we grab someone else's public domain code and slap the GPL on it! This isn't at all like that!

    25. Re:Why? by TheRaven64 · · Score: 1

      People misunderstanding a document that is several pages of dense legalese and is commonly advocated by people who have never read it? I'm absolutely shocked that this could be the case!

      --
      I am TheRaven on Soylent News
    26. Re:Why? by Abreu · · Score: 1

      Yeah! We only equate GPL with public domain when we grab someone else's public domain code and slap the GPL on it! This isn't at all like that!

      We? Who's we?

      Did you steal someone's source and slapped the GPL on it? I know I didn't!

      ...

      (yes, yes, I know IHBT,IHL,HAND)

      --
      No sig for the moment.
    27. Re:Why? by Tanktalus · · Score: 1

      Meanwhile, most of the rest of us would have elected to start with lawyers, politicians, and telephone sanitisers before depopulating along ethnic lines.

    28. Re:Why? by sumdumass · · Score: 1, Insightful

      They are all for profit institutions. The only difference is in who makes the profit- investors verses employees. Just because the state funds one of them shouldn't change the reality of what is happening. I know of teachers making over 100k a year teaching grade school and only working 9 months of the year. They will get another 7% increase within the next year because of a contract they negotiated while on strike.

    29. Re:Why? by stim · · Score: 1

      ROFLMAO! The Adult Education organization was the plaintiff you r-tard.

      --
      Browse at -1 to keep an eye out for abuses.
    30. Re:Why? by Anonymous+Cowpat · · Score: 1

      AFPA were permitted to unilaterally terminate the contract (which is what the appeal was about) and so not pay EDU4 for the work.

      I can't be bothered to RTFA, do they get to keep the hardware too?

      --
      FGD 135
    31. Re:Why? by Anonymous Coward · · Score: 0

      GNU/Mussolini made the trains run on time.

    32. Re:Why? by Anonymous Coward · · Score: 0

      the company later went VERY deep into shit, and surfaced after two years of judicial oversight. Nuking today's company wouldn't be that fair, I guess. The company actually lost 8K+expertise+300K (the value of the market, which earned exactly zero for two years' elapsed -- before the first judicial salvos, 7 YEARS ago).

    33. Re:Why? by wastedlife · · Score: 1

      I think it might depend on GPL 2 vs 3, and I am unsure which one VNC is distributed under. Its my understanding that with GPL v2, you have two choices:

      1)Distribute the modified source code with the binaries (i.e. on the CD or in a folder in the tar), ending your obligations.

      2)Provide a written offer to distribute the modified source upon request. This needs to be on a physical medium such as a CD-ROM, but you can collect payment for shipping and materials. You cannot just post a link to your FTP site, but you can offer that for those that do not wish to wait for a CD to ship.

      With the GPL3, I believe you can just have users download the software from FTP, HTTP, or git or whatever. I'm not sure how long you need to maintain this though. Also, remember that the GPL2 was written in 1991, when downloading source code over the net was far less of an option for most.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    34. Re:Why? by wastedlife · · Score: 1

      If you are talking about the case I am thinking of, wasn't it the Russian government that initiated the investigation and then tried and convicted the teacher, with MS stating they did not wish to sue the individual? Please correct me if I am wrong or thinking of a different case.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    35. Re:Why? by steelfood · · Score: 1

      He's the guy in the back who yells, "Population control!"

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    36. Re:Why? by noundi · · Score: 1

      You're both almost right.

      3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

      a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, (rest of section 3 omitted since it's irrelevant here)

      Empahsis mine.

      Basically, edu4 could have either distribute the source with the binaries or accompany the binaries with a written offer to distribute the source to any third parties. (I suppose they technically could have done both and still be in compliance, but that seems rather redundant)

      Sorry I presumed that people would understand that if you don't want the source the distributer can't force it upon you. I didn't feel the need to clarify this simple logic.

      --
      I am the lawn!
    37. Re:Why? by PeterBrett · · Score: 1

      Propagation of this misinformation, specifically, is the reason the GPL is so misunderstood: too many people out there that think GPL is the same thing as public domain and derive a sense of entitlement from it.

      General Public License != Public Domain

      Um, if Alice was distributing binaries of public domain source code, no-one would have any rights whatsoever to request source code from Alice. The rights of recipients of GPL software are considerably stronger than the rights of recipients of public domain software -- but there are obligations to go with those rights. This is what seems to confuse people: they think they are entitled to the rights without the obligation.

    38. Re:Why? by PeterBrett · · Score: 1

      People misunderstanding a document that is several pages of dense legalese and is commonly advocated by people who have never read it? I'm absolutely shocked that this could be the case!

      I'm absolutely shocked! The <set of people that do X> intersects with the set of irresponsible people! How could this thing be!

      I think you'll find that, despite the inevitable idiots, most people who advocate the GPL have read it and do understand it. The GPL is actually very readable. Have you read the terms and conditions for your credit card recently? Or the fine print of your mortgage? The GPL doesn't have a patch on that pile of dense legalese.

    39. Re:Why? by mcgrew · · Score: 1

      Personally, I hate getting first post because mods are quick to downmod without thinking, no matter how informed or insightful the comment is. If you're a subscriber you get a chance to RTFA before the story is posted, which is a boon becuse you actually get to RTFA before the FA is slashdotted.

      Although lately the first posts I've gotten haven't been abused like that, but I still try to wait for the "frosty piss gnaa" post that inevetably turns up as fp before I hit "submit" with my comment.

      With some stories the article conveys no information that isn't in the summary. If you're familiar with the GPL, this would be one of them. Obviously either the GP has no clue or he's a programmer for some proprietary software company.

    40. Re:Why? by sumdumass · · Score: 1

      That is only if you do not give the source code with the distribution of the binary or distribute the source code as the binary.

      You only have to distribute the source code to those you distribute to unless you choose to distribute the source code at a separate time. If you chose to do it at a separate time, you have more obligations to more people depending on how and where it's distributed.

    41. Re:Why? by sumdumass · · Score: 1

      They went about it wrongly. The GPL (version 3 to be exact) specifically allows for that type of scenario to happen. The problem is that Edu4 didn't secure the software enough to remain within the scope of the GPL's exception. Section 2 of the GPLv3, says that you can have a third party run the program solely for you and you do not need to convey any source code that you own the copyright for. Your have to also control access to the program and so on and make sure it's used at your direction. I believe the original intent is to use cloud services or web hosting and so on but a tool to aid in the setup and maintenance of computer hardware could easily fit in there.

    42. Re:Why? by indep · · Score: 1

      AFPA is a public non profit educational organization, financed by french government, approachable free of charge for people who loose their job.

    43. Re:Why? by Schraegstrichpunkt · · Score: 1

      General Public License != Public Domain

      It does if you're talking about crypto export rules according to the Wassenaar Arrangement, which defines "in the public domain" very differently from how US copyright law does. See this

  2. French, eh? by autocracy · · Score: 4, Funny

    They should turn off Edu4's Internet too.

    --
    SIG: HUP
    1. Re:French, eh? by Noryungi · · Score: 3, Interesting

      Very funny... NOT.

      Just remember that the recent HADOPI 'three strikes and you are out' law can -and will- be challenged in front of the French Constitutional Court, which will probably strike it down as un-constitutional and contrary to human rights.

      Which is a big relief, at least for me (being French and all that).

      --
      The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    2. Re:French, eh? by L4t3r4lu5 · · Score: 1

      No, this went to court. To have the internet connection disconnected, they'd need to point at the CEO, stick their tongue out, and shout "FILE SHARER!" three times.

      Ok, I just tried that, and it came out as "THAATH THAAYAAAH!" so maybe the tongue idea was a bit off.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    3. Re:French, eh? by Anonymous Coward · · Score: 0

      Say what ? The only unconstitutional part of HADOPI was "fixed" (disconnection orders have to come from judges, not an administrative body). As far as French law is concerned, I don't see a human rights violation. That one is there to stay...

    4. Re:French, eh? by Abreu · · Score: 1

      To have the internet connection disconnected, they'd need to point at the CEO, stick their tongue out, and shout "FILE SHARER!" three times.

      Betelgeuse! Betelgeuse! Betelgeuse!

      --
      No sig for the moment.
    5. Re:French, eh? by Anonymous Coward · · Score: 0

      How is Internet a human right?

      Next people will argue that driving is a human right too. Absolutely ridicules.

    6. Re:French, eh? by Balinares · · Score: 3, Interesting

      I would very much not count on this. The rewritten law is designed to route around the Conseil Constitutionnel's earlier objections.

      Now the convictions will have to be signed off by a judge using the ordonnance pénale procedure, which is, if I got it correctly, the procedure used to deliver, for instance, driving-related fines. The gist of it: a cop has no right to sentence you to anything, only a judge can, but it's assumed that if a cop directly witnessed you speeding then you're as good as guilty and a simplified, faster procedure is thus used; that's the ordonnance pénale. You can challenge the ruling, in which case it goes to a regular court.

      So is this procedure appropriate to the case of copyright infringement? Hell no. To start with infringement can be witnessed as coming from a given IP address, not an identified person, making those cases immensely less clear cut than common driving-related offenses. But does that make it unconstitutional? Nope, I don't think. My bet is that the law will likely stand as such.

      The law tries to brain-damagedly route around the lack of direct IP to person mapping by making the owner of the Internet account legally responsible for everything that happens on it. I'm not sure of the constitutionality of that, but I'm afraid it may stand too, ill-thought patch job that it is. Meaning the death of open access points.

      So I wouldn't be optimistic.

      All this because the French president's trophy wife is a singer. The mind boggles.

      --

      -- B.
      This sig does in fact not have the property it claims not to have.
    7. Re:French, eh? by Eunuchswear · · Score: 1

      As far as French law is concerned, I don't see a human rights violation. That one is there to stay...

      Did they fix the discriminatory bits (not applying to ministers, the music industry and so on)?

      --
      Watch this Heartland Institute video
    8. Re:French, eh? by Carewolf · · Score: 1

      - Free speech
      - Right to assemble

    9. Re:French, eh? by vegiVamp · · Score: 1

      > Which is a big relief, at least for me (being an evil godless file sharer and all that).

      You made a typo there, I believe :-)

      --
      What a depressingly stupid machine.
    10. Re:French, eh? by Anonymous Coward · · Score: 0

      Which is a big relief, at least for me (being French and all that).

      My condolences...

    11. Re:French, eh? by Toonol · · Score: 1

      There's no right to a microphone, a publisher, or a radio show, though. You have the right to exercise your free speech on the internet; you don't have the right to make somebody give you an internet connection.

    12. Re:French, eh? by rohan972 · · Score: 2, Interesting

      The gist of it: a cop has no right to sentence you to anything, only a judge can, but it's assumed that if a cop directly witnessed you speeding then you're as good as guilty and a simplified, faster procedure is thus used; that's the ordonnance pénale. You can challenge the ruling, in which case it goes to a regular court.

      So is this procedure appropriate to the case of copyright infringement? Hell no. To start with infringement can be witnessed as coming from a given IP address, not an identified person, making those cases immensely less clear cut than common driving-related offenses.

      Not sure how it works in France, but you can get a ticket for speeding sent to you because of the car number plate, which identifies the car not you. If it wasn't you the options are to identify who was driving your car, requiring a statutory declaration from them, or challenge it in court. Sounds like this law will work much the same way.

    13. Re:French, eh? by buchner.johannes · · Score: 1

      Next president's wife should be a pirate

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    14. Re:French, eh? by Carewolf · · Score: 1

      Exactly. The same way the government can't forbid you to hold a speech, they can not forbid you from having an internet connection. That doesn't mean anyone will attend your speech or read your blog, but the you have the right.

    15. Re:French, eh? by zzyzyx · · Score: 1

      This kind of expedited trials are already borderline unconstitutional, but deemed acceptable because the consequences are only minimal (a fine). With the "HADOPI" law, you touch the liberty of speech, communication, and lots of things the European Union starts to recognize as fundamental rights. This can have a lots of consequences if your business relies on Internet for example. An expedited trial should not be considered acceptable in this case.

    16. Re:French, eh? by chowdahhead · · Score: 1

      Very funny... NOT.

      1990 just called and wants its phrase back.

    17. Re:French, eh? by Hurricane78 · · Score: 1

      No. Because of Vivendi.

      And hey, then I will use that rule too, and make the company who owns a street legally responsible for the crimes that happen on it. And the owner of a house for the things happening in it. Etc.
      That thing cuts both ways. Just that my side has a thousand blades, while theirs hasn't even a had full.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    18. Re:French, eh? by Rysc · · Score: 1

      But even if it is struck down you will still be French.

      Badum-ching! Thanks folks, hold your applause. I'll be here all week. Try the veal.

      --
      I want my Cowboyneal
  3. Use public domain! by Anonymous Coward · · Score: 1, Insightful

    Anyone releasing code to the masses should make it public domain to remove any legal controversies that may arise over it.

    Information wants to be free!

    1. Re:Use public domain! by Seth+Kriticos · · Score: 4, Insightful

      People should be able to release code they wrote with whatever conditions they like. And hey, it's the case (for once something positive).

      There is a reason why GPL is so successful and there is so little Public Domain code. The GPL isn't terribly difficult to understand, as it simply says: sure, take this code for free, improve it, but the price is that you redistribute your changes with the same conditions.

      If you don't like this kind of license, then simply don't use GPL'd code. Use something like BSD licensed code, like Apple did with OS X.

      This is not rocket science.

    2. Re:Use public domain! by Runaway1956 · · Score: 4, Insightful

      I'm not sure THAT's a great idea. Convince me, please. Are you sure that public domain has any force or power to ensure that it is NOT abused? GPL at least has teeth to bite it's abusers.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    3. Re:Use public domain! by beelsebob · · Score: 1

      I agree with your sentiment in every way, but not your example... Had BSD been GPL'd apple would have been able to release the exact same amount of source code (the whole of darwin), and still be compliant. Apple didn't chose that code because it was BSD'd, they chose it because it was a good base for their OS.

    4. Re:Use public domain! by beelsebob · · Score: 1

      Can you give an example of an abuser that gets bitten by the GPL?

    5. Re:Use public domain! by Anonymous Coward · · Score: 2, Insightful

      BSD is how a license should be. I'm not talking about granted rights but how it's written. The BSD is short, concise and everybody can understand it. The GPL is the sort of bloated legalese mumbojumbo that makes you think "Oh, screw this!".

      The GPL is difficult to understand, which is documented by the massive amount of posts, threads and questions on what is and what is not allowed. All these posts always end with "I'm just guessing, get a lawyer". It's definitely not easy to understand if you need a lawyer to explain it to you and help you decide if it MIGHT be ok to do what you want to.

    6. Re:Use public domain! by Runaway1956 · · Score: 1

      Bad analogies don't make any sort of an argument. I said nothing about rape, or corpses, and I don't see how even the worst analogy applies here.

      I asked, quite simply, if public domain is actively defended? Can something be removed from public domain? Whether it can or not, if a corporation USES something that is public domain, do they have any obligations regarding that use?

      With GPL, there are obligations, and there are people actively defending it. I asked to be convinced, not mocked, thank you.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    7. Re:Use public domain! by Anonymous Coward · · Score: 0

      Wow, I knew slashdot doesn't RTFA, but here, you've missed both the summary AND THE TITLE!!! "GPL Wins In French Court Case." Edu4 got bitten by the GPL.

    8. Re:Use public domain! by Nadaka · · Score: 1

      In many cases its actually impossible to release something to public domain. Many nations have "natural rights" laws that prevent an author from releasing all rights to something.

      Public domain also does not ensure that derivative works based on your work remain open and free.

    9. Re:Use public domain! by Runaway1956 · · Score: 1

      Sure. RTFA. Or, are you cross posting from another dimension? Company A distributed binaries to Company B. Company B requested the source, which Company A denied. Company B sued, and was awarded the source, along with all their court costs and other expenses. Company A has been bitten, right in the pocket book.

      IMHO, there should have been a punitive award of some sort, but I'm no lawyer.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    10. Re:Use public domain! by beelsebob · · Score: 0

      Yes, but I'm not seeing any abuse:

      Amount of code available already: all of VLC's source
      Code that wasn't available: The stuff that *they wrote*... There's no abuse involved in choosing to not give away code you yourself wrote*.

      * Unless, the license says specifically that you must, which the GPL does. The point I'm making here is that the GPL is not stopping something that's inherently abusive.

    11. Re:Use public domain! by beelsebob · · Score: 0

      My point is that there's no abuse going on here:

      Amount of code available already: all of VLC's source
      Code that wasn't available: The stuff that *they wrote*... There's no abuse involved in choosing to not give away code you yourself wrote*.

      * Unless, the license says specifically that you must, which the GPL does. The point I'm making here is that the GPL is not stopping something that's inherently abusive.

    12. Re:Use public domain! by Anonymous Coward · · Score: 0

      What constitutes as abusing information in the public domain? Isn't it the whole idea of public domain that anyone can do what the hell they want to with it, be it comercial or non-comercial? It simply becomes something everyone owns.

    13. Re:Use public domain! by BrokenHalo · · Score: 1

      Can you give an example of an abuser that gets bitten by the GPL?

      Of course we can. That French firm Edu4.

      Either RTFA or go back to sleep.

    14. Re:Use public domain! by beelsebob · · Score: 1

      Instead of posting what two other people already said, why don't you read my response to them.

    15. Re:Use public domain! by TheRaven64 · · Score: 1

      Amazing. You manage to post the same comment twice, and still can't tell the difference between VLC and VNC.

      --
      I am TheRaven on Soylent News
    16. Re:Use public domain! by beelsebob · · Score: 1

      damn copy paste error! In the mean time, got a response to the actual point being made?

    17. Re:Use public domain! by Nursie · · Score: 1

      The inherent abuse is in that you wouldn't be allowed to have the VLC source if you didn't agree to the rules.

      It's not as simple as "code you yourself wrote", because it's code you yourself wrote as a derivative of something else.

    18. Re:Use public domain! by Aim+Here · · Score: 1

      Except that supporters of the Free Software philosophy believe that refusing to give source to people who receive your binaries IS an abuse of power.

      But nobody really cares about that. We all know that you're just redefining the word 'abuse' retroactively to cover up the fact that you didn't even read the fucking article summary and got laughably owned by everyone who cared to hit the reply button.

      Since you've STILL apparently not even read the article summary, allow me to point out that it's VNC (as in the desktop sharing system), not VLC, the multimedia client.

    19. Re:Use public domain! by beelsebob · · Score: 1

      Your first paragraph is just circular reasoning "it's inherently an abuse because the GPL forbids it in its rules" and "the GPL forbids it in its rules because it's inherently an abuse". I agree that *if* you happen to grab GPL'd source, you should abide by the rules, but again, I'm trying to point out that what the GPL bans is *not* inherently an abuse.

      Your second paragraph makes slightly more sense, but I don't think you're right at all. The original from which you derived is still available, and still just as free, you're not taking anything away there. Based on that, I can't see how being able to chose how to license your own code is somehow inherently an abuse.

    20. Re:Use public domain! by beelsebob · · Score: 1

      Except that supporters of the Free Software philosophy believe that refusing to give source to people who receive your binaries IS an abuse of power.
      Not at all, I'm a supporter of free software, and because of that I've written a good amount of BSD licensed code. The FSF do like to corrupt the idea of freedom rather though. (note, distinguishing between free software, and the FSF)

      But nobody really cares about that. We all know that you're just redefining the word 'abuse' retroactively to cover up the fact that you didn't even read the fucking article summary and got laughably owned by everyone who cared to hit the reply button.
      Not at all, someone suggested just making things you want to be free public domain, and there was a response that that would open things up to "abuse"... The question is... *what* abuse, and so far, no one seems to have been able to highlight some magical abuse that will happen when you do that.

    21. Re:Use public domain! by ClosedSource · · Score: 1

      "There is a reason why GPL is so successful and there is so little Public Domain code."

      Actually, it's because international copyright laws have effectively eliminated the Public Domain option by creating automatic copyright.

      Nevertheless, there's a ton of code out there that was intended to be in the public domain - no doubt RMS used some as a guide when he was learning how to program.

    22. Re:Use public domain! by Eunuchswear · · Score: 1

      How do you know they were distributing an unmodified version of VNC?

      Oh, because you read the source.

      Good thing you had it available.

      --
      Watch this Heartland Institute video
    23. Re:Use public domain! by Nursie · · Score: 1

      "Your second paragraph makes slightly more sense, but I don't think you're right at all. The original from which you derived is still available, and still just as free, you're not taking anything away there."

      You're taking someone's work without their permission, that's the abuse.

    24. Re:Use public domain! by beelsebob · · Score: 1

      Well no, we're arguing the benefits of GPL over public domain... what abuse does the GPL prevent.

      The abuse is not that you're taking their work without permission, because, well, they public domained it, that's your permission, right there!

    25. Re:Use public domain! by silanea · · Score: 1

      Read the GPL. It does not ban anything. It grants rights. In this case it would have granted Edu4 the right to use other people's code had they complied with it.

      It is copyright that bans what they did. And rightly so. You make it sound as if BSD-style permissions were the default and the GPL added any restrictions to that. Nope. If you grab GPL'd source the only reason you may use and distribute that code is the GPL so abiding by the rules is not a "should" but a "must".

      --
      Rudolf Hess edited Mein Kampf. He was the very first grammar nazi.
    26. Re:Use public domain! by beelsebob · · Score: 1

      Except that this entire thread is comparing the GPL with public domain. Of these two the GPL is the more restrictive.

    27. Re:Use public domain! by wastedlife · · Score: 1

      While I agree with the fact that the BSD license is far easier to read than the GPL (and I don't think there are 2 competing version of BSD license out there to muddy it up further), the two licenses have very different goals. BSD license strives mainly to free code so that anyone can do pretty much whatever they want with it and to release yourself of some liability. GPL aims to enforce an "I'll scratch your back if you scratch mine" policy in that anyone redistributing the code must release their changes under the same license. If someone could make a concise license like the BSD license but that grants this protection, I feel it would cover the best of both worlds. Creative Commons comes close by having an easy to read description of whats allowed with a link to the legalese for further details, but I would prefer it if the legalese didn't need to be there. Not to mention that Creative Commons isn't really designed to be used for code as far as I can tell.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    28. Re:Use public domain! by wastedlife · · Score: 1

      Its inherently abusive because the creator(s) of the original source code released it under that license, and EDU4 must abide by it. Granted if the code was released under a different license, like the BSD license, there would have been no abuse. But, because the creator chose the GPL over the BSD license (or another), it should be assumed that they did so because of these protections. If your arguement was that what if there were no GPL license, then depending on the mindset of the creator(s) of VNC, they may have chose to not release the code under any open source license.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    29. Re:Use public domain! by thejynxed · · Score: 1

      But if it's in the Public Domain, anyone can use it, for whatever purpose they see fit. The only thing they can't do is take it unchanged and re-copyright it under their own name. If it was PD code, they could put it in pink lettering for all I care.

      --
      @Mindless Drivel: 100% of Twitter posts ever Tweeted.
    30. Re:Use public domain! by Sparr0 · · Score: 1

      I find CC-SA to be a good alternative to GPL. I personally dual license most works that I create (code, video, photo, text) as CC-BY-SA and CC-BY-NC.

    31. Re:Use public domain! by david_thornley · · Score: 1

      There are only a few versions of the GPL, and they're similar. The GPL is not particularly long, and at least attempts to be clear. (The GPLv3, in its efforts to be more legally bulletproof, is harder to understand.)

      If you can't sit down and read the GPL and understand it, you can't understand code well enough to program well. Legalese and computer language are both attempts to express concepts exactly, and they're not fundamentally difficult.

      Forget, for a short time, that legal documents are supposed to be hard to read. Read it and understand it.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    32. Re:Use public domain! by rohan972 · · Score: 1

      The GPL is difficult to understand, which is documented by the massive amount of posts, threads and questions on what is and what is not allowed.

      That could indicate something about the GPL or something about the posters. Having read the GPL and some of the posts in question, I suspect the latter.

    33. Re:Use public domain! by rohan972 · · Score: 1

      Well no, we're arguing the benefits of GPL over public domain... what abuse does the GPL prevent.

      The abuse is to sell someone a product and retain control over it, such as with the printer drivers that got RMS steamed up.

      Lots of people, even most people, wouldn't consider that to be abuse but it is nonetheless the abuse being referred to.

    34. Re:Use public domain! by Sir_Lewk · · Score: 1

      In that case you should love the WTFPL.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    35. Re:Use public domain! by Courageous · · Score: 1

      It is illegal to create derivative works of someone else's derivative work without their consent. Such unauthorized derivative works are not the sole property of the derivative work creator...

      C//

    36. Re:Use public domain! by Schmorgluck · · Score: 1

      IMHO, there should have been a punitive award of some sort, but I'm no lawyer.

      For your information, and that of anyone interested, this is simply not permitted by French law. No punitive damages, only compensatory ones.

      To state roughly the philosophy behind it: punishment is a job for criminal courts, not civil courts.

      --
      There's nothing like $HOME
    37. Re:Use public domain! by Runaway1956 · · Score: 1

      It makes sense, actually. Thanks for posting! :-)

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    38. Re:Use public domain! by ultranova · · Score: 1

      People should be able to release code they wrote with whatever conditions they like.

      People should be able to release code or any other ideas under whatever conditions they like, but there's no reason why anyone who gets that code or hears those ideas should be obliged to honour them.

      Copyright isn't about granting rights to the author, it's about removing rights from everyone else.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    39. Re:Use public domain! by Schraegstrichpunkt · · Score: 1

      Copyright isn't about granting rights to the author, it's about removing rights from everyone else.

      In legalese, there's no difference. A "right" is just an enforceable entitlement.

  4. Sacre bleu! by BadAnalogyGuy · · Score: 1, Insightful

    Zis is good step for all of us, mon ami. Ze GPL needs testing so badly. Zus far it has only been tested in ze legal depart'ments of business, and not in ze legal courts.

    Pardon my French, but fuckez yeah!

    1. Re:Sacre bleu! by Anonymous Coward · · Score: 0

      Oh my gawd... Why did I read this and imagine the french axe speaking it from Unforgotten Realms...

    2. Re:Sacre bleu! by Chris+Burke · · Score: 5, Insightful

      Ze GPL needs testing so badly. Zus far it has only been tested in ze legal depart'ments of business, and not in ze legal courts.

      That first sentence is not really true, and not only because the second sentence is also untrue. The GPL may not have been tested extensively, but it has been tried in courts around the globe. But since there really isn't any reason no think that it would be ruled invalid, that testing isn't necessary. There's a reason it's been tested so few times -- all those legal departments, all those lawyers of various degrees of sleaziness, can find no basis on which to challenge it which they think would pass the judicial smell test. Even though they and their clients would have every reason to trump something up. The few that have tried to challenge the validity of the license have failed spectacularly.

      That is, as the French say, "Le hint".

      --

      The enemies of Democracy are
    3. Re:Sacre bleu! by dkleinsc · · Score: 1

      I'm misunderstanding your post. I thought that after the Revolution the French were wealthy enough to have their own language rather than a stupid accent. Of course, my understanding of the French Revolution comes from the documentary History of the World Part 1.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    4. Re:Sacre bleu! by Dragonslicer · · Score: 1

      Zis is good step for all of us, mon ami. Ze GPL needs testing so badly. Zus far it has only been tested in ze legal depart'ments of business, and not in ze legal courts.

      Dude, lay off the Zima. Seriously.

  5. PDF of the decision on the FSF France website by Anonymous Coward · · Score: 0

    The text of the /Arret/ (decision):

    http://fsffrance.org/news/arret-ca-paris-16.09.2009.pdf

    1. Re:PDF of the decision on the FSF France website by Anonymous Coward · · Score: 3, Informative

      (self-reply). I'm no Pamela Jones, but here's a quick summary:

      After seeing the 21SEP04 emergency judgement at Bobigny high claims court

      After seing the 21SEP04 appeal by the defendant

      After seing the 22DEC06 decision whee the court agreed (in essence) for hearing expert opinion ..

      After seeing the expert's memo from 25APR08

      After seeing the last demands from the defendant
      After seeing the last demands from the plaintiff

      THE COURT,

      considering that all the due process (from 2000 onwards) has been followed

      considering that the call for tender (CCAP -- administrative part) was correctly structured

      considering that the Validation of Aptitude phase of the contract was botched (3 times adjourned, presumably because of technical issues), all the way from january 2001 to 21DEC01, but was finally declared done (starting the verification in regular service(VSR) phase); that the plaintiff did start to question the legal status of the software at that time;

      considering that AFPA started to question the sincerity of the 25MAY00 tender, (etc.) and that an offer to bargain and drop charges for EUR 228674 has been offered by AFPA; that finally given all that went wrong, the contract had been terminated 4JUN02

      Considering that Defendant sued AFPA for breach of contract because of the contract termination

      Considering that this Court already judged, on 22DEC06, that AFPA was entitled to getting its money back,

      Considering that the expert did perform his work correctly,

      Considering that AFPA's grief is not the use of Free Software, but the stealth use of a version of VNC modified in breach of the licensing terms (GPL), thus performing the act of counterfeiting, and the use of a backdoor password ("en introduisant un mot de passe connu uniquement de EDU 4 et non modifiable, permettant ainsi a EDU 4 de prendre le controle de tout poste en court-circuitant le mecanisme affiche de protection livre par EDU 4") [whoa, they really did this?? ] , and never did tell AFPA any of this

      Considering that EDU4 pretends it never hid the use of GPL, (etc.)

      Considering that EDU4 says the alleged defect on access control cannot justify the termination of contract, given that this defect was to be fixed within 2-3 months,

      Considering that proof was given that AFPA did know on 03AUG01 VNC and GPL software was to be delivered,

      Considering that on 27SEP01 EDU4 delivered licensing documentations which did not tell anything about GPL,

      Considering that on 21DEC01 the VA was pronounced only subject to EDU4 clarifying the legal status of all included software,

      Considering that on 04APR02, EDU4 alleged it never modified the VNC software, never breached GPL or copyright terms (except for set-up
      software, clear delimitation of EDU4 and VNC parts, etc.)

      Considering that the expert was unable to confirm the 04APR02 allegations on the materials delivered in Decembre 2001 (VNC was hidden, the
      license is not identifiable, the properties of the vncviewer.exe and winvnc.exe files had been altered, hiding the AT&T Research Labs name except for the vnc hooks.dll file,

      Considering that EDU4 failed to provide AFPA with the modified source code, which it had pledged to do on 15JAN02, thus voiding the allegation of a proper [GPL] delivery by 5APR02

      Considering that it appears from all facts that EDU4 failed to live up to its contractual obligations [...] caused the copyright notices to
      disappear from VNC, etc.

      Considering that AFPA is entitled, according to art. 1184 from Civil Code, to terminate the contract; that nothing being validated, EDU4 is
      not entitled to any payment

      Considering that EDU4, failing to prove its allegations, has to pay for all expertise and procedural costs (experts + 8K EUR)

      BECAUSE OF THOSE MOTIVES, THE COURT ... OVERTURNS the original judgement, and, deciding anew,

      declares AFPA (plaintiff) is founded in its demands

      declares EDU4 (defendant)'s claims are thrown out

      sentences EDU4 to pay AFPA 8K EUR

      sentences EDU4 to pay for all judicial and expertise costs, and that the appeal costs are to be paid for according to art. 699 of civil procedural code.

    2. Re:PDF of the decision on the FSF France website by e9th · · Score: 1

      Thanks, AC. Very informative.

    3. Re:PDF of the decision on the FSF France website by gnasher719 · · Score: 2, Informative

      A good one, and not without logic: If you take software licensed under the GPL, modify it, remove all the traces of the GPL and sell it on claiming that you wrote it, then this is an act of counterfeiting. Yes, that makes sense.

  6. Not much in the article either. by NoYob · · Score: 5, Funny
    ...an umbrella organization for adult education."

    So they teach about porn?

    --
    It's NOT me! It's the meds! I'm on 1000mg of Fukitol.
    1. Re:Not much in the article either. by Anonymous Coward · · Score: 0

      ...an umbrella organization for adult education."

      So they teach about porn?

      Not only that but it's the Umbrella. So it's Zombie Survival Horror Porn.

    2. Re:Not much in the article either. by wall0159 · · Score: 2, Funny

      French people don't need porn - they get laid.

    3. Re:Not much in the article either. by T.E.D. · · Score: 1

      You really don't want to know what the umbrella is used for...

    4. Re:Not much in the article either. by Anonymous Coward · · Score: 0

      ...an umbrella organization for adult education."

      So they teach about porn?

      Only a slashdotter would think that adult education was about porn and not actually having sex.

  7. Precedent by dr1982 · · Score: 0

    This could be an important legal precendent for the GPL in France and other European countries. Although Europe is more liberal in software licenses etc (no patents!) anyway, it's good to see that the GPL upheld in court.

    1. Re:Precedent by Razalhague · · Score: 1

      It means very little to other European countries. Different laws, different judicial systems etc...

    2. Re:Precedent by Ungrounded+Lightning · · Score: 1

      Isn't this the first time the GPL has proven enforcible by a CUSTOMER demanding the source? All the stuff I recall so far is the COPYRIGHT HOLDER doing the enforcement.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  8. Stupid GPL by Anonymous Coward · · Score: 0

    Yeah, I'll probably be rated flamebait for saying that, but for me as a shareware author the GPL is reason enough not to use GPL-licenced code. That's a pitty, because there are so many useful programming libraries released under GPL instead of the more useful LGPL. Let's face it: If the source code of a shareware app is released, it'll be cloned and ripped off within days. There are just too many people with no ideas on their own that love to make cheap copies just for the $$$, and most end-consumers cannot decide between quality and quantity (until it's too late, and they loose their data, for example). My 2 cents, I know the GPL people strongly/violently disagree.

    1. Re:Stupid GPL by Ash-Fox · · Score: 4, Insightful

      Yeah, I'll probably be rated flamebait for saying that, but for me as a shareware author the GPL is reason enough not to use GPL-licenced code.

      That is absolutely fine with the people who release their code under GPL. They want it in GPL applications, not Shareware.

      Feel free to release your own Shareware compatible libraries.

      I know the GPL people strongly/violently disagree.

      Their goals are different from yours.

      --
      Change is certain; progress is not obligatory.
    2. Re:Stupid GPL by localman57 · · Score: 1

      I'm new to GPL; Do I misunderstand? You aren't required to release everything that links to GPL libraries, right? Just any changes you make to the libraries themselves? Couldn't you continue to keep your shareware source closed, even if you use a GPL library?

    3. Re:Stupid GPL by gnasher719 · · Score: 1

      I'm new to GPL; Do I misunderstand? You aren't required to release everything that links to GPL libraries, right? Just any changes you make to the libraries themselves? Couldn't you continue to keep your shareware source closed, even if you use a GPL library?

      I am not a lawyer, but I can tell you that if you want to use someone else's code, no matter what the license, in your own product, then you better read the license very carefully and don't rely on posts on Slashdot. Asking a lawyer might be a good idea

      That said, if you use a library that is licensed under GPL and not dual licensed, then you cannot publish your code except under the GPL license. That's it. There are libraries published under the LGPL, which has different rules.

    4. Re:Stupid GPL by Anonymous Coward · · Score: 0

      So you don't want others to make money with your work. Why do you think GPL-authors shouldn't be allowed to want the same?

      Of course, it's very annoying if you cannot use a nice library because of its license but that's how its developers want it to be. They think prohibiting commercial use is better for them than what you get back from professional users. So be it. I'll just use something with a more open license and - at the minimum - report bugs and potential fixes/improvements there.

    5. Re:Stupid GPL by Chirs · · Score: 1

      The criterion is that if your work is a derivative work of the GPL'd code, then your work must also be released under the GPL.

      In many jurisdictions an app that links to GPL libraries would be at serious risk of infringing. There might possibly be a situation where it would not be at risk...if the app was written first and the GPL library modified later to conform to the linkage expected by the app, then likely the app would not be considered a derivative work.

      For specifics, please contact a lawyer.

    6. Re:Stupid GPL by Anonymous Coward · · Score: 0

      My understanding is:

      GPL:
      If you use any GPL software as part of your software, you have to GPL it, too. GPL library means GPL software. It's highly contagious. Although you can use products generated by GPL software (images, 3D models) in your apps without having to GPL them.

      LGPL:
      If you only dynamically link an unmodified version of a LGPL library you don't have to LPGL your own code. If you statically link or make modifications, you do.

      I don't rape Justitia for a living, though (read: I am not a lawyer).

    7. Re:Stupid GPL by TheRaven64 · · Score: 1

      Not quite. There is also the question of whether you distribute the GPL'd code. If you create, for example, a device driver for Linux that is binary-only but not a derived work of the Linux kernel, then you may distribute it without having to comply with the GPL. This is basic copyright law: the GPL has absolutely no way of enforcing anything different. Because the license you choose is not GPL-compatible, however, you are then prevented from distributing the Linux kernel. To give a concrete example, nVidia can distribute their Linux drivers in a binary-only format, but Linux distributions can not redistribute them along with the Linux kernel (they typically work around this by providing a simple post-install script that grabs them from the nVidia site and installs them).

      --
      I am TheRaven on Soylent News
    8. Re:Stupid GPL by TheRaven64 · · Score: 1

      If you use any GPL software as part of your software, you have to GPL it, too

      It's slightly more subtle than that. Product A is GPL'd. Product B uses A. Product B does not have to be GPL'd, but:

      • Product B does have to be released under a GPL-compatible license (e.g. BSD licensed) and
      • The combination of A and B is GPL'd.

      If B is not a derived work of A then you can distribute B under whatever license you like, but you can not distribute A at all unless B is under a GPL-compatible license (and that applies to all downstream distributors: no one is allowed to distribute B and A together).

      If you statically link or make modifications, you do.

      Not true. The LGPL has an explicit case for this. You have to distribute your modifications, but you do not have to distribute source code for things that are linked against LGPL'd code ever. If you are statically linking, then you have to distribute object code, allowing end users to link your code against a new version of the LGPL'd code, but you don't have to distribute the source code.

      --
      I am TheRaven on Soylent News
    9. Re:Stupid GPL by jc42 · · Score: 1

      Yeah, I'll probably be rated flamebait for saying that, but for me as a shareware author the GPL is reason enough not to use GPL-licenced code.

      Nah; you're not flamebait. You just want a license to do more with the code than he GPL grants. You should ask the copyright owners for such a license; they might be willing to give it to you. They might also ask a price for such a license. But note that you don't need a license to merely use GPL'd code. Unless you change the code, just running it on your computer is the primary use of such code, so the courts will agree that you have the right to do that (if you paid the vendor's asking price). You only need a license if you want to do something not allowed by copyright law, such as modify the code or distribute copies.

      I know the GPL people strongly/violently disagree.

      In most of the world, it not the GPL people; it's the copyright law. You have no right to make "derived works" at all without a license. The GPL is in part a license to make derived works. It imposes a condition that you apparently don't like: If you distribute your code, you must give recipients the same license. But the GPL is a standard sort of copyright license, since without such a license, you can't do much of anything with a copyrighted work except read it (or run it if it's computer code). This has nothing to do with violence; it's just a fact of life with the copyright mess we have right now. But you can't just take a copyrighted work, modify it, and sell it as your own work. Unless what you're doing fits the list of exceptions in your local laws (such as small excerpts, educational use, and parody), you can't legally do that. You need a license from the copyright holder to do more than what copyright law permits. And the copyright holder can put any conditions on your use that they like (as long as those conditions are otherwise legal).

      (N.B.: IANACL, but there are some here who can explain all this in much more detail. ;-)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    10. Re:Stupid GPL by Nursie · · Score: 1

      "Let's face it: If the source code of a shareware app is released, it'll be cloned and ripped off within days."

      Right, and what you're wanting to do by using GPL code without adhering to the rules is different from "ripping off" how?
      It was released so it can be used by others who are playing the same game, openness.

      You want people to pay for your closed source app, not to give your source back to the community, this is a totally different arena and not what the GPL'ers were aiming at. Sorry, open the source or write your own.

    11. Re:Stupid GPL by Nursie · · Score: 1

      Nope, sorry, I think it's you that misunderstands.

      BSD licensed products cannot use GPL components as they are not under the GPL. BSD code can be brought into a GPL project, but GPL code and GPL libraries cannot be used by BSD.

      "If B is not a derived work of A then you can distribute B under whatever license you like, but you can not distribute A at all unless B is under a GPL-compatible license (and that applies to all downstream distributors: no one is allowed to distribute B and A together)."

      What is a derived work is a contentious issue, but using dynamic links does NOT absolve you of the need to go GPL, regardless of your distribution policy. Just shipping things on separate media doesn't stop you being a derivative work.

    12. Re:Stupid GPL by Anonymous Coward · · Score: 0

      I'm new to GPL; Do I misunderstand? You aren't required to release everything that links to GPL libraries, right? Just any changes you make to the libraries themselves? Couldn't you continue to keep your shareware source closed, even if you use a GPL library?

      If it's a GPL library, then yes, you would have to release your code as well.

      However most libraries are released under the the LGPL rather than the GPL. The LGPL is specifically designed for this situation. LGPL code does allow you to link to it without having to release your own code, but you would still be required to make the library's code available if you distribute it, and to release any changes you made to the library itself.

      Hope that helps.

      (NB: IANAL!)

    13. Re:Stupid GPL by TheRaven64 · · Score: 1

      Read the GPL, and the relevant bits of copyright law, and what I wrote, again. I'm too lazy to check the GPL now, but I seem to remember Clause 5 being the relevant one. BSD licensed code can use GPL'd libraries. The BSD-licensed code remains BSD licensed, but the combined work must be under the GPL (actually, even that's not quite true; it must be under a license which is semantically equivalent to the GPL, but not necessarily the GPL, although from a practical standpoint that's a distinction without a difference).

      --
      I am TheRaven on Soylent News
    14. Re:Stupid GPL by Nursie · · Score: 1

      You're getting into a VERY grey area there. GPL v2 clause 3 (just after subsection c) -

      "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works."

      Now, if your code is dynamically linked at build time and won't even start without the GPL library, I would argue that you're not in the clear. If, however, you code something to dynamically load up a GPL library at runtime, if it's available, and otherwise use some other facility, and the general operation of your program is much the same... well you're probably OK. Probably.

    15. Re:Stupid GPL by Anonymous Coward · · Score: 0

      most end-consumers cannot decide between quality and quantity (until it's too late, and they loose

      It's lose, my stupid dear. And you can shove your shareware where the sun don't shine. Have a nice day!

    16. Re:Stupid GPL by Dragonslicer · · Score: 1

      Unless you change the code, just running it on your computer is the primary use of such code, so the courts will agree that you have the right to do that (if you paid the vendor's asking price). You only need a license if you want to do something not allowed by copyright law, such as modify the code or distribute copies.

      Just to clarify, this is incorrect. You can modify GPL code in any way you want. The restrictions of the GPL only apply to distribution of the software. If you don't give the software to anyone else, you don't have to give anyone else your modified source code either. Also note that this aspect has the potential to be abused by large organizations that use the software internally, even when "internally" means offices in 20 different countries.

    17. Re:Stupid GPL by sumdumass · · Score: 1

      I wouldn't necessarily consider that was a potential of abuse. I would say it's as intended.

      The four freedoms that are supposedly underlying the GPL is about your rights as a user who may become a distributor. I find with that in mind, even with Stallman's print driver story as justification for the GPL and free software, companies using it internally would be as intended.

      I would say that I think it's a loss of valuable improvements when something like that happens. I would also say it isn't necessarily good when a company keeps it's improvements. But I find it completely in line with the intent of the GPL and the movement behind it. I guess we could just call that bug a feature.

    18. Re:Stupid GPL by david_thornley · · Score: 1

      I don't see what the problem is between you and the average GPL fan.

      You see a lot of useful programming libraries out there, and want to use them. It doesn't matter specifically that they're GPLed, only that you are unwilling to pay the price to use them. For some libraries, the price is monetary; for the GPL, it's some restrictions on redistribution. As far as I'm concerned (although Stallman would disagree), your only fault here is that you apparently want to use other people's copyrighted software in ways they don't allow, and that you call a license stupid because it does what the people who wrote the software want and not what you want.

      You complain about what happens when you release source, but this is exactly what the authors of GPLed code want to have happen to their programs. I'm not saying that one side or the other is right, but you have opposed goals here. It's no surprise that you disagree about the licenses you want.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    19. Re:Stupid GPL by Dragonslicer · · Score: 1

      All true, and I'm not saying that it necessarily needs to be changed. First of all, you'd have to draw a line somewhere about what would be considered too big to be internal use, and that line would have to be rather arbitrary. Some people would consider it abuse for a company like Sony to distribute modified GPL software to all of its child companies, and some people wouldn't. The system can never be perfect, you can only try to make it as good as you can.

    20. Re:Stupid GPL by sumdumass · · Score: 1

      I would suggest that as long as the companies are owned by the same parent company and that parent company takes an active role in the direction of the company, it could be considered within the company.

      Let's look at Verizon for instance. They separate their wireless cell phone operations from their pots and broad band or traditional services. Keeping the code within their wireless division would be ok but moving it to their POTs line of Business should be a distribution. However, if they distribute the source code with the binary packages, then their source code distribution obligations are satisfied according to the GPL which leaves us in the same boat outside of Verizon.

      So even if we forced source distribution between sister companies and stretched out divisions under the control of a parent company, there are ways that they can comply and we still do not benefit. Again, I think this is as intended.

    21. Re:Stupid GPL by mqduck · · Score: 1

      So let me get this straight. You're pissed off that people won't share their code for free with you so you can use it to make software to charge other people for?

      --
      Property is theft.
    22. Re:Stupid GPL by SETIGuy · · Score: 1

      Yeah, I'll probably be rated flamebait for saying that, but for me as a shareware author the GPL is reason enough not to use GPL-licenced code. That's a pitty, because there are so many useful programming libraries released under GPL instead of the more useful LGPL. Let's face it: If the source code of a shareware app is released, it'll be cloned and ripped off within days.

      No, you're not spouting flamebait. You're just someone who like to make money off of other peoples' work. I believe the term is "entrepreneur" which (if taken literally) is French for burglar (one who enters and takes).

      If you want to use a GPL library in your shareware, you can always contact the authors and ask if you can buy a commercial license to the code. From what I've seen of other shareware that has stolen GPL code, the GPL code is 99% of the work. If that's the case, they'll probably want 99% of the take. Google "video conversion software" and 90% of the results will contain ffmpeg without attribution or source.

      The other option is that you can write your own damn libraries for use in your shareware.

    23. Re:Stupid GPL by Jedi+Alec · · Score: 1

      I believe the term is "entrepreneur" which (if taken literally) is French for burglar (one who enters and takes).

      Might I suggest you stop "believing" stuff and just look it up instead? There's references online going as far back as the 13th century where the word is used for someone who organises thing, often in the context of public works. The same word occurs in a lot of different languages, although oddly the "entre" (lit. "between") has been exchanged for "under". So in english we have the undertaker(different meaning), but the verb "to undertake" is quite close to the spot. In dutch we have the "ondernemer", in german the "Unternehmer". All of them refer to a person who takes responsibility for a job that needs to be done, often related to construction work. The economic meaning of someone who is in charge of a company developed later.

      wiki link

      --

      People replying to my sig annoy me. That's why I change it all the time.
  9. What the hell? Crazy French! by Rogerborg · · Score: 1

    Hang on just a second. Does the AFPA (the plaintiffs) own the copyright on the GPLd source? They do not. Then what standing do they have to sue anyone over it, or receive payment? This is GPL related, but the relief went to a 3rd party!

    --
    If you were blocking sigs, you wouldn't have to read this.
  10. Re:What the hell? Crazy French! by selven · · Score: 1

    If they added even the slightest bit to the code, and redistributed their version (following the GPL of course), then they own the copyright to that version of the code.

  11. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    As I understand it, the GPL says that the source code has to be available with the binaries.

    So if the binaries are for the general public, everybody has access to the source.

    If the binaries are delivered to a client (in this case AFPA), the source should be available to them.

  12. Re:What the hell? Crazy French! by Rou7_beh · · Score: 1

    The GPL garanties access to the source code for the USER. AFPA is the user here.

  13. Re:What the hell? Crazy French! by Narishma · · Score: 4, Informative

    Read the article. The AFPA requested the source code of the modifications the company (Edu4) did to VNC but the company refused to provide it and so they were sued.

    --
    Mada mada dane.
  14. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    I don't read french so I'm just guessing: The deal AFPA made with Edu4 stated that VLC is used as the base. So AFPA expected to get the source code changes with the binary and sued when that didn't happen... Sounds plausible to me and explains why they were allowed to sue.

  15. Re:What the hell? Crazy French! by Rogerborg · · Score: 1

    Sorry... I forgot where I was for a second. I meant to say: this is like the RIAA stealing your car, crashing into a bus of drunken cheerleaders, then Microsoft embezzling the insurance money.

    --
    If you were blocking sigs, you wouldn't have to read this.
  16. quit spreading FUD - try reading the GPL by Anonymous Coward · · Score: 3, Informative

    Your statement is (sadly) one of the many common FUD scarecrows foes of open source use to try to prevent companies from using GPL software.

    The GPL very specifically only requires you to offer to "convey" the "Corresponding Source" to the parties to whom you have conveyed object or binaries containing your modifications AND that you convey to those same parties your distribution rights so that they may convey your object/binaries and corresponding source to anyone they choose to (as long as they do so under GPL licensing terms).

    The GPL intentionally does not impose the burden for modifiers to positively disseminate their "Corresponding Source" to anyone other than those to whom they have already incurred the burden of distributing the binaries.

    1. Re:quit spreading FUD - try reading the GPL by Chris+Burke · · Score: 4, Insightful

      The GPL intentionally does not impose the burden for modifiers to positively disseminate their "Corresponding Source" to anyone other than those to whom they have already incurred the burden of distributing the binaries.

      GPLv2 section 3b. If you don't convey the source directly with the object code, you must convey a written offer valid for any third party to send them the source code upon request.

      I had forgotten that this was an "or" clause, but it is in the GPL, so maybe you should read it too?

      And this isn't FUD for anyone who wasn't already terrified of the GPL. Why is conveying a link to a website with the source such an onerous burden? Especially when that link can simply be to whatever CVS repository the open source project normally works from, assuming you committed your changes to it? Seriously.

      --

      The enemies of Democracy are
    2. Re:quit spreading FUD - try reading the GPL by wastedlife · · Score: 1

      My understanding of v2 is that just a link is not sufficient, you need to provide other means, including offer to ship a CD.

      I believe that was fixed in v3, though.

      Not that either seems to be a heavy burden considering the wealth of free, stable code you get in exchange. I think the biggest fear is the FUD spread by closed-software corporations that make it seem like you would lose competitive edge or company secrets in order to facilitate the license requirements.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    3. Re:quit spreading FUD - try reading the GPL by MSG · · Score: 1

      You mean section 6b. There are no subsections to section 3. Section 6 provides five options for conveying non-source forms of the software. Any one is allowed. One of them allows you to convey a non-source form if you include a written offer to give the source code to anyone who possesses the object code (subject to a fee if the conveyance is via physical media).

      For someone lecturing people on reading the GPL, you've done a poor job of it yourself. The AC you were lecturing was correct, more or less. You are required to offer the source code only to the parties to whom you've given the object code, or possibly parties to whom they've given the code. You are not required to publish the code to "any third party" who requests it.

    4. Re:quit spreading FUD - try reading the GPL by MSG · · Score: 1

      Oh fuck, and shame on me. I'm looking at a copy of v3 that I was sure was v2. Reading comprehension failure. Hilarious.

      All the same, 3b is one of three options. You are not required to publish the code to any third party unless you opt not to follow either 3a or 3c.

    5. Re:quit spreading FUD - try reading the GPL by Anonymous Coward · · Score: 0

      "In a manner..." oh, whatever. You have to provide on a standard machine readable interchange format.

      Disk, internet, whatever. This is to keep people from printing out 2000 pages of code and mailing them to you.

    6. Re:quit spreading FUD - try reading the GPL by aztracker1 · · Score: 1

      It also doesn't say that the changes to the source need to be given in a convenient format... a printout of the original source, along with printouts of every diff pattern would be sufficient for compliance.

      --
      Michael J. Ryan - tracker1.info
    7. Re:quit spreading FUD - try reading the GPL by Chris+Burke · · Score: 1

      All the same, 3b is one of three options. You are not required to publish the code to any third party unless you opt not to follow either 3a or 3c.

      Yeah, that was my mistake. It's funny I've actually read the GPL like a hundred times but can still fail at some of the details. I guess part of the reason is that if you really are trying to comply, it's so easy that most of the details don't matter much. :)

      One interesting thing though, is that since they clearly did not accompany the binary distribution with source ruling out 3a, and since they are commercial, that rules out 3c, so their only choice for compliance would be 3b.

      Of course practically speaking I'm sure the plaintiffs would be fine with just receiving the source themselves and calling it an instance of 3a. It's in our interest to make complying with the GPL painless even for the non-compliant. :)

      --

      The enemies of Democracy are
    8. Re:quit spreading FUD - try reading the GPL by Rene+S.+Hollan · · Score: 2, Interesting

      Actually, it CAN be a heavy burden. For a company that is starting to use GPL code, and DOES wish to comply with the GPL, but has not historically distributed source, to their clients, much less, anyone who asks, this can be a significant burden because it lacks the distribution channels to do this professionally.

      I ran into this hurdle with a former employer. The problem was that to distribute source effectively would require distributing much of our build mechanism as well because of the dependency hell that would otherwise ensue for anyone actually trying to use it -- and this was (a) hardly polished for external consumption, and (b) there was some desire to keep the build and interdependency resolution system proprietary.

      While I eventually sorted that out, and made it possible to deliver "nice and friendly" source distribution CDs, these were delayed by about a month after the product was ready to ship (an embedded system). Manufacturing was balking at including "unnecesasry" components in the parts breakdown, and IT was balking at having to support a web server to distribute source to ALL comers, or worse, have to go into the CD pressing business. Finally, we actually had some customers that WANTED binaries but EXPRESSLY did not want source. The written offer would have placated them (they could ignore it), but the fact that it would have to be transferrable worried us.

      In our case, we leveraged GPL code in rack-based systems that performed remote internet protocol diagnostics (down to PPP negotiation debugging on T1/E1 digital channels fed from telco-side modems in ISP cages). We sold to few customers, but for millions of dollars. Some of the code we modified was arguably useful outside of that context to a wide audience. But, our whole distribution mechanism was not geared to accomodate a "wide audience".

      So, we had (a) a delay in making a source distro, (b) packaging and IT that were "out of the loop", (c) customers who didn't WANT source distros, and (d) strong opposition to the alternate "offer" requirement to meet all comers.

      In the end, I felt my job had been done in putting together a source distro, and my warnings about what GPL v2 required.

      Our customers (telcos offering ADSL), understandably, having spent millions of dollars for what we provided (hw, software, and support), were not eager to share the bits they got, so the "wide-spread all comers" scenario never came to pass.

      We had a further problem related to distributing source code to some of our subcontractors: RMS was of the opinion that if it runs on their machines and not ours, we have to provide them source. All well and good, but there was a delay in making that possible: our build mechanism was tied into our source control system (Clearcase) for resolving dependencies, and they were not to have unfettered access. We ended up having them work inhouse, on our hardware.

      Oh, and the customer who ademently didn't want a source CD? They didn't get one. but the "parts breakdown" for the manual was interesting in that it included a CD sleave and CD.

      The point is that the logistics of GPL v2 complience for a company not used to wide distribution or source distribution are sometimes non-trivial. Often it comes down to not minding sharing source with direct customers, but not wanting to start up a CD pressing plant.

      --
      In Liberty, Rene
    9. Re:quit spreading FUD - try reading the GPL by SETIGuy · · Score: 1

      The GPL says quite plainly that it must be the source code used to compile the binary (not patches or diffs) and in machine readable format.

    10. Re:quit spreading FUD - try reading the GPL by Schraegstrichpunkt · · Score: 1

      My understanding of v2 is that just a link is not sufficient, you need to provide other means, including offer to ship a CD.

      My understanding of the FSF's interpretation of GPLv2 is that you have to ship a physical medium if somebody actually asks, but if you provide an FTP site or something else that works more effectively, then nobody will ask.

    11. Re:quit spreading FUD - try reading the GPL by Schraegstrichpunkt · · Score: 1

      It also doesn't say that the changes to the source need to be given in a convenient format...a printout of the original source, along with printouts of every diff pattern would be sufficient for compliance.

      It says the source needs to be "machine-readable", distributed "on a medium customarily used for software interchange", and that source code is "the preferred form of the work for making modifications to it".

      I have no idea how you think a printout of "git log -u" would meet those requirements. Judges are not so easily fooled.

    12. Re:quit spreading FUD - try reading the GPL by rustl · · Score: 1

      Actually, it CAN be a heavy burden. For a company that is starting to use GPL code, and DOES wish to comply with the GPL, but has not historically distributed source, to their clients, much less, anyone who asks, this can be a significant burden because it lacks the distribution channels to do this professionally.

      But by doing what you have done you acknowledge that the heavy burden of GPL compliance was more cost effective than rewriting the code you wanted.

      You also now have the benefit of the ongoing GPL improvements to the code you are using, as well, by now having a GPL compliance mechanism in place you can use other GPLed code at no extra cost.

    13. Re:quit spreading FUD - try reading the GPL by Rene+S.+Hollan · · Score: 1

      Well, yes, but as a chemist would say, the activation energy was a bit of a bitch to overcome.

      More to the point, much of the complience burden had to be foisted on departments other than Engineering.

      Using GPL code helped us meet our price and market entry goals, yes, but it messed with the budget of Manufacturing, and because of the contractor issue, HR: "Why, exacly, can't they use their own computers?

      GPL complience isn't an engineering issue, it's a corporate issue. Any time your plan to save money involves costing another department money, even as a "one off" to get process in place, and even if the net effect is beneficial, you have a major hurdle to overcome.

      --
      In Liberty, Rene
  17. Re:What the hell? Crazy French! by Aim+Here · · Score: 5, Informative

    It's an idiosyncracy of French law. The plaintiff here was a customer who did, yes, successfully sue for the source code. It probably couldn't happen in the US or UK.

    FSF France's take on this finds this noteworthy:

    "But what makes this ruling unique is the fact that the suit was filed by a user of the software, instead of a copyright holder. It's a commonly held belief that only the copyright holder of a work can enforce the license's terms - but that's not true in France. People who received software under the GNU GPL can also request compliance, since the license grants them rights from the authors."

    Just when you thought the German courts were GPL-friendly, this shows up. Vive la France!

  18. Re:What the hell? Crazy French! by russotto · · Score: 4, Informative

    Hang on just a second. Does the AFPA (the plaintiffs) own the copyright on the GPLd source? They do not. Then what standing do they have to sue anyone over it, or receive payment? This is GPL related, but the relief went to a 3rd party!

    Well, first of all, this was French law, not US or English, so their idea of standing might be different.

    Second, the AFPA were third party beneficiaries of the GPL -- as receivers of the binary, they were entitled (by the GPL) to receive the source. This might have granted them standing even in the US.

    From
    http://ejustice.org/federal_practice_manual_2006/chapter_5/chap5sec3.html

    Section 302 defines all beneficiaries of a contract as being intended or incidental. Only an intended beneficiary has standing to enforce a contract between two other parties. Whether a person is an intended beneficiary with the resulting right to sue depends upon the intention of the parties to the contract. That intent may be articulated in the contract itself, or discerned or imputed from the statutory context that prompted the contract to be executed.

    The GPL (IMO, IANAL) makes it crystal clear that the person receiving the binary is an intended beneficiary.

  19. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 1, Informative

    Worse. EDU4 never stated in its tender that it was to use VNC.

    It did afterwards, but then in what was supposed to be the final delivery (start of the Validation of Aptitude phase, which is where, in typical French IT purchase contracts, is where you deliver the final software and Client verifies it satisfies all contractual demands, but in practice some leeway for patches is introduced) modified GPL was delivered without ever showing that it was GPL software (and nary a source file in sight).

    EDU4 first sued to get paid as AFPA considered the delivery terminally incorrect and voided the contract (which is an explicit possible outcome in public IT contracts). AFPA showed in the first trial that GPL was being breached; the first judge didn't understand the deal. The Court of Appeals took the GPL at face value (which is hugely significant) and found that perfectly valid grounds for AFPA's behaviour all along.

  20. strike ONE by Anonymous Coward · · Score: 1, Funny

    2 more left for them

    1. Re:strike ONE by schon · · Score: 1

      Nope. The law says that you get one strike for each accusation, not conviction.

      Considering there were at least two other instances where they were told they were infringing (once when they were notified, the second was the original court case) then they're ready to be disconnected.

  21. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0
    FTFA:

    Now, the higher court has confirmed the ruling that Edu4 should pay â8,000 (£7,195) to the AFPA and cover both the cost of court proceedings and two expert opinions.

  22. Backdoor by phme · · Score: 5, Interesting
    From the text of the decision, it appears that the provider (Edu4) had not only removed GPL copyrights from VNC, thus making the product likely to be considered counterfeit, but also introduced a backdoor

    Considering that Edu4 [...]
    - modified VNC protection mechanism by introducing a non-modifiable password known only from Edu4, thus allowing Edu4 to take control of any workstation, bypassing the protection mechanism Edu4 delivered;
    - did not mention any of this to AFPA;
    - [...]

    1. Re:Backdoor by Dragonslicer · · Score: 1

      If that's correct, shouldn't Edu4 be liable for a lot more than copyright violations? Maybe for something like spying and/or wiretapping?

    2. Re:Backdoor by sumdumass · · Score: 1

      Not necessarily. Part of their service agreement and installation contracts could have warranted this back door for convenience of support.

      What would have made it a violation of something like spying or wiretapping (computer trespass) might be if it was actually used outside it's official context or after contract obligations expired or threatened as leverage to a contract renewal or something.

    3. Re:Backdoor by jc42 · · Score: 1

      Edu4 had not only removed GPL copyrights from VNC, thus making the product likely to be considered counterfeit, but also introduced a backdoor

      Hmmm ... In a number of countries, doing this secretly without a court order would be a criminal offense, punishable by large fines and/or some amount of prison time. I wonder if this is the case in France? Anyone know?

      I've written a lot of software, and in most of it I've included debug hooks that I leave in the deliverable for when the users are having problems. I always document the debug hooks. It can be really handy if Customer Support can tell them "Add a -d3 option to the foo command and send us the log file." In several cases, I've included warnings that at levels N and above, the debug log may include things like passwords and encryption keys, so they should be very careful with the logs and erase them quickly. I do this mostly to let them know that such help is available when they need it. But I'm also always thinking that debug hooks can easily qualify as "backdoors", and are probably illegal unless the user is fully informed of their presence. On a couple of projects, the managers have ordered that this information be removed from the documentation. I've let them know (as nicely as I can) that they could be committing a criminal act in hiding the this information from customers. In each case, they have ignored this and trimmed the documentation anyway. So I kept copies of the email, just in case I'm called to testify. So far, this has never happened.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    4. Re:Backdoor by Dragonslicer · · Score: 1

      The text of the decision says that they didn't tell AFPA about the backdoor, so I would assume that it wasn't part of any kind of agreement or contract.

    5. Re:Backdoor by mqduck · · Score: 1

      I wonder if this is the case in France?

      I don't know. Do you or don't you wonder that?

      --
      Property is theft.
    6. Re:Backdoor by sumdumass · · Score: 1

      It wouldn't necessarily need to be actually in the agreement or contract. I have either RRAS or log me in account for every windows site I support along with a bona fide user account on all their servers or domains. I use SSH and a VPN connection for the non-windows sites and for a medical building where half of the network is fire walled off from the other half for HIPPA compliance. This is not spelled out in the contracts but it allows me to do my job by either checking the problem before I show up to make sure I have any tools or parts necessary (out of band management cards are a great help for this) or to see if it's something I can straighten up/accomplish without making a trip which saves the customer money.

      If any place fires me, I can't access them, even to uninstall it or disable my accounts. It would be unethical and perhaps even illegal. I can tell them about it or not, if they look hard enough, it will be in the spec books but the last time I lost a job to the owners "rocket scientist" nephew, he lost the spec books within a week of taking over (it's really fun explaining that the inflated bill is for the replacement tech constantly calling me asking what to do and since they terminated their contract, it's regular price or their lack of preparation or readiness stopped being my emergency when they terminated my contract so night hour rates applied).

      Anyways, the point is, if it enables the job to get done, they do not necessarily need to know about it. It's a legitimate use of the tools and technology to fulfill the contract. Once the contract has ended, if possible, I would uninstall them and disable access before the last day but it doesn't always work out that way.

      Now if I used the remote access for anything that wasn't a bona fide support effort, then I would have crossed the line into illegalities. All my contracts say I can get remote access, they do not say how or when or specify any particulars like my service accounts (which would equal a back door).

  23. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    Crazy American ! How can you to protect yourself against copyright law infringement by which you are affected when you aren't the owner if you cannot sue ?

  24. Re:What the hell? Crazy French! by Archangel+Michael · · Score: 2, Informative

    Just when you thought the German courts were GPL-friendly, this shows up. Vive la France!

    Okay, we are returning "Freedom Fries" back to their original name "French Fries". Happy now?

    We still apologize for French's Mustard, which is not french and can barely be called mustard.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  25. 2 words and a question by ArsenneLupin · · Score: 1

    Gemalto. OpenSC. "Where is the source of libgemsafe0?"

  26. Re:What the hell? Crazy French! by Rogerborg · · Score: 1

    Read the VNC source. Do you see "Copyright AFPA" in there? What kind of crackpot legal system lets Alice sue Bob over Carol's copyrights?

    --
    If you were blocking sigs, you wouldn't have to read this.
  27. Re:What the hell? Crazy French! by Rogerborg · · Score: 1

    But AFPA does not own any copyrights in the original VNC source, and in any sane jurisdiction wouldn't be able to receive relief over those rights. I can't figure out if this case is over contract law (therefore not a GPL issue), over AFPA's rights to any modified source that was created for them as a work-for-hire (therefore not a GPL issue) or is genuinely them asserting rights that they don't own (insane in the membrane).

    --
    If you were blocking sigs, you wouldn't have to read this.
  28. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    Wait a second !

    Are the cheerleaders GPL ? Not.

  29. Re:What the hell? Crazy French! by Rogerborg · · Score: 2, Interesting

    Thanks, that's interesting reading. I'm still puzzled as to what kind of wacky statue gives AFPA standing to receive relief for breach of someone else's rights. That's like... well, there is no appropriate analogy. It's exactly like receiving relief for breach of someone else's rights. The mind boggles as to the size of the can of legal worms that opens up in France.

    --
    If you were blocking sigs, you wouldn't have to read this.
  30. Re:What the hell? Crazy French! by sumdumass · · Score: 2, Interesting

    If I understand the sets of circumstances here, the Edu4 stripped the GPL and copyright notices from the product and pretended it was their own. They even pretended that they didn't distribute the product even though they left it on the computers they installed.

    If these claims are true, it would be near impossible for an end user in the US to claim to be the intended beneficiary. This would be because they had no idea of the specific contract obligations until after the fact which would push them more to the incidental beneficiary then the intended. Further more, the VPN software was installed as a support and deployment resource and it's arguable that under English law, if any transfer actually took place or not. I have installed software under these circumstances and haven't transferred it before.

    In the french court, all that didn't matter and they were found guilty. Now, in an english court, if the GPL was presented to the end user or the software was marketed/promoted as GPLed software, then it would likely have standing under contract law. I have been arguing for years that the GPL is a contract concerning copyright while entities like the FSF and their fan base attempt to claim it's just copyright. The truth of the matter is that the GPL is a contract affording certain rights to copyright under certain conditions so it's rightfully both. (ie, you cannot do the things copyright law reserves to the copyright owner unless you agree to a contract and fulfill obligations specified in it as they pertain to your use)

    This concept of the end user being able to enforce the GPL shouldn't surprise anyone who has been paying attention. In this particular case, the concepts were a little blurry and probably wouldn't survive in a US or UK court. It's sad that the FSF and people like Bruce Perens and Stallman have fought so hard to bury that concept in order to keep in line with their mantra or ideology. IF they hadn't, then the real power of the GPL should have been seen a long time ago.

  31. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    In this case, I'd call it "a fair one".

  32. Re:What the hell? Crazy French! by godrik · · Score: 1

    Any sane legal system should let ANYBODY sue over ANY illegal thing. Unfortunately, it is not like this in France.

    IANAL but I believe in France the only thing you need to be allowed to sue is to have something to gain. Here AFAP have access to the source code to gain, therefore is allowed to sue.

  33. Re:What the hell? Crazy French! by godrik · · Score: 1

    I would like so much the cheerleaders to be free...

  34. Re:What the hell? Crazy French! by tinkerghost · · Score: 1

    All of them when Carol has guaranteed Alice the right to have access to her work covered under the copyright in question. Carol has standing as the original copyright holder and can sue for any number of reasons. Alice can only sue to obtain access to the copyrighted works (the sourcecode) because the GPL explicitly states that Bob has to give them to her if he distributes the binaries. In most cases the relief will be access to the code, legal fees, and possibly some punitive damage amount to remind Bob to play nice in the future.

    Contrast that with Carol's reward in the same case - in the US that would be an injunction on distributing their code until they released the code openly and statutory damages of obscene amounts, and legal fees.

  35. Re:What the hell? Crazy French! by russotto · · Score: 2, Informative

    If these claims are true, it would be near impossible for an end user in the US to claim to be the intended beneficiary. This would be because they had no idea of the specific contract obligations until after the fact which would push them more to the incidental beneficiary then the intended.

    Nothing in the information I posted or linked to says anything about concealing the terms of a contract from an intended beneficiary makes the intended beneficiary incidental. If you have other information please post it.

    Auto analogy:
    Ford sells off-lease cars to independent dealer "Car Emporium", with the contract of sale stating that "Car Emporium" will provide complimentary maintenance for these cars to whoever they resell it to for one year after that sale. "Car Emporium" doesn't do so and conceals the existence of that contract from the buyers. The buyers somehow find out. They _DO_ have standing to sue "Car Emporium", as they were an intended beneficiary of the contract.

    I have been arguing for years that the GPL is a contract concerning copyright while entities like the FSF and their fan base attempt to claim it's just copyright.

    The FSF doesn't claim it's "just copyright". They claim it's a license. They also claim if that IF you don't accept the license, THEN what you have is "just copyright". The defendants in this case could have claimed they never accepted the GPL, but that would have put them in hotter water. There likely STILL would have been a cause of action by the plaintiffs (because the defendant had provided them, unknowingly, with illegal copies of software), and there would have been a cause of action by the copyright owner for copyright violation.

  36. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    The California legal system, the most crackpot in the world!

  37. Re:What the hell? Crazy French! by mea37 · · Score: 3, Informative

    They didn't sue over the copyright. They sued over license violations that impacted them. The operative words are "that impacted them"; that gives them legal standing.

    The license gets its force from the copyright, but that changes nothing. The plaintif had a right which the defendant violated, regardless of the fact that the right in question was granted by a document whose authority came from somebody else's rights.

  38. GPL or LGPL by gr8_phk · · Score: 1

    I'm new to GPL; Do I misunderstand? You aren't required to release everything that links to GPL libraries, right? Just any changes you make to the libraries themselves? Couldn't you continue to keep your shareware source closed, even if you use a GPL library?

    No. If you link to a GPL licensed library, the executable is a derivative work of that code and hence you must release all of the source code for the executable. Fortunately, many "Free Software" libraries are licensed under the LGPL license, in which case you would be correct so long as you dynamically link the library. You still have to offer source for the library when you distribute it (or provide the source to the library with the binary library) but you do NOT have to release source for your application. There are plenty of commercial and shareware game that use the SDL library for example, which uses the LGPL. IIRC, static linking an LGPL library puts you in the same position as if it were a GPL library and you need to provide/offer source to the whole application.

  39. Re:What the hell? Crazy French! by DigitalContradiction · · Score: 1

    I read the court ruling, and the issue is not exactly what it seems ; it's basically contract law. First, it appears that everybody (the AFPA and Edu4) was aware that VNC would be used from the beginning and that it used the GNU GPL license. Both the AFPA and Edu4 were initially fine with that, and Edu4 was supposed to keep the original copyright notice and licence and to distribute the source along with the binary. It seems that Edu4 somehow changed their mind and : 1) changed the copyright notice of VNC to replace the name of the legitimate VNC copyright holder by their name, and distributed it under their own terms with the rest of the software 2) did not distribute the modified source, although the AFPA asked 3) hardcoded a secret password in the modified VNC that allowed them to use it as a backdoor (!) What I understand of the ruling (I'm french, but I'm no lawyer) is that by changing the copyright notice of VNC and licensing it along with the bulk of their software under their terms, Edu4 basically sold the AFPA a counterfeit product, which breaks the contract. (And they didn't like the backdoor part either.) I think it makes more sense when you say it that way.

  40. Re:What the hell? Crazy French! by mea37 · · Score: 4, Insightful

    "Any sane legal system should let ANYBODY sue over ANY illegal thing"

    Say what?

    First let's put this in context: people sue over civil matters - not criminal ones. Indeed the case in question - a GPL violation - is a civil matter. So what you're saying is "if I do something that makes me liable to Bob, Jim should be able to sue me".

    What if Bob and I are perfectly happy to resolve the matter out of court? Why, then, would it be any of Jim's business? The civil courts are there as one means of conflict resolution - and most reasonable people consider them a last resort. If you're not part of the dispute, you don't get to decide what method should be used to resolve it.

    Again, if we were talking about a criminal offense, that's completely different. It would be considered the business of everyone in the society - which is why neitehr Bob nor Jim sue in that case, but rather the state brings charges (potentially even if Bob would rather they didn't).

  41. Re:What the hell? Crazy French! by Permutation+Citizen · · Score: 2, Interesting

    AFPA is a customer of Edu4. They buy an software system from them, for a given purpose. When they receive the product, they see that part of the software is not owned by Edu4 and that Edu4 has no right to redistribute this software as they don't comply to GPL and they don't have alternate license to redistribute it. AFPA sue Edu4 for selling them something they have no right to redistribute.

    Imagine you go to a shop and buy a MS Office License. You go home and it appears this is an illegal copy. Don't you have the right to sue the shop to get a real one you have paid for ?

    To come back to initial case, that's good news as when you are OSS user, you never know if the copyright holder of code you use will bother to take the expenses and risks to go to court to help you.

  42. Re:What the hell? Crazy French! by dwater · · Score: 1

    > We still apologize for French's Mustard, which is not french and can barely be called mustard

    How about English Muffins? I'd never seen one before I went to the US.

    --
    Max.
  43. Ah by Hognoxious · · Score: 1

    Ah sontance yow to a slarp acroz ze face.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  44. Re:What the hell? Crazy French! by wastedlife · · Score: 1

    My understanding of the GPL is that if they made a patch, changed some code, or added some new code, they would own the copyright to those changes only, the rest is owned by the original creator(s) of that code. The GPL is not a copyright assignment, but a distribution license. This is why some of organizations require copyright assignment to them from community contributors, so that they can sell versions of the software under a different license without having to track down the contributors and make licensing arrangements.

    I could very well be wrong, anyone have a link to the FSF explaining this?

    --
    Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
  45. Re:What the hell? Crazy French! by godrik · · Score: 1

    I believe that law should be respected. full stop. My interest as a citizen of a country is that laws are respected. It is the only point in having a state.

    I believe US laws allow a lawyer to sue in the name of someone that may not agree with the lawsuit. I think it is linked with class actions but I am not sure of it.

    There are case where you can not sue due to the costs of the lawsuit or due to pressure applied on you. It is classical in employer/employee relation. It is classical in France in the employment-on-demand system which are sometimes completely illegal. But the employee says nothing because he/she does not want to sleep under a bridge.

  46. Re:What the hell? Crazy French! by Rhaban · · Score: 1

    They receive relief for the breach of their right to have the source code.

    Doesn't matter if they are the copyright holders or not, they have rights on this code. Just not copyright.

  47. Re:What the hell? Crazy French! by selven · · Score: 1

    Sorry, that was a mistake, the distributor only owns the changes, they can't redistribute the work under a different license. But they do still have the power to sue for redistributing their modifications without source code.

  48. Comparison of licenses by Anonymous Coward · · Score: 0

    Release the following under public domain, GPL, and BSD

    10 print "The 50 states of the US"
    20 print "Alabama"

    What happens next?

    1. Re:Comparison of licenses by Frankie70 · · Score: 2, Funny

      Release the following under public domain, GPL, and BSD

      10 print "The 50 states of the US"
      20 print "Alabama"

      What happens next?

      Stallman wants everyone to refer to USA as GNU/USA?

    2. Re:Comparison of licenses by SETIGuy · · Score: 1

      Release the following under public domain, GPL, and BSD

      10 print "The 50 states of the US" 20 print "Alabama"

      What happens next?

      You get sued by a user of the public domain version, because you neglected to include a disclaimer of warranty.

  49. Re:What the hell? Crazy French! by iYk6 · · Score: 1

    It's like somebody else getting in an accident on the highway due to a manufacturing error, and you get to sue the manufacturer for negligence.

    It might not be a great analogy, but at least it involves cars.

  50. Re:What the hell? Crazy French! by mrslacker · · Score: 1

    English muffins are readily available in the UK and other Western countries.

    In the same theme, "Danish pastries" (Wienerbrød) and "Brazil nuts". (castanhas-do-Pará) And to extend it
    further, the shower water heating unit in my UK bathroom had a model name of "California", even though
    I've never seen such a thing in the US.

    Never mind "Double-dutch", or indeed "French", when talking about swearing.

  51. Re:What the hell? Crazy French! by Nursie · · Score: 1

    Are you english?

    Because we just call them muffins over here. Very tasty, not too popular these days though. We also call the US style muffins (cakey things) muffins, just so we can keep things clear.

  52. Mixed Feelings. by jellomizer · · Score: 1

    While it is good to see that the GPL has enough mussel to prevent abuse. However it will also make people feel worried about using GPL software, and possibly being suied from honest mistakes. If you are non-Open Source zealot and doesn't read the GPL like the bible. It is a lot of stuff to take in and understand. And unless you want to pay a lot of money for lawers you may be better off purchasing software and creating closed source apps. As you are more protected.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Mixed Feelings. by ratboy666 · · Score: 2, Insightful

      Have you actually READ the EULA for Microsoft products? Protected? From what?

      Or, pick another EULA for a closed source product. Let use Adobe, shall we?

      "Stock Files may not be used in the production of libelous, defamatory, fraudulent, lewd, obscene or pornographic material..."

      WTF does the actually mean? Isn't it completely dependent on the actual jurisdiction?

      The GPL is simple. You DO NOT HAVE TO AGREE TO IT. You may use the software anyway. The ONLY time it comes into play is if you decide to distribute the software. Which is something you CANNOT do under these "closed source licenses" or under Copyright.

      Just follow Copyright, and the GPL doesn't come into play at all! The GPL is a grant of additional rights, beyond Copyright. Do you want to use "Stock Files" to produce a picture of a woman showing her face (considered obscene in parts of the World)? Go ahead -- you won't need a lawyer. No usage constraints are imposed. No auditing constraints are imposed (you can tell the BSA to pound sand).

      In other words, as a user of software, the GPL is completely reasonable -- use it for anything you want, on as many machines as you want, with no further issues. If you want to use GPL software in your own projects, go ahead, there are no further issues. If you want to give the software to other people, go ahead -- just point them to the place you got it from (or, if you are "sophisticated", give them the source).

      That's it.

      Anything else only kicks in if you want to distribute, or use GPL software in your own projects that you will distribute. But then, you are at the level of developer or systems integrator; not so much an "end user" anymore. In this position it would be sensible to actually READ the EULAs and GPL!

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    2. Re:Mixed Feelings. by PeterBrett · · Score: 4, Insightful

      However it will also make people feel worried about using GPL software, and possibly being suied from honest mistakes.

      Let me describe the typical GPL "enforcement" process (well documented: c.f. Linksys, BusyBox, lots of other examples):

      1. User: "Oooh, your product which I just bought uses some GPL software. Can I get the source code, please?"
      2. (Three months later) "You haven't replied to me... please can I get the source code?"
      3. (Another month passes) "You have read the license, right? It says you have to give me the source code!"
      4. (Another month passes) "(To developer) Hey, these guys are using your software but won't pass on the source code."
      5. Developer: "Oi, you're using my software, and this dude says you won't give him the source code. What gives?"
      6. (Another three months pass) "Look here, you comply with the terms of the license, or I'll send you a nasty letter."
      7. (Another month passes) "Here is a nasty letter, detailing what you're doing wrong and how to fix it!"
      8. (Another month passes) "This is your last chance, we mean it!"
      9. (Another month passes) "See you in court, assholes!"

      The aim of the GPL enforcement process isn't to slap the violators down, it's to encourage them to come into compliance. Going to court is a last resort, if every other measure fails. If it's just that you've made an honest mistake, the people who are complaining will be very happy to give you the help you need to fix the problem, and to direct you to experienced sources of reliable legal advice on GPL compliance.

      If you say, "People won't use GPL software in their products because they're afraid of the legal ramifications," you are doing nothing but spreading FUD.

    3. Re:Mixed Feelings. by petrus4 · · Score: 1

      The GPL is simple. You DO NOT HAVE TO AGREE TO IT.

      This is true in theory, yes. However, part of the reason why the goal with
      the GNU project was to create a monoculture, was in order to also create leverage with which to bludgeon people into accepting the GPL.

      I know, I know; I'll probably get the usual FSF drone response that it still
      is optional. However, the truth of the matter is that the FSF want a scenario
      where ultimately, if people don't accept the GPL, their only other "option,"
      is not to use a computer at all.

      Non-copyleft licenses need no "enforcement." Genuine freedom, and not cultic
      distortions of the word, is not something that needs to be "enforced."
      Anything which requires enforcement is truthfully the direct opposite of real
      freedom, by definition.

      The solution is simple; we need to abandon the GPL.

    4. Re:Mixed Feelings. by sumdumass · · Score: 1

      The so called fud is a legitimate concern to some degree. The problem is that more then one zealot has loudly claimed that accidental use means all your proprietary code is now GPLed despite it never being intended for that.

      Scenario, Code monkey is stressed and short for time, looks on line for help finding something to get some functioning moving faster and finds a piece of GPLed code that does exactly what he wants. He looks it over and finds it's good code and sees the words free software around it and incorporates it into his project. Two years and several revisions later, someone using the software starts poking around (presumably to fix a problem they have) and discovers the GPLed code is there. He then alerts others and they start claiming that because of the derivative language in the GPL, all of the code is open source now. Some of these others could be proprietary plants with the intention of spreading FUD either against the company or the idea of free software (we have seen both).

      The problem is that there is a legitimate copyright violation and the only known way to get the copyright license to the code is with the GPL. That creates an impression of a False Dichotomy where the options are limited. Other options include, replacing the code or contracting with the copyright holders for a specific commercial license. Now depending on the size of the legal department/budget, those options might not be easily known or apparent. Especially, if they decide to look on the inter-web for guidance. Conversely, in the US, statutory damages for unintentional copyright violations can be limited to $200 at the courts discretion but there is no guarantee of this.

      The GPL enforcement seems to be concerned with continued violations and compliance rather then past performances. However, there is no real clear indicator of this and the people making the claims are a drop in a much larger bucket claiming other things.

      As for the op's suggestion of forgoing GPLed software and sticking with proprietary apps, that carries the same risks with proven consequences too. The only difference in the scenario I described between closed and open software is how the community will generally react. The bottom line is no matter which license or type of software they intend to use, they need to understand the licensing requirements involved with doing so if they intend to distribute it.

    5. Re:Mixed Feelings. by dlapine · · Score: 1

      Wow. Can I have some of whatever it is that you're smoking?

      So do you put on your telepathic helmet in order to discern what it is that FSF really wants? Or do they you write secret emails, boasting about their plan to conquer the world? Perhaps they just beam this information directly to your brain.

      There's no secret agenda here. The developer writes something and copyrights it, just like everybody else. For whatever reason, the developer then says, "Here, go ahead and use this. Do what whatever you want with as long as you respect my copyright. Here's a copy of the source code as a bonus, so you can see exactly how I did it. You know what? I'm feeling so generous that you can even have a copyright exemption in order to distribute this wonderful code as you see fit. One caveat though. Since I gave you the ability to see how its done with the source code, you need to give others that same ability when you distribute my work. If that's too much to ask, then just don't hand it out."

      I do admit that I like your unstated base assumption- that only GPL'd software is worth having, and that by not having access to GPL, no computer would be worth anything. Let me take a moment and savor the thought of a world were anything other than GPL protected software was simply a joke... Ahhh. refreshing. Strangely though, I can't anyone thinking that's the way world is now, nor do see anyone claiming it should be that way.

      As for defending freedom, I do believe no one has ever claimed that "Liberty is free", at least, not while sober. In fact, I can easily find many claims to the contrary. Here, try these guys Freedom Monkeys, they have a bunch of quotes. I suspect that those principles apply just as strongly to software liberty as they do for personal liberty. If you want your software to be freely available and usable, then it wouldn't make sense to hand it over to those who will just take it and hide it away. The GPL prevents this. Your way doesn't. Since your goals aren't aligned with those who choose the GPL, then you can simply not use the GPL.

      How did you put it?

      The solution is simple; we need to abandon the GPL.

      Here, let's fix that.

      The solution is simple; I need to abandon the GPL.

      See? So much better for all of us.

      --
      The Internet has no garbage collection
    6. Re:Mixed Feelings. by ratboy666 · · Score: 1

      The GPL is a license that grants additional rights beyond Copyright.

      And that's all it is. How do you infer intent of the FSF from that? (Whatever that intent is; you may be right about the intent, but it actually doesn't matter).

      The only thing that matters is the GPL itself here. Which allows EXACTLY for the cases in my post.

      Does "freedom" require enforcement? In your words, the enforcement itself is against freedom. But, if I write a program, or a book, and it is NOT a "work for hire", I have the Copyright. The copyright can be enforced.

      Interestingly, it doesn't matter if I don't bother to say "Copyright" in the work:

      "Copyright applies to all original:

              * literary or textual works: books, pamphlets, poems, computer programs
              * dramatic works: films, videos, plays, screenplays and scripts
              * musical works: compositions consisting of both words and music, or music only (lyrics without music are considered literary works)
              * artistic works: paintings, drawings, maps, photographs, and sculptures
              * architectural works

      Copyright also applies to three other kinds of subject matter: performer's performances (section 15); broadcast communication signals (section 21); and sound recordings such as records, cassettes and CDs (section 18).

      Protection under copyright laws is automatic in Canada: as soon as an original work has been written down, recorded or entered as a computer file, it is immediately copyright-protected." (http://www.media-awareness.ca/english/resources/legislation/canadian_law/federal/copyright_act/cdn_copyright_ov.cfm)

      Which means I can put source code on the Web, and can sue you for copyright infringement if you redistribute that code. Just that simple.

      I would need to EXPLICITLY change the terms to allow you to redistribute the code. GPL is one possibility. Public Domain is another (and I have used Public Domain more often that GPL).

      Simply abandoning the GPL? If the choice is GPL or nothing at all, the GPL is "more free" (based on automatic Copyright grants). Possibly you want everything to be Public Domain. Which means that anyone can do anything (including ignoring authorship).

      You prefer one of the BSD licenses, perhaps? Please enlighten me on what you propose to replace the GPL.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    7. Re:Mixed Feelings. by PeterBrett · · Score: 1

      Scenario, Code monkey is stressed and short for time...

      Poor management practices and business methods get the results they deserve. News at 11!

    8. Re:Mixed Feelings. by jellomizer · · Score: 1

      So you want your boss to double check everything you do? No You want a degree of professional trust.

      No deadlines and giving developers free will create a product that will never be finished.

      Good management bad management people will get stressed and will make mistakes. There are some libraries that are GNU are very complete and could take weeks/months/years to build from scratch. Commercial versions of these libraries can be thousands of dollars. Your business model doesn't work well with the GNU, where support/distribution/consulting services wouldn't pay the bills. So you have the following options...

      1. Open Source your software and loose money
      2. Purchase the expensive libraries and integrate them. Now approval may not get past the bean counters, or the fact it is a lot of work that code monkeys hate trying to justify paying a lot of money for a product.
      3. Put the open source in and hope know one will find out.
      4. Make your own library taking a lot of man hours, and possibly pissing off the customer who is waiting for the product.
      5. Contact the maker of the library and beg for a license that will work for you. (which may be difficult as if they made a library GPL vs. LGPL means they are probably very anal on the GPL)
      6. Make as much money as possible if they ask for the source code you fax it to them, with the code officiated.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    9. Re:Mixed Feelings. by PeterBrett · · Score: 1

      So you want your boss to double check everything you do? No You want a degree of professional trust.

      You're putting words into my mouth: I never said anything of the sort.

      Good management bad management people will get stressed and will make mistakes. There are some libraries that are GNU are very complete and could take weeks/months/years to build from scratch.

      So you feel that you should be entitled to just take them and use them however you want to with no obligations attached? If you want to use the code, comply with the license; if you don't want to comply with the license, find an alternative. It's very simple. Microsoft Windows "could take weeks/months/years to build from scratch", but it's pretty clear that, if you want to use it, you need to pay for it. In the case of GNU libraries, you pay for the software by following the simple rules associated with it; in the case of MS Windows, you pay by writing a cheque.

      Commercial versions of these libraries can be thousands of dollars. Your business model doesn't work well with the GNU, where support/distribution/consulting services wouldn't pay the bills. So you have the following options...

      Oh, really! So I suppose I'm imagining the fact that Red Hat is in the S&P 500 and seems to have no problem paying the bills?

      1. Open Source your software and loose money

      If you think that Open Source = losing money, you must have been living in a hole for the last decade.

      2. Purchase the expensive libraries and integrate them. Now approval may not get past the bean counters, or the fact it is a lot of work that code monkeys hate trying to justify paying a lot of money for a product.

      "Bawwwwwwww! Why won't all these programmers do my work for me for free!"

      3. Put the open source in and hope know one will find out.

      But as you've seen, they will.

      4. Make your own library taking a lot of man hours, and possibly pissing off the customer who is waiting for the product.

      Maybe you should have negotiated a realistic delivery timescale? It's not GNU's fault that your sales team sucks.

      5. Contact the maker of the library and beg for a license that will work for you. (which may be difficult as if they made a library GPL vs. LGPL means they are probably very anal on the GPL)

      "Bawwwwwwww! You're not allowed to have principles if they conflict with my business model!"

      6. Make as much money as possible if they ask for the source code you fax it to them, with the code officiated.

      I don't know what you mean by "with the code officiated", but I will point you to the part of the GPL which says, "The 'source code' for a work means the preferred form of the work for making modifications to it." I think most developers would be able to make a convincing argument that a fax is not "the preferred form" for hacking on code.

      So far, you've demonstrated that your company is too incompetent to negotiate contracts with clients at an achievable price or with a reasonable delivery timescale. You also put undue pressure on your programmers and refuse to give them the support they need to get their work done. You are so blinkered and focussed on what has worked in the past that you are unable to see beyond your failing business model to any other way of making money out of software. Finally, you think you should be able to compensate for these failings by stealing other people's hard work.

      Care to dig any deeper?

    10. Re:Mixed Feelings. by ratboy666 · · Score: 1

      On a re-read I think I understand the disconnect.

      There is no "theory". You can decline the GPL, and still use the software.

      Do you get that? But, if you decline the GPL, Copyright applies. (Just the normal thing). Same as if you had purchased, or had been lent a book (for example).

      You can still do whatever you want with the software, but would have no right to distribute that software. You know, just Copyright as usual.

      This is what I mean by not agreeing to the GPL. It doesn't affect you as a user of the software in the slightest. In fact, since it is only under Copyright, and not licensed, it is still more free and less risky than the licensed software from most vendors. Where the EULA applies.

      Which is where your risk analysis falls apart. Simply use GPL software, and decline the GPL. This is the least risky path for a user.

      For a developer the licensing should be careful examined. You would be dumb not to.

      This may be a surprising result. It is to many; some software even has a splash screen put in by some zealot that says, in effect, "to use this software, you must agree to the GPL". This is incorrect. To quote the GPL

      "Activities other than copying, distribution and modification are not
      covered by this License; they are outside its scope. The act of
      running the Program is not restricted..."

      Read this carefully; this is what lets you use the program without agreeing to the GPL. You should be able to decline that aforementioned splash screen, and still use the program.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    11. Re:Mixed Feelings. by petrus4 · · Score: 1

      Read this carefully; this is what lets you use the program without agreeing to the GPL. You should be able to decline that aforementioned splash screen, and still use the program.

      This is fine, then. As far as I know, shell scripts aren't considered object code, and hence aren't subject to copyleft; and scripting is the only kind of programming I do. I've used gawk, but that doesn't generate object code either.

      My shell scripts are always BSD licensed.

    12. Re:Mixed Feelings. by Kjella · · Score: 1

      The problem is that more then one zealot has loudly claimed that accidental use means all your proprietary code is now GPLed despite it never being intended for that.

      It's not even possible to get such a verdict. But as a settlement offer you can make any offer you want, and "release your complete source" is a valid and often used offer. But if you do want to take it to court, the worst you'll get is 5 years in federal prison and fines of up to 250,000$. Hey, it's what the FBI warning on a 5$ DVD says...

      --
      Live today, because you never know what tomorrow brings
    13. Re:Mixed Feelings. by sumdumass · · Score: 1

      For the 5 years in federal prison, there needs to be a few qualifiers like reasonably knowing of the violation at the time of infringement and commercial or private gain directly because of the unauthorized distribution. There is also a special condition for movies but it wouldn't apply to software. It's a fine line that may or may not apply depending on the circumstances.

      Anyways, I agree with what you stated. However, the point I was making is that some advocates pretend that losing the code is the only option. What is comes down to is FUD created by GPL enthusiast furthered by outside entities wanting to increase the uncertainty of using products other then theirs. Do you remember the entire line of FUD over word processor documents using GLPed fonts needing to be open source because part of the font was embedded in the document making it a derivative work?

    14. Re:Mixed Feelings. by Anonymous Coward · · Score: 0

      Posting to cancel a mod; please ignore.

  53. Re:What the hell? Crazy French! by Eunuchswear · · Score: 1

    Well, if you read the VNC source EDU4 were using you wont see any copyright notices - they took them out.

    AFPA could sue EDU4 because they bought (a license to) a software system from EDU4, and EDU4 provided a forgery - a GPL'd work obfuscated to hide the fact that it was GPL'd.

    (EDU4 also included a secret back-door password in the version of VNC they provided, which is presumably why they didn't want to provide the source!)

    --
    Watch this Heartland Institute video
  54. what the court ruling actually said by viralMeme · · Score: 1

    "I read the court ruling .. What I understand of the ruling (I'm french, but I'm no lawyer)"

    Do you mind producing a translation of the ruling so as the rest of us can confirm your understanding. What does this bit say:

    - cute -
    Considerant que la societe EDU 4 replique:

    - qu'elle n'a jamais dissimule l'utilisation d'un logiciel libre VCN, sous license GNU GPL.

    - qu'elle n'a jamais souscrit l'obligation d'etre proprietaire des logiciels mis en oeuvre et n'a jamais pretendu etre l'auteur du logiciel GNU-GPL

    - qu'elle disposiat la possibilite de modifier corriger et adapter le logiciel libre sous license GNU GPL, de l'integrer dans sa solution informatique et de distribuer le logiciel integrant les modifications qu'elle a apportees ..
    - paste -

    'In a landmark ruling that will set legal precedent, the Paris Court of Appeals decided last week that the company Edu4 violated the terms of the GNU General Public License (GPL)'

    1. Re:what the court ruling actually said by Taevin · · Score: 1
      It reads (my notes in italics):

      Considering that the company Edu4 replies
      • that it never hid the use of the free software VNC, licensed under the GNU GPL,
      • that it never supported the obligation to be the owner of the software used (that's a pretty literal translation; I'd likely have to read the whole thing to have enough context for a translation that makes more sense) and never pretended to be the author of the GPL software,
      • that it had the option to modify, correct, and adapt the free software under the GPL, to integrate it into its IT solution, and to distribute the software with the changes it made,
      • that it carried out a standard delivery on April 5, 2002, as held by expert Wallon,
      • that this expert found that the software as delivered is composed of three modules: the student module, the tutor module, and the VNC module and specified that the VNC included, version 3.3r7, is distributed under the GNU GPL license,
      • that this expert has further indicated that the modifications made by Edu4 regarding the copyright notices were not intended to conceal the origin of the third program (VNC), and that it's at the moment of final receipt, at the time of the effective transfer of rights to the user, that it should respect the formal obligations regarding licensing, but before that date, the programs could be modified or adapted and not be in their final form (i.e., Edu4 is saying "oh no, no. We're going to put the notices back when we ship, it just helped our developers to remove the notices." lol?),
      • that the AFPA knew about the use of VNC and that it had verified the fitness of its use in full knowledge of the situation, although it reserved its rights,
      • that as of January 15, 2002, it had informed the AFPA that it was going to put the copyrights in place at the time of distribution when the definitive version of the GPL software had been integrated into its IT solution,

      Without reading the whole ruling, my guess is that the above is a summary of Edu4's appeal after the original ruling.

      Basically, I think the ruling comes down to: Edu4 used and modified software licensed under the GPL which extends rights to recipients of the distributed modified software (namely, the right to the source code). Edu4 refused to provide the source code upon request, violating the license agreement and the rights granted to recipients of the software by the original author. What I can't be sure of is if this is directly a result of the GPL which grants rights to recipients of GPL software, or an artifact of the French legal system which has different thresholds for legal standing than perhaps we are used to.

  55. honest non-Open Source zealots by viralMeme · · Score: 1

    "While it is good to see that the GPL has enough mussel to prevent abuse. However it will also make people feel worried about using GPL software, and possibly being suied from honest mistakes"

    Where have people ever been sued for honest mistakes? Why would a case of people wilfully removing the copyright and not providing the source code be a source of worry. What's complicated about: if you distribute GPL progs, you must also include the source, and don't erase other peoples copyright notices. I can understand that and I'm not even a lawyer.

  56. Re:What the hell? Crazy French! by jc42 · · Score: 1

    So do English cows also leave behind muffins? Over here in the Colonies, they're often called meadow muffins or cow pies. It could be interesting to know what the actual English call them.

    I've always thought that this particular metaphor was a bit weak, since the American "muffin" is a rather small cake. It would make more sense to refer to horse droppings as muffins. But there's often no accounting for slang.

    --
    Those who do study history are doomed to stand helplessly by while everyone else repeats it.
  57. Re:What the hell? Crazy French! by s73v3r · · Score: 1

    That doesn't matter. They were given binaries of a modified GPL product. Under the terms of the GPL, they are entitled to the source.

  58. Re:What the hell? Crazy French! by silanea · · Score: 1

    IANAL, but if I understand the issue correctly, AFPA sued not for copyright violation but for the rights they as the users would have been granted by the GPL which Edu4 chose to deny them.

    Had they gotten VNC directly from the official developers, AFPA would have received certain rights, amongst them access to the source code.

    Instead they got a derivative work of VNC from Edu4, but Edu4 did not give them those same rights as required by the GPL. And that is what they went to court for. This is not really about copyright law but about contract law, I would say.

    --
    Rudolf Hess edited Mein Kampf. He was the very first grammar nazi.
  59. Re:What the hell? Crazy French! by sumdumass · · Score: 1

    Nothing in the information I posted or linked to says anything about concealing the terms of a contract from an intended beneficiary makes the intended beneficiary incidental. If you have other information please post it.

    You do not have to link to anything, I said it because it was absent from your post giving the wrong impression. You cannot be an intended beneficiary of something you know nothing about unless the person making you so steps forward to declare that. When the Edu4 group removed the GPL and copyright information, they also removed you as the intended beneficiary for all intends and purposes. They did this in violation of the law, the contract given to them, and copyright, but it's the effect it would have.

    The problem is the acceptance of the contract. I can simply violate copyright law (as was the case of the Edu4 company) and distribute the the software without conveying the GPL or becoming a party to it. Now, in order for you to be a beneficiary of a contract, you have to prove that the contract exists between two or more parties; there is "clear" or "manifest" intent of A and B that the contract primarily and directly benefit the third party (or class of persons to which that party belongs); breach of the contract by either A or B; and, damages to the third-party resulting from the breach.

    Now the problem that makes this particular set of circumstances incidental instead of intended is the wording of the GPL itself. Under section 2 of the GPLv3, it specifically states

    You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

    This one part overrides the intentions of the other sections as far as distribution is concerned within this scope. What Edu4 did was as part of installing the computer hardware, placed the software on site for the sole purpose of them running it remotely for setup and maintenance of the hardware in which they had a contract for. Their use fits under this term in the GPLv3 as the facts are that the sole purpose was to provide you with facilities for running those works (for their installation and maintenance contracts) and, on their behalf, under their direction and control, on terms that prohibit them from making any copies of the copyrighted material outside their relationship with you (which is what the password protection scheme was supposed to accomplish). So while the company benefited in the performance of the install and maintenance of the software, it was incidental to the fulfillment or performance of a second contract involved and not the GPL.

    Auto analogy:
    Ford sells off-lease cars to independent dealer "Car Emporium", with the contract of sale stating that "Car Emporium" will provide complimentary maintenance for these cars to whoever they resell it to for one year after that sale. "Car Emporium" doesn't do so and conceals the existence of that contract from the buyers. The buyers somehow find out. They _DO_ have standing to sue "Car Emporium", as they were an intended beneficiary of the contract.

    This is apples and oranges compared to the claims in the french case. A more apt approach if you insist on using this would be Car Emporium resells the cars to individual franchise dealerships and only offers the maintenance to those dealerships while the independent dealerships own or control the cars. The purchaser, Bob's Car Emporium dealership which is a separate legal entity from Car Emporium, would be entitled to the

  60. Re:What the hell? Crazy French! by jc42 · · Score: 1

    I can't figure out if this case is over contract law ...

    Right now, there's a message directly above from "russotto", giving an auto analogy that might explain it. In general, if A hands X to B with instructions that X is to be delivered to C, and B keeps X rather than delivering it, A and C both have grounds to sue B. The exact wording of the charges will vary depending on the nature of the deliverable product X and the relationships between A, B and C. But B can't just say "I'm not involved in the relationship between A and C, and keep X for personal use.

    --
    Those who do study history are doomed to stand helplessly by while everyone else repeats it.
  61. GPL was created to overcome the problems of PD. by Ungrounded+Lightning · · Score: 1

    Anyone releasing code to the masses should make it public domain to remove any legal controversies that may arise over it.

    GPL was created specifically to overcome the problems of public domain release.

    If your code is public domain, somebody else can appropriate it, make a change (fix a bug, add a feature, etc.) and copyright THAT. Then everybody else, including the original author, is locked out of the derived work. You'll never be able to fix that bug, add that feature (without doing a very different version from scratch), and so on.

    GPL (and the other open source licenses) keeps the work under copyright in order to let the original authors enforce licensing terms that prohibit such shenanigans.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  62. Re:What the hell? Crazy French! by Plunky · · Score: 1

    So do English cows also leave behind muffins? Over here in the Colonies, they're often called meadow muffins or cow pies. It could be interesting to know what the actual English call them.

    Man, you americans are so prudish. We just call it cow shit**

    ** if thats what you really mean anyway. Our cows don't generally get any kind of packed lunch and can't make baked goods on their own..

  63. a different twist... by Registered+Coward+v2 · · Score: 1

    While edu4 clearly violated the GPL, what if they had contracted developer time to modified a copy of the code that was in the AFPA instead of providing (and hence distributing) a modified copy?

    In that case, no distribution would occur and there would be no license obligation to distribute; edu4 could even put in contract terms that AFP could not distribute any of the code written by edu4; eliminating any need to distribute the source.

    --
    I'm a consultant - I convert gibberish into cash-flow.
  64. Re:What the hell? Crazy French! by mea37 · · Score: 1

    "I believe that law should be respected. full stop."

    Civil law is not intended to be a rulebook for society. That's what criminal law is for.

    "My interest as a citizen of a country is that laws are respected"

    Hmm... ok, well the law does not respect your claim that you have an interest in seeing civil law used to resolve disputes of which you are not a part. Do you respect the law in that regard, or only the laws you agree with?

    "I believe US laws allow a lawyer to sue in the name of someone that may not agree with the lawsuit"

    I suggest you research that belief more fully.

    "I think it is linked with class actions"

    In some cases, lawyers can try to gain class-action status for a collection of existing suits, and if they succeed the class will likely cover plaintifs who weren't in the original suits. However, each individaul still has the right to exclude himself from being a plaintif in the suit.

    This is a matter of administrative expediency and is actually a compromise against how the law "ought to" operate; and even so, a plaintif with standing had to be involved to start; and even so, if you don't want to be part of the suit you don't have to.

    In any case, class action suits as implemented in the American law system are anything but an example of how a sane system might work. The only party that benefits from most class action suits is the lawyer; the plaintifs who don't opt out typically get $10 coupons for the defendant's product or service.

  65. Re:What the hell? Crazy French! by Dog-Cow · · Score: 1

    And any marginally intelligent person would understand why AFPA has standing.

  66. All we are missing now.... by dwiget001 · · Score: 1

    ... some crazed babbling about how the decision is wrong, from the GPL's buddy and pal, Alex Terekhov, SUPAH 'TARD!

  67. Re:What the hell? Crazy French! by Dog-Cow · · Score: 1

    The GPL stipulates that receivers of binaries compiled from GPL'd code must be able to receive the code from the distributor. This means that Edu4 owes the source to AFPA when they deliver the binaries. AFPA did not receive the source, so they sued for it.

    If you pay for a car and it's not delivered in a reasonable time, wouldn't you sue?

    You are an idiot of the first order, though, so I suspect that you would not sue. Nor will you understand any of the answers you've received.

  68. Re:What the hell? Crazy French! by sjames · · Score: 1

    Thanks, that's interesting reading. I'm still puzzled as to what kind of wacky statue gives AFPA standing to receive relief for breach of someone else's rights. That's like... well, there is no appropriate analogy. It's exactly like receiving relief for breach of someone else's rights. The mind boggles as to the size of the can of legal worms that opens up in France.

    Not sure, but it probably honors Jerry Lewis or Charlie Chaplin.

  69. Re:What the hell? Crazy French! by pavon · · Score: 1

    And if it were a criminal offense, the problem with allowing anyone to sue is that you run into double jeopardy issues. Assume I broke a law, and I know that someone may sue me to enforce the law, instead I get a puppet organization to sue me first, do a poor job and intentionally loose the case. Alternately, a well-intentioned, but incompetent activist group could arrive at the same result inadvertently. Either way I am now off scot-free, assuming you don't allow double jeopardy.

    On the other hand assume that you do allow double jeopardy, then a well motivated group of people could then continue to bring the same case against me over and over again though different puppet organizations, even if I was innocent. Not to mention that it would require a constitutional amendment to allow this.

    I've thought about this quite a bit with regard to corrupt politicians whose district attorney will not bring a case against them. The only recourse in those situations is to hope they run afoul of laws in a higher jurisdiction (state or federal), who don't have problems charging them with a crime. This situation bothers me enough that I do think it would be worthwhile creating some additional method of bringing charges against politicians, but it would have to be devised carefully for it to work.

  70. Re:What the hell? Crazy French! by godrik · · Score: 1

    Hmm... ok, well the law does not respect your claim that you have an interest in seeing civil law used to resolve disputes of which you are not a part. Do you respect the law in that regard, or only the laws you agree with?

    US laws seem to be like this. I do my best to respect the law as I understand it. The US legal system not allowing me to complain for an unlawful event is an other matter. And I respect it as it is. It does not means I do want it to change. (Well, I do not care that much about US laws)

    You are interested in non-criminal law being respected. You do not want everybody to pass when traffic lights are red. It is not criminal laws but you still want it to be enforced.

    In any case, class action suits as implemented in the American law system are anything but an example of how a sane system might work. The only party that benefits from most class action suits is the lawyer; the plaintifs who don't opt out typically get $10 coupons for the defendant's product or service.

    I think it is all about incentive. No one is going to sue for 10 bucks but a lawyer will sue for million he will get. If I was a company perhaps I will think about it before trying something illegal no individual will complain about.

    I do not read US newspapers enough to see how it applies in practice but it seems to have nice properties.

  71. Re:What the hell? Crazy French! by WaroDaBeast · · Score: 1

    Okay, we are returning "Freedom Fries" back to their original name "French Fries". Happy now?

    Actually, some people claim they're Belgian. Others even think the first people who fried potatoes were the Spaniards. http://en.wikipedia.org/wiki/French_fries#Culinary_origin

    --
    "The body may heal, but the mind is not always so resilient." -- Deus Ex: Human Revolution
  72. Re:What the hell? Crazy French! by mea37 · · Score: 1

    "You are interested in non-criminal law being respected. You do not want everybody to pass when traffic lights are red. It is not criminal laws but you still want it to be enforced."

    I notice you went out of your way to say "non-criminal" rather than claiming that traffic violations are civil, so I assume you already know that you're muddying the waters.

    Traffic violations are prosecuted by the government, not raised in private law suits. In court, nobody is named as a plaintif but rather the government is the prosecutor. It is true that minor tickets ("infractions") are often referred to as "not a crime"... but then more serious offenses are classified as misdemeanors or even felonies.

    Whatever you choose to call them, traffic tickets are not civil law matters. If you apply the arguments I've made in my previous posts to traffic laws, you will find that they are much more like criminal offenses than civil offenses. I don't have the time today to do legal research and see if they're technically part of the body of criminal law, so if you like you can consider them a third category of law. This does not change the fact that the kind of law you sue over -- civil law -- does not include running a red.

    "I think it is all about incentive. No one is going to sue for 10 bucks but a lawyer will sue for million he will get. If I was a company perhaps I will think about it before trying something illegal no individual will complain about."

    If the individual damages were really only $10, that would be a good point. The reality is, most plaintifs in class-action suits never get compensation anywhere near enough to cover real damages.

    Nor do I believe that most companies are really deterred by being ordered to give out a bunch of coupons that will bring them more business from the people they wronged. By contrast, in an individual lawsuit if the judge and jury want to send a message to the defendant they can award punitive damages which really do hurt.

    Of course the court might impose injunctions on them as a result of a class-action. They could do that in an individual suit as well.

  73. Re:What the hell? Crazy French! by Rogerborg · · Score: 1
    Under the terms of the GPL, they are entitled to the source.

    So are you and I. Can we sue Edu4 as well?

    --
    If you were blocking sigs, you wouldn't have to read this.
  74. Re:What the hell? Crazy French! by Rogerborg · · Score: 1

    Then anyone who's not a complete retard should be able to explain why AFPA has standing, while sub-retards and non intelligent people like you and I don't. Want to take a stab at it?

    --
    If you were blocking sigs, you wouldn't have to read this.
  75. Re:What the hell? Crazy French! by gilgongo · · Score: 1

    Hang on just a second. Does the AFPA (the plaintiffs) own the copyright on the GPLd source?

    This is the thing that many, many people do not remember when debating issues of intellectual property: contract trumps copyright. Plain and simple. It may not be right, but it's the law in just about every country I can think of.

    --
    "And the meaning of words; when they cease to function; when will it start worrying you?"
  76. Re:What the hell? Crazy French! by godrik · · Score: 1

    I notice you went out of your way to say "non-criminal" rather than claiming that traffic violations are civil, so I assume you already know that you're muddying the waters.

    In fact I just didn't knew. I thought it might be different, something as a part of it is federal.

    This does not change the fact that the kind of law you sue over -- civil law -- does not include running a red.

    I agree it does not (neither in the US nor in France). But it could make sense.

    By contrast, in an individual lawsuit if the judge and jury want to send a message to the defendant they can award punitive damages which really do hurt.

    I agree with that. My point is that as an individual I would not sue for 10$ hoping the judge/jury will award punitive damage. Whereas if I am a lawyer my whole point will be to get punitive damage. In one case it will stay as it is in the other one someone may (or may not) do it.

    I dont like lawyer, but I like unfair companies even less. :)

    In brief, I believe that being able to sue for any illegal activities whether you are concerned or not may improve the overall good. (Being honest, it may also lead to a lot of junk and stupid trial)

  77. Re:What the hell? Crazy French! by SETIGuy · · Score: 1

    It's an idiosyncracy of French law. The plaintiff here was a customer who did, yes, successfully sue for the source code. It probably couldn't happen in the US or UK.

    They didn't sue to obtain the source code, and I think this would probably hold up in a U.S. court. AFPA were countersuing because the they were being invalidly sued for breach of contract. They contracted with EDU3 to provided them with certain software. EDU3 provided them with software that EDU3 had no license to distribute (because they were violating the terms of the GPL.) EDU3 also included a security backdoor that would allow them access AFPA's computers.

    AFPA noted that EDU3 was providing them with counterfeit software in violation of copyright law and refused to pay them. EDU3 sued AFPA for breech of contract. AFPA counter sued. In this case the appeals judge determined that the AFPA had the right to terminate the contract without payment, and that because there was no breech of contract by AFPA the counter suit was upheld. EDU3 doesn't get paid, and EDU3 must pay AFPA's legal bills.

    I would certainly hope that in the U.S. and in the U.K. that you are allowed to sue someone that provides you with counterfeit software.

  78. Re:What the hell? Crazy French! by SETIGuy · · Score: 1

    If I understand the sets of circumstances here, the Edu4 stripped the GPL and copyright notices from the product and pretended it was their own. They even pretended that they didn't distribute the product even though they left it on the computers they installed.

    If these claims are true, it would be near impossible for an end user in the US to claim to be the intended beneficiary.

    I think you might be wrong about that. Whether the GPL was available to AFPA or not, EDU4 sold AFPA a hacked copy of software that EDU4 had no license to distribute. AFPA was under no obligation to pay them for counterfeit software, so when EDU4 sued AFPA for breech of contract, that suit was without basis. Therefore, even in the US, AFPA would have had standing to counter sue to recover legal fees. I think holders of the VNC copyrights should sue as well for breech of contract. After all, a French court has already held that EDU4 was in violation.

  79. Re:What the hell? Crazy French! by ChameleonDave · · Score: 1

    Under the terms of the GPL, they are entitled to the source.

    So are you and I. Can we sue [AFPA] as well?

    Maybe. There are two ways to be compliant: ship the code with the product, or make it available to all. The latters applies to you and me; both the latter and the former apply to Edu4. They therefore have a much better case to make.

    It's best to leave these lawsuits to the recipient or the copyright holder, but it is true that everyone in the world has the right that AFPA trampled on. Perhaps a class-action suit would be appropriate.

  80. Re:What the hell? Crazy French! by robbak · · Score: 1

    If they sold you a copy of their altered VNC without providing source, then, yes. If they didn't, then no.

    A big part of the comments above hashed this out. A company distributing GPL software has (now) three options: 1, Provide the source with the binaries (say, on the same CD), 2, Include a notice that offers anyone anywhere the opportunity to get the source from them at a nominal cost, or 3. Post it on a server somewhere and include the URL with the documentation (GPLv3 only).

    Possibly, as they messed up and didn't do 1, then they could argued that they are required to 2 or 3, but that is stretching things.

    This case, in French law at least, has provided a precedent for forcing a company missusing GPL code to provide you with the source, and a GPL licence for it. Could be a useful precedent!

    --
    Prediction for end of Universe #42: Fencepost error in Quantum_bogosort.cpp
  81. Re:What the hell? Crazy French! by sumdumass · · Score: 1

    Slow down a minute.

    I'm not talking about contractual obligations between two separate parties. I'm talking about the notion presented in the article and summery that an end user can sue as a beneficiary of a contract between the copyright holders of VNC and Edu4 under the circumstances present in this situation. In US and UK courts, the beneficiary would have to prove that a contract existed, that they were the/an intended beneficiary and not an incidental beneficiary of the contract, A breach of the contract happened and harm was a result of it.

    Now, an easy out in this would be is if Edu4 claimed that it installed the particular VNC software to provide you with facilities for running those software, exclusively on their behalf, under their direction and control, on terms that prohibit them from making any copies of their copyrighted material outside their relationship with them. This is covered by section 2 of the GPL and would prevent both a contract between two separate parties as well as AFPA being an intended beneficiary. In other words, they wouldn't have a case because the VPN software was for the sole purpose of Edu4 setting up and supporting the hardware.

    There would still be copyright violations because they removed the copyright and the GPL notice from the unmodified or non-derivative work. But the source distribution could have been satisfied with just a link to the VNC website. The modification wouldn't have needed to be distributed. What I understand happened in this case, when AFPA withheld payment, they also canceled the contract and because the VNC software remained on site (in the US or UK, after the contract was in dispute, there would be no legal right for Edu4 to enter their systems and remove it), it constituted a part of the sale. That wouldn't necessarily be the case in US court. If I as a landlord lock you out of your apartment and place your items in storage for non-payment of rent or something, they do not just become my property. This is despite it being illegal for me to do so in the first place. The same would go for code, you can't be tricked or manipulated to give up or license your copyrighted works which is what this essentially amounted to.

    Now something that throws a wrench in the entire ordeal is that the violation happened in 2000. The GPLv3 wasn't official then and it the exception wouldn't have been in place at the time of the violation. However, it would be now if someone attempted to do the same under the same circumstances with GPLv3 licensed software.

  82. Re:What the hell? Crazy French! by qc_dk · · Score: 1

    My bessie is ever so happy with her spiderman lunchbox. She did whinge a bit in the beginning. Something about hooves and oposable digits, but I never listen to the cow.

  83. French punning by dugeen · · Score: 1

    Edu4 = edu-quatre = educateur

  84. Re:What the hell? Crazy French! by Nursie · · Score: 1

    Do ignore the other reply you got from that vulgar poster.

    It's a cow pat.

  85. Re:What the hell? Crazy French! by Anonymous Coward · · Score: 0

    As long as you keep in mind that fries aren't French either, but Belgian...
    Who ever thought of the term 'French fries' anyway?

  86. Re:What the hell? Crazy French! by rohan972 · · Score: 1

    When the Edu4 group removed the GPL and copyright information, they also removed you as the intended beneficiary for all intends and purposes. They did this in violation of the law, the contract given to them, and copyright, but it's the effect it would have.

    You evidently understand the justification for the lawsuit better than you want to let on.

  87. Re:What the hell? Crazy French! by sumdumass · · Score: 1

    You evidently understand the justification for the lawsuit better than you want to let on.

    And you obviously do not. Or at least your refusing to see the point being made.

    I'm not saying a law wasn't broken, I'm not saying that they didn't have a case in a french court. I am saying that in a US or UK court, if they removed the contract between VNC and Edu4, then any third party could not know they were an intended third party beneficiary and wouldn't have a case. Only the copyright owner could bring suit because they would be the only party that could prove a contract existed between the two parties (GPL) that intended to benefit the third party. In the US and UK, you cannot say this product is typically licenses this way so it should be here too. You have to prove that a contract between VNC and Edu4 existed and that you were an intended beneficiary. With the GPL and copyright removed, only the copyright holder can declare it or the contract existed unless Edu4 volunteers the information at a later date. Baring an admision from Edu4, you simply cannot prove a contract between two other parties that you were an intended beneficiary of without the copyright owners.

    What that means is, if I or you strip the GPL and copyright from a product and distribute it, the end user which is a third party will not have a legal standing for the case in the first place without the original contractors (read copyright owners). Once the copyright owners get involved for the fulfillment of their contract, the third party suit is not allowed.

    Furthermore, I'm saying that under the current GPL, Edu4 could have installed the VNC software solely for their convenience and discretion and no software transfer would have taken place (section 2 of the GPLv3). The case in question revolves around a 2000 incident so it would be governed under the GPLv2's statements which doesn't have provisions for running software remotely. However, I'm not sure that wouldn't have changed in US court seeing how the VNC GPL notice claims or later versions. So it would appear that the third party claim would/could have disappeared under section 2's terminology of the GPLv3 when it came into effect.

  88. Re:What the hell? Crazy French! by dwater · · Score: 1

    Well, I never heard of them...but it seems I'm in the minority...perhaps I had one when I was young and never liked them, so I never had them again...

    --
    Max.
  89. Re:What the hell? Crazy French! by dwater · · Score: 1

    > Are you english?

    Yes. Liked in Somerset for most of my life, so perhaps they don't have them there much, or I didn't like them or something. Seems I was mistaken. Apologies to all the septics who took offence.

    --
    Max.