What Does It Mean To Be an Open Source Author?

lolococo writes to tell us that Laurent Cohen, founder of the open source project JPPF (Java Parallel Processing Framework), has decided to share what life is like for an open source contributor in general and little bit about what that means. "There came a time of coding, releasing, coding, releasing. The project started gathering some momentum, as a small community of users started to use it, but why was it not working in this case, or why did it not have this feature, or how could I do this, etc...? You get the drift. Oh my, now I had to start interacting with other folks! What was I to do? That started a (thankfully short) period of intense existential self-questioning. What was the purpose of this project? Why did I actually open-source it? I resolved this by deciding unilaterally that it would be a free contribution, for whomever would be interested enough to look into it. I also decided that it was my personal responsibility to support these brave folks into using the project, and to make it, as much as possible, a happy experience for them."

Comments

I'll tell you what it means

[elrous0]

No rent money *THIS* month either!

Re:I'll tell you what it means

[Anonymous Coward]

'cause you couldn't possibly spend your spare time on something like this...

Re:I'll tell you what it means

[bsDaemon]

No, it means having an always-accessable portfolio to show your skills without having to worry about making people believe you without proof, or "stealing" code from previous jobs.

It means "experience" for high school and college kids so that they can work on things other than the rather useless examples in the sheltered setting of academia.

At least, that's what it would mean if you leveraged it properly -- and that would mean further rent cheques from "real" jobs.

hell, maybe it means turning that side project into a real job that generates rent cheques -- even if those are the really, really rare exceptions.

Re:I'll tell you what it means

[Sybert42]

Good stuff, minus the cheap shot at academia.

Re:I'll tell you what it means

[chromatic]

Good stuff, minus the cheap shot at academia.

How many computer science or software development courses include anything resembling:

• Interacting with real users
• Changing requirements
• Deployment, packaging, and releasing
• Maintaining code for longer than a semester
• Prioritizing requirements
• Managing contributors
• Triaging bugs

To my knowledge, only a handful.

Re:I'll tell you what it means

[Anonymous Coward]

This is what I don't get about slashdot and being all gung-ho for open source software.

Its like "hey guys, we're exceptionally talented, in high demand, and we've spent a butt-load on our education" "let's all work for free!"

wooooooooooooo

Re:I'll tell you what it means

[Psychotria]

And that takes a lot of work. When I started my open source project it came as a bit of a shock. The first few emails I got from users were a bit of a thrill and spurred development. Then came support requests. And then every other point chromatic mentions. All of a sudden I found myself under "pressure" to implement features. It was not until I re-assessed what I was doing, and why I began doing it that the pressure lessened a bit (the project was to fill a gap and no project filled my requirements). I still listened to users, and fortunately most of the time their requests were things that I wanted to. But, at the end of the day, I was doing this for myself and I open-sourced the project just for fun and with the hope others found it useful as well.

Re:I'll tell you what it means

[alain94040]

I take offense to that. Good coders deserve to be paid for the code they write.

If the only motivation for open source was to have a shiny resume to get a "real" job, it would be a sad day indeed.

Alain.

Re:I'll tell you what it means

[thePowerOfGrayskull]

This is what I don't get I'd say that's quite clear...

Re:I'll tell you what it means

[kurisuto]

I guess by that reasoning, a womb is a useless setting for a human embryo to develop. After all, the embryo gets no experience at all with such real-world tasks as breathing, walking, or eating.

It's possible to cram so much learning into four years of college precisely _because_ things are set up so that students are not distracted with the kinds of tasks you list.

Re:I'll tell you what it means

[Icegryphon]

Exactly, You have to have a love for it. It sure will not pay the bills. Looks good a on resume imho. That is about it.

Re:I'll tell you what it means

[Anonymous Coward]

None of the good ones, because frankly: what you listed is not computer science. If you have been through a Comp Sci degree and think it is, it is a condemnation of your school or comp sci in general.

Mod me overrated please.

Re:I'll tell you what it means

[zullnero]

For me, it's 100% self-serving. I used no license whatsoever, so that's the best I can expect.

Whenever I try out an app on a handheld that has some features that look suspiciously similar to my work, it makes me well up with self-delusional pride that, just maybe, that's my 45 minutes of actual work in there somewhere.

Re:I'll tell you what it means

[HitekHobo]

Just wait. Open source software never seems to go away.

Just the other day I got an "I clicked it but it won't install" email about a piece of software that works perfectly well if you read the documentation.

The sad bit is that this software hasn't been actively developed since 2002 and I still get support requests fairly regularly.

Re:I'll tell you what it means

[poached]

And I suspect if they included all those real-world lessons that we'll see far less CS graduates, from the sheer boredom. But I wish they had included those courses in my CS curriculum because now I would be doing something else, other than programming. I realized after I started working that programming for a small semester project is very different from programming in the real world and if I had gotten the entire picture I would have said, "this looks interesting, but there is too much stuff other than programming that I have to do that I absolutely don't care about... I think I will pass." But of course not too much highly ranked CS departments will allow this because it's not theoretical enough.

