@edsu@adamgreenfield none of this is to say that Adam’s concept is bad; I genuinely want to explore what an invitational culture would look like in many open contexts. I suspect that if you built it in from day one, some pretty interesting things would result. (I should revisit @cfiesler on AO3 through this lens…)
@adamgreenfield@edsu 👀 wow, that’s a great label for so much of what I’ve been able to benefit from in open over the years.
And what’s increasingly hard to do in many open contexts, because of … well, a whole shit-ton of factors that mostly are well-intended but often have the side-effects of reducing trust and increasing pressures towards efficiency and output.
@adamgreenfield@edsu yeah. At least some open communities have had success along these lines by welcoming people into “intro” tasks like evangelism, or in the Wikipedia case, simply fixing typos. (My origin story is in part about a very invitational part of Mozilla based around bug *triage*, which could be done with just some common sense v. actual engineering chops.)
@edsu perhaps @adamgreenfield can push back, but as I read it his invitationality implies a few things: (1) tasks that can be done immediately (or nearly immediately) by "the person off the street"; this is rare in open engineering projects (though some projects try to change that, with varying degrees of success) 🧵
@edsu@adamgreenfield (2) a certain excess amount of labor which allows for both "people doing work" and "people performing invitationality".
I suspect if invitationality is built into the culture from an early point, this boundary can be made more porous, but again it's easier IRL when you can trivially *invite* someone to "observe over my shoulder" in a way that's trickier online (but again that could be designed for in tools)
@edsu@adamgreenfield (3) work that is highly parallel; i.e., if new person off the street does does something slowly or badly, it doesn’t slow/stop work for others.
Wikipedia does this very well, which is part of its success despite otherwise not being very invitational.
Traditional software development used to be *actively terrible* at this, which was a competitive advantage for open software for a long time. But for many mid-size software projects it is hard.
@edsu@adamgreenfield (4) it works best when the newcomer is likely to be engaged, motivated, and trustable: eg, in the post-Sandy situation (as in most post-disaster situations, despite looter myths) new helper almost certainly was not a thief, so high-trust/low-barrier works great.
That’s true of the median open source contributor, but as we’ve learned the hard way the long tail of trolls/black-hats is very long and highly-motivated :( Unclear how to balance that reality with invitationality.
Missed this Sunday. I think some sorts of engineering projects are very hard to make welcoming in this way, but I should probably still sit with the challenge rather than rejecting it out of hand.
@ntnsndr@rwg@inquiline a fediverse server that did deliberate loss[1] of old messages would be such a fascinating thing. I think a lot of people *say* they prefer disappearing content, but often the revealed preference is for permanence. (I wonder if @signalapp folks has ever considered deletion-by-default.)
[1] could be just taking private older messages, or perhaps complete deletion; perhaps for all messages, or just those that fall below a certain popularity threshhold; etc.
@cwebber 1999-me is surprised about a great many things; “khtml rules the world” is definitely near the top of that list.
“khtml will run on the device in your pocket” “well, yes, that makes sense, because it’s a toy renderer, and I’m a huge geek, so I probably have some extremely niche extremely resource-constrained device running open source, but I’m sure the rendering is terrible and slow” “yeah, so, about that”
@ntnsndr (1) great idea, wonder if RH's story would have been different had this been done when they did this lo so many years ago (2) do we know what percentage of the overall stock pool has been allocated this way?
@jessamyn I do wonder if there’s a spot for something like the Wikidata games for matching these CC0 images with Wikidata records (and eventually articles)? cc @magnusmanske
A great question by @deborahh ("how to search open images?") with a great answer: https://openverse.org, Wordpress's open-image search site.
Update: Apparently the Getty is not yet accessible via Openverse, but they have an API, so it should be doable if someone wants a new hacking project! https://github.com/WordPress/openverse/issues/3893
Some days I wonder if, quietly, CC0 is actually a bigger success story than the other @creativecommons licenses put together. Not to slight the other licenses! But CC0 is increasingly catalytic in the library, museum, and data spaces.
Programmer turned lawyer and community guy. Current: Tidelift, Creative Commons, OpenET, California HDF, 415/94110, dad.Previously: Wikimedia, Mozilla, Open Source Initiative, GNOME, LegOS, Duke, 305/MIA, more.