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

Provide a means of participating in this standard which does not require nonfree software #443

Closed
ddevault opened this issue Dec 21, 2021 · 6 comments

Comments

@ddevault
Copy link

I have feedback to share but I will not share it on GitHub.

@mxmehl
Copy link
Member

mxmehl commented Dec 21, 2021

No problem, please find other contact channels on our website: https://reuse.software/resources/#contact

If you'd have pull requests, you can also send me patches via email. My contact details are linked on the aforementioned page.

@mxmehl mxmehl closed this as completed Dec 21, 2021
@ddevault
Copy link
Author

Thanks, I will use those resources. I will state for the record, however, that hosting an official FSFE project on a nonfree software forge is -- pardon my language -- utter horseshit.

@seabass-labrax
Copy link
Contributor

There's been some development in Gitea (not yet merged) to add suffixes to usernames that come from OAuth providers. This would allow the FSFE Git repository to allow logins with either an FSFE account or an external OAuth provider. go-gitea/gitea#7014

I remember @mxmehl saying (correct me if I'm wrong) that this would be a requirement for the REUSE tool to be hosted on git.fsfe.org, as most of the contributors don't have accounts there.

@mxmehl
Copy link
Member

mxmehl commented Dec 21, 2021

Exactly. While I personally would have no problem with patches or issues be sent to an email list, for most this is a no-go unfortunately. I think REUSE has become a nice tool with contributions from many different people that would not have been able or willing to join the FSFE's Git server (which is used for everything else we do really).

When setting everything up, widely used Free Software services like Codeberg or SourceHut did not exist (or were too unknown or simply not on our radar, or notoriously unreliable), and GitLab.com is proprietary as well.

Solving the linked Gitea issue (which I created because of this exactly) would drastically change the situation indeed. The migration of issues would be some pain, but thanks to Gitea's features in this regard manageable.

@aschrijver
Copy link

Since both Gitea and Codeberg are mentioned here, I'd like to update here the recent developments where Codeberg is now running on top of (the soft fork) Forgejo which has been created as result of the incorporation of Gitea Ltd.

FWIW I will bring attention to @seabass-labrax comment above to the Forgejo matrix chatroom where I am active. Codeberg/Forgejo are fully dedicated to Free Software and might be interested to consider bringing these changes, esp. if that helps move FSFE REUSE to Free Software again as well.

@mxmehl
Copy link
Member

mxmehl commented Feb 15, 2023

I can only speak for myself but I am excited about the recent work done to make Gitea/Forgejo federate. As mentioned numerous times already in different discussions, a working federation would most likely enable the REUSE tool to finally switch to a fully Free Software development platform without losing too many contributors.

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

No branches or pull requests

4 participants