Skip to content

FAIFcast thoughts

06-Jan-11

Finally got myself to listen to a “Free as in Freedom” oggcast (aka “faifcast”), specifically the newest episode 0x06.  (I’m not a big audiocast listener normally, to really make it worthwhile I have to be actually listening, and I don’t have a lot of deadtime in my day where my brain is unoccupied such as during a drive commute.  When exercising, I generally prefer thumping hip-hop.)

Of the two hosts, I know Bradley Kuhn from around the way and more recently as part of the larger group of voices discussing software freedom all over identi.ca.  As a latecomer to this new oggcast and not having heard their previous show, this was my first time listening to Karen Sandler (@kaz on identi.ca).  The two hosts have a good repartee, it’s clear why they enjoy doing this together, and they bring excellent information and insight to their topics, which mainly cover policy, legal, and related issues in the FLOSS (free/libre and open source software) world.  Sandler is the general counsel at the Software Freedom Law Center, and Kuhn is the Executive Director of the Software Freedom Conservancy.  So, it is literally listening to two experts in the field on FLOSS and its legal aspects discuss interesting and relevant topics.

Another reason I was inspired to write this post is in reaction to the latest show, where they discuss the issues and reasons around copyright assignment to appropriate non-profit organizations.  In their discussion around copyright assignment, Sandler had some strong points to make about how useful it can be in cases where code needs to be relicensed.  (To be clear, I understand their preference is, if copyright is assigned it should be to a non-profit organization, such as the Software Freedom Conservancy, that in turn makes contractual promises not to license the software non-free in the future.)

This topic sparked interest in me because of my own experiences relicensing the Fedora Project’s documentation from the deprecated OPL to the CC BY SA 3.0 Unported license in 2009.  In the post I wrote on the subject, “Why relicense Fedora documentation and wiki content“, I discuss clause 2(a) in the Fedora Contributor License Agreement (CLA), which I started referring to as “the nuclear option“, that allowed the project to sub-license contributions to the project under an equivalent or freer license.  Since the content we wanted to relicense (sub-license) was all new contributions (as opposed to content from an upstream), it was clearly something that could be sub-licensed under the CLA.

Without repeating all of the reasoning involved, it boiled down to this:

  1. We achieved a wide consensus from the community that they wanted the relicensing;
  2. We obtained permission to relicense from all substantive copyright owners (i.e., people who wrote the long guides not just short wiki pages) – even though they all had signed the CLA we considered it crucial that we have actual consensus to even proceed;
  3. We didn’t bother to contact wiki authors/editors individually, but we did multiple loud announcements to give people a chance to know, understand, and make reasonable objections – it’s important not to surprise folks;
  4. We used the nuclear option with great reluctance and only after effectively gaining the approval of the community.

This situation was necessary because the OPL we were using effectively put the Fedora Project on a content island, unable to interact with the growing body of freed content under the Creative Commons licenses.  The work coincided with the start of a review by Fedora Legal of the CLA overall, which has resulted in work to replace it with a simpler agreement that relies upon the acceptable FLOSS licenses and doesn’t assign these sort of additional legal rights to the Fedora Project.

So, the FaiFcast put me in mind of this situation where copyright assignment wasn’t involved, a different provision in the CLA was able to save us countless hours of work, and yet we were reluctant to use that provision and subsequently removed it from the next generation agreement.

Yet there is still a clause that seems to provide some protection against having to track down thousands of contributors in a future relicensing scenario:

The Fedora Project Board may, by public announcement, subsequently designate an additional or alternative default license for a given category of Contribution (a “Later Default License”). A Later Default License shall be chosen from the appropriate categorical sublist of Acceptable Licenses For Fedora.

Once a Later Default License has been designated, Your Unlicensed Contribution shall also be licensed to the Fedora Community under that Later Default License. Such designation shall not affect the continuing applicability of the Current Default License to Your Contribution.

Read the entire proposed agreement to understand all of the special terms, especially the very narrow definition of “Contribution”.  The goal, as I understand it, is to ensure continued freedom for contributed code or content by relying upon a simple agreement between the project and the contributor to use a permissive license now and forever.

Why relicense Fedora documentation and wiki content

Time to start Fedora GSoC work

05-Jan-11

As I explained in a previous blog post, I am not going to participate in Fedora’s Google Summer of Code presence this coming year.  If Fedora is going to participate, some of you folks need to start organizing right away.

In particular, Fedora’s GSoC team needs some people to work as program administrators, or “admins”.  It’s about taking responsibility for making sure we get ourselves together before, during the event, and in follow-up.  Otherwise, it’s not a ton of work, and it’s very rewarding to see improvements for the Fedora Project and students gaining greater experience participating in free and open source software.

Step one is to create, publicize, and help manage a wiki page of ideas for students.  You can look at the past year’s pages to see how to do it.

If you want to be involved in running the program, join the discussion group where much of this is organized and introduce yourself.  Old hands such as myself are available to help you make the magic happen.  You just have to be enthusiastic and interested.

Onion marmalade recipe first draft

31-Dec-10

