<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>Hi there,</p>
<p>you’re a bit too late. A forum will come at some point (Discourse).</p>
<p>Best regards,</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_1493638307089789952" 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 1. Mai 2017 um 13:30:55, Mohamed Ebrahim Afifi 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>
<title></title>
<div dir="ltr">
<div>Hi,</div>
<div><br></div>
<div>This is actually not a proposal to improve Swift, it is
actually a proposal to improve the way we use it to improve Swift.
:)</div>
<div><br></div>
<div>It is extremely hard to monitor discussions going over
e-mails.</div>
<div>
<ol>
<li>I always get lost between e-mails especially if there are so
many replies</li>
<li>It is extremely hard to reach the original idea/first
e-mail.<br></li>
<li>New people (like me) usually get lost between e-mails and only
focus on their own idea and don't care about other's ideas because
for example, I don't know how to reply to an idea if I'm not
subscribed to the mailing list. In other words, It’s not a system
that encourages follow-up actions.</li>
<li>You can not browse subjects and all replies in one place.</li>
<li>You cannot follow a specific topic and ignore others.</li>
</ol>
<div>That was the problem! </div>
</div>
<div><br></div>
<div>My suggestion is to move all discussions from this
mailing list to GitHub issues. For the following
reasons.</div>
<div>
<ol>
<li>Easier to browse all topics.</li>
<li>You can see open topics and closed topics. So, if a topic is
done we can close it.</li>
<li>You can subscribe to a topic and follow all replies and
reply. </li>
<li>Markdown support. Currently, I see people create a markdown
page on Github and send a link to it on the mailing list. But
having the markdown inline in the topic is a great benefit. Also,
replies can be in markdown as well.</li>
<li>It's closer to Proposals (Since we already using Github for
tracking proposals why don't we use it also to track pitching
ideas). People like to have everything gathered together in one
place and don't need to remember the Github repo and mailing
list.</li>
<li>Github has <a href="https://developer.github.com/v3/issues/">https://developer.github.com/v3/issues/</a> </li>
</ol>
<div><br></div>
</div>
<div>I think using Github issues instead of the mailing lists will
increase the engagement of the Swift community with
proposals.</div>
<div><br></div>
<br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Best Regards,
<div>Mohamed Afifi</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<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>