Gregory's Server@dajb good clarification! not on the technical side, more on the governance side. there's the "how do we share the load" / "what does admin mean and who does it" / "how do we make decisions" etc considerations (think it would be helpful to have a "so you're thinking about starting a cooperative masto instance; here's things to think about" guide), and my experience is that communities need additional tools to self-govern (we have tried using loom.io on friend camp)
|
5 comments
  @edsu @dajb definitely agree it's a good start! (I'm on darius's server he describes in that piece). I think there's some additional guidance that would be useful from folks who have done the collective governance part, though (which is why I think social.coop folks could be a great source of that material) @christa So I'd like to be part of these discussions as well! 😄 I'm part of social.coop and have experience running a co-op (@weareopencoop) but that doesn't necessarily prepare me, for example, to be admin of https://exercise.cafe My questions would be like yours around: 1. Admin/moderation |
@dajb so, some of it is mapping the technical domain to collective governance. every instance will have its own approach, obviously, but I think it'd be helpful to have reflections from instances that have done it before as others consider it