Skip to content

Seek ye students

29-Mar-08

In the middle of the Summer of Code proposals process and it’s been a mixed yet mostly good experience. We still have room for more proposals, so keep helping interested students and encourage them to get in a proposal for Fedora or JBoss.org. We’ll know at the beginning of next week if the student deadline is extended; currently 31 March still stands as the application deadline.

We’ve had a huge increase in the number of mentors. Where last year we were a little short handed to start, this year we have a very large pool, nearly eight times what I saw last year. Wow. My people are really showing themselves. I’m proud; I mean that.

We’ve had a slight increase in applications so far, maybe twice the number I recall from last year? These aren’t statistics, just a quick gut survey and recall. But definitely more students. We suppose there will continue to be new applications right up to the deadline. As I did in previous years, I am not going to review applications until the deadline. You can do as you wish. It is likely that we’ll divide up the proposals to have mentors focus on one or just a few applications.

If the student application deadline is extended, that would be good for Fedora and JBoss.org. We could use a bit more time to get the word out and attract more students. I suspect Fedora is a bit hard to categorize for students. It is downstream of many projects, yet there are many, many Fedora SIGs and other sub-projects that it’s hard to know where to start. JBoss.org is equally difficult in a different way. There are 42 projects currently on the JBoss.org projects page, and some dozen plus ideas on the SoC ideas page. It’s very focused as a project (application server and components), but it is a large project with hundreds of contributors creating a broad-range of components.

Thanks again, mentors, we’ll definitely have work for you in reviewing and helping to tune the proposals. Keep encouraging students to apply, especially if there is a week extension.

Document Freedom Day and a taste of bittersweet irony

26-Mar-08

While I was enjoying my colleague Ruth’s video for Document Freedom Day, I was struck by the irony that to get her message out widely, she was forced to write to a non-free format (Flash). “From our frying pan we leaped … and landed in another frying pan.” Fedora is often in this situation where, regardless of our stances, we are relying upon video on You Tube to convey a message. Another favorite irony on You Tube is the “How software patents work”, which conveys it’s message using Flash that relies upon patented codecs for rendering video and audio.

Anyway, Ruth’s video is a great juxtaposition of the various hard formats (paper through Betamax to MicroSD flash) that have gone by the wayside over the years, and a reminder of what is at stake with document formats holding our copyrighted content hostage:

Happy Document Freedom Day!

Student proposals for Summer of Code 24 to 31 March

24-Mar-08

One week window to choose and propose.

If you are looking to be a mentor, you need to sign in with a Google/Gmail account and request to be a mentor of “The Fedora Project & JBoss.org”:

http://code.google.com/soc/2008/mentor_home.html

Please do that immediately, thanks!

Chicken excitement

18-Mar-08

We’re getting ready to finally get chickens for the first time. Our neighbor, who we’re sharing the flock with, has done it before. Micah has been a great help in motivating, as well as working with me to get the henhouse in order and figure out the semi-permanent coop and ongoing daily living situation.

Reading books. I guess we have to wait until first week of April for the chicks to arrive at the feed store. We decided to follow the feed store route because then the kids get to pick the chicks by personality and such.

Better hurry up. Since dragged the gypsy-wagon-prop turned play house out to work on it, the kids have been using it as a play house again.

Summer coding 2008 with Fedora and JBoss.org

17-Mar-08

Just spotted the word that the combined projects of Fedora and JBoss.org are accepted as a mentoring organization for Google Summer of Code 2008.

Fedora’s project ideas page is here, and JBoss.org’s is here.

This is the first year that the two organizations have worked together. This was partially at the direction of Google; with so many organizations vying for mentoring slots, it made sense for us to work under one organization. One of my jobs, since I sort-of have a foot in both worlds, is to help us work together effectively.

Now our work in both Fedora and JBoss.org is:

  1. Fill up the ideas pages more
  2. Talk with potential students
  3. Answer questions and encourage people to make proposals

Interested students should be told to look at the ideas pages and the main Google Summer of Code pages.

One more tip: many of these students are new to open source projects. There is plenty of reading they can be doing to understand how the Google side works; make sure they do that reading and don’t get you to do it for them. You are looking for students who know how to ask smart questions and stuff like that. Or at least show the possibility of learning those skills quickly.

More to come via the Fedora planet, especially since Bob McWhirter, the JBoss.org lead, is aggregated there. Also, watch the Fedora Summer Coding 2008 pages. Mentors and those interested in mentoring should begin discussions on fedora-mentors-list.

2 hours 19 mins until wiki freeze of Docs/Beats/

16-Mar-08

… then we’ll finish edits and begin conversion to XML. The POT file is due out to Fedora L10n in 26 hours and 19 minutes …

Update: oh, yeah, you might have the Fedora 9 release notes schedule memorized, or know that 16 March at 23:59 UTC is when the Docs/Beats/ pages on the wiki are procedurally frozen for final edits and conversion to XML. 🙂

Fluendo, Bastien, et al — I’m sorry fwiw

16-Mar-08

Since I can’t apologize for the Fedora Board, I’ll apologize and explain for myself. Despite feeling that we are doing the best we can for Fedora in this situation, I feel bad that we abused our relationship with Fluendo.

We once again are in the midst of making the same mistake we made for Fedora 8, that of reviewing and trying to fix codeina very late in the release process. Greg is right that Fluendo is not being treated well in all this. AFAIK, the Fedora Board never wrote a detailed functional spec on what we expected codeina to do beyond provide a better dialog box than, “The codec you want is not installed, whatever a codec is, sorry.” Without that spec, Fluendo went and did what they thought was the right thing, which just doesn’t happen to fit in with Fedora’s mission of advancing free and open source software.

