look
the development of mastodon needs to be a more organized effort than it is currently
while the features being added are good, there's some that are asked for repeatedly and there just needs to be like 1 or 2 people
sitting and listening and trying to work on the issues that are asked for and only those issues
@boots but apparently "developers do this for FREEEEE so they're not obligated to do anything they're not interested in" and "saying 'fuck off' is totally an acceptable response to people telling you what to develop because OPEN SOURCEEEEE"
@creatrixtiara honestly i think the real issue is that the mastodon team does not scale as well as the software did
Software is rarely developed that way unless there is a CEO making the request for features.
@Algot and
i'm not saying the current team drop everything
i'm saying get some new people where their "job" is to fix the issues that people are asking to be fixed
That might work, assuming the "new" person has the necessary skills and the drive to make the open source contribution.
@boots as big as mastodon is it is still pretty much just a pet project @Gargron started doing.
Turning it into more than that takes a lot of work. Seriously, a lot of work. And a lot of work from people who aren't Gargron. Also if someone is doing it for more than just because they feel like it they need to be compensated somehow.
@boots are you willing to pay for that? I'm not sure you understand how open source software works...
@Daenyth you are the fifth person to tell me this
i understand i am just hoping that people would volunteer. to get stuff done. because there's some semblance of a dev team and i want it to actually be a dev team.
@boots One approach to this if you're not willing / able to work on it yourself, would be to help prep it for someone who can. Make sure everything is well documented, make sure "new contributor" documentation and guidelines are in place, draft up requirements and implementation suggestions and a clean milestone for the features you want to see, and then actively search, letting people know you're looking for a developer to contribute specifically for that feature.
@boots As a FOSS maintainer I think that's the approach most likely to pay off.
like, just have people who work on these seperate types of issues where it's not the thing everyone on the team is working on