<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>What happened to that talk? Were any decisions made internally? Any news?</p>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1475865769672791040" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 21. August 2016 um 17:36:53, Michie via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Incase, the Swift team decided to use a forum.<br><br>I would like to suggest Discourse (http://www.discourse.org).<br>It is one of the most reliable open-source made forum and most <br>companies have been using it as their forum/community eg. Dockers, <br>Let's Encrypt, etc...<br><br>The Swift Team has a choice to host it on their own or pay <br>discourse.org to host it for you. Hosting on their own would be more <br>cheaper and gives you more control on how you want it to be set up. We <br>can easily set up a mailing list to all the people watching the <br>discussion and you can add in your own style of Authentication if <br>needed.<br><br>Slack will be very expensive because Slack cost almost $7 per active <br>member per month. If you don't pay, it will definitely be limiting. <br>Also, I don't think using chat for this kind of project will be more <br>productive as people need to revisit some discussions.<br><br>I can help the Swift Team set up Discourse if they are interested and <br>they can create a subdomain: https://community.swift.org for it.<br><br>Let me know.<br><br>Michie :)<br><br>Quoting Sean Alling via swift-evolution <swift-evolution@swift.org>:<br><br>> +1<br>><br>> I think this is a great idea! The use of a mailing list is <br>> manageable for a small (2-10) groups but doesn’t scale to the size <br>> and frequency of comments/replies that the Swift Open Source project <br>> has seen thus far. Not to mention, it reeks of 1996.<br>><br>> I’m not sure if we should authenticate users via AppleID, because we <br>> want the Swift community to remain cross-platform going forward.<br>><br>> A Slack would be a great idea, for banter but may get crazy. We <br>> would want the slack channels to remain subject pure (i.e., no <br>> shenanigans). Email is good in this regard in that a reply is <br>> expensive and therefore on-topic, whereas slack replies are cheap <br>> and therefore easily off topic. Anyone have any idea to combat that? <br>> Code of Conduct?<br>><br>> I think in making this decision we should separate the determination <br>> that the mailing lists are posing too great a burden at our scale <br>> from the selection of what we should use in its stead.<br>><br>> - Sean<br>><br>><br>>> I think this thread should focus on the mailing list vs forum, Slack is<br>>> not a forum. It could be nice to have it as an extra if we need it.<br>>><br>>> It looks to me that all benefits of a mailing list can be achieved by a<br>>> forum system with excellent support to read and reply using emails. But<br>>> the opposite is not true, one single simple example: we can't even link<br>>> related thread using email (as Tino mentioned on the Gmane thread).<br>>><br>>><br>>><br><br><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>