Slashdot Mirror


On the Ethics of a Code Split?

McWizard asks: "We've recently had a code split at a project I'm leading. (No name given, as this is a question, not an advertisement campaign). While both projects have done some major design decisions in opposing directions, we've been keeping a close eye on the changelog of the spinoff for small changes that could be used. So, whenever we've found an interesting piece of code (mostly GUI stuff, nothing longer than 20 lines of code), we transferred it to our project and gave credit to the spinoff team in the changelog. What does Slashdot say on that matter? Is this unethical or are such things fair game?" "Yesterday, I was contacted by the leader of the spinoff project who told me that he's quiet angry at us for doing that and that it's considered unethical and rude to copy code from the spinoff. As both projects are under the GPL, we have an opposing opinion on that matter and we've more than once invited him to copy code from our project. Nevertheless he's thinking about obfuscating his changelog and only open the source as packages when he's doing a release, which is, as he says, his right under the GPL."

16 of 448 comments (clear)

  1. Sounds like a... by xeon4life · · Score: 5, Funny

    Disgruntled XFree86 developer, are we?

    --
    Real programmers can write assembly code in any language. -- Larry Wall
  2. End the schism! by Anonymous Coward · · Score: 1, Funny

    The (X)Emacs split only helps the VIle!
    Kiss. Make up. In KISS makeup. Emacs akbar!

    1. Re:End the schism! by Anonymous Coward · · Score: 1, Funny

      I wish I had mod points...

      Figuring out what I'd do with them is left as an exercise for the reader.

  3. Re:SlashEthics by whoop · · Score: 2, Funny

    dang, meant to say "hate" there...

  4. Code split? by dbIII · · Score: 4, Funny
    Tell RMS you really do want to use Emacs on X-Windows, and since he's not the developer it's none of his business anyway - if he doesn't like it, he can appoint another developer, spend a year teaching him C and fork Emacs if he wants to.

    Oh, that already happened.

    If you have a good reason, just split the code - emacs survived it, XFree86 survived it.

  5. Who cares? by tomstdenis · · Score: 1, Funny

    If the other little dweeb released his code under the GPL too than I say suck it dry. Use all the work without a second thought.

    Of course if you guys share so much code why not just make a 3rd library of the shared code and be done with? E.g. take the intersection of your projects and make that a new library. That way you can focus on your particular tweaks and still be happy.

    Of course I can come up with these cool ideas because I'm a forking genious.

    Tom

    --
    Someday, I'll have a real sig.
  6. First off... by drigz · · Score: 2, Funny

    First off, I'd have a look at their code and see if they'd taken anything from me...

  7. Hmmm by Sophrosyne · · Score: 2, Funny

    ...well, at least we finally know why Longhorn was delayed.

  8. Re:SlashEthics by Anonymous Coward · · Score: 1, Funny

    aww, I thought you meant "have" in the sexual way...free as in beer often leads to free as in love!

  9. Re:And here we have ... by PHlLlPY · · Score: 4, Funny

    yeah, he has used reverse psychology on all of us to get us to go check out and play his mech board game now that we are all ready to get some practice in before the mech from alaska takes over.

  10. Re:No problem by csguy314 · · Score: 5, Funny

    Well I disagree. I think both should be doing their utmost to destroy the other project. I mean, isn't that the point of the split in the first place? Because you're absolutely right and the others are absolutely wrong... and they're assholes.
    [/sarcasm]

    --
    This is left as an exercise for the reader.
  11. idea and a limerick by TWX · · Score: 5, Funny
    I think that the grandparent was implying that if the fork maintainer doesn't like it, he's free to go and make his own product from scratch and license it however he chooses. He can't truly ignore the GPL (unless his userbase is so small that none of them care) and he can't rightfully claim the original code predating the fork as his, and since his changes are to GPLed code he has no standing as he knew the licensing conditions in the first place.

    I'd suggest replying to the guy with a limerick:
    There once was a man who did fork us,
    His etiquette complaints really torqued us.
    On Slashdot we moaned;
    posts left him quite 0wn3d,
    and now he looks like quite the dorkus...
    --
    Do not look into laser with remaining eye.
    1. Re:idea and a limerick by zsau · · Score: 2, Funny

      Replace line two with:

      His etiquette complaints they did torque us

      and you get the rhyme back.

      --
      Look out!
  12. Re:No problem by pboulang · · Score: 1, Funny

    ummmm, openbsd isn't GPL'd ;)

    --

    This comment is guaranteed*

    *not guaranteed

  13. That's strange by JumperCable · · Score: 2, Funny

    Who ever heard of a coder with anti-social qualities.

  14. Error: Too Many Agreements by rob_levine · · Score: 2, Funny

    Practically everyone seems to be agreeing here.
    Must be the Christmas spirit and goodwill.