Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • About Bonfire
just small circles 馃晩
just small circles 馃晩
@smallcircles@social.coop  路  activity timestamp 17 hours ago

@nicol @nlnet

This will be named SX FractalHEARTS, an #innovation strategy and technology adoption model (TAM) fit for chaotic grassroots ecosystems (and turn them more chaordic over time).

馃挒 HEARTS here, like the FSDL, has a double meaning to the acronym too, depending on the Pyramid of Perspective layer that is focused on.

It stands either for Hedonics-based Early Adoption of Research and Technologies at the individual initiative scale of the pyramid (bottom layer)

And then for Hedonic Ecosystems for Adoption of Responsible Technologies at the higher layers, where we want to deal with the externalities that the introduction of the tech has when it lands in society, as best we can.

Best-known is the TAM of regular Bizz, which LinkedIn is full of. I got inspired in 2022 by some alternative also weirdly-acronymed TAM's, see: https://discuss.coding.social/t/challenge-fixing-the-fediverse-technology-adoption-lifecycle/38#alternative-adoption-models-4

'Fractal' stands for the pragmatic approach SX takes to organic growth at natural speed and rate of evolution, and its feedback loops.

just small circles 馃晩
just small circles 馃晩
@smallcircles@social.coop replied  路  activity timestamp 17 hours ago

@nicol @nlnet

You help with #UI design of #CivicCRM! An example I see often..

A #community-driven #FOSS project where participants, mostly coders, sigh "Oh, if only a #UX designer started contributing, how much better could we reach the broader public". Things like that. And also for various other FSDL-related stakeholder roles you often see this whistful thinking.

So why not actively *attract* people with the skills you need?

The answer often given is that "They are not interested" or something like that. But this is not true. They don't know HOW to contribute, for instance. The workflow of issue-driven feature design-by-concensus that occurs in the issue tracker of a code forge doesn't map well onto workflows a typical designer needs, and vice versa.

https://coding.social/blog/reimagine-social/#free-software-development-lifecycle

FSDL says everyone involved is a stakeholder also the devs themself. If you have a Need, then account for it.

In #SX the Process of solution development is *part of* the solution. Its all one sticky note.

Social coding commons

How We Reimagine the Social Web

We find novel ways to collaborate and create value together.
  • Copy link
  • Flag this comment
  • Block
just small circles 馃晩 boosted
just small circles 馃晩
just small circles 馃晩
@smallcircles@social.coop  路  activity timestamp 3 days ago

@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

Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
  • Copy link
  • Flag this post
  • Block
just small circles 馃晩
just small circles 馃晩
@smallcircles@social.coop  路  activity timestamp 3 days ago

@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

Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
Transition from FOSS project to SOSS initiative. Sustainable open social software, to systems, to services, to solutions. Via the Free software development lifecycle (FSDL).
  • Copy link
  • Flag this post
  • Block

A small Bonfire corner on the internet

This is a small personal instance of Bonfire in the Fediverse.

A small Bonfire corner on the internet: About 路 Code of conduct 路 Privacy 路
Bonfire social 路 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Code of Conduct