[swift-evolution] Community Proposal: "This Week In Swift" newsletter

Chris Lattner clattner at apple.com
Wed Dec 23 01:04:30 CST 2015


> On Dec 22, 2015, at 9:29 PM, Kevin Ballard via swift-evolution <swift-evolution at swift.org> wrote:
> 
> During the development of Rust prior to v1.0, one of the things that really helped with keeping up with changes (both in the language and in the stdlib) was Corey Richardson's weekly newsletter/blog titled This Week In Rust. Since 1.0, that was actually turned into its own website at https://this-week-in-rust.org and appears to still be going strong (although I assume someone else has taken over responsibility at this point).

This would be really great to see.  Here is another point of reference, "LLVM Weeklyā€¯:
http://llvmweekly.org

-Chris

> 
> What Corey did with This Week In Rust was he went through all the pull requests that were merged in the past week, found the "important" ones, and compiled a list of one-line summaries that linked to each PR in question. He made sure to call out any breaking changes (this was pre-1.0 so there were breaking changes almost every week) as well as anything that seemed like it would be of interest to people looking for a weekly summary. He also listed RFCs (Rust's equivalent for our swift-evolution proposals) as well as any interesting news from the community (such as new projects or libraries). This weekly newsletter was posted on his blog and also posted on the Rust mailing list. I'm really not sure where he got all the time to do this (I believe he was studying at University at the time), and I don't know how much time it actually took, but it was widely regarded as being extremely helpful.
> 
> I'd really love to see someone with enough time on their hands start up something similar for Swift. This would include interesting or important changes to the language/stdlib as well as news about proposals (e.g. newly-submitted ones, ones up for review in the coming week, the accepted/rejected resolution of them, and finally news about when implementations get merged in). Ideally, Apple would actually pay someone to do this, but I suspect it's unlikely that there's anyone involved with Swift at Apple that has the time for something like this. And of course I don't have time for this myself (that's why I want the newsletter, so I can make sure I don't miss anything important!).
> 
> -Kevin Ballard
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution



More information about the swift-evolution mailing list