+1 from me as well to anything that allows editing typos after posting. Charles
> On Jul 30, 2016, at 8:22 AM, Haravikk via swift-evolution > <[email protected]> wrote: > > But I like sending out my messages then regretting the many typos and > mistakes I only seem able to notice immediately after it's too late to do > anything about it! > > (so yeah, +1) > >> On 30 Jul 2016, at 12:39, Johannes Neubauer via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> +1 to move away from mail ;). >> >> Another player might be [Slack][0] or [teamwire][1] . Kotlin uses Slack >> extensively. >> >> [0]: https://slack.com/ <https://slack.com/> >> [1]: http://www.teamwire.eu/ <http://www.teamwire.eu/> >> >> Von meinem iPhone gesendet >> >> Am 30.07.2016 um 06:43 schrieb Muse M via swift-evolution >> <[email protected] <mailto:[email protected]>>: >> >>> I'm open to ZenHub that can be integrate as part of GitHub for discussion, >>> pull changes and it makes it easier to reference to the patches within >>> ZenHub than from Discourse or other forums. Swiftly right? >>> >>> https://www.zenhub.com <https://www.zenhub.com/> >>> >>> On Sat, Jul 30, 2016 at 10:10 AM, Tim Vermeulen via swift-evolution >>> <[email protected] <mailto:[email protected]>> wrote: >>> +1. Hirundo makes this format bearable, but it is still far from ideal. I >>> see many advantages for using Discourse: >>> >>> - It has actual syntax highlighting. >>> - It’s easier to moderate. >>> - It supports real-time updates. >>> - It’s easier to follow the flow of a conversation. >>> - It has better search. >>> >>> I don’t doubt more people will take part in the Swift evolution process if >>> we switch to Discourse. >>> >>> > Branching... >>> > >>> > On Fri, Jul 29, 2016 at 5:22 PM, Chris Lattner via >>> > swift-evolution<[email protected] >>> > <mailto:[email protected]>(mailto:[email protected] >>> > <mailto:[email protected]>)>wrote: >>> > > On Jul 29, 2016, at 5:14 PM, Brandon Knope<[email protected] >>> > > <mailto:[email protected]>(mailto:[email protected] >>> > > <mailto:[email protected]>)>wrote: >>> > > > >>> > > >Chris, has the core team discussed opening up a forum for discussing >>> > > >proposal implementations. >>> > > > >>> > > >Some of us aren't as skilled as the core team or other contributors >>> > > >but would like to learn. A forum is a much easier place for us to post >>> > > >for code help and to help others with their questions. I think this >>> > > >could help get more involved as it would be a more comfortable format >>> > > >for them. Think of how there are Apple Developer forums and not >>> > > >mailing lists for iOS betas etc. >>> > > > >>> > > >I am not saying moving swift-evo to forums *yet* but I believe a lot >>> > > >of the newer programmers are more comfortable with a forum format, >>> > > >especially when it comes to help and discussing code. >>> > > > >>> > > >Forums for contributors would: >>> > > >- be more familiar for a lot of the newer and not as experienced >>> > > >developers >>> > > >- be easier to search >>> > > >- be easier to moderate (not really a problem yet) >>> > > >>> > > Hi Brandon, >>> > > >>> > > Moving from email to a forum system has come up before, but they have >>> > > some disadvantages.One of major wins of email is that it is pervasive >>> > > and can be adapted into other forms.For example, if you haven’t seen it >>> > > yet, check out: >>> > > https://stylemac.com/hirundo/ <https://stylemac.com/hirundo/> >>> > > >>> > > -Chris >>> > > >>> > We've discussed forums on swift-evolution before. Maybe it's time for >>> > another go, with Swift 3 winding down. >>> > >>> > For context, prior discussions are on this >>> > thread:https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001537.html >>> > >>> > <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001537.html> >>> > >>> > (-1 for mailman: it's hard for me to even properly find&link to all the >>> > prior discussion about mailing lists, because of how mailman's archive >>> > works...) >>> > >>> > >>> > News in the last few days is that Gmane is at least temporarily >>> > disappearing:https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502 >>> > >>> > <https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502> >>> > >>> > >>> > I'd just like to vote once again >>> > forDiscourse(http://www.discourse.org/faq/#what):-Excellent >>> > <http://www.discourse.org/faq/#what):-Excellent> web >>> > interface(https://meta.discourse.org/ <https://meta.discourse.org/>), >>> > from the people who brought you Stack Overflow(built-in search, etc.) >>> > - Read via email if that's your thing: it has "mailing list mode" which >>> > includes 1-email-per-post, if that's your cup of tea >>> > -Reply via >>> > email(https://meta.discourse.org/t/replacing-mailing-lists-email-in/13099)if >>> > <https://meta.discourse.org/t/replacing-mailing-lists-email-in/13099)if> >>> > that's your thing >>> > - It'sopen source(https://github.com/discourse/discourse)itself >>> > <https://github.com/discourse/discourse)itself> >>> > - I believe it has ways of getting content as JSON and/or RSS, so I'd >>> > hardly say "can be adapted into other forms" is an exclusive feature of >>> > email. >>> > >>> > And, Discourse providesfree hosting for community-friendly open-source >>> > projects(http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/ >>> > >>> > <http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/>). >>> > Istrongly >>> > suspect(https://twitter.com/jtbandes/status/705886542309363712)Swift >>> > <https://twitter.com/jtbandes/status/705886542309363712)Swift> would >>> > qualify for this. >>> > >>> > >>> > There have been several people on this list arguing in favor of mailing >>> > lists — I encourage folks to go read the old thread for themselves. >>> > >>> > It's worth noting there are also plenty of voices that don't get heard on >>> > this list, because people just don't like using mailing lists. One >>> > example:https://twitter.com/pilky/status/755105431555608580_______________________________________________ >>> > >>> > <https://twitter.com/pilky/status/755105431555608580_______________________________________________> >>> > swift-evolution mailing list >>> > [email protected] <mailto:[email protected]> >>> > https://lists.swift.org/mailman/listinfo/swift-evolution >>> > <https://lists.swift.org/mailman/listinfo/swift-evolution> >>> > >>> > >>> > >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >>> >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] <mailto:[email protected]> >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
