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.
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
Then the new GPL Secured Platinum Card from RMS is for you! All the credit you ever wanted, in one small piece of code.
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.
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?
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.
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
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
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.
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!
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?
grisha.org
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?
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... --
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.
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.Overrated / Underrated : Moderation
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.