sorted by: recent | see :
popular
Content Tagged with sprint + python
Plone Paris Sprint wrapup #3, new.plone.org, collective.dist released !
and provide a way for other developers to build the application on their own, by:
Plone Paris Sprint wrapup, part #2: collective.buildbot released !
$ cd /tmp/
$ mkdir my_bot
$ cd my_bot/
$ svn co https://ingeniweb.svn.sourceforge.net/svnroot/ingeniweb/buildbot/trunk .
$ python bootstrap.py
$ bin/buildout
$ bin/master start
$ bin/linux_debian start (that's our slave)
Pimp my buildbot !
[buildout]
parts =
buildmaster
linux_debian
[buildmaster] recipe = iw.recipe.buildmaster project-name = Ingeniweb Public buildbot project-url = http://ingeniweb.com port = 8999 wport = 9000 url = http://buildbot.ingeniweb.com slaves = linux_debian xxxxx projects = iw.recipes
[linux_debian] recipe = iw.recipe.buildslave host = localhost port = ${buildmaster:port} password = xxxx
[iw.recipes] slave-name=linux_debian base-url=http://ingeniweb.svn.sourceforge.net repository=/svnroot/ingeniweb/projects/iw.recipes/ branch=buildout build-sequence = python bootstrap.py bin/buildout
test-sequence = bin/test -v –exit-with-status
Plone Paris sprint D-30
so this is a good opportunity to do a Python european tour
Snow sprint report #1 : indexing
So we are here in Austria, sprinting on Zope and Plone (thanks to Lovely Systems). I have proposed a task on building an alternative indexer system for Plone. So, we worked with Dokai and Tom on this. Those guys rock, really !
Our goal was to create a plone 3 buildout that provides an out of [...]
tarek
I’m really excited about this: we are organizing a Plone sprint in Paris in April at Ingeniweb headquarters !
No topics are planned yet because it depends a lot on who will be able to come. This will be done throughout January.
Please join the project and its mailing list if you are interested:
http://www.openplans.org/projects/plone-3-paris-sprint/project-home
And do not hesitate [...]
Updates from the Latest Python Sprint
Google was pleased to host last week's Python Sprint. From August 22-25th, over twenty developers in Mountain View and Chicago came together to improve next generation Python, also known as Python 3000 or Py3k. Many of the participants got their initial taste of Python internals at the sprint.
There was a flurry of activity at the sprint, and over 100 changes were committed - about five times the normal rate! The team got so much done that you can expect the first alpha release of Py3k in a few days.
If you'd like to participate in Python development or just learn more about the project, check out their general developer's mailing list or the Py3k development mailing list.
The Mountain View Python Sprint Team (starting with the back row, left to right): Larry Hastings, Tom Waite, Ero Carrera, Guido van Rossum, Collin Winter, Bill Janssen, Yuri Ginsburg, Thuon Chen, Christopher Burns, Keir Mierle, Neal Norwitz
(photo credit: Paul Dubois)
Updates from the Latest Python Sprint
Google was pleased to host last week's Python Sprint. From August 22-25th, over twenty developers in Mountain View and Chicago came together to improve next generation Python, also known as Python 3000 or Py3k. Many of the participants got their initial taste of Python internals at the sprint.
There was a flurry of activity at the sprint, and over 100 changes were committed - about five times the normal rate! The team got so much done that you can expect the first alpha release of Py3k in a few days.
If you'd like to participate in Python development or just learn more about the project, check out their general developer's mailing list or the Py3k development mailing list.
The Mountain View Python Sprint Team (starting with the back row, left to right): Larry Hastings, Tom Waite, Ero Carrera, Guido van Rossum, Collin Winter, Bill Janssen, Yuri Ginsburg, Thuon Chen, Christopher Burns, Keir Mierle, Neal Norwitz
(photo credit: Paul Dubois)
