[21:05:50] ok [21:06:00] let us officially [21:06:07] declare this meeting opened [21:06:09] fwiw i wrote up some notes a while back on making these meetings work less poorly -- http://dberkholz.com/2008/05/13/how-to-run-an-effective-meeting-on-irc/ [21:06:43] should we do another roll call? [21:06:45] dberkholz: does that include having everybody stop and read a blog midway? :) Seriously though - thanks for the link. [21:07:01] here [21:07:03] here [21:07:06] here [21:07:10] sure. [21:07:12] here [21:07:18] here [21:07:22] excellent [21:07:33] here [21:07:34] agenda point 1 [21:07:44] - vote for holding meetings every 2nd Tuesday of the month at 2000 UTC (or [21:07:44] 1900 UTC depending on daylight savings) [21:07:57] -*- ulm votes yes [21:07:58] a) general objections? [21:08:01] aye [21:08:02] -*- WilliamH votes yes [21:08:02] b) utc? [21:08:06] aye [21:08:09] ack from me [21:08:14] -*- blueness|chromeb votes yes [21:08:16] Err, let's clarify the utc/dst bit [21:08:19] so 1900 now, and 2000 during US daylight savings? (since we have more US members) [21:08:27] Is this UTC/BST? [21:08:33] Or US DST? [21:08:55] Can we just pick a utc time and stick to it all year? [21:09:04] ok we have 5 general yes about the overall plan [21:09:06] WilliamH, that works for me [21:09:09] FYI - it is 1900 now and we are currently in DST. [21:09:13] i don't really care one way or the other, just pick something [21:09:15] works for me too for utc whole year [21:09:15] now about the dst question [21:09:18] Ditto. [21:09:20] anything works for me [21:09:23] I'm for same utc always [21:09:26] works for me either way [21:09:44] How about 1900 UTC always then. [21:09:51] yes [21:09:52] ok let's have a quick vote, 1b) 19:00 UTC always? [21:09:52] fine [21:10:04] -*- dilfridge yes [21:10:08] -*- ulm yes [21:10:10] -*- WilliamH yes [21:10:14] -*- blueness|chromeb votes yes [21:10:15] cool. 1900 utc year-round on 2nd tuesdays [21:10:22] i will update the google calendar [21:10:36] ok that was point 1! [21:11:00] 2: "vote for continuing last council's workflow considering sending call for [21:11:00] agenda items (2 weeks in advance), sending the agenda (1 week in advance) and [21:11:00] have the meeting focussed, e.g., have major discussions on -project ML prior [21:11:00] to the meeting" [21:11:00] council.g.o has to be updated too, it says 2000 UTC [21:11:12] -*- ulm will update the council page [21:11:16] thanks! [21:11:44] I guess 2 will also be unproblematic [21:11:45] -*- scarabeus looks forward to see that wikified :P [21:11:54] yay for agenda sending from me :-) [21:12:15] -*- WilliamH yes [21:12:18] does point 2 need discussion? [21:12:18] works for me [21:12:20] -*- dilfridge yes [21:12:24] -*- ulm yes [21:12:25] -*- blueness|chromeb yes [21:12:45] dilfridge: I'm fine with aiming for discussions on-list as much as possible. Not so much a rule as a principle. [21:13:01] yep [21:13:01] yeah [21:13:05] agreed [21:13:06] Oh, and ideally not the day before the meeting. [21:13:10] heh yeah [21:13:16] having the discussion on ml first makes sense, also since we may want to prepare [21:13:22] The whole point is to give topic submitters time to refine before the meeting and cut down on churn. [21:13:36] s/may want/need/ [21:13:40] Instead of showing up and getting shot down. [21:13:41] who can read the list? only concil members or is it public? [21:13:46] and who can post? [21:13:55] Gentoo-project - open list. [21:13:58] k [21:14:00] -project is public [21:14:00] we're talking about the gentoo-project list in most cases [21:14:05] oh on -project [21:14:12] or gentoo-dev if it's ebuildy [21:14:12] thanks for the clarification [21:14:22] Or -dev if it makes more sense. We can always cross-ref the thread in the agenda where appropriate. [21:14:57] the only closed list that we have is -core, and council topic discussions there do NOT make sense. [21:15:17] k [21:15:21] ok anything else about 2? [21:15:47] seems not, I guess this is carried then [21:16:05] 3: "appoint chairman for this term's meetings" [21:16:14] how was this handled in the past? [21:16:25] somebody usually volunteered [21:16:28] or it was rotation [21:16:32] people usually just volunteer to do it. [21:16:36] whatever rocks your chair :-) [21:16:39] I can do september and october [21:16:53] we've tried to have people do 2-3 in a row to make it a little less awkward [21:16:57] ok... do we need to decide on a full list now? /me does not think so [21:17:09] Not necessarily [21:17:13] dilfridge: we should decide until end of the year [21:17:16] i'm busy-ish till dec [21:17:22] and last year we just settled on the whole year since that's really just like 6 slots of 2 meetings a piece [21:17:30] ok i can do november and december [21:17:41] anyone taking notes for the summary? [21:17:42] ulm: i would more say we caould appoint one at end of each meeting [21:17:46] *could [21:18:22] dberkholz: I'm logging this anyway... taking notes and typing at the same time is not so easy [21:18:23] Suggest we appoint for next meeting now and take the rest offline. [21:18:31] also when is next meeting; 13.8.? [21:18:44] If somebody just wants to toss out a schedule feel free. [21:18:45] yes [21:18:51] I can volunteer for that if it helps. [21:19:25] rich0, okay [21:19:26] 13.8., 10.9., 8.10., 12.11., 10.12. [21:19:44] whoa, you europeans and your logical dates are confusing me [21:19:49] :) [21:20:16] That's why I get fired if I don't write them as 13-Aug-2013 at my company. [21:20:35] 2013/08/13 [21:20:35] Or 01-Aug-2013 - ##-###-#### [21:20:37] 20130813 [21:20:52] only correct and mandatory is 2013-08-13 :P [21:20:54] Gotta love lawyers. [21:21:00] but dd.mm.yyyy is our syntax [21:21:13] unset LC_ALL [21:21:17] in 2014 it's 14-Jan, 11-Feb, 11-Mar, 8-Apr, 13-May, 10-Jun [21:21:31] ok [21:21:32] anyway [21:21:35] we are disgressing [21:21:43] ulm, if we rotate i'll take some of the 2014 days [21:21:56] but next semester is a bit heavy [21:22:03] then i'm on sabattical and very free [21:22:07] I just noticed I probably can't do december, but oct and nov is no problem [21:22:11] so how about [21:22:28] ulm starts aug sep, I do oct now and the rest will be decided on the way? [21:22:32] dilfridge: I could take aug and sep as well [21:22:35] :) [21:22:43] s/now/nov/ [21:23:01] works for me [21:23:21] works for me also we don't have to decide all of them now [21:23:33] i can do jan-feb. [21:23:57] i can do mar-apr [21:24:04] ok [21:24:07] fine [21:24:09] i can also do dec if needed [21:24:28] so we have the next ones and provisorical list for later [21:24:43] that should conclude point 3 [21:25:02] now come the first tricky parts [21:25:12] fwiw i would prefer to schedule earlier rather than later, my calendar fills up. so let's do "later" on the council alias post-meeting vs some unspecified time [21:25:13] dilfridge: it would pay to number items in the agenda already ;) [21:25:22] 4: "vote on meeting format 1: "the open floor is the mailing list discussion", [21:25:22] i.e. no open floor during the meeting anymore" [21:25:25] ulm: indeed [21:25:34] opinions? [21:25:54] How long has open floor tended to take in the past? [21:25:58] I tend to agree with Roy on that. [21:26:03] almost 0 [21:26:05] dilfridge, with the hardened meetings we do openfloor only at the very end [21:26:07] dilfridge: I won't dismiss neddyseagoon's argument lightly [21:26:09] molsty people are silent [21:26:12] people are not allowed to interrupt [21:26:16] I appreciate the value of openness, but honestly I don't think there is much opportunity to actually resolve issues in open floor. [21:26:20] and open floor tends to be short anyway [21:26:21] when it takes any time, it will just suck up whatever time is leftover [21:26:42] it's kind of a binary thing, because there's usually not much but when there is something, it goes nowhere for 45 minutes [21:26:42] If it isn't currently a real problem I suggest we leave it alone. [21:27:03] I'm fine with reining in open floor. Open floor doesn't mean open rant... [21:27:11] I'm undecided... I dont think we can really decide something because of lack of information, but it never hurts to listen to people [21:27:15] Open it up, and then recognize when we aren't getting anywhere. [21:27:16] rich0: it wasn't a problem during last term [21:27:45] ulm: I was just talking about the 45min example. [21:28:02] last meeting it sucked up 15 minutes, the meeting before it was 20 min [21:28:12] just looking at the logs [21:28:16] yeah but then the chair should probably just call it off at some point [21:28:16] -*- WilliamH thinks we should keep the open floor at the endof the meeting like last term [21:28:42] it is up for chair to drive, after all it can be cut off and moved to ml when needed [21:28:45] dilfridge: Yes, that could happen too [21:28:47] the open floor is just an opportunity to spit out unstructured thoughts in a form that's not conducive to thoughtful discussion about them [21:28:49] dberkholz, can't the chairman call an end to ranting and refer it back to the lists [21:28:49] dilfridge: ++ we don't HAVE to use the full 60 mins just because we end early. [21:29:04] yeah [21:29:06] so [21:29:18] shall we vote? /me will formulate what on [21:29:18] dilfridge: vote? [21:29:28] so, chairs, don't be afraid to shake your big stick. because it typically takes a while to realize that. [21:29:45] 4: "Should we discontinue open floor at the end of the meeting?" [21:29:49] dilfridge, formalate what we are voting on [21:29:55] -*- dilfridge no [21:29:57] s/formalate/formulate/ [21:30:01] -*- WilliamH votes no [21:30:02] -*- ulm no [21:30:06] yes [21:30:07] no [21:30:15] -*- scarabeus nope, chair to handle this [21:30:18] -*- blueness|chromeb voites yes [21:30:35] that's 5 no, 2 yes [21:30:42] means things stay as they are [21:30:55] we can revisit if we regret it. :) [21:31:00] indeed [21:31:02] next point [21:31:14] 5: vote on meeting format 2: "shift council votes to mail instead of IRC" [21:31:28] I'm not sure I summarized that correctly for the agenda [21:31:40] -*- WilliamH is against that [21:31:44] I'm against it, because actual voting is usually the quickest part of a decision [21:31:46] i should note that i suggested mail or bugzilla. some format where we can respond more quickly than a meeting that's 4-5 weeks out [21:31:48] yeah i don't like this [21:31:51] i like the discussion [21:31:56] and it's nice having the votes in the log [21:32:02] indeed [21:32:06] voting is okay on irc, we need to chat on mails, not on the meetings [21:32:09] I'I suggest allowing votes in bugzilla in addition to in meetings, not in place of. [21:32:33] And not as the default. [21:32:51] ok let's first vote on the version as in the agenda, and then afterwards discuss possible alternatives [21:32:57] 5: "shift council votes to mail instead of IRC" [21:32:59] -*- dilfridge no [21:33:00] rich0, the agenda would have to make it clear where the vote will take place if we us both irc and bugz [21:33:03] no [21:33:05] -*- ulm no [21:33:07] -*- scarabeus no [21:33:10] -*- blueness|chromeb no [21:33:14] -*- WilliamH thinks that what this was about then is finding a way for the council to vote on high priority issues between meetings [21:33:36] blueness|chromeb: in general when voting in bugzilla it wouldn't be on an agenda at all. It would be for items that come up that would benefit from resolution prior to the next meeting. [21:33:52] that's already 5 no [21:33:57] rich0, yeah that works, for more urgent issues [21:34:00] If we're going to always stick it on an agenda might as well just vote in a meeting. [21:34:18] now, about "additions" to irc [21:34:33] Proposal: "Allow voting via bugzilla for urgent issues, with prior notice to -project whenever practical." [21:34:36] rich0: in practice, asking for votes per e-mail never worked well [21:34:39] i like the idea of urgent issues being delt with in bugz [21:34:58] but maybe bugzilla works better [21:34:58] i like the idea of considering every issue urgent unless we need to defer it to a meeting for some reason [21:35:31] dberkholz: That is how the trustees generally operated - many issues did get decided in meetings, but if an issue was resolved prior we'd just deal with it. [21:35:31] the default should be getting things done faster [21:35:33] yeah... rich0, how about something like "prior notice at least 3 days earlier" [21:35:58] dilfridge: fine with the 3 days, but again I'd include "whenever practical" - there could always be emergencies. [21:36:01] dberkholz: does that mean we just allow bugs to be assigned to council and deal with them there? [21:36:31] WilliamH: I think that is fine. Oh, we can always summarize the results in the next meeting summary. [21:36:42] dberkholz: then if we defer things to a meeting those end up on an agenda? [21:36:51] WilliamH: I fear a bit that's the road to micromanagement... but for important stuff, fine [21:37:16] Ok... [21:37:16] i'm not sure i see how communicating in a different forum is micromanagement? [21:37:38] dberkholz: more like "ah well let's cc council quickly" [21:37:54] but then we can always defer to meeting if it's not important / not urgent [21:38:09] ok [21:38:13] oh, yeah i had more in mind that people might specifically file bugs for council agenda items. we could attempt to vote on the bugs, or discuss them at the meeting [21:38:46] 5A: "Allow voting via bugzilla for urgent issues, with prior notice (at least 3 days earlier) to -project whenever practical. [21:38:52] votes for 5A? [21:38:58] -*- blueness|chromeb yes [21:39:00] -*- ulm no [21:39:13] -*- dilfridge abstains [21:39:15] yes [21:39:46] the prior notice is probably a good idea for transparency, so everyone doesn't need to track council bugs [21:39:48] yes [21:39:48] -*- scarabeus yes [21:40:29] -*- WilliamH is unsure about this as a separate item [21:40:48] what do you mean? [21:40:49] we've got 4 yes's, vote for posterity if you choose, otherwise let's move on =) [21:40:58] This has sort of ended up confusing... [21:41:09] voting on bugzilla is lousy [21:41:13] can you actually vote "no" with its voting system? [21:41:25] or abstain? [21:41:27] ulm, why not? [21:41:29] I wasn't suggesting that we actually use the voting feature in bugzilla. [21:41:30] we've always just commented in the past [21:41:34] You can just do it via comments/etc. [21:41:34] not used actual "votes" [21:41:38] I guess we mean more "leave a comment on a bug saying yes/no/abstain" [21:41:46] not using bugzilla's voting system [21:41:56] if you suggest building a voting engine, i'm going to come to your house and take away your keyboard [21:41:56] dilfridge, that was my understadning, use comments [21:42:07] dberkholz, heh [21:42:08] Ok, use comments to vote... [21:42:11] ok let's clarify this [21:42:30] rich0: can you point to an example of a bug the trustees voted on, so it's perfectly clear [21:42:58] 5B: "Allow voting via leaving comments YES/NO/ABSTAIN on a bug for urgent issues, with prior notice (at least 3 days earlier) to -project whenever practical" [21:43:08] better? [21:43:14] -*- blueness|chromeb votes yes [21:43:23] -*- dilfridge abstains still [21:43:28] -*- ulm no [21:43:39] yes again [21:44:01] scarabeus: WilliamH: ? [21:44:03] yes [21:44:31] bug 474774 is an example [21:44:33] rich0: https://bugs.gentoo.org/474774 "Proposal to purchase parts for Alpha development system"; Gentoo Linux, Unspecified; RESO, FIXE; mattst88:trustees [21:45:12] we have 3 yes, 1 no, 1 abstention so far [21:45:54] -*- WilliamH is looking at the bug [21:46:06] ok [21:46:11] any more votes? [21:47:07] bugzilla is not the right medium, neither for discussion nor for voting [21:47:12] seems not [21:47:26] True, much discussion ends up in email/lists. [21:47:30] so it's carried with 3 yes, 1 no, 1 abstention [21:47:37] It is a good medium for openly recording votes. [21:47:51] rich0: wiki works much better [21:48:03] if we try this at some point and ulm is right, we can revisit the issue and stop the practice [21:48:09] 6: "open floor to council members to introduce themselves to the others, and/or raise issues they would like to deal with" [21:48:27] should we go around so everyone has a chance to say something? [21:48:33] sure [21:48:34] -*- scarabeus checked the bug (it looks for yes from me) [21:48:46] blueness|chromeb: how about you start? [21:48:51] okay [21:49:16] about me: i'm mostly working in hardened, alternatie libcs like uclibc and musl, and minor arches [21:49:43] my main current project is migrating pax flags out of elf binaries to xattr so our elfs are more in line with other distros [21:50:05] and one issue i'd like the council to look at is documenting pms's vdb directory [21:50:27] getting things like NEEDED.ELF.2 into pms specs ... more details on that later [21:50:37] okay ... very quick intro [21:51:19] next one, dberkholz :) [21:51:19] next? [21:51:46] hi, i've done lots of stuff. i described most of it in my "manifesto" thing [21:52:39] my main project right now is doing some research into quantifying our community [21:52:47] so we can figure out potential problems more easily [21:53:00] and opportunities, like people who should become devs [21:53:22] also doing the gsoc thing, which is at midterms this week. [21:53:24] that's about it [21:53:52] ok next one in the alphabet is myself [21:54:40] I "grew up" in Gentoo in the KDE team, and am still to a large part active there, in the meantime [21:55:10] a few other things have been added, I'm taking care of cups and part of printing and generate libreoffice-bin [21:55:11] --> NeddySeagoon (~NeddySeag@gentoo/developer/NeddySeagoon) hat #gentoo-council betreten [21:55:28] what I'm interested in... [21:55:55] well, one thing I am unhappy about is when discussions about some topic on the mailing lists just branch out and branch out [21:56:14] and noone can make a decision because no real consensus is reached. [21:57:01] this is one of the reasons why I wanted to join the council, so maybe we can make some well-informed decisions when decisions are needed [21:57:12] that's it [21:57:31] next one -rich0 [21:57:39] I won't take up everybody's time. I'm happy to be a part of the team, and I've already written most of how I feel in my manifesto. I'd like to see more indirect influence by the council beyond voting on the lists and out in the community - we have a power to encourage/influence/etc that we should better use. However, we shouldn't be afraid to settle disputes - sometimes any resolution is better than none. That said, I'm always willing to [21:57:40] discuss anything. As far as who I am goes - I work in IT at a Pharma company with a Biochemistry background. I'm a tinkerer, and Gentoo is a tinkerer's distro. As far as things around Gentoo that interest me - I have an interest in the git migration and anything that can be done to help move it along. next? [21:58:13] ok scarabeus [21:58:57] ok most of you know what i did and what i break on daily basis, apart from that i am now in opensuse team ;-) and I really wish we in gentoo could generate better binary distro to attract more people [21:59:27] apart fromt hat the regular stuff, better communication, more fun, booze, etc, whatever rocks your boat to contribute we as council should provide :-) [21:59:30] thats it [21:59:35] ulm? [21:59:43] ok, very short intro [22:00:08] I've started in Gentoo working on GNU Emacs packages and I'm still maintaining them [22:00:21] and for some reason I've inherited eselect ;) [22:00:47] one of my priorities for this term is to finalise EAPI 6 [22:01:04] that's about it - next? [22:01:10] WilliamH? [22:01:26] Hi all, I have been a gentoo dev for quite a while. [22:01:43] I started in accessibility, and I'm still the lead there. [22:02:04] I'm also a member of base-system, upstream for OpenRc, and involved in several other things. [22:03:07] I also maintain some things for Releng, particularly livecd-tools [22:03:39] I am interested in making sure that our distro is accessible to users withdisabilities, and also some base-system and distro wide issues. [22:04:30] One thing I want to do this term (I'll be putting this on the next agenda if no one else brings it up) is to settle the separate /usr support issue that has been a hot button for a while. [22:05:00] That's all I can think of right now. :-) [22:05:26] ok excellent [22:05:48] means we can conclude point 6 [22:06:05] 7: "general discussion on the introduction of a "Bikeshed of the month" " [22:06:10] that's my baby [22:06:21] more or less for the protocol, [22:06:30] let me quickly explain what this is about [22:07:01] the idea is to pick topics where a decision clearly makes sense, but people could not agree during bikeshedding [22:07:22] put them on the agenda and try to settle things [22:07:31] i don't really think we need to formalize that [22:07:37] fine with me [22:07:46] but i do agree with the idea, of council members proposing topics from the ML instead of waiting for someone else to do so [22:08:24] I'm fine with the concept, agree it doesn't need to be formalized. However, before we step into something we should at least confirm that SOMEBODY wants us to do so. [22:08:26] some of the stuff is so trivial, and a lack of a decision is sometimes just blocking things [22:08:27] yeah we can take more of a leadership roll in resolving contraversial issues [22:08:35] yes [22:08:39] If all the parties are already fine with where things stand or are working things out, we don't need to interfere. [22:08:58] rich0: true [22:09:03] We can be proactive though - just suggest we poll the community for whether we should get involved. [22:09:22] So, put on agenda, and maybe just ask for opinions. Utter silence might be a reason to not disturb the silence. [22:09:31] rich0, for some of the bikeshedding we already know where they stand [22:09:32] rich0: but we should see that if we put somethign on the agenda and noone cares [22:10:03] ok [22:10:23] to be honest, I dont think we really need to discuss here much... anything else to say? [22:10:32] dilfridge, one closing comment [22:10:57] might i suggest that you pastebin the agenda just before the meeting and put the url in the topic for everyone to see [22:11:10] or perhaps something more editable like an etherpad [22:11:13] yes [22:11:15] or even our wiki [22:11:23] yeah anything like that [22:11:32] then we could do some crowdsourcing of summaries [22:11:41] did not do anything this time because we already had the link but next time, true [22:11:47] question... [22:11:50] people followign the meeting may not have the agenda in front of them ... like even me on my chromebook [22:12:04] separate subject so I'll wait [22:12:12] i'm done [22:12:15] blueness|chromeb: agenda is in the topic [22:12:16] I like the idea of live summaries. [22:12:19] Etherpad or whatever. [22:12:26] ok anyone else? [22:12:30] ulm, oh yeah so it is! [22:12:38] -*- WilliamH has something [22:12:40] I often do this at work - anybody can chime in on errors as they happen, and after meeting you just hit send. [22:13:06] WilliamH: let's finish the agenda points and then do the new thing, ok? [22:13:10] Sure. [22:13:23] 8: "open bugs with council involvement (currently only #477030)" [22:13:27] bug 477030 [22:13:29] dilfridge: https://bugs.gentoo.org/477030 "Missing summary for 20130611 council meeting"; Doc Other, Project-specific documentation; CONF; ulm:council [22:13:47] who should we kick? [22:13:52] does anyone have that log? [22:14:15] dilfridge: we should kick betelgeuse, unless we want to do the summary ourselves [22:14:25] he had chaired that meeting [22:14:44] ok since he's not around, anyone volunteering (for kicking him)? [22:15:06] blueness|chromeb: log is linked from the council page already, only summary is missing [22:15:06] how about any or all of us when we see him ;) [22:15:14] ok fine [22:15:22] that concludes point 8 [22:15:26] WilliamH: your turn [22:15:26] heh [22:15:37] Actually a couple of quick questions... [22:16:14] Since we have added bugs as action items, does that change how we put things on the agenda -- should we respond to the call for agenda items on -project, and open bugs assigned to council? [22:16:32] <-- blueness|chromeb (~blueness@gentoo/developer/blueness) hat #gentoo-council verlassen [22:16:32] --> blueness|chromeb (~blueness@gentoo/developer/blueness) hat #gentoo-council betreten [22:17:15] i would suggest we document on the council homepage that anyone may file any bugs at any time for council consideration [22:17:40] nice idea [22:17:41] my opinion, let's keep things as they are as much as possible (except if something urgent and important happens) [22:17:52] and also get people to file bugs for agenda items so they don't get lost [22:18:02] (yeah, that happens regularly) [22:18:28] bugs for agenda items are fine, but discussion should still be on mailing list [22:18:34] dberkholz: Ok, so if we file bugs for agenda items should we link to them from -project but ask that discussion stay on the list? [22:18:46] basically what's gonna happen is that you'll have people asking for agenda items all over the place. [22:18:58] council alias, personal email, every list you can imagine, even irc [22:19:16] unless you say this is how you do it [22:19:40] yeah discussion should definitely be on the list. [22:19:54] as ulm pointed out, bugs just aren't a great format for long threads [22:19:54] dberkholz: ++ for trustees recently that became a problem so we've been trying to log bugs for everything. Bugs are good for tracking. [22:20:04] But discussion elsewhere. [22:20:34] dberkholz, you mean -project@ not council@ ? [22:20:56] Ok, so we tell people to 1) assign a bug to council and 2) link to it in a post on -project and the discussion should take place on -project. [22:21:10] when i say list, i'm referring to a mailing list. -project or -dev [22:21:17] i will not say list if i mean alias =) [22:21:18] WilliamH: yes and (NeddySeagoon Iguess that answers the question) [22:21:48] NeddySeagoon: is that how the trustees do it? [22:22:04] dberkholz, I'm not really a techie :) I just wanted to ensure discussion was public, as far as possible [22:22:17] ok I suggest we formalize that with a vote, let me write down a proposal [22:22:21] yep that's my preference too. open by default [22:22:38] NeddySeagoon: How are agenda items proposed and discussed by the trustees? [22:22:44] WilliamH Yes, its public as far as possible, [22:23:12] WilliamH: The trustees just publish agendas on the IRC topic line and add to it whatever comes in via email, lists, bugs, ESP, whatever. [22:23:15] A very informal process. [22:23:28] Many end up getting logged as bugs if they aren't handled immediately. [22:23:33] WilliamH, we invite email to trustees@ and post the growing agenda in /topic in -trustees [22:23:38] The documentation of resolution is more formal. [22:23:40] 9: "For adding an agenda item for consideration by the council we request 1) assign a bug to council and 2) link to it in a post on -project or -dev; the discussion shoudl take place on -project or -dev" [22:23:55] how about this? [22:24:10]