<div class="gmail_quote">On Fri, Aug 20, 2010 at 8:20 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">"This all got hashed out right when the list and group started getting off the ground."<br><br></div>I have to state that was not in any way shape or form a unanimous decision! It was a brief thread that was picked up and ran with ... with minimal "group" inputs that I recall.<br>
<br><br>Cais.</blockquote><div><br></div><div>I agree completely - and like I said, I was originally of the opposing school of thought.</div><div><br></div><div>But, while it is good to revisit these things, it would be best if we could come up with some guiding principles to use moving forward. It is unfair to Theme developers to change these kinds of decisions frequently and arbitrarily. (Some Themes have already been denied, in part, due to lack of support for features that we're now discussing making optional.)</div>
<div><br></div><div>So: just a caveat: we need to tread lightly, and future-proof our decision-making process.</div><div><br></div><div>Chip </div></div>