17 ms·

Codeberg launches Forgejo – Gitea fork

158 points by rubenv 4y ago

rapnie 4y ago
It is great that Codeberg has taken custody of the Forgejo project, and will use it for their own services. Not only is Forgejo using exclusively FOSS tools now, maybe the additional services that Codeberg offers, like Codeberg Pages, Codeberg CI (based on Woodpecker, FOSS Drone.io alternative) and Translations (based on Weblate) will become very easy integrations to any Forgejo installation.
- Havoc 4y ago
  Thanks for pointing out the CI one. Might just make this a long run goal - moving selfhosted gitlab over
  - jacooper 4y ago
    Woodpecker / drone is still not on the same level as Gitlab CI
    - TheChaplain 4y ago
      Woodpecker can't even build with non-root images, so it's pretty far off. :(
    - Havoc 4y ago
      Anything in particular that you feel is missing? My CI needs are fairly modest (homelab so nothing super advanced)
      - jacooper 4y ago
        Multi arch builds, triggers based on environment variables.
shp0ngle 4y ago
Well gitea itself is a fork of a different project, because of some other founder drama (that I forgot honestly). So it’s fine.
- ofrzeta 4y ago
  There was no drama as far as I recall, just complaints that he wasn't agile enough or something like that. The different project is Gogs https://gogs.io/ https://gogs.io/ and its author is Joe Chen ('unknwon').
  - 411111111111111 4y ago
    From what I recall the drama was that the split was timed to his absence and they announced everywhere that "Gogs is dead/unmaintained" until he came back and set the record straight. The reason for the split was understandable, them going around proclaiming Gogs dead and unmaintained felt pretty scummy to me, however.
- sofixa 4y ago
  The drama was that the original project's maintainer had full control and would go absent for weeks/months leaving the project in limbo, and refused to share the maintainer burden with anyone (including refusing features he disliked).
  - Narann 4y ago
    > and refused to share the maintainer burden with anyone (including refusing features he disliked). 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.
  - dspillett 4y ago
    > refused to share … (including refusing features he disliked) 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).
smcl 4y ago
For anyone else who, like me, couldn't decide which pronunciation it was the FAQ says "(pronounced /forˈd͡ʒe.jo/)". I don't know IPA so I can't tell if that j in ".jo" is like "joker" or like the french "jambon" or if it's soft like "yo"
- xigoi 4y ago
  From the IPA, it's soft like “yo”. (And the “e” is not silent, so the word has three syllables.)
  - wink 4y ago
    As a German proficient in English that name just makes my head hurt, no matter how the real pronunciation is. Maybe I'll go with a combination of Jorge and rojo (in Spanish) out of spite... Also, missed opportunity, Codeberg folks. Why Not "Erika"? ;)
    - mhd 4y ago
      > Also, missed opportunity, Codeberg folks. Why Not "Erika"? ;) Oh wow, that's a deep cut. I'm deeply impressed and amused. Almost to the point of yodeling ;) (For those lucky enough not to be this old and/or German, there once were two sisters called "Gitti & Erika" who made some horrible, yet famous Schlager songs – folksy chansons. Including the title melody of the local dub of the "Heidi" anime, triggering basically every "80s/90s kid".)
      - xdennis 4y ago
        Isn't Erika a nazi song about flowers, bees, and maidens?
        mhd 4y ago
        I think it's male name -> female name -> flower named after that -> song named after that. I honestly doubt that that's the first thing that comes to mind and thus would besmirch the good name of, erm, git. ;) (Not that I'm suggesting actually naming something after a boomer-level German in-joke in the first place.)
ricardobeat 4y ago
Background story seems to be that a portion of Gitea maintainers formed a for-profit company, and transferred all the trademarks to it, going against former promises made, and blowing up their own community as a consequence. They go over the now-traditional "companies are using our free software without paying us" discourse here: https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-of-gitea/ https://blog.gitea.io/2022/10/open-source-sustainment-and-th... > 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.
- mpol 4y ago
  > What stopped them from doing that while keeping the original OSS software copyrights intact? 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.
  - capableweb 4y ago
    > 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. 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.
pwdisswordfish0 4y ago
It took a long time, but GitHub has finally (thankfully) shipped privacy settings that allow you to disable the way it broadcasts/publicizes your every move on your profile page. Does Codeberg or Gitea allow this yet? (They really should have been the first to do so...) 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.)
- capableweb 4y ago
  Codeberg is not for private code, it's explicitly for "Free and Open Source Software". Probably it would still make sense to have some privacy for authors/contributors, so you can't simply list all activity by going to someones profile on the website, but the repositories should still be findable, browsable and public, as that's the goal of repositories in the organization Codeberg e.V.
  - pwdisswordfish0 4y ago
    - capableweb 4y ago
      - pwdisswordfish0 4y ago
        Two questions: 1. What can you point to that explains or even suggests that repos "should [...] be findable" directly on codeberg.org and for "people browsing [it] and pages within"? E.g. that creating an unlisted repo and then setting up a publicly facing project landing page/mailing list/etc. that independently refers potential contributors to the repo but doesn't make available a top-level index of all such (possibly unrelated) repos that a given person controls, is something that would run afoul of either Codeberg's policies or goals. 2. What is your relationship to the Codeberg e.V. organization?
alrs 4y ago
As an occasional gitea contributor: irc > matrix
aliqot 4y ago
Change the name.
XiraceFulufuke 4y ago
Kinrany 4y ago
> Take back control Oh jeez, will every marketing copy repeat this phrase forever now?
- albert180 4y ago
  Codeberg isn't a marketing company. It isn't even a company
