14:03:37 <potty> #startmeeting FAmSCo 2016-04-27 14:03:37 <zodbot> Meeting started Wed Apr 27 14:03:37 2016 UTC. The chair is potty. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:37 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:37 <zodbot> The meeting name has been set to 'famsco_2016-04-27' 14:03:44 <potty> #meetingname FAmSCo 14:03:44 <zodbot> The meeting name has been set to 'famsco' 14:03:54 <potty> #topic Roll Call 14:03:57 <potty> .hello potty 14:03:58 <zodbot> potty: potty 'Abdel G. Martínez L.' <abdel.g.martinez.l@gmail.com> 14:04:00 <giannisk> .fas giannisk 14:04:01 <zodbot> giannisk: giannisk 'Giannis Konstantinidis' <giannis@konstantinidis.cc> 14:05:09 <giannisk> Has a meeting reminder been sent to the list? I cannot recall anything. 14:05:25 <potty> giannisk: no 14:05:42 <gnokii> .fas gnokii 14:05:43 <zodbot> gnokii: gnokii 'Sirko Kemter' <buergermeister@karl-tux-stadt.de> 14:05:51 <potty> #info Christoph and Gabriele sent regrets 14:06:08 <tuanta> .fas tuanta 14:06:08 <zodbot> tuanta: tuanta 'Truong Anh Tuan' <tuanta@iwayvietnam.com> 14:06:12 <giannisk> potty: Please make sure that it's either sent automatically via Fedocal or you do it manually youself. :) 14:06:34 <potty> #action potty to assure that reminder is sent automatically or manually 14:06:51 <giannisk> potty++ 14:07:10 <potty> #info Attendance: 4/7 14:07:35 <decause> .hello decause 14:07:35 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com> 14:08:08 * decause is in other meetings too though, FYI 14:08:25 <potty> #topic Lazy Consensus (Ticket #390) 14:08:34 <potty> Do we have any questions about this topic? 14:08:51 <giannisk> .famsco 390 14:08:51 <zodbot> https://fedorahosted.org/famsco/ticket/390 14:09:01 * giannisk is checking. 14:09:52 <giannisk> It's +6 14:10:04 <giannisk> Only lbazan has not voted from what I see. 14:10:07 <potty> The only one missing for voting is lbazan 14:10:13 <giannisk> Any news from lbazan? 14:10:24 <giannisk> He's been missing lately. 14:10:26 <potty> Yes, but still a majority. I spoke to him a few days ago and he agrees with the lazy consensus. 14:10:38 <potty> He have been full with work and unable to attend. 14:11:13 <potty> Are we going to #agree on this ticket? Or wait until he votes? 14:11:45 <giannisk> Would be nice to have a solid +7, although this is already pretty much decided. 14:12:00 <tuanta> We have been waiting for a few weeks so one more week for all votes is fine to me 14:12:06 <potty> ok 14:12:16 <potty> Let me call him later today. 14:12:38 <potty> #action potty will comunicate to lbazan to vote on ticket #390 14:13:02 <tuanta> anyway, we can mark an action for cwickert to put the latest proposal to wiki 14:13:20 <potty> #action cwickert to add the proposal to the wiki 14:13:31 <tuanta> then all done; this ticket could be closed after that 14:13:36 <potty> yes 14:13:44 <potty> Next topic then? 14:13:56 <tuanta> ticket #394? 14:14:18 <potty> #topic Over Regional Sponsoring (Ticket #394) 14:14:23 <potty> Yes tuanta 14:14:25 <giannisk> .famsco 394 14:14:25 <zodbot> https://fedorahosted.org/famsco/ticket/394 14:14:30 <potty> Thank you giannisk 14:15:02 <giannisk> potty: np 14:15:10 <giannisk> Already shared my views on the ticket. 14:15:36 <giannisk> To me, regional budgets are to be spent within their regions respectively. 14:16:08 <giannisk> If a Fedora contributor from X region flies to Y region, the budget should come from the latter 14:16:28 <giannisk> As that event/activity would take place in the Y region. 14:17:22 <potty> giannisk: +1 14:18:28 <giannisk> Of course, if the Y region is running low on the budget, then X may agree to share or even to fully cover the costs, but that should be considered as a secondary option. 14:19:04 <giannisk> Thoughts? 14:20:08 * potty is typing 14:20:10 <tuanta> we should not make this as strict rules, but some open guidelines 14:20:40 <tuanta> I share with cwickert, we need to deal case by case 14:21:27 <giannisk> tuanta: I see, but dealing case-by-case could be time-consuming on the other hand. 14:21:36 <tuanta> historically, some of us in APAC even get sponsorship from EMEA to attend events in APAC! 14:21:39 <potty> Here is my thought. We have the following scenario: region Y have an event and 1) have invited region X Fedora contributor, then the budget should come from region Y 2) the region X Fedora contributor want to go to the event (but is not invited from region Y), then the budget should come from region X (or shared with the Fedora contributor) 14:22:10 <tuanta> have we got any statistics about this? how many cases per year/quarter/month? 14:22:50 <potty> My proposed strategy should be have a shared budget inter-regions. To solve this situations. But, of course, its value should be decided taking in consideration the statistics tuanta asked. 14:23:11 <tuanta> I don't think we have to work out on too many cases 14:23:12 <giannisk> tuanta: speaking for EMEA, there should only be about 2-3 (max) cases per year 14:23:40 <tuanta> the same in APAC, just a few cases 14:24:14 <tuanta> so we expect less than 10 cases per year in all regions, right? 14:24:22 <potty> tuanta: +1 14:25:04 <tuanta> therefore it is possible to deal with case by case 14:26:23 <tuanta> we can have some guidelines as potty mentioned above 14:26:37 <potty> To solve this, let's do two things: 14:26:51 * potty 1. Write a wiki where we write a guideline, as the specified above. 14:27:02 <tuanta> regions can use them or finally ask us (FAmSCo and budget owner) to solve remaining issues 14:27:26 <potty> 2. Include a clause to solve specific cases 14:27:53 <potty> Do you agree? 14:29:08 <potty> Please respond, to move one the meeting 14:30:17 <tuanta> potty, I think firstly, we should show/tell our views on Trac; then someone should form up to a proposal (similar what we did with lazy consensus) 14:30:45 <giannisk> tuanta: +1, all views should be reflected on the trac as well 14:31:05 <potty> giannisk: +1 14:31:44 <giannisk> I like the current proposal: a) set a few guidelines, b) agree to review every case separately 14:32:24 <potty> I will write them on the trac ticket, is that an action? 14:32:30 <potty> #chair giannisk tuanta 14:32:30 <zodbot> Current chairs: giannisk potty tuanta 14:33:17 <giannisk> potty: sure 14:33:39 * giannisk needs to go in about 15 minutes. 14:33:50 <potty> #action potty will update ticket #394 with the proposal: a) set guidelines b) agree to review every case separately 14:33:55 <potty> Next topic? 14:34:17 <giannisk> We need to move on with FOSCo 14:34:20 <tuanta> I have nothing in my mind 14:34:30 <potty> #topic Ticket #373 14:34:43 <potty> Do we have any news about this? 14:34:43 <giannisk> .famsco 373 14:34:46 <zodbot> https://fedorahosted.org/famsco/ticket/373 14:35:22 <giannisk> oh, gnokii timed-out 14:35:29 <potty> gnokii was working on it but I don't know how much had he advanced 14:35:56 <giannisk> We need to put some effort together and make it happen. 14:37:05 <giannisk> If gnokii does not re-connect within the next 5 minutes, then I shall place an action item for him to inform us about the current status and let us know how to assist. 14:37:51 <potty> ok 14:39:10 <potty> Do we have any other topics? 14:40:17 <giannisk> #action gnokii to inform the committee about the current status concerning the transition to FOSCo 14:40:31 <potty> Ok... 14:40:43 <potty> Let's finish the meeting in 3 minutes? 14:40:44 <giannisk> How's #388 and #389 doing? 14:40:49 <giannisk> potty: not yet :) 14:42:20 * tuanta is reading 14:43:00 <tuanta> both for FUDCons 14:43:19 <giannisk> Quoting cwickert's comment: "Now we are facing a different problem. The council approved their ticket, but afterwards the budget jumped from USD 9226.12 to (currently) USD $15,807.73. This is above the limit. potty, lbazan, can one of you get in contact with the event owner or the person who edited the budget to resolve this?" 14:43:36 <giannisk> #topic FUDCon Latam Puno 2016 14:43:40 <giannisk> .famsco 388 14:43:40 <zodbot> https://fedorahosted.org/famsco/ticket/388 14:46:39 <potty> giannisk: there is no problem with the budget, the increase is because the owner estimate all the flights registered on the pre-registration, but this should not be taken as a fixed value on the budget. The owner knows that the budget is 10K and if they need extra cash, another sponsorships should be acquired 14:46:52 <potty> Any questions? 14:50:13 <tuanta> We have no quorum today so we can not decide anything. I think we should use laze consensus to make decisions for those tickets 14:50:36 <potty> Yes 14:51:20 <tuanta> for me, opened important questions must to be answered (by event owners) before we can go further 14:55:10 <potty> #action I will contact the FUDCon LATAM organizers to answer that inquiry 14:55:16 <potty> Any other questions related to this topic? 14:55:23 <potty> #undo 14:55:23 <zodbot> Removing item from minutes: ACTION by potty at 14:55:10 : I will contact the FUDCon LATAM organizers to answer that inquiry 14:55:47 <potty> #action potty will contact the FUDCon LATAM organizers to answer the inquiry 14:57:47 <potty> Do we have any other topic? 14:57:55 <jkurik> Hi Ambassadors. I need someone from Ambassadors to join the F24 Readiness meeting tomorrow. Any volunteer :-) ? 14:58:15 * giannisk_ is back, wireless connection issues. 14:58:30 * giannisk_ needs to go in a bit, though. 14:59:15 <giannisk> So, what has been discussed about #388? 14:59:49 <potty> giannisk: 14:59:50 <potty> 9:46 AM <potty> giannisk: there is no problem with the budget, the increase is because the owner estimate all the flights registered on the pre-registration, but this should not be taken as a fixed value on the budget. The owner knows that the budget is 10K and if they need extra cash, another sponsorships should be acquired 14:59:58 <potty> jkurik: what time is the meeting? 15:00:13 <jkurik> 7PM UTC 15:00:26 <jkurik> https://apps.fedoraproject.org/calendar/meeting/3878/ 15:01:12 <mailga> potty we need to know the task status to explain at the readiness. If we are ok with the steps I can meke it. 15:01:57 <mailga> https://fedorapeople.org/groups/schedule/f-24/f-24-ambassadors-tasks.html 15:02:35 <mailga> there's not so many things we have to do for the readiness meeting. Maybe we're late with swag production. 15:03:16 <jkurik> mailga: does it block the Beta release ? 15:03:24 <potty> jkurik: it does not block 15:03:31 <jkurik> ok, thanks 15:03:31 <linuxmodder> mailga, what on that link still needs done ? I can mention at tomorrow nights famna mtg 15:03:33 <mailga> jkurik: I see some date errors in the tasks 15:04:29 <mailga> jkurik: no, nothing can block the release. 15:04:53 <jkurik> mailga: do you mean the "Start day" ? It is typically set to begining of the F24 15:05:40 <mailga> jkurik also for the beta release? 15:06:12 <mailga> linuxmodder: my opinion is that we are ok, at the moment. 15:06:24 <jkurik> it shows the time interval, when all the tasks needs to be done 15:06:59 <jkurik> if you are looking for Beta release date, it is shown on https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html 15:07:13 <linuxmodder> mailga, feel free to ping me if that changes before tomorrow night's 01UTC famna OR til 24 is GA 15:07:33 <linuxmodder> linuxmodder@fp.o mailga 15:07:59 <mailga> jkurik: ok. Thanks. I'll join the readiness meeting for amby. 15:08:13 <jkurik> great, thanks 15:09:43 <mailga> linuxmodder: ok, we're still in beta readiness, so we have the time for set a planning for swag before the release. 15:09:49 <mailga> EOF 15:10:52 * potty got to go 15:10:59 <mailga> potty: if there's nothing else you can call the endmeeting 15:11:25 <potty> Thank you all for coming 15:11:28 <potty> #endmeeting