17:01:41 #startmeeting Docs Publishing Meeting 17:01:41 Meeting started Wed Aug 12 17:01:41 2015 UTC. The chair is zoglesby. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:49 #meetingname Fedora Docs 17:01:49 The meeting name has been set to 'fedora_docs' 17:01:55 #topic Roll Call 17:02:12 Please join https://bluejeans.com/752806277 17:02:16 we're in a room (room 6) setting up, standby. 17:03:53 * randomuser initializes 17:04:08 beep boop beep 17:04:20 zoglesby, do you have the bjn link handy? 17:04:28 https://bluejeans.com/752806277 17:04:36 ty 17:06:56 #topic Talking in https://bluejeans.com/752806277/browser 17:07:28 jsmith: ping 17:07:28 zoglesby: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings 17:07:42 zodbot: no I will not 17:07:58 zodbot is anti-nudity .. sad really 17:17:40 qa is already doing CI with buildbot 17:17:42 #link attendance 17:17:45 #undo 17:17:45 Removing item from minutes: 17:17:55 #link http://buildbot.net 17:18:27 #link https://github.com/immanetize/anerist 17:18:44 anerist is a good start, randomuser needs help working on it 17:33:28 are we still working on docs stuff 17:33:43 nb: yes 17:33:47 room 6 it seems 17:45:57 * nb is here now 17:47:17 my second nb is gone now 17:47:34 I did have a ZNC connection that only connected to a few channels so i could use it on my phone 17:47:37 but i pretty much never use it 17:59:33 * Git repos that have a web editor and interface option (Pagure) 17:59:33 * Writers can fork a repo, then they write 17:59:33 * Writers need to be able to build their version of the repo for preview (this should be able to be done via the same auto-publishing process) 17:59:33 * Writers can send a PR to get their patch/change in 17:59:33 * Changes are accepted by a more restricted group of contributors 17:59:35 * Branches for each release are automatically built, tested and published based on a commit action 17:59:37 * Today, testing is not well defined, but may be something like emender (think modular) 17:59:39 * publishing is modular based on markup (docbook, rst, md, etc.) 17:59:41 * publishing needs to include a common visual theme and a rebuild of menus, etc. 17:59:43 * Probable publishing workflow 17:59:45 1. Based on commit changes, rebuild the changed repo content to html 17:59:47 2. Generate metadata to be used for the top-level menu/site generation 17:59:49 3. Re-generate the top-level menu/site from the new source and existing unchanged sources 17:59:51 * git repos are organized as master (rawhide) and branches for each release 17:59:55 Team Ideas 17:59:57 * git structure (pagure - may mostly be confirming functionality/config) 17:59:59 * process for triggered publishing/testing (this has been started with buildbot) 18:00:01 * sub tasks to create builders based on the specific markup (docbook first) 18:00:03 * Visual design and meta site builder (needs help - static site generation?) 18:00:15 .hello bex 18:00:16 bexelbie: bex 'Brian (bex) Exelbierd' 18:01:44 * Translation Ideas 18:01:44 * push new strings to Zanata on commits 18:01:45 * allow for publishing of translations automatically 18:11:22 Wow, I have good timing... My ISP finished up with 20 minutes left, then chrome wouldn't connect :P 18:11:27 Hey all 18:11:33 Lots of good talk, notes to come. 18:11:50 #info see list for better notes 18:11:53 #endmeeting