I decided to make-up an onion marmalade recipe without doing any research.  Knowing the final result would still have an onion-y flavor, I figured on complementing it with other flavors that would let it be a sweet+savory topping for a nice hearty bread, quickbread, scrambled eggs, biscuit, steamed vegetables, even a plain grain such as white rice and a touch of salt.

  1. Slice the flower end (paper pointy tip) of nine or more large yellow onions.  Peel onions, leaving root end attached.
  2. Hold root end in an off-hand pinched together fingertip, then slice from the flat end to make onion rings approximately 0.25 inch/0.5 cm thick.  Slicing this way cuts across the grain, making juice-release and sugar-absorption easier.
  3. Fill a five quart/four liter heavy-bottomed pot with the onions, flat and layered on each other.  If you have room, you can add the other dry ingredients at this point.
  4. Add 0.25 cup of water to the pan to keep the bottom onions from scorching  during initial heating.
  5. Turn the pan on very low, just enough to turn the added water to steam, which helps the onions release their juices.
  6. Cover the pan, keep the heat low, and check infrequently.  Use a large spoon to lift and turn the onions until enough juices are released that the onions are covered in juice.
  7. Add 1 teaspoon ground cinnamon and five cinnamon sticks; you may also add other sweet/savory spices, such as a few cloves, a few star anise, a few pieces of fresh or dried ginger, ten whole allspice berries, and so forth.  Add 0.5 teaspoon of salt.  Be light on this, the point is not to make it overly spicy, just provide more background support.
  8. Use a vegetable peeler to remove the orange part of an orange, leaving all the white pith behind.  Cut the peel in to two-inch/four-centimeter long pieces and add to boiling onions.
  9. Juice four oranges, removing the seeds and large pulp pieces.  Add to the boiling onions.
  10. Add three cups of evaporated cane juice such as turbinado (succanat or similar is OK, be careful not to use brown sugar or similar unless you can deal with the strong molasses flavor via spicing) to the boiling onions.  Other sweeteners could be substituted, but may leave a runnier consistency unless a proper caramelization is created  in the final juice reduction.
  11. Cook uncovered for two or more hours, reducing and concentrating the juices.  Turn the onions infrequently.
  12. When the juice is low enough to make the onions at danger of scorching or caramelizing the onion fibers, remove from heat.  Put onions in to colander and drain, then add the drained juice back to the pan and continue reducing over medium-low heat.
  13. Reduce, stirring more closer to the end, until a thick syrup, several minutes after the last wisps of steam have risen.  You want it to caramelize slightly (very soft ball stage?), but watch carefully for scorching.
  14. Add in any remaining juices that have drained from the onions, reducing to a thick syrup.
  15. Add syrup back to onion mixture, and carefully mix with one or two soup spoons until even consistency.
  16. Resulting marmalade should be very thick with no apparent wateriness. Put in clean jars and refrigerate. Eat soon!

My first run of this resulted in one and a half quarts of marmalade.

This is a first draft of the recipe, pulled from memory, and done entirely without additional research.  I am certain that the recipe needs fixes, and now we have something to work from.

Hope your 2010 is finishing well, and happy new year/2011 to you and yours.

Summer of Code – time to do something, anything … but not by me

22-Dec-10

Folks:

For this coming year, if Fedora chooses to participate in the Google Summer of Code (and I think we should), I have decided that I am not going to be involved.

This is not complete abandonment.  In fact, this blog post is the first of potentially several that can be part of a package of mentoring-the-mentors as I pass on my mantle of leadership.

So if you care about the future of Fedora’s participation in Google Summer of Code (GSoC), for the love of all that you hold dear and then some beyond that, please read on. More…

Lindependence Hour starting up in Santa Cruz

23-Nov-10

Larry and Drew got talking on #lindependence about the idea of holding a regular hour-long Linux event at a local coffee shop, and they pulled me in to the idea.  The event is styled on the Ubuntu Hour concept.  In discussing it, Larry really wanted to emphasize a distro-agnostic viewpoint.  I like Larry’s approach.  First, meet people and talk with them about Linux, open source, and software freedom.  Second, find out what’s important to them and try to help them find a Linux community that matches their personality, needs, social circle, etc.  In doing the event, be welcoming to Linux users of all types.

The details:

  • What: Lindependence Hour to discuss GNU/Linux, software freedom, and open source.
  • Where: Santa Cruz Coffee Roasting Company, 1330 Pacific Ave., Santa Cruz, CA. http://www.santacruzcoffee.com/
  • When: Wed. 29 Dec. 2010 from 6 pm to 7 pm PST (1800 to 1900) — repeats last Wed. of the month.
  • Who: You, if you use or want to use Linux, such as Fedora, Ubuntu, or Android.

Any planning that I do will also include Fedora components, so we’ll keep those details on the Fedora wiki.

First fall textbook sprint

05-Nov-10

This Monday 8 November from 1600 to 2200 UTC we’ll be having the first writing sprint for the next version of the Practical Open Source Software Exploration textbook.  Anyone interested in helping or watching should meet in #teachingopensource on irc.freenode.net (webchat interface.)  You can attend all, some, or none of the sprint. 🙂

