Grokkerdam sprint
Reports, accomplishments, releases, blogs
From the mailinglist:
- http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/4716
- http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/4713
- http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/4705
- http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/4672
Reinout van Rees did a lot of reporting and created nice impressions:
- http://vanrees.org/weblog/archive/2008/05/02/quick-intermediary-grokkerdam-sprint-roundup
- http://vanrees.org/weblog/archive/2008/05/01/some-presentations-at-the-end-of-the-second
- http://photos.reinout.vanrees.org/gallery/4836966_693t8#287920926_nAPcp
- http://vanrees.org/weblog/archive/2008/05/02/philipp-von-weitershausen-grok-and-wsgi
- http://vanrees.org/weblog/archive/2008/05/01/grok-sqlalchemy-and-traversal
- http://photos.reinout.vanrees.org/gallery/4836966_693t8/1/#288419030_Hm6wm-A-LB (1.5 min video)
Other impressions:
Other blog entries:
- http://maurits.vanrees.org/weblog/archive/2008/04/a-grok-tour-and-todo
- http://maurits.vanrees.org/weblog/archive/2008/05/grok-sprint-wrapup-sunday
Releases made:
- http://pypi.python.org/pypi/grokcore.component/1.2.1
- http://pypi.python.org/pypi/martian/0.9.5
- http://pypi.python.org/pypi/grokcore.component/1.2
- http://pypi.python.org/pypi/martian/0.9.4
- http://pypi.python.org/pypi/grokcore.component/1.1
- http://pypi.python.org/pypi/grokcore.component/1.0.1
- http://pypi.python.org/pypi/grokcore.component/1.0
Preperations:
Sprint information
Where: Rotterdam, the Netherlands, at the offices of The Health Agency
When: 30 april - 5 may 2008
The Health Agency is our host for this sprint. The sprint itself is free, but you do need to arrange transportation and your stay yourself. The sprint location is in the centre of Rotterdam.
Please supply which days will you be attending. Why do we ask? The Health Agency will provide breakfast and lunch on all of the days of the sprint, dinner on the first three days.
| Name | wed 30 | thur 1 | fri 2 | sat 3 | sun 4 | mon 5 |
|---|---|---|---|---|---|---|
| Martijn Faassen | + | + | + | + | + | + |
| Jan-Wijbrand Kolman | + | + | + | + | + | + |
| Jan-Jaap Driessen | + | + | + | + | + | + |
| Eric Casteleijn | - | + | + | + | + | + |
| Joachim Schmitz | + | + | + | + | + | - |
| Daniel Nouri | - | - | - | - | + | + |
| Godefroid Chapelle | + | + | + | - | - | - |
| Jeroen Vloothuis | - | + | + | - | - | - |
| Jasper Spaans | + | + | + | + | - | - |
| Christian Theune | - | + | + | + | + | + |
| Philipp von Weitershausen | - | + | + | + | + | + |
| Wim Boucquaert | - | + | + | + | + | + |
| Christian Klinger | + | + | + | + | + | ? |
| Uli Fouquet | + | + | + | + | + | ? |
| Kamon Ayeva | + | + | + | - | - | - |
| Wichert Akkerman | - | - | - | + | + | - |
| Tim TerlegÄrd | + | + | + | + | + | - |
| Jean-Paul Ladage | + | + | + | - | - | - |
| Reinout van Rees | - | + | + | + | - | - |
| Maurits van Rees | + | + | + | + | + | - |
| Guido Wesdorp | - | + | + | - | - | + |
| Fred van Dijk | + | + | - | - | - | - |
| Peter Bengtsson | + | + | + | + | + | + |
| Jan Murre | + | - | + | - | - | - |
| Reinoud van Leeuwen | - | - | - | + | - | - |
Contact
Your general contact person for anything sprint-related is Martijn Faassen (faassen@startifact.com), so please mail him with any comments or questions.
Sprint topics
Final sprint topics are to be determined at the sprint, but here are some possible topics:
- Martian directives improvements
- Grok introspector improvements (connected to the directive improvement, and possibly subject of a Summer of Code project)
- Relational database integration (SQLAlchemy?, Storm)
- Improving KSS integration
- Improving WSGI integration
- Menu infrastructure: automatically generate menus out of views, viewlets
- Improve authentication/authorization story
- Consider optional model-based security
- Higher-level CRUD/BREAD patterns: create high-level constructs supporting browse, read, edit, add, delete patterns common in applications
- Back to the future topics: through the web views, schemas, etc.
- megrok.form improvements: more fields, more widgets, more documentation
- Reference documententation - boring but necessary
- Improve details for layers and skins, best practices
- Improve resources (in addition to "static")
- Use newer, tested-together versions of packages in the KGS for Grok. Make sure they have windows binary versions where necessary.
- Work on a way to easily install (to try it out) a Grok-based app using easy_install. Look at repoze?
NOTE: You can edit this page without having a zope.org account.