I check in here quite often, but for now, I’m just focusing on clearing spam and keeping the instance alive. In January, I was working on the AP module, and there has been significant progress in the work, which hasn’t been publicly published yet. Unfortunately, at the beginning of the year, I developed a skin condition that worsened from week to week, reaching a point where I couldn’t even leave the house. In February, I spent my time visiting doctors and undergoing treatment with medications, which often had very unpleasant side effects. Therefore, I decided to hold off on any major updates to avoid causing even more chaos. Today, I’ve undergone one procedure, and I have another one scheduled for Thursday, which I hope will be the last.
Just because it’s not visible that something is happening doesn’t mean I haven’t been doing anything during this time. In fact, two really significant things have been successful, which I’ve been working on for a long time and which I intended to announce soon once I recover.
This weekend, I also plan to work on infrastructure with Piotr, and from next week onwards, I intend to resume committing, provided my health allows it. I understand if you’re exploring alternatives, but I hope I’ve exhausted my bad luck limit for this year, and the remaining time will be marked by gradual, steady progress, especially since new opportunities have emerged, about which I will hopefully write soon.
Good luck to you!
But i think instead of waiting to announce planned things you should just show them, even in early stages.
Then we can give feedback, check your code and contribute ourselves.
You dont have to do everything, we really want to help.
Sometimes showing that things are being done is more work and way more stressful than the act of doing them, so I can relate to that.
But it would probably be a good idea to get more admins on board - sometimes one needs to take a break, and a one-person moderation team for a page with this many users cannot be sustainable in the long run. But I guess getting to a point where that is feasible, not to mention finding qualified people, might in itself be a fair share of work. :)
And of course - get well soon, Ernest! It’s great to hear from you.
It doesn’t have to be a show-and-tell. Just pushing your changes to a branch is enough. That way people can at least see that something is being worked on.
As a software dev I find it strange that you can go a month or more without pushing. At work I push at least daily, even if it’s just a WIP commit that I reset the next day.
Exactly this is what i mean.
Name your branch something useful and push reguarly.
Ernest feels like doing so much secrecy for code that is ultimately going to be public anyways… We wont scold you for having fucked up code. We will fix it ourselves if we have to.
On the other hand, if people really wanted to contribute, there’s plenty of open issues on Codeberg that are unadressed. I agree that it would be better to announce plans in advance rather than surprise drop them, but I doubt there would be more contributions from the community.
Done that, tried that. Not working great. Hence Mbin was created.
I know. I’m just saying that the idea people would magically help out on kbin if he was more open about his plans doesn’t work out, because the people willing to do so would either already be contributing to cleaning up the backlog or have moved on to mbin.
Btw, do mbin devs look at kbin issues too or do common problems have to be posted to both repositories to be seen?
Currently I wouldn’t count on it as for as long as there is no activity on codeberg, looking at it in general is a waste of time. If you find an issue on both Kbin and Mbin and are convinced it is the same issue, it’s definitely worth reporting on both.