VVV turns 7

In today’s edition of my how the time flies, Varying Vagrant Vagrants, an open source Vagrant configuration focused on WordPress development, turns 7.

It’s amusing to me that I chose to celebrate the first anniversary, casually mention the second, and let the remainder of the decade go by in a flash. Where did that in-between go?!

I am grateful that the project continues, despite my general absence. My role as “project lead” over the last couple years has really been to just be there if needed, renew the domains, and pay $1.84 every month for the S3 bill.

Having Lorelei and Tom as lead developers to do the heavy lifting along with Daniele as a committer along with the many, many individual contributors across all of the repositories is so very great and has eliminated all of the mental frustration I had during those middle years with the project.

I really do have the best role. 🙂

I continue to be astounded when I hear of how people have used VVV over the years. That a project like this took off and became useful for so many people is a strange indication of how horrible working with development environments can be. Even though this one isn’t perfect, it keeps getting better.

So happy 7th anniversary to VVV. Many, many thanks to Lorelei, Tom, and Daniele. And check back here again in 5 years. 🎉

An open source WordPress multisite talk

I was watching a talk at WordCamp Boise earlier today and thought to myself that it would be a great set of slides to open source so that others could give the same or a similar talk to their local meetup group or another WordCamp.

I then wondered why more people don’t open source their talk material. 🤔

I then realized I had never open sourced my talk material. 🙃

In well timed fashion, I spent some time this week recreating the slides for the multisite talk I’m about to give because I misplaced the Keynote files and only had a PDF. I’ve given several iterations of the talk over the years and it seems like a nice candidate to open source so that others can use it as a launch pad for sharing that knowledge or creating talks of their own.

I’m considering the latest version, built in Keynote, the most prepared, though I’ll link to previous iterations of the slides so that anyone can see how they’ve progressed. I built the first set of slides in reveal.js, but kept coming back to Keynote as it always ends up being the least time consuming way for me to develop slides. I’m happy to integrate any changes that others suggest, especially as multisite and the set of solutions built around it continues to ebb, flow, and grow.

The talk content is published under the Creative Commons Attribution-ShareAlike 4.0 International License. The image of Thelonious Monk used on this page and in the slides was dedicated to the public domain by its photographer, William P. Gottlieb.

Download the slides for “Behind the Scenes of WordPress Multisite”

I’ll probably adjust this post or replace it with a page once I figure out a better way to structure this.

Talk history:

These are the videos and slides for iterations of the talk that I’ve done in the past. The videos available on WordPress.tv are also published under the same CC BY-SA-4.0 license as the talk material. I’m not sure if the LoopConf video on YouTube has a specific license, so maybe refrain from any remixes? 🙂

Note: There should soon be an accompanying video from WordCamp Boise that I’ll add to this post once it’s available on WordPress.tv.

Documenting VVV’s governance model

Earlier tonight I submitted a first draft of VVV’s governance model for comment by the community. This is one of those times as an open source software maintainer where you realize you’re doing something that should have been done a long time ago.

See also the time we added a license 1.5 years in 😅

As I started researching how one goes about documenting a governance model, I ran into “Planning for Sustainability“, from OSS Watch. At the bottom of that document are a few time estimates to help you project the level of effort in doing this all. They’ve marked 30 hours to “understand the different governance models” and create the document (from a template).

I kind of laughed at first, especially because VVV is not that big of a project. But here I am after 2 days of on and off research and documentation, probably somewhere about 6 hours in, thinking that they aren’t so far off.

It’s easier for VVV because it is (IMO) a fairly clear benevolent dictator model. I’ve led the project for 5 years and have relied on active members of the community for input throughout. I can imagine this being near impossible for larger projects where the project structure is less clear.

Of course, the benefit of spending so much time researching is parsing the great information that’s available thanks to years of others’ successful and failed attempts.

Here’s a walkthrough of some material I’ve found useful, along with commentary.

First, I’m happy to have run into the “Open-source governance” Wikipedia article early in the process. This does not directly describe governance for open source software, but instead the political philosophy of a community editable legislation. This helped set the tone in my head that my intent should be to document a clear explanation of how the project is managed rather than just a brief overview of my assumptions.

Next, all of the OSS Watch documentation was very useful. I spent some quality time with “Governance Models“, “Roles in Open Source Projects“, “Meritocratic Governance Model“, and “Benevolent Dictator Governance Model“. I almost used one of the provided templates, because it’s nicely open sourced as CC BY-SA 4.0, but decided to go completely custom.

I explored the models used by other other open source projects. In the process, I studied those from NodeJS, WP-CLI,  and Ubuntu among other random finds I stumbled on through GitHub’s search. This process taught me that not nearly enough open source projects provide a statement on governance. WP-CLI in particular inspired the inclusion of the project administration section so that clear documentation existed on server and domain management.

I also spent some time with some hard copies. The “Project Structures and Ownership” page from Homesteading the Noosphere was useful in wrapping my head around the word “benevolent dictator”, a term that I still don’t really like. And Producing Open Source Software is always so valuable. I went back again and again to “Benevolent Dictators“, “Social and Political Infrastructure“, “Choosing Committers“, and “Writing It All Down“.

My favorite phrase of the process comes from that last section:

living reflection of the group’s intentions, not a source of frustration and blockage

This sums the process up. A documented governance model is a document of intent, one that can be changed as the project matures, and it’s meant to provide a clear way for work to happen rather than a roadblock.

I’m looking forward to seeing what the community thinks!