Absolutely true. Nokia can - if they wish - close source of *further* releases - if (and only if) they're not basing it on already (L)GPL'ed stuff (so, basically, closing source of further releases, would need re-writing it from scratch). So, all posts about "Nokia can change their mind" are plain wrong - it's not /bsd license, where You can base Your work on FOSS thing, and close You resulted code.
Is the developer of a GPL-covered program bound by the GPL? Could the developer's actions ever be a violation of the GPL? (#DeveloperViolate) Strictly speaking, the GPL is a license from the developer for others to use, distribute and change the program. The developer itself is not bound by it, so no matter what the developer does, this is not a “violation” of the GPL. However, if the developer does something that would violate the GPL if done by someone else, the developer will surely lose moral standing in the community.
Can the developer of a program who distributed it under the GPL later license it to another party for exclusive use? (#CanDeveloperThirdParty) No, because the public already has the right to use the program under the GPL, and this right cannot be withdrawn.
Still, all of this does *not* apply here, cause we're talking here about stuff already released under LGPL. And, we are not interested in further releases, but in this release (I've written here about "changing their mind" just for the records).
As for ideas, I've none how we can proceed now - other than rising LGPL violation (which is also not a thing, that I would like to do on daily basic for fun). My mail got ignored (up to date), and bug was commented only with "we will release it soon". I'm just worried about us getting sources, before those "suckers" got bankrupt - this doesn't change license obligation, but at least argument about "too few hands on board" become more true. /Estel
Who has the power to enforce the GPL? (#WhoHasThePower) Since the GPL is a copyright license, the copyright holders of the software are the ones who have the power to enforce the GPL. If you see a violation of the GPL, you should inform the developers of the GPL-covered software involved. They either are the copyright holders, or are connected with the copyright holders.