I think this is also why there are so many open source programmers, because their day job just don't allow them to do what they love, or they don't have a significant role.

Re:I'll tell you what it means

[Drakonik]

But as a real-life software developer, you're going to have to deal with maintaining your code, adding features, optimizing the code, and porting it to various operating systems.

Most school courses require you to meet a fixed spec sheet, allow for terribly sloppy and inefficient code, and require no maintenance because they only last a semester.

Yes, you learn, but to follow your analogy, in college, you might learn all the nuances of getting food to your mouth with forks, spoons, and obscure African eating implements, but if you don't get practice chewing, you're still fucked.

Re:I'll tell you what it means

[SirLurksAlot]

I'm nearing the end of my (yeesh) 5th year of my CS degree, and I think the best experiences I've had which are anything close to real world are the practicum courses I've taken. I'm currently a project leader in my capstone class, and I have certainly run into many of the situations which you've described. We were handed a classroom scheduling application which was originally written in VB.NET (of all things), rewritten in C# (not much better), and is now being ported to Java (simply because that is the only thing that the IS staff at the university will support at the moment). I've already had the requirements change on me once, and I now know the joys of having to manage a team of developers who are located in geographically disparate locations (I'm talking continents here, not states). Despite the many problems that come up I wouldn't trade these experiences for any amount of typical classroom programming exercises.

I think any CS program worth its salt has these types of classes in one form or another, but I don't believe that they provide the kind of experience you need to get ahead by themselves. A lot of what you're talking about (maintaining code, interacting with users, etc) can really only be learned once you're in the trenches (I think I'm qualified to say this, if only minimally, as I've recently entered the industry), but the classes still provide a foundation to build on.

Re:I'll tell you what it means

[chromatic]

[What] you listed is not computer science.

I agree.

Unfortunately, a lot of employers seem to think that computer science graduates make decent programmers, and a lot of schools do nothing to discourage that wrongheaded idea. Ideally, they'd stop. Until then, I wish they taught practical matters of programming as well.

Re:I'll tell you what it means

[chromatic]

I guess by that reasoning, a womb is a useless setting for a human embryo to develop. After all, the embryo gets no experience at all with such real-world tasks as breathing, walking, or eating.

False dilemma.

I said that academic studies of software development rarely include the difficult issues which real-world programmers face regularly. That doesn't make academic studies bad.

Re:I'll tell you what it means

[cromar]

Amen to that brother!

Re:I'll tell you what it means

[Anonymous Coward]

hmmm... maybe you should develop a filter!

Re:I'll tell you what it means

[Anonymous Coward]

Yes, but remember the other advantages, like all the girls you get....

Re:I'll tell you what it means

[ivucica]

Indeed; I'm very disappointed by my university courses. From the real life programming stuff, we've only met SQL and databases. I don't count the introduction course into C, and even less the introduction lesson for "OOP" as a part of algorithms course (and of the OOP, we learn classes only to the level of structures with functions; no polymorphism, no inheritance, nothing!)

It's sad when the only useful course I've learned during the past two years and which I'll run into when I'm programming "for real" is databases.

Course called "Project" is closest people get to producing actual product in the three years after which they get the bachelor's degree ("baccalaureus"). Without developing for the community (not necessarily under an open source license, but it's imho preferred) people get invaluable experience they don't get at Croatian universities and schools. I don't see why it would be significantly different elsewhere.

Re:I'll tell you what it means

[elrous0]

I showed my portfolio to my landlord. He said he still needed a check or cash.

Just like any other developer, except no paycheck

[EmbeddedJanitor]

Sure the money might come, but that takes time and tends to be erratic.

People still expect some support, because you need that with software.

One word

[UnknowingFool]

Groupies. Lots of groupies. In that way it's a lot like Islam. There WILL be 72 virgins around you. Unlike Islam, they will be no guarantees that they are female.

Re:One word

[Anonymous Coward]

Mister, you ain't kidding.

Re:One word

[Anonymous Coward]

"Ah, in life you were a terrorist. Well, welcome to the afterlife. Here are your 72 women."

"Are they virgins?"

"Yes. And they have to stay that way."

Re:One word

[Profane MuthaFucka]

Allah, could I have just one experienced whore instead?

Re:One word

[techno-vampire]

"Are they virgins?"

"Yes. In life, they were all nuns, and they all have shotguns."

Umm

[Anonymous Coward]

I am going to go with "vitamin D deficient"

Re:What Does It Mean To Be an Open Source Author

[Anonymous Coward]

THE MORE YOU MOD ME DOWN, THE MORE NERDS I WILL PUNCH. SAVE YOUR KIND FROM THE RIGHTEOUS BEATING THEY RICHLY DESERVE AND MOD ME UP, PEONS, BECAUSE YOU FEARED ME THROUGH HIGH SCHOOL AND YOU WILL FEAR ME NOW. FOR EVERY NEGATIVE MODERATION I RECEIVE, ANOTHER INNOCENT NERD WILL HAVE THEIR GLASSES BROKEN AND THEIR TEETH KICKED OUT BY ME AND MY FRIENDS. NONE OF YOU STAR WARS FAGGOTS CAN STOP US.

