Live data from Hacker News

Open letter to Gitea

gitea-open-letter.coding.social

51–60 of 152 posts

Re: Open letter to Gitea

#51

Am I right in assuming that though lots of work has happened in gitea since the fork, at least half of the code there was still written by the guy behind gogs? They're just going to form a for-profit based on his work and cut him out entirely?

The issue isn't about access to the code (which is not threatened at all). The issue is about community enjoying access to the project name and domain name.

Re: Open letter to Gitea

#52
post #37
post #33

Earlier quoted context omitted.

I feel you're missing the point. This person is saying that one should communicate first. If you perceive communication exclusively as "activism" or "apology" seeking (or cancellation?), then I understand why you might not choose that path. But others often choose open comms before heavy action, and many contributors would support that. And yes, "forking" is subjectively a heavier action to some ppl. It's subjective,…

Quoted post unavailable.

I'm having trouble understanding why you're so bothered by people having a quick round of communication or two before deciding forking is necessary, when it's possible it may not be.

It's not "get[ting] mad about a ball game", it's basic communication. Right?

Re: Open letter to Gitea

#53
post #48
post #46

Earlier quoted context omitted.

> qualify yourself, you've contradicted me! No. It's friday. Go write some code. The essence of this thread is people feeling they're owed what they aren't.

You sound like the sort of tech peer who I don't get along with, nor want to work with, and so I'll take my leave

No post body was provided.

Re: Open letter to Gitea

#54
post #34
post #19

Earlier quoted context omitted.

> Tellingly, it never appears to be the ones who do the actual work who throw such tantrums. And how do you know that, if I may ask?

Quoted post unavailable.

This is just a feeling you have, which you're asserting as fact. It's a thought terminating cliche that's employed to dismiss a group of people without having to listen to them.

Re: Open letter to Gitea

#55
post #37
post #33

Earlier quoted context omitted.

I feel you're missing the point. This person is saying that one should communicate first. If you perceive communication exclusively as "activism" or "apology" seeking (or cancellation?), then I understand why you might not choose that path. But others often choose open comms before heavy action, and many contributors would support that. And yes, "forking" is subjectively a heavier action to some ppl. It's subjective,…

Quoted post unavailable.

[deleted]

Re: Open letter to Gitea

#56
post #28

Earlier quoted context omitted.

The dispute here isn't about the code. It's about the domain name and trademark.

Quoted post unavailable.

Standard HN weirdo behavior getting angry at imaginary opponents and ranting about personal agency

You’re in a discussion section. Things will be discussed. Unless YOU are a top contributor to gitea, you’re doing exactly what you’re complaining everyone else here is doing: wasting time opining on the direction of a software you didn’t write

Re: Open letter to Gitea

#58
post #37

Earlier quoted context omitted.

Quoted post unavailable.

What an absurdly condescending and inaccurate comment, especially for someone saying just fork it instead of actually interacting with people to try to reach resolution of an issue. “Just fork it” is literally the opposite of working with others. Splintering an ecosystem can end up with a worse outcome for everyone. A fork that no one cares about, created because someone had a tantrum instead of reaching resolution i…

No post body was provided.

Re: Open letter to Gitea

#59
post #27
post #16

While communication may not have been handled perfectly, this is an annoyed, entitled, entirely unnecessary tract. Tellingly, it never appears to be the ones who do the actual work who throw such tantrums. And how about just extending the benefit of the doubt instead of immediately feeding the outrage machine?

You can't slander them by saying they're throwing a tantrum, without even talking about what parts of the document you're referring to or why it is you feel that way, and then decry how they're not giving anyone the benefit of the doubt. That is pearl clutching. Writing them to resolve this issue in good faith, is giving them the benefit of the doubt.

Outsider opinion:

So I think the entire doc as a first step in supposed good communication is in bad faith. Bringing this out into the public, and being on the front page of HN makes it seem like a stunt, and for pressure, not a good faith plea. I feel like a private conversation between the concerned parties should have happened first, and if it did that should have been mentioned. If that didn't work then maybe make it public for pressure, and then fork (and or consider legal action to get the trademarks if there's grounds idk not a lawyer).

If people's idea of good first step communication is to create a public letter with accusatory undertones and get it plastered places, I don't want to work with those people. They went from 0mph to 120mph way too quickly.

Re: Open letter to Gitea

#60
post #44

I’ve never participated in an open source community so this is the view of an ignorant third party. Everytime I see anything related to the open source world bubble up into the public I am only reminded of high school and college level social drama. It seems utterly exhausting to be involved

Disputes are not unique to open source projects. But they usually have no hierarchies and no contracts. So disputes are settled this way.
Post reply on HN