On Wed, 25 Jun 2008 16:54:43 +0200 Johannes Winkelmann <jw@smts.ch> wrote:

Hi Victor,

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.

Well, yesterday you traveled over bug reports, but without a planning. I mean, you see an error and you talk about it (I don't mean this is a bad way to go trought them, because the meeting for me was productive, but may be can be interesting to fill the agenda of a meeting with interesting bugs that can affect directly to one person, in this way, someone can put one item in the agenda making a reference to a bug, which can be found interesting by him, and more if he will be in the meeting, of course it can be told in the meeting, but may be people didn't thought about it, and can be a bit fast).

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.

The DE discussion was only an example, but you took the point (discussed before the meeting to don't lose too much time, or at least, to prepare points of view about the big items).

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.

This sounds great for me. This is some kind of organization to make meetings. Btw, I tried to explain here my thoughts to see if you found them interesting and helpfully to organize the meetings. May be, making this kind of meeting groups can make them harder.

We could in addition have one meeting per month as a regular IRC meeting, where we discuss about group #1 stuff.

If you feel confortable with the aproach you have now, I mean, looking for items which have been discussed (or it will be) and implement them, I think it's enought. I like the idea of meetings to make a bridge between maintainers/core members/users and to take decisions which will affect all people using CRUX. But in fact, making too much meetings in a month, can be hard to people to follow them, this was my point about items to be talked, to let people organize theirselves.

Does that sounds right, or is it too complicated? I understood the point, but not sure if it can be good for all people to follow this pattern, may be sounds hard to follow instead of hard to understand.

Thank you very much for reading these posts and sharing your opinion.

Best wishes, Johannes

Same from here, pitillo. -- Learning bit by bit. -pitillo-