see http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2019-August/002458.html gitea would be replacing the gitolite3 and bugzilla installations. gitea may replace the wiki as well. https://gitea.io/en-us/ https://docs.gitea.io/en-us/comparison/ migrating bugzilla to gitea: https://github.com/go-gitea/gitea/issues/7802 one other pain point is that git over ssh currently uses a port other than 22.
note that the github issue for bugzilla to gitea migration is only 4 days old, so if we have anything to add, now's the time.
Port 922 is deliberate, to stop automated script kiddie attacks and portscans.
(In reply to Luke Kenneth Casson Leighton from comment #2) > Port 922 is deliberate, to stop automated script kiddie attacks and > portscans. In my experience, fail2ban is sufficient to handle the script kiddie attacks (I used to have an ISP that didn't block incoming connections, which was nice for running servers). gitea even has a section of the documentation dedicated to fail2ban integration. if they can see that we're running ssh, I wouldn't call that much of a problem (as long as automatic updates are turned on), since we're not the only ones by far. If you're worried about them breaking passwords, the server can be set up to only allow authentication using ssh keys (which are generally more secure anyway, if protected on the client computer). gitea, i would assume, supports authentication using ssh keys, since everyone logs in using the "git" username.
i tried gitea on my home server, it took 85MB of disk space of which 84MB is the gitea executable. running it takes 100MB of ram.
According to their current plans, they will be self-hosted on gitea.com by september 14 as part of release 1.10.0 (see milestone on github). They have already moved everything but the gitea repo. When they finish moving, I would assume that their issue tracker would be on gitea.com since that's where the trackers are for for all their other repos.
(In reply to Jacob Lifshay from comment #4) > i tried gitea on my home server, it took 85MB of disk space of which 84MB is > the gitea executable. running it takes 100MB of ram. nice. that's tiny. that just leaves learning golang and having a full build environment installed as a prerequisite emergency measure, should there be any serious bugs that absolutely have to be fixed immediately, in the middle of the night.
Update: gitea have not yet moved to be completely self-hosted also, they're applying for nlnet grants: https://github.com/go-gitea/gitea/issues/16827