From today, I’m starting a small series of daily devlogs where I’ll be describing the changes being implemented before the official release of the first version of /kbin. As I mentioned earlier, I had some minor turbulence in my private life from which I’m slowly emerging. I have partially stabilized my life situation in various aspects. I hope this will help me smoothly return to old habits, maintain consistency, and keep you updated on what specifically is happening in the project.
There’s a lot of mess I need to sort out, starting from overdue tasks that failed in queues, improving the infrastructure, and ending with going through pending emails and private messages. The first report will be out either today or tomorrow evening, as I am just about to start working on it.
@[email protected], please. All they need is commits, PRs and comments that add something. True, dev work is full of cool updates and reporting, but it crosses roads with other mundane activities. Devlog is probably going to drain you more than it’s worth, so I hope you’ll build your priorities straight.
Let’s be open: I’m only making a press-kit for Mbin recently (and nothing much) just after being introduced to the fork as a result of @[email protected] migrating. It’s a crazy amount of reviewed and merged pull requests, which I couldn’t dream of committing nor reviewing in detail. There is simply a lot that can be done with community harnessing the project. No way this fork would be considered serious if it were to feed everyone with blog updates. At this point, your words set up a head start. It’s a matter of whether it will start: will these old habits offer something that was not served already? (Big downtimes happen to be one of those things…)
No idea if any competition will take place - again, introduction to a fork was ever so sudden, making me wonder if it didn’t have to come to this. In any case, whatever we continue doing I hope remains healthy for the wider community of contributors and users. Thank you for returning! 🤝