<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 Dec 14, 2015, at 3:48 PM, Brett Cannon <<a href="mailto:brett@python.org" class="">brett@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 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-stroke-width: 0px; float: none; display: inline !important;" class="">This also means neither GitHub or GitLab offer any specific benefit over each other from what I can tell (if we dropped unique NEWS entries and did cherry picks manually then I think GitLab EE gets us web-based squashing if I understand things properly). But this bot-based approach gets us the common-case managed entirely in the browser with a clean history.</span></div></blockquote></div><br class=""><div class="">Correct. You’re down to more nebulous things like “I like X’s UI better”, “X is more Free”, “X has a large community buy in” and such. Of course the downside is that we’d be diverging from the “normal” process for either tool so we’d be a bit special snowflake which increases the overhead for potential core developers… but I don’t think a bot command is a particularly onerous requirement for core developers to learn, and since it’s limited to just core developers it doesn’t affect the (hopefully) larger pool of external contributors.</div><div class=""><br class=""></div><div class="">Since Gitlab CE is OSS you could potentially modify it to have these things baked directly into it, but that feels like a less optimal solution than a bot since we’d be essentially forking it and then maintaining it ourselves. </div><div class="">
<br class="">-----------------<br class="">Donald Stufft<br class="">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br class=""></body></html>