nektro 4y ago
thinking i'm going to forgo this

158 points by rubenv 4y ago

It is great that Codeberg has taken custody of the Forgejo project, and will use it for their own services. Not only is Forgejo using exclusively FOSS tools now, maybe the additional services that Codeberg offers, like Codeberg Pages, Codeberg CI (based on Woodpecker, FOSS Drone.io alternative) and Translations (based on Weblate) will become very easy integrations to any Forgejo installation.

Havoc 4y ago
Thanks for pointing out the CI one. Might just make this a long run goal - moving selfhosted gitlab over
- jacooper 4y ago
  Woodpecker / drone is still not on the same level as Gitlab CI
  - TheChaplain 4y ago
    Woodpecker can't even build with non-root images, so it's pretty far off. :(
  - Havoc 4y ago
    Anything in particular that you feel is missing? My CI needs are fairly modest (homelab so nothing super advanced)
    - jacooper 4y ago
      Multi arch builds, triggers based on environment variables.

shp0ngle 4y ago

Well gitea itself is a fork of a different project, because of some other founder drama (that I forgot honestly). So it’s fine.

ofrzeta 4y ago
There was no drama as far as I recall, just complaints that he wasn't agile enough or something like that. The different project is Gogs https://gogs.io/ https://gogs.io/ and its author is Joe Chen ('unknwon').
- 411111111111111 4y ago
  From what I recall the drama was that the split was timed to his absence and they announced everywhere that "Gogs is dead/unmaintained" until he came back and set the record straight. The reason for the split was understandable, them going around proclaiming Gogs dead and unmaintained felt pretty scummy to me, however.
sofixa 4y ago
The drama was that the original project's maintainer had full control and would go absent for weeks/months leaving the project in limbo, and refused to share the maintainer burden with anyone (including refusing features he disliked).
- Narann 4y ago
  > and refused to share the maintainer burden with anyone (including refusing features he disliked). 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.
- dspillett 4y ago
  > refused to share … (including refusing features he disliked) 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).

smcl 4y ago

For anyone else who, like me, couldn't decide which pronunciation it was the FAQ says "(pronounced /forˈd͡ʒe.jo/)". I don't know IPA so I can't tell if that j in ".jo" is like "joker" or like the french "jambon" or if it's soft like "yo"

xigoi 4y ago
From the IPA, it's soft like “yo”. (And the “e” is not silent, so the word has three syllables.)
- wink 4y ago
  As a German proficient in English that name just makes my head hurt, no matter how the real pronunciation is. Maybe I'll go with a combination of Jorge and rojo (in Spanish) out of spite... Also, missed opportunity, Codeberg folks. Why Not "Erika"? ;)
  - mhd 4y ago
    > Also, missed opportunity, Codeberg folks. Why Not "Erika"? ;) Oh wow, that's a deep cut. I'm deeply impressed and amused. Almost to the point of yodeling ;) (For those lucky enough not to be this old and/or German, there once were two sisters called "Gitti & Erika" who made some horrible, yet famous Schlager songs – folksy chansons. Including the title melody of the local dub of the "Heidi" anime, triggering basically every "80s/90s kid".)
    - xdennis 4y ago
      Isn't Erika a nazi song about flowers, bees, and maidens?
      - mhd 4y ago
        I think it's male name -> female name -> flower named after that -> song named after that. I honestly doubt that that's the first thing that comes to mind and thus would besmirch the good name of, erm, git. ;) (Not that I'm suggesting actually naming something after a boomer-level German in-joke in the first place.)

ricardobeat 4y ago

Background story seems to be that a portion of Gitea maintainers formed a for-profit company, and transferred all the trademarks to it, going against former promises made, and blowing up their own community as a consequence. They go over the now-traditional "companies are using our free software without paying us" discourse here: https://blog.gitea.io/2022/10/open-source-sustainment-and-the-future-of-gitea/ https://blog.gitea.io/2022/10/open-source-sustainment-and-th... > 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.

mpol 4y ago
> What stopped them from doing that while keeping the original OSS software copyrights intact? 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.
- capableweb 4y ago
  > 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. 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.

pwdisswordfish0 4y ago

It took a long time, but GitHub has finally (thankfully) shipped privacy settings that allow you to disable the way it broadcasts/publicizes your every move on your profile page. Does Codeberg or Gitea allow this yet? (They really should have been the first to do so...) 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.)

capableweb 4y ago
Codeberg is not for private code, it's explicitly for "Free and Open Source Software". Probably it would still make sense to have some privacy for authors/contributors, so you can't simply list all activity by going to someones profile on the website, but the repositories should still be findable, browsable and public, as that's the goal of repositories in the organization Codeberg e.V.
- pwdisswordfish0 4y ago
  - capableweb 4y ago
    - pwdisswordfish0 4y ago
      Two questions: 1. What can you point to that explains or even suggests that repos "should [...] be findable" directly on codeberg.org and for "people browsing [it] and pages within"? E.g. that creating an unlisted repo and then setting up a publicly facing project landing page/mailing list/etc. that independently refers potential contributors to the repo but doesn't make available a top-level index of all such (possibly unrelated) repos that a given person controls, is something that would run afoul of either Codeberg's policies or goals. 2. What is your relationship to the Codeberg e.V. organization?

alrs 4y ago

As an occasional gitea contributor: irc > matrix

aliqot 4y ago

Change the name.

XiraceFulufuke 4y ago

Kinrany 4y ago

> Take back control Oh jeez, will every marketing copy repeat this phrase forever now?

albert180 4y ago
Codeberg isn't a marketing company. It isn't even a company

nektro 4y ago

thinking i'm going to forgo this