17:00:23 #startmeeting FAmSCo 2013-05-06 17:00:23 Meeting started Mon May 6 17:00:23 2013 UTC. The chair is sesivany. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:26 #meetingname famsco 17:00:26 The meeting name has been set to 'famsco' 17:00:32 #topic Roll call 17:00:33 .fas tuanta 17:00:34 tuanta: tuanta 'Truong Anh Tuan' 17:00:38 .fas eischmann 17:00:39 sesivany: eischmann 'Jiri Eischmann' 17:00:58 hello, I am back :) 17:01:03 .fas aeperezt 17:01:04 aeperezt: aeperezt 'Alejandro Perez' 17:01:16 hello tuanta 17:01:35 .fas nick@bebout 17:01:36 nb: nb 'Nick Bebout' 17:01:53 hello aeperezt et all 17:02:03 great, we've got a quorum today :) 17:02:21 let's wait a few more minutes for others... 17:03:05 hello all 17:04:22 ok, let's start... 17:04:28 #topic Announcements 17:04:42 does anyone have an announcement to say? 17:05:51 nope from me 17:05:54 seems like there are no announcements... 17:06:17 ok, let's move on then 17:06:38 #topic F19 t-shirts for contributors 17:06:58 as I promised I started a discussion in the ambassadors mailing list. 17:07:20 have you seen that? 17:07:31 yes, I see. an interesting discussion. 17:07:46 yes good points 17:08:18 yeah, some claimed that having t-shirts just for release party organizers is not fair. 17:08:38 sesivany, right 17:08:38 I agree, but I've got one concern. 17:08:40 I share ideas with John to have it for all contributors (not only ambassadors). I think, that's also our point. 17:08:43 and true 17:09:31 what concern, sesivany? 17:09:32 but I don't think we have budget to make that many t-shirts or to send them 17:09:51 we might make it so big that we won't be able to make it happen. So the result may be that we won't have t-shirts for anyone just not to discriminate. 17:10:19 T-shirt for all contributors so budget should come from other sources, not one for ambassadors 17:10:42 sesivany: yes, that a big task 17:10:43 the way I think is we wanted to do something special for those people that do release parties now ended up with nothing 17:10:53 tuanta: it's not only about the budget, if you want to send t-shirts to any contributors, it's logistically much more difficult. 17:11:11 but we can do one by one 17:11:41 we have a big plan for all contributors, but we can start with smaller groups like ambassadors 17:12:22 ok, let's assume that ambassadors can handle it. What do you think it would be the best approach? Should we produce it in each region locally? 17:12:41 tuanta: the problem is that we have a budget till May 20th, then it's gone. 17:13:12 sesivany, that is the other consideration, if a t-shirt cost 3 dls to make send it to Panama may cost 15 dls to other countries that shipping can be higher making almost imposible to budget it if we can find a provider that wanted to do the logistics for us 17:13:56 I can produce, say, 200 t-shirts very quickly, but then how to distribute it to other regions? 17:14:17 sesivany, we can produce them locally 17:14:46 the problem is that people say that every contributor should get a t-shirt, but no one says that he/she gives a helping hand. 17:14:50 sesivany, depending on the amount of colors an all that we can make them here for between 5 to 8 each 17:14:58 dls 17:15:09 then is the shipping cost 17:15:35 and countries like Argentina and Venezuela that people may ended up paying import taxes 17:16:27 aeperezt: the problem is how you'd pay for it? If I produce it here, I can charge Red Hat directly, no reimbursement and other hassle. 17:16:46 aeperezt: is there any way to pay for things by Red Hat in LATAM? 17:17:42 sesivany, well in latam we can produce in Nicaragua then Neville can charge it to Red Hat credit card and I have ear that cost to make is cheaper than Panama 17:18:17 the issue will be the logistics and shipping 17:18:32 Producing locally is better at first glance; but see more carefully, I think do that centrally is better because of quantity (about 100-200 at first, I think) 17:18:49 aeperezt: and time because based on experience, 14 days is damn short to trigger such a thing... :-/ 17:19:36 sesivany, I can make them on 14 days in Panama 17:19:41 not sure Nicaragua 17:20:19 there are a lot of issues in shipping (import tax, etc.) in APAC regardless from EMEA or from other APAC countries 17:20:47 aeperezt: btw the problem with charging a community credit card is that payments made in May will land in RHT accounting in June, so we won't make this quarter. 17:20:51 also, we have not much time, so I vote +1 for the option to produce it centrally 17:21:38 sesivany, well the other way around will be Chile or Brasil were Red Hat has offices but no idea that can be done on time 17:22:43 sesivany, the way I see it, it is to late to create a t-shirt for all contributors and now we cannot make anything special for people that work on release parties 17:23:00 aeperezt: ok, for now, I'd go for the central production as first option. We can also explore local production options. But first we need the design. 17:23:04 Maybe you can do for EMEA and that will be good 17:24:35 #info producing F19 t-shirts for contributors centrally seems to be more likely doable, but we'll explore local options, too. 17:25:02 #info it needs to be done in 2 weeks (very short time). 17:25:05 If we want to use the budget that is left then we should made for EMEA and NA. 17:25:44 aeperezt: why don't we make for APAC, LATAM as well? 17:25:46 pic up a design and make it happend or we lose the budget that is there and we must not allow that to happend 17:25:57 I'll also explore how expensive sending small packages worldwide is. In EMEA, it's about $4 for a package. 17:26:37 tuanta, two issues we cannot paid them on time so it is spend on this quater budget 17:27:01 and the logistics to send them to latam countries 17:27:11 and Apac countries 17:27:16 but we are planning to produce T-shirts centrally in EMEA, right? 17:27:40 aeperezt: I think it'd be easier to send one t-shirt per package to APAC and LATAM than sending a big package with 100 t-shirts. 17:27:56 +1 sesivany 17:28:04 aeperezt: big packages attract customs much more 17:28:12 big +1 17:28:24 and small packages with one t-shirt may not even be applicable to taxation. 17:28:33 sesivany, who is going to do the logistics 17:29:09 it got more efforts to sender, but much less efforts to receivers, especially in APAC 17:29:20 sesivany, you need a list of all contributors with the t-shirt size, package it and send individually that plus how expensive it will be is the trick 17:29:29 so in the end, it might be even cheaper because I'd send small packages with normal mail, I wouldnt dare the same with an expensive package with 100 t-shirts. 17:30:32 sesivany: that's one thing I concerned. Thanks for that information. 17:31:01 sesivany, to me it make more sense at this point create a special label for f19 and send it to all contributors that could be on a letter 17:31:09 easy cheap and fast 17:31:11 aeperezt: criteria who's going to get one should not be our problem outside ambassadors. If other teams want to participate, they should do their homework and at least decide how's going to get them. 17:31:32 even you send a big package to a central point, you still need to divide to each one to send to each person 17:31:55 so sending one by one from beginning is much better 17:32:24 sesivany, the logistics is going to be massive if we send to all amabassadors and other groups 17:33:30 aeperezt: definitely not all ambassador, only packagers have about 600 contributors, the whole contributor base of Fedora might have thousands of people. We certainly can't give a t-shirt to everyone. 17:33:55 for us, it's still the same: only release party organizers. 17:34:16 sesivany, I'm trying to think how we can make it easy and simple to manage, maybe later we can create something more special 17:34:38 other teams will have an opportunity to recognize their contributors. 17:35:05 we have over 65,000 accounts registered in FAS 17:35:30 aeperezt: my plan is to produce some number of t-shirts for F19 to use the money left. Then we will have time to figure out how to use them. There is a plenty of options. 17:36:11 the decision is: t-shirts or no t-shirts. 17:36:32 sesivany, on the other hand there are many countries with people on the ambassador list that don't do a thing for Fedora anymore 17:37:17 +1 t-shirts :) 17:37:28 aeperezt: as I said, for ambassadors, we'll have the t-shirt for organizing a release party, other teams will have to come up with some reasonable criteria, too. 17:37:32 sesivany, well that is why, mention that we could made the t-shirts for EMEA and NA 17:37:53 aeperezt: only active contributors (and unfortunately not all of them) should get one. 17:38:28 sesivany, lets do the t-shirts and see the logistics later 17:38:57 sesivany, I know that all QA team deserve them 17:38:59 there are a lot of active ambassadors in APAC, aeperezt. 17:39:00 ok, I'll get the design a quotes for the next meeting, then we can move it forward. 17:39:12 sesivany, right 17:39:46 #action sesivany to get a design for F19 t-shirts and get quotes from a vendor. 17:40:02 ok, let's move on, we've spent a lot of time on this. 17:40:21 ok 17:40:31 #topic Flock 2013 17:41:16 cwickert was complaining in the fudcon-planning mailing list that he didn't know about Flock and that it was replacing FUDCon EMEA and NA... 17:41:28 I know we touched it several times. 17:41:40 but is here anyone who didn't know about it? 17:42:06 because as cwickert pointed out no one approached us officially. 17:42:22 I announced it in the last APAC meeting 17:42:41 yes, just us, in FAmSCo :) 17:42:43 sesivany, well I have to say it, we all have ear rummors about flock, and it came as a sorprise to see all created and done in not so open way 17:42:43 #link http://fedoraproject.org/wiki/Flock 17:43:35 the last time I read FAMSCO has to nominate someone to be on a commite in flock 17:44:04 aeperezt: yeah, I wasn't involved in planning it, I just kept hearing little info about it and I've known more only for last 3 weeks after it was revealed in the fudcon-planning list. 17:45:11 aeperezt: where did you read it? 17:45:21 and sinces the organization of flock has a obscure or grey area not sure what we can solve around it if we discuss it 17:45:33 #info Flock is replacing FUDCon EMEA and NA 17:45:36 sesivany, an email on the flock planning list 17:45:58 aeperezt: yeah, I see it. 17:46:08 #link http://lists.fedoraproject.org/pipermail/flock-planning/2013-April/000031.html 17:46:42 oh, a new mailing list 17:46:57 tuanta: yeah, there is a new one. 17:47:04 sesivany, flock will have one FAMSCO member on therir committe 17:47:35 just subscribed 17:47:35 I don't understand why we needed a separate list we could have that on the fudcon-planning list 17:47:42 aeperezt: still, we haven't been approached by anyone from the organizer's team. 17:47:50 sesivany, right 17:48:19 sesivany, and that will be for the conference committee 17:49:05 :) 17:49:13 should we wait or should we be proactive and ask them what's FAmSCo's role in Flock's planning? 17:49:40 * nb is somewhat concerned at the lack of transparency in flock planning 17:51:03 nb: I'm afraid that the damage has been done, the planning should have been transparent from the very first beginning. 17:51:10 nb, we all are 17:51:48 yeah 17:52:43 sesivany, and we keep been in the dark 17:53:14 * nb wonders if we could send a request from famsco to the flock team to start being more transparent 17:53:22 about the planning process 17:53:40 nb: that's a good idea 17:54:01 I can do that 17:54:10 #proposal FAmSCo formally requests the Flock planning team to be more transparent with the Flock planning process. 17:54:15 +1 17:54:18 +1 17:54:26 + 17:54:28 +1 17:54:58 tuanta: your vote matters ;) 17:54:59 tuanta, ? 17:55:12 +1 17:55:17 great 17:55:31 #agreed FAmSCo formally requests the Flock planning team to be more transparent with the Flock planning process. 17:56:30 do you have anything else to discuss today? 17:56:48 i do not 17:57:14 #topic Openfloor 17:57:34 btw there is a discussion going on in the fama list. 17:57:39 sesivany, can you send our request to the planners? (i.e. spot, suehle, rbergero)? 17:58:02 nb: I'll write to the flock mailing list directly. 17:58:06 ok 17:58:23 nb: if we want them to be transparent, we should be transparent too :) 17:58:30 true 17:58:58 #action sesivany to write the request to the flock mailing list 18:00:11 ok, if there is nothing else to discuss, I'll end the meeting. 18:00:26 thank you, everyone, for attending today! 18:00:31 see you next week! 18:00:35 see you 18:00:55 see you next week 18:01:20 #endmeeting