<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 2, 2017, at 2:44 PM, Nevin Brackett-Rozinsky 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="">Where do you propose to hold and publicize such a vote in order that the people who would participate on a forum but not on a mailing list—ie. those for whom the switch will be most beneficial—are enfranchised?</div></blockquote><div><br class=""></div><div>The traditional method on a list like this is +1 or -1 in response to a given thread. (Note that I’m not calling for such a vote, as I have nothing to propose). A perhaps more modern approach would be to give a link to an external site that would run the vote/poll.</div><div><br class=""></div><div>As to your question of how to reach an audience larger than what we have now for a vote, I don’t see any obvious solution: the current community is what it is. And I would argue that the current community has invested the most time into the project (and likely will going forward) and should have the largest vote for how project communication should be facilitated. I wouldn’t advocate for advertising far and wide over the internet “how should the swift-evolution community communicate?”, as this would be a vote of the internet, and not of the swift-evolution community. I do admit you could argue the community may have already self-selected to some degree based on the current method of commutation; I see no real solution to that apart from continued advocacy from people such as you who are speaking up to bring awareness about the issues you feel are keeping outsiders from participating.</div><div><br class=""></div><div>James</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""></div><div class="">Nevin<br class=""><br class="">On Thursday, February 2, 2017, James Berry <<a href="mailto:jberry@rogueorbit.com" class="">jberry@rogueorbit.com</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
> On Feb 2, 2017, at 1:45 PM, Dave Abrahams via swift-evolution <<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')" class="">swift-evolution@swift.org</a>> wrote:<br class="">
><br class="">
>> On Feb 2, 2017, at 12:58 PM, Karl Wagner <<a href="javascript:;" onclick="_e(event, 'cvml', 'razielim@gmail.com')" class="">razielim@gmail.com</a>> wrote:<br class="">
>><br class="">
>> somebody build a parallel site to support the style of open community which the core-team seem unwilling/unable to do.<br class="">
><br class="">
> I don't think this is fair. We may not be moving as quickly as you'd like but we are looking into it.<br class="">
<br class="">
I would encourage everybody to remember that though there have been a vocal few advocating for something other than a mailing list, the question has never really been put to the community for a vote. I think it’s important to remember that while some people on list may be very vocal in advocating for a position, that doesn’t mean the majority of community members agree. At the least, such a matter should be put to a vote or poll once leading options have been identified.<br class="">
<br class="">
Speaking for myself only, discourse seems to give me little of value, while it would plaster emails with html-laden buttons, etc, thus making my favored experience worse than it is today. I’m fairly happy with using a gmail account and server-side filters to file my swift-evolution mails into a mailbox that I can then read on or offline with the threaded email client of my choice.<br class="">
<br class="">
James<br class="">
<br class="">
</blockquote></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>