14:02:33 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:02:33 Meeting started Mon May 16 14:02:33 2016 UTC. The chair is zoglesby. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:02:33 The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings' 14:02:39 #meetingname Fedora Docs 14:02:39 The meeting name has been set to 'fedora_docs' 14:02:47 #topic Roll Call 14:02:54 * grundblom here 14:03:25 .hello LinuxHippie 14:03:26 linuxmodder: Sorry, but you don't exist 14:03:29 .hello linuxmodder 14:03:30 linuxmodder: linuxmodder 'Corey W Sheldon' 14:03:34 .hello bex 14:03:36 bexelbie: bex 'Brian (bex) Exelbierd' 14:03:40 (has to bounce at 1030) 14:03:49 .hello drewmeigs 14:03:50 drewmeigs: drewmeigs 'Drew Meigs' 14:04:34 if I d/c or have to leave /#nick/ me and I'll check the logs 14:04:51 going to give it a few more minutes for others to join 14:05:07 also I need to get notes together as I was not ready to run the meeting 14:05:29 zoglesby, thanks for stepping up to do it 14:06:03 #info Participants are reminded to make liberal use of #info #link #help in order to make the minutes "more better" 14:07:12 * randomuser arrives 14:07:12 thanks for running the meeting, zoglesby 14:07:25 We did not have a meeting last week so, no follow up. 14:07:31 #topic New Writers 14:07:50 Any new writers with us today? First time at the meeting, etc.? 14:08:40 #chair randomuser 14:08:40 Current chairs: randomuser zoglesby 14:09:15 do we have a setup sssd guide or tie in? 14:09:49 i ask as with Gnome 3.20 sssd and libsoap are making SSO much more accessible 14:09:54 linuxmodder: lets stick to the meeting here please :) 14:10:37 I will take that as no new writers, anyone working with someone new who may need help and or a mentor? 14:12:22 #topic Release Notes 14:12:31 randomuser: what is the status of the release notes? 14:12:53 we have a decent amount of content, but I've struggled to publish it 14:13:41 when I published for the previous release, publican did not create a "fedora 23" section of the menu, it put those docs at the top of the product's doc list 14:14:10 ... with no discernible adjustment to the factors used to build the menu 14:14:27 hopefully I'll figure that out in the next couple of days 14:14:54 .hello ryanlerch 14:14:55 ryanlerch: ryanlerch 'ryan lerch' 14:15:11 I also intend to review @standard packages for changes, and there are surely other packages with notable changes if folks want to do the research 14:15:11 good luck randomuser! 14:16:24 Can anyone help randomuser with that? 14:16:48 I can come mid week 14:17:04 #info randomuser could use help with publishing problems 14:17:08 today and tomorrow are crap for me 14:17:30 linuxmodder: great, sync up with randomuser when you can help! 14:17:38 will do 14:17:40 linuxmodder, you're welcome to try, but it's a somewhat esoteric problem space, and your docs time might be more effectively spent on other things 14:18:10 that said - not turning down any help :P 14:18:11 I can not help too :) 14:18:23 and stick to the guides 14:18:37 anything else on release notes? 14:19:29 yes 14:19:35 someone needs to push POTs 14:20:10 POTs? 14:20:24 can someone tell me what POTs means? 14:20:33 seconded 14:20:37 3rd 14:20:38 * nirik has a query for open floor or the like. 14:20:43 the source files for translations 14:20:58 so i18n stuff 14:21:02 publican generates POTs, we push them to zanata, we get POs back. 14:21:10 nirik: okay! 14:21:19 yeah, the T stands for Template 14:21:32 grundblom: for translations https://en.wikipedia.org/wiki/Gettext 14:21:48 so, I'll do that today unless someone else does it first 14:21:52 we can move on 14:22:14 https://en.wikipedia.org/wiki/Gettext 14:22:19 ah 14:22:25 #topic Publican/Publishing 14:22:38 I could say a lot here, but I will try not to do so 14:22:43 * linuxmodder has to leave will catch up with minutes :) 14:22:53 * randomuser smirks 14:23:04 First, the report from the FAD is on the community blog 14:23:10 #link https://communityblog.fedoraproject.org/event-report-fedora-docs-fad/ 14:23:17 Should we skip this in lieu of the FAD report .. since it is all going to change 14:24:02 I am using this section as our "way forward" block 14:24:34 i like it 14:24:35 Next, the source for what we are working on, and the issues/tasks are on pagure 14:24:36 #link https://communityblog.fedoraproject.org/event-report-fedora-docs-fad/ 14:24:40 #undo 14:24:40 Removing item from minutes: 14:24:46 we do have some todo items, yeah 14:24:51 #link https://pagure.io/docs-fp-o/ 14:25:04 #link https://pagure.io/docs-fp-o/issues 14:26:01 notably, imo, someone needs to figure out how to create the landing pages 14:26:19 If you see something in the issues section that you can help with please jump in and help. I would like to see this work start to progress quickly, but hands and brains are needed. 14:26:24 * randomuser did not absorb much ducktype knowledge from shaunm and did not find reference materials 14:26:28 * c0mrad3 waves 14:27:23 the last part along that line is that I started to redo the documentation guide, and as we work on that it will outline the new process 14:27:26 #link https://pagure.io/documentation-guide/branch/new-workflow 14:27:37 again, help is always welcome 14:28:35 #info zoglesby will be in #fedora-docs Thursday during office hours to answer questions about the FAD and our new publishing system 14:28:35 randomuser: i have been looking at how i can style pintail 14:28:50 the most interesting thing here, imo, is that we're tracking tasks somewhere :P 14:28:53 should have a better handle on it by the end of the week 14:29:12 ryanlerch: that is great news! 14:29:23 just need to learn xslt 14:29:23 +1 for task tracking :) 14:29:30 again 14:30:11 anyone else have anything for this section of the meeting? 14:31:08 ryanlerch++ 14:31:08 randomuser: Karma for ryanlerch changed to 14 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:31:24 feel free to ask me questions any time, but I have dedicated time on Thursday if you want to talk in real time and know that I will be around 14:31:24 nomnomnom 14:32:06 #topic Guide Status 14:32:17 anyone have anything on guides? 14:34:58 I will take that as a no. 14:34:59 #topic GSoC Updates 14:35:33 and c0mrad3 is here, huzzah 14:35:46 o/ 14:36:08 c0mrad3 is a week away from the start of the coding period, but we still need to work out his goals 14:36:39 zoglesby: yes 14:36:39 that is something that we need to do this week and will report back on next week 14:36:54 c0mrad3: any other updates for the group? 14:37:12 I will attend the office hours this time and we shall discuss at that time zoglesby 14:37:44 zoglesby: nothing much for the community bonding period 14:38:20 c0mrad3, when do you plan to be online? 14:38:30 just so those of us not in NA can think about overlaps 14:38:31 looking forward to your community bonding, c0mrad3 :) 14:39:15 bexelbie: around the same time on thursday 14:39:19 randomuser :) 14:40:10 c0mrad3, can you phrase that more absolutely, like you'd read it from a clock? 14:40:51 * randomuser is dense, needs things explained 14:41:07 c0mrad3: I think the question is, during GSoC, what hours do you plan on working during 14:41:21 randomuser: 15:00 - 17.00 UTC 14:41:25 as zoglesby yes .. but only roughly 14:41:33 c0mrad3, ok cool, so nice overlap with EMEA 14:41:37 and I understand that it will fluctuate 14:41:52 * bexelbie will tolerate no fluctuations .. just kidding 14:42:31 ok, so you'll be around before thursday's office hours, cool 14:42:41 nice overlap with AEST too :D 14:42:45 i'll try to be available 14:43:11 0100 - 0300 :) :/ 14:43:22 ryanlerch, did you know that in the southern hemisphere, clocks and toilets spin counterclockwise? 14:43:24 * randomuser ducks 14:43:40 they do? /me goes to flush the toilet 14:43:45 okay, moving on as we are short on time 14:43:46 #topic Outstanding BZ Tickets 14:43:52 #link http://tinyurl.com/lbrq84 14:43:59 bugz bugz bugs 14:44:05 zoglesby: I will working from 11:30 - 18:30 UTC for the first few days and will be flexible in the next days 14:44:18 * c0mrad3 I was late! 14:44:42 on a side note, the best part of rewriting all of the guides is that as we do we can close all of the bugs we have! 14:44:49 yay! 14:45:16 anyone have anything else here? 14:45:20 we should also look into.. what, removing the Fedora Documentation product from bugzilla? we aren't really going to use it anymore 14:45:22 let's crush some bugs! 14:46:01 randomuser: I think we need to talk about that more before we do so 14:46:07 randomuser: are we shifting to trac / pagure ? 14:46:08 randomuser: can you post that to the list? 14:46:59 #action randomuser to bring up future bugzilla usage plans on list 14:47:14 thanks! 14:47:24 anything else? 14:47:57 #topic Open floor discussion 14:48:15 nirik: thanks for waiting, your up. 14:48:22 Oh hey... so... 14:48:40 we currently have about 3 docs things in infrastructure. 14:48:57 The current 'production' thing with publican docs in git repo 14:49:16 the docs-backend thing with rpm builds in koji for guides 14:49:16 'production' 14:49:26 some cloud instances for another setup 14:49:51 Do we need to keep all these? :) or should we wait and see what the new world looks like before doing anything? 14:50:06 the rpm thing is the el6-docs koji tag, right? 14:50:09 we're definitely done with that 14:50:17 are the rpmbuilds thing for desktop packages? 14:50:37 ryanlerch, it was an attempt to replicate the brew publishing workflow 14:50:46 randomuser: yes. ok. can nuke it... and/or did you want to file a ticket to nuke it so we don't forget? 14:51:09 sure - releng or infra ticket? 14:51:44 infra probibl 14:51:47 probiby 14:51:48 k 14:52:06 are the cloud instances still of use? or can they be nuked too? 14:52:39 we might have need for them soonish, actually, let me get back to you on that 14:52:50 ok, completely fine. ;) 14:53:02 just wanted to check... 14:53:10 nirik++ 14:53:13 sure, thanks 14:53:30 #action randomuser to file ticket with infra to remove el6-docs koji tag 14:54:11 and the docs-backend01 host. 14:54:36 thats all I had. 14:55:18 any other topics? (5 min left) 14:55:36 sssadssaassaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaasasaaaaaaaaaaaaa 14:55:43 whoops. sorry 14:56:24 ticket filed 14:56:41 hey nirik, since you're here, what do you think about elasticsearch 14:56:59 good call! 14:57:11 we're looking at a publishing tool that can use it 14:57:31 I've not used it, but I know it's packaged now (at least for fedora) 14:58:17 * randomuser nods 14:59:29 i'll study up, in any case 14:59:46 #info pintail has support for elasticsearch and we need to look at using it for search on docs site 15:00:19 with that we need to end this meeting. Thanks you everyone for your time. 15:00:21 #endmeeting