15:59:25 #startmeeting Fedora CommOps (2016-03-15) 15:59:25 Meeting started Tue Mar 15 15:59:25 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:59:25 The meeting name has been set to 'fedora_commops_(2016-03-15)' 15:59:30 #meetingname commops 15:59:30 The meeting name has been set to 'commops' 15:59:38 .hello decause 15:59:39 decause: decause 'Remy DeCausemaker' 15:59:39 #topic Agenda 15:59:44 #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-03-15 15:59:48 #info 1. Roll Call 15:59:49 jflory7: we should talk about whether we are going to stick to UTC, or use DST 15:59:52 #info 2. Announcements 15:59:58 #info 3. Action items from last meeting 16:00:02 #info 4. Tickets 16:00:06 #info 5. Wiki Gardening 16:00:10 #info 6. Community Blog 16:00:14 #info 7. Open Floor 16:00:17 #topic Roll Call 16:00:22 #info Name; Timezone; Sub-projects/Interest Areas 16:00:22 .hello skamath 16:00:24 skamath: skamath 'Sachin Kamath ' 16:00:28 If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! 16:00:30 .hello jflory7 16:00:31 jflory7: jflory7 'Justin W. Flory' 16:00:51 #info Justin W. Flory; UTC-4 (as of now...); CommOps, Marketing / Magazine, Ambassadors, Join, and more 16:01:07 decause: Yeah, we definitely should. It totally blind-sided me for the meeting this week. 16:01:14 .hello trishnag 16:01:16 trishnag: trishnag 'Trishna Guha' 16:01:24 #chair decause skamath trishnag 16:01:24 Current chairs: decause jflory7 skamath trishnag 16:01:27 Welcome everyone! 16:01:30 #info Sachin Kamath; UTC +5.30; CommOps, Ambassadors 16:01:51 #info decause: UTC -5; Commops, Council, * 16:01:54 Hi jflory7 :) 16:01:58 decause: It mostly seems like a USA schedules vs. rest of world schedules. :) 16:02:01 err, are we now -4? 16:02:04 Hiya, skamath! :) 16:02:10 decause: I think so. 16:02:12 .localtime jflory7 16:02:13 jflory7: The current local time of "jflory7" is: "12:02" (timezone: US/Eastern) 16:02:21 UTC is easier to track :P 16:02:25 skamath: Agreed... 16:02:29 Hi all :) 16:02:35 None of this silly Daylight Savings stuff! :D 16:02:49 We'll wait a couple more minutes for some more folks to come in too. 16:02:59 Bee said she might be late because of the time change. 16:03:01 No aylight Saving here :P 16:03:04 it helps the folks on the other side of the planet a lil bit cause it is an hour earlier, but still confusing 16:03:31 decause: Yeah. Not sure about you, but I could move back an hour to 11am our time pretty easily. 16:03:38 Anyone who is here for GSoC should take an extra moment after rollcall to introduce themselves 16:03:56 #topic GSoC introductions 16:04:05 I guess I already did. Should I do it again? 16:04:38 skamath: more than just the standard info; we wanna know more about what projects you are interested in, and where you are working so far, etc... 16:05:11 Alright. I am Sachin from India. Currently pursuing my B.Tech in CSE. I am interested in CommOps WebDev in general. I am good with bash, python and DevOps. 16:05:58 skamath: thanks :) 16:05:59 I can manage servers effectively and have also done a bit of content-writing. I occasionally design stuff too 16:06:00 anyone else? 16:06:11 skamath: you wear lots of hats it sounds like 16:06:13 * linuxmodder late 16:06:19 commops folks tend to be generalists 16:06:24 you'll fit right in :) 16:06:28 .hello corey84 16:06:28 decause: Just exploring stuff :) 16:06:28 linuxmodder: corey84 'None' 16:06:40 * decause waves to linuxmodder 16:06:45 thanks for helping with fedora-hubs 16:06:51 decause, no prob 16:06:53 I've got a huge backlog of welcome emails to get through after this meeting 16:07:05 #chair linuxmodder 16:07:05 Current chairs: decause jflory7 linuxmodder skamath trishnag 16:07:08 decause, and there were 5 more this morning :) 16:07:13 linuxmodder: :) 16:07:22 linuxmodder: the welcome kit been any help to you? 16:07:40 Alright... shall we roll into the agenda? 16:07:47 #link http://etherpad.osuosl.org/fedora-gsoc-welcome-2016 16:07:49 jflory7: good 16:07:56 #topic Announcements 16:08:04 #info === No tickets closed this week === 16:08:05 decause, the etherpad more than anything has 16:08:08 #info === Ticket #21 === 16:08:13 #link https://fedorahosted.org/fedora-commops/ticket/21 16:08:17 #info * "Ambassadors - Event Report Template" 16:08:22 #info This ticket is open for anyone to claim and start working on. The idea is that we have a recommended "format" for Ambassadors to use for writing event reports of places that they represent Fedora at. This is a *great* task for someone who wants to get involved and either has experience as a Fedora Ambassador or going to other events as open source representatives. If this interests you, ask to claim this ticket at Open Floor or on the 16:08:22 mailing list! 16:08:35 #info ...mailing list! 16:08:41 #info === Ticket #26 === 16:08:43 :P 16:08:45 #link https://fedorahosted.org/fedora-commops/ticket/26 16:08:50 #info * "Mailing lists analysis and graphs" 16:09:03 #info This ticket is also open; another *great* ticket for someone new who wants to get involved. Ticket looks at mailing list activity in Fedora with fedmsg and tries to try conclusions from that data. If this interests you, ask to claim this ticket at Open Floor or on the mailing list! 16:09:08 #info === Ticket #45 === 16:09:14 #link https://fedorahosted.org/fedora-commops/ticket/45 16:09:15 #action linuxmodder to draft a rough copy for ticket 21 16:09:19 #info * "Talking Points: Python" 16:09:26 .hello sayanchowdhury 16:09:26 #info Ticket needs collaboration! Cross-effort between Marketing and CommOps. 2016 is the Year of Python in Fedora! If you have experience with working on Python in Fedora, your input is needed and valued for this ticket for helping come up with ideas and points about why working on Python in Fedora makes your life easier. If this interests you, ask to help on this ticket at Open Floor or on the mailing list! 16:09:28 sayan: sayanchowdhury 'Sayan Chowdhury' 16:09:31 #chair sayan 16:09:31 Current chairs: decause jflory7 linuxmodder sayan skamath trishnag 16:09:37 #info === Ticket #59 === 16:09:42 #link https://fedorahosted.org/fedora-commops/ticket/59 16:09:45 decause: Is there anything I have to do before I submit my proposal? 16:09:46 #info * "Modernization of Trac wiki page" 16:09:57 #info Justin (jflory7) and Ryan (masetrax) have been collaborating over email on this ticket; masetrax will become the new owner and is looking at bringing the Trac wiki page "up to date" for 2016. Thanks for taking this on, Ryan! 16:10:02 #info === Google Summer of Code announced on Community Blog === 16:10:07 #link https://communityblog.fedoraproject.org/fedora-accepted-google-summer-of-code-gsoc-2016/ 16:10:13 #info GSoC 2016 is about to get in full swing! Applications opened yesterday, watch the mailing list for new activity. 16:10:16 #info related to ticket #45: https://fedoraproject.org/wiki/Objectives/Fedora_Marketing_Python 16:10:20 skamath, you were the one talking about the Web Application options yesterday eys? 16:10:22 decause: You might have a minor typo to fix in the featured image. :) 16:10:24 #link https://fedoraproject.org/wiki/Objectives/Fedora_Marketing_Python 16:10:28 linuxmodder: yep 16:10:34 jflory7: srsly... 16:10:38 it was pretty late 16:10:52 skamath, which do you want to do more devops-y stuff or content 16:10:57 sumer of code! 16:11:01 sayan: Welcome, welcome! Feel free to do an introduction with this line: #info Name; Timezone; Sub-projects/Interest Areas 16:11:02 omfg 16:11:29 I'll go with devOps linuxmodder 16:11:32 decause, don't you use auto-spellcheck ? :) 16:11:37 decause: Heheh, yeah, I figured it was because it was pretty late. Should be an easy fix if you upload a new revision (should automatically update in the article). 16:11:44 did the meeting get started ? 16:11:48 linuxmodder: No spellcheck in Inkscape. :) 16:11:55 skamath, then come find decause or I after the meeting if you have further w?s 16:12:00 oh! I forgot that 16:12:00 c0mrad3: Yep, we're going right now! Feel free to introduce yourself with: #info Name; Timezone; Sub-projects/Interest Areas 16:12:01 #action decause fix the typo in gsoc-announce.png featured image 16:12:08 linuxmodder: inkscape does not have spellcheck... 16:12:11 #chair c0mrad3 16:12:11 Current chairs: c0mrad3 decause jflory7 linuxmodder sayan skamath trishnag 16:12:13 #goldenfeature 16:12:29 In terms of new announcements, that's all I had. 16:12:33 Anyone have anything else? 16:12:43 Otherwise, we can get into previous meeting action items. 16:12:49 jflory7, if you missed it I'm actioning myself for #21 16:12:50 #info Sayan Chowdhury; UTC+5:30; CommOps, Magazine, Ambassadors, Marketing 16:13:06 #info Tummala Dhanvi; UTC+5.30;CommOps,Ambassadors,Fedora Security 16:13:17 will tag up with kk4ewt and award3535 for best template ideas and have something for sure by net week's meeting 16:13:19 and I get the Secretary General badge. \o/ 16:13:39 linuxmodder: Feel free to leave that one open for some new folks who might be coming in from the Ambassadors side too. That ticket is flexible and might make a great starting project for someone who wants to get involved but doesn't know where to start. There's a lot of folks I've seen coming from Mozilla-y side of things who might have ideas for that too. 16:13:48 sayan++ c0mrad3++ 16:13:58 #topic Action items from last meeting 16:14:03 #link https://meetbot.fedoraproject.org/fedora-meeting/2016-03-08/commops.2016-03-08-16.55.html 16:14:06 jflory7, noted 16:14:08 #info * #info How This Works: Simple, completed action items from previous week are not brought up; action items that were either important tasks or have an unclear or incomplete status are brought up again for an update or to be given an #action again 16:14:16 #info === decause Let us know in #fedora-commops if the mailing list announcement about the Fedora Diversity Adviser position is ready to ship === 16:14:28 decause: Any idea if we're good to ship this one to announce@lists.fp.o? 16:14:38 tatica: is back, so I think we are gtg. let's vet with her one more time 16:14:43 * jflory7 nods 16:14:45 Sounds like a plan. 16:15:08 #action jflory7 / decause Follow up with tatica about the Diversity Adviser announcement email on announce@lists.fp.o 16:15:12 you two are major slackers :) 16:15:13 #action decause send a "greenlight?" email to tatica to push to announce lists 16:15:16 #info === [COMPLETE] jflory7 Draft up a GSoC announcement post confirming Fedora's participation and linking to the essential pages [DUE: March 11] === 16:15:21 linuxmodder: :P 16:15:23 #link https://communityblog.fedoraproject.org/fedora-accepted-google-summer-of-code-gsoc-2016/ 16:15:30 jflory7++ 16:15:36 jflory7++ 16:15:37 #info === [INCOMPLETE] jflory7 Begin writing small pieces of the Trac for Beginners article this week === 16:15:37 nice work on the GSoC announcement post 16:15:43 jflory7 did not complete, but Ryan (masetrax) is actively working on the Trac pieces and is going to claim Ticket #59 while he makes progress 16:15:53 masetrax++ 16:15:55 #info Trishna Guha; UTC+5:30; CommOps, Magazine, Tools 16:16:00 Wasn't as timely as I wanted, but it did the trick. Wait until you see the metrics on that one too. :) 16:16:02 trishnag++ 16:16:10 trishnag++ 16:16:11 c0mrad3: Karma for trishnag changed to 5 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:16:15 decause: He's also Australian so he has some troubles making it out to this meeting time. 16:16:21 #info === bee2502_ Finish up on the fedmsg2gource article, share with CommOps, and push out this week === 16:16:30 So, Bee updated on that before the meeting. 16:16:49 #info [COMPLETED] bee2502 drafted the article and it is pending review. jflory7 to edit and get it ready for this or next week, depending! 16:17:05 #action jflory7 Review and edit bee2502's fedmsg2gource article for the Community Blog 16:17:07 bee2502++ 16:17:19 #info === decause follow up with noriko/pravis about commblog announcement === 16:17:30 16:17:42 #action decause ping pravins/noriko 16:17:47 * jflory7 nods 16:17:48 #undo 16:17:48 Removing item from minutes: ACTION by decause at 16:17:42 : decause ping pravins/noriko 16:17:52 #undo 16:17:52 Removing item from minutes: INFO by jflory7 at 16:17:19 : === decause follow up with noriko/pravis about commblog announcement === 16:18:17 #action decause ping pravins/noriko about commblog announcement 16:18:20 #info === [INCOMPLETE] jflory7 Convert Etherpad => Tickets === 16:18:22 "ping with data" 16:18:24 #link https://etherpad.gnome.org/p/commops-power-sessions 16:18:28 #action jflory7 Convert Etherpad Power Session items into tickets in CommOps Trac 16:18:30 decause++ 16:18:42 So that's all previous action items from last meeting. 16:18:49 Let's get into the main focus of the meeting! 16:18:49 #topic Tickets 16:18:54 #link https://fedorahosted.org/fedora-commops/report/9 16:18:58 #info === Ticket #17 === 16:19:03 #link https://fedorahosted.org/fedora-commops/ticket/17 16:19:08 #info * "Interview Fedora's Diversity and Inclusion Advisor, tatica" 16:19:10 I'll #info this one 16:19:16 kk 16:19:22 this one is *so* close to being done 16:19:23 :) 16:19:47 #agreed This ticket should be good for completion this week. Earlier in the meeting, decause actioned following up with tatica to review the email announcement before pushing it to the announce@lists.fp.o list. Once it's announced, ticket can be closed! 16:19:51 #info === Ticket #29 === 16:19:58 #link https://fedorahosted.org/fedora-commops/ticket/29 16:20:03 #info * "G11n - proposal for the group revitalization" 16:20:20 So, were there any new updates to this one? 16:20:26 I know the due date for the CommBlog article is coming up soon. 16:20:31 March 23rd I think was the date 16:21:12 #link https://fedoraproject.org/wiki/G11N/vFAD_Translation#Prerequisite 16:21:24 this is an important item relating to the vFAD 16:21:27 I'm clueless as far as G11n goes but willing to help others draft something if needed 16:21:40 jflory7: is the g11n meeting tonight? 16:21:55 decause: Hmmm... I think it's every two weeks, and I don't think they met last week. 16:22:00 * decause checks fedocal 16:22:02 * jflory7 goes to Fedocal 16:22:12 in 13 hours decause 16:22:39 you two need to learn bot commands : ) .nextmeetings 16:22:43 #link https://apps.fedoraproject.org/calendar/i18n/ 16:22:45 hrmm, not on the g11n fedocal? 16:22:54 ahhh 16:22:54 Tomorrow, 6:00 UTC 16:23:02 nvm that is i18n 16:23:23 #link https://apps.fedoraproject.org/calendar/G11N/ 16:23:44 jflory7: so, 1am tonight 16:23:45 kk 16:23:54 decause: ...or is it 2am our time now? 16:24:04 DST is messing with me... 16:24:15 jflory7: it was midnight last time, so I /think/ it's one 16:24:19 DST-- 16:24:28 pravins: \o/ 16:24:32 Okay, confirmed, we are UTC-4 now, decause 16:24:35 0200EST jflory7 decause 16:24:43 what time is the g11n meeting? 16:24:49 T_T 16:24:52 0200EST decause 16:25:04 as in 13 hours from now 16:25:30 pravins: Welcome, welcome :) 16:25:33 UTC++ :D 16:25:45 skamath: Yeah, seriously. So much easier. :P 16:25:47 kk, enough timewizardry 16:26:12 #action decause follow up with pravins and noriko about g11n vFAD tasks on commops list 16:26:21 * jflory7 nods 16:26:23 Next ticket? 16:26:54 +1 16:27:09 #info === Ticket #39 === 16:27:10 #link https://fedorahosted.org/fedora-commops/ticket/39 16:27:16 #info * "CommOps and Google Summer of Code" 16:27:21 #link https://communityblog.fedoraproject.org/fedora-accepted-google-summer-of-code-gsoc-2016/ 16:27:41 \o/ 16:27:46 * decause highfives jflory7 16:27:47 I can't remember what there was to discuss on this ticket, though... 16:27:51 * jflory7 returns the high-five 16:27:51 it's done 16:27:56 fridayPowerSession++ 16:28:19 yep 16:28:23 I invited the mentors 16:28:27 now they need to accept 16:28:27 so 16:28:28 maybe 16:28:33 #action decause reping mentors 16:28:40 Cool. So it's a waiting game, then. :) 16:28:41 #action decause follow-up with applicant intro emails 16:28:58 we do need someone to update the onboarding calendar 16:29:01 jflory7, the fedmag pointer and commblog both are gtg iirc 16:29:01 but that is a sep ticket 16:29:11 #action jflory7 Create a ticket for updating the Onboarding Fedocal 16:29:29 jflory7: you can pretty much copy/paste the link/desc from power session etherpad 16:29:39 viorel++ 16:29:39 decause: Karma for viorel changed to 2 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:29:48 decause, lmk what needs updating I can hit it tonight 16:29:52 linuxmodder: Magazine article was not done, I didn't have the cycles to finish that... but I will today. I have some Magazine debt to repay before I disappear for the rest of the week. 16:30:17 So, I think next ticket, then 16:30:21 the ticket above was starting them not completing :) 16:30:27 We've got some bigger discussion-oriented tickets up next 16:30:45 is ms. mack here today? 16:30:56 Also, if anyone from GSoC has some questions, now would be a great time to ask too! 16:31:06 If there's a burning question specific to GSoC you want answered. :) 16:31:29 * linuxmodder is one of several mentors and is available here and email 24/7 16:31:30 GSoC, going once– 16:31:36 going twice 16:31:40 Going thrice– 16:31:42 #info === Ticket #49 === 16:31:42 skamath, ? 16:31:50 #link https://fedorahosted.org/fedora-commops/ticket/49 16:31:52 linuxmodder: I'm here. 16:31:54 #info * "[Onboarding Series] Infrastructure" 16:32:16 * skamath is thinking 16:32:18 So, decause, I believe you had some points about this one from Config Mgmt. Camp with puiter wijk. 16:32:21 skamath, was not sure if youhad GSoC ?s still but later i guess 16:32:35 jflory7: yes, I reckon I added those to the power-sessions etherpad 16:32:40 skamath: There will also be time at the Open Floor for questions if you have any later on. :) Same goes for the other GSoC people here! 16:32:46 linuxmodder: This is my first GSoC 16:32:56 decause: I think they just need to be extracted from the pad and placed on the ticket. 16:33:04 jflory7: nod nod nod 16:33:06 Probably related to my earlier action of ticketing from pad => Trac 16:33:19 Soon™ 16:33:26 :) 16:33:28 wfm 16:33:30 next 16:33:32 I have heard a lot about GSoC. I had a mentor named banas earlier. I have heard a lot about GSoC from him. (he did GSoC twice with fedora) 16:33:33 wfm 2 16:33:35 #info === Ticket #57 === 16:33:40 #link https://fedorahosted.org/fedora-commops/ticket/57 16:33:46 #info * "[Onboarding Series] CommOps!" 16:33:50 jflory7: hi :) 16:33:53 * jflory7 can't remember if we had notes for our own yet 16:33:56 * jflory7 digs into the Pad 16:34:12 Hi pravins! Did you catch the discussion earlier about Ticket #29? 16:34:14 jflory7: I think we just needed to file this one on the badges-trac 16:34:21 it's basically the bootstrapped series 16:34:24 so 16:34:40 maybe we create a new ticket, and then add the suggested decause art? 16:34:53 decause: Hmmm. Is Bootstrapped really specific to CommOps, though? 16:35:07 welcome bee2502_ :) 16:35:08 jflory7: decause ticket is almost fixed as we have now a good wiki page 16:35:13 * jflory7 thinks "Bootstrapped" would be better served as its own independent series from any sub-project 16:35:21 Hi bee2502_! 16:35:23 #chair bee2502_ 16:35:23 Current chairs: bee2502_ c0mrad3 decause jflory7 linuxmodder sayan skamath trishnag 16:35:31 .info bee2502 16:35:31 bee2502_: Error: You don't have the rss capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 16:35:36 .fasinfo bee2502 16:35:37 bee2502_: User: bee2502, Name: Bhagyashree Padalkar, email: bhagyashree.iitg@gmail.com, Creation: 2015-10-14, IRC Nick: bee2502, Timezone: Asia/Kolkata, Locale: en, GPG key ID: None, Status: active 16:35:40 bee2502_: Approved Groups: commops cla_done cla_fpca 16:35:46 c0mrad3: This ticket goes a little bit above and beyond just the wiki. :) It also goes into the Fedora Badges side of thing. 16:35:54 Hi everyone ! o/ 16:36:01 decause: We had some discussion about this at the last meeting, let me dig through the logs for half a minute 16:36:02 jflory7: or may be we create a new ticket for each sub team 16:36:21 c0mrad3: eventually yes 16:36:32 infra and commops were closest to getting theirs 16:36:36 .fasinfo dhanvi 16:36:37 c0mrad3: User: dhanvi, Name: Tummala Dhanvi, email: dhanvicse@gmail.com, Creation: 2015-04-30, IRC Nick: c0mrad3, Timezone: Asia/Kolkata, Locale: en, GPG key ID: None, Status: active 16:36:40 c0mrad3: Unapproved Groups: gitfedora-india test3 fedora-join commops 16:36:43 c0mrad3: Approved Groups: cla_done cla_fpca 16:36:44 17:56:36 #agreed CommOps badge ideas: (1) Wired In, for initial and continued activity on the mailing list, (2) [name idea], for getting sponsored in the CommOps FAS group and "officially" becoming a member, (3) [name idea], for submitting a pull request / committing code to github.com/fedora-infra or Pagure, (4) [name idea], for filing an issue on Fedora Hubs 16:37:05 jflory7: ok, I like these as ideas 16:37:06 decause: we have meeting tomorrow mostly on i18n side at 06:00 UTC 16:37:08 but 16:37:10 c0mrad3: Yeah, it would be a new ticket on the Fedora Badges Trac for each sub-project. 16:37:21 we have to be careful to not create any more new badges than necessary 16:37:26 badges-design is *tapped* right now 16:37:44 but more badges are cooler! 16:37:47 so unless we're making the graphics too (and properly filing the style guide, and going through proper review) those new badges are going to stall 16:38:09 c0mrad3: I *totally* agree, but we need more badge designers and contributors if we're going to up the number of badges 16:38:10 and next week we have meeting focused on translation in EMEA TZ. i think its 9pm CEST 16:38:22 decause: True, I can understand that. Well, my personal take on the "Bootstrapped" series is that it's good for all sub-projects and shouldn't be tied too closely to any sub-project in particular. For our own, I think establishing a unique set of criteria specific to CommOps is necessary to distinguish us as a sub-project as well. 16:38:22 +1 to being judicious with badge requests 16:38:23 pravins: thank you for the info 16:38:30 decause: Design is not part of commops, is it? 16:38:31 decause then we have work with the design/art team too! for this one 16:38:34 pravins++ 16:38:34 decause++ 16:38:34 sayan: Karma for decause changed to 29 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:38:54 #chair threebean 16:38:54 Current chairs: bee2502_ c0mrad3 decause jflory7 linuxmodder sayan skamath threebean trishnag 16:39:20 jflory7: +1 16:39:22 c0mrad3: they design/art team is one of the busiest teams in Fedora. Filling their plate with more stuff is something we need to be careful about. We want to help them, not just pile on more work :) 16:39:35 skamath: not directly 16:39:39 jflory7, technically we loosely do (re:design-team) as I see it 16:40:01 I definitely understand taking it slow on badge requests because there's a pretty large backlog there already and not enough people. But I think it's also important to not cut ourselves short with the badge series too. 16:40:04 meant skamath 16:40:09 design team is it's own team, and we share some members and tasks, but it is it's own group 16:40:12 This type of onboarding badge series is going to inevitably build the backlog bigger 16:40:28 So perhaps we also need to focus on some other strategy to train more badge designers or brainstorm other solutions 16:40:32 decause: then let's see how it goes, and I don't think I am good at designing either 16:40:37 jflory7: I agree, and we want to accompany our requests for more badges with some of our own efforts to help reduce the queue 16:40:40 also 16:40:43 Some sub-projects and groups don't have any badges for their sub-project whole others are very well-represented 16:40:46 it's just a twinkle in the eye of the design team righ tnow 16:40:48 but 16:40:56 there was talk of having a badges FAD in July-ish 16:40:56 my designing skills suck but I like the packaging it up part 16:40:57 decause: +1 to helping with our requests too from a design perspective 16:41:02 badgesFAD++ 16:41:02 badgesFAD++ 16:41:06 yes 16:41:07 quick question do we have any common members in commops and design team ? decause 16:41:13 it would likely be in westford boston 16:41:22 c0mrad3: I don't think we *distinctly* do. 16:41:25 c0mrad3: nb is both, I reckon 16:41:28 c0mrad3: It would be cool if we did :) 16:41:32 Oh yeah, nb is one, I forgot. 16:41:33 at least badges-design 16:41:36 linuxmodder: I might help you with that! 16:41:49 c0mrad3, find me post meeting then pls 16:41:51 * decause is like lvl 5 inkscape user too 16:42:01 jflory7: I agree let's learn some gimp and some other tools :) 16:42:05 but not officially a design team member 16:42:07 jflory7: i missed #29 discussion, i will read log later. thanks :) 16:42:10 badges-designer, and badges-admin 16:42:28 Is GlitterGallery coming up anytime soon? I believe it will make collaboration a lot more easier. 16:42:32 pravins: basically we just wanted to check in with you about the vFAD and commblog 16:42:42 skamath: I think glittergallery is done? 16:42:45 c0mrad3, linuxmodder: There are some great resources in place already for helping with badge design. Before jumping in head first, it's important we connect anyone willing to help with badges to those resources. There's a lot of different small requirements to designing badges, and the Design Team did a great job of documenting the entire badge creation process. 16:42:47 like, shipped and we use it? 16:43:13 skamath: the badges style guide and templates are amazing 16:43:15 decause: Isn't too far of a trip for me, technically, although I don't know how much of a "badge designer" you could really call me. :) 16:43:16 I will do some progress tomorrow, will update on ticket. 16:43:40 linuxmodder: but bear in mind I am a programmer and security enthusiast, never done design part ;) so I am total noob in it 16:43:41 pravins: I just want to make sure we get the commblog updated without missing any deadlines 16:43:50 pravins: Sounds good -- the main thing we wanted to check in was the CommBlog update for the G11n vFAD. I think we had agreed on March 23rd as the tentative deadline for the first draft. 16:43:58 c0mrad3, much the same here :) 16:44:17 my drawing skills and such dropped off years ago with loss in cycles for it 16:44:36 we'll get there, a big help is also just coming up with concepts for the badges 16:44:37 +1 16:44:44 Okay, 15 minute time check... anything we want to put down in this ticket for certain? 16:44:55 jflory7: linuxmodder let's have a look at the resources and give a shot before asking for the design team time! 16:45:12 Maybe we just focus on getting the "Bootstrapped" series done in the immediate sense and then readdress ours after? 16:45:16 c0mrad3: +1 from me. :) 16:45:20 Bad connection :/ 16:45:26 We are planning for vFAD from 21-27, so only this week remained for commblog + tickets. I will start pinging you all again from tomorrow :) 16:45:26 +1 jflory7 16:45:32 decause: I mean, is it not going to be setup as a Fedora subdomain for the fedora design? 16:45:42 Will discuss again with BNE guys noriko and aeng. 16:45:43 skamath: No worries – thanks for being here nonetheless. :) 16:45:47 jflory7: yeah, I think I could deliver a badge design, but it is pretty low on my priority totem pole 16:45:47 praveenkumar: Excellent! 16:46:10 pravins: yes, please do. we want to make sure we get the info in there asap 16:46:10 * pravins apologies for mixing up discussions. 16:46:13 decause: Acknowledged. So maybe we'll put our own on the backburner for a bit and look at getting the pre-existing one done and implemented. 16:46:21 So, let's put a proposal to vote here. One second... 16:46:33 decause: yes then let's continue with other tickets 16:46:37 skamath__: what do you mean subdomain? 16:47:14 #proposed The Fedora Design team is pretty tied up in cycles so we want to avoid putting any more work requests on them than is absolutely necessary. Planning to focus on the "Bootstrapped" badge series as a general "Fedora 101" sort of series and readdress the CommOps-specific badge series later on in the future. 16:47:15 +1 16:47:21 I meant, set up for production for fedora-design team to collaborate. 16:47:23 decause: I think skamath meant subteam for design in commops :) in which jflory7 linuxmodder and me will be the members :P 16:47:29 (If this is your first time at our meetings, you can vote on this with +1 / +0 / -1) 16:47:39 +1 16:47:45 +1 16:47:49 +1 16:47:53 +1 16:47:58 Going once... 16:48:01 Twice... 16:48:02 decause, as in design.fp.o is what he means i think 16:48:04 +1 16:48:05 Thrice... 16:48:08 #agreed The Fedora Design team is pretty tied up in cycles so we want to avoid putting any more work requests on them than is absolutely necessary. Planning to focus on the "Bootstrapped" badge series as a general "Fedora 101" sort of series and readdress the CommOps-specific badge series later on in the future. 16:48:15 skamath: https://badges.fedoraproject.org 16:48:18 And that's all for tickets! 16:48:19 #topic Wiki Gardening 16:48:23 #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ] 16:48:24 +1 to prop 16:48:26 #undo 16:48:26 Removing item from minutes: ACTION by jflory7 at 16:48:23 : NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ] 16:48:29 #nick NewMembers 16:48:29 +1 16:48:31 #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ] 16:48:39 #help The Fedora Join page could use some cycles for tidying up, reformatting, and general cleanup. It's a well-visited page and it's important the information on this page is current and correct. 16:48:45 #link https://fedoraproject.org/wiki/Join 16:48:51 #help The Marketing team is in the process of working on Fedora 24 talking points and extra hands are needed to organize some of the key talking points for this upcoming release . 16:48:56 #link https://fedoraproject.org/wiki/Fedora_24_talking_points 16:48:59 #link https://fedoraproject.org/wiki/Fedora_24_talking_points 16:49:15 #action decause reping server list for F24 talking points (due:today) 16:49:16 Both of these above wiki gardening tasks are great places to start for someone looking for something to do. 16:49:24 jflory7: I agree about the cleanup of join page 16:49:30 jflory7, the 24_taling+points is a joint docs ticket no? 16:49:33 #action jflory7 Create tickets for the two wiki gardening tasks of the Join page and F24 Talking Points 16:49:41 linuxmodder: Docs team? 16:49:47 linuxmodder: Talking points is a Marketing thing. 16:49:59 linuxmodder: talking points is not technically docs team, usually marketing 16:50:06 then Docs has one out for same thing then 16:50:22 linuxmodder: well, as long as we're hacking on the same page, that is fine 16:50:28 but if it is diff pages, then we have a problem :P 16:50:31 jflory7: then I can take up the wiki gardening of the join page 16:50:31 Hmmm. Seems like Docs and Marketing could possibly use a little better talking unless the Docs stuff is being packaged somewhere in the actual docs.fp.o place. 16:50:37 linuxmodder: if you find a ticket, let us know, so we can consolidate 16:50:42 decause, will check today and advise 16:50:49 linuxmodder: thank you 16:50:56 c0mrad3: Cool! Let's get a ticket created for that so we can set you to the task. :) Want to follow up on that after the meeting in #fedora-commops? 16:51:04 we're happy to hack on 'upstream' tickets in other subprojects here in commops 16:51:11 jflory7, as a RN beta of sorts 16:51:19 jflory7: ack I will follow on that ! 16:51:26 c0mrad3: Awesome, let's set it in stone. :) 16:51:50 #action c0mrad3 / jflory7 Follow up in #fedora-commops after the meeting about making a ticket for the "Join" wiki page gardening and come up with ideas about what needs cleaning up specifically 16:51:53 c0mrad3++ 16:51:59 Okay, wiki gardening... anything else? 16:52:02 * jflory7 notices the time 16:52:06 Wiki gardening, going once... 16:52:11 8 mins 16:52:13 Going twice... 16:52:20 #info decaus says add "== headers ==" to the join page for instance 16:52:20 Going thrice... 16:52:28 #topic Community Blog 16:52:35 decause, easy peasy fix 16:52:50 jflory7: rapid fire :) 16:52:54 Okay, for those of you joining us for the first time, here's a "lightning round" of stats about the CommBlog. Afterwards, we have a bit of discussion. :) 16:52:56 Here we go! 16:52:57 #info === This Week in CommBlog === 16:53:00 decause, as separators right? 16:53:01 #info (1) "Modularity Use Case: Application Independence" 16:53:06 #link https://communityblog.fedoraproject.org/modularity-use-case-application-independence/ 16:53:10 #info Total Views (Mar. 09 - Mar. 15): 161 16:53:15 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1122 16:53:21 #info (2) "Taskotron Results to Notifications" 16:53:25 #link https://communityblog.fedoraproject.org/taskotron-results-notifications/ 16:53:30 #info Total Views (Mar. 10 - Mar. 15): 82 16:53:35 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1088 16:53:40 #info (3) "Fedora accepted to Google Summer of Code 2016" 16:53:46 #link https://communityblog.fedoraproject.org/fedora-accepted-google-summer-of-code-gsoc-2016/ 16:53:50 #info Total Views (Mar. 12 - Mar. 15): 873 (!!) 16:53:54 nice 16:53:55 ^ did we even get on social media yet?! 16:53:56 jflory7++ commops++ 16:53:57 yeah, nice 16:54:00 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1174 16:54:00 :) 16:54:04 #info === Coming Up in CommBlog === 16:54:08 #info (1) "Campus Ambassadors Initiative" 16:54:09 jflory7, my blog and associated social media 16:54:13 #link https://communityblog.fedoraproject.org/?p=759&preview=1&_ppp=6a119154dd' 16:54:20 #link https://lists.fedoraproject.org/archives/list/campus-ambassadors@lists.fedoraproject.org/thread/TQJS6SX4EMHOSF3O7R3SZNICW7B7IV5I/ 16:54:24 #info There is ongoing discussion to further develop this article. Will also be shared with FAmNA for review before being posted. Since this article will be shared on many feeds, it's important to make sure all the "ducks are in a row" before publishing. 16:54:26 * decause posted to personal channels too 16:54:28 #info (2) "DevConfCZ 2016: Event Report" 16:54:32 #link https://communityblog.fedoraproject.org/?p=1027&preview=true 16:54:37 #info (3) "Fedora Essentials: Trac for Beginners" 16:54:42 #link https://communityblog.fedoraproject.org/?p=1025&preview=true 16:54:47 #info (4) "I contributed ! 2015 Fedora Contributions Video using Gource(fedmsg2gource?)" 16:54:53 #link https://communityblog.fedoraproject.org/?p=722&preview=true 16:54:57 #action decause ship DevConf.cz article (due: Friday) 16:54:57 ^ pending review :) 16:55:05 Okay, and that's all the updates I have! 16:55:09 srsly tho 16:55:14 devconf must ship this week 16:55:18 Did we actually get the GSoC stuff on social media yet? 16:55:21 I can't remember! 16:55:21 I have a question about campus ambassadors ; should they be a ambassadors before becoming a campus ambassadors ? 16:55:29 jflory7: action to post to social-media 16:55:31 I know it's on Reddit and Telegram broadcast group. 16:55:34 decause: Let me check first 16:55:40 I have a few cycles tonight decause I'll review devconf 16:55:40 we talked with bkp, he said that is the official workflow 16:55:48 decause: Oh, no, it's there 16:55:51 linuxmodder: it's not totally written yet :/ 16:55:54 have to add more "meat" 16:55:55 Went up yesterday, or at least on Twitter 16:56:03 my last report actually got a "quote of the week" in LWN 16:56:10 jflory7, posted on my blog + my fb / G+ /twitter /LI which is no small audience :) 16:56:12 so I feel better about dumping major cycles into the reports now 16:56:14 doesn't make sense about the becoming first one ambassadors and then campus ambassadors 16:56:28 linuxmodder: Nice, every bit helps :) 16:56:43 decause: Looks like Facebook needs some love 16:56:49 And Google+ 16:56:50 jflory7, ALL my blog posts hit those outlets by default 16:56:55 jflory7: nod nod 16:56:57 linuxmodder: I mean on the official channels 16:57:12 #action jflory7 Follow up with bkp for the GSoC post on Facebook / Google+ 16:57:14 I actually had to report some comments yesterday on the Fedora FB page :( 16:57:18 :( 16:57:27 it was a compromised account, not malicious, but still 16:57:33 c0mrad3: Yes! So that is actually a discussion we are having. 16:57:41 c0mrad3: Before, it was Ambassador first, then Campus Ambassador 16:57:53 c0mrad3: We are looking at making it so one can become a Campus Ambassador first too 16:57:53 c0mrad3, its not a hard req atm but the idea was to consolidate member reqs 16:58:01 firefox has a awesome thing for this one we called it firefox friends https://friends.mozilla.org/ 16:58:03 And then become a full Ambassador if they please 16:58:04 jflory7: the EDU objective is under major review by the council right now 16:58:08 and this ties directly into that 16:58:20 decause: Ahh, I missed all discussion at the Council meeting about that. 16:58:23 c0mrad3++ 16:58:23 skamath: Karma for dhanvi changed to 3 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:58:25 I have some big decisions to make in the next week as to whether I'm going to continue as Objective Lead 16:58:26 * jflory7 needs to catch up on emails and logs... 16:58:30 * tatica just arrived from the bank 16:58:35 tatica: o/ 16:58:35 tatica++ 16:58:44 jflory7, yeap, I'm ready to go with the interview, lets kick it out 16:58:46 jflory7: you got a link to the interview article? 16:58:52 nm 16:58:54 :) 16:58:55 #chair tatica 16:58:55 Current chairs: bee2502_ c0mrad3 decause jflory7 linuxmodder sayan skamath tatica threebean trishnag 16:58:56 tatica++ 16:58:56 :) 16:58:58 tatica++ 16:59:06 hi tatica 16:59:17 zodbot++ for all the hardwork :D 16:59:18 I <3 u all! 16:59:22 Okay, so I think this is it for CommBlog. Let's get to Open Floor and do the real talk about meeting time... 16:59:23 .tatica 16:59:23 I love tatica, you love tatica, WE ALL LOVE TATICA! 16:59:25 tatica++ 16:59:26 jflory7: do we already have a draft for the mail-lists for me to send? 16:59:26 skamath: Karma for tatica changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:59:35 I think it makes scence if they first become a fedora campus ambassadors and then a full ambassadors 16:59:37 decause: Yep, on an Etherpad, digging 16:59:40 #topic Open Floor 16:59:52 we only 1 min left :P 16:59:53 So, meeting times! DST! 16:59:57 decause, were you able to get to the websites team about the survey? 17:00:12 bee2502_: I don't think anyone is after us, so we should be okay to go over juuuust a little bit. :) 17:00:26 tatica: yes I was! 17:00:30 awesome then ! 17:00:44 jflory7: I agree with that and the team looks active to :) 17:00:45 since it is not a static site, we wouldn't be able to do the same approach as the budget site 17:00:47 decause, tatica (interview): https://etherpad.gnome.org/p/announce-list-tatica-interview 17:00:48 however 17:00:50 next meeting in here is in the early AM ( i18n is next in here at 06UTC) 17:01:05 we are going to look into piggy-backing on a paid instance for hosted limesurvey 17:01:11 linuxmodder, thank you 17:01:15 fantastic 17:01:25 we already have one in OSAS, it is FOSS, and will make deployment easy 17:01:36 tatica, I still owe you some edits to the survey too 17:01:42 I was asked to take a look to the Armenian issue, so I'll be reading the backlogs about it 17:01:42 tatica: I'll be sure to cc you on those conversations (new action items on my plate from meetings at EoB yesterday) 17:01:47 decause: let's use the FOSS one instead of paying 17:01:49 linuxmodder, yeah! 17:01:58 c0mrad3: limesurvey IS FOSS :) 17:02:06 it's just hosted 17:02:09 For the meeting time: Because of the Daylight Savings shift in the US, the new meeting time 17:00 UTC correlates to 1:00pm US EST (where it was 12pm before). Do we want to stick to the UTC time or do we want to maintain the 12:00pm US EST time for the US folks? Who has conflicts with either time? What works better? 17:02:13 c0mrad3++ 17:02:15 like gandi.net 17:02:15 decause, please do so. I will be driving like crazy for the next 6 days, yet, I will be reading emails while I'm on the road 17:02:28 FOSS, fully open source but hosted options 17:02:28 tatica: hopefully in between trips ;) 17:02:33 * c0mrad3 searching about limesurvey 17:02:39 decause++ 17:02:40 decause, yeah... I'm the driver, husband is the DJ u_U 17:02:47 #link https://www.limesurvey.org/ 17:02:58 tatica: Hey, you and me both for the driving thing. 17:03:02 * Heh, 17:03:11 * decause just did 12 hours to rollywood this weekend 17:03:22 that isn't 6 days tho :P 17:03:23 ok 17:03:27 rollywood being raligh? 17:03:34 That reminds me of a personal update I need to give after we settle on meeting time 17:03:35 limesurvey++ WYSIWYG editor is awesome :D 17:03:39 something I think he married me just because he needed a driver... but oh well 17:03:39 #action decause follow-up with OSAS about hosted limsurvey instance, cc tatica 17:03:45 tatica: :P 17:03:53 I've worked with limesurvey, so I think it's fantastic 17:04:04 great! 17:04:07 For the meeting time: Because of the Daylight Savings shift in the US, the new meeting time 17:00 UTC correlates to 1:00pm US EST (where it was 12pm before). Do we want to stick to the UTC time or do we want to maintain the 12:00pm US EST time for the US folks? Who has conflicts with either time? What works better for the people not affected by Daylight Savings? 17:04:35 both are fine for me jflory7 now that I know the changed time 17:04:38 then let's stick with limesurvey then 17:04:45 wfm utc or dst 17:04:51 time.me will help ;) 17:04:57 anything that works, works for me 17:05:15 Personally, I like the 12pm US EST time (i.e. 16:00 UTC) 17:05:17 since we have many folks from APAC here with us, I bet the earlier time works better? 17:05:31 bee2502_: ? 17:05:35 pravins: ? 17:05:37 I'm not hearing any -1s to the 16:00 UTC time as of yet 17:05:42 * linuxmodder has to bounce tho see everyone next week (GSoC folks feel free to email me or get me in -commops -summer-coding later) 17:05:46 linuxmodder: See ya! 17:05:49 linuxmodder++ 17:05:58 decause yes, earlier the better 17:06:00 let's stick with UTC 17.00 17:06:06 jflory7: is this right? http://time.is/ET 17:06:13 Both are fine with me. But I'd prefer 16:00 UTC :) 17:06:14 This time is good. 17:06:18 skamath: Indeed. 17:06:21 +1 for 16:00 17:06:29 Okay, let's actually put this to a +1 / -1 vote. Proposal: 17:06:36 ok, let's use DST, and then /maybe/ not 'fall back' in the fall? 17:06:44 #proposed New meeting time: 16:00 UTC <=> 12:00pm US EST 17:06:45 +1 17:06:48 +1 17:06:54 +0 17:06:55 +1 17:06:58 +1 17:06:58 +1 17:06:59 -1 17:07:00 +1 17:07:05 +1 17:07:13 #agreed New meeting time: 16:00 UTC <=> 12:00pm US EST 17:07:28 jflory7, ++ 17:07:31 #action jflory7 Update Fedocal entry for the meeting time 17:07:31 +1 17:07:47 skamath++ 17:07:48 decause: Karma for skamath changed to 2 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:07:51 Okay, so that's all the official business I think. 17:07:52 jflory7++ 17:07:52 trishnag: Karma for jflory7 changed to 35 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:07:57 Whooo, cookies :) 17:08:01 On another note--- 17:08:21 * c0mrad3 linuxmodder: sure I will ping you about gsoc 17:08:29 Next week is looking pretty hectic for me. At the last minute, I decided I'll be going home next week and driving back up the coast 17:08:42 jflory7: good to know 17:08:42 I'm not sure if I'll be able to be here for next week's meeting as of yet. 17:08:54 Either I'll be in the air, in an airport, or home. 17:08:58 We'll see how it goes. 17:09:08 jflory7: kk, we'll have your back :) 17:09:11 let's end the meeting and take it to commops channel :) 17:09:13 :) 17:09:15 c0mrad3: +1. 17:09:15 jflory7++ your next weeks' share of Karma ;) 17:09:19 Going once... 17:09:22 Going twice... 17:09:27 Going thrice... 17:09:39 Thanks for coming out to the meeting today, everyone! See you in #fedora-commops... 17:09:40 jflory7: yes we are there to have your back :) 17:09:40 #endmeeting