Isn't the Gitea company for-profit? Wasn't the leadership committee restructured to mandate half of its members are elected by the for-profit?

Browsing the blog archives, there doesn't appear to be any indication that the concerns that were brought up around the incorporation of the for-profit have been resolved.

[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/

If the article is correct, Thundermail will be built using Stalwart[1], which appears to support JMAP

[1]: https://stalw.art/

[1]: https://arstechnica.com/gadgets/2023/05/review-framework-lap...

Forgejo v10 is the first release I've seen where there's been a focus on tiny UX improvements (versus trying to remain compatible with Gitea). I'm hopeful these will continue to come, but it does still feel essentially identical in appearance and functionality with Gitea.

[1]: https://extensionworkshop.com/documentation/publish/signing-...

I've found Athena doesn't appear to search through all log entries (possible user error on my part); I've been downloading the cloudtrail logs directly from S3 and grepping through the logs directly to find the relevant entries to figure out the permissions needed.

If you need to decode an encrypted error message, use `aws sts decode-authorization-message --encoded-message $MESSAGE`. It'll return a JSON string. I typically use `aws --profile limbledevadmin sts decode-authorization-message --output text --encoded-message $MSG | jq .context.action` to extract the needed permission.

[0]: https://mariadb.org/mariadb-contribution-statistics-march-20...

[1]: https://phpc.social/@marcan@treehouse.systems/10981800943090...

I'd recommend checking your settings to see if sponsored suggestions are enabled.

> We do not have an adequate history with our subscription or pricing models to accurately predict the long-term rate of customer subscription renewals or adoption, or the impact these renewals and adoption will have on our revenues or operating results.

For context, GitLab recently axed their lowest priced plan and grandfathered in existing users at cheaper rates for the next year. Their retention rate may drop once discounts run out and the new pricing kicks in.

As to the parent's comment about "The Homer" and non-core features being bad, I'd point to their CI autoscaling solution as an example of being underdeveloped, over-marketed, and suffering from technical debt. Their autoscaler uses docker machine behind-the-scenes, which hooks into various cloud providers to abstract away the act of spinning up new VMs. It works reasonably well, but Docker has archived the repository and no longer supports the software. GitLab forked the repository and maintains it for critical fixes, but is not willing to develop or accept new features. It has been known to break against new versions of Docker, does not handle concurrency very well in new environments, and does not allow [1] executing multiple concurrent jobs within spun up VMs, despite marketing that it can [2].

While the autoscaler does work, it's limitations and quirks reduces it's utility and cost-savings significantly within smaller organizations. The technical debt leaves me doubting any improvements will come within the next few years as they try to architect a new solution to replace the existing one.

I have no idea how GitLab compares in other areas, but within CI autoscaling it seems they're stuck with a cliff to climb down before they can move forward again.

[1]: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2787#no...

[2]: https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runner...

> Premium is for team (s) usage, with the purchasing decision led by one or more Directors

Doesn't this conflict with the stewardship promise that "The open source codebase will have all the features that are essential to running a large 'forge' with public and private repositories"?

[1]: https://github.com/chaoslawful/lua-nginx-module

What went live in 5.4 was support for brackets in lieu of array()

    // Typical array syntax
    $arr = array('key' => 'asdf');

    // Supported in 5.4+
    $arr = ['key' => 'asdf'];