Slashdot Mirror
Engaging with the OSS Community
s390 writes "Olliance has the second of its Open Source articles up at the Inquirer. It's called "Engaging with the Open Source Community (Part Two)", and it explains the different levels of involvement that companies can have with Open Source. More education for managers, and an outline of a corporate process for approaching adoption and deployment of Linux and other Open Source software."
...at Wolf 359 ;)
"Hey! Unless this is a nude love-in, get the hell off my property!!"
Most of us would love to see Open Source widely adopted as a business strategy. The major barrier to this is that business adopts the path-of-least-resistance to profitability, and changing your current strategy for a largely untested and hence managerially mistrusted one is a brave move indeed. No amount of educating managers is going to change the fact that its better to wait and see others succeed (or fail) before you try yourself.
"I am not bound to please thee with my answers" [William Shakespeare]
you are first brains
monkey, pigeon, or human? i prefer pigeon.
...is easily big enough to polish and support OSS in house (they have nearly 5,000 support staff world wide and 2,000 developers supporting 100,000 workstations). They get no support direct from Microsoft. They have no interest in making money from software - things (and there are a lot of things) that get written in house stay in house, no matter what the commercial potential.
And yet they still don't use OSS, despite the fact that it would offer them huge cost savings, less problems with obsolescence, a decent code base for internal development and many other advantages. It's really, massivly bizarre why why don't see what they could gain.
Perhaps they have been locked in a cuboard for the last 10 years and don't realise it exists?
Mind you, this _is_ British industry - a culture exists where if there had been a practice of lopping off the foot of every new hire for the last 20 years it would carry on forever, because 'that's the way we have always done things'.
Beep beep.
I decleare this post -1, troll^H^H^Hue, because its TRUE but only a troll understands why.
Debian : We don't like USB, we wan't you to use our 2.2 kernal and force you to use PS/2 mice. Oh, we want you to use X4.1 and Gnome 1.4 as your "desktop" that is you have a five year old graphics card.
KDE : We like to have giant throbbing buttons and eye candy, but we don't want you running it on enything less than a Athlon 3000 with 1GB of ram.
GNOME : We won't give you proper file dialog or split pane in nautlus because it will be to compicateed for the average user (read : the average user in our view can't even find the on button). Yes we give you stuff like tear off menus and rearranging buttons, but you have to use our special "gconf-editor" for it (which is nastier than winregedit32.exe)
Mozilla : We force you to use gtk 1.4 without compiling it because the average user likes the pain of their eyes straining on the alaised pcf.gz fonts.
Trolls : This is all true, delusion is an anagram of slashdot when spelled the "taco" way.
Wonderful. I can't wait until phrases like "Open Source engagement spectrum" become commonplace.
Maybe i'm a little naive about the needs of enterprise users (a term that seems to be more and more misused as a selling point), but this article makes things seem a lot more complex than they need to be. Engaging the open-source community? Five levels of involvement? Gimme a break.
A business that's considering moving into widespread use of open-source software has a lot to consider, that much is obvious. However, the article strikes upon the most resonant point simply by mentioning that a company has to consider what suits their business best.
Most of what this article touches upon is simply extraneous, as it's covering basically what one goes through when deciding on *any* software. Budget constraints, long-term cost, difficulty of adoption for the end-user, and so on and so forth.
The community should be taken into consideration as necessary; it's a resource like any other, and your level of participation is dependent upon your needs as a company. Go with a commercial vendor, you get tech support, plus the benefit of community feedback and assistance. Go with a free one, you negate the tech support and interact with the community at large as much as necessary.
Honestly, if you're running a company and need a guidebook on how to engage with a community of developers and users, you need to step back and re-evaluate your tactics. This is mindless cruft for managers without a clue as to how to interact with people. "Deciding to engage"..pff. What are we, the friggin' Borg?
I can't help but be reminded of Fear and Loathing In Las Vegas, where a so-called expert is on stage droning on about the various levels of a dope fiend. You can describe as many "levels" or "points" as you like, but in the end, software is software, a dope fiend is a dope fiend.
Regardless of how you "engage", considerations like your budget and potential risks as a result of a adoption are pretty damned universal. It's not a goddamned 5-step program.
My experience is that Enterprises which do not view software as a capital investment, don't treat the procurement of software as an investment. In that respect, they get trapped into the same vicious cycle of vendor lock-in as the common consumer, and it costs them a lot of money later.
I think that as Enterprise IT managers start to wake up to the costs of vendor lock-in for tailored or custom applications, the response will be a demand for greater control.
Total control is obviously Free and Open source.
Code escrow it the next degree of control - think, when the corporate development and support ends, the source is delivered to the Enterprise.
Finally, proprietary code with an extended waranty that provides no-cost fixes for custom or tailored software that fails to perform as advertised is the minimum degree of control that would be required by the Enterprise for it to be considered a capital investment.
I can think of a half-dozen crappy custom product vendors that couldn't survive such a method being adopted by a broad slice of their market, and I think it would make the world a better place.
I'd be more apt to listen to people from the OSS Community if they started bathing, shaving, and look less like dirty hippies and more like professionals.
Oh, it's true, it's true.
Here, software is not made by armies of "Microserfs" employed by a giant corporation, but by armies of volunteer programmers who "donate" their code to the *public domain.*
public domain != OpenSource/Free Software
i'm worry about people dont getting this.
Is that a scientific experiment to see how much bullshit the general public will accept?
What were they thinking when they wrote sentences such as "Engagement with an Open Source community is a continuum"? Whom were they trying to impress with this pseudo-scientific marketing fill-word collection?
They go on and on about the various ways in which a company can contribute to the open source community, but completely fail to say why a company would want to do that in the first place! The first installment of this diatribe was even worse, containing some vague assertions like "open source software is more stable" or "open source software is much more secure" and didn't even begin to consider backing this drivel up with facts of any kind.
Argh! Just read this little gem here: "This first decision is not a foregone conclusion, because different enterprises and IT organizations have differing objectives, resources, capabilities, enabling factors, and business constraints." Even pros like Accenture couldn't have packed less content and more hype fillwords into a single paragraph!
But the best part is the "conclusion" where they simply assert "In this paper we've reviewed the definition and advantages of Open Source software". Uh, WTF?!
Waaah, I want to puke when I read this crap! They actually have a headline called "High Level Process" and then proceed to talk about "milestones" and "enabling factors" and "identifying opportunities", it's like an ugly satire on KPMG, Accenture and all the other hype bubble spewers. It could be right out of one of these hollow Gartner Group reports, just blowing in a different hype horn.
This is exactly the kind of lip service the open source community does not need. I say: stay with your SAP friends.
On the other hand, maybe it's a good sign that the open source market is now big enough to attract their share of parasites.
And I hope thats (a very poor attempt at) humour..
since when did choosing to give away something that you wrote yourself constitute theft?
Idiot.
Yeah, I hope it's not a good attempt at humor too.
YHBT! YHL! FOAD!
In Part 1 of the article, the authors like to point out how OSS turns the tragedy of the commons into the triumph of the commons. Then in Part 2, they tell you how to "engage" with the OSS community in order to get higher quality software. This article is never going to convince businesses to switch to open source because it never uses the magic words: this is how to make money fast.
The "triumph of the commons" argument is a obvious example of how arguments by analogy can be used to support a ridiculous conclusion. OSS opponents deride the GPL because they say the tragedy of the commons will prevent anyone from making any money. The authors respond "No, it's the triumph of the commons because the result is high quality software." That's great, but you're still evading the real question.
Show me the money!
Show me the money!
Show me the money!
-a
People usually use this kind of language to somehow "prove" that whatever they have is "serious" and "businesslike."
Here's a better idea: Computers are so flippin' cheap these days. If you want to sell OSS services, get ahold of the IT manager, or even better, the CFO of the corporation and drop $200 to GIVE them a FREE box with FREE software on it. $200 is cheaper than most advertising, and I guarantee you that it would be booted, played with, kicked over to IT for awhile, and so on. If a CFO (or other high exec) sees that OSS genuinely works and how much money they can save... well, that's the kind of thing that will make a sale. Throwing a bunch of corporatespeak at people is well, what all the other corporations do. No one really pays attention to it, they only care about the bottom line. The effects have to be effectively demonstrated.
IAAL
Propaganda Lies Bullshit Fake News Vast Right Wing Conspiracy Yellow Journalism
0 03 bcf15ba4da931a66c090c8a353a276ed62f49e7376f6a5857d b626d0ede885348d23c2ed8ed3dc935590f018d77bda49fc84 d5b322cfa789ad4df09370ef745cc3c8765acabdd6f17e2870 4bf2b4702992842989431d24efba0d602748d6f5066384a22b 186e5b362e95a098223bb09b80ff75afd0150f42ada6a11600 5062613a49add8ab908bb6017bb363380c627b4185ca2a0330 b29542f2f27285580fe8d6aa82e179ed28d1d39169296da883 1511eb37a5cb73ea4bc2d171e7cff7fa3c2c4bd0bf5dabc4bd 27a4ddb5342c89a94726eca36469b39673ed352d35974c9920 242edac18fa38c7695898356f60cfdabfb38bab5b538c2a154 9a69a4d96c96d61752639661d055b9d07f95df2d8a39167372 6bf4ef3dc57738bf8572500fd2a569d9be99afc7896aaecf88 85240bdc179b3b285279a34c4e65bb11e628e0383351d2eeb3 7fca4d4c9145a0a5352d6f6f6ba50a0c3f4f1d153493d4189a 91c0e59ac035307a7554821d182370046edc3fa2d37a254cdc e90f24cff5f0c12e4041b8e3eaa3a623ec27a7368c3b476de0 3d37bf85db033ad00097f89aa7f7c624679166827181c2
Scientology Scientology Scientology Scientology Scientology
anusfeast
1cbaa4e5609fb6517f54f0ab0c205adae02721e864b2649
Propaganda Lies Bullshit Fake News Vast Right Wing Conspiracy Yellow Journalism
a 3f 50c5c8d0d3086bff2b3bdc12322a599dd08c10a3612b95eb8c 64007b726195df839807c82918198765b8b2696f325fde67ae aa049ac7a58a13dab3f5ec9e22d0d1495c8c85e436b30be338 efa14f74a40949dbafd02b57
Scientology Scientology Scientology Scientology Scientology
anusfeast
ded693405194bd811d9dde0e3cf270e8e2521b89f813157
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
7 dc 8c5d41276b4ecdd6de154e29d21fbba350dd07853a895b5118 cf43025d0a1446b9171f22bdda0b34209cfdd843c38888b83c 3a807d3cdf9807e8ebfb97d09f0b9ac74acd2c0454eae4f6bc b74544e22156b0c45bab412f170277c92bb14228ea593cb85b 2654a9e3124019ddf381323ab6e2395f8d5da045357744aeca 58e25b55d49ff3e28706ea2bba2322f3e38b75cd5e35bad903 40
anusfeast
56ba199d2c826a25b96938b750b1f89aa1363880b0e51db
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
b 67 da47a4007fdb12fac7337f5615c1611b2e2a21f92b7fe9e302 3cb26ee1da6bcc0c72ebd9a4524ddad9375c9bd04516b37e25 662b76e0eb03e68135e0895efe7ac9d0abac64f8a087383af6 bec917df4d27b26d9604ddf6507a6965f32d702499488a7392 af9a4b18ba9d7c0fd222f5c996923ab15667ad
anusfeast
2609acbab44e192aa3764849a69b7dd8b9abc54b685d47d
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
5 ea ad06cc5cd9ed66f99413118c15585b6dffad00b6c3d19ef9be e5723ce292818361a7f05beca98340025295e30fc6de2015af 73793e583b6320267b4965e7a50b2996cbd2d6c60ff0829444 4e4fca65ce79af841033f9b4480d0c9cb2cc4ac70a9a55cfab 1118c87c3a2600addf965583459867fd2a8200bea3ffc1d964 46a163e19bb2271675082c104bbfb1635cf8115a8ccf2d3001 033ee4085ce6f44d7591dbacfd9b0613ac0698a0dc0ddb3c0f 1b942ab02f683ce1a1d89a61350db9f159eede79cbb4468e47 38d3e80d86e941acb882e1afef5119faa13131f61414bcf3ea c257e464629d79d51f4d7e4d54d54b55519c3b462d004ddc45 a9de1065695a90e87be37471c087c31c6fa12b5f9a93d4d886 c0e9b151d826eb2c8a89edd8de57f376576d9287
anusfeast
f8e64e825cf4fd949b32961ad1b4312a2006a1ab495a5a5
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
f d6 b3f79270c16075f258367ae371f7e2b69c63148c45b143470d f9a82529229215d270480eed14c63327d2a42b3c91cf73eaef 07f32e80b6fa32fb1b06afb7b2a5f06b7efa66ea77e3c216d5 21607da146fa23d65cfcc6b60b5f2caf4c5de1e3a8e68f505a e6899b87cbdccd7c4f57001c682af769ef9b156e8ad22f2de4 a390ac6d27f4dd52f5e8
anusfeast
28172a8c15bfbc0714c5a2cd0d1ed2a4dedc7340c663a84
Like here?
"It's not your information. It's information about you" - John Ford, Vice President, Equifax
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
7 c8 ef5843c08a854a0fb94b5238b785967da7765e33a7d8aad53f 539e0e5b10ad4a14a5852132a5dd
anusfeast
28ee246ec2eb21c48f71abd66eb5d2e6b6ddc699659f736
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
a ae dacf320a2857306b86b2b1457106cdd16d2e93b86a6f29984f afabd1df5143b9adc43c0c8864b747452281c1ebbb2d13b757 99e814029b1b1e001aeff89d13fffafa39914b09fe1e55b97f 89a8c4258b73ac3dedf1d02e2613eb51b0ce09c12b6cac14c5 1dc38ca48dcfbc8082e8fcaf883c8264ae3180ddd81e516735 4b09f1f95703d1a9fa94daa6007fc501269cdd024a980b0817 29936d1f13b9aac641b5d124d96dc7cff9a85af1dd596e68f8 edf31f774681944fe12999c8d752abf6f612f729e4800e77b2 eb6c419ece4ac78f64ae9ad6309f6b8642785813491d703d51 7ddd009440548908c0cdcc298c5b09c1ef128437d07776e600 a50e0863171787f22bd589719e250aa0985d9e292b68c8841c 3c95aa10c329c60213cd6060de16fdce02849062adafcff122 44ae37c05f80084d1dce685d450c92915e657f24d8a5b58327 5ffd6871e7ecc0d05b7e8c849dcbbc92c9b8682bed004aa3e6 06604638227f1d8e6c
anusfeast
736c1908fbbb3c33c217dff33ec717ee870bfaead6f1619
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
2 bc 85f00974c0b13326c5dca2512a4c7fe8810bd04191b1b32672 ac9f946d9bd59e83f1d2e31ad3eb8969a7f7fe8b1fbc83fe42 52322bd640dc898d5e41b3565e59bf91133acbd85e48b92800 5eb587644756f16e5705e3f0e6bae1c9be547688245a31269a 1fd38a9cdda2a6d2b0c4d2ad70a7f008c35b14a71d605a4f81 4847ac5b0d96f11ee44467a83eab0da5d5e1357e82cee4ea99 07bc2afc5afe07c798fe901794ef40646f14919153f8aaf3af 893165510756de564853deb8a06838c502fc6cb6ce91f70410 eb682451408211883d77aa2edd7ebbcd2d79224cd58d9c9bcc c3c9622e208f7929d0c1c363d229873f32a2364556f941797f 1859f4ef658bab6ce33334dec795a5a82212ea714ba2923f1b b3f1ffa1c51736ad2d1327f55d9f8c5d33d78b3d0b49b88c68 f7ecbdb73f50496c084a1ebc942c813742a75278f0cacbc3f9 5f3021935258b5b2603016a3cfe1ab392393a5ce06eab3875b 07f519198536925f3b74b7b433df00d7a7d43820adcd5b22fd
anusfeast
95e2374e4c9f5f49f0e03fac57fb95d337911fc4a6eb755
Pee Eightch Pee sucks. PHP sucks, because it's a piece of shit. Suck ass PHP, it blows goatse balls. I hate PHP and you should too for all these reasons I have just outlined. Thank you, eat my ass hole out now.
7 dc cff51c078409003210806875ddb9745d3d8313e65b81ab49d0 a82eeff713b74763ec2aefde176b1d9c75dde258f64a842e31 ea888708d90f81e7e57ebcb5b8078b3f35e6491ffc
anusfeast
8640d7a945445a1efbe208c1017e5b41aa3e602dc876a6d
I feel like a broken record, but what has been very effective for our company is not usually mentioned in these kinds of discussions.
We found an open source app that did nearly what we needed, so we contracted the developer to add features for us (into the main open source version).
Obviously this works best when there is one person or a company behind a project, and also when the features you need are in line with the overall direction the developer is willing to take the project.
I envision a system where this could be expanded, where end users would bid competitively on which features to be added or bugs to be fixed. I've seen some attempts at realizing this sort of system, but none have caught on in a big way.
This could even work in a micropayment world, since a central site could take a block donation of a minimum of say $20-50 and then you could split that up as small as a dollar at a time between different projects, features, and bugs. The developers would get paid in minimum sized chunks too, so on both sides, the traditional barriers to micropayments (high transaction costs) are reduced.
Think of it kinda like a bug bounty that some projects do before a major release, but instead of being initiated by the developers, it would be initiated by the users.
An economy like this of development work ensures that the bugs that are most important get fixed, and the features that people want get added too.
I've had enough abrasive sigs. Kittens are cute and fuzzy.
What's your issue with Fox?
They're the only outlet not heavily influenced by whiny liberals.
How small a thought it takes to fill a whole life
What were they thinking when they wrote sentences such as "Engagement with an Open Source community is a continuum"? Whom were they trying to impress with this pseudo-scientific marketing fill-word collection?
I see an objective and insightful article here. It's not clear to me what you are whining about, perhaps you are trying to appear cool by dissing it? Remember, it wasn't written for you, it's obviously aimed at managers.
They go on and on about the various ways in which a company can contribute to the open source community, but completely fail to say why a company would want to do that in the first place!
Luckily for you too, because now is your golden chance to write your own article. As far as this one goes, they apparently assume that the reader is already aware of the benefits and is now at the point of wondering how they can get aboard the train, i.e., "engage the community" in PHB-speak.
The first installment of this diatribe was even worse, containing some vague assertions like "open source software is more stable" or "open source software is much more secure" and didn't even begin to consider backing this drivel up with facts of any kind.
Heh, you are just a troll, have a nice day.
Have you got your LWN subscription yet?
- Asking a question on IRC and being told to RTFM
- Posting to a newsgroup and being told to RTFM
- Writing an email and being told to RTFM
- Posting to Slashdot and being told to RTFM
Did I miss any?if you see both objectivity and insight at the same time, your eyes see w/ neither. insight comes from intimacy w/ some matter, whereas objectivity relies on consensus of the senses only. better to say frankly that you enjoyed the article and agreed w/ it enough to be willing to read more in the same vein.
back on topic: it would be nice for managers to engage in their own open-foo initiatives, like: open-door policy, timely feedback on well-delineated expectations, actual participation in the work to understand its grotty nature, and so forth. the manager that understands the congruence of these practices w/ the motivation behind free software (and, by extension, open source software) is best positioned to grow. those that don't, won't.