Just to clarify, we (Gitea) are not crypto shillers, the linked post explicitly mentions not creating some scamcoin.
Beyond that, we also haven't looked further into it as it became increasingly clear it was unwanted.
I'm unsure about the wording on Wikipedia, but I don't recall Lunny ever trying to take all the credit, just that he was an early and frequent committer.
We (Gitea) inherited the UI from Gogs, and iirc the UI choice was partially because Gogs was a one man show and partially because a familiar interface eases transition from GitHub.
We have talked about UI refreshes over the years, but it would be a huge undertaking while also keeping up with the rapid iteration.
This was not a company decision, it was proposed by a non-company member and approved by two other non-company members (and one company member, but just pointing out context).
> it's about community decision-making procedures (which have been removed during the incorporation)
A quick clarification here, the new TOC is comprised of three company members and three community members, with community members having a slight advantage should there be a split vote on anything.
I am a community member of the Gitea TOC, and there will be no open core model.
Gitea will remain fully open source with no tiers.
The community TOC also has advantages in any such voting where something may negatively affect the OS project, although as you mentioned that hasn't happened yet, and I don't expect it will.
I'm one of the community members on the Gitea TOC.
Just to clarify, only one maintainer left the project to my knowledge, although a few other contributors did as well. The majority of us remained with the Gitea project.
Actions are mostly still in beta with 1.19, disabled by default.
In general, one big thing that's been mentioned is that our actions don't currently support things like services (among other things), so while they are good for a quick CI, they aren't quite ready to replace a full CI system yet.
Possibly, yeah. Although Codeberg was already sort of similar, they had patches on top of Gitea, so assuming it doesn't change too drastically it may stay feasible for quite a while.
We have a list of maintainers, not all of whom can merge, so I apologize for getting this terminology incorrect.
I have usually referred to frequent contributors as maintainers interchangeably, but I am glad to have it clarified.
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.
I'm unsure about the wording on Wikipedia, but I don't recall Lunny ever trying to take all the credit, just that he was an early and frequent committer.