1949
submitted 11 months ago by TxzK@lemmy.zip to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] perishthethought@lemm.ee 58 points 11 months ago
[-] Pyroglyph@lemmy.world 18 points 11 months ago

I want to like Forgejo but the name is really terrible.

Is it "forj-joe"? Nah, that double-J sound is way too awkward.
Do you then merge the J sounds to make "forjo"? If so, why not just call it that?
Is it maybe "for-geh-joe"? That seems the most likely to me, but then that ignores the "build < forge" marketing on their website.

I know it's pretty inconsequential, but it feels weird using a tool that you don't even know how to pronounce the name of.

[-] rvgamer06@leminal.space 18 points 11 months ago

There is an official pronounce on the site. It comes from Esperanto anyway.

[-] jaybone@lemmy.world 9 points 11 months ago

Of course, the international non-ambiguous language.

[-] Deckweiss@lemmy.world 7 points 11 months ago

You mean lojban or toki-pona?

[-] tslnox@reddthat.com 2 points 11 months ago

Bonvolu alsendi la pordiston? Lausajne estas rano en mia bideo!

[-] kurcatovium@lemm.ee 2 points 11 months ago

Love me some Red Dwarf!

[-] Nelots@lemm.ee 13 points 11 months ago* (last edited 11 months ago)

Yeah, like the other person mentioned, the origins of the word and its pronunciation are the very first thing in the FAQ on their website. It's pronounced more like for-jey-oh.

[-] nilloc@discuss.tchncs.de 2 points 11 months ago

Thanks! That’s how I read it as a joke, but why not?

For yay ho would be too much though.

[-] TxzK@lemmy.zip 16 points 11 months ago

Yeah Fogejo is amazing. Moved all my personal projects from GitLab to Codeberg recently. Wish I knew about it sooner

[-] jerrythegenius@lemmy.world 13 points 11 months ago
[-] Deckweiss@lemmy.world 18 points 11 months ago

afaik it got bought by some company and people fear that there will be anti-user changes like with all the other open source projects that were bought by a company in recent years.

[-] lastweakness@lemmy.world 10 points 11 months ago

No company has bought gitea. They just made a commercial entity which can accept contracts for enterprise installations and make some hyper specific customisations not needed for normal users (like some specific mode of internal authentication) in those installations. So far Gitea has been great still.

[-] moonpiedumplings@programming.dev 2 points 10 months ago

The security implications on this page concern me: https://forgejo.org/compare/#better-security

[-] QuazarOmega@lemy.lol 11 points 11 months ago

Gitea is still maintained though?

[-] GammaGames@beehaw.org 12 points 11 months ago

They got bought so people jumped ship, I haven’t heard anything bad personally

[-] QuazarOmega@lemy.lol 5 points 11 months ago

Yes as you say, I think they're still pretty fine, though I do prefer Codeberg as a hosted solution myself and in turn Forgejo, especially for their federation plans

[-] GammaGames@beehaw.org 2 points 11 months ago* (last edited 11 months ago)

Gitea has federation plans too though?

Edit: and apparently had them as far back as January 2022

[-] QuazarOmega@lemy.lol 1 points 11 months ago

Oh, I wasn't updated on that, I honestly don't know which came first

[-] GammaGames@beehaw.org 2 points 11 months ago* (last edited 11 months ago)

Looking at the forgejo issue, the dev working on the federation tools for gitea had worked for 6 months (gitea issue opened Jan 2022) before opening the issue Nov 2022 with the initial goal being to merge into forgejo and then merge that upstream with gitea

[-] PlexSheep@feddit.de 9 points 11 months ago

Is that really the case? I selfhost gitea and am pretty happy with it.

[-] dukk@programming.dev 14 points 11 months ago

They’re both pretty on par for the most part. If it’s too much of a hassle, there’s no real need to switch.

Now that Gitea is owned by a for-profit company, people are afraid that they’ll be making anti-user changes. This, Forgejo was born. It pulls from Gitea weekly, so it’s not missing anything. It’s also got some of its own features on top, but they’re currently pretty minor. Also, most of the features end up getting backported back to Gitea, so they’re mostly on par with each other. However, many features find themselves in Forgejo first, as they don’t have the copyright assignment for code that Gitea does. Additionally, security vulnerabilities tend to get fixed faster on Forgejo. They are working on federation plans, however, so we’ll see how that pans out.

Overall, there’s no downside of switching to Forgejo, and you’ll probably be protected if Gitea Ltd. makes some stupid decisions in the future. However, at the moment, there’s no immediate advantage to switching, so you can stick with Gitea if you’d like.

[-] PlexSheep@feddit.de 1 points 11 months ago

I thought gitea was doing federation too? Im pretty excited about that part, as I've wanted to move away from GitHub but the visibility it gives is just on another level. Users can't register on my instance, therefore they also can't open issues and PRs.

Is switching to forgejo more work than just changing my compose file a little? I hope my database can get transferred.

this post was submitted on 30 Jan 2024
1949 points (100.0% liked)

Programmer Humor

32742 readers
618 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS