@reiver

Yes, I know. And endless strife.

SX separates #FOSS from the movement of people that creates it. FOSS is code/software + an open license. Period.

Under SX, where solution development involves software creation, FOSS is the end of the supply line. FOSS software is a SX artifact. Its only purpose is to serve the formulated solution that was the reason to start programming. And that solution in turn is only meaningful to the extent it fulfills people's needs.

Including the creator, if they need sustenance to continue their good work. This is the crux. It isn't there for FOSS creators, its an inherently unsustainable field.

Separating FOSS software from those creating it allows focus on healthy processes, that do not burnout their participants and they leave.

Here SX defines #SOSS, Sustainable open social systems..

https://coding.social/blog/reimagine-social/#sustainable-open-social-systems

#SX #SocialCoding #SocialWeb

@nicol @nlnet

It is the right ask though. The ask is: What are ALL the moving gears that make sustainable #FOSS (i.e. #SOSS) be produced, and in an entire healthy technology ecosystem at that.

My investigation around commons based social dynamics started when I had basically given up "trying to herd cats" at #SocialHub where it was already clear that most people didn't much beyond the interest for their own #ActivityPub project, to mingle in the discussions. I mentioned at the time in various thread "Do you want 'community-of-action' or just a mere discussion forum. But even for those questions there's hardly anyone interested.

I knew all this already from my time facilitating Humane Tech Community - now dormant, waiting for value at https://community.humanetech.com - but needed to more deeply understand.

The notion of #FSDL in its double meaning of #FreeSoftware development lifecycle, and #Fediverse solution delivery lifecycle rose from there, but also the need for a new adoption model.

@abeorch @gary

Totally. I am myself as technical person stuck in Yunohost because of all kinds of upgrade issues. The "bring together" on a holistic basis is exactly what I do applied research on with Social experience design i.e. #SX.

In the case of #FOSS that means transitioning (or rather evolving) towards #SOSS. And considering the entire #FSDL, which either stands for #FreeSoftware development lifecycle. Or for #Fediverse solution delivery lifecycle.

Under SX software development involves service development, delivery, and exchange. Within commons based ecosystems and across them, to the broader public.

In SOSS + FSDL it is natural that you try to attract a #UX designer if you need one and not just sighed "If only a UX designer became a contributor", which I've often seen people do.

https://coding.social/blog/reimagine-social/#sustainable-open-social-systems

#ThoughtProvoker 🤔

For those who chimed in to join the #brainstorming and want to be nerdsniped potentially you may ponder that..

♟️ #Chess is a great example of an #EmergentSystem.

🌱 Recipe for #Emergence of chess #game

- [chess ingredients here]

And then to continue onwards and think how the relationship is between #FOSS individuals who give their all-in best-efforts for world improvement, make real sacrifices, and who gift their 2 cts with best-intentions, still are faced with uncomfortable questions.

To turn that into solution-orientation we must find a good recipe, and note down #recipe ingredients..

🌱 Recipe for Sustainable open social systems i.e. #SOSS

- [sustainable FOSS ingredients here]

Hint / rule: Max. ingredients is 10.

https://social.coop/@smallcircles/116316524763055082

@helge Recipe support on the #ActivityPub fediverse?