Slashdot Mirror


theKompany's Shawn Gordon On The GPL

replicant_deckard writes "In this short but insightful essay Shawn Gordon, the founder of theKompany, explains why GPL doesn't work for software companies producing graphical and end-user friendly stuff. This reminds us that GPL has so far been useful just for infrastructure-level hacker stuff like operating systems, databases etc. " Of course, it's been used for end user - OpenOffice, GAIM, and other projects.

350 comments

  1. Attitudes will change by Tebriel · · Score: 1

    Some people just want to be "rebels" and just cop attitudes to be different. As more people come to know/love Linux, the attitudes will come around from "rebels fighting The Man(tm)" to "using the right tool for the right job."

    It'll just take some time.

    --
    The Blaster Master Fighting for Truth, Justice, and Evil Pie since 1979
    1. Re:Attitudes will change by Anonymous Coward · · Score: 1, Insightful

      BSD is for people that love Unix.

      Linux is for people that hate Windows.

    2. Re:Attitudes will change by Anonymous Coward · · Score: 0

      Good point. Many people need to start using their heads instead of blindly following what Stallman has to say.

    3. Re:Attitudes will change by Anonymous Coward · · Score: 0, Flamebait

      GNU/Linux is for people that love users.

      *BSD is for people that love vendors.

    4. Re:Attitudes will change by Anonymous Coward · · Score: 0

      "(Score:1, Insightful)"??

      Moderators - can't live with 'em, can't shoot 'em.

  2. Wrong URL by BoyPlankton · · Score: 5, Informative
    1. Re:Wrong URL by Anonymous Coward · · Score: 0

      subscribe today!

    2. Re:Wrong URL by zeugma-amp · · Score: 1

      I'm entering this fairly late in this thread's life judging from the number of comments already in it, but I'd like to make a couple of comments.

      I use the Quanta+ editor most of the time for my html editing because I really like the way the program works for the most part. (lack of configurability of keyboard shortcuts is a big minus though)

      Much to my suprise, upon visiting at theKompany's website, I discovered that they actually had a retail version of the product that seems to be a bit of an upgrade from the version I'm currently using. "Cool!" thought I. I'm not one of those folks who has a genetic aversion to purchasing software, and I am perfectly willing to do so when I find something that really works well for me. (I'm the only person I know who has a registered copy of pkzip.)

      I downloaded the 'time-limited demo'. I figured that it would be one of those deals where the program wil run for 30 days or so, and then self-destruct itself. Wrong! The program will only run for 5 minutes! After the 5 minutes is up, you are prompted to regester, and if you don't it gives you an opportunity to save your files, then exits! What a crock-o-shit!

      There is no way I can comfortably evaluate this software, which I was alreay greatly predisposed to purchase under those conditions. Here is a major example of cripple-ware destroying a sale. I can't say for sure that I won't buy it because I find quanta+ so useful, but I've already noticed some inconsistancies in the way the programs work that make me slightly hesitant to make the change now. Couple this with the fact that you can't gain any kind of familiarity with the crippleware version, and I have to say that it's time for me to go looking for a new editor again.

      Sorry for the rant, but it kinda hacked me off.

      --
      This is an ex-parrot!
  3. And there's Mozilla... by samrolken · · Score: 2, Interesting

    Mozilla is (partially) GPL too. There are good and bad sides to the GPL... it's a tricky issue for sure. There's a good criticism of it here... in my opinion, there are extreme views either way. But, a company (or a Kompany) has to make money. But really, a copyright and its terms would be just as enforcable on open source code as it would be for a fiction, paperback book, wouldn't it?

    --
    samrolken
    1. Re:And there's Mozilla... by nat5an · · Score: 4, Insightful
      But really, a copyright and its terms would be just as enforcable on open source code as it would be for a fiction, paperback book, wouldn't it?
      A paperback book has a sort of built in copy deterrant: it's really hard to make a copy of it. I mean, print is analog, so to make a copy of a paperback book you'd have to either: 1) Photocopy every page, 2) Scan and OCR, then proofread every page or 3) Type the book into your computer manually. It comes down to an economic question, is it really worth someone's time to make that copy rather than just pay $7 for a legal copy? In the case of books for the most part, the answer is no. For software, it's much easier to copy, so the answer in many cases is yes, the time spent cracking or copying is worth it. Hence the only deterrants to copying software, even open source, are either legal penalties or moral qualms.
      --
      Head down, go to sleep to the rhythm of the war drums...
    2. Re:And there's Mozilla... by Anonymous Coward · · Score: 0

      fortunately the hard part of copying a book only needs to be done once, which is why sites like gutenberg.net can exist.

    3. Re:And there's Mozilla... by ichimunki · · Score: 1

      You left out an option WRT to paperbacks. Scan each page as an image. Distribute as PDF or HTML bundle. With a page-feeding scanner (they do make those, right?) or a decent digital camera and a little bit of very unsophisticated software, this process is largely automatic and probably not even that time-consuming. This method reduces entirely the analog issues encountered with photocopying and doesn't require the extra effort of OCR. This method also has the benefit of preserving layout and illustrations exactly. I have heard, but not seen, that there is a small warez-type scene that does this already, but that it will grow in the near future seems inevitable. Even the FBI is involved (legally of course), check out their FOIA Reading Room. Keep in mind that once the scans are done, duplication is nearly instant and no further degradation of quality is found.

      --
      I do not have a signature
    4. Re:And there's Mozilla... by Anonymous Coward · · Score: 0

      I don't think the critic on morons.org is good at all, really. It reports about a parallelism established between Microsoft (in its struggle against Netscape) and GPL. It says: as microsoft did with netscape, FSF give away for free thier products to put other programmers out of market.
      I think that such an opinion is so absurd... one can *have* a GPL software in his hands not just use it, as a IE user can.
      I think it's a big difference

    5. Re:And there's Mozilla... by Fjord · · Score: 1

      And yet you can still find all of the Harry Potter books on Kazaa

      --
      -no broken link
  4. Why does everyone confuse the GPL by TrollMan+5000 · · Score: 4, Insightful

    With "Public Domain"?

    It's still a copyright(?) license, just not nearly as restrictive as a traditional license.

    I'm all for reasonably priced software, but giving it away for free often isn't.

    1. Re:Why does everyone confuse the GPL by Anonymous Coward · · Score: 0

      Well, because if 1 (one) single user buy the GPL code from theKompany, they can share it with everyone they like.
      Have you seen the warez scene in action?
      It is higly effecient, and then if it is LEGAL to distribute the code, I don't think it will go any slower.

      //lean

    2. Re:Why does everyone confuse the GPL by V.P. · · Score: 1
      Have you seen the warez scene in action? It is higly effecient, and then if it is LEGAL to distribute the code, I don't think it will go any slower.

      Think again. If it is legal to distribute the code, they won't bother.

    3. Re:Why does everyone confuse the GPL by dup_account · · Score: 1

      What the person was saying is that one person could pay for the GPLed code and then put it on SourceForge for the rest of the world to download.

  5. So Why Use It by Daveman692 · · Score: 1

    So if this GPL liscense is so bad why do so many projects use it? Look at Sourceforge, everybody on there uses it. Also what is the difference between the GPL and the GNU liscense and why do we see them written as GPL\GNU?

    1. Re:So Why Use It by LinuxInDallas · · Score: 2, Insightful

      Most of those projects don't plan on trying to make money. A vast majority of those projects are by people like you and me who have an itch to scratch. If someone else finds it useful, then great.

      I think Shawn Gordon is right in saying that for a user-friendly piece of software there is no money to be made in services because the goal of the software is to be easy to use. If they meet that goal, no one needs the service.

    2. Re:So Why Use It by Anonymous Coward · · Score: 1, Insightful

      now go back and look and actually tell me how many of those projects are actually usuable by the average person (ie consistent UI, help files, manual, etc.).

      It's not that the GPL is bad but rather with few exceptions because you can't make money on GPL software the programs don't get the "polish" that most people expect from their programs.

    3. Re:So Why Use It by LordNimon · · Score: 5, Insightful
      The people who choose the GPL for their software do so because they don't care about making money but they don't want anyone else to make money. The software is done on the programmer's free time as a hobby, and the GPL allows others to use his work without giving them to opportunity to make money from it.

      A programmer who use the GPL see it as a tool for distributing code that he wants to write. The programmer knows that no one will be able to do more with the software than he can. Since he doesn't care about commercial concepts like support and ease-of-use, the GPL allows him to do only what he wants to do with the code, and doesn't give him any incentive to do more. How many times have you emailed a developer of a GPL'd program for some feature or help, and gotten a reply along the lines of, "You have the source code, you figure it out!"?

      Frankly, I like the idea. Without the GPL, a lot of programmers who don't want to worry about support and end users constantly bugging them for new features would never have released their programs at all.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    4. Re:So Why Use It by October_30th · · Score: 1, Insightful
      Indeed.

      The argument is so simple and brilliant that I can't but wonder why no-one else has said it out loud before.

      If you license your software so that the only thing you can charge for is service, then why should you make the program easy to use? That would just deprive you of the only way you could make money with it. Combine that with the elitist geek bullshit about how "real men" should only use programs that are difficult to learn and use (emacs, for instance, is an extreme example of this - a bloated 23 MB package with absolutely incomprehensible key-bindings) and you see why OS desktops are so full of crap.

      --
      The owls are not what they seem
    5. Re:So Why Use It by Anonymous Coward · · Score: 0

      Because most zealots have no idea what a license is, let alone what the GPL is.

      Just read most /. posts. It is not hard to see people on here wanting to apply the GPL to everything under the sun, whether the idea of a license applies or not.

      Quite a number of /. readers would cry out to GPL their beowolf cluster of turds, they are just that stupid.

      It is sort of a good thing and a bad thing. A good thing, because of all those projects, most peoples intention probably is Public Domain, they just don't care who uses it for what. A bad thing, because they just don't get it, what the down sides are, what might be a better license for their intended purposes, etc.

    6. Re:So Why Use It by ergo98 · · Score: 1

      Most of those projects don't plan on trying to make money. A vast majority of those projects are by people like you and me who have an itch to scratch. If someone else finds it useful, then great.

      That explains the BSD license (which is a funny name because the BSD license really isn't so much of a license at all, but rather a lack thereof) more than it explains the GPL license. The BSD license is saying "Here you go world : Some source. If you find it useful then great". The GPL license is saying "Here you go world : Some source. To use it you must sign onto the Borg Collective though.". It is not a misnomer to call the GPL a virus. I'm not trying to start a flame war or to troll, but truly the BSD license is the "selfless" license, and the GPL license is asking for something in return (which is compliance). To each his own I suppose.

    7. Re:So Why Use It by LMCBoy · · Score: 3, Interesting

      How many times have you emailed a developer of a GPL'd program for some feature or help, and gotten a reply along the lines of, "You have the source code, you figure it out!"?

      Never. Not even once, and I've been on both sides of that conversation, many times. I don't buy your argument that a programmer of GPL'd software has no incentive to support or improve the program beyond what they personally see fit to do. I get a huge kick out of the fact that people use and enjoy my program, and I've made a large number of changes based on user feedback. I think the same can be said for many (if not most) GPL'd programs, including all of KDE.

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    8. Re:So Why Use It by October_30th · · Score: 0
      I fully agree with you.

      I have been on the broadband since 1992 and used *nix and GPLd stuff on a daily basis even before that. It is truly disappointing to me to watch these young "GPL Talebans" coming out of the woodwork and calling out for a dictatorship of software licensing.

      I used to be all gung-ho for GPL since I thought that it would be necessary for software freedom. Wrong. The freedom the GPL gives you is the "freedom" of a religious cult.

      Avoid it all costs and use anything else instead of it. Even closed source is better.

      --
      The owls are not what they seem
    9. Re:So Why Use It by ftobin · · Score: 2

      How many times have you emailed a developer of a GPL'd program for some feature or help, and gotten a reply along the lines of, "You have the source code, you figure it out!"?

      Interesting you ask this. Anyone who's written to me asking questions about my software always gets their question answered. I take pride whenever someone asks me a question, because to me, it means that I have another person using my software. It's definitely an ego thing, and might not scale if I got dozens of people asking me questions every day, but for now, it works, and I like to think my users are happy.

      Oh, and if someone mailed me with unreasonable requests, I would never say anything along the lines of "use the source luke", but probably more along the lines of "That isn't a high priority for me" or "That would not fit well within the scope of the program", both of which would be entirely accurate statements.

    10. Re:So Why Use It by efgbr · · Score: 1

      The people who choose the GPL for their software do so because they don't care about making money but they don't want anyone else to make money.

      This is completely untrue. The GPL says you can redistribute the software, and you can also charge for it.

      There's an endless number of companies making money by selling free software.

      Since he doesn't care about commercial concepts like support and ease-of-use,.

      Support and ease-of-use are not commercial concepts. Free software is easy to use, and there are _a lot_ of people and companies providing support for free software.

      --
      evandrofg

    11. Re:So Why Use It by Anonymous Coward · · Score: 0

      I have no objection to you making money. But if you have to withhold source to do it, you want a monopoly on the right to improve the code. Since work for hire is the only ethical business model for software development I know of, the degree of control you want over your customers is unacceptable. The GPL is legal technology with which I can refuse to subsidize such an assault on the free market.

    12. Re:So Why Use It by istartedi · · Score: 1, Offtopic

      The people who choose the GPL for their software do so because they don't care about making money but they don't want anyone else to make money

      Almost. You just need to add from software sales on the end.

      GPL'd software makes plenty of money for distributors, consultants, and businesses that run servers.

      A lot of people fail to make the distinction. What if there were a strong GPL community for music? Then musicians would allow the RIAA to distribute without ever signing them, and they wouldn't allow other musicians to cover their tunes under contract.

      I get a real kick out of people who whine about the RIAA's contracts, but think IBM using Linux is great for programmers.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    13. Re:So Why Use It by Anonymous Coward · · Score: 1, Insightful

      The people who choose the GPL for their software do so because they don't care about making money but they don't want anyone else to make money. The software is done on the programmer's free time as a hobby, and the GPL allows others to use his work without giving them to opportunity to make money from it.

      I'd substitute "making money" with "limiting access to the source code". GPL is not about money at all. Why make it look like it is?

    14. Re:So Why Use It by LordNimon · · Score: 1
      GPL'd software makes plenty of money for distributors, consultants, and businesses that run servers.

      In other words, everyone but the programmer. I think you just proved my point, thank you!

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    15. Re:So Why Use It by LordNimon · · Score: 1
      This is completely untrue. The GPL says you can redistribute the software, and you can also charge for it.

      So what? It also says you can't stop anyone from re-distributing it for free. So maybe you can charge for it, but then your first customer can put the code on some ftp site and everyone will get the code from there instead. Granted, you no longer have to pay for the bandwith, but this is still a lousy business model.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    16. Re:So Why Use It by Anonymous Coward · · Score: 0

      What do you think consultants do? To my mind, the original author should have found people who'd value the software highly enough that they'd pay for the labor of creating it before they even started.

    17. Re:So Why Use It by Anonymous Coward · · Score: 0

      If BSD people are all about freedom, then why do they rail against the people who have chosen the GPL?

    18. Re:So Why Use It by Anonymous Coward · · Score: 0

      Why can't the distributors and businesses hire programmers. And what do you think consultants do? Count eggs?

    19. Re:So Why Use It by dup_account · · Score: 1

      Which is why some much software is released under GPL. People want to give their stuff away, but they don't want some company to wrap it up as start selling it as their own. GPL ensures that the original author still gets credit for their part, and that the repository of useful free software continues to grow.

    20. Re:So Why Use It by dup_account · · Score: 1

      I believe that during the up times last year that is what happened. There were frequent messages posted about so and so who developed such and such being hired by xyz corp to further develop so and so's project.

    21. Re:So Why Use It by dup_account · · Score: 1

      IMHO The people who argue that they need to close their software are the people who fanatize about becoming super rich from the program, or putting a bunch of development up front and then living off the results. But in reality, even if you close your software and charge for it, most of the time you will at most be able to make a living for yourself and maybe a couple others (if you're lucky) And I suspect that most of that living will come from consulting and specializations to the product for specific customers....

    22. Re:So Why Use It by rusty+spoon · · Score: 1

      IMO The people that argue so vocally about wanting GPL software are those that either:
      a) have yet to get into the real world
      b) have yet to pay their own bills
      c) have yet to actually create something
      d) all of the above

      The logical end result:
      Student goes to school to learn CS, whilst there creates OS(GPL) project and puts another closed source business on the edge. Student leaves school and moans about lack of gainful employment. Student realises after all the years of schooling that the only thing learned is how to kill the goose that lays the the golden eggs. Student practices "want fries with that" and "wanna go large" while thumbing the stuations vacant.

      It also seems to me that those truly vocal already have a career of being vocal. Their hacking days a distant memory with no need to now live from software creations, instead just a need to be ever more vocal.

      What you suspect and reality are worlds apart.

    23. Re:So Why Use It by arsaspe · · Score: 3, Interesting

      You pretty much nailed it with that statement. I've written a number of GPL'd programs, my current project being phpShare. I originally wrote it for personal use, but decided that it would be a good idea to give something back to the community, However I didn't want some company just stealing my hard work. The GPL fits that perfectly. I don't use it because of some political notion that all software should be free, but because it's the best fitting licence for my needs. If a company wants to sell my code commercially under a non-gpl licence, I can decide whether to give them the right to use it (possibly for a modest fee), or force them to abide by the GPL's rules.

      If I wanted to start my own company and write software commercially, I most likely wouldn't use the GPL. I would probably release various parts of the code because I believe in Open Source, but I do not believe the GPL alone is commercially viable long term. Yes, there are companys that are starting to make a profit selling GPL'd software, but most of the revenue comes from services, not the actual sale of the software.

      To sum it all up, the GPL is a great licence that is best suited for "part time" projects. It has proven that the community can come togethor and write some excellent software, BUT it is not the licence-to-end-all-licences. the Unix mantra of the right tool for the job applies here- use the right licence for the job at hand.

    24. Re:So Why Use It by Anonymous Coward · · Score: 0

      HA.

      Software SHOULD be free. What a quick way to belittle the process.

      Do you also think health care should be free? If so who is going to pay people who spent 8 years + in med school?

      Oh wait, they can charge for the after surgery consultations.....

    25. Re:So Why Use It by askgopal · · Score: 1

      How many times have you emailed a developer of a GPL'd program for some feature or help, and gotten a reply along the lines of, "You have the source code, you figure it out!"?

      Never. Being a free software (free as in both price and freedom) developer myself (http://www.developercentral.org), I have made changes, fixed bugs upon user requests.

      The software is done on the programmer's free time as a hobby, and the GPL allows others to use his work without giving them to opportunity to make money from it.

      Yes, I do accept the fact that I'm working for a cmopany that doesn't do free software but at free time, at home, I write free software. Its like helping your neighbor, helping other people who can't afford to buy expensive stuff, helping developers who don't know how to do some stuff... and I really enjoy writing free software and I'll continue to do it. :-)

      With proprietary software, you can't add some new feature, fix some bug I've made and stuff like that!

      Writing free software is a way of life.

      --
      Gopalarathnam V. Registered GNU/Linux User #218746 http://counter.li.org Please avoid sending me Word or Powerpoint
    26. Re:So Why Use It by Anonymous Coward · · Score: 0

      > There's an endless number of companies making money by selling free software.

      Don't you think you should exaggerate your point a bit, someone might miss it if you don't ;-).

    27. Re:So Why Use It by Anonymous Coward · · Score: 0

      But if you sold the software to a company, why should you control it?

  6. Um, no.... by Anonymous Coward · · Score: 5, Insightful

    There doesn't appears to be anything in the essay that suggests that "GPL doesn't work for software companies producing graphical and end-user friendly stuff." It *does* note -- and this is no shock to any of us -- that GPL is inappropriate for commercial software, but "graphical and end-user friendly stuff [sic]" isn't a complete subset of the former.

    -Baka!

    1. Re:Um, no.... by SteveX · · Score: 2

      I think the assumption was that "graphic and end-user friendly stuff" is consumer-level software, software where the services model doesn't really make sense.

      This has been one of my concerns with the whole services model: The goal of (consumer) software development should be to make software that doesn't need services.

      Software doesn't wear out or rust; paying a programmer the way you pay a plumber won't work.

      - Steve

    2. Re:Um, no.... by jat2 · · Score: 1
      Actually, what I took away from the article was that the more "end-user friendly" a (free) piece of software is, the less you will need to pay for support. Thus, we have the author's claim that the pay-for-support business model that works for operating systems under the GPL is not nearly as effective (or doesn't work at all) for end-user friendly software.

      That is why the original essay gives the analogy of selling software in a retail store versus giving it away for free and selling support.

    3. Re:Um, no.... by Bodrius · · Score: 3, Insightful

      Also, getting an application to the point where it's "user-friendly" enough not to need support costs a lot of money, and not exactly in development.

      Linux depends on relatively tech-oriented people to not only develop the software, but also to use it, and design the user interface according to what they need.

      These are people that are usually intelligent enough to read the documentation and cope with an interface that might not be exactly intuitive. These are also people with their own subcultures, that find intuitive what the mainstream definitely does not: why does more read text? because it's more than cat. why less? because less is more! now let's learn 120 keyboard shortcuts so we can save 2 minutes a day of typing time!.

      The "scratch an itch" model is not the best way to design a user interface for end-users. Even when an attempt is made, quite a lot of the techie users complain about the "dumbing down" of the interface, for good reason... they have different needs than the typical end-user. It follows that they will develop to meet their own needs.

      Of course, attempts are made to develop "end-user-friendly" interfaces in open source programs, but the most successful of those UIs happen to be copies of someone else's design (KDE/GNOME/etc).

      Designing a really good new GUI for end-users, be it for the OS or for some graphical/art app or something like that, requires input from non-tech-oriented users. People who are not likely to be using Linux in the first place, and who are also unlikely to become beta testers without a very good reason.

      I can think only of two good reasons to get a LOT of users to provide input, assuming you have the interface designers to analyze the data: you're have enough marketing to convince people to volunteer (costs money), or you give them money (costs money).

      The GPL-model tends to save on development costs, but I don't see how could it save on these expenses, and it obviously takes away a revenue source that covers for it (and since user-friendliness means less support, the new revenue source is in direct conflict with that goal). That would seem to indicate that the GPL is not appropiate for such applications, unless their UIs are imitations of propietary ones.

      --
      Freedom is the freedom to say 2+2=4, everything else follows...
    4. Re:Um, no.... by LinuxInDallas · · Score: 1

      Of course it wears out. Don't you know that's why Microsoft forces people to upgrade to the latest and supposedly greatest? If they didn't you'd spring bit-bucket leaks all over the place.

    5. Re:Um, no.... by Florian+Weimer · · Score: 2

      You mean it's not suitable for commercial off-the-shelf software, don't you?

    6. Re:Um, no.... by Ilan+Volow · · Score: 1

      Too true. Somone once did a study showing that every $1 spent on usability design saved $100 in tech support costs.

      --
      Ergonomica Auctorita Illico!
  7. Well, There's Your Problem by The+Gardener · · Score: 5, Funny

    I had RMS come to me on this product to make sure we weren't violating the GPL, and he admitted that we were not, but in the course of the conversation he proceeded to project onto the KDE project aspects of theKompany in a totally inappropriate fashion and was very negative about KDE in this regard.

    He talked to RMS; always best avoided, at least without shielding. That's enough to throw anyone off their game.

    THe Gardener

    --
    --
    1. Re:Well, There's Your Problem by renehollan · · Score: 5, Insightful
      Having dealt with RMS with regard to the use of GPL software in a commercial environment, I don't find his "policing" of the GPL unreasonable.

      There are a few sticky issues (like pre-release distribution of binaries only to outside contractors because you don't yet have a clean source release mechanism), but with proper planning, even these can be overcome.

      As for selling GPL source, this is permitted, though I thought that there was some cap on price, based on reasonable distribution expenses (media, shipping, overhead, etc.)

      --
      You could've hired me.
    2. Re:Well, There's Your Problem by 10Ghz · · Score: 2, Funny

      So RMS hates KDE? My God, who would have guessed! I am shocked! Shocked, I tells ya!

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:Well, There's Your Problem by bleuchat · · Score: 2, Insightful

      If there is a cap on the price it is only a "gentlemen's agreement" because it's not in the GPL. It's just one of the things he was talking about when he said that the GPL is vague in some areas.

    4. Re:Well, There's Your Problem by ftobin · · Score: 2

      If you write software and release under the GPL, you can charge whatever you want. It's only the recipients that are limited by in what they can charge for re-distributing.

      I think one of the 'issues' with the GPL is that the 'free beer' part of it tends to be the dominant image in most people's minds. It would be nice if GPL'd software could be non-free-beer yet Software Libre. Unfortunately, if we did this, we would likely end up with a situation where monetary figures start trampling on the Libre aspect.

      For example, consider if the GPL allowed recipients to charge. If they charged $10, this is reasonable to most people, even if the distributor got it for free beer. However, if they charged $300, this gets out of control, and starts trampling on idea that the GPL requires you to pass along the same rights.

      If we could resolve this issue, I think a lot of people's worries about the GPL would go away. The most important part of the GPL is the 'free speech' part; the 'free beer' simply appears to be a necessary clause to help ensure the 'free speech' part.

    5. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      cost of getting the source if fairly irrelevent, if it can be redistributed for free once it has been obtained.... Although it probably should be capped to something reasonable, and I believe the wording was that only "reasonable media and distribution costs" were to be charged, but I could be wrong.

    6. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      You don't find a fat, hairy communist who won't even do others the courtesy of bathing to be unreasonable? Jeezus, it's like a busker that wants to be paid to STOP playing - RMS will go away if only you comply with his idea of "freedom".

    7. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      He was talking about providing the source, not the binary. The source (in the case of commercial distribution which is what he's talking about) must either be accompanied by the source (i.e. no extra charge - you'd be paying for source and binary in one go) or else be available for no more than the cost of distribution.

      From the GPL :

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

      a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

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

      c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)


      What made you think the GPL didn't include this?

    8. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      I can't help but notice that this is the main KDE company dropping the GPL. And all the sucessful examples listed in the article summary were all gtk/GNOME projects.

      KDE's been falling behind for a while now, and this just accelerates it.

    9. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      not really--- the GPL clearly says that source code must be offered for whoever asks at the same price as distribution.

      sooo... if a program costs free, source is free

      if a program costs 500$, source is 500$

    10. Re:Well, There's Your Problem by Anonymous Coward · · Score: 0

      who cares? the GPL is flawed anyways.. this is why 95% of the software in the world is under closed licenses.

      i don't use kde/gnome/linux shit, but congrats to the KDE companies

  8. Covalent and Apache by agentZ · · Score: 5, Insightful

    While I agree with the author that it's hard to sell an Open Source only project, I'm really curious to see how Covalent does selling Apache web server management systems. They take a good open source engine and add something of value, a good user interface for doing complicated tasks, to it before selling it. Perhaps that's a better business model than trying to sell GPL'ed software directly?

    1. Re:Covalent and Apache by agurkan · · Score: 1

      this is of course a good example of making money with open source software. However, apache is distributed under their own license not GPL.

      --
      ato
    2. Re:Covalent and Apache by nusuth · · Score: 1

      But model is unapplicable to GPLed software. Any such interface, config tool etc. is bound to be tagged as "derivative work" if it depends on the specific GPLed software to perform, consequently will be licenced with GPL.

      --

      Gentlemen, you can't fight in here, this is the War Room!

    3. Re:Covalent and Apache by Stentapp · · Score: 1

      But the GPL will not cause any problems. If theKompany wants to make a closed source product of their own GPL'ed product, it is fully legal as long as theKompany holds the copyright on the GPL'ed code.

      But, of course, in the Apache example (if I have understood the Apache license correctly), everyone is allowed to make a closed source product based on the Apache code, which is not the case with GPL'ed code (for example: from theKompany (or any other copyright holder)).

    4. Re:Covalent and Apache by rsidd · · Score: 2

      Well, Covalent can do that because the Apache license allows it. (It's basically BSD-like, with some modifications, eg you can't call the modified code Apache.) The GPL doesn't allow you to link to GPL'd code without making the whole thing GPL, which makes it rather to hard to use GPL libraries to write a commercial word processor, for example.

    5. Re:Covalent and Apache by Arandir · · Score: 1

      It's a different business model. Covalent is selling a service, the Kompany is selling a software product.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    6. Re:Covalent and Apache by Anonymous Coward · · Score: 0

      But, but, but... the GPL isn't viral! You guys said so. I feel so duped :(

    7. Re:Covalent and Apache by J.+Random+Software · · Score: 1

      The GPL is a piece of information that requests being copied, which makes it a virus in the broadest sense. But the GPL negotiates advantages with rational users who have the final say, while DNA and machine code viruses imitate benign information and then spread uncontrolled until their environment is destroyed, so it doesn't deserve the usual pejorative sense of the word.

    8. Re:Covalent and Apache by ambrosius27 · · Score: 1

      I think you're on to something here. If there is a pre-existing open-sourced application out there (like Apache), the company can relatively cheaply add some value to it and sell services. On the other hand, if you are creating an application from scratch (like what theKompany is doing with Kivio or Ximian with Evolution), you are spending too much time and money making something from which you'll never see direct return. You sweat and bleed to make the application, and *anyone* can use it or charge for services. It's economic suicide. If you don't care about the money, it's all good, though.

      --

      ~~~~~~~~~
      dissertus scribendo latine videri volo.
  9. Volunteer projects vs. commercial products by Anonymous Coward · · Score: 3, Insightful

    > Of course, it's been used for end user -
    > OpenOffice, GAIM, and other projects.
    All these projects do not aim to be profitable for their original developers. GPL might work for purely volunteer projects, but world has yet to witness sustainable business model for commercial companies developing GPLed products.

    1. Re:Volunteer projects vs. commercial products by Anonymous Coward · · Score: 0

      Ummm. IBM, RedHat???? Both sell GPL products and make money off of value added to those products. Though I don't advocate hacking a company and demanding code because you feel they are not living up to the GPL the Kompany did choose to use GPL'ed KDE and build their code on top of code Troll Tech specificly did not want to end up in a commercial product without them getting paid. So let me understand this. The Kompany is whining because they want to make money off the software but they don't want to pay Troll Tech for a licence to produce the code in a non GPL enviornment. Oh, well. Should have chose a different tool kit.

    2. Re:Volunteer projects vs. commercial products by Anonymous Coward · · Score: 0

      Face it. IBM does not make money selling GPL softwate, it sells _hardware_ and uses "free" software as an additional gimmick to lure customers in. Their business model is not based on GPL and never will be. RedHat, and every other Linux distribution vendor, for that matter, did not demonstrate stable profitability yet and question whethetr or not their model is sustainable is still up. To date their success has been dependent on recruiting more and more developers under GPL banners in order to profitably sell their work and on creating press hysteria during dotcom boom. Both sources dried considerably recently and we already witnessed several Linux vendors biting the dust. More to come in not so distant future.

    3. Re:Volunteer projects vs. commercial products by HeUnique · · Score: 2

      IBM - Makes money on the metals, and on other software packages...

      Red Hat - doesn't make much money at all - read the finance report and see for yourself. They DO make money from the high-end packages (Redhat Oracle, RH Advanced server) but it's peanuts against other corporates at the same size who sell software.

      --
      Hetz (Heunique)
    4. Re:Volunteer projects vs. commercial products by infiniti99 · · Score: 2

      world has yet to witness sustainable business model for commercial companies developing GPLed products

      Take a look at Trolltech. Their Qt/X11 product is GPL, but they'll sell you a non-GPL version for around $2K. This is the best business model around GPL I've seen yet.

  10. Re:He doesnt get it by crivens · · Score: 1, Redundant

    If you're bound to a license, where's the freedom? Freedom is having no license and the freedom to do anything you wish with the software/code.

    There, that's my bad mood expunged for the day. :P

  11. totally valid by vvikram · · Score: 3, Insightful

    at last someone with proper experience has spoken in a sane voice.

    its _easy_ to say sell services . its pretty easy to say hack at your will and lets develop things as a community - it just doesnt hold water in a serious [read enterprise] environment. its very tough for everything to be projected as a service.

    its surprising NOBODY thinks like an enduser, it really begs the question whether the open source people are techno-elitists. i know because i am one of them:) but after having so many sessions with my friends and helping them out - its almost stupid to think that selling services is enough and being noble in intent and academic in character is the right thing to do. people dont care for that, they want things to use, support in case of help and a smooth passage in unknown waters. NOTHING of which is provided even remotely by the warped and usually obtuse/convoluted software which come out from people like us [the oss community]

    the GPL has a lot of problems. it does solve a lot. BUT it has its limitations. if OSS people are not so fanatical they might actually realize this and present an _easier_ option for most people.

    think enterprise. you have a loose group of hackers , no documentation, all irritable and having no time [standard response: i am doing it in my free time, dont bug me] and you want a million dollar company to trust these software ?:) yes msft is evil, OSS coders rock but please lets be a little more _realisitic_ . fanaticism doesnt get us anywhere.

    i mean , look at linus and his statement on the bk license. he is right...there is no pt in arguing about license because if the tool is right you use it .

    a rant , flame me all you can......

    linux will never rule the desktop unless they actually get out of this horrible mess and convolution that the licenses have come to
    be. guess why people like windows? why people prefer aol? dammit , its easy to use. everybody is not a CS hacker, physicists need to use comps - they dont give a jackass that qt violates the license and debian wont include pine. PLEASE.

    whatever...maybe i am too put off this morning...

    v

    1. Re:totally valid by Anonymous Coward · · Score: 0

      I've come to suspect that very few Open Sourcers are end-users in the sense of the average person (obviously, the average person can't code). Both the attitude of disdain for the average user and the inability to think as an inexperienced user are what have driven me away from Open Source projects.

      On a day to day basis, most of the contributors are probably reasonable people, but reasonable people do not speak up to be heard. All we ever hear from are the elite, who care less about the average user's experience than they do about promoting their own coding ability.

    2. Re:totally valid by Donny+Smith · · Score: 1

      Right on...
      We provide (mostly) HA solutions to enterprise customers - they don't give a shit about open or closed source, GPL, and all this open source stuff.
      They want (at least) equally good support, quality of software, maintenance and all of it at a lower price than Windows. Very few of them are interested in developing anything or being able to peek in the code. Actually quite the contrary, they hope to be able to do everything via a Web interface and not have to do anything with Linux, as long as their DB2 on top if it works fine.
      And then there are other enterprise customers, but they are in minority, at least in our case.
      If anyone wants to be successful selling Linux (and this is what you essentially do even if you're a developer in a company that sells Linux software or services), (s)he must understand the customers. You can expect *your* supplier trying to understand you, but when it comes to your customers/users, you'd better understand them if you want to stay in business (or keep your job).

    3. Re:totally valid by HiThere · · Score: 2

      guess why people like windows?
      Because that's what came on their machine, and they don't know anything else.
      why people prefer aol?
      Because if you have windows installed (i.e., if you bought a computer at a store and just used it) all you have to do is put a CD into the drive.

      I'm not really sure why this is important to you. And yes, there are many competent professionals who don't care about the things that are important to hackers. So? It is to be expected that people whose goals are in different areas will find different things important. The physicist will care when he wants to hook up the instruments that he has designed to the computer. The lawyer will care when he wants to keep the text of his word processing document both private and accessible. etc.

      Of course, this is based on the assumption that, e.g., Linux word processors will continue to improve. Or if not, that the instructional manuals will. E.g. Lyx probably isn't unreasonable, but the instructions have caused me to look elsewhere whenever I have looked at it. Once upon a time I was reasonably competent with roff, but that's so long ago that I don't quite remember it. Yet I haven't been able to pick up groff from the accessible documentation. Etc. So accessible and useful instruction manuals seem to be missing. (OTOH, I do seem to recall that there was a significant change between roff and troff, so it might be that the program itself has changed in ways that make it simultaneously less friendly to use and more powerful.)
      .

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:totally valid by Steveftoth · · Score: 2, Insightful

      One of the problems with developing software that is free with the intent of selling a service to support it is that it implies that the software you are developing is HARD TO USE, and requires support in order to use. Thus most GUI applications and configuration programs are the least profitable and also reduces value of the product it is tring to configure.

      Who wants to buy service on their media player, web browser, or word processor. Most people, once they figure out how to use a program are very happy and content. (Unless they want more features) GUI applications should be fairly self contained and self sufficiant.
      Only software that has lots of options that need to change, or software that has to have 100% reliablity is very good for the support model. But a word processor that should run 95% of the time, but it's ok if it crashes ( nobody dies ) and your work is mostly recoverable, then selling support doesn't work so well.

    5. Re:totally valid by Vanders · · Score: 1

      its surprising NOBODY thinks like an enduser, it really begs the question whether the open source people are techno-elitists.

      I'm sorry, but please do not tar us all with your own brush. I take pride in the ease of use of my own projects and I consider "ease of use" by an end user just as important as stability and the feature set when I develop my software.

      Some of us understand the KISS principle. Many don't.

    6. Re:totally valid by youngsd · · Score: 2

      I guess I don't completely follow your reasoning. You do point out that different people have different goals. But then you defend that whiny essay as "totally valid" when all that I can tell Shawn Gordon is doing is complaining that RMS has different goals than he does.

      Some folks write software and distribute it under GPL because they find it meaningful. In fact, I do that. My goal in doing this is not to help folks like Shawn make a living selling software. If he can, more power to him. If he can't, he should get a day job like I have.

      Telling me that my distribution of software under the GPL is "a horrible mess and convolution of licenses" and won't lead to Linux on the desktop merely tells me that you don't know, or care, about the reasons that people like me release software under the GPL.

      -Steve

      --
      Democracy is a poor substitute for liberty.
  12. "Communites" are their own worst enemies. by ari{Dal} · · Score: 3, Insightful

    Speaking generally, communities are almost always their own worst enemy. This goes for the linux community, the GPL community, and just about any moderately social community you can name.
    And the reason for it is stated quite clearly in the article:
    We sell one product that is GPL. On at least a weekly basis we get someone telling us that we have to give them the source code because it is GPL. Some of them become verbally violent and abusive when I point out that the GPL provides for us to charge for the source code, we just have to make it available, and this we have done. Some of these people even tried to hack our system to get the code because they thought it was their God-given right to have it. These are also typically the people who contribute nothing to the community.
    While I think that the majority of any community is made up of decent, honest people who truly care about what they're involved with (yes i am that idealistic), there are always those marginal and VERY vocal few who MUST ruin the party for everyone else.
    These people usually know just enough of what they're talking about to make them dangerous... the uneducated public believes them because they sound like they know what they're talking about. The business community listens because they're loud, vocal, and usually ready to do something stupid to get their point across.
    It's because of people like this that GPLd products haven't gotten a big foothold in the commercial world. The thought that someone might actually CHARGE for their hard work and effort sends these people over the edge into a screaming, frothy frenzy of angry postings, DoS attacks, and god knows what other lame actions to 'punish' the bad guys who won't give them something for nothing. Never mind the fact that what they're doing is completely legal and good business... this self-righteous minority doesn't need messy facts to get in the way.
    It's those marginal people that make me see red, and make companies head in the same direction as TheKompany has.. they won't bother with the GPL because the vocal, obnoxious minority makes it too hard for them to be profitable from their work. Frankly, I don't blame them for deciding not to GPL anything else one bit.
    End Rant.

    --
    Moral indignation is jealousy with a halo - H. G. Wells
  13. Should be Any Company that Sells Software by Uggy · · Score: 5, Insightful

    ESR says in Cathedral and the Bazaar, if you are a company who's primary business it writing and selling software, then GPL isn't going to be your bag. That's ANY software. You may write software an give it away hoping to sell some other service on top... in which case your company's primary product wouldn't be software would it?

    However, if your company sells widgets and you maintain an in house software development team to manage your process/accounting software, then you are the perfect candidate for GPL. Outsource your software to the world and get more code review, more features, and more man hours spent on the product at a lower price... then you can dedicate yourself to what you do best, making widgets instead of overhead (software development).

    Other GUI and cool software maintained strictly as software under the GPL is done for fun not profit.

    It isn't rocket science.

    --
    Toddlers are the stormtroopers of the Lord of Entropy.
    1. Re:Should be Any Company that Sells Software by Anonymous Coward · · Score: 0

      There would seem to be value in a license something like this:

      I sell my software (online, in retail stores, whatever) and provide the source (so allowing user patches for features I didn;t think of, or features that aren;t of interest to most people (so not worth my while) but useful for someone who's prepared to spend the time. It's not GPL - you can't give away copies, but you can patch your own copy, recompile it against different library versions or whatever, and probably distribute the patches.

      It also contains a provision that if I stop supporting the software, or go bust, or stop supplying source, then the existing source becomes GPL.

      That way I can make money, but you are protected against me going bust or stiffing you for subscriptions/upgrades a la Microsoft.

      Comments?

    2. Re:Should be Any Company that Sells Software by J.+Random+Software · · Score: 1

      If I can't "give away copies", do you intend to tell me how many machines I can run the software on or how many people can use it? Can I hire other people to improve it for me? Can I collaborate with other owners to improve it, and can we sell the improvements?

    3. Re:Should be Any Company that Sells Software by Anonymous Coward · · Score: 0

      As a matter of fact, that is the license under which all the other products theKompany makes are sold. (Besided the infrastructure-type projects that are free as both in speech and beer).

  14. Define "charging for source" by Shagg · · Score: 3, Informative

    Some of them become verbally violent and abusive when I point out that the GPL provides for us to charge for the source code, we just have to make it available, and this we have done.

    Yes, the GPL allows you to charge for the source, rather than offer it as a free download. But, IIRC you are only allowed to charge for your cost in producing the copy of the source. IE you can charge for the cost of burning a CD and shipping to the customer, but you can't offer the source for $500 and be compliant with the GPL.

    Anyone else have more details on what he meant by this? If they're using GPL software, and then trying to charge for the source in order to make a profit off of distributing it, then the customers have a right to complain.

    --
    Unix is user friendly, it's just selective about who its friends are.
    1. Re:Define "charging for source" by ip_vjl · · Score: 4, Informative
      According to the GPL FAQ

      Does the GPL allow me to charge a fee for downloading the program from my site?

      Yes. You can charge any fee you wish for distributing a copy of the program. If you distribute binaries by download, you must provide "equivalent access" to download the source--therefore, the fee to download source may not be greater than the fee to download the binary.


      It's funny that people assume downloading from a company costs nothing. I can only guess that these are people who are unaware that most companies pay for whatever bandwidth they use, as opposed to the all-you-can-drink type access you get from home/dorm internet access.

      - vin

    2. Re:Define "charging for source" by pigpen_ · · Score: 1

      They can charge as much as they like for the source, as long as it is not more than the cost of the binary. See this answer in the GPL faq. Also read up on the FSF's position regarding 'selling software.'

      --
      Zambozay! My brain must've been eatin' a sandwich!
    3. Re:Define "charging for source" by Cro+Magnon · · Score: 3, Insightful

      Bzzt! Wrong! Shawn can charge whatever he wants to. Of course, there are practical problems with trying to charge $500 when somebody else can put the source code on his website. Unless, nobody buys that first copy, in which case he still won't make any money.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    4. Re:Define "charging for source" by drac · · Score: 1

      Yes, but this "availability of source" only applies to people to whom you have distributed the binaries- in his case, *paying customers.*

    5. Re:Define "charging for source" by anonicon · · Score: 1

      There's a big difference between profiting from your source code and covering your expenses. If I pay two programmers to make program X, plus pay all the other costs associated with producing program X, I'm not going to be freely (as in beer) giving away the program's source code. I can't afford to.

      However, if you're willing to pay the $1000-$1500 (at the *very* low end) to help defray my costs of creating program X, I'll be happy to give you the source code. Your payment will help me keep my company solvent, and also signifies that you're serious about contributing back to the source base (or else you wouldn't pay for it).

      Of course, YMMV.

    6. Re:Define "charging for source" by An+Onerous+Coward · · Score: 2

      His ambiguity here bothered me, too. It's possible that he means, "You buy the product, and you get the source along with it." That would work under the GPL. It's also possible that he means, "You can buy the source-free version for $50, or the sourced version for $5000. Take your pick." That would just be evil. I browsed around theKompany, but couldn't figure out which product he was referring to.

      --

      You want the truthiness? You can't handle the truthiness!

    7. Re:Define "charging for source" by dachshund · · Score: 2, Insightful
      This is the section of the license, which might be more helpful than the FAQ (bold/italics mine):

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

      a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

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

      c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

      It's possible that earlier versions of the GPL read differently. I don't know about that, and I don't know which version theKompany uses. However, from reading the above I would imagine that some reasonable limits can be placed on the physical cost of the distribution.
    8. Re:Define "charging for source" by Mr+Windows · · Score: 2, Informative

      The product that he's referring to is korelib

    9. Re:Define "charging for source" by duffbeer703 · · Score: 2

      The italics provider a backdoor for anyone who wishes to withhold the source.

      "for a charge no more than your cost of physically performing source distribution"

      Let's say that I only distribute via CD-ROM. If I pay a subcontractor $500 to reproduce the source code onto a cd-rom, then my cost is $500.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
    10. Re:Define "charging for source" by J.+Random+Software · · Score: 1

      If you commissioned software, it must be because being able to use it is worth more money to you than what you'd pay to have it developed. Why does it matter who else has it? The more people who have it, the more likely you are to be able to use improvements they've made--which you didn't have to pay anything for.

    11. Re:Define "charging for source" by dachshund · · Score: 1
      Let's say that I only distribute via CD-ROM. If I pay a subcontractor $500 to reproduce the source code onto a cd-rom, then my cost is $500.

      I think that'd be up to a judge, though I'm no lawyer. I can't imagine that that sort of tactic isn't tried in other legal circumstances, and that there isn't some legal principle governing it.

    12. Re:Define "charging for source" by mvdwege · · Score: 1

      Uh, no.

      If his customers receive the binaries under the GPL, then they are free to redistribute them whichever way they see fit, and those that receive the binaries from them still have the right under the GPL to ask for the source from the original distributor.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    13. Re:Define "charging for source" by drac · · Score: 1

      Just checked the GPL- the commercial distributor has the obligation to

      "offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange"

    14. Re:Define "charging for source" by greenrd · · Score: 1
      That can't be right. If you could get around it by bribing someone to charge you arbitrary amounts, that sentence would be meaningless.

    15. Re:Define "charging for source" by mvdwege · · Score: 1

      Sorry, are you saying I'm right?

      Note that to any third party in that clause. It's been rehashed several times already in this discussion: that means you're not just obliged to distribute source to those that paid for the binaries, but to anyone who has a legal copy of the binaries.

      Since by the terms of the GPL, anyone can obtain a legal copy of the binaries without paying for it (if he finds someone willing to distribute it for free), and since asking for proof is a bit difficult, this means in practice that once you distribute a GPL app, you have to provide source at cost price to anyone who asks for it, not merely your paying customers.

      Mart (who, for the record, thinks that this is a Good ThingTM)
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    16. Re:Define "charging for source" by duffbeer703 · · Score: 2

      government contractors use this trick all the time to gouge government agencies.

      in many cases it is actually not illegal.

      if I offer you $500 to tie my shoes and you accept my offer, there is nothing illegal about that. if I offer you $500 so that I can have my shoes tied, bill it to the company expense account, and demand a kickback, then that is illegal.

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
  15. obligatory mirror by po_boy · · Score: 2
    http://dotslash.dynodns.net/02/03/18/sgordon.html


    Let me know if it's a problem.

    1. Re:obligatory mirror by po_boy · · Score: 2

      removed by request. The real site is pretty quick now, anyway.

    2. Re:obligatory mirror by Anonymous Coward · · Score: 0

      amoore@gotany.com, you are a goddamned waste of space, and a pathetic karma whore to boot.

  16. In related news... by AirLace · · Score: 4, Informative
    RedHat explains how they make money off services: Making free software pay - BBC News:



    Red Hat does not own Linux, so it cannot charge for each copy it puts out in the way that Microsoft charges for Windows or Sun charges for Solaris.

    "The only way we can make money in this business is in support," Mr Hoffmann told BBC News Online.

    "That ranges from training down to system maintenance, deployment and integration with other applications.

    "We focus on those customers who are able to pay the bill - the enterprises," he said.



    Give me a company that sells support over one that sells software any day. The moment you put software in a box, its most important component -- the ability to be adapted and updated for security fixes and feature enhancements -- dies. Anyway, which is more successful, "theKompany" or RedHat?

    There's also an interesting analysis on LinuxToday of theKompany's tactics and how they allegedly intentionally damage Free Software. Although I wouldn't take all the accusations at face value, there's certainly something worrying about the claims.

    1. Re:In related news... by craigeyb · · Score: 1

      Give me a company that sells support over one that sells software any day.

      Here's a financial analysis of Red Hat.

      The question of using the GPL for flagship software is not one of morality or ethics but one of financial practicality. Red Hat has lost $0.72 per share in the last 4 quarters, which is quite a bit considering that they've never once turned a profit.

      IANAL, but the GPL was not originally intended nor is well suited for the corporate world. What that world needs is a good balance between the free as in freedom and the ability to turn a profit. A license agreement that would allow such a beneficial compromise would be invaluable.

      --

      Social Contract? I don't remember signing any Social Contract!

    2. Re:In related news... by WildBeast · · Score: 1

      Not true, the only reason why RedHat is making more money than the others is because for many people, RedHat = Linux

    3. Re:In related news... by Anonymous Coward · · Score: 0
      Give me a company that sells support over one that sells software any day. The moment you put software in a box, its most important component -- the ability to be adapted and updated for security fixes and feature enhancements -- dies. Anyway, which is more successful, "theKompany" or RedHat?


      Uhh... which is more successful, Microsoft or RedHat?


      Which is more successful, Adobe or RedHat?


      Which is more successful, Apple or RedHat?


      Which is more successful, Oracle or RedHat?


      etc. etc.

    4. Re:In related news... by Anonymous Coward · · Score: 0

      Red Hat has lost $0.72 per share in the last 4 quarters, which is quite a bit considering that they've never once turned a profit.

      I wouldn't use a company's stock price as a gauge of its profitability. Remember the dot boom of the late '90s? The stock price is simply what investors are willing to pay (or sell) a share of stock for. That's all. It's the investors that determine the stock price - not the company's performance.

    5. Re:In related news... by Anonymous Coward · · Score: 0

      I'm so tired of people pointing to Red Hat and saying "look, charging for support is a viable business model." Red Hat has a number of different revenue streams, one of which is support. Before I'm convinced that Red Hat is a good example, I'd like to see a breakdown of all of their revenue streams.

      I'd also like to see some other companies as "successful" as Red Hat. Specifically, I'd like to see an example of a software company that produces one or more truely GPL software products that aren't OS's.

    6. Re:In related news... by GigsVT · · Score: 1

      I think he meant earnings, but of course he counted one time charges, i.e. worthless goodwill that came from the purchase of companies when Red Hat's stock was high. You can't really count that as a loss, since that money appeared out of thin air in the first place, due to their inflated stock price.

      Also, Red Hat was profitable before the IPO, and has broken even the last three quarters once you take out one time fake-money charges.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    7. Re:In related news... by Anonymous Coward · · Score: 0

      Dude there is no "analysis" there, its simply a "gee, well your software sucks anyway" (no exaggeration) king of rant.

      Plus, I found it delicious the guy who put the rant together has a hotmail account.

      You know...the accounts given away by evil microsoft?

      The irony is rich and deep, like the manure coming out of a lot of the FSF folks mouths.

    8. Re:In related news... by taion · · Score: 3, Informative

      There's also an interesting analysis on LinuxToday of theKompany's tactics and how they allegedly intentionally damage Free Software. Although I wouldn't take all the accusations at face value, there's certainly something worrying about the claims.

      What, I shouldn't take all the accusations at face value just because they've been debunked as being completely wrong in a reply?

      Such skeptics we have here... tsk tsk.

      --

      ----------
      Floccinaucinihilipilification - the action or habit of judging something to be worthless
    9. Re:In related news... by Anonymous Coward · · Score: 0

      Before they went public, Red Hat claimed to be (slightly) profitable. When they went public, they used the cash to expand their core business and buy up other businesses (cygnus, etc), and stopped being profitable. They are bleeding cash, but unlike a certain other LiNUX company, they'll probably still be around next year.

    10. Re:In related news... by Anonymous Coward · · Score: 0

      Hm, I wish I could do that with my credit cards! You can;t just write offone-time charges for gods sake. Not when that one time is 5 times a quarter and will be from now on. If the entire cost of doing buisness is more than you make then you are loosing money. Lose money long enough and your history...

    11. Re:In related news... by Anonymous Coward · · Score: 0

      A license agreement that would allow such a beneficial compromise would be invaluable.

      That's what is so great about the much more free BSD License.

      The kiddies in hell will be eating snow cones before I sign a damn thing over to RMS.

    12. Re:In related news... by Theom · · Score: 1

      If you use the BSD license you *are* doing that. Think about it.

      --

      mp3: l33t term for empty.
    13. Re:In related news... by GigsVT · · Score: 1

      Look, do I need to explain it in simpler terms for you?

      RHAT IPOed. Their stock became worth several hundred dollars. Was the company worth that? Hell no! RHAT knew that, and spent this "funny money" buying companies that had real worth. The price difference between what the companies are worth now, after being absorbed into Red Hat, and the price they paid (with fake money, remember?) is Goodwill. Goodwill is taken as one-time charges.

      When a company like Cisco writes off 3 billion in inventory as a one-time charge, that is a real cost, there is physical goods that are now, in esscence, worthless.

      When a company like RHAT takes a goodwill one-time charge, it's vastly different. That is money that would not exist today, had they held on to their stock reserves, and not spent it while it was way overvalued.

      Let me know if you still have more questions.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    14. Re:In related news... by HiThere · · Score: 2

      It's certainly a reasonable response. More reasoned than the original claims were. But proof, by either side, requires a bit more than claims. Preferably, in this case, links to original documentation of either the assertions or the rebuttals.

      Lacking any real evidence one way or the other, perhaps we should accept that The Kompany has been acting in good faith. The users of KDevelop have certainly benefitted from their contributions, and there is other miscellaneous evidence that at least part of the time they were acting as good members of the community. Not to claim that this is proof, but I seem to remember several donations of software to the KDE applications. (And I don't have any links either. Sorry. But then I don't claim this as proof.)

      It hardly matters at this point, and vituperation assists noone. More to the point, everyone should ask themselves "How does this affect what I intended to do?", and adjust their intentions accordingly. (This will be a bit difficult until the finally choosen license is decided upon and announced, but interim decisions should be possible.)

      I see nothing inherently wrong with purchasing IDEs. But it needs to be justifiably in terms of benefit. And they had better not stop working just because I upgraded my os version (that's why I have stayed away from CodeWarrior ... I really liked it on the Mac, but the Linux version never seems to be willing to promise that it will work on the version of the os that I have installed).

      There's a change though. Perviously, I thought of buying software from The Kompany in the way that I thought about buying Linux distributions. "This is one of those things that I do periodically, because it will benefit the community." Now I can't see that purchasing from The Kompany is giving back to the community. So they need to meet a more stringent benefits test. They don't get the check box saying (roughly) "15% of this purchase counts as a donation to Free Software.", because they aren't making donations to free software.

      Of course, I'm guessing about what the new license will be. Perhaps when I find out I'll change my mind.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    15. Re:In related news... by Anonymous Coward · · Score: 0

      Giving away the software just to sell the support is the biggest crock of shit to ever come down the pike. Some other models make sense, like selling consultancy, but selling service is not.

      Redhat is just giving themselves the incentive and excuse to release crappy software. And then they go bragging about how moral they are for giving away their software, while charging you up the ass for support. I'm sure that guy that snuck in gcc-2.96 made a big bonus for his contributions to the bottom line.

    16. Re:In related news... by MisterBlister · · Score: 2
      I think you missed the whole point of the article, which is that not all software NEEDS support. If your end-user desktop application client software requires support to the extent that many users would pay for it, something's wrong..Why is your software so hard to use that it needs that level of support? Don't you see the paradox here? Should companies intentionally make all free software hard to use to get in on the 'support' money? While some software (Linux, Apache, databases, etc) is inherently complex and a good candidate for money-through-support, some software (end-user apps) is NOT! That's the whole point of the article.

      Nobody is ever going to make a living selling support for your typical END-USER type software. If you don't believe this then the burden of proof is on you to provide a real-world example proving me wrong.

  17. Re:He doesnt get it by SteveX · · Score: 3

    How is he removing them freedom? He gives the people that buy his software the source code. If you don't buy his software, you don't get it.

    He hasn't taken away any freedom. He just hasn't given you anything.

    You want freedom not his crappy software. Well, then don't buy it. Problem solved.

    - Steve

  18. We should all *emulate* the Kompany! by zulux · · Score: 4, Insightful
    Every Free Software programmer need two things.

    To Eat!

    Contribute Free Software

    The Kompany manages both, and yet people are getting all hot and bothered about the fact that they have software that you must pay for if you want it.

    As long as the Kompany keeps making contributions to Free Software - they are alright by me.

    Let's judge the Kompay an their efectivness in giving Free Software. If they happen to make a buck on the side, good! That money helps them make more Free Software.

    --

    Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    1. Re:We should all *emulate* the Kompany! by bcrowell · · Score: 3, Insightful
      Amen, brother! People are too hung up on maintaining their ritual purity. Sorry, but it does not say in the book of Leviticus that thou shalt not mix open-source and closed-source software.

      The author's company likes to GPL their system-level stuff, but thinks GPL doesn't work for end-user GUI apps. So the community gets some open-source system software. Same thing for Apple, which has open-source licensed the Darwin kernel, but doesn't open-source any of the GUI stuff. Are we supposed to be angry at them for giving us a state-of-the-art open-source microkernel for free?

      Personally, I use a lot of open-source apps on a (mostly) closed-source OS (MacOS X). So for me, the setup is reversed. If open source is going to grow on the desktop, a great way to lure people in is to make it possible for them to use open-source apps on their closed-source systems. Fink, for instance, is doing a great job on this. It's not gonna work if you tell people they have to erase Windows off of their hard disk and undergo Hare Krishna training if they want to use open-source software at all, especially given how hard Linux is to install.

      Gosh, somehow a lot of open-source software is getting written, both at the system level and at the application level. Where's the problem?

      The problem is the whiners, zealots, and wannabes, who should get off Usenet and start writing some software.

    2. Re:We should all *emulate* the Kompany! by mjh · · Score: 3, Insightful
      Every Free Software programmer need two things.
      • To Eat!
      • Contribute Free Software

      While that's true, I think that one of the best responses that I've seen to this so far has come from someone at LinuxToday He says:

      frankly most Linux users don't care about your profit margin -- and *there're not supposed to*! It's up to you to make your business a success, not the community. If the community wants GPL'd stuff, then it's up to you to figure out how to make it profitable. If you can't...well, there's always barber college.

      Finally, for many of us, using the GPL is as much a philosophical as a practical matter. RMS, whatever his faults, has been crystal-clear on this issue from Day 1. GPL'd software is first and foremost a way to make software Free. If software houses find it difficult to make a buck that way, that's not his problem. It's not our problem. It's *your* problem.

      The point is, that while software developers need to eat, that's not the community's problem. If a software developer can't eat, and that developer licensed his/her code under the GPL, that's not the GPL's fault. Do we know why the software developer isn't eating? Is it because the GPL prevents it or is it because the software developer doesn't understand the GPL enough to be able to make proper use of it?

      I would think that releasing code under the GPL, and then making it harder than normal for people to get that code, just invites the kind of extra effort to deal with the myriads of people requesting the source code. The fact that you wasted time answering all of those questions isn't a consequence of using the GPL. It's a consequence of trying to use the GPL in a non-standard, albeit completely legitimate, way. Unless you're microsoft, there's a penalty for not conforming to standards. Should you be surprised when chosing to do so actually costs you something? In this case, the cost was spending too much time arguing instead of charging money for some value added service.

      I think it's a cop out to say that they didn't make money because of the GPL. I think it's a way of deflecting attention on what might be the real issue: a poorly managed business.

      --
      Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
  19. GPL bogeyman by stevenj · · Score: 2
    If you read the essay, it really sounds like the Kompany wants to give up on all free (open-source) licenses altogether, not just the GPL. He wants to be able to force every user to buy the software:
    Look at it this way. I can send 1,000 copies to a distributor who will put it on store shelves around the world. People will walk in, pick it up and buy it. Now let's say that the software was free (as in cost) and I just sell services. Well, now I can't put it on a store shelf and for every customer; I have to go and hunt them down somehow and persuade them to use our free software and then pay us for support -- but they should only really need support if our software is hard to use or poorly designed, which isn't the case or our objective.

    I certainly agree that it is (often) harder to make money with free-software licensing than with a proprietary model (although it's not true that you "can't put [free software] on a store shelf"). However, I am disappointed that he (apparently) tries to shield himself from criticism for abandoning free software by ostensibly attacking only the GPL, everyone's favorite bogeyman (citing unnamed "ambiguities," complaining that RMS doesn't like them, ...)

    --
    If a thing is not diminished by being shared, it is not rightly owned if it is only owned & not shared. S. Augustine
    1. Re:GPL bogeyman by kawlyn · · Score: 2
      He wants to be able to force every user to buy the software:
      Well, that's not really a big deal now is it. If you don't want to pay for the software, don't buy it. He's not really forcing you to do anything. There's no spooky mind control going on.
      --

      When someone yells "Stop" or goes limp, or taps out, the fight is over.
    2. Re:GPL bogeyman by Anonymous Coward · · Score: 0

      "He wants to be able to force every user to buy the software:"

      OH! The Horror!

      Somebody ought to stop this "charging for products" stuff and go back to the good old days when everything was free.

      Like in Star Trek. Everything was free in Star Trek.

    3. Re:GPL bogeyman by stevenj · · Score: 2

      Oh please...I meant force every user of the software to buy it. Nor was I taking position on whether this is right or wrong, per se, just that I feel that he's intentionally confusing the issue by focusing on the GPL---he's rejecting all free software (and open source) licenses.

      --
      If a thing is not diminished by being shared, it is not rightly owned if it is only owned & not shared. S. Augustine
  20. Re:Klerck on page widening by Anonymous Coward · · Score: 0

    Bloody BASTARD!!

  21. Short, but sweet. by proxima · · Score: 2

    I am not at all surprised by some people's reaction to theKompany. However, I think it is terrible that the Linux community (which does not necessarily equal the Open Source or Free Software community) acts hostile towards commercial software. Most people agree that not all software can be reasonably free - not enough end users would pay.

    Frankly, in many cases we as a community are spoiled. We've lived through the internet bubble of free services and negative cash flow companies having free websites, and now we can't accept the fact that all software and internet sites can be free. Some sites are simply too expensive to operate without subscriptions, and some software simply doesn't have the developer support to create a competitive Open Source version. For proof just look at the KOffice interview from earlier - creating Word filters is tough work that people simply don't want to do for free. Open Office, Mozilla, and many other Open Source software is created in part by paid programmers from big companies (AOL/TW, Red Hat, IBM, etc.). But certain software projects will inevitably not prove worth the time of those companies.

    I think it is important to remember that not all commercial software companies are as bad as Microsoft. Commercial software (especially games) is a HUGE market, with a very successful business plan. We need more commercial developers for Linux - users will want to see their familiar software, games, etc. available for Linux before they decide to switch. Even the simple presence of more Linux software at your local Best Buy will get Joe Windows User to think about Linux if he's tired of Windows.

    I think it's wonderful that I can build an entire system from nothing but Open Source software and have it perform a good majority of my daily work. Much of this software is worth purchasing, but we are lucky in that we have the choice with who and how we choose to support the software programmers. In the end, regardless of whether or not you like theKompany's software, the fact that they remain one of a few commercial software developers for Linux is important. Other companies will be looking to it as an example of how viable the future Linux market is. Loki has already stained Linux's reputation for commercial software.

    I wish theKompany the best of luck in developing high quality commercial software.

    --
    "The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
    1. Re:Short, but sweet. by Anonymous Coward · · Score: 0

      What's the point of Linux, if not freedom? If you want all your base are belong to a vendor, you already know where to find those.

  22. Are you John Nash by October_30th · · Score: 0
    John Nash, is that you?

    Please try to concentrate on using your mathematical genius to find secret messages in newspaper articles. That's the way the Islamic terrorists are communicating in order to place a nuke in the US.

    Your friend, Parcher

    --
    The owls are not what they seem
  23. What we really need by Anonymous Coward · · Score: 1, Interesting

    Is a licence that allows developers to develop the source code openly and sell the compiled "End user" program in a boxed copy with manuals, support and a REAL INSTALLER. But allow the basic source code to be downloaded.

    This would be a good idea in my opinion.

    1. Re:What we really need by An+Onerous+Coward · · Score: 2, Informative

      There is such a license, and it is called the GPL.

      Red Hat's boxed distros, just as an example, fulfill your requirements exactly. The only real difference is that RHAT ships source CDs instead of making you download it off the Net.

      Or have I missed the point of your post?

      --

      You want the truthiness? You can't handle the truthiness!

    2. Re:What we really need by hyphz · · Score: 1

      It would be *far* too easy for them to abuse this by making the package depend on items installed by the proprietary installer.

      It would also undermine a lot of the community. The idea is to create a software commons, which isn't really what you're creating when one guy in the commons can shout louder than everyone else for his particular flavour of the code.

    3. Re:What we really need by spitzak · · Score: 2


      It would be *far* too easy for them to abuse this by making the package depend on items installed by the proprietary installer.

      No that would violate the GPL.

      I agree with the previous response, the GPL allows exactly what the anonymous poster is asking for. He seems to think the GPL requires the user compile the code, that is absolutely false and I don't understand why anybody would think that.

      He also seems to think the GPL means the source code must be free to anybody, in fact the GPL says the source code must be available to the person who buys the software. The source code could in fact be on the disk, or the downloading could require something proprietary from the disk, so you have to buy the disk to get the source code (the GPL does say that you can't prevent one person from buying the disk from doing anything with the source code such as give it away for free).

      Also nothing prevents a company from packing the disk with proprietary add-ons as long as they can make a convincing demonstration that these add-ons are not required by the core GPL program for it to do useful things.

    4. Re:What we really need by SilentStrike · · Score: 1

      I think he meant more like forcing binary distrobutions of the program to be bought from the original author. making it illegal for them to be transferred, whilst still enabling the source to be spread freely. This way the hackers can still fix the product, if they so desire, but the 99% of people who just use the product, and have no interest in actually modifying it are forced to buy it. I posted something similiar yesterday. tp://slashdot.org/comments.pl?sid=29629&cid=317954 1

  24. of course by Anonymous Coward · · Score: 1, Insightful

    I don't get all these people who slam the gpl because they can't make money with it. Well duh, it was not designed to help companies make money. It is for people who want to make their code available, but want other people's code as payment for their own.

    Of course there are always the people who go on about how they don't think it is fair that they pay with thier source code to get some small piece of functionallity from a peice of gpl software. Well if you don't like the price, don't pay it. Changes are there is someone else that wants money instead of code.

    As for this article, I can understand the trouble that people are causing with gpl inquireries. But I can't blame the gpl people either, since they are trying to protect themselves from people stealing their source code, without payinging them the price they are asking. Violating the gpl is the same as stealing a copy of word. So yes switch licenses if you think it is better for the company, it is the smart thing to do. Everything does not have to use the same licence, use the one that does what you want. And of course it is the less informed people that are causing the most problems, that is how it works for everything.

  25. You don't get it by NeoOokami · · Score: 0

    How is open source only freedom? Freedom is having a choice. If you provide a choice then you're certainly aiding freedom. Microsoft doesn't hinder freedom because they are closed source, but because they attempt to force consumers to follow in their plans/software. Just like people like you.

  26. The idea is by Anonymous Coward · · Score: 0

    I haven't read his essay yet.
    I am the kind of person who wished every software would be gpl (But, then again. I would also like to see peace on earth).

    I see nothing wrong in paying for good software.And I also think there is nothing wrong in Open Sourcing your software. It will just not be a gpl license.
    But everone that buy's a license can hack away on that software and share there hacks with others (under GPL eg.).

    If somebody then decides to make a similair product in GPL he could do that.
    Then people would stop buying the commerciel product and would use the GPL instead.

    I also think there is nothing wrong with that. Software products are hard to make, no matter if it has been done before.
    Just look at office suites.
    So if the commerciel product stays ahead from the competition (from the GPL), they will keep earning cash.

    The most important things of an operation system is already GPL (take a look at the software in a Linux distribution), so it is only software there adds an ekstra bonus that will survive.

    With this I don't say that companies cannot make commercial profitable GPL code. Take a look at Sun Staroffice. They make it to be able to sell there hardware (and get huge handliftning from the community by doing so).

    The only thing I don't understand at the moment, is why every commercial software product isn't Open Source (not GPL).
    Maybe is it because they write buggy code (shame on you), or maybe it is just that the company got too many suits and to little guts.

    //lean

    P.S I will go and read the article now, and hope to get smarter.

  27. well, duh by mmusn · · Score: 2, Insightful
    Of course, the GPL isn't very useful for end-user software aimed at non-programmers. I mean, the whole point of the GPL is to enable the user to modify the source and share their improvements with others if they like. If the end-users don't program, the GPL isn't going to be very meaningful to them.

    But Gordon doesn't seem to understand the purpose of the GPL. He seems to think it's some mastermind plot to undermine Microsoft and commercial software vendors. He seems to think that the main aspiration of Linux is to become just like Windows and used by just the same class of people. But what the GPL really is is a way of giving users the tools to build the environments they find useful; that the software ends up costing nothing in many cases is just a side-effect.

    And the fact that Gordon doesn't get it shows in TheKompany's products. Kapital just isn't competitive with Quicken or Money in terms of functionality or support by financial institutions, but it also fails miserably as a flexible, end-user programmable UNIX-style component.

    Maybe Linux will become a mainstream desktop platform, and maybe eventually, there will be a significant market for Windows/MacOS style applications on it. But I think that's a long shot, and until that happens, I'll just get the real thing in the few cases where I just want a consumer-grade piece of software.

    1. Re:well, duh by t_hunger · · Score: 1

      Hey, you can allways give ask some developer to do changes for you if you have the source. So I really think the GPL is meaningful to endusers. Even if it's only because they are allowed to share the software with their friends:-)

      --
      Regards, Tobias
    2. Re:well, duh by Wildfire+Darkstar · · Score: 1

      Yeah, to a degree. But making use of GPL code involves some sacrifices for the enduser that non-open code does not: you need to be willing to get a little more technical, to put up with potentially more (or at least different) frustration, and so forth. It also has numerous benefits that non-open code does not.

      If you're willing to put up with the differences in exchange for the benefits, good for you. I was, and that's why I'm a devoted Linux user.

      --
      Sean Daugherty "I have walked in Eternity -- and Eternity weeps."
    3. Re:well, duh by wilhelm · · Score: 1
      But what the GPL really is is a way of giving users the tools to build the environments they find useful; that the software ends up costing nothing in many cases is just a side-effect.

      That's the thing that most people (especially around here) don't understand about the GPL. Nothing in the GPL says anything that the software should have no cost, but only that if you obtain the software, you get the source as well. Not only does it allow the users to modify the software for their own needs, but it provides protection for the users in case the software company goes belly-up - you can still fix bugs and get some level of support, even if it's only from your internal developers.

    4. Re:well, duh by Chris+Johnson · · Score: 2
      To the GPL, there is no concept of an 'end-user'. The notion does not enter into its world. No such thing as a person who CANNOT program.

      In that light, it's very strange and suspect to be trying to write software for 'end-users' that are expected to remain end-users...

      The nearest analogy I can think of is a publisher who publishes books for only such people that can read but cannot write...

  28. What? by kevlar · · Score: 2

    Of course, it's been used for end user - OpenOffice, GAIM, and other projects.

    ... ok and which ones are owned by companies that are actually attempting to make money? Oh wait.... none of them? Thats what I thought.

    1. Re:What? by mobydobius · · Score: 1
      In the category of "other projects":

      Ximian wants to make money. Ximian makes friendly programs like Evolution and Gnumeric. If Ximian were to require me to pay for the convenience of their testing and packaging and download servers, I would pay. And the software would still be "free".

      OpenOffice is built by Sun. Sun wants to make money. Sun makes money off off of OO by using it to build StarOffice. They get free contributions to their code base in exchange for a free (libre) version of StarOffice.

      Similarly for AOL and Mozilla/Netscape.

      Perhaps TheKompany could consider a scheme like these two have: Have a free and commercial product, with the free one constantly in a development state for people to contribute to, and a polished, tested version suitable for sale.

      --

      "I like to wear big boy pants."
    2. Re:What? by An+Onerous+Coward · · Score: 2

      OpenOffice is supported by Sun, and IIRC the two share a codebase similar to the relationship between Mozilla and Netscape. It looks like Sun will be charging for SO6.

      Speaking of Mozilla, it's also a good example of a successful end-user app being developed by a major corporation.

      GAIM probably isn't intended as a moneymaker, since its intent is to provide similar functionality to the AIM client which is given away for free. However, when a linux distro includes GAIM, it makes the distro as a whole more valuable. So it might nevertheless make financial sense to develop it.

      Oh, and on an unrelated note, it's sad when the president of a company doesn't bother to spellcheck his public correspondences (and then proudly links to it from their homepage). If I'd come across this article as a /. post, I would only mod up if it were below +3. TheKompany's new "You may have the source but you may not redistribute the source" license is an interesting idea, but I'm not sure how satisfactory it will be to OSS users.

      --

      You want the truthiness? You can't handle the truthiness!

    3. Re:What? by kevlar · · Score: 2


      The statement wasn't about GPL and end-user apps. It was about GPL and end-user apps that can actually MAKE money.

      "Supported by SUN" and "Will charge" are not success stories. A company cannot make a profit and at the same time release its software under the GPL. They don't mix. You won't make money. Even if you're lucky to make a significant buck with the first version, you won't make it very far after that before someone takes your source and sells it in the same market.

    4. Re:What? by kevlar · · Score: 2


      Wrong. Sun makes money from selling hardware. AOL makes money from selling a service, i.e. Internet access and content.

      Ximian may want to make money, and they actually might. Unfortunately it will all be via peeps like you who want to give them hand-me-outs which is hardly enough to maintain a business, let alone a realistic economical model. Ximian is a VC money pit. Sure they may make cool and very useful stuff. If its released under the GPL (which I don't even know for sure if it is), they simply will not succeed.

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

      Wrong. Sun makes money from selling hardware. AOL makes money from selling a service, i.e. Internet access and content.

      Who cares? I like Mozilla, I also like the fact that it's GPLd. I wasn't so keen on Open Office last time I looked at it. In neither case is how the company makes its money an issue for me. Shawn Gordon's inability to make money on GPLd software simply isn't my concern.

    6. Re:What? by J.+Random+Software · · Score: 1

      That's only true if the company's business model consists of selling copies of the software they wrote with their own money. If they were paid to write it, or are in any business other than selling software, they could easily come out ahead on having access to others' contributions.

    7. Re:What? by kevlar · · Score: 2

      Shawn Gordon's inability to make money on GPLd software simply isn't my concern.

      ... and that my friend, is precisely why there will never be a company that utilizes the GPL and actually turns a profit.

    8. Re:What? by Anonymous Coward · · Score: 0

      ... and that my friend, is precisely why there will never be a company that utilizes the GPL and actually turns a profit.

      You seem to be suffering a touch of amnesia since you've already covered the point that Sun and AOL utilise GPLd software and make a profit. So do IBM and any number of companies. The point you were making before you suddenly lost the plot was that you can't make a profit by selling licences to use free software, and frankly if anyone's stupid enough to try to sell licences to something openly licenced to all then that's their problem.

      Free software can be developed and supported, we know this because it is in fact developed and supported. Who cares where a company can make money selling licences to it (which, again, OF COURSE THEY CAN'T).

  29. The correct url is by Anonymous Coward · · Score: 0
  30. Re:He doesnt get it by Anonymous Coward · · Score: 0

    And there you have it...

    theKompany's software is far from crappy with
    Blackadder i can even make Free software ;)

  31. Re:He doesnt get it by Anonymous Coward · · Score: 0

    Nice troll -- topical, content-free, with a nice tweak at the end. Keep it up, kid -- you'll go far.

  32. wonderful /. by MegaFur · · Score: 0, Offtopic

    Gotta love that slashdot quality.

    --
    Furry cows moo and decompress.
  33. Free source by dachshund · · Score: 2
    On at least a weekly basis we get someone telling us that we have to give them the source code because it is GPL. Some of them become verbally violent and abusive when I point out that the GPL provides for us to charge for the source code, we just have to make it available, and this we have done.

    What Shawn said is correct. The GPL only requires you to provide the source code on request (for a reasonable fee). However, most companies realize that it's a whole lot less trouble to put the source up on a website than to deal with obnoxious people on the phone. This is an excellent example of that phenomenon, and though I agree that folks shouldn't try to hack into a server to get the source, people do have the right to vent their frustration over the phone. If theKCompany doesn't like it, they can easily address the problem.

    I'm also curious why some of these folks didn't just write away for the code and post it on their own site. This is the best way to guarantee that code is easily available. Perhaps some did, and the "hackers" were just too lazy to google for it. Or maybe the "hackers" were just typical malicious types who would have gone after any company with every bit as much gusto.

  34. appropriate licensing by Anonymous Coward · · Score: 0

    The GPL is not always the most appropriate license depending on your goals -- not just commercial goals, but political goals, as well. Imagine if Google had GPL'd their search engine software. We would be out a really great search engine, because they would be unable to fund the bandwidth required to have a product as great as theirs. They are a very important part of the community, however, since they are demonstrating the cost-effectiveness of Linux in an enterprise application. Sometimes it's more effective to use a proprietary license to achieve the Free Software goals.

  35. You're partially correct by Anonymous Coward · · Score: 0

    The GPL lets you charge whatever you want for the act of distributing software. However, if you charge $4000 and only distribute binaries, that is when you must supply source for no more than a reasonable copying fee.

  36. Re:He doesnt get it by Graymalkin · · Score: 2

    You are the one that doesn't get it. He charges for the source code, this in no way removes the GPL definition of freedom from the software. Don't fucking bitch because you can't download the source code for zero dollars. Can you get the source and change it under the terms of the GPL? Yes you can. No GPL endowed freedom is removes. What part of that don't you get? The Free Software community isn't necessarily a community that gives their code away for zero dollars.

    This confusion and retarded statement is a direct result of RMS and his dumbfuckery using recursive definitions. The free as in beer free as in speech crap has caused more needless confusion than LSD. The GPL goes into the fact you can charge money for your source code. The provisions for the "free" software are source code must be available. It doesn't say I you can't require someone to reimburse you for your work.

    --
    I'm a loner Dottie, a Rebel.
  37. Paradox by nagora · · Score: 2
    The odd thing is that I agree with Gordon as regards making money on GPL'ed software but, on the other hand, I think a world without the Kompany's products would be a better one. Perhaps the answer is to make good software and to hell with the license.

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  38. Background info by Mr+Windows · · Score: 2

    The interview says "We sell one product that is GPL", but doesn't mention which product, but a bit of Googling reveals that it's Korelib, and in principle there's a uri for the source: ftp://ftp.rygannon.com/pub/Korelib/releases/koreli b-0.0.1.tar.gz, though the server is very reluctant to let anyone in. I got the message "Sorry, rygannon.com already has 6 users logged on. Try again in 10 minutes.". A bit more Googling reveals that there are RPMs and debs (libkore0) available, and I can (on my Debian box) get the source with apt-get source libkore0.

    1. Re:Background info by Dr.Dubious+DDQ · · Score: 2

      Actually, I don't think that's it (I'm trying to figure out which one that they SELL is GPL as well...). He's specifically talking about SELLING something and demanding money to see the source code, but they've got download links to Korelib right their on their own page for it and no place to click "add to cart" for it...

  39. Re:He doesnt get it by slaughts · · Score: 1

    Gordon can't post a message without trying to belittle Gnome is some way. He has been doing this since his name has been 'known' which is why I don't pay any attention to him. If you are so unhappy, Mr. Gordon, please go and write some closed-source, Motif apps and sell them for Solaris, AIX, etc., and not have any license issues to worry about. And thank the Gnome folks on at lease one occasion for giving people an alternative that they can choose.

  40. "We won't use the GPL for anything anymore." by Anonymous Coward · · Score: 1

    I guess its time to say goodbye to QT and open source KDE apps.

    1. Re:"We won't use the GPL for anything anymore." by GlowStars · · Score: 1

      I guess its time to say goodbye to QT and open source KDE apps

      Care to explain why?

  41. very foolish by 47PHA60 · · Score: 1

    If you want to contribute to a "commons" for software, release it under the GPL. If you want to sell it, you should probably not release the software or code under the GPL or a BSD license.

    The important point here is not how much you are permitted to charge for access to the software and source code, but that you cannot stop the recipient from redistributing it.

  42. link misleads - plz edit post by darthlazy · · Score: 0

    the "theKompany" link leads to thecompany.com not thekompany.com.. please edit..

    --

    you can pick your friends,
    you can pick your nose,
    you can't however,
    pick your friends' nose.
  43. Re:He doesnt get it by jonbelson · · Score: 1

    (I doubt that.. he stuff is not open source).. But he is definitely not part of the Free Software community. We can even consider him a parasite that tries to suck the Freedom out of our free desktops.

    Kamera, KDE-DB and leafnode are open source.

    --Jon

    http://www.witchspace.com

  44. Strange notion of support by t_hunger · · Score: 1

    Is it only me or does Gordon think that suppoort is holding the users hand during the installation?

    Support is adapting the software to the needs of a user (company). So writting a new module to connect to some proprietary server is 'Support', rearranging the whole UI is 'Support'. All this is completly independent of the userfriendlyness of a piece of software.

    Well, if he want's to use something else but the GPL, in god's name, let him do so! As long as he does not use GPLed code in his products and thus plays according to the GPL rules...

    --
    Regards, Tobias
  45. Let's clear this ALL up right NOW... by wrinkledshirt · · Score: 0, Offtopic

    There's only one possible explanation between the continued jabbing back and forth between the KDE and GNOME camps.

    Two words.

    "Sexual tension".

    --

    --------
    Bleah! Heh heh heh... BLEAH BLEAH!!! Ha ha ha ha...

    1. Re:Let's clear this ALL up right NOW... by Dr.Dubious+DDQ · · Score: 0, Offtopic

      Thanks for that. Now I'll be having nightmares about tiny green scaley children wearing pointy red hats, lurking around unsuspecting people's gardens...

      What's your mailing address, so I can send you my therapy bills? :-)

  46. Why you make it usable... by sterno · · Score: 2

    First of all you need to meet certain usability constraints before anybody will use your software in the first place. Second, if you don't make it usable and relatively bug free, somebody else can come along and hijack your software and fix it (or write something new from scratch that is better).

    Remember that a corporation doesn't pay for software under the assumption that it's going to be a pain to use and buggy. They assume it's going to work well and yet they still pay for support contracts as insurance. It's risk aversion and has almost nothing to do with the inherent quality of the product. I worked at one company where they actually forced Microsoft to sell them copies of IE (yes, SELL, for money) so that they could feel they had some leverage in seeking support if something went wrong with it. Corporations will always buy support contracts for the same reason that people get health insurance. You don't buy health insurance because you plan to get sick, you do it just in case.

    Now, assuming that corporations are going to get support contracts anyhow, the underyling financial model of support contracts becomes important. If you pay me $50 and it costs me $25/hour to support any problems you have, then I need to keep it under 2 hours in support calls or I'm losing money. Companies don't want to get into open ended time and materials contracts, so you have a strong incentive to get rid of bugs because they cost you money.

    Having said all that, I grant that if you could write a piece of software that was:

    1) instantly intuitive for everybody to learn and use
    2) completely bug free

    Then the service models would cease to be viable. Furthermore, I'd personally open a church to honor your name since you are clearly a God of some sort.

    --
    This sig has been temporarily disconnected or is no longer in service
  47. he's right by mark_lybarger · · Score: 2

    he's probably right, it doesn't work for a business to release their gui application as gpl source code. if you business model is based on producing IP, you want to try to get some revenue generating from that IP.

    this could too very easily be taken to sound like quality, business level software doesn't come in the form of a gpl. many times when i mention to people that i use free software, they get some look in their face like i'm using low quality tools. articles like this scare busnisess folks away from the gpl/free software.

  48. The Corporation? by Anonymous Coward · · Score: 0

    Oh, good! I thought maybe they meant The Coroporation... though, in checking that my url was correct I found that it's gone! Anybody know when it died?

  49. Establishes a fair playing field... by sterno · · Score: 1

    Basically the GPL, as you point out, provides a good way to get developers to put source code out into the world. The advantage that it has over some other options is that it also forces other people to do the same for you. It's not so much you don't want people to make money off your code, rather that you want to have equal opportunity to make money off that code. It prevents situations where you write 10,000 lines of code, some other guy adds 5 and then he packages the whole thing to sell and you get nothing. You could turn around, take his 5 lines, and do the same thing.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Establishes a fair playing field... by Anonymous Coward · · Score: 0

      If 5 lines of code make the commercial version of the program that much better, that the original program becomes that much less useful, then the original coder deserves what he gets.

      I realise that what you stated is probably hyperbole but using it makes your argument far less compelling rather than more compelling.

  50. Why selling support doesn't work by LordNimon · · Score: 5, Insightful
    but they should only really need support if our software is hard to use or poorly designed

    Gawd, I wish every GPL advocate really understood the significance of this statement. If you give the software away and sell support, then the only way you make money is by getting enough people to pay for support. Logically, the more valuable the support is, the more likely people will pay for it. In other words, people will only pay for support if they need it. So what kind of support could a user want?

    1. New features or other code modifications, like customizations specific to your company
    2. Outsourcing of installation or deployment. That is, instead of installing the software on every computer in your company, you hire them to do it for you.
    3. Help with using the product itself.
    Let's evaluate the problems with these on a case-by-case basis:
    1. Because the user has access to the source code, it's possible for him to make the modifications himself. In fact, the GPL encourages this. So chances are, he won't pay someone else to do it.
    2. Only large corporations will be interested in this, and only if the corporation has an insufficient internal IT staff to do the job itself.
    3. The end-user will only pay for help using the program if he can't figure it out himself. However, the easier the software is to use, the less help the user will need. That's what the term "ease-of-use" is all about. So the developer has an incentive to make the software hard to use, to improve the likelihood that the customer will pay for support. In other words, the pay-for-support-only model is completely contrary to making the software easy to use! The ramifications of this are astounding. It results in a business model that encourages making the product difficult to use, but not too difficult that people won't use it.
    The kicker is that because the revenue model is so weak, the company will charge more for support than if it also sold the software.

    Although I hate Microsoft as much as anyone else (I'm an OS/2 user, so I've been hating them longer than most Slashdot readers have), they have been trying to explain these issues to everyone. Of course, in typical Microsoftian style, all they end up doing is making themselves look stupid to anyone who isn't computer illiterate.

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
    1. Re:Why selling support doesn't work by Dan+D. · · Score: 2
      Because the user has access to the source code, it's possible for him to make the modifications himself. In fact, the GPL encourages this. So chances are, he won't pay someone else to do it.

      Not if he's some small ma'n'pa shop who knows how to sell antiques and would really like to inventory on a machine, but doesn't want to get a batch of source and try to figure out what the word compile means.

      Only large corporations will be interested in this, and only if the corporation has an insufficient internal IT staff to do the job itself.

      Large corporations are probably the only entity *with* an internal IT staff.

      The end-user will only pay for help using the program if he can't figure it out himself. However, the easier the software is to use, the less help the user will need. That's what the term "ease-of-use" is all about. So the developer has an incentive to make the software hard to use, to improve the likelihood that the customer will pay for support. In other words, the pay-for-support-only model is completely contrary to making the software easy to use! The ramifications of this are astounding. It results in a business model that encourages making the product difficult to use, but not too difficult that people won't use it.

      This is definitely one way to look at it, and I don't really have an argument against that because I think some people really do operate that way. However, working in one of those corporate development positions I can speak directly to my users. Even with this much involved, we still have to take time after each delivery to explain what's changed in this version and what's new. Not because we made it difficult for them to use, that wastes alot of our time, but because they haven't seen this before and the new features they wanted in this release aren't going to be sticking out at them like the Paperclip (because our users aren't stupid enough to request a paperclip...)

      Selling support to a large corporation probably isn't going to work, but selling a corporation on the idea that they wouldn't need a large internal support unit may.

      --
      People who quote themselves bug the crap out of me -- Me.
    2. Re:Why selling support doesn't work by macshit · · Score: 1


      1. Because the user has access to the source code, it's possible for him to make the modifications himself. In fact, the GPL encourages this. So chances are, he won't pay someone else to do it.







      Of course he can, but I think the point is that many customers don't want to, because it means they've got to become experts themselves. So unless the prices for support/enhancement are too high, many customers will buy support anyway. Note that it's possible for other companies to offer support for the product, but I guess the conventional thought is that the original supplier has an advantage (as long as their prices are reasonable) because they are more knowledgable about the product (having written it), and probably more familiar to the customer (having supplied them).



      It would seem that the effect of the GPL would be to keep prices reasonably low -- but not at zero!

      --
      We live, as we dream -- alone....
    3. Re:Why selling support doesn't work by dido · · Score: 2

      You're right on almost all points, however, I think that you have gotten things slightly wrong with point #1:

      1. Because the user has access to the source code, it's possible for him to make the modifications himself. In fact, the GPL encourages this. So chances are, he won't pay someone else to do it.

      Most of the companies who need specific modifications are generally unable or unwilling to perform these modifications themselves. If you have one of those companies which are not in the business of actually writing and creating software (and of course there are far more of these than those that do), for them to actually make customizations of some GPLed software for themselves is counterproductive and wasteful. Yeah, if you think of it this way, they'd pay someone else to do the work I think.

      Programming is not easy work, and understanding and making modifications to someone else's code is even harder. Have you ever tried to make major modifications to a large free software codebase? If so, then maybe you'll understand why most enterprises are reluctant to do this kind of work themselves, and prefer to outsource such work to other companies that specialize in the task.

      --
      Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
    4. Re:Why selling support doesn't work by KjetilK · · Score: 2

      Because the user has access to the source code, it's possible for him to make the modifications himself. In fact, the GPL encourages this. So chances are, he won't pay someone else to do it.

      Or chances are, he doesn't care to do it himself, so he will pay somebody else to do it! Look, there are very few coders out there, most people would rather pay somebody else to do it than do it themselves. I can do some coding, but a lot of work is something I would like to pay somebody to do.

      Only large corporations will be interested in this, and only if the corporation has an insufficient internal IT staff to do the job itself.

      Where have you been? Outsourcing is the Cool Idea of the Year in the Business world. Outsourcing is hot. Many corporations don't want a internal IT staff (at least not a big one), and they certainly don't want a bunch of hackers sitting around. They just want to focus on their business, and everything that isn't their business they outsource or buy from somebody else. OK, there are many different models out there, but this is certainly not as simple as that. However, some clued managers appreciate the fact that with free software, you can take things in-house if all else fails.

      The end-user will only pay for help using the program if he can't figure it out himself. However, the easier the software is to use, the less help the user will need. That's what the term "ease-of-use" is all about.

      Well, you can't drive a car without training, and if you don't know how to use a chainsaw without a good chance you will not be hurting yourself and others, you shouldn't use it.

      OK, there are software systems that are very simple, and that you can go on using without any knowledge whatsoever.

      But then, there are many tasks that you need some brains to accomplish. While "ease-of-use" today means that it should be easy to a beginner, what it should mean is that it would be easy for an experienced operator to do powerful things, and then, trainers should focus on how to teach people to become power users in the shortest possible time.

      So, there are a lot of money to be made in this anyway.

      --
      Employee of Inrupt, Project Release Manager and Community Manager for Solid
  51. So -- he chose the wrong license. by hey! · · Score: 5, Insightful

    GPL is a license chosen by authors who want their source code to be available and to remain available. The question is, why should they have chosen GPL for this product? If they are the sole author of their product, then GPL is simply a really poor choice for what they wanted to achieve and they should simply release under a different license. In this case, he may have a point about GPL activists.

    If this product is a derivative work, then they were forced to use GPL. In that case, charging high reproduction fees to create a barrier to users (as Mr. Gordon frankly admits he is doing) is a violation at the very least of the spirit of GPL, if not a legal violation. It breaks the understanding under which he was granted the right to use the original work by the original authors. In this case he has no right to complain about people attempting to find clever ways to get their hands on source code without paying, since he would be doing exactly the same thing.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:So -- he chose the wrong license. by jbn-o · · Score: 1
      The question is, why should they have chosen [the] GPL for this product?

      Because unlike so many other free software licenses, the GNU GPL is written by an organization well-versed in both programming and law, it now has genuine court time under its belt (with a judge that shows no indication of finding it to be an invalid license), and it has language to handle a number of cases that come up (including patented code, maintaining software freedoms for derivative works, distinguishing between linking and executing as a separate program).

      More importantly, they should have selected a license they understood and agreed with. I cringed early on when Shawn Gordon indicated his ignorance:

      I didn't really care so much, or pay attention to all the licensing stuff...

      There's the first problem. People who ignore software licensing can not run a software business effectively. Gordon should have taken the time to learn about licensing or he should have hired someone to train him on the details of licensing. Licensing is as important to your code as your code is to your business. If you ignore licensing, you will regret it. If you find out too late you don't agree with the license you chose, you might have already done something not in line with your business plan. This is nobody's fault but his.

      If this product is a derivative work, then they were forced to use [the] GPL.

      Nobody is ever forced to use the GPL because nobody is forced to derive their program from a GPL'd work. It's important not to overlook that they could have written their code from scratch or based their work on something else.

      In that case, charging high reproduction fees to create a barrier to users (as Mr. Gordon frankly admits he is doing) is a violation at the very least of the spirit of GPL, if not a legal violation.

      It is not any kind of violation. You are encouraged to charge as much money as you can get for distributing free software. The "free" in free software refers to freedom, not price, and giving away your free software is wasting an opportunity to make money for development.

      In this case he has no right to complain about people attempting to find clever ways to get their hands on source code without paying...

      Gordon does appear rather unclear on the GPL. But, not paying attention "to all the licensing stuff" will do that to you.

  52. Re:He doesnt get it by Tester · · Score: 2, Interesting

    How is he removing them freedom? He gives the people that buy his software the source code. If you don't buy his software, you don't get it. He hasn't taken away any freedom. He just hasn't given you anything.

    He is taking away the freedom of his users to user/modify/share the software. This is clearly opposite to the way the FSF sees the world. He is clearly doing something that the Free Software community thinks is wrong and that the GPL was written to prevent. So he shouldnt complain that the GPL is making is life harder because that's exactly what is was written to do. Make as much code Free as possible. His software is useless to me.. I dont want it. What worries me is that its availability will discourage people from making a good free replacement.. That's how he is taking away my freedom...

    My main point is that his business model is exactly what the GPL is there to prevent, so its normal that he doesnt like it... But many people dont seem to get that. The FSF wants all proprietary software to away! And yes, that will piss off proprietary software vendors!

  53. Strange argument against free (as in beer)software by k98sven · · Score: 3, Interesting

    From the article:
    Look at it this way. I can send 1,000 copies to a distributor who will put it on store shelves around the world. People will walk in, pick it up and buy it. Now let's say that the software was free (as in cost) and I just sell services. Well, now I can't put it on a store shelf and for every customer; I have to go and hunt them down somehow and persuade them to use our free software and then pay us for support -- but they should only really need support if our software is hard to use or poorly designed, which isn't the case or our objective.

    Now this is an argument, but he doesn't adress the most common case, namely:
    You package the thing with manuals and charge for it (with 30 days free support),
    but also provide a free download at your site.
    Now send it to the distributor.

    This is how most distros work, and Redhat seems to be doing fine. Even I was surprised when I saw SuSE Linux on the shelf at the store Åhlens
    (~Walmart, but not cheap) here in Sweden last christmas, that's good market penetration!

    But he does have a point: Consumer-oriented products shouldn't need support.

  54. I think the problem isn't politics. by Anonymous Coward · · Score: 2, Insightful

    The GPL *can* be used for sexy, graphical, user-friendly stuff. Look at KDE - as much as I hate it for being a Microsoft clone, I will admit it does look sexy. And look at the sheer graphic beauty of Enlightenment (If you've got a beefy box).. I'd say that's graphically sexy, moreso than anything Microsoft has produced at least.

    Userfriendliness is another issue (I fail to see MS Windows or clones as userfriendly), but that's another matter.

    Here's the thing - many of the best people working on Linux projects are command line commandos. They don't *need* sexy, user-friendly interfaces.

    The people who do may be journeyman coders, but they tend not to have the experience necessary to lead large groups to the end of a project.

    I do think we'll continue seeing vast increases in graphic beauty and userfriendliness as more people use Linux. Look what we've already done.. E!, KDE, etc. It's a far cry from some of the things being distributed with earlier distributions.

    Anwyay, in the end, I think people will wise up and start using the best tool for the job. Want a low cost decently stable server? Use Linux. Want the latest and greatest games? Install MS Windows (Or even better, learn how to code, how to write docs, or how to test things, and hop onboard a Linux project. :))

  55. Proprietary software companies (in general)... by Dr.Dubious+DDQ · · Score: 3, Insightful

    It seems Mr. Gordon's complaint with the GPL is similar in nature (but not quite the same in "spirit") to Microsoft's - "If someone releases software under the GPL, the license says that if you redistribute something made with it, you have to also make your changes available under the GPL, and, gosh, that's just too much hassle. No fair." (more or less).

    That's what the GPL is FOR. Now, don't misunderstand - I'm GLAD to see (believe it or not) proprietary software available as a choice, whether I would choose to buy any or not. I also have no problem with a company choosing to avoid GPL-licensed code because they don't want to deal with the hassle of contributing back to the community in the manner that the GPL requires. I further sympathise and agree with Mr Gordon's characterization of the handful of loud, self-appointed "GPL Zealots" that tarnish the reputation of the more numerous but quieter "normal" people who just happen to agree with the GPL's philosophy.

    What I DO dislike is hearing companies' ever more frequent complaints about not having permission to do whatever they want, at whatever price they want, with GPL-licensed source code. First MS, now TheKompany (and surely I've missed one or two others in between, didn't Caldera or someone from Mandrake or Red Hat say something similar a while back? I forget...). It seems obvious to me that if a programmer offers original source code under the GPL license, it's BECAUSE they don't want their work to be capitalized on without the "community" benefiting at the same time. In that respect, the writing in this opinion piece might have been "I went outside while it was raining, and I discovered that I got all wet, and people who I visited sometimes got unreasonably upset when I dripped all over their floor, and some of them got irrationally upset when I told them I wouldn't dry myself off before coming in if they didn't supply the towel for it themselves. Therefore, I felt compelled to write another editorial explaining why rain is bad for people who go outside..."

    Please excuse the touch of "rant" in this post. In fairness I should emphasize that I can't fault TheKompany themselves too much, as they DO seem to contribute in one way or another back to the community (e.g. the GPL'd version of Kivio in the KOffice CVS), and even their "proprietary" license seems pretty darn reasonable as far as proprietary licenses go, but the continued complaints by proprietary software companies in general that the GPL doesn't let them redistribute proprietary, modified versions with restrictions (and typically at the same price as completely proprietary software developed from scratch, it would seem) and the implication that follows that it is therefore somehow "unfair" or unduly burdensome is just getting on my nerves...

    (On the plus side, at least the complaints reaffirm that if you don't want your software to be "hijacked" for the profit of proprietary software companies [which here I define as companies whose business model is "charge for permission to use software"], the GPL will keep them away...[and for the moderators reflexively reaching for the 'flamebait' button, I reiterate - I'm not accusing TheKompany, specifically, of doing this])

    1. Re:Proprietary software companies (in general)... by mwa · · Score: 2
      I hate to spoil a perfectly good rant, but he's not talking about taking someone else's GPL code and doing what he wants with it, he's talking about doing what he wants with his (or, theKompany's) own code that they happen to have released under the GPL.

      This isn't even close to the "don't touch GPL code" philosophy of most proprietary vendors. I think the significant point he raises is that the zealotry of some GPL bigots has pushed theKompany to the point that, although they've used the GPL in the past, they're unlikely to do so again.

      In a sense, the GPL bigots (a small and vocal subset of GPL supporters) have managed to snatch defeat from the jaws of victory. They've subjected a GPL friendly vendor to enough abuse that they're turning their backs on the GPL.

    2. Re:Proprietary software companies (in general)... by Anonymous Coward · · Score: 0

      This isn't even close to the "don't touch GPL code" philosophy of most proprietary vendors. I think the significant point he raises is that the zealotry of some GPL bigots has pushed theKompany to the point that, although they've used the GPL in the past, they're unlikely to do so again.

      In a sense, the GPL bigots (a small and vocal subset of GPL supporters ) have managed to snatch defeat from the jaws of victory. They've subjected a GPL friendly vendor to enough abuse that they're turning their backs on the GPL


      According to him they only produced one program under the GPL so it doesn't sound like they've ever been that keen on it and there doesn't seem to be any basis in the article for supposing that they chose the licence themselves rather than because they wanted to build on other people's GPLd code.

      Also you seem to have missed the main thrust of his essay. He says :

      I can send 1,000 copies to a distributor who will put it on store shelves around the world. People will walk in, pick it up and buy it. Now let's say that the software was free (as in cost) and I just sell services. Well, now I can't put it on a store shelf and for every customer; I have to go and hunt them down somehow and persuade them to use our free software and then pay us for support -- but they should only really need support if our software is hard to use or poorly designed, which isn't the case or our objective.

      This has got nothing to do with "GPL bigots". His problem is with the whole idea of free software. He wants to adopt a proprietary software model. BSD or any other free software licence is no better for this than GPL. It isn't bigots, it's practical packaging and selling software that people can get for free that's his problem. The business he wants to run is not compatible, so far as he can see, with providing free software.

    3. Re:Proprietary software companies (in general)... by Chris+Johnson · · Score: 2
      It is hard to credit anyone behaving this way as being 'GPL friendly'. I could see 'unclear on the concept'. But when it is so unclear that it starts harming the concept, then what?

      The basic concept behind the GPL is, 'Access to ideas, at all costs'. Nothing's allowed to get in the way of that.

      Shawn Gordon is twisting an implementation detail of the GPL ('try to prevent GPL developers from being bankrupted by demands for copies of the source- a 'DOS attack', demand of source!') into a conflict with the basic desire of the GPL ('access to source, at all costs'). Someone should pay for his source and then mirror it far and wide, and the development should be forked away from him.

    4. Re:Proprietary software companies (in general)... by mwa · · Score: 2
      It is hard to credit anyone behaving this way as being 'GPL friendly'.

      Not anymore. That's his point.

      Someone should pay for his source and then mirror it far and wide, and the development should be forked away from him.

      First, they aren't charging for "the source", they're charging for the product. In accordance with the GPL, the source is also available to whoever acquires the binaries.

      Second, forking is fine. The GPL allows for this, and theKompany knew that going in, yet they still chose the GPL. This was a fairly bold move for a company that's trying to make a buck on software. So go ahead and fork it, but don't expect them to continue to support your ideals with their code.

      Your problem is that, despite the actual terms of the GPL, if someone doesn't play by your interpretation then they're wrong, even when RMS agrees that they are not. You aren't going to get more companies to buy into the GPL by treating those that are trying as a free teat to suckle at. All you, and whiners like you, have managed to do is convince theKompany that the GPL is bad for them. The result is a company that was GPL friendly isn't any more. And the reason is not that the GPL is bad for them, it's that the GPL fanatics are too expensive and annoying to babysit.

      The GPL has met it's enemy, and they are it's most vocal supporters. The sooner they get under control, the better off the GPL will be. If they don't get under control soon, the GPL will be dead for commercial products. I support the GPL. I want more GPL code. We're not going to get it by blasting contributors because they want to contribute code AND make money, too.

  56. Does he read his own writing? by ajs · · Score: 4, Insightful

    This man has a very skewed idea of what's going on here. He says that he gets regular complaints that they don't release the code, and then tries to jump from there to the idea that using the GPL has hurt them.

    Um... sorry guy, but Microsoft gets this complaint EVERY DAY OF THE YEAR. Hell, they get that from much larger and more influential commers than poor little RMS.

    As for RMS, if I had a dime for everyone who had a troubling conversation with RMS, I'd probably be providing dimes to the US Treasury... they would be out. RMS is a fanatic. This is neither good nor bad, really. He has done a lot of good because he cares a heck of a lot more than he should. He's also refused to back down from some ideas which are pathalogically idealistic, and that has caused any number of problems. In the end, I think we should all reality-check Open Source against RMS just to keep that perspective, but he should never be thought of as the ultimate voice of anything (including, oddly, his GPL).

    The GPL is an amazingly good tool for protecting free software AS free software. If that's not your goal, you probably chose the wrong license :-/

    Sorry man.

    1. Re:Does he read his own writing? by Anonymous Coward · · Score: 0

      Um... sorry guy, but Microsoft gets this complaint EVERY DAY OF THE YEAR. Hell, they get that from much larger and more influential commers than poor little RMS.

      Sorry to have to tell you this Aaaaaron, but you seem to think that "Um..." means "I do not agree". You are mistaken. It means "I learned to speak by watching Friends". Now, even though you have a poor command of the language I am going to explain to you what is wrong with your comparison with Microsoft:

      They don't fucking care what GPL-loving freeloaders say.

      Choosing to avoid the GPL might not make you treat your customers like Microsoft does, but it removes the expectation of those customers that they are entitled to get your source code.

    2. Re:Does he read his own writing? by ajs · · Score: 2

      Sorry to have to tell you this Aaaaaron

      My name is Aaron. Look it up. In your average dictionary, it comes pretty early, usually just after aardvark. Sorry for being snippy, but your next comment:

      you seem to think that "Um..." means "I do not agree". You are mistaken. It means "I learned to speak by watching Friends"

      was not appreciated. When I use "Um", I am attempting to convey a confused pause. Simply using ellipses would not suffice, e.g.: "... sorry, guy".

      [Microsoft doesn't] fucking care what GPL-loving freeloaders say.

      Heh... (used to indicate amusement). First off, Microsoft spends a very large ammount of money on countering the credibility of those "GPL-loving freeloaders" via their marketing and PR departments, so I think they care quite a lot.

      Second, Microsoft gets these complaints from such varried sources as OEMs, third-party software developers and a number of states. They have been asked, at various times, to release the source to their APIs, implementations of proposed standards, implementations of other companies' proposed or existing standards (e.g. Java), browsers, etc, etc.

      Choosing to avoid the GPL might not make you treat your customers like Microsoft does, but it removes the expectation of those customers that they are entitled to get your source code.

      It depends on what license you use. Certainly, if you use a license that says that your users are entitled to the source code, you're really going to have to expect to get called on it.

      That's really what got me about this article. This guy released code under a license that was intended to ensure that source code was available, modifiable and re-distributable... and then he expected people to understand when he didn't want to give up the source.

      Odd.

      Have a nice day, Mr. Coward.

    3. Re:Does he read his own writing? by Anonymous Coward · · Score: 0

      Come on Aaaaaron (in your average dictionary proper names are not to be found), think critically - Microsoft doesn't care about what GPL-loving freeloaders say at all. They care about what paying customers think. The customers are unlikely to even hear the rants of the software communists, because those smelly hippies don't spend money to make themselves heard - they participate in circle-jerk discussions like this one here and believe the world will magically change as a result. In fact Slashdot seems to do as well as any site in propagating statements from Mundie, etc., all for free! Thankfully most of those customers are professionals anyway, people who understand that anything of worth costs money. (Those people wouldn't piss on RMS if his beard was on fire, although hopefully they would record the event, because I would love to see it.)

      They have been asked, at various times, to release the source to their ...

      And because they have not given in to the temptation of attempting to curry favor by using the GPL or other so-called "free" licenses they have been free to say "NO". Which is why (and I want to stress this, you didn't get it the first time) any comparison with a company that did make that mistake is meaningless.

      This guy released code under a license that was intended to ensure that source code was available, modifiable and re-distributable... and then he expected people to understand when he didn't want to give up the source.

      Intent? If RMS can't write a license that spells out the terms, the terms, under which software may be distributed then he should leave it to professionals. Nobody but the people who want something for nothing give a fuck for intent.

      Have a nice day, Mr. Coward.

      You may call me Noël.

    4. Re:Does he read his own writing? by reflective+recursion · · Score: 1
      I have not found Microsoft paying any money to slam free software/open source. They may place a page or two of PR stuff on their web site, but where is this large amount of money they are spending? I'm sure not getting pounded by bulk mail saying "open source is bad." I believe they care about open source, but only because the value of software will become tarnished if average joe types (i.e. anyone who does not program, yet asks for open source.. i.e. probably 75% of Slashdot readers) start demanding all software become open source.

      Open source to a large number of people today means "no-cost" software. This is not good and definately not what GNU and the FSF stands for.
      Certainly, if you use a license that says that your users are entitled to the source code, you're really going to have to expect to get called on it.
      From what I understand, theKompany is selling GPL software and not distributing it freely. The users have absolutely no right to demand access to their source code. The GPL does not say that the source code licensed under it has to be distributed to everyone freely. Please read www.gnu.org and learn about the GPL before you spew this nonsense into an already confused community. You are the precise reason that theKompany is avoiding the GPL. You expect that if software claims to be GPL'd, then you should have immediate and direct access to it without pay. Little history lesson: RMS (yes, the guy who started GNU and created the GPL) used to sell disks with his program Emacs on them. IIRC, he sold it for quite a profit too.
      --
      Dijkstra Considered Dead
    5. Re:Does he read his own writing? by Anonymous Coward · · Score: 0
      Little history lesson: RMS (yes, the guy who started GNU and created the GPL) used to sell disks with his program Emacs on them. IIRC, he sold it for quite a profit too.

      Yeah yeah sure. And record companies used to sell music on CDs back before file sharing became so popular. Sold for quite a profit too.

      Oh wait they still sell for quite a profit. Hmm...

    6. Re:Does he read his own writing? by Anonymous Coward · · Score: 0
      They care about what paying customers think.

      Lately, you can add the Department of Justice and various states to that comment :)

    7. Re:Does he read his own writing? by reflective+recursion · · Score: 1

      File sharing w/ copyright music is illegal (in the US). Free software sharing is not.

      --
      Dijkstra Considered Dead
    8. Re:Does he read his own writing? by ajs · · Score: 2

      Come on Aaaaaron (in your average dictionary proper names are not to be found)

      I don't know who you're refering to, but my name (Aaron) appears in most dictionaries. It's a biblical name (that my mother chose for secular reasons, not that it matters), so the reference is almost always listed. Aaron was the grandfather of Eli, and the brother of Moses and the first high-priest of the Hebrew nation.

      you will find several references to it in on-line dictionaries as well....

      If you can't be bothered to check even a fact that exists at the very beginning of your dictionary, this conversation is really not worth having.

    9. Re:Does he read his own writing? by ajs · · Score: 2
      I have not found Microsoft paying any money to slam free software/open source.

      You haven't been paying enough attention.

      They've initiated a huge campaign against open source which as included: tailoring their sales pitch to convert oss customers back to Microsoft; using just about every high-profile member of the Microsoft staff (from Mundi to Balmer to Gates) to recite the reasons that they feel open source is harmful (using each one of these men costs the company a great deal of money in terms of the other efforts that they could be working on); trade show talks; creating "Shared Source"; etc.

      Certainly, if you use a license that says that your users are entitled to the source code, you're really going to have to expect to get called on it.
      From what I understand, theKompany is selling GPL software and not distributing it freely. The users have absolutely no right to demand access to their source code. The GPL does not say that the source code licensed under it has to be distributed to everyone freely.

      I could not agree more. You're 100% correct.

      However, my statement still stands. They're using the GPL in a way contrary to the spirit of the GPL. They should expect to get called on it. They should expect it to result in negative publicity (possibly their desire). An they most certainly have no right to act suprised that legions of whiners come knocking at their door. If they'd stopped and thought about it for more than a minute, they would certainly have known that was coming (I'm no more saying that this is a good thing, than when I tell someone that they should expect people to start trying to break into their system the moment they put it on the net).
  57. Pure FUD by megalomang · · Score: 1
    . To use it you must sign onto the Borg Collective though

    This is the kind of ignorant drivel that gives GPL a bad name. GPL is intended for someone to be able to create source to implement a great idea they want to donate to the rest of the world. They want to make sure that their idea will be used to benefit others, not hidden away in someone's proprietary software to fatten someone else's wallet. That would be absurd.

    The permission GPL grants is that others may use and modify for their own use a piece of software freely (no restrictions). For your own purposes, it's that simple -- no borg collective or other FUD. If someone wants to modify and redistribute the software, they must distribute it with the source code.

    If I wrote an ingenious new app and wanted to give it to the world, why shouldn't I be able to stipulate that nobody can repackage it and sell it without redistributing the source? If you don't like it, rewrite it so you can resell it! You have every right to do so.

  58. Why GPL is not a virus by Anonymous Coward · · Score: 0

    A virus (either real or software) doesn't ask your permission to "installs" itself, but you are free to use a GPL'd source if you agree on its conditions, and otherwise just don't use it.

    The author sets the license. Do you agree? Okay, just use it. Don't agree? Well, then you'll have to find something else or code it yourself.

    1. Re:Why GPL is not a virus by sithkhan · · Score: 0

      Then how do you explain EULA's and people who did not know that when the said "I Agree", they were giving their IP/pr0n/content provider exclusive rights to modify their machine WITHOUT their knowledge or tacit permission? Just because someone installs software doesn't mean they read all the fine print. So perhaps the virus analogy is valid. I hadn't thought about it that way before.

      --

      is it that bad seein a hot chick again? if i see a hot chick walkin down the hall i dont say "repost"
    2. Re:Why GPL is not a virus by danakil · · Score: 1

      Then how do you explain EULA's and people who did not know that when the said "I Agree", they were giving their IP/pr0n/content provider exclusive rights to modify their machine WITHOUT their knowledge or tacit permission?

      They said "I Agree".

      Just because someone installs software doesn't mean they read all the fine print.

      They have to. But here we're talking about developpers, not users.

      So perhaps the virus analogy is valid. I hadn't thought about it that way before.

      It is not, because if you release some code, you have to know that you're not allowed to use any kind of code you do not own, except public domain code. Then maybe, if you're lucky, there exists some code you can reuse (which license gives you the right to do this). Unless you find that you're allowed to do so, the code must be considered "forbidden" (for release, and even for use).

      Then someone releasing GPLd code with non-GPLd code could be sued, but that doesn't mean his code would become GPLd. He'd just have to stop releasing the actual software (since he has no right to do so), and maybe pay. The code doesn't "become" GPLd automagically. So there's no virus comparison.

    3. Re:Why GPL is not a virus by Principal+Skinner · · Score: 1

      One of the beauties of the GPL is that it is ALWAYS the SAME (sometimes mod a few special dispensations which are easy to find). That means if I download a piece of software that is GPL, I don't have to read the license; i've already read it fifty times in other pieces of software or on the FSF site, and unlike the other EULAs for all the various sofware procucts out there, I've seen this same one enough times that I can actually understand it and how to follow it.

      --
      one hundred twenty
      is just enough characters
      to write a haiku
  59. You guys are both wrong by burris · · Score: 4, Informative

    You can charge as much as you want for GPL software no matter where you got it from. However, if someone you sold a binary-only copy to comes asking for the source code then you have to make it available to them for a reasonable cost of media and distrobution only. You can't sell GPL software for $19.95 and then say source will cost an additional million dollars (effectively making the software closed source.)

    The clincher is you can't stop someone you sold a copy to from giving it away for no cost.

    burris

  60. Re:Klerck on page widening by Anonymous Coward · · Score: 0

    Hmm..must be a bug in IE. The margins are OK in Mozilla.

  61. Unless of course you have competitors by Anonymous Coward · · Score: 0

    in which case you don't want all the stuff specific to your industry being available to new startups...

    I write tools to help me do my work. There are several similar free tools out there but they are all rubbish. Our existing competitors no doubt have similar tools. I doubt my boss would want me to release my code to the world, since this would help potential new competitors.

  62. Fork It by sdowney · · Score: 5, Insightful
    If someone is really hot and bothered by Shawn's position on his software, then pay him for it, take the source, and put it on SourceForge. GPL gives you the absolute right to do so.

    This is the reason that the price of GPL software tends to zero.

    1. Re:Fork It by sh_mmer · · Score: 1


      This is the reason that the price of GPL software tends to zero.

      ...and one of the reasons that this company dosen't want to have anything to do with the GPL ever again.

      --
      Interested in learning Chinese or Japanese? check out Chinese/Japanese-English Dictiona
  63. Heres whats wrong with the GPL! by Anonymous Coward · · Score: 0

    Its viral, if microsoft mixed the windows source code with JUST ONE LINE, theyed be in deep shit. Thats why companies hate the GPL and wan't it to be destroyed.

    A much better licence is ADL licence, which covers the best of both worlds.

    But unfortunely, the GPL is anti commercial and the corperate world will NOT welcome it.

    Remember the QT liecence? it helped make a shoddy gpled rip off desktop clone of KDE which is now GPL anyway.

  64. Re:He doesnt get it by nakhla · · Score: 2

    Great statement, I agree totally. Of course, the best part of this comment is the word "dumbfuckery"! I laughed hysterically in my office when I read that one. :)

  65. GPL\GNU?? by great_flaming_foo · · Score: 1

    Also what is the difference between the GPL and the GNU license and why do we see them written as GPL\GNU?

    The last time I looked they are diffrent names for the same license. The nomenclature goes something like this: GPL stands for Gnu Public License. This and the lesser or LGPL at the licenses of choice for GNU projects.

    1. Re:GPL\GNU?? by jsprat · · Score: 2

      Actually, it's the (GNU) General Public License.

  66. Re:He doesnt get it by nirvdrum · · Score: 1

    What worries me is that its availability will discourage people from making a good free replacement.. That's how he is taking away my freedom...

    Where does the concept change? Now it's just people not giving you software that they never wrote. Furthermore, it's not like anyone owes you this unwritten software. How is that freedom?

    --
    If there was a "-1 Not Funny", that'd be my most used mod.
  67. And who will be selling software in ten years? by ondelette · · Score: 3, Interesting

    Honestly, the "I sell software" market is just not what it used to be. I think that the internet changed things. Software is now abundant, easy to come by.

    Except for games which aren't really 100% software (mix of art and code), the consumer market doesn't exist or will not exist much longer for software-only solutions.

    Corporations will always buy software... or will they? For niche applications, I think that proprietary software will always survive, but for generic software, I don't much of a future. As soon as the market is dominated by both free software (GPL and al.) and large corporations such as Microsoft, there isn't much room for growth anymore, not much room for new software companies.

    It has been my experience that coders working inside companies that sell code have had very stressful lives recently and this isn't about to go away. Salaries might be high, but requirements are also very though.

    So, not only is the market more difficult, but coders have a more stressful life... I just think that a lot of them will eventually switch to companies who make a living off something else (not software) and people who know the market well will not want to invest and start companies in the software industry.

    In ten years, you'll have Microsoft, Oracle, IBM, a couple more... and everything else will be free software.

    Want to bet?

  68. Re:He doesnt get it by An+Onerous+Coward · · Score: 4, Funny

    No, you don't get it. Neither do I. In fact, nobody could get it by reading the article, because he simply doesn't explain what he means by "charging for the source."

    If he means, "You don't get our GPL'ed product with source until you pay us $50," that's perfectly OK. If he means, "You get the binary for $50, and the source will cost you $5000 extra," then that's not okay under the GPL.

    In the latter case, Windows XP perfectly and completely fulfills the terms of the GPL. After all, if you were able to scrape together $300 billion, I'm sure Bill Gates would be more than happy to sell you a copy of the source code with unlimited distribution rights. And then come over to wax your Ferarri.

    --

    You want the truthiness? You can't handle the truthiness!

  69. Re:He doesnt get it by Tester · · Score: 1

    What worries me is that its availability will discourage people from making a good free eplacement.. That's how he is taking away my freedom...

    Where does the concept change? Now it's just people not giving you software that they never wrote. Furthermore, it's not like anyone owes you this unwritten software. How is that freedom?

    Well, its freedom because I can't do what I want to do with my computer without giving up my freedom. This is like saying, you are allowed freedom of speech, except that, you will not be allowed to work if you exercise your freedom. That's not freedom... That a parody of Freedom!

    But that was NOT the main point of my post, the main point was that he complains about the GPL while doing exactly what the GPL wants to prevent. So the GPL is working 100% correctly in that case.

  70. Charging for (GPLed) source code by Anonymous Coward · · Score: 0

    Some people seem to be walking away from this article thinking that a company can license their software under the GPL, and then keep people from getting at the source by charging large amounts of money for a "source cd" etc and not making it available as a public download.

    Not quite.

    Why not?

    1. First off, I believe their is a limit to what you can charge for sending people the source.

    2. Even if you could charge whatever you wanted for the source CD, all it takes is one person to actually pay the money to get a CD from you.

    Then that person can setup an FTP server where people can download your source, and people who download your source from that person can also setup FTP servers etc...

    That person can also burn 500 copies of your source CD and sell them for $5 U.S. + Shipping

    So in conclusion, if the original author of GPLed software is a real pain, they COULD make some trouble for the FIRST person who wanted to get the source MAYBE

  71. This just in! by Anonymous Coward · · Score: 0

    The sky is blue!

    Mozilla sucks! (Kinda funny, as I am posting this from Mozilla, which sucks)

  72. An essay that isn't six pages? by AIXadmin · · Score: 1

    Am I the only who is impressed that a essay written by a member of the free software community is only 3/4 of a page?

    My god, a concise well thought out essay. On todays internet, god forbid!

    1. Re:An essay that isn't six pages? by Anonymous Coward · · Score: 0

      Am I the only who is impressed that a essay written by a member of the free software community is only 3/4 of a page?

      A member of the free software community? I think he made it abundantly clear that he wants to be a memeber of the proprietary software community :

      I can send 1,000 copies to a distributor who will put it on store shelves around the world. People will walk in, pick it up and buy it. Now let's say that the software was free (as in cost) and I just sell services. Well, now I can't put it on a store shelf and for every customer; I have to go and hunt them down somehow and persuade them to use our free software and then pay us for support -- but they should only really need support if our software is hard to use or poorly designed, which isn't the case or our objective.

  73. bu*coff*it by miffo.swe · · Score: 1

    The reson that GPL apps dosnt have a single cooherent way of behaiving and arent user friendly is not because of the GPL license. Its rather a question of the diversity of the ppl developing for linux/bsd and others. Coherence is one way of gaining user friendlyness. Can anyone really call any now used OS really user friendly? Can it interpret your wishes and perform them as you like at all time? In time when you have learned one way you to do things you get custom of that way of doing things user friendly or not. A way of getting to userfriendly is to focus on how someone unused to computers would do. They rather compare to something in real life. Like a newspaper, a book or irl talk. The desktop analogy isnt a good one since it has gone too far away from the desktop as it is used at an office. Startbuttons and folders arent a very good way of handling big amounts of information as in todays computers. Take a stroll around your linux box, is it easy to get the big picture of your files and folders? Is it intuitive? The same thing with windows, just plain non intuitive. A way of fixing this would be to separate whats really on the HD and what the user see. Simplify it stupid! The final question is, can there be and OS for all? The technically gifted and those not_so_bright will have different opinions in the future too. I think that userfriendly linux and GPL apps would create a fork. One for technics and one for Joe. I think that thinking about endusers when creating apps is good but dont focus on it blindly.

    --
    HTTP/1.1 400
  74. GPL Compliance: The source will be "available" by petard · · Score: 2

    in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard."

    (with apologies to Douglas Adams)

    --
    .sig: file not found
  75. GPL great for others, but shouldn't apply to me by r0ckflite · · Score: 2, Interesting

    Everybody who's against the gpl or some subset of it wants to make money off their code. That's fine, but they want to be part of the open source movement too.
    His argument is so hilarious. GPL is fine for others, but I want to make money. I love the fact that I can base my code on free stuff and run it on a free platform, but I want people to pay for my stuff. sheesh.

    How's this: The OS should be free, but the device drivers should cost money. no, wait, the OS and drivers should be free but (insert your money making scheme here).

    He's a hypocrit IMHO.

    --

    Push the button Max!!!!

    1. Re:GPL great for others, but shouldn't apply to me by Anonymous Coward · · Score: 0

      Agreed. Microsoft sell operating systems and applications so they say that operating systems and applications shouldn't be under GPL. The Kompany don't sell operating systems but do sell applications so, surprise surprise, they think that GPL operating systems are great but applications, well that's different...

  76. Bandwidth Costs Money by SyntheticTruth · · Score: 1

    Okay, so they are charging for the source, and as you say, the GPL says the charge is for the cost of producing the source.

    Say, a couple bucks for a CD burn of a copy...

    ...or...

    ...or a couple bucks to pay for the bandwidth, the HDDs, and the hardware to host the source on.

    It all costs money, even if you could download the source from the above hardware for "free" -- it doesn't mean the existance of that download point cost them nothing to create nor to maintain.

    I see no problem here.

  77. Services vs payware, the 3rd way. by marcovje · · Score: 1


    People in pro or anti GPL items always focus on the
    entire codebase is GPL/ vs the "services/manual" branch.

    However there is a third, which is also the most common one. Mixing Open Source basic infrastructure with pure payware.

    The key point is that the GPL is viral, but only with respect to linking. Once you have several binaries that interoperate (a service and a client,
    OS and application, commandline compiler and fancy GUI high 0productivity IDE, virtually anything that
    is not "linked"), things change.

    Iow, the trick seems to be to open up the basic support, and sell the additions, make-it-easy-usable stuff etc.

    This is partially in line with the article. Sure,
    there is OSS GUI stuff, but only in a handful highly sponsored, all-industry, magical projects.

    There is hardly any small, but professional (fulltime) end user development.

    Sure, there are dedicated volunteers, and the eye
    catchers at StarOffice, Mozilla and Gnome, but nothing in between.

    I think that is really worrying. It might not be a
    real showstopper, but

    I come from the Delphi world, and the commercial
    activity in components is _very_ large, though it
    has some rotten aspects also.
    (too little free stuff, no multi vendor integrated libs, though Jedi is trying desperately)

  78. What's Stopping multi-bill transfer fees? by Jchrome · · Score: 1, Insightful

    Example of workaround to GPL:

    This software is a derivitive work based on an open-source GPL licensed forum system. This means that this derivitive work (FunnyExample Forums) MUST be free software as well (as stated in the GPL, free means in terms of rights, not in terms of price) per clause 2B of the GNU GPL [ http://www.gnu.org/copyleft/gpl.html ], the FunnyExample Forum system can be relicensed (including all source code) under the terms of the GPL as well at a source code transferrance charge of $30,000,000.00 U.S. dollars. Please note that this system is a seperate entity than the FunnyExample site, even though the application is called within an iframe in the site. This means that no portions of the site other than the FunnyExample Forums will be made available. If you are interested please contact me immediately!

  79. Fight FUD with FUD? by ergo98 · · Score: 2, Insightful

    It isn't FUD whatsoever : To use GPLd code you might apply the GPL license to your own code as well. That is a viral license, and just because you might not like the term viral doesn't mean it isn't so. Again, to each his own: And to some they think that's a great idea, but then there are people who seem offended when someone points out the reality so they cry FUD incorrectly.

    They want to make sure that their idea will be used to benefit others, not hidden away in someone's proprietary software to fatten someone else's wallet. That would be absurd.

    If someone incorporates your code, in no way do they make what you've actually created disappear or lesser (it doesn't matter how many people incorporate zlib in proprietary programs, you can still grab it from zlib.org), but instead the GPL is saying "here's what I've done....but now you have to give me what you've done as well.". It ISN'T protecting the original work because there is nothing anybody can do to degrade the original work. Instead it's claiming ownership over derived works as well. The real FUD is the perpetual claims of GPLers that somehow they would be deprived of their code is someone else used it in a commercial app.

    1. Re:Fight FUD with FUD? by danakil · · Score: 1

      It isn't FUD whatsoever : To use GPLd code you might apply the GPL license to your own code as well.

      It is FUD. A virus won't ask you to choose if you want it or not. GPL is not public domain, you can't use it without restrictions. The fact that you have source code doesn't mean you own it.

      Actually you just want to steal the code.

    2. Re:Fight FUD with FUD? by ergo98 · · Score: 2, Insightful

      Bah, whatever. My whole point is that BSD (and the many variants) developers are selfless, whereas GPL advocates are mostly moral crusaders imposing a vision (see Richard Stallman). A single .c file covered by the GPL is a virus if added to a project (yes, voluntarily, or because a moral crusader employee snuck it in) because it insists that all other files in your project, or that use its features in a binary fashion, ALSO be GPLd : That is a virus. I'm not the first to use the term virus, and I hardly think I'm the last.

      The stealing code comment is just pathetic. Yes every day I'm deviously scouring through BSD code laughing at how I'm taking advantage of them...oh wait : They are giving away that code. They WANT it to be used in whatever fashion you want.

    3. Re:Fight FUD with FUD? by dup_account · · Score: 1

      So it doesn't bother you the M$ (the real Borg) embraced and extented kerboros so that their implementation is incompatable with the rest of the world?

    4. Re:Fight FUD with FUD? by Anonymous Coward · · Score: 0

      And that damages kerberos in what way ?

    5. Re:Fight FUD with FUD? by megalomang · · Score: 1

      GPL isn't a virus in any sense. Yes, you are not the first to use the term. Rather, you are ignorantly joining the me-too bandwagon and repeating your favorite mantra.

      A virus is defined as a bit of code that autonomously finds a host for itself so that when that host is executed it can come to life and wreak havoc or self-replicate. So, by definition, GPL is not a virus.

      You might argue the GPL is instead a trojan horse, poised to take advantage of pathetic, unare individuals, that once granted access to the system (i.e. a source distribution) will unleash untold fury upon the poor idiot who added the source code to the project. This is far from the truth. The GPL (you apparently need to read it) mandates that any software that is to be distributed under the license clearly display the abridged license in source files and upon running command-line applications. Because the license information is prominently included in all source files with copyright information, any honest programmer (i.e. one that is not simply trying to steal source code) would note the copyright and exercise his full right to either comply with it by using the code and GPL'ing the resulting work or by not using the code.

      Either way, the programmer has a choice. There is no virus-like behavior whatsoever.

      If you are a programmer and agree with the GPL, you have been granted full permission to leverage any GPL'd code in your application provided you share the source of the result. If you do not agree with the GPL, take a hike -- don't use GPL code in yours.

      What I really don't get is what the hell this KDE guy is really complaining about. If he is using GPL'd code that he obtained for free, he shouldn't be bitching about it (i.e., never look a gift horse in the mouth). If he is GPL'ing his own code, he still owns the copyright (unless he gave it away, doh!) and can sell it all he wants. He apparently chose to incorporate GPL'd code into his software and thought he could make money off of it, but it turns out he was wrong. He made a bad decision. Really, it's not like Mr. GPL came up to him and infiltrated his business and destroyed his entire business model!

    6. Re:Fight FUD with FUD? by EllisDees · · Score: 4, Insightful

      It isn't FUD whatsoever : To use GPLd code you might apply the GPL license to your own code as well.

      Incorrect. If all you want to do is use the code, you are under no obligation to give anyone the source code. You can even modify the source to fit whatever needs you might need and nobody can force you to release those changes. It's only when you try to distribute your modified version of the program that you are also forced to include the source code.


      Instead it's claiming ownership over derived works as well.


      As our current copyright laws already enforce...


      The real FUD is the perpetual claims of GPLers that somehow they would be deprived of their code is someone else used it in a commercial app.


      You don't get it. What we are being deprived of are the improvements to our code, which is all we are really asking for in return for the use of our code.

      --
      -- Give me ambiguity or give me something else!
    7. Re:Fight FUD with FUD? by ergo98 · · Score: 1

      Wow, we're debating a metaphor. Anyways...

      A virus is defined as a bit of code that autonomously finds a host for itself so that when that host is executed it can come to life and wreak havoc or self-replicate. So, by definition, GPL is not a virus.

      Sounds more like you're describing a trojan. Biologically (since we're discussing the validity of the metaphor) a virus is a non-living thing that `co-opts' its host to replicate it : It cannot replicate itself. If I stick a GPLd gnu.c file in my project then I am co-opted into GPLing all other code in that project. No I don't HAVE to use the GPLd code, nor does a heroine addict have to share a needle, but the end result is the same.

      If you are a programmer and agree with the GPL, you have been granted full permission to leverage any GPL'd code in your application provided you share the source of the result. If you do not agree with the GPL, take a hike -- don't use GPL code in yours.

      And here is where the virus metaphor comes into play : You are bound to not only share the modifications of the source, but also the entire project which it is linked into. Note: I don't, nor have I ever, use GPLd source. I personally have no attachment to or against the GPL, however seeing the same ignorant me-too bandwagon GPL promoting rhetoric just gets tiring.

    8. Re:Fight FUD with FUD? by ergo98 · · Score: 1

      You don't get it. What we are being deprived of are the improvements to our code, which is all we are really asking for in return for the use of our code.

      Apparently you don't get it. Say that there's a great compression utility called gnucompress, so I grab gnucompress.* and add it to my project : Now I find a couple of quirks with gnucompress.* that I fix up, and I contribute them to the community. Now I build my giant, 400,000 line application and put it on the market : Technically this is a gross violation of the GPL, because to use ANY GPLd code, ALL my code (including MY code that is not an addition or improvement to GPLd code) must be GPLd. Again, don't say "don't use it!", because the simple fact is that I don't use GPLd code (I like retaining the right to do what I'd like with my own creations), however there are a lot of people that seem rather misguided about why the GPL is called a virus.

    9. Re:Fight FUD with FUD? by Anonymous Coward · · Score: 0

      Apparently you don't get it. Say that there's a great compression utility called gnucompress, so I grab gnucompress.* and add it to my project : Now I find a couple of quirks with gnucompress.* that I fix up, and I contribute them to the community. Now I build my giant, 400,000 line application and put it on the market : Technically this is a gross violation of the GPL, because to use ANY GPLd code, ALL my code (including MY code that is not an addition or improvement to GPLd code) must be GPLd.

      So could you explain what your problem is? If you WANT to use the gnucompress code in your project then you can do so, the price for which is that your project will have to be released under the GPL. If the price is too high then you are free to try to try to obtain equivalent functionality elsewhere or to write it yourself... what is the virus element? It's a simple bargain you can enter into or not at your discretion. You even say that you choose not to so how can you think it's equivalent to a virus?

    10. Re:Fight FUD with FUD? by Anonymous Coward · · Score: 0


      1) Microsoft extended kerberos in a fully standards compliant way. If you want to complain, go to the standards organization responsible for the specification.

      2) To this day nobody knows if MS used the reference code (they probably did but I have not heard either way). Not that it matters, but if MS rewrote the code from scratch, then what difference is it to you. You are confusing a standards issue (which is not being broken by MS) with a source issue.

    11. Re:Fight FUD with FUD? by rusty+spoon · · Score: 1

      If the GPL people were truly in a 'giving' mood then they'd give and ask for nothing in return. Instead they remove freedom. They themselves are working against productivity by removing a choice that many developers would love to take were it not for having to eat and pay bills.

      The whole point to GPL is to *encourage* source sharing. However, it oversteps the mark by *forcing* sharing. Choice is removed whichever way you look at it.

      I'd like to see an alternative. I'd use GPL code, and might therefore be encouraged to share more, if it wasn't so restrictive.

      I saw one licence (was it mySQL) that grants either a GPL or commercial(pay) licence. I kinda like this but then we are back on the honor system (which we know doesn't work because of the vast army of dishonorable people out there).

      And yes, I do consider GPL to be a disease, a cancer that simply grows, the logical end result being death of the host.

      If you want to give then go ahead (and I do), but please do it on a less restrictive license.

    12. Re:Fight FUD with FUD? by rusty+spoon · · Score: 1

      So much contra-argument!

      You want to give your code out to the world. You also want the world to give back any mods. I think that's great and I'd love that too. I'm a rather slick coder and my design skills are pretty good so we will all do well from the arrangement.

      I *want* to use your code and I *want* to see it improve. If it's well written and well designed then it will have patches applied that reflect that.

      But you want me to give my project to the world if I use your project.

      This is grossly unfair and I choose to not use your code because of it, you have removed a choice and created more work for everyone.

      Releasing my code would give an unfair advantage to my competitors. It would also reduce my income down to nil because charging for my service would be crazy since I designed my product to require very little support - I also have ongoing costs not related to developing software, these are fixed costs not related to user numbers so where would the money for that come from...and without it the software is useless.

      There is no way I can currently release my code as OS.

      So has your code improved? Not from me and not from the army of developers like me. I'm pretty sure that closed source developers outnumber open source developers so why have you alienated them I wonder.

      Believe me when I say that commercial software houses *would* give back mods and anything *not* related to their core business *if* they could use the open source. I've worked on some cool in-house projects that many developers could have had great benefit from, but the licencing and infrastructure isn't there. It's hard to convince a corp to give when they get nothing in return - it's impossible to convince them to go for GPL when their competitors aren't.

      But you won't let them because they don't want to join the GPL club. If not GPL then nothing.

      I think it's a shame, it wastes millions of man-hours of development and reduces software quality overall. Change the licence and everyone benefits.

      GPL is selfish and narrow minded, time for it to move over so the software development community can work together a little more. What would be nice is if Mr Stallman 'invented' the next phase - might make it seem a little less like a religous fruitcake ;-)

    13. Re:Fight FUD with FUD? by crucini · · Score: 2
      Again, don't say "don't use it!", because the simple fact is that I don't use GPLd code (I like retaining the right to do what I'd like with my own creations)

      You like that? So do the authors of gnucompress.
      In your example, let A=gnucompress, B=your additional code, and C=the final product. A + B = C. Given that, which of the following sounds fair?
      1. The authors of A and B are both free to extend and reuse C, providing they don't take that right away from others.
      2. The author of B is free to extend and reuse C, but the author of A is not.
    14. Re:Fight FUD with FUD? by IsaacW · · Score: 1
      The fact that you have source code doesn't mean you own it.
      Isn't this awfully familiar to what the closed-source companies say?

      "The fact that you have the software doesn't mean you own it."

      While I agree that some software works well when it's free as in speech, there is also a need for developers to make money. The GPL is overly restrictive, as it requires any project that contains any GPLd code to release all their code. That is ridiculous. I will give credit where credit is due, but I will never release any of my code under the GPL, because I believe in capitalism.
    15. Re:Fight FUD with FUD? by ahde · · Score: 2

      no, all you have to do is supply the source to your improved gnucompress. Now, technically, if you statically link it all into one binary, you do have to give the whole source. But this is against the spirit of the GPL. The GPL asks you to do a little work (that will usually make your project more robust anyway) and separate the functionality you "borrowed" out. For an extremely small project, or one where a library call is too much overhead, you may be out of luck, but that is a sacrifice the GPL makes for clarity's sake, not out of malevolence.

    16. Re:Fight FUD with FUD? by ergo98 · · Score: 2

      I am entirely likely to be wrong, however the last time that this whole GPL discussion broke out it was resolved that separated functionality, whether as a compile time linked library, a dynamic load library, etc, does not remove the requirement that using code be GPLd. Indeed, as far as I heard there were special exceptions to the Linux libraries to allow commercial software to work on it, however if a module was a library, or a DLL in the Windows world, and it was not a part of the core OS, then it is contravening the GPL for non-GPL code to utilize it in any way.

    17. Re:Fight FUD with FUD? by xonker · · Score: 1

      Instead it's claiming ownership over derived works as well.

      No one is forcing you -- or anyone else -- to make use of GPL'ed code. Why aren't the people who complain about the constraints of the GPL complaining about the constraints of having to license commercial libraries or other code? Lots of companies charge fees for code to be included in commercial apps. You have to pay to use their code. You have a choice whether or not to use the code. It's the same with the GPL, except the people who use the GPL want a different kind of payment. If that payment is unacceptable to you -- fine. Don't use it. There seems to be a large number of people who think that requiring money for code is fine, but requiring code for code is somehow a horrible thing.

      The real FUD is the perpetual claims of GPLers that somehow they would be deprived of their code is someone else used it in a commercial app.

      The fear is that if a company, say Microsoft, "embraces and extends" an application they will make changes that cause the derivative program to be incompatible with the original and then the derivative program becomes the standard and users are forced to go with a proprietary application. Whether this happens in every instance or not is debatable, but that is the reason for concern. I don't believe that it qualifies as FUD -- whether you agree with the conclusion or not. It's a legitimate reason for concern, unlike real FUD.

    18. Re:Fight FUD with FUD? by Znork · · Score: 2

      It's not viral at all. You dont have to apply the GPL to your own code, and you can distribute your own code any way you want, under any license you want. You just cant distribute the GPL licensed code with it, unless it doesnt impose any further restrictions on the bundle. Your own code is not, in any way, affected by the GPL.

      Of course, your own code may be useless if you cant distribute the GPL code, but that isnt the GPLd codes authors problem now, is it. You'd do better to write code that actually works without depending on code you dont have the right to distribute.

      Preventing leeches from distributing my code in proprietary format falls entirely under protecting my original work. Go do it yourself if you cant abide by the terms.

    19. Re:Fight FUD with FUD? by Znork · · Score: 2

      Your code doesnt have to be under the GPL at all. You could release it under the revised BSD license for example (you like the BSD license, right?). Or any other license that imposes no additional restrictions beyond the GPL. You have the right to do whatever you want with your creations, the GPL only affects the GPL code, and it's just the GPL code you cannot distribute together with proprietary code.

      Or, what, you only like BSD licensed code when you can 'embrace and extend' it? Sorry, but in that case you'll find little sympathy from me. People like that are exactly why it's necessary to slap the GPL on code. If the world hadnt been full of them, the GPL wouldnt be necessary.

    20. Re:Fight FUD with FUD? by Znork · · Score: 2

      Yes and no. Code linked against a GPL binary or library, must be released, not necessarily under GPL, but under GPL or freer license (BSD, X11, public domain), or you cannot distribute the GPL code.

      There is an OS exception like you say (for GPL binaries using proprietary OS libraries), altho that does not work the other way around (proprietary apps linking against GPL libraries that are part of the OS). Fortunately most libraries are LGPL, which does allow linking.

    21. Re:Fight FUD with FUD? by TooTallFourThinking · · Score: 1

      The GPL is a software answer to intellictual property. GPL'ed source code can be freely distributed and others can use it, but they are restricted on what they can and cannot do with it. Instead of paying a fee to the intellictual property holder, your fee for using this code is to keep it freely available to all. It's non-profit IP.

      The GPL does what it sets out to do. The same goes for a virus, I suppose. However, a virus does not have a detailed description of what its purpose and intent are. It doesn't ask for permission before infecting you. There is no conscious decision. If the GPL is a virus, it is the nicest fucking virus I have ever meet. It explains what it is about before "infecting" you. When was the last time the flu did that?

      I think some people are just pissed because they cannot use GPL'ed source in their code without the "freedom" to do whatever they want with it. Well, tough shit. That's the GPL.

      The best course of action is to know the differences between the licenses and use the one that more accurately reflects your own personal philosophy and goals. Christ, it's not like there is a shortage of choices out there. There are other licenses to use if GPL is not right for you.

      protecting the original work because there is nothing anybody can do to degrade the original work. Instead it's claiming ownership over derived works as well. The real FUD is the perpetual claims of GPLers that somehow they would be deprived of their code is someone else used it in a commercial app.

      Just to reiterate, yes, this is the point of the GPL. Can you hack Microsoft's code, create your own derived work from it and release it for a fee? No, you can't. It's their property. They did the work, they put in the time, they want to reap the benefits.

      The GPL is just like it in this regard: it says, here is my code which you can look at and read; but if you want to use my code, your code must become freely available as well, with the same restrictions. You can't steal from Mircosoft and you can't steal from the GPL. It's nearly the same fucking reasoning, expect one you are free to look at the source.

    22. Re:Fight FUD with FUD? by EllisDees · · Score: 2

      Again, don't say "don't use it!", because the simple fact is that I don't use GPLd code (I like retaining the right to do what I'd like with my own creations), however there are a lot of people that seem rather misguided about why the GPL is called a virus.

      The GPL is no more a virus than any commercial piece of software. If you went out and bought a commercial product and decided that some .dll included with that product would be super-duper useful in the product you are working on, do you think you would get away with including it in your software? Of course not. The author would either demand that you remove the code or pay him in some way. Is this really that hard to understand?

      --
      -- Give me ambiguity or give me something else!
    23. Re:Fight FUD with FUD? by EllisDees · · Score: 2

      But you want me to give my project to the world if I use your project.

      This is grossly unfair and I choose to not use your code because of it, you have removed a choice and created more work for everyone.


      Your choice is clear cut - either you don't use GPL code or you live with the consequences of it. How much duplication of work do you think happens in the commercial software realm? Tons. I don't hear people bitching about not being able to use that code.

      --
      -- Give me ambiguity or give me something else!
    24. Re:Fight FUD with FUD? by rusty+spoon · · Score: 1

      But that's exactly the problem. GPL is cutting off great swathes of professional developers because they can't (not don't want to) live with the consequences.

      And it's this lack of choice that leads to the 'tons' of duplication. If GPL were really in favour of productivity and sharing then it wouldn't be so unreasonable, instead it would encourage sharing, not attempt to force it. There is a world of difference between the two.

      GPL is selfish, it's a mantra reapeated with no understanding of what it actually means.

      No-one bitches about lack of code from the commercial group because they don't pretend to be generous, they don't say anything is "free" and they don't try to hide behind idealistic goals. They are earning a living and making no apologies for it. Using a commercial library doesn't normally mean you need to give your code to anyone, and your code is normally *why* you are in business.

      I wonder how many of the GPL advocates actually earn their living from *writing code* and how many of them are students, lecturers and, errm, 'consultants'. I bet most are the latter, with more than enough money to pursue their, almost religous, "Star Trek" crusade (yup, it's two sci-fi shows rolled into one).

      If GPL is the right thing then I don't think lecturers and consultants should be paid for what they do either, afterall, passing on their knowledge is the best thing for mankind. Let's talk about farmers next, I mean, they don't actually 'own' the land so how can they 'own' the produce...

      I'll work for free providing my needs, and the needs of my family, are met.

    25. Re:Fight FUD with FUD? by EllisDees · · Score: 2

      But that's exactly the problem. GPL is cutting off great swathes of professional developers because they can't (not don't want to) live with the consequences.

      Huh? Nobody is forcing anyone to use GPL code. If you don't like the conditions, just don't use it. Is that difficult?

      And it's this lack of choice that leads to the 'tons' of duplication.

      What lack of choice? You have exactly two choices - use GPL code and be bound by its terms, or find an alternative. Nobody can make you use GPL code.


      If GPL were really in favour of productivity and sharing then it wouldn't be so unreasonable, instead it would encourage sharing, not attempt to force it. There is a world of difference between the two.


      I don't consider it unreasonable to require the work of others in exchange for the benefits of my own work.

      GPL is selfish, it's a mantra reapeated with no understanding of what it actually means.

      I think most of us have a pretty good grasp of what it means.

      No-one bitches about lack of code from the commercial group because they don't pretend to be generous, they don't say anything is "free" and they don't try to hide behind idealistic goals. They are earning a living and making no apologies for it. Using a commercial library doesn't normally mean you need to give your code to anyone, and your code is normally *why* you are in business.

      It all depends on what kind of payment you are willing to make. With commercial components, you are going to pay cash. With the GPL, you are going to pay with code. Choose whichever you like.

      I wonder how many of the GPL advocates actually earn their living from *writing code*

      I do, but I sure as hell don't sell canned code. The idea that you should be paid for the same piece of work repeatedly is ridiculous. Does a farmer demand that you keep paying for the food you ate last week?

      If GPL is the right thing then I don't think lecturers and consultants should be paid for what they do either, afterall, passing on their knowledge is the best thing for mankind. Let's talk about farmers next, I mean, they don't actually 'own' the land so how can they 'own' the produce...

      If a lecturer or farmer wants to work for free, that is their right. Just as it is my right to put every line of code I write (on my own time) under the GPL.

      --
      -- Give me ambiguity or give me something else!
    26. Re:Fight FUD with FUD? by danakil · · Score: 1

      Isn't this awfully familiar to what the closed-source companies say?

      No, this is just a copyright notice. You have the source, you can use it (no discrimination), modify it, redistribute it, etc. Only the license cannot be modified.

      While I agree that some software works well when it's free as in speech, there is also a need for developers to make money.

      No. If developers want to make money, that's their problem. They can choose proprietary licences. They can do what they want. GPLd software is not for them if they want to take away the users'rights.

      The GPL is overly restrictive, as it requires any project that contains any GPLd code to release all their code. That is ridiculous.

      No. These projects do not just "contain" GPL code. They are derivative work of GPL the code. Obviously you want public domain code.

      I will give credit where credit is due, but I will never release any of my code under the GPL, because I believe in capitalism.

      Free software has not been made for capitalism. On the contrary, it's based on cooperative work. GPLd code cannot be used by capitalist proprietary software companies ? Not a problem, it wasn't made for them.

    27. Re:Fight FUD with FUD? by danakil · · Score: 1

      A single .c file covered by the GPL is a virus if added to a project (...) because it insists that all other files in your project, or that use its features in a binary fashion, ALSO be GPLd

      No that's plain FUD. The rest of the code is not GPLd and will never be GPLd if you don't want to. The result is just illegal. If you want it to be legal, remove this GPLd .c, and rewrite it or use another one.

    28. Re:Fight FUD with FUD? by danakil · · Score: 1

      If the GPL people were truly in a 'giving' mood then they'd give and ask for nothing in return.

      GPL is not about giving. It's about the users having some freedoms, all of which exist in GPL and other free software licenses.

      Instead they remove freedom.

      No they don't : it prevents you from taking away the users'freedom. Freedom doesn't imply freedom to abuse and to remove users'rights. They just fight the reuse of the code in software that should not exist (proprietary software).

      The whole point to GPL is to *encourage* source sharing. However, it oversteps the mark by *forcing* sharing. Choice is removed whichever way you look at it.

      No. The point is not to encourage source sharing, it is to consider non-free software unacceptable, because it remove users'freedom.

      And yes, I do consider GPL to be a disease, a cancer that simply grows, the logical end result being death of the host.

      You can, but I've never seen any valid argument for this comparison. If you prefer other licenses, use them, no problem for that, but the disease comparison is just irrelevant.

  80. GPL can be for sale? WTF? by Anonymous Coward · · Score: 0

    Is it just my misguided perceptions or isn't it true that GPL code is ONLY to be sold for the purpose of -covering- the cost of the delivery method employed?

    IE...no profit involved.

    or is article B somehow nullified in some cases (see article B below)?

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

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

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

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code. (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

    THE whole shebang: http://www.gnu.org/licenses/gpl.txt

    1. Re:GPL can be for sale? WTF? by lpp · · Score: 1
      The last sentence of paragraph 0. of the GPL reads:


      Each licensee is addressed as "you".


      This means that the licensee (i.e. not the original copyright holder) is the one being referenced in the section you quoted. The original copyright holder may sell the software as they please, but if doing so under the GPL, must provide the source code at nominal additional cost (i.e. for only the price of distribution). Of course, as has been mentioned previously, once the cat is out of the bag, there's nothing to prevent a purchaser from subsequently redistributing their product for free.
  81. Why do GPL stuff? by Junta · · Score: 2

    From a business perspective where you are focusing on the product more than the services, GPL is a horrible, horrible idea. His company is intentionally trying to profit off of the work of others, charging for the programs and making it more difficult to get the source.

    At the core, they are selling code written by others without compensation.

    In this circumstance, there are two ways to go. First, find BSD licensed code to steal from. This is still bad behavior, but it is more legitimate bad behavior, the original authors by using BSD license have consented to the bad behavior.

    Also, how much of what they make use of from the GPL community is LGPLed? That is a very good license for libraries that don't mind commercial products based on them, yet want to protect the freedom of the bits they did themselves. This would fit perfectly with the Kompany's goals without bastardizing themselves.

    On a side note, how does QTs licensing play into commercial products like this? I guess they can still claim the work is GPLed and therefore they can ignore the commercial license of qt, but in practice could Trolltech have legal grounding to punish them for being a commercial product without paying commercial fees?

    I think qt's license is a very big reason why a lot of companies push gnome more than KDE. Even though they have to dance around the GPL with Gnome, at least they don't have to worry about Qt's license on top of everything else. The result I see is that very good free software is available for KDE (qt's license is perfectly fine for free software), but some big players mostly ignore KDE if they can..

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Why do GPL stuff? by Warwick+Allison · · Score: 1

      The Qt C++ library is available for X11 under the terms of the GPL. This permits the free development of Free Software. Qt is also available under a commercial license. This additionally permits commercial software to be written.

      The GNOME and GTk C libraries are available under the terms of the LGPL, this permits the development of open and closed software development.

      Both projects are assisted by a community of open source and Free software developers.

      The difference is that GNOME/Gtk requires donations from Sun, etc. to support its development, while Qt is funded by the commercial customers that have supported Trolltech and which Trolltech has supported in return.

      The future will tell which business model works, and which business model commercial software developers are willing to risk their businesses on.

      --
      Warwick

    2. Re:Why do GPL stuff? by *coughs+loudly* · · Score: 0
      From a business perspective where you are focusing on the product more than the services, GPL is a horrible, horrible idea. His company is intentionally trying to profit off of the work of others, charging for the programs and making it more difficult to get the source.

      At the core, they are selling code written by others without compensation.

      Idiot. If you read the article, his company is `intentionally trying to profit off' their own work. The stuff they do to feed their families. They don't have to release their source, and in the future they won't, because of the reactions of people like you.

    3. Re:Why do GPL stuff? by Tomun · · Score: 1

      Yes, this is a good point. But you failed to mention the KDE libraries which are mainly GPLed.

      Doesn't this mean that any application that links with KDE be GPLed too ? Didn't TheKompany by targetting KDE as their platform force the GPL licence upon themselves ?

    4. Re:Why do GPL stuff? by Anonymous Coward · · Score: 0

      Simple fix: use GNOME instead of KDE.

  82. What is the value of free software? by pdoubleya · · Score: 2, Insightful

    what seems absent from this discussion is the notion of free speech, versus free beer.

    my understanding of the Free Software Movement's origins are that RMS and colleagues were frustrated that they had no access to source code--thus they couldn't fix problems with software they used at work or school, even software which had been donated. they couldn't fix, learn from, couldn't write better versions, couldn't help their neighbors etc. anybody who's used commercial software should recognize this limitation. the four freedoms embodied in the FSM are about this--the ability to study other people's code, do something with it, change it, fix it.

    if the kompany doesn't make source code freely available for their products (any of their products) then you, as a person who may be a programmer, are dependent on them to fix bugs, make changes, etc. you also can't learn from what they've done and come up with something better--something which may not even be a competing product. this type of relationship is frustrating to those of us who are forced to use commercial software packages that are buggy or limited in some way.

    i think the question of the value of the software then becomes very difficult to place. software as a commercial product is valued based on its apparent usefulness, dominance in the marketplace, uniqueness, etc. i don't have proof, but i suspect that software is rarely just valued directly in relation to the cost to produce it. companies sell products at a loss to gain market share (thus opening up a wider market for other products), or in other cases, resell products they bought from another company who was already selling it, and where the development cost was either recouped or written off.

    the FSM suggests that the value of a software package is not tied to the cost to produce it. this is implicit because as we all know, if the source code is made freely available (or at low cost) and documents are available, savvy users can roll their own distribution and share it, reducing the income of the original provider to (in principle) zero. so the question i have is then, what is the value of a piece of software, if we believe in the freedoms of the FSM?

    p*ya*ya

    --
    "I honestly would vote libertarian if their candidates weren't usually total cooks."--slashdot poster
  83. Re:He doesnt get it by lpp · · Score: 1

    Um, given that RMS agreed that theKompany complies with the GPL in this case (though expressed dissatisfaction with what they are doing in general), I doubt very much that there is a problem like that which you are describing, which is an explicit (as you pointed out) violation of the GPL.

  84. Gratuitous by Phillip+Birmingham · · Score: 1

    From my point of view, this is just a gratuitous slam at the least mature members of the GPL community. I suspect that the real problem is that the Kivio business model is not working out too well, but a slap at the "nasty GPL people" plays a lot better in the press.

    If Kivio were making a lot of money for The Kompany, I have a hard time believing that *any* amount of bitching from non-paying customers would cause them to change their minds.

    --
    Make me aerodynamic in the evening air
  85. Perspective problem by pyxl · · Score: 1

    I hope this is a privately traded company, as this guy is the President of the company and he's making a business choice based on his personal reaction to lamers and rude people. If this was a publicly traded company, he could run the risk of setting himself up for a shareholder lawsuit.

    If he's saying that this is because people are mean to him, but he really wants to change the licenses his company uses so that they can make more money and restrict competitor access to the source for their products, then he should just say so and be done with it.

    And the best part is, he's blaming RMS's feedback as the last straw and the reason why he's making the change - which is ludicrous. He spoke to the one of the people most famously known for espousing the ideals of stubbornly free software ON THE PLANET and then freaks out when this person misunderstands how his business operates in a way that this person will want to complain about.

    And then he writes an essay telling the whole world about it. Sorry, this whole thing is just silly.

    --


    Given enough hydrogen, just about anything is possible.
  86. Look, we ARE the borg you rebellious fool. by Anonymous Coward · · Score: 0

    Stop referring to the collective as though you're outside of it. The borg is a metaphor of postmodernity. You just don't get it obviously. So, don't even refer to the borg anymore. You're lucky you were even assimilated.

  87. charging for a GPLed SW -- framework by Anonymous Coward · · Score: 0

    ok, so you CAN charge -for- a GPL program IF and only IF you are the original author AND it includes NO portion of any GPL code from ANYONE else

    unless you (the 'original' author of software X) is a collaboration consisting of multiple people

    then the code qualifying as an original copy of a program, and which could thus be charged for, would be limited to the code written by the original group of collaborators alone

    if i understand correctly, then this is a fairly complete picture of what original authors can do in terms of charging for a GPLed software package release right?

  88. Count me also by kastard · · Score: 1

    I couldn't agree more. How on earth is any company suppose to make money from their work. I'm all for them. We just shouldn't be expecting any companies to be creating any software for linux.

  89. OT - But anyway.... by Anonymous Coward · · Score: 1, Interesting

    Why does The Kompany's website look SO bad in Konqueror. The fonts are tiny and HARD to read. Worse yet is that they are fixed and cannot be increased in size by Konqueror's Increase Font Sizes button.

    I expect this kind of thing when I go to Microsoft's site but, The Kompany?? Don't they make KDE and Konqueror? Have they seen their site through Konqueror?

  90. Cake eat it and have it by dup_account · · Score: 1

    Seems like they want to eat their cake and take you money too. The classic company that wants to say they are releasing stuff under GPL, but also wants to make the money selling it as a product. It may even meet the letter of the GPL agreement, but certainly doesn't meet the spirit. I worked for a company that claimed they were open source, but what they really meant was that they wrote their own proprietary programs on top of open source software.

  91. Selling services doesn't work in ed. software. by ahfoo · · Score: 1

    Instructional media is one place where you've got to dumb it down so far it makes people wretch, but there's a reason it has to be that way and it's because students will use any excuse to say they don't understand what they're supposed to do. This means as an educational media deveoper you've got to provide a package that is totally self explanatory from any angle. Who's going to pay for service on something like that?
    A great counter argument to this is that anybody creating software for an educational environment should be doing it out of their love of the subject and not for profit. After all, it's for education, for passing knowledge from generation to generation. What could be more noble? To sell educational media is akin to prostitution.
    The catch here is that in reality education is a lot like a lot like prostitution and always has been --at least since Plato and probably long before that. In fact, both Aristotle and Socrates made reference to this in various writings so it's not quite as blasphemous as it initially sounds to the modern ear.
    So, oddly enough, tax payer funded education is one place where free software simply cannot succeed. Students prefer whorish graphics and in-yer-face flashy multimedia for reasons that seem obvious to one who has some familiarity with the history of education. Getting true slut work is not something you get for free, but something you get from paid whores like myself who do gaudy educational apps that look like wannabee arcade splash screens. The acceptance of this within the educational mainstream is evidenced by the coinage of phrases like edutainment.
    You might think that educational software can create jobs for teachers and thus still fit in the services model, but I wouldn't bet on that. More likely, software in classrooms can make teacher's jobs easier for the time being by eliminating tedious tasks like taking roll and keeping grades. Over time, these changes will be used to justify larger class sizes resulting in less teachers or perhaps the same amount of teachers with more time for the students, but probably not resulting in higher teacher to student ratios.
    I don't think it's all bad as long as it's accompanied by a restructuring of the physical layout of the classroom which computer assisted instruction does push and that's a great thing. But in order for it to happen, there has to be lots of hired whores making tons of media that can hold the interest of jaded kids with vast media libraries sitting at home competing with the school's pathetic efforts at being slutty and almost attractive enough to hold their attention for more than a few minutes at a time.
    This doesn't mean these apps have to run on MS. There's no reason commercial instructional media apps can't be made to run on Linux except of course the companies who make the tools that educational media developers use --like Macromedia for instance-- are scared shitless about having anything to do with rhetorical entities like the GPL.

  92. Interesting Piece... by feloneous+cat · · Score: 1
    As it says more about the authors frame of mind, than the state of GPL. Personally, I think, much like many, he is trying to put the "blame" of his decision to move away from GPL on others.

    This is a pity.

    I would have rather heard about the plight of what is WRONG with GPL than read someone whining (and that is seriously what some of it sounds like) because they feel inconvenienced by it. To that I say "grow up!".

    GPL is a contract. If you don't have the balls to deal with it, then don't! But don't blame others because you have issues.

    Sheesh!

    --
    IANAL, but I've seen actors play them on TV
  93. He Doesn't Understand the Value of Freedom by FreeUser · · Score: 3, Insightful

    He simply doesn't understand the value freedom would give his own software. Indeed, he doesn't appear to understand the free software/open source community at all, which will likely cost him his business in the end.

    Contrary to popular myth many, probably most, free software users will pay for software if they see a clear benefit in it. However, there are certain things free software gives a person that many of us are not willing to sacrifice, whether the product is free-as-in-beer (like Blender was) or not.

    One of these, and perhaps one of the greatest values of free software (although it has many, mind you), is that one will not be left with an orphaned product should a company go under.

    I have hundreds of hours invested in Blender animations that are now essentially worthless (or soon to be, as soon as the binary I have stops working with current libraries and the older libraries become harder to get, and harder to make work). I will never put myself in that position again, which means I will never use any of the Kompany's products, with the possible exception of the one they GPLed. Period.

    This isn't because I have some philisophical ax to grind against proprietary software, it is because I've been burned once and will not be burned again. It is because my data is far more valuable than the software I use and the hardware I use it on, combined. It is because companies do not necessarilly last, particularly in these post-boom times with the Microsoft Monopoly hovering over us all and likely to get away with the corporate equivelent of assault and murder with little more than a slap on the wrist, thanks the Bush Junior's DOJ snatching defeat out of the jaws of victory.

    There are other models for making a profit on software and keeping the code free that he didn't address and likely hasn't explored. One is the service model, which he declines to use because it "doesn't fit" his business model. Fine. There are other approaches.

    One, which fits any software product which improves and adds features over time is to "time shift" the freedom. The author of Ghostscript understood this well, in releasing a free version of his software about a year behind the non-free version. Want the latest drivers and features? Pay up (if you're using it for commercial use). Want the free version? That's okay too, just expect to wait about a year for the same features the paying customers are enjoying today.

    This approach would at least insure their paying customers against the possible orphanage of their product (and is an approach Trolltech has used, with a little twist, quite successfully...indeed it makes their commercial product far more appealing than any of their competitors for that reason alone).

    If blender had done that their animation community wouldn't have died with the company a week ago. If the Kompany were to do that, I would consider using their products.

    But, having learned the lesson RMS, for all his abrasiveness, has been trying to teach us for the last several years the hard way, I will not be using any product that results in my data, my work, loosing its value and usefulness simply because the software seller goes out of business.

    Which means the Kompany will never have me as a customer, and that is a shame, because contrary to popular myth about free software and GNU/Linux users, I do pay for software, as evidenced by a shelf full of commercial Linux apps, from Applixware to Mainactor to various and sundry Linux games.

    He simply doesn't get it, and if he doesn't figure it out it will likely cost him his business as a result. And then his customers will be SOL, something they wouldn't have been had they insisted on some insurance ... the kind only free software can really offer.

    --
    The Future of Human Evolution: Autonomy
    1. Re:He Doesn't Understand the Value of Freedom by Capt.+Beyond · · Score: 1

      Can't eat freedom, buddy...

      Nor does it feed the kids...

      --
      -- "Perceptions create reality. By changing your perceptions you change your reality."
    2. Re:He Doesn't Understand the Value of Freedom by FreeUser · · Score: 2

      OK, I know you're a troll but some uninformed person might actually read the nonsense you just wrote and without thinking actually ascribe it a value greater than it is worth, i.e. greater than zero.

      Did you read my post at all? The Kompany is going to sell less of its products because their customers cannot be assured that it won't go bye-bye tommorow, taking the value of their stored data created with his proprietary, non-GPLed products with it. I touched on two different approaches that have been very successful in allowing companies like TrollTech to make good money while releasing their software under free licensing terms (as recognized by the FSF), and pointed out precisely why non-free, proprietary software that can be orphaned from one day to the next is of significantly lower value and appeal than software that has the kind of guaranteed longevity the GPL gives it. People who make informed decisions and are congnizant of the value of their data will not opt for potentially orphaned products at any price, and as data management and recovery become more commonplace this issue will grow in visibility. The Kompany is shooting themselves in the foot, and will likely lose business they can't afford to lose as a result.

      But you knew and understood that already, didn't you troll?

      --
      The Future of Human Evolution: Autonomy
    3. Re:He Doesn't Understand the Value of Freedom by Anonymous Coward · · Score: 0

      "Contrary to popular myth many, probably most, free software users will pay for software if they see a clear benefit in it. "

      Is that so ?
      Even is it is true, more people are paying for commercial software.
      What's your point ?

      "There are other models for making a profit on software and keeping the code free that he didn't address and likely hasn't explored. One is the service model, which he declines to use because it "doesn't fit" his business model. Fine. There are other approaches."

      What approaches ?
      As far as I know RMS still mostly begs for money.
      Is that the model your propose ?

      "If blender had done that their animation community wouldn't have died with the company a week ago. If the Kompany were to do that, I would consider using their products"

      No, if blender went commercial and managed to deliver better product than its competitors then it would have survived.
      Simple as that and already proven so many times I won't even bother to pursue that any further.

      "has been trying to teach us for the last several years the hard way, I will not be using any product that results in my data, my work, loosing its value and usefulness simply because the software seller goes out of business."

      Yeah, RMS well know businessmen and who is known to run many successful enterprises.
      Please, give me a break.

    4. Re:He Doesn't Understand the Value of Freedom by Anonymous Coward · · Score: 0

      "People who make informed decisions and are congnizant of the value of their data will not opt for potentially orphaned products at any price, and as data management and recovery become more commonplace this issue will grow in visibility. "

      What are your credentials to make such predictions?
      So far , closed source business model is doing very well and ,frankly, RMS and his "revolution" is nothing but a noise compared to the real world.

    5. Re:He Doesn't Understand the Value of Freedom by Anonymous Coward · · Score: 0

      Dude, one look at your page is enough to establish that your out of touch with reality freak.

      Boycott GIF files ? Why ?
      Because somebody wants to charge for their work ?
      Boycott Adobe?
      Why?
      Because they followed the law ?

      But support MEIGS because , of course, Jean needs to have a place to put his fucking plane down.
      Fuck all these people who would love to have this spot available for their enjoyment..
      Support the privileged few who want to fly their asses into downtown.
      Fucking hypocrite.

    6. Re:He Doesn't Understand the Value of Freedom by software_non_olet · · Score: 1

      You can't eat money, captain...

      While the TV set is feeding you children...

      The TV set you bought from the money you got while working in the office where you wouldn't be on your own interest. To where you drove in the car you wouldn't need if you'd stay at home with your children. And so on.

      What value is it to you, to do what you want?

      As a software developer I want to be able to see the source code. That's my fun. Otherwise I'm wrong in the job I'm doing.

      Top down or bottom up? Live life from the roots of joy or the dictatorship of money and so called "facts of life" (which are just "fears of life", fear of following one's own feelings)?

      If we all had more time we would all do GPL software, if at all. But because 'everybody' wants to get paid, we also have to get paid. And then most of your life becomes something which you don't want to do, but do it for the money - as everybody else.

      Is it that, what your kids can learn from you?

    7. Re:He Doesn't Understand the Value of Freedom by software_non_olet · · Score: 1

      Well, FreeUser,

      you try to sell freedom with the concept, that it will bring more money (or more satisfied customers) later.

      So there is the idea in what you say, that money is value and freedom is not (because it needs to be justified). Hence your call for freedom is just that - a call for, but not freedom itself.

    8. Re:He Doesn't Understand the Value of Freedom by TheAwfulTruth · · Score: 2

      First sentece, completely wrong. In fact it's so wrong it points out that you do not at all understand what money is. It's a bit frightening. It must mean that you're oh, 15 yrs or younger? Or retarded? Living off of someone elses money?

      In fact money IS food. Money IS shelter. Money IS entertainment. That is unless you think that eating out of the trash (And I mean that in every metaphoric way possible) is an acceptable way to live your life. Well, have fun! SO tell me how you get YOUR food! I really want to know...

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
    9. Re:He Doesn't Understand the Value of Freedom by software_non_olet · · Score: 1

      Money is an impersonal way to exchange human services. We all get food, support, shelter from each other. It's just a matter of _how_ we manage that.

      Of course in a society of addicted people one need to survive by using the accepted means of social behaviour - impersonal exchange of impersonal drugs.

      But we have let the drug take over our thinking and feeling.

      If there were no people, what would you do with your money? So we buy support from each other, instead of supporting each other out of friendship, love and joy.

  94. GPL is least of Kompany's problems. by noumena9 · · Score: 1

    Terrible user support is. I bought the blackadder beta and this is what happened:

    * it wouldn't work as I didn't have a proprietary library that was not distributed. I wrote an email and was assured that they would fix it. They never did.

    * I wrote more email, and Shawn replied to every one with the same message: This will be fixed.

    * After months of repeating this I gave up.

    If you treat your customers this way you will not sell software and you will go out of business. Personally I wish some evil on the Kompnay -- about $80 worth, to be exact... I paid for my software and thay never delivered.

  95. Sophistry by FallLine · · Score: 2
    Well, its freedom because I can't do what I want to do with my computer without giving up my freedom.
    This a completely nonsense statement. Just because you have the option of giving up your freedom for something you desire does not mean that the software producer is somehow impinging on your freedoms, yet this is precisely what you are implying. You do not have the right to the product of my mind. You are not entitled to my work: past, present, or future. It is mine, not yours. If I am allowed to not create (and I am), then it's only reasonable to allow me to choose the how, when, who, and under what conditions if I choose to do so [especially when such conditions are essential to its creation in the first place]. So to each person that wants my work must agree to pay a fixed amount for it and agree not to share it with others. If my conditions are not acceptible to them, well then they're no poorer then if I am had not created it.

    This is like saying, you are allowed freedom of speech, except that, you will not be allowed to work if you exercise your freedom. That's not freedom... That a parody of Freedom!
    No, this is not nearly the same. In neither case is using my hardwork a RIGHT for you. It's neither equivalent to freedom of speech (a so-called natural right) nor is it like the "right to work" that some courts have found to be valid and can be said to be necessary for survival. You are perfectly capable of doing without my software and the conditions for its use are quite reasonable and germane to my software. You are simply being asked to make a choice, a choice that is not so different then choosing to pay for a carpenter's handiwork or not get it at all.

    In any event, if you wish to claim that you are somehow entitled to do whatever you want with your computer, then with your same reasoning the GPL is absurd on its face as it demands that you share your modifications. Even if the intellectual property framework were torn down, this simply does NOT come along with the package and is quite contrary to even that notion of freedom. Nor does a world free of copy prevention techniques, and so on...
  96. No, not every software company by Anonymous Coward · · Score: 0

    There are different kinds of software businesses. Slashdot once posted this interview with Sleepycat Software. They seem to do just fine with a dual copyleft/proprietary license. Note that they do not produce end-user software however.

  97. he's totally wrong-headed by alan_d_post · · Score: 1

    IP is a totally broken concept. Do you really want to live in a world where "Remembering is copying, and copying is theft?"

    Please, go read some stuff by Eben Moglen. With zero copying costs for software, free riders aren't a problem. The only trouble at the moment is that anyone without a job has no health care, and can't pay rent. I really think that if we had another 100-200 good programmers set loose from the capitalist system, most of the software "industry" would disappear pretty quickly.

    1. Re:he's totally wrong-headed by mark_lybarger · · Score: 2

      why do you say it's a broken concept?

      i agree that there's _lower_ copying costs for software than traditional ip mediums (paper), but that doesn't consider the fact of the time to create the item. even a book/magazine takes time and arguablly skill to write (certainly some spell checking skills :) ). this cost is factored into the cost of the item, along with printing costs, administrative costs, etc.

      please correct me if i'm wrong, but the software model is really no different that i can tell. we figure we've spent 2.5mill$ over all to create our software package, and we'll be able to sell .5mill copies at 14$ each. this covers the cost of support along with recouping the cost of our investment. that's right, we just spent 2.5mill$ on creating this damn thing, i sure as hell as an investor will want some ROI. i could have put my money in stocks otherplaces, but i invested in the flimsy software company because they said they could build something that people will want to buy. so, unless all those builders (developers, testers, doc writers, etc) are working for FREE, and i can get free bandwidth or "printing", i'll need to charge money for the product to be successfull.

      even universities, which revolve around IP, aren't really giving it away. they have the same business model, to attract more customers, which in this case is students of education.

  98. If you can charge for access to GPL source code... by shatfield · · Score: 1

    ... wouldn't an evil company just put a very very high price tag on the source code, to prohibitively keep people from having it?

    Think about it -- Microsoft takes Linux, makes dozens of changes to it that we would love to have (this is a theoretical question.. stick with me here...) and then proceeds to charge 5 Billion dollars for access to the source code that they did. Noone can afford it, so it effectively remains closed.. right?

    Houston, we have a problem.

    --
    "To make a mistake is only human; to persist in a mistake is idiotic." Cicero
  99. Re:He doesnt get it by shatfield · · Score: 1

    Well, its freedom because I can't do what I want to do with my computer without giving up my freedom.

    No, you can't do what you want with your computer without giving up MONEY, not FREEDOM. You want the source code? Pay for it.

    --
    "To make a mistake is only human; to persist in a mistake is idiotic." Cicero
  100. A new generation of OSS by electroniceric · · Score: 2
    Well, first of all, taking RMS with a grain of salt is a pretty good idea. RMS is an academic. Which means that he's very good at following an idea where it leads, but not very good at understanding when the time comes to compromise on the philosophical to achieve the practical. He's also clearly unwilling to admit to the world (and probably to himself) that he really wants to be the Most Important and In-Charge Comrade Among Equals of the Soldiers of Free Software. You could actually make a pretty good case that this has caused people (in the US at least) to ignore some of the very good ideas at the root of socialism - they have been articulated too ideologically by college professors, without the fleshing out of practical life.

    The GPL was good for giving momentum to the idea of Open Source Software by throwing the doors open to hobbyists and smart, curious people, capitalizing on tremendous interest and enthusiasm by people who didn't already know they liked this field to build intellectual excitement to a movement. For evidence of its power, just compare Linux culture to *BSD culture.

    But at this stage the GPL is starting feel restrictive. Yes, it protects your intellectual freedom in the absolute (RMS' failure to include this adjective, which is totally obvious to him because his life is lived intellectually, is the source of many flame wars), but it restricts your practical options very severely. It's a bind, because the GPL builds intellectual excitement into Open Source, and giving it the boot could cut the movement off from its fueling enthusiasm. But clinging tightly to the GPL is a pretty sure way of making sure OSS stays inside the academy and a few l33t h4x0r circles. To see what OSS can be, you gotta give people who don't live by ideas a crack at seeing what they can do, in the way that they do it.

    So good for you, Shawn Gordon, you are reaching the inevitable phase where the student supersedes the teachings of the instructors. So far you've kept the Open Source spirit of contribution to a community pretty well intact. Perhaps you can take Open Source where many of use would like to see it go.

    1. Re:A new generation of OSS by software_non_olet · · Score: 1

      I agree, that ideas have their time and have to make the practical life easier. And I also agree, that the GPL is somewhat - say - stubborn. But the latter comes from the fact, that the idea of the GPL has to fight it's way through many layers of money-oriented behaviour.

      What I miss from your standpoint is the educational value of Open Source. We never had so many and so well trained and enthusiastic computer programmers before the times of OSS. That's it's real value: education, training how to write good software. A multidimensional training course for hack3rz as well as sysadmins.

  101. Not a very insightful essay by horse · · Score: 1

    What I read was
    1) People hassle you when you use GPL but don't provide source for free,
    2) Closed source allows distribution to store shelves, which gets the software "in front of" people,
    3) Whining that not everyone likes commercial Linux companies.

    The only remotely insightful point was (2), and it was pretty feeble. (How many Linux users look for software in stores? That sure isn't where I'd go first for Linux...)

    As for GPL zelots hassling him or saying unpleasant things, yeah, so? Not everyone out there is going to appreciate you, and the Linux community is less commercially oriented than most. I'm not defending the zelots (who are often a**holes), but this isn't exactly a great revelation.

  102. name of a successful company please? by nodrip · · Score: 1
    OpenOffice, GAIM, and other projects.

    I'd like the name of one company, which relies on a GPL based product, that is profitable.

    --


    -- "The best way to predict the future is to invent it."
  103. Reference to selling free software from the FSF. by jbn-o · · Score: 1
    As for selling GPL source, this is permitted, though I thought that there was some cap on price, based on reasonable distribution expenses (media, shipping, overhead, etc.)

    Your point has been debunked already but I thought you'd want an authoritative essay on selling free software and a brief GPL FAQ reference to payment.

  104. double standards? by h4x0r-3l337 · · Score: 1
    they should only really need support if our software is hard to use or poorly designed

    I've been saying this for years. Why is it that when I say it it gets marked as "troll", but when Shawn Gordon says it, everyone agrees?

  105. Of course it has! by Arandir · · Score: 2

    Hemos: Of course, it's [GPL] been used for end user - OpenOffice, GAIM, and other projects.

    Well duh! But that's really not germaine to the discussion now is it? You can count the number of people who have purchased OpenOffice on one hand. It's a free download damnit!

    Shawn is trying to sell a product. He's trying to be a team player in the community. But he has suddenly realized that he can't do both.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  106. Hmmm... GPL... by evilviper · · Score: 2
    This reminds us that GPL has so far been useful just for infrastructure-level hacker stuff like operating systems, databases etc.

    You know, you could have fooled me. It looks to me like the GPL is second to the BSD License. Operating systems, databases, webservers, scripting languages... It seems that the best stuff is under the BSD (or VERY similar) license.

    So if we follow this logic the way you have, changing the license of the Linux kernel to the BSD license will instantly improve it by leaps and bounds. It will be as secure & fast as OpenBSD, as portable as NetBSD, and as popular as Apache.

    That solves EVERYTHING. The LICENSE. It's just so simple. The LICENSE has been the problem!
    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  107. The BSD license gives you just that by Anonymous Coward · · Score: 0

    Yes no one will read because I'm so late....

    but the BSD license gives you just that... as long as you keep track of whats open and whats closed. Simple and plain.

    No isues with deriving something from your own bsd licensed stuff and commercializing the result...

    That way you can care and give as well as make a living. Only catch is: one given away, always given away which is quite logical.

    The GPL tries to protect egos and their wallets. That doesn't work in the long run. Giving away is giving away.....

  108. Sorry but that's the wrong answer by hayden · · Score: 1

    Yuo can only charge reasonable distribution costs (possibly only to a person who has bought yuor software, gray area here). $10 for a cd or download would be about the most yuo could reasonably charge.

    It appears as though GPL zealots aren't the only ones who misunderstand/haven't read the licence.

    --
    Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
  109. Nitpicking aside by HiThere · · Score: 2

    Ignoring numerous details:
    This is the way that software licenses were generally licensed prior to about 1980 (perhaps 1975). Then there started to appear large software houses that created progressively more restrictive licenses. When most of the customers were large businesses, and the software houses were relatively small, they didn't try to beat up their customers. If they did, the customers would go somewhere else. Generally access to the source code was guaranteed, and the larger companies often arranged provisions that in case of contractual problems, they could have someone else fix any problems.

    Predictably, as the vendors became more powerful than the customers, this declined. The GPL is about creating a new base level playing field where the customers are more important than the vendors, starting from the original assumption that every programmer is a software customer.
    .

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  110. Re:Reference to selling free software from the FSF by Tomun · · Score: 1

    Not entirely..

    Here is the faq entry worth reading.

    It basically says that you can charge one price for the binary and up to the same price again for the source.
    This is not ideal, nor what I would expect, but its there in the FSF's own faq.

    I hope V3 addresses this.

  111. We need a version EULA's for proprietary software by Ilan+Volow · · Score: 1

    One way to improve the world of proprietary software would be for customers that buy proprietary software to require some form of End User License Agreements for big software companies (maybe it could be called "End User Purchase Agreement (EUPA))The EUPA would state that upon the end user opening the box of software, they is entitled to the source code for the software if the vendor ever goes bankrupt or completely discontinues the piece of software. If IT departments (and maybe governmental organizations too) would require software with EUPA's for purchases, I think there would be enough pressure and momentum for this scheme to work. I know this scheme is not as good or open as Free Software, but that's still no reason not to try to make the world of proprietary software better and make sure that far less people are screwed over.

    --
    Ergonomica Auctorita Illico!
  112. Re:He doesnt get it by Graymalkin · · Score: 2

    Oh please, the GPL states you can charge a reasonable fee for source based on the price of the binary. If you sell the binary for 20$ you can't charge 3000$ for the source code. What the original poster was bitching about was the act of charging for the source code. It isn't some given right that source code ought to have zero cost like I fucking said. How the fuck did this get modded up to 4?

    --
    I'm a loner Dottie, a Rebel.
  113. The argument for support-based revenues by Spinality · · Score: 2

    Many of the comments here essentially say "software companies should base their revenue model on support and services." Setting aside all the questions about the obligations and advantages of GPL and LGPL and other licenses, let's just look at the "software companies ought to be support businesses" argument.

    There are some business plans that work very well with a services model, and can leverage the strengths of an open source infrastructure to provide good value for customers. But there are other businesses where this just won't work. A relatively small, specialized market niche requiring sophisticated software is often unable to sustain an open-source community robust enough to address its technical problems adequately. Instead, some bunch of high-powered wireheads needs to work full-time on those problems, and somebody has to pay their salaries. Support/services revenues are often simply not an adequate way to recover the R&D costs of running a team like that. If you sink a few million on a project, how can you recover your costs through distribution charges and manuals? Never!

    For such problem spaces, proprietary licensing schemes prove more practical -- licenses are an easier and better-understood way to get a group of user organizations to chip in the $50-200K a year or more, each, needed to run the development group. Companies are familiar with the idea of buying a license from a software vendor, and expect a bunch of contractual benefits as a result that they couldn't get through open source strategies. It would be riskier (and more politically dangerous) to pay comparable fees to a support organization that isn't contractually obligated to develop and maintain its own product, but instead is promising to work earnestly with a bunch of public-spirited open source volunteers to get the code written.

    A strong engineering group is simply easier to build and run when one company controls the checkbook. With a big, diffuse problem space, like an OS or a DBMS, this isn't so important, and the open source advantages are more pronounced; but with a specialized need, the open source route can be more problematic.

    The bottom line is that it's fine to say "you shouldn't be a software vendor, you should be a service vendor" but some companies really ARE and SHOULD BE software vendors -- they do a good job at it, they keep their customers happy, the business model pays for the R&D work, and at the end of the day the guys who founded the company WANTED a software company, not a services company. If you've worked in both environments, you know how different they can be.

    Some of these closed-source companies are in fact Good Guys, and the open source world should try to find ways to let them into the tent. Locking them out, and just saying "proprietary is evil," limits open source to those problems that lend themselves to group solutions. Not all do, IMO.

    --
    -- We all have enough strength to endure the misfortunes of other people. La Rochefoucauld
    1. Re:The argument for support-based revenues by Chris+Johnson · · Score: 2
      Why, exactly, should the 'open source world' try to find ways to let the 'closed source companies' into the tent?

      If 'the tent' is marked 'open source' and defined on economic and productivity grounds, surely the closed source companies can and should fend for themselves without help? Are you trying to give 'em open source welfare or something?

      If 'the tent' is marked 'free software', doesn't the whole concept suggest that proprietary guys are by definition outside it? And again, isn't it best to let them fend for themselves?

      I'm not aware of any serious intent to KILL off proprietary software by either open source or Free software advocates. If some or a lot of us wish it would DIE off, well, I'm sure they wish that of us too, welcome to the world. What possible reason could there be for TRYING to help proprietary software? Can't it help itself? Doesn't it have its own 'tent'?

  114. Re:Klerck on page widening by Anonymous Coward · · Score: 0

    no shit.. too bad nearlyu 70-90% of shushdot users are using IE.

  115. Re:Reference to selling free software from the FSF by jbn-o · · Score: 1
    This is not ideal, nor what I would expect...

    What did you expect? What is ideal to you?

  116. Namecalling is a clue of irrationality. by jbn-o · · Score: 1
    There's a good criticism of it here...

    That's a very clueless essay, actually. The silly question the essayist poses doesn't address the copyleft issue at all. It doesn't even give the reader the impression the author is aware of software freedoms. Instead it looks like just another RMS-bashing screed (complete with tired namecalling). Fair use, picking another program to base one's changes on, the problem of conflating physical and conceptual works (resulting in thinking of copyrights and patents as "property"), and writing one's program from scratch are some of the overlooked issues in "Nick"'s tirade. You'd do well to avoid this reference.

  117. Chain Letters and GPL by yintercept · · Score: 2

    I agree, stuffing the viral marketing concept into software was a horrid mistake, and is a major reason why I avoid the GPL issue. Look at all the white noise created by the people trying to force this thing down everyone's gullet. One of the main complaints of theKompany was the incessant humming caused by GPL rants, source code requests, etc.. I understand the desire to be able to focus on ideas and work, and not this type of stuff.

    Quote from the article:

    I think far too many people spend far too much time and mental energy tied up in license discussions when their creativity and focus could be spent building something fantastic for themselves or maybe the community.

    If I wanted to waste my life yammering about legalese, I would have gone to law school and make more money. Have you notice how lawyers tend to strut about blabbering about their great altruism, and some seem to sneak out the back door with all the cash. GPL is just another case showing that people feigning altruism generally have a deeper greed than the people they denounce.

    I've given out a great deal of code. Released stuff into the public domain, etc.. But I would never touch the GPL just as I try to avoid forwarding email with virii. If I give something away, I do so because I want to help increase the knowledgebase (some times just cause I am an egotistical snob) but never because I want to spawn a revolution.

    BTW, I dislike the viral nature of other licenses as well. A lot of contracts have this nasty effect. Having a non-disclosure agreement in one contract will force its way through other contracts. If your code encapsulates someone elses code, then your license has to encapsulates the other license. In just about all cases, however, the legalese ends up diverting attention from the problems to be solved to pure power mongering. TheKompany has x amount of altruism. They want to spend that on the community. The people people pounding at the door demanding the souce code were simply playing power mongering games.

    I have to agree with Shawn Gordon. Life is too short to waste it on chain letters and GPL.

    kd

  118. Counterexample: Cygnus by Per+Abrahamsen · · Score: 2

    The people who worked at Cygnus claims it has been profitable in all the many years (since 80'-something) it existed as a seperate firm. Cygnus was for many year the main contributors (and often official maintainers) of the GNU development tools.

    That is a lot longer than most other commercial software companies.

  119. Moron. by Anonymous Coward · · Score: 0

    RMS points out KDEs lack of commitment to freedom. This guy pisses his pants. Then he points out that he himself, a core KDE developer is switching to a proprietary license. At the same time, before Qt went GPL, the KDE developers didn't care. They just want to make a product, regardless of freedom and licensing issues. That's what RMS was pointing out, and RMS was right. The next critisism was that he didn't like the GPL because there were stupid people out there who misunderstood the GPL. There's absolutely no logic there. Correct me if I'm wrong, but there wasn't a single solid argument in that essay. (I say this not as flamebait; someone please do correct me if you see a good argument nested somewhere in there).

    As far as I can tell, this loser wants to rationalize switching to proprietary, and so wrote this essay.

  120. Because you can never have too many good engineers by Spinality · · Score: 1

    Why, exactly, should the 'open source world' try to find ways to let the 'closed source companies' into the tent?...Are you trying to give 'em open source welfare or something? -- Chris Johnson

    Put that way, I admit it sounds silly. But look at it this way. Consider two classes of organizations: those that develop software as part of their core business, versus those that develop and use software in support of their (non-software) core business: manufacturing, services, distribution, whatever. Although it's axiomatic that some of the strongest development teams and best engineers work for software-driven businesses, it's ironic that we make it much more difficult for such businesses to participate in the open source community. Few people would seriously say "They should get out of the software business so that they can benefit from open source" -- that's what they are and what they do. But shutting down the business seems to be the price of open source admission.

    Should such organizations fundamentally be isolated from open source? Perhaps, since there would always be some conflict between their core business and the open source concept. But what a waste! Often, these are our best bastions of good engineering.

    Imagine a small, high-quality development team, working in a traditional-model software business on an interesting problem -- financial analysis, restaurant POS systems, automated mapping, database design, whatever. The company and the team are funded by license revenues. But they're good guys. They use and support open source development tools, and they choose open source components for internal use. Their accountants have Linux desktops. Their web server is Apache. They don't use commercial products if good open-source alternatives exist. And they *don't* try to steal open source components from others to distribute as their own products. They have good engineering practices. They never comingle their product with open source components, in the same way they would never steal software from a customer. Employee morale is high.

    In the course of building their products, they make rational decisions about whether a particular component should be built within their proprietary framework, or released as open source. On a case-by-case basis, they decide whether that component is more appropriate to be community-maintained or privately-maintained. The stuff that represents their core business, they keep secret and sell to their customers; the stuff that is more generally applicable, they share, getting the benefit of a wider support community and the other open source advantages.

    Such companies do exist, and they provide a great work environment. I believe that this is the *right* model for a software company. But at the moment, it is relatively hard for such a business to integrate open source into its operations. It's relatively easy for a non-software company to use open source: just share everything. But it's hard to use open source selectively within a software company. We give some of the best teams of developers insurmountable legal and political barriers to open source.

    I think it would be to everybody's advantage if right-minded software vendors could participate in open source. They have some of the strongest resources and are in a better position to help than many others. I don't know *how* to make this happen, but I believe it's better for all than dismissing this large class of professional developers.

    --
    -- We all have enough strength to endure the misfortunes of other people. La Rochefoucauld
  121. Re:Because you can never have too many good engine by Chris+Johnson · · Score: 2
    "Although it's axiomatic that some of the strongest development teams and best engineers work for software-driven businesses..."

    Is it?

    Prove it.

  122. Not correct by hey! · · Score: 2

    You wrote:
    You are encouraged to charge as much money as you can get for distributing free software [gnu.org].

    This is not entirely correct. You can charge as much as you want to distribute free software with source code. However you cannot (or at least ought not) distribute free software binaries and then charge restrictive fees for the source code afterwards. From the FSF site:

    The one exception is in the case where binaries are distributed without the corresponding complete source code. Those who do this are required by the GNU GPL to provide source code on subsequent request. Without a limit on the fee for the source code, they would be able set a fee too large for anyone to pay--such as, a billion dollars--and thus pretend to release source code while in truth concealing it. So in this case we have to limit the fee for source, to ensure the user's freedom. In ordinary situations, however, there is no such justification for limiting distribution fees, so we do not limit them.

    There you go. In a nutshell: You can charge as much as you want to distribute the software, but you can't use distribution fees to separate source code from binaries.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  123. Didn't think this would be disputed by Spinality · · Score: 1

    This has been my experience from 25 years in the software biz. Are you saying you don't think there's good engineering being done by any software vendors?? I'm certainly *not* saying that there aren't great developers in end-user organizations, in research labs, and in the academic world -- of course there are. But there are lots of strong developers working for software companies. Remember that many vendors offer great salaries and working conditions, and therefore have attracted impressive talent. Good engineering is what good engineers do, in the same way that science is what scientists do. Therefore if you have a lot of good developers working for software vendors, there should be a lot of good engineering being done.

    I dunno, perhaps this is a troll, it never occurred to me that folks who develop software products for a living might be suspected as a class of being inferior engineers or as belonging to inferior teams. My observations have been the reverse. If I poked into twenty development organizations, ten end-user and ten software vendors, and ranked their general competence and experience levels, I'd expect to find more of the software vendors in the top ten, because Darwinian selection destroys bad software vendors more quickly and completely than it destroys bad in-house development teams.

    In fact, through the years I've had several consulting assignments that consisted of helping an end-user organization run its development groups more like software vendors. A structured release process, rigorous version control and distribution management, bug tracking, support protocols, beta testing, regression testing, investment in development tools -- these have all historically received more serious attention by software vendors. Again, many non-vendors have good practices as well, but I've always found that the specialists have taken the lead.

    Well, I doubt there's much more to be said in this thread, this seems to be sliding into ontology. At the end of the day, all I was really trying to say was: there are good developers working for good software vendors, and I believe they would contribute more to open source projects if we didn't put unnecessary barriers in their way. Leave the necessary barriers, but remove the religious ones.

    --
    -- We all have enough strength to endure the misfortunes of other people. La Rochefoucauld
    1. Re:Didn't think this would be disputed by Anonymous Coward · · Score: 0

      Hard to say, we can't see their code. We can, however, see them trying to weasel out of an astonishing, infamous litany of defects in stability and security. Not to mention that the most successful vendors prosper through an unacceptable degree of control over their customers' use of their own property, leaving little reason to expect a vendor that wastes money on making good software to survive in this environment.

      "Contributions must be open source" is a barrier that prevents developers from contributing to open source projects? If we remove that barrier, all we accomplish is to subsidize our rivals (who already have the huge advantage of monopoly rents to commission development that we don't benefit from) and perpetuate the unethical business model that has crippled the profession.

    2. Re:Didn't think this would be disputed by Anonymous Coward · · Score: 0

      > Hard to say, we can't see their code.

      C'mon, there's plenty of good code from software vendors that is available and visible. They're not all morons hiding behind licenses. (Some are, of course. But please note that M$ may be the biggest vendor but it is also the least typical.)

      > We can, however, see them trying to weasel out of...defects in stability and security.

      Some of them, certainly, but others seem to deliver good support and have loyal customers.

      >"Contributions must be open source" is a barrier...?

      No, that's certainly a cornerstone of open source, and is not the problem I think is being discussed here. Open source projects should indeed be open source -- duh. But what we've done is create the equivalent of a 'software vendor tariff' -- we discourage software vendors from participating in open source efforts, even when they're trying to play by the rules. If they choose to keep certain parts of their work proprietary, that doesn't mean they can't be good open source citizens in other areas. Couldn't a database vendor support and maintain an open-source compiler without a conflict of interest?

      > perpetuate the unethical business model that has crippled the profession.

      Well, here we are at the nub of the matter. Nobody has yet convinced me that there's anything unethical about writing and selling software products. By extension, all authors, poets, composers, and artists are unethical the moment they try to sell their work. This seems essentially to be saying that all creative activity should be viewed as "work made for hire" owned by the public domain, and that the creator doesn't deserve more than an hourly stipend for the time spent creating that work. Personally, I'd rather dig ditches.

  124. Better answer for *both* sides by Ogerman · · Score: 2

    I've heard the arguments about selling services, but for what we are doing it just really doesn't work.

    Software that everyone needs should be developed by everybody--sorta like the idea behind Apache. Everyone chips in a little and everyone gets back a great piece of software. GPL works beautifully here. The same can apply for all of the "general, end-user" software that Kompany produces because none of it is all that specialized. Perhaps the question becomes: Why is the Kompany trying to make money on general purpose software like development environments or messaging/organizer clients or whatever that literally hundreds of thousands of people need? That is software better written as a community. The place to make money in Open Source software is consulting--providing solutions, not services. He's right: selling services as an after-market.. err. after-download.. addition to free software doesn't work very well. But there is money in customizing or extending existing free software to clients likings, assuming that cost is less than they would have to spend on proprietary solutions. There may never be a place for corporations of any size in free Open Source software. But there will always be a market for the individual or the small consulting firm.

  125. You don't own my thoughts by alan_d_post · · Score: 1

    I take it you didn't read the moglen link. Private property is usually justified by pointing out the damage to its owner were it to be taken away. Knowledge does not have this problem -- if you share your knowledge, you are no worse off, and may in fact benefit in non-monetary ways (they do exist!).

    That is what I meant by IP being a broken concept. How can you really think that someone owns a thought? Do I own "blue"? Or "crunchiness"?

    You bring up a separate issue, that of temporary monopolies to promote creative endeavors (aka copyright). Note the very substantial differences between copyright and standard property concepts.

    Even copyrights are a workaround, rather than a real solution, to the need to for creative work. If we weren't all trapped in jobs, making money for the owners of the corporation, and consuming ourselves to death, we might have time to do creative work without having a business model. In fact, such a world would not involve the horrendous overhead (sales, marketing, finance, investors, investor magazines, etc.) that your "software model" involves. All those salespeople could be doing something else with their time -- raising their children, for example, or dancing, or reading, or walking around in the out-of-doors.