More MS, Less Talent In Open Source's Future

alphadogg writes "The open source industry in 2008 will be marked by more news out of Microsoft, IBM, Oracle and other big IT vendors, less start-up funding, more M&A activity, and an increasingly serious talent shortage, according to Raven Zachary, open source research director for The 451 Group. One example of the talent shortage will be people with expertise in the Tomcat open source Java servlet middleware from the Apache Foundation. 'There are 25 or so core contributors to that project,' Zachary said. 'Over the past four or five years that number has stayed virtually [unchanged]... but the growth of Tomcat has been astronomical.'"

Comments

Talent shortage?

[RandoX]

Maybe talented coders like to get paid better.

Re:Talent shortage?

[wwmedia]

u mean not all programmers like to give away their work and answer support questions for free with their open source software?

Re:Talent shortage?

[RHSC]

I prefer to get paid by the semicolon...just so long as I don't have to code in VB

Re:Talent shortage?

[Anonymous Coward]

Exactly. Unfortunately, support and consulting are arguably the least desirable way to make money in this sort of industry. Ideally, you'd sell product and get only positive feedback to improve it. No support. No dumb questions. No issues.

Companies that make money from support contracts are, in my opinion, doing the least favorable work. It's certainly not sexy and for every dollar you earn, you have to work an amount directly proportional to that. There's not much concept of exponential growth. In other words, your income per hour flattens out much faster than with a product-based model.

Re:Talent shortage?

[xanadu-xtroot.com]

not all open source is derived from hobby work ya know

Perhaps, but you're missing his point. Here's another example:

• Wake up around 6 am. Eat, get dressed, and get physched up for the fun fun hour plus drive via major congested roads to get to work by 9am. That pre-leave time also includes helping get my Son ready for School (breakfast, persistant reminders that he's running late, etc.).
• Work 'till 5pm (usually closer to 6 pm).
• Fun fun hour plus drive home. Home around 7 pm.
• Eat dinner, help Son with homework, spend a bit of time with him before his bed time.
• Spend sometime with Wife and un-wind a bit (and "un-wind", if you catch my drift...)
• Shower, go over meeting notes, maybe catch the the earlier late news).
• 10pm Head to bed.

