---

---

Sponsors

Thanks to all my sponsors across any of the donation platforms! Special thanks to my biggest sponsor HealthSherpa!

Looking for a Rails Developer?

The Rails Foudnation has just launched the Official Job Board for Ruby On Rails!

Here are the latest jobs posted there as of < 60 minutes ago:

• Senior Integration Engineer (Rails) @ Social Venture Startup at Mon Ami, Inc.
• Engineering Manager, Platform at Fleetio
• Senior Ruby developer at CloudDevs
• /^(Full-?stack|Backend) Engineer$/i at Better Stack at Better Stack
• Senior Application Security Engineer at Huntress

Signup now!

---

I Am Using GitHub Under Protest

Github decided to sponsor me, because they rely on my tools.

In spite of that, I'm (partially) leaving. Why? I certainly do not have the spare-time to move hundreds of projects to a new home... but I'm getting started. I'll enumerate some of the reasons below, but first, where am I, and some of the organizations I control, going?

• pboling @ 🧪 GitLab
• rubocop-lts @ 🧪 GitLab
• oauth-xx @ 🧪 GitLab (chosen amongst all options, including staying at GitHub, by a majority of the dozens of respondents)
• pboling @ 🧊 CodeBerg
• galtzo @ 🛖 SourceHut

Reasons to Leave GitHub

1. A recent proposal to extend Github-flavored Markdown (ref)
   • Literally breaks regular markdown syntax of links in headings.
   • English-only
   • Incompatible with Semantic HTML (POSH) (by abusing the blockquote tag; this also raises issues of accessibility)
     • Note: Latest version has switched to a <div> treamtment, which is just as bad because now Markdown's ">" with admonitions is no longer a blockquote, thus breaking Markdown. The number of bugs caused by this uncountable. A new bug is reported nearly daily on the thread.
   • Incompatible with existing Markdown standards proposals
   • Ignores the community-centered approach to extending Markdown, which, ironically, Github started
   • Contributes to vendor lock-in.
   • Will force countless volunteer FOSS developers to waste time adding compatibility to their projects that use Markdown and attempt to support GFM.
2. More than 2 years of ignoring requests to add an important feature (allow-failure) to Github Actions (ref, ref). When not ignoring, Github is completely misunderstanding the feature. How are those building Github Actions so deeply unfamiliar with core features of competing CI platforms?
3. Latest iteration of Achievements was bad.
4. Github Copilot. Much has been written about this, and I won't repeat it all here. Making money by abusing the licenses of open source code, without recognition, compensation, or respect to the developers, the craft, or the ideals of open source is nauseating.

---

What about community?

I am interested in people's thoughts on where to go next. Community involvement matters for open source projects, and I have dozens of them that could be affected, the biggest being oauth and oauth2 Ruby gems.

Regarding fragmentation, hopefully it will be resolved by federation, which is to source forges (like Github) what git was to version control (i.e. makes it distributed, at least in theory).

It looks like Gitea, Codeberg and Hostea will join the fediverse soon, within a year, and there are projects that will integrate Github with the fediverse as well (i.e. federate Github commits, PRs, issues, etc).

I'm interested in your thoughts, leave a comment on the blog post!

Recent Releases

• sanitize_email (2.0.8)
• rspec-block_is_expected (1.0.6)
• sanitize_email (2.0.7)
• debug_logging (4.0.2)
• sanitize_email (2.0.6)
• sanitize_email (2.0.5)
• standard-rubocop-lts (1.0.10)
• sanitize_email (2.0.4)
• version_gem (1.1.4)
• silent_stream (1.0.8)

Recent Blog posts

• Generate Gem Checksums
• RequireBench: When do you use it?
• Put the D in DVCS
• How to Repair an Old Gem (Part 5) - Rakefile & RuboCop LTS
• How to Repair an Old Gem (Part 4) - Upgrade Autotest
• How to Repair an Old Gem (Part 3) - Upgrade RSpec
• I'd like to post here again
• List of (Currently) Maintained RubyGems
• Life After Github?
• I'm Leaving Github

Contributions

🧒 How it started

A cheeky me holding a baby black caiman, Amazon River, Brazil, June 24, 1997, shortly after completing my first programming course - Pascal. The black caiman, a baby specimen of the family Alligatoridae and order Crocodilia, was unharmed, and released back to the water, where it promptly continued following its mother. Full grown they are among the largest alligators and crocodiles in the world.

How it's going

• 🦷 I'm putting more of my focus on FLOSS efforts (of myself and others)! and from
• 👷 I build big things and small things out of tiny bits.
• ✨ Recently created rubocop-lts for library maintainer happiness 👩‍❤️‍👩.
• 🔭 I’m working on finishing the migration away from TravisCI to modern CI tools.
• 🌱 I’m learning Svelte & SvelteKit, with Lucia, Drizzle, Zod, Inlang Paraglide, Skeleton, Tailwind, Typescript, and so many more cool tools.
• 👯 Preparing next release of seed_migrations and oauth gems!
• 🤔 I’ve moved my suite of Resque plugins to the Resque org!
• 📫 How to reach me
• 😄 Pronouns: He/Him
• 🗨️ I speak 3 languages fluently, and for a 4th I'm learning Bahasa Indonesia!
• 👷‍♂️ I help refugees and ex-refugees in Ghana🇬🇭 and Liberia🇱🇷, respectively, through Hope For Tomorrow, a Liberian NGO. DM me if interested in knowing more.

🛠️ My Dev Tools:

💼 Career

• The list is long, even in summary, see my LinkedIn.

🧻 Current Roles

• CTO | Fisecal
• Principal Cloud Engineer | Vital Connect
• Full Stack Instructor | Michigan State University Bootcamp
• FOSS Blogger | RailsBling
• FOSS Author | RubyGems
• FLOSS Maintainer | Tidelift Enterprise OSS
• Researcher | WordTree Foundation
• Member-worker | Bed of Roses Club
• Advisor | Hope For Tomorrow (Liberian NGO)