So here it goes, how might our council look like? Currently we have 5 council members, which is good as it's an odd number so we get always a decision (if no one abstains). at the moment we only have 3 active members (even not too bad since it's still odd). So I think we should keep the 5, making doniphon the official project lead/chairman (given the legal stuff is sorted out). We need to define the turn of the members (might be different from the chairman). I would propose to replace Ken and Paul for now only, so that we don't have to replace the whole council at once *every* turn. This will provide some stability in our direction. I think a term should be a year at least (debatable though). I will offer my seat after work on f3 took off, at latest half way of the term of the new members, so that we get a refresh in the council after that time. What is the responsibility/duty of the council has still to worked out. Usually decisions should be made by discussing with developers on irc or ML (preferable for persistance), and only in cases where no clearly superior solution emerges, the council/leader is meant to decide (in small bits it's the packager anyway, as he probably knows it's package best). I think even with a council at hand, we should be a community driven project, so that every developer/member? (we need to talk about these names again one day) should be heard and be involved in the discussions.
I'm not going to throw any names in yet. Useless to say that there a way more candidates than seats, even if we're going to replace the council as a whole. Mark -- Mark Trompell Foresight Linux Xfce Edition Cause your desktop should be freaking cool (and Xfce) _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
