From Mon, 2009-09-14 to Fr, 2009-09-18 in Cologne (Germany)
WRAP-UP
First I'd like to use this space here to thank the organizing committee for their Excellent Work (TM). It was really nice to see many of the Grok community in person. Also the release of 1.0b2 bears witness of the fruitful cooperation that week.
For future reference, the housekeeping notes are kept below. At the bottom of the page you will find the aims of the sprint as jotted down the first morning. Judge by yourself how much of our ambition was brought into reality by reading JW's blog who faithfully created an entry at the end of every day. There are even a few pictures to be seen!
Where:
GfU? Cyrus AG in Cologne-Deutz, 10 minutes away from the Cologne main railway station (http://www.gfu.net).
Who should participate:
Grok developers or Python programmers with programming experience enough to contribute to Grok.
Themes:
The sprint priorities will be discussed in the grok-dev@zope.org mailinglist and should be aimed at the further progress of Grok as a whole. As the sprint host is an IT corporate training company, any work on Grok as a learning approach to Zope3, including work on the Grok/Zope3 documentation, is also welcome.
Participants (add your name here):
Also tell your primary topics if there are any
Name When Interests Uli Fouquet mon-fri ZTK/Python2.6; Grok documentation Aroldo Souza-Leite mon-fri Grok tutorials; Grok documentation Thomas Richter mon-fri Grok tutorials; Grok Dokumentation REST with Grok Timo Stollenwerk mon-fri Grok documentation; Website; Grok in Plone; RDB/formalchemy Jan-Wijbrand Kolman mon-fri ZTK integration; alternate menu implementation; post-1.0 bugs and features; model-based security checking; extending catalog support; DirectoryResource? and hurry.resource Jan-Jaap Driessen mon-fri Martijn Faassen mon-fri ZTK integration, publication changes Christian Klinger mon-fri Souheil Chelfouh mon-fri Grok + Dolmen + Simple features (copy, paste) Hanno Schlichting mon-tue ZTK; Babel vs. zope.i18n; WSGI Vincent Fretin mon-fri Joerg Baach not sure yet Documentation, tutorials Roger Erens mon Documentation, installation story Christian Theune mon-tue Sylvain Viollon mon-fri grokcore, grok and five.grok Leonardo Rochael Almeida mon-fri offline initial instalation Etienne mon-? Sascha Gresk mon (+fri) Tutorial on a Zope Live CD
GfU? shuttle
As one can see on the map the sprint location is distant from next train station 'Messe-Deutz'.
Therefore we cen use the shuttle bus provided by GfU? which will bring all sprinters from main entrance of Messe-Deutz station to the GfU? building every morning.
So the meeting place for sprinters not staying just around the sprint location will be train station Cologne-Messe-Deutz every morning.
The shuttles will leave the station
- at 10:00 h on monday,
- at 9:00 h on other days
Working, eating and sleeping at Neanderthal:
The sprinters will be treated as GfU? regular seminar participants. Two regular seminar rooms and all other facilities of the seminar centre can be used by the sprinters. The Neanderthal sprinters, like the participants of other GfU? seminars, have lunch in the GfU? buffet canteen for free.
Cologne is a busy trade fair city. Hotels are in general expensive and reservations difficult to manage. Please write early enough to Uli or Aroldo if you want help in looking for a room to stay during the sprint.
We reserved 9 beds for sprinters at the Weltempfänger backpacker hostel in Cologne-Ehrenfeld (http://www.koeln-hostel.de). The Weltampfänger agreed to keep the reservation until 4 weeks before the sprint. Sprinters can call or write to the Weltempänger and book a bed under the keyword "Neanderthal", or write to Uli or Aroldo if they need help.
Weltempfänger costs are (for the whole week (Sep 14 to Sep 19))
- for a single bed room: 175 EUR (only one available)
- for a bed in a four-bed room: 118 EUR
Breakfast has to be booked separately (6 EUR a day per person).
The Weltempfänger has free WLAN (we havent't tested this yet).
A midpriced hotel nearby is the Kolping Messehotel (http://www.kolping-messehotel.de/)
Both hotels are are shown on the Google map above. The Kolpinghaus-Messehotel in Deutz and the Weltempfänger in Ehrenfeld are connected to each other by direct and frequent underground lines until late in the evening (lines 3 and 4). It takes about 25 minutes to go from one hotel to the other by public transport.
Social events:
Right now, the following events are planned for the sprint. Sprinters from remote might want to check with their timetables.
Bootstraping
Everyone is welcome to the bootstraping event on the evening before the 'buildout' phase starts.
Sunday, 13.9.2009, 19:30 h
at the
Cafe Especial <http://www.cafe-especial.com/especial.html> Neuhöfferstr. 32, Cologne-Deutz (near railway station Cologne-Deutz)
See also google-map for finding the location. We will have a table reserved for "Grok".
Here you can enjoy some local beers and/or some mexican food together with other grokkers.
Bump-version breakfast
To give the sprint a nice fade-out, we will have a common breakfast on the day after the sprint, i.e. on
Saturday, 20.9. somewhen in the morning
Exact time and location will be published ASAP.
Cultural events:
By midweek we will have a Neanderthal day. We will go out together to grok some aspects of the Rheinland area. Apart from the Neanderthal valley itself, there are lots more to see in and around Cologne, Düsseldorf and Bonn.
Software Freedom Day
As september, 19th (the day following the sprint) is the Software Freedom Day and Grok is an open source product, we consider to present Grok (and eventually the progress we made during the sprint) to the public on this day.
This would include some presentation or lecture and being available for questions.
For SFD2009 there will be an public event in Cologne on this day from 10am to 4pm in Odysseum: presentations and an linux install party see: http://pv-rheinbogen.de/CcpWiki/InstallParty2009
About the sprint host and further sponsors:
The GfU? Cyrus AG is a traditional corporate IT training and consulting company. Although its technological spectrum is very wide, the directors have always shown a special interest in OpenSource?. They are planning to expand their Python marketing considerably.
Novareto gmbh (http://www.novareto.de) is sponsoring a substantial part of the organizing costs of Neanderthal II.
Sprint planning
- 1.0 release. Start out with a beta? A RC1?
- release RC1 on monday, set a fixed release date for 1.0
- review issues and take a decision.
- ==> jw, jj, (rvr on IRC), help from martijn, ctheune, leonardo
- @ monday
- other releases.
- documentation, second episode to the tutorial.
- WindowsInstallation
- review current docs, TutorialOutline
- take them and improve it TutorialMusicalPerformanceOptimizer (see also OutlineEtienne)
- what can promoted to "official"
- find general issues with documentation and find solutions
- somehow get grok-doc mailinglist updated about the efforts here
- how to get all the interesting componnents into an interesting application
- how does real-world Grok application actually look like?
- apply "Show-me-do" model?
- review "Musical Performance Organizer" tutorial, talk to the author
- maybe mine the image store application
- launchpad "blueprint" for documentation
- be focussed, define a baseline of experience
- keep a list of references about general web developement, templating, security, etc. (we shouldn't write all of this as a part of the grok documentation)
- ==> thomas, etienne, aroldo, timo, uli, roger,
- @ monday -
- Martian compatiblity (post-1.0).
- get grok(core, etc.) compatible with latest martian
- ==> jw, martijn, sylvain
- @ tuesday -
- ZTK, Dependency reduction (post-1.0)
- make grok work with a version of the ZTK
- help ZTK from a grok perspective
- grok(core) is probably mostly depending on ZTK packages (not 100% strict)
- investigate dependency structure of grok(core, etc) itself
- see also z3c.recipe.depgraph
- ==> hanno, ctheune
- @ monday -
- Coming from the other end: what would a lightweight version of grok look like?
- Grokui.admin
- lighter-weight, lower dependency version of the ui to install grok apps?
- commandline tools?
- your application as the root object?
- pluggability of grokui.admin, sending events
- ==> souheil, uli, martijn
- Aspect oriented programming in grok, as an alternative e.g. for events
- Grok on python-2.6
- see ZTK efforts
- Five.grok
- extracting more bits from grok to make it easier to reuse
- reuse in Five
- grokcore.site, grokcore.annotation in grok
- five.grok on zope 2.12
- ==> sylvain, vincent
- Security
- model level checking of security - how would that look like in grok?
- switching to default denial of access
- implement it so it is optional
- ==> chteune, jw, sylvain
- Templates and resources
- Different way to register templates in grokcore.view
- hurry.resource - grok.DirectoryResource? integration
- make hurry.resource part of grok?
- z3c.hashedresource part of grok?
- ==> martijn, vincent, christian klinger, souheil, jj
- Hurry.custom
- TTW customizing of resource
- Client-side templates with grok
- Easier to (de)serialize JSON in grok
- plugin different (de)serializers
- grokcore.json?
- ==> jj, jw, sylvain, martijn
- Integrating useful libraries with grok
- Relational databases integration with grok
- formalchemy - SQLAlchemy? based forms
- Future sprints
- Migrate http://grok.zope.org to Plone-3.3
- improve the search box on the site to include the Sphinx based docs
- ==> timo
- Chameleon
- as an alternative implementation to zope.pagetemplates
- megrok.layout
- integration into grok?
- ==> christian klinger, souheil
- z3c.form, megrok.z3cform
- relation to formalchemy
- ==> souheil, vincent, sylvain, timo
- offline-deployment
- Future Of Grok
- evangelism
- vandalism
- e-vandalism
- @14/09
- Better error pages by default in grok