Where in there am I supposed to find time to sit in front of my machine spending hours debugging code for an OSS project? I'm not saying that I don't contribute, once in a while I have sometime on weekends to submit a bug report (with some same code usually - but not always), or something small like that, but by far and large, us "older" (I'm only 34, but...), "Family Guys" simply don't have the time the younger people (in High School or College) do.

That was his point, I think.

Re:Talent shortage?

[kdemetter]

so don't use GLPv3 . There are plenty of other open source licenses . It's not because the FSF makes a new one that you have to use that. There is no good or bad license in there , it just depends on your needs . I don't think there's a talent shortage , it's more like a shortage of new ideas . Basically , if you think of an application you could use , there's a good chance it already exists . And it's a lot more fun working on something you helped create , than on improving something someone else wrote .

Re:Talent shortage?

[dvice_null]

> Where in there am I supposed to find time to sit in front of my machine spending hours debugging code for an OSS project?

"We" have the same amount of time what everyone else has. It is just how we want to spent it.

For example I moved to very close to my current work place when I started working there. It takes about 10 minutes for me to get to work and I don't even have to use a car for that. I save probably 10 hours every week compared to you. That is something like 500 hours every year (+ I save a lot of environment and money at the same time).

I like to think that my skills are too valuable to be wasted in traffic jams every day. I would ever turn down a job, if I couldn't move close enough to it. You obviously have different priorities, which are probably better than mine. But you really can't claim that you would have less time than anyone else. (I also have a wife, child, job and I spent my free time on Slashdot and with open source projects.)

Re:Talent shortage?

[Anonymous Coward]

if they use that code to hinder the modification of modified gnu source code than yes GPLv3 would prevent that, if their code was a seperate entity that in no way affected the modification of modified gnu code then there is by design, no problem. Tivo allowed you to view the source but not to modify it for your own use on their hardware, that would be considered anti-ethical to software freedom. Then again there's nothing preventing said company from using BSD code or writing their own code for the job nor does it prevent Torvalds from keeping Linux under GPLv2 or forking it for those that wish to do so.

Yes, Tivoization is bad, but all the GPL v3 did is just get people to run back to MS and other closed source providers for fear of unwarranted lawsuits, or fear of giving away hard-won corporate assets.

wait what? are you fscking kidding me? need I remind you that you can't really modify MS code because it is closed source? quit spreading FUD troll

Quantity != Quality

[dintech]

Tomcat is an excellent product and a gem of the open source community. Just because there are 'only' 25 core developers working on it doesn't make it inferior in any of the other offerings out there. I'm not sure throwing more developers at it would necessarily make it better. See, Mythical Man Month for details...

Why?

[Gotung]

Why does an open source project magically need more programmers because it has become popular? What's wrong with the 25 guys that have obviously been doing a kick-ass job with Tomcat? Throwing more bodies at it will just lead to bloatware.

Re:Why?

[ByOhTek]

I think they were stating it's size and complexity as the rational, not the popularity.

Still, yes there are 25 core contributors to Tomcat, but what is the total contributor size in a per-mont/per-year breakdown for the server.

And what percentage of the updates are being done by the core developers? If the proporition of the development done by the core team is half of what it was the year before, at any given point, but about the same absolute amount of work - then the development on the project is still growing exponentially, even if the core team remains the same size.

From TFA

[Silver Sloth]

"Microsoft is still trying to work out its strategy," he said. "Ultimately, I think we'll see them embrace open source much more." Now I'm worried.

Number of maintainers falls as project ages

[xant]

High-quality products general stay flat or lose developers over time without losing any quality. I have no idea whether tomcat is a high-quality product or not, but the core of it probably requires very little maintenance now, leaving the "core" developer circle free to work on edge features. There are an unlimited number of those for any given project, but the urgency of those edges falls off rapidly as a project ages, so it's rarely the case that a project needs to grow in developers just because it's getting older. Such projects usually split into separate projects with their own functionality core.

Also, it's ridiculous to extrapolate this process and make a statement about all open source. Developers are rarely destroyed, converting their energy into entropy. Instead, they are simply attracted to new products that need developers.

Finally, the talented open source developers pool will only grow, as it always has. If Microsoft is hiring people to work on open source, then those people will be new talented open source developers.

Re:MS...

[teknopurge]

Chairs.

Everyone knows that.

I don't see it

[Wylfing]

First: who the F cares about announcements from Microsoft regarding open source projects, unless they are actually contributing.

OK, that out of the way, I can't see how a shortage in one project is a shortage overall. OS is about coders scratching an itch. I have contributed to projects but only when it was something that impacted me personally, and I wanted to see it fixed in a hurry. If the number of users of a project grows astronomically, that's great, but it has no bearing on how many coders participate if nobody feels an "itch" they need to scratch. Maybe the software is good enough for end users, and they feel fine about it.

Those coders aren't "gone." They're just off scratching some other itch, is all.

Huh?

[snoyberg]

'There are 25 or so core contributors to that project,' Zachary said. 'Over the past four or five years that number has stayed virtually [unchanged]... but the growth of Tomcat has been astronomical.'"

I don't get it. There's an open source project run by 25 or so people that's had "astronomical" growth, but since they aren't bringing in new people there's a lack of talent? If they're doing well with those 25, why does the team have to grow?

Re:Huh?

[Shadowlore]

Because that is how management thinks. I'll break It out for you.

Management types want more people to manage because it gives them a means to argue they deserve more money. Their management wants to see more money first. SO if your product is successful and growing, your management expects to be able to bring on more workers so they can be considered more important and worth more money. Think of it as HR bloat just like feature bloat in an application.

Since these "analysis" articles are done by people who are trained in, experienced in, or familiar with that model that is what they expect of everything. It's the notion that success brings growth. They are blissfully ignorant of the small world concepts, or how real work gets done, or how software is different from building a Model T, and only see the "business" side - especially since that is what pays their salary.

25 is about 15 too many.

[Organic Brain Damage]

The assumption that a bigger team is an indicator of health is insane. Large teams in software development spend most of their time NOT WRITING CODE and NOT DEBUGGING CODE. They spend their time in meetings trying to figure out how to get 25 people or 50 people to all work together. If you have a really big job, like making a modern spreadsheet product, your best bet is to figure out how to partition it into a series of jobs that can be handled more or less independently by separate 5 person teams.

What you need is *not* a *core* developper.

[DrYak]

That's the typical opensource situation where whom you need is NOT a core developer.

25 developers are a pretty good team to constantly write, re-write and improve the inner workings of tom-cat. In fact, there are a lot of commercial project that don't have that much developer 100% dedicated to the project. And as GP poster pointed out : "Mythical Man-month" explains us why this team doesn't need to grow much more because of the added inter-communication and training of newcomers overhead.

What a lot of newcomers into the OSS world fail to realise, is that there is a lot beside "writing code" that is important for an OSS project to be useful. There's, for example, a very strong need for artist to make the visuals (UI design, themes, other graphics) in order to avoid having the OSS project look like some 10 year old ass-ugly Athena interface with a cryptic UI based on a non obvious metaphor.
And, like in your case, projects also needs people with good writing skills, to write nice documentation, specification, HOW-TOs, and other guides, because frankly there are a lot of OSS projects out there that are technical marvel from a technological point of view but whose documentation consist mainly of a a big dump of code comments and function names and where, in fine, the old classic formula "Google + {error message} = posts in newsgroups" is the only way to get decent help.

People usually fail to realise it. For them Open-Source mostly remind them of complex C/C++-code and they think that GPL is only for programmer good at writing code. And thus a lot of people aren't motivated to contact a project and start helping because they think they don't have the necessary coding skills. Whereas in fact, even with no competences at all in programming, they could be critically important with their artistic, litteracy, or other skills. (Even things like helping organising appearances of the project at major Meetings and Expo can help because it bring attention to the project, and that requires skill that are neither coding nor artistic).