Re: [pypy-dev] [Speed] Moving the project forward

2011-09-08 Thread Jesse Noller
PING: Did we make progress? On Thu, Sep 1, 2011 at 2:44 PM, Miquel Torres wrote: > You can also do that in Github, which I prefer. > > However, since CPython and PyPy use mercurial, the general preference > for Bitbucket is understandable. > > > 2011/9/1 Brett Cannon : >> On Thu, Sep 1, 2011 at 0

Re: [pypy-dev] [Speed] Moving the project forward

2011-09-01 Thread Brett Cannon
On Thu, Sep 1, 2011 at 01:10, Nick Coghlan wrote: > On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni wrote: >> On 31/08/11 22:11, Brett Cannon wrote: >>> >>> The PyPy folk could answer this as they have their repo on bitbucket >>> already. Else I guess we can just create a standalone account that >>>

Re: [pypy-dev] [Speed] Moving the project forward

2011-09-01 Thread Miquel Torres
You can also do that in Github, which I prefer. However, since CPython and PyPy use mercurial, the general preference for Bitbucket is understandable. 2011/9/1 Brett Cannon : > On Thu, Sep 1, 2011 at 01:10, Nick Coghlan wrote: >> On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni wrote: >>> On 31/08

Re: [pypy-dev] [Speed] Moving the project forward

2011-09-01 Thread Nick Coghlan
On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni wrote: > On 31/08/11 22:11, Brett Cannon wrote: >> >> The PyPy folk could answer this as they have their repo on bitbucket >> already. Else I guess we can just create a standalone account that >> represents the official speed.python.org account. > > for

Re: [pypy-dev] [Speed] Moving the project forward

2011-09-01 Thread Antonio Cuni
On 31/08/11 22:11, Brett Cannon wrote: The PyPy folk could answer this as they have their repo on bitbucket already. Else I guess we can just create a standalone account that represents the official speed.python.org account. for pypy we do exactly that. There is a bitbucket user named "pypy" wh

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Noah Kantrowitz
Its all branches all the way down, so we can start work anywhere and push it to an "official" PSF bin later I think. I'm sure we will want to host a mirror of it on the python.org hg server too, just for discoverability. --Noah On Aug 31, 2011, at 1:12 PM, Miquel Torres wrote: > Oh, cool, so t

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Brett Cannon
On Wed, Aug 31, 2011 at 11:34, Miquel Torres wrote: > Hi all, > > though I took up on the task of installing a Codespeed instance > myself, I didn't have time until now. This weekend I will definitely > have  a *lot* of time to work on this, so count on that task being > done by then. > > The bitb

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Noah Kantrowitz
Opscode has already agreed to donate a Hosted account as long we keep it under ~20 clients :-) I can hand out the info for it to anyone that wants. As for setting up the Chef repo, just remember we are trying to not manage this system in isolation and that it will be part of a bigger PSF infrast

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Miquel Torres
Oh, cool, so there will be an Opscode hosted account for the PSF, right? Then the Chef repo should be for the PSF. Maybe in a current account somewhere? What do you propose? Miquel 2011/8/31 Noah Kantrowitz : > Opscode has already agreed to donate a Hosted account as long we keep it > under ~20

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Jesse Noller
Noah is one person, yes you should help On Aug 31, 2011, at 3:43 AM, Jeroen Ruigrok van der Werven wrote: > -On [20110831 02:57], Noah Kantrowitz (n...@coderanger.net) wrote: >> Yahr, I be here. I would really like to see this done under a config >> management system (I prefer Chef and thats b

Re: [pypy-dev] [Speed] Moving the project forward

2011-08-31 Thread Jeroen Ruigrok van der Werven
-On [20110831 02:57], Noah Kantrowitz (n...@coderanger.net) wrote: >Yahr, I be here. I would really like to see this done under a config >management system (I prefer Chef and thats been the plan so far unless there >are heavy objections). In general no one should ever be changing things on any >