Viewing profile — jolheiser

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 becam…

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.…

I am not with the fork, but seeing as people ask this about us all the time I can relate. https://forgejo.org/static/forgejo.mp4

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 a…

Out of curiosity, why did that stand out? We've had the .com domain for a little while, so now we're starting to consolidate things to it.

We are actively working on it, everything other than the main repo is on gitea.com and a lot of that is also being converted to dogfood actions. The main repo, however, has a lot o…

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…

Currently the fork is simple rebranding with a few small changes here and there. Both of them will give you nearly the same experience, and they are a soft fork so all Gitea change…

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 majorit…

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 (a…

As far as I know the plan is to upstream it to Gitea as well, fwiw

The TOC is our owners team, but three are from the company and three are from the community. The reason to say it as a disclaimer is because we are going to have some bias.

You can go look at the demo/site for Gitea if you want. At the time of writing the interface will be identical.

Gogs -> Gitea -> Forgejo Gitea is a hard-fork of Gogs, while Forgejo is (currently) a soft-fork of Gitea.

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 whil…

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 int…

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 si…

A soft fork means Forgejo will be periodically pulling from Gitea. As far as I know they intend to upstream patches they make as well. And yes, Gitea is still open source and MIT l…

As a quick clarification, Forgejo is a soft fork, not hard. They will still benefit from upstream contributions.

The current plan, as far as I know it, is to continue on the OSS part predominantly. The only parts that would not be, would be anything that comes from a contract and doesn't make…

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 …

Gitea has been working on federation, slowly but surely.

The way I read it is "company x has some internal system that they want to integrate with gitea" Where it may not make sense to contribute it back.

I didn't read this as open core. The previous point from the quote was that the project remains MIT. The following point was that contracts favorable to those conditions would also…