17:02:47 #startmeeting CommOps 17:02:47 Meeting started Tue Jan 12 17:02:47 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:47 The meeting name has been set to 'commops' 17:02:55 #meeetingname Fedora CommOps 17:02:58 .hello corey84 17:02:59 linuxmodder: corey84 'Corey Sheldon' 17:03:07 #meeetingname Fedora CommOps 17:03:07 #chair decause jflory7 threebean bee2502 lmacken cproffit mailga danofsatx 17:03:07 Current chairs: bee2502 cproffit danofsatx decause jflory7 lmacken mailga threebean 17:03:10 #topic Roll Call 17:03:10 .hello aikidouke 17:03:11 aikidouke: aikidouke 'Zach Villers' 17:03:15 #info Name; Timezone; Subprojects/Interest Areas 17:03:17 .hello decause 17:03:18 decause: decause 'Remy DeCausemaker' 17:03:21 .hello jflory7 17:03:21 .fas mailga 17:03:22 jflory7: jflory7 'Justin W. Flory' 17:03:25 mailga: mailga 'Gabriele Trombini' 17:03:36 late morning to all 17:03:41 #info Justin W. Flory; UTC-5; CommOps / Marketing / Fedora Join / Ambassadors / etc. 17:03:42 #info decause; UTC-5; CommOps, Council, Ambassadors, * 17:03:48 Morning, all! 17:03:49 .fas bee2502 17:03:49 bee2502_: bee2502 'Bhagyashree Padalkar' 17:04:00 .fas corey84 17:04:00 linuxmodder: corey84 'Corey Sheldon' 17:04:01 #info aikidouke 17:04:08 Looking like it will be much more lively than last week. :) 17:04:16 welcome back everyone :) 17:04:23 anybody else? 17:04:54 dgilmore, you get my email about the livemedia-creator ? would like to start using that more for events and the planned reboot of campus | youth ambassadors 17:05:10 decause: I think we should plow on ahead, we have a packed meeting today 17:05:14 jflory7: agreed 17:05:18 decause, I'm here to (ws not able to make last week) 17:05:24 linuxmodder: welcome back :) 17:05:27 linuxmodder++ 17:05:31 linuxmodder: No worries, it was post-holiday time. :) linuxmodder++ 17:05:31 aikidouke++ 17:05:31 decause: Karma for aikidouke changed to 6 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:05:39 mailga++ 17:05:44 bee2502++ 17:06:01 jflory7: press on 17:06:02 decause, my fas is corey84 if that's waht you meant :) 17:06:02 :) 17:06:08 #topic Tickets 17:06:13 corey84++ 17:06:14 #info === Ticket #8 - https://fedorahosted.org/fedora-commops/ticket/8 === 17:06:15 decause: Karma for corey84 changed to 1 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:06:20 #info * CommBlog Article: Flock Call for Bids 17:06:29 Mainly follow-up on this ticket. See my last comment on the ticket. 17:06:41 linuxmodder: not sure I got your email 17:06:43 so this is for flock 16 bids yes? 17:06:53 Do we want to close it or do we want to push for the social media posting a bit more? 17:06:55 linuxmodder: Correct. 17:06:55 dgilmore, after mtg then I guess 17:07:27 The article was written a month or two ago, in late November, I think. We wanted to get an extra push for it in December and got it circulated on a few mailing lists and we have new bids, but we were wanting to do an additional push on social media. 17:07:30 jflory7: I think we just need to double check the social-media list to make sure that folks with creds are on there. I /think/ I have creds, but I rarely use them manuually 17:07:53 the overall theme again for flock16 ? 17:07:53 decause: Probably something we should check out, yeah. I also CC'd the marketing list with those replies though. 17:08:07 linuxmodder: I'm not sure about the theme as of yet, but we were hoping to get some more bids in the EMEA region. 17:08:09 jflory7: there is good discussion happening around strategy 17:08:17 I saw that on the marketing list too 17:08:52 #action jflory7 / decause: Make sure people with the social media powers are subscribed to the social-media mailing list 17:08:53 jflory7: lets just ping bkp directly for now, to get one last tweet out the door today 17:08:57 * jflory7 nods 17:08:59 jflory7: next 17:09:13 #info === Ticket #15 - https://fedorahosted.org/fedora-commops/ticket/15 === 17:09:20 #info * Hook up email posting functionality for CommBlog 17:09:26 #action jflory7 Ask puiterwijk about this, see if ticket should be filed in Fedora Infra Trac 17:09:39 this is an oldie, but a goodie ;) 17:09:50 * puiterwijk reads back 17:09:58 Mainly wanted to follow up on this, was hoping to clarify with puiterwijk about how to set this up. 17:10:02 Hiya Patrick :) 17:10:08 puiterwijk++ 17:10:10 hi. Sorry, give me one minute to read back 17:10:13 Sure thing. 17:10:28 Mainly just wanting to look into setting up email-to-blog for Community Blog. 17:10:38 Wanted to know if and how to go about doing that. 17:10:44 puiterwijk: (I have some FOSDEM/DevConf/configmgmtcamp related questions for you after this meeting, fyi) 17:11:10 Ah, okay. I'll need to dig into that. If you assign the ticekt to me, I'll take a look at it 17:11:12 We could file a ticket in the Infra Trac if that's easiest, just wanted to see what your workflow was like. :) 17:11:15 (as you will need inbound SMTP and all) 17:11:28 jflory7: I think we should file on the infra trac, reference comomps ticket, and cc puiterwijk and decause 17:11:31 I'll take tickets on the commops trac as well. Just assign to me 17:11:38 decause: Agreed. 17:11:39 puiterwijk: awesome 17:12:01 #agree Assign puiterwijk Ticket #15 in CommOps Trac, file ticket in Infra Trac, cc puiterwijk and decause 17:12:05 jflory7: just commops should be enough. I prefer to have issues in one central point :) 17:12:05 Next ticket? 17:12:11 net 17:12:12 puiterwijk: Noted 17:12:13 next* 17:12:14 #undo 17:12:14 Removing item from minutes: AGREED by jflory7 at 17:12:01 : Assign puiterwijk Ticket #15 in CommOps Trac, file ticket in Infra Trac, cc puiterwijk and decause 17:12:15 only immediate issue I see is the spam from posting via email like that Gary skeete idoot on -docs ml 17:12:24 #agree Assign puiterwijk Ticket #15 in CommOps Trac 17:12:34 linuxmodder: we'd whitelist addresses likely 17:12:41 linuxmodder: Yeah, it would have very special privileges, no spam for sure. :) 17:12:47 #info === Ticket #17 - https://fedorahosted.org/fedora-commops/ticket/17 === 17:12:51 linuxmodder: good call though 17:12:51 #info * Interview Fedora's Diversity and Inclusion Advisor, tatica 17:12:56 Here's a more recent topic! 17:12:58 woo 17:13:05 We ticketed this in December but haven't had a chance to discuss it yet. 17:13:11 like a established user/contributor bar of entry kinda thing ? 17:13:37 decause: and feel free to ping me in any channel at any time :) 17:14:00 linuxmodder: we have a tool, wordcloudbot, that creates wordclouds of meeting minutes, and it would be nice to have it auto-post those to the commblog with a template 17:14:33 linuxmodder: it could be used to have our commops members send posts via email as well, yes, but would require special attention to templating 17:15:03 jflory7: I know tatica wanted to get a few things underway before we heavily promoted her presence, so let us ping her and see how she's doing 17:15:15 #action decause/jflory ping tatica, invite her to commops list 17:15:23 not suretemplating would be the issue even tho as that dude spamming the docs ml is hardly a typical template but later 17:15:25 decause: Sounds good. How do we want to handle this interview? 17:15:32 Do we want to ask her if she has some things she wants to highlight? 17:15:41 Or do we want to come up with the questions and pose it as an interview? 17:15:51 Well, either way, it's posed as an interview, I suppose. 17:15:57 jflory7: perhaps creating an "interview template" would be a good idea 17:16:06 we have similar things in OpenSource.com-land 17:16:07 * decause digs 17:16:07 Guess it just depends if she or us are coming up with the questions, or probably both. 17:16:15 Ooh, that would be a good resource 17:16:17 decause++ 17:16:20 why dn't we ask her to write a topic and then let users asking questions? 17:16:26 #link https://opensource.com/how-conduct-interview-opensourcecom 17:16:55 mailga: Hmmm. What do you mean a topic, like specific kinds of things about her roles and then let users ask questions about those things? 17:16:57 we can port this to be more Fedora-specific, but it is a good place to start 17:17:05 would a AMA style blog interview be out iof the question re:317 17:17:16 mailga: an "AMA" would be a cool thing to do at some point, great idea :) 17:17:16 decause: definitely, this is looking like good fuel. I'll read it all later. :) 17:17:23 jflory7: exactly 17:17:24 jflory7: nod nod 17:17:25 err, current ticket 17:17:33 linuxmodder: took words right out of my mouth :) 17:17:42 mailga++ linuxmodder++ I'm liking the sounds of all of that. 17:17:48 great minds think alike :) 17:18:19 So, what I'm seeing is: we ask tatica_ about some of her thoughts about her role and major areas that might be uncertain, ask CommOps + other list(s) for questions, then aim for CommBlog? 17:18:20 jflory7: cc her on the ticket in trac, and we'll send her a personal email too 17:18:28 I'm great at the thinking part and brainstorm part not so much at the content creation tho :( 17:18:58 jflory7: I know she's going to want to have some more stuff "done" before we publish her interview, so lets just open a loop, and start gathering the interview questions in general 17:19:12 linuxmodder: No worries - the brainstorming is just as important as the content creation. I can always help out with the content creation too :) 17:19:15 decause: Sounds good. 17:19:19 jflory7, or even possibly tie it in the 2016 goals thread -- what would you like to see yourself locally regionally or more broadly 17:19:45 make it less Ny resolution ish 17:19:46 as far as "big idea" stuff for this: Doing Contributor Profiles (which can be easily ported to Hubs pages) is something that commops will be doing in the 90-120 days from now range if we can get our ducks in a row and things go according to plan 17:19:55 #agree Contact tatica_ about the plans to conduct the interview, begin the process of bringing everything together (cc her on Trac ticket) 17:20:05 maybe even make the default for this year's interview have that tie 17:20:08 #action jflory7 CC tatica on Ticket #17 17:20:20 solid 17:20:24 decause: Contributor Profiles... that sounds awesome. 17:20:27 Looking forward to that! 17:20:31 jflory7: :) 17:20:36 we'll get there. Hubs will get there. 17:20:41 Hubs++ 17:20:43 Next ticket? 17:20:46 nod nod 17:20:53 #info === #Ticket #20 - https://fedorahosted.org/fedora-commops/ticket/20 === 17:21:00 #info * Year in Review - CommOps Retrospective 17:21:04 #link http://etherpad.osuosl.org/fedora-commops-yir-2015 17:21:21 We began discussing this at the least meeting. 17:21:24 I've updated the etherpad with more bullets, but I need to get more concrete content in there 17:21:35 I wanna ship this by Thursday if we can 17:21:35 I'm also planning on really going for it soon too. 17:21:38 Oh, wow! 17:21:40 Okay. 17:21:46 I think we can do that. 17:21:53 we need our "model" so we can encourage other ones too 17:22:00 Right. 17:22:07 as an aside, I'm also looking to do one for Council YiR 17:22:20 arent the fedmsg metrics done with the threebeans gource videos ? or do we have something else in mind ? 17:22:27 #action jflory7 Raise Ticket #20 priority 17:22:59 decause: I'm thinking we try to hammer out the final outline in the Etherpad today, and then begin converting to an article today / tomorrow, then share with list ASAP once finished 17:23:08 Also, gathering input in channel today and tomorrow would also be good 17:23:13 bee2502_: yeah, those fedmsg/gource vids will be nice supplments to each YiR if we get separate ones, or bullets int he larger YiR aggregate taht we push before Feb 17:23:18 Definitely a hands-on thing for anyone wanting to be involved 17:23:28 jflory7: that sounds like a good plan to me 17:23:39 I'll cycle direct with you today if you got time to get that hammered out 17:23:49 jflory7: let's check in after this 17:23:54 * jflory7 nods 17:24:05 anyone else is welcome to come hammer out deets as well, we'll meet in #fedora-commops and discuss after meeting 17:24:27 #agree Finish outline for CommOps YiR article today, begin porting to a CommBlog article today / tomorrow, get feedback in channel while working on this and on mailing list once finished 17:24:32 jflory7: has anyone submitted any YiR content besides us yet? 17:24:38 decause: Not that I've seen. 17:24:40 Hiya, danofsatx! 17:24:46 sure sure 17:24:51 danofsatx: welcome back 17:25:02 are you all wanting yir content from all of the groups? 17:25:07 jflory7: maybe that is another item for our social-media blast request to Bkp 17:25:09 Any other thoughts on Ticket #20 / CommOps YiR article? 17:25:16 aikidouke: ideally, yes 17:25:25 aikidouke: Yes, we're encouraging participation from as many subgroups as possible. :) 17:25:26 jflory7: we should post the request to announce list 17:25:32 I don't think we did that yet, right? 17:25:38 CommOps is helping make the process as easy and straightforward as possible. 17:25:41 decause: Correct, we did not. 17:25:47 Do we want to add that to the list today? 17:25:52 jflory7: yes 17:25:55 k, i could take a stab at something for infra (even tho I haven't been an apprentice all that long) 17:26:05 #action decause/jflory7 post request for YiR input to announce list 17:26:20 jflory7: decause tell me differences between Yir and the retrospective. 17:26:31 aikidouke: simply dropping an email to infra list, and in IRC, pointing to the commblog post would be helpful 17:26:42 if you want proofreading, just send commops a draft :) 17:26:43 aikidouke: That would be awesome! The first step would be to open a discussion with the Infra team about it. The main goal is to find three highlights of 2015 and one goal for 2016. Let me find the link to the announcement article! 17:27:02 mailga: I guess technically they're the same thing. Just one way of saying it versus the other. 17:27:02 will do, our meeting is on thursday, appreciate the link 17:27:07 * mailga still thinks about mktg retrospective... Is it the case to merge things? 17:27:07 aikidouke++ 17:27:19 mailga: that would be a great thing on it's own too 17:27:19 #link https://communityblog.fedoraproject.org/share-your-year-in-review-with-fedora/ 17:27:25 aikidouke^ see that. 17:27:27 mailga: and thank you for your input on that thusfar 17:27:33 mailga: that needs to be higher on my priority list too 17:27:39 aikidouke++ for looking at opening the discussion with Infra :) 17:27:39 jflory7: Karma for aikidouke changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:27:45 yep 17:27:52 mailga: when do you think we should get that out the door? 17:28:02 mailga: That would go hands-on with the retrospective we were wanting to start! 17:28:08 I totally forgot about that until now. 17:28:08 mailga++ 17:28:10 decause asap, IMHO 17:28:18 mailga: let's shoot for EoW 17:28:21 Holiday fog, I can't believe I forgot about that. 17:28:43 mailga: maybe ping the mktg list one more time, asking for input, and letting folks konw that we want to use it for YiR posts in the next week or two 17:28:51 mailga: sound good? 17:28:58 decause +1 17:29:15 +1 to the idea from me too 17:29:19 mailga: lets shoot for retrospective done on wiki by EoW, and YiR by EoW next week? 17:29:37 #info EoW = End of Week 17:29:38 decause: a YiR should be the starting point for next year... and the next year just started. 17:29:59 mailga: as long as we get our YiR content out before Feb, we're on track 17:30:28 once January is gone though, the content won't be as fresh 17:30:28 decause I'll shoot a reminder mail on mktg list today. 17:30:32 mailga++ 17:30:35 mailga++ 17:30:35 Anything else for Ticket #20? 17:30:48 #action mailga ping mktg list again on retrospective to be completed by end of week 17:31:09 jflory7: we got into a few other loops, but i think we're good. we'll sync after this. 17:31:13 * jflory7 nods 17:31:15 #info === Ticket #22 - https://fedorahosted.org/fedora-commops/ticket/22 === 17:31:22 #info * Publishing graphics tools / resources via Fedora Magazine Images Repo 17:31:43 See my last comment on that ticket 17:31:43 There is a Magazine page with that info 17:31:49 Although it isn't in an easily viewable location 17:31:54 You have to know it's there or have someone link you. 17:32:06 #link https://fedoramagazine.org/creating-a-featured-image-for-a-fedora-magazine-article/ 17:32:27 Perhaps adding a section in the "Writing for the CommBlog" page about featured images and linking to the Magazine about how to make one for an article if you want to? 17:32:39 I think that we can just make a link in our toolbox wiki section, and basically regex magazine/commblog, and post our own how-to within the "writing for commblog" page? 17:32:45 Still wondering if we should do something beyond that to make it more exposed. 17:32:47 jflory7: nod nd nod 17:32:52 decause: It's in our toolbox as of yesterday :) 17:32:56 jflory7: you are reading my mind :) 17:33:16 jflory7: I don't think it is a big issue that it doesn't have menu real-estate 17:33:29 just curious, are images from sites like unsplash usuable in fedora content 17:33:37 I'm not as worried about it being discoverable, as much as we need to be able to point at it when needs be 17:33:41 So basically make the same page on the Magazine our own independent page on the CommBlog? 17:33:41 i beleive they are CC do what you want with 17:33:52 aikidouke: I think it depends on the licensing - I'm not familiar with Unsplash specificallyu. 17:33:54 aikidouke: if it is CC, it is potentially usable 17:33:58 s/specificallyu/specifically 17:34:10 our magazine images repo is specific graphics made for banners by Fedora Design and other contributors 17:34:15 they could be useful elsewhere too 17:34:32 decause: My main thought on mirroring for the CommBlog is that we don't really have a high barrier for featured images for our articles. 17:34:37 They're nice to have 17:34:44 jflory7: agreed 17:34:55 But I imagine it might appear intimidating to some who are writing for the first time 17:34:55 it is also a good candidate for design-team onboarding 17:35:00 Ooh, yeah 17:35:02 link if ne1 is curious; All photos published on Unsplash are licensed under Creative Commons Zero which means you can copy, modify, distribute and use the photos for free, including commercial purposes, without asking permission from or providing attribution to the photographer or Unsplash. 17:35:04 oops 17:35:06 Didn't think of it like that 17:35:16 https://unsplash.com/license 17:35:17 aikidouke: I want to say that would be okay to use? 17:35:34 Pretty sure public domain is safe. 17:35:45 aikidouke: that would be a great resource for folks looking to use graphics within their featured images, yes 17:35:53 cool 17:36:00 we can add that to our "writing for commblog" section on graphics perhaps 17:36:11 Ooh, looking at the site now 17:36:15 This is a good treasure trove 17:36:18 ikr :) 17:36:19 #link https://unsplash.com/ 17:36:38 #action jflory7 Add Unsplash.com as a resource for finding images to "Writing for CommBlog" page 17:36:45 aikidouke++ 17:36:58 one more if you havent seen it; https://github.com/neutraltone/awesome-stock-resources 17:37:00 ok, we're just past the half-way point 17:37:03 timecheck 17:37:14 So beyond our toolbox and CommBlog mention, anything else we want to do with this? 17:37:36 jflory7: maybe update the ticket with ideas from this meeting, after this meeting 17:37:57 it's low-prio for me right now, but also not too intense of a task if anyone wanted to pick it up 17:38:01 #agree Fedora Magazine Images repo in CommOps toolbox, to be mentioned / added to "Writing for CommBlog" - still an ongoing discussion, details will be added to ticket for further discussion 17:38:03 * jflory7 nods 17:38:17 jflory7: next 17:38:17 So I think that will wrap up today's tickets 17:38:22 awesome! 17:38:26 #topic Wiki Gardening 17:38:26 ? 17:38:31 #action NewMembers Add your timezone / interests on CommOps Wiki [ http://fedoraproject.org/wiki/CommOps ] 17:38:37 mailga: What's up? 17:38:54 decause: Anything you wanted to add to wiki gardening for today? 17:39:11 not really important, but some days ago talking with Paul 17:39:20 jflory7: I got one 17:39:35 this is a recently added wiki page: 17:39:38 #link https://fedoraproject.org/wiki/Community_Leader 17:39:46 ohhai ;) 17:39:47 I didn't understand the raelly diccerences between commblog and magazine posts. 17:40:03 if there are other leadership positions within Fedora that do not have a wiki page, that is something commops can help with 17:40:06 * mailga sorry very slow..... 17:40:20 I'm thinking of the D&I advisor specifically, but also, our release manager would be a good one too 17:40:29 mailga: Hmmm - I think if that's something you're a little confused on, then there's likely many others who may feel the same way. We could probably use a little more specific clarification. 17:40:57 jflory7: +1 a wikipage? 17:41:02 decause: I did see that wiki page added! Good call for D&I. Who is release manager? 17:41:04 danofsatx: Hiya! 17:41:18 mailga: I think a wiki page would be good. I also like the idea of adding it somewhere obvious to the CommBlog. 17:41:23 To answer your question though-- 17:41:23 mailga: CommBlog and Magazine are two of our official channels of communication. Magazine is specifically focused on User content, whil CommBlog can include more Contributor focused content, and stuff outside of Fedora that is interesting to Fedora. 17:41:27 jflory7: 6 17:41:27 ^ 17:41:29 Or that. 17:41:31 :) 17:41:47 jflory7: wouldn't be a bad idea to add that description to the commblog toolbox entry 17:41:47 decause: 6? 17:41:53 * jflory7 nods 17:41:56 jflory7: I missed the shift key ;) 17:42:03 decause: jflory7 tnx. 17:42:05 Ahhh, gotcha. :) 17:42:08 mailga++ 17:42:11 good question 17:42:57 #action commops create a ticket to create a wiki page for Release Manager, RelEng Lead, and Diversity and Inclusion Advisor (among any other new Fedora Leadership postions not on the wiki yet) 17:43:11 #action jflory7 Add clarification about Magazine vs. CommBlog to our toolbox, add section to Community Blog wiki page about CommBlog vs. Magazine specifically 17:43:16 jflory7: that is all I got for wiki gardening fo rnow 17:43:16 decause++ 17:43:23 I think same for me 17:43:27 next :) 17:43:28 ? 17:43:30 Anything else wiki-related anyone wants to add? 17:43:34 mailga: Go ahead. 17:44:00 can we ask to each group to merge pages that need love? 17:44:09 such as https://fedoraproject.org/wiki/Marketing/WikiCleanup 17:44:12 ? 17:44:14 mailga: I like that idea of decluttering the wiki a good bit. 17:44:27 mailga: that is exactly what this section of the meeting is for mentioning 17:44:30 :) 17:45:03 mailga: Feodra-infra has been tackling "technical debt" this week too, so "housekeeping" in commops land include wiki 17:45:23 Do we want to ticket that? 17:45:39 decause: we need people to work on it. 17:45:43 Would be a good topic to open discussion for. 17:45:43 jflory7: yes, let's file a ticket so mailga can get some help with all that 17:45:49 mailga++ 17:45:55 mailga: Do you want to file the ticket or would you rather me file it? 17:46:01 decause: of course. 17:46:10 nice job laying out the task list, this is a great way for us to get more heat into mktg 17:46:20 mailga++ 17:46:22 nice work there 17:46:36 jflory7: if you can do that I can go to have a dinner :-D 17:46:40 ;-) 17:46:41 * jflory7 nods 17:46:43 No problem :) 17:46:44 jflory7: thanks 17:46:47 mailga++ 17:46:49 enjoy dinner 17:47:02 decause: I have to cook... ;-( 17:47:09 mailga: :P 17:47:15 #action jflory7 Open ticket on Trac about starting initiative / movement to encourage subgroups to merge related wiki pages (reducing clutter) 17:47:21 Anything else for wiki gardening? 17:47:29 We've got 13 minutes on the clock but I think we can fit the last bit in 17:47:36 jflory7: specifically a ticket for the mktg updates mailga posted to? 17:47:42 too* 17:47:51 I'm good on wiki after that 17:48:01 This is not exactly a wiki task - the page could surely use some love - but I would like to discuss on this : https://fedoraproject.org/wiki/Women decause jflory7 17:48:13 Comes under CommOps right ? 17:48:35 #action jflory7 / mailga: Create and discuss a ticket about the Marketing retrospective and its usefulness for the Year in Review article as well 17:48:37 bee2502++ 17:48:38 Yes!! 17:48:40 bee2502++ 17:48:49 yes, def under comops 17:49:42 We could definitely go through that wiki page and do some updating, especially looking at this article we're looking at preparing too 17:49:43 bee2502_: I will be moderating a Women in Open Source panel at NYU in the next couple of weeks, so I'd really like to have as much updated info there for the potential new contribs who will be hearing about Fedora then too 17:49:58 decause does Fedora have any women specific initiatives ? Debian has https://www.debian.org/women 17:50:08 bee2502_: let's open a loop on the mail list, cc tatica and mizmo (who is on leave) and ask folks to update the page? 17:50:13 I think a ticket for this page would definitely be best to help us keep tabs on this 17:50:24 And a discussion on the list too 17:50:29 jflory7: pointing to the ticket 17:50:35 jflory7 : yeah , the article is why I started searching :) 17:50:35 #byourpowerscombined 17:51:03 bee2502_: As far as I know, Outreachy was the first major "initiative", but I really haven't been around for all too long. 17:51:10 decause - we are having an article out on CommBlog about women in Fedora - sort of - prolly would be helpful 17:51:11 I'm inclined to think something has been done before, though. 17:51:36 bee2502_: Outreachy is one of the big drivers here for us, but adding tatica to the council will help us do more too 17:51:47 * mailga thinks we need people don't disappear. Yes someone can do the work when he/she can, but someone should take the commitment to be available. 17:52:01 bee2502_: that page does need to be updated, and I think there are new women to be added to that page also 17:52:08 In the interest of time, I recommend we make a ticket specifically for the wiki article and look at keeping it updated and current. 17:52:38 mailga: Definitely agreed. 17:52:43 bee2502_: can you file a ticket on the commops tracker to update the women wiki page, and then we cant post to the women/outreach/outreachy lists with a request to update the info before 1/22? 17:53:04 that is when I'll be moderating at the Women In Tech Conference 17:53:04 decause - I was thinking we could link the page with CommBlog article to reach more women 17:53:11 bee2502_: I like that too 17:53:15 +1 17:53:17 decause sure 17:53:27 lets start with ticket, get that posted to mail list, and then post basically the same message tohte commblog 17:53:34 bee2502++ 17:53:36 all sounds good 17:53:51 bee2502_: We could maybe even do a call-to-action at the end of the article to ask women to add themselves to the wiki article too. We can discuss more in channel after meeting. :) 17:53:58 bee2502++ 17:54:04 bee2502++ 17:54:04 bee2502++ 17:54:04