NOW MOD ME UP BEFORE IT'S YOUR TEETH I BREAK NEXT, NERDS. YOU KNOW WHAT WILL HAPPEN IF YOU DISOBEY THE POPULARS!

faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots fuck your dumb filter faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots faggots die faggots die

        * Please try to keep posts on topic.
        * Try to reply to other people's comments instead of starting new threads.
        * Read other people's messages before posting your own to avoid simply duplicating what has already been said.
        * Use a clear subject that describes what your message is about.
        * Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)

        * Please try to keep posts on topic.
        * Try to reply to other people's comments instead of starting new threads.
        * Read other people's messages before posting your own to avoid simply duplicating what has already been said.
        * Use a clear subject that describes what your message is about.
        * Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)

die nerds die

Re:What Does It Mean To Be an Open Source Author

[One Childish N00b]

Troll or not, there something about this perfect example of a jock being foiled by technology that deserves a +5, Funny.

but there are guarantees that

[unity100]

a considerable number of them will be long haired, hairy man. and stuff about moms' basements.

Re:What Does It Mean To Be an Open Source Author

[Romancer]

I love the fact that the poster was listed an "Anonymous Coward"
Just kinda seems to underline the irony (or joke as the case may be).

Release Early, Release Often Doesn't Serve Users

[MichaelCrawford]

I'm working on a Free (GPL) audio application called Ogg Frog. If you explore the site, you'll see that it's been there for several years, but there is no software to download.

I have come down thoroughly on the side of The Cathedral in my development methodology, because I feel that The Bazaar doesn't serve the needs of end-users. It unnecessarily subjects them to buggy, incomplete software.

I can see how The Bazaar would work well for highly technical users, for development tools, text editors and the like, but not for an audio application.

I was up all night last night trying to figure out how to use OpenOffice to print address labels from a database. When I couldn't get it to work, I downloaded the 3.0.0 Beta, only to find that all the same bugs were still there.

It didn't appear to me that the label printing function had been touched by the developers at all between 2.4.0 and 3.0.0, with the exception of a native OS X print job dialog for the Mac version.

Folks, this is a supposedly mature, full-featured and commercial-quality office productivity application, published by one of the world's largest computer companies, yet one cannot do even such a basic task as printing labels from a database?

That's just inexcusible!

I've done quite a lot of work on Ogg Frog, but it's still in a primitive state, and there are lots of bugs. I fear that if I released it, not even the version I have now, but future snapshots, it would get uploaded to all the shareware sites, where it would be downloaded by unsuspecting novice users, who would find it unpleasant to use.

That wouldn't serve their needs, and further, it would give me and my project a bad reputation. Quite likely I wouldn't get a second chance: my wife now flatly refuses to use Free Software, having had such bad experiences herself with Mozilla, The Gimp, and OpenOffice.

I know that I have the greatest chance of success if I wait until I have something rock-solid before I make its first public release.

Now, that doesn't mean the software isn't being tested, or that real end-users aren't giving me feedback. I have a small circle of testers, both end users and other developers, who are testing it for me - privately.

And that's how I think every Free and Open Source Software project ought to be run.

It does mean I get a lot of crap for not releasing yet, as evidenced by Kuro5hin's A Trolled Englishman. But it's a small price to pay for what I am confident will be my ultimate success.

I share the sentiment -- mostly

[Raconteur]

I share the author's appreciation and admiration for open-source users and contributers -- for the most part. In the interest of full disclosure, I have to mention that not all of my experiences with contributors have been completely positive. In rare cases, I have had to deal with contributors who want to make wholesale style changes, or otherwise ignore the submission guidelines. It has been challenging, at times, to manage that sort of thing. Those instances are rare, as I mentioned, and I wholeheartedly agree with the author's sentiments and share his experiences.

There are two types

[WarJolt]

I believe there are two types of open source authors. The first one is the hobbiest. I think the author of this article belongs to this group. Sort of a socialistic approach. Do work for the benefit of the community.

The second is a more capitalistic reason behind open source. Companies are big sponsores of open source. Companies can derive revenue through selling support, selling hardware or supporting an open source piece and selling a close source piece of software. Ubuntu, mySQL and google are for profit companies that support open source and derive revenue from it. For example linux kernel modules are often open sourced, so hardware manufacturers can sell more parts. Often open source advocates overlook the benefit from for profit companies that build a business around open source and in some instances alienate them. The GPLv3 for example has a clause often refered to "anti-tivoization", yet they followed the rules of the GPLv2 and release
the source code to the users.

My point is that the life of a open source contributer isn't always lonely guy in a basement somewhere turning out code hoping to get recognition. It could be a cushie desk job at google.

Re:Release Early, Release Often Doesn't Serve User

[ArikTheRed]

Voltaire:

Perfect is the enemy of good

Does it mean...

[johannesg]

Doing a lot of hard work, and then getting people to bitch about it incessantly as if you were their very own personal slave, all without being paid?

