| attila77 |
2011-06-17 07:32 |
Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
Quote:
Originally Posted by woody14619
(Post 1030320)
Can you show me even a single example of where governance of a system was given to a group of people for all time, and not rescinded?
|
"His Brittanic Majesty acknowledges the said United States, viz., New Hampshire, Massachusetts Bay, Rhode Island and Providence Plantations, Connecticut, New York, New Jersey, Pennsylvania, Maryland, Virginia, North Carolina, South Carolina and Georgia, to be free sovereign and independent states, that he treats with them as such, and for himself, his heirs, and successors, relinquishes all claims to the government, propriety, and territorial rights of the same and every part thereof."
In theory, in some form similar things happened in every country that is a Republic (though in practice modern parliamental monarchies work that way, too) - of course if you talk in context of countries, it's unwieldy because millions of people cannot directly govern anything but formally, it *is* "We the People...".
Quote:
That's all fine and good. The problem is MeeGo is not GPL, at least not the parts we're talking about. The drivers and bobbles we're talking about here are under NDA, and are NOT under GPL nor any other open license. That's what this whole discussion is about! Were the drivers and misc bits open-source and GPL, I'd be all behind this in a second. It's not, and probably never will be.
|
This is what I'm saying when I say people don't know what MeeGo is and thus are wrong when they say MeeGo this or MeeGo that. MeeGo is GPL (and related FOSS licenses). Period. No but. No if. MeeGo is not a complete, device installable product. Nor will it be, it is a proto-distribution, that then people/companies make custom, but compatible versions of adding whatever closed crap they need, drivers, flash, you name it. And no, you cannot say the same to Android as closed API, license driven services are NOT open by any means. In a similar context Maemo is in a similar camp as there are middleware parts that are not open source (though admittedly with Maemo it's impossible to discern the OS from the device/product implementation so it gets a bit tricky).
Quote:
Yes and no... I was comparing it to the model as it exists now. Tell me, do you think the governance council here (freshly elected) has any voice with Nokia now? Many past council members have said they barely had a voice when it was the big thing. I'd be surprised if they can get someone at Nokia to answer an email for them now...
|
Yes. Actually, one of the key priorities in the Council's dealings is to see how to relate to any possible upcoming related Nokia products and projects (hate to use this formal wording, but hey).
Quote:
How so? If it's open source, completely open, one can make a complete copy of it and retain it for their own use. The original presenter can in fact go away, or shut down the service/site promoting it. But if others have valid complete copies, how then can it be stopped?
|
Oh, so when Google pulls an API what happens to your copy of that translation using open source project ?
Quote:
we're talking about governance means we're talking about a closed resource, virtual or tangible, that has limited availability.
|
Yes, but it is not what you think :) In the case of open source projects that is because it's ONE project you are talking about (and to a lesser extent because law links to particular names and entities). There is one Qt, one Apache, one Linux. Hence the question of governance. Don't like it ? Make an Ot, Sioux, Randomdudux (same sources!) and you have just assumed governance ! yay !
Quote:
MeeGo has several closed bits still, which is what we're talking about here. Nobody is talking about "governance" of Mozilla on MeeGo. It's a moot point, as it's completely open. The governance is around how the closed parts are managed, and the general structure of the system as a whole. Both of which could be pulled back in at will by the collective corporations that hold the key bits to make it work on their devices.
|
No, the pullback that kills open projects in company exits is the void created by the size of contribution/maintenance those companies make. There is only so much blood you can lose in one blow without fainting and/or dying. |
