On Thu, Jan 8, 2015 at 12:59 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 6 December 2014 at 06:04, Brett Cannon bcan...@gmail.com wrote:
# Next steps
I'm thinking first draft PEPs by February 1 to know who's all-in (8 weeks
away), all details worked out in final PEPs and whatever is
I did a pull-request with current progress:
https://github.com/python/psf-salt/pull/25
Any feedback is appreciated.
Btw: Donald is very patient and helpful. :)
On Thu Jan 08 2015 at 8:00:59 AM Nick Coghlan ncogh...@gmail.com wrote:
On 6 December 2014 at 06:04, Brett Cannon bcan...@gmail.com
On Jan 8, 2015, at 4:26 AM, Tymoteusz Jankowski
tymoteusz.jankow...@gmail.com wrote:
I did a pull-request with current progress:
https://github.com/python/psf-salt/pull/25
https://github.com/python/psf-salt/pull/25
Any feedback is appreciated.
Btw: Donald is very patient and helpful.
On 6 December 2014 at 06:04, Brett Cannon bcan...@gmail.com wrote:
# Next steps
I'm thinking first draft PEPs by February 1 to know who's all-in (8 weeks
away), all details worked out in final PEPs and whatever is required to
prove to me it will work by the PyCon language summit (4 months
As I didn't hear any objections, I'm officially stating that I expect
initial draft PEPs to be in by February 1 to know who is in the running to
focus discussion. I then expect complete PEPs by April 1 so I can read them
before PyCon and have informed discussions while I'm there. I will then
plan
On Dec 11, 2014, at 9:59 AM, Brett Cannon bcan...@gmail.com wrote:
As I didn't hear any objections, I'm officially stating that I expect initial
draft PEPs to be in by February 1 to know who is in the running to focus
discussion. I then expect complete PEPs by April 1 so I can read them
Just adapt your current PEP.
On Thu Dec 11 2014 at 10:02:23 AM Donald Stufft don...@stufft.io wrote:
On Dec 11, 2014, at 9:59 AM, Brett Cannon bcan...@gmail.com wrote:
As I didn't hear any objections, I'm officially stating that I expect
initial draft PEPs to be in by February 1 to know who
Brett Cannon wrote:
4. Contributor creates account on bugs.python.org and signs the
[contributor agreement](https://www.python.org/psf/contrib/contrib-form/)
Is there an expiration on such forms? If there doesn't need to be
(and one form is good for multiple tickets), is there an objection
On Mon Dec 08 2014 at 3:27:43 PM Jim J. Jewett jimjjew...@gmail.com wrote:
Brett Cannon wrote:
4. Contributor creates account on bugs.python.org and signs the
[contributor agreement](https://www.python.
org/psf/contrib/contrib-form/)
Is there an expiration on such forms? If there
On Mon, 08 Dec 2014 12:27:23 -0800, Jim J. Jewett jimjjew...@gmail.com
wrote:
Brett Cannon wrote:
4. Contributor creates account on bugs.python.org and signs the
[contributor agreement](https://www.python.org/psf/contrib/contrib-form/)
Is there an expiration on such forms? If there
On Sat, Dec 6, 2014 at 7:23 PM, Wes Turner wes.tur...@gmail.com wrote:
On Sat, Dec 6, 2014 at 8:01 AM, Donald Stufft don...@stufft.io wrote:
One potential solution is Phabricator (http://phabricator.org) which is
a gerrit like tool except it also works with Mercurial. It is a fully open
This lists the ReviewBoard workflow steps for a pre-commit workflow:
https://www.reviewboard.org/docs/manual/dev/users/getting-started/workflow/
On Sat, Dec 6, 2014 at 7:55 PM, Wes Turner wes.tur...@gmail.com wrote:
On Sat, Dec 6, 2014 at 7:23 PM, Wes Turner wes.tur...@gmail.com wrote:
On Fri Dec 05 2014 at 3:24:38 PM Donald Stufft don...@stufft.io wrote:
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com wrote:
words
This looks like a pretty good write up, seems to pretty fairly evaluate
the various sides and the various concerns.
Thanks! It seems like I have
On Dec 6, 2014, at 8:45 AM, Brett Cannon bcan...@gmail.com wrote:
On Fri Dec 05 2014 at 3:24:38 PM Donald Stufft don...@stufft.io
mailto:don...@stufft.io wrote:
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com
mailto:bcan...@gmail.com wrote:
words
This looks like a
On Fri Dec 05 2014 at 8:31:27 PM R. David Murray rdmur...@bitdance.com
wrote:
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
wrote:
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
We don't exactly have a ton of people
constantly going I'm
On Sat Dec 06 2014 at 2:53:43 AM Terry Reedy tjre...@udel.edu wrote:
On 12/5/2014 3:04 PM, Brett Cannon wrote:
1. Contributor clones a repository from hg.python.org
http://hg.python.org
2. Contributor makes desired changes
3. Contributor generates a patch
4. Contributor creates
On Fri Dec 05 2014 at 5:17:35 PM Eric Snow ericsnowcurren...@gmail.com
wrote:
Very nice, Brett.
Thanks!
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
And we can't forget the people who help keep all of this running as well.
There are those that manage the SSH
On Dec 6, 2014, at 9:11 AM, Brett Cannon br...@python.org wrote:
On Fri Dec 05 2014 at 8:31:27 PM R. David Murray rdmur...@bitdance.com
mailto:rdmur...@bitdance.com wrote:
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
mailto:ericsnowcurren...@gmail.com
On 7 December 2014 at 01:07, Donald Stufft don...@stufft.io wrote:
A likely solution is to use a pre-merge test runner for the systems that we
can isolate which will give a decent indication if the tests are going to
pass across the entire supported matrix or not and then continue to use the
On 7 December 2014 at 00:11, Brett Cannon br...@python.org wrote:
On Fri Dec 05 2014 at 8:31:27 PM R. David Murray rdmur...@bitdance.com
wrote:
That's probably the biggest issue with *anyone* contributing to tracker
maintenance, and if we could solve that, I think we could get more
people
On Sat Dec 06 2014 at 10:07:50 AM Donald Stufft don...@stufft.io wrote:
On Dec 6, 2014, at 9:11 AM, Brett Cannon br...@python.org wrote:
On Fri Dec 05 2014 at 8:31:27 PM R. David Murray rdmur...@bitdance.com
wrote:
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow
On Sat Dec 06 2014 at 10:30:54 AM Nick Coghlan ncogh...@gmail.com wrote:
On 7 December 2014 at 00:11, Brett Cannon br...@python.org wrote:
On Fri Dec 05 2014 at 8:31:27 PM R. David Murray rdmur...@bitdance.com
wrote:
That's probably the biggest issue with *anyone* contributing to tracker
On Dec 6, 2014, at 10:26 AM, Nick Coghlan ncogh...@gmail.com wrote:
On 7 December 2014 at 01:07, Donald Stufft don...@stufft.io wrote:
A likely solution is to use a pre-merge test runner for the systems that we
can isolate which will give a decent indication if the tests are going to
pass
On 12/6/2014 10:26 AM, Nick Coghlan wrote:
On 7 December 2014 at 01:07, Donald Stufft don...@stufft.io wrote:
A likely solution is to use a pre-merge test runner for the systems that we
can isolate which will give a decent indication if the tests are going to
pass across the entire supported
On Sat, Dec 6, 2014 at 8:01 AM, Donald Stufft don...@stufft.io wrote:
One potential solution is Phabricator (http://phabricator.org) which is a
gerrit like tool except it also works with Mercurial. It is a fully open
source platform though it works on a “patch” bases rather than a pull
On Sat, Dec 6, 2014 at 9:07 AM, Donald Stufft don...@stufft.io wrote:
Heh, one of my thoughts on deploying the bug tracker into production was
via a container, especially since we have multiple instances of it. I got
side tracked on getting the rest of the infrastructure readier for a web
On Sat, Dec 6, 2014 at 7:27 PM, Wes Turner wes.tur...@gmail.com wrote:
On Sat, Dec 6, 2014 at 9:07 AM, Donald Stufft don...@stufft.io wrote:
Heh, one of my thoughts on deploying the bug tracker into production was
via a container, especially since we have multiple instances of it. I got
This is a bit long as I espoused as if this was a blog post to try and give
background info on my thinking, etc. The TL;DR folks should start at the
Ideal Scenario section and read to the end.
P.S.: This is in Markdown and I have put it up at
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com wrote:
words
This looks like a pretty good write up, seems to pretty fairly evaluate the
various sides and the various concerns.
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Very nice, Brett.
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
And we can't forget the people who help keep all of this running as well.
There are those that manage the SSH keys, the issue tracker, the review
tool, hg.python.org, and the email system that let's use
On Dec 5, 2014 4:18 PM, Eric Snow ericsnowcurren...@gmail.com wrote:
Very nice, Brett.
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
And we can't forget the people who help keep all of this running as
well.
There are those that manage the SSH keys, the issue
On 6 December 2014 at 06:24, Donald Stufft don...@stufft.io wrote:
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com wrote:
words
This looks like a pretty good write up, seems to pretty fairly evaluate the
various sides and the various concerns.
Agreed - thanks for taking this on
Hi All
I just want to put my two cents into this.
This would definitely be a great step to take. I have been discussing PEP
462 with Nick, and the automation was definitely something that would be
something that would be great to have - I mean, I was submitting a simple
documentation patch for
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
wrote:
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
We don't exactly have a ton of people
constantly going I'm so bored because everything for Python's development
infrastructure gets sorted
On Dec 5, 2014, at 8:26 PM, R. David Murray rdmur...@bitdance.com wrote:
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
wrote:
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
We don't exactly have a ton of people
constantly going I'm so
On 6 December 2014 at 11:39, Donald Stufft don...@stufft.io wrote:
Maybe our infrastructure folks will have a thought or two about this?
I'm willing to put some work into this if we can figure out what
direction to head in. It could well be tied in to moving
bugs.python.org in with the rest
On 12/5/2014 3:04 PM, Brett Cannon wrote:
1. Contributor clones a repository from hg.python.org http://hg.python.org
2. Contributor makes desired changes
3. Contributor generates a patch
4. Contributor creates account on bugs.python.org
http://bugs.python.org and signs the
[contributor
37 matches
Mail list logo
