Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Winamp Legacy player source code

github.com

Post reply on HN
Print view View original

341–345 of 345 posts

Re: Winamp Legacy player source code

#341

Post by mnau »

joshribakoff wrote: post #330
Novosell wrote: post #19

Earlier quoted context omitted.

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

So someone steals my source code and posts it on GitHub, now i no longer have copyright rights? The duty is on the copier to ensure they are granted a license.

Open source projects on GitHub rely on D6 section of GitHub TOS. That is the part where a user declares that when s/he makes a contribution to a project, s/he does so under repository license. Also that you have right to do so (e.g. when you are on employer clock, your employer must agree).

It's not just a duty of copier to ensure they are granted a license. Legal stuff is never clear cut, but if someone agreed to TOS, it should be generally (that's a funny word that can mean anything) safe to assume that s/he does abide by it.

In this case, there is an obvious conflict and when there are two conflicting clasuses... that's fun for laywers.

Re: Winamp Legacy player source code

#342

Post by simoncion »

bastardoperator wrote: post #192
simoncion wrote: post #177

Earlier quoted context omitted.

One of the many bad things that Github did was to name the button that does the `git clone` action `Fork`. Like, I get why they did it, but (as we can see) it resulted in this stupid terminology confusion.

A fork is a linked copy, a clone is just a copy. They are not the same. Deleting your repository or changing its visibility affects that repository's forks.

  Deleting your repository or changing its visibility affects that repository's forks.
Sure, but this only matters for 'private' repos. See https://docs.github.com/en/pull-requests/collaborating-with-...>.

Github does some cute things behind the scenes to save space, but for all 'public' or 'internal' repos, what Github calls a fork is (from a Github user's perspective) identical to what happens when you run 'git clone' on your machine.

Re: Winamp Legacy player source code

#344

Post by kadoban »

mnau wrote: post #340
kadoban wrote: post #327

Earlier quoted context omitted.

Doesn't that just mean that Github should be mad at them? Doesn't seem obvious that it actually gives me a license to do anything.

Pretty much all open source projects on GitHub rely on section D.6 of GitHub TOS (when you submit PR, it's licensed under project license and you have a right to do so). TOS are not just fluff and paper, but legally binding. Granted, when there is a conflict between two conflicting requirements, it's never clear cut, but it's not just "GitHub will be mad."

Any project I've been involved in has its own explicit license, that allows such things (really allows much more, I don't touch anything closed source).

Re: Winamp Legacy player source code

#345

Post by itslennysfault »

shrikant wrote: post #8
itslennysfault wrote: post #6

Earlier quoted context omitted.

Thanks for sharing. Wonder if they've ever heard of color contrast. Dark blue on dark blue is not very readable. Had to highlight the article to read it.

I'm not seeing that colour combination -- are you sure you don't have Dark Reader or some such add-on enabled..?

Nah, I'm on my work computer. No browser add ons. Just standard chrome in dark mode. Clicking the light/dark toggle on the page (as some others suggested) does fix it.

Here is a screenshot of what I see if you're curious: https://imgur.com/a/eRchEn7

Post reply on HN