<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=""><div class="">But does it already surpass the limits?</div><div class=""><br class=""></div><blockquote type="cite" class=""><span class="Apple-tab-span" style="white-space: pre;">        </span>• There is a bandwidth limit of 100k monthly page views, equivalent to our Standard hosting plan.<br class=""><span class="Apple-tab-span" style="white-space: pre;">        </span>• If you exceed our bandwidth limit – which is very unlikely, unless your project is enormous – you have two options:<br class=""><span class="Apple-tab-span" style="white-space: pre;">                </span>• We’ll help you move to self-hosting, either on your own server or any Docker compatible cloud (a $20/month Digital Ocean droplet should suffice).<br class=""><div class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre">                </span>• Upgrade to our Business hosting plan at 50% off.</div></div></div></blockquote><div class=""><div class=""></div></div><div class=""><br class=""></div><div class="">I wouldn’t be surprised if it’s close if not passed 100k monthly views already. </div><div class=""><br class=""></div><div class="">The big unknown is also around the mailing list support. Is it super robust and work as well for communicating as the mailing currently does? I don’t know. I’ve not been involved with large projects on discourse.</div><div class=""><br class=""></div><div class="">-David</div><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 3, 2016, at 1:34 PM, Jacob Bandes-Storch 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=""><div dir="ltr" class="">As I mentioned at the top of this thread, <span style="font-size:12.8px" class="">Discourse provides </span><a href="http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/" target="_blank" style="font-size:12.8px" class="">free hosting for community-friendly open-source projects</a> which I suspect would include Swift<span style="font-size:12.8px" class="">. If not, that would indeed throw a wrench in the idea.</span><div class="gmail_extra">
<br class=""><div class="gmail_quote">On Wed, Aug 3, 2016 at 1:30 PM, Daniel Duan via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I’d rather the core team work on the language, stdlib and the compiler. Wouldn’t you agree?<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
> On Aug 3, 2016, at 12:59 PM, Brandon Knope via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">
><br class="">
> I wasn't expecting someone else to do it! This would need to be supported by the core team 100%<br class="">
><br class="">
> Brandon<br class="">
><br class="">
>> On Aug 3, 2016, at 3:42 PM, David Owens II <<a href="mailto:david@owensd.io" class="">david@owensd.io</a>> wrote:<br class="">
>><br class="">
>><br class="">
>>> On Aug 3, 2016, at 5:21 AM, Brandon Knope via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>>><br class="">
>>> I still think it is worth doing a test to see how everyone likes it:<br class="">
>><br class="">
>> Even if it is better, someone if going to have to either maintain the server and install of discourse _or_ pay discourse to host it. Until someone on the core team agrees to those terms, what’s the point really?<br class="">
>><br class="">
>> Has anyone looked into the possibility of extending discourse’ mail support to feed into discourse instead? Then discourse would be the view layer instead of trying to the the truth of the data.<br class="">
>><br class="">
>> -David<br class="">
> _______________________________________________<br class="">
> swift-evolution mailing list<br class="">
> <a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</div></div></blockquote></div><br class=""></div></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>