...
So, how do you pronounce Forgejo? Forge-Joe? Forjei-ho? Forjei-o?
They also have a recording posted: https://forgejo.org/static/forgejo.mp4
Also the pronunciation recording does not match how I would expect it to be spelled. Fordgeo is what I'm hearing
Just like .gif, yeah.
Their landing page has this to say:
> Forgejo is a self-hosted lightweight software forge.
This tells me basically nothing, at least nothing useful in terms of what they are offering.
>This tells me basically nothing, at least nothing useful in terms of what they are offering.
What else could they add to be clearer?
* Software forge
* Self hosted
* Lightweight
I find these terms to be clear.
I was wrong.
Golly, I learnt something!
Nobody knows how to pronounce gitea either. Half of people pronounce it "gi-te-ah".
On top of those, I've also heard the k at the end be replaced with h, which would also be correct, as per https://en.wikipedia.org/wiki/Chi_(letter)
The common pronunciation of latex /ˈleɪˌtɛks/ would be incorrect.
For Kubernetes, Wikipedia lists eight different pronunciations: /ˌk(j)uːbərˈnɛtɪs, -ˈneɪtɪs, -ˈneɪtiːz, -ˈnɛtiːz/, with the j after k being optional.
NGINX feels like the most straightforward out of these, even though it is rarely pronounced correctly.
As for myself, I like to call it NG Inks, as in next-gen tattoos, at least whenever I hear it pronounced wrong :)
I have a feeling that's not the best metric, but go off.
....
Yeah, everybody's gonna call it Forge Joe.
Which ones are compatible with GitHub actions? To me that is the most important aspect. So much is done with those and I really don't want to relearn.
https://docs.gitea.com/usage/actions/overview
Both have “Actions” that are act based and very similar to GitHub Actions and offers some compatibility.
https://forgejo.org/2023-02-27-forgejo-actions/
They make no guarantee of compatibility with Github Actions but they seem to be aiming for it based on the syntax.
That seems to be no longer the case?
>> Starting with Gitea 1.19, Gitea Actions are available as a built-in CI/CD solution. ... It is similar and compatible to GitHub Actions, and its name is inspired by it too.
https://docs.gitea.com/next/usage/actions/overview
Which seems to have been released almost a year ago