Email or username:

Password:

Forgot your password?
Top-level
small circle 🕊 in calmness

@cwebber

Thus I had the idea to write a proposal to start, what I call, a fellowship that runs an open social web laboratory, and is able to separate the general discussion to focused input for working groups to quickly iterate on a theme, in a similar way to how BS operates now.

See for info: discuss.coding.social/t/propos

The idea is follow-up to "Vision for fedi spec" feedback gathering that @helge initiated, as a means to cope with the broad subject area.

See: discuss.coding.social/t/wiki-v

/end

3 comments
small circle 🕊 in calmness replied to small circle 🕊 in calmness

@cwebber @helge

Tangential, but to add some more spice to this..

We need more fellowships like this, who explore yet other areas together.

Like for object capability social web at scale.

A couple of years ago, when you were still on Spritely Project, you sent out a toot out in which you sighed that once spritely technology would be mature enough for widespread use, it would probably be already too late.

The institute to the rescue, I guess. Valid and prudent choice.

1/..

Two four-quadrant diagrams with the quadrants being Technical, Socio-technical, Socio-cultural and Cultural.

First diagram places the area of "Protocol support" mostly in technical quadrant and extending into socio-technical. Another area "Solution design" is mostly socio-technical in nature extending to (ideally) socio-cultural, and a bit of technical and cultural.

Second diagram has the same quadrant, but shows areas of DX (Developer experience) to be mostly technical and a bit socio-technical,  and UX area to be mostly socio-technical quadrant. A much larger area covering DX and UX and extending to all 4 quadrants is the area SX which stands for Social experience design.
small circle 🕊 in calmness replied to small circle 🕊 in calmness

@cwebber @helge

It is still hard to hook on to spritely unless you have deep technical expertise. That means most others (large group) are in wait-and-see necessarily.

Choice is perfectly valid, because its the foundation team's own initiative.

Is it the best tech introduction strategy? Best technology adoption model to use?

Your community and ecosystem have to catch up, once you say "it's time for fun".

Randy's community pattern language might serve to unlock upper-stack stakeholders now.

small circle 🕊 in calmness replied to small circle 🕊 in calmness

@cwebber @helge

Because that is highly tangential from spritely core technology, fanning out into vast scope, you might offload that to a fellowship that can facilitate multiple independent initiatives at the same time, not just spritely but also see an ecosystem of convergance and increasing alignment, rather than fragmentation as per the norm.

Go Up