Hi there, in the upcoming kbin releases, I will be describing the changes along with author tags, but for now, you can check out what’s happening here: https://codeberg.org/Kbin/kbin-core/activity, as well as my personal feed: https://ernest.dev
Today, two test instances will be created where we will be looking for bugs for some time, and then the changes will be rolled out to kbin.social and hopefully other instances as well :)
I want to accept as many pull requests as possible, currently, there are still 50 open ones. I’m also following your posts and adding new things to the to-do list.
Have a nice day!
If possible what I’ve seen help very much is to have a second person join on as being the “ticket review guy.” That person will act as a community manager and really won’t do that much coding. Usually they’ll have a technical background and will understand the code they’re reading in pull requests, but for the most part they’re there to allow the primary code writer to focus on writing big features and executing core vision while the community at large contributes fixes, tweaks, and features that hadn’t been baked into the core vision