gitea/awesome-gitea
56
137
Fork 88
Code Issues 2 Pull Requests Actions Releases Activity

Requirement for new items #80

New Issue
Open
opened 2022-05-21 20:05:59 +00:00 by Gusted · 3 comments
Gusted commented 2022-05-21 20:05:59 +00:00
Copy Link

Currently, there is not really a requirement in order to be listed on the awesome gitea list. However, I will propose a hard requirement that needs to be filled for new items.

They must be hosted on a gitea instance (either gitea.com, codeberg.org or a local one). Personally, it doesn't make any sense that software is created around Gitea but then uses e.g. Github to host this software, which is really the opposite of what Gitea stands for. I don't think we should encourage this line by allowing entries that are hosted on Github.

Currently, there is not really a requirement in order to be listed on the awesome gitea list. However, I will propose a hard requirement that needs to be filled for new items. They must be hosted on a gitea instance (either gitea.com, codeberg.org or a local one). Personally, it doesn't make any sense that software is created around Gitea but then uses e.g. Github to host this software, which is really the opposite of what Gitea stands for. I don't think we should encourage this line by allowing entries that are hosted on Github.
👎 1
lunny commented 2022-05-22 02:33:52 +00:00
Owner
Copy Link

I don't think it's a wise limitation currently since most repositories are stored in Github. And for a decentralization objection, Github could still be one node on the network.

I don't think it's a wise limitation currently since most repositories are stored in Github. And for a decentralization objection, Github could still be one node on the network.
👍 1
justusbunsi commented 2022-05-22 03:54:39 +00:00
Member
Copy Link

I agree with lunny. Some projects can't move away from GitHub as they are part of a whole infrastructure running there. Thinking of the Jenkins plugin living inside jenkinsci organization. This might be the case for new items, too.

Maybe it could be a recommendation such as "Consider hosting the project on a Gitea instance" or something.

I agree with lunny. Some projects can't move away from GitHub as they are part of a whole infrastructure running there. Thinking of the Jenkins plugin living inside jenkinsci organization. This might be the case for new items, too. Maybe it could be a recommendation such as "Consider hosting the project on a Gitea instance" or something.
👍 2
Gusted commented 2022-05-22 08:44:51 +00:00
Author
Copy Link

I don't think it's a wise limitation currently since most repositories are stored in Github.

I'm not talking about current repositories, only for new ones.

And for a decentralization objection, Github could still be one node on the network.

Why choose Github over any public Gitea instance? Github has a history of blocking acccess. I don't think it's the best node what you can choose for decentralization.

I agree with lunny. Some projects can't move away from GitHub as they are part of a whole infrastructure running there. Thinking of the Jenkins plugin living inside jenkinsci organization. This might be the case for new items, too.

Yes exception has to be made, for certain items it makes sense that they still live on Github. But e.g. your small toy project can easily be hosted on a Gitea instance unless you need a CI(in which case you're restricted to use a instance with a CI).

Maybe it could be a recommendation such as "Consider hosting the project on a Gitea instance" or something.

I'm fine with that, that should hopefully do the job and let people consider using Gitea.

> I don't think it's a wise limitation currently since most repositories are stored in Github. I'm not talking about current repositories, only for new ones. > And for a decentralization objection, Github could still be one node on the network. Why choose Github over any public Gitea instance? Github has a [history](https://github.com/1995parham/github-do-not-ban-us) of [blocking acccess](https://en.wikipedia.org/wiki/Censorship_of_GitHub). I don't think it's the best node what you can choose for decentralization. > I agree with lunny. Some projects can't move away from GitHub as they are part of a whole infrastructure running there. Thinking of the Jenkins plugin living inside jenkinsci organization. This might be the case for new items, too. Yes exception _has_ to be made, for certain items it makes sense that they still live on Github. But e.g. your small toy project can easily be hosted on a Gitea instance unless you need a CI(in which case you're restricted to use a instance with a CI). > Maybe it could be a recommendation such as "Consider hosting the project on a Gitea instance" or something. I'm fine with that, that should hopefully do the job and let people consider using Gitea.
👍 5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/awesome-gitea#80
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?