17:10:10 #startmeeting FAmSCo 2014-02-24 17:10:10 Meeting started Mon Feb 24 17:10:10 2014 UTC. The chair is sesivany. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:10:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:10:11 #meetingname famsco 17:10:11 The meeting name has been set to 'famsco' 17:10:11 hi sesivany got kicked? 17:10:15 #topic Roll Call 17:10:19 .fas robyduck 17:10:19 robyduck: robyduck 'Robert Mayr' 17:10:21 .fas lbazan 17:10:22 LoKoMurdoK: lbazan 'Luis Enrique Bazán De León' 17:10:25 .fas tuanta 17:10:25 tuanta: tuanta 'Truong Anh Tuan' 17:10:32 robyduck: not only that, I couldn't reconnect. 17:10:43 .fas eischmann 17:10:44 sesivany: eischmann 'Jiri Eischmann' 17:10:57 I saw, yes, a lot of people just at 17UTC 17:11:30 This is the first meeting of the new FAmSCo term? 17:11:42 yes 17:11:44 tuanta: 17:11:50 #info This is the first meeting of the new FAmSCo term? 17:12:01 #undo 17:12:09 tuanta: yes 17:12:17 #topic Announcements 17:12:22 ! 17:12:27 LoKoMurdoK: go ahead 17:12:44 Fedora Treasurer badges now ready! sesivany tuanta aeperezt have this badges 17:12:53 eof! 17:13:07 LoKoMurdoK: nice, thanks! 17:13:09 Cool :) 17:13:26 #info Fedora Treasurer badges have been issued. 17:13:50 #info FAmSCo activity in the last term: http://eischmann.wordpress.com/2014/02/18/famsco-in-f20-term/ 17:14:03 I worked on some stats. 17:14:18 nice 17:14:44 #info This is the first meeting in the new term. 17:15:24 sesivany: Nice, thanks 17:16:08 what we have to do today: elect a chair for this term, discuss a meeting time for this term. 17:16:21 but there are still three members missing... 17:16:27 :( 17:16:28 especially the new members. 17:16:33 yes 17:16:49 except the new/old Tuan :) 17:17:08 :) 17:17:14 should we proceed anyway or wait until we have at least 6 members present? 17:18:10 :) 17:18:14 I think it's a rather important vote, let's wait next meeting 17:18:29 sesivany: the new memebers have the info of the meeting time? 17:18:36 members* 17:18:50 I am not able to make it next meeting 17:19:00 Due to FOSSASIA 17:19:03 oh 17:19:16 tuanta: nice! 17:19:32 robyduck: +1 the next meeting 17:19:46 I think we can do vote for new chair and meeting time on the list 17:19:55 ok, it doesn't make sense to discuss the meeting time either while it's mainly for input of new members. 17:21:02 I personally hope meeting time could be an hour sooner 17:21:03 LoKoMurdoK: Jon was present at the last meeting. 17:21:46 sesivany: yes! 17:21:55 It's much more convenience to me 17:21:57 tuanta: with summertime it's going to be an hour later here :) 17:22:08 ok, let's start with a normal topic. 17:22:10 it's true.. 17:22:19 sesivany: +1 17:22:59 #info Voting about new famsco chair and meeting time discussion will be moved to the mailing due to 3 members missing at today's meeting. 17:23:19 #topic Reviewing process of selection/approval of mentors for ambassadors 17:23:28 .famsco 259 17:23:29 https://fedorahosted.org/famsco/ticket/259 17:23:39 I saw this topic brought up again. 17:24:07 ah yes 17:24:36 We should close it, the ticket is not more up to date I think 17:24:52 robyduck: +1 17:24:53 There were a lot of changes in the process 17:25:08 robyduck: but IMHO there should be a way to "revoke" a mentor. There is none currently. 17:25:31 yes, true, but this is not related to that ticket 17:25:59 +1 sesivany and robyduck either 17:26:00 * robyduck prefers to have a new one filed for this special topic 17:26:02 I think you should open a ticket with the current process 17:26:24 yes, you're right that the ticket topic is outdated. 17:26:39 I'm going to close it. 17:27:09 ok, but we can surely try to define a new process to revoke mentors 17:27:57 robyduck: +1 17:28:04 although I think most of the active mentors have responsibility enough to step back by their own if they can't do their job anymore 17:28:10 mmm period, work, inactive? 17:28:11 it's not only about mentors. I think we should also think about revoking ambassadors, too. I know the whole topic is on and on again, but mainly because it hasn't be resolved. 17:28:54 robyduck: yes, in the ideal world, people would step down, but as we can see it doesn't work that way. 17:29:33 sesivany: we did a first step in that direction by cleanuing up the ambassadors process and FAS group 17:29:52 for F21 term we should really go on working on that, I agree 17:30:26 but I think there are different criterias between mentors and ambassadors 17:30:39 Sure 17:30:52 my basic idea is that regions can propose FAmSCo to revoke a mentor if they agree that they're not satisfied with his/her work and FAmSCo needs to approve it. 17:30:52 +1 robyduck 17:31:09 create guideline to revoke ambassadors and guideline for mentors 17:31:13 sesivany: yes 17:31:16 +1 17:31:46 sesivany: yes, that's a good starting point 17:32:11 I think if a regional community agrees that the mentor or ambassador doesnt work well or at all and at least 5 other ambassadors vote for it, there is a strong sign that it's true. 17:32:24 sesivany: +1 17:32:39 I think mentors should attend regional meetings, at least once per quarter or something 17:32:53 * robyduck is a bit concerned about that easy process 17:33:10 we can always tweak nuances if there are any abuses, but basically it could work. 17:33:34 robyduck: why? do you think it can be abused? 17:33:46 yes, it's like a ticket 17:34:21 you can easily get 5 votes, exspecially in metings were not so many ambassadors show up 17:34:39 5 votes in regional meeting and them pass to famsco to confirm the revoke? 17:34:48 but if you mean the vote is just for a proposal to FAmSCO, why not 17:35:17 robyduck: yes, but then you need to defend your decision in front of famsco. Do you think we would approve such a decision if the other party gave us at least a bit of proof that the claim is false? 17:35:53 robyduck: no, there needs to be at least two-step process. 17:36:06 the mentor must have the ability to say what is happening? 17:36:12 ok 17:36:26 I see some mentors seem suddenly disappear 17:36:43 yes, we should also involve the mentor once he gets the "5 votes" from his Region. 17:36:46 LoKoMurdoK: definitely, the mentor and ambassador will have to have an opportunity to defend himself/herself. 17:37:14 So count his/her attendance in regional meetings could be a sign 17:37:16 ok, that sounds good 17:37:22 in the other case (ambassador) the mentor can create ticket in famsco to request revoke 17:37:29 I think they should prove that they've tried to contact the person before the vote to get his input. 17:37:37 and ambassador say what happening.. 17:37:43 .. 17:38:14 we should speak just for mentors now 17:38:17 Unless he/she does not respond for xxx weeks 17:38:35 frankly, >90% of cases will be: 1. someone completely inactive and/or unresponsive, 2. someone who violates the Fedora values a lot, obviously. 17:38:44 sesivany: +1 17:38:49 both cases are pretty clear. 17:39:01 I like the workflow: 1) revoke proposed by Region with 5 votes 17:39:20 2) FAmSCo contacts mentor asking what's happening 17:39:32 3) Final FAmSCo decision 17:39:42 robyduck: +1 good very simple! 17:39:46 I've got one example for the second case... 17:40:02 step 2 can be done also with a ticket 17:40:14 so it's public 17:40:22 We should have deadline beetwen step #2 and #3 17:40:24 one ambassador in EMEA ordered a polo shirt when it was still paid for, cwickert paid for it, sent it to him and never saw money. 17:41:05 :( 17:41:06 :O 17:41:08 :S 17:41:15 :O 17:41:30 the guy never wrote back. I don't know if he is still an ambassador, but if he is, it's a shame because I don't want such a person among us, someone who pretty much robbes money from a fellow contributor. 17:42:00 that's why I think we DO need a revoke process. 17:42:52 sesivany: create the first ticket! 17:42:57 :( 17:43:06 LoKoMurdoK: yes, I will. 17:43:26 I also think we should have some easier process for those who become active again. 17:43:52 sometimes it doesn't have to be your fault that you become inactive without stepping down. 17:44:13 this process should come hand-to-hand with the revoke process. 17:44:22 sesivany: in the second case any mentor can create a ticket revocation 17:44:33 cwickert: hi 17:44:36 sesivany: yes, but mentors don't raise high obstacles if someone comes back I think, but we could define that too (hopefully we don't make too much rules) 17:44:42 cwickert: we were just discussing your case :) 17:46:23 robyduck: I think it should only apply to ambassadors. If you want to become a mentor, the procedure should be the same, you should work reliably as an ambassador and then you can become a mentor. 17:46:58 sesivany: +1 17:47:02 in other words, it should not be easier for them just because they used to be mentors in the past. 17:47:14 yes sure, only for ambassadors 17:47:36 moreover, new nominations of mentors usually come from need for one. 17:47:55 so if the region needs a new mentor they can nominate him any time. 17:48:59 minimum 6 months active ambassador ? :-) 17:49:00 What us going on if most mentors in a region are unresponsive 17:49:26 s/us/is 17:49:54 tuanta: need change! 17:50:02 ok, so basics are: we want a revoke process for contributors who are clearly inactive or obviously violates Fedora's values, the process should have two-levels (region, famsco) and there should be an easier process for ambassadors who got revoked and want to become ambassadors again. 17:50:23 sesivany: +1 17:50:26 tuanta: btw, shakti had a dozen of active tickets in the FAMA track... 17:50:45 sesivany: +1 17:50:59 tuanta: revoke them! better no mentor than a mentor who just seems to be active, but in fact he's not. 17:51:12 Yes. And now we need other APAC mentors to take them over 17:52:09 #info FAmSCo will start on a revoke process for mentors and ambassadors. Basics are: we want a revoke process for contributors who are clearly inactive or obviously violates Fedora's values, the process should have two-levels (region, famsco) and there should be an easier process for ambassadors who got revoked and want to become ambassadors again. 17:52:19 sesivany: In some cases, it is hard to get nomination from existing mentors 17:52:53 tuanta: well, that's candidate for another change perhaps. 17:53:00 since they seems not response any messages 17:53:14 nominations only from existing mentors seems to be a bit outdated condition. 17:53:35 it was set in the time when we didn't have the region-based community. 17:53:58 nowadays, I think nominations from regions make more sense. 17:54:11 sesivany: +1 17:55:06 wow 17:55:12 Do we want to keep the double nomination criteria: Regions *or* FAmSCo member? 17:55:12 With that way, the number of mentors in a region could be increased much 17:55:21 seems I was not really online, sorry, I thought you were not :) 17:55:36 sorry to be late, blame pidgin 17:55:39 cwickert: yes, it happened to me at the beginning of the meeting, too. 17:55:45 robyduck: regions and famsco no? 17:55:51 cwickert: yes, I'm also using Pidgin :) 17:55:52 5 votes and then in famsco ? 17:56:07 LoKoMurdoK: mentors are appointed by FAmSCo now, too. 17:56:15 LoKoMurdoK: it's just about nomination. 17:56:17 can somebody quickly give me a some info what we are discussing? 17:56:21 sesivany: a ok 17:56:22 ok 17:56:28 * cwickert can only see half of the backlog 17:56:40 cwickert: evergreen topic: revoke process for ambassadors and mentors. 17:57:12 oh noes! 17:57:24 :D 17:57:40 Frankly speaking I don't see the need to revoke any status 17:57:49 cwickert: we'd like to cover at least cases when the contributor is inactive obviously long term or violates Fedora values a lot :) 17:57:50 it should be fine to mark people as inactive 17:58:03 cwickert: yes, but the requests come again and again. 17:58:12 define "long term" 17:58:40 if somebody violates the guidelines, ok 17:58:59 cwickert: that's a topic for discussion, I think 3 months sound reasonable. 17:59:04 but inactivity is hard to measure and should IHMO not be a critieron 17:59:09 srsly? 17:59:26 cwickert: well, more precisely unresponsiveness. 17:59:32 ah 17:59:40 unresponsive to what then? 18:00:03 cwickert: you cannot measure inactivity, but if someone can't even let others know, then he is probably very inactive :) 18:00:24 I mean, I see the need for a mentor to respond, but to what requests does a mentor receive that need to be responded to in time? 18:00:47 sorry, in the 2nd case I meant "ambassador" 18:01:31 cwickert: the idea was to let the regions nominate ambassadors/mentors who are unresponsive in long term, they should try contacting him during the process. 18:01:47 but why? 18:03:18 I really see no use-case here 18:03:22 cwickert: well, sometimes people try to contact ambassadors and it doesn't look very healthy if half of them never answers. 18:03:31 so? 18:03:52 just to make us look "more healthy" to some outsiders? 18:04:05 for Fedora community members it should not matter 18:04:13 * bckurera interesting discussion all time :) 18:04:14 and they probably know who is active and who not 18:04:17 sesivany: weren't we talking about mentors only for the regions proposal? 18:04:18 cwickert: there are countries such as Brazil where there are 40 ambassadors and maybe 10 of them are somehow active. 18:04:33 sesivany: so? I still don't see the problem 18:04:45 we can ask them if they still want to be ambassadors 18:05:06 but I don't see any reason nor a justification to revoke a status 18:05:13 cwickert: I do see a problem, the ambassadors are point of contact for outside of the community, if 3/4 of them are completely unresponsive, I think it's a problem. 18:05:44 and it will become a bigger problem as the project gets older, at some point 90 % ambassadors in our list might be inactive. 18:06:03 and there wont be any point to have something like ambassadors membership. 18:06:05 ok, how many contact requests do we really get? 18:06:35 I mean, we go to events and showcase Fedora, but it's not like somebody asks us to do something every other week 18:07:10 I am a very active contributor and in 6 years that I am ambassador, I received like 5 mails if not less 18:07:34 and most of them probably because I was also in FAmSCo, FESCo or the board 18:07:45 cwickert: ok, let's put it the other way: what's so wrong on having an option to revoke an ambassador? 18:08:10 sesivany: I think every status people achieved is basically for lifetime. 18:08:36 I know ambassadors who are inactive 360 days of the year but then they do this one event every year 18:08:50 cwickert: and that's probably the difference between our opinions :) 18:08:54 are they responsive? probably not! are they good ambassadors? yes! 18:10:12 what about extend the unresponsiveness or whatever period then? I think it should not be for lifetime, nothing is for lifetime. 18:10:13 sesivany: would you want to remove jens' ambassadors status? 18:10:47 cwickert: well, it's a matter of regional vote. If someone knows that they're good ambassadors, he can easily speak up. It's not that we say: those ambassadors don't meet these criteria and need to be removed. It's about giving regions and countries an option to revoke inactive ambassadors if they don't feel comfortable having 30/40 ambassadors inactive. 18:10:49 there are a lot of ambassadors which don't do anything for 2-3 years now, they are not really ambassadors. 18:11:20 I beg to disagree, robyduck. at least from the people I know 18:12:00 cwickert: do you think we in EMEA would vote to revoke Jens as an ambassador? 18:12:36 sesivany: that is a different question. Before discussing the process I need to understand the usecase 18:13:04 I think the mentors need the process, the ambassadors we must review.. 18:13:10 cwickert: probably you don't have the examples I have in my mind, and Jens should not be kicked IMHO. We are not meaning that kind of ambassadors, if I get it correctly. 18:13:46 but I would continue with this topic in a ticket I will create. we're a bit over time now. 18:14:11 robyduck: I don't think we in EMEA have this problem. There will be somebody in the meeting to speak up for jens. but can we sure this works in the other regions as well, even if there only 5 people at the meeting? 18:14:16 sesivany: +1 18:14:26 sesivany: +1 18:14:28 if we start this discussion, we should do it systematically 18:14:38 I think the core question is if we think that ambassador membership is a status for lifetime or not. Then we can move on further. 18:15:01 ok agree with cwickert, let's do it step by step 18:15:37 robyduck: +1 18:15:38 #info Topic on ambassador/mentor revoking process will be discussed further in a ticket in FAmSCo trac. 18:15:39 and that means: 1. define the target audience (ambassadors, mentors), 2. define the criteria, 3, define the result (revocation, inactive, ...) and 4. define the process 18:15:48 #action sesivany to create a ticket on this topic. 18:16:02 cwickert: +1 18:16:08 please send the link to famsco list, I will then add my thoughts 18:16:46 I would like all famsco members to describe if they see a problem in their region and if so, what it is (only a few ppl, many etc) 18:16:52 would that work? 18:17:01 cwickert: sure 18:17:56 * cwickert feels like he crushed a party when he entered the meeting. seems everybody but me agrees 18:18:09 * cwickert loves to crush parties :) 18:18:24 sorry for making the meeting extra-long and being so vocal then 18:18:29 cwickert: we were going to discuss it futher in a ticket anyway. 18:18:45 cwickert: no, I appreciate your input. 18:19:03 you *need* to be vocal 18:19:08 * sesivany will have to leave soon, is that it for today? 18:19:18 sesivany: +1 18:19:20 I think so sesivany 18:19:25 cwickert: :-) 18:19:48 ok, thank you for attending today and meet you next week! 18:19:52 #endmeeting