[Checkins] SVN: zopetoolkit/doc/source/zope-dev/ update for todays meeting

Christian Theune ct at gocept.com
Tue Sep 21 01:55:11 EDT 2010


Log message for revision 116693:
  update for todays meeting
  

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

-=-
Modified: zopetoolkit/doc/source/zope-dev/index.rst
===================================================================
--- zopetoolkit/doc/source/zope-dev/index.rst	2010-09-20 21:50:58 UTC (rev 116692)
+++ zopetoolkit/doc/source/zope-dev/index.rst	2010-09-21 05:55:10 UTC (rev 116693)
@@ -4,6 +4,7 @@
 .. toctree::
     :maxdepth: 2
 
+    zope-dev-20100921
     zope-dev-20100831
     zope-dev-20100824
     zope-dev-20100817

Copied: zopetoolkit/doc/source/zope-dev/zope-dev-20100921.rst (from rev 116440, zopetoolkit/doc/source/zope-dev/zope-dev-20100831.rst)
===================================================================
--- zopetoolkit/doc/source/zope-dev/zope-dev-20100921.rst	                        (rev 0)
+++ zopetoolkit/doc/source/zope-dev/zope-dev-20100921.rst	2010-09-21 05:55:10 UTC (rev 116693)
@@ -0,0 +1,82 @@
+==========
+2010-09-21
+==========
+
+This is the agenda and summary for the weekly Zope developer meeting of
+Tuesday, 2010-09-21 on #zope at irc.freenode.org from 15:00 to 15:30 UTC.
+
+Summary
+=======
+
+The IRC log is available here:
+    XXX
+
+Attendees
+---------
+
+XXX
+
+
+Agenda
+======
+
+- Post-summit thoughts
+
+- Bug day organization
+
+- Meta
+
+
+Ongoing issues
+--------------
+
+Those issues are currently ongoing. We don't have to discuss them. We just
+need to follow up on them eventually.
+
+
+- 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?)
+
+- Test runners / nightly builds
+    - Supporting Python 2.7
+        - Needs help from the buildbots
+    - Windows
+        - Compiler licenses (Tres, postponed until after 2010-06-14)
+    - Build bot organization
+
+- Bug day organization
+
+- Documentation
+    - Consolidate "floating" documentation into Sphinx/docs.zope.org
+        - Write blueprint for the consolidation effort (Theuni)
+          see
+          https://blueprints.edge.launchpad.net/zopetoolkit-project/+spec/consolidate-documentation
+        - 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)
+    - Unified index?
+
+- 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.



More information about the checkins mailing list