Is there any chance that we can get a weekly/biweekly, or periodic, update on what is new with kbin? @ernest has done a couple in the past. I doubt I would be the only one interested in hearing what is new or what is coming down the pipe more on a regular basis.
I’m aware that I can look at the codeberg and see what is being worked on, but I’m not quite as dev saavy as a lot of you are and really appreciate some plain spoken explainers sometimes.
If not, that’s cool too. I just thought it might help keep people involved and retain users if we could see a list of exciting new additions, updates, and things to look forward to.
Hey, that’s the plan. After the first release, the status update will probably be every two weeks. Currently, I’m struggling with the preparation of the release, it’s taking up a lot of my time because I have many changes to integrate. On top of that, I’ve been going through a tough period in my personal life, but I’ve overcome it and starting from Monday, I’ll be giving it my 100%. Contributors continue to be active, and their assistance is invaluable to me. To make matters worse, I have to deal with waves of spam that have recently surfaced on kbin.social, which you’ve probably noticed. Stay tuned ;)
Don’t know how often this gets said, but everything you’ve done and are doing with kbin is deeply appreciated.
I’d say “keep it up” but I don’t want to create pressure or push anyone to burnout. Been there, done that.
Do what you’re able when you’re able.
(That doesn’t trip off the tongue quite so easily, but it’s my motto these days).
Sorry to hear you’re having a rough go of it, but glad you’re on the other side of it now. <3
Also, thanks for the reply! Would this be something you could delegate out to someone? I understand you have a lot on your plate.
Currently, all I need is a bit more time ;) I’m gradually granting additional permissions and sharing responsibility with contributors. We still need to establish a some policy. If it speeds up work on /kbin, I’m okay with that. They are great and experienced developers. However, it’s important to remember that they all do this in their free time.
the thing is that the only people who are capable to do that are those who are involved with the development. and to write something about all the changes, someone would have to be involved or at least knowledgeable about a variety of aspects of the software.
The people who run this particular repo are pretty vigilant at tagging the issues. It’s not necessarily comprehensive but you could try filtering by pr pending (also toggle the open/closed option at the top left; I can’t find a way to display all of them together on codeberg)
“PR” = pull request. which is what it’s called when someone makes a change to the code.
I am also not a developer but I like to nose around in these things. :) I’m sure you can understand the gist of a lot of them. Like we have “Strip whitespace of emails on login”, “Add a “show password” option when logging in”, “Email Address Confirmation Cannot be Re-triggered”. Also things like “Actor is null in Page and Note” which means nothing to me.
You can also look directly at the pull requests. Not everything is discussed in the Issues first. It’s not the case with every project but this one is reasonably clear for a non expert to look through. eg “Show full language names in smaller badges”, “Add upvote color when an item is boosted” etc.