6 ms·

There’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/ https://forgejo.org/

by mikl 1y ago

techknowlogick 1y ago
The Gitea project is still community-driven and has the same yearly elections for leadership that has been around for close to a decade now :) edit: Gitea is fully MIT and per our governance charter that cannot change
- tgmatt 1y ago
  This is nice in theory, but what happens when a community member wants to implement SAML for the community edition, or other premium features?
  - gchamonlive 1y ago
    Is MIT license and SSO features mutually exclusive? Or is it just a business model to sweep such features under a paid subscription?
    - tough 1y ago
      has nothing to do with licensing and ´everything to do with business model
    - techknowlogick 1y ago
      I'm not sure what you mean, as Gitea has SSO using many different ways, such as LDAP, OAuth2/OIDC, OpenID, SMTP, and more.
      - gchamonlive 1y ago
        I was responding to: > what happens when a community member wants to implement SAML for the community edition It's surely just business model, but I was intrigued and thought that maybe there were some kind of incompatible licensing in popular libraries people use for these so-called "premium features"
        techknowlogick 1y ago
        Gitea would have SAML too (I'm the main author on the SAML PR to the Gitea project), but it's been held up by community reviews requiring esentially an entire re-write with another library. We'd love some help to get it across the finish line :) In open-source, money isn't the only thing that can be spent; we can also use our time.
  - mappu 1y ago
    The SAML support in https://github.com/go-gitea/gitea/pull/29403 https://github.com/go-gitea/gitea/pull/29403 seems like it will get merged once the MR is a little bit higher quality. EDIT (bit better source): > Gitea Enterprise is an offering of CommitGo, not the Technical Oversight Committee of Gitea or the Gitea project itself. CommitGo remains committed to contributing back functionality to Gitea under the MIT license. Via https://blog.gitea.com/gitea-enterprise/#faq https://blog.gitea.com/gitea-enterprise/#faq
    - techknowlogick 1y ago
      Yup, this is the case. I'm the main author on that PR. It sadly stalled due to reviews from other maintainers requiring it to be rewritten using another library, but hopefully I'll be able to get back to it, or someone else will be able to pick it up. We've been able to get other functionality into Gitea already, and I've personally funded maintainers and others' work for the project, which goes directly into the project itself.
  - techknowlogick 1y ago
    I'm the main author of the PR to implement SAML in Gitea, and it sadly has stalled due to reviews from maintainers requiring it to be rewritten entirely using another library. Our governance charter requires a certain process for PRs going into Gitea, and cannot be side-stepped by anyone. As for some of the others, we've been able to merge them in already.
    - tgmatt 1y ago
      SAML was just an example - I didn't see the PR before I made that post. That said, it feels fundamentally incompatible to a business strategy where your community edition is able to offer all of the features of the premium offering. I just can't see how that business would be able to survive if they allow that to happen. I'm always dubious of freemium software, because the free version is always gimped in some way, be it SSO compatibility (OK, yours supports OIDC it seems so that's not _terrible_), role-based access controls, high availability, etc. I will concede that businesses probably _should_ be paying for good software that is critical to their business to help support the vendors, but given how important cost savings are to companies these days, one can hardly blame engineers looking for cheaper offerings.
      - TheNewsIsHere 1y ago
        I agree with your last point, but as someone who co-owns a technology business that doesn’t have an “Enterprise” sized bank account, I still have all of those needs. The SSO tax in particular is ridiculous. Functionality like HA or SSO being gated behind enterprise licenses only makes it harder for smaller businesses to “get there”. My business is comprised exclusively of technology professionals. We tend to be really cheap customers to have because we typically only raise a ticket when something beyond our responsibility breaks. And from the community side — I already have enough credentials to maintain in my personal life. It’s annoying when you can’t use SSO with a community edition product. I like having SSO at home. It makes life so much better, and it also makes me more likely to use a product in my business, which makes it more likely I’ll buy a license to backstop support.
        1y ago
- adduc 1y ago
  > The Gitea project is still community-driven and has the same yearly elections for leadership that has been around for close to a decade now :) [1] mentions changes to the election process that mandates half of the oversight committee to be appointed by the Gitea company. Doesn't that conflict with your assertion that the "same yearly elections" have been around? Where can one find the governance charter for the Gitea project? [1]: https://blog.gitea.com/quarterly-23q1/ https://blog.gitea.com/quarterly-23q1/
TheNewsIsHere 1y ago
I love Forgejo. I recently started a project to exit my business (and eventually personal) git from Github. Gitea was my target having ruled out GitLab based on prior experience administering an instance, but I ended up going with a Forgejo and I am glad I did. The Gitea shenanigans around the for-profit entity and its opaque ownership structure were mainly what left a bad taste in my mouth, but there were a few other more minor factors that were use case specific. Fedora recently decided to switch to Forgejo, which is quite a feather in their cap. I also was somewhat skeptical that a git hosting platform that had a business behind it with enterprise oriented offerings wasn’t yet self-hosting in the technical sense.
- kstrauser 1y ago
  Same here. Forgejo is amazing and their development velocity is soaring. And https://codeberg.org https://codeberg.org is a great host for FOSS projects, in a way I wished Sourcehut would've been except that it leaned hard into some (to me) strange workflow choices. I'm glad I made the switch.
esafak 1y ago
Where are the screenshots?!

