Slashdot Mirror


RMS Weighs In On BitKeeper

An anonymous reader writes ". . . and boy, is he pissed! The BitKeeper license, he told the Linux kernel mailing list, is 'the whip hand' of proprietary software. His brief but pungent comment is carried by Linux and Main."

128 of 800 comments (clear)

  1. But I'm sure that... by kirkb · · Score: 5, Funny

    if they agree to rename it to GNU/Bitkeeper, everything will be allright. :)

    --
    Slashdot: come for the pedantry, stay for the condescension.
    1. Re:But I'm sure that... by mAIsE · · Score: 5, Interesting

      If you read the entire story, not just the slashdot post. It looks like Bitkeeper is getting a little microsoftian about what type of project they 'allow' you to use with their product.

      I am not a huge RMS fan, especially with all of his "it is a GNU/World!!" assertions, but i think he has a good point this time.

      Maybe RMS should not cry wolf so often; so we might learn to listen.....

      Ghandi had a great point

      First they ignore you...
      Second they laugh at you...
      Then they fight you...
      And then you win!

  2. Philosophical Question by 0101000001001010 · · Score: 4, Funny

    If RMS speaks, but nobody listens, does he make a sound?

    1. Re:Philosophical Question by ender81b · · Score: 5, Funny

      Shamelessly stolen from the BOFH.

      2. You're locked in a room with Richard Stallman and Bill Gates and have only a gun with two bullets in it (which you normally secrete on your person in case you ever get locked in a room with Richard Stallman, Bill Gates, etc). They both clear their throats to speak. What do you do?

      A. Shoot Bill, hoping he hasn't got a tablet device (or the XP Security Vulnerability notes) crammed up his blazer
      B. Shoot Richard, hoping he hasn't got the notes for his speech in front of his heart
      C. Shoot Richard AND Bill and take your chances
      D. Shoot yourself, twice, for getting into such a contrived situation

  3. point by Karma+Sucks · · Score: 4, Interesting

    What RMS is doing his best to ignore is that these restrictions are lifted if you (gasp!) buy a commercial license.

    I realise what point he is trying to make, but I think it is unfair of him to cloud the issue like that.

    --
    (Please browse at -1 to read this comment.)
    1. Re:point by xean · · Score: 5, Insightful

      But what it comes down to really is why are they using a commercial product at all to develop one of the most sophisticated open source products.

      While (most|some) of us dont always agree with what RMS says - he almost always does have very valid points - and this is something that I personally agree with him on.

      Maybe its time for someone to start developing a OSS competitor to BitKeeper (without using BitKeeper of course!)

    2. Re:point by eyez · · Score: 5, Interesting

      Maybe its time for someone to start developing a OSS competitor to BitKeeper (without using BitKeeper of course!)

      Nobody will; Why? Nobody has really tried so far- even RMS is too stubborn to ask "Well, what is it that bitkeeper does that (cvs|subversion|arch|pcrs) doesn't do?", and then gone off and tried to implement it- in fact, this is what all of bitkeeper's advocates, including it's creator, Larry McVoy, and Linus Torvalds have been saying all this time. "Make me something better, and we'll use it.". Yet, everyone is very willing to complain, and just ignore when $KERNEL_DEVELOPER_USING_BK says "$FEATURE is something i use every day with BK, and isn't in any of the OSS source management tools."

      It's funny how much people will bitch when they're not the ones that have to deal with the inadequacies of $OSS_SM_TOOL when it comes to kernel development.

      (Actually, i believe that the subversion author (although i may be wrong about which project) has asked, but they're still a ways off in everyone else's eyes- Hell, even bitkeeper isn't there yet. Larry takes plenty of input and actually implements the missing features that Linus and company ask for, though, which is much better than any oss project.)

      I'm fairly dissappointed in RMS in this- You'd think if anyone was going to make a GNUkeeper, it'd be him.

      --
      get 0wned. irc.w30wnzj00.com
    3. Re:point by starling · · Score: 4, Insightful

      You answered your own question. The kernel developers decided that BitKeeper was the best tool for the job so they used it, and if the FSF comes up with something better then I bet they'll switch to that in an instant.

      That's one of the real strengths of Linux - ideology takes a back seat to getting the job done, and IMO it explains why Linux has been one of the most successful Unix variants.

    4. Re:point by eyez · · Score: 4, Insightful

      Well, CVS is fine for small projects. Linux is anything BUT a small project; there's a lot of things that cvs either doesn't support, or supports poorly. Binary files and renaming files, for example. There's a handful of other things, but the bottom line is, the linux developers who are using BK would laugh in your face if you told them CVS was a viable replacement.

      --
      get 0wned. irc.w30wnzj00.com
    5. Re:point by FooBarWidget · · Score: 5, Interesting

      "You answered your own question. The kernel developers decided that BitKeeper was the best tool for the job so they used it"

      The kernel developers didn't decide, Linus decided to use BitKeeper!

      "That's one of the real strengths of Linux - ideology takes a back seat to getting the job done, and IMO it explains why Linux has been one of the most successful Unix variants."

      Untrue. Why do you think they break "kernel module source compatibility" with every patchlevel release? Obviously this has something to do with ideology, because not having to recompile kernel modules is a lot easier to the end user.

    6. Re:point by fault0 · · Score: 3, Informative

      > I said Apple uses cvs and they use it for a large project Mac OS X.

      Putting source available on CVS is much, much, different from actually using it for source control. Apple likely uses quite expensive SC software for internal use in actually developing OSX.

      > Also gcc and it is large project uses cvs, there are currently 10 experimental branches plus 1 stable branch plus the head. Look at all the *BSD, they use cvs and they are the kernel plus userland even imports sources from else where too.

      And none of these projects has the number of developers/hackers that Linux currently does. Anyways, with this logic, we should all be using Windows right now.

    7. Re:point by Anonymous Coward · · Score: 4, Insightful

      Ye gods, man. What are you talking about? Sure, Linux is a pretty big project. Maybe it's not best suited to CVS management, that's not my call, nor anyone elses, besides the main kernel contributors, and Linus himself. However, I think you do yourself a great disservice when you completely ignore many of the other GIANT projects that utelize CVS successfully. I can't comment on Net or OpenBSD, but FreeBSD development is very much tied to CVS. CVS is used to keep track of the ports distrubution, the necessary bins and source to make an install run, and the main kernel source itself. Grass(the GIS software) is another absolutely huge project (the full source weighing in many times the size of Linux), XFree86 (pretty huge in it's own right--also many times Linux's size, with a large ammount of active development), and god knows how many other Open Source and in-house software is developed using CVS.

      By making a blanket statement like you have, you ignore what good CVS has done to a great many projects (some enormous, some not). Frankly, if the developers want certian features, they can certianly add them; the source is there, afterall. If they have no intrest in making the tools they use better for themselves directly, the least they could do is point out the flaws in the system to somebody who is interested in that project. Instead, all I hear is "CVS sucks, subversion sucks, it won't/can't do what I want, so I won't even bother with it!" Unwarrented and constructive criticism are different things, the latter being a good way to help progress, the former being a great way to hinder progress.
      That is bullshit, plain 'an simple. If they are unwilling to support their ideals, then they should not be OSS devs in the first place.

    8. Re:point by eyez · · Score: 3, Interesting

      Software with non-restrictive licenses should be used for important free software projects even when it is not seemingly the best tool for the job.

      Try telling them this; The kernel developers would laugh in your face. They've said before (Linus Especially) that they're not going to use an inferior tool just because it's free. As long as it doesn't hurt them, they'll use what they consider the best tool for the job.

      A license like this makes things harder for someone who wants to hack on the kernel but who is prohibited by BitKeeper from getting the source the way the rest of the kernel team does.

      Not really. like has been pointed out many many times on lkml, you don't need to even touch BK to be involved in kernel development.

      As linus said in one of his posts to lkml a while back, "Or just go on and ignore the fact that some people are using BK - you don't actually have to ever even know.". The kernel team using bk doesn't hurt on anyone's ability to develop the kernel.

      --
      get 0wned. irc.w30wnzj00.com
    9. Re:point by Ian+Bicking · · Score: 3, Interesting
      It's funny how much people will bitch when they're not the ones that have to deal with the inadequacies of $OSS_SM_TOOL when it comes to kernel development.
      RMS's integrity with respect to this is unquestionable -- he restricts himself solely to using free software, regardless of the flaws in that software. He has also puts a great deal of effort into encouraging and supporting the filling in of holes in available free software. In fact, I think this has been one of the most important things that GNU did -- in the early years, people in the GNU project spent considerable time implementing really boring code that needed to be implemented to create a complete system, laying the groundwork for the completely free systems we can use today.

      I would expect that in addition to this post to the kernel list, RMS is also doing what he can to support BK alternatives. But that probably would not be as public or controversial.

    10. Re:point by eyez · · Score: 5, Insightful

      I would expect that in addition to this post to the kernel list, RMS is also doing what he can to support BK alternatives. But that probably would not be as public or controversial.

      That's precisely the problem. He's making himself look like more of an ass by doing this. It would be 5000% more effective for his post to lkml to say "I've decided to support the (subversion|arch|aegis|pcrs|whatever) project as an official GNU project, and give them funding and development help so that the kernel team will have a viable alternative to BitKeeper. The project page is at http://www.gnu.org/projects/gnukeeper. Any input from kernel developers about what features are needed to replace BK are welcome at the mailing list, gnukeeper-devel@gnu.org"

      *THAT* is constructive. Sending a post that says that he's doing something about his situation. Otherwise he looks like every other crybaby group, like the Group of university students earlier this year, or whoever started last weeks huge thread. Saying "I Hate that you're using this closed product!" is all good and well, but if you don't follow it up with "So here's what I'm doing to remedy the situation", you look like an idiot. If you care that strongly about something, especially if you're in charge of or high up in the GNU foundation or the Free Software Foundation, you should put some backing behind your words.

      I expect more out of RMS as this; Others have pointed out that the linux environment is kind of a "flagship" of opensource development in GNU/FSF's eyes. You'd think they'd be committed to providing an alternative if they cared. They've done it with lots of other stuff in the unix world, and they've done a very good job. But, it's been since April or so since bk started being used for kernel devel, and not a single project has stepped up with GNU/FSF's backing and put some real work into doing everything bitkeeper does and more.

      Or, the reason could be that Larry McVoy's estimates on the time and money required to create another such beast are shockingly accurate, that's why nothing's stepped up.

      --
      get 0wned. irc.w30wnzj00.com
    11. Re:point by leandrod · · Score: 3, Insightful
      > The kernel developers decided that BitKeeper was the best tool for the job so they used it

      Interestingly enough, if everyone used the same arguments Linux, the kernel, would never had coming into being.

      Just imagine that gcc and the other GNU utilities carried a similar license. Linus would have had to buy a real compiler and developer toolbox before even starting, and these cost real money in those days, much more than he could afford. And then no one would use his work or collaborate with him, because BSD and the other Unices were so much better for the task. The few tinkerers would have stayed with BSD.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    12. Re:point by sql*kitten · · Score: 4, Insightful

      Untrue. Why do you think they break "kernel module source compatibility" with every patchlevel release? Obviously this has something to do with ideology, because not having to recompile kernel modules is a lot easier to the end user.

      The ideology that defines Free Software people in general is that you make things easier for the developer, not the user. If the user doesn't like it, they should do their own development (that's what the source is for). If they don't want to do that, they can pay someone to do it for them (even RMS has no problems with that, so long as the source is available). If they don't want to code and they don't want to pay, they're irrelevant and should shut up and be grateful for having any software in the first place. Harsh, but that's the way it works in practice.

    13. Re:point by jgerman · · Score: 3, Offtopic

      As long as ($TASK !~ /server/i), "Windows" is often the most suitable software.



      Untrue, try, for playing games, and the business end of things maybe windows has the edge, but when it comes to just about anything else, not just server oreiented domains, unix systems have the edge.

      --
      I'm the big fish in the big pond bitch.
    14. Re:point by eyez · · Score: 3, Insightful

      Does that not seem a little childish, to demand of the person who gave you most of the operating system you are now using, that he continue to get you out of proprietary software ruts in the future?

      Not really; I'm not the one who has a problem with the kernel developers using BitKeeper. But that's what my problem is. Over the years, RMS's attitude has gone from "The world is wrong, I should fix it" to "The world is wrong. I should tell everyone else to fix it."

      The answer that's repeatedly given on the kernel mailing list is "Well, if you want us to use something else, build it for us.". This is like RMS walking up to a carpenter, taking his hammer, and telling the carpenter to invent something better-- Nevermind that he's in the middle of building a house.

      But none of the naysayers ever ask "What can *I* do to fix this?". I only expect more out of RMS, because he didn't say "HEY! YOU GUYS ARE USING PROPRIETARY UNIX COMPILERS! USE SOMETHING MORE FREE!". He said "Hey, i should make a truly free compiler."

      So why isn't this the situation for BitKeeper?

      --
      get 0wned. irc.w30wnzj00.com
    15. Re:point by himi · · Score: 4, Insightful

      The day Larry changes the format to be incompatible with SCCS is the day the kernel developers stop using BitKeeper. Larry knows this, and he's not likely to shoot himself repeatedly in the foot by doing that.

      You might ask yourself why BitKeeper is still using the SCCS file format. The answer is for exactly this reason: they don't want to lock their users in by using a proprietary format.

      What might be a real risk is if Larry loses control of BitMover and the new owners decided to make such changes. As it stands, that's not even a mid-term threat, and with any luck the Free alternatives would have caught up enough to be usable if it /did/ happen.

      himi

      --

      My very own DeCSS mirror.
    16. Re:point by rseuhs · · Score: 4, Informative
      KDE uses cvs just fine.

      Now I don't have counted the developers of KDE and Linux, but I'd guesstimate that there are more on KDE.

    17. Re:point by pdqlamb · · Score: 3, Insightful
      Maybe its time for someone to start developing a OSS competitor to BitKeeper (without using BitKeeper of course!)

      Nobody will; Why? Nobody has really tried so far- even RMS is too stubborn to ask "Well, what is it that bitkeeper does that (cvs|subversion|arch|pcrs) doesn't do?", and then gone off and tried to implement it- in fact, this is what all of bitkeeper's advocates, including it's creator, Larry McVoy, and Linus Torvalds have been saying all this time. "Make me something better, and we'll use it.". Yet, everyone is very willing to complain, and just ignore when $KERNEL_DEVELOPER_USING_BK says "$FEATURE is something i use every day with BK, and isn't in any of the OSS source management tools."

      Since I don't follow the kernel mailing lists, has anyone compiled a list of features Linus and the other developers want? From what I've read, it sounds like Linus glanced cursorily at a few other source control systems, and then pounced on BK. (Maybe Larry bought him a beer at the right time, or maybe the planets were aligned correctly the night he tried it out.) But I haven't seen a list of what the kernel developers want in the product. And the only comment I've read about why Linus didn't use one of the free source control systems basically said they didn't give him the warm fuzzies.

      Unless somebody can put together a comprehensive list of what features they want or use, the rest of us will just keep wondering: why can't Linus use CVS, for instance, when other projects apparently can use it? Looking at the largest downloads I have, gcc, gdb, and xemacs have similar sizes, but they don't use BK. Why? and why can't the kernel developers?

    18. Re:point by blibbleblobble · · Score: 3, Insightful

      "So why isn't this the situation for BitKeeper?"

      Simple. The tech community should be smart enough to help themselves. It would be a weak industry indeed if we all depended on one person to solve the difficult problems.

      Subversion was written by people who saw CVS and wanted something which was free. This is the way things should work, and indeed, it seems to be working very well. No need to go begging back to our political leaders. Isn't GCC enough of a gift?

      At a guess, the fundamental reason your requests are being ignored is that people who write software on their own don't need CVS. What ESR calls the cathedrals, they don't need committees to decide whose turn it is to design the roof today. So why should somebody who can shut themselves into an office for 2 weeks and write a programming language need a CVS replacement? Isn't that something for the teams of 20 people next door divvying up tasks between themselves?

      Like the kernel developers, for example.

      Or the mozilla team.

      Or any of the thousands of companies who pay for Visual-SourceSafe licenses each year.

      Or literally, anyone with an interest in DIFF and GZIP with time on their hands looking for a project.

      Or the Subversion team.

    19. Re:point by Rich · · Score: 3, Informative

      Whilst it's true we manage ok with CVS, it's certainly not without its problems. We've discussed changing to something else several times, and I suspect when subversion is sufficiently developed we'll change to that.

      Rich.

  4. I don't get it by ZeroLogic · · Score: 3, Insightful

    Maybe I don't understand the issue, BitKeeper is a private company, they make a product that they don't want their competitors to use for free. What's the harm in that? Ford doesn't donate cars to Chevy neither does McDonalds give Burger King free food, why is this different?

    1. Re:I don't get it by stefanlasiewski · · Score: 4, Informative

      This is different because occasionally, a Chevy worker will drive a Ford to work; and a McDonalds worker will eat Burger King food. Neither activity is restricted by their job.

      --
      "Can of worms? The can is open... the worms are everywhere."
    2. Re:I don't get it by Scott+Wood · · Score: 5, Insightful
      While I certainly don't speak for RMS's looniness, this is a rather unfortunate clause given Larry's stated goal of helping kernel development. Not only do most Linux vendors ship "competing" products such as CVS (which Larry handwaved away by calling it distribution rather than selling, even when someone pays Red Hat for a CD that contains CVS, and thus contains functionality that competes (even if pathetically so) with BitKeeper). Furthermore, given the volunteer nature of much of Linux's development, there are many people that would have to go beg Larry for a special waiver to make use of BitKeeper in kernel development simply because of something their employer works on or sells.

      It's not that BitKeeper shouldn't have the right to choose to whom they give away their product for free; it's just that many feel that it's not appropriate for something intended to be used to maintain an Open Source project such as the Linux kernel.

    3. Re:I don't get it by renehollan · · Score: 3, Insightful
      Maybe I don't understand the issue

      Well, aside from RMS getting the legitimate right to go "I told you so!"ing, perhaps an analogy might help:

      I produce carbon dioxide via exhalation. Others are permitted to use this carbon dioxide for human breathing (via the use of plants) so long as they do not compete with me for the resources of the Earth, or, in any way, hinder my life. Upon being informed of a violation of this license, it shall be incumbant upon the alleged violator to prove they have not used any of the carbon dioxide I produce.

      There, how's that? It can be relatively easily shown that each breath anyone takes is bound to have some molecules of oxygen from the transformation (via a plant) of the carbon dioxide I exhale. I have effectively produced a license that makes everyone in the world my slave.

      Would anyone successfully argue that what my body produces is not mine to license at will?

      O.K., the analogy isn't perfect (in that one has little choice in being exposed to what I produce), and others could foist the same license on me in retalliation, but the point is that using BitKeeper may taint the production of particularly useful free software, in the same way that the GPL is accused of being "viral".

      Use it to maintain the Linux kernel, and perhaps you can't now develop a BitKeeper clone under Linux because of the "pollution".

      If anything, license shenanigans like this one are the one thing that justify RMS' concern and disdain for non-free software.

      --
      You could've hired me.
    4. Re:I don't get it by AstralSeeker · · Score: 3, Insightful

      And the Chevy worker paid for it's car, and the McDonald employee will pay for it's food... where's the difference with BitKeeper? And anyway a Chevy worker or a McDonald employee is (probably) just a guy executing a job like he was told to. He's not responsible for the research that went behind his job so nobody cares what he uses/knows. It's not gonna give any competitive advantage to the company.

    5. Re:I don't get it by Guppy06 · · Score: 5, Funny

      "And burgers?? Don't want tomato or pickle?"

      On the other hand, the GNU license prevents you from adding secret sauce without disclosing the ingredients.

    6. Re:I don't get it by JohnnyO · · Score: 3, Funny

      Ahh, but only if you let your friend have a bite of the burger.

    7. Re:I don't get it by innocent_white_lamb · · Score: 4, Insightful

      On the other hand, the GNU license prevents you from adding secret sauce without disclosing the ingredients.

      No, you can add your own secret sauce if the burger is for your own consumption and nobody will object. However, when you pour a mysterious liquid over the burger and offer it to the guy sitting at the next table, he is entitled to ask you what's in it and he doesn't have to eat it unless you tell him.

      --
      If you're a zombie and you know it, bite your friend!
    8. Re:I don't get it by Atzanteol · · Score: 4, Insightful

      Yes, but that Chevy worker probably *bought* that Ford, and wasn't given it by Ford.

      --
      "Ignorance more frequently begets confidence than does knowledge"

      - Charles Darwin
  5. what's the alternative? by Anonymous+Cowrad · · Score: 5, Insightful
    "What would be even better is if it convinced free software people to develop a tool as good as, or better than, Bitkeeper," -- Rik van Riel.


    Well spoken, Rik. Until RMS can propose an alternative to BitKeeper, he's just pissing in the wind.

    Of course, he has every right to piss in the wind as much as he likes.
    --

    --
    pants ahoy
  6. "no free licenses for our competition" by CoughDropAddict · · Score: 5, Interesting

    It seems reasonable enough that Larry would want to prohibit people from using bitkeeper to compete against bitkeeper.

    However I think it is telling that the license goes a step further and disallows any person or entity who ever works on a competitor from ever using bitkeeper. So Larry is essentially helping to see that many people (Linux kernel hackers using bitkeeper) are unable to ever compete with him, even if the kernel hacking and open-source-SCM hacking are in no way related. Way to drive a wedge through the free software community.

    1. Re:"no free licenses for our competition" by hotgazpacho · · Score: 5, Informative

      Actually, if you read the article, it says that the FREE version of BitKeeper cannot be used to work on its competition. i.e. You cannot use the FREE version of BitKeeper to develop CVS. HOWEVER, one can BUY a license from BitKeeper to do just that.

    2. Re:"no free licenses for our competition" by CoughDropAddict · · Score: 5, Insightful

      I am quite aware of this distinction, however you are missing my point. The license says more than "you cannot use the free version to develop the competition." It also says "if you, the person, do any kind of unrelated development on a competitor (perhaps even submitting a bug report!) you no may no longer use the free version of bitkeeper. Which means that any kernel developer who has become accustomed to using BitKeeper will retstrain himself from aiding competing free software projects at all.

      This divides the world of open-source developers into two mutually exclusive groups: those who use bitkeeper for kernel development and those who can ever work on free alternatives.

    3. Re:"no free licenses for our competition" by fv · · Score: 3, Insightful
      Yes, this restriction supposedly only applies to the free version. But Larry can easily exclude people he doesn't like from the paid version via discriminatory pricing. Note how he immediately threatens lawsuits when someone posts the BK pricelist. Even if the pricing was not discriminatory, few open source hackers have an extra $5,800 lying around for a single-user Bitkeeper license. So if you are or ever want to be a kernel hacker, Larry wants you to think long and hard before contributing that little Subversion or CVS patch. It is true that you can still "work around" using Bitkeeper for kernel development, but Linus seems to be subtly encouraging its use more and more.

      I for one plan to resist this bogus, anticompetitive license. As others have mentioned, this is like MS changing their EULA to exclude developers of competing operating systems. The best way to fight BK is to write a compelling replacement. My best wishes go out to those who are already doing such admirable work!

      Cheers,
      Fyodor

      Concerned about your network security? Try the Free Nmap Security Scanner.

  7. Simple Solution by chill · · Score: 5, Insightful

    Code something GPL that performs equal to or better than BitKeeper.

    I'm not familiar with the arguments of CVS vs BitKeeper. If it is a philosophical argument about a way to do things, then fine. Someone take the CVS code, fork it, and modify it to do what BitKeeper does.

    It is a question of the "Software as Religion" vs "Software as Tool".

    I'm going to go out on a limb and assume that Linus and the other kernel hackers were pretty proficient with CVS and knew what they were doing. If they are more productive with BK, then there is something wrong with CVS.

    Productivity is what counts. This isn't an addiction -- if people want to they can switch back to CVS at any time.

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:Simple Solution by maw · · Score: 5, Informative
      It's called subversion. Currently, the goal is for it to be a suitable cvs replacement.

      Maybe post-1.0 they'll offer features that would bring it up to the level of bitkeeper, but right now, that isn't their main goal.

      --
      You're a suburbanite.
    2. Re:Simple Solution by eyez · · Score: 5, Informative

      Here's a handful of links to kernel archive mirrors discussing subversion. There current attitude of kernel developers is that subversion is nowhere near mature enough to replace bk for kernel use yet. once it is, people will happily switch.

      So, for the time being, live with them using BK, and know that you don't have to use it at all to help with kernel development.

      --
      get 0wned. irc.w30wnzj00.com
    3. Re:Simple Solution by sql*kitten · · Score: 4, Insightful

      Code something GPL that performs equal to or better than BitKeeper.

      Well that is the structural problem of Open Source, and it goes all the way back to when RMS worked at MIT, and spent years reverse engineering Symbolics products and giving the code away to their competition. It's always been about seeing a commercial product - whether it's BitKeeper, Photoshop, CDE or even Unix itself - and producing a free clone. All the innovation and risk-taking happens in the commercial world, yet the Open Source movement damages the commercial world by making it more and more difficult for them to afford to create new products. It's not a sustainable situation.

    4. Re:Simple Solution by Ed+Avis · · Score: 5, Funny

      'Piece of shit' is a bit strong to describe CVS. 'Crude but effective' is closer to the mark.

      Or perhaps 'piece of shit, but one that has been lying around in the hot sun and baked so hard that it actually makes quite an effective tool for banging in nails, provided you don't mind the smell'.

      Bitkeeper sounds good technically but c'mon, the stink from McVoy's licensing surely outweighs the small amount of nose-holding you have to do when using CVS. When the choice is between something technically crude (but 80% good enough) and something that does 100% of the job but has odious licensing policies, surely the difference in licences outweighs the 20% of extra functionality you're getting.

      --
      -- Ed Avis ed@membled.com
    5. Re:Simple Solution by JordanH · · Score: 5, Insightful
      • Well that is the structural problem of Open Source, and it goes all the way back to when RMS worked at MIT, and spent years reverse engineering Symbolics products and giving the code away to their competition.

      Well, RMS' view was that both Symbolics and LMI were benefitting heavily from his own (and others) work at the MIT Lab. He felt it only fair that the MIT Lab should have access to their changes. To facilitate this, he had to make sure that both companies had access to any changes made so as to make any further changes they made applicable to the current source base.

      • All the innovation and risk-taking happens in the commercial world, yet the Open Source movement damages the commercial world by making it more and more difficult for them to afford to create new products. It's not a sustainable situation.

      Funny how your first sentence provides a counter example to your thesis. All the innovation that went into to the LMI and Symbolics development initially was done in the public-domain free-software world of the MIT AI Lab. Then, the commercial entities sprang up to take advantage of this when it was shown to have value.

      It also ignores the history that the FSF's first product was Emacs, which was initially developed in the free-software world. Another example of where the innovation was done in the Free Software world and commercial entities sprung up to take advantage of that development, btw. Gosling Emacs was a commercial clone of the Emacs that was developed at MIT.

      Anyway... BitKeeper, Photoshop, CDE and Unix are innovative? Seems to me that each borrowed very heavily from other products before them, yet you don't complain about how they reengineered known solutions making it more difficult for those who went before them. In the case of BitKeeper, the most widely known predeccesors were, in fact, free software solutions.

      What you are describing is competition. Whether from free software or from commercial software, that's all it is. Funny, I thought competition was good for markets. It clears out bad products in favor of others that have more favorable attributes, be it features or price.

      If it's not sustainable, as you claim, what is the solution? Extend copyrights even further, more software patents? What? Seems like the commercial world, with it's software patents, DMCA, copyright extensions, batteries of lawyers and marketroids have all the competitive advantages already. If they can't win with the legal system on their side, then perhaps there is something seriously wrong with their model.

    6. Re:Simple Solution by sql*kitten · · Score: 3

      Funny how your first sentence provides a counter example to your thesis. All the innovation that went into to the LMI and Symbolics development initially was done in the public-domain free-software world of the MIT AI Lab. Then, the commercial entities sprang up to take advantage of this when it was shown to have value.

      But that's how it's always worked, in every technological industry. Universities do the basic, theoretical research (paid for by industry sponsorship or government grants, which is the same thing indirectly) then commercial entities are formed to make the theories into something practical. Some of the profits made end up back at the universities to fund more research, even more so if the university was smart enough to take some equity - I believe MIT do that quite a bit.

      What you are describing is competition. Whether from free software or from commercial software, that's all it is. Funny, I thought competition was good for markets. It clears out bad products in favor of others that have more favorable attributes, be it features or price.

      Competition is good for markets, but RMS wasn't competing, he was safe in his academic position, insulated from the risks of the market. All he was doing was destroying Symbolics - in doing so, he created no value.

      If it's not sustainable, as you claim, what is the solution?

      The solution is for the Free Software world to stop thinking in terms of free versions of commercial products, and start looking for solutions to problems that are too exotic or novel for the commercial world. New interfaces for example, and entirely new applications.

      A good test would be: if it wasn't free, would anyone buy it? An awful lot of Free software fails that test. If MS Office and Star Office were the same price, which would be better?

    7. Re:Simple Solution by back_pages · · Score: 4, Interesting
      Oh, but I bet it is a sustainable situation. Has anyone considered that the conflict between closed-source proprietary software and open source freely distributable software as a checks and balances? They complement each other, and I doubt either would be where they are today without the other.

      Consider that the open source software often chases the coattails of proprietary software, and it is like an erosive force against a software monopoly. Rather than let a given company build an invincible fortress of refined, polished, peerless software, they are constantly forced to accept that their current innovations will eventually become basically public domain through free software. This is an incredible incentive to keep in touch with their market, make real and substantial improvements to their product, and avoid heavy handed dictator style behavior.

      If closed-source proprietary software blazes the trail, open source paves the highway. Making a practical public domain out of so much software ensures that innovation in proprietary software is a process, not an end point. It's competition, it's checks and balances, and it benefits everyone who uses the software.

      Open source does hardly any damage to commercial products. It does ensure that the #1 commercial product has a competitor close on its heels that cannot be driven away not by competitive pricing but by smart business and new inventions. I wouldn't argue against having competition around here, I get the feeling that Microsoft isn't loved. At any rate, this is a very sustainable situation and the checks and balances benefit the users substantially.

    8. Re:Simple Solution by JordanH · · Score: 3, Interesting
      • But that's how it's always worked, in every technological industry. Universities do the basic, theoretical research (paid for by industry sponsorship or government grants, which is the same thing indirectly) then commercial entities are formed to make the theories into something practical.

      To my way of thinking, Universities should provide free software when it's supported by Government grants in that the public paid for it. And, no, I don't buy that government support is the same as industry grants. If that were the case, we should close the libraries since there are plenty of fine book stores available. After all, Government support is the same as Industry grant and we can't expect the book stores to support their "competition" through their taxes now, can we?

      Government support is the same as Industry grant when Industry runs the Government. I don't think we're there yet, but with people thinking like you, I suspect we're not far from it.

      So, which is it, do these risk-takers in industry provide all the innovation, or is it done in Universities as you are saying now?

      • Competition is good for markets, but RMS wasn't competing, he was safe in his academic position, insulated from the risks of the market. All he was doing was destroying Symbolics - in doing so, he created no value.

      Total baloney. Read, Free as in Freedom: Richard Stallman's Crusade for Free Software RMS created a lot of that software, even after Symbolics and LMI were formed, and offered value to BOTH companies. He felt it only fair that they kick back by providing their changes back to him. When one of the companies balked at the arrangement, he proceeded to produce all of the Symbolics changes on his own without looking at the Symbolics source code and work with LMI in integrating that into their shared base. It seems to me that it was Symbolics who were destroying the value equation here by not sharing their changes and facilitating common advancement.

      Sure, competition is good for markets, but cooperation can be better for advancement in some areas.

      • The solution is for the Free Software world to stop thinking in terms of free versions of commercial products, and start looking for solutions to problems that are too exotic or novel for the commercial world. New interfaces for example, and entirely new applications.

      So, should the Apache folks just stop working and cede the market to iPlanet and MS? Should people stop donating their time to work on Perl and Python and let Activestate do that for the "market". Should the PostgreSQL and MySQL people stop work now that we have Oracle and Sybase?

      Why should people suddenly stop working on code they themselves need and use and start only looking into far out research projects? I guess you would argue that no value is created by Apache, Perl, MySQL and the like and that these things just needlessly distract from the commercial marketplace?

      Web Servers and Web Browsers were all initially free software. I guess you'd argue that those teams should stop working as soon as the commercial "innovators" move in, huh?

      Actually, I think you'll find a lot of free software does extend into exotic areas, like advanced clustering, new OS models, P2P, new languages (Icon, ML, Mercury, most Schemes are all free software), AI. Of course, it doesn't take long before commercial interests start to work in these same areas if they show promise. I guess your take would be that the free software community should back off at that point.

      • A good test would be: if it wasn't free, would anyone buy it? An awful lot of Free software fails that test. If MS Office and Star Office were the same price, which would be better?

      Why is that a better test? Since when is value not related to price? There are some areas that Free Software has not competed well with commercial offerings, like UI, documentation and support. Why should Free Software give up it's advantage in price?

      OK, let's compare MS Office and Star Office at the same price. Free. Oh wait, MS Office could never exist at that price, so it's not a realistic comparison. Why is it any more a realistic comparison to raise the price of free software?

  8. So? by The+Tyro · · Score: 4, Insightful

    RMS has an opinion, and has expressed it... I don't see where all the ad hominim vitriol is coming from.

    Like him or not, RMS is one of the Free Software movement's Great Thinkers (TM).

    Sheesh... let him expound upon his point, and if you don't like it, ignore it.

    --
    Even if a man chops off your hand with a sword, you still have two nice, sharp bones to stick in his eyes.
    1. Re:So? by asv108 · · Score: 4, Interesting
      RMS has an opinion, and has expressed it... I don't see where all the ad hominim vitriol is coming from.

      RMS is certainly entitled to his opinion; I don't think that is the issue here. The issue here is his choice of forum. The Linux Kernel Dev list is for technical discussion related to the Linux kernel. If RMS has issues with the bitkeeper license he should post his opinions somewhere else, like the GNU website or Usenet. It doesn't matter who you are or what you've accomplised, offtopic is offtopic.

    2. Re:So? by civilizedINTENSITY · · Score: 4, Interesting
      "The issue here is his choice of forum."

      Yet, thats where Larry posts liscense issues. Thats where the discussion was taking place. Who are you to tell them where they can discuss kernel issues?
      From: David S. Miller
      Subject: Re: New BK License Problem?
      Date: Fri, 04 Oct 2002 17:04:51 -0700 (PDT)
      From: Roman Zippel
      Date: Sat, 5 Oct 2002 00:36:16 +0200 (CEST)
      On Fri, 4 Oct 2002, Dr. David Alan Gilbert wrote:
      > Just to be clear;
      ... this is completely offtopic, can this _please_ be moved to a bk list?
      Thanks.
      It is very ontopic because it affects a number of kernel developers.
      Whether you like BK or not, it is the primary source management tool used by Linus and others, it is even documented in the source tree as such.
      Therefore, such a license change could change that, so it's a relavant topic.
      And finally, as the person who has to maintain this list and deal with the daily bounce pool this list generates every day, I declare it as ontopic so :-P~~~~~~
  9. that couldn't have been a RMS quote... by DuctTape · · Score: 4, Funny

    That couldn't have been RMS in that quote. He didn't say GNU/Linux.

    --
    Is this thing on? Hello?
    1. Re:that couldn't have been a RMS quote... by pyman · · Score: 5, Informative

      That is because he was talking about the Linux kernel... NOT the GNU/Linux system.

      --
      a ^= b; b ^= a; a ^= b;
    2. Re:that couldn't have been a RMS quote... by Restil · · Score: 3, Informative

      GNU/Linux only applies in those situations where you refer to the entire operating system. The kernel itself is pure Linux, and even RMS doesn't debate that issue.

      Since BK is purely a kernel development issue, his failure to prefix GNU isn't proof of his lack of sincerity. :)

      -Restil

      --
      Play with my webcams and lights here
  10. Re:Questions wanted answered: by Scott+Wood · · Score: 4, Insightful
    They do dual license; there's one license for free-as-in-beer use, and another, less restrictive license for people that pay for the product.

    Oh, wait, you want one of those licenses to be Open Source because you feel you have an entitlement to use their product for free on terms of your choosing, and somehow the existence of another license is going to make the Open Source Fairy fly by and pay the bills. Sorry, I forgot.

  11. Usual disrespect for RMS by dh003i · · Score: 4, Interesting

    As usual, RMS gets little or no respect around here, despite the fact that, as usual, he's right.

    Those of you saying that the restrictions RMS mentions would be lifted if you bought the commercial version are missing the point. The point by RMS is that all of the licenses under which you can use BitKeeper are draconian, as they're EULA's. The problem with EULA's is that they can be changed at any time by the developer, thus creating an unfair situation; BitKeeper could just as easily include such restrictions on its paid-for version. The other problem is that accepting them is mandatory, thus creating another power imbalance.

    That said, this is all the more reason for developers to switch from BitKeeper to alternatives. BitKeeper can impose any draconian restrictions on you they wish, and you'd best not wait until you're trapped into using BitKeeper and dependant on it to change.

    I'd advise the rest of /. to listen more to RMS when he speaks and suppress your obvious desire to bash a man because he has a certain set of ideals.

    1. Re:Usual disrespect for RMS by TheFrood · · Score: 3, Insightful

      I agree with you all the way that RMS gets less respect than he deserves. He should be speaking out against the BitKeeper license. He should be using it as an example of what kind of restrictions proprietary licenses can put on you However, he should not be doing it on the LKML.

      Starting a political argument on the LKML accomplishes nothing. Almost everyone who reads the LKML knows about the BitKeeper issue and has an opinion already. Posting a rant on the LKML is more likely to polarize people against his position than anything else.

      Keep at it, RMS, but be smarter about it.

      --
      If you say "I'll probably get modded down for this..." then I will mod you down.
    2. Re:Usual disrespect for RMS by eyez · · Score: 4, Insightful

      That said, this is all the more reason for developers to switch from BitKeeper to alternatives. BitKeeper can impose any draconian restrictions on you they wish, and you'd best not wait until you're trapped into using BitKeeper and dependant on it to change.

      Trapped? Not so. If they stop using bk, everything bk ever did still works in patches, and they'd just be in the same boat they were BEFORE using bk-- diff and patch. In fact, right now, if RMS wanted to send Linus a regular patch, he could, without ever using bk. There's also currently a rsync'able bk mirror out there, and bitkeeper retains SCCS compatibility. Anyone can use that and get the latest bk tree, write a patch, and send it on to Linus.

      But ask yourself this- If any SCM software out there worked anywhere near as well as bk, why are there so many out there with personal bk trees, and using bk, and none using anything else, exporting their stuff to diff format, and sending the patches that way?

      Because none of the OSS SCM tools can do that for them. So all the complainers out there should get to hard work fixing up an OSS SCM to the linux developers' needs, and spend less time bitching.

      --
      get 0wned. irc.w30wnzj00.com
    3. Re:Usual disrespect for RMS by xigxag · · Score: 3

      The problem with EULA's is that they can be changed at any time by the developer, thus creating an unfair situation; BitKeeper could just as easily include such restrictions on its paid-for version. The other problem is that accepting them is mandatory, thus creating another power imbalance.

      Just to be clear here. Yes, new versions of software can come with revised EULAs. Yes, accepting the EULA is mandatory if you want to use the software you purchase. But once you buy the software with the EULA, you're not compelled to accept any changes in future EULAs, which is what both you and RMS seem to be implying. In other words, they can't just unilaterally revoke the license you have already got. They can simply do their best to persuade you to accept a new EULA by releasing an improved product.

      Note: This last point is a key difference between freeware projects and commercial software concerns. The latter are under pressure to release improved product because their bottom line depends upon it. The former can certainly improve a great deal as the various GNU projects demonstrate, but they improve on their own timetable. In a sense, there are no customers, just users. Users can wait for improvements, but customers usually won't. And reacting timely to the needs of the customers is why BitMover is a success.

      I do, however, agree with you that RMS is worth listening to. Even when he is wrong, he is always compelling.

      --
      There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
    4. Re:Usual disrespect for RMS by Twirlip+of+the+Mists · · Score: 3, Informative

      The problem with EULA's is that they can be changed at any time by the developer....

      Except, no. When you enter into a license agreement with a licensor, the terms of the agreement are set in stone at the time that you and the licensor enter in to the agreement. It's not okay for one or the other party to make arbitrary changes to the license agreement after the fact.

      Agreements governing a service are different; this is probably what you're thinking of. If you enter into a service agreement with a provider, sometimes that provider reserves the right to change the terms of service, with proper notification, whenever he likes. This makes sense because a service is an ongoing engagement, and it is unreasonable for a provider to be bound permanently by a set of terms when neither party can predict what circumstances might arise during the term of the agreement.

      But software license agreements can't just be arbitrarily changed by either party.

      --

      I write in my journal
  12. Re:Mc Voy is an idiot by Dionysus · · Score: 4, Insightful

    He doesn't give a flying fuck about open source, he only wants to sell his product.

    If he wants to stay in business,he better want to sell his product.

    --
    Je ne parle pas francais.
  13. Dear Mr. Stallman by ndogg · · Score: 4, Interesting

    Firstly, this isn't your project. Mr. Torvalds has made his points and position quite clear, and it's time that you and the rest of the Free Software people leave the kernel hackers well enough alone.

    Also, do you have no respect what's so ever? What are you doing posting on the LKML, which is not meant to be political.

    Also, it would be nice if you would get your facts straight. Bitkeeper (the gratis version, anyway) only restricts you from using it to develop a competing project, not from using one.

    --
    // file: mice.h
    #include "frickin_lasers.h"
    1. Re:Dear Mr. Stallman by Ian+Bicking · · Score: 3, Insightful
      Bitkeeper (the gratis version, anyway) only restricts you from using it to develop a competing project, not from using one.
      That both those freedoms are essential is a defining aspect of Free Software. That both those freedoms are important is a defining aspect of a true member of the community.
    2. Re:Dear Mr. Stallman by nathanh · · Score: 3, Insightful
      Also, do you have no respect what's so ever? What are you doing posting on the LKML, which is not meant to be political.

      Spoken like somebody who has never read LKML.

      Also, it would be nice if you would get your facts straight.

      Practise what you preach.

  14. Re:Mc Voy is an idiot by Dr+Kool,+PhD · · Score: 5, Funny

    Yeah, this guy is a total loser, he is only interested in making money. This is totally different from IBM, O'Reilly and especially VA Software/Linux/Whatever, they only want to contribute to open source world domination. In fact, VA is happy to lose millions every year. Imagine, a company only interested in making money!! Someone should tell the FBI to bust these BitKeeper clowns.

  15. Money where your mouth is... by sterno · · Score: 5, Insightful

    I preface this by saying that I'm a big fan and proponent of open source but anyhow...

    If free software really is better then why do people like RMS need to come out ranting about giving into the evils of proprietary software. Either it's a better model of development or it isn't, and if you have to brow beat people into using it, maybe it's not a better way of doing things. It always seems to me that the people most afraid that their beliefs are wrong are the ones screaming the loudest that they are right.

    As long as we have the freedom to write free software and use free software, then I don't really see the point of such ranting. Let the software itself speak quietly of the benefits of being free rather than screaming about the evils of proprietary software.

    I'm sure that Linus would be happy to use a more free product if he felt it was suited to the task. Linus, unlike RMS, has never, to my knowledge, been much of a politician. He wrote open source software because it made sense to do so. He's made his choices for the same reason anybody should, because they made good sound technical sense. (if I'm wrong here, please don't hesitate to point it out :)

    Either it will survive and thrive because it has benefits or it will shrivel up and die. Evolution marches merrily on. I mean the process, not the mail client. Though I LOVE the mail client :).

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Money where your mouth is... by rgmoore · · Score: 4, Insightful

      You misunderstand RMS's point about Free vs. proprietary software. He isn't the one who claims that Free Software is better because it has a superior development model, or at least that's not his primary point. His point is that Free Software is better because it gives freedom to its users: freedom to use it as they choose, to understand how it works, and to modify it to fit their needs. The points that he's making about BitKeeper are exactly in line with the points that he's always made about why proprietary software is so bad- it doesn't respect the needs of its users.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    2. Re:Money where your mouth is... by Have+Blue · · Score: 3, Insightful

      You misunderstand the parent's point. Why don't we (and RMS) try to objectively evaluate which tool and development model is better for a given project, instead of always demanding free software and frothing at the mouth? And why does he seem to take it as a personal offense every time a high-profile project makes a decision he doesn't like?

    3. Re:Money where your mouth is... by wd123 · · Score: 3, Funny

      Hitler was also once on a crusade. So was Stalin, so were the Knights Templars, so is George W. Bush for that matter. Your point again? Idiot.

      I hereby call attention to Godwin's Law and ask that the editors stop all commenting on this story.

      Good night.

      --
      "question = (to) ? be : !be;" --Shakespeare
    4. Re:Money where your mouth is... by sql*kitten · · Score: 4, Interesting

      His point is that Free Software is better because it gives freedom to its users: freedom to use it as they choose, to understand how it works, and to modify it to fit their needs.

      Question: is the average Word user made more or less free by having the source code to Word?

      proprietary software is so bad- it doesn't respect the needs of its users

      On the contrary, proprietary software must respect the needs of its users, otherwise they won't buy it. There are no such incentives for free software, which doesn't have to respect the needs of anyone but its author.

    5. Re:Money where your mouth is... by bfields · · Score: 3, Insightful
      If free software really is better then why do people like RMS need to come out ranting about giving into the evils of proprietary software.

      RMS has made his position extremely clear on every possible occasion: his dedication to "free software" has nothing to do with the ESR's dubious theory that open source development is a magical technique capabable of the effortless production of vast quantites of excellent code. RMS cares about the freedom itself. Freedom that we take for granted in the physical world but that is completely gone in the world of proprietary software:

      • The freedom to use tools that you own for any purpose that you see fit, not for only those purposes that the hardware store has specifically authorized its use for.
      • The freedom to modify tools that you own.
      Linus, unlike RMS, has never, to my knowledge, been much of a politician.

      On the contrary, Linus is very much a politician. The word "politician" is not synonymous with "person who is willing to argue that some decisions should be made on ethical, and not merely technical, matters."

      --Bruce F.

  16. Re:Questions wanted answered: by npietraniec · · Score: 3, Informative

    Larry said in a previous thread that if the kernel developers wanted to contact bitkeeper and get dispensation on the stuff they were worried about (because it doesn't follow the spirit of the license even though it might fall under the wording) that they could do that.

  17. RMS makes a good point by Henry+V+.009 · · Score: 4, Interesting

    According to RMS: If you even run bitkeeper, you can't contribute to CVS or other competetors.

    That seems to be quite a restriction. Imagine a Microsoft EULA that says: if you run Windows, you can't contribute to Linux.

    RMS has a point. Licenses like these are there to kill free software alternatives.

    Goddamn, but what has happened to slashdot? Judging by the posts from the majority of the slashdot crowd, I think that they'd be happier if slashdot started reporting every new Microsoft Update patch instead of new Kernal releases.

    1. Re:RMS makes a good point by Twirlip+of+the+Mists · · Score: 4, Informative
      You have it a bit backwards. The more accurate way of saying it is this: if you contribute to CVS or other competitors, you aren't eligible for the free license for BitKeeper. You can either buy BitKeeper, or not use it at all.

      Here's the relevant part of the license:
      (c) Notwithstanding any other terms in this License, this License is not
      available to You if You and/or your employer develop, produce, sell,
      and/or resell a product which contains substantially similar capabili-
      ties of the BitKeeper Software, or, in the reasonable opinion of Bit-
      Mover, competes with the BitKeeper Software.
      --

      I write in my journal
    2. Re:RMS makes a good point by RedWizzard · · Score: 5, Insightful
      According to RMS: If you even run bitkeeper, you can't contribute to CVS or other competetors.

      That seems to be quite a restriction. Imagine a Microsoft EULA that says: if you run Windows, you can't contribute to Linux.

      You've missed the point. You should have said "imagine a Microsoft EULA that says: if you don't contribute to Linux you can use Windows for free". Not such an issue anymore, is it?
    3. Re:RMS makes a good point by maunleon · · Score: 3, Interesting

      Some compiler makers (propbably Microsoft too, but I can't dig out their eula right now) do specify in their eula that you cannot use their compiler to create a competing product (e.g. another compiler)

      Just digging through my computer, I find that the borland BDE license specifies that if you use the BDE, your programs may not be "...general purpose database program or otherwise generally competitive with or a substitute for Paradox, dBASE, or the Borland Database Engine".

      For the MS Jet engine.. "your Licensed Product shall not substantially duplicate the capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, compete with same;"

      I wouldn't be surprised if MS inserted this into eulas for all their products (e.g. you cannot use word to write documentation for a competing product, you cannot use Windows to facilitate Linux development, etc)

  18. Someone mod parent down... by npietraniec · · Score: 3, Interesting

    He doesn't give a flying fuck about open source,

    That's bullshit. I read a good portion of the thread where they first discussed this and Mr. McVoy was pretty receptive to everything that the kernel people were saying. Did you read any of the threads or are you just flaming?

  19. Answer me this. by yeOldeSkeptic · · Score: 4, Insightful


    Stallman is correct. Bitkeeper is a proprietary product
    produced by a commercial company and that commercial
    company has the legal means (whether right or not)
    to suddenly change their license terms.


    I quite understand Linus' and Rik's aversion to
    puritanical arguments against their use of proprietary
    products when such proprietary products keep
    them productive.


    McVoy is a good guy as far as the
    Linux kernel hackers are concerned, but what will
    happen if a certain Mr. Bill Gates offers
    loads of cash to Mr. McVoy for his company?


    Steve: Hey Bill, do I have a deal for you.

    Bill: Yeah?

    Steve: What do you say to spending just a little over
    50 million dollars to derail Linux development
    on its tracks?

  20. We will never know by msobkow · · Score: 4, Interesting

    We will never know the answer to this puzzler because he is the only person in the world to get slashdot headlines by posting flamebait to the wrong news groups. Anyone else would either be ignored, flamed for cross-posting, or deleted by the moderators.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:We will never know by Bishop · · Score: 4, Insightful

      I don't really understand just how he can justify recommending that others use it.

      Linus has answered this question several times: Bitkeeper works. No opensource project aproaches the functionality of Bitkeeper. Remember that Linus cares more about functional software then open source software. Opensource software is just a means to an ends.

  21. Re:RMS kneejerk by GigsVT · · Score: 5, Insightful

    BK is not preventing Redhat, Suse, Mandrake (et al) employees from using BitKeeper, only those who actively develop Subversion or arch

    It's not that they are, it's that they could.

    EULAs that dictate terms of use of software (as opposed to EULAs that only address distribution), and companies that support those kind of EULAs, and a very dangerous thing.

    That is Stallman's point.

    --
    I've had enough abrasive sigs. Kittens are cute and fuzzy.
  22. While you're all busy insulting RMS... by dh003i · · Score: 3, Insightful

    While you're all busy insulting RMS, think about this...

    Have you contributed more to the Free Software community in terms of software than RMS?

    Have you contributed more to the spirit & philosophy of the OSS & FS software communities than RMS?

    Are you smarter than RMS? Ok, this one here's subjective; but I doubt most of the people criticizing RMS have an IQ of 170.

    Until you can answer affirmative to all of the following questions, I'd suggest you be more respectful to one of the founding fathers of our community.

    Without RMS and the FSF, there would be no GNU/Linux...Linux-based OS' would be some obscurity with little or no useful tools on them.

    1. Re:While you're all busy insulting RMS... by s20451 · · Score: 3

      IQ is like penis length, it doesn't matter how big it is, it matters how you use it. As if IQ is a measure of a productive human being.

      If Stallman was really smart, he would try using some diplomacy to convince people rather than alienating everyone and causing a flame war to erupt every time he opens his mouth.

      And for the record, my own IQ is well short of 170. But I seem to get along just fine.

      --
      Toronto-area transit rider? Rate your ride.
  23. What did you expect? by molog · · Score: 4, Insightful
    This is RMS. We have known all along how much he hates proprietary software. He has always been consistent with that. Of course he's going to be mad, this is Linux, the so called flag ship of Free software, using a proprietary product in its development.


    It just comes down to this. The current kernel developers don't have the same views that he has and they are angry that he expressed his views on their mailing list.


    We might get annoyed at the likes of RMS but we need people like him around. And as far as those people who would want to criticize RMS for not putting out code to have a better source control then CVS, remember that the man has written quite a lot of software in his time.


    Molog

    --
    So Linus, what are we going to do tonight?
    The same thing we do every night Tux. Try to take over the world!
  24. Stallman in the wrong by derch · · Score: 5, Interesting

    Normally I don't mind RMS spouting off about something when he has a decent leg to stand on or is using his own forum. In this case, he really doesn't.

    First, he didn't seem to choose the right forum to speak in. A listserv for kernel development is not the correct space to bring political speach into. RMS's post was very possibly off topic to the list.

    Second Linux is not his project, and he is not managing it. Torvalds has expressed his opinions on the Free Software movement. He doesn't believe in Free Software as an all important political idea, thus he has not don anything wrong by using Bitkeeper. Torvalds chose Bitkeeper, and that's what the project uses. Period.

    RMS should attempt to open a serious technical discussion directly with Torvalds. RMS should say "What do you need?" and then deliver it. Or RMS should violate the license in a clearly absurd manner and let Bitkeeper take him to court to test the validity of the license.

    1. Re:Stallman in the wrong by eloki · · Score: 4, Insightful

      Second Linux is not his project, and he is not managing it. Torvalds has expressed his opinions on the Free Software movement. He doesn't believe in Free Software as an all important political idea, thus he has not don anything wrong by using Bitkeeper. Torvalds chose Bitkeeper, and that's what the project uses. Period.

      But how is this relevant? For example, Windows isn't our product, and neither was Blender, nor Qt, nor many other things. Yet people seem to be quite happy to have opinions on the development and licensing of those pieces of software. Why can't RMS have an opinion on the development software used by the kernel? I can disagree with Linus any time I like if I think he's wrong, and RMS damn well can too.

      All these people saying 'write something better' are also somewhat missing the point if you ask me. Of course that would be a solution to the problem, but it just means that those people aren't as strong about the free(dom) software ideal as RMS is. They would prefer to use a free tool, but are willing to use BitKeeper - RMS would never do that, and that's the key difference.

      People saying 'write me something better' are basically taking the lazy way out; 'if you write me something better, then I can feel better about my decision as being the best on both a technical and ethical level'. Yet what good are ethics and morals if you always want somebody else to make them easy for you? The whole point of morals is about making the right choices, not the easiest or most convenient ones.

    2. Re:Stallman in the wrong by Chris+Johnson · · Score: 3, Insightful
      You're quite correct- it's just that, if everyone thinks on strictly technical and practical concerns, RMS is hosed. The whole concept of Free software, as in software that's beholden to no authority but the rules of its own license, is not a technical concern. You could make an argument that it produces the most effective collective structure for development, but that's more of a research paper- it's not a simple technical point.

      If you're going to refuse to deal on anything other than a technical or pragmatic level, then you should expect trouble from RMS, and you should expect to get some flak you don't understand and don't consider appropriate. What RMS observes that you don't is, operating purely from a technical/pragmatic level TENDS TOWARD non-optimal proprietary software.

      It's pure game theory. Unless you jump outside the system of tech/pragmatic, you can't understand the manner in which you lose. Self-interested rationalism, even among coders, leads to game-theoretical problems like refusal to cooperate (what's in it for me?) and a variety of failures to efficiently produce a commons.

      I'm afraid you can't stick to just pragmatic concerns. No, let me correct that- you can, but you can't expect everyone else to, because some people out there know better- and pragmatically, you don't have the power to control them or shut them up.

  25. Blender anyone? by PaddyM · · Score: 3, Interesting

    There's a solution. Buy out BitKeeper and GPL it.

  26. There is no equivalence relationship by argoff · · Score: 4, Insightful

    The problem is that all to often people come off with the attitude that free software is all the same as licensed software, it's just a matter of your choice. Many people don't seem to understand that many people who advocate free software consider this like a slap in the face.

    You might want to recall 150 yrs ago when some were saying "if you don't like slavery - don't own slaves, otherwise mind your own business. it's all up to whoever chooses" , there problem was that there was no equivalency relationship back then and there is none now.

    Copyrights are abusing peoples right to copy, and free software is a response to that. Mixing, matching, and choosing is not the answer, because people are using copyrights to controll me even if I don't wish to exercise them myself. It is very harmfull to try and promote some type of equivalency relationship, and IMHO this is a great example of why.

    1. Re:There is no equivalence relationship by PhxBlue · · Score: 4, Interesting

      I understand why it's a slap in the face, too; but comparing software licensing to slavery is a bit overboard. Software is not sentient by any stretch of the imagination. Further, no one is restricting your rights toward software development - only your rights toward the use of their system.

      A far better analogy is to compare a software licensing agreement to a lease--some landlords are perfectly respectable, while others are more than a little shifty. In any event, as long as you live on their property, you abide by the terms of the lease.

      Unfortunately, software manufacturers don't require notice before changing the terms of their licensing agreements. I think they should - and I think that people who purchased software licenses have a right not to have the license changed on them arbitrarily. That sort of fly-by-night treatment is my principal objection to BitKeeper's practices: it's unethical. And unethical behavior is not limited in practice to companies which distribute proprietary software.

      Their treatment of their own customers deserves a response - and the best response is to cease doing business with them. That couldn't work with slavery, which was far too widespread. . . but when you're dealing with a single corporation, a little bit of financial pressure goes a long way.

      --
      !#@%*)anks for hanging up the phone, dear.
    2. Re:There is no equivalence relationship by Guppy06 · · Score: 3, Informative

      "Many people don't seem to understand that many people who advocate free software consider this like a slap in the face."

      Their problem, not mine. Deal with it.

      "You might want to recall 150 yrs ago when some were saying "if you don't like slavery - don't own slaves, otherwise mind your own business. it's all up to whoever chooses" , there problem was that there was no equivalency relationship back then and there is none now."

      OK, you just took "information wants to be free" to an undefensable extreme.

      First off, until software starts contemplating "cognito ergo sum," it's just a bunch of 1's and 0's to me. Comparing it to slavery is not a proper metaphor.

      Secondly, if you're trying to call those of us who choose to use "enslaved software" the slaves, guess what: I can wipe Windows off my hard drive and give Mandrake more room whenever I damned well please. My decision not to is not an invitation for you and your ilk to "liberate" me against my will.

      At any rate, IMO the Confederacy was saying the right things in the wrong way for the wrong reasons. And, ultimately, you're not attacking the "Let me keep my slaves!" part of the argument as much as the "Leave me alone!" part.

      "Copyrights are abusing peoples right to copy,"

      As practiced in the United States today? Yes. As a concept? No. As a concept it is the fair exchange of rights between the producer and the consumer. It gives the producer compensation for their work wile ultimately giving the consumer new public domain works.

      "Mixing, matching, and choosing is not the answer, because people are using copyrights to controll me even if I don't wish to exercise them myself."

      WTF?! How is my decision to use non-GPL software infringe on your right to use GPL software? Should I also be prevented from writing this post lest I hurt your feelings?

      "It is very harmfull to try and promote some type of equivalency relationship, and IMHO this is a great example of why."

      The more vehemently you GPL sheep denounce the evils of EULA software the more you end up sounding like Steve Ballmer. Or do you enjoy becoming that which you claim you hate?

      And how can you argue against equivalency? The BitKeeper license is over-broad in preventing you from using it to work on a competing product (you have to pay money to get out of that requirement). The GPL is over-broad in preventing you from using GPL software on a competing product (you have to agree to GPL your own code to get out of that requirement). Both of them serve to restrict the public domain by applying terms not only to their own works but to derivative works as well. Not even plain ol' vanilla copyrights do that ("Sorry Wierd Al, you can't release that parody unless you agree to publish through Sony.")

      Want to write free software? Waive your Title 17 rights. You use what software you want, I'll use mine.

  27. The Emporer's New Clothes by derch · · Score: 5, Insightful

    A man's accomplishments do not put him above critique, questioning, or insult.

  28. Re:Software communism by GigsVT · · Score: 4, Insightful

    Look, it is as simple as this: you don't like the copy protection, patent protection, whatever you have every choice NOT to buy or watch or listen to a product

    All Stallman is doing in this case is showing people the consequences of choosing to use this product.

    No one (no reasonable person at least) is expecting or asking McVoy to open source his product. Sure, it would be a good way to end this mess, but it's more reasonable to just stop using his closed product.

    No one ever said you couldn't use closed source software, we just want to make sure that people understand the inherent risk in any closed solution with bad EULAs.

    --
    I've had enough abrasive sigs. Kittens are cute and fuzzy.
  29. Re:Obligatory GNU comment by fault0 · · Score: 4, Insightful

    Perhaps RMS should call much of GNU software, BSD/GNU software, since much software in the GNU project are derived from works in various BSD releases. Linux distros would be called "BSD/GNU/Linux based".

    Or maybe RMS just needs to STFU. I think the general concensious in the free software community is that the whole GNU/Linux argument is really quite silly.

  30. RMS, and budding democracies by A+nonymous+Coward · · Score: 4, Insightful

    I support RMS in many ways, he's the driving force which got us most of the free software we use today, indirectly or directly. But he fails to understand that freedom doesn't come all at once.

    Think of trying to implement democracy in Iraq after Saddam's fall, or even better, in some far more impoverished nation with much less technology. You can't just put up voting booths and say you have a democracy. Democracy requires an informed citizenry, it requires literacy, it requires a stable social climate, it requires reasonable expectations of the citizens that their vote might matter, and it requires them to have their immediate concerns taken care of, like stable income and work, safe from government persecution, safe from crime.

    Same with free software. I think BitKeeper's license sucks in many ways, but perfection is the enemy of good enough, and right now, BitKeeper's license is good enough for the kernel folks, so RMS should just butt out, work on an alternative if he wants, but butt out of something that is none of his business.

  31. Re:Question on RMS by Chris+Johnson · · Score: 5, Insightful
    Fine- you do that. In ten years- hell, in three years- your 'open' source movement will be indistinguishable from proprietary software.

    Isn't it true that for any proprietary software you could presumably get code if you satisfied the owners, paid them enough or whatever? It sounds very much like you see the point as being able to get code, but completely don't 'get' the idea of taking authority out of the original developer's hands.

    'Open' source and proprietary source can both be transmitted to different coders given that you satisfy the owner, get their okay. Maybe sometimes they'll agree. Maybe they won't. Maybe they're dead, or out of town, simply unavailable.

    Free code, you don't have to satisfy the owner- you have to qualify to BE an owner, at which point you get all privileges of ownership to the extent that the license permits. You're not dealing with a PERSON, you're dealing with a set of legal rules. It's set up in the only way it can be so that if you see code you can HAVE it. It defines a commons that is to some extent self-protecting.

    The reason it's that way and not simple public domain is, a certain person saw years ago that the public domain naturally tended towards the proprietary. Stagnation, walling off IP. That person saw fit to arrange for something else to be available.

    That's the person you want to get rid of.

    That's why I say- go RIGHT ahead. I already know what will happen. You wouldn't be reacting the way you are, if you didn't have some underlying assumptions about how coders should have say over what happens to their code- the idea that people should make their own 'open' licenses, should get to determine their own rules for their openness.

    This is no different from very permissive proprietary licenses. The thing about the GNU sphere that is different is that it is set up to balk any effort to impose authority, up to and including RMS's. If he did a new version of the GPL in which he got to come into your house and eat your Fritos and microwave all your nonfree software CDs, GNU would promptly fork and nobody would adopt his new license at all.

    Because the GNU/GPL sphere goes against the grain in balking authority from outside itself, it isn't the instinctive choice of anybody- it's giving up your power to something bigger than you. Not a person or authority, but a concept- but it's still giving up your power, to use the GPL. You have legal rights that you intentionally let go of when you use GPL, because legally you are allowed to be proprietary and take ownership of your code.

    RMS may or may not have known that what he was creating in Free code would be collectively successful- in fact it's led to huge things, much grander than cooperation among non-Free independent developers (given that Linux is grander than POV-Ray ;) ). However, since it is collectively successful as a result of individual coders giving up some of their power to support the common interest, it makes sense to be interested in the reasons for this.

    And it makes sense for RMS to be tireless, unbending, even maddening in his demands that people respect and understand this collective.

    You only see him, the figurehead, loudly heading up this thing, and because you don't know better you see him as being in control. You see this guy as the leader, the one in charge.

    The difference is, what he's leading, he has no real control over whatsoever- and he likes it that way. He can parade his ego all he wants and it won't do any harm because he HAS no authority over what he's supposedly leading.

    Shouldn't you be reconsidering your hostility to the guy in light of the fact that he's not the boss of you, not the boss of Linux, not the boss of GNU, and not the boss of the GPL? You gotta make some allowances for the visionary type. Name one more socially acceptable person who's innovated something like the GPL universe, while not leaving a loophole for himself to direct and control it.

  32. Let's learn from history, shall we? by shoemakc · · Score: 5, Insightful

    It's amazing that the same people who put themselves in a bad position with their pictures and music would again willingly do so with their kernels.

    Bitkeeper could easily change their license with after an acceptable amount of market share, just as GIF, JPEG and MP3 did before them. RMS, as usual, is dead on target here.

    -Chris

    --
    --an unbreakable toy is useful for breaking other toys--
  33. In related news... by shoemakc · · Score: 4, Funny

    ...Redhat announced today that starting with Redhat 8.1, all further releases would be compiled entirely in Visual C++.

    Safedisc licensing agreements are also pending.

    -Chris

    --
    --an unbreakable toy is useful for breaking other toys--
  34. Re:RMS might need to consider some prozac. by nick+this · · Score: 4, Insightful

    Yeah, but that's his job. He's the voice of conscience. Kind of like the ACLU.

    Without someone to constantly point out the difference between "almost free" or "free-like" and "truly free" we might get lazy and do what's convenient, rather than what is morally right.

    And no matter how you feel about him: if you hate him, agree with him, consider him a whiner... whatever... you *have* to respect someone who has such an unwavering set of principles that he is not afraid or ashamed to look like an idiot to stand up for them. No matter what, you have to admire him for that.

    So despite the fact that he spins me up occasionally, I shut up and listen to what he has to say because when you come right down to it... he's right. Annoying. Irritating. But right.

    Oh. And you have to respect him for emacs, too. Obviously.

  35. About RMS & BitKeeper by Ektanoor · · Score: 5, Insightful

    Well I don't like RMS due to many reasons, mainly that he follows his ideas like a religious fanatic altogether with some very faint ideals on how the world should be. It reminds me those hippy, extreme left revolutionaries that raised Che to the level of a saint, considered Mao's sentences the Bible and USSR a traitor to communist ideals... Meanwhile there are many things on RMS that deserve some high respect. Here is one of them, because, RMS is absolutely right...

    I may understand the reasons kernel developers point to hold up to BitKeeper. However they can't and shouldn't ignore the consequences of ignoring the legalities of their move. The fact that BitKeeper is factually an EULA much worse than M$ is something that may put into question the future of Linux. Yes, it is much worse because ethically violates some principals of market, things that were formed not yesterday but millenia ago. It is much worse because it is clearly not a commercial license but a typical feudal decree of the worst kind, in common terms: "you can't do that or do this while you are under my service". This is what is inside this license and it is so superficial that any deviation may turn it void. For some you may have had the chance to read documents from the V up to IX centuries, one may note that feudalism started this way. First they said "while", then they said "because" and later they didn't say nothing as everyone considered it natural...

    And to consider things worse:
    Larry McVoy of BitKeeper:

    "Our position:
    "1) No free licenses for our competition, they can buy them if they like.
    "2) The software is not open source because the open source business model doesn't have a prayer of supporting the development costs.
    "3) If you had built a decent system instead of sitting around and whining, we could be doing something else instead of sitting around listening to your whining."

    If we look at the reaction of BitKeeper's owner, we can see that we are really going the worst way. He is ultimative, he is arrogant, for him OSS lacks prayers. But this is not the worst. The worst is that we are a mass of apatic whinners, but he stands higher and listens to the crowd of gentiles. And he only can listen whinning, nothing else, because the brilliance and crystal sound of BitKeeper's castle blinds and deafens everything else.

    This is not OSS, this is not Free Software. This is not even the M$ Empire. This is the Black Cathedral.

  36. Pulling a Qt by kris · · Score: 5, Insightful

    Normally I do not agree with RMS at all. In this particular case, though, he is flat out right.

    BK is infrastructure for the kernel development. This is not something that you happen to rip out and replace on a moments notice in case the license changes to something unacceptable. changing infrastructure is a painful process in which more often than not valueable metadata is lost and in which you have to change processes and retrain people.

    In fact, this is precisely the reason while Linus is still using BK despite the controversial license: Convenience vs. da pain of changing.

    Now, consider the license change BK put through, and what it mandates: It basically says that you cannot use the free license for Bitkeeper to use Bitkeeper for anything including Kernel development if you or your company happen to work on a version control system.

    Can Bitkeeper legitimately impose such license restrictions? Yes, they can - it is their product and they can do whatever they fucking want with it.

    Is such a license acceptable for Linux kernel development? Not at all. Despite the fact that there are Bitkeeper-to-CVS and Bitkeeper-to-Subversion and Bitkeeper-to-tgz-Gateways all over the place now, Non-BK users are second class citizens in Linux kernel development. They do not have realtime access, and they do not have proper access to BK metadata at all. Also, patch submissions that do not come in via BK are treated worse than patches that come in via BK - Linus and friends may say they aren't, or they aren't intentionally, but they are - again matters of convenience and infrastructure working against Non-BK users.

    Switching from BK to a different systems becomes harder the longer you use them, because the systems accumulates metadata and processes center around BK - the infrastructure mechanics I explained above at work.

    Finally, is this situation sane at all? That is, is there at least one party that wins because of this license change?

    Well, the people who cannot use the free BK license are certainly not winning. They are shut out and have to use second-class systems to contribute to the kernel. Their enthusiasm and energy that could be used for Linux kernel development is diverted to integrating into a principally broken infrastructure.

    The Linux kernel development process certainly is not winning at all. There is war and blodshed on the list, and people are switching or turning their back on kernel development out of principle, others defend Bitkeeper out of purely technical reasons, shutting out all the process problems and political outrage BK creates.

    Bitkeeper, the company, certainly isn't winning, too. They created this license in order to discourage the development of BK alternatives. Well, that backfired big time. I couldn't have devised a better Subversion promotion campaign than this particular license change.

    Basically, BK has pulled a Qt. That is, they created a great product that is important infrastructure for other projects, with a license that is unacceptable for many people. This is just what Qt was in the beginning of the KDE project: a truly great product in an pivotal infrastructure role for an important project (the Linux Desktop). And just like the license to Qt forced many people to create an alternative to Qt, spawning the Gnome desktop, the BK license change will be a great incentive for many to work on Subversion, Arc and related projects.

    So BK actually achived the opposite of what they intended with the license change.

    Is there any other party that might be winning? Well, yes. Microsoft. But you already knew that. And hey, they even have a version control system.

    1. Re:Pulling a Qt by himi · · Score: 3, Informative
      Is such a license acceptable for Linux kernel development? Not at all. Despite the fact that there are Bitkeeper-to-CVS and Bitkeeper-to-Subversion and Bitkeeper-to-tgz-Gateways all over the place now, Non-BK users are second class citizens in Linux kernel development. They do not have realtime access, and they do not have proper access to BK metadata at all. Also, patch submissions that do not come in via BK are treated worse than patches that come in via BK - Linus and friends may say they aren't, or they aren't intentionally, but they are - again matters of convenience and infrastructure working against Non-BK users.


      I'm sorry, but this is just plain wrong - Linus will accept patches with as much alacrity as he'll accept URLs for a repository to pull from. As evidence of this, consider the number of patches he's merged from Andrew Morton and Al Viro, neither of whom use BitKeeper. Hell, Linus basically demanded excellent support for importing patches into a repository from Larry McVoy, and got it without the slightest argument.

      All told, Linus using BitKeeper has noticeably sped up and smoothed out the development process - he's now merging more patches (particularly trivial patches that often got lost in the noise before), and thanks to his use of BitKeeper you can literally watch every single commit he makes, so you get a far better view of what he's doing. The development process has been helped by this, not suffered, and that's the consensus of all the core people (including ones like akpm who doesn't use bk for philosophical reasons).

      Go and actually /read/ lkml for a few months, and then come back and tell us all that things are terrible and the development process is collapsing.

      himi
      --

      My very own DeCSS mirror.
  37. Looking the wrong directions by Paul+Komarek · · Score: 5, Insightful

    RMS doesn't give a damn about convenience, especially for his own sake. He cares about ideals, and challenges everyone else to do the same. Most of his life has been spent trying to make living with his ideals more convenient. Most of us losers spend our lives rationlizing about our ideals until our ideals are convenient. I hope this explains where RMS is coming from and why he says the stuff he does.

    Linus Torvalds is more like the majority of people whose ideals meld (by design or otherwise, I don't want to guess) with convenience. This is probably part of why he is fairly popular and seen as a regular guy (unlike RMS). For instance, Torvalds feels the "best" tool for the job should be used regardless. Unfortunately, Torvalds has never taken the time to describe for us exactly what "best" means. I'm sure he doesn't mean anything so sinister as "if unpaid child labor makes the tool cheaper, then it's better!", or so naive as "I'll pay anything for the best, screw value/dollar!".

    RMS doesn't give a damn about Larry McVoy's company succeeding with propietary software. I believe (I don't want to put words in RMS' mouth) this is because RMS feel propietary software is worthless in the long run, and hence a waste of society's time, energy, and money. I believe he could win this argument, should he choose to make it. Torvald's feelings on the subject are useless until he defines what he means by "best".

    My second personal interjection for this post is about competition versus scratching itches. It's not clear to me that the "competition" from BitKeeper is what will spur the creation of a Free package with similar features -- Torvalds doesn't seem motiviated by competition with Microsoft (he's said such several times), so it's not obvious to me that software authors will be motivated to compete with BitKeeper for the sake of competition alone.

    The people in the Free and Open Source communities most affected by the lack of Free BitKeeper alternatives are the Linux (i.e. kernel) developers. Most others seem to be happy enough with existing tools, with just enough disgruntelment that subversion is finally emerging. Thus BitKeeper is providing non-Free itch-relief for the only people in the communities who are have this particular itch. Rik and Linus are dreaming if they think I care about their itches more than I care about mine. Essentially, the only people who are likely to produce BitKeeper alternatives are those kernel developers who refuse to use BitKeeper because of their ideals (if they don't use BitKeeper because they don't like source control, or because they're lazy, then they're unlikely to write a replacement).

    That is, only people with strong ideals about Free software are likely to write a replacment for BitKeeper. That means people more like RMS and less like Linus.

    -Paul Komarek

  38. it looks like a Linux problem to me by g4dget · · Score: 4, Interesting
    Nobody has really tried so far- even RMS is too stubborn to ask "Well, what is it that bitkeeper does

    There are plenty of open source systems for version control and configuration management. Furthermore, they way open source works, if you need an unusual tool for your project, you create it yourself and share it.

    It's funny how much people will bitch when they're not the ones that have to deal with the inadequacies of $OSS_SM_TOOL when it comes to kernel development.

    There are plenty of huge open source projects, and they work fine with CVS. GNU Hurd is being developed with CVS. BSD is. To me, the real question is: what is going wrong with Linux kernel development that CVS is not sufficient?

    1. Re:it looks like a Linux problem to me by eyez · · Score: 4, Informative

      There are plenty of huge open source projects, and they work fine with CVS. GNU Hurd is being developed with CVS. BSD is. To me, the real question is: what is going wrong with Linux kernel development that CVS is not sufficient?

      Neither have the magnitude of Developers or incoming patches that the Linux kernel has- *BSD have very small development teams. HURD's developer team is slightly larger, but still nowhere as large.

      Here's an archive of the recently-set-up bk-commits-head mailing list, which shows patchsets sent through the bk 2.5 development tree alone.

      --
      get 0wned. irc.w30wnzj00.com
    2. Re:it looks like a Linux problem to me by autrijus · · Score: 5, Insightful
      If I recalled correctly, the FreeBSD development tree makes heavy use of an internal Perforce depot, which keeps in close mirror with the public CVS tree, as seen in this status repport:

      The release engineering activities for 4.6.1 are taking place on the RELENG_4_6 branch in CVS, while the work on 5.0 DP2 is taking place in Perforce so as not to disturb ongoing -CURRENT development.

      Also, the current Perl 5 development also takes place on a Perforce repository, with public-accessible rsync mirrors available.

      What is going wrong with Linux kernel development that CVS is not sufficient?

      CVS is painful to use for many common tasks required for large-sized software projects -- its shortcoming on atomic commits, directory versioning, copy-on-write branches, etc. are widely acknowledged.

      It is a good thing that, for a relatively small software sector where the neccessary designs are hardly well-understood, proprietary version control systems could use its customer's funding to experiment with advanced features. As long as nobody gets a monopoly on those ideas (read: software patents), they create a pool of ideas that related free software projects can learn from it -- it is really more like a symbiosis, not antagonism.

      It is all a very healthy process of ideas in the 'niche' market, first commissioned by paying customers, then trickle down to the low-end market (think iMovie), which makes enough people to appreciate and understand how it should work like, and finally appears as a full-fledged free software -- and everybody can just move forward and play with new things, proprietary or not.

      The remark on lkml that the new BKL is 'pulling a Qt' is probably right on the mark, though: The new Perl pumpking (Hugo) wishes to migrate Perforce to Subversion, and help building the missing pieces that people needs. No doubt that many people are doing the same thing right now, myself included.

      /Autrijus/

    3. Re:it looks like a Linux problem to me by g4dget · · Score: 3, Insightful
      Neither have the magnitude of Developers or incoming patches that the Linux kernel has

      Yes, and that's perhaps at the root of the problem: the Linux kernel is a huge, monolithic project. If it were broken up into smaller, independent subprojects, for example, then each subproject would have fewer developers and fewer patches coming in.

    4. Re:it looks like a Linux problem to me by nusuth · · Score: 3, Funny
      There are plenty of huge open source projects, and they work fine with CVS. GNU Hurd is being developed with CVS.

      Which part did you mistype?

      --

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

    5. Re:it looks like a Linux problem to me by gmack · · Score: 4, Informative

      How can you even argue this?

      Given that the Linux kernel is much newer than the Hurd yet has matured faster don't you think Linus got something RIGHT in his development process?

      The Linux tree is actually very organised but that doesn't solve all of the problems.

      Hmm lets take a recent scenario: Combine an interface change with the maintainer adding functionality while a kernel janitor cleanes up random portions of code? In each case the code changes are only on a single driver yet you have 3 people making changes.

    6. Re:it looks like a Linux problem to me by scrytch · · Score: 5, Informative

      > GNU Hurd is being developed with CVS.

      It's being developed?

      > BSD is.

      They gave up on the client end and created cvsup for distribution instead (which was meant to replace sup, but turns out to beat cvs in terms of reliability). Many private branches use Perforce

      > To me, the real question is: what is going wrong with Linux kernel development that CVS is not sufficient?

      Why don't you ask Linus? He's tired of answering, but now and then, he will give you a *big* rant on what he hates about CVS. Let's start with the fact that you can't even rename a file in CVS without losing its history. Or the fact that you can't make one changeset (in CVS terms, a tag) depend on another. Or that you can't even back out individual changesets -- history in CVS is entirely linear when going backward. The reason this worked for Linux before was because Linus did it all by hand, and now he's tired of it.

      But seriously, don't take it from me, ask Linus.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  39. You obviously don't know Larry McVoy... by tlambert · · Score: 5, Interesting

    You obviously don't know Larry McVoy.

    I first met Larry McVoy on usenet. He was highly cogent in his arguments, and generally a very intelligent guy. Unlike a lot of the idiots who came in after the NSF quit running the Internet, you could actually hold a technical discussion with him, after which you would have a solution, or an approach to a solution, for the problem at hand.

    I've talked with him on the telephone on several occasions, when issues have come up that merited a telephone conversation; I've called him, and he's called me, though it has been a while since our last voice conversation.

    When Larry McVoy left Sun, he wanted to take the SunOS 4.1.3_U1 code (U2 has not yet come out), and release it under the GPL. This was quite visionary, given the amount of competition that Linux is now giving Sun, even internally, within their own engineering staff, these days. Sun would not do the release, because it would cannibalize their SVR4-derived "Solaris" market.

    Larry's motivations in this case were, I think, base... in that he wanted to "rescue" the important work which had been done on the BSD dervice Solaris (SunOS) code base. He saw the GPL as a way to do that.

    Larry was an early GPL advocate, in this sense. Frankly, I'm glad he failed in this endeavor; it wporbably would have meant the end of BSD derived OSs, which generally exist only because the GPL is too draconian for people who need to do business.

    Larry became an outspoken Linux advocate; he authored the "lmbench" suite of micro-benchmarks, all of which show Linux in a good light, compared to its competition. One can argue that these tools drove a number of the important design decisions in the Linux kernel itself, which, among other things, led to the current threading model and code, which *depends* upon the fact that process context switch overhead is minimal, and there is very little difference between it and thread context switch overhead.

    Larry advocated Open Source software, in general: BitKeeper, by it's nature, *from the beginning*, offered free licenses those people who woul publish their source archive, as the cost of the license.

    Thus, by its nature, BitKeeper encourages free software by providing economic incentive.

    But, like the GPL itself, it is an instrumentality, and the instrumentality must not obey the same rules as that on which it acts.

    The GPL carries a prohibition against modification: it is not itself under the GPL. Ask yourself "Why?".

    For this same reason, good or bad, BitKeeper can not itself be Open Source software. Yes, there are economic issues. Despite people's intentional misinterpretation of the word "support" in Larry's statements to mean "technical support" rather than "economic support", Larry's correct: the Open Source model is not economically self supporting for stategic projects... it only supports itself for tactical projects.

    That RMS is complaining about BitKeeper now is, I think, sour grapes. That's the kind interpretation. The unkind interpreation is that BitKeeper is a more effective mechanism than the GPL itself for achiving the goals of the GNU Manifesto, of which the GPL is an instrumentality.

    So before you call Larry an idiot, or blindly GPL or even BSDL your next set of source code, understand the long term consequences of the license.

    Frankly, I'm glad he's let go of the understandable bitterness that comes from pouring your soul into a product, only to have it hidden away in a vault by an employer with goals other than advancement of the art and science of computer science.

    I think this license demonstrates that he's come to his senses, on strategic issues -- a painful lesson. Would that RMS would so the same.

    Thanks,
    -- Terry

    1. Re:You obviously don't know Larry McVoy... by Chris+Johnson · · Score: 4, Insightful
      Whoa. Very interesting and insightful background there, thank you muchly for all the information.

      However, how can you possibly say dependence on proprietary software is more effective at achieving GNU goals than the GPL is?

      Methinks you are radically misunderstanding something about whose goals for what and why. If you'd said 'it was more effective at achieving Linus's goals for Linux than the GPL', that would be very debatable and hard to prove, but it wouldn't be an insane statement. You need to rephrase, because in no sense would reliance on BitKeeper further any GNU or FSF goals.

      What you have here is a situation where BitKeeper might be effective at furthering 'Open Source' goals, but completely bitchslaps 'Free Software' goals. Schism. This is where you can split the diamond with only a very light tap.

      I think it is interesting that this has come up: it is a wonderful opportunity for Microsoft or some interested party to do some damage, or just lay plans. If you split the community into Open Source vs Free Software camps (ESR vs RMS?), the results are interesting. The Open Source camp would be considerably larger, have bigger projects, but it would be vulnerable to catastrophic failure- you could destroy it. The Free camp would be smaller and have fewer ties to big companies and 'name' projects, but it is the one that cannot be 'taken out' by hostile action.

      It's a bit like Napster vs. Gnutella. Napster was much, much bigger- but it was possible to destroy, and it was destroyed. Gnutella and similar designs are just not as efficient, but you can't get rid of them...

      This is much the same. In the end, RMS will be the last man standing. However, if you stand with him, people are gonna pass you by, pursuing grand plans that have fatal flaws, undertaking huge projects and suffering great defeats. To side with RMS you have to be thinking longterm. Few seem to.

  40. Idealism by Stalyn · · Score: 3, Interesting

    I agree with you on the most part however I find it that idealism doesn't really accomplish anything other then logically consistency. Which really doesn't mean anything either since you can construct a logical consistent argument for anything. No, its the pragmatic people who are to able to bend and find solutions to problems. Bitkeeper is only an idealogical problem at this time if it becomes a problem that deters effciency then it becomes one of pragamatism.

    RMS can rant and rave about how BitKeeper is idealogically inconsistent, but who cares? Also its not like BitKeeper owns the linux kernel it's just a tool. If the licensing truly becomes a nuisance then just use another tool.

    --
    The best education consists in immunizing people against systematic attempts at education. - Paul Feyerabend
  41. Yes... by RedBear · · Score: 3, Interesting

    ...they can. Anyone can. If they purchase a commercial license for BitKeeper. Then the product belongs to you, fully and completely, and you can do anything you want with it, short of copying and redistributing it, since it will still be a copyrighted work.

    I think this is the point everyone seems to be missing. Larry McVoy sells BitKeeper commercially to pay for its development, and possibly to even make a little profit (the philistine!). He doesn't feel like letting people use his product FOR FREE to develop a competing product. But he isn't attempting to dictate what you will do with the product after you buy it.

    This is a long way from the kind of insane grabastics we've seen from Microsoft et al, where they ignore the 1st Amendment and try to tell you that you can't talk about their products without their permission (Frontpage, anyone? SQL Server?), and that's with products that you've paid good money for the privilege of owning. (How is that even legal? I never did figure that one out.)

    IMNSFHO, Mr. McVoy has a quite reasonable license attached to his commercial product, which he has graciously allowed the Open Source community to use for free. Maybe even because he wants to (wait for it) support Open Source! (DOH! Really?) If you actually take a look at what kind of guy he is, as obviously Linus has, I don't think anyone here (except the true zealots) would think for a moment that Mr. McVoy would try to stick such draconian requirements into the commercial version of the license. All he's saying is, "If you want to work on a replacement for BitKeeper using BitKeeper, at least pay for a license, so I can afford to keep BitKeeper going until you're done developing the replacement." So, to reiterate, every single developer using BitKeeper is free to develop a replacement for BitKeeper, just not with the FREE version. Using the free version of a commercial product is a privilege, not a right. If you want to have rights, buy the damn thing.

    I haven't read the article so I won't comment on that, but the people posting here have definitely gone off the deep end, dumping on Mr. McVoy like he's some kind of "Microsoft, Junior" in disguise, while giving no consideration to his character, the character of his company, the professional judgement of Linus Torvalds and company, and the immense benefit the Open Source community is currently receiving from this "evil capitalist bastard" who dared to attach a restriction to the FREE use of his COMMERCIAL product. Geesh.

    Disclaimer: None of this has much to do with whether Proprietary software licenses are good or bad. Obviously, they can be quite bad, since abusive companies can abuse them. But this license and these terms aren't unreasonable by any stretch of the imagination, and will probably never become so as long as Larry McVoy is at the helm. Whether such a proprietary license could ever be used in a bad way by a future owner of the company is another matter, as is the question of how far software licenses will hold up in a court of law, be they reasonable or unreasonable. Those are all separate questions.

    I send you this post to ask your advice. Have a nice day. All your opinions are belong to Microsoft.

  42. Actually, it would be a big issue by Per+Abrahamsen · · Score: 4, Insightful

    Imagine Bill Gates realising that his real cash cow is Microsoft Office, and that MS Windows is just the technology that keep MS Office ahead of the competitors, by having early access to new or secret API's. In that case, it might make perfect sense to license MS Windows gratis in order to keep off any competitors. And of course, not license it gratis to people who worked for companies who contributed to software that compete with Microsoft offereings.

    Suddenly, any company that used Linux/Samba/Apache on their servers, and occationally contributed a bug fix to either of these, would have to pay for all their MS Windows desktop licenses, which could be arbitrary high as most customers would not be affected.

    In other words, MS could make it arbitrarily expensive for companies to participate in the development of free software that competed with Micosoft products.

    The BitKeeper trap would be an excellent way for Bill Gates to kill of the competion from free software. We just have to hope he doesn't realise this, or that he have a higher sense of business ethics than Larry McVoy.

  43. Allready Forgotten ? by Diabolical · · Score: 5, Insightful

    Let's see.. a few years back Linus just used CVS. Developers began complaining about shortcomings since Linux became too big to be handled in plain CVS etc.

    Since CVS is a different beast then the Linux Kernel they did not try to develop something themselves. Besides, that would only distract them from kernel development. To make things worse the competitor, subversions, wasn't much usefull eather since it was still in development (and still is).

    So Linux chose BitKeeper. Not because he was pushed or otherwise but because it was, and still is, the best alternative offered then and now. Not because out of convenience but to keep the development going in a strong pace lest it become, like the HURD, a product which seems to be never finished.

    BitMover provided the software for free to kernel developers. The only real restriction is that you ae not allowed to use BitKeeper to create a competitive product. Why? Because that's the way BitMover earns it's money to pay it's employees and to fund development for BitKeeper.

    So, to be able to use a good product (BitKeeper) which in it's turn made it possible to create a good product (linuxkernel) Linus agreed on the terms that were layed out. If they should have to go back to CVS (which is technologically still possible although people claim otherwise) they would also have to go back to all the problems there were before they started using BitKeeper.

    And may eventually a better product come by which is OSS then i would have no doubt everyone would switch to using that.

    I can understand RMS's opinion. He sees the flagship of the FSF being "corrupted" by closed source software. This is of course a big blow to him. The FSF always tried to create the tools to do the job themselves. Apparently their jobs were not as big as the Linux kernel though. So their tools became inadequate. However, instead of arguing he could also try to understand the forces that work here. If he could start up a project aiming to replace BitKeeper i think alot of people would jump right in. But if he does not then please be a bit more polite against the people working on the Linux kernel.

    So far for this not entirely coherent post...

  44. The pile of bricks called RMS. by Qbertino · · Score: 4, Insightful

    Say what you want, but the man shure has one hell of an impact.
    He get's pissy on some issue (for valid reasons too), drops a word on it and all of a sudden even slashdot has some really intelligent controversial discussion going on.
    It is really all what someone like RMS could want and bargain for, and if I judge him right it's just what he intended.
    Presumtion:
    From what I gather the kernel group can use a little self reflection to. Because: If kernel dev is actually stalled by this BitKeeper vs. OSS Tool debate (I hope not so hefty) it is in a state where carrying on with buisness as usual would have driven Linux into a messy corner.
    I predict that, within a relatively short term, either Bitkeeper will see a chance for cool PR and modify their license to 'free for free Software products' or something or just now some people are firing up a VCS project that is to Emporer Linus' likeing and thus will be prefered :-).

    --
    We suffer more in our imagination than in reality. - Seneca
  45. Re:As I understand it... by nagora · · Score: 5, Interesting
    Of course there is the possibility that BitKeeper could take away someone's right arbitrarily to use the program. But it's not going to happen.

    It already did. If you are on a campus where anyone (not you - anyone) is working on patches to CVS you are not allowed to use Bitkeeper in the same way I am. What's not arbitary about that?

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  46. Insightful? Insightful? are you ppl nuts? by gregm · · Score: 3, Insightful

    The scenario wouldn't be Ford Donating anything to Chevy. The scenario would be like you signing a paper that says by driving this ford for free (the EULA doesn't apply to the purchased ver AFAIK) you agree to never use it to drive to work at a Chevy plant. Taken a bit further, you may not drive the car to work at a garage that works on anything but Chevy vehicles since everyone knows used car sales compete with new cars sales.

    Also you may never re-sell the car to anyone who would drive it to work at a Chevy plant.

    Or to go a little further down that road.... you can never use the Ford to get parts for the homebrew car you're building out in that garage that you plan to donate to Sally Struthers.

    You may not use that car to drive to work at the golf cart factory since golf carts could conceivebly compete with cars. Same with scooters, bikes motorcycles, planes, trains, helicopters... you get the idea. This sounds absurd but not nearly as crazy as some of the lawsuits we've heard about in the last few years.

    RMS posted his comments to the wrong list and should apologize to the list (but not on the list). But he's still right. Your comment missed the mark a bit, but is excusable, heat of the moment and all, the insightful moderation however was just nuts.

    Now it's the kernel hackers right to do what they will... it's Stallman's right to bitch about it, (but not on the dev list), it's your right to make a bad post and my right to try to get you to think about Stallman's message and life's work in your own terms and it's Slashdot's right to give us a place to have this discussion.

    It is also most certainly BitKeeper's right to make whatever EULA they like, however that right has nothing to do with anyone donating hamburgers or cars between companies.

    Imagine this... I write the ultimate BitKeeper replacement.. I take the linux kernel, some gnu stuff and create a distro entitled Byte Arranger. It's a totally gpl'd bootablle ISO. You stick it in your PC and voila you're arranging Bytes/keeping bits, so to speak. Does this mean that any of the kernel hackers that continue to use the free version of bitkeeper have now violated the EULA because their work has gone into a system that competes with bitkeeper?

    I agree a linux kernel has nothing todo with a userland app that keeps bits, but it'd be a good enough argument to drag a few developers to court.

    Once we come to accept this type of license because it's free, we are then another step closer to accepting even stronger versions of this type of license on stuff we pay for. Imagine the EULA of a Windows product first saying

    "By installing this software you must agree to never use this software to contribute to Linux."

    Version2 states "By installing this software you must agree to never contribute to gpl'ed software." Seems kinda the same at first glance but NOT the same.

    G

  47. RMS Says: by peterpi · · Score: 3, Funny
    "Sorry, this Module isn't active!"

    I think he sums it up pretty well with that comment.

  48. Brave GNU World by cicatrix1 · · Score: 5, Funny

    Did you mean, a "Brave GNU World"? I'm sorry Mr. Huxley, but it's just so appropriate.

    --

    I know more than you drink.
    1. Re:Brave GNU World by scrytch · · Score: 5, Informative

      > Did you mean, a "Brave GNU World"? I'm sorry Mr. Huxley, but it's just so appropriate.

      GNU's monthly e-zine is, in fact, named Brave GNU World

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  49. Re:And in other news.. by Ektanoor · · Score: 3, Insightful

    Ok, burning you to the stake...

    First load of lumber: GNU is not nazi and it is not merely a vocal minority. If you consider GNU just a minority you are simply wrong because more than 99% of Linux soft is made on GNU stuff. If you consider that there are some fanatics in GNU, nazis as you name, they are more leftists rather than nazis and it is an offense to name them like this. And they have a right to voice because they are the founders of all things GNU, no matter the rant. And it is good to hear some voice from the Founding Fathers, to help us remind that all this didn't come from nowhere and there are reasons for things being what they are.

    Second load of lumber: GNU/Linux is frankly a stupid name. But the ideology not. And the ideology states a very important thing - free software is a share of ideas among equals. Yes, we don't live in a perfect world but software is also not a perfect thing. Software is a mean term between Science, Technology and Human Thought. To develop, it needs to be shared. GNU tries to show one of the most optimal ways of sharing it. It is hard to be universally accepted, but is is the main engine that moves the whole machine Linux is now.

    Third load of lumber: Bitkeeper may do what kernel devlopers want. Cool be this way. So why they didn't start Linux on some Borland C or Visual C++? The GNU/GPL/OSS ideals are not only a problem of technicities but also of ideology. And these ideals mean freedom of use, development or choice. And that's why people fit things to open source and not the other way around. The other way around would be furninshing a bunch of owners a cheap working force.

    Well, were I put the matches?

  50. Re:Freedom to get value by Ektanoor · · Score: 4, Interesting

    This is not FUD and it is not panic. It's a problem and a serious one.

    The fact that RMS is frequently one-sided is a fact and I agree with partially with you on the case of single criteria. However you should note that a larger part of the people here is worried not about this but on the fact that someone is being more papist than the Pope. And it's not RMS but BitKeeper. These license policies may lead to the fact that, in one point of time, BK may hinder a lot the development of Linux. Note that Linux is not ONE product for ONE objective on ONE SINGLE environment. Inside of it, along with it and beyond it there are TONS of programs, applications, drivers and other stuff which depend on Linux and which Linux depends of. To understand how BK may hinder this, try to get a deeper look at their license.

    This is a license directly against best value. It is a binding that forces people into conditions where they may be unable to find that same best value. The license is even anti-commercial as it forbids people to sell third-products, that may have nothing to do with BK, except some similarity on functionality. No matter the qualities of BK, such term is enough to put it more dangerous than M$.

    If BK is sincere on being a good company, willing to receive a direct reward, they should choose three ways - turn the license into a genuine commercial license, make a license in terms near to BSD,or separate it into components with different licensings. Probably this would hinder kernel developers, but there is a problem on playing with half-agreements, not seeing dropped nets, accepting broad middle-terms and forgetting about consequences. In one way or the other this may one day turn into the bad corner. Much like M$ did since its advent, let's not forget that 10 years ago BG was Luke against the Empire. Frankly I would not like to see Torvalds being compared to Dart Vader...

  51. Larry's Comment by pez · · Score: 4, Insightful

    "If you had built a decent system instead of sitting around and whining, we could be doing something else instead of sitting around listening to your whining."

    Man, did that quote put me off. I wonder, for instance, what compiler Larry uses to build BitKeeper. Or what version of shell utils. Or what editor. Or what MTA. Or what DNS server.

    RMS and friends *did* build a decent system, which is exactly the reason that Larry is getting all of this publicity for BitKeeper. Think anyone would have heard of BitKeeper if Linus didn't endorse it? Think anyone would have heard of Linus if it weren't for RMS' "decent system"?

    -Pez

  52. Yeah right by Aapje · · Score: 4, Insightful

    What a load o' crap. Larry McVoy basically says three things:

    1. We very much like to give both the poor and the rich the option of using our software (without illegally using it), the only thing we disagree with is that our competitors use it for free. While it may be short-sighted, in no way is this worse than Perforce or any of the other commercial versioning tools which cannot be used by anyone for free.

    2. We don't believe that an open source product can financially be succesful in this market segment (that is what he actually said, not that all OSS is hopeless). You call this arrogant, but where o where is this money making open source versioning tool to disprove Larry? Besides, there is no reason to call someone arrogant for a honest opinion (unless you are part of the thought police).

    3. You have every right to create your own ultracool open source product, but don't claim that you have any right to use our work for free unless you follow our rules. If you want a versioning tool that doesn't have these restrictions, build your own instead of whining.

    I certainly don't think that Larry is against OSS or its proponents. What he is against, is people who blame him when he is ten times nicer to users than most other developers. Because no matter how you twist the argument, a commercial license is all your gonna get with almost every other commercial product. BitMover gives you another option, one which you may accept or not, but it can never take anything away from the basic proposition that you get with most commercial products: pay to use it. Besides, the commercial license they use is not a shinkwrap EULA, but a legitimate contract that you must sign. So all in all, BitMover doesn't seem to be any more evil than other commercial developers (probably much less actually). I agree that Larry could have used a bit more tact, but the same can be said for RMS. That's why they should both stick to coding IMHO ;)

    --

    The Drowned and the Saved - Primo Levi
  53. Mirror of the comments by Arkham · · Score: 5, Informative
    I can't believe no one found a mirror when the site got slashdotted. I spent a minute on Google and found this:


    http://www.uwsg.iu.edu/hypermail/linux/kernel/0210 .1/1767.html


    In case this get slashdotted, here is RMS' post (and I quote):



    The new restrictions on Bitkeeper, saying that people who contribute
    to CVS or Subversion and even companies that distribute them cannot
    even run Bitkeeper, have sparked outrage. While these specific
    restrictions are new, their spirit fits perfectly with the previous
    Bitkeeper license.

    The spirit of the Bitkeeper license is the spirit of the whip hand.
    It is the spirit that says, "You have no right to use Bitkeeper, only
    temporary privileges that we can revoke. Be grateful that we allow
    you to use Bitkeeper. Be grateful, and don't do anything we dislike,
    or we may revoke those privileges." It is the spirit of proprietary
    software. Every non-free license is designed to control the users
    more or less. Outrage at this spirit is the reason for the free
    software movement. (By contrast, the open source movement prefers to
    play down this same outrage.)

    If the latest outrage brings the spirit of the non-free Bitkeeper
    license into clear view, perhaps that will be enough to convince the
    developers of Linux to stop using Bitkeeper for Linux development.


    --
    - Vincit qui patitur.
  54. Some of us read before posting by msobkow · · Score: 3, Interesting

    I and many others do read articles before commenting. I happen to agree with many of Rick's philosophies, but not the way he has been presenting them over the past 4-5 years.

    His fame and founding-father status with GNU mean that he gets a lot of respect and press, even from those who disagree with his ideals. But when he ignores whether a forum is appropriate and storms on with his idealistic rants, he provides the anti-open-source community with a poster boy to paint the community as a bunch of fanatics.

    Some claim that his persistant ranting is a "challenge" for us all to follow our ideals and morals regardless of the consequences. While this is a terrific sentiment for those who wish to be seen as dedicated religious icons, it is hardly a suitable approach for those who don't live in their office as RMS does.

    But in a world where "reality" TV is so popular, I guess I shouldn't be surprised. Realism is the last thing the sound-bite hungry populace seems to want, and a few "sure win" discussions like this ensure that the page counts stay high enough to improve the eyeball stats for advertising.

    --
    I do not fail; I succeed at finding out what does not work.
  55. RMS and point of view by the+eric+conspiracy · · Score: 3

    While I certainly don't agree with RMS's point of view on everything by a long shot, I think it is valuable to have his opinions around for discussion. The FSF has been a seminal contributer to the Open Source movement, and many of use use their software on a daily basis.

    I also think that a lot of us find BitKeeper's anti-competitive free-beer license troubling, although nobody should be particularly shocked since there are other components in the BitKeeper license that are clearly not 'Open Source'. If for whatever reasons you feel that the use of Bitkeeper is inappropriate for your work, fine. I have severe doubts that the anticompetitive clauses are tolerable in a project like the Linux kernel since they might prevent some entities from making what might be a valuable contributuion to the project, or prevent somebody from working on another project in addition to the Linux kernel. That is a very dubious situtation for an open source project like the kernel to be in.

    I hope that the upshot of this will be rapid progress on an open alternative to BitKeeper - I expect that it will be. I've long felt that CVS is a rather crude system, and open source development, especially large projects like Mozilla and the Linux kernel deserve better. Ultimately I think the Bitkeeper license will backfire, and there will soon be an open source choice with a similar or better feature set.