20:55:22 #startmeeting Fedora Marketing meeting (2016-05-25) 20:55:22 Meeting started Wed May 25 20:55:22 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:55:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:55:22 The meeting name has been set to 'fedora_marketing_meeting_(2016-05-25)' 20:55:25 #meetingname marketing 20:55:25 The meeting name has been set to 'marketing' 20:55:30 #topic Roll Call 20:55:37 #info Name; Timezone; Other sub-projects / interest areas 20:55:43 .hello nb 20:55:43 nb: nb 'Nick Bebout' 20:56:01 #info Justin W. Flory; UTC-4; Marketing / Magazine, CommOps, Ambassadors, Diversity, and more 20:56:03 #chair nb 20:56:03 Current chairs: jflory7 nb 20:56:05 Evening! 20:56:23 Good afternoon 20:56:44 #info James Bishop; UTC-3 20:56:45 * mailga is here 20:56:54 #chair jbishop mailga 20:56:54 Current chairs: jbishop jflory7 mailga nb 20:57:40 As usual, we'll wait until about five after the hour before getting started. 20:57:50 Here is the agenda one more time if you didn't catch it: https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2016-05-25 21:03:27 .hellomynameis jzb 21:03:28 jzb: jzb 'Joe Brockmeier' 21:03:31 #chair jzb 21:03:31 Current chairs: jbishop jflory7 jzb mailga nb 21:03:40 I'm here, but only briefly. 21:03:43 * jflory7 nods 21:04:00 I think we might as well go ahead and begin with the agenda, then. 21:04:15 .hello decause 21:04:16 decause: decause 'Remy DeCausemaker' 21:04:19 #chair decause 21:04:19 Current chairs: decause jbishop jflory7 jzb mailga nb 21:04:23 * decause was in the other channel :P 21:04:31 Let's hit announcements. 21:04:34 Heh, no worries decause :) 21:04:40 #topic Announcements 21:04:45 #info decause; UTC-4; CommOps, Council, Bugget, GSoC, Flock, * 21:04:48 #info === "Flock 2016 schedule is now out" === 21:04:52 #link https://fedoramagazine.org/flock-2016-schedule-now/ 21:04:58 #info Flock is Fedora's annual contributor conference where Fedorans across the world get together for talks, sprints, workshops, and more. The schedule for this year's Flock was recently published and you can find out what talks and workshops there will be for this year. stickster is giving a talk about the Magazine this year!! 21:05:03 #info === Fedora @ PyCon US === 21:05:15 #info There will be Fedora sprints at PyCon this year. They're from Thursday, 2016-06-02 to Sunday, 2016-06-05. The brochures will also be making it out here! 21:05:20 #info === "Fedora 24: Let’s have a party!" === 21:05:24 #link https://communityblog.fedoraproject.org/fedora-24-have-a-party/ 21:05:30 #info The Ambassadors are getting ready to organize release parties in their regions for Fedora 24. If there's any resources worth sharing, now would be the time to begin spreading the word about them. 21:05:31 eof 21:05:37 Anyone else have anything they want to add in? 21:05:54 nope 21:05:59 Going once... 21:06:04 Twice... 21:06:14 And thrice... 21:06:17 * decause is good 21:06:23 #topic Action items from last meetings 21:06:28 #link https://meetbot.fedoraproject.org/fedora-meeting-1/2016-05-18/marketing.2016-05-18-20.55.html 21:06:32 #info === [INCOMPLETE] jflory7 Open discussion on Marketing mailing list about needs for password storage and distribution to pass on to Infrastructure team based on feedback from Infra team about what we need === 21:06:36 #action jflory7 Open discussion on Marketing mailing list about needs for password storage and distribution to pass on to Infrastructure team based on feedback from Infra team about what we need 21:06:41 #info === [COMPLETE] jbishop / jflory7 Post to the Ambassador list (with jflory7 if needed) and council-discuss list introducing Affiliate program concept and asking for input / feedback === 21:06:45 #link https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/thread/YGRG7JRTDOTNOKASW3PP7OJOFEEBRLQL/ 21:06:54 #info === [IN PROGRESS] decause Reach out to Docs team and get their input on the Marketing task pipeline === 21:06:56 #action decause Visit Docs Team Office Hours about finding ways to improve the Marketing task pipeline 21:07:02 #info === [COMPLETE] jflory7 Close Ticket #219, everything needed is complete! Take churchyard's feedback into Design ticket for updating for later prints (just one or two minor typos) === 21:07:07 #link https://fedorahosted.org/marketing-team/ticket/219#comment:41 21:07:14 #info === [COMPLETE] jflory7 File a Marketing Trac ticket for the F24 final release announcement === 21:07:19 #link https://fedorahosted.org/marketing-team/ticket/227 21:07:24 #info === [COMPLETE] jflory7 Create a ticket for screenshots in F24, CC mailga, decause, cprofitt === 21:07:28 #link https://fedorahosted.org/marketing-team/ticket/226 21:07:33 #info === decause ask council about objective co-ownership === 21:07:39 Any updates on this one, decause? 21:07:56 jflory7: we did a subproject report, should probably open a ticket 21:08:03 * jflory7 nods 21:08:06 for next time 21:08:16 Is this a Marketing ticket or Council ticket? 21:08:19 #action decause open a ticket on council track for Python Marketing Objective request 21:08:22 * jflory7 nods 21:08:24 Excellent. 21:08:31 Alright, that's all of last week's action items! 21:08:36 anyone can open it, just assign it to me to pitch 21:08:46 on the ball mktg! 21:08:48 decause, brining python brochures/stickers to self? 21:08:50 Acknowledged. 21:08:55 nb: yes, def 21:08:57 #topic Tickets 21:09:02 #link https://fedorahosted.org/marketing-team/report/12 21:09:04 Lots of tickets tonight. 21:09:11 Since jzb is here, I'm going to skip to a big one 21:09:14 #action decause bring "Fedora <3 Python" Stickers and brochures to SELF 21:09:18 #info === Ticket #227 === 21:09:22 #link https://fedorahosted.org/marketing-team/ticket/227 21:09:27 #info "Create the release announcement for Fedora 24" 21:09:31 It's that time of year! We need to begin discussing the release announcement and how we want to shape it this year. There were some concerns about how to do so for Fedora 23, but we ran out of time to make those discussions into something tangible. Now, we have some extra time to plan this out. Please review the ticket briefly, and let's move discussion here to the meeting about how to proceed. 21:09:44 nod nod nod 21:09:59 Please take a minute to read the ticket and let's discuss back here after. 21:10:12 #idea Fork the GA F23 wiki page now if we haven't already 21:10:12 The main idea I think mattdm was aiming for was the storytelling aspect with the release announcement 21:10:27 That's definitely a good action item for soon 21:10:53 I think we should just fork immediately 21:11:08 socialize the existence, starting now 21:11:13 so 21:11:14 Doing so right now 21:11:16 decause: sure 21:11:21 and ask for input on mktg and docs lists 21:11:24 that's the big thing we need for the final release 21:11:26 is the "story" 21:11:30 we do need the overall narrative angle still though 21:11:35 jzb: nod nod nod 21:11:38 what's the what behind this release and not just a bundle of features. 21:11:46 it might be good to start that thread on marketing@ 21:11:52 tbh 21:11:56 #link https://fedoraproject.org/wiki/F24_release_announcement 21:12:04 "F24, more than a bag of bricks" 21:12:09 I'm having a hard time discerning a theme for this release other than "work continues" 21:12:10 * mailga thinks the easy way is to repeat what done in the previous announcements, but doing that we can't be distinguished from other distros. I'd like to be innovative also in this aspect. 21:12:35 also also 21:12:48 we should probably provide some kind of direction/suggestions for F25 21:12:53 w/mattdm 21:13:02 nod nod nod 21:13:22 mailga: Did you have any ideas in mind for how we could distinguish ourselves from others? 21:14:44 jflory7: I'm a writer, not able with technical stuff, so my idea is to write the story from fedora 24 started, the thoughts of the FPL, of the engineers etc... 21:14:46 other than we're much better looking as a group 21:14:57 which is a given 21:14:58 Heheh 21:15:39 mailga: I think some kind of introduction by the FPL is a good opener for a release announcement, like a personal flair to add to it 21:16:29 #idea One way to make this release announcement more unique is by telling the story from how F24 started. There could be a brief introduction / "Thoughts from the FPL" to open it. Other engineers, like FESCo, could maybe add statements about F24 to the announcement. 21:16:34 jflory7: sure thing. Maybe explaining where we wanted to go with F24 and instead where we arrived... something like that. 21:17:02 One of my big questions still is: 21:17:08 How many announcements will there be? 21:17:10 One or two? 21:17:17 And if two, how will they interact with each other? 21:17:25 IMHO one, with tchnical links 21:17:32 (two being the "story" and the other being the technical low-down) 21:17:42 (technical low-down being almost done already for F24 Beta) 21:17:48 jflory7: how do you mean? 21:18:05 we usually only write one release announcement. 21:18:32 jzb: Some of the discussion from last time, if I remember, was what kind of info is put into the release announcement. Do we have one with everything inside of it now, or is there the "promoted" one that links to a more technical one inside of it 21:18:38 I think one makes sense and is easier for us to maintain 21:18:47 But I remember this topic from last time and wanted to bring it up for clarity 21:18:53 +1 to one announce 21:19:09 So it seems like there's no disagreement on this one then as far as I can tell 21:19:09 we can point to docs teams' release notes for more techincal version? 21:19:26 decause: Actually, yeah, that's what we wanted to do before, I think 21:19:33 * jflory7 wishes he had the logs on-hand for that discussion 21:19:50 decause: that was what we intended to do last time (if I recall correctly). 21:19:52 I think that was the plan for technical details was pointing over to the release notes 21:19:55 * jflory7 nods 21:20:11 So do we want to omit the "full" technical details for this announcement then and just heavily promote the Docs? 21:20:18 +1/-1? 21:20:38 it sounds like we are entusiastically in agreement ;) 21:21:03 jflory7: I'm not sure how full full is. 21:21:07 +1 one with links to docs release notes. 21:21:23 I'm +1 to an announcement similar (but better) than prior release announcements. 21:21:40 #idea For the final announcement, we can omit the "full" technical details and point to the release notes via the Docs Team for what has changed, what's new, and anyone who is looking for the raw differences between the release 21:22:13 jzb: I guess that brings us back into the angle we're wanting to cover. 21:22:27 jzb: this one? https://fedoraproject.org/wiki/F23_Final_release_announcement?rd=F23_release_announcement 21:22:33 or before? 21:23:15 hmm 21:23:22 "service is currently unavailable." 21:23:33 Ohhhh, I think Infra just launched some maintenance 21:23:37 this is a question that we need mattdm, WG members, and maybe FESCo to help us answer. 21:23:43 [16:53:06] REMINDER: outage starting in about 8minutes. Various services will be up and down in the outage window. 21:23:45 If I could throw some input around 21:23:46 :-D 21:23:52 I think we have a strong "auth" narrative going too 21:23:52 d'oh 21:24:03 there is FreeIPA, and possibly Clevis/Tang 21:24:10 https://fedoramagazine.org/fedora-23-released/ 21:24:22 that's what I'm referring to. 21:24:40 it's not super-detailed, but hits the highlights of what should be important to _users_ 21:24:45 there is also the "wayland: Doing the same stuff, but differently without you noticing!" angle too 21:24:50 not a list of we added this thing and that thing and the other thing 21:24:59 but "we made it easier to do foo, bar, and take cat pictures." 21:25:18 It's like embroidery: 21:25:25 On the front, it all looks the same as it always has 21:25:31 .hello ardian 21:25:33 ardian_: ardian 'Ardian Haxha' 21:25:35 but on the back, it's not a nest anymore ;) 21:25:38 "in this release, your computer will no longer asplode if you click the desktop" 21:25:41 that kinda thing. 21:25:52 #chair ardian_ 21:25:52 Current chairs: ardian_ decause jbishop jflory7 jzb mailga nb 21:25:54 FYI, wiki should be back, but no promises during the outage window. ;) 21:26:00 nirik++ 21:26:02 nirik: Cheers, thanks! 21:26:03 thanks for the heads-up 21:26:05 nirik: thanks 21:27:24 jflory7: any more discussion on this? 21:27:28 I think we just need to open a ticket for the narrative specfically too on the mktg tarc 21:27:30 jzb: you don't like a short story about the F24 story? 21:27:31 trac 21:27:34 and assign it to mattdm and cc me 21:27:45 I think in the interest of time, we should come up with a few actionable items to follow up on 21:27:49 mailga: AFAIK we don't have a story, yet. 21:27:55 decause: You mean in addition to this ticket? 21:28:00 jflory7: yes 21:28:07 I'll do a short-n-sweet one now 21:28:07 a separate ticket for the narrative 21:28:09 it is a blcoker 21:28:17 so make the old ticket block on this one 21:28:37 jzb but we had any target for F24 when we started after F24. 21:28:48 sorry after F23 21:29:27 mailga: sorry? 21:30:14 I mean, there was a point where we would to be with F24, e.g. a new feature o something else. 21:30:46 #link https://fedorahosted.org/marketing-team/ticket/228 21:32:30 What actionable items can we take out of this ticket? 21:32:46 (1) decause / mattdm sync up on the announcement, (2) post ideas in ticket... ? 21:32:53 Anything else? 21:32:58 Or is this good for now? 21:33:18 jflory7: I think we should also have a thread on marketing@ 21:33:22 more brains good 21:33:39 (3) Post a thread on the Marketing list to bring some more exposure to this ticket and developing the story of F24 21:33:45 Those three items sound good? 21:33:47 I think mattdm should post his idea at first. 21:34:15 jflory7: +1 21:34:17 jflory7: +1 21:34:25 mailga: he may not have an idea :-) 21:34:38 #agreed (1) mattdm and decause will sync up about ideas and plans for the story of Fedora 24 and the announcement. (2) The ideas from this meeting will be posted in the ticket. (3) A thread will be posted to the Marketing list about the announcement. 21:34:50 I will handle (2) and (3) after this meeting 21:34:52 jflory7: I'll start the discussion now 21:34:56 jinx 21:34:59 PErfect, even better! 21:34:59 jzb: of course. 21:35:03 Go for it, I'll do the ticket. 21:35:17 #action jflory7 Add ideas to the Marketing ticket about announcement from meeting 21:35:26 #action jzb Post to the Marketing mailing list to get some more eyes on this ticket and the F24 story 21:35:30 Alright, let's hit the next ticket. 21:35:41 We're a little bit past halfway. 21:35:42 #info === Ticket #219 === 21:35:46 #link https://fedorahosted.org/marketing-team/ticket/219 21:35:53 #info "Publicizing "Fedora affiliates" (or groups using Fedora)" 21:35:54 There's been a lot of feedback added to the ticket, differing from whether this is an Ambassadors task, what the name of the program should be (and what it implies), how to keep in contact with the affiliates, and how intense the process is. Please take a minute to review the comments, and then let's discuss what the next steps and action items are. 21:36:12 Wait, this is *not* 219 21:36:17 Argh 21:36:20 #undo 21:36:20 Removing item from minutes: INFO by jflory7 at 21:35:53 : "Publicizing "Fedora affiliates" (or groups using Fedora)" 21:36:22 #undo 21:36:22 Removing item from minutes: 21:36:27 #undo 21:36:27 Removing item from minutes: INFO by jflory7 at 21:35:42 : === Ticket #219 === 21:36:46 #info === Ticket #222 === 21:36:51 #link https://fedorahosted.org/marketing-team/ticket/222 21:36:55 #info "Publicizing "Fedora affiliates" (or groups using Fedora)" 21:36:59 Same message as before. 21:37:52 Anyone know what WIIFM is an abbreviation for? 21:37:58 What's in it for me. 21:38:06 Hey, jbishop! 21:38:12 #chair jbishop 21:38:12 Current chairs: ardian_ decause jbishop jflory7 jzb mailga nb 21:38:29 ok 21:38:32 sent 21:38:36 jzb++ 21:38:37 off to food the cats 21:38:41 have a good night all 21:38:47 jbishop: Oh, whoops, you were chaired already, my mistake. 21:38:47 jzb: See ya! 21:38:52 * decause waves to jzb 21:38:55 Not a problem. :P 21:39:01 jbishop: Have you had a chance to read the feedback yet? Any thoughts on some of the ideas in the ticket? 21:39:13 I'm not native, so I'm not able to find any name, but my thought is posted in the ticket. 21:39:26 see you soon jzb 21:39:41 I think in the interest of avoiding bikeshedding, we should skip over the name until later, or at least for this meeting 21:40:01 I think a FAS group is the best way to handle issuing badges to the "affiliates" FAS accounts 21:40:03 +1 21:40:14 I have had a look at the ticket, and while I'm not really sure about who should take on the task of managing affiliates, I feel that the naming issue is valid. That said, I did like your suggestion of "Friends of Fedora" and have updated the wiki pages to reflect that. 21:40:16 Although alick does raise a good point of having some kind of process for someone to "replace" another person 21:40:28 jflory7: affiliates can be several and manage them from mktg is really hard. 21:41:06 usually mktg relationships have a designated "owner" who is the go-to for that entity 21:41:53 jbishop: The question of who should manage them is a good one, and I think that's what mailga was pointing out in this comment. We don't have to have affiliates / Friends of Fedora waiting on unanswered mails or questions for the process, so making sure we have the manpower and resources to handle this is definitely something worth considering. I could see this as a good point of collaboration between marketing and Ambassadors. 21:41:56 decause: for structured mktg, IMHO we are not structured yet. 21:42:12 jbishop: I like the idea of Friends of Fedora for now, or at least until someone says "not possible" otherwise :) 21:42:37 mailga: Could you elaborate a little on that? 21:42:37 jflory7, It is a good question, I just don't have an answer. 21:44:08 jflory7: I mean that until we are four/five people doing stuff we cannot create a organisaton chart 21:44:31 * jflory7 nods 21:44:43 That makes sense to me 21:44:58 and so if I'm the affilate manager (wrong word) to which person i can relate? 21:45:06 #idea Having this as a shared responsibility between Marketing and Ambassadors might be a good idea 21:45:27 mailga: I think that it's a 1-1 with an affiliate and someone who is responsible for mantaining that relationship 21:45:38 so, let's take RIT for example 21:45:47 RIT? 21:45:53 Rochester Institute of Technology 21:45:57 RIT is a college in NYS 21:46:04 ok 21:46:07 they have a relationship with Fedora and Sugar Labs 21:46:13 jflory is on the marketing team 21:46:36 jflory sponsors their "request" to be an afiliate, because he has an existing relationship with the organization 21:46:50 much like a new ambassador gets sponsored by a mentor 21:47:19 * jflory7 nods 21:47:23 jflory may also be the sponsor for say, spigott or some other minecraft commnity if ever someone wanted to officially get involved from another place 21:47:29 What happens in the event of a non-existing relationship? 21:47:31 decause: I think affiliates are also in their native language so they can find hard the relationship with the higher structure (mktg), maybe is better they get in touch with the regional ambassador and the the amby get in touch with mktg. 21:47:32 rather than ahve one person responsible for all the relationships 21:47:43 jflory7: someone has to approve the ticket :) 21:47:50 I see. 21:47:51 mailga: yes 21:48:17 mailga: That approach seems reasonable to me. 21:48:21 Time check, 12 minutes left. 21:48:24 we said the same thing (you in English, I... don't know) 21:48:50 #idea A potential affiliate could get in touch with an Ambassador (or vice versa) and the Ambassador can come to Marketing with the affiliate request 21:49:13 jflory7: works for me. 21:49:35 #idea An individual in Marketing / Ambassadors can "sponsor" a request based on previous relationships (example used in meeting is jflory7 with Rochester Institute of Technology in NYS (as a student), or similar type of idea) 21:49:43 Do these ideas suffice for now? 21:49:55 If so, I will add them to the ticket after the meeting and we can wait for some additional feedback. 21:49:57 Sound good? 21:50:02 jflory7: +1 21:50:10 Going once... 21:50:13 Going twice... 21:50:15 REMINDER 21:50:20 +1 21:50:21 FICloud maintenance tonight at 02:00 21:50:24 Going thrice... 21:50:33 puiterwijk++ 21:50:47 #action jflory7 Update ticket #222 with ideas from meeting 21:50:59 #info === Ticket #225 === 21:51:03 #link https://fedorahosted.org/marketing-team/ticket/225 21:51:07 #info "Transition to FOSCo - Nomination of the marketing coordinator" 21:51:10 FOSCo (Fedora Outreach Steering Committee) is planned to be the future replacement for FAmSCo (Fedora Ambassador Steering Committee). FOSCo would have more participation and involvement from multiple areas of the project. mailga nominated jflory7 as the representative for the Marketing sub-project and wanted other members of the Marketing team to review the nomination. 21:51:20 mailga: Sound good? 21:51:26 +1 from me :-D 21:51:33 Excellent! 21:52:02 mailga: I feel like a post to the Marketing list about this one as well would be a good idea. 21:52:17 To make sure anyone who wishes to have a voice in this has chance to review the ticket and nomination, or ask questions if needed. 21:52:19 FOSCo will coordinate the outreach area of the Project. 21:53:00 jflory7: I'll take care to send a mail mail in ML (tomorrow), is it good? 21:53:17 mailga: I think that's the best action item for now, if nobody in the meeting has any questions or thoughts to add in. 21:53:25 * decause is +1 21:53:39 #action mailga Send a mail to the Marketing list 2016-05-26 about jflory7's nomination for the FOSCo Marketing seat 21:53:45 jflory7: just a clarification. 21:53:55 Sure, what's up? 21:54:02 there's nothing to do as far, 21:54:35 we only want one coordinator from each group interested to be part of FOSCo 21:55:02 * jflory7 nods 21:55:10 So we're looking for +1/-1 on the ticket, correct? 21:55:34 And might be good to mention this is for a future seat at the moment and that it is something in progress for the near future 21:55:38 jflory7: yes. Or other self-nominations. 21:55:41 * jflory7 nods 21:55:49 I think that's fair. 21:55:57 Tehre's another question 21:56:33 we still don't know if magazine should be considerated apart from mktg (IMHO no). 21:57:04 I think the Magazine is best tied to Marketing for now, until it becomes a larger entity with its own significant group of individual contributors. 21:57:17 #agreed mailga's email will mention that this nomination is for a future seat, that +1/-1s are needed, and ask for other self-nominations 21:57:36 Okay, last ticket, which mailga might be able to add some info too :) 21:57:42 * jflory7 knows it's super late for mailga right now 21:57:48 #info === Ticket #226 === 21:57:53 #link https://fedorahosted.org/marketing-team/ticket/226 21:57:56 #info "Screenshots for Fedora 24" 21:57:59 Screenshots for F24 are listed as an action item for the release cycle around now. We opened the ticket to see what needs to be completed, where the screenshots will be used, etc. If mailga is around, he may be able to advise on this, but if not, any other Marketing member who knows about the process may be able to add more context here. If not, we should skip for now and come back once mailga or another Marketing member is able to add more 21:57:59 info to the ticket. 21:58:17 We might be able to figure out some action items on this one tonight. :) 21:58:57 I posted my comment in the ticket. Not too much to say. Be careful with the last adjustements before the release. 21:59:36 * jflory7 refreshes page 22:00:13 mailga: Do we need to do "full" screenshots of everything, or do we only want to highlight new things? 22:00:24 This time I'm not able to take care of the ticket. 22:00:26 e.g. desktop wallpapers, any new apps or improved features that are visually obvious, etc. 22:00:41 mailga: cprofitt mentioned he was interested in helping with screenshots, so he might be able to lend a hand. 22:00:50 If not, we might see if some Ambassadors want to assist with this. 22:01:25 I don't have the network speeds or bandwidth to download all of the ISOs in a reasonable time anymore, heh 22:01:45 #idea cprofitt might be able to assist with gathering some screenshots. 22:01:58 I choose some common features and made screenshot with there features for each DM. If you pay attention you'll see the same application opened. In a case or two some features are different. 22:02:04 #idea The Ambassadors might be willing to assist with gathering more screenshots too. 22:02:30 #idea For screenshots, use common features and make screenshots with their features for each environment. Sometimes small changes are visible between releases. 22:02:32 mailga++ 22:02:39 Awesome, I think this is enough to go off for now. 22:02:53 Anything else for this ticket? 22:03:00 * jflory7 notes we're a few minutes over 22:03:18 Going once... 22:03:23 Twice... 22:03:28 Thrice... 22:03:35 #topic Upcoming Tasks 22:03:39 #link https://fedorapeople.org/groups/schedule/f-24/f-24-marketing-tasks.html 22:03:44 #info (1) Email WGs to solicit bullet points for GA release announcement (starting: Mon 2016-05-23) 22:03:50 #info (2) Marketing: Final Screen Shots (starting: Tue 2016-05-24) 22:03:54 #info (3) Brief news distribution network (starting: Tue 2016-05-24) 22:03:59 #info (4) Monitor news sites to provide corrections & info (starting: Tue 2016-05-24) 22:04:04 #info (5) Create GA Announcement (Docs & Marketing) (starting: Tue 2016-05-31) 22:04:18 * jflory7 notes that most of these items have been covered in tickets or are related to pre-existing tickets as of today 22:04:25 #topic Open Floor 22:04:34 Alrighty. Anything else we want to mention or cover tonight? 22:04:55 * decause is good 22:05:22 I'm ok as well 22:06:03 Okay, I think we're all good to close up this evening, then! 22:06:15 Thanks for coming out tonight, all. Enjoy the rest of your evenings... 22:06:19 #endmeeting