Files
Gitea/MAINTAINERS
T
yp05327andGitHub 300b724abf Leave MAINTAINERS and the organization (#32820)
## Why join
I didn’t talk about myself before, so some people may think that I am an
employee from the company. So I think it is necessary to talk about why
and how I joined.
At the begining, my boss gave me a task to find a git software which can
self hosted in on-premise. Then I found that there are not many project
which meet our needs. But finally, I found Gitea. A easy use, easy
maintenance, and without a good machine you can also run it.
At that time, I just finished my previous work which is using helm to
deploy something in K8s. So I tried to use Gitea’s helm chart to deploy
in my work PC to see whether we can use it. But soon, I found a bug, and
reported it (https://gitea.com/gitea/helm-chart/issues/382), but after
about 1 month, there’s no fix. So I try to check the source code, and I
found that it is caused by Gitea’s code and it is easy to fix it. So I
created an issue (https://github.com/go-gitea/gitea/issues/22523) in
Gitea. But unfortunately, after a long time again, it is still not
fixed. So I tried to finish it by myself.
I’m not a pro programmer, coding is just my hobby since I was 13 or 14
years old. (I will tell the reason later), I even don’t know the
workflow about the contribution of OSS, so maybe I did some bad things
at the early time, I apologize.
But the people here are very kind, at that time, I start to consider
whether it has worth to recommend to my boss. So I started to use it,
but I found more and more bugs in a short time. Japanese company is very
sensitive to it, so I gave up to recommend.
But I can try to fix them! Because I can learn too many things during
the contribution, not just about the programing but also the usage of
other tools and the general contribution rule in the world of OSS. It
let me grow up, and to become (maybe) a perfect full-stack engineer
which is my dream. (Why it is my dream? I made a wrong decision in my
college, I took/followed the advice of my parent, choosed communications
engineering instead of computer science which is my favorite thing)
 
# Why leave
Several days ago, there’s an
[article](https://juejin.cn/post/7446578471901626420#comment) came into
my eye. Something about JiHu (GitLab Ltd in China) start to file a
lawsuit to the company which is using GitLab CE version which is under
MIT License. So people start to find other git service/application to
avoid it. And in the this article, a project called Fogejo is mentioned.
It says it is a hard-fork of Gitea. But I don’t know the meaning of
`hard-fork`, so I access the home page of this project to find where it
comes from.
Finally, I found it here:
https://forgejo.org/compare-to-gitea/#why-was-forgejo-created. They
said:
> As of early 2024, Forgejo is developed independently of Gitea, as a
“hard-fork”.

`hard-fork` has a quotation, so the meaning is not the original meaning
of it, but they said `as`, which means `like` or `similar` I think. So
just focus on the words before `as` is ok, because `hard-fork` is a
simile, `As of early 2024, Forgejo is developed independently of Gitea`
is what they want to say.
In my mind, this means:
since early 2024 Forgejo’s codes (new changes) are all written by
themselves, and emphasize that these changes are not related to Gitea,
because they can simply say `As of early 2024, Forgejo is developed
independently, as a “hard-fork”`

But after I check the commit history, I can still find some strange
commits in recent month:

https://codeberg.org/forgejo/forgejo/commits/branch/forgejo/search?q=author%3Ayp05327&all=
The author is me, but the commit is signed by someone I even never
heard.
Considering the words they said above, it feels/sounds like my work has
become their work. Although Gitea is under MIT license, is this allowed
in the OSS world?
Even it is allowed, I can not accept it personally.
So I created a issue to ask them:
https://codeberg.org/forgejo/forgejo/issues/6236
https://codeberg.org/forgejo/discussions/issues/251

Finally, it seems that they understood the problem and promised to
improve it. But I also required a public statement to explain it which
means they need to apologize, otherwise it is hard to the users who
believe these are all their work know it, and it seems they ignored some
of my words again? So it is hard for me to believe they will really make
changes and post the apologize. If they did, I will consider to come
back. Otherwise, I think there’s no worth to continually contribute to
any OSS project, so I decided to leave.

ps: TOC voting is still ongoing, please remove me from the list. And I
will leave the organization after the merge.

At the end, thanks to all people who have helped me to finish the
contribution and teach me new knowledges.
2024-12-16 00:38:18 +00:00

66 lines
3.0 KiB
Plaintext

Alexey Makhov <[email protected]> (@makhov)
Bo-Yi Wu <[email protected]> (@appleboy)
Ethan Koenig <[email protected]> (@ethantkoenig)
Kees de Vries <[email protected]> (@Bwko)
Kim Carlbäcker <[email protected]> (@bkcsoft)
LefsFlare <[email protected]> (@LefsFlarey)
Lunny Xiao <[email protected]> (@lunny)
Rachid Zarouali <[email protected]> (@xinity)
Rémy Boulanouar <[email protected]> (@DblK)
Sandro Santilli <[email protected]> (@strk)
Thibault Meyer <[email protected]> (@0xbaadf00d)
Thomas Boerger <[email protected]> (@tboerger)
Patrick G <[email protected]> (@geek1011)
Antoine Girard <[email protected]> (@sapk)
Lauris Bukšis-Haberkorns <[email protected]> (@lafriks)
Jonas Östanbäck <[email protected]> (@cez81)
David Schneiderbauer <[email protected]> (@daviian)
Peter Žeby <[email protected]> (@morlinest)
Matti Ranta <[email protected]> (@techknowlogick)
Jonas Franz <[email protected]> (@jonasfranz)
Alexey Terentyev <[email protected]> (@axifive)
Lanre Adelowo <[email protected]> (@adelowo)
Konrad Langenberg <[email protected]> (@kolaente)
He-Long Zhang <[email protected]> (@BetaCat0)
Andrew Thornton <[email protected]> (@zeripath)
John Olheiser <[email protected]> (@jolheiser)
Richard Mahn <[email protected]> (@richmahn)
Mrsdizzie <[email protected]> (@mrsdizzie)
silverwind <[email protected]> (@silverwind)
Gary Kim <[email protected]> (@gary-kim)
Guillermo Prandi <[email protected]> (@guillep2k)
Mura Li <[email protected]> (@typeless)
6543 <[email protected]> (@6543)
jaqra <[email protected]> (@jaqra)
David Svantesson <[email protected]> (@davidsvantesson)
a1012112796 <[email protected]> (@a1012112796)
Karl Heinz Marbaise <[email protected]> (@khmarbaise)
Norwin Roosen <[email protected]> (@noerw)
Kyle Dumont <[email protected]> (@kdumontnu)
Patrick Schratz <[email protected]> (@pat-s)
Janis Estelmann <[email protected]> (@KN4CK3R)
Steven Kriegler <[email protected]> (@justusbunsi)
Jimmy Praet <[email protected]> (@jpraet)
Leon Hofmeister <[email protected]> (@delvh)
Wim <[email protected]> (@42wim)
Jason Song <[email protected]> (@wolfogre)
Yarden Shoham <[email protected]> (@yardenshoham)
Yu Tian <[email protected]> (@Zettat123)
Dong Ge <[email protected]> (@sillyguodong)
Xinyi Gong <[email protected]> (@HesterG)
wxiaoguang <[email protected]> (@wxiaoguang)
Gary Moon <[email protected]> (@garymoon)
Philip Peterson <[email protected]> (@philip-peterson)
Denys Konovalov <[email protected]> (@denyskon)
Punit Inani <[email protected]> (@puni9869)
CaiCandong <[email protected]> (@caicandong)
Rui Chen <[email protected]> (@chenrui333)
Nanguan Lin <[email protected]> (@lng2020)
kerwin612 <[email protected]> (@kerwin612)
Gary Wang <[email protected]> (@BLumia)
Tim-Niclas Oelschläger <[email protected]> (@zokkis)
Yu Liu <[email protected]> (@HEREYUA)
Kemal Zebari <[email protected]> (@kemzeb)
Rowan Bohde <[email protected]> (@bohde)
hiifong <[email protected]> (@hiifong)