> we’re planning on establishing a fund to be able to provide support to contributors who not only contribute features, but also bug fixes, performance enhancements, and important refactors.
Sounds like any other for-profit company building commercial software. What stopped them from doing that while keeping the original OSS software copyrights intact?
Also curious to see their plan to pay out all the developers working on the OSS that underpins Gitea itself. The list is pretty long.
The GPL is not scary. It just provides you the means to enforce what everyone knows is basic decency in Free software: you get total control of the software, in return you release your changes, and provide your downstreams with the same freedom.
That's simply too much friction. There's a reason most projects that see commercial adoption and are AGPL (or SSPL) started out more permissive.
I have some vague notions for “community supported software”, where features and implementation priorities are driven by the community and not the enterprise. In order to give the developers a fair share, I was thinking of something similar to kickstarter rounds for feature sets, with a defined group of developers for that round.
I’m sure the practical reality is challenging. For example, that means doing fundraising and marketing regularly. There is also an opportunity cost — this is meant to serve the community, and it’s unlikely anyone will get FAANG level compensation for work on this.
But the original copyrights and license stay intact, not?
By the way, hard forking always gives a sense of confusion to me. Will both projects have a bright future ahead, or will one of them fall by the wayside. Sometimes it takes a few years to crystallize, like with ffmpeg/libav.
I do understand Codeberg has ambitions and a place in the FOSS ecosystem (that is why I moved to it), I just hope it all pans out and they don't bite off a bite that is too big. No idea about Gitea, as I wasn't directly involved. They seem to go somewhat towards a RedHat model, offering support for money. It might be that if Forgejo will really take off and builds a community, Gitea will base off of Forgejo in some future scenario.
Countless examples either way. It can lead to a "nodejs/iojs" situation where the fork happened because of disagreement, and the upstream project realizes their mistake and eventually integrates the fork into mainline development repository. That probably would count as a success for everyone.
Or it goes the way of webkit/blink, where both forks are successful in their own way, although the project they forked from (khtml), probably is considered less successful.
Either way, that it's even possible to fork and continue working on both I'd consider a success in it's own way. It's the beauty of FOSS.
Maybe the best fork win, and also the base it was forked from.
They will still benefit from upstream contributions.
It's not clear to me if they intend to further develop Gitea or work on the non open parts. Looking at the reactions and the announcement it looks like everyone assumes the latter.
I wonder why not both?
Currently (as I checked 30 seconds ago), downloading and installing is easy, but finding the small "Install" text on the bottom of the page is not. You need to further dig the docs to find the location of the source in the webpage, too.
Everybody assumes that Gitea took the first step towards this state, and they are right to assume that, because we have no other prominent examples.
And I tend to agree with them, too.
The only parts that would not be, would be anything that comes from a contract and doesn't make sense to contribute back. For example, if a company wants some bespoke functionality that doesn't make sense in the main repo.
Might just make this a long run goal - moving selfhosted gitlab over
The reason for the split was understandable, them going around proclaiming Gogs dead and unmaintained felt pretty scummy to me, however.
That makes the maintainer of Gogs sound rather petty, which I don't think is true. It is their project, they don't have to give control to anyone else if they don't want to, or implement features that they don't want.
A number of projects are explicitly “open source, not open contribution” and this is perfectly OK. If it is a problem for other individuals or “the community” than there is always the fork option (as taken by Gitea and now Forgejo) or if that isn't practical maybe offering to pay the maintainer, so can afford to make time to bother more with needs/wants away from their own (though in the latter case, don't be offended if this is politely rebuffed also).
I realize gogs is MIT license which is subject to easy fork. To avoid a fork when using such license, you have few options. One is fully feature your product, the other is expect your product to require domain specific skills that makes fork less trivial to move on; file format, data manipulation, etc.
So I wondered if original maintainer really wanted to avoid the fork, or simply don't care. It would be interesting to hear.
It would be nice to also disable the public listing of repositories for your profile page and to control it for organizations, too. (Not talking about private repos. Instead: these should be ordinary repos that remain accessible to anyone who has the link, but they are simply not aggregated into a single unified list that's available to anyone who clicks over to the "Repositories" tab. Think of them like unlisted YouTube videos, except they are all unlisted by default, rather than having to specifically designate each one as being unlisted—although that would work, too, it's just not the way it should be implemented.)
.. except from the owners of Github, and their paid clients ! you don't realize this?
But diacritic marks aren't optional in Esperanto, they change pronunciation and meaning. "Forgejo", which is pronounced with a hard "g" (IPA /g/), is a nonsense word which means something like "distant gay".
The correct transcription without diacritics would be "forghejo".
Also, missed opportunity, Codeberg folks. Why Not "Erika"? ;)
Oh jeez, will every marketing copy repeat this phrase forever now?
