Tag Archives: Community

GoOSe Project: Progress toward Skein 2.0

As some of you may already know, I’ve been a part of this enterprise rebuild project for a while now and things have been going pretty well. Recently, though, I’ve made some good progress on our import and build tool, skein.

Skein’s goal is provide easy functionality for rebuilding SRPMS from upstream and import them into github, where they can be built using our koji instance. The process is actually easier than one might think:

  • skein request – Request a particular repository be setup on our github organization for the specified package. The package itself should be able to be requested from the SRPM, but that feature is not yet available.
  • skein query – To verify the request has been placed, this shows the open queries (by default).
  • skein show – For a particular request, show the detail of who requested and the purpose of such a request.
  • skein grant – Only an admin can grant the repository. Only members of the admin team on our github organization can grant the repository.
  • skein extract – Once granted, the SRPM can be extracted and placed into two basic directories:
    • /path/to/package/lookaside/ – contains the archive from the SRPM, usually a tar, tar.gz or zip file. The contents of this directory can then be pushed to the lookaside cache.
    • /path/to/package/git/ – contains the spec file, any patches and other sources that are not archives. A Makefile and sources file are also generated along with a .gitignore to provide useful functionality during the koji build

Other functionality is currently under development:

  • skein push – Once extracted and committed to the git repository, this pushes the git commits to github.
  • skein upload – Once extracted, this uploads the content of the lookaside directory to the lookaside cache at pkgs.gooselinux.org.
  • skein import – A combination of skein extract, push and upload, since that seems fairly logical.
  • skein build – Albeit mostly complete, it will need to be tested with an SRPM that has been run through this process.

I took a few minutes the other day and created a video of the completed process. I post this here for others to use for their benefit, but also so I can have it in another place besides my laptop.

Skein video

Cheers,

Herlo

The future, part 36 : UTOS

Ladies and Gentleman, Boys and Girls, may I have your attention please!

You know, I’ve always enjoyed that statement.  I love hearing it over the PA at the circus, at a restaurant when someone is about to make an announcement, or at a the start of a presentation at a conference.  Not sure why, but it just gets me all excited about the world, the future and I perk up wide-eyed with anticipation of what’s going to happen next…

I’m as excited as ever to say these words myself.  I’m so happy, in fact, that I wanted to share it with you, my dear audience.  My friends, colleagues, fellow UTOS compatriots, I would like to share with you some wonderful news!  The future is bright for free and open source software right here in our fine state.

Just look around you and you will see companies coming into Utah right and left.  While some do not appear open source friendly, don’t be fooled, they want you with your amazing Linux skills, or incredible Python Fu.  It’s you they want, Miss PHP master, scripting fiend, fanciful master of kickstart!  The real question though, will be, where will these companies look for their talent?

In my opinion, they will look to the great technical community already here in Utah.  They will strive to find and hire the best and brightest from our ranks.  They will want to hire those from our communities of experts, skilled craftsman, coders, system administrators and much, much more.  It is my belief that they will want to hire from those of you who participate in our Local User Groups and directly with Utah Open Source.

I say these things with great fervor and joy.  I’d like to announce the 2011 theme of Utah Open Source, ‘Community’.

My departure from the Executive Director position leaves me to work more closely with the UTOS board of directors.  In my stead, Victor Villa will take the responsibilities and leadership of the Executive Director.

Victor comes to UTOS with a great deal of community leadership.  As the former president of the Utah PHP User Group for the past several years, Victor grew the local PHP community every year.  He’s been a great supporter of UTOS since its inception in 2006.  With his foresight and leadership, I know that UTOS will continue to grow and flourish.  I am excited to pass the baton of leadership of UTOS to a man I have grown to admire and appreciate. Thank you Victor for taking on the role of leading Utah Open Source into this bright future!

During our conversations, I’ve asked Victor to spend some extra time during 2011 focusing on community growth and development.  With this in mind, Victor and I agree that 2011 will be a year of community building.  In 2012, the Utah Open Source Conference will return.  I will let Victor respond to my comments, with a post of his own, addressing the rest of his vision for UTOS.  I’m truly excited to be a part of UTOS, and with all of the goals Victor has set forth, I am very excited for the future!

Thank you for letting me be part of this community.  I will never forget you.  I will miss you all so very much when our family moves to Southern California in the fall.

Much Joy and Excitement,

Your friend,

Clint

Combating Apathy in [Free and Open Source] Communities — Part 3

This article is a part of a three part series, if you haven’t read the first part and second part, you really should.

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.

Combating Apathy in [Free and Open Source] Communities — Part 2

This article is a part of a three part series, if you haven’t read the first part, you really should.

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

