Commit Graph

87 Commits

Author SHA1 Message Date
yp05327 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
hiifong ae90b21db0
Apply to became a maintainer (#32614)
[PRs
list](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Ahiifong+is%3Aclosed+is%3Amerged)
2024-11-22 18:26:05 +00:00
Kyle D d6f8a60b65
Add bohde as maintainer (#31601)
[4 merged
PRs](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Abohde+is%3Aclosed)
2024-07-10 08:18:35 +08:00
Kemal Zebari 880e0b7c82
Apply to become a maintainer (#30884)
Hello! After contributing for some time I am interested in taking a more
involved role as a maintainer. When time allows it, I plan to perform
code reviews, continue resolving/triaging issues, and engage with the
community to see if I can offer any useful insights. My current
interests are in backend work, but I plan to study the web frontend
architecture to see if I can contribute there as well.

Thanks for this awesome project. I hope I can both learn and contribute
to its continued success!

PR list:
https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+author%3Akemzeb
Discord: kemzeb
2024-05-07 14:41:52 +02:00
HEREYUA 7ba485bd49
Apply to become a maintainer (#30151)
PRs:https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3AHEREYUA+is%3Aclosed

Discord: hereyua
2024-03-28 02:47:05 +00:00
Tim-Nicas Oelschläger ff9dc51243
Apply to become a maintainer (zokkis) (#29383) 2024-02-24 14:19:49 -06:00
Gary Wang 4335c332ba
Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Kerwin Bryant 47258fad63
Apply to became a maintainer (#27491) 2023-10-07 13:24:17 +08:00
Nanguan Lin a457eb9415
Apply lng2020 to maintainers (#27068)
Hi all,

I've very much enjoyed working on Gitea and was hoping to make it
official by requesting maintainership. 

My [merged PRs
list](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+sort%3Aupdated-desc+author%3Alng2020+is%3Amerged)
2023-09-14 12:10:12 +08:00
Rui Chen bfa22a473e
Add @chenrui333 as maintainer (#26917)
relates to https://gitea.com/gitea/homebrew-gitea/pulls/179

Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-09-05 14:47:07 -04:00
CaiCandong e9d631ec03
Apply to become a maintainer (#26514)
Here is my PR list:- [go-gitea/gitea/pulls (author:caicandong is:merged)](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+sort%3Aupdated-desc+author%3ACaiCandong+is%3Amerged)
2023-08-15 11:30:06 +02:00
puni9869 32b26181d7
Apply to became a maintainer. (#25745)
Hi Gitea Team, 
I would like to apply as a maintainer.
I don't have that much in-depth knowledge of the codebase, but I would
like to help to review PRs for the beginning in my free time and
contribute in frontend, backend tasks and new proposals.

Here is my PR list:-
https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Apuni9869+is%3Amerged+
2023-07-07 13:49:34 +02:00
Denys Konovalov e7f281e1ae
Application as a maintainer (#25614)
Hi everyone,
as discussed in `#develop` I would like to apply as a maintainer.
I don't have that much in-depth knowledge of the codebase, but I would
like to help to review at least smaller PRs for the beginning.
Here is my PR list:
https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Adenyskon+is%3Amerged
2023-07-01 07:54:17 +08:00
Philip Peterson 69e73fdcff
Add self to maintainers (#23644)
Hi all,

I've very much enjoyed working on Gitea and was hoping to make it
official by requesting maintainership. :) Excited to see what the future
holds for this project.

My [merged PRs
list](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Aphilip-peterson+is%3Amerged+)

Cheers,
Phil

---------

Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2023-05-25 07:58:38 +08:00
Gary Moon c367b63b7f
Add @garymoon to MAINTAINERS (#24752)
Hi all.

I would like to apply to be a maintainer please. I have [four accepted
PRs](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Agarymoon)
(such as they are), sign my commits, and have MFA enabled everywhere. My
hope is to continue with code contributions where I can (I'm not a
developer, just a wannabe), take some work off kdumont's hands, and
contribute on the infrastructure side where there is room 💚 🍵

Thank you!
2023-05-16 11:46:46 -04:00
wxiaoguang 3274ab2943
Apply to become maintainer (#24254)
PRs:
https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+author%3Awxiaoguang
2023-04-21 21:23:16 +08:00
Yarden Shoham 6a0ef71984
Yarden Shoham has a new email address (#23767)
Got a domain
2023-03-28 18:24:08 +08:00
Matthias Loibl ad6444ff1c
Remove @metalmatze as maintainer (#23612)
It's time. I haven't been active in years.
2023-03-21 06:17:58 -04:00
xin-u d27d36f2f4
Remove xin-u from maintainers (#23170) 2023-02-27 03:20:57 -05:00
HesterG 045becf9aa
Add HesterG to maintainers (#23104)
[List of mine merged
PR](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3AHesterG+is%3Amerged+)
2023-02-24 14:31:02 +08:00
sillyguodong 90a7bba1f2
Add sillyguodong to maintainers (#23067)
[List of mine merged
PR](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Asillyguodong+is%3Amerged+)
2023-02-22 18:32:00 +08:00
yp05327 4fcf3a3f90
Add me to maintainers (#23026)
Add me to maintainers.

[My PRs
list](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Ayp05327+is%3Amerged+)
2023-02-21 10:56:13 +08:00
Zettat123 1d64eafe8f
Add me to maintainers (#22998)
Add me to maintainers.

[List of merged
PRs](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3AZettat123+is%3Amerged)

Co-authored-by: Jason Song <i@wolfogre.com>
2023-02-20 16:42:02 +08:00
Morgan 4d306325c1
Remove thehowl from maintainers (#22917) 2023-02-15 08:35:46 -06:00
Xinyu Zhou 84001467bd
Update username (#22147)
update my email & username
2022-12-16 15:11:03 +02:00
silentcodeg 3243dbe1a9
remove silentcode from MAINTAINERS (#22143)
Signed-off-by: silentcode <silentcode@senga.org>
2022-12-15 09:41:38 -06:00
Gusted 4c6b4a67d9
Remove Gusted as Gitea maintainer (#21676) 2022-11-03 19:34:24 -05:00
Yarden Shoham 578b43ddb5
Add yardenshoham to maintainers (#21566)
[List of merged
PRs](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3Ayardenshoham+is%3Amerged)
(with many more on the way!)

Co-authored-by: Lauris BH <lauris@nix.lv>
2022-10-23 12:09:21 -04:00
Jason Song 5710ff343c
chore: add myself to maintainers (#21028) 2022-09-02 20:23:48 +08:00
PEN² 070e5d4a4a
Add myself to MAINTAINERS (#20786)
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2022-08-14 13:08:53 +03:00
singuliere 1fef9a2d69
Remove singuliere from MAINTAINERS (#19883) 2022-06-13 21:05:41 +01:00
Wim d9b50e4fd1
Update MAINTAINERS (#19896)
Added myself as maintainer
[List of PRs](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3A42wim+is%3Aclosed)
2022-06-05 20:55:08 +01:00
silentcodeg f6c992974e
Add silentcodeg to MAINTAINERS (#19771)
* Add silentcodeg to MAINTAINERS

* add missing trailing g to chat nick

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2022-05-21 20:09:37 +08:00
singuliere 5d4ee44ed3
Add singuliere to MAINTAINERS (#18148)
Signed-off-by: singuliere <singuliere@autistici.org>
2022-01-02 02:12:13 +01:00
Andrey Nering aa4355ba1f
Remove me from the maintainers (#17599)
I haven't being involved in a while.
2021-11-09 22:40:16 +08:00
Gusted 9d97cf3a71
Add @Gusted to maintainers filer (#17581) 2021-11-07 14:23:39 -05:00
delvh a82c799fc8
Add delvh to MAINTAINERS (#17170) 2021-09-28 14:28:12 +02:00
Jimmy Praet 2a98ec1c3c
Add jpraet to MAINTAINERS (#16274) 2021-06-27 18:35:31 +01:00
Steven 3d991319df
Update MAINTAINERS (#16162) 2021-06-15 15:16:18 -04:00
KN4CK3R 07aa3845f8
Update MAINTAINERS (#15382) 2021-04-09 19:11:31 -04:00
Patrick Schratz ab70b2f4e4
add pat-s to MAINTAINERS list (#15007) 2021-03-16 14:37:04 +00:00
Kyle D e475ccfe09
Add kdumontnu to MAINTAINERS (#14964) 2021-03-11 23:25:07 +01:00
Cirno the Strongest 736928286b
Remove self from MAINTAINERS (#14286)
My time is limited and given recent developments, I don't think i want to dedicate any more of my time to this project.
2021-01-09 01:53:19 -05:00
Norwin b8c58edf39
add @noerw to maintainers (#13997)
* add @noerw to maintainers

* format

Co-authored-by: 6543 <6543@obermui.de>
2020-12-15 14:19:26 -05:00
Karl Heinz Marbaise 18e4477ad4
Add Karl Heinz Marbaise as maintainer. (#13915) 2020-12-09 09:39:14 -05:00
a1012112796 5e34d3d2c0
Apply to become a maintainer (#13201)
Dear gitea's managers and contributors, I apply to become a
maintainer of gitea. I'm interested in this project and has
sent prs to gitea also. I will do more things to make gitea
better and reviw other contributors's pr in my free time.
Thanks.

Signed-off-by: a1012112796 <1012112796@qq.com>

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-10-18 12:12:51 -04:00
Cirno the Strongest 29fbe63ba9
Add myself to MAINTAINERS (#11494) 2020-05-18 16:50:22 -05:00
techknowlogick cbf18f61d1
Update Owners for upcoming year (#9290)
Close #9230
2019-12-07 21:51:55 -05:00
David Svantesson 4256781781 Add myself to maintainers (#9240) 2019-12-03 14:05:23 +01:00
jaqra 5b33ffe7c5 Add myself as maintainer (#8708) 2019-10-27 16:45:21 -04:00