[core-workflow] workflow proposal update: Xmas week edition
Brett Cannon
brett at python.org
Mon Dec 21 14:45:23 EST 2015
Just wanted to sum up where I think everything stands as we approach
January 1.
First, everyone seems to like the bot idea for managing pull requests. It
should buy us easier cherry-picking across branches as well as
fast-forward/rebasing PRs so we get a linear history. And all of this done
through the browser. It can also help automate things such as Misc/NEWS and
Misc/ACKS. Plus it buys us workflow independence from our hosting platform
since the bot will be what needs changing if we change hosts in the future
and not how our overall workflow works. Wins for everyone! It also won't be
a blocker on switching since everything being proposed can be done
manually. And I will be pushing for a Monty Python and the Holy Grail black
knight reference for the bot's name and trigger command (black-knight or
none-shall-pass are tied in my head).
Second, my email asking if anyone would walk away from contributing to
Python if we switched to GitHub resulted in *no one* stepping forward. I
actually got an equal number of "I'd prefer not to use GitHub, but I won't
stop contributing" compared to "please choose GitHub" emails. And in the
end there were more emails wanting clarification on the intended tone of
the email than on the topic itself. So switching to GitHub won't impede
development due to its closed source nature.
Third, Guido asked what GitLab offers over GitHub to win over the network
and familiarity effect that GitHub offers. I don't remember a direct reply
to that email yet so if there is something to be pointed out beyond
GitLab's open source nature or ability for us to host our own instance if
something were to happen to GitLab then please let it be known.
I think that's everything up to this point. I'm still hoping we can figure
out all the hosting issues before January 1 so I can make a decision by
then.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20151221/107ecc90/attachment.html>
More information about the core-workflow
mailing list