Funniest bit:
"Forking is not allowed" vs. "Contributions encouraged"
On GitHub, that requires a fork however 🤔
or do they want us to use git send-email?
Top-level
Funniest bit: "Forking is not allowed" vs. "Contributions encouraged" On GitHub, that requires a fork however 🤔 or do they want us to use git send-email? 20 comments
@pixel i think they mean making derived software, not github forks.
0
0
24 September at 16:54 | Open on stereophonic.space
Our friends at Winamp do not seem to know git that much, do they? Lection, the effectiveness of a "Remove closed source code" commit: https://github.com/WinampDesktop/winamp/commit/0a4b7d32d090696e5aab8de9c61dda9dab76aabf Jef is hard at work trying to remove the SHOUTcast code from the repository after merging it back in again... https://github.com/WinampDesktop/winamp/commit/1be04037cdba95396eef7728134043ba3ee6fbf4 Winamp, it really whips the authority of their executables. They accidentally pushed all codesigning stuff, including signature passwords into the repo as well :blobcatnotlikethis: https://github.com/WinampDesktop/winamp/tree/community/Src/codesign Actually, I am highly doubting *accidental* at this point, but the poor employee who just remembered that Winamp wanted to release their code today just went and slapped EVERYTHING into git. I'm a bit in a rollercoaster of emotions of thinking this is catastrophic and catastrophically hilarious. @pixel https://github.com/WinampDesktop/winamp/blob/community/Src/resources/media/Sean_Bones_Dancehall.mp3 ... didn't expect to find an entire song in their repository. @porglezomp it most likely is, but that's what is written in their license. As mentioned above, probably nothing a software/publishing lawyer looked over. |