18:06:32 #startmeeting cwg -- http://fedoraproject.org/wiki/Fedora_Community_Working_Group 18:06:32 Meeting started Tue Jan 4 18:06:32 2011 UTC. The chair is bpepple. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:06:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:06:50 #meetingname cwg 18:06:50 The meeting name has been set to 'cwg' 18:07:11 ping red_alert rbergeron nirik mjg59 18:07:16 * rbergeron is here 18:07:19 * nirik is around. 18:07:27 #topic roll call 18:07:27 all caffeinated and ready to rummmmmmbbbbllllllllllle 18:07:34 * rbergeron 18:07:39 * red_alert 18:07:49 18:08:17 #info nirik rbergeron red_alert bpepple mjg59 present 18:08:42 ok, looks like we've got everyone here. ;) 18:09:05 #topic agenda 18:09:24 ok, I'm not sure where we left things at from our last meeting. 18:10:00 I think mjg59 was going to come up with a draft Code of conduct for us to look at and discuss? 18:10:09 prabindatta_: ? 18:10:19 * prabindatta_ sorry 18:10:24 Yes, and I utterly failed to 18:10:28 Apologies for that 18:10:52 I've got some bare bones, I'll try to finish that off this afternoon 18:11:15 mjg59: that works, and then we can discuss that on the mailing list & at our next meeting. 18:12:02 #action mjg59 will draft a code of conduct and send it to the mailing list for discussion. 18:13:03 alright, do we want to discuss enforcement again, or is there something else folks would like to discuss? 18:13:39 sure, we could talk about enforcement. 18:14:13 +1 18:14:44 I'll reiterate that I think we should try and have enforcement happen in the area where the issue takes place... 18:14:56 #agenda Conduct enforcement 18:15:04 I think we'd left it with the idea that existing authorities handle things where possible (ie, IRC, forums and the like) 18:15:06 oop. 18:15:15 #topic Conduct enforcement 18:15:30 yeah. Of course sometimes people are not going to be happy with what happens/doesn't happen. 18:15:34 mjg59: correct. that seems the sanest solution. 18:15:46 Right 18:16:11 If people are unhappy with the result then I think we need a group of people who are trusted to decide whether or not things were handled appropriately 18:16:21 But final enforcement pretty much has to come down to the board 18:16:24 nirik: they can the escalate disagreements to a higher body (Board, CWG, or something else) can't they. 18:16:29 right. 18:16:48 I guess I would say as a first cut: 18:17:00 try and solve at the local level 18:17:02 I don't think we want to create a group of people who themselves have the power to exclude people from project resources 18:17:20 Merely a group who can say "This should probably have been handled differently" and then refer it back to the local level 18:17:44 yeah, I was thinking of perhaps CWG being a mediation level. 18:18:06 ie, talking with the group and providing input for how to better handle things like that. 18:18:16 I figure we're also supposed to find out how to best deal with any kind of conflicts within the project and this is just one type of such conflicts 18:18:51 in specific cases where someone feels unfairly treated, should we just ask the board to look at it if local and mediation doesn't solve their issues? 18:18:53 so we should probably set up a SOP for all kinds of conflicts we're supposed to handle/support/mediate 18:18:59 yeah 18:19:05 That's true 18:19:13 nirik: similar to how FESCO sometimes recruited a third party to arbitrate disagreements. 18:19:25 yeah. 18:19:31 the "special prosecutor" model. 18:19:42 So, we should probably talk a little about what seems in-scope 18:20:04 For instance, the discussion about the request for F15 to ship with upstream's GNOME artwork 18:20:16 There was certainly community disagreement on that issue 18:20:44 Is that the kind of thing we should be looking at, or is the working relationship between Red Hat, the board and the community the board's responsibility? 18:20:45 mjg59: yup. some of the art team wasn't terribly thrilled about that. 18:21:28 well, I don't think it should be up to CWG to solve all community disagreement. 18:21:41 we should try and make sure the discussion is nice 18:21:54 nirik: No, but should we try to work on how decisions are presented? 18:22:17 mjg59: well, what decision are we talking about here? 18:22:24 Not so much the decision 18:23:00 But should we limit ourselves to behavioural standards, or also look at the kind of generic issues that can trigger ill-tempered discussion? 18:23:11 ah, I see what you are saying... 18:23:45 ie, should we do something like write best practices documents for groups to present their decision making process rather than things just appearing as fait accomplis? 18:24:25 I don't know that we should be in the business of making groups adhere to specific processes for decision making. 18:24:33 Or recommending, really. 18:24:42 well, it's going to vary a bit I fear too... 18:24:53 Every group is different 18:24:59 and every situation is different 18:25:05 rbergeron: I was thinking of presentation, not the process itself 18:25:14 I'm happy for us to feel that it's out of our scope 18:25:37 ideally, I would like to see folks step in where there is something like this and urge calm and reasonable discussion in the right place. 18:25:42 But it's something that has an impact on the community interaction, so I think we ought to at least decide where our boundaries are 18:26:18 so, perhaps for us it would be nice to make a Putting_out_flamewars_SOP :) 18:26:25 I think our boundaries should be: If someone asks for help or mediation, we should be willing to give it. We shouldn't be going out of our way to find situations, or to implement processes to "fix" things that aren't yet broken. 18:26:34 I'm kind of a hands-off person, though :) 18:27:29 rbergeron: I think anything we did in this respect would be purely as advice, with no expectation that failing to follow that advice should result in bad things happening 18:28:10 But, like I said, I'm not wed to the idea of us doing this :) 18:28:14 * rbergeron nods 18:28:21 I think a document for mailing lists like freenodes http://freenode.net/catalysts.shtml would be good to have and point people to. 18:29:38 so, perhaps we should focus on code of conduct stuff for now? 18:29:45 I think that's fair 18:29:53 We seem to have agreement that it's a good starting point for discussion 18:30:15 might be best. I don't think mjg59 suggestion is a bad idea, just might be worth giving some more thought down the road. 18:32:40 so, back to enforcement for a bit. Is everyone in agreement that existing authorities handle things where possible, and disagreements be brought to a higher authority for some type on arbitration? 18:33:17 Yes, and I'd say that the initial focus should be on mediation 18:33:18 that sounds reasonable to me. 18:33:41 I also think we should make sure to have a 'buck stops here' place... which I assume would be the Board. 18:33:49 Right 18:33:57 sounds good. just wanted to make sure so we could mark it in the minutes. 18:34:01 and hopefully they could vote/rule/whatever on things in a timely manner. 18:35:14 #agreed existing authorities handle conduct enforcement where possible, and disagreements be brought to a higher authority for some type on arbitration, with the Board being the final 'buck stops here' place. 18:36:01 ok, so is there anything else in regard to enforcement anyone wants to add? 18:37:03 alright. moving on then... 18:37:06 I think after we have a (first version of the) code of conduct we should get in touch with all authorities to find out what they think about the code and its enforcement 18:37:41 and their role in the latter 18:38:24 I'd say if we get a c-o-c we like, we should ask the board what they think, then if they like it ask for more widespread input... 18:38:39 and yeah, asking places that would have to enforce it seems like a good idea. 18:39:01 nirik: seems reasonable to me. 18:39:05 Yes. I don't think we can justify the implementation of anything like this without talking to the community as part of the process 18:39:16 * nirik nods. we need community buy in for sure. 18:39:22 But clearing it with the board first before moving on to that step seems reasonable 18:39:28 #topic misc 18:39:36 +1 for asking the board first, probably fesco next 18:39:39 The obvious people we need to talk to are IRC operators and forum moderators 18:39:48 and mailing list admins. 18:39:50 mailing list mods. 18:39:51 Yes 18:40:50 SIG/project commitees as well 18:40:55 alright. is there anything else we need to discuss this week, or should we start to wrap it up? 18:41:04 * nirik is still not sure a c-o-c will help us any, but I guess it's really just a more detailed version of 'be excellent' 18:41:13 lol 18:41:14 yep. 18:41:37 it's worth a try 18:41:42 if nothing else :) 18:42:52 does this meeting day & time still work for everyone? 18:43:08 indeed. 18:43:16 fine with me usually. 18:43:17 Works for me 18:43:17 couldn't work any better for me :) 18:43:51 works for me also. so let's plan on meeting next tuesday at this time. 18:44:08 +1 18:44:19 anything else? otherwise I think we can put a fork in this meeting. 18:45:18 * nirik has nothing. 18:45:27 ok, thanks for your time everyone! 18:45:30 looking forward to mjg59's proposal for a code of conduct :) 18:45:31 * rbergeron is out of commentary ;) 18:45:37 #endmeeting