The original work of CodecBuddy done by the Fedora Board was before I was appointed, and although I was interested I didn’t pay much attention in advance to how the process went. This is a problem in free software — sometimes we don’t show interest in a project until it does something we don’t like, when it’s too late to easily fix it.

That is exactly what happened. Late in the Fedora 8 testing cycle I got a peek at how codeina behaved, and I was thoroughly shocked. It had very little explanatory text, just a link to CodecBuddy (iirc), and lots of up-front web shopping links directly from the Fedora desktop. Where was the user education? Why was it not there in favor of a list of for-sale closed-source, patent-encumbered codec plugins?

At that point in the Fedora 8 release cycle it felt too late to affect the underlying code and flow. It might even have been after feature freeze, meaning our only choice was to drop the plugin entirely. Of course, we knew that would be bad treatment of Fluendo, but to be honest, since the Board’s job is watching over Fedora, we have to care about upstream but not over the interests of Fedora. We chose a middle-ground to see how it would progress, which happened to leave Fluendo’s shopping path intact.

So Bill Nottingham offered to get the up-front education fixed so that was the first thing a user saw before being offered a shopping experience. We left the situation as-is from there, knowing it was sub-optimal, but being new software, we didn’t know how it would all turn out. Sometimes you have to try things that even seem like poor ideas. It sure worked in this case, where everyone has been nicely vocal about how they feel about the solution.

In the meantime, over the Fedora 8 life, the Board came under fire for apparent double-standards, that is, allowing codeina to fetch non-free bits but resisting autodownloader doing the same thing for open source game engines. We began to discuss what was the right thing to do, and nothing seemed like a perfect situation.

So here we are again … too late in the release cycle to get new coding done on codeina but with the same situation. Same mistake made in not engaging with Fluendo earlier to get the situation resolved properly. What could we have done?

  • Encouraged Fluendo to come up with a more modular approach, so we could remove direct links to fetching non-free software and make it possible for someone to, for example, grab another plugin that would enable Fluendo’s webshop.
  • Given them more time than “nearly zero” to come up with any other solution, or the same solution but executed better.
  • Done all this with enough time to have a longer discussion cycle.

I’m unclear if it is too late to do much else other than what we decided to do with patching out the links to the non-free software. Users can still go to the web shop, and that could be linked from codeina better.

Even though it is rather late to try fixing this situation, that doesn’t mean a good enough solution can’t be worked up. There are updates to packages, maybe even a zero-day fix, if we can’t get better changes to ship with Fedora 9. Rather than asking the Board to “reverse its decision”, please join us on fedora-advisory-board to figure out what is the right thing to do.

Can you help make the world’s best Linux release notes?

14-Mar-08

Almost time to freeze and fork the wiki into the Fedora 9 (Sulphur) release notes. This release we did not rely as much upon assigned writers to cover the different content areas (the beats) for two reasons. The developers and packagers have gotten much better at finding and editing their relevant content. Also, the feature process is doing a lot of the work of gathering release notes about important Fedora initiatives.

On 16 March we take a snapshot of the wiki, convert it to XML, and roll a POT file for the translators. This is included with the Preview Release (PR) of Fedora 9 as a preview of the release notes. Any fixes and additions from that work goes into the wiki by you all, then we manually carry changes into the XML for the F9 gold release notes.

Running fsck on a LUKS encrypted partition in LVM

04-Mar-08

Coming back from a reboot yesterday afternoon, I ran into some bad attribute blocks that fsck couldn’t handle in the boot space and shelled me out to take care of it. Since I was not in the office or staying there for much longer, I powered down to take care of when I got home.

Doing this fsck was a bit needlessly complicated, especially as it was not at all like what I’ve done before nor what the boot shell recommended, which was to run fsck without -a or -p. I couldn’t find enough pieces to figure it out from Google. I eventually got pretty far but was stuck in something weird that Red Hat’s helpdesk helped me figure out. Note that world — Red Hat has a helpdesk that actually helps people.

Skipping all the false pathways I took, here are the steps that worked:

  1. You need a better environment than the Fedora 8 rescue CD. The rescue CD does not have the kernel modules to handle the LUKS decryption. I used an F8 live CD.  (This sounds like it’s fixed in the rescue mode currently in rawhide.)
  2. Decrypt the partition at the command line, for example: cryptsetup openLuks /dev/mapper/ VolGroup00-LogVol02 home
    • Note that you have given the name of ‘home’ to the decrypted partition; a name is required by cryptsetup
    • The unlocked volume is now /dev/mapper/home
  3. Run fsck on the unlocked volume: fsck.ext3 /dev/mapper/home

Ah, three simple steps … that took more than 3 hours to figure out. But all is good now. 🙂

The return of the open Board meeting

04-Mar-08

As part of trying to make it clearer wtf the Fedora Project Board does (buzzwords: open, visible, accountable), we decided to start holding open meetings once a month (approximately one out of every four meetings.) The current goal is to use the Project’s Asterix server, so the Board can talk in real time and have the audio streamed as a simulcast for everyone to listen to. Then contributors with questions or comments can either queue up for a limited pool of voice lines, or ask on IRC with the question read out loud.

The first of these meetings is going to be IRC-only, so we can get started on the goal before the technology is ready for us. Details are in this f-announce-l post from Paul.  It’s today, in just a few hours.

Kind of like the venerated town hall concept.  Let’s find out if it is cool or not, eh?