Combating Apathy: How to Keep a [Free and Open Source] Community Alive

This June will mark the fourth anniversary of the creation of the Utah Open Source Foundation.  In October, we will be hosting approximately 500 attendees at the fourth annual Utah Open Source Conference.

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

UTOSC 2009: Breakfast is served!

As part of my effort to help out folks coming in for the Utah Open Source Conference 2009, we have filled up our household with out-of-towners. However, when I asked my awesome sweetie , Jennifer, about food, she had this reply:

21:37 <herlo> did you say you were willing to cook breakfast for us during UTOSC ??
21:37 <herlo> :-P
21:37 <herlo> I couldn’t remember if you agreed, or balked
21:37 <Jennifer> I did. I will make sure I don’t work so I can do it properly.
21:37 <Jennifer> 5 people, right. Plus us, of course.
21:38 <Jennifer> ?
21:38 <herlo> yeah
21:38 <Jennifer> Yep, for 3 days? I can do that. :)
21:38 <herlo> so far, I have Ian, Scott, Larry and Mirano and possibly Scott (from LA)
21:39 <herlo> it does mean that it has to be ready kind of early though…
21:40 <JenniferDean> Yep
21:40 <herlo> kk, grerat!
21:40 <herlo> or just great!
21:40 <JenniferDean> That’s what prep the night before is for
21:40 <herlo> lol, yeah
21:41 <JenniferDean> The only rule is: stay out while I’m cooking. Lol

So as you can see, I just had to comment about it right now!  Jennifer is awesome!

Looks like our guests will be well taken care of during UTOSC 2009!!

See you all there! October 8-10, 2009.  Register today!

Cheers,

Herlo

I’m Going to FUDCon

So it looks like my whining and moaning paid off!  I didn’t expect that anyone could help me, the money had been spent, things were cancelled and I was screwed!

I recieved a comment on my blog from Mo inviting me to stay at her and halfline’s place for the weekend of FUDCon.  So nice, but I still didn’t have the $600+ it would cost to come to FUDCon.

And then I received this email:

Clint,

Don’t cancel your trip.

Give me receipts,…

–Max

Wow! So I’m coming to FUDCon.  I’d like to thank Max, Mo, Paul (and any others I don’t know about) for helping me get to Boston.  I’m sure it’ll be a blast.

I’ve got some serious plans to make it worth Fedora’s while :)  I don’t think there’s a better way than to be included in the community than to know people care about you and want you to be a part of the community as a whole and to succeed.  I’m going to do all I can to make sure the money will be well spent.

So as I said in my reply email to Max.  Thank you! thank you! thank you!  FUDCon will be a blast!

Cheers,

Herlo

PS – I would also like to thank my employer, Guru Labs, for being so kind to let me attend my second FUDCon.

Fedora, Getting Involved Guide (GIG)

Recently, I’ve been very interested in getting involved more and more with the Fedora Project.  In fact, the latest project in which I’m involved, the Getting Involved Guide (GIG).

I started with this guide because my so-called friend Jared Smith (hi Jared!), introduced me to the original creator of this document, Paul Frields at FUDCon a couple months ago.  I started the hackfest portion, not entirely clear where I’d end up, but somehow I rolled back to hang with Jared and Paul while they were working on this Contributor Guide, if I remember the name correctly.  I got involved late in the day, and either my misunderstanding, or pure genius took over and the Contributor Guide (intended mainly for developers), quickly turned into the Getting Involved Guide or GIG, which had a much broader focus.

While I am happy to be a part of this guide, and have had a hand in changing its purpose, I’m not at all familiar with much of the Fedora Community processes.  Which, for this document to be successful, I am going to have to learn, since that’s the point of this guide to begin with, helping others get started when they want to help the Fedora Project.
Think of it this way, if you are a corporate entity, an individual, or a small non-profit group (like my UTOSF group) and want to give back to the community that has helped you so much.  How do you do that?  What’s involved in getting started?  What projects are out there where we can help?  Do we need to be developers? If not, what else is there for us to do?  Well, those are all good questions, and I am sure there are many, many more we haven’t yet considered.

I guess what I am doing here is soliciting from the general communities at large, what they’d like to see in this guide.  What confused them about joining a large project.  I’d also like to hear stories about being a contributor to the Fedora Project, and why you think its a good idea.  I want to take these ideas and integrate them into the Getting Involved Guide.  I want to take these issues and make it clear for others how to get involved, why its important, and show that value.

Currently, if you are a Fedora Project member, I have a document in gobby.fedoraproject.org called GettingInvolvedGuide, which you are welcome to modify as you feel necessary.  I may also be hitting you up to answer questions regarding particular processes in your group as well.

Cheers,

Herlo