Ah, I kid: back when I was an active open source developer (for fMSX Amiga, for those that care) there were plenty of nice people too. And I got a grand total of 25 DMark for my six years of work! (and that's the truth!)

Re:Does it mean...

[RiotingPacifist]

Doing a lot of hard work, and then getting people to bitch about it incessantly as if you were their very own personal slave, all without being paid?

But if there is no software you can use to do something, you have to do the hard work anyway. and your free to ignore the bitching.

I'm an "Open Source Author"

[datachild]

I'm sure there are many ways of going about open source project management. Here is mine:

I mainly write tools dealing with games and game related file formats (used for mod creation, amongst other things), and some programs on the side regarding audiovisual analysis.

While some may find the release early, release often model to work, it's too incomplete for me and I don't use it myself. What I do is:

• Do some research, grab some documentation
• Write the program to be fully functional, commenting the functions along the way
• Release the code along with the program once it is finished and thoroughly tested
• Sit back and see if any users are experiencing difficulties or come across bugs, and release the new version of the binary and source code with the fixes/changes

In short, I believe in releasing complete, stable software, and providing the source for it if anyone wants to expand it or see how a certain part is done. And, going along with Crawford's issue with OOorg, a thing like that will not pop up -- because the program wouldn't be released half-finished (let alone be in it's third version!).

Re:What Does It Mean To Be an Open Source Author

[JCSoRocks]

Hmm. I'm posting to remove my mod. I modded it "overrated". I was hoping to go for the opposite... -5 funny. Instead it turned into -1 flamebait because of the other moderation it already had. So sad!

hardheadedness a good quality

[radarsat1]

I think part of the success of some open source projects like Linux is due to the hardheadedness of the principle author. I think that generally releasing early and often is a good thing, but if you do it, you have to be prepared to be extremely honest about your intentions, and STICK to them.

That is, if people come crying to you for features, you have to remember that you have other priorities, and you can't be scared of telling people to show code or step back. Basically, TFA here is talking about feature requrests that will start appearing before the project has the infrastructure (developer momentum) to support them. In that case you have to simply say, "this feature will be available when someone gets around to coding it, I'M working on this other thing over here." In other words, you've got to stick to your guns, you can't let your users own you.

It takes a certain amount of jadedness to realize this, I think. At the onset of a new project, people want to attract attention and make potential new users happy, because they think this will help the project. But it won't; it will even be detrimental if you get "users" too early. Keep the *project's* health in mind, forget the users.. until the project reaches a level of maturity. At that point, if it's useful, it'll sell itself.

Re:Release Early, Release Often Doesn't Serve User

[QuantumG]

Just because you have no idea how Open Source works, doesn't mean you have The Answers.

The rest of us are getting along just fine without your mistaken insights.

It didn't appear to me that the label printing function had been touched by the developers at all between 2.4.0 and 3.0.0, with the exception of a native OS X print job dialog for the Mac version.

Folks, this is a supposedly mature, full-featured and commercial-quality office productivity application, published by one of the world's largest computer companies, yet one cannot do even such a basic task as printing labels from a database?

That's just inexcusible!

Here is the irrefutable evidence that you don't understand Open Source (and can't spell inexcusable). Clearly, the only people who care about printing labels are jerks like yourself who are uninterested in even reporting the bug, let alone contributing some code or other support to make it work. This is the point of Open Source.. the software is what *you* make it. Sure, someone else might be willing to write the code for you, but its up to you to let them know what you want and to provide some motivation for them to fix it. Whining on Slashdot is not such a way.

Those bugs have clearly been there for years

[MichaelCrawford]

And I encountered other bugs that were reported on mailing lists back in the 1.x days, yet were still in 3.0.0 Beta.

Looking through the OOo forums, many others have trouble with label printing as well.

I don't think the existence of those bugs has anything to do with my failure to report - and in fact I did report the bugs just a few hours after I encountered them, in my oooforum post linked from my original comment.

Re:Those bugs have clearly been there for years

[QuantumG]

There's reporting "labeling is borked!!" and there is reporting "with configuration X, running version Y, I had problem T and this prevented me from doing real work".. but yeah, if no-one is interested in fixing the bug, then no-one is interested in fixing the bug.. It doesn't matter if Sun is backing the project or not. If they don't consider it a priority then its up to you to fix it. Step up. If you can't code, post on the mailing list that you're willing to help anyone who can to reproduce the issue.. even if that means sending them any special hardware that might be required.

Re:Those bugs have clearly been there for years

[ivucica]

Beg someone to do it, code it yourself or pay someone else to do it. That's how OSS works. And don't whine; you get the application for free and you want more. Doh.

How many open source advocates...

[ibanezist00]

...actually contribute to the source of any given project? I find that for all the fanboyism that surrounds FOSS, there are very few that actually contribute time to it, then bitch incessantly when either something is wrong with the software or when something is proprietary. I find this quite hilarious.

Example conversation with many techie friends of mine:

FOSShead:"OMGZ FIREFOX IS TEH BEST BROWSARS EVAR!!1!"
Me:"Why is it so great?"
FOSShead:"CAUSE LIEK TEH SOURCE IS OPENS AND STUFF!!1!"
Me:"Do you code?"
FOSShead:"NO BUT TEH PROPRIETARIES IS TEH EVAL! TEY MAKE MONIES AND STUFFS"
Me:"Is that why Opera, a proprietary browser, far outshines Firefox, and why Mozilla corporation is recording record profits?"
FOSShead:"..."

Disclaimer: I like FOSS software too, nothing against it, I use a lot of it, and I don't code. I'm more into hardware/IT, electrical engineering side of things.

Re:How many open source advocates...

[ibanezist00]

Correction: I do code, in fact a lot, but I don't do it as a hobby or anything along those lines.

Re:How many open source advocates...

[Daniel Dvorkin]

Is that why Opera, a proprietary browser, far outshines Firefox,

Matter of taste, Personally, I think the various flavors of Moz brwosers are better right now than Opera, although there have certainly been times when Opera was ahead. Quantifying "far outshines" would be pretty difficult in this domain.

and why Mozilla corporation is recording record profits?

There may be a few ideologues who believe it's morally wrong for any F/OSS company to make a profit, but they're in a distinct minority. Most of us "FOSSheads" as you put it are glad to see F/OSS companies making money, because it shows that there's a sustainable business model there. Make no mistake, F/OSS isn't going away any time soon whether there's money to be made in it or not. But there will undoubtedly be more of it if some of it is profitable.

Your 13375P33X-ing "FOSShead" is a strawman. Most F/OSS users don't use it because it's morally superior. They use it because it's good at a partcular task, because it's available for a wide variety of platforms, and because the price is right.

Re:How many open source advocates...

[ibanezist00]

I know it's a strawman, that was the point. :-) But you'd be surprised how many FOSS fans think that way, that they somehow become morally superior by using it... And I'm glad to be seeing F/OSS making money too. My point was that those who make it out to be something it is not end up contradicting themselves in the process.

Re:How many open source advocates...

[Cal Paterson]

There may be a few ideologues who believe it's morally wrong for any F/OSS company to make a profit

I know there are a few, but I have no idea where that comes from. RMS thinks profit is important.

That said, if you don't use FOSS because of ethics, I don't think we'd find much to agree on. I do use FOSS because of ethics.

Re:How many open source advocates...

[RiotingPacifist]

You dont have to code to help, bugreport help too. while ive not done any coding yet, i do take the time to support other users and submit bug reports, hell in one case i even submited a patch.

Re:How many open source advocates...

[ivucica]

From experience, Opera is faster. On the other hand, Gecko and XUL are a bit more powerful; can't imagine life without Firebug and a few other extensions. Opera tries to hardcode them, but really, the best thing Opera does is the rendering engine itself. As fast as they can get, imho.

Re:How many open source advocates...

[sibte]

I think this is great contribution and a vital element of open source development methodology.

Like they say

[commodoresloat]

Open Source is the bomb! Linus-u Akbar!!!

The names we give

[PopeRatzo]

I've never written software (IANAP?) so I can't relate directly, but I've seen the term "author" used for someone who writes code before.

I'm curious: is this the best term to use? Is "author" a term of art in the the software world? Do those of you who create software prefer any other descriptor? Why "author" and not "composer" or "creator", "programmer" or "engineer"? I'm not aware of the various strata of people who code, but I'm pretty sure that the world of software "designers" shakes out categorically just like other fields. In music, there's "composer", or "songwriter" (which mean very different things) and "engineer" and "producer" (which can mean all sorts of things). In film it gets even crazier with "production assistant" and "producer", "director" (which can overlap), "set designer" and "art director" which can mean lots of different things, too. And of course, "best boy" which turns out to mean something quite different from what I thought when I was a movie-loving teenager.

So, would Laurent Cohen also use "author", do you think? I'm really interested in hearing from you software wizards and conjurers.

Re:The names we give

[Raconteur]

I prefer the term "developer". It encompasses most of what we do. Other terms are appropriate; author is as descriptive as programmer, I suppose. I do shy away from "engineer" or "designer", as those monikers evoke different and more restrictive facets of our profession. Referring to programming as an art form elicits strong and varied reactions from many people. Personally, I do see the field as an art form. A sculptor or painter (for example) has the joy of creation, taking raw materials and creating a (hopefully) pleasing and meaningful result. They also have the joy of experiencing their work being examined, critiqued, and possibly purchased by total strangers. And, they have an appreciation for the hidden beauty of the work that the audience never gets to see -- the minute changes in texture of the canvas or the structure of the stone. Software developers share all of these experiences with other artists. There is beauty in the finished product (ostensibly) and a hidden beauty in well-turned algorithms and eloquent functions. Those who would chafe at the notion of software developers as artists usually believe that an artistic bent is an unwholesome trait for a developer, that we need rigidness and structure in our psyche to be able to produce good code. While I wholeheartedly disagree with that belief, I have to acknowledge that it exists.

Re:The names we give

[BountyX]

I prefer "computer god" it strokes my ego, invokes fear of damnation, suggests omnipotence, and has potential to start a cult ^_^

Re:The names we give

[nuttycom]

Interesting. I really dislike the "developer" term because I associate it most closely with real-estate developers, who are mostly financiers and middlemen. Engineers are the ones who get the real work done.

I agree that there is a distinct art to producing software; in my mind engineering of all sorts has always been a distinctively creative and artful endeavor, so I don't think that it's particularly restrictive in terms of describing the scope of what we do.

Re:Release Early, Release Often Doesn't Serve User

[dbcad7]

You might check out.. http://glabels.sourceforge.net/faq/

There are also label templates for OpenOffice but I think the glabel program will do what you want to do.

Mainly, it means you don't get paid !!

[Anonymous Coward]

Like any good Stallmanist-Kommie, you don't need to be paid. Yeah, that's about the jist of it. Why do you need to know more ??

Re:Release Early, Release Often Doesn't Serve User

[grumbel]

I fear that if I released it, not even the version I have now, but future snapshots, it would get uploaded to all the shareware sites, where it would be downloaded by unsuspecting novice users, who would find it unpleasant to use. Thats what we have CVS/SVN/Git and friends for. Simply don't release it in tarball form until it is ready, instead just dump it into a public repository and be done with it. The repository will make sure that no shareware sites pick it up and that distris stay away from packaging it. It will also make sure that the end user gets that it isn't done yet.

That wouldn't serve their needs, and further, it would give me and my project a bad reputation. It doesn't have to serve a need, it simply has to be there to take a look. If nothing else just to see that it is actually real and not just one of the thousands of vaporware projects on sourceforge. By just having a webpage up and no code you are basically wasting peoples time.

I know that I have the greatest chance of success if I wait until I have something rock-solid before I make its first public release. On the other side the bus-factor can kick in and we are left with nothing but an empty webpage. It has happened before, it will happen again and maybe to you.

What is more important to you in an OS project....

[KPexEA]

Since I am the only developer on my OS project and I have a limited amount of time, what should I focus on?

Documentation or
Lots of small example programs?

According to the Microsoft PR rep..

[lmnfrs]

..that I met over the weekend, it means you're a "weirdo who ate too much paste as a kid."

I don't think that convinced the other guy to install a closed-source alternative to OpenOffice.

Re:What is more important to you in an OS project.

[Anonymous Coward]

just give it up and go out and find a girlfriend. you don't want to be associated with those faggots.

As an open-source author...

[gillbates]

• I don't have any arbitrary deadlines to meet.
• I can rework parts that I think need reworking, without any change control forms or paperwork.
• I can create in my own particular way, at my own particular pace. I don't have to release or publish anything until it's ready.
• I don't have to bother (much) with issues like licensing compliance or chasing down deadbeat payers, or filing stupid lawsuits because someone is sharing my stuff over P2P.
• I'm free to pursue projects that aren't commercially viable; I can do the kind of creativity that will never be seen in the world of commercial writing.
• I can sate the urge to create without sacrificing my heart and soul to the whims of a corporation.

Okay, on the bad side...

• I'm not sure how many people are using my code, or reading my works, or if anyone even cares. I could be a really bad writer and wouldn't know the difference...
• Because I have no professional obligation to release code, I don't release most of it. I have quite a few projects which are perpetually almost ready.
• I'm spending a substantial amount of time for which I won't ever reap a dividend. Could I do something more productive with this time? Perhaps. But then I'd still have to find some way to sate my creative instincts, so it might end up a net wash.
• There are things which I just can't work on because of my agreement with my employer. Working for a large corporation means that almost anything technical, which has the ability to change the world for the better, would fall under my employment agreement. Sure, I could probably post beer recipes (yes, I do brew...), but the work I've been doing with this FPGA kit is probably covered in part, if not completely, by my employment agreement. Because of the general wording of the agreement, and my desire to continue working there, I generally do not publish anything which could be construed as belonging to my employer in any way. So I typically can't publish anything related to my areas of most proficiency.

Re:As an open-source author...

[Broofa]

There are things which I just can't work on because of my agreement with my employer. Working for a large corporation means that almost anything technical, which has the ability to change the world for the better, would fall under my employment agreement. Sure, I could probably post beer recipes (yes, I do brew...), but the work I've been doing with this FPGA kit is probably covered in part, if not completely, by my employment agreement. Because of the general wording of the agreement, and my desire to continue working there, I generally do not publish anything which could be construed as belonging to my employer in any way. So I typically can't publish anything related to my areas of most proficiency.

I understand what you're saying, but just to be clear, by,"proficiency", you mean, "intellectual property", right? The issue being that the company "owns" any IP you create while on their payroll or using their property (computers, offices, etc.). In practical terms, the problem is that you spend 40 hours a week writing such-and-such a library, and it'd be great to share this work, but the pointy-heads in management are reluctant to opensource it.

Ideally, you can convince management that it's in the company's best interests to allow you to opensource the code. Regardless, there are several good arguments you can make:

• Opensourcing allows you to leverage the efforts of a broad community of developers (that the company doesn't have to pay for) to get your job done.
• Opensourcing gives your company influence (but not control) over a technology that 1) provides a distinct competitive advantage and 2) is highly visible within your industry
• Opensourcing provides for a maintanence plan for your software. i.e. the company isn't screwed if you decide to leave. Either you, or other contributers to the opensource project, will continue to support the codebase.

