<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 Aug 8, 2017, at 3:06 PM, Erica Sadun 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 class="Singleton" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><blockquote type="cite" class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">I imagine that the core team will assist in providing implementations for proposals that are crucial to the progress of the language and/or highly popular — regardless of whether the proposal was authored by the core team or a community member.</div><div class=""><br class=""></div><div class="">From what I know of the team, they’re not going to let a good idea languish just because of the name that’s in the author field. I’m sure they _are_ going to strategically prioritize what gets attention, and that’s not a bad thing.</div></div></div></blockquote><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></div><div class="">Perhaps I'm being overly optimistic but I see this change as enhancing collaboration between idea-level and code-level evolution. Requiring a preliminary implementation:</div></div></div></blockquote></div><br class=""><div class="">This change is also intended to strengthen the community in two other ways:</div><div class=""><br class=""></div><div class="">1) a person or organization sufficiently motivated and able to push an effort forward can now do it, even if it is outside the scope of Apple’s current priorities.</div><div class=""><br class=""></div><div class="">2) it encourages more folks to get involved in implementation tasks, by providing an incentive to do so.</div><div class=""><br class=""></div><div class="">Hopefully both of these will lead to a broader and stronger Swift community.</div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>