00:58:27 #startmeeting FAmNA 00:58:27 Meeting started Fri Apr 14 00:58:27 2017 UTC. The chair is award3535. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:58:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:58:27 The meeting name has been set to 'famna' 00:58:42 #meetingname FAmNA 00:58:42 The meeting name has been set to 'famna' 00:58:56 #topic === FAmNA Roll Call === 00:59:05 #chair jsandys reher 00:59:05 Current chairs: award3535 jsandys reher 00:59:10 * mikedep333_ is here 00:59:35 #chair mikedep333_ 00:59:35 Current chairs: award3535 jsandys mikedep333_ reher 01:00:26 * mikedep333_ needs to fix his _ account 01:01:37 #topic === Announcements === 01:02:06 I have one to post when everyone is ready 01:02:19 ready 01:02:38 #info Fedora Council wiki page development requirement 01:02:38 What - what the event is and what its all about 01:02:38 Where - Where the event is located to include lodging availability if applicable 01:02:38 When - Dates of the event, schedule of events to include time frames 01:02:38 Who - List of Fedora attendees, major guest speakers and sponsors 01:02:39 Why - Give a general or specific reason why Fedora is making an appearance at the event or conference 01:03:15 the 5 W's must be on every wiki that we create for events or conferences 01:03:32 Sounds good 01:03:40 jsandys, please look at the SELF wiki and form yours for LFNW 01:04:12 .hello dmossor 01:04:13 danofsatx: dmossor 'Dan Mossor' 01:04:19 for events that are already past there is no need to change what is already there 01:04:26 #chair danosatx 01:04:26 Current chairs: award3535 danosatx jsandys mikedep333_ reher 01:04:52 close, but no cigar ;) 01:05:04 I took a first cut at changing it, some of the topics didn't seem to apply 01:05:16 #chair danofsatx 01:05:16 Current chairs: award3535 danofsatx danosatx jsandys mikedep333_ reher 01:05:25 I'll take a cut with 5Ws 01:05:32 danofsatx sorry, got ahead of my own typing 01:05:44 o/ 01:05:48 danofsatx did you see the earlier post 01:05:55 #chair juggler 01:05:55 Current chairs: award3535 danofsatx danosatx jsandys juggler mikedep333_ reher 01:06:24 reposting for those who just entered the room 01:06:28 9:02:39 PM - award3535: #info Fedora Council wiki page development requirement 01:06:28 9:02:39 PM - award3535: What - what the event is and what its all about 01:06:28 9:02:39 PM - award3535: Where - Where the event is located to include lodging availability if applicable 01:06:28 9:02:39 PM - award3535: When - Dates of the event, schedule of events to include time frames 01:06:28 9:02:39 PM - award3535: Who - List of Fedora attendees, major guest speakers and sponsors 01:06:28 9:02:39 PM - award3535: Why - Give a general or specific reason why Fedora is making an appearance at the event or conference 01:06:28 9:03:16 PM - award3535: the 5 W's must be on every wiki that we create for events or conferences 01:06:32 yes, reading 01:06:43 er, read, I should say 01:07:20 the council has pointed out they want more dedication to the event of why we need to be there 01:07:58 justifiable, IMHO 01:09:34 I agree, at first I looked at it as more squeezing of the money pot, but after I cooled off and started asking more questions it seems very reasonable and justifiable 01:10:47 most of the wiki pages we create already have 4 of the 5, we were just missing the why 01:11:38 I believe we should have a presence and support the organizations that support us, it is a balancing act. 01:11:58 Also the reports should cover the basis of all the 5 areas. we already do very well in the reports 01:12:32 5 areas = 5 Ws ? 01:12:38 award3535: ack. 01:12:51 jsandys that also is true, but the council wants more of why should we be there, and what we expect to get out of the event 01:13:01 jsandys yes 5 w's 01:13:43 I guess you can say that they want metrics for the money spent on the event 01:14:37 What should be measured? New installations? How? 01:15:40 jsandys for example your event, you are promoting the security spin, how many did you bring with you, and how many you gave out that is one metric. 01:16:31 another could be did you assist in loading the same or did you demonstrate how to, and how many were there 01:16:36 I'm building the kiosk to take guest comments? 01:16:55 jsandys that too is a metric 01:17:00 What checkboxes should I ask? 01:18:17 jsandys that is where you as an ambassador that knows your event should come up with questions 01:18:44 be creative, the council really likes the creative edge 01:19:40 #chair kk4ewt 01:19:40 Current chairs: award3535 danofsatx danosatx jsandys juggler kk4ewt mikedep333_ reher 01:19:49 Just testing a webcam on the RPI to capture the badge QR code to get contact information. 01:21:11 jsandys, that is exactly what the council is looking for, creative and innovative thinking, now just tie in the why metric and your good 01:21:21 ok lets move onto tickets 01:21:35 #topic === Tickets === 01:21:51 https://pagure.io/ambassadors-na/tasks/issues 01:22:01 I think the council is also looking for marketing with ambassadors 01:22:15 .famnaticket 170 01:22:16 award3535: Issue #170: Bitcamp 2017 - tasks - Pagure - https://pagure.io/ambassadors-na/tasks/issue/170 01:22:25 jsandys that too is correct 01:23:04 Bitcamp folks please complete your reports and reimbursement requests 01:23:25 I will complete my reimbursement request. 01:23:36 http://mikedep333.blogspot.com/2017/04/fedora-bitcamp-2017-wrap-up.html 01:23:55 mikedep333_ thank you.... 01:24:32 Do reimbursement go on the same ticket or new? 01:24:38 that is all I had on that ticket 01:25:26 jsandys new ticket under FAmNA requests and make a private ticket, that way only a very limited number of people have access to the ticket 01:25:39 and on pagure 01:26:24 moving on 01:26:27 #topic == Open Floor === 01:26:28 Link to FAmNA requests? 01:26:38 jsandys stand by... 01:27:26 TRAC ? 01:27:30 https://pagure.io/ambassadors-na/tasks/issues?status=Open&tags=reimbursement&tags=request 01:27:41 jsandys trac is dead 01:27:45 Thanks 01:28:15 ok we are having an issue getting stuff back from Bitcamp, I have contacted the event lead and he is contacting the event people to find out why our stuff hasnt been seen by ups 01:28:41 jsandys ensure you go on the right side of the ticket under metadata and select reimbursements, and the check in the private block 01:28:48 kk4ewt rgr... 01:28:56 K 01:29:30 so did the event take responsibility for the event box 01:29:46 mikedep333_ were you there 01:30:03 do you know of this situation 01:30:17 award3535, i am just making the report, its being worked on 01:30:18 I left it on the table. 01:30:35 I left it during the award ceremony. 01:30:41 kk4ewt ok thank you 01:30:51 I did not hand it over to anyone personally. 01:30:57 (same with the banner) 01:31:24 mikedep333_ sounds like kk4ewt has it under control 01:32:54 kk4ewt did you see my edit on the SELF Wiki 01:33:02 nope 01:33:53 yep 01:34:59 kk4ewt just pm'd you 01:37:48 How does the council expect to use ambassadors for marketing and other development activities? 01:38:12 jsandys they have not come down with that information yet 01:38:39 Part 2 of the note. 01:39:29 the only reason I found out about this requirement was a ticket I filed with the council, and got the 12ga blast 01:40:20 so my recommendation is that if you can sit in on a council meeting and listen I would 01:42:17 when do they meet, on IRC or telecon? 01:42:34 gonna head out to commute for my next meeting. have a good evening all. 01:42:56 juggler thank you for attending... have a good evening 01:43:40 you too, award! 01:43:56 jsandys let me check 01:46:14 I can probably find it. 01:47:57 https://fedoraproject.org/wiki/CommOps is a good place to start 01:48:37 open in other screen 01:49:14 Does anyone else have anything for the group 01:49:36 not i 01:49:57 jsandys https://fedoraproject.org/wiki/Council_Meetings 01:51:17 OK, back to testing the webcam. 01:52:06 ok folks, our next meeting is 20 April 2017 same time.... 01:52:13 thank you all for coming 01:52:29 aye 01:52:38 good night 01:52:41 thanks award3535 01:52:53 #endmeeting