I think standardization is just a distant goal. The model would be probably similar with what boost libraries achieved with tr1. The portable c++ library should evolve in a coordinated way (by Herb Sutter & Co), because of the composability and type consistency.
Here is also a relevant quote from the last day panel of the conference:
Advice for people who are willing to help to close the libraries gap and put food on the table?
First, please email. Let me know. If you are a zlib, boost, adobe, apache, poco, apple, and so forth developer who has access to in-house libraries that could be contributed, or just want to help, please let me know because that's what we try to put together. We have a spreadsheet with a list of the features we want, only half of them are filled in with existing practice and smaller that that with people who are able to contribute work on them. So if you have time, it is not expected to be a full time job, but it does require help, and that's what we need most, expert help.
The 'food on the table' part was addressed: it is volunteer work (with a funny comment from Bjarne regarding this
If Poco has on the TODO list an overhaul in order to better use and not overlap with new C++11 features, this may be the way: the changes could be coordinated as part of this larger effort.