Free Software Development Goes Public
Coming Out of the Programming Closet
I remember the first time I suggested an improvement to a piece of free, Open Source software. The testy response I got was, "Learn to program and do it yourself." This attitude was similar to that displayed by what I call "academic writers," whose fiction and poetry is so obscure that no one reads it except other academics.
But in the last few years, I've noticed a slow change in attitude among the Open Source and free software developers I know personally. More and more of them seem to be thinking in terms of writing software that is useful to others, not just what they want for themselves.
There is nothing wrong with this. Artists need audiences. So do techies. Sure, it's nice to write a "deep" piece of fiction that only top-rung English professors will appreciate, but it's also nice to write something that a whole bunch of people will read and understand, and perhaps even write you a letter or e-mail now and then that says "Thanks. Nice work."
Playing an instrument, reading a poem or performing a dramatic work on a stage in a theater full of adoring fans is certainly more gratifying than doing it alone, in private, or strictly in front of other musicians or actors.
Let's not veer off into the skeptical-but-valid "Is programming really an art?" question. Let's just say that it is a skill that takes both talent and practice, and that not everyone can do it well. In this way, if no other, it is similar to acting, singing, and other performing arts. And there is no reason talented programmers shouldn't get the same level of recognition as talented actors and musicians.
Will Success Spoil Rock Codeson?
It depends on what you call "success." By monetary standards, Bill Gates is more "successful" than Alan Cox a million times over. But I know who I'd rather invite over for a beer, and I'm sorry, Bill, it's not you. I can also think of dozens of actors and musicians whose work I think is wonderful, but who have never been (and may never be) nearly as famous or rich as others for whom I have no respect.
To go back to the theatrical metaphor, there are plenty of marvelous shows that run for months in off-Broadway and off-off-Broadway theaters without taking in one percent of what a big-time musical like Cats can earn on a single weekend night. But the small theatrical productions often have better acting than what you see in the "major" shows. The music is often more interesting. Scripts in low-budget shows are often far superior to the blanded-down words used in productions with millions of dollars invested in them, that have been tested and revised in so many out-of-town tryouts that somuch life has been squeezed out of them that all they have to offer is glitz and glitter with little or no underlying value. The soul of theater, if you will, is in people working out on the edge, going beyond the norm, thinking with their hearts instead of reading market research studies and holding "focus group" sessions with audience members.
There is beauty in putting your heart into a creation, and there is beauty in watching others respond to that creation. Whether that creation is a song or a piece of code hardly matters; the "click" that comes from connecting with an audience can and should be there in either case. Actors generally recognize this, which is why there are dozens of small stage theaters in and around Los Angeles where screen actors perform - almost always unpaid - works that would never make it onto TV or into movie theaters. There is commercial success, and there is satisfaction. The two are not always the same.
Most of the "free software" writers I know make their livings writing commercial software or from some sort of programming-related consulting. But, like auto mechanics who build race cars on weekends for fun, when they go home they work on projects of their own choosing.
Mechanics who prove their creds on the racetrack always have their pick of the best "shop" jobs. Actors who get good reviews in small stage productions tend to get steady work in movies and TV. And a programmer who has gained recognition by doing excellent free software development is likely to have his or her pick of jobs. In this sense, fame gained by writing free software has direct financial value, and if it is widely-used software, not something that will be used only by a few other programmers, that value is increased substantially.
Building a Portfolio
When an actor, musician or writer goes looking for a job, he or she is expected to show potential employers or freelance clients samples of previous performed or published work. If that work has been performed or published to great public acclaim, so much the better.
Right now, programmers, like auto mechanics, are in short supply. A resume that says you have worked for So-and-So inc. for X amount of time, and have experience with Y language (or for the mechanic, on Z make of car) will get you in the door and will probably land you a decent job. And if you're satisfied with that, fine. The world needs ordinary grunt-work coders and ordinary "do brake jobs all day" mechanics. But in either field, the plum jobs go to those who can point to extraordinary individual accomplishments.
For the mechanic, the best proof of accomplishment has traditionally been the winning race car. For the programmer, the stellar proof of personal accomplishment is a popular piece of free software.
Look at Miguel de Icaza. A few years ago he was an obscure listing in the Linux Source, best known for his work on Midnight Commander. Today he's running a well-financed startup, and I'm sure he didn't have to look very hard for backers. But his work on Midnight Commander and other free software projects, even before Gnome made him famous, was more than enough to guarantee him not only an excellent living as a programmer, but complete freedom from "industrial-style" code writing for the rest of his life.
I suspect we'll see a lot more energetic, imaginative young programmers following in Miguel's footsteps instead of going into the highest-paying jobs they can find as soon as they can find them. Will some of them be doing this so that they can reap great financial rewards later? Of course! Not everyone can be a saint like Richard M. Stallman; Jean-loup Gailly, previously best-known as the principal author/maintainer of gzip, is now CTO of MandrakeSoft. And I'm sure there are countless others whose free software fame is getting them not only kudos but excellent salaries. And there's nothing wrong with that.
Passing Batons
We can sit around and cry about how free software developers are being "corrupted" by fame and money, but it's pointless. For one thing, just as the mechanic who gets promoted to shop foreman can still build race cars on his own time, and successful movie actresses often do unpaid stage acting on the side, there's no reason for people who use free software work as a springboard to fortune to give up their prior love. And many don't. They keep on doing what they always did, after work, on their own time. (And a few exceptionally lucky ones actually get to develop free software all day long for pay, but they're still a rare breed.)
But today's free software developers are not the be-all and end-all of the idea. Free software is starting to produce enough success stories that even if all of today's luminaries end up working for Microsoft, Adobe, and other big proprietary development houses within the next decade, plenty of new ones will come along, as hungry for applause as any group of talented young actors and singers.
And as more free software developers realize that by treating users as adoring fans - not as annoyances - they can earn even more applause, there will be more users. And more applause. And more developers. And if this upward spiral can become self-perpetuating, in a few years movie stars may be asking free software developers for their autographs instead of the other way around.
I finally get a first post. Cool. Now, to be on topic, its exciting to see a new idea like Open Source evolve before our very eyes. The coming changes will prove the strength or weakness of the concept, and whether or not it will become a dominant paradigm for future software development. I am glad to be a (potential) part of this evolution since my company may well be producing software which will end up as GPLed when completed (not sure at the moment of its status). This is not a concept we would have entertained a few years ago. Viva la Revolution!
I see a problem with the fact that many vocal supporters of the open source world are basically just here because it's the underdog.
Right now, it's "cool" to do Linux so that you have a chance to diss those Windows lamers... (visit any usenet discussion about it.)
Now that Linux starts being successful, it seems that many people already look out for the next underdog. With Linux usage not being a sign of Elite anymore...
------------------
------------------
You may like my a cappella music
I know a few people who have Rob's Autograph. The view the things as prize possesions. But they also run Be in a VMWare window on a windows box, so you can't really judge from that.
-Crutcher
-- Crutcher --
#include <disclaimer.h>
So what if Microsoft opens it's source code?
Allowing the different tiers of their users the ability to use the "stock" version, or to customize it to their own likes and dislikes.
That will not make the "alternative" quite so alternative (or atractive) to new users anymore.
because post modernism is a self reflective art, and you cant evolve past it, it is the top.
The same thing applies to the open source software movement, you can't have a new underdog if the domminant group is FREE, it doesn't make sense. A ne OS, sure fine; a new language? No Problem, about time for D anywhay, but where could you go after open source?
-Crutcher
-- Crutcher --
#include <disclaimer.h>
Young? But what about old farts like me?
Jack
- -
Are you an SF Fan? Are you a Tru-Fan?
What's wrong with Open Source style development becomming commercialized? For quite a few products, it's a sensible move for the most part (depending on your choice of license), so I don't see any problems there. Corporate support of Open Source style development is the shot in the arm that many projects need - it allows people who worked on a project as a hobby to work on the same project as a job, something akin to being paid to do what you loved to do in the first place! As for the people behind the source becoming interested in making money, either from the work that they have done on Open Source style projects, or on projects independant of Open Source projects (IE - having a real job, or building a new company) - So? Most of them will continue to contribute as they have time for doing so, just like they do now. And the desire to have a decent life and not spend all of thier time struggling just to pay the bills isn't bad - nor is actually accomplishing the goal. As for the increased number of followers of the Open Source style development - I can only view that as a good thing. Yeah, new lamers come along into the scene (*SIGH*), but, new coders come along with that. More people are now working on projects. The people who did all the original work on Open Source style projects are getting credit and recognition for thier efforts. I can't see any of this as bad, and none of it seems like a corrupting influence. I'm still not sure what the point of this article was, to be honest. Was it to point out the personality of these people involved in Open Source style projects? Was it to point out that many of them are moving on and doing something different with thier lives? Was it to point out the obvious, that Open Source style development is getting a larger and larger following? I read it twice, just to make sure, and it's a very all over the road type of piece, IMHO, that seems to not attempt to address a single issue, but instead, just rambles. Next time, pick an area, and stick with it. (Yeah, you can moderate me down for that comment... but read the article again, and realize it's true.)
Davis Ray Sickmon, Jr - looking for something to read? Check out my three free novels at MidnightRyder.org
Making money on free software might be possible in theory, but in real life it's not that easy. I seem to get contacted by one or two companies every month nowadays with job offerings as a programmer (programming ordinary commercial closed source software). I don't know of any company I could apply for a job where I could be doing free source development.
;).
For every job where you get paid to write free software there are several order of magnitudes many more "commercial" closed source job offerings. And I don't see this changing in the near future either (sadly). Sure, open-source jobs might pop up here and there, but the majority of jobs available will be closed source jobs for a very long time to come.
I'm now working more than half time and studying full time, and I don't really buy into that "code free software in your free time" argument (1) I don't have any free time 2) if I had any I'd go out for beer). Besides, full time development on an application can't be compared to putting down a couple of hours per weekend.
And another point; the majority of ordinary companies don't care one bit about if you've done free source development. All that counts is experience from a commercial environment. (This is at least my experience from going to job interviews).
And the comparsion between open source coders and artists is flawed. If I'm a real good actor I can get a job at a a theater. If I'm a real good open source coder I go to work on closed software. If I'm a really bad closed source programmer I go to work on closed software (might take a little longer before I get a raise though
The sucessfulness of open source should be base on usage, not on how much the people working on it make. Microsoft is not successful, IMHO, because it makes a lot of money, but because they sell so much stuff. Of course, they make a lot of money because they sell a lot of stuff, so there is a linkage.
Apache is successful because it is wide-spread in usage.
Linux is quasi-successful because it is wide-spread in usage for servers (but not nearly so for personal machines)
Has Linus become rich? To the best of my knowledge, no. However, I would call Linux, as a open source example, much more successful than Midnight Commander (this is not a judgement about the quality of either program, just usage).
Looking at what has happened to the software industry as whole, it seems to be remarkably similar to a concept in genetics (and mathematics) known as "regression towards the mean." In this concept, a given community with a large degree of diversity (such as the set of companies in the software industry) will, in successive generations (or years), slowly move from a diverse set of subjects to a less diverse set where most companies hover near the mean in respect to various measurements. In the context of the software industry, an anomalous mutation (such as a hypergreedy company like Microsoft) skewed the mean, causing companies in the future to move towards the new way of business. Then, the widespread adoption of Open Source philosophies, (and maybe even the antitrust suit!) created a second anomoly that is balancing the mean away from the region Microsoft had skewed it to. So, to make a VERY (sorry!) long post short, do we as a movement want the mean to keep moving towards pure open source philosophies, or do we want the mean that future efforts will regress to to be closer to benevolent yet profitable companies like Red Hat and MandrakeSoft?
I really hate to do this, as it just gets more
and more off topic, but what the hell makes that
post a TROLL? Off-topic, maybe -- the Subject
and the first line.. Overall it was a good post.
Anyway, I'm glad that people are realising that
Open Source programmers who then decide to go
earn money aren't evil. Just because you like
free software doesn't solve that old problem of
needing to eat....
I think Roblimo is absolutely right to say,
There is commercial success, and there is satisfaction. The two are not always the same.
Also I've been worrying a bit about the 'negative spiral' which results only in the goods bits of the "ivory-tower" nature of software becoming commercialised and lusers getting their hands on it, etc. To see the "upwards spiral" instead is much more enlightening - "by treating users as adoring fans - not as annoyances - they can earn even more applause, there will be more users. And more applause. And more developers."
Now where was I with my book on ML...?
~Tim
--
Rushing on down to the circle of the turn
Something we need to keep in mind and watch when signing employment contracts is intellectual property agreements.
A previous employer of mine owned any work I designed and developed related to my job whether I performed the work on work hours or off work hours.
I wasn't a coder (just a router grease monkey) so it didn't concern me too much, but I suspect it could conflict with some GPL aspects if a company attempts to assert "intellectual property rights" on a piece of GPL/free software.
--
John Kramer
John Kramer
God may be my co-pilot, but the devil is my backseat driver.
This is merely another student trying to look 'cool' amongst his/her peers.
Dont dignify this with further comment. CODE - its where the value of our worth lies.
I appreciate that this is going against the dogma of the Nerd World, but what the heck - its still true. Moderators - just deal with it.
There are other measures of success than the size of your income (it's not how big it is, it's what you do with it ;-) ).
Linus is quite successful. He can have any programming job he wants, making plenty of money to live very comfortably, doing what he wants.
If that's not success, then I don't know what is.
...richie - It is a good day to code.
Its just recently that its been given a Buzz Word of "Open Source".
Open Source will only be commercialized if people think they can make money off of it.
Major companies will not give anything away for free unless they see another way to get money from something "FREE".
Visit the Arcade Restoration Workshop @ http://www.arcaderestoration.com
Ok that's how to become a great mechanic and small plays make you great actor (that waitress must the best actress there is).
But really how many people have landed good jobs from working on open source projects? Sure Rob gave a couple of examples but in the multi billion dollar IT industry there are a lot of great jobs. Certainly more than there are famous open source developers worshiped by slashdot readers.
Any job can be gotten with resume successfull previous experience open source or not.
" Conquest is made of the ashes of one's enemies. "
But those are all technology companies, and there are many programming jobs that aren't in technology companies. Almost every medium-to-large company has an IS department that has real technology problems to solve every day, and it's in this kind of results-centirc environment that Linux and its kin have flourished in the past, and they still do today.
One shining example of this is Burlington Coat Factory. They have been using Unix for about as long as there has been Unix to use. They have an IS department that is constantly creating and improving the software that they need to use every day to sell coats. They have long realized that opening the source code for many of their tools can only help them, and that by using Open Source tools that already exist, they can leverage good stable code as a basis for their own future improvements. People in thier IS department have been contributing to projects like lprng , and the Red Hat distribution. It is in no small part due to their positive experiences with these projects that they felt comfortable embracing Linux.
There have got to be plenty of jobs doing real programming work for non-technology companies where Open Source is so natural a solution that it's hardly worth mentioning, and thus rarely gets news coverage.
I do not work for Burlington Coat Factory, although I have friends that do. I do not speak for BCF.
--Chouser
--Chouser
"To stay young requires unceasing cultivation of the ability to unlearn old falsehoods." -LL
The OpenSource movement reminds me of the software industry in the late 70's and early 80's. It seemed like the only people involved in computer work were the "geeks", and most did it more for love than money (and especially for the chance to use nice hardware, which was much more expensive then). Some techies came up with cool ideas, like the spreadsheet, and formed startup companies to sell them. When some of these startups became wildly successful, the money attracted business people; and soon managers (lots of them), and marketing departments were running the companies, with the techies subordinate to them. And techies were told to stop wasting time on their "cool ideas", because there was no market for them. Besides, there were too many Windows bugs that they had to work around before the next release.
I see OpenSource as a reaction against purely profit-driven software, much of which is dull (as in how many Windows fix-it programs does the world need?) and lifeless (like, why are 80% of the game titles in the stores FPS's?). In fact, OpenSource reminds me a lot of Alternative Rock in the 80's, which finally swept away the cheesy disco and boring balads of the previous decade.
Should the new software "artists" profit from their work? I certainly believe they should. And they should also be careful to keep control of it.
There is commercial software. Commercial software operates on standard capitalism principles -- there's a demand, you create a supply, you profit off meeting the need. This system is self-sustaining because the profits of one product can keep a group solvent enough to go on to create another (or to improve further on their original design).
There's free software. This is given out for free, for whatever purpose -- bragging rights, ulterior motives (like locking people into your platform or software model), or just because you're a really nice person who wants to share with the world.
Then there's open software. This is often done for bragging rights, for philanthropic reasons, and one major added bonus -- it allows other people to help you get around the platform issue that a single person in a garage might not be able to handle (I don't have an SGI Irix machine around, but if I release something open source, I'm sure someone could pick it up and make sure it works on their Indy).
Lately, commercial software has gotten a bad rap, and open source is in the limelight. The problem is that I personally don't see open source being self-sustaining. Look at this original message -- people writing the best open source code have lucrative day jobs. What happens if open source hits the marketplace in such a fashion that software companies can't compete aside from releasing free products (cf. DoJ vs. Microsoft)? There are quite a few major software development firms out there, sustained by a commercial market. If open source is reliant on people who have lucrative jobs (and thus, the outside money to support the open source development), what happens when those jobs slim down? Are we all going to become graduate students looking for grant money for the rest of our lives?
This is not to say that I disapprove of the free software initiative, or the open source efforts. However, I do not see either of these forms of software development becoming more prevalent (Drat, I can never remember how to spell that word) than commercial software.
Worse yet, I see people's hangups on the whole free software thing has being detrimental to what they often support. Linux is a free OS. Great. How do you expect to get very high-quality applications for it if you're unwilling to shell out the money to support people doing concentrated software development for that platform? I put down $50 for LokiSoft's port of "Civilization: Call To Power" and I fully plan to purchase Railroad Tycoon II as soon as I see it. These are quality software products that deserve my money, and I want to communicate to LokiSoft (and the rest of the industry) that I, for one, want to pay for high quality software.
You can't live on high praise. For all those people giving their work out the public, THANK YOU sincerely and truly. But for everyone else, realize that free software is a privilege, not a right.
--
If it's not important, you can probably find it in...
If it's not important, you can probably find it in...
Project Galactic Guide (
Just another example of /. zealottery talking up something into what it's not.
"Those who fail to acknowledge political behavior and hierarchical structures in OSS community ignore the reality. OSS community as a whole and each project in particular are political systems with corresponding (sometimes fuzzy) hierarchical structures. That fact can explain much of what may be seen irrational behaviors in OSS movement. It can explain for example why some people distort or withhold information, restrict their output, overpublicize their successes, hide their failures, distort statistic to make it look better, and engage in activities that appear to be at odd with OSS goals."
t he_catb.shtml
http://www.softpanorama.org/OSS/second_look_on_
> If Open Source was so widely adored, we would not have to suffer a constant flow of propoganda being shoved in our faces on an almost deadly basis.
Non sequitur. The Net is full of 'propoganda'(sic) on any topic - look at Usenet.> Dont dignify this with further comment. CODE - its where the value of our worth lies.
A good suggestion (which I'll ignore) in this case - this sentence doesn't even make sense. WTF is the 'value of our worth' - and how does it compare to the usefulness of the worth of our value? Bleh.> I appreciate that this is going against the dogma of the Nerd World, but what the heck - its still true. Moderators - just deal with it.
Oooh, attitude - and with nothing to stand on, either. Go look up a thing called 'argument' - it's something which those nerdy students learn at a place called 'school'.I have written the same sorts of programs over and over again. I think you'd find it probably doesn't matter company-to-company that you are using the same code again, since you are using the same brain, so to speak.
I haven't asked anyone yet, but perhaps if you talked with your boss about it, you might convince him to let you release the code. In any case, it doesn't hurt to ask. If the project needs to be done, say as polietly as possible, you'd prefer to release it under the GPL. Claim that people who use it must also release the source, so that in fact, you could have other people work for the company...
The majority of companies don't know much about what open source development is. Heck, I had my boss say he was afraid if we wrote a game for Linux, we'd have to release the source or something. You could always point your browser to some page like freshmeat, and show how many people d/l'd your package, or to the credits list in the Linux kernel, and maybe people would think that's interesting. They might think you have initiative, but at worse, were some geeky computer hobbist, but they like the sound of people who work for free.
This mechanism DOES work. Take ISPs for example. Yes, perhaps they are "technology" companies, read broadly, but they are users. They employ techies, many of whom work on the *BSDs, GNU apps, or Linux both on their free time (the mechanic working on the weekend paradigm)as well as on work time. ISPs, particularly the small ones where being held up by the OS manufacturer can be a serious problem, have recognized and adopted open source whole heartedly. And are likewise a good example of how this can work. The recent work by MS and others to worsen the legal environment by abusing the licensing paradigm (be it within or without the Uniform Commercial Code) should drive more companies, industry wide, into this model. The large software companies have gained their monopolies at the cost of the consumer because of transaction costs. Those transaction costs have been so abused that we have collectively recognized the value of open source development. How much better to allow your techs to work on, and commit open source development on commercial time for commercial advantage, than to end up held up by proprietary software magnates like Sun and Microsoft. The "mechanic" jobs we should be looking for, if we really believe in this model, and if we can see the future, are in commercial IT space. Most companies are waking up to this reality... again.
The analogies made are a bit misleading. Try to think of programmers as music performers. RMS is like those rock stars that are not very very popular but still admired wildly by enthusiasts of music. Well, actually trying to build systems targeted primarily, if not only, at average users is like trying to become like a pop star, say Ricky Martin.
For the enthusiast your work will no more carry value. Sorry, I don't buy Ricky Martin crap. And I don't see why someone who is a "pop programmer" is really more likely to get a decent job.
After all, I've got an autograph from RMS. It reads "Happy Hacking!" and that's exactly what I want to do.
Read the GNU Coding standards some time, GNU proggys provide reasonable defaults and a basic usage but are highly flexible and contain advanced features. So... keep that in mind.
.
--exa--
I fear that Open Source as a 'movement' has a few stigma to surmount before it can really be successful in *my* eyes.
I need to be able to depend on the authors who are out there to make good on their Open Source commitments and pledges. That is, if I hear that someone's planning to do something, that it actually get done. I can't make solid plans myself if I depend on someone else who doesn't follow through. This problem exists in Industrial/Commercial software too, but not to the same extent as the nascent Open Source community that is still figuring out how to be organized.
Example One: Whether for good or for bad, there's little doubt out there that Microsoft will ship Windows 2000, and if it's not in the promised February, it won't be far behind, and press releases are made occasionally when there've been slips or advances along that path. IS departments founded on Windows NT are making plans around the expected release of Windows 2000.
Example Two: the GNU pages list a lot of what has been written, but not a lot about what is planned. A few requests out there for hobbyists to slip in some changes, bug fixes, or pick up some project ideas, but not much in the way of "you can pick up GNU HotApp_1.4.605.3.tar.z in two weeks, and it will have HotFeature, HotGizmo and HotThingy completed. HotWishItem is planned for 1.5.000.0 in two months."
Example Three: I won't say where I've grabbed this quote, but you can find it yourself with one click from the page you're reading now. It was written by someone I think is safe to call an Open Source advocate. It was written before the company that was responsible for posting it announced a pending stock IPO. It was written about ten months ago, with no visible change since then.
It's almost as if we're the pre-1988 Olympics of software. No corporate branding, no professionals in the competition, nobody but amateurs who write code for the sport of it, for the achievement of pushing the envelope. I say almost because many if not most of the developers of Open Source code are doing it in their "copious free time," not as a job or profession. The phrase "copious free time" is always said with sarcasm, because there's never enough time to get to those lower-priority things like writing code that someone else might need. Packaging an after-dinner software project doesn't buy the dinner, while packaging software written at a day-job does.
I certainly don't want Open Source to be more Industrial or Commercial than it is, but until Open Source is treated as a professional pursuit, with published goals and objectives that can be met by the people who pick up projects, then we're stuck where we are... bad as it sounds, a "fringe" group instead of a powerful force that can succeed.
[
All I'm trying to say is that I don't think OSS is as popular and mainstream as some people have proposed. I'm not saying this is good or bad, just want to throw a reality check in.
Someone tell Judy Chicago, Norman Mailer and Krzysztlof Kieslowski, I'll get the lights.</SARCASM
Post-modernism is a critical stance, subject to the whim of fashion and the dead-hand of time; art is in no way so constrained.
illegitimii non ingravare
My biggest problem is that I have to hold a real job to pay my rent and buy pizza and computer parts which blows quite a bit of my time. Does anyone else really feel like programming by the time they're done getting their brain pumped all day? Now and then I do but it leads to slow coding. I've always found I write my best code when I can do it in a solid stream. Y'know sit down and don't get up for 3 days and when you look you have some wonderful amazing piece of code. My usual attitude is once I've done it then I throw it out to the community (I've never actually licensed code but if I had anything I deemed perfect it'd probably be GPL'd instead of public domain) and let them build off of it. While some of my code has been highly used it is usually highly specialized stuff that 99.999% of people would have no idea what the description even meant. Any idea how to turn such things into a nice job that lets me code GPL'd stuff for a living?
At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
For one thing, just as the mechanic who gets promoted to shop foreman can still build race cars on his own time, and successful movie actresses often do unpaid stage acting on the side, there's no reason for people who use free software work as a springboard to fortune to give up their prior love.
How many of us CAN really continue to code freely though? My employer made me sign a contract requiring their permission for me to work on any other software projects. I know this issue has been raised before, and I can see both sides of it, but I know I can no longer send code out as often or as freely as I used to.
The most important thing about this form of advertising is that you are telling potential employers/investors that, given a completely free reign, I can create high quality, groundbreaking software
Posters have noted that you'll get a job, if you've got a good resume, open source or not. While that is true, if you're stuck doing VB hacking in Microsoft hell, contributing to other projects can show potential employers that you've got more strings to your bow.
Besides, it's fun. And that's the most important reason to me.
Can I be the only person here who spent a decade or so earning money and investing it, and is now at the point where working is optional? And I didn't even have stock options to help me out, all I did was buy bonds and stock index funds off of a salary while living an inexpensive life day-to-day.
Once you have enough money to live a comfortable life, its apparent that you can either accumulate money and rachet up your lifestyle past middle class to "upper class", or you can spent your remaining days doing things that matter to you -- which in my case, includes writing/maintaining free software (among other things).
Well, this is all very droll. We cn see the new direction that open source is taking, but the real question is "Will it survive??"
Back in the old DOS days I released some high memory drivers for the 286 (Still needed at the time so that you could access a full Meg of memory) for free to the internet and BBS'es. Alot of people used these things. Then AOL started listing them for download. Now I spent too much time responding to user mail, and on into the 486 era, I would get the occasional rude paniced phone call asking me why my program didn't work.
Those of you who run LUG's know what I'm talking about. We gave out LUG info to get noticed, and now our home phone #'s are splattered across the Red Hat pages, Linux.com, etc... Now I get phone calls at 9:00 A.M. and I work nights. Needless to say I am none too cordial when woken up. (BTW, attempts to get this info off various pages does not work. If the offending site takes it down, some other site has picked it up before then and the cycle perpetuates.)
With a market share equal to that of Microsoft would the community crumble or flourish??
The future of Open Source is much more likely going to be a corporate/individual shared effort.
For Linux to survive, the Open Source movement will need to evolve to encompass corporate culture as well. Look at Rasterman and Red Hat.
Bleach and boobaroo!
Jason Maggard
I am one of those people, and I write open source, zero cost software for electronic music composition and processing. I do this as almost a full time job (well, it seems that way). I do it because I like programming, I like creating music, and I like combining both interests in a context that is free of commercial BS.
The company I helped start has produced several hundred paper millionares, and quite a few actuals. There are stories like this happening a lot these days, and it has the potential to create a pool of programmers who can choose to do things their own way.
I don't honestly know how much impact this will have, but I think that it will have some.
--p
When did Slashdot stop becoming a news site and start becoming an editorial site for moderators who can't spell?
Lets just focus on scrapping Windows, 'kay?
You are so amazingly ignorant it frightens me. Many IS depts use Linux internally. More than you can POSSIBLY imagine. IS is not high profile. IS does not market a product to the consumer. IS has no need for advertising. IS has no need for market share. IS has no need for focus groups. IS has no need for people like you.
The original poster is correct. IS needs solutions that work, NOW, that can be debugged NOW. Not by a deadline. Not when tech support calls you back 3 weeks later with a reference to a completely useless "Knowledge Base" entry for a bug fix they have renamed "supplement". Not to meet an RFP. Not to meet some PHBs retarded marketing requirements. Get a real IS job before you even start to comment.
I think there are a few very valid points here, but the one i'm interested in is working on these projects. I'm a newbie to linux and to programming. Hell i haven't even been able to get my sound card working yet, but i'm more then eger to find a project and start cracking. The problem is, and i will go out on a ledge to say i'm not alone on this, is where to start. I don't have a good idea (yet) myself, and i don't even have a lot of coding experance yet, but i know some C and i'm willing to spend a bunch of hours over this long winter break, in front of my computer. i've always learned by trying to code in the past. I'd love to hear how some of the more influencial people, to linux, got their start. Do i just knock on someones door and ask if they need help? Especially with the widespread fame of some these programs. what if i screw up, i'll never be allowed in on a project again! well, i may be thinking about this a little too much, but i'd love to hear someone else's story.