Do you mean git hosting in Peergos? Bare bones hosting (literally syncing a git repo to peergos, and sharing the repo normally) can be done now using the sync client and a local dir. But this is probably more appropriate for private repos.
Well one of the reasons we stayed on Github so far is that most of our discussions took place there. Now we moved the discussions to the forum, this point has become a lot less important. The biggest boon of being on github right now is the simple fact that almost everyone has a github account and with that can easily contribute by leavung feedbacknon our open PR’s.
4 Likes
How often to external people contribute to the repo? If it’s not that often, it’s likely not a strong enough point.
Quite often
2 Likes
I’ve never set anything like this up for git but for streaming ingestion we have the active-active architecture where you can commit to either repo but one generally acts as the default.
I wonder if any ops folks (true or honorary) here have rigged anything like that up for git.
I imagine most people contributing outside of the PG team regularly wouldn’t mind setting up on codeberg or one hosted on the neat servers and then simply have github mirror it for the tail end of one off contributions from github to sync to the other.
I think in the rare event there’s a collision it wouldn’t be too hard to resolve.
We can accept code sent to any of our mirrors already. I would just download their contribution and upload it to a GitHub PR myself in this case. It is just harder because we then can’t easily communicate back and forth with the author, since GitHub is the discussion platform for contributions. It’s fine for one-off edits though.
I am not too worried about this because Forgejo (and Gitea) can make perfect GitHub clones including non-Git things like Issue and PR discussions, so whenever we want to we can switch to Forgejo and not lose any history.
We do have very many one-off or infrequent contributors though who I am not convinced would sign up for another account just to edit Privacy Guides. When federation arrives I will feel more comfortable telling them to sign up for a Codeberg or other federated instance account, because at least they’ll be able to use it for other stuff too. I think we’ll probably still lose contributors but the benefits of a decentralized ecosystem will make up for it in this case.
To be honest we also make pretty substantial use of GitHub’s free compute (like you’d probably be surprised lol). When the time comes I’ll be fine switching to self-hosted Forgejo Action runners, but that will be missed.
3 Likes
Jonah spoiling the overengineering party 
jfyi
Thank you. I was scared the project was over as I recently read they weren’t financially sustainable.
Edited the title to not scare people.
1 Like
How can you change the title of the thread I opened?
1 Like
Update: According to this it looks like Organic Maps is migrating to Codeberg. And it seems like there will be a post-mortem, nothing from the side of GitHub yet.
4 Likes
They said it was actually a legal issue and not to blame Github aa it wasn’t their fault.
The migration is complete:
9 Likes
Actually really impressive! Glad they are selfhosting their repo using Forgejo.
People who installed it using Obtainium will need to change their config, however. The Obtainium instructions link in the repo still points to GitHub (and to the now non-existent wiki), but it should probably be fixed eventually. Unfortunately, some people may not even notice this change and just stop getting updates altogether, but on every other store it should be transparent.
Good decision overall, considering the circumstances they found themselves in.
I didn’t find any release in the new Forgejo repo, how did you change your Obtanium config?
I installed it through Accrescent, but since the repo itself changed I assume they’ll start releasing in the new one soon and you’ll just need to put the new repository in your config once that happens. Otherwise, they’ll probably share new instructions.
I mostly gave the warning as something to keep in mind for future releases, if you use Obtainium.
EDIT: They do have the releases in the new repo. I have just tested and if you use this link in your Obtainium config, it should fetch the latest release!
1 Like