- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
I made a blog post discussing my biggest issues with Lemmy and why I am kind of done with it as a software.
I made a blog post discussing my biggest issues with Lemmy and why I am kind of done with it as a software.
How should developers handle feature requests? Keep in mind there is a need for the whole team to see the suggestion and it’s also good to have a place to gather feedback and further discuss.
No, that’s fair. I meant to illustrate that there is also a technical gap between developers and especially the general users that come on board with mass adoption.
Community managers - sometimes just talking about your issue with someone will help tremendously in figuring out how to put it and they often can just do it for you. That said, Lemmy devs do not value work being put in the issue tracker - they have admitted to not reading it. People who cannot contribute code are just entirely ignored and have no power in the project’s direction.
I suspect the small size of the dev team and the general nature of an OSS project means there aren’t swarms of people around volunteering to be community managers.
Small projects your sway with the project is directly proportional to your ability to submit pull requests. It’s just a sad fact that it’s easier to say “I wish we had feature X” vs. “Here is a pull request that implements feature X”.
At least with OSS you are getting what you paid for (nothing!), vs commercial companies where you pay for the software and they STILL ignore you.
I mean, I essentially proposed to do this myself in private conversations with Dessalines but there was no willingness for a shared roadmap so it felt pretty pointless.
If the developers’ wants and needs don’t intersect with a given user, there is no way forward for that user, community manager or not.