18:31:37 #startmeeting Fedora Docs Workshop 18:31:37 Meeting started Thu Mar 26 18:31:37 2015 UTC. The chair is randomus`. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:31:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:31:58 #chair yruseva 18:31:58 Current chairs: randomus` yruseva 18:33:21 um, wait, what? 18:33:32 randomus`? :) 18:33:48 yeah, we decided you're the new docs project lead 18:33:51 have fun 18:34:05 * randomus` runs away 18:34:39 haha I only opened xchat to check some network names to join from my personal laptop 18:34:52 well, um 18:34:59 thanks for the honour 18:35:04 free ice cream for everyone :D 18:35:27 what would you have us do, oh dear leader? 18:35:42 best leader evah! 18:36:24 https://theboeskool.files.wordpress.com/2014/12/kim-jong-un-7.jpg 18:39:07 All in favor of randomus` being named the Benevolent Doctator for Life, raise your hands and salute him! 18:39:47 I've been doing that every time I see his name on IRC... you mean I'm the only one?! 18:40:11 pbokoc, we didn't want to tell you... 18:40:14 pbokoc: At least the only one willing to admit it in public... 18:40:59 you're compulsively saluting? this could be fun... 18:41:12 :D 18:41:13 oh, no, I just raise my hands 18:41:31 oh, ok 18:41:40 I mean, how do you even salute with both your hands raised 18:42:14 I raise both elbows whenever I see pbokoc online 18:42:57 * smccann thought randomus was the more interestic nick... very roman 18:43:11 http://media.giphy.com/media/KJmORsw9VYFQQ/giphy.gif 18:43:30 :D 18:43:49 I assumed this happened in your office, all day 18:44:43 no, we just have a giant ball we occasionally throw around... you know, the kind normal people sit on 18:45:35 that's fun too 18:46:12 so, did everyone get a chance to read the email I sent to the list about standardized metadata? 18:46:20 and further, did you care? 18:47:51 oh, I missed that 18:48:32 there's even a glaring omission, just to help you get engaged 18:49:09 ಠ_ಠ 18:50:37 jsmith or bcotton will probably pick it out away, so I feel the need to pretend it was deliberate 18:51:36 oooh, I found it! I think Mr. Obvious Pseudonym is not a real person! 18:53:54 ehh... no 18:56:09 so anyway, I'm not sure where you're going with that... where would we use the information? 18:56:34 any tools that format and present the documentation could use it 18:58:18 right, so we wouldn't necessarily depend on publican to build the website, or we could, I don't know, package all docs and have some system to sort everything and create a splash page? 18:59:16 yes, exactly 19:00:06 well, that sounds cool - and not too hard or time consuming to do, so why not 19:00:39 yeah, I already started building the 'some system' 19:00:44 even though... I think the bigger a certain document is, the less useful the description would be 19:01:19 if you have something like the System Administrator's Guide that has a few hundred pages and covers 30 wildly different topics... 19:01:41 having avenues for short articles should help scope creep, I would think 19:05:57 true 19:06:56 we'll need a definite list of acceptable values for a lot of fields though 19:07:28 indeed 19:09:19 especially the taxonomy stuff, or it would get out of control 19:10:11 yeah, nothing better than having each tag used exactly once because there's a difference between "network" and "networking" :)) 19:11:03 ohh... good point 19:11:23 I dunno that I want to make something that has user-visible tags, tbh 19:11:51 maybe just drop them in the html header, or use them for some mythical search feature 19:12:15 I don't think there's any harm in that, but not much to be gained either 19:15:39 * randomuser groans 19:15:51 tags would be very difficult to control 19:16:25 you'd end up with a whole layer of request/approval for every new article 19:16:36 I don't think they'd be more difficult than the taxonomy stuff... we'll need to automatically check that too, anyway 19:17:16 sure, but with the taxonomy stuff, we could probably sit here for an hour or two and knock out a draft that would cover almost everything 19:17:39 but tags could be a set of attributes specific to that one article 19:21:28 I guess it would depend on how easy or hard it would be to add a new tag 19:21:43 if it's easy, and the only barrier is that not everyone can do it, then we could add them on the go 19:21:54 I can't think of a way to do it without human involvement 19:22:19 someone makes a new article, goes through existing tags, and finds that there aren't any existing tags specific enough - so they ask someone with access to create a new one 19:22:34 but yeah, I can't think of a way to do it without a human "gatekeeper" 19:22:36 that would work at this scale, sure 19:23:28 I guess we'll have to wait for Skynet 19:23:38 but if we get a 50 or a hundred or more people writing, and one percent write or edit one article each day, and half of those article edits involve adding tags... 19:24:01 that's like 4,375 new tags per minute 19:24:03 well, that would be a good problem to have :) 19:24:09 yes 19:24:21 we'd have to hire an army of primate tag wardens 19:24:39 as I'm saying, Skynet 19:24:57 or one of us could just go full Lawnmower Man 19:25:33 I nominate ignatenkobrain 19:26:44 anyway, what we do with the tags isn't as crucial at this stage as the question of whether or not tags would be valid in the proposed specification 19:29:21 so where do you propose the metadata be stored? As a separate file in each repo? Some sort of header hidden in a comment in each document's source? 19:29:52 packaged with the documentation somehow 19:30:15 using in a comment would sort of defeat the purpose of abstracting this information from the document's markup format 19:30:32 yeah, that's true 19:30:59 but on the other hand, we could do fun stuff like having different sets of metadata for different parts of a single big document 19:31:02 but, I do have a halfway written thing to extract the title, subtitle, and abstract from ie Book_Info.xml 19:31:29 hey.. now that is an interesting idea 19:31:52 randomuser: Let me guess -- you're not using XPath to get that data :-p 19:32:00 that would be really helpful for e.g. the cookbook 19:32:29 jsmith, BeautifulSoup :) it's adequately simple. 19:33:38 ...but then again, someone would have to maintain that 19:34:08 pbokoc, it might be doable with... say, a markup: attribute and something to signal which section the metadata describes 19:34:36 then $tool that knows about $markup would know how to find that section in that markup 19:36:16 yeah, that's what I'm thinking 19:36:31 https://github.com/immanetize/anerist/issues/2 19:36:41 but I don't want to be the person to tell Capesteve to go make 30 different configs each pointing to a different part of the sysadmin guide :) 19:37:08 ? 19:37:12 actually, you got me thinking bow 19:37:15 bowbowbow 19:37:18 oh, hello Stephen :) 19:37:39 someone asked about how linking between docs would work in this thing, and I hadn't figured it out 19:38:05 but, if $tool can make anchors for named sections, it can also produce a list of anchors that a given document provides 19:38:48 so if I wanted to link from my very short firewall tutorial to the Networking Guide, I could discover the link by browsing to that section of the NG and pressing some magic button 19:39:03 #chair 19:39:07 #chair pbokoc 19:39:11 #chair Capesteve 19:39:21 I have to go back to work, you kids have fun 19:39:26 share your popcorn, Capesteve 20:09:10 #endmeeting 20:09:31 no? oh well 20:32:45 #endmeeting harder 20:33:05 zodbot stopped responding at some point before you made me chair 20:33:34 oddly, I still get fedmsg signal about the meeting ending 20:33:47 it still logs the meeting though: http://meetbot.fedoraproject.org/fedora-docs/2015-03-26/fedora-docs.2015-03-26-18.31.log.txt 20:34:18 * pbokoc wonders if having that link appear in the meeting log inside the link will make the thing explode 20:34:32 fedora-notifs> randomus`'s meeting titled "Fedora Docs Workshop" ended in #fedora-docs https://meetbot.fedoraproject.org/fedora-docs/2015-03-26/fedora-docs.2015-03-26-18.31.html 20:34:32

randomus`'s meeting titled "Fedora Docs Workshop" ended in #fedora-docs https://meetbot.fedoraproject.org/fedora-docs/2015-03-26/fedora-docs.2015-03-26-18.31.html 20:34:40 hm 20:35:00 I was just gonna point that out :-D 20:35:02 #endmeeting