Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can you give an example?

E.g., the MIT license wasn’t motivated by collaborative considerations, but it was mostly about the effectiveness and practicality of software distribution.



The Linux kernel definitely has the interest to force people to upstream modifications. GCC rejected the idea of converting itself as a library to force vendors to upstream their changes.


If something is "forced", it is inherently not an "invitation".

Additionally, GPL and derivatives focus on sharing code with users, which isn't necessarily the same thing as collaborating with the project's creators upstream. It depends entirely on how and where the software is used.


Not in that sense of the word "forced". You can of course maintain your own kernel fork, it is just a lot of work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: