Live data from Hacker News

Winamp Legacy player source code

github.com

281–290 of 345 posts

Re: Winamp Legacy player source code

#282
post #269

Earlier quoted context omitted.

That’s not good enough. You can’t put out an open source project and expect to control the community around it to that degree.

Well, it's not an Open Source project. So there's that. ;)

Actually this is open source. This is what the term refers to. What you mean is that it's not free (libre) software, which is most certainly is not. They do not respect you and your rights: https://www.gnu.org/philosophy/open-source-misses-the-point....

Re: Winamp Legacy player source code

#284

Earlier quoted context omitted.

Well, it's not an Open Source project. So there's that. ;)

Actually this is open source. This is what the term refers to. What you mean is that it's not free (libre) software, which is most certainly is not. They do not respect you and your rights: https://www.gnu.org/philosophy/open-source-misses-the-point....

When people who care about open source talk about "open source", they often mean the Open Source Initiative definition. https://opensource.org/osd

Re: Winamp Legacy player source code

#285

Earlier quoted context omitted.

Actually this is open source. This is what the term refers to. What you mean is that it's not free (libre) software, which is most certainly is not. They do not respect you and your rights: https://www.gnu.org/philosophy/open-source-misses-the-point....

When people who care about open source talk about "open source", they often mean the Open Source Initiative definition. https://opensource.org/osd

sigh OSI was established specifically because they just wanted to share code and didn't care about GNU's 4 freedoms, so don't be surprised when the proponents of open source give you projects you can't even fork.

Re: Winamp Legacy player source code

#286

Earlier quoted context omitted.

Open an issue and type your patch into the description. Note that you can't test or debug your patch, because that would mean creating a modified version of the codebase, which is prohibited. Just type that stuff straight in, directly from your fever dreams, unmediated by common practice. If it's good enough for the license, it's good enough for the code.

No, it says: "You are granted the right to Modify the software for private use only. You may make, run, and propagate Covered works that you do not Convey, without conditions, so long as your License otherwise remains in force." It's clear they don't want you distributing modified versions. The thing people are getting caught up on is "You may not create, maintain, or distribute a forked version of the software." The…

I believe the parent commenter was being deeply sarcastic with their suggestion

Re: Winamp Legacy player source code

#287

Earlier quoted context omitted.

Well, it's not an Open Source project. So there's that. ;)

Actually this is open source. This is what the term refers to. What you mean is that it's not free (libre) software, which is most certainly is not. They do not respect you and your rights: https://www.gnu.org/philosophy/open-source-misses-the-point....

You might want to read the WinAMP license that you're claiming is Open Source.

Though it sounds like you might be misunderstanding things on purpose. (?)

Re: Winamp Legacy player source code

#288
post #7

I'm curious how they expect people to contribute to the project. Section 4 of the license says "Contribution to Project: You are encouraged to contribute improvements, enhancements, and bug fixes back to the project. Contributions must be submitted to the official repository and will be reviewed and incorporated at the discretion of the maintainers." However, the restrictions in Section 5 ban forking the code or dist…

The Github ToS gives users the right to fork any public repos.

It's not clear that Github's ToS can do such a thing, is it? What gives them the right to overrule the license from Winamp to me?

Re: Winamp Legacy player source code

#289
post #7

I'm curious how they expect people to contribute to the project. Section 4 of the license says "Contribution to Project: You are encouraged to contribute improvements, enhancements, and bug fixes back to the project. Contributions must be submitted to the official repository and will be reviewed and incorporated at the discretion of the maintainers." However, the restrictions in Section 5 ban forking the code or dist…

Anybody know whether this would preclude patches that contain none of the project's own source code?

Re: Winamp Legacy player source code

#290

Earlier quoted context omitted.

When people who care about open source talk about "open source", they often mean the Open Source Initiative definition. https://opensource.org/osd

sigh OSI was established specifically because they just wanted to share code and didn't care about GNU's 4 freedoms, so don't be surprised when the proponents of open source give you projects you can't even fork.

I'm not surprised. In this case, however, it doesn't even meet the OSI definition because it doesn't allow distribution of modified versions.
Post reply on HN