Slashdot Mirror


Fink Maintainer Steps Down Due To GPL Infringment

DShadow noted that the Fink maintainer Christoph Pfisterer has resigned largely because of GPL violations by openosx and macgimp, as well as macosx.forked.net. There's definitely some tension between the mac world and the Open Source and GPL worlds. Certain amounts of culture clash are inevitable, but hopefully great projects like this will continue, and commercial vendors will be able to play nice without alienating developers. The good news for Macheads is that fink will continue just fine.

260 comments

  1. Exactly. by tang · · Score: 1

    The message by Christoph Pfisterer when he resigned is something that I think anyone working on a project feels. Even for you slashdotters who don't always read the articles, read the email. Damn users who think they own you.
    I wish him luck in his future dealings:)

    1. Re:Exactly. by Zurk · · Score: 1

      yeah but most people who work on open source projects deal with it by ignoring bullshit. heck i deal with it all the time too. that doesnt mean i give up. i just deal.
      looks like this guy cracked under pressure. come on people. put your flame suppressing clothes on and wear a thick skin and then start an open source project. its not for sensitive types.
      be an asshole - youre doing something for the community for free. the community can deal with it whether it wants to or not.

    2. Re:Exactly. by Anonymous Coward · · Score: 1

      I just read through the link above and several links through it.

      It sounds like he's upset that someone used his GPL'd software and didn't credit him. I thought the GPL did not enforce visible credits. If he was that interested in getting credit, then he needed to go with another license. I admit its nice to be credited, BUT the folks doing the cd's that he's complaining about are following the rules of the game.

      Besides, it also looks like folks had only used his application to create their product. Does this mean that every time I edit something in Photoshop I am required to list that it was edited in Photoshop?

      Again, I read through these quickly and I kept seeing the main theme as what was stated above. I could be missing some of the finer details. It sucks not to be recognized for your work, but if you are only doing it for the recognition, then you are in the wrong field. Write the software because its what you want to do and give it away. Don't support it, let others do that. And most of all, don't take it so personally when others actually use something that you've created...consider it a compliment.

      Ok posting as an AC to see if anyone actually reads AC comments :-)

    3. Re:Exactly. by Tony+Hoyle · · Score: 1

      I know how he feels... users all seem to thing that they are the first people to find the 'bug' and that they are entitled to an instant fix. Over the last 3 days I've answered the same question over a dozen times to different people all who can't be bothered to read the documention *or* the list archives.

      Not to mention the 'you must have a virus because symantec antivirus is never wrong' trolls (symantec antivirus thinks that installshield is the nimda virus).

      Luckily there are enough supportive users who make it worthwhile.

    4. Re:Exactly. by Computer+suck! · · Score: 0

      > Ok posting as an AC to see if anyone actually reads AC comments :-) > he needed to go with another license
      You can't, he's porting GPL stuff, which (as it's the GPL) means he's ports are GPL'ed.

      Plus he did suffer from Stupid User Sindrom(sp). Alas that can't be helped, or even avoided. unless you kill stupid people, but then what is stupid?

      CS!

    5. Re:Exactly. by Anonymous Coward · · Score: 0

      or how about prima-donna programmers that break compatability for an app because they want to use the bleeding edge libs?

      damn the users, I want new toys!

    6. Re:Exactly. by mr100percent · · Score: 2

      It's all mac users. I'm one too, so it's not a flame. But I'm pretty sure it's mostly newbies, the mac news sites posted fink, and people who never used Xfree86 could suddenly try DLing and compiling it. There's bound to be hundreds of questions.

  2. gpl community by jrs+1 · · Score: 3, Insightful

    the gpl's there for a reason - it's a community effort and you can't take from the community and not give back. i don't think resignation's the answer - how about fixing some of the problems instead? if you exit the game, you loose by default - keep playing!

    1. Re:gpl community by Derek · · Score: 2, Insightful

      It sounds like his resignation goes a lot deeper than simple GPL violations. Sounds like "the community" he is involved with is less than appreciative. His feelings of frustration are understandable. I hope these experiences don't scar his attitude permamnently, good hackers are rare breed.

      -Derek

    2. Re:gpl community by spongman · · Score: 4, Insightful
      the main problem is that the community in general does nothing but take and in reality only a few individuals actually do the giving.

      taanstafl.

    3. Re:gpl community by erat · · Score: 3, Insightful

      I don't believe that resigning was an answer to anything. Afte reading his message on geocrawler, it seems that he's sick of a lot more than just Fink. I can't say I blame him, although reading some of his "evidence" links didn't exactly paint him in the most favorable light (even when I'm sick to death of people asking me dumb questions or making me justify every statement I make in a mail list, I try not to be as hostile as Chris was. Good grief, that guy has a MAJOR attitude problem).

      I think someone like him really should stay out of the "people" business and stick to working behind the scenes for someone else. That's an honest statement, and is not meant to be a flame. He just doesn't have what it takes to deal with the inevitable cluseless newbie. Some "have it", but some (like him) will never work out in that arena.

    4. Re:gpl community by dvdeug · · Score: 2

      There will always be more people who take than give, in any community. Many people don't have the skills to give, and some people will just mooch no matter what.

      One solution is to make sure anyone taking has already given, like I'm told some BBS's used to do.

      The solution the free software community uses is ignoring the problem and shooing away the obnoxious takers. Which really isn't as bad a solution as it sounds - the thousands of quiet takers aren't usually a problem. The people who are problems are the ones who loudly demand support and the like, and you can usually tell them to get lost and add them to your killfile.

    5. Re:gpl community by benedict · · Score: 2

      ITYM tanstaafl.

      It's always going to be the case that most of the work gets done by relatively few people, because learning enough about a particular project to be able to contribute meaningfully is difficult.

      IMHO, developers can ask their users to provide polite, relevant bug reports, and expecting any more than that is wishful thinking.

      --
      Ben "You have your mind on computers, it seems."
    6. Re:gpl community by ChuyMatt · · Score: 2, Insightful

      This is especially true with the fact that it has been a development platform for GPLd Software for all of a year, really. It makes since that the first projects to be visible will have little feedback, the community doesn't know any better. Maybe this will highlight what is really not acceptable in GPL circles. This is a process that will take a while to make the difference. Hold on. Both on the development and the user side. Learn why things are done the way they are.
      What OS X did was thrust the Mac community into opensource and not the other way around. They are a, for the most part, a bit clueless. Help them along, while arrogant, they are still ours.

    7. Re:gpl community by Anonymous Coward · · Score: 0

      Open source software with ratios..that's the best! Oh wait, 99% of the lamers out there don't know what gcc even is. =)

    8. Re:gpl community by Anonymous Coward · · Score: 0

      COMPSCI 101

      for statement this, give it an integer value of about 1000 or so; start off at one and increment by 1 each time printing the comment below to screen using your trusty dusty printf statement class.
      /*
      Yeah I can't get "blah blah" to install because of "blah blah" in "blah blah".

      .. Yes "blah blah is explained in a file called README"
      */

      I don't think he has a problem with a inevitable clueless newbie.. the problem is that amount of clueless newbies and the fact that they don't RTFM. Not only that but the majority of users are horridly ungreatful.

      If you punch the most passive person in the face a couple of times they are bound to lash out. Your statement is the type of thing that comes from the mouth of a PHB who thinks they know.. but in reality is seriously disconnected from the problem, how it is caused and how to fix it. In this case you either stop programming, or put someone between the programmer and the user.. you'd have to do that every so often as that in between would get pissed off as well.. This is why tech support people never stick around in one place too long.

      I think you should stay out of the "people" business as you would only cause both parties in a situation like this.. grief.

      good day chap

    9. Re:gpl community by maxpublic · · Score: 1

      I suppose if you define the givers as only coders. But if you define those who participate as anyone who downloads the code, discovers bugs or problems and reports back to the developers on these things then I'd say the 'givers' are quite a bit larger than this tiny subset.

      Not to mention the folks who maintain web sites, mailing lists, mirrors, etc. A large number of folks contribute according to their ability and inclination, which is precisely the idea behind open source in the first place.

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    10. Re:gpl community by bruthasj · · Score: 1

      Looks like ... a Corporate Environment.
      Sounds like ... the Gnutella network.
      Feels like ... reality.
      Smells like ... poop.
      Tastes like ... chicken.

    11. Re:gpl community by Anonymous Coward · · Score: 0

      Especially true for the Mac community (sorry, this had to be said, and it's not meant as a flame). Been there, done that. No surprise.
      chrisp's getting screwed over by other distributors without being given proper credit excuses the bitter tone of the resignation note, though.

      Michael

    12. Re:gpl community by drunkenbatman · · Score: 1

      the main problem is that the community in general does nothing but take and in reality only a few individuals actually do the giving.

      I wonder how long it will take the open source community to learn the lessons of why communism in general doesn't work?

    13. Re:gpl community by Anonymous Coward · · Score: 0

      folks.. pay attention. This isn't about getting paid for what you do. It's about doing the right thing, and hoping it will effect some changes further down the line. Writing a program for free is a voluntary service (in the charity sense). In fact, I see the GPL community as nothing short of revolutionary (ie, *beyond* communism, capitalism, etc)

      If you expect to get something for writing a GPL program, then you're not only missing the point of GPL and the Open Source movement -- you're actually degrading it into a crap and disorganised form of barter; degrading an astoundingly generous and altruistic movement and discoloring it until it becomes the crappy capitalism that it actually tries to fight.

      Take off the capitalist-colored spectacles folks, and stop trying to get rich off of our vision.

    14. Re:gpl community by dvdeug · · Score: 1

      >> the main problem is that the community in general does nothing but take and in reality only a few individuals actually do the giving.

      > I wonder how long it will take the open source community to learn the lessons of why communism in general doesn't work?

      Libraries are more like communism than open source; people are compelled to support their local libraries through taxes. Why do libraries work? Why do charities work? Maybe there's more to life then a bogus dictomony of democracy and communism.

    15. Re:gpl community by erat · · Score: 1

      It amazes me that loners and folks with few (if any) people skills insist on getting into the computer science biz, thinking that it'll guarantee that they'll not have to deal with people, and if they do, the people they'll be dealing with will be other techies. Bah! What a load... Of all the industries (other than teaching the mentally disabled) that require extensive patience and the ability to tolerate the endless, repetitive questions of people not in the know, the computer science industry takes the prize. If you can't handle it, for God's sake DON'T GET INTO IT. Turn around, find a forest ranger job, and bring a laptop to hack on in your spare time if you still want to program.

      If you want to get into the tech industry, read my words and burn them into your brain: YOU WILL ENCOUNTER IGNORANT PEOPLE, AND YOU WILL NEED TO BE PATIENT BECAUSE MANY OF THEM WILL *NEVER* LEARN. Deal with it. This is not an option, folks! The most ignorant, impossible to teach people use computers, and you -- being a techie -- will have a long string of them stuck to you like toilet paper on the bottom of your shoe. They won't learn no matter how many times you explain things to them, mostly because they expect you to be around forever to do their remembering for them. Cut them off if you wish, but bemoaning the fact that they exist only shows how clueless you are about the reality of being a techie in a technical industry.

      There are always those folks who actually are capable of learning, but they don't know where to start looking. Patiently pointing them to docs helps. Not everyone knows that if they download a tarball, use an arcane tar command to extract it, use "cd" to change to a directory, then use "less" to view a file called "README" that their questions will be answered. If you've never seen a command line before, how would you want something like this explained to you? "Idiot, read the fscking README and then erase my software and never soil my web site with your plebian presence again!" Yeah, that's effective... And to think that if half of the effort of flaming the person went into patiently saying how to obtain docs, both you and the person trying to learn would be much better off.

      ... or is this perhaps your idea of "...how to fix it"?

      As for "the majority of users are horridly ungreatful [sic]", not only are you 180 degrees off (most are extremely grateful for any tid bit of help you can throw their way), but I'll go so far as to say most developers -- the ones lacking people skills who got into the tech industry anyway -- are the problem. When someone asks for help, many times (s)he doesn't even know where to start looking for info. And on sites like SourceForge (to give an example), the UI is so un-intuitive that even clicking on a documentation link may get you no closer to documentation than reading source code. Inconsistency, docs that are hard to find (if any exist at all, and aren't cryptic as hell), illusions of grandeur as if the software you're porting/writing/supporting makes you a God, etc... The problem lies mostly with arrogant techies IMHO.

      COMPSCI 101, huh? I guess that means you have school smarts. Street smarts beats school smarts in a situation like this, "chap". (And yes, I'm a professional working in the tech industry as a software engineer. I know what I say from experience, not from wild guesses...)

    16. Re:gpl community by spongman · · Score: 2
      One solution is to make sure anyone taking has already given, like I'm told some BBS's used to do.
      Alright!

      In other words, attach a value to effort? Something that can be tangibly counted and traded.

      I believe that's that the rest of the economic world is already doing: money for a day's work.

  3. The GPL doesn't have an advertising clause by bhurt · · Score: 5, Informative

    It would be perfectly legal for me to grab a copy of the Linux source code, rip out all the credits as to who did what work, and release my new OS "Brianux". This would be reprehensible (and for the record, I have no intention of actually doing this, so save your flames)- but perfectly legal so long as I released the source.

    1. Re:The GPL doesn't have an advertising clause by ryants · · Score: 5, Informative
      Well, there's no advertising clause, but there is this:
      2 a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change
      So you would be obligated to state in each of those files that you changed them, and when, which should make it easy for people to see what you did (and did not do).
      --

      Ryan T. Sammartino
      "Ancora imparo"

    2. Re:The GPL doesn't have an advertising clause by anthony_baxter · · Score: 2, Insightful

      legal, yes. ethical? no.

      I know I wouldn't purchase anything from a company that was found to do this.

      Let's face it, one of the few benefits of working on opensource projects is the kudos - if parasitical companies start coming along and ripping projects off in this way, it's going to have a pretty severe impact on the developers of the ripped-off projects.

    3. Re:The GPL doesn't have an advertising clause by cjsnell · · Score: 2


      Interesting point. It seems kind of vague, though. Perhaps they should spell out exactly what a "prominent" notice means. Does that mean that it should be at the very top of every source file? What about the application, since most people will never look at the source?

    4. Re:The GPL doesn't have an advertising clause by wishus · · Score: 2

      From the GPL:

      1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty;...

      So yes, you could rip out all the comments as to who did what, but you are required to maintain the copyright notice which would include the developer's names. You can even rename it to Brianux, as long as you maintain that copyright notice, which would include Linus Torvalds, et. al.

    5. Re:The GPL doesn't have an advertising clause by jas79 · · Score: 1

      It would be perfectly legal for me to grab a copy of the Linux source code, rip out all the credits as to who did what work

      no , it is not ok to do that. you still have to mention who own the copyright in the place where you mention copyright,but you aren't required to mention it on the box or in ads.

      from the GPL:
      "1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice ....."

    6. Re:The GPL doesn't have an advertising clause by Carl · · Score: 1

      > rip out all the credits as to who did what work

      You may not rip out any copyright notices.
      The GPL even requires that you "conspicuously
      and appropriately publish on each copy an appropriate copyright notice".

    7. Re:The GPL doesn't have an advertising clause by pete-classic · · Score: 2

      I believe that this is intended to prevent the opposite case. A "vendor" making modifications and then passing it off as "official." (And then probably acting (?) dumb when it breaks.)

      I don't think that there is any attempt in the GPL to preserve "credit." Of course, copyrights are maintained, but I didn't see anything in the emails about copyright notices being whacked out.

      Basically, I think that this guy is trying to enforce what he thinks the GPL means, not what it says.

      Not that this isn't an f-ed up situation, but I think it is tough luck.

      -Peter

    8. Re:The GPL doesn't have an advertising clause by Jason+Earl · · Score: 5, Insightful

      Heck, at first Mandrake was nothing more than RedHat with KDE. They happily took RedHat's GPLed installer (and other features) and put Mandrake in where RedHat had been.

      That's Free Software.

      Now, it sounds to me like the people that these groups that were actually selling copies of this software should have been a little more careful about giving credit where credit was due if for no other reason than ticking off the primary developer is a bad deal.

      Now, the fact that forked.net wasn't providing source code along with their binaries, is a different story all together. The GPL does not guarantee that the original author will get credit, instead it guarantees that the end user gets source code. If you want credit then use a different license. Just remember that advertising clauses and the GPL don't mix, so you won't be able to use any GPLed source in your new product.

    9. Re:The GPL doesn't have an advertising clause by eyeball · · Score: 3, Insightful
      The GPL even requires that you...
      Me != lawyer, but wouldn't GPL requirements only apply if I entered into a contract with the owner of their code? I wasn't paying attention, but I don't remember agreeing to an end-user-license-agreement last time I installed linux. But I dunno since I get the impression that the Slashdot/Opensource community is opposed to EULAs...

      Or is it that because they hold the Copyrights, so they can specify how the materials are used? If that's the case, then aren't we contradicting the usual Slashdot opinion that copyright laws should protect the copyright, and not be used to enforce the license restrictions (or copy protection)?

      I'm sure this kinda stuff has been brought up before, and I'm not trying to stir up trouble or argue... I'm Just curious.
      --

      _______
      2B1ASK1
    10. Re:The GPL doesn't have an advertising clause by Osty · · Score: 1

      Now, the fact that forked.net wasn't providing source code along with their binaries, is a different story all together. The GPL does not guarantee that the original author will get credit, instead it guarantees that the end user gets source code.

      Not providing source with a binary distribution of a GPL'ed software is not a problem. Refusing to give out the source when asked (and you can limit this to customers who have paid for a valid license, though you can't restrict them from modifying and redistributing your work for free) is "wrong" according to the GPL.

    11. Re:The GPL doesn't have an advertising clause by Anonymous Coward · · Score: 0

      Me != lawyer, as well. As I understand it, you are correct in that the GPL requirements only apply if you enter into a (implicit) contract.

      But if you do not enter into that contract, then you have no rights to use it all.

      A standard EULA is when you have purchased the software, gaining full rights to it under standard sales laws. The EULA then *removes* rights.

      Since you do not purchase GPL programs -- and since they are *not* in the public domain, even though they may be in public view -- you have *no* rights to read, distribute or use them at all. Except that the GPL *grants* you those rights.

      That's the difference.

    12. Re:The GPL doesn't have an advertising clause by AnotherBlackHat · · Score: 1

      Yes, it's old news.

      You aren't required to follow any licence at all,
      but there's nothing besides the GPL which gives you the right to distribute copies

      IOW, if you don't agree to the licence, then you can't (legally) make copies.

    13. Re:The GPL doesn't have an advertising clause by reynaert · · Score: 3, Informative

      I wasn't paying attention, but I don't remember agreeing to an end-user-license-agreement last time I installed linux.

      You're half right. You don't need to accept any kind of licence to use or modify Linux or any other GPL'ed software.

      However, if you want to distribute (copy) GPL'ed software, there are two possibilities:

      1. You don't accept the GPL. In this case, standard copyright law applies, and you're not allowed to distribute the code without special permission from the owner of the software.
      2. You accept the GPL, and you are required to follow its terms.

      So you can't copy GPL'ed software without following the terms of the GPL or getting special permission.

    14. Re:The GPL doesn't have an advertising clause by BlueWonder · · Score: 1

      Me != lawyer, but wouldn't GPL requirements only apply if I entered into a contract with the owner of their code? I wasn't paying attention, but I don't remember agreeing to an end-user-license-agreement last time I installed linux.

      IANAL, but Eben Moglen is. Read what he has to say about enforcing the GPL.

      In short, proprietary software vendors usually want to take away rights which copyright law would otherwise grant. This is only possible if both parties enter into a contract. The GPL, on the other hand, adds rights to those provided by copyright law. You are free not to accept the GPL, in which case you are bound by copyright law (ie, no modification or distribution at all).

    15. Re:The GPL doesn't have an advertising clause by decade_null · · Score: 2, Interesting

      Reading the links in the article, it seems that OpenOSX did everything correctly and didn't try to hide anything from its customers. But that was not enough for Christoph Pfisterer, he wanted OpenOSX to give more credit to himself on the website.

      With macosx.forked.net there seemed to be some real problems with GPL, but they at least seem to want to fix those problems.

      After reading all the material directly linked from the story, it seems to me that Christoph is the asshole here.

    16. Re:The GPL doesn't have an advertising clause by Skuld-Chan · · Score: 1

      What about all the borrowed bsd code that is under a similar license that requires you to give credit?

    17. Re:The GPL doesn't have an advertising clause by nateb · · Score: 1

      #this file changed 11/14/01 - brianux release party.

      --
      -- Nate
    18. Re:The GPL doesn't have an advertising clause by Anonymous Coward · · Score: 0

      But the guy didn't modify Fink. DUH

    19. Re:The GPL doesn't have an advertising clause by benedict · · Score: 2

      I don't know that anyone was being an asshole. I think that Chris P.'s work earns him a little better treatment than calling him an asshole as soon as he does something you don't like. I will say that after reading that email exchange, it seems like maybe he was/is suffering from a touch of project burnout. I don't think the OpenOSX guy was as unreasonable as Chris implies.

      --
      Ben "You have your mind on computers, it seems."
    20. Re:The GPL doesn't have an advertising clause by seann · · Score: 0

      Bull
      Shit.

      --
      I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
    21. Re:The GPL doesn't have an advertising clause by julesh · · Score: 2, Insightful

      Now, it sounds to me like the people that these groups that were actually selling copies of this software should have been a little more careful about giving credit where credit was due if for no other reason than ticking off the primary developer is a bad deal.


      Having just read through the details of what happened here, I don't even see this point. The person selling the CDs wasn't actually aware that any credit was being missed out, and upon being informed of this problem, offered and in fact did rectify it. I think all of the problems here come down to a clash of personalities and the fink maintainer expecting his name up in lights or something, while the CD distributor (IMHO rightly) focussed the credit upon those who wrote the original program (ie GIMP) and only mentioned the porting efforts embodied in fink as a side reference.

    22. Re:The GPL doesn't have an advertising clause by Happy+Monkey · · Score: 2

      In short, proprietary software vendors usually want to take away rights which copyright law would otherwise grant.

      Actually, the proprietary software vendors do give you one thing that copyright law doesn't. Due to a bizarre reading of copyright law, the installation of the software on the computer, and the copy of the software in RAM are considered copies that can be regulated by copyright law. So you can't install or run software without the permission of the copyright holder.

      --
      __
      Do ya feel happy-go-lucky, punk?
    23. Re:The GPL doesn't have an advertising clause by DavidTC · · Score: 1
      Wrong, that loophole was fixed with the DMCA. It's perfectly legal to make copies into memory if you have to do it to run the program.

      Read this, a 1 and 2.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    24. Re:The GPL doesn't have an advertising clause by Happy+Monkey · · Score: 2

      Wow. That's good news. So what separates software from books now, with respect to the 'first sale' doctrine?

      --
      __
      Do ya feel happy-go-lucky, punk?
    25. Re:The GPL doesn't have an advertising clause by DavidTC · · Score: 1

      Nothing at all. Especially if you get a minor to agree to the 'contract' at the start.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  4. If we were too... by Phaze3 · · Score: 1

    If we were to steal their code we would most likely give them credit. They will not allow this, but they will still ours without giving credit to us. What a double standard...

    1. Re:If we were too... by anothy · · Score: 1

      it's not a double standard. it's a choice. the writers of fink and most other software projects make a choice as to what terms they want to license that software to users. fink, and lots of other people, choose to release it open source. others do not.
      a double standard would be for some projects to have that choice, and others not to.

      --

      i speak for myself and those who like what i say.
  5. Re:Just so everyone knows... by Feyr · · Score: 1

    you're DoSing websites because they're violating the GPL? how old are you? 12, 13 at most? grow up please, DOS are NOT the way to go

  6. Should Apple be involved? by inkswamp · · Score: 4, Insightful
    Someone on Macslash commented that Apple should be financially backing these kinds of projects. I wonder what sort of effect that would have on this kind of thing.

    BTW, being a long-time Mac user myself, I'm totally clueless to how these kinds of open source issues are worked out, but I am curious about it. These kinds of issues can't be new. Can any of you more acquainted with this topic offer any sort of precedent for these kinds of issues/disputes?

    --Rick

    --
    --Rick "If it isn't broken, take it apart and find out why."
    1. Re:Should Apple be involved? by Anonymous Coward · · Score: 0

      Well, maybe Apple should be more involved but at least they are already funding a number of open source projects. See

      http://www.opensource.apple.com/

    2. Re:Should Apple be involved? by benedict · · Score: 2

      Apple seems to be backing the other horse, Open Packages, though I see from a later post that they have helped the fink group.

      In the long run I think that OP is a more promising project, though one should never be too quick to dismiss the advantages of running code and an installed base.

      --
      Ben "You have your mind on computers, it seems."
    3. Re:Should Apple be involved? by Anonymous Coward · · Score: 0

      Apple should probably remain neutral. Apple is successful partly because of Photoshop et al. If Apple is financing a competitor, whatever its shortcomings, it gives it a lot of validity, and suddenly 90% of the people who use Photoshop (or whatever) realize that all they do is edit pictures for their homepage, and don't need to fork out the cash for the professional tools. Apple sinks.

    4. Re:Should Apple be involved? by nycdewd · · Score: 1

      Don't look now, but if all I wanted to do was edit pics for a homepage I'd use Graphic Converter shareware, $30 I think. I bought it so many years ago now I forget the price. It is fast and powerful and works with any image filetype you can mention. Yes, I am now and forever a Mac user. Always have been and I am fairly old. I should mention that a couple of years before OS X came out I sent several long and thoughtfully worded emails to Apple BEGGING them to opensource a large part of what is now called OS X. Lo and behold, they did.

    5. Re:Should Apple be involved? by seann · · Score: 0

      Just like we blame one woman for all the choas and destruction in the world, we blame you for all the greatness and accomplishments anyone has ever done.

      --
      I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
    6. Re:Should Apple be involved? by nycdewd · · Score: 1

      heh heh, clever... i am sure that i was hardly the only one to beseech Apple to do *something* for opensource as regards OS X. i merely meant to imply that it is nice that they likely listened to us (as they most/so often do) and made some effort.

    7. Re:Should Apple be involved? by seann · · Score: 0

      just playin

      glad to see somebody actually takes stands agains software companys

      --
      I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
  7. Woooooah Nelly.... by cjsnell · · Score: 4, Informative

    Before anyone starts bashing the macosx.forked.net guys, let's keep a few things in mind:

    1) There's nothing wrong with charging for access to files. You pay your ISP, right?

    2) Apex *is*, apparently, working to comply with the GPL. From what I've read in the past on his site, he works in the commercial fishing industry up in Alaska. I would imagine that his time to work on the site and the packages is limited.

    3) Apex has been very helpful in the past on the forums hosted on his server. Lots of people have requested ports of software (some of which are difficult) and he has come through for them.

    Chris

    1. Re:Woooooah Nelly.... by BlackFingolfin · · Score: 3, Informative

      I don't think one should put down Apex generally, and I don't suspect real bad will behind his actions. But I also think it was pretty lame by him to pretend he did port all the software, when in fact a large subset of his packages were straight "ports" (or should I say: rip-offs?) of Fink packages. That in turn wouldn't be too bad, if he just gave credit where credit was due.

    2. Re:Woooooah Nelly.... by ghack · · Score: 1

      So what? He still has a legal obligation to abide by the rules of the GPL.

    3. Re:Woooooah Nelly.... by Ziwdam · · Score: 1

      I contacted Apex about the GPL violation, and I contacted him about a violation of his privacy policy (UBB was giving out cookies, his privacy policy said his site didn't give out cookies).

      As a result, he removed his privacy policy and posted a notice on his web site that he was "Working to comply fully with the GPL license."

      I have to say that it's not really all that hard to comply with the GPL for him... he just needs to tar and gzip the source of the package he's working on after he makes any changes and make it available for download. Not a big deal if he started out that way. Certainly slightly harder if he deleted his old source, but he really should have known about the requirement to make source accessible. (Hell, he could just say, "If you ask me for the source, I'll send it to you." That would be compliant.

      --
      It is a miracle that curiosity survives formal education.-Albert Einstein
    4. Re:Woooooah Nelly.... by LetterRip · · Score: 2

      "Apex *is*, apparently, working to comply with the GPL. From what I've read in the past on his site, he works in the commercial fishing industry up in Alaska. I would imagine that his time to work on the site and the packages is limited. "

      Apparently you are not familiar with the Alaskan Commercial Fishing Industry - he probably has nine months of the year to work on it . (Actually he might be crabbing during the winter, but most of us put it three or four months of hard work doing dangerous shit (ie sleeping for 2 (or less) hours in 48 hours in the second most dangerous job in the US...), and then slack the rest of the year. (Of course if he's been commercial fishing these past couple of years, then he probably works the rest of the year to support his commercial fishing habit ).

      LetterRip

    5. Re:Woooooah Nelly.... by cjsnell · · Score: 2


      Actually...I am, a bit. I've read all of Spike Walker's books, which seem to be pretty accurate. I know that there is fishing (crabbing?) for king crab up in the Bering Sea during the winter. He might be working in a cannery or doing maintainence on boats. Who knows... I'm just going off of what I've read in his forums.

  8. Attitude? by pbur · · Score: 5, Insightful

    Ok, I read through the supplemental information and his attitute to the first guy posting to Sourceforge just seemed wrong. Not knowing this guy, he seems very abrasive and doesn't understand that not everyone is a freaking computer genious. Yes, people who don't read the manuals are annoying, but when you YELL at someone you are turning them off big time. Especially when it seems that the guy just downloaded an old version of mysql and there seems to be no indication that the new version is required. It really comes down to the fact I can't get over HIS USE OF SHOUTING in what seemed to be a normal civilized support request.

    Pbur

    1. Re:Attitude? by Xerithane · · Score: 3, Insightful

      Keep in mind, that he stated that they discussed it on the forked.net board and apex deleted the thread from the message board.

      You don't know what the discussion was like before then.

      --
      Dacels Jewelers can't be trusted.
    2. Re:Attitude? by Big+Jason · · Score: 1

      You've obviously never posted a stupid question to misc@openbsd.org and received the wrath of Theo.

      There is no such thing as a stupid question, only stupid people who don't/can't RTFM.

    3. Re:Attitude? by No-op · · Score: 2

      this guy actually seems like a clone of Theo DeRaadt. an abrasive asshole who insists on acting like a child. I'm sure he busts his ass doing the fink work but he really goes about all this the wrong way. you catch more flies with honey than with SULFURIC ACID.

      --
      EOM
    4. Re:Attitude? by Anonymous Coward · · Score: 0

      Absolutely, all the good people working for open source projects owe it, not only to themselves, but to their projects to RELAX

    5. Re:Attitude? by Erasmus+Darwin · · Score: 2
      "Yes, people who don't read the manuals are annoying, but when you YELL at someone you are turning them off big time."

      I would gladly piss off a dozen users who are too obnoxious to bother reading the manual as opposed to pissing off one developer who's spending the majority of his time working on a free software project.

      It seems to be a simple fact that running any sort of high profile project (software or otherwise) is an easy way to net yourself a world of shit. A vocal minority of users will bitch at the people in charge for anything and everything, even if the people are donating their time.

      I honestly don't know whether this guy was abbrasive to begin with or if the continual grief just eventually took its toll. All I can really say is that someone who (according to all accounts) was quite talented and willing to put in quite a bit of time into the project got fed up with dealing with crap that, ideally, he shouldn't have to deal with.

    6. Re:Attitude? by efgbr · · Score: 2, Insightful

      I'd rather be an ignorant asking the wrong questions than a nerd yelling at people "go read the manual, stop wasting my time, blah blah blah".

    7. Re:Attitude? by ethereal · · Score: 1

      flies: "Ah, my compound eyes! The goggles do nothing!"

      --

      Your right to not believe: Americans United for Separation of Church and

    8. Re:Attitude? by Apotsy · · Score: 1

      I'm pretty sure the previous poster was not talking about the e-mail exchange with apex, but instead was talking about this, which really does look like a bad attitude. Flaming someone in all caps because they forgot to include the version number in the bug report is just plain out of line.

    9. Re:Attitude? by Pete · · Score: 2, Insightful
      I think what you meant to say was "I'd rather be a hardworking opensource developer spending large amounts of my valuable time patiently answering repetitive questions (about the product I work on) from people who haven't even made the attempt to look in the product documentation in which the answer to their question can be found.... than a hardworking opensource developer telling such people to 'go read the manual and stop wasting my time, blah blah blah'"

      Because otherwise your remark doesn't make sense, and you're essentially saying "I'd rather be part of a large problem than part of a small problem (which could even be considered a partial solution to the larger problem)."

      Pete.

    10. Re:Attitude? by No-op · · Score: 2

      that's true- nobody can deny theo's got some massive skills.

      I don't understand why this fink guy would use something as silly as debian apt-get or whatever instead of using the FREEBSD ports mechanism- which (in my opinion) is vastly superior, and would probably represent less work on his part. when someone creates the Fbsd ports tree for OS X I'll finally buy a system with it.

      why go and muddy up the BSD license world with lots of icky GPL code? ewwww!

      --
      EOM
    11. Re:Attitude? by Xerithane · · Score: 1

      Looking at both of those I would definitely agree that he is not making good choices as to how to handle things. For his all caps, I think he was trying to illustrate the point that people only read things if it's big and obnoxious (referencing context)

      I don't think there is any excuse to be rude, even if you are a volunteer or not. I can relate, and understand where he is coming from. After devoting a lot of time to any project, compensated or not, when you start to feel the nagging lack of justification for doing it it's easy to fall into that role. Being a developer is more than writing good code, it's having the frame of mind that people will criticize and hate your work; just like any artist.

      --
      Dacels Jewelers can't be trusted.
    12. Re:Attitude? by Anonymous Coward · · Score: 0
      It's the sign of someone coming unglued. He's had too much and went over the bend.


      Find much older posts to compare, hopefully they will be more curtious.

  9. Re:Just so everyone knows... by cjsnell · · Score: 1, Redundant


    Don't feed the trolls, please. Thank you, drive through.

  10. Re:Just so everyone knows... by Anonymous Coward · · Score: 0

    They won't be distributing software illegally, I can tell you that! Come on, who's with me?? T - 10 minutes.

  11. he needs to de-stress by nehril · · Score: 5, Insightful

    this fink maintainer (Christoph Pfisterer) really does need to get off the project, and onto some valium. reading the threads he posted after his rant one gets the impression that he is on a permanent caffeine-stress-hairtrigger high. jeez.

    The email exchange between him and the supposed gpl violators is a hoot. The very first response Christoph got from the company was "did we screw up? tell us how to give proper credit," and Christoph then proceeds to continue bashing and raving.

    It really sounds like christoph needs a major vacation, the stress seems to be breaking him. I don't know any of the people/orgs involved, but just read his rant and the links he posted at the bottom.

    1. Re:he needs to de-stress by NMerriam · · Score: 2

      I agree -- after reading through all the messages, it certainly seems that Christoph is genuinely upset, but not about anything that anyone in particular has done.

      There are no GPL violations or real ethical lapses here, it just seems like maybe the community is too big for the kind of relationships he wants the developers and users to have.

      This is more of a "tragic on all sides" situation than a case of anyone doing something wrong.

      --
      Recursive: Adj. See Recursive.
    2. Re:he needs to de-stress by AbsoluteRelativity · · Score: 1

      Actually they both made mistakes and lost their cool. Jeshua Lacock wasnt exactly cool headed, they both started off rather cool headed, but by the third and fourth emails they both lost their tempers, any one of them could have prevented it from getting worse by keeping a cool head. I mean Jeshua Lacock went so far as to use the word ignorant. How do you tell someone they are wrong and get them to cool down by using words like "ignorant"? You dont.

      --
      disclaimer : My views do not represent those of every one else in slashdot.
    3. Re:he needs to de-stress by flacco · · Score: 2
      this fink maintainer (Christoph Pfisterer) really does need to get off the project, and onto some valium. reading the threads he posted after his rant one gets the impression that he is on a permanent caffeine-stress-hairtrigger high. jeez.

      Agreed. Chris needs to take a break for awhile, then maybe come back with a lighter schedule.

      --
      pr0n - keeping monitor glass spotless since 1981.
    4. Re:he needs to de-stress by efgbr · · Score: 3, Insightful

      I know what you mean. He even acts as if he created the packages, when the only thing he did was ported them.

      Sure, give credit where its due. But tell me something: do you know who is responsible for porting Linux to CRIS?

    5. Re:he needs to de-stress by Anonymous Coward · · Score: 0

      Well, he was a bit extreme. Maybe you should shoot him.

    6. Re:he needs to de-stress by flacco · · Score: 2
      Well, he was a bit extreme. Maybe you should shoot him.

      hee hee hee... if i only had a gun....

      --
      pr0n - keeping monitor glass spotless since 1981.
  12. GPL: Law or Social Understanding? by dominion · · Score: 5, Insightful

    Situations like this underscore the real strength (and weakness) of the GPL. The strength is that the GPL has worked so far without any large-scale legal challenge. There's a strong social understanding that comes with GPL'ed code, that you give back to the community from which you've taken.

    The weakness is that the GPL would probably lose in court, to some degree. This is because copyright law and, in many ways, the legal system, in the US and elsewhere, were never designed to work in accordance with the common good, especially when it comes to issues of property, and even moreso when it comes to the issues of intellectual property (really just an illusion of modern society).

    Therefore, when approaching breaches of the GPL, it's probably in our best interest, as a community, to not immediately threaten legal repurcussions, but instead work on other ways to pressure entities to abide by our community's standards.

    Any entity that uses GPL'ed code in bad faith ultimately will recieve a pretty bad reputation in the growing free software community. Also, if they're not willing to abide by our rules, what says that we should abide by theirs? For instance, if Microsoft rolls a bunch of GPL'd code into a new product, then we retain an ethical (if not legal) right to distribute the resulting binary of that product as much as we'd like.

    I didn't intend this post to be as long as it is, but basically, think about this: Do we see free software as a phenomenon? Something that just happened? Or as a movement? Something that we all made happen? If it's a phenomenon, then the best we can hope for is that the GPL sticks, on a legal basis. If it's a movement, then we're going to have to be prepared to come together and face challenges. So far, although a lot of us haven't acknowledged it, we've functioned as a movement, and we've been very successful. Witness the FUD that Microsoft used to spread about Linux. Our responses to that FUD ended up making MS look more like sore losers than better producers.

    Also consider that it's possible the struggle for collectively owned information and intellectual property may some day move far outside of the internet, and into the real world. That might require a whole new re-evaluation of our tactics and ideals.

    Okay, enough ranting.

    1. Re:GPL: Law or Social Understanding? by Anonymous Coward · · Score: 0

      Thank you for the heart-felt copy and paste.

    2. Re:GPL: Law or Social Understanding? by Anonymous Coward · · Score: 0

      Your concept of "the common good" including "Free" software is so out of whack with reality that it's difficult to even begin flammage.

    3. Re:GPL: Law or Social Understanding? by dominion · · Score: 1


      Actually, I wrote it just for this article. If you're capable of finding this rant elsewhere on the internet, I'll concede, but considering the impossibility of that, I stand that this is an original work.

      Thank you, please come again...

    4. Re:GPL: Law or Social Understanding? by dominion · · Score: 1


      If it's so out of whack, I would think it would be easy to begin flammage. Why don't you give it a whirl anyway, eh?

    5. Re:GPL: Law or Social Understanding? by Anonymous Coward · · Score: 0

      Yep. Pretty good post.

      An important corollary nearly always forgotten by the /. crowd is that *not liking the GPL does NOT make you a troll..."

    6. Re: GPL: Law or Social Understanding? by ProfDumb · · Score: 2, Informative
      The weakness is that the GPL would probably lose in court, to some degree.


      Well, the Lawyer for the Free Software Foundation says he enforces the GPL all the time by threatening to sue and companies always back down because the GPL is so easy to enforce. The point is that the GPL grants the customer rights that do not exist under standard copyright law. If you re-distribute a work based on someone else's copyrighted code and you then challenge the GPL then you are in for a big-time copyright violation. If the GPL is invalid, you had no right to the code in the first place!

    7. Re:GPL: Law or Social Understanding? by cowbutt · · Score: 2
      Also consider that it's possible the struggle for collectively owned information and intellectual property may some day move far outside of the internet, and into the real world. That might require a whole new re-evaluation of our tactics and ideals.

      It already has. My involvement with Free software has already led me to protest about the actions of RiceTec Inc. who have patented Basmati rice!

      IMHO, Basmati rice is used by humanity under the terms of a GPL-like license (if it wasn't, why does it produce seeds (aka source code) that can be grown (compiled) to produce new rice?)

      Luckily, it looks as though, for once, the system came through and ruled that 75% of their claims were invalid

    8. Re:GPL: Law or Social Understanding? by timster · · Score: 3, Interesting

      You say "the GPL would probably lose in court". Why? You don't claim to have any legal experience, and neither do I, but it seems odd that you'd make claims about probabilities.

      The GPL is based on the same theory that commerical software licenses are based on: we take a piece of software and copyright it (it's been clearly established that software is copyrightable; therefore there is not any sort of doubt as to whether GPL'd works are validly copyrighted). Since the work is copyrighted, we can require people who wish to copy the work to agree to our terms, whatever they are. We can require them to quack if we want.

      If the GPL is not a valid grant of copy license, realize that means the works cannot be distributed at all. It's impossible for copyrighted works to enter the public domain before expiration unless the copyright owner allows it. The GPL is clearly not a statement of public-domain intentions.

      If you violate the GPL and are sued, you can either admit that you agreed to the GPL or you can claim you didn't. If you did, we're out of copyright law (and so it doesn't matter what copyright law was designed for) and into contract law. In contract law, you largely don't have rights that you've agreed not to have; you agreed not to violate it when you agreed to it. If you claim you never agreed to the GPL, you're copying a copyrighted work without a license: old-fashioned copyright infringement. It doesn't even matter if the person who gave it to you in the first place violated the GPL and took the copyright notices off; it's still copyrighted (though the penalties would likely be smaller in that case). Copyright doesn't just magically disappear because someone uses it for something other than "you-give-me-money-I-give-you-software" material-world emulation.

      --
      I have seen the future, and it is inconvenient.
    9. Re:GPL: Law or Social Understanding? by Anonymous Coward · · Score: 0
      You're right, you're not a lawyer.

      It's by no means considered the case that software licenses and/or EULA's have the property of assent which allows for the consideration necessary to form a contractual obligation. This alone multiplies the possibilities beyond those you've considered.

      Additionally, the law is not binary even though legal arguments have a foundation in logic. You suffer from a common malady affecting programmers and other "tech" types. The subjectivity of argument is one of the factors which makes law in the large more politics than system.

    10. Re:GPL: Law or Social Understanding? by maroberts · · Score: 2

      The Free Software Foundation has persuaded numerous people to back off in the face of the GPL. The reason is simple - it is a license giving you EXTRA FREEDOMS over standard copyright restrictions and you can choose to abide by it or be taken to court under standard copyright legislation, which IS well tested.
      In giving you those extra freedoms, you have to accept the terms of the license. The GPL is not like a shrink wrapped license which restricts your freedom, you may only see after opening the package, and therefore may be legally invalid.

      If the GPL is held to be invalid the person who is breaking the GPL terms is guilty under standard copyright law, which carries very hefty penalties. The cleverness of the GPL is it is a catch-22, i.e. break the terms of it, and they can get you whether or not the GPL is valid.

      --

      Donte Alistair Anderson Roberts - hi son!
      Karma: Chameleon

  13. Maybe I missed something... by --daz-- · · Score: 2, Interesting

    It looks like Chistopher is complaining about a few points, to which Jeshua replies and proves Chistopher wrong (i.e. "No where I have I taken credit for porting the software. Where is the word 'ported' mentioned?").

    I guess I miss Chistopher's argument, as Jeshua pretty much set him straight. Jeshua is also right. Chistopher knows nothing about Jeshua. Jeshua could be a huge OSS contributer in a bunch of other projects.

    Sounds like Chistopher is a crybaby and doesn't felt he got his way for some reason, so now he's quitting.

    If that's not it, what'd I miss?

  14. Short Fuse by nate1138 · · Score: 3, Insightful

    I understand that this guy is working for free, But if you are not prepared to deal with users who need some help, why in the hell are you developing end-user software? I work as a developer, and idiotic questions make up about 20% of my average day. Read some of the email exchanges with openosx, and with users on sourceforge, and you may come away with the same impression I did, mainly that this dude has a real short fuse and nasty temper. Remember, he VOLUNTEERED to do this project, nobody was forcing it on him. If he doesn't like it, go start another project, or find a cushy commercial position (he's obviously talented enough to get paid some real money).

    --
    Where's my lobbyist? Right here.
    1. Re:Short Fuse by Fnkmaster · · Score: 2

      Well, my guess is that nobody would tolerate that in a commercial position. I mean, we all have our limits and we can all lose our tempers with a sufficient amount of stupidity thrust on us. But you can't go around losing your temper every time you get a dumb question from somebody who didn't RTFM. My favorite strategy is just to repeatedly refer them to the written material, or if they repeatedly refuse, to ignore their requests. This tends to make you more friends than just flaming away at everybody, and works in the corporate world too.

  15. Sounds like a shareware author... by Zoop · · Score: 5, Insightful

    The majority of this guy's decision to resign actually sounds like he's tired of dealing with what shareware and freeware authors have been dealing with for years, with only the good will of people to get any compensation or credit (most shareware on the Mac is not time-limited). The Mac community does have a high standard for software performance and does expect polish from its programmers.

    It results in a fair amount of whinery, but it sounds like this guy is going to be shocked when he finds that users in the professional world will be just as nasty, plus they'll threaten to withhold payment.

    The e-mail exchange didn't impress me a lot either--it sounded like he had one or two points that the guy was willing to concede on, but he blew up and brought other things into the mix for a flame-o-rama.

    So I'm sorry that he's no longer a Mac developer, and I'd encourage him to put his studies first. On the other hand, I'm not going to get too worried about the nature of the Mac community over it.

    1. Re:Sounds like a shareware author... by Arandir · · Score: 2

      I agree with your assessment. He's whining about what everyone else in the industry has to put up with every day. I get the crap he's complaining about constantly.

      He needs to decompress and get back to his studies.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Sounds like a shareware author... by Erasmus+Darwin · · Score: 3
      "He's whining about what everyone else in the industry has to put up with every day."

      I believe you mean: He's whining about what everyone else in the industry gets a paycheck for putting up with every day. Instead, this guy was volunteering his time and because of it, he was getting a bunch of extra shit he didn't want. We know beggars can't be choosers, but apparently philithranopists can't be, either.

      "Lead Developer of a Major Software Project" or whatever his equivilant corporate world title would be would probably be worth six figures and would include support staff. The free software world usually doesn't have the luxury of having other people responsible for handling testing and the like.

    3. Re:Sounds like a shareware author... by rodentia · · Score: 2

      This calls to mind the disjunct between the shareware camps around Wintel and Apple, on the one hand, and the libre community grown up around the OSS *nix on the other.

      Nomination for oxymoron of the month: Linux Shareware.

      While I think OSX is the smartest thing Jobs and Co. has done since the first consumer GUI, I don't think its automatic by any means. The coifed, turned-out designer in Buddy Holly specs gets onboard the BSD bus, scores beaucoup street cred, but has to sit next to that smelly, hairy unix guy. The Mac community will find performance in spades, but polish is not often a value. On the projects I'm familiar with, even the most professional, the response to obnoxious support demands goes: You didn't pay for it and I'm not paid to listen.

      You're more likely to be ignored, or firmly and politely (chrisp is an exception) invited to DIY and while you're at it send a patch.

      --
      illegitimii non ingravare
    4. Re:Sounds like a shareware author... by sydb · · Score: 2

      All well and good, but developers shouldn't get into Free Software without expecting thankless effort. If they expect that, when they do get thanks, it'll be all the more appreciated.

      OTOH users shouldn't get into it expecting polished customer service attitudes from all of the developers, all of the time. If they expect to be lambasted at every turn, then when they find someone who's extremely polite and helpful it will be very pleasant. I'm thinking of Muhri, lead developer of the Pronto mail client. He is the most helpful developer I have ever spoken to. Then again, I try to be a polite user.

      Best of all is if people can forget their roles of "user" and "developer" and just try and be partners in the whole game. We can dream.

      --
      Yours Sincerely, Michael.
  16. Been there, done that by Anonymous Coward · · Score: 1, Insightful

    So many maintainers of various projects have "resigned", but many of those have quietly returned to the projects after a short hiatus.

    This freak will be back and answering support requests. He may not like it, but like others before him, he needs it.

  17. His resignation say otherwise. by victim · · Score: 5, Interesting
    He lists the following reasons for resigning...
    • Tired of unappreciative people.
    • Tired of people who think they are owed immediate support.
    • Tired of being yelled at by above people.
    • Tired of people that complain about bugs but won't help fix. note: you do not need to be a coder to help fix. testers and analyzers are always handy
    • Tired of defending decisions.
    • Tired of people using the mailing list instead of the docs.
    • Tired of working with people that make money off of other peoples work without credit. here we get to some of the headline.
    • Tired of working with some specific offenders of the above.
    • Tired of spending every waking hour on fink.
    • repeat variations of the above some more...


    Sounds more like just plain tired than GPL violations, but then I'm not a slashdot media spinner.

    Christoph deserves a great big THANKS from the world of computer users. I have worked on similar ports to other processors and it is mind numbing tedious work that stretches to the horizon and beyond. Every day you know that you will spend it fixing bugs in a dozen programs, bugs that will range from the trivial to the near impossible to find.

    You do not plan and execute your plan as in the development of a program. You work your way down the list of unwashed packages, build them, test them, fix them and check them off only to find more packages added to the list than you checked off that day. Most of the packages you won't give a rat's ass about, but you do them because someone, somewhere will be wanting it.

    Take a break Christoph. Get caught up in school, then when that itch returns create another wonderful thing.
    1. Re:His resignation say otherwise. by cjsnell · · Score: 2

      I'm an open source developer and have dealt with plenty of this with my own project. I'd like to comment on a few of his reasons...

      * Tired of unappreciative people.

      Fact: most people don't give a flip about how much time you spent coding. Perhaps he should focus more on those who love his work (I'm one of those folks).

      * Tired of people who think they are owed immediate support.

      Procmail does wonders. If its happening on the mailing list, ignore it. If they keep persisting, kick them from the list.

      * Tired of being yelled at by above people.

      See above.

      * Tired of people that complain about bugs but won't help fix. note: you do not need to be a coder to help fix. testers and analyzers are always handy

      Hey, at least they are using the software. When I first started coding Bronc, I was grateful to receive so much as a flame from one of my users. At least people are paying attention!

      * Tired of defending decisions.

      Defending decisions? It's *his* software!! He doesn't have to defend a thing. If someone doesn't like it, they can fork his code and start their own project.

      * Tired of people using the mailing list instead of the docs.

      Welcome to free software, bro. :)

      * Tired of working with people that make money off of other peoples work without credit. here we get to some of the headline.

      You don't have to work with them. Sue them if you want. If you don't want to do that, you can always tweak your code to keep it from working with their product. :)

      * Tired of spending every waking hour on fink.

      I hear ya.

      Chris

    2. Re:His resignation say otherwise. by Eil · · Score: 2

      I've been following the open source software community for quite a while now, and prior to that, the shareware community.

      And I have seen lots of this before. A guy works hard and endless hours trying to perfect his code, his program becomes popular, and then not long after, the critics and flames come along. The writers of the software can't deal with the fact that newbies ask too many questions, or that (heaven forbid) someone decides to extoll his opinions on why the program in question sucks. The pressure mounts, the author gets frustrated and then he gives up and quits.

      This is not the way to do it. Like someone else mentioned, flames, critics, and newbies all mean that your program is popular. If it sucked, it wouldn't be popular. Some (not the majority) of open source software writers expect that if their program rocks, they'll be Linus Torvalds overnight. (This is where my habit of pessimism comes in handy.)

      Most open source programmers get their reward for their time and effort in knowing that their code is good, their code is useful, and people are using it. That's it, nothing more, nothing less.

      You take bug reports, you answer the polite questions (while ignoring the stupid ones), and you thank those who have helped out with testing or the code itself. If the flames get too rough, you just sit back and say to yourself, "Self, this is *my* program and *I* know it's good, so fuck everyone else."

      To this Christoph guy, if he reads Slashdot: While it is very unfortunate that the events you list above occured, you need to accept the fact that developing software in the public's eye comes with these downfalls. If you get into another project and begin to face the same problems, do yourself and the open source community a favor. Don't give up quite so easily the next time.

    3. Re:His resignation say otherwise. by LanMan · · Score: 1

      The GPL violations are most likely just the straw that finally broke him. The other reasons you cite are probably at the core of the problem.

      As the creator/developer of NetSaint (soon to be Nagios, I can understand where his frustration comes from. I've gone through several periods where I feel like just throwing in the towel and calling it quits. During those times I usually take 2 or 3 months to stop development, not respond to email, etc. and just relax. After a few months time I feel like starting up again at full swing. Granted, I've got a load of email and coding to catch up on (or to redirect to /dev/null) when I return, but its the only thing that has kept me going this far. For me I've always returned because:

      • I felt I still had unfinished business in the project (TODO lists never die)
      • I felt I had invested too much time in the project to simply quit and leave it all behind
      • I didn't want to leave all the users out in the cold
      • etc...

      It also helps to develop an attitude of *not* wanting to help people at a certain point. If people are not reading the docs and always coming to me for help, I discard their support requests. References to the docs and mailing lists must be in a dozen places, but people just don't care to try things on their own. The only way you can survive in the long run is to leave these people to their own helplessness and concentrate on what you feel is important. If you loose sight of that, you're done for. Bad attitude, I know, but a necessary evil I think.

      I realize that people always say that because a project is released under the GPL that others will step in and pick it up. I tend to question this attitude. People often don't realize what they're getting into when starting or taking over a project. I would guess most developers of popular GPL packages never thought their apps would require the amount of work that they do. Besides, having a mob of coders trying to have their way at making architecture decisions never got a project very far. Its a better bet that several forks of the project will emerge, each with a small number of leaders. Remember, meetings don't become more meaningful if you add more PHBs.

    4. Re:His resignation say otherwise. by HiThere · · Score: 2

      Better might be to give up more easily, while he still has some cool left. Then he could see if he could find an assistant to take over while he takes a break. Much better all around. And it would be easier to come back when he chose to.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    5. Re:His resignation say otherwise. by mamahuhu · · Score: 2, Insightful

      Chrispy - I'm on your side.

      I love Fink - it's one of the reasons I love Mac OS X - it opens the world of UNIX apps to Mac users... I think it's shitty that others don't appreciate the hard work involved - but I think the other /.ers are right - shit happens - sounds like you need to take it a little less personally. And this post is right on - take a break and get back into it when the time is right.

      GREAT WORK..... I use it every day!

  18. I dunno... by update() · · Score: 5, Interesting
    There's definitely some tension between the mac world and the Open Source and GPL worlds. Certain amounts of culture clash are inevitable...

    There's certainly some clashing between the Mac and Unix worlds (the iTunes installer issue was probably caused by that kind of mutual ignorance) but Apple and proprietary developers have generally gotten along well with the BSD and gcc people as far as license issues go.

    The problems described here don't strike me as being a Mac vs free software conflict. They sound a lot more like the stuff Linux developers have been dealing with for the last few years -- LinuxOne-style abuse of redistribution and self-absorbed users who think that because you gave them something you work for them.

    1. Re:I dunno... by Samrobb · · Score: 4, Informative
      Apple and proprietary developers have generally gotten along well with the BSD and gcc people as far as license issues go.

      What?

      Recently, maybe, but take a look at this link to a copy of the 1993 g++ FAQ:

      Because the legal policies of Apple threaten the long-term goals of FSF, as well as the concept of free software, no support will be lent to efforts to port GNU software to Macintosh or other Apple hardware.

      The FSF didn't end the boycott of Apple until 1995, and even then, they pretty much said that unless supporting MacOS was ridiculously easy, they wouldn't bother accepting patches because that might impact their effort to produce the "GNU operating system".

      If you want a quick summary of the boycott, the reasons, and how the FSF eventually "forgave" Apple the same way he "forgave" KDE, you can check out this link. Frankly, I'm surprised that the FSF and Apple are managing to get along as well as they are; it speaks volumes about Apple's commitment, and about the way the FSF has matured over the years, as well.

      --
      "Great men are not always wise: neither do the aged understand judgement." Job 32:9
    2. Re:I dunno... by dvdeug · · Score: 2

      > the way the FSF has matured over the years

      What do you mean? Apple was following a course of action (a look-and-feel suit), that if it had been upheld in court, could have meant the end of a lot of free software. A lot free software has the look and feel of some other software, ranging from the Unix look and feel to trying to emulate some proprietary application. The FSF was almost obliged to take action, and I fail to understand why you think a boycott is immature.

      Also, I don't they've changed much over the years. GNU/FSF software doesn't usually support Mac (pre-OSX) out of the box. It usually supports Mac OS/X as just another Unix. And the support is almost invariably added by a non-FSF person.

  19. Open source problems by CordMeyer · · Score: 1

    If this project is to continue, everyone involved has to respect the ground rules. when you begin something like this, there is roughly a 50/50 chance of it working or going insane and this just shows how vulnerable the open source world is.
    anyways, i hope Fink keeps going beacuse it hase huge potential and its the main reason I bought OSX.

  20. Apple offers pre-release seeds by Cryptosporidium · · Score: 3, Informative
    Q: What is your relation with Apple?
    A: Apple is aware of Fink and has started to support us as part of their Open Source relations efforts. So far they are providing us with pre-release seeds of new Mac OS X versions in the hope that Fink packages can be adapted in time for the release. Quote: " Hopefully it underscores the commitment that many suspect we're not willing to provide. We'll get better at the open source game over time." Thanks Apple!
  21. Weenies by Large+Green+Mallard · · Score: 2, Flamebait

    Christoph Pfisterer seems like quite the weenie from his email exchange. OpenOSX is just trying to make things easier for people. It's not like they've gone out of their way to anonomize Fink and change its name.

    Are the creators of RPMs forced to give credit to the writers of bash or csh because their programs use these languages to run post/preinstall scripts? Of course not. If you're just using a program to install another program, and the installer program is based on the GPL, don't be expecting to get damn credits all over the packaging.

    In the email exchange posted by Christoph Pfisterer (no less), Josha looks like he's being quite reasonable and that it's actually Christoph Pfisterer being a pillock.

    1. Re:Weenies by jazman_777 · · Score: 1
      In the email exchange posted by Christoph Pfisterer (no less), Josha looks like he's being quite reasonable and that it's actually Christoph Pfisterer being a pillock.


      If you read Gogol's _Diary of a Madman_ (which is hilarious, by the way), the diarist is perfectly logical and rational, and describes things that way. Everyone else is always acting strangely. Of course, he is the one going mad. But to the madman, everything he does is perfectly rational. Not to suggest that Pfisterer is mad (he may be getting there...), but that it's human nature to view things this way.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    2. Re:Weenies by donkeyboy · · Score: 1

      This web browser brought to you by RPM brought to you by glibc broutght to you by make brought to you by gcc brought to you by ...

      This could get messy

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

      Are the creators of RPMs forced to give credit to the writers of bash or csh because their programs use these languages to run post/preinstall scripts?

      Are the creators of the various modules which compose Linux forced to give credit to the GNU...oh..

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

      Not only is he a leech, he apparently has a Slashdot account and mod points.

  22. More on MacSlash by acaben · · Score: 3, Informative
    You can also read about this story on MacSlash, which published the story first. We've got some good discussion going on over there, and lots of people jumping in the fray on both sides of Chrisp.

    Personally, I'm sad to see him go, but hope he'll be back eventually. I understand his frustration with the "community" but hope he notices all of us who forgot to say how much we appreciated his work before he left.

    I think I'm gonna' make a bumper sticker: "Have you hugged an Open Source Programmer today?"

    1. Re:More on MacSlash by Emil+Brink · · Score: 1

      Mmmmm, more people should have stickers like that, that's for sure. Great idea. ;^)

      --
      main(O){10<putchar(4^--O?77-(15&5128 >>4*O):10)&&main(2+O);}
  23. Overworked and burned out... by Amokscience · · Score: 3, Insightful

    Sounds like something I read recently:

    http://www.firstmonday.dk/issues/issue4_10/bezro uk ov/

    (section: "Cult of Personality, burnout of the leader")

    As a maintainer of my own growing project on sourceforge I often emphathize with the items listed in this paper. Some people have a tendency to put an enormous amount of pressure on themselves. When this happens you naturally become very defensive and intolerant. This is probably lessened when you have a strong core group.

    Time to take a vacation.

    --
    Fsck cluebie moderators. I'll say what I want, offtopic or not. And fsck having to qualify every bloody statement just
  24. Read it damnit. by protonman · · Score: 1

    IANAL, but it seems to me an "appropriate copyright notice" refers to some copyright stament made by the author. If you write something, you've got copyright, GPL'ed or not. The way you exercise that copyright is what licenses are all about.

    //---

    GNU GENERAL PUBLIC LICENSE

    Version 2, June 1991

    -= snip =-

    1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

    --
    The man of knowledge must be able not only to love his enemies but also to hate his friends.
  25. I shouldn't have been so slack ... by Strepsil · · Score: 3, Insightful

    Over the last two days, I've set up a couple of new Macs at work, and used Fink to throw all the extra goodies that I needed on. Ever since I started playing with it around 0.20 time, I've found the whole distribution to be wonderful.

    I really meant to post a "thank you" note at some point. I wish I had. I can't possibly account for how much time the Fink people have saved me.

    OK - from reading the background material, I think that Christoph has made some dubious assumptions about people at times, and attacked people a little too eagerly - but these are really just symptoms of someone working way too hard for too little reward. I get like that at work sometimes.

    How about we all take a little bit of time today to send out a simple "thanks" email to one person involved with one piece of free software that you use regularly. It'll only take a minute or so, and may just keep that person feeling good enough about doing what they're doing that they'll keep on doing it.

    Just go and do it now. Slashdot will still be here when you get back.

    1. Re:I shouldn't have been so slack ... by Lumpy · · Score: 2, Redundant

      Ok,

      anyone have linus's or Alan Cox's email addresses?

      I should actualy send them each a case of beer for all that linux has done for me.

      --
      Do not look at laser with remaining good eye.
    2. Re:I shouldn't have been so slack ... by DAldredge · · Score: 1

      Linus...Daddy@Kernel.Org
      ;->

    3. Re:I shouldn't have been so slack ... by qwerty823 · · Score: 1

      How about we all take a little bit of time today to send out a simple "thanks" email to one person involved with one piece of free software that you use regularly. It'll only take a minute or so, and may just keep that person feeling good enough about doing what they're doing that they'll keep on doing it.

      Just what we need... why keep the slashdot effect only on the web, when we can take it straight to you via email! :-)

    4. Re:I shouldn't have been so slack ... by chromatic · · Score: 2
      It's not just programmers. When was the last time *anyone* thanked the people behind Slashdot or OSDN or VA (big target!) or Slashcode? (I did, today. :)

      Really, if people were more inclined to spread praise where it's deserved, it would be easier to deal with legitimate gripes and to dismiss the random whining that's going around these days.

  26. hmm by Suppafly · · Score: 2

    I dont know all of the specifics, but by reading through the supporting materials listed by Christoph Pfisterer in his resignation, it seems to me that he has at many points actively engaged in flaming people on the various support boards for their ignorance.. sure its not all him, but he's doing just as much flaming as any of the people he's complaining about..

  27. Did Christoph by Anonymous Coward · · Score: 0

    miss this page:

    http://www.openosx.com/kudos3.html

    1. Re:Did Christoph by BlackFingolfin · · Score: 1

      No, you missed that page was only added after Christoph complained. And even now, it is not as if you were ever to see it, unless you specifically look for it.

  28. Fink -- what's the point? by George+Walker+Bush · · Score: 1

    Sorry if this is ignorant, as I'm not a Mac guy, but what is the purpose of Fink? It seems like it's a means of porting UNIX apps to OS X?

    But isn't OS X BSD UNIX itself? Just with a nice GUI, some additional APIs and some compatibility/API layers for MacOS apps, lying on top of the BSD UNIX subsystem/MACH kernel?

    --
    George W. Bush
    President, United States of America
    1. Re:Fink -- what's the point? by moof1138 · · Score: 2, Informative

      Fink is a port of the debian package management tools combined with a source based install system. By defauly many Open Source tools need a few tweaks to get them to compile on Mac OS X. Fink automated those tweaks. So you can just use apt/dselect to get software installed, of use 'fink install xxx' and have it automatically download compile and install the software (making a deb file in the process). And it does it without clobbering any of the default system (unlike GNU Darwin - grrr).

      --

      Hyperbole is the worst thing ever.
    2. Re:Fink -- what's the point? by Anonymous Coward · · Score: 0

      Then I guess even this fink guy is violating something, how can anyone violate the santity of apt-get?

  29. These guys aren't part of the Mac world. by selkirk · · Score: 1
    There's definitely some tension between the mac world and the Open Source and GPL worlds.
    This is an irresponsible statement. openosx, macgimp, or macosx.forked.net are more a part of the Open Source and GPL world than they are a part of the mac world. GPL violations by these folks should not be used to characterize the Mac world in general.
  30. Between Mac and OS? by Anonymous Coward · · Score: 0

    > There's definitely some tension between the mac
    > world and the Open Source and GPL worlds.

    THAT'S kind of a "carpet-bombing" kind of statement, given the fact that it's the former head of Fink vs. two now-companies.

  31. Complaining about bug reports by dvdeug · · Score: 2

    > * Tired of people that complain about bugs but won't help fix

    There was a person on Linux Weekly News recently complaining that people wouldn't report bugs on his package. This is part of the reason why. I run across several bugs where I don't have the time or interest to deeply investigate. I can try to make a quick and clear bugreport, but why bother if all I'm going to get is crap for it, or it's just going to get ignored?

  32. Title is false; make up your own minds by rsfinn · · Score: 5, Informative

    There is no evidence of any real GPL infringement here. I urge SlashDot readers, especially the kneejerk "GPL good, Apple bad" crowd, to read the conversations at the indicated links and make up their own minds:

    1) OpenOSX appears to be distributing source code on their CDs, and now gives credit to fink on the MacGIMP CD web page.

    2) Macosx.forked.net has also posted credit to fink on the home page web site, as well as indicating their intention to address GPL issues.

    Apparently Pfisterer is irritated in part because they were slow to give fink credit; but as others have pointed out, that's not a GPL violation.

    Following the other links he includes in his "resignation letter" suggests that he's quick to get irritated -- especially when people point this out to him (cf. the "abiword" thread). Perhaps there are other things going on in his life, and this isn't a good time for him to lead an open-source project. Fine. Kudos to him for leaving his ball behind instead of taking it with him.

    But the article title ("Fink Maintainer Steps Down Due To GPL Infringment") is misleading at best. Even Pfisterer didn't make this claim.

    1. Re:Title is false; make up your own minds by mandolin · · Score: 1
      Apparently Pfisterer is irritated in part because they were slow to give fink credit

      Maybe they should call it fink/OpenOSX..

    2. Re:Title is false; make up your own minds by Anonymous Coward · · Score: 0
      Apparently Pfisterer is irritated in part because they were slow to give fink credit; but as others have pointed out, that's not a GPL violation.
      Well that's the crux of it. But does anyone happen to know what length of time would construe a violation? What is a reasonable period before you should and/or legally can get on them?
    3. Re:Title is false; make up your own minds by AbsoluteRelativity · · Score: 1

      Yep, that is copy-paste news if I ever seen it.

      But Pfisterer is not the only one with a short fuse. While Pfisterer started spuing out about a few things about credit and none trivial things like the naming of XFree86 versioning, Lacock said Pfisterer was "ignorant" and wasting *his* valuable time (as if Pfisterer is a waste of time, which is probably the part that struck Pfisterer the hardest). Although Pfisterer probably should have clarified or made distinct that the credit is not a part of the GPL (in the context he was asking) after they got past that in the second (or so) email, so Lacock may have still thought he was being accused of violation and started an attitude, it may have also been the long email who wrote back.

      --
      disclaimer : My views do not represent those of every one else in slashdot.
    4. Re:Title is false; make up your own minds by fredrik70 · · Score: 1

      no, you don't have to give credit *at all* if you don't wish, as long as you keep the copyrights correct.... GPL does not state you have to give credit. It just a nice thing to do - give credit that is

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
  33. Negative reinforcement by dilvish_the_damned · · Score: 1

    I would not presume to have the knoweledge to fix all the problems he has identified in the 'Give for free, everyone benifits' proccess.
    But it is something that most of us believe in for our own reasons. And becouse of that I would suggest that maybe developers need more positive reinforcement in what they do. Most of us (me included) only think to give feedback when we want something more or we think they are doing something badly.
    What about when we agree with what they are doing or when they are doing something well?
    You have to admit that when everything you see in hear about what you are doing is negative, you gain negative feelings about what you are doing.

    --
    I think you underestimate just how much I just dont care.
  34. Office vX and OSX [Slightly OT] by Nate+Fox · · Score: 1

    Ok, mostly OT, but its an apple thread, right? :) Anyhoo, was talkin to one of the girls I work with last night, and she mentioned that MS Office for OSX comes out today (I think). It dawned on me that OSX has a BSD core. Does anyone know if/what possibilities exist for Office to run on a unix core (ala *BSD/Linux)? The thought crossed my mind, and I had to ask. Anyone got any links or anything of valuable info regarding this topic?

    1. Re:Office vX and OSX [Slightly OT] by Genady · · Score: 1

      It would be difficult because Office v. X looks to be built in Cocoa, the widget set it completely different than GTK or KDE, and it's probably dependant on Quartz to do rendering. So... If someone were to port Quartz and Aqua to *BSD then yes it would be portable. However I don't think Apple will be doing that anytime soon.

      --


      What if it is just turtles all the way down?
    2. Re:Office vX and OSX [Slightly OT] by palndron · · Score: 0

      No.

      It is built using quartz and carbon, which are apples, and run "above" the bsd portion. Equate this to being able to run Windows version of office on a i386 bsd distro.

      Unless someone creates a compatability layer or emulator

      --
      a man, a plan, a canal, panama
    3. Re:Office vX and OSX [Slightly OT] by grendelkhan · · Score: 1

      Actually, I think Office X is a Carbonized app, making it near impossible, even if you had the code, to make it run, as is, on Linux or BSD. Cocoa and Carbon are API layers, not widget sets, with Carbon being the "cleaned up" version of the Classic Macintosh API that will run without the emulation layer on OS X.

      Quartz is the display engine built around Display PDF, a superset of Display Postscript. Considering that Display Ghostscript is basically done, I don't know if the GNUStep guys are thinking about expanding it to encompass the new API's and functions exposed through Display PDF.

      So my theory is no way, no day, not anytime soon. And really, except for Access, what is there that OpenOffice doesn't offer you that MS Office might?

      --
      Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
  35. Bogus Claims by augustz · · Score: 3, Insightful

    In his funny email exchange this guy claims that the violation is the same as if someone took RedHat and repacked it without giving RedHat credit.

    He misses the point that that is FINE. In fact, mandrake did that for a while, with a few changes.

    The GPL means you can copy, rename etc as long as you contribute the source back, and make sure copyright in the source is accurate.

    He needs to get a grip.

  36. Finding out the history of webpages by sjmurdoch · · Score: 1, Informative
    In his webpage, Christoph mentions: "I guess I should have made daily backup copies of their front page. It will be interesting to see how long it lasts this time..."

    The website Wayback Machine allows you to see the way website looked in the past. For example:
    macosx.forked.net in September or
    slashdot.org from 1998.

    --
    Steven Murdoch.
    web: http://www.cl.cam.ac.uk/users/sjm217/
  37. Hmmm... by Anonymous Coward · · Score: 0


    THANK ME, THANK ME VERY MUCH!

    Come on people, if you want fame and fortune the future is in plastics.

  38. I'm eating my words by feldsteins · · Score: 1

    Just the other day I was commenting how Slashdot stories regarding Apple *always* uses a negative slant.

    Well color me wrong, just a day later. An article having to do with the world of the Macintosh and narry a snide remark to be found in the lead-in.

    I'm stupified. But pleased. :)

    --
    You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
  39. Mac Developers by Anonymous Coward · · Score: 2, Interesting

    I don't think that it is true that...

    "There's definitely some tension between the mac world and the Open Source and GPL worlds. Certain amounts of culture clash are inevitable, but hopefully great projects like this will continue, and commercial vendors will be able to play nice without alienating developers."

    The Mac has been an excellent environment for hacking around. Apple has always been the brave alternative for more free-thinking computer users than IBM-PCs and 'nix boxen. It wasn't about the source code then, but it was definetly a matter of integrity. There isn't a culture clash taking place, Fink's maintainer was simply overworked and too posessive of his changes. I think he's more than a bit arrogant and if you take the time to read his stuff I imagine that you'll agree. He didn't _write_ the programs he's porting and he's generally not helping their developers port it (which, IMHO is the correct and standard way to port an Open Source app)!

    Apple should be recognized and praised for releasing Darwin as Open Source. In olden times source code was prized as a resource because you could share it, learn from it, extend it, appreciate it, etc not because of a highly politicized IP philosophy. The GPL does not define Open Source software! If you write code and truly want to share it then do so! Truly respectable developers will credit you appropriately. But, Fink's maintainer is over-estimating his due praise!

    1. Re:Mac Developers by Anonymous Coward · · Score: 0

      > He didn't _write_ the programs he's porting and he's generally not helping their developers port it
      > (which, IMHO is the correct and standard way to port an Open Source app)!

      You are wrong here. Completely wrong. ChrisP wrote one crucial package, dlcompat, that is used by *everyone* porting Unix stuff to Darwin, as soon as dynamic libraries are involved. He is a member of the XonX developer team. He worked with many developers of important packages to straighten out bugs found during the Darwin port, and he urged the Fink developers repeatedly to contact the original package maintainers instead of using some ad-hoc hack.

      Don't judge ChrisP from his last over-excited e-mail exchange, although anyone valuing the quality of software over the right to make a fast buck should support him there, too. During many months before that, he very patiently answered all kinds of users' and developers' questions - too many, probably. And the Fink project will, unfortunately, have a hard time if he doesn't come back soon.

  40. educate yourselves by Anonymous Coward · · Score: 0
    This thread has already been going on Macslash. IMO I think he was perfectly justified in his attitude in answering those emails from people. He was giving his time away for free and people were taking advantage of it. Instead of them bothering to read documentation, they make him answer their questions. They want him to give up a fraction of his life so they can save themselves time and you know if he answered them nicely they would just keep doing it. If this was a professional application and these were paying customers, this would be great. He could charge a fee per support question or (monthly, yearly support subscriptions) and great - they save time, he makes income. Instead all they do is ask questions they're to lazy to answer themselves and then become angry when he answers them in a tone belittling them for wasting his time. If his rudeness makes any of them a little more apprehensive to ask for help and thus in future situations they look up the answers themselves, then I think he's done IT support people everywhere a favor. Personally I think he should not have been rude to them but he should not have told them the answer and instead he should have replied similar to this:

    "Your question can be answered by looking through documentation and simple investigation. I suggest you figure out the answer for yourself as this is a good habit to have. Here [href to docs or page] is a good place to start looking for how to solve your problem. I could give you the answer but it's better for you to be able to give it to yourself. Thanks."

    I've seen the stress of IT support when that was my job. It didn't affect me much but co-workers constantly needed to vent about it. I couldn't imagine how bad it would have been if they weren't paid for it, and Chris wasn't.

    1. Re:educate yourselves by Melantha_Bacchae · · Score: 1

      In an ideal world, all computer users would be well educated geeks capable of looking up any kind of document and understanding it instantly. This is not an ideal world.

      Mac users (well, those of us who don't have professional Unix programming or system administration skills) are used to programs designed well enough that they are intuitive to use without reading a manual (except for programs like Photoshop, which you can stock a library with all the books written for it ;). Such programs also do not need compiling, as they are nicely packaged, so they are child's play to install. Apple designed OS X well enough that the average Mac user shouldn't have to wander into the "geek only/read the docs" areas.

      The problem arises when programs like Fink and MacGimp show up on sites like Version Tracker. VT doesn't have any special section for them, and doesn't provide any instructions. People download them, thinking (especially in the case of MacGimp) that they are just another Mac freeware program. If it isn't a package file that they can just double click, they can't even decompress it. If they somehow get it decompressed, they have no clue how to compile something, or where to put the files, or even access to the root login (which they are better off *not* knowing). If they were to somehow stumble across the documentation, could they even understand it?

      Mac OS X is a wonderful operating system, that is bringing together a wide range software. That is great! What is not so great is that it is throwing together a developer community of the intellectual elite, with a user community that contains a lot of people that are barely computer literate beyond the basic concepts of drag-and-drop and clicking on icons. Apple is having plenty of trouble convincing some of these folks to move their mouse to a different part of the screen to do something (one of the major reasons old-timers give against upgrading). These people are *not* going to be reading man pages anytime soon.

      So I guess its going to be up to the open source developers to change (if you want to develop for OS X/Darwin and want to reduce your stress levels and improve peoples' experiences with open source). Here's some suggestions:

      1) If your application is to be used by non-developers, make sure the user interface is simple and intuitive. Demonstrate it to a friend or neighbor in the target audience to make sure it is relatively idiot proof.

      2) Make sure that the target audience can understand the documentation. If the target is a wide one, you might want a simple section first for the beginner, followed by an indepth one for the expert (clearly label both). FAQs for both using and problem solving should be included, if applicable. Quick reference cards for GUI programs with a lot of options or keyboard shortcuts (like the GIMP) are nice too. Test with target audience.

      3) Linux is not the only bit of open source that needs an easy, idiot-proof, install. Easy installs are nice for just about everything, but neccessary for anything aimed at a non-developer, especially for a GUI program. They are *absolutely essential* for something put up for download at a place like Version Tracker!

      4) Make sure your descriptions on items you put up on sites like Version Tracker let the user know exactly what they are getting into. Is it an X Window, Java, Unix command line, Cocoa, Carbon, Classic, library, or whatever program? What type of install procedure is neccessary? Does it need specialized knowledge to run? If people know ahead of time whether or not they can install and use the program, they can just choose to not download it, and save you oodles of time supporting them.

      5) The form letter FAQ to answer simple questions that several people have mentioned sounds like a great idea. Another thing that I have had done to me is to send an auto-response saying that you got their email, and giving them a random response number that they have to email back to you. Your auto-responder then sends them another email saying that you got their email, and giving them a random response number that they have to email back to you. Repeat until the user gets bored and goes off to find their own answer (usually tossing your program). Mind you, this won't endear you to your users, but it should help with your sanity. ;)

      One month until Mothra returns!
      (With Godzilla, King Ghidora, and Baragon.)

    2. Re:educate yourselves by Anonymous Coward · · Score: 0

      I wouldn't call Unix-heads the "intellectual elite". The ability to make and install gnu packages does not make one a genius.

  41. For the best. by Enahs · · Score: 3, Flamebait
    It's pretty obvious that Cristoph is screaming "sour grapes" and doesn't fully understand the GPL.



    In his email, he mentions releasing, say, Red Hat Linux with a few changes and no mention of RH, which would be okay. Not nice, but okay.



    Can anyone point out the GPL violation, or is this another Slashdot fuckup?

    --
    Stating on Slashdot that I like cheese since 1997.
    1. Re:For the best. by mrpotato · · Score: 1
      Can anyone point out the GPL violation, or is this another Slashdot fuckup?

      There aren't any GPL violation, and yes it is another Slashdot misleading headline (read: "fuckup").

      --

      cheers
  42. Exactly! by Enahs · · Score: 2
    I'll have to pore through the GPL tonight, but AFAIK there's no violation here...Christoph wants credit for porting, basically. AFAIK that's not required and for it to be required Christoph would have to slap on an advertising clause in his copy of the GPL, which would a.) be a violation of the GPL and b.) would require special permission from all the authors of said ported software.



    Eh, let him resign. Who needs crybabies?

    --
    Stating on Slashdot that I like cheese since 1997.
  43. mac users are understanably upset ... by wobblie · · Score: 1

    because linux / bsd users have robbed them of their martyr-like counterculture image, which was a corporate created sham to begin with.

    Get a life.

  44. Perfect example of why NOT to use the GPL. by Fucky+Badger · · Score: 4, Informative

    The GPL license offers a very beautiful dream, free, unrestricted access to software for the people of the world. No doubt this would be great, free technology for people in the third world countries (including me) and no more gigantic monopolistic companies telling you where to go today. I also believed in that dream, however I tried FreeBSD because I wanted to see how the traditional UNIX was. I could have tried NetBSD but I simply had a contact with FreeBSD first. FreeBSD has only one distribution and, of course, includes many GPL'd programs, something that shows without doubt that BSD hackers don't "hate" the GPL as a general rule, in fact, there is a sense of respect towards of the code written by the FSF and any comment against the GPL starts a never ending flame war in the lists.

    I then decided to follow my ideals, and some years ago I pursued some email with Richard Stallman (RMS for short) on three issues:

    1) The Free Software Foundation should support the efforts against crypto export restrictions in the US. It was suspected some linux distributions were exporting this code but there was no official statement on this.

    He (RMS) agreed that such restrictions were against the spirit of free software redistribution. He included a link to the Electronic Frontier Foundation in the Free Software Foundation's site.

    2)During our email, he insisted I should use the term GNU/Linux, something that sounded perfectly logical although somewhat uncomfortable. I then asked if I could use the term GNU/FreeBSD and GNU/AIX (I used AIX with a complete GNU development system since those parts were unbundled by IBM) since I was using GNU components that were much bigger and equally important (at least to me) as the kernel.

    RMS responded on both cases with a clear " no".

    3) I commented that, given the FSF's objectives, FreeBSD was doing a better job than Linux.

    He (and no doubt many readers) was surprised by this affirmation and asked for an explanation. I reasoned that since the objective behind the FSF was providing free software, and Linux was being heavily commercialized while FreeBSD was not, FreeBSD was nearer to the objectives. In those days, the newly born Caldera's distribution had a lot of commercial goodies and their base distribution couldn't be downloaded anywhere, I also commented that no one could stop the companies like Caldera from gradually replacing free parts of GNU/Linux with commercial elements until they would effectively replace the complete OS (I also mentioned the linux emulation in BSD in another context). To this final point, RMS responded that the only thing we could do was write more free software.

    Nowadays I personally think that Richard Stallman is a good person but he is confused (I hope he thinks the same of me when he finishes reading this article :), and I am not going to analyze the answers RMS gave because that is not the objective of this article. I arrived, however, to two important conclusions:

    the GNU Public License will not save the world,
    there shouldn't be a universal license; different situations require different licenses.

    1. Re:Perfect example of why NOT to use the GPL. by forii · · Score: 1

      I reasoned that since the objective behind the FSF was providing free software, and Linux was being heavily commercialized while FreeBSD was not, FreeBSD was nearer to the objectives.

      Actually, you're using the wrong meaning of "free" here. The FSF itself says: The FSF promotes the development and use of free (as in freedom) software. This is different from the meaning of "no cost" that you claim.

      The first clue that the FSF is not opposed to software being non-free (as in no-cost) is on their page: Most of the FSF's funds come from its distribution service. This is why we urge you to order CD-ROMs and manuals (but especially CD-ROMs) from the FSF when you can.

      The confusion is understandable, as the ability to get sourcecode anywhere without paying for anything other than bandwidth has made many people assume that the "free" in "free software" means that software should be without cost.

    2. Re:Perfect example of why NOT to use the GPL. by ChrisJones · · Score: 1

      This whole article is extremely confused. The Fink maintainer resigned for a number of reasons, only one of which was the supposed ordeal he's been through with these other Mac sites. It looked to me from his resignation mail more like it was general tiredness with the project.

      Firstly, he was being a little unfair by getting into slanging matches with people where he pretty much demanded credit, something he is not granted by the GPL (so that issue is therefore irrelevant).
      In fact, the only thing this article has to do with GPL (and thus utterly negating the "due to GPL infringement" in the title) is that forked.net didn't provide source and removed the license details from binary packages, but that's not even what the Fink maintainer seems to care about. I quote from his email discussion with the forked.net people:

      "My problem is not that you take Fink and
      repackage it. My problem is that you hide the origins and take credit for the work"

      ...and that is just retarded, he can have that problem all he wants and he can whine about it to whomever he wants because he has no right under the GPL or anything else to demand credit for his work. If he'd said "hey, you're supposed to stick the source with that and not take out my copyright statements from the source, or the license agreement from both source and binary packages" then this would probably all be solved by now, at least it would mean that /. got the headline right.

      THINK people, don't just knee-jerk react on the assumption that either the /. headline or article body are the full facts, they rarely are.

      --
      Chris "Ng" Jones
      cmsj@tenshu.net
      www.tenshu.net
  45. Jeshua Lacock is a rat fink. by Erris · · Score: 1

    Jeshua Lacock is a fink, but he either does not know it or he does not care. It would seem he does not care, as he used "fink install". That makes him a rat to me. If there is a real GPL violation, we will hear of it.

    --
    DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
    1. Re:Jeshua Lacock is a rat fink. by sydb · · Score: 4, Interesting

      There is no GPL violation. Read the email exchange. Pfisterer does not seem to understand the licensing terms of the GPL himself. There is no need to 'give credit' beyond maintaining copyright notices, and they don't need to be on the web site, they need to come with the source. Trust me, I'm a GPL bigot.

      --
      Yours Sincerely, Michael.
    2. Re:Jeshua Lacock is a rat fink. by Erris · · Score: 1
      Credit is not really the issue. It's strange that Jeshua would not have a little page on how his software works and that it would include Fink. It may not be required, but it can't hurt. After all, user understanding of software so that they might then use, change and share it to suit their purposes is the whole point of the GPL.

      What looks more sinister from the letters is that Jeshua's derivative work may not be GPL. While he claims, "Further more, our products are distributed under the GNU GPL, so our products may be freely copied and distributed.", he also claims to not understand Fink. I'm an honesty bigot and something here does not add up.

      --
      DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
  46. The Notorious Avi Tevanian? by Anonymous Coward · · Score: 0

    In the resignation link, Chris gives a few links to explain the resignation. The first one is an exchange with a person who signed the name 'avi'. Could this be The same as the Apple VP who is a complete _ASSHOLE_?

    If so, I am understanding much better Chris's attitude...

    1. Re:The Notorious Avi Tevanian? by TheInternet · · Score: 1

      The first one is an exchange with a person who signed the name 'avi'

      Avadis Tevanian's nickname is "Avie."

      - Scott

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:The Notorious Avi Tevanian? by Infonaut · · Score: 2
      Actually, Chris was not dealing with Avie (note the spelling) from Apple. He was dealing with an old, annoying .AVI file that Sparkle somehow couldn't convert to QuickTime. Thus the annoyance.

      --
      Read the EFF's Fair Use FAQ
  47. Hello, by Anonymous Coward · · Score: 0

    What in God's name is a "Taco-snot" ? You people's website owner is emailing me about it. I wish he'd stop.

  48. Apple may have supported GIMP by Anonymous Coward · · Score: 0

    I can tell you for a fact that Apple representatives viewed the GIMP as a priority for porting to MacOS X early on, so I wouldn't be surprised (not a fact) if Apple provided some direct support for GIMP, not just Fink. And I wouldn't be surprised if Adobe found out and got even more p*ssed than they already were from MacOS X's PostScript-compatible Quartz interface stealing their revenue.

  49. This happens all the time by jlv · · Score: 4, Interesting

    There are lots of "developers" out there that take other people's work and include it in their own project, without keeping the license and/or without giving due credit. This happens all the time.

    The only way to police this -- and stop it -- is to go public with the problem. But that has it's own problem -- most no one will care about the problem.

    Notice that Fink went public with these infringements 3 weeks ago.

    It takes making the "public" is glaring away -- via a front page posting at /. That will get the infringement dealt with.

    This will work for big projects like Fink. That means that little projects will get their work stolen from without any real means to fight back.

    I know all too well.

    I worked up what I consider a really clever kludge for blocking banner ads via the Proxy Auto Config mechanism built into Netscape (since 2.0) and IE (since 4.0). http://www.schooner.com/~loverso/no-ads/ I made this kludge right around Netscape 2.02, Spring 1996. (That was my JavaScript hacking days)

    The PAC file I make available has been mentioned by me /. and by others on memepool and metafilter. I release it under a simple license: you may use it or distribute it as much as you like, as long as you don't charge, keep my copyright, the notice that I wrote it stays intact.

    I do this for the fun of it, after all.

    Last year I read in the 5/28 "Gearhead" column in Network World Fusion where he talks about this a spyware blocking software. He mentions that it can also generate proxy auto config files to block web sites with ads.

    Hmmmm, I think.

    I download the software. Yup, there's my stuff inside his package. I go to the author's webpage. His documentation on Proxy Auto Config files turns out to be identical to the my documentation in my PAC file.

    My copyright notice is gone. There is no mention that the PAC file was (originally) written by me. There is no indication the package in question contains works by anyone other than the author of the package.

    I mentioned this in email to the author of the package. I mentioned this in his forum. I mentioned this to the author of the "Gearhead" column.

    This person is still using my ideas, my code, and my documentation in his tool, and still isn't giving credit (or my copyright notice).

    His attitude is: "I got it off some web site, so I can do whatever I want with it.".

    Here's my post to his message board: http://www.morelerbe.com/cgi-bin/ubb-cgi/ultimateb b.cgi?ubb=get_topic&f=36&t=000140

    (psst: don't use his software: he's a plagerist!)

    1. Re:This happens all the time by jlv · · Score: 1

      I forgot to add:

      I do things like my no-ads.pac for my own use and for the pleasure of seeing others use them. That's a common reason for much free software. How do you stop someone from stealing your free work and ... giving it away for free?

    2. Re:This happens all the time by Anonymous Coward · · Score: 0

      That's not Free Software! It doesn't allow commercial distribution or distribution of modified versions. Why not just use a standard Free Software license?

  50. clarification please? by Anonymous Coward · · Score: 0
    based on your last question, does that mean that you don't want people to use your software in anything else that they sell? Even if given full credit, etc?

    Thanks

  51. non-conforming conformists by Anonymous Coward · · Score: 0

    well, the subject says it all!

  52. It IS a GPL violation. by juju2112 · · Score: 1
    Why are people saying that this isn't a GPL violation?

    You must provide a copy of the source code when you redistribute software that is under the GPL license. Forked.net and Openosx.com did not do this. Not only that, but they were both charging for the software that they basically just downloaded and repackaged.

    Furthermore, i'm pretty sure both parties violated parts A, B, and C of section 2.

    From the GPL



    2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

    c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)


    Anyway, it's pretty clear to me that there are a lot of Mac folks out there that haven't a clue about open source. It doesn't look like forked.net or openosx.com meant any harm, though. that they didn't mean any harm -- They just don't understand the GPL.

    It looks like forked.net isn't charging for downloads anymore, and are trying to make it right. So it looks like it's all taken care of now.
    1. Re:It IS a GPL violation. by forii · · Score: 2, Informative

      Why are people saying that this isn't a GPL violation?

      Because it isn't.

      You must provide a copy of the source code when you redistribute software that is under the GPL license.

      Read this exchange. The source for fink was included, along with the source for bzip, tar, etc. etc.

      Not only that, but they were both charging for the software that they basically just downloaded and repackaged.

      Show me the part of the GPL that forbids charging for software.

      Furthermore, i'm pretty sure both parties violated parts A, B, and C of section 2.

      Oh really? Which part? From reading the exchange between Christoph and Jeshua, There doesn't seem to be any issue of modifying code, but instead a matter of giving credit. There is no part of Section 2 that deals with that issue.

    2. Re:It IS a GPL violation. by Anonymous Coward · · Score: 0

      The only reason forked.net started charging for downloads was because of the massive bandwidth they were going through. He had to cover his ass somehow. He wasn't charging for the file, he was charging for the bandwidth.

    3. Re:It IS a GPL violation. by Enahs · · Score: 2

      True, but...

      All the Openosx folks were doing was redistributing the packages the Fink project had made with Installer.app targets Did I get it right? Eh? It's on the Fink website; go take a look.

      Unless the packages themselves are GPLed (unlikely, and likely not enforcable) the only violation would be not distributing source.

      Now, I've not used the Fink packages, but if Christoph had added himself to the list of authors after patching the apps to run on OS X, then the Openosx folks *removed* said reference, then yeah, that'd be a violation.

      --
      Stating on Slashdot that I like cheese since 1997.
  53. uymm. Slanted Journalism here by imneuromancer · · Score: 1

    the GPL violations of various folks was just one of the MANY reasons chrisp quit. I think it is jsut a little skewed to take this one aspect and say, "See, see! Apple has a problem with Open Source!!"

    No, people, it was not Apple or Apple people. The problem came from THE COMMUNITY not from a corporation. And even so, it was only a part of the problem.

    PLEASE read the letter and see for yourself that Mr. Malda is being pretty irresponsible with his journalistic integrity here.

  54. Even Apple dosent have a clue about GPL by Anonymous Coward · · Score: 0

    Even the folks at apple for the most part dont have a clue about what the GPL says, some of the behind the scenes developers do but not anyone I dealt with. Apple modified several GPL applications for us in OSX and Darwin, I requested those changes, via the GPL written offer clause, it took an enormous amount of bitching and moaning to get them , then they asked me what I wanted them for before they would send em, I told them to offer them for download to other users that were having problems finding them, about 10 of us were on a 2 week hunt for some specific items, anyway APple told me "You cant do that" I went off, before they could finish their sentence I told them they better think VERY carefully about what they were saying, another thing was they said for them to provide me with the GPL apps, I had to agree to the Apple public Source liscence, this is what starte the hunt in the first place none of us thought it was right to agree to their liscencing to have to download the apps, round....and round....and round... Bugs the hell out of me I wrote code in some of those apps I was looking for ! I even offered to pay for the redist and media charges whatever they thought was fair, once again as per the GPL

    Wind up of it was they told me since they provided a download even though you have to agree to the APSL to get to the area they were in compliance with the GPL, I informed them that is not sufficient as per the GPL FAQ on just that matter, at that point I suggested they reffer me to their legal dept. , they finally agreed to send me the requested source but after a 2 week battle, the fact that they had to burn me a special CD of GPL components that I didnt have to agree to the APSL liscence shows, normally some are bundled with the ADC stuff and some arent even avaliable for download !, that alone shows me they are out of compliance with the GPL.

    Companies love to make money of the new GPL fad as they see it , get their bugs fixed and features added by the comunity at large but have a problem giving back, when they told me I couldnt offer the GPL apps for download I saw RED. Lets hope this is just due to the front lines at Apple being inexperience when it comes to GPL liscence issues and not the shape of things to come.

    1. Re:Even Apple dosent have a clue about GPL by NDPTAL85 · · Score: 0

      Do you have lots of friends, cause it sounds like you quibble over the smallest of details. Apple provides all the open source software they use as a download either as Darwin or in the Mac OS X Developer Tools. If you want it in some other form, tough cookies.

      --
      Mac OS X and Windows XP working side by side to fight back the night.
    2. Re:Even Apple dosent have a clue about GPL by Anonymous Coward · · Score: 0

      First of all NO they do not provide a download of all the GPL software, either at all or WITHOUT agreeing to the APSL liscence , once we recived the disks that was abundantly clear, even more so than we thought in the beginning, if they did it would have NEVER been an issue, second of all as per the GPL it isnt even required to make available a download, but it is required to provide it physically,

      Not a small detail, you cant pick and choose what parts of the GPL you like or fit you business model.

      And lastly yes I have a lot of friends, probably too many but its always like that when you have something to offer, but its always nice to know there is one more I can count out :)

    3. Re:Even Apple dosent have a clue about GPL by j-beda · · Score: 2
      I am a bit confused. I thought the GPL only required distributing source code to the people you distributed the binaries to? How did you get the binaries?

      It does seem like there might be a conflict between the need to agree with the APSL and access to GPL source, but does the web-based APSL agreement button require you to agree to the APSL for code under the GPL or does it say "I promise to abide by the APSL for APSL code"? While perhaps not ideal, it does not seem too onerous, since obviously you are only interested in the GPLed bits of code available in the ADC areas of their website.

  55. Re:Just so everyone knows... by Anonymous Coward · · Score: 0

    Are you trying to say that the Slashdot effect
    is a deliberate DoS attack?


    At least Slashdot can take what it dishes out, all
    those people slashdot-ing what ever page you are
    referring to were on slashdot not too long ago.
    Heck, the slashdot team even preformed better than
    the CNN weenies on 9/11.



    Great job slashdot team! We thank you for your hard work, and the fact that you give it away for free.

  56. duh, they're supporting *Mac* users by Anonymous Coward · · Score: 0

    let me get this straight, they develop a product to provide software for the Macintosh platform but expect their users to have a clue?

    hello. McFly! Is anybody in there?!?

    (and as his examples clearly show, this guy has PMS)

  57. Attitude Problem by redcliffe · · Score: 1

    It sounds like this guy has a bit of an attitude problem. Okay it was a stupid post, but he didn't need to respond like that. It's not a good way to endear yourself to the users. Nowhere there did they expect him to be perfect, or 24hour support. They just asked some questions.

    Don't get into free software developement if you are not prepared to answer stupid questions.

  58. Never claimed as a GPL violation by barberio · · Score: 5, Interesting

    I hardly ever post comments to Slashdot, but this time I'm going to.

    This article steps over the line and into libal. OpenOSX is not violating the GPL, it never was, and it wasnt even acused of doing so. What did happen is that Pfisterer thought that every redistributor who used Gimp and Frink should point out that he's responsable. Which may seam reasionable, but the problem is you have lots of contributors behind gimp, do they all get credits on the web page and promotional material? Or do you do what *every* other distribution does, and put the READMEs and CONTRIBUTORs files in the documentation and source.

    Acusing OpenOSX of violating the GPL on a high trafic site like this is going to damage them a lot. How about an apology for publishing something that was flat wrong? its what I'd expect from a real news source.

    What have OpenOSX done wrong? Sell open source software CDs at a high mark up, RedHat does that.

    As a long time reader of Slashdot, I'm getting fed up of the Tabloid instincts being shown, and I'd like the Editorial Staff to Grow Up and show some Responsability.

    1. Re:Never claimed as a GPL violation by Anonymous Coward · · Score: 0

      RIGHT ON! I sincerely urge everyone to email rob et al. with this comment pasted into an email, they need to wake up, and more importantly, undo the damage they have caused with this insane story and headline.

  59. Actually; Chris is right by Anonymous Coward · · Score: 1, Insightful

    I don't know what exactly is happening to the crowd on slashdot as I haven't been reading it much lately. However Christoph from what I read in the email exchange was genuinely trying to educate this guy on several different things. First and foremost he was trying to point out the way the GPL works. Secondly he was trying to help macosx or whoever those people are along the lines of not violating the GPL and or BSD. Thirdly all he was asking for was a little recognition, there are alot of installers for windows based machine that say "This installer uses blah" or "Wise Installer or whatever it is blah", the point is blantantly stealing someones code and making some tiny patches and distributing it publically deserves some credit even if it's not stated in the GPL; especially for money, it's called just covering your ass regardless. Last but not least he was trying to help the guy make stuff clear. How would you like if you went to buy a copy of "Said Program" and in the box there was an early access beta of the program but they didn't tell you? From what I can see Christoph is trying to save himself from a barrage of emails asking him to help fix something that he doesn't even know about. When the email discussion starts he clearly states that he found out through a third party. I don't know whether the third party was a developer, programmer or a bitching user. It's not fair to have to be subjected to some companies problems for support when they use your product and don't tell you.

    All in all.. I'd have to side with Christoph.. as a developer and systems administrator I know the frustration that he's going through and it's not significantly burn out. It's releasing free code and supporting and at the same time dealing with people making money of your free work and time, not giving credit where it's due and then subjecting you to their customers barrage of email questions making money based off of your product. It's not fair; I use Mac OSX and I was going to purchase a couple of those cd's to save me some headache but I'll be goddamned if I support a company that doesn't support the authors they make a buck off, via code, recognition and/or money. The GPL wasn't meant to make developers sweat shop workers.

  60. rat... by Anonymous Coward · · Score: 0

    ...fink? Guess the name is appropriate after the violations.

  61. Hmmm by mrcparker · · Score: 1

    This Christoph sounds a whole lot another like Mosfet.

    Read his posts - he flames the crap out of people that begin to piss him off. Yea, he might be an amazing developer, but all the talent and skills in the world won't get you very far if you are an irrational asshole.

  62. Open Note to Christoph Pfisterer by Whatchamacallit · · Score: 5, Insightful

    Having worked customer service for the last 10 years, I have to make this comment. You should not be doing customer relations or customer service in any way shape or form. You simply cannot handle the stress...

    It took me about 3 years to develop an attitude that didn't make me want to kick my cat or yell at people for cutting me off in a gas station after work.

    If you can't take the stress of dealing with idiots and morons, you should not be a project leader/maintainer. Especially for Mac users! (Not a dig or a flame!) But they aren't known for their technical self-help-can-do attitudes. These folks are used to the = MacOS 9 and not a Unix based system like MacOSX. They are used to simple easy to use software and operating systems.

    What I learned was the ability to not give a shit if I pleased these people. Don't get me wrong, I truly care to help people and do so every single day. But I always see the same idiots over and over calling me to walk them through the same exact procedure over the phone. Most of these guys/gals are a communications nightmare who can barely use a mouse and they don't know how to listen nor follow directions. We are talking about 3 hour phone calls to accomplish something that should only take 10min.

    That said, I can relate to what you are going through. I've written over 300MB worth of web pages detailing all sorts of technical data and my own technical teammates still line up at my desk with questions that are answered in the documentation. Heck if the techs don't read it what makes you think the end users will?

    However, it is a crime to just loose it with a customer. Even if that customer is not paying for your services (mine sure as hell aren't...). It was even worse that you publically did it in an open forum. Heck in a professional environment, if I am going to tear someone a new asshole, I take them into a private location where no one else can hear us and I let'em have it.

    What you need to learn to do is to roll with the punches, dodge and weave to avoid the bullets, and still maintain an easy going attitude. I do not carry these frustrations around with me. I have learned to exercise extreme patience. If you cannot learn to do this, stay far far away from customer service positions.

    I do the bare minimum for the idiots and morons but go the extra mile for the ones who are at least polite and pleasant. If an idiot happens to be at least pleasant and nice then they might get extra help.

    Things you could have done:

    1. Made an email template with RTFM and links to the FAQ, etc. in it. The latest versions that have been tested, etc. Just forward these automated responses to the idiots.

    2. You could just ignore the morons, heck you are not making money on this. You don't need to email all of them. I am sure people like Linus ignore emails all the time.

    3. Setup a survey to find out just how many users are actually happy with the Fink project. I bet they outnumber the ones who were pissing you off!

    1. Re:Open Note to Christoph Pfisterer by Anonymous Coward · · Score: 0
      Especially for Mac users! [...] They are used to simple easy to use software and operating systems.

      Kinda makes you wonder why Apple decided to go with hard to use software like Unix, doesn't it? For all their blather about it being "powerful" and "advanced", all they've done is make the Mac harder to use. They would have been better off trying to construct something like BeOS, rather than come up with the bloated mess that is Mac OS X.

    2. Re:Open Note to Christoph Pfisterer by Ecyrd · · Score: 2

      I use the "butt factor". If a co-worker wants to ask me something, I won't answer unless he gets up from his butt and comes to ask me personally.

      The theory is that if the question is not worth getting out of the chair for him, it is not worth answering for me.

      This sounds perhaps a bit rude, but frankly, when someone just shouts from the other side of the room, asking a question he knows he can get easier from you than from a simple look at the manual, he not only interrupts my work, he also interrupts everyone else's work. And that's just plain lazy and selfish.

      Of course, it works for me too: If I really need to know something, I always consider whether it's worth for me to get up and go ask someone who knows as opposed to just trying to search the manual.

    3. Re:Open Note to Christoph Pfisterer by Anonymous Coward · · Score: 0

      "It took me about 3 years to develop an attitude that didn't make me want to kick my cat or yell at people for cutting me off in a gas station after work. "


      It's called "being beaten down by all the authority figures above me". HAHAAHA!!!!

    4. Re:Open Note to Christoph Pfisterer by Blake · · Score: 1

      Things you could have done:

      Or you could do what I do, just shove that anger and frustration deep down inside, and if you ever feel like it's going to overflow, just slam a cork on it, and shove more in...

      Later,
      Blake.
      --
      "Tick, tick, tick..."

  63. Tard. by Anonymous Coward · · Score: 0

    Commercial fishing in Alaska takes but a few months out of the year. it pays extremely well though.

  64. This isn't a GPL violation. by Bowie+J.+Poag · · Score: 2



    What we have here is an ego conflict, and one guy whining about not getting credit. IMHO, OpenOSX has in no way violated the GPL -- If I remember correctly, the GPL does NOT make "giving credit to the original author" a manditory requirement of authorship. Sure, its a nice thing to do, but you're not obligated to do so. However, the GPL does make provision of the sourcecode upon request manditory, and OpenOSX has easilly exceeded this. They've bundled the source with the CD. No request necessary--its right there under your nose.

    What happened here looks more like Fink's author had his feelings hurt when he realized people were using his work without giving him a pat on the head. Welcome to the open-source movement, Cristoph. Thats how it works. If you wanted to be assured of recieving some sort of acknowledgement of your efforts, you should have went with a BSD license, and not the GPL.

    I might also add its terribly irresponsible (not to mention unprofessional) for Slashdot to assert that OpenOSX is guilty of GPL violations.

    No, I don't use a Mac. I don't even have a stake in this whole argument.. I just don't like it when the facts are misrepresented. Read it for yourself.

    Cheers,

    --
    Bowie J. Poag

  65. An old lawyer's joke... by fm6 · · Score: 2
    Lawyer to client: Sir, you have a very good case. Our firm is ready to proceed. Only one small detail remains to be settled: How much justice can you afford?

    That pretty much summarizes the gap between theory and reality when it comes to enforcing legal rights. It's one thing to have a legal right. It's quite another thing to force people to respect that right.

    And this is a practical matter that does not seem to occur to the "software wants to be free" crowd. You can impose all the "copylefts" and "artistic licenses" you want. But when the time comes to enforce your rules for distributing your software, you have to pay some very expensive professionals to make this happen. How are you going to do this if you software is not a source of revenue?

  66. Going Down by Anonymous Coward · · Score: 0

    Fink may have been wronged by the other sites, but one site made amends and that chrisp dude is vindictive as hell. I'm sorry, but he was just plain rude to those people on the mailing list. I think he's about to go postal.

  67. GNU Darwin ?? by Anonymous Coward · · Score: 0

    GNU Darwin is GNU'd too, but most of their base is actually the BSD ports system (no adv. clause). So..no more fink but there is GNU Darwin, what is the problem??

  68. He needs a good sleep.. by Anonymous Coward · · Score: 0

    Coz he kept saying how tired he is.

  69. I agree by Anonymous Coward · · Score: 0

    Mac users are *much* more gay than this mac dude.

    (Who is plenty gay himself. Who the fuck writes out all of Christopher.)

  70. I wonder.. by Anonymous Coward · · Score: 0

    ...if the REAL reason people bail on a project like this is due to an initially poor understanding of the true nature of humans.

  71. Boycott _WAS_ immature by Roy+Ward · · Score: 1

    Please read this before you mod me down ...

    The reason that the boycott was immature is that a boycott needs to be aimed at making things more difficult for the people who are doing the bad things, in order to discourage those bad actions.

    Now who did this boycott actually inconvenience?

    Not Apple ... they were quite happy selling boxes with closed software, just like every other computer maker at the time. Maybe it had a minor effect on people who wanted to work on open source software choosing different hardware.

    The people who were really affected were the Apple owners, not the company, in that we didn't have a good way out of the proprietary software (I used proprietary tools for many more years).

    I had a Mac at the time, and wasn't too happy about the 'Look and Feel' lawsuit (wasn't happy about MicroSoft either) and one of my flatmates, knowing that I had a strong interest in compiler design, tried to get me interested in gcc and other free software. I was quite interested until I found out that 'oh, it won't run on your computer because there is a boycott', so I lost interest and put my energy elsewhere. I didn't have the resources to buy another machine just to do free software stuff, and doing a Mac port would have been a pretty big hurdle to start to use something.

    The loss in this case was to me as an Apple owner, and to the Free Software movement, for whatever people like me didn't contribute.

    For anyone planning a boycott, think through that you are actually aiming at the right target.

    1. Re:Boycott _WAS_ immature by HiThere · · Score: 1

      Sorry you were inconvenienced, but...
      What they really said was "We don't intend to put in any time supporting equipment sold by this vendor. Any."

      I don't see anything wrong with that. The don't put in much time supporting the z-80 either. You've got to make choices when your resources are limited. The Mac commanded a large enough market share that if it had been friendly turf, it would have been a natural addition. But it wasn't friendly turf. Playing in that area might have lead to a lawsuit (whether valid or not, that takes time and money). So staying out was the prudent thing to do. Calling it a boycott was, perhaps, a bit of extreme grandstanding, but it was nothing compared to, say, Apple's 1984 ad campaign.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:Boycott _WAS_ immature by Roy+Ward · · Score: 1

      > Sorry you were inconvenienced, but...

      Well I wasn't inconvenienced much - all it really meant was that at I time that I had a lot of energy that could have gone into that particular free software, that energy went somewhere else.

      > What they really said was "We don't intend to put in any time supporting equipment sold by this vendor. Any."

      I'm a bit curious - who said that? I haven't found a reference to it. This would be quite different than a boycott.

      It's the idea of a 'boycott' over this that I find immature, not the desire to not spend time on Macintosh support.

      The irony is that I'm now running Mac OSX, and guess what the compiler that comes with it is? GCC

  72. Maturity seems to be lacking by macdaddy · · Score: 2

    I don't know about the rest of you, but I took some time to read all of the links provided; the resignation letter and the links that came with it, the email correspondence with the packager of openosx, all of that. I'll probably get flamed for this, but I came away with a feeling that all the involved parties have serious maturity problems. One person takes another person's comments too seriously and blows up at them. One person takes a user's simple oversight and turns it into a haneous crime. chrisp and finyard in the bug tracker were just plain rude at times. Users ask dumb questions. We've all been on mailing lists and in the newsgroups. In fact we were all there at one point or another asking those same stupid questions. If people had flamed us with snide remarks, we would have probably said 'fsck this' and moved on to something else. There's no reason for chrisp to have been rude in the bug tracker, no matter how dumb of a question was asked. That's a responsibility that comes with being in a position such as that. All I can say to the parties involved is either grow up and be adults about this or meet out by the swing set at recess and settle it like the children you're acting like.

    1. Re:Maturity seems to be lacking by Anonymous Coward · · Score: 0
      I'm just an AC, but I agree with your conclusion. I also read the resignation, bugtracker exchanges, and the ChrisP/Jesha exchange. I had to resist the urge to put everyone in time out.

      It reminded me of a scene in the old Robin William's "Popeye" movie. "You owe me an apology.", "No, you owe me an apology". Sheesh.

      When I was younger, I learned that no good ever came from flaming someone in a public forum. It doesn't matter if you're legitimately angry ... you still come off looking like a jerk.

      Count to ten, walk away, calm down. Come back later and write your response. Anyone with two brain cells to rub together will properly figure out who (if either) was the jerk in the exchange.

      Sorry for the loss to OpenSource and especially MacOS X, but someone else (hopefully more mature) will step up to continue work on Fink.

  73. BTW by macdaddy · · Score: 2

    For the record before anyone replies to my message, I do understand the frustrations of chrisp. Dealing with stupid questions can quickly get on your nerves. Doing something with little to no credit also makes you question the worth of what you're doing. However if you do something good and you don't get public credit for it, you shouldn't doubt what you've done. You've already done it. If you doubt yourself after the fact when something doesn't go your way then it wasn't worth doing in the first place.

  74. A big strike against Open Source by Anonymous Coward · · Score: 0
    This is an example of why programming is a better left as a professional occupation. If he had been working at a company with the financial resources to deal with a user base, he would likely not have gotten so fed up.

    This points to the second component of the myth of open source (the first being that there large numbers of people out there capable of writing high quality software who will contribute to your project, which there are not). The idea that writing software, giving it away for free, and then dealing with all the crap is at all rewarding -- is absolute fantasy. Just look how frustrated and resentful Pfisterer became.

    If open source "succeeds" the way some people want it to (i.e., it takes over the majority of software development), that will mean the only way anyone will ever get to program is in a situation like Pfisterer's. All software will be written by unpaid, naïve, and gullible volunteer students, doing everything in their spare time. Such people will only put in a few months or years worth of work, as they will get burned out after a very short time, just like Pfisterer.

    Getting paid to write commercial software doesn't seem so evil when you consider that, does it?

  75. Chris doesn't know deplomacy by sordid · · Score: 1

    I really agree with Chris' attitude towards these groups (or so called businesses). Most of them are creating a "hodge podge" effort at combining a few packages with the gimp, sticking it on a CD and then calling it "their product" and selling it!

    One of the things that really irks me is that when I compiled (I won't say ported because it didn't involve any coding) the gimp and uploaded it to GNU-Darwin, it was available for those people who had the right dependencies to download from the GNU-Darwin ftp (under a contrib folder). But MacGIMP.org came along and listed it on versiontracker.com. Now what a stupid thing to do, it was like they were trying to get people to download it and understand what was going on. Accordingly people wrote in the description how crap it was, because they either couldn't install it or it was "crap because it ran on xwindows".

    Today I notice people uploading debian package files of MySQL and other such things to the same sites. I personally think a lot of it is trash, and out there to confuse people who *don't* know anything about unix rather than to help them understand and use these applications.

    I don't know if Chris will get much support with his attitude towards Tenon though, but maybe he will. I don't exactly know what his issue with them are. Xtools has been around before xdarwin (xaqua), and did at one stage offer more features. It is a typical case of commercial software being beaten by free software, and I think we will begin to see a lot of this happening on OSX as many of the development tools on OSX are free.

  76. I don't understand the problem either by cyberon22 · · Score: 1

    OpenOSX uses Fink to produce a salable good. Where's the problem???

    Christoph Pfisterer wants credit for work other people do using free software. That's like insisting that anyone who uses KWord to write reports or GIMP to make graphics needs to explicitly say so. Push this logic to the extreme and every binary produced by G++ would require a similar notice.

    If this complainant has a problem with people using free software freely, he's the one in the wrong. Oh, and to cover my ass (in case I'm wrong about the GPL) I wrote this message in Netscape 6 under Linux.

  77. Oops by Apotsy · · Score: 1

    (Er, I meant to link to this bug, actually. But that other one was pretty bad, too.)

  78. Boardroom Shakeup by TheInternet · · Score: 1

    to a copy of the 1993 g++ FAQ

    Some very significant management and software changes took place at Apple in 1997 which modified a lot of the variables in this equation.

    - Scott

    --
    Scott Stevenson
    Tree House Ideas
  79. Manuals can really suck by TheInternet · · Score: 3, Insightful

    I would gladly piss off a dozen users who are too obnoxious to bother reading the manual

    Which is fine as long as the manual in question is usable. All too often in the open source world, the manual is useless unless you already know what you're doing. Apache and PHP do a good job of getting the user up and running quickly. MySQL does a very reasonable job as well. Too much software ignores that fact that spending five hours reading documentation just to get one thing to work is an extremely frustrating experience.

    Make the obvious stuff (the purpose for downloading the software) ridiculously easy to accomplish. Make the rest accessible. That will keep a lot of users off your back.

    - Scott

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Manuals can really suck by Erasmus+Darwin · · Score: 2
      "Too much software ignores that fact that spending five hours reading documentation just to get one thing to work is an extremely frustrating experience."

      I certainly agree with you there. I suspect part of the problem is that spending time writing documentation usually doesn't serve to help scratch the "personal itch" that's generally considered the motivation behind free software. I suspect it also doesn't help that it's easy enough to consider the software as "still in development", allowing the developers to put off documentation indefinitely.

      Still, in the case of Fink, the documentation seems pretty straight-forward. Checking the Fink site, there are links for both documentation and a FAQ. The user's guide seems to be pretty straightforward. It has a couple extra details in there (such as explaining the use of pico to edit the user's .cshrc), but it looks like an experienced user could pull out the important details in a few minutes (at most). The FAQ looks like it does a decent job of picking up some of the more esoteric problems that're too detailed to clutter the manual.

      On the other hand, it's possible that the Fink user guide is a little too brief. It's hard to tell without a further understanding of exactly what the actual Fink software is beyond the Reader's Digest description of the project (porting Unix utilities over to OS X).

  80. Photoshop by TheInternet · · Score: 1

    If Apple is financing a competitor, whatever its shortcomings, it gives it a lot of validity, and suddenly 90% of the people who use Photoshop (or whatever) realize that all they do is edit pictures for their homepage

    There may be some percentage of Photoshop users people that don't really need Photoshop, but I suspect this number is quite small. Photoshop is too expensive to be taken lightly, and in additional to several long-run shareware Mac image editors, Adobe sells Photoshop Elements, a watered-down consumer app.

    Everybody I know that uses Photoshop needs Photoshop (or something as full-featured).

    - Scott

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Photoshop by nycdewd · · Score: 1

      i use it myself (PS), full version. i use Graphic Converter more often, it does the fast image editing i most often require and with very low overhead: low RAM usage, launches in a half of a blink... as opposed to PS on both counts.

    2. Re:Photoshop by Shadowmist · · Score: 1

      For the market that buys Photoshop, as opposed to bootlegging a copy, installing it on their machines, and then never touching it after getting lost among the menus, there IS no compeitition.

      The GIMP and others are fine within their limits, but they don't even operate in the critical fields that Photoshop professionals call their bread and butter. And when you count in the plug-ins which are a cottage industry all to themselves, Photoshop isn't so much a program as an operating environment.

  81. culture clash by rodentia · · Score: 1

    I don't know about anyone else, but reading your brave alternatives and matters of integrity makes my hair stand on end.

    --
    illegitimii non ingravare
  82. No, you miss the point. by Anonymous Coward · · Score: 0

    *His* point was he wants credit anyway, because that's the right thing to do. I would too. He never said the GPL demanded it.

  83. Moral Right by tubs · · Score: 1

    I know in Europe there is a "Moral Right" that goes along with copyright, which can be signed away - basically it includes the right to be the named Author(s) of a piece of work.

    If the same is "Moral Rights" are available in the US then surely it becomes a case of simple copyright infringement, rather than a GPL infringement?

    (If you look in any recently published UK book you will usually see 'The moral right of the Author has been asserted')

    --

    try to make ends meet, you're a slave to money, then you die

  84. Why does everybody use GPL? by Anonymous Coward · · Score: 0

    Please have a look at this and see if you still want to.

    And why do so many projects use the GPL but put in exceptions to it? Why bother with the GPL at all?

  85. He didnt resign over violations.. by Thomas+Charron · · Score: 2

    For crying out loud. He didnt resign over the violations. He resigned becouse he didnt feel he was being given credit where he thought it was due. Totally understandably. In none of the above cases where there ANY GPL violations. If anything, I'd say wanting to recieve public credit is, in part, against the 'feeling' of the GPL. It shouldn't be, but the GPL basically says 'Take it, use it, modify it, pass it on'. It doesnt say 'Ensure that you've bent over backwards to stroke the ego of the individuals that wrote it'. Ok, last statement not really fair the the above individual, becouse credit IS deserved, but I dunno, hes so fed up, he sounds kinda whiny..

    --
    -- I'm the root of all that's evil, but you can call me cookie..
  86. All I know is... by drowsy · · Score: 1

    I just started using fink two weeks ago. It works and does not destroy the system in the process. If the only cost of the software is time for education and time for giving thanks to the author, then what is all the user whining about?

    Running apps like gnumeric, the GIMP and Dia on the Mac makes my mac much more useful.

    apple fans, projects like these come just in time, as the old way of just pirating software won't cut it soon, so get used to a little work to make good software happen on your mac. Get used to the fact that good software is sometimes made by difficult people and there is no marketing to shield you from them. It is a small price to pay.

    Thanks chrisp and all of you who actually contribute to authoring, testing, supporting software like this.

  87. What's the issue? MacGIMP posted the source by ubiquitin · · Score: 1
    --
    http://tinyurl.com/4ny52
  88. Fink should start using a newsgroup by musicmaster · · Score: 1

    There are a lot of reasons why people don't use manuals and FAQs. Think of: lazyness, not being able to understand it, difficult to find your way, no manual can answer all questions. "What is the smartest way to do this" is a typical question where a manual usually doesn't help.

    If you have a newsgroup users can exchange experiences and the maintainer of the software needs only to jump in when the users can't help each other.

    Unfortunately Fink doesn't have a newsgroup. It only has a mailing list. This has a much higher threshold. Many people are prepared to share their knowledge. But they want it at their time and speed. The don't like to be spammed by a mailing list when they are busy with something else.

    In such way Pfisterer could have kept the users at a bigger distance and spent more time programming.

  89. But that's what it used to be! by Jill+Bates · · Score: 1

    Mentality won't change in a night, if you feel too tire to fight the battle, do take a rest, it is good for you. But don't give up, just don't give up because the future is still bright.

  90. Couldn't you just do this? by Anonymous Coward · · Score: 0

    "Added all the cool Brianux stuff, whilst modifying existing code to suit."

  91. Fraud laws still apply by David+Jao · · Score: 1
    In the US there are laws governing fraud which are separate from the laws governing copyright. A copyright license such as the GPL in no way invalidates the protections afforded by laws governing fraud.

    Misrepresenting the authorship of a software program such as Linux, depending on the situation, could easily be prosecutable as fraud even if you have a copyright license.

  92. Re:GPL: Troll or Misunderstanding? by Royster · · Score: 2

    The weakness is that the GPL would probably lose in court, to some degree. This is because copyright law and, in many ways, the legal system, in the US and elsewhere, were never designed to work in accordance with the common good, especially when it comes to issues of property, and even moreso when it comes to the issues of intellectual property (really just an illusion of modern society).

    Oh, what an excellent troll!

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  93. If you want credit, it'd better be in the contract by mactari · · Score: 2, Informative

    The fink author should talk to Warren Robinette, the author of Adventure for the 2600. Or in a more recently example, speak to the authors of anything coming from Apple.

    What these people have in common with the author of Fink is that they wrote software for which they didn't receive obvious credit (Apple recently removed credits so that people couldn't target specific Apple employees for recruitment to another software house). Just as not getting specific credit is written into Apple employees' contracts and was written into Atari programmers (one reason so many of the best worked for Activision), the "contract" your essentially "sign" when releasing GPL software doesn't have any provisions to retain who did the work.

    One might take a cue from Mr. Robinette and include something in the code that gives you specific credit -- he created the first easter egg in a video game that displayed his name on the screen as the game's author (take a look at the end of the decompiled source to the game. Download the zip on this page: http://www.biglist.com/lists/stella/archives/20011 1/msg00086.html).

    Or one might take an even better cue from those who worked for Activision: If it's key for you to receive credit for your work, make sure it's in the contract!

    --

    It's all 0s and 1s. Or it's not.
  94. Tenon... by pfistech · · Score: 1

    Just for the record, my problem with Tenon is not Xtools, but the Gimp package they offer for download. I looked inside it, found that it looked very much like it was built with Fink, and contacted Tenon about it. They were very quick to respond and confirmed that they used Fink, forgot to include credits and were in violation of the various licenses by not providing source (GIMP, glib, gtk+, gnome-libs, gettext and some other things included inside the .app bundle are GPL/LGPL). I was told they'd correct the situation in "a few days". That was on September 25, and when I got back to them some weeks later, I was simply told their lead programmer was very ill. Still nothing has happened to date...

    --
    -chrisp

    "If that makes any sense to you, you have a big problem."

  95. He's right, dude. by cduffy · · Score: 1

    One can, under the GPL, provide binary software and source only on request, and one can charge for that initial binary.

    My company does just that with the "professional edition" of our linux-based embedded systems development environment, though it's based on Free software.

    1. Re:He's right, dude. by seann · · Score: 1

      but you can not charge for access to the source
      (say if I lived 2 minutes away from your said company, and provided the means for transferring)

      --
      I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
    2. Re:He's right, dude. by cduffy · · Score: 1

      You're right, we can't charge for access to the source -- for people we already gave the binary to. If you didn't buy (or otherwise acquire from us) the binary, we don't have to give you the source.