There’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/ https://forgejo.org/

by mikl 1y ago

There’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/ https://forgejo.org/

techknowlogick 1y ago

The Gitea project is still community-driven and has the same yearly elections for leadership that has been around for close to a decade now :) edit: Gitea is fully MIT and per our governance charter that cannot change

tgmatt 1y ago
This is nice in theory, but what happens when a community member wants to implement SAML for the community edition, or other premium features?
- gchamonlive 1y ago
  Is MIT license and SSO features mutually exclusive? Or is it just a business model to sweep such features under a paid subscription?
  - tough 1y ago
    has nothing to do with licensing and ´everything to do with business model
  - techknowlogick 1y ago
    I'm not sure what you mean, as Gitea has SSO using many different ways, such as LDAP, OAuth2/OIDC, OpenID, SMTP, and more.
    - gchamonlive 1y ago
      I was responding to: > what happens when a community member wants to implement SAML for the community edition It's surely just business model, but I was intrigued and thought that maybe there were some kind of incompatible licensing in popular libraries people use for these so-called "premium features"
      - techknowlogick 1y ago
        Gitea would have SAML too (I'm the main author on the SAML PR to the Gitea project), but it's been held up by community reviews requiring esentially an entire re-write with another library. We'd love some help to get it across the finish line :) In open-source, money isn't the only thing that can be spent; we can also use our time.
- mappu 1y ago
  The SAML support in https://github.com/go-gitea/gitea/pull/29403 https://github.com/go-gitea/gitea/pull/29403 seems like it will get merged once the MR is a little bit higher quality. EDIT (bit better source): > Gitea Enterprise is an offering of CommitGo, not the Technical Oversight Committee of Gitea or the Gitea project itself. CommitGo remains committed to contributing back functionality to Gitea under the MIT license. Via https://blog.gitea.com/gitea-enterprise/#faq https://blog.gitea.com/gitea-enterprise/#faq
  - techknowlogick 1y ago
    Yup, this is the case. I'm the main author on that PR. It sadly stalled due to reviews from other maintainers requiring it to be rewritten using another library, but hopefully I'll be able to get back to it, or someone else will be able to pick it up. We've been able to get other functionality into Gitea already, and I've personally funded maintainers and others' work for the project, which goes directly into the project itself.
- techknowlogick 1y ago
  I'm the main author of the PR to implement SAML in Gitea, and it sadly has stalled due to reviews from maintainers requiring it to be rewritten entirely using another library. Our governance charter requires a certain process for PRs going into Gitea, and cannot be side-stepped by anyone. As for some of the others, we've been able to merge them in already.
  - tgmatt 1y ago
    SAML was just an example - I didn't see the PR before I made that post. That said, it feels fundamentally incompatible to a business strategy where your community edition is able to offer all of the features of the premium offering. I just can't see how that business would be able to survive if they allow that to happen. I'm always dubious of freemium software, because the free version is always gimped in some way, be it SSO compatibility (OK, yours supports OIDC it seems so that's not _terrible_), role-based access controls, high availability, etc. I will concede that businesses probably _should_ be paying for good software that is critical to their business to help support the vendors, but given how important cost savings are to companies these days, one can hardly blame engineers looking for cheaper offerings.
    - TheNewsIsHere 1y ago
      I agree with your last point, but as someone who co-owns a technology business that doesn’t have an “Enterprise” sized bank account, I still have all of those needs. The SSO tax in particular is ridiculous. Functionality like HA or SSO being gated behind enterprise licenses only makes it harder for smaller businesses to “get there”. My business is comprised exclusively of technology professionals. We tend to be really cheap customers to have because we typically only raise a ticket when something beyond our responsibility breaks. And from the community side — I already have enough credentials to maintain in my personal life. It’s annoying when you can’t use SSO with a community edition product. I like having SSO at home. It makes life so much better, and it also makes me more likely to use a product in my business, which makes it more likely I’ll buy a license to backstop support.
      - 1y ago
adduc 1y ago
> The Gitea project is still community-driven and has the same yearly elections for leadership that has been around for close to a decade now :) [1] mentions changes to the election process that mandates half of the oversight committee to be appointed by the Gitea company. Doesn't that conflict with your assertion that the "same yearly elections" have been around? Where can one find the governance charter for the Gitea project? [1]: https://blog.gitea.com/quarterly-23q1/ https://blog.gitea.com/quarterly-23q1/

TheNewsIsHere 1y ago

I love Forgejo. I recently started a project to exit my business (and eventually personal) git from Github. Gitea was my target having ruled out GitLab based on prior experience administering an instance, but I ended up going with a Forgejo and I am glad I did. The Gitea shenanigans around the for-profit entity and its opaque ownership structure were mainly what left a bad taste in my mouth, but there were a few other more minor factors that were use case specific. Fedora recently decided to switch to Forgejo, which is quite a feather in their cap. I also was somewhat skeptical that a git hosting platform that had a business behind it with enterprise oriented offerings wasn’t yet self-hosting in the technical sense.

kstrauser 1y ago
Same here. Forgejo is amazing and their development velocity is soaring. And https://codeberg.org https://codeberg.org is a great host for FOSS projects, in a way I wished Sourcehut would've been except that it leaned hard into some (to me) strange workflow choices. I'm glad I made the switch.

esafak 1y ago

Where are the screenshots?!