14:02:47 <randomuser> #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
14:02:47 <zodbot> Meeting started Mon Sep 26 14:02:47 2016 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:47 <zodbot> The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings'
14:02:47 <randomuser> #meetingname Fedora Docs
14:02:47 <zodbot> The meeting name has been set to 'fedora_docs'
14:02:49 <randomuser> #topic Roll Call
14:02:53 * pbokoc 
14:04:05 * jsmith is here, for once
14:05:01 <randomuser> g'morning, jsmith
14:05:57 <shaunm> quack
14:07:08 <randomuser> #topic Release Cycle
14:07:18 <randomuser> #link https://fedorapeople.org/groups/schedule/f-25/f-25-docs-tasks.html
14:07:33 <randomuser> #info beta freeze is tomorrow
14:07:44 <randomuser> #action randomuser to build relnotes rpm today for beta release
14:08:13 <randomuser> #link https://pagure.io/release-notes/issues
14:09:29 <randomuser> one thing not in the notes so far.. F25 alpha went out with Wayland as the default workstation session, iirc
14:09:51 <randomuser> if that is going to persist, we should have something substantial to say about wayland
14:10:23 <pbokoc> oh yeah, and I hear there's no support for the proprietary nvidia driver
14:10:39 <randomuser> #link https://fedorahosted.org/fesco/ticket/1615
14:11:14 <pbokoc> also I totally forgot to close beats on the wiki as I promised last week :(
14:11:23 <randomuser> pbokoc, anecdotally, from the GDM wayland experiment, users are more likely to have issues with nvidia drivers via wayland
14:11:31 <randomuser> and I got the issues closed :)
14:11:39 <randomuser> or beats closed, rather
14:11:46 <pbokoc> oh, nice
14:12:51 <randomuser> #chair pbokoc
14:12:51 <zodbot> Current chairs: pbokoc randomuser
14:13:02 * randomuser has a distraction to deal with
14:13:27 <pbokoc> I'm opening some additional issues in the release-notes repo so we can track the wayland thing
14:14:04 <pbokoc> btw it's strange that the wayland thing isn't a Change. Seems more important to me than ibus emoji typing...
14:15:19 <pbokoc> ok, soooooo
14:15:34 <pbokoc> write release notes, people!
14:17:14 <pbokoc> I see grundblom commited some stuff in the last few days, good job
14:17:19 * zoglesby is here
14:17:35 <pbokoc> we should probably do some cleaning up though
14:17:57 <randomuser> i'll branch off the 'clean' branch and pull in grundblom's commits
14:18:24 <pbokoc> which one even is the clean one? master? that repo is a mess
14:19:49 <randomuser> origin/blank iirc
14:20:30 <randomuser> #action randomuser to branch release-notes git repo for F25 when building RPM
14:22:25 * randomuser has averted distraction
14:22:54 <randomuser> and yeah, i expected a Change thing for Wayland
14:24:00 <pbokoc> anyway, we have 2 weeks, so let's do this. I'll try to get some help from people in the office but a lot of people are very busy right now
14:24:06 <randomuser> jkurik, Wayland by default seems like a system wide change thing, there's no change proposal on it for the wiki.
14:24:10 <randomuser> FYI
14:25:25 <randomuser> anything else for release notes?
14:25:41 <pbokoc> about branches, I think the "blank" one is ancient, the last commit message says "Clean out F12 content to make way for F13"
14:25:48 <randomuser> bah
14:26:11 <randomuser> okay, that won't work, then
14:27:59 <pbokoc> it also won't build because missing revnumber or something, I've never seen that message before. master should be usable if we get rid of the content that's currently in and only keep the structure - I think I cleaned that up before f24 or f23.
14:28:38 <randomuser> yeah, that's the thing I was thinking of
14:28:43 <pbokoc> btw, is there a way to lock a branch in pagure? We should probably make one that's actually clean, lock it so almost nobody can commit to it directly, and then branch off of it every release
14:28:58 <randomuser> ... maybe
14:29:44 <randomuser> it'd most likely be outside the pagure UI, but i think we can drop in a merge hook like `if branch is locked, exit 1`
14:30:21 <pbokoc> echo "Spank! Spank! Bad writer!"
14:31:02 <randomuser> heh
14:32:37 <pbokoc> I think that's it for relnotes today
14:32:45 * randomuser nods
14:32:52 <randomuser> lost the agenda in tabs already :P
14:33:00 <randomuser> #topic specific doc status
14:33:17 <randomuser> pbokoc, cspicer1 - what's the status of the installation guide?
14:33:36 <randomuser> oh, actually, there's the default deliverable change
14:33:43 <pbokoc> cspicer's out sick, he should be back on Thursday
14:33:52 <randomuser> we need to cover that for both the IG and release notes
14:34:10 <pbokoc> you mean the media writer?
14:34:14 <randomuser> right
14:34:31 <pbokoc> yeah, both relnotes and the IG have an issue open for that
14:34:41 <randomuser> any takers in the audience?
14:35:12 <pbokoc> should be a really short section, the tool looks pretty simple from a user's perspective
14:35:43 <pbokoc> plus it's supposed to work the same way on all platforms
14:35:48 <randomuser> easy
14:35:51 <pbokoc> anyway I'll talk to cspicer about it once he gets back
14:35:57 <randomuser> cool
14:36:06 <pbokoc> that plus installer release notes
14:36:47 <randomuser> what other specific doc stuff should we cover?
14:38:08 <randomuser> sounds like none
14:38:15 <randomuser> #topic Outstanding BZ Tickets
14:38:18 <randomuser> #info All Bugs - http://tinyurl.com/lbrq84
14:38:35 <randomuser> #info pagure issues exist too
14:40:36 <randomuser> #topic Open Floor Discussion
14:40:43 <randomuser> okay folks, what's on your mind?
14:41:40 <pbokoc> I was thinking about reworking release notes. Right now we have this rigid structure that never really works, half the sections we have are stuff I've never seen used
14:42:02 * randomuser is intrigued
14:42:05 <pbokoc> and at the same time, fedora has a bunch of special interest groups
14:42:24 <pbokoc> so how about basing the structure on those
14:42:40 <randomuser> it would make sense to model the book after the community that way, yeah
14:42:48 <pbokoc> we could send a mail to each group and ask them to tell us what they did for the next release, and we'd just compile that
14:43:01 <zoglesby> indeed! we have needed a change since the workstation/server/cloud change anyway.
14:43:15 <randomuser> do we want to restructure it that way for this release?
14:43:25 <pbokoc> I think it might be a wee bit late for that
14:43:30 <pbokoc> 2 weeks till beta
14:43:42 <randomuser> change freeze tomorrow for beta
14:44:12 <pbokoc> also we'd need to sort of split the book into 2 parts - changes (those don't really map to SIGs) and SIGs themselves
14:44:30 <randomuser> well, many changes map to SIGs
14:44:42 <pbokoc> or "changes + stuff that spans multiple groups"
14:44:47 <randomuser> even if we have a 'core' pseudosig
14:45:58 <randomuser> pbokoc, for now, open a pagure issue?
14:46:05 <pbokoc> alright
14:48:09 <randomuser> Quiet here... anything else for today?
14:48:29 * jsmith has nothing else
14:48:31 <randomuser> I'm deliberately not touching on publishing stuff b/c I'm not caught up with the list thread
14:49:06 <randomuser> okay, calling it
14:49:10 <randomuser> thanks for coming
14:49:13 <randomuser> #endmeeting