Slashdot Mirror
Fun and Informative Way to Introduce Open Source?
jwg asks: "I work in an office environment where I provide technical services and solutions to my co-workers (as I am sure most Slashdot readers do at their respective places of employment). Once a month, we have a round-table meeting to discuss pressing issues in our office. At the beginning of these meetings, it is one person's job to provide some form of 'professional development', usually an activity or game to teach some skill, idea, or trend directly related to their job. My turn is coming up soon, and I would like to introduce my co-workers to the idea (and to some, the way of life) of Open Source. There are many examples of Open Source software and communities out there to reference (Mozilla, Wikipedia, MySQL and... oh yeah, Linux), but has anyone come up with or come across a method to introduce it in a quick, fun, and informative way to a wide variety of people each of which possess a even wider range of technical skill? Did I mention it has to be fun?"
How about creating or buying a ready-made "computer on a stick"? That is a USB memory stick...there's a fair bit of open source software, OS, apps, utilities etc., that can boot from a USB drive. You can put this together or buy one from third-party vendors. Another inexpensive alternative would be to pass around a "how to" sheet to your group after you give them a demo off a USB drive. On it you could also include the PCmag reviews of OpenOffice reassuring Microsoft Office compatibility. If you want to go the extra mile, you could even set up the Mozilla browser with all the open-source resources bookmarked like wikipedia, Wikinews, imdb, openmedia.org etc. It's an eye-opener for those not familiar with open source. More here: http://mp.blogs.com/mp/2005/07/on_computers_on.htm l
you could always try the whole falling thing you know where everyone catches the falling person. then demonstrate it if everyone tried to make there catching system "propritary"
Ask everyone in the group to imagine a simple piece of paper.
Ask them:
What would use a blank sheet of paper for?
What do you know about where the paper was manufactured?
What do you know about the inventor of paper?
There are few simple alternatives to paper. Sure there are whiteboards / chalkboards / computers / sheets of mylar, etc., but each has limitations that are not inherent to paper.
Ask them how they would feel if it suddenly cost $300.00 to purchase each sheet of paper simply because the biggest vendor decided that that was what they wanted to charge. What would they do to get around this barrier to their productivity. The alternatives aren't very convenient for most people. Would they look into making their own paper?
Then tell them that there is a community that is offering other ways to manufacture paper that drastically decreased the cost - back down to the previous rate - how would they feel about that.
Better still, what if that community were all volunteers, whose goal is to make access to this type of information / service / activity available to as many people as possible?
This is rather simplistic, and doesn't address a lot of what OSS/FOSS is about, but it is a simple way to introduce the subject.
It wouldn't hurt if you could download an Open Source paper airplane design so that they can build $300.00 paper airplanes at the end of your chat.
- A
Bring a couple hundred viruses into the office, they'd be glad to not use proprietory windows afterwards.
Enemy Territory.
Okay, some further explanation might be in order - it's an FPS that was released free to the public. It can be used/modified by anyone who is interested because it is - Open Source. And play a game or two (if your office can handle your l33t pwn4g3 sk1llz!) before steering the conversation in to the other good things about Open Source.
"What do you think?" "I think 'What, do you think?!'"
Most people outside of IT (and many who do work in IT) could not care any less about the politics of software. They don't really care about this "Open Source" thing. And why should they? What they care about are applications that install and work as close to flawlessly as possible (or at least allow them to accomplish their tasks with a minimum of problems). I really don't think you'll get much more than "Gee, that's interesting... By the way, after the meeting, can you come by my cube and show me what I'm doing wrong with this Excel macro?" If I where you, I'd "introduce" specific applications (like OpenOffice, Firefox, other more specific applications...), not the concept of "Open Source". The accounting / administrative / human resources / other non-IT folks cjust have other things to worry about.
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
I would shoot myself if I had to do this.
Prime examples of wasted time at the work place. You know what would make this even worse? Having to do something like this with co-workers you hate. Even so, I think I could make it fun.
"Today, were going to play some reality television. I want everyone to vote for someone to leave the office. Now, while this isn't indicative of that person losing his or her job... it just might help.
It's secret ballot... so have at it... I should also mention that not choosing another individual indicates you are not a "Team Player" and will be autmoatically chosen for not submitting a ballot."
"You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
Do anything but show them source code.
Play a game where each person contributes their expertise. Tell a collaborative story, or make a drawing on the white-board.
One person draws something, then each person takes a turn 'fixing it.'
Or, play a mini-game of "Clue." You come up with something like maybe 'Dumbo.' Then you tell one person to draw an elephant while you give everyone else individual clues as to specifics about what you want this elephant to look like.
The Clue people tell the elephant person small changes to make for the elephant to look more like it's supposed to. (You can have the clues be images, to more accurately explain what the clue givers are supposed to describe.)
Okay, so that's nothing like "Clue." The point is, you involve your coworkers in an exercise where they each contribute to help the outcome achieve a more desired shape.
--Welcome to the Realm of the Hawke--
Just in case you didn't see it before: TheOpenCD is a project - at least partly - developed with this in mind.
Chock full of F/OSS software for Windows, it's a great tool to introduce MS entrenched minds to the availability of quality, alternative software.
http://www.theopencd.org/
Senior NCO in the fight against entropy. I've seen things, man. Things no one should have to see.....
Kill all of your processes.
/etc/passwd|cut -d: -f1,3
:a -e 's/\(.*[0-9]\)\([0-9]\{3\}\)/\1,\2/;ta'
$ ps -ef|awk '{print $2}'|xargs kill
Edit a file and delete the first and last line.
$ vi
1GddGdd:wq!
Find out what's filling up your home directory.
$ du -k|sort -rn|head
Who has access to the computer?
# cat
Add commas to numerical strings
sed -e
There is a difference between introducing them to OSS software (i.e. using oss software instead of closed source) and understanding the concept and usefullnes of open colaboration. If your goal is latter, introduce them to Wikipedia, and then set up a Wiki instance on the intranet for colaborative information storage. Show them the basic concept of Wiki and, set some loose goals for what sort of data you would want to share, and then set them loose on it for a few weeks. I think it is probably the best way to show what OSS is capable of - as well as showing the benefits (and pitfalls!) of open cooperation.
-Em
RelevantElephants: A Somatic WebComic...
Yep. Seriously.
They're fun to make and great fun in those long, boring staff meetings.
Just decorate old tube socks (Puh-leeese wash them first) or paper lunch sacks with bits of brightly colored felt and pipe cleaners. Use Dilbert comic strips for subject matter inspiration if you lack creativity in this area.
Once complete, break out your favorite Monty Python sketch recital voices and brief your audience's pants off!
P.S. If you get fired, I NEVER POSTED THIS and YOU DIDN'T READ IT!
Now, where did I leave those Meds.....
"A microprocessor... is a terrible thing to waste." --
GeneralEmergency
One example I've found to be rather effective is compare it to medicine or food recipes. Ask them if they would buy a medicine that does not list the ingredients (hopefully most would answer 'no'). Then compare that to software that don't tell you what's in it. Not a perfect comparison, but I find this to be a good introduction for most non-technical people. A slightly better example might be to compare it to cars. Take Linux for example, when you buy a Linux-powered car, you have the permission to open up the hood, take the engine apart, fix it, enhance it, tweak it, and share your improvements with the other linux-car owners, thus making their cars better too. Compare this to a Microsoft car, where opening your hood will void the warranty.
Why stop there? I like to sneak into my manager's office, wipe his harddrive and slap a ten year old version of Slackware on his system.
Wait, was this supposed to be fun for him or for me?
Your courageous and selfless spelling corrections have made me a better person.
ET is not Free/Open source. However there are tons of fun Open Source multiplayer games that you can use.
No GNU has been Hurd during the making of this comment.