But that's not always possible. The best alternative is to bide your time and start an opensource project the next chance you get (i.e. between jobs). The company may own you while you work for them, but when you leave, you are no longer bound by your employment agreement. The company will own the IP you create for them, and you might be bound by a non-compete agreement, depending on where you work(ed), but those are different beasts, with different rules. IMNAL, but I suspect that as long as you aren't explicitely using IP owned by the company - i.e. not infringing on patents or using code you had access to - than an opensource project will be relatively immune to non-compete claims. (Anyone else have experience with this?)

There are strong incentives for you to do this that only grow as you grow your career. You get to take your code with you as you move from job to job. The opensource effort embodies your expertise and proficiency. And it gives you some modicum of identity, prestige even, within the industry in which you work.

Re:As an open-source author...

[gillbates]

One of the big issues with allowing open-source development is that it *could* contain otherwise patentable algorithms. If I implement a patentable idea in some OS project, my employer could lose the rights to the revenue that would have otherwise been gained. While I understand that most here think patents are evil, many corporations see nothing wrong with a revenue model based in part on licensing their patents to others. In fact, some would rather license another company's patent than spend the R and D money to develop a workaround. Corporations often think in a "How much to bring this product to market" mindset and could care less who gets paid as long as the costs are reasonable.

Last time I checked...

