Forgego, why not to collaborate with GitNext?

Looking at ForgeGo: a mobile client for Forgejo | devXY and I am slightly disappointed that you are not cooperating with GitNex for Forgejo and Gitea | F-Droid - Free and Open Source Android App Repository It seems like doing basically the same.

GitNex is a Android-only App. We ware of course aware of it when starting this project.
Our main goal was to offer an app for both Android and iOS.

Besides, one cannot simply “cooperate” with such a project. GitNex is hosted on Codeberg, it doesn’t accept AI contributions therefore (even though it seems likely that AI is being used when looking at commits such as this one), and has a predefined app style and approach. We wanted to have a different approach to it.

What disappoints you in particular? You are free to use GitNex if you like it more :slightly_smiling_face: . There’s just (yet) another option now which anyone can choose from.

OK, you have a point. So, the only problem I see that I cannot find ForgeGo in F-Droid. Will you add it there?

Unfortunately we can’t publish to FDroid as the app isn’t public right now and FDroid requires that.

Does this mean ForgeGo will eventually be open-sourced in the future?

We can’t say whether this will happen or not. During the development phase in early 2026, there hasn’t been any Forgejo mobile app for both iOS and Android and we wanted to avoid somebody stealing the source code before the app was published and announced.

If we would do so, we will likely need to split the app to avoid somebody forking it and simply removing the licensed parts out of it to publish it under a new name. While a license can try to protect from this, it doesn’t give a guaranteed protection in practice. (And surely we could go for legal steps in this case but we’d also rather save this time and effort for cooler things).

Once other apps exists and the ecosystem has become more diverse, all of this becomes less of a concern.

??? Hypocrisy? Have you noticed that whole Forgejo is just a “stolen” code from Gitea, and both of them are FLOS software?

@mcepl Please be a bit cautious with your wording.

Forgejo didn’t “steal” anything, they just did a normal fork under the active license. Nobody stole anything from anyone.
Otherwise the fork we use for CodeFloe as a platform would also be “stolen”. Re-using code from others under permitted licenses is just fine and forever will be.

The case of ForgeGo described here is something entirely different. It is (yet) a private and unique codebase including features that aren’t present anywhere else. Even with an appropriate license in place, the risk of someone soft-copying code is at an all time high right now. One can essentially say: “look at this codebase and build me an app with all the ideas and behaviour of that repo” to an agent and copying code 1:1 wouldn’t even be necessary.

This applies especially to the features which belong to the subscription tier within ForgeGo.
CodeFloe can be used with any other mobile app just fine - or alternatively just in the browser, as all the years before. It provides added value already in the free tier. If one doesn’t like it or trust it, there isn’t any pressure at all in using it.

My use of that word was just a reaction on your first use of it. Of course, I have put the word into quotes to make it clear that I don’t mean it literally. Yes, of course, you have your legal right to cover your project with proprietary (or even only-for-paying-customers) tools, and nobody can sue you. As a former lawyer (with former specialisation in computer copyrights) I know that very certainly. That doesn’t make such action any less hypocritical, when you are building this whole project on FLOSS (and I have my huge doubts about morality of forking Forgejo from Gitea, but that’s certainly not your problem).

Rest probably doesn’t make much sense to even write down, so I won’t waste ours time.

Be well!