In my line of work I get to test, try and evaluate all kinds of new open source software and the occasional new distribution flavor of the month. Sometimes it's a smooth process but other times I find myself casting a line in the lake of forums hoping to get a bite. In a lot of ways, this is how it was when I was first introduced to Linux in the late 90's. When I look back and compare my experiences then with my experiences now I see the progress we've made in a number of areas but I am left with one conclusion: we're not quite there yet.
We've all experienced the agonies of an app that just won't install or otherwise function as hoped for. When this happens, inevitably we all find ourselves grasping at the same tried and true straws we've know for years now: forum boards and IRC channels.
Using a forum board or IRC channel is a lot like trying to solve your problems by walking down a dorm room hallway. Room by room you poke your head in, say hi to everybody, and ask around quickly to see if anyone has an idea. The responses can vary depending on which door you knock on.
A lot has changed since I first started knocking on doors to solve my problems. First and foremost, there are a LOT more doors. Second, there are a lot more people to ask as open source finds itself becoming more and more mainstream. What doesn't seem to have changed much are the responses.
There will always be the self righteous neighbors. I knocked on one of these doors the other day. The first response was "why don't you just come out and tell us what you broke...". There's the newbie rooms full of happy people that are just as lost as you are and have huddled together in the kiddie pool. There's the oh-so-elite rooms (you know who you are Gentoo users!) who only have one response for any question "RTFM". Remind me to further rant on these types some other time.
Occasionally (and less and less by accident of late) you get lucky and find a room full of sympathetic techies. These rooms are filled with people who can explain your problems simply enough to enable you to actually fix something.
All of this leads to my point: those of us who are passionate about open source projects are by nature, somewhat evangelistic. We want to share them with everyone and convert the masses. Nothing is more frustrating than meeting someone who tried open source at one time and couldn't get the kind of support they needed and in anguish, scrapped the hole thing in lieu of the very matrix we're trying to unplug them from. I had the pleasure of sitting in an IRC room the other day when a complete newbie walked in. One by one, the entire room took turns walking him through a wide array of problems. In the end, he left the room excited. He'll be back soon and his questions will be a little more complex each time (a good indication that he's learning, and solving the easier stuff on his own).
You never know who's gonna pop their head in. It could be a complete newbie, it could be a professional with a tech issue his paycheck depends on (like myself). It could be the next Torvalds, in his ***formative years. Either way, how you respond will either encourage them, and swell our numbers by one, or discourage him, and everyone who will listen to him. Be nice. Be understanding. Most importantly, be patient with them. It takes a village, and you might be raising the next Linux fanatic.
*** Note: the use of the word formidable was removed for the sake of world peace.
Chase Crum is the IT Infrastructure Manager for Voicenation and a self-proclaimed Linux FANATIC.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Roll your own dynamic dns
20 min 6 sec ago
- Please correct the URL for Salt Stack's web site
3 hours 31 min ago
- Android is Linux -- why no better inter-operation
5 hours 46 min ago
- Connecting Android device to desktop Linux via USB
6 hours 15 min ago
- Find new cell phone and tablet pc
7 hours 13 min ago
8 hours 42 min ago
- Automatically updating Guest Additions
9 hours 50 min ago
- I like your topic on android
10 hours 37 min ago
- This is the easiest tutorial
17 hours 13 min ago
- Ahh, the Koolaid.
22 hours 51 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?