Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Gitea/Forgejo #154

Closed
ghost opened this issue Nov 14, 2023 · 4 comments · Fixed by #214
Closed

[Discussion] Gitea/Forgejo #154

ghost opened this issue Nov 14, 2023 · 4 comments · Fixed by #214

Comments

@ghost
Copy link

ghost commented Nov 14, 2023

I don't really know the best way to handle this...but thought I would bring it up for discussion.


Context

Forgejo is a soft-fork of Gitea. They provide a justification for existing:

Why was Forgejo created?

In October 2022 the domains and trademark of Gitea were transferred to a for-profit company without knowledge or approval of the community. Despite writing an open letter, the takeover was later confirmed. Forgejo was created as an alternative providing a software forge whose governance further the interest of the general public.

Forgejo was initially presented as a “soft-fork” of Gitea, similar to LineageOS, a community led distribution based on Android from Google. It is however better described as a product built on top of Gitea, Git and hundreds of other Free Software projects. Forgejo also has its own documentation, infrastructure, release pipeline, CI infrastructure, distribution channels etc.

Why did you open this discussion issue, @wkeiuluf?

As you may or may not know, users aren't always the brightest. Seeing "login with gitea" might be confusing to a user (not the admin setting everything up, but one of their users) that is like "hey, what's gitea?"

Basically, I think it would be nice to have an aliased set of GITEA stuff but with FORGEJO in place. But that might not be the cleanest way to handle it. Hell, people reading this may even just think "you're dumb, who cares" and that's fine, too; that's why I opened up a discussion for this. 😅

Another idea: maybe just change the button to "login with git" or something?


Anyway, just curious other people's thoughts on it.

@ghost
Copy link
Author

ghost commented Nov 14, 2023

Aside: since I'm spamming the repo, thought I'd also at least take a moment to thank you, @thomiceli, for making this. I've wanted exactly this product Forever™ (it seems like). 😭

@thomiceli
Copy link
Owner

I did not mess with Forgejo yet, but I guess since it's a fork, the oauth system works as same as Gitea, so it's more like a semantic problem ?

@ghost
Copy link
Author

ghost commented Nov 19, 2023

I did not mess with Forgejo yet, but I guess since it's a fork, the oauth system works as same as Gitea, so it's more like a semantic problem ?

Correct.

I have my Opengist using my Forgejo for auth and it works 100% as expected. :)

@crapStone
Copy link
Contributor

I opened a PR that let the server admin decide what name the button should have. I think it's ok for server admins to know that Gitea and Forgejo can be used interchangeably as long as the APIs do not break compatibility. And when that happens we have to implement another integration anyway 🤷‍♂️.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants