| |||||||||||||
LWN sourceLWN sourcePosted Jan 15, 2013 9:35 UTC (Tue) by dlang (✭ supporter ✭, #313)In reply to: LWN source by Duncan Parent article: LWN's 2013 Predictions
> Why does LWN continue to get away with it?
Because most LWN readers apparently believe that the people who write code (including the people who pay others to write code), have the right to decide what do do with the code.
The fact that many people are willing to release the code under copyleft licenses is something that we appreciate, but we don't believe that anyone should be forced to release code (unless it's a derivative work of code where the license requires release)
This is one of the places where Free Software and Open Source Software differ.
Free Software believes that writing non-Free software is unethical.
Open Source Software believes that releasing the code is a choice, and frequently a very good choice the from purely pragmatic viewpoint.
In the case of the LWN codebase, I would rather have more articles and no code release rather than having them concentrate on the code audit and release and go under because they aren't producing articles.
(Log in to post comments)
LWN source Posted Jan 15, 2013 10:39 UTC (Tue) by anselm (subscriber, #2796) [Link] In the case of the LWN codebase, I would rather have more articles and no code release rather than having them concentrate on the code audit and release and go under because they aren't producing articles. The LWN.net site code was presumably written in response to the specific requirements of LWN.net and much of it is probably not directly useful unless you are, in fact, LWN.net. Personally I, too, would much rather see Jon and his team concentrate on content, which they demonstrably do better than just about anybody else, than get sidetracked by having to sanitise the LWN site code for release and running a community development project (because naturally the people clamouring for a LWN.net code release don't want them to just throw the code over the wall, Android-style, no, they want them to accept bug reports and patches, do new releases, etc. etc. on an ongoing basis). Especially since, these days, ready-made free content management systems with support and a community are a dime a dozen.
|
|||||||||||||