[syousef]

...it meant you wrote code, and released it as open source. But maybe that's just me?

Re:Release Early, Release Often Doesn't Serve User

[ShakaUVM]

>>And that's how I think every Free and Open Source Software project ought to be run.

Four years into it, a website, and no release? While that does sound like the majority of open source projects... I don't think that's a good thing.

Please. If you can't put together something stable and usable after a month, then you are Doing It Wrong. Start with a small workable tool, release it, open the source, and improve on it from there.

When I wrote CustomTF (an open source mod for Team Fortress for Quake 1, which people still play now 10 years later), I started with a very simple concept of being able to build your own classes in Team Fortress, and put it together, relatively cleanly, in about 48 hours of frenzied coding. This provided the structure that the mod has grown and developed with over the last 10 years, with something like 20 different people adding code and features when it interests them. It's been a very successful project, though it does seem to be winding down now that TF2 is out.

From your web site:
"I owe you an apology. I promised Ogg Frog's 1.0 release for August 2006, then February 2007, and here it is August 2007 - a whole year later - and there is still no software for you to download."

Yeah. Looking at your feature list for an unsupported product, it looks like you shot the moon, realized about halfway through that it was way more complicated than you realized and that what you had was basically unusable, and then went and started playing World of Warcraft instead. Happens quite a bit, actually, don't feel bad about it. But at the same time, it's philosophically wrong to say that Open Source projects should be run that way.

