Announcement

Collapse
No announcement yet.

FSF Wastes Away Another "High Priority" Project

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • prokoudine
    replied
    @intellivision

    LibreDWG is still GPLv3+. QCAD was relicensed under GPLv3 too, but LibreCAD hasn't been updated against it yet, and I'm not sure whether it will be due to amount of changes in both projects since the splitting. FreeCAD is currently using a proprietary lib to open DWG in 2D.

    Leave a comment:


  • intellivision
    replied
    Has there been a resolution to this situation yet or is the GPL still fragmenting these projects?

    Leave a comment:


  • intellivision
    replied
    I do hope that there will be a solution for this situation, it seems a pity that license politicisation has gotten in the way of advancing open source projects.

    Leave a comment:


  • dfx.
    replied
    oh, fuck off

    Originally posted by ворот93 View Post
    Only religious wackos are concerned by this stuff.
    uh-huh, and lawyers are priests then, right ?

    Leave a comment:


  • a user
    replied
    +1

    no really!

    Leave a comment:


  • brosis
    replied
    Originally posted by energyman View Post
    Gplv3 is less free than GPLv2. Plus overly complex. And while the v2 has been proven by courts, GPLv3 has not.

    So there are good reasons not to use GPLv3.
    Complexity synonym for Details. Details synonym for Clarity. For example, in HD you have more details and better quality as in VGA, more picture clarity.

    Moving to more Freedom means puting more Restriction on the antonym.


    GPL2 is less Free, as in "containing more ways to Restrict Freedoms".
    GPL3 is more Free as in "adding more Restrictions on removing Freedoms".
    You can also read it as: GPL3 is less Free as in "it is more restrictive to "have more Restrictions on removing Freedoms".

    But hold on, a Freedom to "add a Restriction" is NOT Freedom, but is freedom to Restrict.
    Last edited by brosis; 26 January 2013, 10:12 AM.

    Leave a comment:


  • varikonniemi
    replied
    The enthusiasm Michael has for Valve, and the hate he has for RMS almost make me feel like he is being bought by some corporate interest.

    Why is it so hard to understand that in the long term these silly licensing disputes might prevent adoption, but it also ensures that corporations cannot easily just do their R&D on the public and pick up the fruits and reap all the money like BSD license is designed to.

    Leave a comment:


  • XorEaxEax
    replied
    Originally posted by archibald View Post
    I'll admit to this point of what may be unforgivable: in my day job I write closed source code.
    Heh I'm guilty of that aswell. Well to be clear, I don't explicitly write proprietary code, I simply write code on a contract basis, I have no control of what those paying me for the code does with it.

    That doesn't prevent me from liking or contributing to open source though. Unlike RMS I don't see anything morally wrong with proprietary code, I do however see alot morally wrong with the lock-in tendencies which sadly often accompany proprietary code.

    Leave a comment:


  • thalaric
    replied
    Unlike gpl2, gpl3 was partially authored by lawyers and was subject to a very intense public vetting. There's no reason to suspect it won't stand up in court. Besides, the worst that can happen is that the prosecuting party loses their license to use the code. So yes, that argument is FUD, just like it was used against gpl2 before it went to court.

    As for freedom, yes, you are more free to open source code and then sue anyone who uses the code for patent infringement. Congrats, if that is a desirable outcome.

    Leave a comment:


  • prokoudine
    replied
    Originally posted by thalaric View Post
    Rewriting is *always* an option.
    In a perfect world where there's no pain, sorrow and tons of lousy licensed code? Sure. In the real world? Unlikely.

    Originally posted by thalaric View Post
    What they should be doing now is separating the portions out that are gpl2 only into separate files and dual license the rest to gpl 2 and 3. Only accept contributions with the dual license going forward. Deprecate the code and libraries that use gpl2.
    Again, in the real world there is nothing you can use in place of Open CASCADE, and writing a substitude is unrealistic. Would you like to prove me wrong?

    Leave a comment:

Working...
X