17:03:18 #startmeeting CommOps 17:03:18 Meeting started Tue Nov 3 17:03:18 2015 UTC. The chair is decause. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:03:32 #chair jflory7 threebean lmacken 17:03:32 Current chairs: decause jflory7 lmacken threebean 17:03:42 #topic RollCall 17:04:00 .hellomynameis jflory7 17:04:01 jflory7: jflory7 'Justin W. Flory' 17:04:01 #info Name, Timezone, CommOps Interest Areas 17:04:08 Ahhh, right 17:04:10 * danofsatx watches from the sidelines wearing his FAMNA hat 17:04:15 .hello dmossor 17:04:16 danofsatx: dmossor 'Dan Mossor' 17:04:16 jflory7: .hello is good too though :) 17:04:25 danofsatx++ 17:04:25 decause: Karma for dmossor changed to 1 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:04:42 * danofsatx blushes 17:04:49 awww, shucks... 17:05:20 decause, UTC+5 (ET), CommOps, Infra, Council, Amabassadors 17:06:13 #info jflory7, UTC+5, CommOps, Marketing, Join, Ambassadors 17:06:57 * mailga around 17:07:02 #info danofsatx. UTC+6(CT), Ambassadors (not sure what else fits in this unbrella) 17:07:12 others who join can intro themselves later 17:07:22 Sounds good. 17:07:53 #topic Agenda 17:08:01 #link http://etherpad.osuosl.org/commops-110315 17:08:15 1) Outreachy 17:08:21 2) WikiGardending 17:08:31 3) CommBlog 17:08:39 4) 5tftw 17:08:47 #5) plumbing 17:08:55 6) OpenFloor 17:09:06 #topic Outreachy 17:09:23 Yesterday was the deadline for outreachy applications 17:09:31 #link http://outreachy.gnome.org 17:09:44 we've had a number of folks contributing as part of the application process 17:10:15 Definitely. It's been awesome to see new faces helping around! 17:10:21 I know I've seen some submissions, but any folks who haven't formally submitted their application should do so immediately 17:11:13 We will likely be connecting with folks who applied in the near future, but all applicants should know their final status by November 17th 17:11:33 #info Outraechy applicants will be informed of their status by November 17th 17:12:41 Outreachy is an ongoing program that I hope Fedora will continue participating in for future cycles, so even if you don't get one of our two slots this time around, there will be openings in the future 17:13:32 thank you everyone on the CommOps team for your help recruiting and mentoring, I've gotten great feedback about how welcoming you all have been :) 17:13:47 next 17:13:57 unless anyone has Outreachy questions? 17:14:00 going once 17:14:02 going twice 17:14:03 I'm good. 17:14:04 going thrice 17:14:13 #topic WikiGardening 17:14:44 anyone who is a new commops member should be sure to add yourself to the matrix on our wiki page: 17:14:48 #action newmembers Update your lisitng on CommOps Wiki 17:14:55 #link http://fedoraproject.org/wiki/CommOps 17:15:28 This is the place where we can identify who is interested in what, at least until we get so many members the table is unreadable ;) 17:15:53 #action commops Add a "UTC" column to the interest areas table 17:16:25 One of our Outreachy applicants has sunk some cycles into cleaning up a few wiki pages: 17:16:28 #link https://fedoraproject.org/wiki/Community_Architecture_goals 17:16:34 #link http://fedoraproject.org/wiki/Sponsoring_event_attendees 17:16:40 #link https://fedoraproject.org/wiki/Marketing_social_networks 17:16:54 These 3 pages should be more up to date now 17:19:03 All look like solid articles 17:20:03 I've already heard from OSAS Social Media Lead that the page has been useful, and he'd like to meet with us at some point soon 17:20:46 are there any other Wiki pages that have had requested gardenings? 17:20:53 going once 17:20:59 going twice 17:21:06 going thrice 17:21:17 #topic CommBlog 17:21:53 I saw the F23 is a Go post go up! 17:22:00 #link http://CommunityBlog.Fedoraproject.org 17:22:11 Hopefully we can look at officially launching now that F23 is out. 17:22:17 jflory7: yes yes 17:22:30 Just have to check on status with SSL certs 17:23:03 I think it'd be great to repost the announcement on commblog, but we should ask #mktg what they think 17:23:19 Agreed. 17:23:44 commblog doesnt need to have a high barrier ro entry 17:24:10 go/no-go post for example 17:24:31 it had an image, one liner, and 2 links 17:25:28 that type of high utility low overhead post can have much impact 17:26:19 if folks have a link they'd like to share, they should sign up and create a draft for review 17:26:50 jflory7: I believe you have a post draft in the queue, yes? 17:27:09 decause: Yeah, I have the one announcing the CommBlog ready. :) 17:27:26 I think ryanlerch had whipped up an image for it too if I recall. 17:27:47 i know you said you were waiting on the redirect/alias from infra, yes? 17:28:41 My understanding is the official plan is to keep communityblog.fp.o as default and commblog.fp.o as alias. The real holdup is with SSL since it's a subdomain of fp.o, there's certain rules in place that require it to be in place. 17:28:58 puiterwijk might actually be able to explain a tad better than me if he's around right now? 17:29:13 jflory7: good to know, and good work 17:29:18 * puiterwijk reads back 17:29:37 puiterwijk++ 17:29:38 decause: Karma for puiterwijk changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:29:44 Right, so for that we need SSL to be enabled, for which we need to put it through the proxies. 17:29:55 To do that needs a small config change that I can push tomorrow (the day after release) 17:29:59 because that's when infra unfreezes 17:30:18 puiterwijk++ 17:30:18 jflory7: Karma for puiterwijk changed to 8 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:30:20 If anyone can ping me tomorrow afternoon to remind me, I'll get it all setup 17:30:39 I'll make a note! 17:30:42 puiterwijk: can do. 17:30:50 Heh. Two people, even better :) 17:31:31 #action jflory7 ping puiterwijk about ssl cert dance for commblog. due:11/4 17:31:42 excellent 17:32:07 i gave your draft a read and lgtm 17:32:27 will ship as soon as we get ssl 17:33:37 Awesome. 17:33:51 #action decause migrate RegionalAmbassador Budget Plan proposal to commblog post (and wiki page) and post to ambassador-related lists 17:34:14 anyone else got anything for commblog? 17:34:37 Ooh- 17:34:46 Probably should get something up there about the Developer Portal 17:34:59 I would suggest to bee2502 that she or someone else repost her outreachy posts there too 17:35:12 jflory7: agreed 17:35:28 that would be a really quick one 17:35:46 Definitely, I can get that snagged this week. 17:35:59 #action jflory7 draft up a post for the Developer Portal for the CommBlog 17:36:05 use same image as magazine, take "about" paragraph from their site, post with link 17:36:35 Definitely can do. 17:36:48 jflory7: utility post is all we need (save your heavy cycles for magazine) 17:37:09 Yeah, I can probably get that done in the next hour 17:37:41 jflory7++ 17:37:45 ok 17:37:59 any other CommBlog biz? 17:38:05 going once 17:38:11 going twice 17:38:17 going thrice 17:38:20 ok 17:38:32 #topic 5tftw 17:38:49 this is a new-ish tool in our box 17:39:10 i reckon it may even be on our wiki page now? 17:39:18 decause: keekri added it there. :) 17:39:52 mattdm artisinally crafts a post about 5 things happening in Fedora this week 17:40:02 keekri++ 17:40:53 we wanna help make his life easier, and start putting up our radar (and commblog posts) for content to contribute there 17:41:36 basically, 5tftw is 5 utility posts in one post stacked up 17:42:08 if we can publish atomic stories on commblog, mattdm can easily link to them 17:42:57 he says he likes to have this done by tuesdays, which fits us well 17:43:48 if anyone has items, post them to the commops list with "5tftw" in the subject 17:44:13 any questions? 17:44:18 going once 17:44:24 going twice 17:44:28 #link https://lists.fedoraproject.org/pipermail/commops/2015-November/000080.html 17:44:32 going thrice 17:44:37 ok 17:44:49 #topic Plumbling 17:44:56 lol 17:45:37 well, as funny as that word is to think about 17:45:56 what it means is internal infrastructure 17:46:50 on our wiki, it mentions that commops will have ticket-driven meetings 17:47:26 since we're now onto a regular cadence, we need a trac instance too 17:47:58 i checked today, but noticed i didnt create/request one yet 17:48:03 so 17:48:36 #action commops file an infra ticket to get a trac instance 17:48:43 What is this? :o https://fedorahosted.org/fedora-commops/ 17:48:49 lol 17:49:03 search failed me 17:49:09 No worries. :) 17:49:23 #undo 17:49:23 Removing item from minutes: ACTION by decause at 17:48:36 : commops file an infra ticket to get a trac instance 17:49:48 #action commops populte front page with resources 17:50:33 this is the place where we start hanging our tasks and actions in the future 17:51:09 #link https://fedorahosted.org/fedora-commops/ 17:51:22 we've been posting to the mailing list, which worked, but that doesnt capture the whole story 17:52:26 now, we do the same ml post to commops with missions, except now we link to tickets 17:52:57 Outreachy will be using trac for sure, whomever we pick 17:53:41 there will be a ticketing soon 17:54:05 any other infra related biz? 17:54:12 going once 17:54:17 going twice 17:54:23 going thrice 17:54:28 ok 17:54:44 #topic OpenFloor 17:55:06 Developer Portal CommBlog article up for review. http://communityblog.fedoraproject.org/?p=77 17:55:14 Whenever we want to get to that 17:55:23 we've got a handful of minutes left, so any takers before we close? 17:55:39 jflory7++ 17:55:48 going once 17:55:53 going twice 17:56:00 going thrice 17:56:02 ok 17:56:12 #topic farewell 17:57:23 thanks all for attending, and hopefully starting next week, we can point to old action items as open/closed tickets 17:57:41 HappyHacking! 17:57:43 decause++ 17:57:52 #endmeeting