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

GitHub Terms of Service & What That Means For This License #4

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Hellscaped
Copy link

@Hellscaped Hellscaped commented Jan 15, 2025

GitHub does NOT allow Source Available in public repositories. There is a clause in the terms of service that says any public repository you dump on GitHub must be free for users to fork and redistribute, and therefore NOT Source Available.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

If you publish your source code in a public repository on GitHub, according to the Terms of Service, other users of GitHub.com have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see Setting repository visibility.

If you still wish to keep it Source Available, I would advise moving off GitHub to a selfhosted Gitea instance as Essential is inadvertently breaking the GitHub Terms of Service.

@Hellscaped
Copy link
Author

The README.md update was a placeholder to open this PR, can be ignored.

@blryface
Copy link

inb4 ignored & closed

@Hellscaped
Copy link
Author

inb4 ignored & closed

I've already reported the repo to github as contingency in the event this happens. The only way they do not get mauled by github is they either relocate or relicense.

@blryface
Copy link

inb4 also ignored by GitHub and this is just the way this repo will be for the foreseeable future

@Lamby777
Copy link

The only way they do not get mauled by github is they either relocate or relicense.

inb4 also ignored by GitHub and this is just the way this repo will be for the foreseeable future

or they just delete the repo and go full closed-source. truly a winampdesktop moment

also hey it's you from the polymc 2022 commit shitposting thread :D

@Eveeifyeve
Copy link

If you still wish to keep it Source Available, I would advise moving off GitHub to a selfhosted Gitea instance as Essential is inadvertently breaking the GitHub Terms of Service.

An other alternative is moving to gitlab or an self hosted gitlab instance of their own.

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

Successfully merging this pull request may close these issues.

4 participants