15:56:05 #startmeeting Fedora CommOps (2016-04-19) 15:56:05 Meeting started Tue Apr 19 15:56:05 2016 UTC. The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:56:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:56:05 The meeting name has been set to 'fedora_commops_(2016-04-19)' 15:56:07 #meetingname commops 15:56:07 The meeting name has been set to 'commops' 15:56:14 #topic Agenda 15:56:18 #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-04-19 15:56:22 #info (1) Roll Call 15:56:26 #info (2) Announcements 15:56:30 #info (3) Action items from last meeting 15:56:34 #info (4) Tickets 15:56:39 #info (5) Wiki Gardening 15:56:44 #info (6) Community Blog 15:56:49 #info (7) Release Schedule 15:56:54 #info (8) Open Floor 15:56:58 #topic Roll Call 15:57:03 #info Name; Timezone; Sub-projects/Interest Areas 15:57:20 #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Join, and more 15:57:28 We'll wait about ten minutes or so for roll call. :) 15:58:29 jflory7: nice. Last week I joined around 10 minutes late and forgot to do the roll call 15:59:28 justharshal: No problem! Feel free to do an intro with: #info Name; Timezone; Sub-projects/Interest Areas 15:59:35 #chair justharshal 15:59:35 Current chairs: jflory7 justharshal 15:59:46 #info Tummala Dhanvi; UTC+5:30; CommOps,Docs,Security, * 15:59:50 .hello decause 15:59:51 decauseTravel: decause 'Remy DeCausemaker' 16:00:07 #chair dhanvi decauseTravel 16:00:07 Current chairs: decauseTravel dhanvi jflory7 justharshal 16:00:09 #info decause; UTC-4; CommOps, Council, * 16:01:07 * jflory7 is pulling together last minute CommBlog info on the agenda 16:01:13 #info Dimuthu Lakmal, UTC 5.30, Commops, Hubs * 16:01:23 .hello skamath 16:01:24 skamath: skamath 'Sachin Kamath ' 16:01:31 * c0mrad3 waves every one 16:01:32 .hello meskarune 16:01:33 meskarune: meskarune 'Dolores Portalatin' 16:01:45 .hello dhanesh95 16:01:46 dhanesh95: dhanesh95 'Dhanesh Bhalchandra Sabane' 16:01:50 #info Sachin S Kamath; UTC +5.30; CommOps, Hubs, Ambassadors 16:01:59 .hello cialu 16:02:01 cialu: cialu 'None' 16:02:20 .hello trishnag 16:02:21 Hello CommOps :) 16:02:21 trishnag: trishnag 'Trishna Guha' 16:02:29 Hi everyone :) 16:02:32 #chair skamath trishnag dhanesh95 meskarune 16:02:32 Current chairs: decauseTravel dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:02:34 #info Harshal Bhatia; UTC +5:30; CommOps, Hubs 16:02:34 Hi hi, all! 16:02:41 jflory7: chair decause also plz :P 16:02:49 lol 16:02:50 Hi everyone :) 16:02:51 #chair decause 16:02:51 Current chairs: decause decauseTravel dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:02:54 TY 16:02:59 #chair c0mrad3 16:03:02 #unchair decauseTravel 16:03:02 Current chairs: decause dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:03:09 #chair c0mrad3 16:03:09 Current chairs: c0mrad3 decause dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:03:11 #chair decause c0mrad3 16:03:12 Current chairs: c0mrad3 decause dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:03:14 There we go, hahah. 16:03:25 Anyone who just walked in, feel free to do a quick intro in this format: #info Name; Timezone; Sub-projects/Interest Areas 16:03:33 That will put it in the Meetbot minutes after meeting :) 16:03:44 So getting the Secretary General badge is really easy in CommOps :P 16:04:09 skamath: Hahah, yeah :P I usually give chair to approved members of the CommOps FAS group 16:04:34 :) 16:04:43 #info Dhanesh Sabane; UTC +5:30; CommOps, Packaging 16:05:37 #info cialu; UTC+2; Trans 16:05:47 .hello dmossor 16:05:47 danofsatx-n6: dmossor 'Dan Mossor' 16:06:29 #info Luca Ciavatta; UTC+2; Trans 16:06:34 * danofsatx-n6 is busy & on phone 16:06:41 Okay, and the agenda is updated for Community Blog section now. :) 16:06:42 #info Dolores Portalatin; UTC -4:00; CommOps, Diversity 16:06:59 For reference: https://fedoraproject.org/wiki/Meeting:CommOps_2016-04-19 16:07:11 Welcome to all old and new faces :) 16:07:16 Let's get started with announcements! 16:07:22 #topic Announcements 16:07:24 \o/ 16:07:24 #info Dan Mossor; GMT-5; bunch o' groups 16:07:29 #info === "Photography with the Fedora Design Suite" === 16:07:38 #chair danofsatx-n6 16:07:38 Current chairs: c0mrad3 danofsatx-n6 decause dhanesh95 dhanvi jflory7 justharshal meskarune skamath trishnag 16:07:40 #link https://fedoramagazine.org/photography-fedora-design-suite/ 16:07:45 #info YouTuber Riley Brandt did a review of the Fedora Design Suite and its applications towards photography. It's a great overview of the Design Suite. Feel free to share the article or video among your own circles! 16:07:58 #link https://youtu.be/mEYiafBl01s 16:08:03 #info === "Fedora 24 Wallpapers: Vote now!" === 16:08:08 #link https://communityblog.fedoraproject.org/fedora-24-wallpapers-vote-now/ 16:08:14 #info The Fedora 24 Supplementary Wallpapers are open for voting until this Friday. This year's election is a new record breaker with over 225 badges issued for voting this year. If you want to vote, it's still not too late. Get your vote in on Nuancier. 16:08:19 #link https://apps.fedoraproject.org/nuancier/ 16:08:25 #info === "BrickHack 2016 and Fedora: Event Report" === 16:08:31 #link https://communityblog.fedoraproject.org/brickhack-2016-event-report/ 16:08:36 #info The full event report for BrickHack 2016 was published last week. It looks at what happened at BrickHack 2016 and tries to evaluate our impact at the event. 16:08:39 hi 16:08:43 #info === "Time to test Fedora 24 internationalization" === 16:08:49 #link https://communityblog.fedoraproject.org/time-test-fedora-24-internationalization/ 16:08:56 #info The F24 Internationalization (I18n) test day recently came to a close. You can read more about what it aimed to accomplish on the Community Blog. 16:08:58 Hiya, nb! 16:09:01 #chair nb 16:09:01 Current chairs: c0mrad3 danofsatx-n6 decause dhanesh95 dhanvi jflory7 justharshal meskarune nb skamath trishnag 16:09:08 #info === "Live Media Writer Test Day (2016-04-19)" === 16:09:14 #link https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/HBOKKIJ5BSFPEVJVLKYRSM7PVU2SC3PO/ 16:09:19 #link https://fedoraproject.org/wiki/Test_Day:2016-04-19_Fedora_Media_Writer 16:09:26 #info The Fedora Media Writer (formerly known as Live USB Creator) was recently rewritten and is being tested for default inclusion in F24. If you have a 4GB USB drive, you too could help with this! Check out the mailing list announcement and wiki page for more details about the event. 16:09:32 And that's all I have for today. 16:09:38 Anyone else have anything they want to add? 16:09:53 * decause does not 16:09:59 well 16:09:59 Also, welcome back to Rollywood, decause :) 16:10:17 #info GSoC Selected Students should be notified by 4/22 16:10:25 jflory7: TYVM 16:10:43 Awesome! 16:10:49 Announcements, going once... 16:10:52 #help Ambassadors please submit your updated Budget Proposals, Reports, and Delegate Selections ASAP 16:10:53 Going twice... 16:11:03 Going thrice... 16:11:03 EoF 16:11:09 #topic Action items from last meeting 16:11:15 #link https://meetbot.fedoraproject.org/fedora-meeting/2016-04-12/commops.2016-04-12-15.56.html 16:11:20 #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward. 16:11:31 #info === decause JFDI the LimeSurvey Account, cleared with jzb === 16:11:39 tatica was interested in this one too. 16:12:02 I think she might be having a power outage right now, however 16:12:34 * skamath is checking out the wallpapers 16:12:40 Ahh, good timing :) 16:12:51 tatica_: Was just asking decause about the LimeSurvey account. 16:13:00 jflory7: I have an account created, I'm working on mkaing it complete 16:13:06 making* 16:13:11 * jflory7 nods 16:13:17 power out 16:13:17 Any action items necessary for this? 16:13:33 #action decause complete limesurvey account creation process 16:13:40 eof 16:13:41 I'll make sure to update tatica post-meeting too 16:13:50 #info === [COMPLETED] jflory7 / decause Check in with pravins and noriko for any closing items for Ticket #29 === 16:13:55 #info All that remains is a report of how the vFAD went, which is currently pending review in the Community Blog. Once published, ticket can be closed. Will discuss later in Community Blog part of meeting. 16:14:01 #info === [COMPLETED] jflory7 / decause re-ping designlist with speak-up series proposal, ask for feedback === 16:14:09 #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/JRDNZ5L3BXP7457AKXUJC62T256Q6MAN/ 16:14:17 #info === decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format) === 16:14:23 I think this is still a WIP 16:14:29 it is 16:14:31 I also added details to the ticket for this 16:14:35 re-action me plz 16:14:40 Let's touch on it later again too 16:14:43 jflory7: nod nod 16:14:48 #action decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format) 16:14:53 #info === [IN PROGRESS] jflory7 Begin writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open) === 16:15:00 #action jflory7 Continue writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open) 16:15:07 #info === [COMPLETED] decause up jflory7's privs on commops admin list === 16:15:13 #info === [COMPLETED] jflory7 Update CommOps mailing list signature once the permissions are set === 16:15:18 ^ I believe we're set with that now 16:15:25 #info === [INCOMPLETE] decause / jflory7 ping mktg list about alpha->beta release announcement research for May 3rd === 16:15:32 #action decause / jflory7 Ping Marketing mailing list about Alpha to Beta release announcement research for May 3rd 16:15:39 #info === [COMPLETED] jflory7 Create a WhenIsGood for determining an ideal hack time for the future === 16:15:44 #link http://whenisgood.net/fedora/commops/power-sessions 16:15:58 All CommOps members interested in joining our hack sessions should check out this poll! ^ 16:16:07 jflory7++ 16:16:07 Many of you have already added your info to it :) 16:16:13 jflory7++ 16:16:23 #info === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team === 16:16:24 #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team 16:16:38 #info === [INCOMPLETE] decause post the etherpad link to the design-team ticket, and update the University_Involvment Objective page === 16:16:39 #action decause post the EDU Etherpad link to the design-team ticket and update the University Involvment Objective page 16:16:50 #info === [IN PROGRESS] decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog === 16:16:51 #action decause / jflory7 Explore how to subscribe the social-media mailing list to the RSS feed of Community Blog 16:17:00 Okay, and that's all the action items from previous meeting. Onward! 16:17:07 #topic Tickets 16:17:12 #link https://fedorahosted.org/fedora-commops/report/9 16:17:17 #info === Ticket #29 === 16:17:20 lots of things that still need to get done on the plate for decause 16:17:22 #info "G11n - proposal for the group revitalization" 16:17:28 #link https://fedorahosted.org/fedora-commops/ticket/29 16:17:35 #agreed Last meeting, we checked in with pravins and agreed that the last remaining step for this ticket would be to publish a report of how the vFAD went. There is currently a final draft pending editor review in the Community Blog for this already. Once it is published, this ticket can be closed. 16:17:43 #action jflory7 Upload the local Albanian F24 translation sprint group photo to the G11n vFAD article on the Community Blog 16:17:50 pravins++ noriko++ jonatoni++ elioqoshi++ g11n++ 16:17:50 <3 16:17:57 pravins++ 16:17:57 Does anyone else have much to add to this ticket? 16:18:01 noriko++ 16:18:03 decause: Karma for noriko changed to 4 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:18:07 jonatoni++ 16:18:14 elioqoshi++ 16:18:18 I really don't know what else we have down for this other than the aforementioned items :) 16:18:26 pravins++ noriko++ jonatoni++ elioqoshi++ g11n++ 16:18:28 skamath: Karma for pravins changed to 13 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:18:31 skamath: Karma for noriko changed to 5 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:18:34 Lots of awesome work and story-telling in this one. 16:18:37 jflory7: I think that we can open another one for next release though ;) 16:18:39 I feel good about this ticket :) 16:18:42 decause: For sure! 16:18:53 this'll be a recurring event 16:19:06 for a "first run" the results on this were *very* promising 16:19:19 Definitely. It'll be great if we can work this in on our calendar too for recurring tasks. 16:19:26 nod nod nod 16:19:36 With that note, let's do something we've never done before... two tickets at once. :P 16:19:37 #info === Ticket #34, 49 === 16:19:45 #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series" 16:19:48 #action commops add Translation vFAD to regular release schedule on Fedocal 16:19:50 #info #49: "[Onboarding Series] Infrastructure" 16:19:55 #link https://fedorahosted.org/fedora-commops/ticket/34 16:19:57 #link https://fedorahosted.org/fedora-commops/ticket/34 16:20:02 #link https://fedorahosted.org/fedora-commops/ticket/49 16:20:05 Last meeting, we wanted to follow up with the Design Team about the badges we were proposing for all teams (e.g. mailing list posts) and the Pagure-specific ones for Infrastructure. An email was sent to the Design Team list and awaits a response. Outside of assisting the Design Team in getting these next few badges created and pushed, are there any other tasks we want to focus on now? Preferred to focus our own resources on getting these badges 16:20:05 done, but new badge ideas welcome, especially if they can be used for *all* sub-projects. 16:20:10 Whoops, long message 16:20:21 You linked #34 twice ;) 16:20:42 skamath: with the extra 'space' in front, it won't go to minutes 16:20:43 FYI 16:20:45 skamath: The first one didn't take because I had a space before #info. 16:20:52 Oh, and here's the link again to the mailing list post: 16:20:53 #link https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/thread/JRDNZ5L3BXP7457AKXUJC62T256Q6MAN/ 16:20:56 ohh. Cool. 16:21:20 So, I think it would really cool if we could try using our own resources to creating these badges. 16:21:24 The design work might be a blocker for some 16:21:31 jflory7: I think a badges powersession is in order 16:21:31 But some of the badges also require YAML files 16:21:37 Like for fedmsg hooks 16:21:43 e.g. Pagure commits, mailing list posts, etc. 16:21:59 This might be something anyone interested in could try doing to help lighten the load with our badge requests. :) 16:22:05 jflory7: perhaps we can query the design-team and see if/when they'd wanna do a co-team powersession? (/me realizes this will make it harder, not easier to meet) 16:22:20 I would be down, personally 16:22:33 I would be willing to do some badges designwork 16:22:36 I could help work on some of the YAML file definitions in a hack session 16:22:38 * decause has made a couple 16:22:43 And maaaaaybe badge design itself 16:22:43 +1 16:22:50 decause++ 16:23:06 Anyone else have any ideas they want to add in? 16:23:16 * dhanesh95 has nothing 16:23:20 Or questions too :) 16:23:44 If not, we can look at scheduling a hack session for Badges with the Design Team. 16:23:49 I used to work in graphic design if you guys need some help, but I've never made anything for fedora before :) 16:24:21 Sounds good to me 16:24:29 meskarune: The cool thing about badges is that there's a lot of resources for designing them that makes it super easy if you're savvy with design. There's a style guide, templates, and all other kinds of great resources. 16:24:31 meskarune: the badges style guide is *very* well done, and there are templates also for getting it right 16:24:33 * jflory7 goes to find the link really fast 16:24:49 jflory7: on the fedora-badges trac 16:24:52 that sounds really great decause, jflory7 I'll have a look at it :D 16:24:58 #link https://fedorahosted.org/fedora-badges/wiki/DesignResources 16:25:01 thanks 16:25:14 thanks too. 16:25:18 #link https://fedorahosted.org/fedora-badges/wiki/NewBadgeGuide 16:25:19 And here's the magical ZIP of everything. 16:25:22 #link https://fedorahosted.org/fedora-badges/attachment/wiki/DesignResources/FedoraBadgesResources.zip 16:25:26 jflory7++ 16:25:27 decause++ 16:25:28 thats the one 16:25:47 Okay, that's the Holy Grail of Fedora Design Team. 16:25:50 jflory7++ 16:25:50 dhanesh95: Karma for jflory7 changed to 50 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:25:51 meskarune: fair warning, the badges poster is *very* large though, so be mindful if you're going to open it 16:26:00 jflory7: 50! 16:26:02 Can be a lot of bandwidth for one download 16:26:03 jflory7++ 16:26:03 cialu: Karma for jflory7 changed to 51 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:26:03 oh ok, thanks 16:26:21 woohoo! Cookie rain. 16:26:24 and 16:26:28 riecatnor++ 16:26:28 :) 16:26:37 riecatnor++ riecatnor++ riecatnor++ 16:26:42 for all those badges resources 16:26:45 ^ she's the one who put together all of the badges resources 16:26:51 Yep 16:26:55 riecatnor++ 16:26:55 skamath: Karma for riecatnor changed to 5 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:26:56 nice :D 16:27:03 riecatnor++ 16:27:03 cialu: Karma for riecatnor changed to 6 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:27:08 riecatnor++ 16:27:08 dhanesh95: Karma for riecatnor changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:27:14 riecatnor++ 16:27:14 Dimuthu: Karma for riecatnor changed to 8 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:27:17 lol 16:27:23 :p 16:27:28 So, with the above info in mind, I say we plan on a hack session for this ticket. 16:27:28 I don't get it 16:27:28 karmastorm++ 16:27:29 Question: 16:27:52 Do we want to possibly have our own CommOps hack session for working on badges, or save all badge-related work for the joint session with the Design team? 16:28:04 Can be a little crossover too 16:28:11 jflory7: we should send along the poll 16:28:16 and maybe do one of our own first? 16:28:22 Yeah, and get the gears rolling for that 16:28:30 make sure the backlog is groomed, and our requests are clear 16:28:39 concepts are fully fleshed out 16:28:50 * dhanesh95 thinks it should be done together 16:28:52 I mean, I'm +1 to having a portion of our next hack session allocated to badges. I think I could write the YAML hooks for the Pagure + mailing list badges 16:29:01 Or help teach anyone else interested in learning. 16:29:16 jflory7++ 16:29:16 Dimuthu: Karma for jflory7 changed to 52 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:29:29 Yeah, it would be good to take a look at what's on our backlog for sure first, make sure there's not anything else we're lagging on. 16:29:53 :) 16:30:07 Here's a quick proposal to vote on: 16:31:04 #proposal Next major work on badges will happen partially at our own hack session, where we can work a little bit on badge design and YAML definition files. Otherwise, we will wait for a joint session with the Design Team for most of our Badges work for tickets #34 and #49. 16:31:05 +1 16:31:19 time check : 30 min left 16:31:26 dhanvi++ 16:31:34 +1 16:31:34 Thanks for the check 16:31:39 +1 16:31:41 +1 16:31:41 +1 16:31:42 +1 16:31:57 Going once, 16:32:02 * c0mrad3 confused with using 2 clients :P c0mrad3 and dhanvi 16:32:02 Going twice, 16:32:10 +1 16:32:13 Going thrice... 16:32:16 +1 16:32:20 * jflory7 waves the gavel of agreement 16:32:21 #agreed Next major work on badges will happen partially at our own hack session, where we can work a little bit on badge design and YAML definition files. Otherwise, we will wait for a joint session with the Design Team for most of our Badges work for tickets #34 and #49. 16:32:26 Next ticket! 16:32:32 #info === Ticket #68 === 16:32:37 #info "Reconstructing the Campus Ambassadors program and campus outreach" 16:32:42 #link https://fedorahosted.org/fedora-commops/ticket/68 16:32:48 +1 16:33:13 So I didn't clear this with decause quite yet, but I think he might be on board with the following: 16:33:14 Last meeting, we identified that the next step for this ticket would be converting the raw Etherpad notes into the University Involvement Initiative wiki page. Once this is done, it will be easier to identify where to go with planning and organization for Campus Ambassadors in the future. This is a great task for someone wanting to dive in to help with. If you want to help with this, feel free to volunteer! 16:33:26 #link http://etherpad.osuosl.org/fedora-EDU-refresh 16:33:26 #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative 16:34:01 My thinking is that if someone wanted to help take down the raw notes into an organized format on the wiki, we could then check in and review it once it's converted from Etherpad => wiki. 16:34:14 As long as decause is +1 to opening this task up, I'd say it's open for claiming. 16:34:17 * decause is ok with this, but realizes that his notes may be a bit 'gibberish-y' for someone not familiar with his mannerisms 16:34:31 +1 16:34:36 it'll require edits eitherway 16:34:39 Awesome, great! 16:34:41 Right, right. 16:34:50 I can convert it into wiki 16:34:52 So I would classify this as a "wiki gardening" sort of task. 16:35:06 maybe you guys could also do something similar to https://education.github.com/pack 16:35:08 Can I do this? I'll be happy to take inputs from decause and jflory7. 16:35:15 * dhanesh95 would like to help with #68 16:35:36 or even get involved with the developer pack 16:36:01 meskarune: I like the concept and the delivery, I just wish there was more FOSS in the EDU pack from GitHub 16:36:09 meskarune: That could be really cool... maybe a FOSSpack or something. 16:36:12 decause: I totally agree 16:36:23 As for the task at hand, seems like there's a lot of willing participants :) 16:36:28 Ill ping decause if I don't understand. 16:36:31 there are some vps hosts though so people could learn to isntall/use fedora on a server 16:36:51 How about this... one person can work on converting it over to the wiki, and a second person can review their edits before sending the wiki page link to the CommOps mailing list? 16:37:02 meskarune: the model of giving students access to paid services for free when they're in school is a vendor lock-in scenario, no offense to GitHub intended here 16:37:23 jflory: +1 16:37:27 decause++ 16:37:27 justharshal: Karma for decause changed to 40 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:37:36 * decause has opinions about the Ivory Tower and EDU outreach strategies a lil bit ;) 16:37:38 jflory7, assign the task to some one else 16:37:43 c0mrad3 / justharshal: Do you two think you might want to work on this together? Maybe c0mrad3 can do the moving over, and then justharshal can review the changes before we get all of CommOps involved? 16:37:56 Okay, maybe dhanesh95 could take c0mrad3's place there? :) 16:38:13 jflory7, I also saw few other hands raised 16:38:19 decause++ 16:38:19 it's going to take multiple passes eitherway 16:38:24 Agreed 16:38:26 decause: oh, I just meant you guys could have a program that accepts people with .edu mails 16:38:31 * decause wishes he took better notes 16:38:48 jflory7: +1 16:38:54 meskarune : also don't forget GitHub is proprietary 16:38:58 maybe they can get fedora cd's and sticker or other useful things 16:38:58 justharshal: Want to take lead on this one and dhanesh95 can assist with edits? 16:39:01 meskarune: def def def. I like that approach too, we should talk more about it 16:39:07 If both +1, let's #action it next :) 16:39:08 Sure. 16:39:12 jflory7: +1 16:39:16 +1 16:39:16 Great! 16:39:36 c0mrad3: you've seen http://pagure.io yeah? 16:39:37 Not used to the vocabulary yet 16:39:38 pingou++ 16:39:45 #action justharshal / dhanesh95 Work on moving the Etherpad notes into a more readable format on the University Involvement Initiative wiki page; after converting it, send to CommOps mailing list for feedback and review 16:40:01 You can also always ask questions in IRC if you're confused about anything :) 16:40:14 decause, yes and I use it too :) 16:40:19 :) 16:40:32 jflory7: we're nearing the 75% mark 16:40:39 c0mrad3: I know, but having fedora's name next to microsoft might give students a good alternative to look at 16:40:46 jflory7: +1 16:41:00 Good call, let's leave this ticket where we are now and revisit it later on. 16:41:01 or having an alterntive to the student pack that is fedora's 16:41:02 meskarune: we can reach out, we just have to know what we're looking to offer 16:41:08 meskarune: Whoops. I guess you offended a bunch of people. 16:41:09 yeah, totally 16:41:14 meskarune: I personally like the idea of having a FOSS student pack too, maybe we can see what we can pull together? 16:41:23 decause, one thing I like most about Fedora is that everything is free as in Freedom 16:41:34 jonobacon is a friend of Fedora, the new Community Lead for GitHub, and we know John Britton as well (EDU Lead) from my days at RIT 16:41:38 and Free as in Free Beer too ;) 16:41:58 let's do this discussion in open floor and stick to the topic now jflory7 decause skamath :) 16:42:00 #agreed justharshal and dhanesh95 are going to work on moving the Etherpad contents into a more readable and formalized format on the wiki. We'll check in on this ticket again next week or earlier, depending. We'll break down more tasks later on. 16:42:02 skamath++ 16:42:02 justharshal: Karma for skamath changed to 6 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:42:09 Let's hit the next ticket. 16:42:14 #info === Ticket #69 === 16:42:18 #info "Fedora Modularity onboarding" 16:42:23 #link https://fedorahosted.org/fedora-commops/ticket/69 16:42:25 well, the great thing about freedom is being able to use both foss and proprietary as you like, and giving people the choice/chance to see what is out there 16:42:26 A great start for this could be to help generate some traction with a Community Blog article announcing the Modularity WG. A badge proposal would be useful for sponsored / official members of the WG. A review of the wiki pages linked in the ticket would be helpful. Can we break up these tasks among members of CommOps? 16:42:43 langdon: Happen to be around? 16:42:47 I personally try to use only FOSS, but many people have jobs that use a wide range of technology 16:43:19 this is a good oppertunity to push fedora to future devs and CEOs :) 16:43:31 meskarune: let's wait till the open floor and discuss this furthur :) 16:43:39 bconoboy also might be involved with the Modularity efforts? 16:43:40 oh ok, sorry :) 16:43:41 meskarune++ 16:43:45 langdon is lead, but nils is the real driver from the modularity team on this 16:43:52 Okay, that's good to know. 16:44:07 I know nils said this time wasn't the best for him for meetings somewhere. 16:44:15 So I had an idea for how this ticket could be broken down a bit... 16:44:32 * decause listens 16:44:41 * c0mrad3 decause https://pagure.io/user/dhanvi :) 16:44:41 (1) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members) 16:45:10 (2) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora 16:45:39 (3) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac) 16:45:58 ^ makes me leery about putting too much on the Badges Team plate, but I think a membership badge would be good for the Modularity WG 16:46:14 I just want to know more about how they accept / bring in members. 16:46:18 we just need to provide concepts/designs then as a start :) 16:46:19 e.g. if there is a FAS group 16:46:25 decause: +1 16:46:37 jflory7: I don't think there is a FAS group (yet?) 16:46:45 So, just from these, I see three action items we can break this into. 16:46:46 also, i would put (1) at the end 16:46:54 Yeah, I think so too 16:47:00 after we've got all the ducks in a row on the onboarding steps and wiki page 16:47:08 decause: +1 16:47:22 Heheh, yeah, don't want to announce it until they're ready for the exposure :) 16:47:23 jflory7: but yeah, those steps are solid I reckon 16:47:30 Okay, great. 16:47:43 jflory7: I think we want to see if we can make this happen this week though if possible 16:47:50 next week at the latest 16:48:02 So an action item for (1) would be to reach out to a member of the Modularity group (do they have a mailing list?) and ask if anyone from the WG would like to pen an announcement in the CommBlog. 16:48:05 so, maybe we get all the materials ready, and then publish next week 16:48:11 Do we have a deadline for #69? 16:48:12 It doesn't need to go out ASAP until everything else is ready, but no harm in drafting early 16:48:31 jflory7: I think we just ask nils 16:48:36 Oh, they use devel@ 16:48:42 See it mentioned in the ticket 16:48:45 they've already identified as the "lead" on this 16:48:55 nils? 16:48:59 Oh, yeah 16:49:02 * decause thinks that is the nick 16:49:02 See your above message now 16:49:35 Okay, so someone could reach out to nils in the #fedora-modularization channel and see if he is interested in starting an announcement draft in the CommBlog about the WG 16:49:37 there is fas group now for Modularity, its modularity-wg 16:49:40 let's create tickets for these actions (if they don't already exist) 16:49:41 Also gives them time to get ideas / discussion flowing 16:49:45 paragan++ 16:49:45 jflory7: Karma for pnemade changed to 6 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:49:46 paragan++ 16:49:48 decause: Karma for pnemade changed to 7 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:50:04 #info The Modularization WG does have a FAS group: modularity-wg 16:50:28 #info (1) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora 16:50:33 #info (2) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac) 16:50:33 jflory7: let's make tickets for each of those tasks you've laid out, and call the existing ticket the "master" ticket 16:50:43 #info (3) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members) 16:50:47 decause: +1 16:50:49 decause: +1 16:50:50 #nick commops 16:51:07 set master ticket to blocking on the sub-tickets 16:51:18 #action commops / jflory7 Create tickets for the above items 1-3 so they can be assigned and broken up among CommOps members 16:51:19 then we can close them all in one run, hopefully next week 16:51:27 Sounds like a plan to me. 16:51:33 * decause sees this as a top prio for the powersession 16:51:44 decause++ jflory7++ 16:51:49 Sounds cool :D 16:52:02 decause: So once the tickets are created, we can get going on this at a hack session 16:52:05 I'm +1 16:52:09 +1 16:52:12 +1 16:52:14 +1 16:52:14 +1 16:52:17 +1 16:52:22 I'll do an #agreed and we'll move on quickly! 8 minutes left. :) 16:52:29 jflory7++ 16:52:45 #agreed We will create tickets for the above three items identified for this ticket and begin working on them at our next hack session! 16:52:51 * justharshal was just about to mention time 16:52:53 #topic Wiki Gardening 16:53:00 jflory7++ 16:53:00 justharshal: Karma for jflory7 changed to 53 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:53:01 #nick NewMembers 16:53:05 #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ] 16:53:13 Oh man, so many cookies! 16:53:19 Anyone else have any wiki gardening to add in? 16:53:32 jflory7: you're saying like that's a bad thing. 16:53:36 Target Unicorn Poop, jflory7 :P 16:53:53 :P 16:54:14 If there's no other wiki pages on the agenda right now, we can hit the Community Blog next. :) 16:54:18 Going once... 16:54:22 jflory7: just the modularity wiki onboarding 16:54:27 those are the big ones I reckon 16:54:38 decause++ Agreed. We can wrap those up in Ticket #69 though :) 16:54:40 Going twice... 16:54:42 * decause vaguely recalls something from council yesterday... 16:54:47 maybe 16:54:55 Want to come back if it comes to you? 16:54:58 yeah 16:55:02 go ahead tho 16:55:08 Cool cool. 16:55:08 #topic Community Blog 16:55:29 Okay, for anyone who is not used to this, this section is a blast of info really fast, and then some discussion after. 16:55:33 Here we go! 16:55:36 * decause gets popcorn 16:55:39 #info === This Week in CommBlog === 16:55:42 (in a good way) 16:55:43 #info (1) "BrickHack 2016 and Fedora: Event Report" 16:55:48 #link https://communityblog.fedoraproject.org/brickhack-2016-event-report/ 16:55:52 #info Total Views (Apr. 12 - Apr. 19): 98 16:55:57 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1143 16:56:01 #info (2) "Time to test Fedora 24 internationalization" 16:56:06 #link https://communityblog.fedoraproject.org/time-test-fedora-24-internationalization/ 16:56:11 #info Total Views (Apr. 12 - Apr. 19): 316 16:56:12 * c0mrad3 decause pass to me also :) 16:56:15 nice 16:56:16 #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1405 16:56:22 #info === Coming Up in CommBlog === 16:56:25 * decause passes to c0mrad3 16:56:27 * dhanesh95 bookmarks the link for a read later 16:56:34 #info (1) "DevConfCZ 2016: Event Report" 16:56:40 #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=6b95d2c034 16:56:41 lolololcrycrycry 16:56:44 #info (2) "Fedora translation sprint – 5 days, 50 members and 20+ thousand words" 16:56:53 #link https://communityblog.fedoraproject.org/?p=1434&preview=1&_ppp=b2e060d3ee 16:56:59 * c0mrad3 eating the hot pop corn :) 16:57:00 #action jflory7 Review and edit "Fedora translation sprint" article for publication on Thursday, if possible 16:57:05 <3 that's gonna be a good one 16:57:09 #info (3) "Time to test Fedora Media Writer" 16:57:15 #link https://communityblog.fedoraproject.org/?p=1446&preview=1&_ppp=6ffd1bc529 16:57:20 #info (4) "Fedora at Bitcamp 2016" 16:57:27 #info Still in progress (no link yet) 16:57:32 And that's the show! 16:57:33 \o/ 16:57:38 woo 16:57:41 So the Fedora Media Writer was one that I just noticed 16:57:48 That would need to ship today... 16:57:53 :) 16:57:56 It's not too late 16:58:07 jflory7: nah, we can def still ship that today 16:58:21 open floor? 16:58:26 #action jflory7 Ship the "Fedora Media Writer" article ASAP, contact author about dropping a link on the CommOps mailing list next time so we don't wind up last minute 16:58:41 jflory7: nod nod 16:58:47 Bonus points if someone can find me a great image for that article :P 16:59:03 Anyways, if nothing else CommBlog, let's hop to Open Floor 16:59:12 Oh, wait-- 16:59:17 #topic Release Schedule 16:59:21 #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html 16:59:24 Anything to check in on here? 16:59:29 #info Fedora 24 Beta Freeze is happening in Fedora Infra 16:59:34 #link https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/DLCO4JGG3YNN47Z2PR2RT6X7ID2DYS4B/ 16:59:43 * jflory7 nods 16:59:43 that means we're getting close to the beta announce 16:59:52 probably a next week focus 16:59:59 Oof, we gotta get rolling on getting the ducks in a row for beta announcement 17:00:07 Sounds good, let's hit Open Floor now 17:00:10 #topic Open Floor 17:00:11 it should be a modified version of the alpha, but yeah, def 17:00:17 32-bit images will be retired? 17:00:36 dhanesh95: Ah, yeah, that should actually be tomorrow's Fedora Magazine article, if I recall 17:00:42 meskarune, feel free to talk :) 17:00:42 * jflory7 is a little bit behind on email this week 17:00:56 jflory7: +1 17:01:00 oh lol 17:01:28 Anything else we want to hit on while we're all still here? 17:01:29 ok, fedora FOSS student, or maybe getting involved somehow with the github student pack 17:01:34 ╰( ͡° ͜ʖ ͡° )つ──☆*:・゚Open Floor should look cool like this! :P 17:01:50 meskarune: I personally think we could try to wrangle together a FOSS student pack. 17:01:51 * dhanesh95 feels sad 32-bit images are being retired 17:01:53 just throwing out ideas since you guys are doing a focus on college outreach 17:01:56 Maybe... 17:02:01 jflory7: yeah, I sorta love that idea 17:02:15 foss student pack would promote projects and tools to students 17:02:15 Foss student pack sounds good. 17:02:17 It could even be a cross-distro collaboration... not sure if that's a bit too starry-eyed though. 17:02:18 FOSSPack! Are we going to do it? 17:02:31 +1 for FOSSPack! 17:02:34 Or if it might devolve things into politics 17:02:36 Loved the idea! 17:02:39 jflory7: I think digital ocean would def sponsor it, and ubuntu would probably jump on board 17:02:42 Focus should be on linking students with FOSS resources and tools 17:02:50 FOSSpack +1 17:02:53 +1 17:03:06 but all the software we provide is FREE as in FREEdom and any one can install it using dnf install not just students 17:03:15 jflory7+1 17:03:15 Ubuntu folks are into the #PenguinFamily idea, they'll help if even as indivuals 17:03:19 I'm thinking this would be a great ticket for our Trac. At least, I think it would be ours. Not sure if ours or Marketing, decause? 17:03:20 Wow so much excitement 17:03:57 jflory7: I think it is more related to CommOps than marketing.. 17:04:10 Arch has some folks able to help. And politics need not be part, its about sharing IMO 17:04:16 dhanesh95: +1 17:04:20 I agree with jflory7 focus should be on linking students with FOSS resources 17:04:50 dhanesh95: It definitely does have a Community approach to it but I also think the Marketing folks would be interested in this too. 17:04:53 btw, I just found an empty channel. If anyone need to test zodbot / fiddle with it, head over to #glittergallery. zodbot is kinda alone there. 17:05:06 Before saying "let's file a ticket!", I want to make sure we do it in the right place. :) 17:05:18 jflory7: We can work together with the marketing folks for sure! 17:05:38 skamath: glittergallery is used only occasionally, I have owner there if some changes are needed 17:05:57 Oww.It looks deserted 17:06:05 * decause is in another call, fyi 17:06:13 dhanesh95: Definitely will be cross-collaboration between CommOps and Marketing for sure. I'm going to *tentatively* say we can file this in CommOps Trac unless decause thinks Marketing Trac is more appropriate. 17:06:21 I'm a little on the fence about which one it can fall into 17:06:38 jflory7: +1 17:06:47 meskarune: Would you like to take an #action item to file a ticket for the FOSSpack idea in our Trac? 17:06:59 ok, how do I do that? lol 17:07:02 After that, I think we can close up shop here and head back to channel. :) 17:07:02 jflory7++ 17:07:08 this is my first fedora-meeting 17:07:15 \o 17:07:20 MarkDude: Consider adding the channel Guard if you have Op there. A deserted channel might end up with freenode-staff as owner after a while 17:07:37 meskarune: Mine too! And I'm loving it! 17:07:39 meskarune: So, funny you mention it, one of our CommOpsers not here right now actually updated the Trac wiki page guiding how to use it. :) One second. 17:07:50 skamath: will do after meeting, I can ping the "actives" might need some help :D 17:07:52 :D 17:07:54 meskarune, dhanesh95: By the way, welcome welcome to both of you! First meeting is always a big milestone. :) 17:08:15 #topic Using Trac 17:08:17 #link https://fedoraproject.org/wiki/Trac 17:08:24 meskarune: ++ dhanesh95 ++ 17:08:27 Have been observing CommOps for a couple of weeks. Thought this would be the right time to dive in. :) 17:08:29 #link https://fedorahosted.org/fedora-commops/ 17:08:43 #link https://fedorahosted.org/fedora-commops/newticket 17:08:53 jflory7: Thanks for the warm welcome 17:09:06 dhanesh95: Gladly. :) 17:09:07 MarkDude++ jflory7++ 17:09:07 dhanesh95: Karma for markdude changed to 5 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:09:12 #topic Open Floor 17:09:23 * justharshal sighs 17:09:36 Also, jflory7, Don;t you think 200 cookies are a little too high for a release cycle? 17:09:49 *Don;t 17:09:50 * justharshal forgot to check in on his first meeting 17:09:52 *Don't 17:09:59 meskarune: Those links there should be useful for checking out to file a ticket. All you have to do is log into the CommOps Trac with your Fedora account, click "new ticket" and add details for the request. It should be straightforward from there. If not, questions always welcome! 17:09:59 ouch. Bad keyboard 17:10:19 ok thanks jflory7 17:10:22 * justharshal so his name wasnt in the notes 17:10:25 skamath: The badge is global for all release cycles, not per release cycle. :) 17:10:28 dhanesh95, meskarune welcome to the CommOps team 17:10:32 :) 17:10:34 dhanesh95++ 17:10:34 c0mrad3: Karma for dhanesh95 changed to 1 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:10:36 Oh, okay. 17:10:42 meskarune++ 17:10:45 c0mrad3: Karma for meskarune changed to 3 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:10:46 Okay, anything else? We're ten minutes over now. If not, let's end the meeting and head back to #fedora-commops. 17:10:54 Let's go! 17:10:55 Going once... 17:11:00 Going twice... 17:11:00 meskarune++ dhanesh95++ (take two) 17:11:00 MarkDude: Karma for meskarune changed to 4 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:11:02 jflory7+1 17:11:03 MarkDude: Karma for dhanesh95 changed to 2 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:11:05 OK 17:11:05 Going thrice... 17:11:14 Okay, thanks for coming out today, everyone! 17:11:16 See you in channel... 17:11:18 #endmeetnig 17:11:20 #endmeeting