Live data from Hacker News

Open letter to Gitea

gitea-open-letter.coding.social

11–20 of 152 posts

Re: Open letter to Gitea

#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 they often flame out with the top contributor finding one day they have a self-appointed board of directors for a passion-project that they just wanted to share with the world.

Re: Open letter to Gitea

#12
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…

The word "just" is doing a lot of work here.

Re: Open letter to Gitea

#13

This is in response to: https://blog.gitea.io/2022/10/open-source-sustainment-and-th... as discussed here: https://news.ycombinator.com/item?id=33339421

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. The new company represents a shift from the community model that attracted many developers and users.

The issue is that ultimately Lunny holds the trademark and isn't legally bound to uphold whatever agreement is stated in the repo.

Re: Open letter to Gitea

#14
post #6

Gitea was a fork of Gogs. I'm assuming we'll see a fork of Gitea now?

I'm also reminded of Audacity, so maybe we'll see a half-way popular fork and then the "parent" amending their ways?

Re: Open letter to Gitea

#15
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…

Sometime people make mistakes, big ones. That happens and this open letter gives them the opportunity to make right by the community. A fork is a last resort option, when everything else failed. Patience and understanding is a good thing in Free Software communities. Even when facing what appears to be a malicious action.

Re: Open letter to Gitea

#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?

Re: Open letter to Gitea

#17
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…

It is a multi-step process. First you do the right thing and kindly ask to repair trust that has been breached. If that doesn't work, which is a likely outcome, discussion about forks are in order. "Just fork it" is easy to say, but with large projects require careful consideration. There's too many people saying "just fork it" all too casually, if you ask me.

Re: Open letter to Gitea

#18

This is in response to: https://blog.gitea.io/2022/10/open-source-sustainment-and-th... as discussed here: https://news.ycombinator.com/item?id=33339421

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!

Re: Open letter to Gitea

#19
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?

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

Re: Open letter to Gitea

#20
post #17
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…

It is a multi-step process. First you do the right thing and kindly ask to repair trust that has been breached. If that doesn't work, which is a likely outcome, discussion about forks are in order. "Just fork it" is easy to say, but with large projects require careful consideration. There's too many people saying "just fork it" all too casually, if you ask me.

> First you do the right thing and kindly ask to repair trust that has been breached

Gitea is a self-labeled "DoOcracy". nobody owes an apology. forking is inherent to open source methodology. ideological conflicts help nobody but those who lead them. the fact is that the work is done by few, and those few have decided to exercise their rights in open source to do what is their prerogative.

Post reply on HN