Hi Victor, On Wed, Jun 25, 2008 at 10:38:00 +0200, Victor Martinez wrote:
On Wed, 25 Jun 2008 09:43:40 +0200 Johannes Winkelmann <jw@smts.ch> wrote:
Hi there,
Hello Johannes,
[...]
That said, next meeting is tuesday next week. Hope to see you there.
Is there a way to put some points that will be talked in the next meeting? I guess we'll always go through the active bug reports and discussions from the mailing lists, so whatever comes up there which is relevant to developers can come up in the IRC meeting.
I think it can be a good idea to plan ourself to assist or not to the meeting. I mean for example the point about DE which was talked and can be very interesting to have some points before start the meeting (some kind of little organization). I agree. I'd even go further and say that such big things like the DE discussion (for those wondering: contrib ports depending on gnome/kde/xfce) should be discussed before, to avoid losing too much time during the meeting with single issues.
For that, I guess it could make sense to have an agenda with two groups of items: 1. needs discussion 2. needs decision or implementation At the casual meetings, we would typically address items from group #2. Items of group #1 should typically be discussed on the mailing list. Once we have a clear picture about an issue, we can move it to group two. We could in addition have one meeting per month as a regular IRC meeting, where we discuss about group #1 stuff. Does that sounds right, or is it too complicated? Best wishes, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch