Update README.md with company info #10083

Closed
opened 2025-11-02 08:57:47 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @buhtz on GitHub (Jan 11, 2023).

Description

Please update your README.md with informations about "Gitea Limited" and note that the project is now commercial drivin.

Gitea Version

latest

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I don't.

Database

None

Originally created by @buhtz on GitHub (Jan 11, 2023). ### Description Please update your README.md with informations about "Gitea Limited" and note that the project is now commercial drivin. ### Gitea Version latest ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I don't. ### Database None
GiteaMirror added the type/docs label 2025-11-02 08:57:47 -06:00
Author
Owner

@jolheiser commented on GitHub (Jan 11, 2023):

We are currently discussing/voting on governance amongst the maintainers, after which I'm sure there will be an update to CONTRIBUTING.md.

In the meantime, I'm not entirely sure what would be changed in the README, do you have suggestions?
Just mentioning Gitea Ltd?

@jolheiser commented on GitHub (Jan 11, 2023): We are currently discussing/voting on governance amongst the maintainers, after which I'm sure there will be an update to `CONTRIBUTING.md`. In the meantime, I'm not entirely sure what would be changed in the README, do you have suggestions? Just mentioning Gitea Ltd?
Author
Owner

@buhtz commented on GitHub (Jan 11, 2023):

Then maybe I misunderstood the organization.
I thought the maintainers/admins of this repo here at github do work for "Gitea Limited".

If they are not maybe you should write a small section about the "relation" between this repo and "Gitea Limited" and its current state.

Maybe it is not clear for all persons.

btw: Because of "Gitea Limited" there was a fork out of Gitea created named "Forgejo". So there happens a lot around and it is sometimes hard for coming-by-users to be aware of all details.

@buhtz commented on GitHub (Jan 11, 2023): Then maybe I misunderstood the organization. I thought the maintainers/admins of this repo here at github do work for "Gitea Limited". If they are not maybe you should write a small section about the "relation" between this repo and "Gitea Limited" and its current state. Maybe it is not clear for all persons. btw: Because of "Gitea Limited" there was a fork out of Gitea created named "Forgejo". So there happens a lot around and it is sometimes hard for coming-by-users to be aware of all details.
Author
Owner

@jolheiser commented on GitHub (Jan 11, 2023):

I thought the maintainers/admins of this repo here at github do work for "Gitea Limited".

Currently (as far as I know) there are three maintainers who work for the company, and a few others who are being compensated on a part-time contract basis (paying open source developers 🥳)

If they are not maybe you should write a small section about the "relation" between this repo and "Gitea Limited" and its current state.

I think this will likely happen once we have concluded the maintainer governance discussion, at least in some form. 🙂

Because of "Gitea Limited" there was a fork out of Gitea created named "Forgejo". So there happens a lot around and it is sometimes hard for coming-by-users to be aware of all details.

We are aware, and it has been an interesting time trying to keep all the details sorted. 😅

@jolheiser commented on GitHub (Jan 11, 2023): > I thought the maintainers/admins of this repo here at github do work for "Gitea Limited". Currently (as far as I know) there are three maintainers who work for the company, and a few others who are being compensated on a part-time contract basis (paying open source developers 🥳) > If they are not maybe you should write a small section about the "relation" between this repo and "Gitea Limited" and its current state. I think this will likely happen once we have concluded the maintainer governance discussion, at least in some form. 🙂 > Because of "Gitea Limited" there was a fork out of Gitea created named "Forgejo". So there happens a lot around and it is sometimes hard for coming-by-users to be aware of all details. We are aware, and it has been an interesting time trying to keep all the details sorted. 😅
Author
Owner

@wxiaoguang commented on GitHub (Jan 11, 2023):

(OK, edit with details)

Some people of the fork Forgejo, they are lying about Gitea.

Please see how they lie, I am NOT.

image

@wxiaoguang commented on GitHub (Jan 11, 2023): (OK, edit with details) Some people of the fork Forgejo, they are lying about Gitea. Please see how they lie, I am NOT. ![image](https://user-images.githubusercontent.com/2114189/211867202-d71424cd-74d1-4343-bce5-520646dd7f3b.png)
Author
Owner

@jolheiser commented on GitHub (Jan 11, 2023):

I think we've gathered and responded to what will happen to clarify this issue, so I'm going to lock it as further discussion likely won't yield any further results.

For any other concerns, I think there are other public spaces that could probably be used that are better than a GitHub issue.

@jolheiser commented on GitHub (Jan 11, 2023): I think we've gathered and responded to what will happen to clarify this issue, so I'm going to lock it as further discussion likely won't yield any further results. For any other concerns, I think there are other public spaces that could probably be used that are better than a GitHub issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10083