14:03:18 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:03:18 Meeting started Mon Nov 28 14:03:18 2016 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:18 The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings' 14:03:18 #meetingname Fedora Docs 14:03:18 The meeting name has been set to 'fedora_docs' 14:03:18 #topic Roll Call 14:04:28 * Capesteve waves 14:05:05 good day to you, Capesteve 14:05:18 GDTY too 14:05:35 quack 14:06:18 * pbokoc 14:06:40 #info Participants are reminded to make liberal use of #info #link #help in order to make the minutes "more better" 14:09:04 #topic New Writers 14:09:26 any newer folks with questions they'd like to get out of the way? 14:11:53 quiet morning 14:12:04 indeed 14:12:50 no action items from last week, so 14:13:00 #topic Where are with the Release Cycle and Docs 14:13:19 #info F25 GA release is out, stuff was published 14:13:37 #action randomuser to publish available translations 14:13:45 ? 14:13:51 because that still needs to be done 14:14:27 yes, Southern_Gentlem ?\ 14:15:01 if possible can the release notes and installation guide be published at least a week before release ? 14:15:24 not retroactively, no 14:15:46 the schedule does want us to publish sooner, fwiw 14:16:36 we get a lot of questions from people the week before in the #fedora channel 14:16:50 * randomuser nods 14:17:28 Southern_Gentlem, that's good feedback, we'll make an effort to publish sooner next cycle. 14:18:58 there's also pagure issues for any content issues, feel free to direct people there for requests and such 14:20:24 I think the specific doc topic will be just as lively... 14:20:47 is there anything in particular the attendees today would like to discuss? 14:21:11 *crickets* 14:21:51 I mean... f26 is supposed to be the release where we switch to asciidoc and a new website, isn't it? 14:22:07 ahyup 14:22:16 we should probably make some sort of a plan for that 14:22:38 #topic Publishing Plan 14:22:58 I wanted to do asciidoc conversion first, personally 14:23:46 it seems like a more productive activity than coding the tools 14:23:51 ...for me 14:23:58 it is 14:24:09 so we'd convert book sources to asciidoc, but publish by getting docbook output from that and then with publican still? 14:24:27 * randomuser gulps 14:24:31 i hope not! 14:25:05 I recommend picking one document and working at it, and not just doing a simple format conversion, but really thinking about a topic-based structure 14:25:20 * randomuser nods 14:26:02 and not the install guide 14:26:12 there are apparently some holes in the format conversion tools, bexelbie came up with a list, basically what's on pkovar's blog article from back when 14:26:26 well the thing is, if we move to topics, we'll need to figure out some sort of content map - what topics we need, what would be nice to have, how they relate to each other 14:26:40 so i have at least identified such things and started on regexing them out 14:27:02 pbokoc, enter sgilson? 14:27:37 maybe I should email him out of band and see if he's still on board for strategizing 14:28:57 well, anyway, I'm wary of trying to get to meta about it 14:29:14 there's existing content I'm sure can be categorized quite intuitively 14:30:09 yeah, I think that's where we should start. Split existing content into self-contained chunks in separate topics/articles/whatever and string them together 14:31:08 .hello bex 14:31:09 bexelbie: bex 'Brian (bex) Exelbierd' 14:31:11 * bexelbie is sorry for being late 14:31:29 welcome, bexelbie 14:32:44 I am wondering if we should see if each doc has an owner who wants to make it into topics 14:32:56 for those folks we could have them work together on a single doc to get a feel for the process 14:33:08 then tools people could work with that docs while the owners organize the rest 14:33:09 hm 14:33:16 for docs with no converter we could just convert them to asciidoc as is 14:33:21 or decide if we need to keep them at all 14:33:30 that way we get all content to asciidoc and have two teams strategizing 14:33:41 I do not mean to say owners should do all the work for their doc, but should def organize it 14:34:06 eom 14:34:30 I'm also wary of making plans that involve participation not volunteered... 14:34:33 most docs have "owners" who aren't active... 14:34:52 its a good time to clean that list 14:34:59 (I AM ALIVE) 14:35:11 so I can make plans like "I am willing to work on content conversion" and generally understand what else needs to happen 14:35:37 I would not voluntell anyone - agreed 14:35:48 I think conversion organizers need to step up ... and cleaning the list is good per zoglesby 14:36:10 * terminal__ is here now also, apologies for lateness, but i've read the meeting up to this point also 14:36:25 I'm just glad zoglesby survived that ferris wheel incident 14:36:42 hello, 14:36:49 my first time meeting in this list 14:37:27 Hello Luc__ 14:37:41 zoglesby, clean the list, how? 14:37:52 if I want to modify content of wiki 14:37:53 https://fedoraproject.org/wiki/ScreenCasting#Using_Gnome.27s_embedded_screencast_tool 14:38:00 is that part of scope of this group? 14:38:06 So we need to put together a "final" conversion tutorial, and then ask people to start working? 14:38:31 or just the fedora documentation? https://docs.fedoraproject.org/en-US/index.html 14:38:47 randomuser: find out if people are still willing to own guides, find new owners for guides that need them discontinue guides that we can't support 14:38:51 Luc__, the wiki is a collaborative effort of everyone in Fedora, but not a specific charge of Docs 14:39:12 so it will just be a docs.fedoraproject rithg 14:39:43 ok, I need to understand what the group is doing first... I will read archive 14:39:53 ok 14:40:18 our active guide owners are basically Capesteve and pbokoc 14:40:21 I think you need to work your way through one first before you can write a tutorial for others 14:40:37 very true, good call 14:41:01 #chair pbokoc zoglesby shaunm 14:41:01 Current chairs: pbokoc randomuser shaunm zoglesby 14:41:04 sysadmin guide is a prime candidate for that 14:41:07 I agree with shaunm on having one doc worked first - but I think it is critical that active guide owners who want to own topic based conversions participate int hat 14:41:20 I'm going to need to part for a commute soon 14:41:59 another quick, I request to join this group but not accepted yet. Who can help me? 14:42:00 do you want me to take one over? 14:42:12 or work in pair with an existing guide owner? 14:42:21 sure, shaunm, participation welcome 14:43:06 I think you helping drive the topic conversion is a huge help shaunm 14:43:42 there's a relatively well known set of tasks available, I don't want folks to be roadblocked because we're not giving specific instructions for how to go about them 14:43:57 Luc__, those tasks are places where you can start 14:44:11 or, are we thinking that if there's a procedural checklist people will show up to complete it? 14:44:12 Luc__, there isn't a formal "you're in" process - we accept all contributors 14:44:39 is there a list of guides with owners? pretty sure there is on the wiki 14:44:48 guessing somebody has the link handier than my searching 14:45:22 https://fedoraproject.org/wiki/Docs_Project_admin_notes 14:45:40 the table is an include, that's just the page I had up 14:46:03 oh, the links on that need to be updated to pagure 14:46:49 Luc__, that would be easy to pick up, if you're interested 14:46:53 another option is the security guide, sparks has said he is ready to work on it when we give him the go, and I think he has the support of his boss at rh. 14:47:22 thanks, I will read and follow 14:47:34 neat 14:48:30 zoglesby: doesn't look like we've published the security guide in a few releases 14:48:57 since F19 in fact 14:49:09 is that table accurate in terms of releases they apply to? 14:49:17 okay, i have to go, someone can close out the meeting? 14:49:38 terminal__, no, the table is not up to date in that regard 14:49:49 ah ok 14:49:54 I'm just going on what I see published on docs.fp.o 14:50:30 I got blocked by CLA+1, I ask some group but not pass through 14:50:34 not even able to edit wiki now 14:50:59 maybe the best bet is to post to the list and ask if any doc owners want to work with shaunm to convert there doc as a first run? 14:51:16 Luc__, right, i guess there were spam issues or something so they upped requirements for wiki edits 14:51:16 zoglesby: I was just halfway through typing the same thing :) 14:51:38 you want to take that action item? 14:51:45 yeah, I can do that 14:51:48 i'm going to go ahead and assume that one of the chairs can #endmeeting when the time comes 14:52:01 * randomuser & 14:52:21 #action shaunm to mail the list to find a doc owner to work with on conversion 14:52:27 Luc__, perhaps you could start with a documentation contribute via pagure.io that would earn the docs group which would put you at CLA+1 14:52:42 Luc__, otherwise I suggest you approach commops if you are interested in only working on the wiki 14:54:05 anything else? 14:55:42 * bexelbie is good with this plan - lets move forward with hopefully a team starting on topic conversion by next week 14:56:54 ok 14:57:06 zoglesby: want to end the meeting? 14:57:18 #endmeeting