Great question! I never shared this story. I can only answer this from my own perspective and NOT on behalf of the entire project or other devs if you can imagine. And you're correct every open-source project can have this similar situation.

1. I try to make Mbin as decentralized as possible in terms of development, contributors and no single-maintainer. I hopefully advise that by putting time and effort in writing out the C4 specification: https://github.com/MbinOrg/mbin/blob/main/C4.md. This means that every contributor can become a maintainer. So even today, I'm not the only maintainer and hopefully I will never be the only maintainer. And this goes as far as full access on the git repo(s) as well as Matrix chats.
2. Recently, a very dedicated contributor did left Mbin sadly without any announcement. This person is still being missed to this day (I hope he is doing well in RL). So bad things do happen, at the same time I hope we as a project will also attract new developers and contributors (even documentation, translation or picking up a simple UI change can already help a lot and often that is the best way to getting started).
3. I believe it's important to also take some time off. Like in the recent holiday period I forced myself to take some time off. Even then, I also do feel the pressure sometimes. At the same time; nobody is actually pressuring me. Crazy right?. Nobody is paying me to contribute to Mbin. And nobody expect me to spend time on it daily. So it's important to be aware of this situation and know it's mainly in your own head, sometimes just let it go... But you're right, you do feel a kind of obligation.
4. I also asked among the contributors if you should accept any form of money or NLnet funding or anything in that regard. Our common conclusion was: NO. Because we are doing it for fun, asking money will only create a situation were you might even feel more obligated.
5. Luckily the state of Mbin is also getting better and better over time. I'm really glad about that. In the past year we really focused on stability and scalability. Mbin also inherited a lot of issues from /kbin to be honest, and we really did some major overhauls to get the stability we and the server admins want and need (thank you all for this!). I can say that we are now in a good spot at the moment, Hopefully we also stay focused on the quality of the code, so the project will still be alive for years to come. Since nothing is worse then inheriting technical dept on top of a huge pile of issues, that is no fun.
6. Developing software for the fediverse is in general quite demanding work, no doubt about that. On top of the social media drama that often also happens. So the most important part of each open-source project is the community, the people, the interactions we have. The jokes we sometimes make. I can't thank the community enough and in the end we are all part of the fediverse community, so only we can make it fun and lead by example.

~Melroy

#mbin #firefish #kbin #activitypub #developers #developers #developers #fediverse

I think we are getting there. Currently the biggest problem I see is that melroy and I are currently the main contributors with other experienced contributors gone or at least not regularly active (which is of course their right, but its just how it is). I do have a whole lot of ideas and plans for features and I am working on a lot simultaneously, though I wouldn't say that it is a burden, more like a fun hobby. Admittedly this hobby takes a lot of time though 😅

I am very happy that new contributors are currently dipping their toe in the water and I hope they do stick around. Also a lot of the server admins are active in the matrix chat to help others out. So in this regard we are not alone.

I was honestly shocked that debounced left so suddenly and basically completely vanished... I didn't think that anyone would do that... So honestly we cannot promise anything, but I think melroy will stay around and I certainly will as well 😇

I do agree that developers should use their own software, but doing so on a smaller instance with strict active user limits is probably the right call -- at least until you are certain the software has a "stable" version, but even then you probably will want to run a master branch instance that is much less stable and prone to errors. Until you can afford it, it's probably not a good idea for developers to be spending a huge amount of time debugging in-progress features (which IIRC, firefish had a lot of those.)

I'm going to get shit on, but outside of Lemmy, there are just... no active groups on the various fediverse group site aggregators that I'm remotely interested in.

It's all news, politics, political news, and political peacocking. Which fine, if that's what you're after, but I'm here for nerd shit, and Lemmy is utterly completely awash in nerd shit.

The other problem is an ActivitPub problem. Even if you follow someone, if you're not following every single human on fucking earth, you're not going to see all the replies to their posts on your server. So your clever post was already made 8 hours ago, and unless you click on another link that takes you to their instance you can't actually browse what replies actually exist before posting.

Which is just stupid: if I have to visit someone else's shit in order to see if I should reply, I might as well just you know, use that server and save myself the trouble.

IDK, I liked the UX and it was interesting while it lasted, but it was really just a massive resource drain and had far less interesting nuggets than other options did.

Ugh, of course there is.

I thought it was more like transfem.social drama, no?