9

Somebody who was previously active on the kbin codeberg repo has left that to make a fork of kbin called mbin.

repo: https://github.com/MbinOrg/mbin

In the readme it says:

Important: Mbin is focused on what the community wants, pull requests can be merged by any repo member. Discussions take place on Matrix then consensus has to be reached by the community. If approved by the community, no additional reviews are required on the PR. It's built entirely on trust.

As a person who hangs around in repos but isn't a developer that sounds totally insane. Couldn't someone easily slip malicious, or just bad, code in? Like you could just describe one cool feature but make a PR of something totally different. Obviously that could happen to any project at any time but my understanding of "code review" is to at least have some due diligence.

I don't think I would want to use any kind of software with a dev structure like this. Is it a normal way of doing stuff?

Is there something I'm missing that explains how this is not wildly irresponsible?

As for "consensus" every generation must read the classic The Tyranny of Stuctureless. Written about the feminist movement but its wisdom applies to all movements with libertarian (in the positive sense) tendencies. Those who do not are condemned to a life of drama, not liberation.

you are viewing a single comment's thread
view the rest of the comments
[-] TheVillageGuy@kbin.melroy.org 0 points 1 year ago

Ernest has said many things in the past and many times has not lived up to his promises. So I doubt this words now. Also he's already contradicted himself on this matter.

[-] ernest@kbin.social 8 points 1 year ago* (last edited 1 year ago)

Yeah, that's true. Real-life stuff was kinda more important for me at the moment than managing the project.

For me, it's straightforward: I pushed some dev code that wasn't even a complete feature, and it got approved in your pull request. That's why I was advocating for everyone to only merged their own PRs in the /kbin repository – so that each person could take responsibility for their own work. I won't go on about this any further.

[-] TheVillageGuy@kbin.melroy.org 0 points 1 year 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.

[-] fr0g@kbin.social 10 points 1 year ago

Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill.

Now, you see, this is the part that I as an uninvolved observer who's just now catching up on the happenings do not get. Promises that were never fullfilled?
How long has or hasn't this actually been an issue? Because from what I can see looking at the codeberg commits, it seems like development stalled for how long, like a month or so?

I totally get not wanting to be left hanging and having some answers and pathway for how contributions can happen. But as you also agree on, I also get real life being more important and getting in the way sometimes. And in that sense, being out of it for a month or so does not exactly seem like an earth-shattering amount, even if it's annoying when it happens to be the project lead and not much can happen.

I just can't help but feel like all of this has been pretty impatient and premature, which also makes it hard for me to really understand the point of the fork, even if I can relate to the basic rationale behind it. But then again, I have no knowledge of the direct going ons and communications between the contributors and the events that led to this. So there might be a lot I'm just not getting.

[-] density@kbin.social 3 points 1 year ago

@fr0g I am in substantial agreement with you after reading all this back n forth.

load more comments (10 replies)
load more comments (10 replies)
load more comments (10 replies)
this post was submitted on 09 Nov 2023
9 points (100.0% liked)

Fediverse

17 readers
2 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago