I noticed instead of CodeFloe being a deployment of vanilla Forgejo, it’s a deployment of the code in the forgejo-codefloe repo. I’m just curious, is this considered a soft fork? Commits applied to this repo would be continually re-applied on top of each release of Forgejo as opposed to CodeFloe being based on a hard fork of Forgejo where they diverge over time?
Yes, technically it is a soft-fork but in the same way as Codeberg sees is → “Forgejo with modifications”.
These patches mainly relate to UI parts such as the footer, version display, icon sets, etc.
The core functionality is the same as vanilla FJ.
Though moving forward, CodeFloe might also include larger patches that relate to functional changes which were either not accepted in FJ or are “too experimental” (e.g. an early draft of a HA concept).
1 Like