[Checkins] SVN: zopetoolkit/doc/source/zope-dev/ add agenda for today

[Christian Theune]

Log message for revision 115123:
  add agenda for today
  

Changed:
  U   zopetoolkit/doc/source/zope-dev/index.rst
  A   zopetoolkit/doc/source/zope-dev/zope-dev-20100727.rst

-=-
Modified: zopetoolkit/doc/source/zope-dev/index.rst
===================================================================
--- zopetoolkit/doc/source/zope-dev/index.rst	2010-07-27 14:08:16 UTC (rev 115122)
+++ zopetoolkit/doc/source/zope-dev/index.rst	2010-07-27 14:33:09 UTC (rev 115123)
@@ -4,6 +4,7 @@
 .. toctree::
     :maxdepth: 2
 
+    zope-dev-20100727
     zope-dev-20100720
     zope-dev-20100713
     zope-dev-20100706

Copied: zopetoolkit/doc/source/zope-dev/zope-dev-20100727.rst (from rev 115122, zopetoolkit/doc/source/zope-dev/zope-dev-20100720.rst)
===================================================================
--- zopetoolkit/doc/source/zope-dev/zope-dev-20100727.rst	                        (rev 0)
+++ zopetoolkit/doc/source/zope-dev/zope-dev-20100727.rst	2010-07-27 14:33:09 UTC (rev 115123)
@@ -0,0 +1,90 @@
+==========
+2010-07-27
+==========
+
+This is the agenda and summary for the weekly Zope developer meeting of
+Tuesday, 2010-07-27 on #zope at irc.freenode.org from 15:00 to 15:30 UTC.
+
+Summary
+=======
+
+The IRC log is available here:
+    XXX
+
+Attendees
+---------
+
+
+
+
+
+Agenda
+======
+
+- Review EuroPython
+
+- Review languishing bugs. (See
+  https://mail.zope.org/pipermail/zope-tests/2010-July/016049.html
+  https://mail.zope.org/pipermail/zope-tests/2010-July/016050.html
+  https://mail.zope.org/pipermail/zope-tests/2010-July/016051.html
+  https://mail.zope.org/pipermail/zope-tests/2010-July/016052.html)
+
+
+Ongoing issues
+--------------
+
+Those issues are currently ongoing. We don't have to discuss them. We just
+need to follow up on them eventually.
+
+- Abandoned projects (Tres)
+
+- Expectations for the upcoming Zope summit?
+
+- Meta
+    - Review meeting itself, maybe add extra 15 minutes for "meta" once a
+      month or every two months? (postponed until 2010-06-01)
+    - How to organize open issues in the long run (Blueprints?
+      Other tool? Continue text files?)
+
+- ZTK status
+    - Towards a ZTK release
+        - Documentation
+        - Release scope
+
+- Test runners / nightly builds
+    - Windows
+        - Compiler licenses (Tres, postponed until after 2010-06-14)
+        - Win egg builder (Adam)
+        - Documentation about VM setup (Adam)
+    - Supporting Python 2.7
+        - Needs help from the buildbots
+
+- Documentation
+    - Consolidate "floating" documentation into Sphinx/docs.zope.org
+        - write blueprint for the consolidation effort (Theuni)
+        - Find candidate links and gather them centrally
+        - Edit/update the documentation from the link list and
+          land in Sphinx-style during a sprint
+    - Turn ZTK package documentation into sphinx style (like zope.event)
+        - write bug and assign to toolkit projects (Theuni)
+    - Provide package documentation under docs.zope.org/<packagename> and keep
+      updated based on the projects' trunks. (Jens)
+
+- Releases
+    - How to find a good point when to cut a new release for a package for
+      which fixed bugs where registered (or changes have been made)? Any
+      automation possible to alert us when changes have been sitting around
+      unreleased for a while?
+
+Topic proposals
+---------------
+
+- Chris McDonough: Pondering *some* (re-)structuring of the ZTK to allow for
+  better maintenance/release management/communication/marketing. 
+
+- Christian Theune: I'd like us to ponder how we can (in addition to the
+  housekeeping and cleanups we do) also move to do constructive work together
+  to expand the stuff that Zope packages (ZTK) is about. How do we go about
+  implementing new technologies together, like supporting HTML 5 in the
+  various parts? I'd like to start putting in new code in the foreseeable
+  future in the zope.* namespace.