Mattcrampy wrote:
Sorry for the troll, but I'm sort of annoyed at those that suggest that closed source no longer has a purpose now that open source is around. I'm taking obscure legal matters far too seriously.
Were you specifically talking about the FSF here? (I'm not sure you had a specific target in mind) The FSF is not the only group promoting the view that "
free/open is better"
; the OpenBSD developpers seem to share the same view, in so far as open software is the way to go for security *provided* that people are working on the code. I have heard a few Linux advocates that almost seemed to think that "
source code available for all automagically maintains itself and fixes its own bugs in the process"
, which, oddly enough, is a good deal less convincing than the continual auditing of code (I think FreeBSD also does that, and I wouldn't know about NetBSD).
The main difference between the GPL camp and the BSD followers seems to be the goal of being open in the first place. The FSF promotes the idea of "
freedom for all"
(at the expense of the initial developper), so that openess is a means to an end, whereas the BSD folks (and some of the others aforementioned) see openess as an end in itself. I don't think the picture is quite that clear cut, though.
I don't see the FSF, as in the organisation, as being particularly political. They certainly have an ideology, and some of their members are quite vocal (Stallman wpuld be the obvious example). As an organisation, I'm not sure the FSF has that much of a clout. While the ideology *could* be extended beyond software, the FSF itself is not going that way: I haven't heard them supporting open hardware, and they plainly state on the
GNU website licence page that "
We don't take the position that artistic or entertainment works must be free, but if you want to make one free, we recommend the Free Art License"
, which sounds quite like the carpet statement to me (what in the nine hells is a "
work"
in this sentence? I could make a case of "
work"
including software here).
So, the FSF mostly focuses on software (or a subset of software), and follows that line in their interpretation of the GPL. The GPL is sometimes used beyond software, but I don't think it is linked to the FSF itself. Along the same lines, the FSF encourages the spliting of software and documentation, with documentation being less important in their reasoning (the GFDL licence is not nearly as protective as the GPL, but if the GPL is such a good thing, why not extend it to documentation?). The GFDL is also, of course, incompatible with the GPL, and, of course, means yet another licence hanging around, as if we didn't have enough of them already. I think it is more advocates of free software than the FSF or the GPL themselves that are really being political (Debian has a quite interesting and uncommon organisation, among others).
That aside, I don't see the BSD side as being solely focused on just better software. OpenBSD strikes me as being stricter on certain requirements than any mainstream Linux distro I know of (check their Lyrics page, for example). If memory serves, OpenBSD doesn't carry more than user-land firmwares (Debian has a few binary drivers in kernel-land), has been rewriting some software when the licence was found to be inadequate, has questionned licences the FSF and Debian found adequate (last time I toyed with OpenBSD, there was no Apache 2.0 there; it looks like the situation is still the same now), and has been quite involved in getting open hardware. The FSF did give their award to Theo de Raadt in 2004, and they might have a better relationship with OpenBSD than with Debian these days.
I think the chief difference between the GPL and the BSD licence is their safeguards. The GPL rests on copyright or civil law, and uses copyright provisions, albeit in a reversed manner, whereas the BSD licence is closer to the public domain than to an actual licence. Instead, the BSD model seems to be more empowering, and more based on trust with regards to support for further development (the end product of GPL code will be more restricted than BSD, where the one thing to do is credit the original developpers). Note that the GPL seems about as permissive as BSD licence if you are *not* redistributing the program: you can do pretty much what you want with GPL code so long as it is not publicly distributed (copyleft only kicks in with full force at this stage). In the Ideal World, I think I would prefer a BSD-style licence over the rooted-in-law GPL (hmm, I'd better watch out or I'll become more vocal than Jamie at that rate). In the Less than Ideal World, I would prefer to keep the two licences strong and kicking, just in case.
Or I'm just rambling. Or stuff. Definitively rambling it seems.
jamie wrote:
And I hope people reading this thread don't think OSS==Linux.
Heh, that's the main thing I like with the FSF label of GNU/Linux. While I don't have an opinion regarding the merits of their claim (I wasn't born to begin with when GNU started out, so my knowledge is third-hand at best), I do like the reminder that Linux just isn't synonymous with "
everything not related to MacOs X or Windows out there"
, and that somehow most people use software rather than kernel calls. Of course, that covers only Linux, but that one seems the most overreaching name out there (I have yet to see someone using "
*BSD"
to cover more than the operating system taken as a whole).
I also like Unix-like or a similar name for the same purpose, applying this time to the diversity of related operating systems out there (Unix isn't a wholly accurate name here, but still). I'm not overly fond of the (F)OSS label, though. In any event, I would prefer that Linux doesn't make "
OSS"
stand for "
Operating System Specific"
.