OS VS CS

[naich]

Yonks ago when I wrote a door for the Renegade BBS system, I thought I'd be able to make some money out of it by selling it as Shareware. At the time there was an immensely popular game called "Legend of the fwibble bwibble (can't remember what it was called - something to do with dragons, I think)" which I and many other people registered, obviously making the authors some money. "If they can do it, so can I" I naively thought. What I didn't realise is that for every popular piece of CSS software that makes money, there are about 1000 that don't - and, of course, mine was one of them. It was used by quite a few people in unregistered mode but people just didn't buy the full version. With hindsight, I wish I'd just released it with the source so that more people could have enjoyed it and maybe contributed to it. As it was, all my effort was almost completely wasted, which is a shame.

Since then I've made infinitely more money by writing bespoke software for companies, and this is where the money is made. Selling "boxed" software can obviously make you very rich, but only for a tiny fraction of the people who do. The rest write bespoke software, relying on tools from the few who make money from CSS and the many who write OSS.

And this is where contributing to the general Open Source community really pays. By keeping the spirit of OS going in whatever way, either by writing software or supporting a project with money or even just bug reports, you are inspiring others to create more software, which will include the tools that you use for the jobs that actually make money.

So it seems to me that the obvious sensible choice to get a guaranteed return for your efforts is to write exclusively open source software.

Re:Release Early, Release Often Doesn't Serve User

[backwardMechanic]

I'm curious - why do you have a website at all? I find an increasing number of dev project sites and sourceforge projects with no code whatsoever. It's all noise.

I'm working on a project I intend to open too. Like you, mine really isn't ready for public consumption. However, I am quietly tidying up my code, filling in some holes, and generally trying to make it useable/developable by someone who isn't me. Once that is done, I'll release it.

Maybe this is harsh, but isn't building the website before the project a way of enjoying the achievement without achieving it?

Re:Release Early, Release Often Doesn't Serve User

