Live data from Hacker News

Open letter to Gitea

gitea-open-letter.coding.social

41–50 of 152 posts

Re: Open letter to Gitea

#41
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.

It might be helpful if you share information on where your perspective is coming from. Your comments here confuse me, as someone peering in from the outside.

(disclaimer: I co-organize within an IRL 5000 member community revolving around civics, software and open culture. and through that, I chum around with folks involved in organizational transformation in general.)

EDIT: or not. Just maybe ppl will care more to hear or understand the opinions you're broadcasting if you offer some context?

Re: Open letter to Gitea

#42
post #18

Earlier quoted context omitted.

A bit of context (why this matters) is useful: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#... > Since Gitea is a pure community organization without any company support, to keep the development healthy we will elect three owners every year. > When the new owners have been elected, the old owners will give up ownership to the newly elected owners According to CONTRIBUTING.md, this dates back to 2016.…

It may be the case that Lunny forgot he has a moral obligation to the Gitea community that elected him year after year. Even though there is no legally binding contract. What was done is morally unacceptable. But that can be easily fixed. Just give it all back!

[deleted]

Re: Open letter to Gitea

#43

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?

[deleted]

Re: Open letter to Gitea

#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

Re: Open letter to Gitea

#45
post #11

I get tired of community uprisings and activism that fundamentally misunderstand how open source works, fork it. If you're not the in the top producers in a DoOcracy then you neglected your right to exert influence in the direction of the project. I've led a few larger projects and the rate at which the least of us will have the biggest opinions about who is -owed- what is flabbergasting. DoOcracy's are great, but th…

This is the step right before forking. If diplomacy fails, then you fork. A silent fork is much less likely to gain traction. This letter raises awareness for the problem and is the reaction to it is a solid foundation for a fork.

Your improvements to the code do not require 'traction'. The only thing that undoes a do-ocracy is another do-er, and that starts with a fork, like how Gitea started.

Re: Open letter to Gitea

#46
post #41
post #28

Earlier quoted context omitted.

Quoted post unavailable.

It might be helpful if you share information on where your perspective is coming from. Your comments here confuse me, as someone peering in from the outside. (disclaimer: I co-organize within an IRL 5000 member community revolving around civics, software and open culture. and through that, I chum around with folks involved in organizational transformation in general.) EDIT: or not. Just maybe ppl will care more to he…

> 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.

Re: Open letter to Gitea

#47
post #11

I get tired of community uprisings and activism that fundamentally misunderstand how open source works, fork it. If you're not the in the top producers in a DoOcracy then you neglected your right to exert influence in the direction of the project. I've led a few larger projects and the rate at which the least of us will have the biggest opinions about who is -owed- what is flabbergasting. DoOcracy's are great, but th…

Right to the source code is a completely separate issue from rights to the project name and domain name. You can guarantee decentralised access to the source code but you can't guarantee the same for the name and domain.

Re: Open letter to Gitea

#48
post #46
post #41

Earlier quoted context omitted.

It might be helpful if you share information on where your perspective is coming from. Your comments here confuse me, as someone peering in from the outside. (disclaimer: I co-organize within an IRL 5000 member community revolving around civics, software and open culture. and through that, I chum around with folks involved in organizational transformation in general.) EDIT: or not. Just maybe ppl will care more to he…

> 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

Re: Open letter to Gitea

#49
The most distasteful part about Gitea incorporating is that the overwhelming majority of the code is written by Joe Chen (unknwon) the creator of Gogs (which is where Gitea is forked from).

Is Joe part of the incorporated company?

Folks who are not happy about this should just switch back to Gogs.

Re: Open letter to Gitea

#50
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.

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 is not a home run. It will eventually fall so far out of sync with the main project that it will no longer get any of the maintenance or other benefits of a large project.

Post reply on HN