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.

Cheers,

Herlo

While at work today, setting up test environments for Ubuntu Gutsy (7.10), I needed to check something with the ubuntu.com DNS entries. So I ran the following:

# dig -t ns ubuntu.com

And got something very interesting and entertaining. Can you see what it was? Yes, the mythic-beasts are definitely alive and well within Ubuntu! Now that you are having fun, try these commands immediately afterward:

# dig -t ns mythic-beasts.com

And

# whois mythic-beasts.com

Note the other nameservers. Quite an entertaining 5-10 minutes of your life.

Enjoy,

Herlo

Sorry Aaron if I am stealing your thunder….

Enjoy,

Herlo

What’s wrong with SUSE you ask? Just about EVERYTHING! I’m not comfortable at all in this rancid environment. It sucks the life right out of you. I hope some SUSE people come running to save me from this turmoil I feel as I currently hate using this distro. Here’s my first impressions: (beware, the list is rather long)

GOOD

The items below are positives and the openSUSE team deserves credit for all of their hard work in these areas.

• Wireless works (+1)
  • My Intel wireless card from my T60p is recognized and associates with my access points
• The nautilus-open-terminal package is enabled by default (+2)
  • This is the right-click on desktop –> Terminal option, (something severely lacking in fedora and not easily installed in a kickstart)
  • Having this feature, its very simple to get started with the terminal which is definitely needed for the power user in me
• Install allowed me to choose not to use their grub (0) [while this is nice, if I had installed their grub, it would have wiped out my fedora grub components]
• zypper is much improved over the previous rug (10.1) tool (+1)
  • still needs work though
  • easy to add repos compared with fedora
    • packagekit can solve much of the incontinuity in fedora
    • though its nice to have a simple gui to add repos, knowing which repos is still a bit of an exercise in futility.

Positive Score: +4

BAD

Whle there is some good in openSUSE, its apparent to me that there is much to be improved.  As noted below, many more things are in need of improvement, to put it nicely.

• The install takes much longer than necessary (-3)
  • Still uses ugly YAST text user interface
    • YAST didn’t recognize my video driver, but could have just used the VESA driver for the gui install
  • Asks too many questions about details that could easily be simpler
  • Did not work well with other OSes (GRUB)
    • YAST installer wanted to overwrite my fedora GRUB configuration, shouldn’t Linux play well with each other in this sense?
• One-click install is more like 10-click (-1)
  • From opensuse.org, you can do what is called a “one-click install”, and about 8-10 clicks later its installed. If its one-click, its should be one (maybe two) clicks total.
• The initial GNOME config of openSUSE is too Windows-like (-1)
  • If I wanted my Linux desktop to look like Windows, I’d use KDE (or even run Windows)
  • It has only one bar, and at the bottom, not enough room for status apps
  • I had to add workspaces as only one was provided by default, that seems limiting
• bluez-gnome doesn’t have hidd or any sort of recognition for my bluetooth mouse (or anyone’s bluetooth mouse, for that matter) (-2)
  • dbus fails to recognize bluetooth mouse
  • There’s even a bug on it blaming others, yet it works in Fedora – https://bugzilla.novell.com/show_bug.cgi?id=330461
• The bash prompt is ugly - (0)
  • This one is a personal preference, but its hard to tell when I am the root user and when I am not. As such, I will modify my .bashrc and fix the PS1 value
• The wireless driver for my T60p is not the new iwl3945, but the ipw3945 proprietary from intel – (-1)
  • The open driver has been out for quite some time
• Proprietary codecs were not easy to find, nor install (0)
  • Fedora doesn’t make this simple either really.  Yet, when I found them in Fedora they worked first try, gstreamer failed miserably several times in openSUSE
  • an attempt at a codec buddy like tool was made, but doesn’t work…
• zypper does not inform you of the dependencies needed to install even though it reports how much it will download (-1)
  • I want to know what packages I’ll be installing before I install them

Negative Score: -9

Total score for day 1:  -5 OOPS – that’s not good!

To be honest, I think I’m being very generous in some of the points I’m giving.  OpenSUSE makes it very difficult for my lifestyle so far.  I’m not sure what they can do with 10.3 to make it better, but I’d like to hear comments and suggestions on ways to help.

I’m sure hoping that day two will be better.  I’m already starting my list and will be testing such things as; video, development, lvm, raid, kvm/xen virtualization and much, much more.  As I continue to suffer through this bluetoothless mouse world openSUSE has created for me.

Cheers until tomorrow,

Herlo

In the meantime, I’ve got a post that may knock your sock off! If you’ve not yet heard about it, there’s a new transport protocol on the way, and its called Stream Control Transmission Protocol (SCTP). Its an amazing new way of looking at the network, providing multi-stream transmissions through one port.

Have you ever thought it would be nice to take three network connections, one ethernet, one fiber and one wireless and bond them?  What about using those three connections to stream video?  Or to manage data on one and have a control connection on another?  TCP/UDP can’t really do this for you without some external elements, but SCTP might just be the thing you’re looking for, and its already here.  Currently in testing, SCTP looks to be a great replacement (augmentation) to the already popular TCP and UDP prototols.

Linux Journal is doing a 3 part series on this protocol which started in last months article: Introduction to Stream Control Transmission Protocol.  This article is a quick look into how this protocol works.  The follow-up, in this month’s issue (not yet available for non-subscribers) talks about how the protocol is implemented in the Linux kernel and even gives some good code references.

I suggest you take a look at SCTP if you’ve not yet heard of it.  I am very excited to see where this protocol could take us in the future.