<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=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 12, 2016, at 7:50 AM, Михаил Страшун via dmd-internals <<a href="mailto:dmd-internals@puremagic.com" class="">dmd-internals@puremagic.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Proposal<br class="">--------<br class=""><br class="">I have described my vision of new process here:<br class=""><a href="https://github.com/Dicebot/DIPs" class="">https://github.com/Dicebot/DIPs</a> , check<br class=""><a href="https://github.com/Dicebot/DIPs/blob/master/README.md" class="">https://github.com/Dicebot/DIPs/blob/master/README.md</a> for actual<br class="">description.<br class=""><br class=""></div></div></blockquote></div><br class=""></div><div class="">Regarding the “draft” stage, I think “draft” really can just be PR. I think we should not involve a separate system (i.e. D wiki) for this process at all.</div><div class=""><br class=""></div><div class="">If you give permission to others to pull or reject the drafts, it’s likely Walter/Andrei never see frivolous or unworkable PRs. Essentially, we can collectively screen such DIPs to lessen the burden of the DIP manager himself, leaving the task of managing the DIPs past draft.</div><div class=""><br class=""></div><div class="">DIPs aren’t happening 10 a day, like PRs or bug requests, so we can probably find time to review them.</div><div class=""><br class=""></div><div class="">I’d say a DIP draft should not be pulled for at least 1 week (month?) to allow others to provide feedback (overrides by W/A of course are possible).</div><div class=""><br class=""></div><div class="">Note that this will be a huge improvement over the current DIP system where the DIP itself retains prominence in the wiki, but the discussion around it generally happens lost in the forums. Having comments/discussion right in the PR is a huge improvement.</div><div class=""><br class=""></div><div class="">I’ll point out that Apple uses github for swift community-driven language improvements, with pretty good success (not that I agree with all the improvements): <a href="https://github.com/apple/swift-evolution" class="">https://github.com/apple/swift-evolution</a> .</div><div class=""><br class=""></div><div class="">-Steve</div></body></html>