11–20 of 44 posts
Does any commit to forgejo benefit gitea ltd also? What about other way around (while gitea is still opensource - is it, btw?) Or how does a soft fork work?
As far as I know they intend to upstream patches they make as well.
And yes, Gitea is still open source and MIT licensed.
As someone who hasn't been following this: what's the split look like between Forgejo and Gitea for where the contributors are going? Is is mostly going to Forgejo (other than Gitea Inc employees obviously), mostly staying with Gitea, a mix?
As a quick bias note, I am a Gitea maintainer, but a majority of frequent maintainers appear to be staying with Gitea so far. That being said, Forgejo is a soft fork, so they will still benefit from those contributions.
Forgejo was officially launched yesterday...
Also what's a "frequent maintainer"?
How do you pronounce this? Forge Joe? Forego? Forgeaux?
Earlier quoted context omitted.
As a quick bias note, I am a Gitea maintainer, but a majority of frequent maintainers appear to be staying with Gitea so far. That being said, Forgejo is a soft fork, so they will still benefit from those contributions.
> a majority of frequent maintainers appear to be staying with Gitea Forgejo was officially launched yesterday ... Also what's a "frequent maintainer"?
I have no real description for a "frequent maintainer", so maybe my wording was incorrect there.
I simply meant someone who contributes to the project often, but I don't have a concrete description for you considering "often" could also be subjective.
As someone who hasn't been following this: what's the split look like between Forgejo and Gitea for where the contributors are going? Is is mostly going to Forgejo (other than Gitea Inc employees obviously), mostly staying with Gitea, a mix?
Earlier quoted context omitted.
> a majority of frequent maintainers appear to be staying with Gitea Forgejo was officially launched yesterday ... Also what's a "frequent maintainer"?
Yes, but the soft fork discussions began a few days after the first blog post. I have no real description for a "frequent maintainer", so maybe my wording was incorrect there. I simply meant someone who contributes to the project often, but I don't have a concrete description for you considering "often" could also be subjective.
A frequent contributor then?
"Maintainer" usually implies some sort of admin rights, e.g. the people merging in the contributions.
Earlier quoted context omitted.
Yes, but the soft fork discussions began a few days after the first blog post. I have no real description for a "frequent maintainer", so maybe my wording was incorrect there. I simply meant someone who contributes to the project often, but I don't have a concrete description for you considering "often" could also be subjective.
> someone who contributes to the project often A frequent contributor then? "Maintainer" usually implies some sort of admin rights, e.g. the people merging in the contributions.
Yes, frequent contributors.
Earlier quoted context omitted.
The article provides an mp4 that answers this question: https://forgejo.org/static/forgejo.mp4
No way anyone will pronounce it that way.
So I just invalidated your argument, lol.