14:01:15 <randomuser> #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
14:01:15 <zodbot> Meeting started Mon Aug 29 14:01:15 2016 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:15 <zodbot> The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings'
14:01:15 <randomuser> #meetingname Fedora Docs
14:01:16 <zodbot> The meeting name has been set to 'fedora_docs'
14:01:16 <randomuser> #topic Roll Call
14:01:54 * Capesteve waves
14:02:28 * pbokoc 
14:02:34 <pkovar> /me ist hier
14:03:38 <bexelbie> .hello bex
14:03:39 <zodbot> bexelbie: bex 'Brian (bex) Exelbierd' <bex@pobox.com>
14:04:07 <randomuser> hello everyone
14:04:19 <randomuser> #topic New Writers
14:04:35 <tkumar> Hi
14:04:40 <randomuser> in this part of the show, we take a moment to give new folks an opportunity to say hello or ask questions
14:04:47 <randomuser> hi, tkumar
14:04:57 <tkumar> hello randomuser
14:05:02 <pbokoc> hey tkumar
14:05:02 <tkumar> How are you?
14:05:29 <randomuser> it's monday morning here, I'm not sure yet :/
14:05:39 <tkumar> hehe
14:05:51 <tkumar> It's night over here :)
14:05:56 <randomuser> welcome to our meeting, do you have any docs questions?
14:06:57 <tkumar> Sure. I was going through guides.
14:07:25 <tkumar> If I remember it correctly, I have to put my name in front of a guide name
14:07:50 <tkumar> for guide lead or QA contact
14:07:55 <tkumar> right?
14:08:02 <randomuser> no, that's not really important
14:08:27 <randomuser> you don't need to list yourself as the lead writer or QA contact to work on a guide
14:10:04 <tkumar> Sure. I guess I will go over few guides and see if something needs updating or improvement.
14:10:26 <randomuser> Sure.  You might pick up other ideas as the meeting continues as well.
14:10:51 <tkumar> Yes, I will.
14:11:01 <randomuser> #topic Where are with the Release Cycle and Docs?
14:11:16 <randomuser> we're behind schedule, actually
14:11:26 <randomuser> https://fedorapeople.org/groups/schedule/f-25/f-25-docs-tasks.html
14:12:04 <randomuser> there's not a lot on our list for alpha, but we should be ramping up to cover beats
14:12:39 <randomuser> Release notes work is tracked at https://fedoraproject.org/wiki/Category:Documentation_beats
14:13:22 <randomuser> putting your name on this one is more significant, since we're more likely to have multiple people working concurrently
14:13:45 <randomuser> if there's an asterisk, it means that person hasn't confirmed their participation
14:13:57 <randomuser> aaaand I still need to clean that up so it reflects current status
14:14:08 <randomuser> #action randomuser to update beats table
14:14:55 <randomuser> the disruptive stuff in f25 shold all be covered in https://fedoraproject.org/wiki/Releases/25/ChangeSet
14:15:37 <randomuser> with a bonus wayland as default for workstation that was done out of the change process
14:16:16 <randomuser> ... that's where we start, anyway.  Thoughts?
14:16:50 <pbokoc> I'll take some changes as usual and I'll talk to cspicer1 about collecting info on installer changes
14:16:53 <bexelbie> do we know if any of these will also be written for the magazine/comm blog so we could ask those authors to help with Release Notes?
14:17:24 <randomuser> yeah, i expect the magazine folks will be doing their own documentation work
14:17:56 <bexelbie> randomuser, cool - that way we can leverage that
14:18:05 <randomuser> anyone want to be our bridge to marketing and bring it up to them?
14:19:05 <randomuser> if not, I guess it will be me
14:19:15 <bexelbie> I can mention it to jflory7 and send an email or two if you'd like
14:19:24 <randomuser> yes please, bexelbie
14:19:40 <bexelbie> #action bexelbie to contact marketing/commblog about having article writers for new features do a release note too
14:20:26 <randomuser> I'd also like to represent SIGs better; if you're involved in one, please talk to them about release notes
14:21:30 <randomuser> any other thoughts?
14:21:35 * jflory7 reads
14:21:55 <bexelbie> well this action item may be easy :P
14:22:11 <bexelbie> jflory7, we can talk after this meeting if you'd like
14:22:22 <jflory7> bexelbie: Okay, sounds good, ping me whenever :)
14:23:31 <randomuser> #topic Specific Doc Status
14:24:03 <randomuser> I like the linguistic change away from 'guide' here bex, well played
14:24:12 * bexelbie bows :P
14:24:26 <randomuser> #info What has changed with specific docs? What needs to be republished? Any blockers or issues?
14:24:37 <randomuser> #info virt getting started guide probably needs to be republished
14:25:01 <pbokoc> grundblom also fixed something in f24 release notes and was asking for them to be republished some time ago IIRC
14:25:15 <randomuser> hm, i'll check on that too
14:25:47 <pbokoc> a month ago on docs@lists,fp.o, subject "Fixed release notes for Publishing"
14:25:55 * randomuser hangs head
14:26:32 <pbokoc> hey that's nothing man, I promised to clean up beats and set them to Open like 2 months ago and I'm just doing it now :))
14:26:41 <randomuser> heh
14:28:39 <randomuser> anything else you folks can think of we should do for the release cycle this week?
14:29:06 <randomuser> oh, actually, i've got one for you pbokoc
14:29:18 <pbokoc> :I
14:29:49 <randomuser> you could write a readme for the install guide to explain your process when updating the guide
14:29:56 <randomuser> where to check, who to talk to, etc
14:30:21 <pbokoc> oh yeah, that's probably a good idea
14:30:30 <randomuser> that would make it easier if you or cspicer don't have cycles to take care of it
14:30:42 <pbokoc> yep
14:30:45 <pbokoc> alright, I'll do that
14:31:02 <pkovar> i published the rn a while ago
14:31:30 <pkovar> the virt guide is waiting on author to fix the fedora release info etc.
14:31:39 <pkovar> there's a bug for that
14:31:41 <randomuser> pkovar++
14:32:26 <pbokoc> btw, I'll update the "beats closed" admonition in wiki so it links to pagure instead of cgit while I'm at it
14:32:40 <randomuser> nice
14:32:42 <randomuser> good find
14:33:31 <randomuser> pbokoc, https://pagure.io/install-guide/issue/4
14:35:10 <randomuser> huh, just discovered https://pagure.io/dpdk-guide
14:36:08 <randomuser> what other things should we discuss about specific docs that need work?
14:37:29 <randomuser> i'll throw this out: we're thinking of prototyping asciidoc stuff with the cookbook
14:37:46 <randomuser> so if folks come along that want to write standalone articles, they should be committed there
14:37:47 <bexelbie> should we change topic to the "the new hotness?"
14:38:00 <randomuser> ha, sure
14:38:07 <randomuser> #topic The New Hotness
14:38:11 <randomuser> #chair bexelbie zodbot
14:38:11 <zodbot> Current chairs: bexelbie randomuser zodbot
14:38:15 <randomuser> #undo
14:38:15 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x273dc890>
14:38:19 <randomuser> #chair bexelbie zoglesby
14:38:19 <zodbot> Current chairs: bexelbie randomuser zodbot zoglesby
14:38:40 <randomuser> #info prototyping asciidoc stuff in the cookbook
14:39:09 <randomuser> i started doing some cleanup in a branch there, but didn't get super far on it
14:39:11 <zoglesby> oh its that time of the week again.
14:39:23 <bexelbie> I have a test build of the install guide in pintail - the biggest bug, I recall got fixed, but i want to try it on another guide
14:39:45 <pkovar> link for the lazy ones: https://pagure.io/fedora-cookbook/branch/asciidoc-master
14:39:59 <bexelbie> #link https://fedorapeople.org/~bex/pintail/
14:40:07 <bexelbie> #info test build of Install Guide with bex mods using pintail
14:40:14 <randomuser> just for fun I wrote a little tutorial on setting up fedora as a hyperv guest, will push after polish
14:41:02 <randomuser> thanks pkovar
14:41:20 <randomuser> i do need some help with part of this, however
14:41:36 <randomuser> and zoglesby maybe you can answer this
14:41:52 <randomuser> how are we communicating the document metadata to pintail?
14:42:09 <randomuser> some kind of header or correlating file, right?
14:42:33 <zoglesby> we are not yet. That is still a pending task on pintails side. May not be a ticket for it now that I think about it
14:42:37 <bexelbie> why aren't we using the pintail.cfg?
14:43:31 <randomuser> aaah ok.  I wasn't sure if the functionality was pending or just my knowledge of it
14:43:35 <zoglesby> but yes, it will be yaml at the top of the doc
14:45:37 <randomuser> we spent a bunch of time on this last week, so I don't want to get too far into it this time
14:45:46 <bexelbie> Do we have an MVP definition for the new system?
14:46:03 <randomuser> I don't know what that means, bexelbie
14:46:06 <bexelbie> Are we just goaling for install guide from docbook and the cookbook from asciidoc styled and published?
14:46:25 <bexelbie> MVP = minimum viable product - what is our definition of success so we can think about actually cutting over
14:46:31 <bexelbie> in this case
14:46:49 <bexelbie> I am concerned about theming and a style guide for our asciidoc
14:47:03 <randomuser> aaah.. we want to publish the guides we'd want to publish with publican
14:47:05 <zoglesby> if we can get the install guide and cookbook working I would call it a success
14:47:34 <bexelbie> so we are sure we are not going to drop any guides as part of this transition?
14:48:38 <randomuser> in general, we've been trying to separate content redesign efforts from tooling efforts
14:48:54 <bexelbie> ok
14:49:10 <randomuser> i know that's somewhat counterintuitive, but the aim is to avoid circular dependencies
14:49:10 <bexelbie> has anyone looked at the theming issues with pintail?
14:49:23 <bexelbie> I am all for separating them
14:49:31 <zoglesby> bexelbie: are you using the most recent version of docs-fp-o repo?
14:49:46 <zoglesby> shaunm had done some theming and I don't see it in your example
14:49:48 <bexelbie> zoglesby, depending on how recent it was updated, maybe
14:49:57 <bexelbie> zoglesby, ok - then I'll need to pull and regen
14:51:53 <randomuser> have we heard from ryanlerch at all about site design?
14:52:05 <zoglesby> no
14:52:12 <randomuser> i'm thinking that when he started things were perhaps a bit too raw for design work
14:52:38 <bexelbie> wasn't there also an xml vs css issue? or am I thinking of something else?
14:53:02 <zoglesby> that was a part of his issue, trying to get xslt to do what he wanted it to do
14:54:38 <randomuser> We're running low on time, let's get the bz link in the minutes and get to open floor
14:55:05 <randomuser> #topic Outstanding BZ Tickets
14:55:09 <randomuser> #info All Bugs - http://tinyurl.com/lbrq84
14:55:17 <randomuser> also, pagure issues
14:56:00 <randomuser> #info idle thought - some script or panel to aggregate pagure issues from all our projects into a single view would be neat
14:56:56 <randomuser> #topic Open Floor Discussion
14:57:42 <zoglesby> I'll look at the api and see if I can make something work
14:58:08 <randomuser> zoglesby++
14:58:09 <zodbot> randomuser: Karma for zoglesby changed to 5 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:59:31 <randomuser> well, if there's nothing else, I'll wrap it up
14:59:44 <randomuser> thanks for coming, everyone
14:59:50 <randomuser> #endmeeting