15:06:41 #startmeeting Laura's office hours 15:06:41 Meeting started Wed Jul 22 15:06:41 2015 UTC. The chair is lnovich. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:06:52 #rollcall 15:07:04 anyone here today? 15:07:09 * grundblom here 15:07:24 hi there grundblom! 15:07:51 * smccann is here 15:07:53 kirsti: smccann are you joining today? 15:07:56 time appropriate greetings! 15:08:00 hi smccann! 15:08:26 *waves to one and all* 15:08:41 yes I am in 15:08:49 ok so grundblom what happened? 15:08:56 * kirsti joins 15:09:24 let's get the branching issue solved so we can all go on happy and merry 15:11:02 yay happy 15:11:20 So, I merged the changes in master to branch f22 15:11:30 grundblom: which guide? 15:11:43 virt-getting-started 15:11:55 and the changes are not reflected in the docs.fedoraproject.org page 15:12:06 ok when did you make the change? 15:12:07 so I think I missed a step 15:12:17 Monday evening 15:12:21 ok 15:12:36 I have not published in a VERY long time 15:13:04 maybe I am impatient? 15:13:07 it used to be that in order to see the changes on the website you had to put the guide into the folder for the webserver on the repo 15:13:17 i am not sure that is true today 15:13:19 grundblom - I don't think you and I have full publish rights. I think we can change master but have to ask someone else to do the publishing 15:13:40 smccann, Ah! that would make sense 15:13:58 maybe I did not mess it up after all 15:14:12 :-) 15:14:14 probably not 15:14:23 sounds like you did all the steps you can do 15:14:35 randomuser: are you here 15:15:08 there's a batch of problems in the virt-manager chapter that I'm hoping kirsti can help with. Then maybe we can ask TPTB to republish? 15:15:15 grundblom I started going over the guide this week and added some suggestions on https://fedoraproject.org/wiki/Virt_Getting_Started_Planning 15:15:37 hi Kristi! 15:15:42 hoping not to cross your work ;) 15:16:10 first and foremost we need to change the titles so that they match the style in Boxes 15:16:33 -having the how to in the title yields for a more productive google search - so I hear 15:17:25 then we need to make sure that the information and instructions are simple enough for the scope and audience of getting started 15:17:49 smccann you might have to send me a link 15:18:02 if not it needs to go into the bigger deployment and admin guide 15:18:10 my nickel - keep it virt-manager and boxes only. The rest (libvirt raw commands etc) are out of scope imo 15:18:18 does that make sense? 15:18:41 so why cannot we make that part of ch 4? 15:18:48 agreed - move virsh command line out to the VDAG 15:19:20 Also we need to tackle the storage issue in chapter 4 15:19:24 Well, moving machines requires some command line work for boxes... 15:19:55 thats a question my users ask as soon as I introduce any desktop virt tool 15:19:55 and chapter 4 is misleading 15:20:01 #info 6.4. Creating guests with virt-manager - needs cleanup - updated screen caps but did not update text to match in the procedure. 15:20:29 moving machines is more complex and not part of getting started grundblom 15:20:38 kirsti - that is the change I'm talking about. Fairly straightforward - if you look at the screencaps, you'll see they moved naming the VM to the last step 15:20:54 but the text in the procedure still mentions it in the first step. 15:21:12 the getting started should be only about setting up a VM from start to finish 15:21:44 smccann ok, ping me tomorrow, see what I can do then 15:22:17 lnovich, I see your point. That content took some time to create, should I park it on a wiki page so it is not lost? 15:22:18 I focused on chapter 3, where advantages are mentioned. 15:22:31 sure 15:22:36 It seems a bit limited in information to me. 15:22:50 grundblom: wherever you want to put it so it doesn't get lost is fine 15:23:46 we may just want to comment it out of the chapter for now and keep it there -just as an option 15:24:19 and indicate as such in the wiki that the content is in something.xml 15:24:56 so when we're ready to incorporate that into the VDAG - it is a copy paste and update 15:25:07 So, if I am understanding this correctly, we really need to simplify the doc 15:25:21 getting started needs to be simple 15:25:33 just get the person started 15:25:35 The idea: Help a new user build and keep a VM in two graphical VM software products 15:25:46 yup 15:26:08 those who are more advanced, may skip the getting started guide and go straight to the VDAG 15:26:31 i would like to keep the getting started to the complete novice 15:26:40 or to the person who is new to Linux 15:26:48 grundblom - where do your users fall in the spectrum? Why do they need to migrate their VMs etc? 15:27:16 Do we need to bother with education of Why people should use virtualization? 15:27:44 not in great depth 15:27:50 In that light ch 3 should read as a sort of business case to sell it to managers right? And to convince beginners that it is not too difficult? 15:28:24 smcann, they usually build VM's on their desktops and laptops, and then want to clone it to other people so they can experiment in the exact same enviorment with different data sets 15:28:31 grundblom I think so, we could add a few examples of how to use it perhaps 15:29:43 my thought is to put the migration cloning and snapshot creation out of the getting started, but we can mention it is possible to do so and point to the VDAG for more info 15:29:56 k 15:30:08 lnovich, sounds good to me 15:30:20 i like telling users what else they can do once they have installed and configured a VM 15:30:28 lnovich I come from a back ground of project manager and adviser to management, I would want to be sold by the beginners guide, would look for the why 15:30:41 I agree 15:30:57 we need to have a place for decision makers to read 15:31:08 getting started is a good a place as any 15:31:18 kirsti, ah, that was an angle I wasnt thinking about, a non technical person reading it 15:31:23 can I make a new proposal for Ch3, elaborate a bit 15:31:44 sure what's on your mind 15:31:46 maybe we need to make the selling points Chapter 1 for the pointy hairs to read first 15:32:11 we need a proper introduction 15:32:20 with a high level overview 15:32:25 or at least close to the beginning 15:32:39 lnovich, right! 15:32:45 on what the solution looks feels and acts like 15:32:52 Using the set up for ch 3 as a baseline, but adding a more elaborate explanation, and perhaps a few tips or use cases 15:33:12 then explain the benefits and possibilities 15:33:21 as well as the vocabulary 15:34:02 that would be great, yes :) 15:34:07 tell people about what a host/guest/and hypervisor are 15:34:37 vs a client and server etc 15:34:48 Ok, so that makes Chapter 2 seem odd to me 15:35:21 2.2 needs to go 15:35:28 to another location 15:35:49 to the VDAG? 15:35:59 migration seems to be a more advanced topic 15:36:05 virtualization deployment and administration guide 15:36:12 ie the BIG Kahuna 15:36:17 have you ever worked with an appendix where terminology is explained? 15:36:30 as in a glossary? 15:36:35 yes 15:36:45 kirsti, read them, never made them 15:36:53 glossaries are problematic when it comes to translation 15:37:09 lnovich good point... 15:37:12 as we can't guarantee that the translated terms will be in alphabetical order 15:37:24 so we traditionally have not used them 15:37:28 which I don't agree with 15:37:54 well you can alphabetize per language as long as the refernces are made right 15:38:15 we can bring it up at the docs meeting if you want 15:38:27 also a lot of western European just use the English technical words 15:38:57 No use in translating those, when the product is English 15:40:41 yes they use them - maybe we can put it into a table and then tag the term as so it isn't translated? 15:40:55 good plan 15:40:56 and this way the term is not translated and the definition is? 15:41:03 yes 15:41:07 this will only work if the terms are not translated 15:41:21 example: migration is used when 15:41:44 we will need to ask the translation group 15:41:57 Migration wordt gebruikt als (Dutch) 15:43:43 I'll bring it up next week at the docs meeitng 15:43:46 meeting 15:47:10 for my understanding, does the product fedora come in multiple languages or only the documentation? 15:47:21 both 15:47:30 but they may not be matched 15:47:43 complicated... 15:47:53 as I am not completely multi-lingual I can't check 15:48:28 it is complicated 15:48:54 and frustrating if you are dependent on the translations being correct 15:49:43 ok so 10 minutes to the end of the hour 15:50:14 Shall I open a Wiki with a re-write for Chapter 3? 15:50:36 just add it to the current wiki - let's keep it together 15:51:22 will do 15:53:53 I would be happy to create content for making a vm with Virt-manager with screen shots, 15:54:44 I think that would be an update to chapter 6, 15:55:14 smccann, oh I see your working on that chapter, oops! 15:55:58 the chapter is there already grundblom yeah 15:56:20 was thinking a good easy starter task for kirsti would be fixing my fubars tho :-) 15:56:40 i changed the images but not the text 15:56:57 smccann, I will look at it :) 15:58:41 smccann: what are you currently working on? 15:59:20 I appreciate the time everyone, I wont be able to make it tomorrow 15:59:30 removing RHEL etc from VDAG 15:59:36 that's fine grundblom - 15:59:49 ok that is enough to keep you busy 15:59:56 grundblom: what will you do? 16:00:05 i can go back and clean my own cruft if you'd prefer :-) 16:00:21 from the getting started? 16:01:00 lnovich, for the virt getting started guide, I was thinking I would remove 2.2, 2.2.1, and the boxes moving machines chapter 16:01:36 ok - comment those sections out and update the wiki that it was done 16:01:37 at least park the moving boxes VMs in a wiki page or something, and commenting it out for now 16:01:50 lnovich, right on! 16:03:47 ok so #action grundblom - remove the 2.2 and 2.2.1 by commenting out the XML 16:05:12 and grundblom will also update the wiki 16:09:54 * kirsti is leaving, see you tomorrow 16:10:10 #ACTION kirsti - will revise the getting started parts smccann menttioned 16:10:57 #ACTION laura - will go though the minutes and put together questions for the DOCs meeting and will finalize the outline for the getting started 16:11:28 ok folks - I think we're done! 16:11:45 thanks again lnovich! I appreciate it 16:11:45 thanks everyone 16:11:51 pleasure 16:11:57 thanks ! 16:12:04 ok ending meeting 16:12:23 #endmeeting