17:00:58 #startmeeting FAmSCO 2012-07-09 17:00:58 Meeting started Mon Jul 9 17:00:58 2012 UTC. The chair is cwickert. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:05 #meetingname famsco 17:01:05 The meeting name has been set to 'famsco' 17:01:29 .fas aeperezt 17:01:29 aeperezt: aeperezt 'Alejandro Perez' 17:01:44 * aeperezt helo everyone 17:01:45 .fas dbruno 17:01:45 danielbruno: dbruno 'Daniel Bruno' 17:01:52 #topic Roll Call 17:01:56 .fas cwickert 17:01:56 cwickert: cwickert 'Christoph Wickert' 17:02:53 .fas bckurera 17:02:53 bckurera: bckurera 'Buddhika Kurera' 17:05:20 * cwickert counts 5 people 17:05:31 no, 4 17:06:51 cwickert, what is the quorum minimal 4 or 5 17:07:05 don't know 17:07:16 I am not sure even have something like this 17:08:32 anyway shall we move? 17:08:37 cwickert, o then I'm not sure why I got that idea that we need a number of famsco members for the meeting 17:08:59 so lets move on 17:10:00 We have the majority here, isnt that enough? :) 17:10:40 think so, maybe we can review tickets on https://fedorahosted.org/famsco/report/9 17:10:40 I think so 17:10:55 if there is something we can add or change on any of them 17:11:16 but I guess the one we need to tal about is 265 17:11:28 #info aeperezt, bckurera, cwickert, danielbruno present, sesivany is traveling, no news from herlo and nb 17:11:34 sorry, I got distracted 17:11:34 with bckurera page https://fedoraproject.org/wiki/User:Bckurera/Draft_Sponsoring_event_attendees 17:11:41 lets move on 17:11:49 #topic Announcements 17:11:53 any announcements? 17:11:54 and fpl notes on the matter 17:12:42 no announcements? 17:12:51 ok, then lets move on with tickets 17:13:34 aeperezt : lets discuss it at the topic, ticket #265 17:13:55 ok, lets do #265 then 17:14:03 #topic Sponsoring event attendees 17:14:07 .famsco 265 17:14:07 https://fedorahosted.org/famsco/ticket/265 17:14:30 bckurera: when you make a draft, you should update the ticket 17:14:50 this being said, thanks for your work, but I don't think your draft really works 17:15:12 ohh couldnt update the ticket, but I forwarded the link to the mailing list 17:15:31 should we go through it by bullet points or should we use rbergero's mail? 17:15:56 there is a long mail from FPL as well 17:16:18 bckurera: oh, I see, trac is not yet updated, it still has the old FAmSCo members 17:16:23 hold on... 17:17:23 the focus is FUDcon, I got the idea from noted links and prepared a draft 17:17:45 we can change/add it, till it looks fine 17:18:36 bckurera, think it should mention that it focus on fudcon only will not affect request to other events 17:18:57 ok, updated 17:19:36 #info trac updated, all FAmSCo members now have full trac access 17:20:17 I think the problem with the draft is that it focuses on FUDCon and that it does not include the old policy 17:20:31 aeperezt : I dont think there is special need for other events, if anyone need funds for any other event FAmSCo can discuss it 17:21:30 again, my question is: how do we move on? 17:21:36 suggestions? 17:21:36 bckurera, right but it need to mention it on the track and on the draft doc so it does not get confused 17:22:16 hello? 17:22:24 aeperezt : ok then will add it :) 17:22:42 cwickert : you mean the draft? 17:22:54 bckurera, :-) 17:22:56 no, I mean: How do we move on??? 17:23:15 cwickert : you mean the meeting? 17:23:17 lets go to the fpl points 17:23:23 yes 17:23:37 that was meant for bckurera 17:24:19 danielbruno: ? 17:25:31 * nb here 17:25:32 sorry 17:25:40 bckurera, many points from the openSUSE page will not be valid now if we just close it to fudcon 17:25:42 sorry guys, i had to answer an important call. 17:25:47 * danielbruno is back 17:25:55 ok, can we please move on? 17:26:00 yes 17:26:07 lets move on 17:26:19 and some of those are what got response by Rbergeron 17:26:26 or comments 17:26:45 my question was: how should we move on with this ticket? 17:27:03 I made 2 proposals, only one aeperezt answered 17:27:08 being frank I dont get time to read the email, it was sent today evening 17:28:08 ok fedora moving on shall we understand the need of such proposal? 17:28:14 bckurera, ok then lets stop here so everyone can review and propose the changes on the ticket, considering that is only fudcon and not all event 17:28:24 hold on 17:28:51 can we please answer one question first? for over 10 minutes everybody is just talking but not answering my question 17:29:12 given that not everybody read rbergero's mail I suggest that we all have a look at bckurera's draft first 17:30:23 cwickert, ok 17:30:49 the others? 17:30:57 one thing we need to clarify, does this required to cover all the requests? 17:31:06 ok, I am done 17:31:17 who will lead the meeting? 17:32:02 sorry, but I feel we are not getting anywhere with this 17:32:19 we are talking for half an hour and we have not even agree how we should discuss 17:32:30 instead everybody is just talking random stuff 17:32:42 and others don't seem to be present at all 17:32:49 so who is still here? 17:33:04 cwickert got it :) 17:33:17 cwickert, here 17:33:39 cwickert, im here 17:33:39 danielbruno, nb: still there? 17:33:43 cwickert, looks like only bckurera you and I 17:34:13 aeperezt, me too :) 17:34:32 yes 17:34:39 ok, has everybody read the draft? 17:34:48 yes 17:35:01 yes 17:35:04 yes 17:35:07 ok 17:35:12 but i'm reading the rbergeron mail 17:35:24 Me too reading it is long 17:35:30 guys 17:35:50 can we please all pay attention to this meeting and not read any mails? 17:35:59 cwickert : ok done 17:36:00 sure 17:36:13 I thought we agreed on going through the draft and not discussing rbergero's mail 17:36:30 +1 17:37:16 any questions about the draft before we start? 17:37:16 +1 17:38:01 no questions, awesome 17:38:17 lets go through the bullet points 17:38:28 I think the draft lacks an introduction 17:38:31 only sugestion I have was to specify that is only for Fudcon 17:38:43 but nice work bckurera by the way 17:38:44 it should not be 17:39:00 ok, maybe we need to go one step back 17:39:00 thanks 17:39:14 the ticket was about "sponsoring event attendees" 17:39:25 not about FUDCon attendees 17:39:36 so we need to work on something generic and not specific 17:39:49 we want to improve http://fedoraproject.org/wiki/Sponsoring_event_attendees 17:40:03 this means we need to incorporate the old and the new suggestions 17:40:10 or am I wrong? 17:40:22 so, for something generic 17:40:31 it need to change somepoints 17:40:36 about the committee 17:40:43 you right 17:40:49 yes but for general fund requests to attend a event, we can discuss in FAmSCo 17:41:20 I don't think we really want that 17:41:29 maybe it can be have a condition whe the event is a fudcon or not 17:41:36 they should be discussed in regional meetings 17:41:41 we want to move more budget decisions away from FAmSCo and we want event owners to decide 17:41:55 +1 17:41:56 the event owners know better about the event than FAmSCo 17:41:56 having a separate committee is not required if it is an ordinary request asking fund 17:42:10 cwickert, i think the same 17:42:41 bckurera: we are not trying to reinvent the wheel, we want to improve the current process 17:42:59 well if it is more generic I don't think all events should have a committee 17:43:17 ok, who will lead this meeting? 17:43:19 * nb suggests leaving it up to the regions 17:43:59 nb: we are talking about things that go through the tracker, premier Fedora events 17:44:12 which are usually bigger than the regions 17:44:42 ok, again, I ask somebody to take over leadership of this meeting 17:44:59 it seems I am not leading this discussion well because we are no getting anywhere 17:45:13 so if anybody would take over, I appreciate it 17:46:40 who was vice chair? danielbruno? 17:46:51 cwickert, yes, i am 17:47:00 ok, please chair this meeting 17:47:12 #chair danielbruno nb aeperezt bckurera cwickert 17:47:12 Current chairs: aeperezt bckurera cwickert danielbruno nb 17:47:37 ok.. move on 17:48:58 I think that we need to do a merge with the old model 17:49:18 with the new suggetions 17:49:57 ! 17:50:05 -> cwickert, 17:50:43 I think we should start with the old page and not change too much. we should go through the list and think carefully what to add. 17:50:49 just as we are, I believe that there is no need of formality to ask to speak 17:51:04 this being said I don't think that bckurera's draft is really helpful, it is just too much 17:51:07 EOF 17:51:41 the old page is a good start point 17:51:51 ok then do we need a new committee or body? 17:52:19 bckurera: we don't really need a new committee, all the big events already have theirs 17:52:20 I think that all of us have experience in events in general 17:52:38 to propose improvements 17:53:39 improve what already exists is more efficient than making a new 17:53:58 * nb wonders what we are trying to solve abou the current process 17:53:58 cwickert : yes but we need something "a defined entity" 17:54:10 the new draft by bckurera seems really restrictive 17:54:38 nb: what we are trying to fix is that we currently use "first come, first serve" 17:54:44 in that case we can substitute committee with the organizing team, but they need to follow the guideline? 17:54:54 what guideline? 17:55:15 we are not trying to change *who* decides but *how* they decide 17:55:16 how to serve requests, not first come first serve 17:55:40 therefor I suggest we remove all the formal requirements about the committee 17:56:19 I think we should base our improvements on the assumption that there already is some kind of committee for the events 17:56:29 I m fine with it, will remove the committee, and refine how decision is made 17:56:31 the people almost always are the same, usually the changes is the way things are done 17:57:02 so lets just make it "the event organziers" instead of "the committee" 17:57:18 sounds good 17:57:23 cwickert : got it, I ll refine it 17:57:49 the FPL just doesn't have enough time to be head of yet another committee 17:58:55 * cwickert has more ideas but wants to hear the others first 17:59:48 so, bckurera will work on his draft or we'll work to improve the old page? 18:00:30 I think we should not change the old page until we have something better, but we sould carefully think what to change 18:01:05 danielbruno : Will remove the idea of the committee, but we need to decide *how* it is done 18:01:11 +1 18:01:31 for me the most important parts are the ranking and the deadlines 18:01:33 i think the rest of it sounds ok 18:01:39 +1 18:01:40 * aeperezt I think that inode0 intention on the ticket was for fudcon only 18:01:48 although i almost think there should be a little bit of priority to people who ask earlier 18:02:03 and requests should not have to wait until the final deadline to find out of they are approved 18:02:09 i.e. how we have multiple subsidy meetings currently 18:03:48 I could think of 2 rounds, but doing subsidy meetings very week will lead to first come, first served 18:04:01 well, we could continue doing them every week 18:04:12 but only approve the people that have rank 1 18:04:26 and whoever is average or below needs to wait 18:04:30 2 rounds will be enough, if there is any funding left at the end of the 1st one 18:04:33 because we want a fair decision for them 18:05:02 it's a good approach 18:05:27 Will narrow down the time line and then 1st subsidy meeting 18:06:54 I am not sure if we should set deadlines in the document, the event owners should set them 18:06:55 someone else? 18:07:26 what about the ranks? do we really need 5? 18:07:35 * cwickert thinks 3 are enough 18:07:44 will set 2 week, all interested parties should apply with in 2 weeks, then 3rd week subsidy meeting will be held 18:08:13 bckurera: but this may differ from event to event. they have different deadlines for hotel, flights etc 18:08:34 about the deadlines, I think we should suggest how it should be done, but it's not mandatory because the situation change in each event 18:08:44 danielbruno: +1 18:09:20 think of FUDCON APAC where we only had very little time. on the other hand we are already planing for FUDCon EMEA now even if it is 4 months away 18:09:31 so deadlines should be up to the even owners 18:10:06 and I think the number of meetings should be up to them, too 18:10:42 cwickert : I dont agree with it, we need to set a minimum period, letting others to have enough time to apply 18:10:42 they can have as many meetings as they like and approve requests ASAP, as long as they make sure the rest is treated fair and equally 18:11:20 cwickert, +1 18:11:40 bckurera: of course, we can say the time frame should at least be X weeks 18:11:59 good, that is what I mean 18:12:23 if we say 4 weeks, and they are doing meetings every week; I think they can approve people already in the first week 18:12:26 I dont think we should determine time because not all events have the same proportion 18:12:28 cwickert, +1 18:12:31 but only if they are really ranked 1 18:12:48 and all the others who are 2 or three need to be discussed later 18:13:02 the last meeting is the important one 18:14:04 but again my concern is rank 1 is relative 18:14:28 it should not be 18:15:01 rank 1 is "This person needs to be at the FUDCon to make it happen or because he/she is very important otherwise" 18:15:43 cwickert, +1 18:15:56 should we discuss this on the mailing list? 18:16:07 strong yes 18:16:16 this meeting is taking very long and I think it does not make much sense to discuss details 18:16:31 I would rather like to think about the general approach 18:16:37 * aeperezt I'm sorry are we talking about general events or fudcon events, the two of them are completly different events and issues 18:16:52 and it seems we already agree on this ever much 18:17:02 we need to make a proposal to generic events 18:17:14 aeperezt: we are talking about those events where we have more people applying for sponsorship than we can crant 18:17:16 grant 18:17:19 we're forgotting our focus 18:17:25 thinking on fudcons 18:17:42 well, I think for normal events it works quite well already 18:18:05 we don't have so many people who apply and we just grant sponsoring, right? 18:18:51 if we just grant it anyway, we don't need a committee, the regional meetings or FAmSCo can decide 18:18:53 If and only if it is important, suck matters will be handled by regional communities or FAmSCo 18:18:57 if we are not talking about fudcon then it should be as simple as its, the two events were we have more people than budget are FADs and Fudcon 18:19:11 s/suck/such 18:19:25 aeperezt: right, any some other big events, but usually that does not happen 18:19:32 s/any/and 18:19:39 were bckurera doc fits better than general events 18:20:26 guys, i think that we need to think better about and move the discuss to the mail list 18:20:30 +1 18:20:35 basically the http://fedoraproject.org/wiki/Sponsoring_event_attendees page works fine for all other request except fad and fudcons 18:20:50 aeperezt: amen! 18:20:57 so I think we should work on those tow 18:21:00 *two 18:21:01 yes will move this to mailing list, it is almost 1.5 hr here 18:21:10 yes, I need to leave now 18:21:14 yes, the time is running 18:21:19 me too 18:21:20 can we have a few quick questions though? 18:21:57 sure 18:22:10 I m fine with it, quick and fast :) 18:22:13 bckurera: what do you mean with "Blog about being sponsored. Please use one of the badges in your blog post" 18:22:15 ? 18:22:24 what badge? 18:22:32 what about those of us who don't want a blog? 18:22:38 * nb currenty just sends a report to the amb list 18:22:44 it is extract from open SUSE 18:22:48 nb: there is a requirement 18:23:04 but what I was thinking is I m going FUDcon badges :) 18:23:16 there is not currently a requirement AFAIK 18:23:17 nb: for the record: http://fedoraproject.org/wiki/Event_reports 18:23:36 hmm ok maybe there is 18:23:38 * nb reads 18:23:47 I think one event report should be mandatory 18:23:56 because the finance guys really need it 18:24:08 but I agree that daily blogging can become too much 18:24:11 cwickert, I do make a report 18:24:16 cwickert, i email it to the amb list 18:24:25 i just don't have a blog, and don't want one 18:24:36 cwickert, +1 about the event report 18:24:39 it should be linked in the ticket, but that's a detail 18:24:55 back to my question 18:24:55 you can use your existing blog, no need to have a separate one for that 18:25:04 bckurera, i don't have a blog, and don't want one 18:25:09 that was my point 18:25:13 the report daily report is optional, but it's a good thing to do 18:25:18 lets not discuss event report, seems we all agree 18:25:20 * nb sends his event report to the ambassadors list via email 18:25:46 I think we should remove the badge thing because we don't have badges 18:25:53 cwickert, I know that daily blogs can be a heavy load but it is a way to talk about the event on the web so think we keep it maybe not daily 18:25:54 and we should remove the blogging requirement 18:26:12 I mean, not blogging about the event but that you were sponsored 18:26:36 cwickert, can we change it to "make an event report" not necessarily a blog 18:26:57 I am not talking about event reports *themeselves* 18:27:04 +1 18:27:07 it seems in OpenSUSE you need to write blog "Hey, I was sponsored" - and this is a bad idea 18:27:16 because it will just make people jealous 18:27:21 cwickert, i agree 18:27:29 ok, so we remove this and the badge 18:27:42 but we agree that we should have some kind of event reports 18:27:47 what about the ranks then? 18:27:50 do we really need 5? 18:28:20 I think with 5 we have wide range to make up the decision, that is the reason behind for 5 18:28:22 yes, some kind of event reports 18:28:36 we could suggest 5, the event owners could choose to only use 3 if they want 18:28:41 the open suse format can be a model, it's not necessary is how we should to do 18:28:42 if there is 3, it is yes, no, neutral 18:28:59 bckurera: +1 18:29:20 but this can still be discussed later, maybe 4 or 5 make sense 18:29:31 what about " Be available to educate or mentor other people who want to get involved with the Fedora Project, help with any Fedora activities, e.g. booth duty. " 18:29:41 I think we should drop this requirement, too 18:29:50 because it is very specific for FAms 18:30:13 brb 18:30:31 so you have a FUDCon and they want to make an ARM hackest there. Do we require pbrobinson or jmasters to mentor people or write good code? 18:30:35 * aeperezt have to leave, took more that expected. 18:30:43 * aeperezt will read logs 18:31:50 nobody? 18:32:07 cwickert, +1 to dropping that requirement 18:32:12 if nobody has an opinion on this, we should move it to the list 18:32:13 cwickert, +1 18:32:16 ok 18:32:24 the rest of the requirements looks goo 18:32:27 good 18:32:34 what about food? 18:32:47 i suggest to move to the list 18:32:50 ok 18:32:58 we dont have time enough anymore 18:33:03 most of the time it is provided by the organizers 18:33:04 you are the leader, you can decide :) 18:33:34 yes will move to the ML +1 18:33:39 +1 18:34:11 lets finish the meeting 18:35:11 #action move the discussion about the "Sponsoring event attendees" ticket #265 to the list 18:35:27 #endmeeting