Gitea hosted Gitea

[lunny]

For the first big stage, we would like Gitea's development could be based on a Gitea hosted and github will only a mirror. This will maybe completed in v1.x. So that this issue will list all the features needed to be implemented before v1.x. And of course please discuss them and change my post.

• Squash merge (Pull request merge strategy #712 Add Pull Request merge options - Ignore white-space for conflict checking, Rebase, Squash merge #3188)
• Complete Protected branch (Protected branches system #32 Protected branches system #339)
• Complete API support ([Meta] Improvements to the API #64)
• API Documents (API documentation for endpoint #194)
• Webhooks implementation (Webhooks implementation #2418)
• Better CI Integration ( (PR Status-API #1332)) Drone PR: (OS thread limit reached while compiling from source #2017)
• Comment on commit and PR (Commits and pull files #124 Comments on pull files #2583 Pull request review/approval and comment on code #3748 )
• Approvals system (Permissions to accept/merge Pull request #2794 Pull request review/approval and comment on code #3748 )
• Approvals limitations (Pull requests approvals limitations #5251)
• Migrate a throughout github repository to gitea (Improve migrations to support migrating milestones/labels/issues/comments/pullrequests #6290, Proposal: Store original author in database for use with migrated content #7293, Move migrating repository from frontend to backend #6200, Change ownership of issues/comments/PR from Github user to Gitea user after migration #7410)
• Dump/restore github/gitlab repository data to a local directory and restore to gitea Dump github/gitlab/gitea repository data to a local directory and restore to gitea #12244

Migrating Progress Updated:

• migrate gitea repository -> https://gitea.com/gitea/gitea blocked by Add support to import repository data from an exported data of Github #18165
• migrate go-sdk repository -> https://gitea.com/gitea/go-sdk
• migrate git repository -> https://gitea.com/gitea/git
• migrate tea repository -> https://gitea.com/gitea/tea
• migrate website repository -> https://gitea.com/gitea/website
• migrate blog repository -> https://gitea.com/gitea/blog
• migrate theme repository -> https://gitea.com/gitea/theme
• migrate redirects repository -> https://gitea.com/gitea/redirects
• migrate homebrew-gitea repository -> https://gitea.com/gitea/homebrew-gitea

[Lourens-Rich]

Very good idea!

[bkcsoft]

1.2 in February, 1.3 in April, 1.4 in June, 1.5 in August? should be enough time to implement all that 😄

[zellyn]

If you haven't seen it, fantastic and insightful comment supporting your approach to self-hosting only when ready: https://lobste.rs/s/gokjbo/gitea_1_1_0_released/comments/dg9pwe#c_dg9pwe

[bkcsoft]

@lunny Now that I think about it (thanks @zellyn for that link 😂 ) Why do we need oauth-provider, complete webhook support, api-documentation, and a complete API for self-hosting?

OAuth Consumer is required (it's merged AFAIK) so people can login using github auth.
Drone only uses push hooks, so why would we need the other?

As for API, not sure why self-hosting requires that at all TBH :)

[strk]

I agree about trimming that list. Earlier self-hosting will very likely help us setting priorities better :)

[lunny]

@bkcsoft maybe we can setup a hosted site and have a try.

[lunny]

@bkcsoft I updated the issue, do you mean that?

[ekozan]

-> OAuth provider (#27) is not closed

[bkcsoft]

@ekozan not closed, but scratched from the list of "things we need"

[bkcsoft]

Added "Repository Size Limits" since we don't have unlimited storage on the servers...

My proposal for limits:

• 0 Orgs
• 3 Repos
• 1GB/repo

[lunny]

@bkcsoft Did you mean it will be a public service for anyone?

[bkcsoft]

Maybe, maybe not, but if it becomes a public service we can't have it unlimited ;)