How do we address this problem?  Who does it?

In other words, how do small to medium communities battle Apathy?

In all honesty, I don’t have the answer for this question.  If I did, I’d be preaching it to every community group that would listen.  But it does occur to me that the/re are a few things the folks in charge can do to help.  And some of these are documented by the larger communities too.

1. First thing that comes to mind is to build a proper structure.  A meritocracy where those who do the work can decide what gets done.  As most will note, this is no different from any other Free Software development project.  But we need to state it out loud.  If you do the work in the community, you get to decide how the community functions. As part of this process, community leaders can define a loose structure where others can join up, and help build where they find holes.  It’s a definite organic structure, but one that really works well when encouraged.
2. Have something people want, and give it to them.  For us, it’s the Utah Open Source Conference and the other events the Foundation has been providing, like hackUTOS, Nerds in the Sun, Geek Lunch, etc.   Most of these events are free and for anyone to enjoy, learn and network.  However, I can see the need for even more events and services that UTOS can provide.
3. Remind people regularly that community is here.  Reminders are very important.  It’s like what Coke and Pepsi do, constantly remind you they are out there.  The only real difference is that they are looking to sell you something for money.  UTOS and other communities are really here to help you grow and learn.
4. Constantly invite people to join the community and help.  The community is a process that is always evolving and growing, people are needed to make it evolve and grow the way they see it.  Notice I said the way they see it.  It’s up to the community members to decide where the community goes.
5. Get out of the way.  This is somewhat of a corollary to step 4, but it’s really important to point out.  Once the community machine is going, don’t put process and leadership in the way.  The community can do what it needs to do if we just get out of the way, don’t be an obstacle to progress of the community.

As UTOS, we’ve excelled at some parts of this list, and failed at other parts.  I suspect many of the other communities around have succeeded at some of the parts as well.

Mostly, I wrote this to help me understand what the goals for UTOS will be as we start to expand into a more regional community.  But I think these things can help us all deal with apathy and encourage others to get involved.  I hope to hear from the community on this as my article is definitely a work in progress.  I believe I’ve got a good set of problems and possible solutions, but it’s definitely not me that is going to implement most of them.

Please take a few hours out of the month of June and help us grow and become an exciting, active prosperous community.  You’ll feel better for it, and you’ll definitely make a few friends along the way, grow your skillset, and possibly even encourage someone else to join up and help.

One of the coolest things to attend has arrived here in Salt Lake City.  That’s Agile Roots next Monday and Tuesday!  I’ll be going this year and am very excited to see presentations that will likely enlighten and excite me to do more with Agile.

I look forward to seeing you all there.

Cheers,

Herlo

Why don’t more people actually volunteer 2-3 hours per month?

One word, Apathy.  Yes, apathy.

I believe apathy is what kills communities around the globe.  They don’t have to be any specific type of community, but when someone, or enough people stop caring about a particular activity, event or cause, the community will die.  I don’t have any cold, hard facts on this, just my experiences, what I’ve read and my gut telling me it’s so.

If it were up to me, as an individual running a medium sized community conference based around Free and Open Source Software, I’d suggest that everyone come and spend 2-3 hours volunteering at the event.  While I know that’s not realistic, it can combat the apathy of which I speak.  But that’s kind of a problem too.

Where are we heading with this discussion?

For one, there are only so many volunteer positions available at the Utah Open Source Conference, or at a LUG meeting, or any such event.  But there are events that are currently not happening.  Imagine if everyone in the FOSS community in the Mountain West spent those 2-3 hours each month either helping a particular event, or creating their own special event or group.  What would the FOSS community landscape look like?

Each month I run into at least 5 people who want to help out within UTOS.  Each time I tell them the same thing, we have lots of things we need help with, we meet here at this time each month and would love to have you attend.  On rare occasion, we get a new volunteer coming to our meetings.  Sometimes they stay, sometimes they realize it’s too much and other things are a priority, and sometimes, they get so excited, they become one of the Utah Open Source Foundation’s ‘Core Team’.  So far, it’s been working well, but recently, we’ve been experiencing growing pains of our own and a little apathy as well.

Another thing to note, larger communities tend to have already dealt with this problem and have a plethora of answers for dealing with things like Apathy, a lack of knowledge and all of the other standard problems that smaller communities must deal with to thrive.  Most of those answers aren’t documented anywhere, at least not very well documented.

How does a community suffer because of apathy?

