Go ahead and make a new API, no problem, but don't break the apps we built over the last N years while Flickr was hibernating.
* You decided when the spec should be frozen. You're asking Flickr to give away control over their specs.
* Freezing a spec incurs no ongoing cost to you. You're asking Flickr to maintain current services indefinitely.
A comparable situation would be to put Userland under the control of some external entity, which had the right to impose obligations on you to (for instance) keep the data available in current formats forever.
That's of course assuming that it's possible to do with a new API what you could do with the old one. We've seen with Twitter that's not necessarily true.
But thanks Dody for thinking of users. That's often pretty far down the priority list for developers, esp at big companies.
Even if this made any sense, when you declare something a landmark, you also make it nearly impossible to upgrade. You're saying that most of its value lies in preserving what was, not what will be.
Before you do the "waaaaah Flickr hasn't upgraded in a long time anyway"... http://www.flickr.com/services/developer/changelog/
They are hiring people to work on the API full-time, last I heard.