<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 13, 2017, at 1:08 AM, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Mon, Jun 12, 2017 at 9:31 PM, Paul Cantrell via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">I support everything Jon wrote.</div><div class=""><br class=""></div><div class="">+1 Free-for-all brainstorming venue separate from focused proposal discussion.</div></div></blockquote><div class=""><br class=""></div><div class="">+1, particularly for this being a section in Discourse ;-)</div></div></div></div></div></blockquote><div><br class=""></div>You posted this with a wink, but I think it's actually quite important. I see some value in having a "sounding board" area where people can talk through ideas that maybe aren't anywhere close to proposal yet, but actually encouraging the use of a completely different venue would be pretty unfortunate:</div><div><br class=""></div><div>1. That venue would become important to the community, but it wouldn't really be a *part* of the community in some ways. For example, it would be a terrible failure if the fashionable place for (say) talking about new reflection APIs was a website where not everyone felt comfortable participating because some of the established contributors there were jerks. We really want everything in the project to be covered under the Code of Conduct.</div><div><br class=""></div><div>2. Today, there's one standard venue for in-depth conversations about Swift evolution: this mailing list. Having one venue is self-reinforcing: if you have a conversation somewhere else, you're always missing people, and convincing people to join your side-conversation naturally makes them ask why you're not having it on the main venue. In contrast, telling people to have conversations elsewhere means intentionally fracturing the community, and there's no reason it would stay with just two venues. We'd probably end up with a ton of short-lived, hard-to-find, poorly-archived discussion groups with their own isolated focus and culture; that's a situation that naturally leads to different groups not realizing that they need to be talking to each other. It'd be more like the <i class="">salon</i> system than an engineering project.</div><div><br class=""></div><div>3. Having a separate venue for early-stage discussions also creates an awkward transition when the proposal is ready to move on. Discussion probably doesn't totally stop in the old venue, and in the new venue the discussion has lost a lot of context, and it's annoying to constantly refer back to the old venue. In contrast, if early discussions are just threads on a different part of the same forum, they can simply be moved around as they mature.</div><div><br class=""></div><div>So, in my opinion, we should just bear with the current situation until we have a proper forum.</div><div><br class=""></div><div>John.</div></body></html>