top | item 44654438

(no title)

techknowlogick | 7 months 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

discuss

order

adduc|7 months 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/

tgmatt|7 months 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?

mappu|7 months ago

The SAML support in 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

techknowlogick|7 months 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.

gchamonlive|7 months ago

Is MIT license and SSO features mutually exclusive? Or is it just a business model to sweep such features under a paid subscription?