17:00:34 #startmeeting FAmSCo 2012-07-16 17:00:34 Meeting started Mon Jul 16 17:00:34 2012 UTC. The chair is cwickert. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:40 #meetingname famsco 17:00:40 The meeting name has been set to 'famsco' 17:00:49 #chairs cwickert danielbruno bckurera 17:00:53 #chair cwickert danielbruno bckurera 17:00:53 Current chairs: bckurera cwickert danielbruno 17:00:57 who else is here? 17:01:11 #topic Roll call 17:01:16 .fas cwickert 17:01:16 cwickert: cwickert 'Christoph Wickert' 17:01:20 .fas bckurera 17:01:20 bckurera: bckurera 'Buddhika Kurera' 17:01:27 .fas dbruno 17:01:27 danielbruno: dbruno 'Daniel Bruno' 17:01:35 #chair aeperezt 17:01:35 Current chairs: aeperezt bckurera cwickert danielbruno 17:01:45 #chair nb 17:01:45 Current chairs: aeperezt bckurera cwickert danielbruno nb 17:01:48 .fas aeperezt 17:01:49 aeperezt: aeperezt 'Alejandro Perez' 17:02:19 .fas nick@bebout 17:02:19 nb: nb 'Nick Bebout' 17:02:50 is the wiki down? 17:03:09 working fine to me 17:03:17 fine for me too 17:03:24 working fine for me too 17:04:32 for me it is very slow 17:04:40 so how many are we? 17:04:49 * cwickert counts 5 17:04:57 * nb counts 5 17:05:01 we're 6 17:05:02 * bckurera 5/7 17:05:11 ops 17:05:23 * nb sees no clint or jiri 17:05:39 #info aeperezt bckurera cwickert danielbruno nb present, jiri still traveling, herlo missing 17:05:47 * bckurera seems same what nb seems :) 17:05:53 #topic Announcements 17:05:58 any announcements? 17:06:34 ok, none 17:06:47 hi have one 17:07:03 go ahead please 17:07:23 we should welcome 4 new Ambassadors for our team 17:07:27 #link http://lists.fedoraproject.org/pipermail/ambassadors/2012-July/019990.html 17:07:34 welcome all 17:07:36 eof :) 17:10:37 great 17:10:44 not sure if this is worth an announcement as we have new ambassadors every week it already was announced, but thanks 17:11:09 can anybody take over chairing the meeting for me? I am currently very busy and only have one eye to follow this meeting 17:11:23 so I am probably pretty slow and it's not good to waste time 17:11:35 we can make it a regular announcement from today, we need to welcome them to our team :) 17:12:02 I can do that 17:12:13 thanks, lets move then 17:12:36 another announcements? 17:12:46 nothing from me 17:12:53 bckurera: I don't think we should announce this. this is none of FAmSCo's business but FAMA 17:13:01 and FAMA already announces it 17:13:36 ok, let's move to the tickets 17:13:54 cwickert -1, this is just saying welcome to them, not any formal announcement 17:14:23 i have two tickets in mind to discuss about 17:15:36 bckurera: do as you like but I would like to use the meetings to discuss important stuff 17:16:08 danielbruno , shall we start discussing them 17:16:37 cwickert +1 , their joining is the most important thing I have :) 17:17:31 .famsco 265 17:17:31 https://fedorahosted.org/famsco/ticket/265 17:17:48 first ticket 17:18:01 is the ticket about the sponsoring event 17:18:08 danielbruno, change the topic as it suits for the ticket 17:18:45 #topic ticket 265 17:19:23 we agreed at the last meeting to discuss it in the mail list 17:19:40 danielbruno, not sure if we need to spend time disusing this ticket if the fudcon may organization and goal may change as mention on an email by rbergeron 17:19:50 yes, and FPL has something new against FUDcon 17:20:19 therefore I suggest we need to wait and see what is about to happen. 17:20:29 bckurera, +1 17:20:56 so, for me no problem 17:20:58 .fas 265 17:20:59 cwickert: habibjr265 'Mahmud Ridwan' - fathy2650 'fathy hassan' - mcmahan265 'Steve McMahan' - rajesh1265 'Rajesh Sundaram' - hill33lovehill33 '黃進福' - lan712653192 '阿龙' - white2651 'paritoshsharma' - cloud681133 'Cloud' <26572274@yahoo.com.tw> - (1 more message) 17:21:10 .famsco 265 17:21:11 https://fedorahosted.org/famsco/ticket/265 17:21:32 Therefore will move to other tickets (reimbursements) and clear them, if we have time we can discuss those proposals 17:21:39 #topic Sponsoring event attendees 17:22:34 let's move to other ticket that i have in mind 17:22:43 I think the current proposal still totally misses the point we are trying to address, but I haven't had the time to work on something myself either :( 17:23:04 should we go for 265 now or for something else? 17:23:25 go to other ticket 17:23:40 about reimbusements 17:23:40 Will move to other tickets, reimbursements, pls 17:23:54 ok 17:24:02 #topic Reimbursements 17:24:11 .famsco 301 17:24:12 https://fedorahosted.org/famsco/ticket/301 17:24:29 it's ticket is the Release Party in Peru 17:24:30 301 is not on the agenda 17:24:50 i just want some suggestions about 17:25:11 because it was very confuse 17:25:15 about what? 17:25:30 I don't think we can do anything here 17:25:43 cwickert, +1 17:25:49 * nb thinks robyn is taking care of it 17:25:56 what we should do in similar cases in the future? 17:26:05 just pay what is not approved? 17:26:21 I thing we are facing two problems 17:26:25 or even 3 17:26:31 one was stuff not approved 17:26:48 I think this was a misunderstanding and these things will happen 17:27:15 I think we should not let down our contributors in this case 17:27:27 * nb thinks it isn't a large amount 17:27:28 just pay it 17:27:32 btw: should we now officially approve the shirts? 17:27:43 * nb moves to approve the tshirts 17:28:00 actually, we can peer review it I think 17:28:02 proposal: officially approve the shirts, even if Julita said she would pay them herself 17:28:04 ok, i just think it a bit no sense 17:28:11 because every thing was clear 17:28:34 without "ifs" 17:28:45 * cwickert cannot follow danielbruno 17:29:57 ok 17:30:05 it's my personal opnion 17:30:21 sorry, but *what* is your personal opinion? 17:30:25 danielbruno, I think we should approve the tshirts, but define a warning again this type of thing. 17:30:31 aeperezt, I agree 17:30:32 * herlo apologizes for being late 17:30:43 I think this opens up scope for similar actions in future 17:30:52 danielbruno, true 17:30:55 danielbruno, +1 17:31:14 * inode0 notes no one reads these tickets to even notice and thinks you should just let it go :) 17:31:33 inode0, yeah true 17:31:37 only famsco members can read them 17:31:39 i aggree that we should not let dow out contributors 17:31:58 I think soon the new funding guideline is ready, we dont have such problems 17:32:05 but, things should be taken seriously 17:32:19 danielbruno +1 17:32:33 will inform this via FAm ML 17:32:33 especially when money is involved 17:32:46 ? 17:33:24 so for me there are now 3 questions: 1) should we now officially approve the shirts? 2) can we do something for this ticket now? 3) what can we do to prevent things like this from happening again? 17:33:32 She misunderstood, when it was explained to her she offered to pay for her "mistake" - what more do you want? 17:33:45 is everybody fine with discussing these 3 questions in that particular order? 17:34:17 I m ok 17:35:26 our time is short 17:35:30 * cwickert wonders if people fell asleep at the keyboards 17:35:40 to avoid this time of misunderstands we need to include the amount of what was approved on the ticket for the future tickets 17:35:57 we have things to do in the other ticket 17:36:26 but if someone have something to speak about, the mail list is good place to do that 17:36:31 1) Yes 2) Will approve it now 3) Soon we need to establish funding guideline which is on the trac as a proposal 17:37:01 I feel we are not short on time but we are wasting it. it cannot be true that one asks a simple yes/no question and 3 minutes later only one person replied 17:37:12 this is supposed to happen in 10 seconds 17:38:10 cwickert: I think a minute is pretty reasonable to think and reply, not everyone thinks as fast as you :) 17:38:25 or types, probably, either. 17:38:35 hello herlo welcome :) 17:38:53 bckurera: hi, I sneaked in a little bit ago 17:39:04 I feel like the meetings are becoming more and more ineffective because we are just talking randomly and nobody seems to pay attention 17:40:23 I paid attention, my response is there 17:40:27 understood. Let us move forward 17:40:51 * nb already stated his opinion 17:40:59 and cwickert already made a proposal 17:41:04 * cwickert thinks we have a problem as danielbruno left 17:41:25 * herlo hasn't responded because he came in the middle of the conversation and doesn't have enough context 17:41:29 I made a proposal how to discuss this ticket 17:41:45 cwickert, well, wouldn't the t-shirt amount be small enough to fall under peer review? 17:41:51 therefore, we dont' need a quorum of famsco to approve it/ 17:42:20 nb: we don't have a peer review yet as this policy was not yet ratified 17:42:22 nb peer review is not effective yet, it is yet a proposal 17:42:38 nb: and to that point, we shouldn't be discussing this if we already have a process. I thought it hadn't been approved yet, however. 17:42:57 should we approve the shirts now or should we continue with random stuff? 17:43:09 * nb wonders why it takes forever just to approve a policy 17:43:21 nb: let's table that 17:43:29 we can discuss after we get this issue resolved 17:43:43 nb: because nobody has a written proposal, you are welcome to work on it 17:43:46 well, i guess we don't have a quorum now if we have to have 5 members 17:43:52 cwickert, there is one in the ticket 17:43:55 i wrote it out a while back 17:44:14 this is not yet a fully worded proopsal, but anyway 17:44:16 again, let's discuss the issue at hand folks 17:44:35 $70 isn't worth all you spending all this time worrying about when it was spent to promote Fedora - just approve the actual expenses and move on :) 17:44:44 inode0: +1 17:44:48 +1 17:45:13 +1 17:45:19 I have already cast my vote above 17:45:25 I approve it 17:45:30 +1 just approve it 17:46:46 +1 17:46:54 cwickert: btw, we have 5 17:47:07 herlo: 4 17:47:12 * herlo needs a ticket number to gain context, but will +1 approval based upon what we have 17:47:17 now we have 5 again 17:47:21 herlo: 301 17:47:24 cwickert: count again :) 17:47:28 ahh, 5 :) 17:47:31 cwickert: thanks 17:48:03 sorry guys, the energy supply get down 17:48:07 i'm back 17:48:15 awesome, it only took us 20 minutes to approve USD 70 17:48:57 pls lets move >> 17:49:00 #agreed we'll cover the costs for the shirts at the F17 release party Peru, even if we did not approve them initially 17:49:11 ok, next question: is there something we can do now? 17:49:21 my humble opinion: no 17:49:33 9 minutes left :) 17:49:35 i think no 17:49:58 I just pinged rbergero again, but that's all I can do 17:50:17 +1 from me as well 17:50:28 just finished reading the ticket 17:50:38 no, but add specific amounts approve on next tickets when it is partially approved and pass this suggestion to the next approval procedure 17:50:53 aeperezt: please try to stick at one topic at a time 17:51:17 ok, lets just say there is nothing we can do 17:51:33 question 3) how can we avoid something like this in the future? 17:51:47 cwickert, that is the response to your question "is there something we can do now?" I'm on the topic 17:51:49 easily, let's get the approval process pushed through 17:52:00 #3 17:52:04 aeperezt: now != next approval 17:52:12 I think there will always be misunderstandings like the shirts, but when we say we approve something, we need to make sure it happens 17:52:23 and I wonder who of you spoke to Julita? 17:52:38 danielbruno, aeperezt: did she talk to you? 17:52:46 i do 17:53:00 cwickert, she talked to me 17:53:02 she sent an email to me 17:53:11 ok, and what did you guys do? 17:53:26 telling her that we won't pay for the shirts was not helpful 17:53:27 I think we should talk to her after we confirm the amount was cancel 17:53:53 i said for her that the ticket was approved withoutd the t-shirts 17:54:01 *without 17:54:07 yeah, but that doesn't make the payment happen 17:54:22 Julita said somebody promised her the payment will be taken care of 17:54:31 and whoever this was then needs to make it happen 17:54:49 until she contacted me on Tuesday evening, Neville was not even aware of this ticket 17:54:54 i don't know who promised it for her 17:55:06 if you want Neville to pay something, you need to assign the ticket to him 17:55:41 I think every time we approve something, we should reassign the ticket to somebody 17:55:57 and that person needs to take care of the ticket and make sure it really gets paid 17:56:05 cwickert, I did not promises her that 17:56:13 ideally, we reassign it to the credit card holders 17:57:04 in the next case we can do that 17:57:15 no, we MUST do this 17:57:20 not we *can* 17:57:30 ok, so who takes over this ticket now? I mean, even if it's on rbergero to pay, who will have an eye on it? 17:58:08 ok, I'll do it 17:58:15 I will do it 17:58:18 I am used to nagging people and kicking butts 17:58:31 #info danielbruno will make sure that #301 gets paid 17:58:32 cwickert, leave it with me 17:58:49 I think we should handle responsibility regionally 17:59:11 so when a request is from LATAM, either danielbruno or aeperezt should take care of it 17:59:14 +1 17:59:19 nag Neville and make sure it gets paid 17:59:31 No need to misundetand, but people who are in the same region knows what is the best than others, therefore we need to take care of those region wise 17:59:39 and if he cannot pay it, like in this case, we need to nag harish or rbergero 17:59:43 cwickert, but FPL is the one who has the ticket now 18:00:08 aeperezt: no, neville has it 18:00:37 aeperezt: the ticket is assigned to yn1v, not to rbergero 18:00:38 k, moving on 18:00:47 let's move to the next 18:00:52 danielbruno: I'll reassign it to you 18:00:58 ok 18:01:14 #topic Cheatcubes, printed material to Jreznik 18:01:19 .famsco 304 18:01:19 https://fedorahosted.org/famsco/ticket/304 18:01:54 ok, I think we just need to rubberstamp it 18:01:56 +1 18:02:00 USD 55 18:02:02 +1 18:02:04 I approve +1 18:02:15 +| 18:02:19 +1 18:02:23 +1 18:02:24 +1 (i disagree that this needs to be approved by famsco, it should be approved by peers) 18:02:28 but i agree with approving it 18:02:34 #agreed #304 is approved 18:02:47 #topic Request for reimbusement train tickets to Rome 18:02:52 .famsco 305 18:02:52 https://fedorahosted.org/famsco/ticket/305 18:03:30 I think we should approve it but tell him to request approval *before* he expenses something next time 18:03:38 Fedora is no self-service 18:03:44 +1 approve and notify 18:03:53 +1 approve and notify 18:04:02 +1 approve and notify 18:04:10 +1 18:04:16 +1 18:04:20 #agreed #305 is approved 18:04:30 ok, any other tickets? 18:04:39 yes........ 18:04:43 reimbursement process 18:05:09 nb: you mean 284? 18:05:23 erm. 281 18:06:08 I think we should try to get this approved asap so we can stop dealing with these smaller tickets directly and let the regional groups handle their own business. 18:06:15 it'll be good for both famsco and the regions. 18:06:24 Yes 18:06:30 I move we approve, at this meeting, https://fedorahosted.org/famsco/ticket/281#comment:10 18:06:49 USD 0-499: Approval by peer (FAmSCo member, credit card holder or a person approved by the credit card holder) 18:06:49 USD 500-1999: Approval by regional community 18:06:49 USD 2000-5000: Approval by FAmSCo 18:06:49 USD 5000+: Approval by FAmSCo. Additionally, we need somebody from Red Hat to issue a PO. 18:07:01 the guidelines of what constitutes a regional community meeting should be left up to the region t decide 18:07:04 nb: but that is only half of it 18:07:12 what is the other half? 18:07:26 Who and how to approve? 18:07:27 this is only the limits, not *how* approval works 18:07:42 what is meant by Regional Community, who is responsible? 18:07:51 bckurera, the regional meetings..... 18:07:52 or should we completely leave this to the regional communties? 18:07:58 those are the questions we need to have 18:08:00 cwickert, i think we should jsut set the amounts 18:08:00 nb: LATAM does not have regional meetings 18:08:01 bckurera: cwickert: I seriously think the Regions can decided that for themselves, we shouldn't be deciding that 18:08:08 and then the regions can decide the rest 18:08:21 cwickert, then they need to get them started...... 18:08:31 I mean we need to have clear definition to avoid misunderstandings 18:08:33 cwickert: they need to sort that out too, if meetings are not needed, that's fine, but they need to define a process themselves. 18:08:33 or come up with a way to have votes in tickets or something 18:08:37 bckurera, let the regions do it 18:08:51 the latam meetings were taken 18:08:58 FAmSCo spends way too much time on approving minor expenses 18:09:02 I think the mandate should be that each region has a process for approving money up to $2k USD 18:09:05 what about the concerns that inode0 stated? 18:09:12 whether it's in a meeting or over email 18:09:19 no 18:09:37 well, I don't care how it is done, meeting or email, but it needs to be transparent 18:09:43 I like the idea, will approve it and let the regions to handle it 18:09:45 we are giving guidelines here, not stating a hard requirement 18:09:52 this means we need a ticket in the tracker and a link to the mail or the meeting log 18:10:09 one of the biggest problems we are facing is finding out who approved what 18:10:12 No every request should be on the trac 18:10:18 cwickert, latam is in the process to have regional meetings 18:10:27 cwickert: agreed. We can require that it be transparent and reported on every transaction. It just means tht the famsco member in that community will need to be the watchdog for that region. 18:10:27 and we need to make sure to not loose control when we give it to the regional communties 18:10:32 or the CC holder maybe 18:10:58 I argued about this with inode0 for quite a while 18:11:09 I think some of his concerns are valid 18:11:20 yes, but we need to start somewhere 18:11:24 if this doesn't work, then change it 18:11:27 say you only have the same 3 people at the meetings every time and they make decisions 18:11:28 but right now what we have isn't working 18:11:38 +1 , FAmSCo member should be responsible, if there is something wrong it should be taken into FAmSCo by the member 18:11:44 cwickert: and this is a problem how? We are a meritocracy 18:11:50 cwickert, then more people should start showing up 18:12:09 say these three people make 10 decisions over 2k each 18:12:19 voila, there does the budget for the complete year 18:12:27 bckurera: exactly, I agree that a famsco member or cc holder should be involved with every decision in a region 18:12:34 cwickert, but we are making up problems that haven't happened 18:12:37 if nothing more than being aware, that's involvement 18:12:50 we keep mentioning "what if"...... but we haven't had a problem as it is 18:12:58 not everything goes through famsco now anyway 18:13:01 cwickert: that wouldn't happen according to the guidelines above 18:13:06 herlo: involved is ok, but not being held responsible 18:13:11 $2kusd requres famsco involvement 18:13:12 herlo: why not? 18:13:19 herlo: then 1999 each 18:13:20 aka approval 18:13:29 afaik the max spevack rules are still in effect (so far) that say people can spend $300 or $500 without any approval 18:13:40 and at least some regions approve stuff on their own as it is 18:13:46 There are FAmSCo members, cant they take the responsibility in their own regions? 18:13:59 cwickert: I think you are not trusting the peopel in the region if you are concerend about that 18:14:12 nb: they never were effective. I know two credit card holders who said they don't and cannot follow Max's rules 18:14:27 cwickert, they were in NA at least 18:14:27 truthfully, some people liek to take advantage of the situation you present, but I am just willing to trust the contributors to the point that they will police themselves. 18:14:33 i know no one approves the small expenses I make 18:14:36 no one as in no committee 18:14:46 nb: inode was one of the cc holders I was talking about. 18:14:48 if i buy shipping supplies, i just ask inode0 to paypal me money 18:15:00 I am afraid we are putting them into a difficult situation 18:15:13 because they are ultimately responsible 18:15:16 I think it's all about trust 18:15:20 cwickert, nothing says they have to pay it 18:15:24 they can say no, ask someone else 18:15:27 they have signed a contract with RH 18:15:32 and then? 18:15:34 FAmSCo cannot force the credit card holders to do something 18:15:39 right 18:15:48 cwickert, plus there's always the redhat cc holders 18:15:50 who can pay for stuff too 18:16:08 lets not advocate this, this is dangerous 18:16:16 you just have to trust that people will do the right thing. I am less concerned if someone tries to screw us over. It's just if that happens, we'll deal with it then. Arguing over piddly amounts like $70USD seems more wasteful than worrying about the chances of being scammed 18:16:24 herlo, +10000000 18:16:39 * nb suggests we take a damn vote on this, we've been discussing it long enough 18:16:42 we need to do SOMETHING 18:16:43 because people will start: oh, lets make a stupid decision and buy a pink pony. if inode0 doesn't pay it I'll look for somebody else 18:17:03 cwickert: and if they do, so be it. It's not up to us to police the people 18:17:05 FAmSCo should not be asked for approval for $70 purchases 18:17:20 nb: I fully agree 18:17:21 it's up to them to police themselves. They are here because they want to help fedora, not cause pain and anguish 18:17:30 * nb requests we take a vote on comment 10 18:17:33 but before I change something, I want it bulletproov 18:17:42 nb: what exactly? 18:17:55 the suggestions in that comment, too or only the limits? 18:18:09 comment 10 is not a fully worded proposal 18:18:16 the limits 18:18:20 and let the regions decide the rest 18:18:22 cwickert: it's not going to be bulletproof. 18:18:31 #proposal approve the limits in comment 10, let the regions decide how to implement them 18:18:42 plus, we can state that all decisions be recorded and transparent in some fashion 18:18:53 nb +1 herlo +1 18:19:07 I don't care how, just that they report them each quarter, month, or something. 18:19:15 and plus every region FAmSCo member should be responsible for every decision the region take 18:19:24 bckurera: no, please not 18:19:31 they cannot be held responsible 18:19:49 cwickert I dont get the idea? 18:19:57 * nb thinks they should just be held responsible for what they approve as a peer 18:20:01 not for everything the region does 18:20:39 bckurera: I am traveling a lot recently. say some idiots and approve a pink pony for USD 1999 and I am the one who is held responsible even if I was not at the meeting or even though I disagreed? 18:20:40 bckurera: no, I agree with cwickert and nb here. The problem is that would take way more resources. I think we just need to trust our contributors. 18:20:45 My point is this, we need to make sure the approval is transparent, for that we need to responsible 18:21:08 bckurera: approval is not the issue here, it's responsibility 18:21:15 what they agree is not our responsibility but we need to make sure that the process is transparent, if it is not we need to ring the bell 18:21:16 bckurera: what does "responsibility" mean? do I have to pay it from my own pocket if nobody else wants to take it over? 18:21:37 the value of this is who's responsible. I think that's a collective thing. We're all here because we like the values in the fedora project, no? 18:21:39 bckurera, later it could be that there is no famsco member for a particular region then who will be responsable 18:22:12 aeperezt it is tricky question to answer, :) 18:22:17 * nb thinks the famsco member should try to make sure that it is transparent 18:22:23 but i don't know that we should use the word responsible 18:22:26 If so, I believe we should let others in the group have the same right. We judge them only if there is an error or as cwickert says, they buy a pink pony. If we're transparent and willing to correct mistakes as we go, this will likely not be a concern at all. 18:22:32 plus, it is not guaranteed that there is a member in each region 18:22:32 ok, so lets add: "If your request was approved, you are responsible of documenting this decision in a transparent manner for reporting and make sure the credit card holder is aware of it" 18:22:36 nb that is his responsibility I mean :) 18:22:36 nb, +1 18:22:40 cwickert, +1 18:22:56 cwickert, +1 18:22:58 cwickert: +1 18:23:01 ok, lets try to break this down into smaller pieces 18:23:06 first only the limits 18:23:14 +1 to the limits in comment 10 18:23:19 Id like to change 5000 to 4999 please :) 18:23:22 ok 18:23:28 not that it really matters, just for consistency 18:23:32 bckurera: no responsibility clause, it causes problems against volunteers who are just trying to do the best that they can. 18:23:41 herlo: +1 18:23:50 everybody agrees to the limits? 18:24:00 +1 18:24:03 +1 18:24:09 +1 18:24:19 +1 18:24:25 +1 18:24:29 ok +1 18:24:34 yay! 18:24:40 #topic Budget review guidelines 18:25:20 #agreed limits from https://fedorahosted.org/famsco/ticket/281#comment:10 are approved, only 5000 will be changed to 4000 for consistency 18:25:30 * bckurera since there is 5 votes mine makes no difference :) 18:25:38 ok, next thing is the transparency 18:25:41 but I agree with the idea :) 18:25:55 bckurera: yes it does :) 18:25:56 +1 for what I proposed before: "If your request was approved, you are responsible of documenting this decision in a transparent manner for reporting and make sure the credit card holder is aware of it" 18:26:01 the more votes is better 18:26:04 shall we agree to use trac please? 18:26:11 bckurera: no 18:26:18 why? 18:26:23 bckurera: your region can discuss and agree on their own 18:26:34 each region should have a transparent process for approval, however. 18:26:34 I think we need trac 18:26:59 herlo -1 we need to be uniform all over the project, not APAC can use something and EMEA another thing 18:26:59 I mean, for that amount of money, requiring a ticket is not too much, is it? 18:27:04 we all need to use something common 18:27:10 I think the region should decide. I agree that *we* personally need trac, but I don't want to force trac on every region just because they might do it a bit differently. 18:27:21 bckurera: we do not 18:27:44 trac is the ebst way to track it, so I strongly +1 to trac 18:27:46 so say we use mailing lists... I then link to a ticket and say: "hey, we approved this here in this mail" 18:27:55 but then a flame war starts and people disagree 18:28:03 now try to find out who is right 18:28:21 yes indeed cwickert 18:28:31 cwickert: are we talking about famsco or above approvals? or per region here? 18:28:41 herlo: per region or per peer 18:28:57 I stil think the region can use trac and we can recommend it. I just don't like the requirement of trac if something else works. 18:29:06 I mean, we need a trac ticket anyway to attach the invoice and handle the payment 18:29:21 good point :) 18:29:24 you wouldn't do this on a mailing list 18:29:33 the trac is a great tool for that 18:29:36 and if you use private mail, it's no longer transparent 18:29:52 no private mail at all 18:29:56 please, let us make the live of the CC holders a bit easier and require a ticket 18:30:21 I know how much time kital needs for reporting and RH accounting folks want to see everything 18:30:31 they even require him to print out event reports 18:30:43 of recently, they wanted a list of people who were at a dinner 18:30:48 I don't think the conversation about payment or what not needs to be transparent, only the resulting amount and justification for the costs 18:30:59 again, I think it's a regional thing. 18:31:14 all regions have trac instances already 18:31:17 cwickert: I actually think it will make the lives of the cc holders more complex. 18:31:39 they shouldn't need to be the one putting in the information, whether it be in a ticket or whatever system they use 18:31:41 herlo: how so? kital prints out the tickets and the event reports and attachments 18:32:00 herlo: but RH accounting wants to see it 18:32:22 IDK, i'm kind of +0 to requiring trac 18:32:30 i think its a good idea to do stuff in trac 18:32:39 but what if a region wants to use a mailing list or something? 18:33:07 nb: how can you make sure a mail on a list is authoritative? 18:33:10 I think it's a good idea to have stuff in trac, I'm ont arguing that. I'm just saying that the regions should decide that for themselves. Maybe they want to use some other ticketing system or a bit of software that we haven't considered yet 18:33:17 No they should use the trac for the sake of the clarity, or soon this system will collapse 18:33:42 meh 18:34:04 we don't say the decision needs to happen in trac 18:34:11 'trac' is the problem here. It's *one* system that we're locking people into, I want to let them choose the system as long as it provids the information we need. 18:34:22 herlo they can use whatever they need but should be align with the projects' tools as well ! 18:34:24 * herlo notes the foss mentality here :) 18:34:28 but you should add a link to the meeting log or the mail where the decision took place 18:34:43 cwickert: +1 18:34:45 herlo: try to tell RH accounting of floss mentality ;) 18:34:46 i agree with cwickert 18:35:16 * herlo thinks the problem is with 'requiring' software 18:35:29 I don't care how it's done and we can 'recommend' trac as it makes the most sense now. 18:35:40 I just care that it's not an edict 18:36:02 shall we please take a decision not 18:36:13 time is running, it is 1:30 hrs now 18:36:41 bckurera: I don't think there's a decision to be made, really. It's just a matter of how we state it to the regions. 18:36:44 #proposal strongly recommend using trac, do not require trac, leave the decision up to the regions 18:36:51 *require* transparency and *recoomend* trac? 18:36:53 nb: +1 18:36:59 cwickert: perfect! 18:37:01 #proposal require some form of transparency 18:37:22 +1 18:37:39 My opinion is they *should* use the trac and I vote for it. 18:38:07 bckurera: should is a fine word :) 18:38:40 bckurera: "should" is pretty weak, but I get what you mean and I am with you 18:38:49 who is still around? danielbruno, aeperezt? 18:38:54 strongly recommend is fine with me 18:38:57 * danielbruno is here 18:39:09 here 18:39:09 ok, danielbruno: require or recommend? 18:39:10 good cwickert :) 18:39:22 * nb suggests "strongly recommend" 18:39:32 "urge" /me runs 18:39:42 i'm "strongly recommend" 18:39:52 ok then *require* or *strongly recommend* ? 18:40:00 * aeperezt strongly recommend 18:40:06 ok, it seems we have a winner 18:40:06 cwickert: hehe 18:40:29 ok, what about the other suggestions, lets quickly go through them 18:40:37 but the region that don't want use must to prove that the tool or way used are trusted 18:40:48 *dont't want use trac 18:40:58 "minimum of 5 ambassadors at regional meetings"? +1 or -1? 18:41:11 +1 18:41:28 danielbruno: do you think this is realistic for LATAM? 18:41:34 bckurera: how about APAC? 18:41:41 meh, I tihnk the process is still should be up to regional folks. To decide the process itself there, sure 5minimum is good 18:41:43 cwickert, yes 18:41:46 we already practice and we are fine with this 18:42:18 just define what the results should look like, let them come up with the process. Trust them to find a better way than we can. 18:42:29 5 would be a good minimum limit 18:42:40 herlo: how about we require a minimum of attendees, we recommend it to be 5 but leave it up to the communities? 18:42:43 I'm sorry I'm being difficult, but I don't think it's up to us to decide even this detail 18:43:20 * cwickert is going to have meetings with himself and approve everything with 100% of the votes :) 18:43:23 cwickert: it should be 'reasonable'. In NA it can and has been 2 or 3 for approval 18:43:36 ok, "more than one" :) 18:43:36 cwickert: go ahead, as long as you are transparent 18:43:42 cwickert: sure 18:44:09 ok, so should we require a minimum at all? 18:44:12 * herlo ribs cwickert about approving in meetings with himself and wonders if he actually talks :) 18:44:28 cwickert: I think it's an implementation detail that each region will take care of on their own. 18:44:39 recommending something though, I'm all for that 18:44:44 just like trac 18:44:47 :P 18:44:52 ok, I just had a private famsco meeting with myself and agreed with me that we should have at least 5 people :P 18:45:04 lol 18:45:15 too bad you don't make a quorum :) 18:45:26 in my private famsco I do :) 18:45:28 the region should meet to discuss the rules 18:45:35 it's not up to famsco 18:45:44 Further FAmSCo should have to have the control, like if something went wrong ! 18:45:49 cwickert: even your private famsco in your head :) 18:45:58 herlo, +1 18:46:38 can we please now all cast our vote: should we set a minimum (no matter what)? +1 or -1? 18:46:45 -1 18:46:51 +1 18:47:11 * herlo needs to go in 5 minutes 18:47:16 +1 18:47:19 -1 18:47:23 +1 18:47:30 there is the winner :) 18:47:32 nb: your turn 18:47:38 bckurera: nb hasn't voted 18:47:38 not yet bckurera 18:47:48 and we don't have a majority yet 18:47:58 * bckurera :) 18:48:08 3 out of 7 is not enough I think 18:48:31 silence means 0 ? ;) 18:48:40 won't help us either 18:48:56 ok, lets delay this 18:49:04 I think we already achieved something 18:49:13 almost 2 hrs on the meeting :) 18:49:23 well, I think we can get the documentation started. This detail can be discussed later and added if voted in... 18:49:38 then it can be added at that time. 18:49:43 I think we can start using it right away, but we really need somebody to make a nice paragraph for the wiki of it 18:50:05 cwickert: I can do that this afternoon. I think nb wanted to help me, so we'll start on it.... 18:50:07 I suggest that a native English speaker like herlo or nb goes for it 18:50:11 if he doesn't I can still do it... 18:50:14 herlo, can you do that? 18:50:21 :) 18:50:27 #action herlo to word our decisions nicely 18:50:29 danielbruno: yas, as I stated above. 18:50:34 :) 18:50:41 * herlo heads out 18:50:43 herlo: but no cheating, don't strip down our requirements ;) 18:50:46 thanks gang! 18:50:51 cwickert: lol, I don't cheat 18:50:58 only in horshoes and hand grenades 18:51:00 lets have a final approval next week 18:51:06 sounds good 18:51:06 lol 18:51:12 ok, thanks everybody 18:51:13 take care! 18:51:15 that is fine, till next week will wait then? 18:51:19 horseshoes even! 18:51:27 thanks for the very long meeting B) 18:51:30 bckurera: well, I am going to write up the details 18:51:34 then we can vote on it 18:51:36 i'll miss the next meeting 18:51:37 :( 18:51:48 bckurera: yes, you can start using it in your next meeting, as long as you don't make the decision alone, you are fine 18:51:49 i 'll be traveling to the FISL 18:51:49 nb will be missing too 18:51:58 danielbruno: I'll email when the text is up 18:52:03 then you guys can vote at that point. 18:52:06 k 18:52:07 I will miss the next meeting, too I think 18:52:10 cwickert like the private FAmSCo meeting :D 18:52:12 by email or on the talk page or something. 18:52:23 cwickert: maybe we should move the meeting to a differnet day?? 18:52:39 a special meeting? 18:52:39 3 people out is a likely problem. 18:52:42 Just for next week 18:52:43 herlo: only for a week? 18:52:47 yes 18:52:52 i'll send my vote from some airport 18:52:56 lol 18:52:59 herlo: doesn't make a difference for me, the rest of the week is actually worse 18:53:09 we use the trac to vote without shifting the meeting 18:53:16 cwickert: earlier, like sunday at the same time? 18:53:33 please, no 18:53:38 bckurera: sure, it's not that. I would like to have people there to discuss the other issues if we're going to meet 18:53:46 lets discuss this on the list 18:53:50 #endmeeting