Skip to content

Pyramid Summer Sprint in Halle (DE) August 2013

Jump to bottom Edit New page
Veit Schiele edited this page Aug 16, 2013 · 21 revisions

Pyramid Summer Sprint in Halle, Germany, August 2013

Sprint Topics

Feel free to add your own topics! If you plan on helping with an existing topic, please add yourself below.

Fix bugs / provide enhancements in Pyramid/Pylons libraries

  • Chris McDonough (mcdonc)
  • Andi Zeidler (witsch)
  • Tom Lazar (tomster)

The following packages require bug triage. Many of them have issues that are marked as "sprintable", which means it should be possible for a normal human being to verify that the issue is a bug and possibly provide a pull request to fix the issue. Unfortunately in GitHub, pull requests cannot be marked with labels, so there are also items not marked as "sprintable" but which are technically sprintable, because code has already been provided; these just need someone to verify that the pull requests do what they say they do, fix an actual problem, and have associated hair such as a changelog entry and a CONTRIBUTORS.txt addition.

See http://docs.pylonsproject.org/en/latest/#contributing for general Pylons Project coding standards and idioms.

pyramid (https://github.com/Pylons/pyramid/issues?page=1&state=open)

substanced (https://github.com/Pylons/substanced/issues?direction=desc&sort=created&state=open)

webob (https://github.com/Pylons/webob/issues?direction=desc&sort=created&state=open)

pyramid_debugtoolbar (https://github.com/Pylons/pyramid_debugtoolbar/issues?direction=desc&sort=created&state=open)

colander (https://github.com/Pylons/colander/issues?direction=desc&sort=created&state=open)

deform (https://github.com/Pylons/deform/issues?state=open)

pyramid_deform (https://github.com/Pylons/pyramid_deform/issues?state=open)

waitress (https://github.com/Pylons/waitress/issues?state=open)

pyramid_jinja2 (https://github.com/Pylons/pyramid_jinja2/issues)

webtest (https://github.com/Pylons/webtest/issues)

pyramid_ldap (https://github.com/Pylons/pyramid_ldap/issues?state=open)

venusian (https://github.com/Pylons/venusian/issues?direction=desc&page=1&sort=created&state=open)

translationstring (https://github.com/Pylons/translationstring/issues)

pyramid_handlers (https://github.com/Pylons/pyramid_handlers/issues)

supervisor (https://github.com/Supervisor/supervisor/issues?state=open)

Managing development environments with Batou

  • Christian "Theuni" Theune

batou is gocept's utility to manage deployments. Besides deploying to server environments like "staging" and "production" it is also able to deploy locally.

As a developer the situation isn't completely broken but quiet awkward in some places:

  • Manage system-level components (MySQL, PostgreSQL) gracefully, integrate startup/shutdown with project-specific supervisor
  • Manage checkouts of code in a nice way: we end up with too much duplication in application and library buildouts, especially test configuration, also, paths become way too deep many times
  • Think about mr.developer usage.
  • Think about the interaction between library packages/repositories, application packages/repositories, and deployment packages/repositories
  • Think about integrating with vagrant
  • Think about allow scripting batou's own bootstrapping to support very barren target environments
  • Think about 'pseudo hosts' to allow assigning components that live in unmanaged places
  • Think about debugging: better output, especially with dependency problems and NonConvergingWorkingSet.
  • Look at the situation in other projects: Django? Ruby on Rails? How do the Java guys do this? Microsoft?

Extract best practices for Pyramid SQLAlchemy applications into some libraries and a more advanced SQLAlchemy scaffold.

  • Daniel Havlik

generate colander/deform schemas from sqlalchemy models (admin interface)

Building forms in JavaScript

  • Sebastian Wehrmann

What are the best practices to build forms on the users client with the server being only the datastore and validation machine? I'd like to implement some use cases with jQuery, AngularJS, … and pyramid as the server component. My goal is to find out the "best" way how to implement client side forms and to extract code snippets and/or tools for reuse.

Try to use legacy zope.testrunner layers with py.test to facilitate gradual migration

  • Thomas Lotze

Once this works, an interesting application would be to have flaky gocept.selenium tests be run multiple times until success or repeated failure. If it turns out that py.test and layers cannot be combined at all, some other way of having flaky selenium tests repeated might be a worthy topic for the remaining sprint time.

Advanced error logging / ubiquituous graphing

  • Christian Kauhaus
  • Wolfgang Schnerring

Schedule

Thursday, 15th

  • 10:00 CEST – Sprint starts
  • 18:00 CEST – BBQ

Friday, 16th

  • 09:00 CEST – Sprint starts
  • 18:30 CEST – city ​​tour (Meeting point: 18:00 gocept or 18:30 Marktschlösschen/Tourist information, Martkplaltz 13)
  • 19:30 CEST – Dinner (http://www.daluca-halle.de/ reserved for «pyramid»)

Saturday, 17th

  • 09:00 CEST – Sprint starts
  • 16:00 CEST – gocept summer garden party

Sunday, 18th

  • "Family day"
  • Join us for a relaxed after-sprint and after-party in our garden. Get some breakfast, coffee, and say "bye" to everyone.
Add a custom footer
Add a custom sidebar
Clone this wiki locally