+1 for a forum or other editable medium. <br><div class="gmail_quote"><div dir="ltr">On Sat, Jul 30, 2016 at 4:55 PM Charles Srstka via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>+1 from me as well to anything that allows editing typos after posting.</div></div><div style="word-wrap:break-word"><div><br></div><div>Charles</div></div><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Jul 30, 2016, at 8:22 AM, Haravikk via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>But I like sending out my messages then regretting the many typos and mistakes I only seem able to notice immediately after it's too late to do anything about it!</div><div><br></div><div>(so yeah, +1)</div><br><div><blockquote type="cite"><div>On 30 Jul 2016, at 12:39, Johannes Neubauer via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div dir="auto"><div>+1 to move away from mail ;).</div><div><br></div><div>Another player might be [Slack][0] or [teamwire][1] . Kotlin uses Slack extensively.</div><div><br></div><div>[0]: <a href="https://slack.com/" target="_blank">https://slack.com/</a></div><div>[1]: <a href="http://www.teamwire.eu/" target="_blank">http://www.teamwire.eu/</a></div><div><br><div>Von meinem iPhone gesendet</div></div><div><br>Am 30.07.2016 um 06:43 schrieb Muse M via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>>:<br><br></div><blockquote type="cite"><div><div dir="ltr">I'm open to ZenHub that can be integrate as part of GitHub for discussion, pull changes and it makes it easier to reference to the patches within ZenHub than from Discourse or other forums. Swiftly right?<div><br><div><a href="https://www.zenhub.com/" target="_blank">https://www.zenhub.com</a><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 30, 2016 at 10:10 AM, Tim Vermeulen via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1. Hirundo makes this format bearable, but it is still far from ideal. I see many advantages for using Discourse:<br>
<br>
- It has actual syntax highlighting.<br>
- It’s easier to moderate.<br>
- It supports real-time updates.<br>
- It’s easier to follow the flow of a conversation.<br>
- It has better search.<br>
<br>
I don’t doubt more people will take part in the Swift evolution process if we switch to Discourse.<br>
<br>
> Branching...<br>
><br>
> On Fri, Jul 29, 2016 at 5:22 PM, Chris Lattner via swift-evolution<<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>(mailto:<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>)>wrote:<br>
<span>> > On Jul 29, 2016, at 5:14 PM, Brandon Knope<<a href="mailto:bknope@me.com" target="_blank">bknope@me.com</a>(mailto:<a href="mailto:bknope@me.com" target="_blank">bknope@me.com</a>)>wrote:<br>
> > ><br>
> > >Chris, has the core team discussed opening up a forum for discussing proposal implementations.<br>
> > ><br>
> > >Some of us aren't as skilled as the core team or other contributors but would like to learn. A forum is a much easier place for us to post for code help and to help others with their questions. I think this could help get more involved as it would be a more comfortable format for them. Think of how there are Apple Developer forums and not mailing lists for iOS betas etc.<br>
> > ><br>
> > >I am not saying moving swift-evo to forums *yet* but I believe a lot of the newer programmers are more comfortable with a forum format, especially when it comes to help and discussing code.<br>
> > ><br>
> > >Forums for contributors would:<br>
> > >- be more familiar for a lot of the newer and not as experienced developers<br>
> > >- be easier to search<br>
> > >- be easier to moderate (not really a problem yet)<br>
> ><br>
> > Hi Brandon,<br>
> ><br>
</span>> > Moving from email to a forum system has come up before, but they have some disadvantages.One of major wins of email is that it is pervasive and can be adapted into other forms.For example, if you haven’t seen it yet, check out:<br>
<span>> > <a href="https://stylemac.com/hirundo/" rel="noreferrer" target="_blank">https://stylemac.com/hirundo/</a><br>
> ><br>
> > -Chris<br>
> ><br>
> We've discussed forums on swift-evolution before. Maybe it's time for another go, with Swift 3 winding down.<br>
><br>
> For context, prior discussions are on this thread:<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001537.html" rel="noreferrer" target="_blank">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001537.html</a><br>
><br>
</span>> (-1 for mailman: it's hard for me to even properly find&link to all the prior discussion about mailing lists, because of how mailman's archive works...)<br>
<span>><br>
><br>
> News in the last few days is that Gmane is at least temporarily disappearing:<a href="https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502" rel="noreferrer" target="_blank">https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502</a><br>
><br>
><br>
</span>> I'd just like to vote once again forDiscourse(<a href="http://www.discourse.org/faq/#what):-Excellent" rel="noreferrer" target="_blank">http://www.discourse.org/faq/#what):-Excellent</a> web interface(<a href="https://meta.discourse.org/" rel="noreferrer" target="_blank">https://meta.discourse.org/</a>), from the people who brought you Stack Overflow(built-in search, etc.)<br>
<span>> - Read via email if that's your thing: it has "mailing list mode" which includes 1-email-per-post, if that's your cup of tea<br>
</span>> -Reply via email(<a href="https://meta.discourse.org/t/replacing-mailing-lists-email-in/13099)if" rel="noreferrer" target="_blank">https://meta.discourse.org/t/replacing-mailing-lists-email-in/13099)if</a> that's your thing<br>
> - It'sopen source(<a href="https://github.com/discourse/discourse)itself" rel="noreferrer" target="_blank">https://github.com/discourse/discourse)itself</a><br>
<span>> - I believe it has ways of getting content as JSON and/or RSS, so I'd hardly say "can be adapted into other forms" is an exclusive feature of email.<br>
><br>
</span>> And, Discourse providesfree hosting for community-friendly open-source projects(<a href="http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/" rel="noreferrer" target="_blank">http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/</a>). Istrongly suspect(<a href="https://twitter.com/jtbandes/status/705886542309363712)Swift" rel="noreferrer" target="_blank">https://twitter.com/jtbandes/status/705886542309363712)Swift</a> would qualify for this.<br>
<span>><br>
><br>
> There have been several people on this list arguing in favor of mailing lists — I encourage folks to go read the old thread for themselves.<br>
><br>
</span>> It's worth noting there are also plenty of voices that don't get heard on this list, because people just don't like using mailing lists. One example:<a href="https://twitter.com/pilky/status/755105431555608580_______________________________________________" rel="noreferrer" target="_blank">https://twitter.com/pilky/status/755105431555608580_______________________________________________</a><br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
><br>
><br>
><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div>_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div>_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>