Other writing: October 2023

Posted on by
Reply

What have I been writing when I haven’t been writing here?

Stuff I wrote

Fedora

Duck Alignment Academy

Technically We Write

Other writing: September 2023

Posted on by
Reply

What have I been writing when I haven’t been writing here?

Stuff I wrote

Duck Alignment Academy

  • One approach to AI contributions — All communities will need an AI contribution policy at some point, and the Apache Software Foundation’s example is a good one to follow.
  • What are you optimizing? — If you start optimizing for a process and then discover you’re optimizing for the wrong thing, you’ve wasted time.
  • For companies, community should be “us” not “them” — Referring to the community as “them” as if there’s no overlap encourages treating company & community interests as separate, harming long-term sustainability.
  • New logo! — Almost two years after I meant to get around to it, Duck Alignment Academy has a logo.
  • Preparing for Hacktoberfest contributors — If your project is participating In Hacktoberfest, you’ll want to make sure you’re ready for an influx of new contributors.

Fedora

On “non-code contributors”

Posted on by
Reply

I was dismayed when I read Justin Dorfman’s “Why I’m proud to be a non-code open source contributor and you should be too” this morning. It’s mostly a great article. Dorfman makes valid points about the value of contributing to open source projects beyond code. Open source needs — and should encourage — these kinds of contributions.

Which brings me to my issue with the article. Dorfman anonymously quotes a well-respected open source leader:

If you find yourself about to use the phrase “non-code contributors” you should stop and use entirely different language.

He calls that a “horrible idea” and suggests that it discourages the kinds of contributions we need. But this take is disengenuous at best. I happen to know the post he’s referring to and it continues:

Defining people by what they are not is not a valid pathway to inclusion. Want to attract designers? Say so. Want to attract technical writers or community managers? Say so.

Far from suggesting that people should be quiet about non-code contributions, the post is calling on project leaders to stop othering those contributors and explicitly value them. The author is saying that lumping everything that’s not code as “not code” diminishes it. It’s just a shame that the article misrepresents a post when it could just agree with what was actually written instead.

Hurricane Lee forecast game

Posted on by
Reply

Update: we have a winner!

It took longer than I’d have liked to publish the results of this contest. I was traveling out of the country. But I’d like to congratulate KP on winning the Lee forecast contest.

One thing that I realized after the fact: my changes below made it so only whole numbers could be used for latitude and longitude. I’ve fixed that for next time!

Original post

The prodigal game returns! A technical glitch ruined the Dorian contest in 2019, so we haven’t seen a Funnel Fiasco tropical forecast game since Hurricane Matthew in 2016. But I’m pleased to announce that we’re up and running for Hurricane Lee. You can submit your landfall forecast by 2100 UTC on Wednesday 13 September.

In keeping with tradition, we’re still using the same crappy Perl script I wrote in 2005. Despite the fact that I’ve been putting off a total rewrite for over a decade, I did make a few improvements recently:

  • Numerical fields now require numeric input. If you were hoping to submit “butts” as your wind speed, I’m sorry to disappoint you.
  • Coordinates are constrained to reasonable ranges. I refuse to give in to Kevin’s whining about west being negative numbers. (I believe my exact words to him were “take it up with the Prime Meridian.”) But I was feeling magnanimous so I’ve constrained the latitude to 0–90 degrees north and the longitude to 180 degrees west to 10 degrees east.
  • Similarly, wind speed is now constrained to realistic values. You can’t submit a wind speed less than zero or above 200 miles per hour.
  • Furtherly similar, the time segments can’t be negative or overflow.

So go ahead and submit your forecast by 2100 UTC on Wednesday so you can join in the grand tradition.

Other writing: August 2023

Posted on by
Reply

What have I been writing when I haven’t been writing here?

Stuff I wrote

Duck Alignment Academy

Docker

  • Protecting secrets with Docker — Keeping your secrets secret is an ongoing process, but it’s worth the effort. Learn about Docker features you can use to help prevent leaking secrets.

Other writing: July 2023

Posted on by
Reply

