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

Remove word “open” from repo description #44

Closed
Wuzzy2 opened this issue Jan 11, 2020 · 4 comments
Closed

Remove word “open” from repo description #44

Wuzzy2 opened this issue Jan 11, 2020 · 4 comments
Assignees

Comments

@Wuzzy2
Copy link

Wuzzy2 commented Jan 11, 2020

Current repo descriptoin:

The source code to VVVVVV, now open and public!

As this game is not an open source game, I recommend to remove the word “open” to avoid misleading users.

This game is not open source software as the license is too restrictive to meet the Open Source Definition (namely, commercial). The correct term is “source-available software”.

https://en.wikipedia.org/wiki/Source-available_software
https://opensource.org/osd

@flibitijibibo
Copy link
Collaborator

Should be easy enough to fix. @TerryCavanagh?

@RoestVrijStaal
Copy link

RoestVrijStaal commented Jan 11, 2020

The code IS open. It's not however free as in the FSF's ugly definition of "free".

Also, the OSI is a "company with an agenda" , and not a standards agency like the ISO.
Thus the authority of the OSI is like "Any fool can make a rule, and any fool will mind it."¹

Anyhow, stop demanding license changes. Swallow the decision of Terry or create your own viral licensed VVVVV-clone. (It's not that hard to remake).

¹ from Henry David Thoreau

@kitlith
Copy link

kitlith commented Jan 11, 2020

@RoestVrijStaal the author(s) have already shown they are willing to change the terminology used, and in fact already has on the announcement post (and elsewhere?), so this issue is basically just "you missed a spot", waiting on the person who owns the repository to change the description.

I would find your comment much more understandable they said "no, we're not changing the wording, because xyz" and then this issue popped up. If you want to argue with the people requesting a different license, then maybe you should head over to #7?

@TerryCavanagh
Copy link
Owner

Sure, I'll change the description.

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

5 participants