@sam @michaelafisher @Matt_Noyes @flancian @emi
Hi #MastoAdmin folks and cooperative fellows,
Sorry for the late answer.
I certainly am happy with our consensus, in this cooperative #neighbourhood.
(I try to show no "reason" and i have a personal problem with the verb "should".)

I advocate for people and - in our case - #FediCollectives to ❤️#learn about what they are doing.
I tried a #longThread contribution there: https://social.coop/@eric/109421900837608818 #MastodonBoughs

Please participate 🧐

Here is an illustration: the 🌱#dataProtection and #GDPR of the #MastodonBoughs heavily depends on the "upstream" project.
So #MastoAdmins install a framework insecure by design: https://github.com/clening/MastodonPrivacyGuide/blob/main/README.md

Would you try to improve the framework unsafe by design? 📢
... or ❤️#learn about #GoToSocial: https://docs.gotosocial.org/en/latest/

So you #MastoAdmin may:

This separation is fundamental for tackling maintainance and governance. The bough depends on the trunk.
The software called MastodonForks (principally #Hometown and #GlitchSoc) depend on "upstream" code with a dominating #devGovernance.

So i may argue that "flavours" are not #forks (independent) but #MastodonBoughs. (They are not plugins either.)

Here https://triangletoot.party/@autumn/109280156146184950 is a conversation on #codeMaintenance and doing #MastodonBoughs between @autumn @jon @matt and @darius