ProseMirror's Migration to Forgejo

Announce
1

Hello ProseMirror community. I am in the process of moving as much of my code as is practical off GitHub and onto my own Forgejo instance at code.haverbeke.berlin. I’m looking into migrating ProseMirror soon, so this message is a heads-up about that and a call for feedback.

The plan is to create a prosemirror organization on that server and migrate the repositories over so that they keep the same structure, and then archive the GitHub repositories. That means link to issues or patches under github.com URLs will continue to work, but issues there cannot be further commented on. Issue numbers are retained by such a migration, so finding the matching issue on the new tracker is easy enough. If you have notifications turned on for an issue on GitHub, you won’t automatically be notified of activity in the corresponding Forgejo issue though, so you’d have to manually resubscribe to issues you want to follow.

My Forgejo instance allows logging in via GitHub Oauth2, which means it should be low-friction to log in and participate there.

I realize such a move can still be somewhat inconvenient for users in some cases, but I feel rather strongly about reducing my dependence on GitHub and big “free as in you have no recourse” platforms in general. Having a big part of my daily workflow tied up to a platform that continues to get slower and buggier, and could ban my account or change their terms on a whim, is something I’m motivated to avoid, even if there’s a cost to it.

In case you feel worried about the way that development happening on my server puts more power over the project in my hands, I can reassure you that the power over the project is already in my hands. I’ve realized that I work best as a solo maintainer, and that that’s okay. I’m happy to look at bug reports, I will listen to your feedback, and you are always free to fork if you really want to take the project in another direction, but this is not really a community project. So I don’t think anything really changes there. If we ever come to the point where this no longer works, we can look for a solution at that time.

I intend to start working on this in about two weeks. If you have any concern, tip, or other comment, let me know.

1 Like
3

Oh, that’s big news. Understandable and I’d say reasonable, given the circumstances. Is it possible though to keep a mirror to GitHub? Like Linux does? Just saying, incase your site goes down it’s no good either.

My biggest concern is just the UI. While GitHub might be buggy, it is still the gold standard for hosting git repositories. But Rome wasn’t built in a day and so on, so I expect it’ll get there eventually.

4

For the issue-less repositories (the core packages, which organize issues under prosemirror/prosemirror), it might be a good idea to, instead of archiving them, just disable pull requests and set them up as a mirror. For those with issues, I think the only way to preserve existing issues but disallowing new comments/issues is to archive a repository, so I guess those would have to become archives.

From what I’ve seen so far, the UI is fine. It’s a lot faster than GitHub, and has the features I use covered. And given that displaying comments on patches has been broken for several weeks in GitHub now, it feels like GitHub is regressing rather than improving, lately.

1 Like