15:02:06 #startmeeting FAmSCo 2017-03-15 15:02:06 Meeting started Wed Mar 15 15:02:06 2017 UTC. The chair is robyduck. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:06 The meeting name has been set to 'famsco_2017-03-15' 15:02:15 #meetingname famsco 15:02:15 The meeting name has been set to 'famsco' 15:02:24 #topic Roll Call 15:02:49 .hello robyduck 15:02:50 robyduck: robyduck 'Robert Mayr' 15:02:53 .fas jonatoni 15:02:54 jonatoni: jonatoni 'Jona Azizaj' 15:03:13 fas mailga 15:03:22 #chair fredlima jonatoni mailga itamarjp 15:03:22 Current chairs: fredlima itamarjp jonatoni mailga robyduck 15:03:23 * jwf waves 15:03:34 hi jwf 15:03:40 .fas itamarjp 15:03:40 itamarjp: itamarjp 'Itamar Reis Peixoto' 15:03:41 .fas fredlima 15:03:43 fredlima: fredlima 'Frederico Henrique Gonçalves Lima' 15:03:44 .fas mailga 15:03:46 mailga: mailga 'Gabriele Trombini' 15:04:03 .hello bex 15:04:05 bexelbie: bex 'Brian (bex) Exelbierd' 15:04:21 bexelbie: o/ 15:05:02 #topic Updates for mentor's and ambassador's status 15:05:04 o/ alle 15:05:18 hi bexelbie 15:05:23 ok so these are quick updates, I don't think we are through yet 15:05:34 giannisk is not around, so jonatoni any updates? 15:05:55 so robyduck helped me to run the ambassadors script 15:05:59 this is https://pagure.io/famsco/issue/417 15:06:41 now I have the svg file and I'm preparing the email to send to the ambassadors 15:06:52 .hello jflory7 15:06:53 jwf: jflory7 'Justin W. Flory' 15:06:57 and I need to do another script to send them an email 15:07:13 I mean to those that were active the last 18 month 15:07:34 svg? 15:08:19 sorry csv file 15:08:51 you should have a cvs and can just order the nicknames. Make a file and you will be able to add the email alias easilz 15:09:29 csv that is 15:09:40 yeah, but I was thinking that I have ~500 emails to send for example 15:09:46 and I cant do it manually 15:09:58 uuh? 15:10:23 jonatoni: how many people were active last time more than 18 months ago? 15:10:29 500?? 15:10:52 no was just I guess, I haven't checked them yet 15:11:02 s/I/a 15:11:32 ah ok 15:12:38 If the current script doesn't send email, jonatoni and I were talking about a way to automate mass email with the FAS API / SMTP service like SendGrid 15:12:50 I did it last time by copying pasting all addresses, no script 15:13:30 all addresses in CCN, not to: and not CC: 15:13:56 yes 15:13:57 and used just sed to add the @fedoraproject.org 15:15:08 jonatoni: if you don't mind I can help you with that, then you can send out the email 15:15:39 yeah sure, that would help me a lot 15:15:41 thanks 15:15:57 we should mention people have 2 weeks to make some activity (login to one of our servers), and we will un the script again at the end of march 15:16:28 jonatoni: sure thing, then let's move on if you have nothing else to add to this? 15:16:31 any other? 15:16:39 eof 15:17:27 giannisk is not around today, let's see if we can have an offline update in the ticket about mentors activity 15:18:16 before discussing the mentoring process, can we decide aboout the ML ticket? 15:18:34 that should be quicker (hopefully) 15:19:03 #topic Take final decision whether open/set private/whatever the FAmSCo mailing list 15:19:13 #link https://pagure.io/famsco/issue/419 15:20:03 I missed getting my response in the ticket (probably not worth finishing now), but Brian's suggestion seemed reasonable to me. 15:20:07 * robyduck tried to put together some pros/cons on that, and bex added his thought too 15:20:11 https://pagure.io/famsco/issue/419#comment-430670 15:20:53 jwf: to take FAmSCo discussions completely to the ambassadors list? 15:21:18 and set FAmSCo as private? 15:22:19 I really think making the discussions and activity with FAmSCo more accessible is important. 15:22:28 So long as the private list is strongly avoided whenever possible 15:22:34 Similar to the private Council mailing list. 15:22:58 jwf: private lists are used *only* in special topics 15:23:39 So long as that is the condition (and maybe written somewhere too since all seats can change, unlike in Council), I think it makes sense. 15:23:45 jwf: so,, do you think that would improve communication between FAmSCo and ambassadors? 15:25:03 robyduck: So long as FAmSCo discussion does actually happen on the public list, then yes. I think it would be a meaningful to better involve and inform a wider community to FAmSCo's activities and give them a platform to also have input if they have something to contribute. I'm personally favorable to two public lists, but I think I'm few in that opinion. 15:25:24 Sorry for slow responses, a little distracted offline 15:26:18 jwf: well, two public lists is what we shoudl avoid IMO 15:26:20 I am curious what business of FAmSCo you think is not important to Ambassadors jwf? 15:26:36 as that is what would be on public ML #2 15:27:17 robyduck: Right, which is why I'm not holding to that. I also like bexelbie's proposal in the ticket. 15:28:14 ok, we can start a voting here but we don't have a valid quorum today AFAICS 15:28:33 bexelbie: My original motivation behind two public lists was that it allows a level of choice for Ambassadors to whether they want to involve themselves with FAmSCo activity and discussion, whereas on the Ambassador list, it's a list of maybe 700-1000 people. I wasn't sure if some of them might have an issue with the extra noise, but then I also realized that if FAmSCo activity feels like extra noise as an Ambassador, they might not be the most 15:28:34 active Ambassador either. 15:28:48 .fas giannisk 15:28:50 giannisk: giannisk 'Giannis Konstantinidis' 15:28:53 * giannisk waves at everyone 15:29:03 aha, so we have a quorum now 15:29:07 hi giannisk 15:29:34 we are going to vote about the FAmSCo ML proposal, let me rephrase that 15:30:05 final proposal for ticket 419: Do you want to take all FAmSCo discussions to the ambassadors list and set FAmSCo ML as private, for only specific and sensible topics? 15:31:00 this is thought to improve communication between FAmSCo and ambassadors (as the ambassadors list is also invite only) 15:31:21 I am +1 on this 15:31:31 +1 15:31:37 +1 15:31:46 -1 15:32:04 We cannot take all FAmSCo issues on the ambassadors ML, simply because we risk dropping the ball 15:32:33 -1 15:32:36 I'd agree we can however take important FAmSCo issues to the ambassadors ML, which would require important feedback from the majority of the ambassadors 15:33:10 giannisk: the ambassador list is not so noisy, and we are discussing mainly tickets in the list 15:33:20 which are public 15:33:25 What I'm afraid of here, is the fact we risk making communications and decision making less effective 15:33:51 robyduck: The ambassador ML in fact, gets extremely noisy when it comes to decision making 15:33:53 and why less effective? 15:34:31 robyduck: Imagine dozens of replies over a single thread, regularly involving passive aggressiveness among community members 15:34:38 It's what we've seen several times so far 15:34:39 giannisk: yes, true. But it is also wrong to decide something in a dark corner and get this out to all others when it is already done, or? 15:34:55 I'd personally avoid having "fights" over the ambassador ML 15:34:59 giannisk, passive aggressiveness is bad and should be stopped. Ambassador input should be welcome, with FAmSCo bringing it to a close as appropraite 15:35:20 giannisk: right, but should we avoid that by keeping communication less effective? 15:36:26 giannisk: I see your point, and it's true, but how many things do we discuss over the ML? And how many in the tickets? 15:37:00 bexelbie, robyduck: I totally get your points also, but I'm personally not yet convinced whether we can succeed in effectively facilitating those discussions over the ambassador ML 15:37:06 I saw a lot of noise when we changed the processes, but what came out was also good 15:37:24 giannisk, and for that reason we shouldn't try? If we don't try, how will we ever know we are "ready" 15:38:18 bexelbie: That's true and I was also considering the same in fact. We could possibly try this as "pilot program", yes. 15:38:51 I am not aware of any other groups that have two mailing lists, one for members and one for "leaders" 15:38:55 are there any others in Fedora? 15:39:42 bexelbie: None that I'm aware of 15:40:02 not off-hand, but members and leaders should always find the best communication 15:40:07 Is there something about Ambassadors that inherently means it needs to be different? 15:41:02 the main change would be to change notifications in pagure and send them out to the ambassadors list instead of the FAmSCo ML. We are actually not discussing so much on the FAmSCo list 15:41:11 bexelbie: The major difference I see is, the ambassadors sub-project is much larger compared to several other ones. 15:41:27 no comes this nonsense again 15:41:35 Which means we need to be a bit more careful when it comes to facilitating discussions between members. 15:42:10 gnokii, please be civil 15:43:52 bexelbie I am, but why you think openess on the ambassador list will change anything as long famsco relativates concerns of ambassadors and ignores them nothing will change 15:43:53 I'm willing to explore new ways, but I ask that we should please keep some things in mind: a) try and have some tips/rules/whatever for ambassadors that wish to chime into topics to provide feedback effectively, b) have a plan to deal with non-effective communications, especially when they get out of hand (e.g. passive aggressiveness) 15:44:36 giannisk, I think those are great points. I hope you won't see them as blockers. 15:44:39 giannisk: I see also positive inputs with that, even if some might be strong, at the end FAmSCo will consider them to make its own decision 15:46:04 giannisk: bexelbie: we need to write a communication to the ambassadors list about the change, and could include some points people should be aware of 15:46:25 sounds like a good plan 15:46:30 robyduck: +1 15:46:43 but for now we have 3 +1s and 2 -1s, this needs to go to the trac anyway 15:46:55 oh 15:46:57 don't need, I will change my vote to +1 15:47:06 bexelbie make me get the point 15:48:08 #agreed FAmSCo will take all FAmSCo discussions to the ambassadors list and set FAmSCo ML as private, for only specific and sensible topics 15:48:47 robyduck: It's a +1 from me as well, as long as we communicate with the ambassadors and include some of those points 15:48:50 robyduck: So yes :) 15:49:07 #info This will imply communication to the ambassadors of the change and include some points people should be aware of when participating to FAmSCo discussions 15:50:03 #action robyduck to change ticket notifications in the pagure repo 15:50:44 should I also write to the ambassadors list? does anyone else want to do that? 15:51:49 ok will do that too :) 15:51:59 robyduck++ 15:52:15 #topic Open Floor 15:52:55 I have a question related to the readiness meeting 15:52:59 we don't have time to start the mentor nominating stuff, but could you read my proposal for next time? 15:53:10 mailga: yeah, I was digging up the schedule 15:53:59 #link https://fedorapeople.org/groups/schedule/f-26/f-26-ambassadors-tasks.html 15:54:31 actually we have one upcoming task by the end of march 15:54:33 FAmSCo and Regional teams call for Preparation of Media/SWAG 15:54:35 By the way, I will hopefully update the ambassador mentor's wiki page today. I will send another reminder to mentors who did not reply back to me - If they do not reply back again within a week, I will mark them as inactive (with an option to be reinstated if they wish in the near future) 15:54:59 giannisk++ 15:54:59 robyduck: Karma for giannisk changed to 7 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:55:21 mailga: you question? 15:55:26 So far, about 60-70% of mentors replied. 15:55:40 s/you/your 15:56:07 giannisk: this is quite good 15:56:23 robyduck: seems we are up to date at the moment, since the Media/Swag period didn't start yet. 15:56:29 Is true? 15:56:39 yupp 15:57:14 I am also not aware of anything for which ambassadors are not ready (if you mean the readiness meeting) 15:57:48 robyduck: Jan asked me to be there for the ambys part, and I can make it. Yeas the readiness meeting. 15:57:57 s/Yeas/Yes 15:58:06 cool 15:58:11 that's all from me. 15:58:38 mailga: thanks 15:58:45 anything else for today? 15:59:48 nope 16:00:09 thanks for coming, see you next week 16:00:25 thanks for chairing robyduck 16:00:32 #endmeeting