On 03/31/2010 05:16 PM, Christian Theune wrote:
here's this week's summary.
That was a lie. Here's the summary.
Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
Weekly Zope developer meeting
This is the summary of the weekly Zope developer meeting which happened on
Tuesday, 2010-03-30 on #z...@irc.freenode.org from 2pm to 2:45pm (UTC).
Unfortunately the scheduled time was mixed up due me forgetting about the
recent switch from CET to CEST in my place.
The agenda for this meeting is available in the mailing list archives:
The IRC logs are located here:
We discussed how to establish a better routine for dealing with the bugs we
receive, e.g. fixing, triaging, ...
Two supplementary approaches solidified: taking up on bug days again and
running automatic checks to warn us if new bugs aren't dealt with for a longer
period of time.
Bug days seemed to have disappeared because nobody stepped up for organizing
them. Christian Theune volunteered to organize a bug day in April. We'll see
how that works out and figure out how to deal with them regularly later on.
To allow people from multiple time zones to join in comfortably the bug day
will span a longer period in time, probably starting around 9am CEST for
Europeans allowing the Americas-based developers to join in later.
Bug days also could be a good way to allow fresh developers to pick up
somethign easy and get immediate assistance with the process and internals.
For that the moderator of the bug day should be prepared to help others with
fixing bugs and documenting process-related issues along the way.
Checking for orphaned bugs
Charlie Clarke volunteered to try writing a script that uses Launchpad's API
to poll for bugs that have been sitting without a developer paying attention
for too long and sending mail to zope-tests accordingly. Christian Theune will
Proposed API changes vs. moving towards Python 3
Our current Python compatibility target is 2.6 with 2to3 converting for
compatibility with 3.1.
We're still in a chicken-egg situation with Python 3 as both libraries and
important parts of the toolchain (packaging, testing) aren't compatible with
Python 3 yet. The ZTK as a large set of libraries is a part of the problem
itself for many consumers.
There was preliminary work by various people, especially Martin von LÃ¶wis that
is bringing the packaging utilities to Python 3. From our perspective we need
to first get the BTK (bicycle toolkit) and especially testing infrastructure
to run on Python 2.6 and 3.1 before dealing with further pacakges. This seems
to be a good task for a sprint. (The next upcoming sprints are: Plone
Symposium East in late May, EuroPython in July, and DZUG in September)
As Lennart Regebro brought this topic onto the agenda but wasn't present due
to the DST confusion we'll raise it again next time to allow him to express
his view on the topic.
Meta: Reviewing the weekly meeting experiment
Tres, Charlie, and Stephan expressed they find the weekly meetings helpful and
like them to continue.
To make them viable in the long run Christian Theune will try to find a second
person that can take over organizing the meetings when he's not around.
Charlie also noted that short time and agenda are helpful.
In the future we'll have to figure out how to keep track of the open issues
that we put on the backburner. Christian Theune will check whether Launchpad
or another specialised web application might help with that.
The meeting summaries have been found useful, although the participants of the
IRC meetings suspect that those developers that could not join may find them
even more useful. Feedback from the mailinglist (hey, are you reading this?)
would be welcome.
People asked for the agenda/notification mail to include an ICS file.
Christian Theune can't do that with his tool chain and the Google calendar at
seems to have timezone issues, too.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -