blaineJan 3, 2023

I am forever grateful to him for building & popularizing Mastodon, but I don't think @Gargron should be working on features at all right now.

Instead, he and the Mastodon non-profit (and a whole bunch of others) should be figuring out governance for collectively making decisions about Mastodon. Features in the Fediverse shouldn't be up to one guy, or even one company.

That's the whole point of the Fediverse. We do this together, or not at all.

Show threadDee Toher
@blaine I think that concentrating on what features/ changes should be prioritised would be a useful focus for @Gargron - then perhaps (partially at least) outsourcing implementation - with some useful code review happening, would help prevent burnout.
Jan 3, 2023 at 11:57amWeb
Show threadMatt HaugerJan 3, 2023
@DToher I THINK (?) @blaine may be hoping for another level of abstraction here. I.e., @Gargron wouldn’t be concentrating on which features to add—rather on how the community DECIDES which features to add?
Show threadDee ToherJan 3, 2023
@matt I know - but my proposal would help ease him on the way to this!
Show threadMatt HaugerJan 3, 2023
@DToher Gotcha! Makes sense. I wonder if the Masto nonprofit currently has enough funding for him to yield the coding to others?