I’ve been having a difficult time getting organized and starting the big work on the next edition of the textbook. However, my recent calls for help have gained a fair amount of attention and multiple really good offers, so we are clearly underway again.

My goals in calling for this first sprint are to:

  1. Start a writing rhythm for the team;
  2. Take care of some administrivia (decide upon weekly work times, order of work, etc.)
  3. Get some initial writing done that may still help the Teaching Open Source professors who are using parts of this textbook this school semester.

See you on IRC bright and early (for me) on Monday!  (This weekend is the end of daylight savings in most of North America.)

Using Four Seasons of Code to help run Fedora Students Contributing program

27-Oct-10

Anyone interested in helping us setup, run, and use the Four Seasons of Code (FSoC) tool for the upcoming Fedora Students Contributing session?

FSoC is a web-based tool for administering a student contributing program — handling proposals, commenting, automatic reminders, and so forth.

There is a running instance to look at, and we could get a similar instance running on a Fedora Infrastructure public test server.  We have a ways to go for it to be fully hosted by the Fedora Project, but why not try using it for the next session?

Please pass on the word. Anyone interested should join the mailing list to discuss it.  I’m available for direct questions.  Reach out, if you think you might be interested, I’d like the chance to talk with you.  Thanks.

Useful guide’s ideas attract people to a project

25-Oct-10

One of the response’s I got to from the call for writers for the Practical Open Source Software Exploration textbook was an offer of an  excellent content source, Terry Hancock’s book Achieving Impossible Things With Free Culture and Commons-Based Enterprise.  This is a great example of a longer work that the Practical OSS Exploration textbook and The Open Source Way handbook are standing on the shoulders of.

One of the articles that comprise the book’s source is “Ten easy ways to attract women to your free software project“.  Actually, as Terry points out in the article introduction, nine of the ten ways are clearly useful for making your project more friendly for anyone and especially women.  That means implementing Terry’s ideas covers double — egalitarian attractiveness of the project while adding to the solution of the serious gender imbalance problem in free and open source software (FOSS).

There is a lot that makes this article great.  One part is the quality and quantity of research and supporting evidence.  I found the explanations of the different ways to support women instead of just men in a project to be very compelling.  I suppose some people might find it hard reading all of that, especially if it is the first time they have faced up to how easily a mono-culture arises when it is just men involved.

In reading over the points, I was very pleased that I see initiatives in the Fedora Project to address nearly all of the points there.  As the author points out, these ideas have been floating around.  I see projects such as Fedora have implemented them in a semi-haphazard fashion, partially because we haven’t had a guide.  I’m excited to have a chance to extrapolate these points in to The Open Source Way, as well as the Practical OSS Exploration textbook.

My only complaint about the article is the word “easy” in the title — I suspect that fell from the modern style of doing lists of how-to items as articles and blog posts.  I’m not sure that all of the items are easy, in fact I think changing an existing project to use a mailing list instead of a web forum would be a huge challenge.  My solution is to find ways to bring the forum up to the importance level of mailing lists, somehow.

Big weekend in Utah

05-Oct-10

It’s the last day flurry around here as we get ready for Utah Open Source Conference (UTOSC) this weekend.

On Wednesday, my girls and Larry and his girl are catching a train in Emeryville, CA.  It’s a 19 hour journey to Salt Lake City, which seems long but is only 7 more hours each way than driving without all the downsides of driving.  Also, it should be an awesomely beautiful ride, even at night.  We’ll get a chance to finish our presentations, explore the train, and relax.  Also, sleeping is more comfortable than in a driving car even without a sleeper car.

If you are attending, or know anyone else who is, here a list of the talks we’re giving:

Wow, that’s a lot of stuff!

Looking forward to the train ride and the chance to meet folks at a conference that is new to me (first UTOSC for my girls and me.)

After posting this, I was reminded that Ryan Rix is doing a BoF, Fedora, FOSS, and Schools.. The story of Fedora Campus Ambassadors at 6:30 on Thursday 07 October, and Robyn Bergeron is presenting Tour de OMNOM (Open Marketing, not Obscured Marketing at 1:30 pm on Friday 08 October. Of course, Jared Smith is giving the Thursday night keynote at 4:30 pm, Swimming upstream: How Linux distributions help the entire community.  Jared is also giving a second talk, Automated Deployments of Linux in a Small-business Environment at 6:00 pm Friday 08 October. *whew*

Looking for writers for Teaching Open Source textbook

23-Sep-10

Hey!

Do you want to help us write the next version of the first textbook that teaches open source participation?

We need writers, editors, reviewers, and researchers to find or create content on:

  • Testing code in FOSS communities.
  • Working in open communities.
  • Different types of open source community cultures.
  • Open communities and diversity.
  • Licensing FOSS  code.
  • Threats and risk analysis of FOSS as a technology choice.
  • FOSS business models.
  • Determining program requirements.
  • Designing FOSS programs.

Join the mailing list and let us know what you are interested in, or you can email me directly.

Note: The textbook Practical Open Source Software Exploration is licensed under the CC BY SA 3.0 Unported.  We are very interested in reusing and modifying existing content that is compatibly licensed.  This is especially true if we can use the content as an active downstream.

Tl;dnr version follows …

More…