• 2 Posts
  • 19 Comments
Joined 1 year ago
Cake day: July 21st, 2023
  • TheVillageGuy@kbin.melroy.orgtoFediverse@kbin.social•Mbin: A kbin fork that promises to never review PRs before merging them
    0·
    8 months ago

    Thank you for your in depth, genuine, reply

    Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn’t visible from the outside

    I am sorry but I’m having a hard time believing you when you say that you were seriously trying to delegate, as not a single soul ever said anything which would remotely confirm this. I believe you had conversations, but they ultimately didn’t result in anything in this context.

    However, in that mental state, the last thing I wanted to do was resolve conflicts among adults

    I am not sure how to interpret this as there were no conflicts that I’m aware of that needed resolving during your absence, everybody was just waiting

    I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.

    There’s nothing wrong with being like that, there are other people willing to do things like resolving issues. Like me. I realize I appeared out of nowhere. As a new instance owner it took a while for me to notice, but when the situation became clear to me I was ready to jump in and help, just like all the other people who had offered their help (before me).

    You’ve basically just admitted that you were either incapable of or unwilling to engage in structural problem solving and management of the kbin project. That’s fine, but you should have reached out and informed the community as soon as you became aware of this.

    forking turned out to be the best thing that could happen

    Yes, forking can have positive side effects and perhaps having two versions in development synchronously can merit more than one. This however was not the proper way to achieve this and using it as an excuse to justify your behavior and inaction is unjust.

    However, it is not too late. You can still do the right thing by starting delegation now, by clearly assigning multiple people to all essential tasks, and giving multiple people complete control of kbin.social, so that, should a similar situation occur in the future, you and the community will confidently know that the project will not grind to a halt again.

    Then seek a constructive dialog with the mbin community and we can make the project, in it’s current for, work. Together.

    If you feel uncomfortable with or are have trouble doing any of this, as you’ve clearly indicated you’d rather spend your time on coding, you are always welcome to ask me for advice.

    Never hesitate to ask for help.

  • TheVillageGuy@kbin.melroy.orgtoFediverse@kbin.social•Mbin: A kbin fork that promises to never review PRs before merging them
    0·
    8 months ago

    Real-life stuff was kinda more important for me at the moment than managing the project.

    As it should be, always, for everybody, you won’t ever hear me judge you on that, so please don’t try to make me look bad by implicitly suggesting I am.

    What you failed to do however is delegate, even temporarily, your responsibilities to people you trust. Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill. It seems keeping them on a leash was kinda more important to you than securing the future of kbin.

    I won’t go on about this any further.

    I hope I’ll never have to mention this again, so you’ll never have to. Which would imply that you’ll have come to terms and lived up to your promises, both recent ones and from the past.