Skip to main content

Worker-owner at Agaric web development collective, co-author of the Definitive Guide to Drupal 7, and person who gives a damn about justice, liberty, and gaining the most power possible for all people over our own lives.

benjamin melançon

One more way @GitLab could be better than GitHub: Give creators more tools to manage their communities, and generally work to encourage a culture of appreciation of open source free software.

Per @johnonolan and @ErisDS of on a recent podcast, discussion starts at the 40 minute mark on this podcast, and goes just over three-and-a-half minutes:

This is definitely of relevance for - we want to be fully open, we definitely don't want to be driven into a private issue to discuss a feature that will be in the open code, but we cannot have our energy drained by help vampires or anything like that.

It's not currently possible to let everyone see the code and issues, but only people who are in the group/project edit issues. If that were made possible, a relatively minor tweak to GitLab's permissions, then we could lock participating in issues to people who have joined the Drutopia Software Cooperative, with the $5 entrance fee (and agreement to the code of conduct, ) will surely be plenty of a filter to ensure quality and respect in contributions.

benjamin melançon

I have been advised, very wisely, that as a hosted platform should be as focused and locked-down as possible— the more variations allowed, the more often things will be broken with upgrades. But what if, instead, we had such a rock-solid culture and practice of continuous integration and testing that we let people put almost anything into production that passes tests? What if we told people that they could break the seal and do anything, configuration-wise at least, and the warranty wouldn't be broken as long as they write tests for their use case?

benjamin melançon

Modern Monopolies: What it Takes to Dominate the 21st-Century Economy

1 min read

by Alex Moazed & Nicholas L. Johnson

Picked up at the Spry Group HQ. Only read a few pages. It would be well worth reading with in general and specifically in mind.

The more commoditiized a service or profit offering — more commoditized means it "has only a limited number of relevant characteristics that consumers care about" — the less complexity purchasers should have to deal with.

"The hard part is determining how commoditized or noncommoditized a platform really is"

benjamin melançon

Global and local Drupal community


Could see features Enzo is calling for on - multilingual, local group control over portions of sites (or sub-sites?), integration with different events platforms in particular - as being good Drutopia features.