On Sat, Jan 11, 2025 at 10:06 PM Gregory Nutt <spudan...@gmail.com> wrote:
> > On 1/11/2025 6:00 PM, Tomek CEDRO wrote: > > On Sat, Jan 11, 2025 at 11:02 PM Lee, Lup Yuen <lu...@appkaki.com> > wrote: > >> What is Forgejo? Think GitHub… But Open-Source and Self-Hosted! Forgejo > is a Git Forge, the server code that will publicly host and share a Git > Repo. (Including our NuttX Repo) > >> > >> In this article, we talk about Forgejo Git Forge, and whether NuttX > could possibly switch from GitHub to a self-hosted Git Forge... > >> > >> (1) If GitHub Breaks: What’s our Contingency Plan? > >> > >> (2) GitHub is Blocked in some parts of the world… > >> > >> (3) Can we Mirror our NuttX Repo outside GitHub? So NuttX Community > becomes more inclusive? > >> > >> (4) Also: We’re outgrowing our Budget Limits at GitHub, might need to > move out > >> > >> Check out the article: https://lupyuen.org/articles/forgejo.html > > Thank you Lup :-) Do you know how does Forgejo compare to GitLab? :-) > > I am not sure how much wiggle room we have in this matter. Remember that > the software belongs to the Apache Software Foundation and not us. We > would need to ask, but I suspect that the ASF would object to hosting > the master version of their software outside the Apache repositories. > > By the way, there are two Apache GIT repositories: Github and GitBox. > They mutually synch with each other periodically. I don't understand > all of this. I suggest anyone interested review documents on Apache.org > regarding repository usage. Then discussing this with Infra. As I understand it, our official repositories are actually the ASF-hosted GitBox on ASF-controlled hardware, and GitHub is actually a mirror. Both mutually sync to each other so if a committer would commit any changes to the GitBox repository it would immediately show up at the GitHub repository. In practice we haven't used this, so it's easy to forget that GitBox exists and to think that GitHub is the official one. Nothing stops anyone from creating their own mirrors of the repositories (though any other mirror would not have the same kind of two-way synchronization as our GitBox <-> GitHub). Here's one related document: > > Project Code Repository Policy: > https://infra.apache.org/project-repo-policy.html > > I think we would need to have some discussions with members of the board > and/or with infra. I don't see any issue with maintaining a mirror of > Apache NuttX, but getting things back to the Apache master or GitBox > could be a pain. IIRC when we joined the incubator we discussed the question of how to handle contributions from anyone who can't or won't access GitHub and one possibility that was discussed was that they could always send a [PATCH] to the mailing list and we could either review it by email and commit it directly or convert it into a GitHub PR if we want to maintain a consistent process. Nathan