What have I been writing when I haven’t been writing here?

Stuff I wrote

Duck Alignment academy

Fedora

Does open source matter?

Posted on by
3

Matt Asay’s article “The Open Source Licensing War is Over” has been making the rounds this week, as text and subtext. While his position is certainly spicy, I don’t think it’s entirely wrong. “It’s not that open source doesn’t matter, but rather it has never mattered in the way some hoped or believed,” Asay writes. I think that’s true, and it’s our fault.

To the average person, and even to many developers, the freeness or openness of the software doesn’t matter. They want to be able to solve their problem in the easiest (and cheapest) way. Often that’s open source software. Sometimes it isn’t. But they’re not sitting there thinking about the societal impact of their software choices. They’re trying to get a job done.

Free and open source software (FOSS) advocates often tout the ethical benefits of FOSS. We talk about the “four essential freedoms“. And while those should matter to people, they often don’t. I’ve said before — and I still believe it — FOSS is not the end goal. Any time we end with “and thus: FOSS!”, we’re doing it wrong.

FOSS advocacy — and I suspect this is true of other advocacy efforts as well — tends to try to meet people where we want them to be. The problem, of course, is that people are not where we want them to be. They’re where they are. We have to meet them there, with language that resonates with them, addressing the problems they currently face instead of hypothetical future problems. This is all easier said than done, of course.

Open source licenses don’t matter — they’ve never mattered — except as an implementation detail for the goal we’re trying to achieve.

Barbenheimer

Posted on by
Reply

Over the weekend, I took part in the Barbenheimer Experience. We saw “Barbie” and — after a break to feed my sister’s dogs and also myself — “Oppenheimer”. I’ll be honest: I mostly did it because it felt like a silly Internet thing to do. But I’m glad I did it.

Barbie

Not since “Citizen Kane” has a movie about a beloved childhood possession made such good Art™. I wasn’t prepared for how much I enjoyed it. It was fun in a silly, self-aware way. Credit to the folks at Mattel who approved this, because it addresses some of Barbie’s problems.

It’s not just a fun movie, though. The movie addresses serious themes, sometimes satirically and sometimes earnestly. The message gets a little ham-handed in a few spots, but it quickly reels back in. Overall, it provokes thought in a fun way.

One thought it provoked in me: how many times did they have to shoot the beach off scene before they got a usable take?

Oppenheimer

“Oppenheimer” is not a fun movie, but it was interesting. I didn’t know much about Robert Oppenheimer before the movie, and I’m not sure how much I can claim to know now. While not fawning, the movie’s portrayal of Oppenheimer is complimentary. It doesn’t ignore his personal failings, but it also doesn’t explore them. They are just facts in the story.

I spent the rest of the evening thinking about atomic weapons. Truman’s decision to drop atomic bombs on Japan may be the ultimate Trolley Problem. An American invasion of mainland Japan would have cost many military and civilian lives. But that didn’t happen. The death of a few hundred thousand civilians did happen. No matter what the outcome of the road not traveled, we can’t ignore what did happen.

Was Oppenheimer’s opposition to Teller’s hydrogen bomb principled or was it petty? I either case, was it hypocritical? Was it ethical? What lessons should we take for the things we invent today?

Barbenheimer

Both movies are about the end of the world as the characters know it. Both grapple with what that means for the future. They are very different movies, but they compliment each other quite nicely. They’re good on their own, but I’m glad I saw them together.

Booth Tarkington on “The Golden Bachelor”

Posted on by
2

This weekend, it came to my attention that ABC is making a change in its long-running dating show The Bachelor. A 71 year old man will be the first “golden bachelor” in the upcoming 28th season. I don’t have much of an opinion on the show generally or the new season particularly, but I couldn’t help but think of Booth Tarkington’s Pulitzer Prize-winning The Magnificent Ambersons.

