I wonder if we should simplify the cds workflow a bit to go straight to an etherpad outline of the blueprint instead of the wiki blueprint doc. I find it a bit disorienting to be flipping between the two, and after the fact find it frustrating that there isn't a single reference to go back to for the outcome of the session (you have to look at both the pad and the bp). Perhaps just using the pad from the get-go will streamline things a bit and make it a little more lightweight? What does everyone think? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
