GNOME Foundation Elections - Final Candidate List
Motor writes: "The list of candidates for the forthcoming GNOME foundation election is now available. And yes, RMS is on there..." Note for voters, the email will be sent out the 13th. Please note the Election Rules and Director Overview Good luck to all the candidates!
No kidding... In the flerbage article, ESR asked this question of both RMS and Tim O'Reilly (when the latter two were having their debate): if you two could get a law passed making proprietary licenses illegal, would you do it?
Did RMS ever answer? Because if Mr. It's All About the Freedom To Choose wants to forbid the existence of proprietary software -- not just discourage it through discussion, but to forbid it beyond discussion -- then he's clearly unfit for any kind of leadership position.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
I think he means that Gnome is the only GNU-Desktop that succeeded. KDE is (thank god!) not part of the GNU-project.
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
Also, he has all kinds of technical stuff going for him. He was one of the original authors behind X, for example.
He also has a lot of (IMHO) good opinions on design. A short piece on that.
I believe he can (continue to) do a lot of good for Gnome.
"An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
I can answer this. You can distribute only the code that you either own (the one that you wrote yourself) or when you have an explicit permission to distribute it (such as GPL, BSD, etc.). When you write code for a company, you do not own it. Repeat: it doesn't matter that you wrote the code -- whoever pays you to write the code owns it. Therefore, if the contract you signed prevents you from distributing the code, you cannot distribute it because 1) it's not yours; 2) you don't have permission. The company you did the work for -- and only the company -- can decide whether to distribute the code or not. You can of course distribute the original, unmodified version.
No grey area there. Move along.
___
If you think big enough, you'll never have to do it.
1. False. I am not claiming that at all. Read my post again. And again. As long as it takes for you to understand. What I said was: you are still allowed to distribute the original (unmodified) version; you are not allowed to distribute the code that you wrote by contract because you don't own it -- the company does. If the comany decides to distribute this code then they must do so according to the terms of GPL. If they decide not to distribute it then they can do whatever they want. Point is: the company owns the code, not you -- therefore the company makes decisions about the code, not you.
2. GPL has absolutely nothing to do with contract law. It is based entirely in copyright law. Therefore, it is actually stronger than most proprietary licenses (well, until all states pass UCITA anyway ;-)
___
If you think big enough, you'll never have to do it.
It depends on your definition of open source.
The way I understand open source, what it means is that when you give somebody your binaries, you give them the source as well.
You just don't glom onto the binaries the way M$ does and refuse to hand over the source.
This is the normal way of doing in-house code at many establishments. The exception is when the in-house company hires a consultant firm to write the code.
The definition you seem to be going by is that open source means that you give the source to anybody who asks. This is "free as in beer," and is different from the kind of "free" that RMS talks about all the time.
my old sig used to be funny, but then slashcode ate it and now it's not funny anymore
Oh, I see what you mean. The only thing I can think of off the top of my head is the 1854 (?) supreme court ruling that corporations are individuals and thus have all the rights mere mortals have. (Their vast resourses in effect make them super-people). But in any case, companies are generally treated as one entity in matters such as this. The secretary receiving the peice of software is an employee of the company and, therefore, a part of the same entity. She uses the software for the benefit of the company while doing her job (i.e. she does not get a copy for her home machine). Also, as I mentioned earlier, any work you do for the company is the property of the company (this mystical entity). If the secretary were able to legally get the copy of the software while off work and off the copany's property, then she would be treated as individual if the matter went to cort, and she would not be under contractual obligations to the company. But that implies that the software is distributed outside the company.
So I guess basically what I'm saying is that an employee is not an individual; an employee is a number in the HR database ;-) When you become an employee, you voluntarily choose to give up some rights in exchange for a paycheque.
By no means do I claim to be an expert on the subject, but it just wouldn't make sense to me otherwise.
___
If you think big enough, you'll never have to do it.