I am going to use the Utah Open Source Foundation to give some examples of where we fail.  Currently, I fear that our community suffers from apathy for a few reasons.

1. The economy.  While it’s definitely important for people to have jobs, a paycheck and a promise of more work, I find that this is among the lamest excuse people use for not helping.  If you aren’t participating in the community, you are doing yourself a disservice.  Just think of all of the lost opportunities for employment, education, skill improvement (aka resume material) and networking.
2. Family.  Again, I find that a lot of people in our community use their family as an excuse for not participating.  I’m not saying that families aren’t important.  In fact, I would say that participating in the FOSS community is a perfect example of how to show your family what you do, as well as encourage them to be part of a community and volunteer their time to their passions.  Families do take time, but I can guarantee that everyone can find 2-3 hours per month to volunteer.
3. Time.  While possibly related to the other two issues, time itself can get in the way of volunteering to help the community.  People regularly fear that they can’t dedicate enough time to help, when a community really just wants people to dedicate a few hours a month.  If you are spending a couple hours a month in front of your TV, you could cut that down and spend it helping your community instead.

Watch for part three of this series next week.

Cheers,

Herlo

What started out as a simple idea in my backyard in Springville, Utah has blossomed into something much larger, a community of people who want to participate in the coolest events in the Mountain West.   Many of those events are hosted right here in Utah.

While there are other, larger communities in cities like Boston, New York and Los Angeles, the Mountain West has something that most other communities don’t have, a sense of volunteerism, community and brotherhood.  This even holds true for the most part in the Free and Open Source [FOSS] community.  I’ve really enjoyed being part of the Utah Open Source Foundation and Conference for the past 4 years and look forward to seeing it grow beyond Utah and its humble roots.

There are some really good examples of the FOSS community coming together right here in the Mountain West.  These include Local User Groups like the Salt Lake Linux User Group, Idaho State LUG, MontanaLinux.org, Rexburg Open Source as well as some great community events like AbleConf, PodcampSLC, Geek/Blogger Dinners, hackUTOS, BYU Unix User Group Installfests and many more.

While each of these events are great in their own right, there could be so many more.  But why are there not more amazing, or more complete events?

My real question here is why aren’t there more people helping do more of these events?

If I must use an example from my experience, I find that a lot of people really enjoy attending events and networking with others.  They believe that when they do this, they will have stronger relationships and when (not if) they need to change jobs, those they networked with will likely know of a position available.  While this is generally true, it seems to me that if people actually helped with these events, they’d actually have more contacts and more opportunities when they need to find work fast.

Just think about that premise for a few minutes…

If you spend just 2-3 hours per month, yes I said per month, volunteering your time toward the FOSS community, there will be many more opportunities for you when you need it most.

Read the next segment on ‘Combating Apathy in Communities‘.

Cheers,

Herlo

From the announcement by Jesse Keating:

The countdown is on: Fedora 13, "Goddard," is set to launch in mid-May.
Fedora is the leading edge, free and open source operating system that
continues to deliver innovative features to users worldwide, with a new
release every six months.

But wait! What's that? You can't wait a whole month to try out the
latest and greatest in Fedora's leading-edge technologies? You want to
be the first to see what's new? Well, you're in luck. The Fedora 13 Beta
release is available NOW. Hop on board and take a tour of the rocking
new features.

Get it here!!

I’m downloading the LiveCD version right now to try out on my laptop.  Consider helping out by testing the new Fedora Beta as well.

Cheers,
Herlo

I spent the morning at PodCampSLC 2010, including my presentation at 10am entitled ‘Capturing audio and video on the cheap’ or ‘How to keep the wife happy while buying lots of electronic equipment’.  I’ve been tinkering with audio and video recording equipment for several years now as part of the Utah Open Source Foundation and the Utah Open Source Conference and figured I had a lot to share.

My presentation slides were pretty basic, but cover some of the equipment I have purchased on the cheap.  In addition, we recorded the presentation using FreeSeeR, a free software application for  recording the desktop screen, external video and/or audio.

Enjoy the presentation slides and video as I really enjoyed presenting and am looking forward to PodCampSLC 2011!

Cheers,

Herlo

I was saddened to hear this, Drew and his crew have been doing a bang-up job and have been great hosts.  We will surely miss the BetaLoft.

As all good things must end, I’ve decided to stop holding the SLLUG Daytime monthly meetings as well. We’ve had a good run and SLLUG Daytime has been decently attended.  However, for several reasons which I will not go into here, I decided that I cannot run SLLUG daytime.  If someone else is interested in pursuing the continuation of SLLUG Daytime on their own, I’d be happy to hand over the reigns.

