14:15:52 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:15:53 Meeting started Mon Oct 17 14:15:52 2016 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:15:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:15:53 The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings' 14:15:53 #meetingname Fedora Docs 14:15:53 The meeting name has been set to 'fedora_docs' 14:15:53 #topic Roll Call 14:16:13 paste from the page, Pete, not to the page... 14:17:39 .hello bex 14:17:40 bexelbie: bex 'Brian (bex) Exelbierd' 14:17:48 randomuser, zodbot bot should just be smart enough to auto-agenda 14:18:04 that's a good idea, bexelbie 14:18:07 something like #nexttopic :) 14:18:28 randomuser, left you a PM as well 14:18:28 * pbokoc 14:18:38 how do you do that pbokoc ? 14:18:49 magic 14:18:59 (/me) 14:19:00 that explains a lot about you 14:19:09 bueno as the TV here just said 14:19:26 /action 14:22:13 ok then, we're here 14:22:38 #topic Where are with the Release Cycle and Docs? 14:22:57 we need to push translations 14:23:17 habitually and incidentally 14:23:50 I'd like to set up one of our cloud instances to do so programatically for us, I think 14:24:15 +1 14:24:39 I'd love to see translation comment on how often they want pushes and republishes as well 14:24:45 the whole 100% versus mix issue 14:25:18 You know, I've asked them a few times, and I don't know there's a one true path 14:25:43 randomuser, I believe a lot of them will be at FUDCon APAC - I'll try to start some f2f around this 14:26:12 the consensus from the person I talked to here was push often to translation and republish everytime English changes .. even though that means a mixed document 14:26:14 I think they most want us to be predicatable and consistent 14:26:18 here == FUDCon LATAM 14:26:39 predictability ... so ... predictable :P 14:28:05 i can say firsthand that waiting for 100% translation is not a good idea 14:28:25 works simply do not get to 100% 14:28:52 then let's make a definition of predictable for us and cc their lists for feedback. I suggest we follow your lead, randomuser, and get a builder to do it and we adopt a pull and republish on all English changs 14:28:55 changes 14:29:27 we should know if a team has opted for review, and publish all reviewed or available translations depending on their choice 14:29:48 randomuser, as long as we can automate it :) 14:30:08 on that, I would like to have English builds and translation builds separate actions 14:30:35 if I update a doc and publish it immediately, we obviously would not immediately have the translations available 14:30:57 randomuser, are you proposing a queueing system or a manual second action to get trans published? 14:31:19 that just gave me a builder idea ... 14:31:23 I was thinking a nightly/periodic rebuild of translations 14:32:25 because pulling in POs is frankly quite slow, and pulling all langs on every publish is going to take a republish job from ~30s to ~30m 14:32:28 randomuser, it'd be great if we could get Zanata to tell us if there are changes so we don't publish without need 14:32:37 ~30m is generous :P 14:32:42 * randomuser nods 14:33:00 the transifex API was better designed for that purpose 14:33:01 I should see Alex Eng in APAC - I'll see if he has signaling ideas from a Zanata perspective 14:33:38 I know they've added some features in that area in the last year or so, but don't recall what 14:33:58 I'll let you know what I hear 14:34:16 in the meantime, I see no reason not to push POTs all the time from release branches 14:35:03 +1000 14:35:23 But I also think we could easily put that on a timer so we don't do it a lot if we have a lot of translations 14:35:42 something like push no more than 1/hour or 1/day as is appropriate 14:36:12 why hold back? 14:36:36 was thinking it could cuase problems if someone was actively translating 14:36:40 but you're probably right 14:37:33 I can easily support push POTs on all English updates and dial it back if t18n asks us too 14:38:35 I wasn't making a statement; I really do not know why they would ever prefer to have outdated POTs in the system 14:39:02 agreed 14:39:59 but yeah, talk to them about it 14:40:10 will definitely do 14:41:04 otherwise, our release cycle activity should focus on guides at this stage 14:41:06 so 14:41:12 #topic Specific Doc Status 14:41:43 Any guide coordinators around today? 14:43:27 sounds like not 14:43:27 #topic Open floor discussion 14:44:45 do we have convo to have around publishing yet? 14:44:53 randomuser, I want to set dates for us to meet 14:45:11 yes, please, I need to give those dates to my employer 14:45:50 Anytime between 21 and 27 - what is best for you? 14:46:31 I'm thinking over that weekend or monday/tuesday but let me get back to you 14:47:15 i'll email/telegram/call/carrier pidgeon/smoke signal 14:47:31 randomuser, please - I need to get beds and tickets bought :) 14:47:46 * randomuser nods 14:47:46 also would like a hotel recommendation in Austin that is convenient for you - remember I don't drive :P 14:48:17 will work on that too 14:48:49 I do drive, convenience is relative 14:49:25 I have $dayjob stuff building up this morning, let me get back to you a bit later 14:49:26 uber drives too :P 14:49:31 sounds good randomuser 14:49:50 no uber in austin 14:50:07 is there a similar service, assuming uber is a generic noun? 14:50:41 categorically, those services are now legally required by the city of austin to do rigorous backround checks on their drivers 14:50:51 and they pretty much all just backed out 14:51:31 ahh 14:51:43 * bexelbie picked the wrong month to be without his driver's license 14:52:16 we'll sort it out, i don't mind driving as needed 14:52:34 brb .. going afk to deal with the real world 14:52:45 yeah, let's wrap this up 14:52:51 #endmeeting