11:58:30 <jflory7> #startmeeting Fedora Diversity Team - 2016 Sept. 21
11:58:30 <zodbot> Meeting started Wed Sep 21 11:58:30 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
11:58:30 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
11:58:30 <zodbot> The meeting name has been set to 'fedora_diversity_team_-_2016_sept._21'
11:58:35 <jflory7> #meetingname diversity
11:58:35 <zodbot> The meeting name has been set to 'diversity'
11:58:45 <jflory7> #topic Roll Call / Q&A
12:02:21 <devyani7> .hello devyani7
12:02:21 <zodbot> devyani7: devyani7 'Devyani Kota' <devyanikota@gmail.com>
12:02:46 <marinaz> .hello marinaz
12:02:47 <zodbot> marinaz: marinaz 'Marina Zhurakhinskaya' <marinaz@redhat.com>
12:04:19 <jflory7> Hiya, devyani7 and marinaz :)
12:04:23 <jflory7> #chair devyani7 marinaz
12:04:23 <zodbot> Current chairs: devyani7 jflory7 marinaz
12:04:34 <devyani7> jflory7: o/
12:05:04 <jflory7> Hopefully a few more should pop in soon. :)
12:05:10 <marinaz> hi devyani7 and jflory7!
12:05:22 <devyani7> marinaz: hello :)
12:06:53 <a2batic> .hello a2batic
12:06:54 <zodbot> a2batic: a2batic 'Kanika Murarka' <kmurarka@redhat.com>
12:07:11 <jflory7> #chair a2batic
12:07:11 <zodbot> Current chairs: a2batic devyani7 jflory7 marinaz
12:07:13 <jflory7> Hiya, a2batic!
12:07:25 <jflory7> Alrighty. We'll go ahead and get started now, hopefully some more people should float in as we go. :)
12:07:30 <jflory7> #topic Announcements
12:07:38 <a2batic> jflory7, o/
12:07:42 <jflory7> #info === "What is the Fedora Code of Conduct?" ===
12:07:47 <jflory7> #link https://communityblog.fedoraproject.org/what-is-fedora-code-conduct/
12:07:58 * devyani7 clicks
12:08:37 <jflory7> #info Amita wrote a brief introduction to the Fedora Code of Conduct for the Community Blog. The post is intended to be a brief introduction to the code of conduct and why it exists.
12:09:28 <jflory7> Since it's tentative right now, I won't put it in #info, but we're looking at doing a hack session for the FAD planning on Friday.
12:09:42 <Amita> hi
12:09:46 <devyani7> Amita++
12:09:53 <jflory7> Specific time is yet to be decided, but in the range of 04:00 UTC to 09:30 UTC.
12:09:57 <jflory7> #chair Amita
12:09:57 <zodbot> Current chairs: Amita a2batic devyani7 jflory7 marinaz
12:10:07 <tatica> moin!
12:10:10 <a2batic> amsharma++
12:10:11 <tatica> .hello tatica
12:10:11 <jflory7> Hi Amita!
12:10:12 <zodbot> tatica: tatica 'Maria Gracia Leandro Lombardo' <tatadbb@gmail.com>
12:10:16 <jflory7> Hi tatica!
12:10:17 <Amita> hello jflory7
12:10:19 <jflory7> #chair tatica
12:10:19 <zodbot> Current chairs: Amita a2batic devyani7 jflory7 marinaz tatica
12:10:29 <devyani7> tatica: morning :)
12:10:37 <tatica> moin! breakfast almost in time!
12:10:57 <Amita> hello tatica a2batic devyani7 and marinaz
12:11:07 <jflory7> tatica: Just briefly mentioned Amita's post on the CoC on the CommBlog, and then the (tentative) hack session on Friday morning.
12:11:18 <marinaz> hello Amita, tatica, a2batic!
12:11:26 * jflory7 doesn't have any other announcements than those
12:11:56 <Amita> jflory7, you may want to announce about hack session?
12:12:03 <Amita> oh you did, sorry
12:12:06 <jflory7> :)
12:12:13 <Amita> you are always ahead :)
12:12:19 <tatica> I like the hack session timing
12:12:31 <jflory7> tatica: Heh, yeah...
12:12:31 <tatica> since on saturday they will remove the stitches to the doggie
12:12:42 <jflory7> tatica: I'm only awake then because I'm catching a flight...
12:12:43 <Amita> good
12:12:47 <jflory7> Wait, you will be up that early???
12:12:56 <Amita> tatica, is crazy in doing that
12:13:13 <tatica> yeah, no problem, just let me know the time and I'll be there
12:13:29 <tatica> as I told you before, for me is easier super early than afternoon, since I usually run errands or so after work
12:14:01 <Amita> but how do you work when you wake up in the night
12:14:03 <jflory7> tatica: For us, it's anywhere in the range of midnight to 5:30am so far. I think we can probably decide something in a bit. We can revisit a specific time when we get to talking about the FAD ticket.
12:14:08 <Amita> I mean for me it is very disturbing
12:14:25 <jflory7> We can cover previous action items from last week's meeting for follow-up.
12:14:44 <tatica> that works for me, no problem at all
12:14:51 <jflory7> #topic Action items from last week
12:15:00 <jflory7> #link https://meetbot.fedoraproject.org/teams/diversity/diversity.2016-09-14-11.59.html
12:15:04 <tatica> I also saw the outrech initiative on the maillist, any candidate?
12:15:27 <jflory7> #info === [COMPLETE] jonatoni Share any info you learned about venue options in Brno in the ticket for the FAD planning ===
12:15:29 <jflory7> #link https://pagure.io/fedora-diversity/issue/8#comment-6334
12:15:36 <jflory7> jonatoni++ lots of good info there. :)
12:15:51 <a2batic> tatica, I am thinking of applying :)
12:15:54 <jflory7> tatica: I don't think so yet, but there's still a fair amount of time until a candidate is selected (early October, I think).
12:16:04 <jflory7> a2batic++
12:16:04 <Amita> jonatoni++
12:16:04 <zodbot> Amita: Karma for jonatoni changed to 6 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
12:16:13 <tatica> a2batic, great!!!
12:16:32 <a2batic> jonatoni++
12:16:32 <Amita> a2batic++
12:16:32 <zodbot> a2batic: Karma for jonatoni changed to 7 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
12:16:39 <Amita> go for it a2batic
12:16:44 <jflory7> #info === [IN PROGRESS] jflory7 Amita Work on defining planned impact / scope of the FAD ===
12:16:56 <jflory7> #info Will revisit this in our hack session on Friday / weekend!
12:17:08 <Amita> +1 yeah we need to
12:17:10 <jflory7> #action diversity_team Work on defining planned impact / scope of the FAD
12:17:13 <jflory7> #nick diversity_team
12:17:14 <devyani7> a2batic++ awesome :)
12:17:24 <jflory7> #info === a2batic Amita tatica marinaz Begin working on initial structure / format of the panel and what content to deliver for FUDCon diversity panel ===
12:17:34 * jflory7 saw some activity on the list about this... needs to catch up!
12:17:52 <Amita> I am not going to FUDCon this time, can't travel
12:18:04 <Amita> so a2batic will take the lead this time :)
12:18:16 <Amita> I am helping her out
12:18:19 * jflory7 nods
12:18:36 <jflory7> Okay, I see. We'll have to catch you at the FAD, then, Amita. :)
12:18:49 <Amita> It will be great if someone knows the mailing list for FUDCon organizers
12:18:54 <jflory7> a2batic: We're all happy to help here too :)
12:18:57 <Amita> jflory7, Sure
12:19:00 * devyani7 thinks she also raised her hand for the diversity panel :/
12:19:01 <a2batic> I saw the follow up mail from Amita , I will be going through the links and come out with the final abstract soon
12:19:08 <marinaz> I added a comment with some feedback to the ticket (similar to what I shared in the last meeting)
12:19:19 <Amita> devyani7, you also dear, we need more people
12:19:24 <devyani7> :P
12:19:33 <Amita> marinaz, yeah that is helpful, thanks
12:19:39 <jflory7> Amita: This came up in another thread on the Ambassadors list, I'm not sure where the list or organizational discussion for FUDCon is taking place.
12:19:40 <devyani7> oh, okay. i thought justin missed !
12:19:49 <devyani7> :P
12:20:00 <jflory7> devyani7: Ahh, was my mistake - I guess it didn't make it into the minutes!
12:20:04 <Amita> jflory7, Bex agreed to join in which is great
12:20:10 <jflory7> Okay, so, it seems like you're all pretty active on this one.
12:20:11 <devyani7> no worries :)
12:20:17 <jflory7> I also saw marinaz's feedback in the ticket too
12:20:18 <a2batic> marinaz, that youtube example was very nice :)
12:20:19 <Amita> I hope more people like Bex can join in
12:20:27 <jflory7> So I will reaction this for follow-up again next week.
12:20:35 <marinaz> a2batic: glad you liked it :)!
12:20:37 <jflory7> Amita: That's awesome to hear he's on board!
12:20:55 <Amita> #info we have a2batic devyani7 bexelbie will join in the panel
12:21:08 <jflory7> #action a2batic Amita tatica devyani7 marinaz Continue working on initial structure / format of the panel and what content to deliver for FUDCon diversity panel, follow up again next week
12:21:16 <tatica> aye
12:21:23 <devyani7> roger !
12:21:24 <Amita> #action a2batic devyani7 need to find out the FUDCon orgaizer list
12:21:34 <jflory7> #info === tatica Give the onboarding process (ticket #2) a final review; if it looks good, it can be closed! ===
12:21:36 * a2batic nods
12:21:50 <jflory7> ^^ this one is on the agenda today, so we can take a peek at it in a bit too
12:22:14 <jflory7> #info Will look at during today's meeting quickly
12:22:32 <jflory7> #info === [COMPLETE] jflory7 Close ticket #13 as complete ===
12:22:45 <tatica> I will work today n ticket 2
12:22:48 <jflory7> Okay, and that's all last week's action items. To the real stuff now! :P
12:22:52 <jflory7> #topic Tickets
12:22:58 <jflory7> #link https://pagure.io/fedora-diversity/issues?status=Open&tags=meeting
12:23:16 <jflory7> #info === Ticket #8 ===
12:23:22 <jflory7> #info "Planning a FAD event"
12:23:30 <jflory7> #link https://pagure.io/fedora-diversity/issue/8
12:23:59 <jflory7> So, this is obviously the big one - jonatoni added a lot of super great info to the ticket about location in Brno. It seems like that might be the best option for us to keep cost down to a minimum.
12:24:13 <jflory7> We also proposed to have a hack session on Friday, but we could go ahead and choose a time to commit to.
12:24:24 <jflory7> I'm tempted to say I probably won't be at the airport until 5:00 UTC
12:25:50 <jflory7> I think the focus for the hack session is demonstrating / showing the impact we hope to achieve project-wide by holding this FAD and how we intend to have that impact
12:26:05 <jflory7> We have a lot of the purpose and activities defined
12:26:09 <Amita> it will be helpful if the candidates will come handy with their air travel ticket cost info, then we can do the rough estimation.
12:26:32 <jflory7> It's a matter of tying that to long-term outcome next, I think. I don't think that will take too long, but after that, budgeting would be the next important thing, yeah.
12:27:03 <jflory7> Amita: Yeah - especially if we end up hosting in Brno, traveling might be easier to wrangle
12:27:41 <Amita> jflory7, yeah and now we have accommodation estimation, travel cost will be helpful to do rough total estimation
12:27:50 * jflory7 nods
12:27:57 <Amita> jflory7, we can go in depth on this topic in the hack session
12:28:10 <jflory7> So I'm going to suggest target items for the hack session will be defining impact and getting a first run of the estimated event cost
12:28:25 <Amita> +1
12:28:27 <jflory7> #idea Target items for the hack session can be defining impact and getting a first run of the estimated event cost
12:28:50 <jflory7> +1 from me too, of course
12:29:16 <tatica> +1
12:29:18 <a2batic> +1
12:29:44 <jflory7> Cool - so... what time?
12:29:58 <jflory7> 5:00 UTC work alright for everyone, or maybe a little later than that?
12:30:07 * devyani7 tries to convert that
12:30:23 <jflory7> 10:30am.
12:30:26 <jflory7> ^ IST
12:30:26 <devyani7> +1
12:30:32 <Amita> +1
12:30:40 <devyani7> jflory7: :)
12:31:13 <jflory7> tatica: You're really up for that crazy time??
12:31:39 <tatica> jflory7, yup, if I fail, you will know I tried... but since the doggie wakes me up about 5 times per night, will be ok
12:31:50 * jflory7 nods
12:31:59 <devyani7> tatica++
12:32:00 <zodbot> devyani7: Karma for tatica changed to 18 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
12:32:09 <Amita> tatica++
12:32:10 <zodbot> Amita: Karma for tatica changed to 19 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
12:32:16 <Amita> .tatica
12:32:16 <zodbot> I love tatica, you love tatica, WE ALL LOVE TATICA!
12:32:22 <jflory7> I will have to bring some of the candies I got from Flock to you the next time I see you. :P
12:32:23 <a2batic> tatica++
12:32:23 <zodbot> a2batic: Karma for tatica changed to 20 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
12:32:29 <tatica> besides... if I get tired... i can start playing ps3 till you all arrive :D
12:32:32 <jflory7> tatica++
12:32:33 <tatica> jflory7, pm
12:32:34 <jflory7> Heheh :)
12:32:36 * jflory7 looks
12:33:07 <jflory7> I'll get this in the meeting minutes:
12:33:43 <jflory7> #agreed Target items for the hack session can be defining impact and getting a first run of the estimated event cost; will start at 05:00 UTC on Friday, 2016-09-23
12:33:57 <Amita> cool
12:35:09 <jflory7> #info === Ticket #10 ===
12:35:13 <jflory7> #info "Next Diversity Panel Planning - lets start it early so that we will do the best next year!"
12:35:17 <jflory7> #link https://pagure.io/fedora-diversity/issue/10
12:35:29 <jflory7> I think we pretty much covered this one earlier, actually
12:35:34 <jflory7> Now that I look at it.
12:36:51 <jflory7> I think we can just reuse the previous action here, I think we're all good here. :)
12:37:01 <Amita> +1
12:37:02 <Amita> yes
12:37:21 <jflory7> #agreed Continuing working on structure / format of the panel and what content to deliver for FUDCon diversity panel, will follow up again next week
12:37:45 <tatica> yeah, the leading ladies should lead this one
12:37:50 <jflory7> +1
12:37:51 <tatica> we are your mere servants :D
12:38:01 <jflory7> #info === Ticket #3 ===
12:38:04 <jflory7> #info "Guidelines for reporting Code of Conduct violations"
12:38:08 <jflory7> #link https://pagure.io/fedora-diversity/issue/3
12:38:37 * jflory7 does a quick mental refresher
12:38:40 <tatica> on this I'm still up to the diversity inbox
12:39:02 <Amita> I know there was an existing one from the old SIG
12:39:10 <tatica> I think that's the best way for us to be reachable for those who need us
12:39:17 <Amita> we need to ask them if we can reuse that
12:39:37 <jflory7> Ooh, yeah! So I requested a feature that was relevant to this in Pagure, but in addition to having private tickets, there will also be an option for having a repository create private tickets by default.
12:39:45 <jflory7> Do we want to use a mailing list format or tickets?
12:40:08 <bee2502> .hello bee2502
12:40:11 <zodbot> bee2502: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
12:40:20 <devyani7> bee2502: o/
12:40:24 <Amita> jflory7, Community_working_group used to have one private mailing list
12:40:24 <devyani7> hiya :)
12:40:26 <tatica> I would say tickets with notifications
12:40:32 <Amita> hi bee2502
12:40:33 <jflory7> I am a little more partial to ticket strategy because then it's clear what's still open, ongoing, or not responded yet. Also in Pagure this week, you can have ticket notifications go to a mailing list, so you could have new tickets go to the private mailing list for notifications.
12:40:37 <jflory7> bee2502: Hiya!
12:40:38 <jflory7> #chair bee2502
12:40:38 <zodbot> Current chairs: Amita a2batic bee2502 devyani7 jflory7 marinaz tatica
12:40:40 <tatica> I wouldn't like to have the info logged at the tickets + the maillist
12:40:53 <bee2502> hi everyone !
12:41:18 * jflory7 nods
12:41:22 <jflory7> So, here is my proposal here:
12:42:30 * Amita thinks something big is coming up
12:42:37 <jflory7> #proposed Create the repository in Pagure for private CoC violation reports, limit it to FPL, FCAIC, and Diversity Adviser, then create guidelines / template for reporting an incident and get those guidelines linked in the official CoC document on getfedora.org
12:42:43 <jflory7> +1/-1?
12:43:23 <tatica> couldn't we resume all that with the inbox?
12:43:27 <tatica> like a form?
12:43:42 <tatica> so, think about this
12:44:04 <jflory7> tatica: Hmm, like a web form to submit the report that then goes to a mailing list?
12:44:55 <tatica> the idea to have a team is to be able to understand all region issues. so for example, if a violation comes from apac, despite having a diversity advisor (which is me right now but can be anyone else) we have a "team of specialists" on that region, so, if in this survey, plus all the info about the violation we can have like some categories, a notification could go directly to those who are more familiar with this topics and can provide further help
12:45:06 <tatica> jflory7, no maillist, private tickets
12:45:43 <jflory7> I see. So you're proposing having the Diversity Team added to the repository as well?
12:46:16 <jflory7> Or maybe something like regional tickets that grant access to certain people?
12:46:23 <tatica> yeap, however, on the inbox, people can decide if they want to do it anonimous or call their names
12:46:35 <jflory7> Okay, I see...
12:46:52 <tatica> but, even if the ticket is open anonimously, we need them to have a fas (just for -activating- process, not recording personal info)
12:47:08 <tatica> because, if they havent sign the fas, they haven't signed the coc, so we can't proceed there
12:47:19 <jflory7> Yeah, so no ticket can truly be 100% anonymous with Pagure
12:47:20 <tatica> general tickets, but task forces
12:47:53 <tatica> could we somehow just don't show who opened the ticket in case they mark an option to hide it?
12:48:00 <tatica> so the server knows, but not us?
12:48:32 <jflory7> Hmm, this would be a question for us to raise with the Pagure team. Something like that doesn't exist yet, but I think it theoretically could.
12:48:33 <Amita> I think, that;s not possible
12:48:50 <jflory7> It's a matter of whether the Pagure dev team thinks it's something to pursue for all of Pagure globally
12:48:51 <Amita> and then how would it be recognized that it is coming from which region
12:49:22 <tatica> the regions is easy, can be a class, a tag, or something similar
12:49:30 * jflory7 nods
12:49:53 <a2batic> We can explicitly add the name of the region as the name of person who opened the ticket, maybe
12:50:24 <Amita> okay, but all the people won't understand the complexity of opening Pagure ticket since it is knew + tagging and all
12:50:34 <Amita> I am in favor of a simple mail
12:50:34 <tatica> a2batic, I like that idea, so it would be private somehow
12:50:39 <jflory7> We could have the person filing the ticket say that - in GitHub, you can have pre-filled issue templates if someone is filing a new issue. It might be possible to suggest something like that for Pagure, where we could then have a custom template of information someone filing the report could fill out in the ticket, e.g. fill in the blank
12:50:40 <Amita> which anyone can write easily
12:51:00 <tatica> jflory7, aye
12:51:10 <devyani7> jflory7: nod nod
12:51:18 <a2batic> +1
12:51:36 <tatica> I really don't want info to be on emails, I rather to have a centralized ticket system (in this case, pagure)
12:51:46 <jflory7> Amita: Maybe keeping the option for an email open? My one concern with email being the preferred method is that it's more difficult for us to keep a record for that one. So if someone sends mail, and then some people leave or join the team, that's going to be in a private archive that might have to be dug up to find history.
12:52:05 <tatica> plus, we can't have metrics with emails, we can with tickets
12:52:06 <Amita> jflory7, tatica I agree to that
12:52:13 <Amita> but..
12:52:24 <Amita> I was thinking from a customer point o view
12:52:36 <Amita> sorry customer --> victim
12:52:37 <tatica> Amita, when we reply the ticket, they will receive an email
12:52:48 <tatica> but all the action will be on the ticket
12:52:51 <Amita> ah that makes a good point
12:53:13 <tatica> like "hey, your ticket is being review by XXXX, do you agree? do you want to change that?"
12:53:22 <Amita> tatica, I loved it
12:53:31 <Amita> that's good
12:53:36 <jflory7> #idea Private-ticket repository with FPL, FCAIC, Diversity Adviser, Diversity Team added
12:53:38 <tatica> or "hey, your ticket has been answer, please go to xxxxxxx to read your diversity team comments, advices and/or resolution"
12:53:39 <tatica> etc
12:53:47 <jflory7> #idea Breaking it up by region so people most familiar from a region can respond
12:53:50 <tatica> so, the information is not on the email, is just a notification
12:54:09 <tatica> now, if someone wants to select multiple "tags" , should be doable too
12:54:19 <Amita> #idea reply to the ticket as "hey, your ticket is being review by XXXX, do you agree? do you want to change that?"
12:54:19 <jflory7> #idea Opening tickets anonymously: Is something like this possible? FAS account required. Maybe keeping the ticket anonymous to people in the repo??
12:54:29 <tatica> like "latam" "gender" "female"
12:54:47 <Amita> #idea if someone wants to select multiple "tags" , should be doable too like "latam" "gender" "female"
12:54:55 <tatica> so if for example, we have someone from latam, but our gender expert is in other region, they can work together
12:54:59 * jflory7 nods
12:55:02 <jflory7> That makes sense.
12:55:08 <Amita> cool
12:55:16 <tatica> because... just imagine the caos if everyone tries to work on each single team
12:55:16 <Amita> and one more concern/question here
12:55:36 <Amita> what if we want to discuss that ticket between us, within the team
12:55:42 <tatica> it can be possible... but... divide and conquer
12:56:00 <tatica> Amita, I would aim to some closed irc or hangout, or something similar
12:56:03 <Amita> what communication channel do we use
12:56:19 <tatica> we could even use bluejeans if the ticket needs more atention
12:56:27 <tatica> example, a sexual harrasment on a conference
12:56:33 <jflory7> I was going to suggest a private IRC channel
12:56:47 <jflory7> We still have #fedora-diversity-ops, although I am the only person there now.
12:56:48 <Amita> tatica, do we need to define that tooling in advance or we do that on the fly as the need arises?
12:57:06 <tatica> yeah, we can do some tests where jflory7 just sugegsted
12:57:10 <tatica> *suggested
12:57:35 <Amita> #info We can use #fedora-diversity-ops as private channel to discuss issues within the team
12:58:09 <jflory7> I think I can invite you all by NickServ... will follow up on that before we close out...
12:58:56 <jflory7> Oh, nb has founder privileges - will need to ping him
12:59:30 <Amita> jflory7, okay cool
12:59:40 <jflory7> Can follow up later on that, minor details
12:59:44 <jflory7> We're almost at time
12:59:56 <Amita> 1 hour it is, it was a 30 min meeting :P
12:59:58 * jflory7 was smart to eat breakfast *before* the meeting this time
13:00:06 <Amita> haha
13:00:16 <jflory7> Amita: Heh, I don't think 30 minutes will work well... too many things to cover. :)
13:00:17 <tatica> jflory7, same here!
13:00:34 <tatica> it's ok, if some days we make 1h and other 30min, as long as people is here, it will work
13:00:45 <Amita> jflory7, I know, just  a trick not to go beyond 1 hr ;)
13:00:47 <jflory7> So, quick verdict here, I can try playing with the Pagure repo in staging I made to test the concept
13:00:53 <tatica> btw, just a kindly reminder that I will be kinda afk from oct12 to nov3
13:00:55 <jflory7> Can bring more info next time or in the ticket.
13:00:59 <jflory7> tatica: \o/
13:01:06 <jflory7> Happy honeymoon :D
13:01:21 <Amita> wooohhooo
13:01:23 <Amita> honeymoon?
13:01:27 <tatica> I will only miss meetings on 19oct and 2nov
13:01:29 <tatica> yeah!!!
13:01:32 <Amita> tatica, ??
13:01:35 <tatica> late late... late.... honeymoon
13:01:36 <jflory7> #action jflory7 Add info to the ticket with technical ideas / details from test repo in Pagure staging repositories
13:01:40 <jflory7> #topic Open Floor
13:01:44 <Amita> hahah xoxoxoox tatica enjoy
13:01:45 <tatica> I add it already to the calendar
13:01:58 <tatica> if anyone is at miami or orlando, please ping me out
13:02:07 <jflory7> :)
13:02:34 <Amita> miami WOW
13:02:46 <Amita> tatica, you gonna enjoy, that's wonderful place
13:02:52 <tatica> or bahamas :D
13:02:53 <jflory7> I'm probably going to have to jump out now - got a bus to catch in 30min.
13:03:02 <jflory7> The last thing that was left was this ticket: https://pagure.io/fedora-diversity/issue/2
13:03:07 <tatica> thank you all for being here!!
13:03:16 <jflory7> But tatica can give it a quick +1 or -1 and we can go from there. :)
13:03:26 <jflory7> And same to you all!!
13:03:31 <Amita> thanks jflory7
13:03:35 <Amita> jflory7++
13:03:52 <jflory7> Until next week – see you all in channel. :)
13:03:54 <jflory7> 3endmeeting
13:03:56 <jflory7> #endmeeting