[Checkins] SVN: zopetoolkit/doc/source/zope-dev/ prepare meeting

Christian Theune ct at gocept.com
Tue Jun 22 03:45:18 EDT 2010


Log message for revision 113751:
  prepare meeting
  

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

-=-
Modified: zopetoolkit/doc/source/zope-dev/index.rst
===================================================================
--- zopetoolkit/doc/source/zope-dev/index.rst	2010-06-22 07:28:39 UTC (rev 113750)
+++ zopetoolkit/doc/source/zope-dev/index.rst	2010-06-22 07:45:17 UTC (rev 113751)
@@ -5,7 +5,9 @@
 
     :maxdepth: 2
 
+    zope-dev-20100621
     zope-dev-20100615
+    zope-dev-20100615
     zope-dev-20100608
     zope-dev-20100601
     zope-dev-20100525

Modified: zopetoolkit/doc/source/zope-dev/zope-dev-20100615.rst
===================================================================
--- zopetoolkit/doc/source/zope-dev/zope-dev-20100615.rst	2010-06-22 07:28:39 UTC (rev 113750)
+++ zopetoolkit/doc/source/zope-dev/zope-dev-20100615.rst	2010-06-22 07:45:17 UTC (rev 113751)
@@ -3,7 +3,7 @@
 ==========
 
 This is the agenda and summary for the weekly Zope developer meeting of
-Tuesday, 2010-06-08 on #zope at irc.freenode.org from 15:00 to 15:30 UTC.
+Tuesday, 2010-06-15 on #zope at irc.freenode.org from 15:00 to 15:30 UTC.
 
 Summary
 =======

Added: zopetoolkit/doc/source/zope-dev/zope-dev-20100621.rst
===================================================================
--- zopetoolkit/doc/source/zope-dev/zope-dev-20100621.rst	                        (rev 0)
+++ zopetoolkit/doc/source/zope-dev/zope-dev-20100621.rst	2010-06-22 07:45:17 UTC (rev 113751)
@@ -0,0 +1,78 @@
+==========
+2010-06-21
+==========
+
+This is the agenda and summary for the weekly Zope developer meeting of
+Tuesday, 2010-06-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 (draft)
+==============
+
+- Bug tracking
+    - Monitoring tracker status (Charlie Clark, ctheune)
+
+- Documentation
+    - Consolidate "floating" documentation into Sphinx/docs.zope.org
+
+- Review bug day
+    - Comments about the bug day
+    - Scheduling the next bug day
+
+Ongoing issues
+--------------
+
+Those issues are currently ongoing. We don't have to discuss them. We just
+need to follow up on them eventually.
+
+- 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
+
+
+- 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?
+
+- 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?)
+
+
+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