[swift-evolution] [Swift4] Mailing list vs. Forum

[Daniel Duan]

Keep in mind: switching to a different set of tools would create disruptions to the core team’s workflow. Context switch is expensive and perhaps hard to understand from outside. Quite a few core team members are active participants of mailing lists out side of Swift.org (yes, those indeed exist! e.g. llvm). So to use a another set of tool, as we say here, is *purely additive* to a lot of folks. I can’t speak for the team, but the fact that we are here is a strong indication of their preference. Unless you are unsatisfied with the Swift 3 process/outcome, I’d the mailing list has proven to be working fantastically.
> On Aug 3, 2016, at 1:34 PM, Jacob Bandes-Storch <jtbandes at gmail.com> wrote:
> 
> As I mentioned at the top of this thread, Discourse provides free hosting for community-friendly open-source projects <http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/> which I suspect would include Swift. If not, that would indeed throw a wrench in the idea.
> 
> On Wed, Aug 3, 2016 at 1:30 PM, Daniel Duan via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> I’d rather the core team work on the language, stdlib and the compiler. Wouldn’t you agree?
> 
> > On Aug 3, 2016, at 12:59 PM, Brandon Knope via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> >
> > I wasn't expecting someone else to do it! This would need to be supported by the core team 100%
> >
> > Brandon
> >
> >> On Aug 3, 2016, at 3:42 PM, David Owens II <david at owensd.io <mailto:david at owensd.io>> wrote:
> >>
> >>
> >>> On Aug 3, 2016, at 5:21 AM, Brandon Knope via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
> >>>
> >>> I still think it is worth doing a test to see how everyone likes it:
> >>
> >> 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?
> >>
> >> 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.
> >>
> >> -David
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> > https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160803/eb89d6e6/attachment.html>