22:05:20 <ryanlerch> #startmeeting Fedora Magazine weekly meeting
22:05:20 <zodbot> Meeting started Thu Nov  5 22:05:20 2015 UTC.  The chair is ryanlerch. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:05:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
22:05:21 <puiterwijk> (to give peopel chair access, aka #info, #topic, etc)
22:05:43 <ryanlerch> #chair puiterwijk decause jflory7 robyduck dustymabe
22:05:43 <zodbot> Current chairs: decause dustymabe jflory7 puiterwijk robyduck ryanlerch
22:05:50 <ryanlerch> .hello ryanlerch
22:05:51 <zodbot> ryanlerch: ryanlerch 'ryan lerch' <rlerch@redhat.com>
22:06:00 <decause> .hello decause
22:06:01 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
22:06:03 <puiterwijk> .hello puiterwijk
22:06:04 <zodbot> puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' <puiterwijk@redhat.com>
22:06:05 <robyduck> .hello robyduck
22:06:07 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
22:06:47 <ryanlerch> thanks all! we will need to figure out the meeting time better for next week with all the DST changes :)
22:07:26 <puiterwijk> ryanlerch: ah, well, I still have issues with DST within Europe myself as well. And that impacted me directly :)
22:07:36 <ryanlerch> #topic review of this week
22:07:52 * decause gets excited
22:07:53 <ryanlerch> So this week was obviously a big one!
22:08:28 <mailga> .hello mailga
22:08:28 <ryanlerch> we had two >30K days with the release announcement, and the accompanying posts
22:08:32 <zodbot> mailga: mailga 'Gabriele Trombini' <g.trombini@gmail.com>
22:08:36 <ryanlerch> #chair mailga
22:08:36 <zodbot> Current chairs: decause dustymabe jflory7 mailga puiterwijk robyduck ryanlerch
22:08:40 <decause> !!!
22:09:28 <ryanlerch> we also had jstanley's post, the third installment in the systemd series, and jzb's marking call to action post
22:09:56 <ryanlerch> we beat f22's release day record by about 2K views
22:10:06 <ryanlerch> and had a more solid followup day too!
22:10:24 <dustymabe> most of those were me refreshing to see if my ansible post was up :-P
22:10:32 <ryanlerch> also, special thanks to puiterwijk for getting the magazine ready for the big increase in traffic
22:10:33 <decause> :P
22:10:35 * dustymabe was eager
22:11:12 <ryanlerch> dustymabe: i'm going to get that one edited and out today! :)
22:11:29 <ryanlerch> anyone else have anything for the review of the week?
22:11:29 <dustymabe> yay!
22:11:43 <robyduck> dustymabe: hehe
22:12:08 * decause not me
22:12:32 <ryanlerch> #topic this week's pitches
22:12:49 <ryanlerch> okies, we have two pitches this week:
22:13:01 * jflory7 is now caught up and here
22:13:28 <robyduck> are there two ansible posts?
22:13:54 * jflory7 is logging into the Mag now
22:14:00 <ryanlerch> first pitch is one i did up about the rust copr:
22:14:02 <ryanlerch> http://fedoramagazine.org/?p=10580&preview=true
22:14:13 <dustymabe> robyduck: I think roshi made a pitch about ansible but never had any content
22:14:27 <ryanlerch> oh, lets do that one then!
22:14:41 <robyduck> oh, indeed roshi is the author
22:14:50 <ryanlerch> ansibale post -- http://fedoramagazine.org/?p=10574&preview=true
22:14:59 <puiterwijk> ryanlerch: this is just my personal opinion, but I am not sure whether we should advertise stuff in copr repos for "normal users" (aka, non-contributors)
22:15:33 <jflory7> Maybe do #link for the articles?
22:15:35 <jflory7> #link http://fedoramagazine.org/?p=10574&preview=true
22:15:44 <ryanlerch> jflory7: thanks!
22:15:50 * ryanlerch is a meeting leader noob
22:15:53 <robyduck> jflory7: it's not needed
22:16:09 <robyduck> zodbot picks them up anyway for the minutes
22:16:32 <ryanlerch> okies, this ansible one seems like a dupe of the one dustymabe has almost got published :)
22:16:39 <ryanlerch> so delete this one?
22:16:45 <jflory7> I was thinking so, yeah
22:16:45 <robyduck> +1
22:17:05 <mailga> +1
22:17:07 <ryanlerch> #action remove duplicate ansible in f23 pitch
22:17:53 <ryanlerch> done, remooved
22:18:06 <mailga> ryanlerch: is there a way to "mark" a post based on its difficulty? newbie - power users and so on?
22:18:11 <ryanlerch> okies, we will loop back to the rustlang one
22:18:19 <ryanlerch> #link http://fedoramagazine.org/?p=10580&preview=true
22:18:23 <roshi> aha, sorry - again got swamped and forgot about this meeting
22:18:40 <ryanlerch> #chair roshi
22:18:40 <zodbot> Current chairs: decause dustymabe jflory7 mailga puiterwijk robyduck roshi ryanlerch
22:18:56 <jflory7> Alrighty.
22:19:07 <cydrobolt> o/
22:19:09 <cydrobolt> .hello cydrobolt
22:19:10 <zodbot> cydrobolt: cydrobolt 'Chaoyi Zha' <summermontreal@gmail.com>
22:19:15 <cydrobolt> hey all
22:19:19 <roshi> I thought jzb was going to write this - I just wanted to get the pitch in to see if people thought it was a good fit, as ansible not being supported would be quite a shock to people who haven't been reading along
22:19:29 <dustymabe> roshi: I wrote it instead
22:19:34 <dustymabe> just wanted to get it out there this week
22:19:37 <dustymabe> sooner than later
22:19:58 <roshi> yeah, that makes sense
22:20:05 <ryanlerch> roshi: yeah the one dustymabe wrote is pretty much ready to go -- i will get it out just after the meeting
22:20:16 <roshi> awesome, glad to hear it :)
22:20:18 <jflory7> So looks like next and last pitch on the list is the Rust programming language available in Copr?
22:20:24 <ryanlerch> #chair cydrobolt
22:20:24 <zodbot> Current chairs: cydrobolt decause dustymabe jflory7 mailga puiterwijk robyduck roshi ryanlerch
22:20:31 * roshi is getting ready to take some PTO and has been swamped getting ready for that :p
22:21:05 <ryanlerch> yeah, my issue with the rustlang one is that it ships the binary, and i wanted to see if it was okay to advertise this
22:21:10 <puiterwijk> So about the rustlang one: I am personaly -1 to advertising COPR repos to non-contributors given the dubious state of COPR supportability. It is not official production
22:21:33 <puiterwijk> (that is me as infra guy speaking)
22:22:05 <ryanlerch> puiterwijk: fair enough -- this is why I proposed this one as a pitch -- this might be something that we talk to mattdm and co about
22:22:13 <puiterwijk> (but of course I'm not official mktg so have no voting power)
22:22:24 <jflory7> Perhaps a ping on the mailing list too to be sure.
22:22:25 <ryanlerch> i think if we put enough of a warning on it it might be ok
22:22:34 <jflory7> Worst case scenario, it could go onto the Planet.
22:22:44 <ryanlerch> but it might be of use to our users
22:22:47 <roshi> I think copr stuff should be on the planet
22:22:54 <roshi> and supported stuff on the magazine
22:23:11 <roshi> however, a post about the planet might be good - showcasing some of the posts?
22:23:27 <ryanlerch> we have had a few links to coprs on magazine before
22:24:01 <puiterwijk> ryanlerch: well, do you want to put a warning on there "Warning: COPR may go down any moment and stay off for multiple days, maybe a week, if you're unlucky"?
22:24:16 <puiterwijk> (if other stuff breaks, COPR gets the lowest priority, in my opinion)
22:24:29 <jflory7> roshi: I actually like the idea of doing a Planet post on the Magazine. Depending on whether that's been already written or published recently, I could do that as a pitch.
22:24:37 * robyduck thinks puiterwijk's concern makes perfectly sense
22:24:46 <ryanlerch> yeah, the post does need to make it clearer that copr is experimental
22:25:34 <ryanlerch> okies -- lets put this one in the holding pen, and i'll try to get some guidance from mattdm to see if this might be a good or bad idea
22:25:41 <cydrobolt> Yeah
22:25:48 <cydrobolt> I don't think Copr stuff should be on Fmag
22:25:56 <puiterwijk> ryanlerch: we may also want to wait a little bit as I'm going to have a meeting on copr supportability soon with the team
22:26:14 <puiterwijk> If we decide we want to make COPR really stable, supported, production, that would change my opinion on this.
22:26:16 <cydrobolt> The packages in Copr don't have the same QA assurances as official packages
22:26:57 <puiterwijk> But yeah, the contents of COPR is the next thing then yeah. Also, the fact that this is someone's personal COPR, so you never know if they're going to update it, and even if there's acritical security issue, provenpackagers can't update them
22:27:29 <dustymabe> i have one other pitch for this week
22:28:08 <robyduck> let's mark an action for this pitch and the go ahead, or?
22:28:20 <robyduck> s/the/then
22:28:43 <jflory7> I'll second that
22:28:48 <puiterwijk> Yeah, I think this needs more discussion, so action sounds good
22:28:56 <ryanlerch> cydrobolt: puiterwijk yeah those points are things that need to be pointed out in the post
22:29:08 <ryanlerch> sorry fell off there for a minute
22:29:58 <ryanlerch> okies -- putting it in the holding pen
22:30:08 <ryanlerch> dustymabe: a new pitch?
22:30:36 <dustymabe> ryanlerch: yeah.. sent to the mail list
22:30:40 <dustymabe> did you guys not get it?
22:31:30 * ryanlerch has not checked his mail this morning
22:31:44 <ryanlerch> dustymabe: can you give us the quick overview here?
22:31:46 <jflory7> #action move Rust to holding pen, seek guidance from mattdm regarding Copr
22:31:55 <dustymabe> ryanlerch: sure
22:32:03 <dustymabe> its basically promoting vagrant boxes in atlas
22:32:09 <dustymabe> https://gist.github.com/dustymabe/f4db1ef857260d216ab2
22:32:34 <dustymabe> also I sent a mail to the list to ask about the use of the logo on https://atlas.hashicorp.com/fedora
22:32:40 <dustymabe> would appreciate a response to that
22:33:00 <cydrobolt> dustymabe, might want to send an email to logo@fp.o
22:33:14 <dustymabe> cydrobolt: :(
22:33:24 <dustymabe> lots of rules to follow
22:33:34 <ryanlerch> looks like a good concept to me -- we probably just need a little more information in the post about what atlas / vagrant are, and why you would want to do this
22:33:45 <ryanlerch> +1 to the pitch for me
22:33:58 <dustymabe> ok so you want me ot add some content?
22:34:31 <ryanlerch> anyone else on this pitch?
22:34:49 <dustymabe> ryanlerch: for a vote?
22:35:17 <ryanlerch> yeah we usually vote on pitches
22:35:19 <robyduck> it's not for beginners, so it should explain what vagrant and atlas is, I agree on that
22:35:28 <puiterwijk> dustymabe: hmm, who uploaded the files there under that name?
22:35:36 <ryanlerch> yeah, the why is important too
22:35:37 <cydrobolt> yeah
22:35:38 <robyduck> + for a pitch
22:35:42 <cydrobolt> I was confused by "atlas"
22:35:51 <cydrobolt> I hadn't heard of it before, so an explanation would be very helpful
22:35:55 <dustymabe> cydrobolt: would one of you might asking the logo list for me. I really don't want another mailing list to keep up with
22:35:58 <mailga> ryanlerch: it seems a bit advanced for me.
22:36:05 <cydrobolt> dustymabe, not a ML afaik
22:36:12 <dustymabe> cydrobolt: ok
22:36:18 <dustymabe> I'll add content to the post about atlas
22:36:37 <ryanlerch> mailga: advanced is typically ok for the magazine, as long as it is targeted at users
22:36:42 <dustymabe> puiterwijk: I uploaded the content.. it's actually just uploading our URLS for our download loacations
22:36:50 <dustymabe> release engineering is aware of what I am doing
22:36:55 <dustymabe> and legal has signed off
22:37:08 <puiterwijk> dustymabe: okay, then I'll stay silent. Thanks for that info
22:37:18 <mailga> ryanlerch: I see, +1 for me
22:37:36 <puiterwijk> (just wanted to be sure you had sign-off, as we had more projects sort of like this that were stopped by legal)
22:38:04 <dustymabe> puiterwijk: np
22:38:14 <ryanlerch> dustymabe: okies, pitch approved
22:38:16 <puiterwijk> Looking further, this looks pretty cool. I would personally be interested in reading this
22:38:17 <dustymabe> ok i'll add the content and send a follow up mail to the list
22:38:29 <ryanlerch> #info dustymabe to draft atlas post
22:38:34 <dustymabe> is it possible that I might be able to get that published tomorrow if there isn't something else already going out?
22:38:35 <jflory7> Looking at the Gist, I think it's a good starting point for an article for targeted users.
22:38:39 <jflory7> +1 from me
22:39:43 <ryanlerch> any editors want to help dustymabe get the post ready for tomorrow, us time?
22:39:49 <ryanlerch> jflory7: :)
22:39:56 <jflory7> I can help from a non-technical perspective.
22:40:42 <ryanlerch> #info atlas post aimed for tomorrow
22:40:55 <jflory7> Might be a good idea if someone more knowledgeable helped edit too - I'd just be doing the English-y sort of stuff
22:41:09 <jflory7> But yes, I can definitely volunteer to help edit that for tomorrow
22:41:14 <dustymabe> ok.. could use someone to work on a picture maybe?
22:41:19 <decause> jflory7++
22:41:35 <puiterwijk> If it's technical and I count, I could help perhaps
22:41:35 <ryanlerch> okies, lets move on to Drafts
22:41:46 <jflory7> Sounds good, +1
22:42:11 <ryanlerch> #topic draft review
22:42:38 <ryanlerch> Okies, the next systemd post should be going out next week.
22:42:53 <ryanlerch> we had the converting init scripts one this week
22:43:19 <jflory7> Right. Unit dependencies one was next, I think?
22:43:57 <jflory7> I know we swapped some of the order around
22:44:26 <jflory7> Looks like that was the one Bryan was working on but had to forego - if I recall correctly, Paul said he was going to take on that next article?
22:44:31 <ryanlerch> #link http://fedoramagazine.org/?p=10228&preview_id=10228
22:45:01 <ryanlerch> okies -- we are getting these out on thurdays, so we will aim for that time again,
22:45:20 <ryanlerch> however paul is not here, so we will need to move this discissoin to the list
22:45:31 <jflory7> +1
22:45:34 <decause> +1
22:45:45 <ryanlerch> #action ryanlerch to start a new thread on the mailing list about this week's systemd post
22:46:02 <jflory7> Want to hit the KDE one next?
22:46:05 <ryanlerch> okies, the next one is one talking about whats new in the KDE spin
22:46:08 <ryanlerch> :)
22:46:19 <ryanlerch> yeah, i approached the kde folks for this one
22:47:02 <jflory7> Content looks good to me, definitely will be some interested people. Minor cleanup but overall +1 from me
22:47:09 <ryanlerch> http://fedoramagazine.org/?p=10726&preview=true
22:47:30 <ryanlerch> yeah -- a proper cover image, and probably make some of the screenshots a bit bigger
22:47:51 <ryanlerch> +1 for me -- lets aim for an ASAP on this one, so ride the f23 wave a bit
22:48:00 <mailga> +1
22:48:03 <jflory7> I can volunteer to help edit that one - are we looking at Friday or Monday?
22:48:09 <ryanlerch> i'll try to edit this one today a bit, and get it out
22:48:20 <ryanlerch> early in the AM us time
22:48:52 <ryanlerch> Okies -- on to the next one
22:49:06 <ryanlerch> OpenVPN -- jflory7 what's the status on this one?
22:49:21 <ryanlerch> #link http://fedoramagazine.org/?p=10253&preview=true
22:49:38 <jflory7> (Time check, we're getting down to the last ten minutes)
22:49:46 <ryanlerch> thanks jflory7
22:50:07 <jflory7> Sounds good, ryanlerch.
22:50:28 <jflory7> As for OpenVPN, still haven't had a chance to flesh out my draft :(
22:50:41 <ryanlerch> all good, we can keep it in drafts!
22:50:54 <ryanlerch> decause, any updates on the SFD post?
22:51:08 <ryanlerch> #link http://fedoramagazine.org/?p=10153&preview=true
22:51:21 <jflory7> I know it's been sitting in there for a while - was looking at this week for sure. Hopefully that ZNC article can carry any "how-to" sort of stuff while I'm working on the OpenVPN one
22:51:31 <decause> it was some time ago now, but I did add the conclusion and and converted the bullet points to narrative
22:51:51 <jflory7> I looked over at that one - I thought it was looking pretty ready to go
22:51:53 <decause> I suppose since I wasn't around for the last couple of meetings that it didn't move, but I thought I had gotten it "ready" for publishing
22:52:12 <ryanlerch> okies, do we want to aim for it on tuesday next week?
22:52:27 <decause> I'm good shipping it whenever, sure
22:52:32 <jflory7> Tuesday sounds good to me, +1
22:52:41 <decause> +1
22:52:56 <ryanlerch> #action decause to get SFD post ready for tuesday next week
22:53:10 <jflory7> I'll move it over to pending review
22:53:19 <ryanlerch> #topic pending review
22:53:42 <ryanlerch> so, the ansible one will be going out shortly after the meeting, as discussed eariler
22:54:10 <ryanlerch> jflory7: ZNC -- want to aim for a wednesday publish on that one?
22:54:40 <jflory7> +1, Wednesday works for me. As far as I know, last thing it needs is a featured image. I think stickster gave that one a thorough edit too
22:55:12 <ryanlerch> #action znc to publish on wednesday
22:55:21 <ryanlerch> anyone keen to do the cover image for ZNC?
22:55:33 * ryanlerch will do it
22:55:48 * jflory7 should probably do more playing around with Inkscape
22:55:57 <ryanlerch> okies -- the final item is the community blog post
22:56:08 <jflory7> I think that one is definitely imminent
22:56:10 <decause> jflory7: there is a decent compilation of how-to in old HFOSS repos
22:56:28 <ryanlerch> once the blog is launched, we will puch this one out
22:56:34 <jflory7> decause: Ooohh - think you can link me that after meeting?
22:56:39 <decause> jflory7: np
22:56:44 <jflory7> ryanlerch: Think we could coordinate that to tomorrow?
22:56:56 <jflory7> Or do we want to get more input from the mailing list?
22:57:12 <ryanlerch> yeah, its up to commops when that blog launches though :)
22:57:23 <ryanlerch> i'm happy to launch now :)
22:57:33 <robyduck> +1
22:57:54 <jflory7> Cool, can try to coordinate over IRC / mailing list depending
22:57:55 <decause> #link http://hfoss-ritigm.rhcloud.com/static/books/inkscapelessons-mairinduffy.pdf
22:58:00 * mailga says that waiting replies from ML is a suicide
22:58:07 <mailga> +1
22:58:08 <jflory7> Yeah, that's my worry
22:58:29 <ryanlerch> okies, so this weeks schedule is:
22:58:38 <jflory7> I think this is pretty fresh, I think tomorrow would be preferred
22:58:45 <ryanlerch> 1. after meeting -- ansible post -- ryanlerch to edit and publish
22:59:23 <dustymabe> ryanlerch: if you don't mind making a note of the changes you make.. I'd like to see them
22:59:23 <ryanlerch> 2. tomorow atals post -- jflory to edit for publish friday
22:59:33 <dustymabe> just for future reference
22:59:42 <dustymabe> you can go ahead and push.. I'd just like to see the diff
23:00:19 <ryanlerch> 3. tuesday SFD post
23:00:29 <jflory7> #action jflory7 edit Atlas post by end of Thursday night for Friday publication
23:00:35 <ryanlerch> 4. Wednesday ZNC post
23:00:43 <ryanlerch> -- ryanlerch to do cover image
23:01:25 <dustymabe> jflory7: it might be later tonight before I have that post fully updated.. do you mind holding off on editing until tomorrow?
23:01:33 <ryanlerch> 5. Thursday new systemd post -- needs to be discussed on mailing list though
23:01:40 <ryanlerch> does that look good to everyone?
23:01:48 <decause> lgtm +1
23:01:50 <mailga> agreed
23:02:00 * ryanlerch thinks he might be failing at using meetbot properly
23:02:03 <robyduck> yes, +1
23:02:04 <jflory7> dustymabe: Think you'd have it ready by the AM hours US EST?
23:02:08 <jflory7> ryanlerch: +1 from me.
23:02:26 <dustymabe> jflory7: yeah
23:02:30 <dustymabe> i'm US east
23:02:35 <dustymabe> i'll have it in the AM
23:02:42 <jflory7> dustymabe: Cool, I will make sure to be up early then for an afternoon publication
23:02:51 <dustymabe> ok cool
23:03:01 <ryanlerch> dustymabe: are you on for much later now?
23:03:10 <ryanlerch> how do i close the meeing?
23:03:21 <decause> #endmeeting when you're ready
23:03:28 <ryanlerch> #endmeeting