23:00:10 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 23:00:10 Meeting started Wed Jul 13 23:00:10 2011 UTC. The chair is Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:00:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:00:13 #meetingname Fedora Docs 23:00:13 The meeting name has been set to 'fedora_docs' 23:00:17 #topic Roll Call 23:00:20 * Sparks 23:00:30 * jjmcd 23:00:40 jjmcd: Oh! You came to run the meeting? 23:00:56 naw, perfectly happy letting you do it 23:01:01 lol 23:01:37 I bet you are 23:02:43 so, where are the other suspects ... sgordon, nb, zoglesby, fnadge, jhradlek 23:02:50 sorry 23:02:52 got distracted 23:02:55 * sgordon 23:03:01 BTW, rudi won't make it 23:03:02 * fnadge is kind of here 23:03:04 having one of those weeks 23:03:16 * mprpic is present 23:03:36 jjmcd: It would appear that the agenda hasn't been updated for a while 23:03:46 yeah 23:04:10 I almost did yesterday, but I didn't know how much you wanted to focus on olf 23:04:48 Well... it's getting late and we should probably really talk about OLF 23:04:52 * ke4qqq appears 23:04:57 woo hoo 23:05:01 I'm here 23:05:02 jjmcd: Care to update the agenda while I get myself straight? 23:05:06 ke4qqq: Excellent! 23:05:34 working ... 23:05:54 i'm here 23:08:05 WOW the gang's all here 23:08:12 * bcotton is here too 23:08:14 got action items updated, continuing on rest 23:08:23 * jhradilek is here as well, just for the record. 23:08:55 OK, now its there - missed the stupid equation 23:09:06 my baby is here as well, but she doesn't want to type right now 23:09:42 jjmcd: I don't see the delta 23:09:52 bcotton: Soon enough! :) 23:09:58 now that's weird ... I can go back and edit it more 23:10:06 Okay, let's get started with some OLF talk 23:10:11 gomix - astrophhysicst 23:10:31 #topic FAD @ OLF 23:10:40 #link https://fedoraproject.org/wiki/FAD_@_OLF_2011 23:11:26 #info jsmith has an Asterisk server setup and ready for the FAD 23:11:46 So here's what we know... 23:12:27 We can get a conference room at Ohio Linux Fest (OLF) and use it to develop guides for F16 all Sunday. 23:12:33 Anything that needs an extra lift. 23:12:49 wahoo 23:13:11 This is nearly perfect timing for putting the final touches on these guides and getting the POT files to the translators. 23:13:48 We'll also be able to have a VoIP connection for anyone who wants to participate that can't be there. 23:14:24 The current goals on the page are: 23:14:33 * jjmcd will be 1 few miles up the road, sadly 23:14:35 Beta Release Notes at 100%. 23:14:47 User Guide updated for GNOME 3.x, KDE x, and default programs identified and discussed. 23:14:57 Smoothing out the translation process and removing barriers. What do Docs people need to be successful? Translators? 23:15:16 Work on other guides: Security, Cloud, any and all others 23:15:39 Which day of OLF, or are you doing it an extra day early / late? 23:15:44 If you are going to be in attendance please put your name on the list. If you need funding let me know and I'll see what I can do. 23:16:01 #info Plan on having the FAD on Sunday 23:16:04 Did we give up on a new specialized guide? 23:16:07 rbergeron: Thanks for the reminder 23:16:15 jjmcd: Nope 23:16:34 jjmcd: Just need someone to document that on the wiki page and we'll put on the list. 23:16:51 I suppose we can wait until we get a victim then add it to the goals 23:16:58 Yep 23:17:07 Or we can use that time to start brain storming 23:17:25 I'd hate to waste the momentum... 23:17:25 which guide? 23:17:45 * jjmcd reached out to robotics sig - no response yet, and gomix did contact his astro buddy 23:18:18 perspectival, we are looking for some expert to work with writers to produce a new guide like the ARG or Musician's guide 23:18:28 sparks: yeah, having a budget at the bottom of the page can help out, and i'm sure we can get folks there. There is money for fads, so long as we don't go crazy. :) 23:19:04 jjmcd: ah, ok, thanks 23:19:11 rbergeron: Yeah, I guess I need to do some research on what we might need a budget for besides getting people there and housing them. 23:19:15 sparks: the fad template has some of that stuff built into it 23:19:29 * Sparks wonders if he removed that 23:19:37 I think robotics could be a slam dunk if they willwork with us 23:19:39 sparks: that's probably about it, aside from maybe having a group dinner or maybe snacks/pizza day of. 23:19:53 rbergeron: Pizza! Thank you! 23:20:09 http://fedoraproject.org/wiki/Template:FAD 23:20:09 It would be nice to have some swag around for our contributors that do make it 23:20:14 Sparks, gonna link the * box into the Findlay repeater? 23:20:28 jjmcd: Go for it 23:20:44 rbergeron, I assume there will be a Fedora booth? 23:20:49 sparks: i'm sure we'll have the fedora event box and fedora shirts there. 23:20:53 At OLF? Oh yes. 23:20:53 Sparks: let me know on that later 23:21:12 VileGent is the OLF master (though i hear it's his last year volunteering to do so) 23:21:48 VileGent: The swag or the funding or ? 23:21:53 swag 23:22:01 swag 23:22:05 i rather keep 23:22:09 FAD funding is mostly self organized by the FAD people 23:22:12 VileGent: Will do. And I should be able to help you out when I'm not at my "other" booth 23:22:17 FAD and event funding separate 23:22:26 correct 23:22:54 but i think i can find hold back swag for the Docs FAD 23:23:09 later i would like to talk about Fudcon 23:23:19 VileGent: Awesome! 23:24:05 Okay, anyone have any questions about the FAD @ OLF? 23:24:32 #action Sparks to update the FAD @ OLF page with the FAD template 23:26:17 Okay, moving on 23:26:48 VileGent: You wanted to talk about FUDCON now? 23:26:54 http://noname.math.vt.edu/Fedoraunity/FUDCon%20Blacksburg%20Working%20Schedule.ods 23:27:19 #topic FUDCON 23:27:26 well i am trying to preplan as much as possible for Fudcon 23:27:29 #link http://noname.math.vt.edu/Fedoraunity/FUDCon%20Blacksburg%20Working%20Schedule.ods 23:27:55 VileGent: Okay, you have our attention! :) 23:28:43 so if the Doc folks like to have a workshop on introduction to the Docs Project etc and be preloaded as a workshop/hackfest it can be done 23:29:11 VileGent: I think that would be awesome. Perhaps an intro to DocBook XML as well 23:29:14 i figure by then you will would like time to work on f17 docs 23:29:36 Yep. 23:30:14 as you see for hackfest we have lots of room so i like to see it be used 23:30:30 Well, go ahead and put us down for a hackfest. 23:30:32 and be used productively 23:30:55 friday and sunday or just friday or what 23:30:59 And I'd like to see an Intro to Docs and an Intro to DocBook XML and Publican 23:31:31 ^^^ Those being talks 23:31:40 I'm not sure how much time we'll need. 23:31:43 jjmcd: Your thoughts? 23:32:02 Need to noodle 23:32:04 sparks do you think you can cover those on saturday ? 23:32:07 might want 2 sessions 23:32:32 Yeah, I think the two topics are related but mutually exclusive. I can do those on Saturday 23:33:20 Yes, definitely separate 23:33:25 do you think you can cover intro to docs in 2 hours 23:33:40 Prolly intro is 1 hr, XML 2 23:33:42 An hour would probably be a stretch 23:33:45 ya 23:33:47 do you think you can cover intro to docbook in 2 hours 23:33:52 yes 23:33:52 yeah 23:34:10 do you think you can cover publicain 2 hours 23:34:15 * rbergeron thought saturday was barcamp day? 23:34:19 part of the xml 23:34:26 I would put DocBook XML and Publican together 23:34:44 they feed off each other 23:34:52 exactly - publican itself is like 5 minutes 23:35:10 rbergeron: we will have barcamp but i am also preloading some topics as well 23:35:28 #action Sparks to talk with jsmith about helping out with the DocBook XML/Publican talk 23:35:32 #undo 23:35:32 Removing item from minutes: 23:35:36 #action Sparks to talk with jsmith about helping out with the DocBook XML/Publican talk at FUDCON 23:36:12 Sparks, if jsmith can't I prolly can 23:36:40 jjmcd: Yeah, I figured you could. 2 hours is a long time to talk and I'd like to see it tag teamed... :) 23:36:45 I hate travelling in the winter, but my godson goes to school there so I gotta go 23:36:45 rbergeron: i want to be sure we have a wide net to possible get new contributors 23:36:54 yeah, good plan 23:38:31 VileGent: Thanks for thinking of us! Need anything else from us right now? 23:38:43 so looking back at my link i posted Intro to Docs before lunch and docbook xml/publican after lunch 23:38:57 Perfect 23:39:11 that does look good 23:40:36 now go sign up for FUDcon and reserve your hotel rooms 23:40:43 :) 23:41:04 and if there is anything you need let me know 23:41:20 as far as fudcon goes 23:42:18 VileGent: Will do. 23:42:21 Anyone have any questions? 23:43:28 Okay, moving on. 23:43:48 #topic Copyright changes for all guides 23:44:04 #link https://lists.fedoraproject.org/pipermail/docs/2011-June/013474.html 23:44:42 Back in June we agreed to modify the copyright statement on our guides to say "Fedora Project Contributors" instead of "Red Hat, Inc and others" 23:45:11 If you haven't done so already, please update your guides and republish 23:45:41 #action Sparks to file a bug and patch to fix this in the Publican Fedora brand 23:45:54 This is probably something zoglesby will want to track. 23:46:08 Questions/comments? 23:46:08 is this actually in the brand? 23:46:13 or is it in the ent for the book 23:46:27 i thought the brands just put YOU NEED TO REPLACE THE HOLDER ENTITY 23:46:30 or something of that ilk 23:46:37 sgordon: It's in the ent for the book. I was thinking that the ent came from the brand. 23:46:45 jjmcd: Wasn't that our discussion? 23:46:54 from previous discussion i think we worked out it doesnt, could be wrong 23:47:09 sgordon: I think it says "Red Hat Inc and others" in the brand because I wouldn't have come up with that by default 23:47:11 easy way to check, hang on i have the brand source checked out 23:47:16 I don't recall the details, but the ent gets heavily edited 23:47:29 I thought it was in the boilerplate that is part of the brand 23:47:44 It comes from somewhere by default. I wouldn't have come up with it by myself. 23:47:57 sgordon is right, I don't think this depends on a brand at all. Just created a new book to verify that. 23:48:02 there is no ent file in the brand source 23:48:11 i think people just copy paste it from a previous book 23:48:16 Maybe 23:48:18 which is why you see some guides with variations 23:48:27 Yeah, a new doc gets a sample ent that's pretty lame 23:48:32 Also, the common brand is used by default, you have to switch to "fedora" manually. 23:48:40 sgordon: It would be nice if it was in the brand... 23:48:51 hmmm 23:49:13 jhradilek: You can make a book with Publican and specify the brand then, correct? 23:49:21 yes 23:49:31 but you still get the default ent file 23:49:50 sgordon: Okay... perhaps I can open a bug for further discussion 23:50:14 23:50:19 True. 23:50:34 and it sets the YEAR entity based on when you did the publican create 23:50:57 so yeah, probably file a bug and ask rudi to follow it up 23:51:05 Okay, I'll do that. 23:51:08 just wondering, does the "Fedora Project Contributors" line make sense in cases where the former contributors were seemingly not connected to fedora project ? 23:51:11 #undo 23:51:11 Removing item from minutes: 23:51:29 pkovar, either way they still contributed to the project 23:51:32 directly or indirectly 23:51:44 ok, i see 23:51:47 imo, i am of course not a lawyer 23:51:54 #action Sparks to file a bug to continue the discussion on whether or not the copyright holder can come from a Publican brand 23:52:04 me neither :-) 23:52:10 :) 23:52:27 pvWhat former contributors weren't Fedora? 23:52:40 pkovar: What former contributors weren't Fedora? 23:52:56 well, look at rpm guide for example 23:53:27 it's derived from a book originally, afaik 23:53:44 Okay. Are we licensed to use that work? 23:53:45 the author was not a fedora contributor 23:54:29 the license seems to be "CC-BY-SA 23:54:41 *IF* we are licensed to use that work in our work then we should give attribution. The person who does the derivative work owns the copyright on the derivative. 23:54:53 spot: You around? 23:55:16 pkovar, original license wasn't, but we got author permission to change it 23:55:27 great 23:55:52 But we should include attribution 23:56:08 So, Sparks, perhaps we don't want it in the brand and hard to change 23:56:17 Since sometimes there are variants 23:56:26 that's what i was thinking, yes 23:57:07 Well... 23:57:12 when you look eg at upstream gnome docs, they do the attribution 23:57:29 Attribution and the copyright holder are two different things 23:57:40 * Sparks is consulting with his lawyer on the couch 23:58:02 noted 23:58:29 pkovar: Because we are short on time, could you post this to the Docs list so I can get spot and/or other RH Lawyer to weigh in? 23:58:49 sure thing! 23:58:51 * Sparks notes we still haven't properly addressed attribution in our docs 23:58:56 pkovar: Thanks! 23:59:02 np 23:59:07 #topic Open Discussion 23:59:15 60 seconds... anyone have anything else? 00:00:30 Well, time is up! Thanks, everyone, for joining us tonight. Sorry it was so... off the cuff. 00:00:35 #endmeeting