Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #101120 > unrolled thread
| Started by | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| First post | 2016-01-01 15:08 -0600 |
| Last post | 2016-01-01 15:08 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 15:08 -0600
| From | Zachary Ware <zachary.ware+pylist@gmail.com> |
|---|---|
| Date | 2016-01-01 15:08 -0600 |
| Subject | Re: We will be moving to GitHub |
| Message-ID | <mailman.150.1451682524.11925.python-list@python.org> |
On Fri, Jan 1, 2016 at 2:03 PM, <paul.hermeneutic@gmail.com> wrote: > Is there a summary document that discusses the options examined and why > others did not meet the requirements? I am -NOT- trying to dredge up > arguments about the choice. I am guessing that there have been some. Easiest would be to look through the archives of the core-workflow mailing list: https://mail.python.org/pipermail/core-workflow/ > If this fact-based decision was based solely on the fact that the BDFL > prefers GitHub, please just say so. It is clear that git is a capable tool. There were three reasons given in Brett's decision message: 1. No major distinguishing features between GitHub or GitLab Note that GitHub and GitLab were the only proposals under consideration; nobody else stepped up to champion any other solution. 2. Familiarity amongst core devs -- and external contributors -- with GitHub 3. Guido prefers GitHub Guido repeatedly stated that his preference should not be taken into account. I believe Brett gave it little weight, but obviously it was in his mind. -- Zach
Back to top | Article view | comp.lang.python
csiph-web