<div dir="ltr">I&#39;m coming around to the idea of discourse, mainly because that would allow providing a consistent display of the discussion and not having every subscriber reinvent the way he wants to see threaded discussion, quotations and code samples. As discourse supports mailing list mode, which would allow keeping the discussion via email but also having an &quot;authoritative&quot; source where you can always hop to and get a view on everything that is going on I think that it becomes an additive win for the community.<br><br><div class="gmail_quote"><div dir="ltr">On Sat, Feb 4, 2017 at 9:46 PM Derrick Ho via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with you on point number two.   There is way too much scrolling.  Im viewing it on mobile so that&#39;s even more scrolling.  Discourse allows jumping to the next topic so if I don&#39;t want to scroll I can jump to the next topic.<br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Sat, Feb 4, 2017 at 2:36 PM Cihat Gündüz via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>&gt; wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg">After trying out Nate Cook’s <a href="http://discourse.natecook.com" class="gmail_msg" target="_blank">Discourse test server</a> I’d like to add a few things on my previous message:</div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg"><br class="gmail_msg"></div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg">#1 I found the <a href="http://discourse.natecook.com/t/discussion-mailing-list-alternative/2989" class="gmail_msg" target="_blank">beginning of this threads discussion</a> without any problems (both from navigating through the threads structure and from the search feature) which was interesting for me, as I couldn’t do that in my mail client given that I opted in to the mailing list later on. Especially the fact that at the beginning Discourse wasn’t even suggested of the original post was interesting. I wouldn’t have known that without the Discourse test server.</div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg"><br class="gmail_msg"></div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg">#2 Following a discussion is much easier in general, but I noticed one downside (I guess that’s one of the hurdles to be addressed): Some quotes within emails were imported to threads in a way that makes reading actually much worse. See <a href="http://discourse.natecook.com/t/strings-in-swift-4/2980" class="gmail_msg" target="_blank">this thread</a> as an example. The initial messages is repeated over and over again, and since it’s very long scrolling all the time is really annoying here.</div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg"><br class="gmail_msg"></div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg">#3 I really like the fact that Discourse makes it very simple to get an overview of all the current discussion threads. For example, I opened the <a href="http://discourse.natecook.com/c/swift-evolution" class="gmail_msg" target="_blank">Swift Evolution</a> category and could see immediately all threads that I’m aware of since I saw new messages coming in my inbox – but many more, that I wasn’t aware of where discussion seem to have cooled down for a while. That’s really convenient!</div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg"><br class="gmail_msg"></div><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg">Mostly following the discussion is much simpler on Discourse, so my previous claim that it would solve all my problems seem to be true. I’d really like to see this getting to Discourse. Then I would even be able to send my fellow Swift developers links to discussions and they would actually read them – this would improve the quality of our internal best practice discussions a lot.</div></div><div style="word-wrap:break-word" class="gmail_msg"><div id="m_1931598832461846382m_-8553063925088057031bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto" class="gmail_msg"><br class="gmail_msg"></div> <div id="m_1931598832461846382m_-8553063925088057031bloop_sign_1486235156020719104" class="m_1931598832461846382m_-8553063925088057031bloop_sign gmail_msg"><div class="gmail_msg">-- <br class="gmail_msg">Cihat</div></div></div><div style="word-wrap:break-word" class="gmail_msg"> <br class="gmail_msg"><p class="m_1931598832461846382m_-8553063925088057031airmail_on gmail_msg">Am 4. Februar 2017 um 16:13:32, Ben Rimmington via swift-evolution (<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="m_1931598832461846382m_-8553063925088057031clean_bq gmail_msg"><span class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg">&gt; On 26 Jan 2017, at 18:02, Nate Cook wrote:<br class="gmail_msg">&gt; <br class="gmail_msg">&gt;&gt; On Jan 25, 2017, at 3:32 PM, Douglas Gregor wrote:<br class="gmail_msg">&gt;&gt; <br class="gmail_msg">&gt;&gt; I’ve looked into Discourse a bit, and it does look very promising. One *specific* way in which a motivated individual could help would be to take a look at Discourse’s import scripts and try importing swift-evolution’s mailing archives with them. We absolutely do not want to lose history when we switch technologies. Do the messages import well? Are threading and topics maintained in a reasonable manner? Does Discourse provide effective UI for looking into past discussions on some specific topic we’re interested in?<br class="gmail_msg">&gt; <br class="gmail_msg">&gt; ✋<br class="gmail_msg">&gt; <br class="gmail_msg">&gt; I forged the mighty, turgid rivers of rubyenv, hand-tweaked gem dependencies, and sed-cleaned mbox files to try this out—you can see the results of an import (using one or two day old data) at this address:<br class="gmail_msg">&gt;         <a href="http://discourse.natecook.com/" class="gmail_msg" target="_blank">http://discourse.natecook.com/</a><br class="gmail_msg"><br class="gmail_msg">Discourse doesn&#39;t properly import names with an acute accent:<br class="gmail_msg"><br class="gmail_msg">&lt;<a href="http://discourse.natecook.com/t/strings-in-swift-4/2980/77" class="gmail_msg" target="_blank">http://discourse.natecook.com/t/strings-in-swift-4/2980/77</a>&gt;<br class="gmail_msg">&lt;<a href="http://discourse.natecook.com/users/_utf-8_Q_F_C3_A9lix" class="gmail_msg" target="_blank">http://discourse.natecook.com/users/_utf-8_Q_F_C3_A9lix</a>&gt;<br class="gmail_msg"><br class="gmail_msg">I&#39;m not sure why &quot;=?utf-8?Q?F=C3=A9lix_Cloutier?=&quot; isn&#39;t automatically decoded by the Mail library:<br class="gmail_msg"><br class="gmail_msg">&lt;<a href="https://github.com/discourse/discourse/blob/f1e7bca3c92ea57f69e6ebb19f7fc75f188ab953/script/import_scripts/mbox.rb#L202-L205" class="gmail_msg" target="_blank">https://github.com/discourse/discourse/blob/f1e7bca3c92ea57f69e6ebb19f7fc75f188ab953/script/import_scripts/mbox.rb#L202-L205</a>&gt;<br class="gmail_msg">&lt;<a href="https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/fields/common/common_address.rb#L43-L47" class="gmail_msg" target="_blank">https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/fields/common/common_address.rb#L43-L47</a>&gt;<br class="gmail_msg">&lt;<a href="https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/elements/address.rb#L80-L88" class="gmail_msg" target="_blank">https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/elements/address.rb#L80-L88</a>&gt;<br class="gmail_msg">&lt;<a href="https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/encodings.rb#L99-L118" class="gmail_msg" target="_blank">https://github.com/mikel/mail/blob/5d9e3441b3efdee4c283093ab2872d017258b62d/lib/mail/encodings.rb#L99-L118</a>&gt;<br class="gmail_msg"><br class="gmail_msg">-- Ben<br class="gmail_msg"><br class="gmail_msg">_______________________________________________<br class="gmail_msg">swift-evolution mailing list<br class="gmail_msg"><a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg"></div></div></span></blockquote></div>_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div></div>