16:04:09 <cwickert> #startmeeting FAmSCo 2014-03-18
16:04:09 <zodbot> Meeting started Tue Mar 18 16:04:09 2014 UTC.  The chair is cwickert. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:04:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:04:15 <cwickert> #meetingname FAmSCo 2014-03-18
16:04:15 <zodbot> The meeting name has been set to 'famsco_2014-03-18'
16:04:27 <cwickert> #chair tuanta robyduck
16:04:27 <zodbot> Current chairs: cwickert robyduck tuanta
16:04:34 <tuanta> .fas tuanta
16:04:34 <zodbot> tuanta: tuanta 'Truong Anh Tuan' <tuanta@iwayvietnam.com>
16:04:35 <cwickert> anybody else?
16:04:36 <robyduck> .fas robyduck
16:04:37 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
16:04:45 <tuanta> ping masta
16:04:56 <cwickert> #topic Roll call
16:05:00 <cwickert> .fas cwickert
16:05:01 <zodbot> cwickert: cwickert 'Christoph Wickert' <christoph.wickert@googlemail.com>
16:05:09 <tuanta> ping sesivany
16:05:11 <cwickert> #info Jiri is going to join is in a few
16:05:12 <sesivany> .fas eischmann
16:05:13 <zodbot> sesivany: eischmann 'Jiri Eischmann' <eischmann@redhat.com>
16:05:20 <sesivany> sorry for being late.
16:05:23 * robyduck is on mobile let's see how it works
16:05:28 <cwickert> #chair masta sesivany
16:05:28 <zodbot> Current chairs: cwickert masta robyduck sesivany tuanta
16:05:33 <sesivany> I somehow missed the beginning.
16:05:36 <cwickert> who is missing?
16:05:42 <cwickert> sesivany: you did not miss much
16:05:54 <tuanta> Neville
16:06:05 <tuanta> and lbazan
16:06:36 <sesivany> ok, should we get started?
16:06:51 <tuanta> yes
16:06:58 <cwickert> yes
16:07:10 <cwickert> sesivany: can you chair the meeting? I'm still kind of busy at work
16:07:26 <sesivany> let's continue with the "inactive ambassador" topic, we've moved a lot last time.
16:07:29 <sesivany> cwickert: sure
16:07:42 <sesivany> #topic "Inactive ambassadors" issue
16:08:05 <sesivany> I think the feedback from ambassadors was very positive.
16:08:20 <sesivany> almost everyone seems to be happy with the solution.
16:08:21 <robyduck> yes excellent
16:08:27 <tuanta> I think we have got a solution, finally
16:08:41 <sesivany> which is a good news after the initial uproar.
16:09:22 <sesivany> what we need to do now is to go to Fedora Infra and ask them if it's doable.
16:09:46 <sesivany> technically it is, but we need to get them on our side to make it happen.
16:10:11 <robyduck> sesivany: the issue will be do it automaticaly
16:10:40 <robyduck> but can we decide how many times we want to run this script?
16:11:01 <sesivany> robyduck: I asked pingou.
16:11:04 <robyduck> if it' 3-4 times a year we can do this also manually if needed
16:11:06 <cwickert> every 1st of the month and being inactive for a year or two?
16:11:23 <sesivany> cwickert: we agreed on 18 months last time.
16:11:41 <sesivany> everyone in the mailing list seemed to be ok with that, so I would stick with 18 months.
16:11:49 <cwickert> that looks like a weak compromise between one and two years ;)
16:11:51 <tuanta> +1 cwickert, we can run it every 1st of the month
16:12:20 <tuanta> +1 sesivany with 18 months
16:12:28 <tuanta> I thought so last meeting too
16:12:29 <sesivany> answer from pingou: Note that this is the part that will always involve some manual work. The script
16:12:29 <sesivany> only generates the data, it does not send the email neither trac 2 weeks later
16:12:29 <sesivany> which account should be acted upon.
16:13:12 <robyduck> then it should be automatically with a cron
16:13:52 <tuanta> yes, I think we can run it automatically
16:13:57 <robyduck> what about every 3 months? I could volunteer if ut's 4 times a year to do the manual work
16:14:17 <tuanta> we should check with pingou if it is possible
16:14:19 <sesivany> robyduck: yes, 3 months is what I had in mind.
16:14:42 * masta looks in
16:14:47 <masta> hello
16:14:50 <sesivany> I don't think it's so timely thing. It doesn't have to be done every month.
16:15:10 <robyduck> yes I'm also for every 3 months
16:15:41 <sesivany> ok, we have 18 months of inactivity and 3 month period for running the script.
16:15:47 <tuanta> 3 months difference for 18 months is fine
16:15:59 <tuanta> but I think every month is better
16:16:15 <tuanta> it depends on how fast it is
16:16:32 <yn1v> hello. I just got free of some work stuff and got call from school to pick up my baby daughter. Sorry. I will catch up with logs
16:16:33 <tuanta> maybe the script need minutes to finish
16:16:43 <tuanta> do you know how fast it is?
16:17:10 <sesivany> what are we going to do with ambassadors who meet the criteria? Send them one notification and after 14 days flag them as inactive?
16:17:38 <sesivany> or more notifications?
16:17:58 <masta> notifications sound good
16:18:18 <masta> an opportunity to rejoin the project, become active again
16:18:45 <sesivany> one notification 2 weeks before and then another one week before?
16:18:59 <robyduck> one notification and 14 days sounds good to me
16:19:08 <tuanta> how about 14 days then 3 days?
16:19:25 <sesivany> tuanta: that could work, too.
16:19:36 <tuanta> we should have at least two notifications
16:19:54 <sesivany> yeah, let's make it 14 and 3 days before, two notifications.
16:20:36 <tuanta> +1
16:21:06 <sesivany> ok, then it seems to be all clear.
16:22:02 <robyduck> ok
16:22:18 <sesivany> let me write a little summary we can vote about.
16:23:05 <robyduck> tuanta: I don't think the problem is the script, it's all the other related stuff we need to do manually and that is what takes time
16:23:31 <masta> it will be good to have more accurate numbers on active participants
16:23:54 <tuanta> if we have to do something manually, 3-months is better, indeed
16:23:59 <robyduck> masta:  +1
16:24:31 <sesivany> Accounts of ambassadors who haven't had any online activity indicated by FAS and Datagrebber for 18 months will be flagged as inactive. They will be notified 14 and 3 days before it happens. They won't lose the membership even after the deadline and can become active again any time. The script will be run every 3 months.
16:24:34 <sesivany> how about this?
16:24:40 <sesivany> did I miss anything?
16:25:32 <masta> looks reasonable
16:25:56 <robyduck> no, just nees to hear infra if inactive accounts are able to manage
16:26:04 <sesivany> can we vote about it to make the decision finally?
16:26:13 <tuanta> so there are two parts of that script, right?
16:26:24 <sesivany> robyduck: ok, let's vote about what we want and then we can go to infra if it's possible.
16:26:25 <tuanta> one runs quarterly, and one run daily
16:26:42 * masta votes +1
16:26:43 <robyduck> no why?
16:26:47 <sesivany> +1
16:26:53 <tuanta> for sending notifications
16:26:57 <robyduck> +1
16:27:41 * tuanta votes +1
16:27:46 <tuanta> just curious
16:28:31 <robyduck> tuanta: let's define this once we know ho we can make this happen every 3 months
16:28:47 <sesivany> #agreed Accounts of ambassadors who haven't had any online activity indicated by FAS and Datagrebber for 18 months will be flagged as inactive. They will be notified 14 and 3 days before it happens. They won't lose the membership even after the deadline and can become active again any time. The script will be run every 3 months.
16:29:24 <sesivany> is anyone volunteering to negociate this with infra?
16:29:47 <robyduck> I can do
16:29:55 <tuanta> thanks robyduck
16:30:07 <sesivany> robyduck: thanks!
16:30:44 <masta> thanks robyduck
16:31:04 <sesivany> #action robyduck to ask infra if it's the agreed solution doable, and figure out the technical solution with them.
16:31:04 <masta> we need to think of how to make the task easy for infra
16:31:05 <robyduck> :D
16:31:15 <masta> (long term)
16:31:42 <sesivany> robyduck: I guess it involves creating a ticket, I think you can CC us to keep us updated.
16:32:38 <robyduck> yes sure
16:32:39 <sesivany> robyduck: don't forget to stress reasons. That it's a solution to our long-term problem.
16:33:44 <sesivany> ok, are we done with this topic for today?
16:33:51 <tuanta> yes
16:33:54 <robyduck> sesivany: will stress :)
16:34:22 <robyduck> mobile is slow at the moment....sorry
16:34:33 <sesivany> I've got one hot topic I'd like to discuss especially with masta...
16:34:53 <sesivany> #topic NA budget for FY2015
16:35:13 <tuanta> so hot :)
16:35:26 <sesivany> masta: we finally have a member from NA again. So hopefully the communication will be better now.
16:35:51 <sesivany> what we're missing is a budget for NA region for this fiscal year.
16:36:43 <tuanta> btw, anyone knows reason why our budget proposal has not been approved yet?
16:36:44 <sesivany> and masta is gone... :)
16:37:14 <sesivany> tuanta: because Red Hat itself doesn't know what the available budgets will be.
16:37:40 <sesivany> from what Ruth told me we should get $90k again.
16:37:58 <tuanta> now, APAC is using FY2014 budget. Is that ok?
16:37:59 <sesivany> which means a 30% cut again.
16:38:10 <tuanta> cutting edge :)
16:38:25 <sesivany> tuanta: you can use the new one already, but count with the cut.
16:38:46 <sesivany> they might surprise us and we might get more money, but it's unlikely.
16:40:30 <sesivany> ok, seems like everyone is gone already today.
16:40:40 <sesivany> should we end the meeting?
16:40:50 <sesivany> or do we have another topic?
16:41:10 <tuanta> #topic Open floor
16:41:30 <tuanta> finally, we got response from Robyn about APAC FUDCon
16:41:36 <tuanta> but it is so closed now
16:41:53 <tuanta> it is the turn of organizing team
16:41:54 <sesivany> tuanta: btw I and jreznik would like to come to FUDCon APAC if it's still happening.
16:42:09 <tuanta> cool
16:42:17 <tuanta> they send call for papers
16:42:21 <tuanta> snet
16:42:26 <tuanta> s/send/sent
16:42:29 <sesivany> we need to know the final decision soon to apply for visa.
16:42:42 <tuanta> how about Flock?
16:43:01 <tuanta> does FAmSCo have any group activities there?
16:43:35 <sesivany> tuanta: I'll be at FLock as well, it's just 2 hours from my home :)
16:43:50 <sesivany> I would definitely like to get all famsco members to Flock.
16:44:08 <tuanta> it would be fine if FAmSCo can organize something there
16:44:42 <tuanta> I see Flock opened now talk submissions
16:44:59 <tuanta> if we have something, we should register soon
16:45:11 <tuanta> I meant FAmSCo
16:45:27 <tuanta> that's all today from me
16:45:50 <tuanta> if we have not got anything to discuss, you can close the meeting
16:46:00 <sesivany> I will probably submit the same talk as last year.
16:46:36 <sesivany> but this year, I would like to have all members there and organize a meeting.
16:47:21 <robyduck> dwould be nice
16:47:28 <tuanta> if we have a (meeting) topic, you should register it under the name of all FAmSCo
16:48:02 <sesivany> ok
16:48:27 <sesivany> #action sesivany to register FAmSCo session at Flock.
16:48:52 <sesivany> ok, I think it's all for today.
16:48:53 <tuanta> I can not make it to FUDCon APAC since I will be crazily busy on May, so I would like to to meet you all at Flock again
16:49:45 <tuanta> another reason: it is difficult for Vietnamese to apply for a visa to China at this time
16:49:56 <robyduck> uhmm
16:50:12 <tuanta> much more difficult than applying for US visa
16:50:28 <tuanta> ok, that;s all today, sesivany
16:50:36 <tuanta> we can close the meeting
16:50:39 <sesivany> ok
16:50:42 <sesivany> #endmeeting