Slashdot Mirror


Credit and Free Software

Hans Reiser - you're thinking ReiserFS, and you'd be right - has a proposal to slather Free Software with credits for its authors. Good? Bad? This is something the community has generally moved away from, but maybe Reiser has a good point. Newsforge is part of OSDN.

208 comments

  1. Points not to be discounted lightly by dtolton · · Score: 4, Insightful

    I strongly agree with Reiser on this issue. Although he doesn't
    necessarily argue for "slathering" software with attributions, rather
    he argues convincingly IMO that the credit for a piece of software
    should remain visible to the public users. This can be tastefully
    done easily, the point is that leaving the credit for writing the
    software in the source code is pointless as most people don't ever
    read the source code.

    It isn't even so much that someone can't supply a new spalsh screen,
    it just needs to include attributions to the original authors. I
    think he makes some very interesting and very valid points. It is
    interesting to note as he states, that although Stallman is a huge
    contributor to many projects, he rarely gets credited on anything.
    I feel the same way as Reiser on this, even though Stallman doesn't
    want to burden the software with licensing restrictions, it bothers
    me that he gets so little in the way of credit for what he has helped
    to bring about.

    --

    Doug Tolton

    "The destruction of a value which is, will not bring value to that which isn't." -John Galt
    1. Re:Points not to be discounted lightly by Fembot · · Score: 4, Insightful

      People that don't read the source code arent the sort of people who are likely to rember names IMO. (Or care about names generaly for that matter)

      Also doesn't this proposed license contradict the definition of a freesoftware license?

      And your point about stallman is probably not a good example. He is one of the very few developers that are well known and have got a big reputation in the opensource community.
      What Reiser was saying is it would be an incentive to smaller developers to contribute stuff if they thought that someone somewhere would randomly see their name splashed on the screen. I think I'm inclined to disagree with this basicaly selfrightosness

    2. Re:Points not to be discounted lightly by usotsuki · · Score: 5, Insightful

      Help\About

      Nuff said? Nuff said.

      (FreeGEM Desktop does about the same thing under Desk\Info)

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    3. Re:Points not to be discounted lightly by UtucXul · · Score: 5, Insightful

      Last I checked, the man pages of nearly all software show the authors' names. And most of the time, it is a program's web page that people need to go to for help pr useful info, and those are always filled with names of people who worked on it. I don't see why we need much more than that.

    4. Re:Points not to be discounted lightly by stevew · · Score: 4, Insightful

      I have some significant problems with - what is the difference between this concept and what was the original BIG problem with "BSD Style licenses" where you had to display the copyright notice at boot time/use time? Remember that??? The GPL people stayed away from BSD licenses because of this copyright clause. Now that the BSD licenses don't have the copyright notice they are perhaps "more free" that GPL since they don't have the "contribute the changes back" requirement!

      Further - the whole concept behind BSD and GPL style licenses is that the user is free to change/modify/use the software as needed. A change to "give the author credit" is a definite usage requirement!!!! It isn't free then?!?!

      Look - the authors have a right to put their code under ANY license requirement they like. If they choose to do this - well, I just don't think the software would then qualify as either Free or Open Source software in my mind.

      --
      Have you compiled your kernel today??
    5. Re:Points not to be discounted lightly by FooBarWidget · · Score: 2, Insightful

      "And your point about stallman is probably not a good example. He is one of the very few developers that are well known and have got a big reputation in the opensource community."

      Well if you look at Slashdot, then I'd say he has a big reputation of being the man who gets most flamed at!
      Just look at the Slashdot article about the GNU/Linux FAQ. It generated well over 1000 comments, of which 95% are trolls, flames and personal insults towards RMS. A lot of them even got modded up to +5 Insightful!

    6. Re:Points not to be discounted lightly by Elektroschock · · Score: 1

      I think Free Sofware is not opposed to the original idea of shareware. ( closed source crippleware) I just remind you of the story of PCFile or the ASP guidelines. Add "open source" to that and the next step of the revolution will be taken. Today it is difficult to spent money over the internet. Penpal sucks. But probably an international donation system has to evolve for application developers that write free software (GPLed) Webeditor Quanta is an example of GPL shareware.

    7. Re:Points not to be discounted lightly by hughk · · Score: 2, Funny

      I remember those BSD-style credits. It took ages for the system to display them all during boot. If someone wants to build a 'click-here for developer credits' into an app then its fine by me. What I don't want is involuntary scrolling credits, particularly on app startup. If this leaked into the kernel, we would be in dead trouble - wait three days for a boot!!!!

      --
      See my journal, I write things there
    8. Re:Points not to be discounted lightly by Anonymous Coward · · Score: 1, Informative

      "What Reiser was saying is it would be an incentive to smaller developers to contribute stuff if they thought that someone somewhere would randomly see their name splashed on the screen. I think I'm inclined to disagree with this basicaly selfrightosness"

      I am a (small) developer. I sprinkle my handle everywhere I go (code I contribute to, not what you thought, silly), in the vain hope it stays there and people will later recognize my work and praise me (or hate me, anyway, recognition is never bad). If I could no longer attach my handle to my work, I would stop publishing my work (albeit not working, I love to code).

      Now, curently it is only in the source and in documentation, but it would rock if my name would be be shown to the "average" user....

      I work and live for recognition...

      Tels (posting AC as always)

    9. Re:Points not to be discounted lightly by mindriot · · Score: 1

      True. I like Reiser's first idea though - giving credit to the developers in splash screens, screensavers, etc. But changing the license - no. As others on the newsforge board said too, a Free Software license does not restrict the user in any way other than forcing people to keep the license. If people want more credit for their products, they could easily change their product so it shows the names in more places (as long as that doesn't lead to nag screens...).

      Maybe Hans Reiser is writing this article because, of course, his software has no higher-level splash screens etc., and credit is thus not too visible, but I think he could reach most distro makers and ask them to, for example, give him more credit in the documentation, and they might happily do it. But I think that enforcing credits through the license is unnecessary. Most software includes credits in many ways, and many people who use free software to improve their own free software do give credit. In the case of ReiserFS, for example, Hans does not gain anything from his name being included in every software building on it. The people he seems to be trying to reach won't read the licenses anyway (he seems to be looking for more of a marketing/'general public' approach).

      So, it would of course be nice (and not much of a problem) to have, say, more splash screens/screensavers/hints in the docs or whatever showing credit (without annoying the user of course). I would take his message as "hey, people, let's promote our own names in a way that's a little more visible", and I'd be fine with that. But a license change? Not justified, imho.

    10. Re:Points not to be discounted lightly by autopr0n · · Score: 2, Insightful

      People that don't read the source code arent the sort of people who are likely to rember names IMO. (Or care about names generaly for that matter)

      Wha? Are you saying that everyone who remembers' Maddona's name, or Bill Gates, or Michal Jordan or Mohamed Saeed Al-Sahhaf are all source code reading geeks?

      People will remember a name if they see or hear it often enough.

      --
      autopr0n is like, down and stuff.
    11. Re:Points not to be discounted lightly by brianosaurus · · Score: 2, Interesting

      Stallman is very well known, but I can't recall any software he's written other than GNU Emacs. While Emacs alone is a pretty huge contribution, I know there is more that he has done, I just don't know what it is.. and its probably stuff I use all the time.

      I think at the root of this is the whole "GNU/Linux" vs "Linux" debate, as that is one of the most prominent cases of not giving credit where credit is due. When that issue was covered on "Revolution OS", Stallman made a very good argument that there are thousands of people contributing GNU software which supports the Linux kernel to make an OS distribution, but GNU gets no credit. Linus's truly brilliant, and well though out response: its mine, so i call it Linux.

      --
      blog
    12. Re:Points not to be discounted lightly by pod · · Score: 2, Insightful
      People that don't read the source code arent the sort of people who are likely to rember names IMO. (Or care about names generaly for that matter)

      That's missing the point. The credits are not there to drill obscure names into people's memory. A little blurb in --help or --about or --version should suffice here. Credit should be given, because it's the Right Thing to do. If someone uses some of your code, no one will ever know about it, even though the contribution was valuable enough, obviously.

      This would be similar to credits shown in movies. Do you really care who the second unit's driver was? Would you remember the name? But they're shown all the same, even at the cost of an extra song for the sound track.

      --
      "Hot lesbian witches! It's fucking genius!"
    13. Re:Points not to be discounted lightly by awol · · Score: 3, Interesting

      People that don't read the source code arent the sort of people who are likely to rember names IMO. (Or care about names generaly for that matter)

      No way. In the new world order where IP goes away, your reputation as a contributor to software will be your stock in trade. It will be the means by which you price your services to those that would consume them from projects to emplyers. It is absolutely critical that software is correctly attributed and that it should be easy and proiminant.

      You see someone who takes attributed code and claims it as their own is committing fraud an ancient wrong that is straightforward to prosecute. The commercial damage to one so wronged is an intruiging question but once the value of reputation in this new order is understood then the value of such damage will be eaiser to understand, both in terms of the private actionable wrong but also the public policy issue in ensuring that work is attributed accurately and completely.

      --
      "The first thing to do when you find yourself in a hole is stop digging."
    14. Re:Points not to be discounted lightly by Anonymous Coward · · Score: 0

      >I think Free Sofware is not opposed to the original idea of shareware.
      >( closed source crippleware) I just remind you of the story of PCFile
      >or the ASP guidelines.
      >
      >
      Wrongo. It was the ASP "guidelines" that turned people off to the concept of shareware. Those "guidelines" weren't there to protect the people interested in actually buying shareware, they were put there to help shareware authors and their distbuters like you to ripp-off the bbs operators.

    15. Re:Points not to be discounted lightly by BrokenHalo · · Score: 1
      trolls, flames and personal insults towards RMS. A lot of them even got modded up to +5 Insightful!

      Which, sadly, says a lot about the adolescent nature of some of the Slashdot community. Let's face it, how many of these kids have even met the man? OK, I never have (and I'm not a kid any more, either:-))

      Fact remains that RMS has contributed a hell of a lot of time and effort over the years to open-source software, and he deserves some credit for it.

    16. Re:Points not to be discounted lightly by Anonymous Coward · · Score: 0

      Try typing gmake --version (or just make --version if GNU make is the default make on your system).

      I think this is exactly the point of the article, that credits such as these are pretty well hidden.

      However, personally, as a developer, I don't care whether my name is well-known. I do have my name in some source files of some open source projects, but frankly I wouldn't care if it weren't there. In fact I prefer that my name is not prominently visible.

    17. Re:Points not to be discounted lightly by leomekenkamp · · Score: 1

      (...) everyone who remembers' Maddona's name, (...), or Michal Jordan or Mohamed Saeed Al-Sahhaf

      It surely seems that you cannot remember to spell the names of Madonna, Michael Jordan and Mohammed S. right

      ;-)

      --
      Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
    18. Re:Points not to be discounted lightly by Fembot · · Score: 1

      No they wont.. People rember things that are interesting to them and they see a point in rembering.

      Will Grandma running kde (or whatever) rember the names she sees on the screensaver? NOPE

      Will kids using linux rember the names? NOPE unless they're some way related to the games and chat apps they like

      Will professionals (other than computer related) rember the names? Nope, they'll try and turn the screensaver off or to one of their holiday photos.

      The only group of people who care what Alan Cox, and others have been upto are developers and geeks. The rest just see software as a tool

  2. Bad credit? No credit? by Anonymous Coward · · Score: 5, Funny

    Then the new GPL Secured Platinum Card from RMS is for you! All the credit you ever wanted, in one small piece of code.

  3. the purpose of free software for many IS credit by Anonymous Coward · · Score: 5, Insightful
    I know quite a few people who have written second rate software under Free licenses for nothing more than a bit of prestige and something to write on their CV. Indeed, even some of the more major F/OSS contributors seem to take development as a career advancement/fame trip.

    I'm not saying there's anything wrong with this, mind. I just want to remind some of the zealots that writing Free software is often not the selfless idealistic cause some make it out to be.

    1. Re:the purpose of free software for many IS credit by Anonymous Coward · · Score: 1, Interesting

      Quite. And anyone who puts their own name in the name of their software, Mr Reiser "of ReiserFS fame", has pretty blatant opinions on modesty that he really didn't need to write a whole article about to reveal.

    2. Re:the purpose of free software for many IS credit by JJahn · · Score: 3, Insightful
      Also, Linux = Linus. What's your point?

      What exactly is wrong with naming something after yourself?

    3. Re:the purpose of free software for many IS credit by Anonymous Coward · · Score: 0

      You appear unable to read. The parent explicitly said that there is nothing necessarily wrong with this, merely pointing out that some people use credit as a major/only incentive for writing FOSS.

    4. Re:the purpose of free software for many IS credit by Cromac · · Score: 2, Insightful
      I know quite a few people who have written second rate software under Free licenses for nothing more than a bit of prestige...

      How much prestige can they get for writing second rate software? I don't recall many people being very impressed by second rate anything.

    5. Re:the purpose of free software for many IS credit by JJahn · · Score: 1

      You appear unable to comprehend that I was responding to the post under the parent.

    6. Re:the purpose of free software for many IS credit by Q+Who · · Score: 1

      Also, Linux = Linus. What's your point?

      What exactly is wrong with naming something after yourself?

      Correct me if I am wrong, but the name "Linux" wasn't given to the OS by Linus himself.

    7. Re:the purpose of free software for many IS credit by Fillup · · Score: 1

      Tell that to my friend. He just bought a Windows machine because of how "great" Windows XP Home is. If that's not second-rate....

      --
      "I think there is a world market for, maybe, five computers." __ IBM Chairman, 1943 __
    8. Re:the purpose of free software for many IS credit by Anonymous Coward · · Score: 0
      I think you are correct. Still, Linus was in a position to give it another name, wasn't he?

      But this is no problem for me, I think Linux is a great name, and thinking of it, Knoppix is also a kewl name.

    9. Re:the purpose of free software for many IS credit by Cromac · · Score: 1

      There's a sucker born every minute.

    10. Re:the purpose of free software for many IS credit by Narcissus · · Score: 1

      I believe you're right: although I don't have references anywhere, I did read once that it was named by the guy who ran the FTP server it was originally on.

      After Linus put it into the incoming directory, it had to be moved / renamed: seeing as Linus hadn't named it anything, the FTP admin named it Linux (obviously due to Linus' name, but also presumably to sound like Minix, which it was intended to "feel" like originally).

    11. Re:the purpose of free software for many IS credit by DarkVein · · Score: 3, Insightful

      Using Ayn Rand's clarified definition, I'd say selfish reasons are the best and most prominent reasons to write good software. Still using Ayn Rand-compliant vocabulary, Reiser is being very selfless.

      Translation: people write software for the feeling of self-fullfillment, self-actualization, and personal pride. This is a personal experiece that does not require anyone else's opinion to realize; you know you've given everything you could. Reiser, however, requires the recognition of others, needs his "greatness" (extremely debatable) to be recognized and advertised by others. This is what people mean by "his ego problems". He is "without self", or "selfless".

      More on a practical point, Hans Reiser has been completely unable to prove that (1) the current setup is insufficient, (2) anything would be gained by modifying the current setup, and (3) his proposals would do less harm than good.

      Further, I have supreme doubts that reputation is the driving force for the best programers. Respect of your peers is a reward. Delivering bad code would cause you to lose respect, and that lose would be a source of fear. Fear does not drive good development. Self-actualization drives good development, and that is incompatible with fear of resentment. Good programers (s/programers/anything) may enjoy the respect of their peers, but that is quite different from fear for your reputation. Reiser is fearful, and ReiserFS is a testament to bad code.

      --

      I'm as mimsy as the next borogove but your mome raths are completely outgrabe.

    12. Re:the purpose of free software for many IS credit by Anonymous Coward · · Score: 1, Insightful

      Yes, and writing some insignificant program from scratch is trivial compared to diving into a complex, existing project written by others and fixing bugs there.

      The latter isn't likely to get a developer any recognition whatsoever outside of other developers involved in the project, although it is a much better demonstration of skill.

      The world isn't fair, and trying to make it fair is hard. Which is why people should be motivated internally rather than externally.

  4. My dick itches. by Bitter+Old+Man · · Score: 2, Offtopic

    Immersing it in vinegar is not helping, either.

  5. help - about by Anonymous Coward · · Score: 0

    If I am impressed with a piece of software enough, I will look. Don't bother me with splash screens or anything else of the sort.

  6. OSS belongs to the community by vosbert · · Score: 4, Insightful

    OSS belongs to the community. There's really no need for credits. Where would we draw the line if we allowed credits? banner ads? annoying pleas for money? pop up windows?

    1. Re:OSS belongs to the community by tomstdenis · · Score: 2, Interesting

      Belong to the community... yeah sure my ass.

      As an OSS developer myself I feel everyone is entitled to use a copy of my stuff for whatever they want. I don't feel they "own" the project though.

      I mean a lot of work goes into something like a Distro [or the stuff in a Distro]. Just because you're smart enough to put a CD in and install a distro doesn't mean you're a significant contributor.

      I'm all for tasteful plugging authors names.

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:OSS belongs to the community by the+uNF+cola · · Score: 2, Insightful

      Ok, hold on a sec. At the current state of things, many softwares are at one extreme. People have no clue on where it comes from.

      Linux is one of the fortunates, 'cause people may easily assume it with Linux. Same with ReiserFS and MAYBE the BSD's. B is for Berkeley, it's good enough for me. Even Netscape Mozilla, Microsoft Windows, Lotus 123.

      Today, I used pan. The news reader. Unless I go search, I haven't a clue who wrote pan, nor do I care. I also used Spammassassin.

      What is being suggested, is there be some default inbetween. You are right, it belongs to the community if it was given to the community. What he's saying is, default it to have something in there. Let the world know, that Linus did the initial work on Linux, and that me, a small developer, contributed to some software or even wrote my own. And if you don't like the credit showing up every time, take it out! That's the nice thing about OSS. Worse comes to worse, if it is hard to remove, someone will write a patch to make it easy to deal with or people just won't use it.

      --

      --
      "I'm not bright. Big words confuse me. But Wanda loves me and that should be enough for you." - Cosmo

    3. Re:OSS belongs to the community by mickwd · · Score: 1

      "OSS belongs to the community."

      OSS is released under various different licences which specify what the copyright owner will allow the "community" to do with it (which is usually pretty unrestricted, compared with closed-source software - after all, that's the point of OSS). But the community as a whole doesn't own it.

      "Where would we draw the line if we allowed credits? banner ads? annoying pleas for money? pop up windows?"

      Most of us would draw the line in a sensible place, and not think a load of bollocks about the "thin end of the wedge".

    4. Re:OSS belongs to the community by aardvarkjoe · · Score: 4, Insightful

      OSS belongs to the community.

      No way. When I write OS software, I retain the copyright. The community didn't write the software, I did. I freely allow the community to make use of it in practically any manner that they see fit, but that still doesn't mean that I have lost the ownership of my work.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    5. Re:OSS belongs to the community by samhalliday · · Score: 2, Insightful
      i agree completely... a standard [insert big brand gnulinux/*BSD here] distro has, what, a few thousand different packages. if each program has even ONE credit given to it, we are talking about so many names in the CREDITS on the back of the box that you wont be able to tell what the product is anymore!!!

      everyone who writes a gnu/oss program knows what they are gettign into before they start. RMS may seek credit everywhere he goes... but he wants credit given to GNU, not for himself! Reiser, on the other hand, even called his FS after himself...

      with GNU/OSS, any author is fully able to place a "Help->About" window in, or "--version" flag. by this method, i ALREADY know the names of the main authors of all the programs i use every day... with an exception to Maple (which along with java are the only non-OSS/GNU apps i have...)

    6. Re:OSS belongs to the community by PetiePooo · · Score: 1

      When I write OS software, I retain the copyright. The community didn't write the software, I did. I freely allow the community to make use of it in practically any manner that they see fit, but that still doesn't mean that I have lost the ownership of my work.

      When you write software, you retain the copyright. When you release it as OS under a BSD-style license, I would agree that you retain the copyright. You can exercise your copy rights and pull the source code off the net to start selling commercial versions for example.

      However, when you release it under the GPL, you essentially branch a version of your copyrighted code and release it to the community. You retain the copyright to your original work, but if I submit a change to your GPL version, my change is also GPL'd. No way do you now own my change! If you want to fold that change into your copyrighted work and sell it, you cannot do that. The GPL explicitly addresses this. (That must be why they call it the copyleft, huh?) I would need to release to you a patch based on the non-GPL'd code, or you would have to implement my patch's functionality without using my code.

      The confusion is between OS in general and GPL'd OS, which most people (especially the /. crowd) generally equate with OS in general. If you release BSD, your copyright is still enforcable. If you release GPL, I agree with vosbert in saying it's now the community's code. You can't exercise any of the normal copy rights on GPL'd code; you gave them up when you released it and accepted GPL'd updates. Of course, if you haven't accepted any GPL'd updates, then you still have an original, non-OS version in your back pocket that you are the sole author of, right? That one you still have exercisable copyrights to.

    7. Re:OSS belongs to the community by _typo · · Score: 1
      When you write software, you retain the copyright. When you release it as OS under a BSD-style license, I would agree that you retain the copyright. You can exercise your copy rights and pull the source code off the net to start selling commercial versions for example.

      And how's that any diferent in GPL'd code? You can also "pull your source code off the net to start selling commercial versions" with it.

      However, when you release it under the GPL, you essentially branch a version of your copyrighted code and release it to the community. You retain the copyright to your original work, but if I submit a change to your GPL version, my change is also GPL'd.

      The only diference the BSD license has in this respect is that it doesn't enforce the changes to come back in any way or license.

      The confusion is between OS in general and GPL'd OS, which most people (especially the /. crowd) generally equate with OS in general. If you release BSD, your copyright is still enforcable. If you release GPL, I agree with vosbert in saying it's now the community's code.

      Both the GPL and the BSD license effectively give the code to the community, what is different between then is what you expect to get back from that code. With GPL changes have to be released back as GPL. With BSD you can pick up the code and run with it. So, the BSD license is more about *giving* to the community where as the GPL is more about the community *sharing* code and making sure that sharing continues.

      You can't exercise any of the normal copy rights on GPL'd code; you gave them up when you released it and accepted GPL'd updates.
      You can exercise copyright on your original code and not on others code. That doesn't change if we're talking about the GPL, the BSD license or any other license for that matter. What you can do with the BSD license that the GPL doesn't allow is to take BSD code and use it in a close-sourced app. That has nothing to do with exercising "normal copy rights on [...] code", since you don't have copyright on code you didn't write.
      --

      Pedro Côrte-Real.

    8. Re:OSS belongs to the community by PetiePooo · · Score: 1

      And how's that any diferent (sic) in GPL'd code? You can also "pull your source code off the net to start selling commercial versions" with it.

      I disagree. You can't legally pull my GPL'd code off the net and start selling commercial versions. So, if you started a GPL project, and I pushed updates into your project's CVS repository, you are absolutely NOT allowed to sell my changes. Get it?

      As I said towards the end, though, if you haven't accepted any GPL'd changes, then you have your original, non-released, non-GPL'd version that you retained sole copyright to. That's the version you can sell. Technically, you shouldn't even pull your GPL'd version off, rip out the GPL notice and sell that, even if you are the only one that submitted changes to it after it was GPL'd. You should go back to the latest version you had before you put it under the GPL and patch that up with non-GPL patches.

      MS views this as viral. Its a sticky clause that's good for the community, not viral corporations that like to embrace and extend. I view it in the same light as beneficial bacteria...

    9. Re:OSS belongs to the community by _typo · · Score: 1
      I disagree. You can't legally pull my GPL'd code off the net and start selling commercial versions.

      Sure I can. If I couldn't do that commercial Linux distributions would be in trouble.

      you are absolutely NOT allowed to sell my changes. Get it?

      Sure I am. The GPL only makes sure that you get changes back GPL licensed, it doesn't have any restrictions on the buying and selling of software. Get it?

      As I said towards the end, though, if you haven't accepted any GPL'd changes, then you have your original, non-released, non-GPL'd version that you retained sole copyright to. That's the version you can sell.
      I can sell any version. What I can't do with GPL that I can do with BSD is take the code and change it, not giving my changes back, and sell *that*.

      Another thing you're overlooking in the BSD vs. GPL discussion is that while in GPL'd code the changes have to be given back as GPL'd code with BSD code there's no such guarantee. Taking that into account, if you release some piece of code BSD licensed you might not be able to use some of the changes you get back in a version you sell commercially because it's not guaranteed that those changes are covered by the BSD license, with the GPL that doesn't happen since all changes have to be given back as GPL and you can sell them at will.

      --

      Pedro Côrte-Real.

  7. Hans Reiser - reiserfs. by Anonymous Coward · · Score: 0

    This guy definitely want credit :-)

  8. Give 'em credit! by rice_burners_suck · · Score: 3, Interesting
    Listen. The authors wrote the software. They did so with the knowledge that it would be distributed freely (as in libremente) and as such they would probably not make any money off it. Despite this, they have put a lot of effort, blood, sweat and tears into making something that is reasonably functional, efficient and safe to use. I know exactly how difficult it is to produce good software.

    The way I see it, the authors deserve to have credits all over the free software that they made. And when you run free software, don't tell yourself that it's your right to take someone else's work and use it "just because." You have the right to use it because THEY gave you that right.

    1. Re:Give 'em credit! by Skyshadow · · Score: 4, Interesting
      And when you run free software, don't tell yourself that it's your right to take someone else's work and use it "just because." You have the right to use it because THEY gave you that right.

      While that's true on it's face, I would counter that making the fruits of your labor available to others in the community is not an entirely selfless act.

      Really, quality OSS projects are not the work of a single person. They're the result of wide-ranging teams who, thanks to the GPL, are able to apply many eyes, ideas and approaches. That's the whole strength of OSS.

      Now, I do believe it's important to give credit to those who work hard, but I also believe it's futile to toss credits in the face of someone who doesn't give a toss (and not giving a toss is a right the GPL gives you, as well).

      --
      Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
    2. Re:Give 'em credit! by antiMStroll · · Score: 2, Insightful
      Developers can do what they want already. They don't because they know it will alienate users, but Help>About isn't enough for Hans. Hans is proposing credit - let's be blunt: commercials for the developers - be a mandated condition of the software license, universally and continually forced on users in screensavers and splashscreens. This isn't due credit, this is megalomania. I can already hear his next argument, that the name Reiser should be displayed equal time on all distros carrying his FS, whether the user chose to activate it or not. Equal time, fair, right?

      I use OSS precisely because it's not personality and marketing driven in user-land. The day Hans' proposal bears fruit is the day I buy a Mac.

    3. Re:Give 'em credit! by Anonymous Coward · · Score: 0

      Credit is fine, when you close the application, pop up a brief credit list, capable of being ESCaped out of... end of story.

    4. Re:Give 'em credit! by Anonymous Coward · · Score: 0

      making the fruits of your labor available to others in the community is not an entirely selfless act.

      That's at the core of the problem: If it is not an entirely selfless act, then what is the motivation? Are there different motivations for people who scratch their own itch and release their code into the OSS world and people who, as MS once put it, do the grunt work?

    5. Re:Give 'em credit! by cbare · · Score: 1

      True, the developers deserve credit. I agree. But, does that make it a good idea to legally mandate that credit? That is an entirely differant question.

      I think the admiration within the open source community for its star developers goes way deeper than anything a legally required splash screen could produce. I also think anyone who would remove an author's name from his work is a special kind of slime.

      But, it's fundamental to the ideas of open source and free software that the authors give the right to use the software with as few restrictions as possible.

      I have no problem with a tasteful list of contributors. The problem comes in with corporate sponsorship. Do we want "This Software brought to you by Schwartz's Foot Ointment!!" plastered all over our screens? I think not.

      That's no longer free. It becomes just another means of getting consumers to buy stuff. Let's hope things don't go that way.

      --
      -cbare
    6. Re:Give 'em credit! by poldis · · Score: 1

      It is abundandtly clear that GPL'd software must be unencumbered by restrictions in use (which does, according to Debian and others, include any credits in source comments, docs, manpages, etc, without exception)

      As such the matter is simple: if you with to impose (even modest) restrictions upon your work (such as a required copyright string in your headers) you simply release it under a license that is accomodating of that. The GPL is not.

      Personally, I agree with the concept of modest immutable credit, such as in source headers. If I wrote a book, my name should be in the copyright page... and when I write software my name should be and always be somewhere on that work, regardless of who doesn't like it there. It has nothing to do with how "free" something is... the opposition of such tasteful practice of this is an excess on the part of the GPL. It has nothing to do with ads... we're losing the forest through the trees.

      Now, if you'll excuse me, I have to go tear the dedication page out of all my books... those shameless profiteers.

    7. Re:Give 'em credit! by DarkVein · · Score: 1

      You suggest that credit is being stolen or snuffed, right now? Reiser is proposing to plaster advertising everywhere possible. He already puts advertising into kernel messasges, and there's a big stinking advertisment in the ReiserFS kernel infopage.

      Credit is given due, and anyone who cares can find out who wrote what piece of code (thanks to the miracle of comments). Reiser wants to plaster author names as advertising.

      Honestly, I don't think he's mentally healthy. I've written other comments on this.

      --

      I'm as mimsy as the next borogove but your mome raths are completely outgrabe.

  9. live on open source? by tychoS · · Score: 1
    Are there any known cases of program ideas, in contrast to projects projects trying to copy and improve the idea of an existing program, that was made available as open source from the start of?

    If yes, how did the people behind the project earn enough money off the idea to at least pay their living expenses and some more to compensate for the risc. they took that failure of the project would lead with them to have lived without income for a while?

    I ask because I am at present engaged in producing a piece of software that is not a copy of an existing product, and cannot think of a way to make a living out of it if I release it as open source.

    1. Re:live on open source? by Silent_E · · Score: 1

      Most open source folks, and most back in the day before micro$oft, made money by offering to supply paid support. Check the web for stuff Beagle Brother's Software for one of the most awesome models in history: they sold the software, but made the source open, and sold support. All software used to be like this.

    2. Re:live on open source? by tychoS · · Score: 1
      Well yes, the service and support route is often mentioned, especially as something that was common up until the pc's came on the scene with their scrink wrapped software. It is still used in the mainframe software business by CA, IBM et. all. with sizeable amounts of money changing being paid for yearly "subscriptions" for the right to use th esoftware as well as access to service and support from its manufactor.


      However apart from cygnus, linuxcare and a few more companies that sold service and support for other peoples open source programs and sort of crashed and burned during the .com age, are there a sizeable number of contemporary succesfull cases especially where the program authors ran the service and support business themself?


      I did look for such cases and while I found some very small mom&pop style operations that apered to operate succesfully, I did not find a huge number of these, and not really anything larger than this.


      I am looking for a way to support a team of around ten people who will work on the product itself on an ongoing base, but have not seen examples of operations doing this well with the income from a service and support organisation for an open source program.

    3. Re:live on open source? by Anonymous Coward · · Score: 0

      http://www.trolltech.com/

  10. Free Our Egos! by Alan+Holman · · Score: 0

    As a provider of free content on the internet myself -- not usually computer programs, though -- I agree with you that programmers, and anyone who provides any free content, deserve recognition. Free materials on the internet are usually high quality. They're free because it's the author's passion to create it, be it a computer program, or a series of unproduced television scripts. Anyone who makes free content, does it out of passion. That passion makes quality products, and encouraging publicity of the author's names will encourage productivity from that author.

  11. Doubled Edged Sword by Heinr!ch · · Score: 3, Insightful

    First, I think that mostly FOSS developers and engineers can appreciate the work that goes into this stuff. So I sortof agree that additional credit might be good as a way of thanking those who have made contributions. Software, especially application software, tends to be like a collage. Do you credit everyone equally? Do some people get more credit? What happens if we forget to thank/credit certain people along the way? I think this could be a disaster and potential hurt the movement.

    1. Re:Doubled Edged Sword by antiMStroll · · Score: 1
      My guess is that in Hans' mind team leaders of the Important Stuff (cough....cough...files systems..) deserve much more credit than the authors of XBill, Ion or Samba Swat module plugins. There is no way to credit the tens of thousands who make any one distribution possible. And what about IBM, Netscape, and Sun, corporations who devote sums and labour no one individual can match? How can this not devolve into another opportunity for commercial advertising?

      The proposal is grotesquely and transparently self-serving, in my opinion incredibly short-sighted and not made with the best interest of the entire developer community in mind. Hans is beckoning developers to OSS hell.

  12. This is a good idea. by Meat+Blaster · · Score: 3, Funny
    For many who contribute, the only compensation they see is in recognition. Everybody knows who Linux is, but how about the guy that put sed together?

    I would like to propose that, in addition to the mandatory screensaver displaying the credits, that every fifth time you run a utility its name, version number, date of creation, and author are read through the speaker. This way, people can truly appreciate the donation of software by others. To celebrate Free Software's global approach towards solving problems, this should be subtitled on the screen in the user's native language. This way, we can truly feel the joy of helping people without compensation while being compensated for it.

    1. Re:This is a good idea. by joshtimmons · · Score: 2, Funny

      Or, better yet, every fifth time you run a utility it should quiz you for the author's name. If you don't know the answer, then it refuses to run.

      That will get people to learn author's names.

    2. Re:This is a good idea. by Vlad_the_Inhaler · · Score: 1

      so, who wrote ls? or cd? or less?

      very bad idea, if serious.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    3. Re:This is a good idea. by Anonymous Coward · · Score: 0

      And every tenth time you run the program, you get a popup asking you if you'd like to register for a free account at the software developer's main website. Err, sounds kinda like that other operating system I've heard of...

    4. Re:This is a good idea. by Anonymous Coward · · Score: 0

      /* `dir', `vdir' and `ls' directory listing programs for GNU.

      Copyright (C) 85, 88, 90, 91, 1995-2001 Free Software Foundation, Inc.
      ...
      /* Written by Richard Stallman and David MacKenzie. */


      Yeah, I'm just doing this for the sake of it ;)

    5. Re:This is a good idea. by moncyb · · Score: 1

      What if you're system doesn't use GNU ls? I wrote the ls for my system. FreeBSD has another version...

    6. Re:This is a good idea. by renec · · Score: 1

      Yes everybody knows who.. umm. LinuS is. Not so many get his name right.

  13. Moot point by Blaine+Hilton · · Score: 0, Troll
    This seems like a good idea on the surface, but in reality I'm not sure if it would work. With open source software you can't really go to any specific entity and demand that they provide bios on every developer. Some developers don't even want to be connected with a project, let alone having detailed biography of them. They probably already are receiving thousands (if not millions) of emails/mail/calls asking for support related questions to the point of harassment.

    However if the developer would like credit then they could release the software under a modified license that would require the display of their bios. Already a lot of the open source projects have some information on different contributors on the project's website. I would think maybe creating something like this in the Help-->About, or man pages type area may be a good compromise.

    As for the BSD license change, I think that's like comparing apples to oranges, because it seems like they did that more for the university and not for any actual developers.

    Need to create a mySQL Table?

  14. Well, he did name a file system after himself. by ChimChim · · Score: 1

    It's no wonder this came from a guy who named a file system after himself. I wonder if he'd namecd his apartm^H^H^H^H^H^H estate after himself.

    1. Re:Well, he did name a file system after himself. by Anonymous Coward · · Score: 0

      " It's no wonder this came from a guy who named a file system after himself. I wonder if he'd namecd his apartm^H^H^H^H^H^H estate after himself."

      why do i always see this on /.

      i'm talking about ^H^H^H^H^H^H^H^H

      any ideas?

    2. Re:Well, he did name a file system after himself. by PygmySurfer · · Score: 1

      It signifies backspace... ie. he's backspacing over apartm, and changing it to estate..

  15. Not sure I agree with his thinking by Skyshadow · · Score: 4, Insightful
    Hans talks about how 99% of people, as it stands, don't see the names of the folks responsible for the software they turned out. I'd counter that 99% of the people certainly could care less, that 99% of people leave movies before the credits are even halfway through and habitually tune them out to begin with.

    IMO, the people who are going to care are already seeing the names, either in the source or at the project websites or in CVS. To everyone else, any sort of more obtrusive crediting is just going to be obnoxious, and they're still not going to know any more names then they did before.

    The whole point, if anyone still remembers the original goal of the majority of OSS projects, is to write some kick-ass code that's going to be done the Right Way, rather than the short-cutty kludgy way that most programmers are forced to code at work. To me, this includes making the software as elegant and streamlined as possible, and the various methods of ego gratification I can think of (extra splash screens, etc) seem incompatible with this.

    --
    Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
    1. Re:Not sure I agree with his thinking by roskakori · · Score: 1
      Hans talks about how 99% of people, as it stands, don't see the names of the folks responsible for the software they turned out. I'd counter that 99% of the people certainly could care less, that 99% of people leave movies before the credits are even halfway through and habitually tune them out to begin with.

      and yet, they usually read the about 10 names showing up at the beginning of the movie, typically including the director, producer, main actors and camera.

      this also seems to be hans' point: he doesn't ask for credits of every little patch-submitter, he wants a list of "rock-stars".

      i wonder how long it will take before we have the developer-equivalent of boy-groups and britney....

    2. Re:Not sure I agree with his thinking by Zork+the+Almighty · · Score: 1

      I agree entirely. Free software became a powerful force because it is free (as in freedom). Now people are continually trying to use it to push their own personal causes - RMS, the anti-drm camp, etc, and likewise with this. Trying to make rock stars out of people might net us a bit more cash in the short term, but it's ultimately a frivolous exercise. Linus has had the right vision from the start.

      --

      In Soviet America the banks rob you!
    3. Re:Not sure I agree with his thinking by Anonymous Coward · · Score: 0

      99% of people leave movies before the credits are even halfway through and habitually tune them out to begin with.

      Yes, and I'm one. I have to remember to look at advertisments, otherwise they'd be invisible. Part of the reason I use Linux is because I can look at the screen and not have to tune out the self-promotion. If I want to know who wrote something, I will look for the information. On the other hand, if the authorship wasn't protected, then I would have to doubt the reliability of the information I found...

    4. Re:Not sure I agree with his thinking by Anonymous Coward · · Score: 0

      and yet, they usually read the about 10 names showing up at the beginning of the movie, typically including the director, producer, main actors and camera.

      We should be moving away from movie opening credits, not towards software credits....

  16. This sucks. by I+Am+The+Owl · · Score: 5, Interesting

    Like someone else mentioned above, this is not free software. If you write software that throws a bunch of credits in people's face all the time (the screensaver idea is an awful one), distros will be inclined not to use your software by default if the license forces the issue. Imagine if business contributes to a free software project and then insists that the business be "given credit" by putting their name all over the place. But then I see ReiserFS doing just that: last time I formatted a ReiserFS partition, I got a list of all the companies that contributed money to the project. Don't get me wrong, ReiserFS is great, but I don't care to see a bunch of ads in my software. Imagine if every time you ran ls you got some companies name listed along with your directory listing.

    Free software is not about egos, it is about keeping software free. Forcing something like this through licensing makes the software non-free. Want the credits? Look at the source code or the documentation!!!

    --

    --sdem
    1. Re:This sucks. by jalet · · Score: 1

      > Imagine if every time you ran ls you got some
      > companies name listed along with your directory
      > listing.

      I'd suggest you to patent this very good idea before someone else does ! (no kidding)

      --
      Votez ecolo : Chiez dans l'urne !
    2. Re:This sucks. by fedaykin42 · · Score: 1

      Free software is not about egos, it is about keeping software free. Forcing something like this through licensing makes the software non-free.

      So, you get the software free (as in beer) and you believe that if someone displays their name telling you they wrote it, that makes it non-free (again, as in beer)? The notion of free software (pay attention, this is the "as in speech" part) is that the person who writes the code shares the code for all to use, not so you don't have to pay money for it. If released under the GPL, the code must maintain credit to the original author. The only new part here is that the credit has visibility beyond those who care to look at the code.

    3. Re:This sucks. by lspd · · Score: 1

      Imagine if every time you ran ls you got some companies name listed along with your directory listing.

      More importantly, imagine if Reiser's view of the GPL was the norm. You write a good piece of software, someone else extends it a bit and slaps adds all over the place. You're now locked out from using their improvements unless you add in all their advertising.

      This is the same nonsence that PHP-Nuke argues. And in both cases, ReiserFS and PHP-Nuke, they complain about their advertising being removed because they're trying to sell commercal versions of their software.

    4. Re:This sucks. by mickwd · · Score: 1

      "Imagine if every time you ran ls you got some companies name listed along with your directory listing."
      -
      Maybe they should list those names in the man pages - no-one would ever think of looking there ;-)

    5. Re:This sucks. by Anonymous Coward · · Score: 1, Interesting

      But then I see ReiserFS doing just that: last time I formatted a ReiserFS partition, I got a list of all the companies that contributed money to the project.

      Note to self: Never ever ever use ReiserFS.

      For any reason.

      Period.

    6. Re:This sucks. by Anonymous Coward · · Score: 0

      The only new part here is that the credit has visibility beyond those who care to look at the code.
      That's a HUGE leap since it becomes advertising. IMHO, people will start paying for free (as in speech) software if free (as in beer) software starts including ads.

    7. Re:This sucks. by fedaykin42 · · Score: 1

      That's a HUGE leap since it becomes advertising.

      And the problem with that is? Don't get me wrong, I hate pop-ups, etc. more than anyone; but, I also have no problem with the credit of who provided you with a piece of software you value being displayed to the user. It can be done in a tasteful way. For example, for years I've seen the name of the author of my 3Com card's driver module in my system log when the driver loads. Do I care that it's there? Nope. Do I think that Donald Becker is a swell guy because now I can use my 3Com card in the OS of my choice? Damn skippy, I do. Would I have known his name if it wasn't in my system log? Probably not since it works great and I have no reason to look at the code. On the other hand, if the driver was logging something once a day or every time it sent 1MB worth of data, I probably would not be a happy camper.

      I say kudos to those who take time out of their lives to allow me to use something I value. I'm glad I get to know a few of their names even though I may not be developing code in their neck of the woods.

    8. Re:This sucks. by Alex · · Score: 1

      More importantly, imagine if Reiser's view of the GPL was the norm. You write a good piece of software, someone else extends it a bit and slaps adds all over the place. You're now locked out from using their improvements unless you add in all their advertising.

      What bit of the GPL says you have to use all of a patch someone submits? The maintainer doesn't have to accept the advert + the code - you haven't thought that comment out very well.

      Alex

    9. Re:This sucks. by vadim_t · · Score: 1

      The difference is, there the name serves a good purpose. First, the kernel tells you the driver is there, and at least one line is going to be spent already, so adding the author's name won't hurt. Second, if while your kernel boots it freezes right after displaying that line you know who could help you.

      What Hans Reiser wants is mandatory publicity for no good reason at all. I think it's quite different.

    10. Re:This sucks. by fferreres · · Score: 1

      Hans has tris problem where he sees open source needs some retribution to some authors. Specifically, a filesystem or a hidden library that is crucial for the wellbehavedness of any OS doesn't get much credit while other end users programs like Mplayer do. So there is much less incentive to develop the boring part where you also don't get any visible rewards.

      And it turns out there is no real way to reward OSS authors, no credit system, nobody (except some few developers) really knows what's the real value added by OSS coders. No way to reward with money nor even credits.

      That's the problem hans sees, he dropped the towel to find a working way to fund OSS developements in a way that makes sense (ie: money goes where is needed, not where it is most visible) so he is now targeting a previous step. Trying to figure out who must be credited and making sure people know about it.

      Of course, that's nearly imposible and intrusive. I want people rewarded, but I don't want a mess of a thouthand names in front of my face.

      There sure is a solution, this ones does not look like one.

      --
      unfinished: (adj.)
    11. Re:This sucks. by lspd · · Score: 1

      What I'm saying is that Reiser wants people to believe you can require that advertising isn't removed from your GPL code. If that view is accepted, then anytime someone does a patch with advertising you either put the advertising into your version or refuse their patch entirely. He wants advertising in GPL software to be the same as GFDL's invariant sections. If someone submits additions to your GFDL text with a new invariant section, either you accept their invariant text or you're barred from using EVERYTHING they've added.

    12. Re:This sucks. by drunk_as_in_beer · · Score: 1

      Note that the guy you responded to plagariazed my comment from Newsforge (ironic it is). Funny thing I am defending my own argument now :)

      The only new part here is that the credit has visibility beyond those who care to look at the code.

      This is a very big change. The idea of free that I was talking about was that you can make any change you want with the software. Reiser wants to force the credits to be displayed on the screen, like how mkreiserfs does so. Now what if you want to fork the code and use it in a project that doesn't output anything to the console? You can't because his licensing clause forces you to output all his advertisements to the console. This is where the software becomes non-free (as in speech), as it violates Stallman's freedom #1, you're unable to adapt it to your own needs. The credits belong in the source code and/or documentation where they will not affect the functionality.

      I suppose this is a grey area, and basically comes down to opinion, but the way I see it is this makes software non-free. Do we really want free software to become ad-ware? If you want to write ad-ware, don't try to license it under the GPL.

      I know Stallman is all about GNU getting credit, and calling the OS GNU/Linux, so I'd be interested in his take on this.

      --
      --Drunk as in Beer
    13. Re:This sucks. by drunk_as_in_beer · · Score: 1

      Have you seen Hans Reiser's "credits" in mkreiserfs that he wants forced upon users? This is it:

      The Defense Advanced Research Projects Agency (DARPA) is the
      primary sponsor of Reiser4. DARPA does not endorse this project;
      it merely sponsors it.

      Continuing core development of version 3 is mostly paid for by
      Hans Reiser from money made selling licenses in addition to the
      GPL to companies who don't want it known that they use ReiserFS
      as a foundation for their proprietary product. And my lawyer
      asked 'People pay you money for this?'. Yup. Hee Hee. Life is
      good. If you buy ReiserFS, you can focus on your value add
      rather than reinventing an entire FS. You should buy some free
      software too....

      SuSE pays for continuing work on journaling for version 3, and
      paid for much of the previous version 3 work. Reiserfs
      integration in their distro is consistently solid.

      MP3.com paid for initial journaling development.

      Bigstorage.com contributes to our general fund every month, and
      has done so for quite a long time.

      Thanks to all of those sponsors, including the secret ones.
      Without you, Hans would still have that day job, and the merry
      band of hackers would be missing quite a few....

      Have fun.


      I formatted a ReiserFS partition a little while ago and read this. Now my first thought after reading this (especially the 2nd paragraph), was what is this idiotic drivel and who is bombarding me with this crap? And he is wants to put a clause in his license that forces this to be displayed every time you run mkreiserfs. This almost makes me want to use another filesystem.

      Now Donald Becker is alright, though, assuming he did one of two things: release his software under a proprietary license (nothing wrong with that, its not like its masquarading as free), released it as open source allowing for someone to hide the credits. However, if he were to use the license to force the credits on the screen, what if a Linux distro wanted to make the bootup hide all console messages, they can't do that as they are required to show this guys name.

      The whole point is, nothing wrong with throwing your names or advertisements everywhere in GPLed software, but if someone, say Debian or Redhat or an end user, wants to come in and remove the names or ads, they should be able to. Otherwise the software isn't free as we've come to know free.

      --
      --Drunk as in Beer
    14. Re:This sucks. by drunk_as_in_beer · · Score: 1

      hmm, yes I understand the irony of you plagiarizing my comment, when I was arguing against credit being visible in software.. But you could have at least provided source code or documentation countaining the credits. Of course, I didn't license my comment and just put it in the public domain, so I guess I was asking for it.

      In any case, MY comment got modded up to 5, even though you posted it. Which does in fact boost my ego. Not what I was aiming for in writing it on Newsforge as an AC, but I'll accept it. More proof that you don't need credit for something you did in order for it to boost your ego, you just need to see it used and have people approve of it.

      --
      --Drunk as in Beer
  17. Is this really a new issue? by sczimme · · Score: 1


    From the article:

    Have you ever worked a day job to fund other coders? Pure hell, let me tell you, especially if you are also so essential that time off becomes unacceptable.

    Have you ever worked in a place where your work was carrying/funding dead weight on a project team? Will all due respect to Mr. Reiser, this is no different, and will probably always be an issue until everyone contributes equally to everything. Even then, what are the odds that eveyone will be credited equally?

    Similarly, the project manager isn't doing his job if one person is "so essential that time off becomes unacceptable". Yes, it happens all the time; for crunch periods it may be a necessary evil, but only if the crunch is the result of uncontrollable external factors. Bad project mgmt != uncontrollable external factor.

    --
    I want to drag this out as long as possible. Bring me my protractor.
    1. Re:Is this really a new issue? by elem · · Score: 1

      I think that you are somewhat missing the point.

      Reiser's points was that if you are the one working to fund the coders then you are the one that is essential - and thus can't take time off. When other people depend apon the money you raise/make then your ability to go "Fuck it all, I'm not going to work today" is lost, in the real world this could be called "an irresponsible attitude".

      Just ask anyone who is running a small startup, or a charity or someone who is the only moneymaker for their family, they understand.

  18. I sure don't like those lame distros by exa · · Score: 0, Troll

    That replace the KDE logos. A bunch of lamers trying to pretend as if it's their shit. It's not.

    Fuckings to them.

    --
    --exa--
  19. Yes, but by I+Am+The+Owl · · Score: 2, Insightful

    legislating developers' name on a screensaver leaves a bad taste in the mouth, honestly. If I had written any significant F/OSS, I would not feel nearly as good about knowing that the license was forcing my name to be displayed on the screen. I would feel nice if someone voluntarily put it up, sure.

    Marketers would not want to "un-necessarily'" give credit. Agreed. Not every company selling (services for) open-source code might be doing it for this reason, though.

    I can think of two more reasons: (a) they genuinely think that they are reducing information confusing to the (target) user; that their graphic is good; (b) they did not realize that the developers are feeling they are not getting enough credit.

    There is merit in the idea that credit to people who write FOSS could be more prominent. There is also a gentler way to do this, IMHO. Like, "Hey Debian dudes! Good work on that release. BTW, my wishlist for the next one is a screensaver that would display names of authors who wrote the packages I installed. Here's a graphic for the background, and here's how I think one could go about it...".

    If enough people support this idea and implement it, then the need to enforce it will not be needed. If some notable exception exists, one could consider license as a way to enforce it.

    --

    --sdem
    1. Re:Yes, but by tychoS · · Score: 2, Insightful
      For a widely used program, the authors showcased would risc. receiving a lot of email from end users thanking them, asking for help or screaming at them. Due to google and friends, including the authors email in the credits is not neccesary in order for the end users to easily reach him/her.

      Of course feedback from end users is nice for the programmer and leads to improved software if the programmer is inclided to listen to the users, however receiving several thousand emails a day from end users of a widely used piece of software would be anyones nightmare.

  20. Credit by Anonymous Coward · · Score: 5, Funny

    Post continued below following legal credits...

    ----------
    This post copyright 2003 by http://slashdot.org/~anonymous-coward

    All rights reserved.

    Typing done by anonymous coward

    Browser made by contributers to the mozilla project: (see bottom of this message for a full list)

    OS made by contributers to the Linux kernel and GNU software, part of the GNU/Linux operating system.

    OS development assisted by Redhat Corporation

    Browser contributers:

    A
    Rut Kristin Aanestad, Matti Aarnio, Jason Ackley, Carl Adams, Tobias Adamson, Christopher A. Aillon, Juan Pablo Alcaraz, Sam Allen, Warwick Allison, Matitiahu Allouche, A. Ambrose, Nicholas Ambrose, Andrew Anderson, Mark Anderson, Ryota Ando, Mike Ang, Hiroshi Annaka, Peter Annema, Edwin Aoki, Vidur Apparao, Carlos Araya, Koichi Ariyoshi, Kevin Arnold, Akhil Arora, Marc Attinasi
    B
    Ninoschka Baca, Ariel Backenroth, Ryan Bacon, Rodrigo Bado, Stuart Ballard, Ralf Baechle, Bradley Baetz, Péter Bajusz, Jeffrey W. Baker, Jerry Baker, Kirk Baker, Mitchell Baker, Jay Ball, John Bandhauer, David Baron, Ricardo Batista, German Bauer, Michael Bayne, Patrick Beard, Glen Beasley, Nick Beaudrot, Nicholas Bebout, Adam Becevello, Neal Bedard, Christine Begle, Stephen Beitzel, Artem Belevich, Ruslan Belkin, Kevin Berkheiser, Juraj Betak, Pete Bevin, Gayatri Bhimaraju, David Bienvenu, Christian Biesinger, Jatin Billimoria, Eric Bina, Marlon Bishop, Colin R. Blake, Jessica Blanco, Joaquin Blas, Christopher Blizzard, Garrett Blythe, Chuck Boatwright, Brian Bober, Travis Bogard, Bozhan Boiadzhiev, Mark Bokil, Nelson Bolyard, Phillip Bond, Chris Booton, Mauro Botelho, Robert E. Boughner, Joey Bowles, Norris Boyd, Kathleen Brade, Justin Bradford, Don Bragg, Ryan Brase, Daniel Bratell, Daniel Brickley, David Brittain, Eric Broadbent, Sarah Broadwell, Tomas Brodsky, Daniel Brooks, Germaine Brown, Jeremy Browne, Erik Bruchez, Ben Bucksch, Leston Buell, Eric Burley, Edward J. Burns, Jonathan Buschmann, Grace Bush, Angela Butler-McDonald, Marc Byrd
    C
    Jeff Caldwell, Conrad Carlen, Bjorn Carlson, Laurel Carlson, Jan Carpenter, Evan Carter, Andrew Cassin, Ryan Cassin, Sudhakar Chandrasekharan, Gary Chan, Wan-Teh Chang, Milind Changire, Christopher S. Charabaruk, Serge Charapaev, Andrew Chatham, Paul Chek, Ray Chen, Tao Cheng, Alexey Chernyak, Troy Chevalier, Lisa Chiang, Hankin Chick, Sean Chitwood, Joe Chou, Robert Churchill, Ashley Clark, James Clark, Steve Clark, Richard Cohn, Pete Collins, Scott Collins, Don Cone, Alex Converse, Chris Cooper, Catherine Corre, Donnie Cranford, Tim Craycroft, Todd Crowe, Jim Crumley, Crysgem, Nicholas Cull, J. Shane Culpepper, Stacey Curtis
    D
    Steve Dagley, Denis Daly, Angus Davis, Anthony Davis, Paul Davis, Michael Dayah, Mo DeJong, John Dee, Javi Delgadillo, Tom Dell, Vince DeMarco, Prashant Desale, Crutcher Dunnavant, Harish Dhurvasula, Matthew Dillon, Patrick-James Dionisio, Steve Dobbelstein, Jeremy M. Dolan, Simford Dong, Clayton Donley, Stephen Donner, Thomas Down, Rick Downes, Asa Dotzler, George Drapeau, Chris Dreckman, Bert Driehuis, David Drinan, York Du, Alvin Duan, Micah Dubinko, Jean-FranÃois Ducarroz, Suresh Duddi, Jim Dunn, Jeff Dyer
    E
    Jason Eager, Rafael Ebron, Sean Echevarria, Brandon Ehle, Brendan Eich, Jan Eldenmalm, Rick Elliott, Steve Elmer, Joseph Elwell, Dawn Endico, Kai Engert, Jean-Jacques Enser, Beth Epperson, Harish Kumar Epuri, Ken Estes, Ramiro Estrugo, Matthias Ettrich, Jim Everingham
    F
    John Fairhurst, Gilbert Fang, Darin Fisher, David Fisher, Matt Fisher, Greg Fiumara, Werner Fleck, Alec Flett, Bret Ford, Robin Foster, Marc Fraioli, Joe Francis, Andreas Franke, Simon Fraser, Jonathan Freeman, Alan Freier, Noah Friedman, Michael J. Fromberger, Chris Fuchs, Koji Fujimoto, C. Fung, Igor Furlan, Scott Furman, Ryoichi Furukawa
    G
    Niccolà Gallarati, Jeff Galyan, Bruce Gao, Sean Gao, David Gardiner, Jeff Garzik, Claudius Gayle, Samir Gehani, Jim Gellman, Henrik Gemal, David Gerard, Rick Gessner, John Giannandrea, Bill Gibbons, Ro

    1. Re:Credit by Anonymous Coward · · Score: 2, Funny

      >now what was I going to say again?

      "First post", I think... ;-)

    2. Re:Credit by arvindn · · Score: 1

      Brilliant, brilliant! Mod that up. It's also a nice way of responding to people who insist you say "Gnu/Linux".

    3. Re:Credit by Turing+Machine · · Score: 1

      I'm glad someone else had the points to mod you up. I saw this and immediately regretted that I'd blown my last couple of points earlier today.

      Bravo.

      Although you did leave out Dennis Ritchie, Alan Turing, Charles Babbage, and the guy who invented the abacus. :-)

      Personally, I'm happy with a listing in the About box and a credits.txt file in the source code for my projects. If someone really cares who wrote the code, chances are they know where to look.

      I hate software that makes you sit through a credits splash screen every time you start it up. Even if it's just killing time while the rest of the code loads, it starts to get pretty annoying the five hundredth time you see it. Rather than admiring Joe Hacker for porting the flux frobnicator module to INTERCAL, you begin to detest the sight of his name.

      (I used to put splash screens to projects, but I got better)

  21. Have to draw a line somewhere by Anonymous Coward · · Score: 0

    Imagine if every page served by Apache were accompanied by a page of credits? Eeek!

  22. Oh please by Fefe · · Score: 5, Insightful

    Reiser has already lost countless users for his software because he started polluting the kernel messages with "a message from his sponsors".

    He should be more concerned with the quality of his software, not with his ego problems. Personally, I find this disgusting. If someone wants to know who wrote the software, he can read the README or ask google.

    I don't even have the slightest reference in my free software source code that point back to me, I don't even use huge copyright comments in my software like the GNU project generally does, and yet people have offered me jobs and asked me about my software many times. In general, the people who want to know who wrote the software, do.

    Those who try to rub it in their face all the time will cheapen free software for everyone. It's like the "I'm so important!1!!" freeware movement from MS-DOS, and I barely remember a single author from all the software that rubbed their copyright messages it in my face all the time. In contrast, I even learned to know several free software authors personally!

    Hans, people are losing data with your file system. I know because I did. Twice. Then I looked at your fsck code and it stunk to the high heavens. You should be concerned with that, not with putting your name in the face of more people.
    And what would be the next step? To insert a few seconds delay so people have a chance to see your messages better? Puleeze!

    1. Re:Oh please by Fnkmaster · · Score: 1
      Yeah, I mean nobody will ever know who wrote ReiserFS - it sounds like this guy has a bit of a chip on his shoulder and ego problem going on. I think the whole "mandatory credit" thing was tried with the original BSD license, and it just becomes an onerous task because of the large number of contributers, copyright holders, and so on.


      I am all for giving credit where it is due, and I think commercial Linux distros should make a serious effort to thank those who've made their products possible, and contribute back to the community. Of course ego fulfillment is one of the major motivators for working on Free Software projects - but it's not the only one, and making the Free Software so onerous to use that it becomes onerous to use is not the right way forward. The motivation to work on something that other people will build on top of and make into something better as a whole than one person could do themselves is a big part of the appeal of Free Software. Let's not pollute important projects with licenses demanding all sorts of overblown ego fulfillment and stroking. A brief copyright note in the kernel message, or a Help->About dialog in a GUI app is plenty of acknowledgement for the majority of Free Software authors.

    2. Re:Oh please by DarkVein · · Score: 1

      As another commenter wrote "This can be tastefully done easily" as Hans has never done. My first exposure to Reiser was the kernel module info page, which, paraphrased and summarized said "if you want features, pay us money and we'll put them in". I had never seen an advertisement in GPL software before, and thank god I haven't seen one since. That stunk of unprofessional, badly designed code. The evidence is in the word-of-mouth reviews: ReiserFS has become incompatible with itself several times even after it was accepted into Linux (WHY?), people lose data, the tools constantly change: sometimes safe flags become dangerous flags between point releases.

      If there's a point to be made, Reiser is not the one to make it.

      --

      I'm as mimsy as the next borogove but your mome raths are completely outgrabe.

    3. Re:Oh please by anoopiyer · · Score: 1
      Hans, people are losing data with your file system. I know because I did. Twice.

      I did too. I had to reinstall everything and during the reinstall, decided to go with ext2. Disabled my HDD's write cache for good measure.

    4. Re:Oh please by Anonymous Coward · · Score: 0

      The nature of fame is that only few have it. The nature of open source software is that many contribute. There are a few who have the mindshare of the users and many who don't. That's similar to the long credit list at the end of a movie: All directly involved people are listed, but only the few stars among them are, well, stars. Are they stars because they are so much better? To a certain extent, yes, but very often it's just visibility. Much like real life stars sniff at others' publicity stunts, you're discouraging the attempts of the lesser known contributors to grab some mindshare by something other than excellence. What makes people take that route? The feeling of getting short-changed. They do a lot of work and get essentially nothing in return, while some diva's fame is based on their work too. They would get paid in real life and that compensates for a lot, but not so in the open source world. The question is: What needs to be done to keep the lesser-known contributors on the team? Is the remote possibility of fame really enough or does the mindshare need to be more evenly distributed? If personal recognition is not the way, then what incentive is there? Or is open source really another attempt at building a society on altruism? If we don't find answers to these questions, we risk ending up in another cycle of ego-freeware.

    5. Re:Oh please by Anonymous Coward · · Score: 0

      Here here! I tried ReiserFS- thought it would be good cuz it's always in Linus' kernel .config, and it was easy and listed as the default in the Slackware setup menu. Ugh!!! Horrible corruption. Problem was caused by Windump/ MS "format"- still have no idea why "MS format" decided to format a partition marked "83", and not the partition I told it to. Anyway, horrible problems with cryptic error messages, version incompatibility, endless loop of utility result messages (A needs B needs C needs A), issues with different kernel versions, and finally different (varying) results each time utilities run. Read the "gotchas" if you want a laugh! Lesson learnt.

    6. Re:Oh please by Gojira+Shipi-Taro · · Score: 1

      I have lost data to ReiserFS as well. Drive was so badly wacked out from a power outage during a write that I'll have to completely zero write it again just to get a filesystem on.

      Bad time for a UPS to fail. I'll never use ReiserFS for anything again.

      --
      "Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
  23. That would explain it... by Steffen · · Score: 3, Informative

    Here, go read:

    a fairly unpleasant thread started by Mr. Reiser himself.

    He has a point, but surely it doesn't hurt to be slightly less aggressive on these matters. Unless he enjoys being credited as an asshole...

    1. Re:That would explain it... by Schubert · · Score: 1

      *shrug* It worked for Theo.

      --
      -- schubert
    2. Re:That would explain it... by shallot · · Score: 3, Informative

      Actually, that's the fragment of the thread from the (entirely offtopic) debian-testing mailing list. Here's the full thread on the debian-devel mailing list.

  24. Good idea, but... by ectospasm · · Score: 2, Interesting
    I don't think it's enforcible. If you make giving credits a requirement to use such-and-such a license, a developer will just create a new license without that restriction.

    And, you'd have balkanization on how it should be implemented. Boot messages? Splash screens? If users get annoyed with these, they'd want to turn them off, and someone would find a way to do so. If a user wants to know who wrote a piece of free software, many times this is not difficult to obtain.

    I guess I just see it as being unenforcible and unnecessary.

    --


    We are the music makers. We are the dreamers of the dreams.
  25. I don't write "Creditware" by danielgast · · Score: 1

    I haven't written very much code that I've opened to friends / others to distribute, but the bit that I have hasn't even had my name in the source code. I don't write "Creditware" and when I think of people who's projects are driven by their egos rather than a desire to just get a job done I think of software packages that are generally full of flashy features with questionable reliability and are the most aggressively defended when people want to add a feature that doesn't align closely with the author's original intent (which makes sense because the more the author's name is attached to it the more you're affecting his/her identity with your feature).

    This said, I'm certainly not against respecting authors identities and their wishes WRT maintaining any branding they choose for their product, but if someone's version of a program is going to pop up a page of text enumerating their life story, possibly obscuring some warning message I really should be reading, I'm going to look very hard for alternatives.

    -Dan

  26. "Linux software" ??? by semanticgap · · Score: 5, Insightful

    From the article: I propose that we as a community insist that all distros make the default screensaver be one that randomly displays a different detailed credit for one of the authors of Linux software every 60 seconds.

    Erm.. Is Python or Perl or Apache or Emacs - "Linux software"? What about FreeBSD or OpenBSD - that's hardly "Linux software"...

    I'm surprised to see someone as knowledgeable as Riser make such a blunder - or is it intentional?

  27. Re:OSS belongs to the community--that IS enough by Silent_E · · Score: 2, Insightful

    vosbert has a really good point. I like the idea of things belonging to the community more than to any individual person. Yet there is a way that an analogy should be made to art here. If you like a sculpture, or a piece of code, you should be able to find the artist/designer. So, perhaps v would say that having credit in the source code is enough, that anyone who really wants to find the designer, could. But the name of the artist adds to the work (yet perhaps only for marketing reasons?)

    I spend a minute being torn.

    I thought that I was going to post that while Reiser's suggestion that linux have a mandatory screen saver that flashes credit is totally micro$oftesque in its totalitarianism, but his point is well-taken, and oss designers deserve credit. Instead, your comment really convinced me. Anyone who wants to find the designers can by looking in the source code. What user would be searching for a designer who couldn't get it togeher to look in the source code? And what *other* sort of person would care who wrote linux or anything else? The glory of OSS comes from being a shared project in every senes. Let's keep the focus on that. Kudos to vosbert for convincing me.

  28. I can see it now.... by RdsArts · · Score: 1

    "This edition of KDE is brought to you in part by Tide(TM). Tide(TM), it's the Tidest. And also by the financial support of coders like you."

    1. Re:I can see it now.... by user+no.+590291 · · Score: 1

      But it's not a commercial. Because NPR and PBS are commercial-free, by definition.

  29. Adobe by Anonymous Coward · · Score: 1, Insightful

    Open up Adobe Photoshop. You will se a list of names on the splash screen, I assume they are all contributing producers, engineers, and coders. Am I right? It is also in the about screen of most porgrams, give credit where credit is due.

  30. Haven't We Been Here Before by Carnage4Life · · Score: 4, Insightful

    It seems history, even short term history repeats itself. This was tried in the past by the BSD license and was taken out because it is way too onerous. The problems with requiring such credit are well enumerated by the Free Software Foundation in the essay entitled "The BSD License Problem".

    On the surface, it sounds like a good idea until you consider what it means to give prominent credit to all the major people who are involved with a piece of software. The larger a project is the larger the number of active participants. More importantly when a project gets large enough it acquires dependencies that provide significant functionality which also are as deserving of credit as the original application developers.

    For example I built a news aggregator that is an now a source code available project on GotDotNet that has 70 developers signed up with about a dozen having been active in one shape or the other. There are also dependencies on three external libraries that also provide significant functionality. If this was a commercial product exactly how feasible would it be for me to give prominence to everyone who provided significant value to the application? What metric would I use?

    1. Re:Haven't We Been Here Before by Ed+Avis · · Score: 2, Interesting

      On the other hand, one of the big advantages of free software is that you can find a *named person* responsible for each line of code and if necessary contact that person directly, rather than some moronic 'helpline'. So the list of credits should definitely be there... But I don't agree that this goal, however desirable, should be enforced by licensing.

      --
      -- Ed Avis ed@membled.com
    2. Re:Haven't We Been Here Before by Pflipp · · Score: 1

      Another very realistic example: try the GNOME about menu, if you still have one in your installation. It scrolls in some attractive manner through all the GNOME developers in alphabetic order.

      The attractiveness is well over once you have passed the B, though. I imagine developers with names starting with Z's constantly falling asleep when trying to check if they're credited.

      --
      "We can confirm that Debian does *not* ship the version with the trojan horse. Our version predates it." [CA-2002-28]
    3. Re:Haven't We Been Here Before by Kashif+Shaikh · · Score: 1

      This doesn't only apply to software but video game software as well.

      I mean, how can you credit one person when it took dozens of programmers, designers, content creators, etc. to make the game?

      This was one of the gripes with "American Mcgee's Alice". I've read one of the developer interviews, and they were dissatisfied with the title as it attributes the entire creation to one single man.

      Kashif

    4. Re:Haven't We Been Here Before by dh003i · · Score: 1

      So what, naming everyone involved is a lengthy process? Some recent papers based on genome-wide microarray methods have 40 or more authors (see Science and Nature). That doesn't mean they shouldn't all be credited. Everyone involved in the project should be credited in the about section. This is simply academic honesty. We need to establish some strong ethical guidelines on how to attribute proper credit.

    5. Re:Haven't We Been Here Before by black+mariah · · Score: 1

      From what I understand, American McGee wasn't all that thrilled with it either.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    6. Re:Haven't We Been Here Before by Anonymous Coward · · Score: 0

      I think Reiser is familiar with the BSD problem, because he does not propose that the names of all contributors be displayed. He is proposing that the names of randomly selected contributors be displayed, on the default bootup and screensaver.

    7. Re:Haven't We Been Here Before by Ben+Hutchings · · Score: 1

      The starting position should perhaps be randomised so developers with later surnames get as much exposure.

      Mozilla's About page just links to a page of credits which one can scroll through at leisure. This is probably a more sensible way to present the list.

      Perhaps categorisation of the areas in which people worked would be helpful to users. The credits easter eggs I've seen generally do this.

  31. Clearly Hans has gone senile... by The+Fanta+Menace · · Score: 1

    Screensavers with credits? Splashscreens with credits?

    No-one wants this shit. If Hans wants to put it it reiserfs, let him feel free to, but I'll compile it all out, or switch to XFS.

    --
    -- Even if a god did exist, why the fsck should I worship it?
  32. Ho-Ho Man! by Anonymous Coward · · Score: 1, Funny

    I've seen your work in Legend of Zelda: the Wind Waker, sir, and I have to tell you, I'm impressed.

    Get your dick outta the peanut butter, cause you're fuckin' nuts!

    1. Re:Ho-Ho Man! by Anonymous Coward · · Score: 0

      OMFG have you seen the Halo 2 trailer it's like slow and it's telling you all the stuff you did in the first one then the music kicks in and and the chief comes out and gets a gun the earf is on fire and chief is like fuck this im jumping and HE JUMPS PUT OF TEH SPACESHIP with angels singing and he lands on the bad guys and that annoying ai lady is like GO GET EM TIGER! WILDCAT IS ON TEH SPOKE!!!~`1 and theres less polys but rawkin bumb mappings you can view this on a special MICROSOFT xbox disk that comes with EB games store.

  33. [Slightly OT] ReiserFS question by Anonymous Coward · · Score: 0

    Does the ReiserFS in Linux 2.6 supports files as directories? And does it support really small files efficiently (i.e, you could convert an XML file into a directory tree and it would not be any less efficient)?

  34. A little confused.... by wiresquire · · Score: 1

    a) If it's an OSS project, then if they're using a source control system, can't you see who wrote it? Or maybe there would be mailing list where someone could ask who wrote this cool code?

    b) I just have this horrible vision of millions of lines of credits buzzing past the screen as Linux boots...

    Give them credit, sure. Congrats to all the authors of the software on my box. But perhaps we are confusing who will see it, and whether they care. Having credits != giving credit.

    a) above is for those that really want to give credit. b) is merely gratuitous self praise.
    (Yes I did read the linked discussion)

    --

    So does Anonymous Coward have good karma?

  35. For God�s sake, just get off the screen! by pabtro · · Score: 2, Interesting

    From the article:

    "I propose that we as a community insist that all distros make the default screensaver be one that randomly displays a different detailed credit for one of the authors of Linux software every 60 seconds."

    This will certainly be the doom for open source software, specially Linux. Would you, or any company use software that displayed beards and glasses every minute? Let me answer that for you: -For God's sake, I'll pay for It! just get off the screen!

  36. I write code, that's it. by taxtropel · · Score: 2, Interesting

    I don't need people to see me in some splashs screen. In fact I presonaly hate splas screens, and remove them from every opensource project I use. It would be nice to see an "about" dialog w/ credit to thoes who helped, but to make something like that mandatory is rather asburd, and pointless. An example situation is found above; The developers will just make a new liscens w/o the "credit clause". Mr. Reiser isn't the first to suggest this, but his FS is used by many (not me tho, I don't like it)

  37. Money by Anonymous Coward · · Score: 0

    ``Money is unimportant only to those who don't work to create it."

    Right on, Mr. Reiser.

  38. No one cares by I_redwolf · · Score: 2, Insightful

    The users of the software probably won't care and most authors who write software really don't do it for fame or they could just plaster their names all over the software (which I rarely see). Perhaps there is something else motivating people to write software.. for instance.. If I sit down and write a zeroconf enabled server daemon for whatever it's probably because I need it or want to use it. Not for fame, because honestly, I could care less who used the shit so long as it worked for me. The blood, sweat and tears pays off in being able to have zeroconf enabled whatever. If other people can benefit then thats great, if they can help make it better thats another plus and if it helps someone else solve a problem in shorter time or makes their life easier then that's gold right there. Usually you get dumps of email from people thanking you for something you just wanted yourself.. It's great.. You get bored? Feel like moving on?? People who were helping with code tend to take up the slack and so the cycle continues.

    If people want to know who wrote the software they'll just look it up. I mean in GUI software there is an "About" dialog that exists solely for info such as stuff in cli utils at the start of the program you can put name of author and email address as most other people do. Or through it into a --help argc or something.

    Also the idea of having someones name plastered all over your personal computer doesn't make it feel that personal anymore. A user will just begin to tune the shit out, and if you write shit like BIND or BitchX etc you catch enough flack.

  39. Let me get this straight.... by Anonymous Coward · · Score: 0

    The idea is to 'advertise' Linux software?

    Great! So long as on FreeBSD I don't have to see "This GNU/Linux software brought to you by." I'll be happy.

    If I wanted an 'advertising clause', I'd still look to the 4 clause BSD licence.

  40. I don't need credit by Anonymous Coward · · Score: 1, Funny

    Only the insecure and hardup feel the need to take credit. Look, I'm gifting the world with this post, and by remaining anonymous, I'm not even taking credit for it.

  41. Control or free software. by YoungHack · · Score: 3, Insightful

    I don't remember who said it on the Debian mailing list, but the sentiment was right:

    You can either have control, or you can write free software.

    Period.

  42. People First by yintercept · · Score: 1

    A great deal of modern philosophy holds that individual egos are bad. We need to supress the individual for the good of society. Companies never mention anything about who their employees are. People are anonymous drones behind the corporate brand, etc..

    That we do so much to suppress the individual is the main reason why some many people find Ayn Rand a breath of fresh air. It is wonderful to read a work that extols the individual, even if the work gets a bit silly at times.

    Except for a few CEOs, the whole computer industry has been pretty much faceless. I think it would be great to see more faces and names attached to computer software. I would hate to see slathering, but a longer list of references would be interesting.

    The downside, of course, is that only the names of avid self promoters will make the list. A great deal of free software is created by someone reverse engineering or often copying code from others. There is also a tendency of people claiming the title System Architect to snag ideas from coders and testers.

    It is disheartening, when you are in the trenches, to see someone you despise using your work in their self promotions.

    When you get down to it. The majority of foundational work in computer science has been done already. To a great extent the work that goes into OSS is porting ideas between platforms, honing ideas and testing. The names that would appear today would largely be the names of people who are porting technologies between platforms.

    The legitimacy of the names will always be in question, but I like the idea of greater recognition for the people behind the scenes. I think it would be great for people in the world to know programmers' names along with the CEOs and venture capitalists.

    1. Re:People First by dwillyson · · Score: 1

      On the contrary, a lot of people from the computer industry who were programmers are quite well known today. Examples of this would be Bill Gates (a prodigious hacker in his time), Larry Ellison, Linus , Stallman etc.

      A lot of people in this industry have been featured in news on radio and t.v. including hackers, crackers etc.

      So your assumption that only CEO's names are well known is not true. Besides the reasons why CEO's are known is because of their job function and not their popularity. Their job includes addressing conferences, shareholder meetings, giving press interviews and appearing on t.v.

      Would you rather interview a programmer in a company to know what the company's future plans are or how the current recession is going to affect the companies bottom-line ?

      Please understand the differences before quoting from books to justify your claims.

      How many engineers names do you know who built damns or roads or other such important infrastructure ?

      This is true about any field you can think of except maybe fashion and photography.

    2. Re:People First by yintercept · · Score: 2, Informative
      How many engineers names do you know who built damns or roads or other such important infrastructure ?


      Engineers and architects off the top of my head: Frank Lloyd Wright, IM Pei, RF Walters (Hoover Dam), Gustave Eiffel, Edward Deming, Filippo di ser Brunelleschi, Alberti...

      In mathematics, the most abstract of all studies, you will find almost every major theorem attributed to a mathematician. The same is true in physics, biology, paleontology, etc.

      More important than the people who achieve super star status, there has been a long tradition of crediting architects and engineers for designs.

      Notice the historical registers for buildings. They often mention the architect. I am not just referring to the historical markers. If you go into the buildings, you will often find a corner stone or plaque commemorating the architects.

      Generally architect firms list their partners. This is becoming less and less the case. The engineering firms of yesteryear generally listed their journeymen engineers. You will find traditional engineering firms were named after their engineers.

      I have to mention things in historical context. Throughout the 1900s various socialist, prolitarian and new think movements went into an extreme anti-individual movement. This movement labelled the attribution of works to people as egotistical. (especially for middle class occupations like engineering).

      Crediting engineers and other workers was considered extraordinarily bourgeoise.

      Ayn Rand wrote in reaction to the new think of her day. So she stands as a very good historical reference point in the debate.
    3. Re:People First by m94mni · · Score: 1


      Sure, but the thing is already called ResierFS. How many theorems in mathematics contain a list of sponsors?

    4. Re:People First by dwillyson · · Score: 1

      Well when I posed the question about "how many engineers etc do you know", I meant the general public. If the whole question is about how a select few know about the contributors of a project, then I think this already happens. People who are the main contributors are well known in the hacker community and even amongst the power users.

      And if the debate is about mentioning every tom, dick and harry who contributed a line of code in a project, then i think it is just noise and so companies like redhat have a very good reason for removing this noise from their end product.

      Would you want to wait a couple of hours so that everyone who ever contributed code to every program installed on your computer gets his/her due before you can do anything useful ?

      Besides as others have already pointed, GUI based programs generally have Help->About dialog mentioning the credits.

      Non gui programs can have a switch similar to -V for version info mentioning those who have contributed significantly to the code. But listing every coder who contributed atleast 1 line of code is insanity and actually takes away from the approach.

      Also reiser is actually including an "Advertisement" with his code. Here's the thing which was removed by Debian which resulted in the controversy.
      ---- Start of shameless advertisement ------------
      The Defense Advanced Research Projects Agency (DARPA) is the primary sponsor of
      Reiser4. DARPA does not endorse this project; it merely sponsors it.

      Continuing core development of version 3 is mostly paid for by Hans Reiser from
      money made selling licenses in addition to the GPL to companies who don't want
      it known that they use ReiserFS as a foundation for their proprietary product.
      And my lawyer asked 'People pay you money for this?'. Yup. Hee Hee. Life is
      good. If you buy ReiserFS, you can focus on your value add rather than
      reinventing an entire FS. You should buy some free software too....

      SuSE pays for continuing work on journaling for version 3, and paid for much of
      the previous version 3 work. Reiserfs integration in their distro is
      consistently solid.

      MP3.com paid for initial journaling development.

      Bigstorage.com contributes to our general fund every month, and has done so for
      quite a long time.

      Thanks to all of those sponsors, including the secret ones. Without you, Hans
      would still have that day job, and the merry band of hackers would be missing
      quite a few....

      Have fun.
      ------ End of shameless advertisement ------------

      Now would you like to see the corner stones in the building mentioning something like this ? What you are talking about is crediting those people who have contributed quite significantly like : Miguel de Icaza for his work on many significant projects. This is totally fine and can be done by having a web page mentioning the chief contributors for each project, maybe even having their pictures and a brief about them.

  43. important for tips . by Anonymous Coward · · Score: 0

    If the "gift economy" is to take off, you need credit--and it needs to be trustable. Think about it, crazy faith healers make tons of money from donations--why shouldn't free software developers? I'd rather it be slathered with begging for donations (not registration) than for advertisements.

  44. No! by arvindn · · Score: 2, Informative
    RMS has a detailed analysis of why the BSD advertising clause was a very bad idea in practice.

    Speaking for myself, I certainly wouldn't want to slap such a clause to anything I wrote. First, I think the egoboo factor is totally overstated. For instance, I wrote a small vocab building app called gretools. I wrote it to scratch a personal itch: to help me with my gre preparation. Ego satisfaction had nothing to do with it. I released it only as an afterthought. Second, what's the point of having J. Random user being being forced to see your name? If you want to build a reputation as a programmer, you would want to build up that reputation with other programmers, which is what you get currenty because your name is in the source. In suspect, most users could consider it as unwanted ads/annoyance. We're trying to get people to use OSS by removing annoyances (like popup blocking), introducing our own forms of annoyance is self defeating. Third, Reiser specifically wants political statements irremovable and visible to users. This is bad. Being free means creating software without trying to impose your idealogy on others. There are practical problems too. You are unnecessarily limiting your user base. If, for instance, your political message included praise for the Falun Gong, it could well lead to any distro that includes your package being banned in the PRC, because you made your statement irremovable. I wonder how many programmers would choose to adopt such a license. Fourth, OSS companies are trying hard to stay afloat and make some money. The better these companies survive, the better your chances of becoming/staying gainfully employed coding Free software. Give them a chance. Don't view them as capitalist evil and impede them from establishing a brand.

    That's just my opinion. You are free to pick your license.

  45. Credit is Fine by oaf357 · · Score: 1

    Just don't slatther up code with it. Put a credits page up on your web site and be done with it.

  46. I am so sick... by Mister+Transistor · · Score: 4, Insightful

    I'm so sick of people trying to cram ads down my throat just because they feel they can get away with it.

    Whether it's pop-up ads, spam, TV inset-credit ads, junk mail, telemarketing, ATM fees, TV channel logos, billboards, etc. The long and annoying list goes on and on and keeps growing.

    More and more, I'm getting pissed off about the multitude of intrusions on my time and attention. If I cared about whether brand A was better than brand B, i'd look into it myself, otherwise it's just an annoyance to be so informed.

    If anyone is particularly interested, or if the software is remarkable in some way, i.e. small, useful, or innovative, then people will find out who's responsible for authoring that piece of work if they care.

    But if they don't, then they don't want to endure YET ANOTHER GOD-DAMNED AD.

    If the software authors want credit for their work, that's fine, I don't begrudge them that. I'm a software author myself. In fact, I co-wrote one of the most popular ray-tracing programs out there, and my name is on the list of contributors.

    The actual software never had my name in it, just in the docs, but people knew me, and had no problem finding out who I was and how to get a hold of me for questions and advice.

    I still can list the software on my resume, if I feel that it's relevant to the position I'm seeking. When I do, most people recognise or have heard of it. The fame is still there waiting, bottled up until needed :)

    Anyhow, without being overbearingly egotistical, I managed to get and enjoy my 15 minutes of fame without pissing anyone off and without cramming my name down everyone's throat.

    --
    -- You are in a maze of little, twisty passages, all different... --
  47. Not the first time.... by Anonymous Coward · · Score: 0

    http://slashdot.org/article.pl?sid=00/05/03/084322 8&mode=thread

  48. i have 2 words to say by Anonymous Coward · · Score: 0

    fucking. egomaniac.

  49. Reiser by G3ckoG33k · · Score: 1

    Yes, today I associate the name Reiser with the Reiser filesystem. But, first I thought of a French cartoonist Jean Marc Reiser (see a tribute page[no, I'm not French]). If you haven't seen his cartoons before, go check them out. Beware, it is dirty underware humor, literally, and any connection with file systems seem farflung indeed.

  50. An alternate proposal? by Drathus · · Score: 1

    Why not just have someone register and maintain softwarecredits.org and then request that distro maintainers and FS/OSS browsers ship with it as the default webpage. That way people will know of it, and they can still change the default page if they want?

    Or is this too logical? =P

  51. my POV by FooMasterZero · · Score: 3, Informative
    I personally think this is silly really, and I have one piece of OSS under my belt. I do use a splash screen however it is easily turned off and all it does is show the product name, no different than Mozilla's splash screen. Credits about me or any other contributers are contained in the respectable 'About" screen of my application.

    Personally I feel credit is given to me in various ways.

    1. Downloads counts stay fairly consistent and gradually seem to be rising.
    2. Occasional email saying that they like it or even better sometimes coupled witha request for new feature or bug.
    3. Simply doing a google of my project shows sites all over the place.
    I figure people who give me credit on their own free will, by performing their own reviews and such good or bad, that certainly helps me to make better software and that is all i really want to do anyhow. It is diifcult enough to write something unique and useful these days and on top of that stand out in the mix of commerical apps. So people who have contributed to the linux kernal have obivous unspoken credit that they know companies like RedHat are using thier work, likewise with mozilla developers one being funded by AOL to some extent as wellas being used in AOL's software, to me that is credit and prestige that is pretty rare for most of the OSS projects out there.

    One day I hope to see my stuff being reused elsewhere, and as long as they just say it somewhere that i helped out, I couldn't ask for more.

  52. Should licenses protect credits? by volkerdi · · Score: 2, Insightful

    Hans has done an enormous amount of really high-quality work and deserves fair compensation and recognition for it. He's got every right to have his code display all the credits that he sees fit.

    On the other hand, the moment you say that these credits cannot be removed (or suppressed from being displayed by default) then you no longer have a fully free license. That's what the problem was with the old BSD license with the advertising clause (that used to make BSD code incompatible with the GPL until that was removed), and that's the same problem with invarient sections in the GNU Free Documentation License that caused such a stink recently. The GPL doesn't allow any additional restrictions either, and since Hans' code is available under the GPL, the best he can do is ask that people are respectful of the credits. There's no legal recourse if they aren't (other than maybe to get mad, and quit GPL'ing future versions). This leads to the question -- maybe there should be a new free software license that attempts to protect author credits while remaining otherwise free?

    That said, I'd have to say that anyone who would remove credits from free software simply because the license doesn't (or can't) prohibit it is being a rude parasite. A good member of the community has more respect for the contributions of others.

  53. well by Anonymous Coward · · Score: 0

    Just grab the source and remove the credits and recompile. Sheesh! Is this rocket science or what?

  54. from what I've seen. by Anonymous Coward · · Score: 0

    The guy (Hans) loves himself a little too much. I remeber reading some posts he's written about his FS and issuses w/ Redhat. Every time I read his posts, it just seems to come across as saying "Love Me!". Him writing this article doesn't suprise me. Don't be fooled, the article is about him, not software writers in general, I believe.
    -Robert

  55. Splash screens are no better than pop-ups by Mustang+Matt · · Score: 1

    Help -> About is a good place to list credits.
    Or maybe developers could start adding Help -> Credits menus to software.

    I do think it's important that developers get credit, but do it in a way that's not counter productive to the end users of the software.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  56. Adobe Photoshop by exhilaration · · Score: 2, Interesting
    Nobody's brought up the Photoshop splash screen - which lists quite a number of the developers, but in a very tasteful manner. I remember it because the first time I saw it, I thought to myself, "Cool, a lot of Indians were involved in this."

    I think a good way to credit a large number of developers, is to make a splash screen with the bottom quarter scrolling the names of authors/contributors. The user would simply have to click to proceed. That's unobtrusive and might even generate some interest in the user - who might one day stop and read the whole list.

    Or perhaps instead of requiring a click, have the splash screen time out after a few seconds, but put a button on it labeled "click here for the credits!" - again unobtrusive.

    But that still doesn't take care of stuff that doesn't have a GUI - like ReiserFS.

    1. Re:Adobe Photoshop by DarkBlackFox · · Score: 1

      I agree. There is nothing wrong with taking credit for great work, so long as it's in an unobtrusive fashion, e.g. Photoshop.

      I personally like Windows 3.1's credits system. It's an easter egg within the program (windows 3.1 was not an operating system ;) where a combination of clicks and buttons in the right places transformed the "About Windows 3.1" section in the help menu of program manager into a scrolling credit system displaying everyone who worked on Windows, with a random little picture to the left that featured Gates, and Gates with a rodent head. Very clever, and once I found out how to do it, I actually read the list of names, simply because it was a cool little thing not many people are aware of.

      So that's another idea, embed the credits in an easter egg type system, where certain things have to be done to get them to dislpay. Maybe then people will actually hunt down the credits simply because it's something most people would never know how to do.

    2. Re:Adobe Photoshop by Anonymous Coward · · Score: 0

      Adobe (Score:1, Insightful)
      by Anonymous Coward on Saturday May 03, @01:51PM (#5869544)
      Open up Adobe Photoshop. You will se a list of names on the splash screen, I assume they are all contributing producers, engineers, and coders. Am I right? It is also in the about screen of most porgrams, give credit where credit is due.
      _________________

      1:51 PM compared to 2:44 PM... I believe I did mention it (I was that AC, I've never gotten around to registering on slashdot)

      Unfortunately my typing sucks, so forgive me for the quoted mistakes

  57. Tough issue by dh003i · · Score: 1

    Look, people should get credit for their work. That's really a pretty simple basic moral. I don't agree with Reiser's method of achieving such (the advertisements displayed whenever using his utils), but we need to properly attribute credit.

    I'm also not sure I agree with the FSF' new documentation license that's coming out, having "invariable sections".

    It's very simple. What RedHat's doing is plaguarism. They have replaced the KDE symbol with one of their own; this implied to end-users that RedHat made it. They are effectively taking credit for someone else' work. This is wrong.

    We as a community should shun those who try to take credit for that which is not their own. I believe that Debian's current issue is that they think that the new GPL documentation license is not free, and I think they have a good argument. However, that does not make it ok to plaguarize other people's work. We should refuse to buy software by distributers like RedHat who plaguarize other people's work. Period. This is as immoral as me posting something written by Dickens and claiming it's mine. So, we should put pressure on RedHat to make more effort to attribute others for their work. We should also make a stronger effort to do that ourselves, and thank others for their contributions. And there are ways to do such that don't involve obnoxious messages (e.g., About).

  58. Adware... by cfallin · · Score: 1

    From what I can tell, this proposes turning OSS into a mild form of adware - randomly displaying credits for developers. Not as bad as, say, "free gambling online" or "eliminate debts now!" in adware like KaZaA (not Lite), but still an annoyance.

    The reason I write software is to fulfill a need that I have, not to get my name in the "most famous programmer" slot... I think many programmers are the same.

  59. Re:OSS belongs to the lusers by Anonymous Coward · · Score: 0

    "annoying pleas for money?"

    hate to break it to ya, already been done.

  60. On request by bobintetley · · Score: 1

    This seems far too invasive. I too write free software, and I'm happy that users can see credits if they ask for them.

    After all, almost all graphical applications have a "Help->About" menu crediting the authors of the software. Why not introduce a standard command line switch similar to --help/-? eg: --credit or something?

    So if a user cares, they can ask for a list of everyone who worked on the software?

    Just my tuppence :)

  61. Requiring attribution is OK; GRABBING credit isn't by Brett+Glass · · Score: 0, Flamebait

    For example, Richard Stallman's attempts to claim Linux as his own ("It's GNOOOOOOOOOOOOOO Linux! It's mine, all mine, I say!) are obnoxious and betray his lust for power and control.

  62. Is that not enough... by Anonymous Coward · · Score: 0

    that you named the software REISERfs, Mr Reiser?

    Remember what Mahatma Ghandi said:
    "I must reduce my ego to zero".

    Or maybe you should reduce yours to 'zero' and 'one'!

    Grtz

  63. Re:Give 'em the shaft by Herr_Nightingale · · Score: 2, Funny
    if authors deserve to have credits all over the free software that they created, then why stop there? Let's have popup ads on websites to give the sponsors their fair due! Let's have status bar scrollers in OpenOffice listing credits, and banners when the program is minimized - just in case using it wasn't annoying enough already.
    Take it a step further, and actually read Reiser's article.. here's my favourite part. With this little gem, Hans reveals that he is totally, unequivocally out to lunch. The rest of the article is nearly as bad..
    This is why distros drop the K from all the KDE programs: somebody else is trying to establish a brand name, and that is a market threat they want to cut off.
    Yeah Hans, it's not because the K is farking stupid or makes free software look like childish Krap; it's Klearly a Konspiracy!
    Users don't care, Hans. I skip channels, block popups, and kill adware faster than you can say "fuck the users." I suspect that many of the 0.3% of computer owners who use Linux full-time feel the same way.

    I guess that's all I've got to say on the matter.
  64. Re:OSS belongs to the community--that IS enough by samhalliday · · Score: 2, Insightful
    in the source code? you really think credits are that hidden?

    try any of these:

    program --version

    man program

    info program

    or if it has a GUI, go to "Help->About" :-)
  65. another proposal: by Anonymous Coward · · Score: 0

    how about rendering some Curly Brawl - like scenes with the developers in place of Nyo ? It would be fun...for example, Linus kicking Gates again and again and again...

  66. "Most prominently displayed" clause by Animats · · Score: 1, Interesting
    If this is done (and I don't have a strong opinion on that one way or the other yet), the way to do it is to insist that the names of the authors be displayed at least as prominently as any other information relating to the distribution and packaging of the software. If a program displays no sign of branding, that's fine. If it displays "Red Hat", it has to display the names of the authors with equal or greater prominence.

    Remember "MacPaint by Bill Atkinson"?. For years, that appeared at the top of every MacPaint window.

  67. 2 points by mhesseltine · · Score: 4, Interesting

    One, I'm currently in the process of re-reading "The Cathedral and the Bazaar" by ESR. In it, he discusses how ego boosting is by nature frowned upon. I'm surprised that Hans has felt compelled to take this point up.

    Two, as others have pointed out, there are plenty of ways for authors to get recognition in a project.

    1. About screens
    2. Help screens
    3. README files
    4. Man pages
    5. Web pages
    6. Mailing lists
    7. Developer forums (sourceforge for example)

    Bottom line: grow up Hans.

    P.S. random "unknown" hackers

    • Larry Wall
    • Linus Torvalds
    • Richard Stallman
    • Andrew Tigdell
    • Guido van Rossum
    But Hans is right, programmers don't get credit for their work. /remove tongue from cheek
    --
    Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    1. Re:2 points by autopr0n · · Score: 2, Funny

      ESR, in it, discusses how ego boosting is by nature frowned upon

      Wow, now THATS ironic!!

      --
      autopr0n is like, down and stuff.
  68. oh sh--... by Anonymous Coward · · Score: 0

    > Beware, it is dirty underware humor, literally, and any connection with file systems seem farflung indeed.

    Until a filesystem utility scrambles your master's thesis. Then they take on a cause-effect relationship.

  69. Reiser works for SCO by Anonymous Coward · · Score: 0

    how many of them out there?

  70. I support giving credits, but... by GrimReality · · Score: 2, Interesting

    I agree with Hans about the academic culture's value of giving credits. However, there are two points worth mentioning.

    1. Effective ways to give credit already exists:
      • AUTHORS and/or CREDITS file (also README): These come with practically all GNU projects, and shows up in the system documentation folders. At least, this is true with most Debian packages, and has to be true with other distributions since it seems to be something that the upstream author puts there.
      • About Dialogue: This is another place where they have credits showing at least the name of the main authors and the current maintainer. For instance:

        ZZZZ@quark:~$ chown --version
        chown (fileutils) 4.1
        Written by David MacKenzie.

        Copyright (C) 2001 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
    2. This could be counter-productive
      • From a personal perspective, I don't want my favourite developers been seen by others as egotisical monsters. Which is probably what will happen if people who care less about the authors (most users, especially the crowd we hope to convert from Windows [please don't consider this a stereotyping of Windows users but this what I have seen]) think if they are forced to read all the name every time they use a software.
      • Some of Hans Reiser's favourite licences seem to favour closing the source, which eventually means withdrawing the credits section after they claim that it is a full rewrite. Or maybe, this crdits only apply to the open-source world--maybe it is the reward for caring to look.

    Thank you.
    GrimReality
    2003-05-03 19:54:57 UTC (2003-05-03 15:54:57 EDT)

    Pardon my stupidity.
    (Score: -10x10^128, Pro-Free-Software)

  71. That won't work. by Dthoma · · Score: 2

    Say I want to run ls. Then I can just do:

    $ man ls | col -b | grep -A1 'AUTHOR' | tail -1 | awk '{print $3" "$4}'

    --

    Note to M1-ers: a curt but otherwise insightful message is not "Flamebait" or "Troll".

    1. Re:That won't work. by Anonymous Coward · · Score: 0

      And what do you do if you wan't to run man?

  72. Up to the developers. by mindstrm · · Score: 1

    The "Community" doesn't own software; the authors do.
    If the authors want their names displayed, they can insist on it. If they don't care, then why should anyone else?

  73. This is not about fair credit by John+Ineson · · Score: 5, Insightful
    "This is why distros drop the K from all the KDE programs: somebody else is trying to establish a brand name, and that is a market threat they want to cut off."

    Have no illusions -- this is what Hans Reiser is worried about, his business. The morality of giving credit-where-due is a red herring.

    The debate that sparked this off was Debian removing 20-something lines of crap about sponsors from mkreiserfs. That scares him, because it weakens his power in promoting his sponsors and his brand.

    To which I say tough. The GPL was written to ensure that users could make software serve them. If a GPLed program spews unhelpful messages, then anybody has the right to remove them. Incidentally, it's undoubtedly justified in this case, when there's a screenful of rubbish, and the program is regularly used in stressful, recovery situations, potentially on a terminal with no scrollback.

    Nobody, I imagine, advocates removing authorship credits entirely, but the GPL does not guarantee free promotion for your company, sponsors, or anything else. If that's what you wanted, you were plain stupid to choose the GPL in the first place.

  74. Will SCO sue named individuals? by PB8 · · Score: 1, Offtopic

    Maybe embedding your name in a program isn't so good an idea if it gives SCO or MSFT lawyers an easy target. Maybe rpm or apt-get could be enhanced to have an option to list developer names as it installs or uninstalls software.

  75. Keep this in perspective folks by Anonymous Coward · · Score: 1, Insightful

    We're all coders and whatnot, right? We'd all love to think that if we shove our info down peoples throats, they will bow down to our abilities. But realize that if we make our products the best we can make them and then appease our own vanity by placing our credits everywhere, the users will move to a product that doesn't place vanity in front of productivity. Our job is to solve problems and help people get work done, plain and simple.

  76. I agree.. by njan · · Score: 3, Insightful

    ..with those who take the debian line; as someone anonymously posted to newsforge, "Even the FSF's attempt to require credit in the GFDL is being considered non-free by the Debian project"; and as he or she goes on to point out, Debian ARE usually fairly thorough on principled issues like this. The point, to my mind, of FREE software is that it's free. And whilst the word 'free' has the immediate connutation of lacking monetary compensation, that's not all that the word means. For me, for something to be free requires it not to have certain other obligations attached to it; it goes against my principles - and against the karma of the notion of free software - to tie advertising into freely distributed software in this way. If authors really can't do without this manner of crediting in projects which they've contributed to of their own free will, perhaps they shouldn't have contributed to them for free in the first place?

    How many slashdot readers run adware.. and why?.. how long might it be before 'free' software which had advertising in this manner decided that 'trading' adverts with other software authors would increase their user base? Really, it wouldn't take very much bending of the rules before free software looked like free websites. And do we really want geocities on our desktops?

    --
    I am a viral sig. Please copy me and help me spread. Thank you
  77. Some minor additions to what I wrote by hansreiser · · Score: 1

    Ego is surely not the only motivation for writing free software, but it is the one that we as a community can make more effective as a motivation. Not everyone contributes to charity for the sake of fame, but respecting those who perform charity is a good thing for society to do even when reputation is not sufficient to make the charitable act worthwhile.

    There is a definable difference between credits and ads. Credits describe how someone contributed. Ads attempt to sell something other than the program.

    Credits are the clearly good part of what the entertainment industry does. Ads are the evil they found necessary, or at least the evil they desired, and maybe we won't share it with them. I personally would rather pay than be advertised to: my time is expensive. I don't mind watching credits, somehow I respect them enough to not mind them.

    This "People First" posting above describes the poetic foundation of a belief that I share, and it does a lot to convey why the members of this discussion disagree.

    I don't agree with the bottom part of what he writes though, when he says that most of the good ideas have been found in CS, rather I think that ideas multiply, and the more ideas have been found, the more ideas can be found.

    Best To All,

    Hans

  78. When it comes down to it.. by eniu!uine · · Score: 0, Redundant

    The idea of owning an idea is just ridiculous.

  79. Interesting... by Anonymous Coward · · Score: 1, Funny

    As long as it's not popup windows. Heh.

  80. DEFAULT, you idiot by autopr0n · · Score: 1

    He wants the default screensaver/splash screen to contain credits for the developers, rather then the people who packaged the distro, as is the case today. He's not saying that they should stay that way forever. Damn, learn to read.

    --
    autopr0n is like, down and stuff.
  81. What next? by Anonymous Coward · · Score: 1, Funny

    GNU/Reiser/Linux ??

  82. The screensaver could be cool by gregm · · Score: 1

    I would seriously probably run it.... unless of course it were shoved down my friggin throat. Really bad idea to mandate any default screensaver, splash screen bash prompt, etc. in a "free" license. I mean that's just about the best example of an oxymoron I could think of.

  83. Just like PBS... by The+Monster · · Score: 1

    ...Twice a year, instead of doing what it's supposed to do, the program would instead tell you how great Free Software is, and ask for your pledge to support Free Software, before continuing with the regular programming

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

  84. Re:Reiserfs by Anonymous Coward · · Score: 0

    >I think reiserfs is great.. realy, i'am using nothing else... it saves
    >so much time on diskchecking after a crash. and it does the entire
    >journal thingy MUCH better than ext3
    >
    >
    That's because you're a brain-dead buzzword-spewing bandwagon jumper from the Windows camp who's never used anything other than that bug-ridden joke of an fs called reiserfs. Reiserfs always was a joke and always will be a joke.

  85. Richard Stallman contributed tons of code by Adam+J.+Richter · · Score: 1
    [...] I can't recall any software he's written other than GNU Emacs.

    I believe that Richard Stallman wrote most of the original GNU C compiler, although it was derived partly from a portable optimizer from a 1978 Univeristy of Arizona research project.

    "GNU `diff' was written by Mike Haertel, David Hayes, Richard Stallman, Len Tower, and Paul Eggert."

    "GNU Make was written by Richard Stallman and Roland McGrath."

    "Richard Stallman was the original author of GDB, and of many other GNU programs."

  86. Reminder of what free software is... by SETIGuy · · Score: 1
    Look - the authors have a right to put their code under ANY license requirement they like. If they choose to do this - well, I just don't think the software would then qualify as either Free or Open Source software in my mind.

    Remember that free software is like free speech, not free beer. If I write an article, free speech means you can quote from it (with attribution) and you can use ideas from it (without attribution). I would be likely to allow you to redistribute it in whole (with attribution). Nothing in the term "free speech" means that you can claim authorship of it.

    I don't see why "free software" should be any different. There is nothing in the term "free software" that can be construed to allow you to claim authorship for code you didn't contribute to.

    If lack of attribution is reducing the number of developers of free software, then that is a problem that should be resolved to ensure the future growth of free software.

  87. Good point, but why license? by logout · · Score: 2, Insightful

    I agree. But why do we need to deal with this issues in the form of license requirements? It's just enough to propose the idea. The actual contributors should be taking care of the details. Additionlly, splash screens don't have enough space to hold all of the contributors. Some names might have *higher* priorities, but who will decide the rankings? Will every developer be happy with the splash screen *policy*? The random display can be a workaround here, but I don't think it's a general solution that will promote the credits of the authors. Actually, we can check the CREDITS file and the Help-About dialog box when we are wondering about the names of the contributors.

    However, it is still a good idea to let users know who are actually contributing to the open source software project. But it will be a complicated problem when this credit information display is enforced as a license requirement. Let the project contributors decide what will be displayed in their splash screen; but don't make it a license requirement.

  88. Maybe because of metadata journaling by r6144 · · Score: 1
    I have lost data on ReiserFS partitions during power failures, too. As far as I know, since ReiserFS does metadata journaling only, it may update the metadata (such as block pointers) before updating the actual data blocks. If the power failure happens after writing the metadata changes to the journal (whether they are committed to the actual location of the metadata before the power failure, or during the journal recovery after that), but before writing the data blocks to disk, then after system restart and journal recovery, the filesystem will still be intact, but the updated data block pointers will point to stale data, so that's what you will see in your (probably newly-overwritten) file.

    In contrast, for ext3 in "ordered" mode, although we also do metadata-only journaling, it is made sure that data blocks gets written before metadata pointing to them, so if a power failure happens when overwriting a file, you either see the new contents (if the metadata got updated) or the old contents (if not), no data will be lost.

    So this does not seem to be a bug in reiserfs, but it does mean that you have lower data integrity gurantees than in ext3 ordered mode (actually it seems to be worse than ext2 --- maybe something needs tweaking). Alas, few users are aware of this before they got bitten.

    Anyway, if you have some frequently overwritten and very important data (like your term paper), I think it is better to store them on ext3 (data=ordered/journal) partitions than reiserfs partitions, if you want to protect them from power failures. Also, it would be great if ReiserFS gets similar features as "data=ordered" in ext3.

    (I'm not an expert on this subject. Please correct any errors I made.)

  89. examples of more stuff you use all the time by Trepidity · · Score: 1

    He wrote a large portion of the original gcc, which you likely have used on occasion, and either primarily wrote or contributed to a huge percentage of the software and utilities you use on a day-to-day basis.

    Or to take a very simple example, the following appears in the manpage for 'ls' on Debian and many other Linux distributions:

    AUTHOR
    Written by Richard Stallman and David MacKenzie.

  90. credit aka slack by 10am-bedtime · · Score: 1
    "credit" in personal finance is more akin to "slack" in programming than to "advertisement", although it's no surprise that social dynamics of limited-mindshare systems evolve the concept towards post-facto visiblity-oriented connotations.

    the crux of the matter is limited mindshare. in an elightened society w/o these kinds of limits, slack is the better currency; slack is what allows people who know you (and your work) to shrug off minor (or even major) transgressions in favor of a postponed evaluation. lazy binding, baby!

    how much to postpone then becomes the question. presumably when you are dead there is no point postponing further, unless you've written some really good self-modifying code, or planted the seeds thereof in enough people who are willing to prefix their credit to yours. and, face it, that's something that's outside your control.

  91. A screensaver would be cool though :) by gnalle · · Score: 1
    I am not a great programmer myself, but I would love if someone took this discussion as a starting point for making a screen saver showing great faces of Free software programming. I am sure that screensaver would become a hit even if it was not forces down peoples throats :)

    Thanks to Hans Reiser for making my day more entertaining :)

  92. Re:Requiring attribution is OK; GRABBING credit is by Anonymous Coward · · Score: 0

    On the other hand, Brett Glass's attempts to discredit the GPL are obnoxious and betray his need for other people to do his (clearly day-job, money-making) work for him.

  93. Credits have their place.... by freeze128 · · Score: 1

    ...but it isn't "slathered" throughout the software. There has always been a special place for credits.

    Click Help, About.

    What is plastering your name and visage all over the software gonna do? It's going to make the users know who to hate. For example:

    "HI! I'm Peter Norton. My fantastic diagnostic software has detected a segment fault, and your program will now close, and all data will be lost.
    You can prevent these problems by using my fantastic optimization software, my fantastic Backup Software, and my fantastic hard disk software."

    Peter Norton made one really useful program in 1990, and then his ego exploded. Since then, the quality of the software has suffered, and the users now have to suffer seeing his big ugly mug everytime they run defrag.

    Oh well, it seems everything is becoming more superficial. Computer case modding has become a little out of control, and the quality of the hardware has suffered. My computer doesn't work right because it tends to overheat (no, I'm *NOT* overclocking it). I can't even buy an effective fan and heat-sink because all the fans have blinky lights, neon colored plastic, and grills in the shape of an alien head. I don't need any of those features... it's going to be INSIDE my plain beige RECTANGULAR case. I want it to Just Plain Work(TM).
    Same for software. It should Just Plain Work!

  94. This comment was plagiarized by drunk_as_in_beer · · Score: 1

    Speaking of giving credit, this comment was copied and pasted from MY comment on Newsforge. Are you that pathetic that you can't come up with your own ideas?

    --
    --Drunk as in Beer
  95. Another comment plagarized from Newsforge by Anonymous Coward · · Score: 0

    Another comment plagiarized from Newsforge.