17:30:18 <jflory7> #startmeeting Fedora CommOps (2017-02-07) 17:30:18 <zodbot> Meeting started Tue Feb 7 17:30:18 2017 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:30:18 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:30:18 <zodbot> The meeting name has been set to 'fedora_commops_(2017-02-07)' 17:30:18 <jflory7> #meetingname commops 17:30:18 <zodbot> The meeting name has been set to 'commops' 17:30:23 <jflory7> #nick commops 17:30:27 <jflory7> #topic Agenda 17:30:32 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2017-02-07 17:30:35 <jflory7> #info (1) Roll Call / Q&A 17:30:38 <jflory7> #info (2) Announcements 17:30:42 <jflory7> #info (3) Action items from last meeting 17:30:46 <jflory7> #info (4) Tickets 17:30:52 <jflory7> #info (5) Community Blog 17:31:00 <jflory7> #info (6) Open Floor 17:31:06 <jflory7> #topic Roll Call / Q&A 17:31:12 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas 17:31:17 <jflory7> #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 17:31:22 <jflory7> If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask. 17:31:46 <jflory7> #info Justin W. Flory; UTC+1; CommOps, Marketing, Magazine, Diversity Team, Ambassadors, Join SIG, sysadmin-badges, and more 17:31:49 * jflory7 waves 17:32:04 <bt0> .hello bt0dotninja 17:32:05 <Rhea> .hello rhea 17:32:05 <zodbot> bt0: bt0dotninja 'Alberto Rodriguez Sanchez' <hotgalan@gmail.com> 17:32:08 <zodbot> Rhea: rhea 'Radka Janek' <radka.janek@redhat.com> 17:32:09 <Rhea> #info Radka Janek; UTC+1; CommOps, Diversity, DotNet,... 17:32:16 <Rhea> =) 17:32:33 <bt0> #info Alberto Rodriguez;UTC-6;Commops, Dotnet, Infra 17:32:43 <jflory7> #chair Rhea bt0 17:32:43 <zodbot> Current chairs: Rhea bt0 jflory7 17:32:51 <jflory7> Hiya, bt0 and Rhea! :) 17:32:56 <bt0> o/ 17:33:10 <jflory7> We'll wait a few more minutes for more folks, and for me to grab CommBlog metrics... :D 17:33:29 <bt0> ok :) 17:33:59 <shantorn> o/ 17:34:07 <jflory7> shantorn: Greetings! 17:34:11 <jflory7> #chair shantorn 17:34:11 <zodbot> Current chairs: Rhea bt0 jflory7 shantorn 17:34:12 <shantorn> good day 17:34:50 <x3mboy> .hello x3mboy 17:34:51 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com> 17:35:02 <x3mboy> Just reading today 17:35:24 <jflory7> x3mboy: No worries, welcome! 17:35:26 <jflory7> #chair x3mboy 17:35:26 <zodbot> Current chairs: Rhea bt0 jflory7 shantorn x3mboy 17:35:32 <Rhea> jflory7 are we hijacking this one for gsoc help? :D 17:35:59 <jflory7> Rhea: Not yet – think we should have more info for GSoC in the next 24 hours. Need to check in with bexelbie first. 17:36:12 * jflory7 knows a lot was discussed and done already, but needs to catch up 17:36:57 <jflory7> Okay, got everything from the CommBlog. 17:37:16 <jflory7> shantorn: Also, feel free to do your own introduction in this format: #info Name; Timezone; Sub-projects/Interest Areas 17:37:26 <jflory7> That way, it will get logged in the minutes after the meeting. :) 17:37:49 * bexelbie is lurking if needed - otherwise not reading at this time will read mintues 17:38:10 <jflory7> Okay, noted, will be cautious with pings then. :) 17:39:11 <jflory7> Alrighty, we're approaching ten minutes after start time - will go ahead and push forward, and anyone who arrives later can chime in. :) 17:39:13 <shantorn> Hi Shane here and I am in the Pacific time zone, I am new and am not on any projects yet, this is onoy my 2nd meeting and am just learning. I am interested in bringing Fedora and FOSS to kids in school and promoting to to the teachers. 17:40:11 <jflory7> shantorn++ Awesome! I certainly hope we can help enable you to do that. If you have any questions, feel free to add in at any point during the meeting. 17:40:11 <zodbot> jflory7: Karma for shantorn changed to 2 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:40:29 <jflory7> That is also a topic I hope we can better address soon too. :) 17:40:29 <jflory7> #topic Announcements 17:40:35 <jflory7> #info === "Submissions now open for the Fedora 26 supplemental wallpapers" === 17:40:40 <jflory7> #link https://fedoramagazine.org/give-fedora-26-a-nice-look-contribute-your-wallpaper/ 17:40:44 <jflory7> #info The submission window for Fedora 26 wallpapers is now open. Contributors can submit wallpapers to be voted on for the supplemental wallpaper package in Fedora 26. 17:40:49 <jflory7> #info === "Find Fedora at FOSDEM 2017!" === 17:40:54 <jflory7> #link https://fedoramagazine.org/find-fedora-at-fosdem-2017/ 17:40:58 <jflory7> #link https://communityblog.fedoraproject.org/fedora-speakers-at-fosdem-2017/ 17:41:05 <jflory7> #info This past weekend, Fedora participated with a community stand at FOSDEM, one of the largest open source conferences in Europe. Once we have some time, it would be helpful to try to analyze our impact at this event, both from a statistic point of view but also on feedback received. 17:41:12 <jflory7> #info === "Ambassadors LATAM: Year in Review" === 17:41:16 <jflory7> #link https://communityblog.fedoraproject.org/ambassadors-latam-year-in-review/ 17:41:22 <jflory7> #info The Ambassadors of the LATAM region put together a "Year in Review" post summarizing their past year and identifying a few goals that they would like to continue focusing on for 2017. You can read more on the Community Blog. 17:41:29 <jflory7> #info === Fedora 26 proposed changes close on Feb. 28th === 17:41:35 <jflory7> #info On February 28th, the window for proposed changes to include in Fedora 26 closes. From there, we will have a confirmed idea of what kind of new changes will be included in the distribution. The Marketing team will work on identifying these changes, breaking them down into talking points, and sharing them with the project. CommOps will be able to assist by helping share and communicate these changes with other groups in Fedora as well. 17:41:37 <jflory7> <eof> 17:41:56 <jflory7> Anyone else have anything else to add in for announcements? (Will give a minute for reading through all of this.) 17:43:30 <jflory7> Announcements, going once... 17:43:40 <jflory7> Going twice... 17:43:45 <jflory7> Going thrice... 17:43:52 <jflory7> #topic Action items from last meeting 17:43:56 <jflory7> #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-01-24-17.29.html 17:44:02 <jflory7> #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward. 17:44:03 <Rhea> i'll add a smile to it 17:44:05 <Rhea> =] 17:44:08 <jflory7> #info === [COMPLETE] jflory7 Work with Rhea on adding her as a subreddit mod (due:2017-01-25) === 17:44:13 <jflory7> #link https://www.reddit.com/r/Fedora/ 17:44:19 <jflory7> #info === [COMPLETE] bt0 Verify the accuracy of the current list of Fedora speakers attending FOSDEM (due: 2017-01-25) === 17:44:24 <jflory7> #link https://communityblog.fedoraproject.org/fedora-speakers-at-fosdem-2017/ 17:44:29 <jflory7> #info === [COMPLETE] dhanesh95 Put a call out on the devel mailing list asking for any Fedorans speaking at FOSDEM to please check if their name is added to our list so that they are covered in a later post on the Fedora Magazine (due: 2017-01-26/27) === 17:44:34 <bt0> :] 17:44:34 <jflory7> #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MOVWJICOUKZOJIYINVZOFCDY5U43XG57/ 17:44:38 <jflory7> #info === [COMPLETE] jflory7 Write article introducing Fedora speakers at FOSDEM on Tue., Jan. 31, publish on Wednesday or Thursday before FOSDEM (due: 2017-01-31) === 17:44:43 <jflory7> #link https://fedoramagazine.org/find-fedora-at-fosdem-2017/ 17:44:49 <jflory7> #info === [COMPLETE] dhanesh95 File a new ticket in the FESCo Trac/Pagure requesting more information to the wiki page about their responsibilities and common tasks (bullet points are great, but if they have time, longer descriptions would help too) (due: 2017-01-29) === 17:44:54 <jflory7> #link https://pagure.io/fesco/issue/1653 17:44:59 <jflory7> #info === [COMPLETE] cprofitt Work on pulling feedback and ideas mentioned in Ticket #90 into smaller, more achievable items, either as bullets in a ticket comment on #90 or as new tickets (due: 2017-01-31) === 17:45:03 <jflory7> #link https://pagure.io/fedora-commops/issue/102 17:45:08 <jflory7> #link https://pagure.io/fedora-commops/issue/103 17:45:13 <jflory7> #info === [COMPLETE] jflory7 File a new ticket to discuss the idea of reviving Fedora Classroom more in depth === 17:45:17 <jflory7> #link https://pagure.io/fedora-join/Fedora-Join/issue/22 17:45:22 <jflory7> #info AWESOME! No pending action items from last meeting. Nice work everyone!! 17:45:25 <jflory7> commops++ 17:45:33 <bt0> awesome 17:45:43 <jflory7> Seriously, kudos to you all! 17:46:08 <jflory7> Since there's nothing left to really cover here, will just continue to next section of meeting... 17:46:10 <jflory7> #topic Tickets 17:46:16 <jflory7> #link https://pagure.io/fedora-commops/issues?tags=meeting 17:46:52 <jflory7> As reference, since some folks are still traveling or getting settled, I kept the agenda a little lighter than normal and just focused on elections. Next week's agenda will probably be a little more full. 17:46:58 <jflory7> #info === Ticket #102: "Improving Fedora Elections Process: Nomination process" === 17:47:03 <jflory7> #link https://pagure.io/fedora-commops/issue/102 17:47:09 * jflory7 takes a minute to fully read through this one 17:48:14 <jflory7> Okay, I think splitting #90 down into this ticket (and the next one) will be helpful for us to focus in on specific ideas for improving the election process... 17:48:43 <jflory7> FranciscoD: Happen to be around, by chance? 17:49:11 <jflory7> I'll give some additional background to understanding the needs of this ticket: 17:49:24 <shantorn> please 17:49:34 * FranciscoD peeps in 17:49:44 <shantorn> o/ 17:49:47 <FranciscoD> hello :) 17:50:37 <jflory7> #info Past and current "election wranglers" of Fedora identified that the nomination process sometimes faces issues. The biggest problem was consistently communicating with the public and also nominees. The public should know with enough time to cast nominations for positions up for election. After, nominees receive updates about the campaign process. This has always been done manually. 17:50:59 * Rhea waves 17:51:26 <jflory7> #info Additionally, another issue is finding out what teams wish to hold elections. Normally it is consistent, but sometimes, edge cases happen where a team that doesn't normally hold elections decides to hold them. This happened recently with the Fedora Ambassador Steering Committee holding their elections. 17:51:50 <jflory7> FranciscoD: As a former election wrangler, I was hoping you might have some insight or pointers for what we can do to try to improve the nomination process for elections. 17:52:17 <jflory7> FranciscoD: As an additional context for you, we took the really big "improve Fedora elections" ticket and tried breaking it into smaller sub-topics for us to address. 17:52:27 <FranciscoD> ++ 17:52:54 <FranciscoD> I just had trouble with co-ordinating the questionnnaire etc. and making sure they were all published at the same time 17:53:05 <FranciscoD> I think you folks managed it really well this year with the magazine posts 17:53:24 <jflory7> The overall "theme" of this ticket, to me, seems to be automation. It would be helpful if the election wrangler didn't have to manually remember these things, because when we forget to communicate, it has a notable impact on participation. 17:53:31 <FranciscoD> But that's after nominations, isn't it? 17:53:39 <FranciscoD> jflory7: ++ 17:54:01 <jflory7> FranciscoD: I do think we did well with communicating the nomination process. However, questionnaire engagement could have been better. Would you consider the questionnaire as part of the nomination process, or uniquely separate? 17:54:09 * jflory7 personally feels like they kind of go hand-in-hand 17:54:23 <FranciscoD> Yea, but we still collect nominations on the wiki, don't we? 17:54:34 <jflory7> FranciscoD: Currently, yes. 17:55:12 <FranciscoD> Ideally, the election app should have a view where people can nominate folks. And once the nominated party confirms, the election tool should handle the questions and all that. 17:55:35 * jflory7 nods 17:55:41 <FranciscoD> Our election app only fulfils the purpose of noting votes at the mo 17:55:55 <FranciscoD> This is just something I had thought of back then, but of course, this requires some development effort 17:56:01 <jflory7> #idea Filing upstream tickets for long-term improvement to the voting application to handle (1) nominations, and (2) questionnaire submissions 17:56:03 <FranciscoD> Probably why it hasn't been done yet :) 17:56:42 <jflory7> I think that would be best, to try removing it from the wiki. The wiki is not exactly a friendly place for this kind of engagement, I think. 17:56:54 <FranciscoD> ideally, it should handle the complete process from start to finish. That way, we have one central place for elections. Folks don't need to go to the wiki + magazine/commblog + announcements + voting app - all different places 17:56:56 * bt0 agree 17:57:12 * FranciscoD goes to check if there is an open source app of the source already available 17:57:21 <jflory7> FranciscoD: Of the Election app? 17:57:30 <jflory7> #link https://github.com/fedora-infra/elections 17:57:49 <FranciscoD> er s/source/election thingy/ 17:58:00 <jflory7> ryanlerch has been working on a UI redesign, but not sure if that would include feature development… 17:58:24 <jflory7> Oh, huh, no issue reporting enabled there… maybe it's on Pagure? 17:58:56 <FranciscoD> worth a look: https://heliosvoting.org/ (althoug, our feature set is quite specific) 17:59:42 <FranciscoD> Not sure if it uses range voting, for example 18:01:22 * jflory7 is waiting for the site to load 18:01:55 <jflory7> Oh, hmm… interesting… 18:02:08 <jflory7> FranciscoD: Any source code for this? 18:02:16 <FranciscoD> seems to be open source 18:02:25 <FranciscoD> https://github.com/benadida/helios-server 18:02:55 <jflory7> Hmm, okay. 18:03:17 <jflory7> So perhaps best plan for now is to file upstream tickets for Fedora Elections app, although they need to migrate it to Pagure pretty soon… ;) 18:04:20 <Rhea> i can set test instance up if you want to check it out 18:05:05 <jflory7> For short-term changes we can make for the next election, I think maintaining the bar we've set for communicating election participation is a priority. I really do think we did well with the nomination process – all the electable groups had no shortage of nominees, which was fantastic considering some past cycles. 18:05:41 <jflory7> Maybe as an additional short-term goal, we can try to also better communicate the questionnaire as a resource for people to participate in the election. Maybe a good gap out from the election, like a week or two before the nominations close. 18:06:28 <jflory7> #idea Maintaining the communication bar we set for the last election: CommBlog / Magazine posts, announcement mailing list posts for nomination and voting process 18:06:54 <jflory7> #idea Short-term, trying to better communicate questionnaire as resource for people to edit / add to for nominees to answer 18:07:21 <jflory7> Rhea: For the Election app? I don't think we'll be able to migrate it without the XML_RPC permissions on Trac. I think ryanlerch or pingou have to migrate it. 18:08:02 <jflory7> I can take an action to file tickets for the features we described earlier. 18:10:12 <Rhea> i mean like to check it out if you like it 18:10:30 <Rhea> if you want to check out a few different options or whatever 18:10:45 <jflory7> #action jflory7 File feature tickets in Election app for (1) nomination of candidates, and (2) questionnaire question interaction (e.g. submitting new questions) 18:10:45 <shantorn> at some point in the near future if i could be brought up to speed as to how we last handled this process and how we expect to move forward I would appreciate that insight. Thank you 18:11:43 <jflory7> Rhea: Ohh, the Helios Voting app? I don't think we'll need one to experiment with yet. I think the focus will be on maintaining the existing app we have and making improvements to it. 18:11:56 <Rhea> ok 18:12:29 <jflory7> shantorn: Sure! I know these discussions are probably a little tough to follow without some of that past context. I think we're all good on this ticket now, so we can move to the next one, and then I can try to give you some of that context in #fedora-commops after the meeting? 18:12:43 * jflory7 is happy to have plenty of free time after meetings again for this semester 18:12:53 <jflory7> #info === Ticket #103: "Improving Fedora Elections Process: Improving Voter Participation" === 18:12:58 <jflory7> #link https://pagure.io/fedora-commops/issue/103 18:13:02 <shantorn> thank you 18:13:22 <jflory7> I'll give some background on this one too: 18:14:31 <jflory7> #info Voter participation has been a key focus point of Fedora elections. In the past, we struggled to have significant participation but it has gradually improved (with the last cycle reaching the second highest record of voter participation for some groups). For the past couple of election cycles, we have tried using some of the following methods to better engage the voting community: 18:14:52 <jflory7> #info (1) Community Blog posts for candidate interviews leading up to the election 18:15:08 <jflory7> #info (2) Posts on the announce mailing list at the start of the voting period, but also close to the end 18:15:20 <jflory7> #info (3) Using social media to promote the election window being open 18:15:40 <jflory7> #info Some of the new ideas we have had to improve voter participation are… 18:16:05 <jflory7> #info (1) A single, general post on the Fedora Magazine announcing the elections 18:16:32 <jflory7> #info (2) Having a badge for voters to receive at the end of the voting period (while keeping in mind potential privacy issues that could arise from such a badge) 18:17:06 <jflory7> #info (3) Having nominee AMAs (Ask Me Anything) hours on the Fedora subreddit, /r/Fedora (or maybe another social media platform of a candidate's choice) 18:17:40 <jflory7> #info (4) Finding ways to build automated reports of candidates for positions while keeping it general and fair to participants - this idea should be approached with caution 18:17:50 <jflory7> cprofitt++ for summing these things up in the ticket, by the way 18:18:17 <jflory7> Again, as with the previous ticket, I think maintaining the bar we had for the last couple of cycles is important. 18:18:36 <jflory7> I would really like to see more community engagement with nominees for future elections. I'm a big fan of the Reddit AMA idea. 18:19:18 <jflory7> This is also a way for users to ask questions, who might not normally get to vote. But that might be useful information or questions for people who do have the ability to vote. 18:19:41 <jflory7> Or maybe people who are on the fringe of the contributor community and don't normally participate in the election process, but might choose to this time. 18:20:29 <cprofitt> jflory7: hope that summary was good. 18:20:45 <jflory7> cprofitt: Yes, thank you :) 18:20:47 <Rhea> yup 18:21:00 <jflory7> #chair cprofitt 18:21:00 <zodbot> Current chairs: Rhea bt0 cprofitt jflory7 shantorn x3mboy 18:22:36 * jflory7 tries to think of action items to break up here, that we can then try to measure the impact of our efforts 18:22:45 <Rhea> uh 18:23:33 <jflory7> I think for the next cycle, we could perhaps try introducing the idea of holding AMAs on Reddit (or other platforms), as well as seriously consider the prospect of having a badge 18:23:45 <jflory7> In addition to maintaining everything else we have done so far. 18:24:28 <jflory7> It would also be helpful if bee2502 could perhaps run some data analysis on election participation to better understand our actions and what is most effective (e.g. did the days we post on social media make a difference?) 18:24:49 <shantorn> would telegram be a useful place to hold those? 18:25:05 <jflory7> #idea Running data analysis on past election participation data would be helpful to understand our impact (cc: bee2502?) 18:25:23 <jflory7> shantorn: Oh, actually, that makes me think… 18:25:46 <shantorn> to be honest i havent ever been to the redit area yet 18:25:57 <jflory7> shantorn: freenode uses an AMA bot for holding AMAs in IRC. It would be cool if we could maybe *run* the AMA on IRC, and then there could be a Telegram bridge bot to link to the Fedora Telegram community… 18:26:13 <shantorn> yes that would be wise 18:26:42 <shantorn> the tools are already in lace 18:26:48 <shantorn> place* 18:26:58 <jflory7> People could then participate remotely from Telegram, but… this idea would deserve some discussion with jkurik, the current election wrangler. The one argument against Telegram I see is that some people may not wish to make an account to participate, but ideally, with a Telegram bridge bot, people would participate on IRC and it's all mirrored to Telegram. 18:27:28 <jflory7> #idea Seriously investigate the idea of having a badge for voter participation (consider security concerns!) 18:27:41 <shantorn> it would cover 2 platfowm instead of forcing to platform user to go to a 3 rd one 18:28:13 <jflory7> #idea Holding AMA on IRC (a la freenode AMA style) and syncing traffic in IRC channels to Telegram to promote participation and awareness of the election process (needs discussion with jkurik) 18:28:21 <jflory7> shantorn: Right. 18:28:46 <jflory7> I'll add this idea as a comment in the ticket and see if we can get jkurik to check it out. His insight here would also be helpful, but I think our meeting times are after he leaves the office for the day. 18:29:11 <jflory7> #action jflory7 Summarize this discussion into the ticket, try to get opinion of jkurik (and also bee2502 for metrics) in the ticket 18:29:35 <jflory7> shantorn++ I do think it would boost participation significantly if we could tap into the large Telegram community we have for Fedora 18:29:53 <Rhea> hmm 18:29:55 <bt0> shantorn++ 18:29:55 <zodbot> bt0: Karma for shantorn changed to 3 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:29:56 <shantorn> i so agree, i saw 715 members yesterday 18:29:56 <jflory7> Anyways… I think this should suffice for now, until we get feedback from jkurik... 18:30:11 <shantorn> ok 18:30:25 <jflory7> Anything else we want to add into this ticket discussion for now? 18:30:35 <jflory7> Going once... 18:30:38 <Rhea> o.o 18:30:40 <Rhea> nop 18:30:45 <jflory7> Going twice... 18:30:50 <jflory7> Going thrice... 18:30:58 <jflory7> #topic Community Blog 18:31:06 <jflory7> #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go! 18:31:13 <jflory7> #info === This Week in CommBlog === 18:31:18 <jflory7> #info (1) "FOSS Wave: FOSS Camp SJCE in Mysore" - sumantrom 18:31:23 <jflory7> #link https://communityblog.fedoraproject.org/foss-wave-foss-camp-sjce-mysore/ 18:31:28 <jflory7> #info Total Views (Feb. 2 - Feb. 7): 75 18:31:34 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3360 18:31:40 <jflory7> #info (2) "Fedora speakers at FOSDEM 2017" - jflory7 18:31:45 <jflory7> #link https://communityblog.fedoraproject.org/fedora-speakers-at-fosdem-2017/ 18:31:49 <jflory7> #info Total Views (Feb. 3 - Feb. 7): 67 18:31:55 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3388 18:32:01 <jflory7> #info (3) "Ambassadors LATAM: Year in Review" - williamjmoreno++ 18:32:07 <jflory7> #link https://communityblog.fedoraproject.org/ambassadors-latam-year-in-review/ 18:32:11 <jflory7> #info Total Views (Feb. 7): 18 18:32:17 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=3344 18:32:23 <jflory7> #info === Coming Up in CommBlog === 18:32:29 <jflory7> #info (1) "Earn Fedora Badges designing Badges!" - riecatnor 18:32:35 <jflory7> #link https://communityblog.fedoraproject.org/?p=3352&preview=1&_ppp=cd7e700f87 18:32:40 <jflory7> #info (2) "TAFFY - Tucson Arizona Fedora Fanatic Yeasayers" 18:32:45 <jflory7> #link https://communityblog.fedoraproject.org/?p=3390&preview=1&_ppp=9873414378 18:32:48 <jflory7> <eof> 18:33:05 <jflory7> That's all the CommBlog content I have… I'll need to check out the TAFFY one, that seems new to me. 18:33:48 <jflory7> #topic Open Floor 18:34:17 <jflory7> Anyone have anything they'd like to add? Or have any questions about anything? 18:34:29 <Rhea> hmm 18:34:43 * jflory7 knows this week has been a bit drowsy because some folks have been traveling, but jflory7 anticipates a busier week next week. :) 18:34:53 <shantorn> not for meeting specific, i have asome commops questions for non meeting 18:35:38 <jflory7> shantorn: Sure! We can answer those in #fedora-commops after the meeting then. :) 18:35:46 <jflory7> In that case… open floor, going once... 18:35:56 <Rhea> thanks Justin... 18:35:59 <shantorn> great,! 18:36:00 <jflory7> Going twice... 18:36:05 <jflory7> Going thrice... 18:36:19 <jflory7> Thanks everyone for coming out today! See you around in channel, on the list, or next week… 18:36:23 <jflory7> #endmeeting