It's great that they decided to open source it (again?). But in some ways it would also have been interesting to see this go to court and establish a precedent on the authority required to license software. Whose signoff do you need? A developer, your manager?, the CEO? Is it enough for people within the company to be "generally aware" of the fact. Seems like an interesting question to me.
Sounds like they might have an official policy on how to release stuff as open-source, but it wasn't followed.
Some random googling brought up:
"Executing Corporate Contracts. Except as otherwise provided in the articles or in these bylaws, the board of directors by resolution may authorize any officer, officers, agent, or agents to enter into any contract or to execute any instrument in the name of and on behalf of the corporation." [1].
But does this apply to software licenses too? As a user of a software package is there any reasonable way for me to determine that the correct legal procedure has been followed. If the source has been out there under the GPL for 9 months, could they still revoke the license because it wasn't authorised? Or have they not done due diligence?
As a software engineer, what kind of authorisation should I be looking for? Does it need to come from upper management?
Those are the kind of issues that might have come up in a court case, and perhaps have been resolved to some degree (perhaps it's already been tested in a previous case, and I'm unaware of it).
[1] http://danashultz.com/blog/2010/06/28/who-can-sign-a-contrac...