Guideline: Forgejo-first orientation in communication #110

I see a lot of mention in various channels that ring like "Gitea/Forgejo .. this and that".

Suggest that as a general rule we mention Forgejo first, our main thing. Followed by Gitea second, the upstream project we are otherwise independent of.

It may seem nitpicking, but it is a marketing/PR thing, and psychology to readers thinking of Forgejo first.

I tend to call Gitea first if talking about issues that come from our shared codebase as well as when talking/writing in Gitea's spaces (like a chat or issue tracker, but there it's more "also applies to Forgejo" or "same behaviour as in Forgejo")...

Yes, @fnetX also mentioned naming Gitea first in reference to bugs that existed well before Forgejo. There's something to say for that, though these bugs are created in issue tracker with 'Upstream' label and referencing a related one in Gitea. That is Forgejo-first tracking.

I'd personally prefer that to be the norm, Forgejo-first, and it also conveys: "We got your back" i.e. it may be Gitea's thing but we monitor it. It's important to our project.