But there is some good news to go with the bad.  In the future, I plan to replace SLLUG Daytime with something of great value.  Something we can do regularly as well, maybe just not monthly.

I want to thank all of those who’ve ever attended SLLUG Daytime and have made it such a success.  I especially want to thank those who presented, as I know your time is precious, but you chose to prepare and share with us.  A special thanks to the folks on the SLLUG board who graciously let us use the SLLUG name, it was much appreciated.

In the future, watch for more activities from the Utah Open Source Foundation, as well as more opportunities to participate in the community and grow free and open source software.  I’m excited for the future.

Cheers,

Herlo

Node.js – building massively parallel applications with javascript and epoll

Node.js [http://nodejs.org/] is a framework for rapidly building massively parallel network applications using non-blocking io. It’s built on the performant v8 javascript engine [http://code.google.com/p/v8/] which compiles javascript to machine code at runtime. Node is similar in design to systems like Ruby’s EventMachine [http://rubyforge.org/projects/eventmachine/] or python’s twisted [http://twistedmatrix.com/trac/]. It’s suitable for building chat-like protocols, comet servers, mmo game servers, etc. This session will cover some of the basics of how to build and install node.js as well as analyze some demo programs.

If time permits, I might talk a little bit about python’s twisted and compare some programs written using twisted/node.js

About Shane Hansen:

I’m a Software Engineer working on Backcountry.com’s replatforming teams. Prior to that I worked on projects ranging from compliance tracking software for the goverment to building  mathematical models for reflectometry to immune system modeling. I’m interested in open source software, web standards, high performance computing and application architecture

Meeting Location:

BetaLoft (http://betaloftslc.com) is located at 357 W 200 S. Upstairs in Suite 201. Salt Lake City, UT, 84101

Betaloft is a coworking space in the heart of downtown Salt Lake City founded by Drew Tyler.

We are a community of freelancers, independents and work-from-home people, who have an interest in getting out of our dull work day and participating in a community that’s designed to support and encourage people who make a living doing what they love.

We provide communication tools, events (social and educational), as well as a physical space to work and collaborate.

See you all there!

Clint

Today, I found myself needing to enable the network (using dhcp) from the anaconda command line (the part that says boot: when you load a CentOS/RHEL/Fedora install disk).

I needed this because I was providing a bit of local media to our external employees for them to use to install, but I had 3 yum repositories I wanted them to be able to use for a few additional rpms I provided.

So, I popped into one of my common support channels and asked the question:

16:11 < herlo> looking for an option that I can put on the anaconda boot: prompt that will force a
               dhcp request even though the install is from a local disk.  I have repos that are not
               being accessed because the network is not being enabled.
16:11 < herlo> things I have tried
16:11 < herlo> ip=dhcp
16:12 < herlo> boot: linux noipv6 ks=hd:sdb1:media/kickstart.cfg ip=dhcp
16:20 < herlo> okay, so for those who might care
16:20 < herlo> if you do
16:20 < herlo> boot: linux asknetwork ip=dhcp noipv6 ks=hd:sdb1:media/kickstart.cfg
16:20 < herlo> anaconda will force a network dhcp request :)
16:20  * herlo is happy again

As you may have noticed above, I resolved this issue without any assistance from the channel, and it only took me 10 minutes to do so.  I found my answer by trial and error from a great page on the fedora wiki: https://fedoraproject.org/wiki/Anaconda/Options

Probably the only thing I wish was documented on that page was when each of the options started being supported in anaconda.  Otherwise, thank you to the folks that wrote and maintain that page.

Cheers,

Herlo

As usual, come from 11:30am-1pm at BetaLoftSLC (357 W 200 S #201)  - http://betaloftslc.com

This month, I thought I would share a basic git introduction.  In my opinion, the best Source Control Management (SCM) system out right now.  I’ve been using it for nigh on a year and I have converted a few systems over to it from svn.  This is more of a work session than a presentation, so come on down and learn how to use git.  It is recommended that you bring your laptops with you as that will benefit more if you do.

Some suggested topics I can cover:

• Local and remote git repositories (different workflows and other fun stuff)
• Using git-svn to ‘convert’ from svn
• Comparing Distributed Revision Control with Traditional (non-distributed) Revision Control
• Git hooks, why they are valuable and when to use them
• Other basic git discussions

See you all there.

Cheers,

Herlo