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

Use of GitHub is unconstitutional, use libre alternative by libre service provider #361

Closed
Kreyren opened this issue Jun 2, 2021 · 3 comments

Comments

@Kreyren
Copy link

Kreyren commented Jun 2, 2021

The use of GitHub which is currently owned by non-free company Microsoft for the reuse tool is unconstitutional as it clearly promotes non-free platform and undermines the "core aspect of the work of the FSFE".

Coining the awareness for the problems related to the digital age in all parts of society is long-term goal and a core aspect of the work of the FSFE -- https://fsfe.org/about/legal/Constitution.en.pdf [26.05.2018]

I challenge you to migrate on Four Freedom respecting platform by providers who share the same ideology:

@Mte90
Copy link

Mte90 commented Jun 7, 2021

Well fsfe has their git instance https://git.fsfe.org

@mxmehl
Copy link
Member

mxmehl commented Jun 7, 2021

That's a discussion we've had a few times before. Three repositories of REUSE – tool, website and docs – are actually the only resources for which Github is the main source forge (of course mirrored to our own git). We did that to maximise external contribution in the form of issues and pull requests.

On git.fsfe.org, the user name is bound to having an FSFE account which can be obtained by becoming a supporter or asking for a volunteer account. Both is a threshold that lowers external feedback (we've tried that for a while).

However, we would obviously prefer getting rid of this exception. With this feature added to Gitea, we could allow easier registration to git.fsfe.org without creating potential conflicts with our LDAP user base.

I'll close this issue since it's not a tool issue but a more general item we regularly review anyway.

@mxmehl mxmehl closed this as completed Jun 7, 2021
@Kreyren
Copy link
Author

Kreyren commented Aug 7, 2021

I'll close this issue since it's not a tool issue but a more general item we regularly review anyway. @mxmehl

I elevated this issue to the mailing list.

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

3 participants