[ProUSASlashdotter]

Hmmmmm, something tells me that you are about to lose your ability to login to /. You have spoken ill of anything FOSS...you will PAY!! ;)

What Does It Mean To Be an Open Source Author?

[Anonymous Coward]

Being poor.

Re:Release Early, Release Often Doesn't Serve User

[Anonymous Coward]

I just printed a bunch of address labels in OOo writer generated from an OOo database the other day. You're probably not doing it right, or maybe its a platform dependent bug and they've fixed the bug on open-source Ubuntu gnu/Linux but not on non-foss Mac for whatever reason.

If you release a beta and state its a beta and let people who just come across and visit know its not ready for everyday use, you would have alot more testers, some contributors and those that can't wait (or 'early adapters') won't talk sh*t. While people like you can just wait for 3 years, or 15 if you were waiting for Wine. (notice: The Wine people were making money with-out a 'stable' release.)

Re:Just like any other developer, except no payche

[bonefry]

Just like any other developer?

I think not ... as Alan Kay said, most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.

The problem with being paid for developing software is that you're always implementing someone else's idea and most times the only motivation for going further is your monthly salary because commercial projects are usually boring as hell, and slaves are needed.

Open-source projects are the next best thing to having your own startup in Sillicon Valey, and not everyone is blessed with the privilege of living in an area where new ideas can thrive.

Re:Release Early, Release Often Doesn't Serve User

[yabos]

I'll give you the reporting bugs part, but do you have any idea how long it would take to even begin to understand how the OO code actually works? It's HUGE, and even figuring out how the printing stuff works would take a long time if you're supposedly doing it in your spare time. Sure you might be able to fix a few bugs that result in crashes if you really wanted to track down the problem, but implementing new features in a huge project like that is a monumental task for someone new to the code.

Re:Release Early, Release Often Doesn't Serve User

[Anonymous Coward]

1. what are you talking about..
2. you get what you pay for
3. go away.

It means...

[Anonymous Coward]

It means never having to ask, "are you sure I'm the father?"

Re:Release Early, Release Often Doesn't Serve User

[QuantumG]

Dude, speak for yourself.

Picking up a new code-base quickly is a skill that many people in the Open Source community have.. and you will never learn it if you're just defeatist about it.

I can try under Windows or Debian

[MichaelCrawford]

I have a real windows box, and also one on my Mac under Parallels. Debian is under Parallels, I don't know if printing would work.

I acknowledge that Ogg Frog has gone far too long without a release - I never meant it to take this long. Some life events disrupted its development completely. But I'll get back on it soon.

Re:Release Early, Release Often Doesn't Serve User

[yabos]

I'm talking about something as big as Open Office. That's a huge code base and unless you have a lot of spare time it would take quite a while to figure it all out. Luckily most open source projects aren't that big.

Re:Release Early, Release Often Doesn't Serve User

[QuantumG]

As much as I understand the point you are trying to make, I really don't think it is as big of a practical issue as much as it is a psychological one. All the people who contribute to the Linux kernel know maybe 1/1000th of the entire code base, because that's all they need to know. Same goes for Open Office or any other large code base. I remember fixing something in Open Office a few years ago.. I looked at the text on the dialog, searched the code, didn't find the text. That stumped me for about an hour, until I figured out that they were internationalization fans.. I found the string I was looking for in a language file. Next to it was an identifier.. I searched for that in the code, found the part which was responsible for the dialog. If I remember correctly, it was some kind of domain specific language for dialogs. So I studied that for a while and found the identifier for the function that was called when the button I was interested in was pressed. That function was written in C++.. it's probably written in Java now. About 20 seconds after looking at the function I saw the obvious error, and fixed it. I sent the patch to the list, they said thanks, ignored the patch and just fixed it themselves. I implemented a couple of other hacks that I wanted to the Presenter app, posted em to the list, they were picked up in some later releases.

This is what programming in the large is all about. Most software is worked on by a team of developers, few of whom understand the entire code base. You need to use "beacons" to navigate around the code and find the local relevant portion that corresponds to the dynamic behavior. This is classic software maintenance.. see Brooks, 1983. I, personally, think the standard mechanism is not good enough.. There should be better tool support for matching program behavior to the source code, and programmers should learn to use them. I wrote a function tracing tool for this reason. Although, looking at that page now, I see this isn't the version that lets me attach to an already running pid. I should really update that. Can't remember if it does multiple threads either.. hmm.

Re:Release Early, Release Often Doesn't Serve User

[Eythian]

Hmm, the way I did my Free software project was to get a basic but functioning app done and released as an alpha to people who were willing to test it. This got me valuable feedback, and people to help out with things like art work (that I'm not so good with), that I wouldn't have gotten otherwise. I'm still not up to 1.0, and I don't know if that's so bad. Maybe the 100th release will become 1.00. The version number no longer really means anything.

But my point is, it's come a long way since release, it's gone from 'just barely able to do what it says on the can' to 'stable, robust, and companies give me money to do custom branded versions for their own services', while trying to keep the 'release early, release often' philosophy going.