this post was submitted on 09 Nov 2023
9 points (100.0% liked)
Fediverse
19 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It is good to really see your true nature now. I'm also think the fork is the best thing that could have happened for the community. It's a pity that you never started a conversation, but instead you still try to do mean things like this.
Oh c'mon, don't be mad. It's just a wrong sorting of posts, it's in an edge case, and seriously it wasn't intentional. I just wanted to check how such management looks in practice, how many merge accepts are needed, etc. I didn't mean to do anything wrong that could cause harm. I even push the same code to my instance to facilitate your tests ;)
But you're right - that's just my nature. I approach PR with very limited trust, whether they're mine or from others.
I know your approach on PRs. Hence the main reason of the fork. The community does believe in their people and the good in mankind. Only 1 approval is required from another maintainer for now. We are using C4 way of working.
I assure you that I didn't intentionally push incorrect code into the repository. These were my first lines of code in a really long time. I simply got involved in other things that I wanted to finish first, and I noticed the edge case in the meantime, but it wasn't a priority. I saw that you were syncing and I was hoping to benefit a bit from it once you fixed it. I didn't expect the review to happen so quickly. By the way, I was genuinely curious about how this project management method works because, you know, I've always avoided such an approach. Merloy, you know how much I owe you, and I appreciate what you've done for the project, as well as the other Mbin contributors. Our overall visions haven't always been the same, and I think it's great that kbin has been forked. You see for yourself how my work looks until the release - there are many things I'll be refining over time. That's why I've put a hold on all other PRs, and now I want to focus on this.
@ernest @melroy
lol this whole conversation is a microcosm of the open source community. I agree with ernest that forks are great and would add that they show that the open source system is working as intended.
You are right. But was the whole debacle that lead to this fork being made worth it? Wouldn't it have been much better if Ernest had just sorted out all himself and we'd all be working on the same project together now instead of introducing mistakes into forks too see what happens? What a complete waste of time, especially under the current circumstances.
“True nature” in this case appears to be slow and cautious. Shocking stuff!
Ow.. it was 100% intentional. You said it yourself: "Wiem, szczerze mówiąc było to celowe. Zauważyłem, że forki synchronizują od razu zmiany z /kbin.". https://karab.in/m/karabin/p/340377/Usterka-z-crosspostami-nie-zawsze-sa-przyporzadkowane-odpowiedniemu-watkowi-matce-at-ernest#post-comment-510980
@melroy I don't think you can really be upset about anyone putting through bad code. According to the philosophy as I understand it, bad code (intentionally so or otherwise) is a useful contribution and you are basically soliciting it. You supposedly have some way other than code review to ensure nothing harmful gets through and it has to do with the reputation of the contributor. Since you already knew @ernest and clearly have a bad opinion of him, how did it happen?
I did not and could not review the PRs themselves. So I am just going on the information as presented here. Sounds like @ernest put through some code (either into kbin or mbin not clear on that) which he knew was not 100% highest quality but which error was not critical or devastating. And that it could easily be found and fixed. Partially he did this to learn more about this governance model. A model which has apparently been developed in direct opposition to his own. Is it approximately accurate?
If so, sounds a bit mischievous at the worst.
I really can't recommend Tyranny of Structurelessness highly enough.
Well I don't have a bad opinion about him (those are your assumptions), we just didn't agree on how a community project would/can work.
If however he did introduce intentionally a bug in kbin, just because of Mbin that's downright childish. The Mbin community does try to test all the incoming PRs (not just kbin sync PRs) on various instances apart from unit-tests, etc. We just do not want to depend on a single maintainer, hence a different way of working in the project.
He saying Mbin can't handle the kbin changes that is just not true (Odpowiedź: nie radzą sobie), at least we try to keep in sync (eg. for API comparability for upcoming mobile clients). But I'll leave it this, I'm not going to waste any more energy. I hope you understand.
Thanks for your recommendation.
Yep, in Polish we call it skrót myślowy.