Youth cannot imagine romance apart from youth. That is why the roles of the heroes and heroines of plays are given by the managers to the most youthful actors they can find among the competent. Both middle-aged people and young people enjoy a play about young lovers; but only middle-aged people will tolerate a play about middle-aged lovers; young people will not come to see such a play, because, for them, middle-aged lovers are a joke—not a very funny one. Therefore, to bring both the middle-aged people and the young people into his house, the manager makes his romance as young as he can. Youth will indeed be served, and its profound instinct is to be not only scornfully amused but vaguely angered by middle-age romance.

Booth Tarkington, The Magnificent Ambersons

In an interesting coincidence, both Tarkington and the “Golden Bachelor” are from Indiana. At any rate, I suppose ratings will tell if Tarkington was right or not.

Ended, the clone wars have?

Posted on by
4

I have done my damnedest to avoid posting publicly about Red Hat’s decision to stop publishing RHEL srpms. For one, the Discourse around it has been largely stupid. I didn’t want any part of the mess. For another, I didn’t have anything particularly novel to add. I’m breaking my silence now because the dust seems to have settled in a very beneficial way that I haven’t seen widely discussed. (To be fair, since I’ve been trying to avoid the discussion, I probably just missed it.)

Full disclosure: as you may know, my role at Red Hat was eliminated earlier this year. This does not make me particularly inclined to give Red Hat as a company the benefit of the doubt, but I try to be fair. Also: during my time at Red Hat, I was the program manager for the creation of CentOS Stream. However, I did not make business decisions about it, nor did I have any say on the termination of CentOS Linux or the recent sprm change.

My take on the situation

I won’t get into the entire history or Red Hat Enterprise Linux, clones, or competitors here. Joe Brockmeier’s ongoing “Clone Wars” series covers the long-term history in detail. I do think it’s worth providing my take on the last few years, though, so you understand my take on the future.

First of all, I don’t think Red Hat (or IBM, if you’d rather) acted with evil intent. That doesn’t mean I think the decision was correct, but I do think it was a legitimate business choice. I disagree with the decision, but as much as they didn’t ask me before, they sure as hell don’t ask me now.

If RHEL development started out with a CentOS Stream model, I’m not sure CentOS Linux (and the other RHEL clones) would have existed in the first place. But we don’t live in that timeline, so RHEL clones exist.

There are plenty of valid reasons for wanting RHEL but not wanting to pay for the subscription. It’s not just that people are being cheap. Until 2018, users of Spot instances on Amazon Web Services couldn’t use RHEL. In a former role, we had RHEL customers who used CentOS Linux in AWS precisely because they wanted to use Spot instances. Others used CentOS Linux in AWS because they didn’t want to deal with subscription management for environments that might come and go. (I understand that subscription-manager is much easier to work with now.)

So while Red Hat may be right to say that RHEL clones don’t add value to Red Hat (and I disagree there, too), RHEL clones clearly add value for their users, which include Red Hat customers. It’s fair to say that, for some people, the perceived value of a RHEL subscription does not match what Red Hat charges for it. How to solve that mismatch is not a problem i’m concerned with.

So what now?

Two community-driven clones popped up in the immediate aftermath of the death of CentOS Linux: Rocky Linux and AlmaLinux. Both of these aimed to fill the role formerly held by CentOS Linux: a bug-for-bug clone of Red Hat Enterprise Linux. I never quite understood what differentiated them in practice.

But now duplicated effort becomes differentiated effort. Rocky Linux will continue to provide a bug-for-bug clone. AlmaLinux, meanwhile, will shift to making an ABI-compatible distribution — one where “software that runs on RHEL will run the same on AlmaLinux.” This differentiated effort allows those communities to serve different use cases. They now have their own niche to succeed or fail in.

Time will tell, but I think Alma’s approach is a better fit for most clone users. I suspect that most people don’t need bug-for-bug compatibility (except in the XKCD #1172 scenario). For many use cases, CentOS Stream is suitable. Of course, people make decisions based on what they think they need, not what they actually need. Third-party software vendors may end up being the deciding factor.

Given the different approaches Rocky and Alma are taking, I think Red Hat’s decision ended up being beneficial to the broader ecosystem. I don’t think it was done with that intent, and I am not arguing that the ends justify the means, but the practical result seems positive on the whole.