Hacker News new | past | comments | ask | show | jobs | submit | jolheiser's comments login

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.


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


Is there ever internal discussion about the name?


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.


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.


Honestly, it's a stupid response from me, but it did feel like a reminder of the recent changes.


No worries, that's totally understandable. The change was made mostly for practical reasons, to be able to upgrade infrastructure piece by piece. So both new and old infra could run at the same time while it was switched. I'm actually writing a blog post detailing the history of our infra, but the TLDR is that too much money and person effort was being spent on managing the infra.

Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.


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 of issues/prs/etc metadata and so migrating is a bit harder.


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.


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 changes will be available.

I'm biased as a community member of the Gitea TOC, so I'd of course recommend Gitea.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: