[Grok-dev] 1.0 bugs selected for the Europython sprint

[Reinout van Rees]

I looked through the `Grok buglist <https://bugs.launchpad.net/grok>`_ with
`Jan-Wijbrand <http://jw.n--tree.net/blog/>`_ today.  Goal: 

- Get a short list of bugs as focus for the `Europython Grok sprint
  <http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html>`_.

- Find the bugs that really move 1.0 forwards.

- Find bugs that are probably doable in two days.

I've `tagged all five bugs we selected
<https://bugs.launchpad.net/grok/+bugs?field.tag=europython2009>`_ with
"europython2009" so that they're easy to find:

- Splitting grok.CodeView (*with just a render() method, so something that
  programmatically returns output*) out of grok.View (*which only retains its
  @template and loses the render() method*) ought to simplify the code a lot
  and open up the way for the last couple of fixes that are needed in this
  area for 1.0.

- grok.require() effectively falls back to the zope.Public permission.
  zope.Public isn't something you can take away.  If we set the default to
  zope.View, we can easily close everything to anonymous visitors.

- Having one ``templates/`` directory for a couple of modules is handy, but
  buries you under unnecessary warnings at the moment.

- XMLRPC in combination with WSGI is broken.  Can we (help) fix/debug it?

- For WSGI when using development mode, something's fishy with logging in.
  `Loads of comments on the bug
  <https://bugs.launchpad.net/grok/+bug/332061>`_, so with that we ought to
  nail it during the sprint.

For all your grok sprint info, see my previous `Grok sprint at Europython 2009
<http://reinout.vanrees.org/weblog/2009/06/09/grok-europython-sprint.html>`_
blog entry (which I updated with the sprint location).


Reinout


-- 
Reinout van Rees - reinout at vanrees.org - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"