Re: [pypy-dev] [Speed] Moving the project forward
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 whose credentials are shared among all the core devs. ciao, Anto ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
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 br...@python.org: On Thu, Sep 1, 2011 at 01:10, Nick Coghlan ncogh...@gmail.com wrote: On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni anto.c...@gmail.com 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 pypy we do exactly that. There is a bitbucket user named pypy whose credentials are shared among all the core devs. The security auditing part of my brain has its fingers in its ears and is singing La La La rather loudly :) What about Google Code? Projects there can have multiple owners and they support hg, have a tracker, and a wiki. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Speed mailing list sp...@python.org http://mail.python.org/mailman/listinfo/speed ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
On Thu, Sep 1, 2011 at 01:10, Nick Coghlan ncogh...@gmail.com wrote: On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni anto.c...@gmail.com 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 pypy we do exactly that. There is a bitbucket user named pypy whose credentials are shared among all the core devs. The security auditing part of my brain has its fingers in its ears and is singing La La La rather loudly :) What about Google Code? Projects there can have multiple owners and they support hg, have a tracker, and a wiki. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
-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 PSF server by hand if at all possible in the interests of disaster recovery, reproducibility, and some modicum of enforced documentation (even if that doc is just a Chef recipe). If Noah's going to pull this, being an Opscode guy, does it make sense for me to help out. I mean, he's the Chef guru here and I doubt there's little I can contribute then? -- Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | GPG: 2EAC625B Under this standard shalt thou conquer... ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
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 n...@coderanger.net: 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 infrastructure management effort. --Noah On Aug 31, 2011, at 11:34 AM, 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 bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things. Regarding the deployment strategy, it turns out I use Chef at work, so I am in full agreement with Noah here (yey!). Actually, I am the author of LittleChef (which we can use as a tool to execute Chef on the node). So, Configuration Management. I would propose that Noah starts the repo with the Chef cookbooks (preferably a complete LittleChef kitchen, but that is not a must :), and gets the main recipes (apache, django) going, while I create a cookbook for Codespeed. What do you think? The benchmark runner question is still open. We need to clarify that. Use the pypy runner? Tennessee's work? Regarding repositories and issues, we could maybe have a speed organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff. Cheers, Miquel 2011/8/31 Jesse Noller jnol...@gmail.com: I've put up a splash page for the project this AM: http://speed.python.org/ jesse ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev ___ Speed mailing list sp...@python.org http://mail.python.org/mailman/listinfo/speed ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
On Wed, Aug 31, 2011 at 11:34, Miquel Torres tob...@googlemail.com 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 bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things. [SNIP] Regarding repositories and issues, we could maybe have a speed organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff. 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. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
