16:55:32 #startmeeting Fedora CommOps (2016-02-23) 16:55:32 Meeting started Tue Feb 23 16:55:32 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:55:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:55:32 The meeting name has been set to 'fedora_commops_(2016-02-23)' 16:55:36 #meetingname commops 16:55:36 The meeting name has been set to 'commops' 16:55:42 #topic Agenda 16:55:51 #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-23 16:55:56 #info 1. Roll Call 16:56:01 #info 2. Announcements 16:56:05 #info 3. Action items from last meeting 16:56:10 #info 4. Tickets 16:56:34 #info 5. Wiki Gardening 16:56:39 #info 6. Community Blog 16:56:43 #info 7. Open Floor 16:56:47 #topic Roll Call 16:56:52 #info Name; Timezone; Sub-projects/Interest Areas 16:56:57 .hello jflory7 16:56:58 jflory7: jflory7 'Justin W. Flory' 16:57:12 #info Justin W. Flory; UTC-5; CommOps, Marketing (Magazine), Ambassadors, Join, and more 16:57:21 We'll let roll call roll for a bit :) 17:00:01 .hello jbwillia 17:00:01 Southern_Gentlem: jbwillia 'Ben Williams' 17:00:27 o/ 17:00:30 #chair Southern_Gentlem 17:00:30 Current chairs: Southern_Gentlem jflory7 17:01:01 We'll wait five more minutes for anyone else to come in 17:01:12 #chair bee2502_ 17:01:12 Current chairs: Southern_Gentlem bee2502_ jflory7 17:01:14 .info bee2502 17:01:14 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. 17:01:35 .fas bee2502 17:01:36 bee2502_: bee2502 'Bhagyashree Padalkar' 17:01:48 .hello bee2502_ 17:01:49 Southern_Gentlem: Sorry, but you don't exist 17:01:56 .hello bee2502 17:01:59 Southern_Gentlem: bee2502 'Bhagyashree Padalkar' 17:02:34 hi,everyone :) 17:02:55 Hi hi! 17:03:18 I'll ping decause really quick 17:04:27 #info bee2502 UTC +5.30 Metrics, Elections, Badges , CommBlog 17:05:07 .hello keekri 17:05:09 keekri: keekri 'Keerthana Krishnan' 17:05:15 #chair keekri 17:05:15 Current chairs: Southern_Gentlem bee2502_ jflory7 keekri 17:05:24 .hello decause 17:05:25 decause: decause 'Remy DeCausemaker' 17:05:29 #chair decause 17:05:29 Current chairs: Southern_Gentlem bee2502_ decause jflory7 keekri 17:05:29 * decause was deep in drafts 17:05:32 thanks all 17:05:40 Hi, keekri! 17:05:45 * decause waves to errbody 17:05:46 decause: No worries. :) 17:05:54 We're five after, so let's go ahead and press on to the agenda 17:05:59 hi jflory7! decause! bee! 17:06:02 For reference: https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-23 17:06:05 taker-away jflory7 17:06:07 :) 17:06:11 #topic Announcements 17:06:24 #info === No tickets closed in the past week === 17:06:31 Anyone have anything to add? 17:06:34 Yes 17:06:58 Shoot. :) 17:07:03 Outreachy application period is open for summer. We have one position for kernel hacking avialable. 17:07:35 eol 17:07:45 #info Outreachy application period is open for summer. We have one position for kernel hacking available. 17:07:50 decause++ 17:07:52 cool cool. 17:07:58 And GSoC will get its own area of discussion 17:08:02 Anything else? 17:08:04 #link https://fedoraproject.org/wiki/Outreachy/2016 17:08:19 .hello fale 17:08:20 jflory7: that is all for me 17:08:20 fale: fale 'Fabio Alessandro Locati' 17:08:25 #chair fale 17:08:25 Current chairs: Southern_Gentlem bee2502_ decause fale jflory7 keekri 17:08:26 * decause waves to fale 17:08:32 Announcements, going once-- 17:08:38 Going twice-- 17:08:40 * fale waves back 17:08:48 *** F23-20160222 updated lives available: http://tinyurl.com/live-respins (.iso & .torrent) Thanks to the community of maintainers and seeders. Addt'l seeders always welcome. *** 17:08:49 Going thrice-- 17:08:57 Welcome, fale! :) 17:09:00 Southern_Gentlem++ 17:09:28 Alright, moving over to last week's action items: 17:09:29 #topic Action items from last meeting 17:09:35 #link https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-16/commops.2016-02-16-16.55.html 17:09:36 Guys, my connection is a bit spotty, did you get a link I just put ? 17:09:49 keekri: I didn't see anything there. 17:09:54 #info How This Works: Completed action items from previous week are not brought up; action items with unclear or incomplete status are brought up again for an update or to be given an #action again 17:10:06 #link https://fedoraproject.org/wiki/CommOps/Join 17:10:13 keekri++ 17:10:16 yeah! 17:10:17 nice 17:10:21 keekri: Yep, see it now. :) keekri++ 17:10:29 I had said, We Have A Join Page Draft People! :D 17:10:50 yaay ! keekri++ 17:10:59 :D 17:11:11 Oh, wow, it's done! Let's definitely get that in Ticket #37. We'll hit that one in just a few. :) 17:11:19 nod nod 17:11:21 #info === jflory7 Start draft on Trac 101 article in Community Blog === 17:11:27 #info Article draft created, content not started; still intending for completion by end of month 17:11:33 #info === decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck === 17:11:38 Any updates? 17:12:05 * Southern_Gentlem fixing mailing list link on join commops page 17:12:10 jflory7: onboarding series hackfest end of this week. I'm budget site sprinting for now. 17:12:17 Southern_Gentlem++ 17:12:27 Cool cool. Will re-action to you 17:12:30 * fale prepared the page https://fedoraproject.org/wiki/Python_Events_2016 17:12:31 jflory7: maybe thursday? 17:12:35 fale++ 17:12:39 #action decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck 17:12:40 saw that! nice work! 17:12:42 fale++ 17:12:45 Southern_Gentlem++ 17:12:45 keekri: Karma for jbwillia changed to 4 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:12:45 Southern_Gentlem++ 17:12:49 #undo 17:12:49 Removing item from minutes: ACTION by jflory7 at 17:12:39 : decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck 17:12:52 fale++ 17:12:54 keekri: Karma for fale changed to 6 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:12:55 jflory7: make that due friday plz 17:12:59 * jflory7 nods 17:13:14 press 'up' key, and then add 'due friday' 17:13:16 :P 17:13:18 karma for jbwillia please :) 17:13:23 #action decause Create an onboarding series ticket on CommOps Trac for Fedora Infra, based on cfgmgmtcamp slide deck [DUE: Friday, 2/26] 17:13:25 #info === decause/fale/pravins schedule a g11n vFAD organizing meeting for 2/22 or nearby === 17:13:25 jbwillia++ 17:13:31 jbwillia++ 17:13:40 decause: I think this one can be deferred to Ticket #29 17:13:47 Was intended for today's meeting, I believe 17:13:53 kk, keep it rollin 17:13:55 I opt we skip ahead and save discussion for the ticket 17:13:55 :) 17:13:57 +1 17:14:01 #info === keekri open a ticket for updating join/intro pages in the wiki === 17:14:08 keekri: :) 17:14:10 keekri: Saw your email this morning, haven't had a chance to reply back yet. 17:14:38 We can get on that my today / your tomorrow. 17:15:06 jflory7: it's ok, kinda my fault too.. 17:15:12 #action jflory7 Get back to keekri's email about the Join pages Trac ticket 17:15:24 keekri: No worries, we'll get it done. :) 17:15:29 #info === decause update onboarding (bootstrapping) ticket on fedora-badges trac. add concept proposal... === 17:15:33 Cool! :) 17:15:34 Related to earlier line, decause? 17:15:52 * mailga around but still working. I may not pay attention enough..... 17:15:58 jflory7: not done, maybe will do this by friday, likely will do it next week 17:16:09 #chair mailga 17:16:09 Current chairs: Southern_Gentlem bee2502_ decause fale jflory7 keekri mailga 17:16:14 I want all of the onboarding steps tickets first on commops trac 17:16:23 mailga: No worries, if you can't stick around, we'll get the minutes out too :) 17:16:26 * jflory7 nods 17:16:27 lets see how for we get with hacksession 17:16:36 decause: Will reaction verbatim for Friday 17:16:42 kk 17:16:57 #action decause update onboarding (bootstrapping) ticket on fedora-badges trac. add concept proposal... [DUE: Friday, 2/25] 17:17:03 Okay, that's all action items. 17:17:05 To tickets! 17:17:09 #topic Tickets 17:17:15 #link https://fedorahosted.org/fedora-commops/report/9 17:17:28 #info === Ticket #2 - https://fedorahosted.org/fedora-commops/ticket/2 === 17:17:34 #info * "Request for a tool to converge tickets from the main teams to commops ticketing" 17:17:37 This ticket is beginning to stall. Do we want to put a request into motion for a tool to be developed for this? Or is it better to close the ticket as "wontfix"? What do we want to do? 17:17:44 decause: Saw your comment on the ticket pre-meeting 17:18:08 jflory7: yeah, see my response 17:18:12 I replied. ;) 17:18:16 kk, word 17:18:20 Anyways-- 17:18:33 My question was how would this info be relayed to us by the sub-projects? 17:18:41 short description goes in the #halp message 17:18:49 Also, context to this discussion was decause's idea in the ticket, comment towards the bottom 17:18:50 jflory7: via commblog draft 17:19:03 #link https://fedorahosted.org/fedora-commops/ticket/2#comment:5 17:19:14 I see, so the tooling for sub-projects to get info on our radar is with Meetbot #help and CommBlog. 17:19:22 And the regular channels like IRC and mailing list 17:19:38 yeah, in general 17:19:39 * mailga thinks there's still the problem of duplicates. If folks don't use two tickets something could be lost. 17:20:01 in specific, i want to advertise that we are tracking the #halp fedmsg's, assuming that we actually track them ;) 17:20:09 this is likely a good job for the metrics team 17:20:13 mailga: decause's suggestion was to avoid two tickets. Instead, we would work in the specific sub-project's Trac and use things like MeetBot and CommBlog to help stay on tack 17:20:15 who already grok fedmsgs 17:20:16 * on track 17:20:28 jflory7: mostly right 17:20:50 decause: Yeah, I think finding a way to better track the #help messages would be useful to broadcast to the rest of Project that CommOps is listening 17:20:55 jflory7: decause this could be the perfect solution, not sure the easiest. 17:21:46 so, instead of copying over all the tickets from an upstream trac to the commops trac (which seems like what was proposed) I suggested that teams (while having their IRC meetings) use the #help or #halp tag, to link to a ticket, and provide a description. This will "get it on our radar" because we (eventually) are going to have a tool that aggregrates all of those help messages and adds them to a queue of soem kind that we can then triage as comm 17:21:58 * jflory7 wonders... do we want something like an email to the list at the end of a group's meeting with any #help messages? Or do we want a website to serve this info? 17:22:36 I think best course of action for today is determine how we want to handle the #help data and make sure that it gets to us, and isn't accidentally missed in IRC 17:22:38 jflory7: we already have datagrepper and fedmsg. perhaps posting those messages (raw at first) to a mailing list would be good? At least having them show up in a file somewhere. 17:22:54 decause: I like the idea of automated emails to the list, personally 17:23:11 Like at the end of a meeting, all #help messages with a link to the møte log could hit our list 17:23:18 jflory7: I don't /think/ the #help messages are too noisey 17:23:21 I think trying to get something like that running would be preferential 17:23:36 decause: I don't think so either, as bee2502_ showed, they are one of the least used commands too. 17:23:44 jflory7: yeah, and python's smtplib or something simliar would be a pretty low barrier to entry 17:24:04 Probably not too difficult to program with the existing infrastructure at our disposal. 17:24:07 a simple tweak to the zodbot is likely the way to go? 17:24:17 * jflory7 is thinking so 17:24:23 Any other comments to add? 17:24:28 Otherwise, let's put it to vote as a proposal 17:24:34 zodbot already emails the logs places, maybe we could have it parse out the help messages and email those specifically to us? 17:24:41 orrrrrr 17:24:55 we can use FMN to give us IRC notifications AND email notifications 17:25:01 FMN is the tool to use I reckon 17:25:03 yes 17:25:23 FMN ? 17:25:44 I'm not familiar with FMN either 17:25:51 Or maybe I am, but didn't know what its name was 17:26:00 https://apps.fedoraproject.org/notifications 17:26:04 #link https://apps.fedoraproject.org/notifications 17:26:05 Ahhh, that 17:26:19 the only issue is that I think you can only sign up for emails related to a fAS account 17:26:28 Had a sneaking suspicion that's what it was 17:26:48 perhaps we can create a new FAS (CommOpsBot or something) and list it's mailing address as the commops mail list as a hack? 17:26:52 this is a hack though 17:26:55 but would be easy :) 17:27:03 let's move on though, and update the ticket with ideas from today 17:27:09 we're at half past now 17:27:18 whatever we decide, we should def advertise on the commblog afterwards 17:27:25 Yeah, this sounds doable to me. 17:27:32 Let's discuss technical details in ticket or on the list 17:27:35 Let's vote on this proposal real fast 17:27:36 #proposed To help keep #help MeetBot messages on CommOps radar, the best course of action is to begin developing or request a tool that will take those notifications at the end of a meeting and email a list of #help messages and møte URL to CommOps mailing list 17:27:37 +1 17:27:41 SideNote: Event Report Hack Session will be hacksession #2 this week :P 17:28:07 +1, with the addition of "posting to IRC" if possible 17:28:16 Will revise proposal to include that 17:28:36 +1 17:28:44 Going once-- 17:28:49 Going twice-- 17:28:56 Going thrice-- 17:29:00 #agreed To help keep #help MeetBot messages on CommOps radar, the best course of action is to begin developing or request a tool that will take those notifications at the end of a meeting and email a list of #help messages and møte URL to CommOps mailing list and IRC 17:29:07 info === Ticket #11 - https://fedorahosted.org/fedora-commops/ticket/11 === 17:29:10 #info === Ticket #11 - https://fedorahosted.org/fedora-commops/ticket/11 === 17:29:15 #info * "Infra + Websites Collaboration: Budgeting Site" 17:29:19 Three months since ticket was last updated. decause want to give any updates on the status of this or how other CommOpsers can help? 17:29:25 Mostly an update to be given by decause :) 17:30:23 Some extra comments were added to the ticket earlier as well 17:30:36 * decause digs for comments link 17:30:52 #link https://fedorahosted.org/fedora-commops/ticket/11#comment:5 17:31:07 tl;dr - I have a working dev encvironment 17:31:33 Heheh, I missed the screenshot 17:31:37 anyone who wants to help can clone the websites repo, and check out the 'budget' branch 17:31:43 NOTE 17:32:00 the master branch of the websites repo is used in production... 17:32:01 so 17:32:10 DO NOT HACK ON THE MASTER BRANCH ZOMG 17:32:14 :P 17:32:18 heheh 17:32:19 I have never been more scared of git in my life 17:32:21 decause: Link to repo? 17:32:21 :P 17:32:36 #link ssh://git.fedorahosted.org/git/fedora-web.git 17:33:03 #info PLEASE talk to the websites team to get started on this, there is a process you should go through to become a member 17:33:29 #info decause has a working development environment of the Budget website; progress is ongoing, as mentioned above, if you want to get involved, work with the Fedora Websites team for more info on getting involved 17:33:32 #info this repo is quite large (hundreds of MB), and will likely be moved to pagure.io in the near future 17:33:34 Cool. Next ticket? 17:33:43 jflory7: yes, let's keep it rolling 17:33:54 #info === Ticket #17 - https://fedorahosted.org/fedora-commops/ticket/17 === 17:33:59 #info * "Interview Fedora's Diversity and Inclusion Advisor, tatica" 17:34:02 Checking in on status of tatica and if we're clear to send to the announce list 17:34:07 jflory7: negative 17:34:11 Gotcha. 17:34:36 tatica unfortunately had *another* death in the family, and we want to keep her plate empty for a while longer :/ 17:34:43 #info Announce email deferred; will check in again next week 17:34:45 :( 17:34:48 That's awful... 17:34:51 yeah :'( 17:34:54 :-( 17:35:05 I'll be keeping my thoughts with her this week 17:35:15 #info === Ticket #29 - https://fedorahosted.org/fedora-commops/ticket/29 === 17:35:22 #info * "G11n - proposal for the group revitalization" 17:35:26 Last week, we opted to make today's meeting the planning session for the G11n vFAD / other relevant activities. 17:35:39 Not sure if any of the G11n people happen to be lurking in here now? 17:35:46 noriko? 17:35:51 pravins? 17:36:23 Looks like pravin disconnected from the net half an hour ago 17:36:24 I know that there is a thread somewhere (telegram maybe??) talking about using the EMEA ambassador meeting as a place where g11n planning can be done a lil bit 17:36:35 decause: It was the EMEA Telegram, yeah 17:36:46 telegram is a non-ideal channel for these conversations for exactly this reason 17:36:55 not sure what his FAS is, but someone wanted to head that 17:36:56 yeah 17:37:10 jflory7: let's just open a good-ole-fashioned email loop with the two of them, see if we can't get them into a hack session? 17:37:19 (unlikely considering the time difference) 17:37:22 unless... 17:37:23 decause: noriko and pravins? 17:37:33 we hack *really* late, so that it is their morning time :) 17:37:40 True. Maybe it's possible! 17:37:46 .fasinfo noriko 17:37:47 decause: User: noriko, Name: Noriko Mizumoto, email: noriko.mizumoto@gmail.com, Creation: 2006-06-01, IRC Nick: noriko, Timezone: UTC, Locale: en, GPG key ID: F45683CA, Status: active 17:37:49 Want to take that action? 17:37:50 decause: Approved Groups: cla_fedora cla_done docs l10n-commits cvsfedora @cvsl10n fedorabugs docs-writers cla_fpca 17:38:11 noriko is only in UTC? 17:38:18 .fasinfo pravins 17:38:19 decause: User: pravins, Name: Pravin Satpute, email: psatpute@redhat.com, Creation: 2007-11-14, IRC Nick: pravins, Timezone: Asia/Kolkata, Locale: en, GPG key ID: 3EDF779F, Status: active 17:38:20 She's in Japan, I thought 17:38:23 decause: Approved Groups: fedorabugs cla_fedora cla_done @cvsredhat-config-language packager @svnsystem-config-language gitenglish-typing-booster @svnitranslit svnlohit @gitibus-rawcode @gitibus-sayura +gitliberation-fonts @gitindic-typing-booster cla_fpca @gitibus-indic-table provenpackager ambassadors marketing 17:38:28 .localtime Tokyo 17:38:29 jflory7: User "Tokyo" doesn't exist 17:38:34 Hmm 17:38:37 .localtime noriko 17:38:38 decause: The current local time of "noriko" is: "17:38" (timezone: UTC) 17:38:47 .localtime pravins 17:38:48 decause: The current local time of "pravins" is: "23:08" (timezone: Asia/Kolkata) 17:38:57 It's 2:38am in Tokyo right now. We might catch her if she is in Japan right now 17:39:12 so, if we hack until 10pm-ish, I think we'd be able to catch both of them maybe? 17:39:28 * decause isn't mathing very hard right now 17:39:31 In terms of time zones, it makes sense 17:39:42 More likely for noriko over pravins, I think it might be very early for him 17:39:44 kk, lets invite them to the hacksessions this week 17:40:01 #nick pravins 17:40:04 #nick noriko 17:40:12 I also spoke with aeng sonme time ago about the revilisation of the group. Maybe he's available. 17:40:15 jflory7: I don't think #nick is a command? 17:40:16 #action jflory7 / decause Get pravins and noriko invited to a CommOps hack-session this week 17:40:25 decause: It is. :) 17:40:28 orly? 17:40:38 decause: It registers the name of a person even if they aren't actually present in the meeting 17:40:39 * decause is learning things everyday 17:40:49 solid 17:40:52 I was digging through the MeetBot docs and learned that one. It's an obscure one but useful 17:40:54 Anyways... 17:40:55 Next ticket? 17:40:57 yes 17:41:02 we're almost at 75% 17:41:04 #info === Ticket #37 - https://fedorahosted.org/fedora-commops/ticket/37 === 17:41:08 #info * "Making a "Join" series on the wiki" 17:41:13 \o/ 17:41:13 #info 8-step process was approved in the ticket; jflory7 needs to begin drafting the CommOps Join page and get that going 17:41:16 Actually-- 17:41:17 #undo 17:41:18 Removing item from minutes: INFO by jflory7 at 17:41:13 : 8-step process was approved in the ticket; jflory7 needs to begin drafting the CommOps Join page and get that going 17:41:19 now is your time to shine keekri 17:41:32 #info 8-step process was approved in the ticket; keekri already drafted and got the Join page up on the wiki! 17:41:46 keekri++ 17:41:53 #link https://fedoraproject.org/wiki/CommOps/Join 17:42:20 keekri++ 17:42:23 next 17:42:24 I think all that's left for this ticket is getting it integrated across the rest of the wiki. 17:42:33 So a little wiki gardening and final review of the Join page, /me thinks 17:42:38 nod nod nod 17:42:44 I can take that one on 17:43:02 I had a window on a $COMPUTER that had all the pages that it would need to be added to 17:43:07 I'll find it 17:43:27 #action jflory7 Work on getting the CommOps Join page integrated with the rest of the wiki's Join series for different sub-projects 17:43:35 Really, I think that's all that's left for that ticket 17:43:48 keekri did the last real bit of work that it needed :) 17:44:14 #info Thanks keekri for getting that page up! 17:44:16 Next ticket? 17:44:19 next 17:44:25 #info === Ticket #39 - https://fedorahosted.org/fedora-commops/ticket/39 === 17:44:29 #info * "CommOps and Google Summer of Code" 17:44:34 #info Fedora has applied for another year of GSoC, making this our eleventh year participating in the program 17:44:38 Any new updates to share? What else is on the horizon for GSoC? Any questions from other CommOpsers? 17:44:47 jflory7: I heard that we missed one actually :/ 17:44:54 :( 17:45:08 well, we still applied, so we attempted to participate 17:45:12 Soooo, technically this is our tenth anniversary then... :P 17:45:12 :P 17:45:18 Anyways-- 17:45:25 Any formal updates on this year's progress with GSoC? 17:45:28 Additionally-- 17:45:35 What is the next deadline on the horizon? 17:45:46 #info GSoC will notify us by Feb 29th with how many slots they have allotted to us 17:45:46 can this ticket be dropped from meeting agendas until $DATE? 17:45:50 Ahhh 17:45:59 So next Monday 17:46:00 #info CommOps will then draft a commblog post if we got >0 slots 17:46:10 So this one is staying on the agenda 17:46:30 * fale is new to the GSoC thing... are mentors needed before or after the Feb29th deadline? 17:46:40 jflory7: yes, since it is a general, "all the gsoc things" ticket 17:46:59 fale: before, during, and after :) 17:47:23 fale: #fedora-summer-coding in IRC, and summer-coding@fp.o mail list, IIRC 17:47:25 decause: Is there an actual hard deadline or distinguishment for mentors being added to the GSoC page? 17:47:40 Or is it more of a mentors available to help in Fedora sort of thing? 17:47:51 * jflory7 knows there are specific project mentors and general mentors (in a sense) 17:48:03 I guess there is a distinction between GSoC Mentors, and general "i'm available to help people" mentors 17:48:04 thanks 17:48:05 Any Fedoran can be involved with the GSoC program over IRC and the mailing lists 17:48:21 I will find out more information, they changed the program since last I participated 17:48:24 decause: Yeah, cool, that's what I was thinking. 17:48:24 the answer is likely here: 17:48:35 #link http://summerofcode.withgoogle.com/ 17:48:49 We can look deeper into that, it's a good question. 17:48:56 I think that really wraps up this ticket? 17:49:00 Until next week, anyways 17:49:04 Next topic? 17:49:10 That was our last ticket 17:49:17 * jflory7 notes we're in the final ten minutes... 17:49:31 Going once-- 17:49:38 going twice-- 17:49:42 I think you apply to be a GSoC mentor 17:49:53 Going thrice-- 17:50:19 #topic Wiki Gardening 17:50:21 bee2502_: yes, mentors will be able to apply within our organization if/when we are accepted 17:50:27 #nick NewMembers 17:50:28 #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ] 17:50:39 Any other links or pages needing some cleaning? 17:50:49 yes... 17:50:53 something from council... 17:50:57 * decause tries to remember 17:51:11 nope, not gonna bock on it. LIkely the budget.next page 17:51:16 s/bock/block 17:51:25 I remember mattdm saying in channel about adding a column to a page. :) 17:51:29 But it's slipping me too 17:51:29 https://developers.google.com/open-source/gsoc/resources/mentors jflory7 fale 17:51:33 jflory7: we did that already 17:51:38 decause: mhmm 17:51:39 ;) 17:51:41 mattdm++ 17:51:45