17:00:04 #startmeeting FAmSCo 2014-03-10 17:00:04 Meeting started Mon Mar 10 17:00:04 2014 UTC. The chair is sesivany. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:04 #meetingname famsco 17:00:04 The meeting name has been set to 'famsco' 17:00:08 #topic Roll Call 17:00:14 .fas eischmann 17:00:57 robyduck, yn1v: ping 17:01:15 .fas yn1v 17:01:21 lbazan: ping 17:01:30 masta: ping 17:01:33 * yn1v at work 17:02:05 sesivany: pong 17:02:17 * masta is here 17:02:47 was actually an hour early due to TZ change in NA region, lol 17:02:50 sesivany: eischmann 'Jiri Eischmann' 17:02:54 yn1v: yn1v 'Neville A. Cross' 17:03:03 I have no pending items on my job. I hope there are no surprises 17:03:34 .fas parasense 17:03:34 masta: parasense 'Jon Disnard' 17:04:08 masta: yes, here come the two weeks when the US is already on summer time and Europe isn't. We've got a lot of experience with it in Red Hat :) 17:05:07 ok, let's start. 17:05:21 #topic F21 chair vote 17:05:58 .fas robyduck 17:05:58 masta: please cast your vote, it's particularly important because it's a tie now :) 17:05:58 robyduck: robyduck 'Robert Mayr' 17:06:41 .famsco 361 17:06:41 https://fedorahosted.org/famsco/ticket/361 17:06:45 sesivany: yes sir 17:08:13 * masta flips a coin 17:08:16 I am happy that I am not the one to break the tie 17:08:40 it took quite a lot of time this time, we were usually done with it in 15 minutes at the first meeting :) 17:08:56 Heads jiri, tails Christoph 17:09:43 it was the head of coin 17:09:48 * masta goes and votes 17:10:44 * yn1v thinking about short Assimov's story "the machine that won the war" 17:10:45 sesivany: done 17:11:05 damn coin... :-) 17:12:33 not that I don't want to discourage you from candidating next time. But what I've learned in the last year is that the position is just duties and no benefits :) 17:13:03 once I'm more comfortable with our meetings... I'm happy to chair any time. 17:13:11 informally 17:13:28 (somebody is sick, or cannot make it, etc) 17:13:37 now I have to choose a vice chair... 17:14:43 I'm picking tuan. He's from a different region and he's been in FAmSCo for some time already. 17:15:35 makes sense 17:16:00 #info The FAmSCo chair for F21 term is sesivany. Tuan was picked as a vice chair if he agrees with it. 17:16:24 I will have to ask him, but let's assume for now that he agrees. 17:17:36 anyway, thank you for your votes, not only the ones for me, but also the ones for cwickert. 17:18:11 next thing we have to finish is the meeting time... 17:18:22 #topic Meeting time for F21 term 17:18:36 * sesivany is checking the results... 17:19:10 there is a link for looking at the results? 17:19:39 #link http://whenisgood.net/famsco-meeting/results/fak82p3 17:20:36 There are two times with least collisions: 17 and 19. 17:21:17 I would prefer 17 because 19 is like 1-2am for tuan which is not very comfortable. 17:21:21 * robyduck is sorry to be the one who can't at 16UTC, but I have to travel from dayjob, so I could attend only during summertime (UTC+2 here) 17:22:19 sesivany: it should be 16 and 18 UTC right? The time is converted to your time, tight? 17:22:38 * sesivany is not sure if the time is UTC or his local time... 17:22:56 But I guess it's local time. 17:23:49 default is UTC unless you change to local time 17:24:54 yn1v: is there any way to switch it between UTC and local? I don't see such a thing. 17:25:27 but what I see is local. 17:25:37 I was looking for the same, but apparently we only have the option at the first time. 17:26:08 no, I think the system converts the hours to your local time, so I see 17:00 local time and 19:00, which should be 16 and 18 UTC actually 17:27:18 I see the 16 UTC as the best compromise. robyduck, if you can make it during summer time it's still better than having it at 18 when tuan can't attend at all. 17:27:25 and I also could attend at 17UTC (which is the actual meeting time) 17:27:34 ok, let's do it 17:28:01 we will switch soon, and then we will see 17:28:16 Mon doesn't work for several people while Tue does. 17:28:30 so should we move the meeting to Tue 16pm UTC? 17:28:36 For F22/F23 there will be also new elections... 17:29:01 +1 17:29:15 +1 17:29:24 robyduck: we can always revisit the decision if it turns out not to work. 17:29:39 robyduck: even during this term, no need to wait for new elections. 17:29:45 +1 17:29:57 masta: does it work for you? 17:30:00 yea, don't worry, I will try to get it working in some way 17:30:43 It is works hours for me, but usually I can arrange my work schedule. 17:31:30 * lbazan here 17:31:32 sorry late 17:31:36 .fas lbazan 17:31:37 lbazan: lbazan 'Luis Enrique Bazán De León' 17:32:06 yn1v: yeah, I know. aeperezt had to attend the meetings in his work time, too. I think we set the time at 16 UTC for him to have the meeting during lunch break. 17:32:29 +1 17:32:29 sesivany: the times look good to me 17:32:39 16UTC? 17:32:47 ok for me 17:32:57 yes tuesday 17:33:19 robyduck: ok 17:33:21 good! 17:33:35 great, we actually did find some time that suits everyone at least a bit. 17:34:08 #info The new FAmSCo meeting time is Tuesday 16:00 UTC. 17:34:08 It will be 10am for me, like a nice long coffee break :-) 17:35:18 yn1v: there is a time difference between Nicaragua and Panama? I travelled through both countries, but don't remember. 17:35:29 Yes, one hour 17:35:35 * masta goes to adjust his calendar 17:35:40 for new meeting time 17:35:47 :-) 17:36:23 ok, adjust your calendars and let's go finally discuss real problems :) 17:36:35 * lbazan meeting tomorrow (the first) :) 17:36:59 how this works with the meeting channel? 17:37:24 that's a good point. 17:37:56 sesivany: need change meeting time in fedora calendar 17:38:51 there are meetings in #fedora-meeting and -1, but nothing in -2. 17:39:05 sesivany: ok 17:39:20 same channel then 17:39:20 continue in this channel 17:39:30 yn1v: yes! 17:39:31 Sorry, i am late :( 17:39:37 tuanta: == 17:39:39 who will update the entry in fedocal? 17:39:49 our vice chair has arrived :) 17:39:52 masta: the owner.. 17:39:55 tuanta: welcome, you just became a vice chair ;-) 17:40:40 Huh. I am? 17:40:45 tuanta: :) 17:41:11 masta: I will try if I have rights for it, can't log in Fedocal right now. 17:41:30 #action sesivany to change meeting time in Fedocal. 17:41:36 We are discussing the meeting time? 17:41:53 tuanta: yes 17:42:00 tuanta: tuesday 16UTC 17:42:01 tuanta, meeting changed to TUE 16UTC 17:42:12 tuanta: yes, it's Tue 16:00 UTC, hope it works for you. 17:42:22 Ah, thanks :) 17:42:34 tuanta: we went for the earlier of the two possible times not to keep you awake till the middle of night. 17:42:51 Cooler to me 17:43:30 ok, let's move to another topic. 17:44:17 #topic "Inactive ambassadors" issue 17:44:33 did you read the mail from pingou? 17:44:43 his tool looks promising. 17:45:47 it checks all kinds of online activity, not only logging to FAS. 17:46:36 I saw the numbers he posted as comments on the ticket 17:46:37 he ran it on the ambassadors group of ~600 ambassadors and ~120 were positive. 17:48:41 I feel that I can't make my mind on this topic 17:48:41 that doesn't mean those people should be removed right away. I think they should get an email that they will be flagged as inactive during a regular clearance and if they want to keep the active status they can just log in to FAS or they can always change the inactive status in FAS admin. 17:49:19 yes, I agree 17:49:21 that sounds good 17:49:32 yes, I agree 17:49:34 I don't find it very invasive and it would give us a tool to remove ambassadors who have left the project forever. 17:49:42 we should also have a fixed timetable to run this script, say once or twice a year 17:50:01 I think that we should add that information as part of the information that new ambassadors get 17:50:16 yn1v: definitely 17:50:18 yn1v: sure 17:50:33 Yes, that sounds good 17:51:13 so we agree this is a way we can go? if so I'll figure out details with pingou before making the final proposal. 17:51:27 sesivany: +1 17:51:45 would be great to have a result where inactive ambassadors choose to achieve active standing.... resume ambassadorial activities. 17:52:04 +1 17:52:06 I will also write it to the ambassadors mailing list to find out opinions of fellow ambassadors. i think it really helped us in the beginning of the discussion. 17:52:20 +1 17:52:23 +1 17:53:11 ok, great 17:53:13 what about time frame? 17:53:26 yn1v: good point again 17:53:48 pingou used 730 days 17:54:10 how long a person can be away of auth that he/she will be updated about fedora_land 17:54:11 which I think is appropriate, but we can set a different time frame if we agree on it. 17:54:41 2 years then, should work also for 547 days (18 month) 17:55:14 we are speaking about *any* loggable activity 17:55:40 I think 2 years is a good time frame. Fedora is a fast-moving project. Being completely out for 2 years is quite a lot. 17:56:37 I like more 547 days because of the fast pace of the project 17:56:56 yn1v: +1 17:57:15 that's what I meant. 17:57:19 +1 for 18 months 17:58:03 I would keep both time frames as options. We'll see what the reaction is. Then we can be more conservative (2 years) or more progressive (18 months). 17:58:04 a release life is about 395 days 17:58:18 +1 18m 17:58:35 maybe we can run it twice a year, so the max timeframe is around 710 days 18:00:06 Why don't we run this script everyday? 18:00:06 this way we will also limit the people we need to send a mail 18:00:21 #info FAmSCo agrees that flagging ambassadors as inactive based on logging online activity is a way we can explore. We will propose it to a broader discussion and figure out details with fedora infra. 18:00:23 thinking in release cycles ... 18 months is F17 and 2 years is F16 18:01:27 yn1v: good point 18:01:28 but probably it will be better, to open discussion with both options in mind 18:01:36 How long does it take to check a who 18:01:37 How long does it take to check once 18:01:52 #info ambassadors should be informed after 18 months of online inactivity. The time frame is still a subject of discussion. 18:02:41 #action sesivany to contact pingou and figure out details with him. For example how often the script can be run. 18:02:43 I have to leave right now :-( 18:03:05 I will catch up with logs 18:03:12 bye 18:03:16 see you 18:03:17 yn1v: yes, we're past one hour of meeting time. I think it's time to finish. 18:03:21 See you next times, yn1v 18:03:38 do we have anything else to discuss? 18:04:26 not from me 18:04:38 if not, let's end the meeting. 18:04:54 Yes, time is up 18:05:00 don't forget, the next meeting will be on Tue 16 UTC ;) 18:05:19 It's easier for me next times :) 18:05:24 tuanta: btw are you ok with becoming a vice-chair? 18:05:28 sesivany: tomorrow? 18:05:30 :) 18:05:54 lbazan: I would wait for the next week :) 18:06:00 * lbazan xD 18:06:09 March 18th to be precise :) 18:06:10 sesivany: yes, I am can do 18:06:19 tuanta: great 18:06:56 s/I can do 18:07:09 meet you next week! 18:07:09 #endmeeting