{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@nolan @smallcircles @baldur my big task for hometown in 2023 is to make it somewhat less of a "me" project
Wow, looks like a great book @baldur and totally agree on what read on the site.
In #SocialCoding holistic systems-thinking is represented by a focus on the entire Free Software Development Lifeycle (FSDL) from Inception to end-of-life. And it can only be a pattern library, because a 'best approach' always starts with "It depends.."
There's also focus on supportive tools to accompany best-practice patterns, and esp. wielding the Fediverse social networking in a new paradigm.
@darius
I'm no expert, but I feel that for the longevity of projects it's more important to have a solid core team of a few people (maybe with two maintainers and other volunteers) than having a big community. Because I think you're only able to grow such mental model through intense involvement. I've been trying to contribute my piece to that objective with @AntennaPod for a few years now. It goes very slow, but it seems to be moving in the right direction.
@nolan @smallcircles @baldur
Maybe you might look in combining efforts with #Ecto cc @weex ?
David is exploring Hintjens C4 approach to Ecto development, see: https://magicstone.dev/why-c4
FYI @RyunoKi and I followed-up with some further thoughts on the Social Coding forum:
https://discuss.coding.social/t/foss-dynamics-from-joy-of-coding-to-duty-and-burdens/234/2