[core-workflow] Questions about the proposed workflows

[Donald Stufft]

> On Dec 14, 2015, at 3:48 PM, Brett Cannon <brett at python.org> wrote:
> 
> 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.

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.

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.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20151214/2c298104/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20151214/2c298104/attachment.sig>