14:07:39 #startmeeting Fedora Docs 14:07:39 Meeting started Mon Feb 1 14:07:39 2016 UTC. The chair is pbokoc. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:07:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:07:39 The meeting name has been set to 'fedora_docs' 14:07:56 #chair randomuser 14:07:56 Current chairs: pbokoc randomuser 14:08:15 #topic Roll Call 14:08:21 * Capesteve waves 14:09:58 * jhradilek waves. 14:09:58 * kirsti waves 14:10:37 oh hi kirsti, I haven't seen you around recently :) 14:10:59 pbokoc, no sorry, been lurking in the back ground 14:13:18 theeere they are 14:13:27 * randomuser arrives 14:14:27 kirsti, I didn't mean it as "where the hell have you been" :) just as "good to see you again" 14:14:46 anyway, randomuser, will you take it from here? 14:14:54 ah, I suppose 14:15:00 I realize that yes :) 14:15:23 #topic Follow up on action itmes 14:15:26 ugh 14:15:27 #undo 14:15:28 Removing item from minutes: 14:15:33 #topic Follow up on action items 14:15:49 #info randomuser did not create poll for meeting schedule 14:16:02 #action randomuser to create poll for meeting schedule 14:16:39 #topic Release Schedule checkin 14:16:41 well, that's for the best, there's at least 2 new people here, I think it's better if they vote too 14:16:50 #link https://fedoraproject.org/wiki/Releases/24/Schedule 14:16:59 #info branch is in three weeks 14:17:27 There are change proposals under discussion too 14:17:59 nothing on the docs tasks calendar yet, but be prepared 14:18:26 and like pbokoc said... 14:18:35 #topic New Writers 14:18:42 I don't think we need to worry about anything right now. Beta release is currently scheduled for May 3, so we'll need to worry about release notes a few weeks before, but that's 3 months from now anyway 14:18:44 we have new folks! 14:18:51 wooooo 14:19:49 any questions from new folks? 14:19:53 though I am not new, I might be wanting a new mentor... 14:20:20 (that means now's your time to speak up, cspicer & msvistun - especially if you want help signing up for FAS or something like that) 14:20:26 :) <-- new folk 14:20:51 randomuser: I am one of the new folks! Could you please give me the necessary rights to work with Fedora docs repos? To boost my credibility, I write the docs for RHEL. 14:21:09 pbokoc: y thx for the guidance :) 14:21:20 sorry, I forget vim keybindings don't work in IRC sometimes... 14:21:45 msvistun, cspicer1, yes, I can help get you the right permissions 14:22:00 do you have FAS accounts yet? 14:22:07 well i suppose my question would be: how can we find out what needs doing, and what do we need to do to get it done 14:22:58 yep I've got one 14:23:26 for the most part, you take up work on your own cognizance; we would need a larger group with more engagement to have a steady supply of work waiting 14:24:04 * jsmith shows up late... sorry 14:24:19 otherwise, we have a product in rhbz with bugs filed 14:24:21 cspicer1: One tip that jhradilek always mentions, when contacting developers, is to get into the habit of asking developers if a change applies to Fedora XX as well as RHEL YY 14:24:54 you could, for example, fix the checksum verification procedure for Windows in the Install Guide O:) 14:25:03 randomuser: is FAS account this? https://admin.fedoraproject.org/accounts/user/view/msvistunov 14:25:07 lol 14:25:34 heh 14:25:49 I intend to take care of that, cspicer1. It's my mess, I should clean it up. 14:26:00 msvistun, yeah, that's the one 14:26:23 do you happen to have a link to the product on rhbz? 14:26:51 yeah, we'll go over it later but the link is in the meeting agenda 14:26:57 kirsti, as for mentoring I have no idea... I don't really have much spare time. You could always just mail the list with any questions, or ask in #fedora-docs 14:27:11 * jflory7 is switching between windows, but doesn't want to forget and has a topic for discussion once open floor rolls around. 14:27:16 at least for now 14:28:04 pbokoc, ok, will keep an eye out, and ask 14:28:06 I'll assume you folks are familiar with a git based collaborative workflow and set up your memberships because pbokoc said so 14:28:08 :) 14:28:46 but please, if you're working on something, commit at the end of the session instead of the end of the quarter, or you risk community folks doing a ton of redundant work 14:29:21 sure 14:29:40 are you dcspicer, cspicer1 14:29:41 ? 14:29:55 no.. on FAS? i'll find a link 14:30:13 ok, let me know 14:30:35 pbokoc and jhradilek can do this too, if we need to take care of it later 14:30:35 https://admin.fedoraproject.org/accounts/user/view/cspicer 14:31:02 cool 14:31:11 #topic Guide Status 14:31:30 well, hm... 14:31:41 * jhradilek has a question. 14:31:47 #action randomuser to remove powershell fail from IG 14:32:19 unless you're really attached to it, cspicer1, that's been a pile of fail since I first contrived it 14:32:31 jhradilek, go! 14:33:08 randomuser: What do we do with bugs that belong to a writer who is no longer part of the Fedora Documentation Project? 14:33:30 reassign them 14:33:47 certainly not really attached to powershell :) 14:34:12 if there's a new maintainer, they go there; if not, we should discuss the guide's future 14:34:45 To whom? 14:35:07 to the loudest volunteer? 14:35:22 Laura Novich's Bugzilla account has been disabled earlier last month and since I was her manager, her bugs are now assigned to me. 14:35:29 And I don't want them. :)) 14:35:29 * randomuser nods 14:35:52 heh, ok. These are for the virt guides? I think we should consider retiring them 14:36:09 the getting started guide is good, the rest wasn't ever really targeted for Fedora comfortably 14:36:49 randomuser: I seem to have been added to this Contributor Group, but not approved. Something I should do? 14:37:13 randomuser: to this https://admin.fedoraproject.org/accounts/group/view/docs?_csrf_token=44a01824f287212b07554e9654b1480eb15224ad 14:37:14 msvistun, I'm just preoccupied because it's monday morning 14:37:24 randomuser: sure, no pressure 14:37:40 msvistun, what will you write, btw? 14:38:18 jhradilek, do you know about owners.git to reset the default assignee for a fedora docs book? 14:38:46 randomuser: Yup. You will see my name on some of the commits. :) 14:39:11 cool 14:39:16 randomuser: the prime motivation was to be able to submit random fixes. I discover them when I read the Fedora docs. Otherwise, I am not sure what I will write. But if you mean in terms of 'which guide', then it's the SysAdmin guide. 14:41:54 ok, I see. I just assumed you had a specific thing, it's not required or even really expected. 14:44:10 well this topic has gone quiet.. let's move on 14:44:18 #topic Outstanding BZ Tickets 14:44:23 #link http://tinyurl.com/lbrq84 14:44:56 randomuser: for the time being, I intend to send patch proposals to the respective guide owners. pkovar recommended this approach. I expect I will be communicating with StephenW the most, as he owns the SysAdmin guide. 14:46:06 good call, he is a cheerful and wise correspondent 14:46:45 msvistun: we could also just meet over coffee to go through changes, might be quicker then making, sending, and applying patches 14:46:50 so, there's the bugs. Communicate if you need help. 14:47:30 thanks, will take a look 14:48:04 #topic Open Floor 14:48:44 not sure if I even dare ask.... 14:49:02 Do we still have a conversation going about personas? 14:49:07 we're plowing through the meeting time and I get the sense that we're not covering everything we should for the new folks, but it does sound like our veterans in Brno are taking good care of them. 14:50:00 I've been tabling the personas thing; I don't want the idea to die, but it's not currently relevant. 14:50:08 jflory7, open floor? 14:50:18 Yes! 14:50:40 randomuser, I have been adding to the idea in the virtual getting started page though 14:50:41 kirsti: I thought that was a bit complicated, can we not just agree on target audience? 14:51:04 Capesteve, that works yes 14:51:13 I thought the point of developing personas was to agree on a target audience :) 14:51:13 I wanted to ask the Docs team about something CommOps has been working on with other groups in the Project. We're helping sub-projects put together a 2015 "Year in Review" article that explain some of the highlights of 2015 and goal(s) of 2016. 14:51:17 See announcement: https://communityblog.fedoraproject.org/share-your-year-in-review-with-fedora/ 14:51:24 See examples: https://communityblog.fedoraproject.org/tag/year-in-review-2015/ 14:51:38 ugh 14:51:40 oh jeez 14:52:32 I don't really want to touch that, but I get the sense that someone's going to have to 14:52:37 The writing part shouldn't be that difficult -- they can be as a short or as long as the group wants. There's a few easy templates on the first link that should make it more along the lines of filling in the blank. 14:53:37 what's the publishing schedule like, jflory7 ? 14:53:41 We want to help make it as easy and straightforward for you guys as possible. :) 14:53:48 what's the deadline for our bit? 14:54:02 randomuser: It's flexible, so there is not a specific due date. By the absolute latest, maybe by the end of month, but sooner, the better. 14:54:17 ok. bexelbie will write something up 14:54:44 Sounds great -- feel free to ping me or ask in #fedora-commops if you have any other questions! 14:54:51 * jflory7 has to check out 14:54:52 will do. 14:54:55 Thanks guys! 14:55:04 * randomuser elbow jabs bexelbie 14:55:15 hehe, you're stuck with it now ! 14:55:32 haha 14:56:47 cspicer1, msvistun, you've found #fedora-docs and our list, right? 14:57:08 yep - still need to write an introduction mail on the list 14:57:10 and is there anything else? 14:58:27 okay, we'll call it a day then, see you around 14:58:30 #endmeeting