On Mon, Aug 4, 2008 at 3:19 PM, Chris Chabot <[EMAIL PROTECTED]> wrote: > Wouldn't the proper thing be to first make sure it's part of the spec, and > then commit it to shindig?
Sometimes. =) There is some precedent for doing it in the opposite order, in order to validate spec proposals or otherwise experiment with features. The advantages of doing Shindig first are that we get better quality spec proposals. The downside of Shindig first is that we may end up redoing work in Shindig to sync up with spec changes. In this case I don't think the order matters much, because the proposal is simple.
