Is there any work towards a v2 API yet? I'd like to have some input on the design, if so. I'd really like to see the configurations API cleaned up and made more consistent with the rest of the API, for example. The way it works currently is a pain to handle in the client libraries because it breaks out of the normal patterns used by the rest of the API. Alternatively, we could just fix the v1 API, but I can't think of a way to handle it without breaking compatibility.
If there isn't anything going on in this area, is it something the community is open to discussing? Greg
