<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">When moving to a forum, the problem becomes a thread splintering to an overwhelming tree. I'd prefer to see a single primary thread (as in the mailing lists) with breakout threads for working groups. These could be built either around already identified areas (see manifestos) or future directions (such as mathematics, fp, merging features from other languages). </div><div class=""><ul class=""><li class="">I think announce should announce. One thread, one purpose.</li><li class="">I think evolution should have a review forum: one thread for each proposal.</li><li class="">Pitches and RFC should have their own forum, with individual threads. The dangers here are (1) losing good ideas, (2) good ideas that are timed poorly, (3) redundant ideas from not having found previous discussions, (4) well intentioned but inappropriate ideas. Having a way to filter types 3 and 4 out to a subforum to raise the S:N should be possible but will require some kind of moderation (such as Xiodi Wu has put such effort into supporting)</li><li class="">Working groups need their own development area. There needs to be some sort of top-level organization to make this usable ("Generics", "Dispatch", "Calendar/Clocks/Time", "Mathematics", "Strings", "Collections", whatever), but there should also be a level of flexiblity. I'd recommend giving manifesto topics initial priority at the top level but I'd also suggest that there have to be some kind of effort to open a new discussion area, to limit the number of "ghost forums".</li><li class="">A SE version of a FAQ, be it "Commonly Proposed"/"Commonly Rejected" and some kind of Quinn-like Eskimo support for directing and moderating.</li></ul></div><div class=""><br class=""></div><div class="">The measures of success are:</div><div class=""><br class=""></div><div class="">* Can track news ("announce")</div><div class="">* Can participate in active reviews</div><div class="">* Can read archived reviews</div><div class="">* Can pitch and develop proposals as part of a working group</div><div class="">* Can search for previous discussions</div><div class="">* Can look up whether common topics have already been hit </div><div class="">* Can support a small and well-populated forum hierarchy with few orphans and ghosts</div><div class="">* Communicates that the forum is a non-social working area and a public record of language development.</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Aug 1, 2017, at 11:13 PM, Ted Kremenek via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">A while back a decision was reached to move from using mailing lists for swift-evolution to using a forum, specifically Discourse. At the time that decision was made, efforts had been already well committed for supporting the development of Swift 4 — including efforts supporting important infrastructure efforts such as the source compatibility suite. I apologize for not providing more transparency in why moving to a forum was being delayed. Some things took longer than expected.<div class=""><br class=""></div><div class="">To be clear, the plan is to still move to Discourse, and with Swift 4 winding down there is now bandwidth to focus on making the transition from mailing lists to a forum. <b class="">As part of that transition, I’d like to get some feedback from the community</b>.</div><div class=""><br class=""></div><div class="">There has been some good conversations on this mailing list on how swift-evolution can possibly evolve to better serve the needs of the community. I’m not talking about whether or not we use a mailing list or a forum — that decision has been made. Specifically, I’m talking about how a forum could best be structured to organize discussions and allow everyone to optimally participate. In the move to Discourse, we have the opportunity here to possibly do things a bit differently than we have been so far.</div><div class=""><div class=""><br class=""></div><div class="">For example, here are some of the questions I’m thinking about how we should be use a forum:</div><div class=""><br class=""></div><div class="">- We currently have swift-evolution and swift-evolution-announce. Should we use a specific “category” in the forum for "proposals that are in active review" — and possibly remove the need to have something like swift-evolution-announce? </div><div class=""><br class=""></div><div class="">- Should we have other topical areas to organize discussions? If so, at what granularity?</div><div class=""><br class=""></div><div class="">We can certainly figure out a lot of this over time, but I’d like some feedback from the community now on things they’d like to see in how we organize the swift-evolution forum based on experiences we’ve had with swift-evolution since it was created.</div><div class=""><br class=""></div><div class="">Please chime in on this thread if you have feedback, and focus on keeping this constructive.</div></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Ted</div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>