gitea

Commit Graph

Author	SHA1	Message	Date
TheFox0x7	664522ec6b	apply as maintainer (#35424 ) Applying as suggested some time ago by techknowlogick. [List of all merged PRs so far](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+author%3ATheFox0x7)	3 months ago
Steven Kriegler	25ed31e220	Step down as maintainer (justusbunsi) (#35212 ) Since I barely contributed to the Gitea code base, this is just a PR for completing https://gitea.com/gitea/helm-gitea/pulls/917 (details there).	4 months ago
Patrick Schratz	67d623580b	Step down as maintainer (pat-s) (#35213 ) Follow up to https://gitea.com/gitea/helm-gitea/pulls/918, even though I didn't contrib a lot to the core repo anyhow. Signed-off-by: Patrick Schratz <patrick.schratz@gmail.com>	4 months ago
Tobias Balle-Petersen	712fccadd6	add maintainer tobiasbp (#34372 ) This PR adds me as a _maintainer_ as suggested by @techknowlogick. A couple of my recent PRs: * https://github.com/go-gitea/gitea/pull/34324 * https://github.com/go-gitea/gitea/pull/34323	8 months ago
ChristopherHX	0070ffe560	Update MAINTAINERS (#33529 ) * Add myself to the maintainers file	10 months ago
metiftikci	83b7e12d4c	add myself to maintainers (#33088 )	12 months ago
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.	1 year ago
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)	1 year ago
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) ✅	1 year ago
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	2 years ago
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	2 years ago
Tim-Nicas Oelschläger	ff9dc51243	Apply to become a maintainer (zokkis) (#29383 )	2 years ago
Gary Wang	4335c332ba	Apply to become a maintainer (#27522 )	2 years ago
Kerwin Bryant	47258fad63	Apply to became a maintainer (#27491 )	2 years ago
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)	2 years ago
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>	2 years ago
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)	2 years ago
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+	2 years ago
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	3 years ago
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>	3 years ago
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!	3 years ago
wxiaoguang	3274ab2943	Apply to become maintainer (#24254 ) PRs: https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+author%3Awxiaoguang	3 years ago
Yarden Shoham	6a0ef71984	Yarden Shoham has a new email address (#23767 ) Got a domain	3 years ago
Matthias Loibl	ad6444ff1c	Remove @metalmatze as maintainer (#23612 ) It's time. I haven't been active in years.	3 years ago
xin-u	d27d36f2f4	Remove xin-u from maintainers (#23170 )	3 years ago
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+)	3 years ago
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+)	3 years ago
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+)	3 years ago
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>	3 years ago
Morgan	4d306325c1	Remove thehowl from maintainers (#22917 )	3 years ago
Xinyu Zhou	84001467bd	Update username (#22147 ) update my email & username	3 years ago
silentcodeg	3243dbe1a9	remove silentcode from MAINTAINERS (#22143 ) Signed-off-by: silentcode <silentcode@senga.org>	3 years ago
Gusted	4c6b4a67d9	Remove Gusted as Gitea maintainer (#21676 )	3 years ago
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>	3 years ago
Jason Song	5710ff343c	chore: add myself to maintainers (#21028 )	3 years ago
PEN²	070e5d4a4a	Add myself to MAINTAINERS (#20786 ) Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	3 years ago
singuliere	1fef9a2d69	Remove singuliere from MAINTAINERS (#19883 )	4 years ago
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)	4 years ago
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>	4 years ago
singuliere	5d4ee44ed3	Add singuliere to MAINTAINERS (#18148 ) Signed-off-by: singuliere <singuliere@autistici.org>	4 years ago
Andrey Nering	aa4355ba1f	Remove me from the maintainers (#17599 ) I haven't being involved in a while.	4 years ago
Gusted	9d97cf3a71	Add @Gusted to maintainers filer (#17581 )	4 years ago
delvh	a82c799fc8	Add delvh to MAINTAINERS (#17170 )	4 years ago
Jimmy Praet	2a98ec1c3c	Add jpraet to MAINTAINERS (#16274 )	5 years ago
Steven	3d991319df	Update MAINTAINERS (#16162 )	5 years ago
KN4CK3R	07aa3845f8	Update MAINTAINERS (#15382 )	5 years ago
Patrick Schratz	ab70b2f4e4	add pat-s to MAINTAINERS list (#15007 )	5 years ago
Kyle D	e475ccfe09	Add kdumontnu to MAINTAINERS (#14964 )	5 years ago
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.	5 years ago
Norwin	b8c58edf39	add @noerw to maintainers (#13997 ) * add @noerw to maintainers * format Co-authored-by: 6543 <6543@obermui.de>	5 years ago

1 2

93 Commits (main)