cyberorg: meeting The_Code, hi * lejo (i=leo@193.202.14.1) has joined #opensuse-soc lars is again very busy, he is at LinuxTag so we will continue without him thought so * The_Code also wants to go to LinuxTag today's agenda 1. Report from you 2. discuss your initial code dump 3. testing pointers good then i will start with 1 did the first module, emulating a terminal using vte-sharp to show the output of the build scripts started with the configuration module i wrote a python script to get the interfaces and their ip (if any) and am currently working on the configuration dialog the first part to make it easy i want to show a dialog with the settings for ip and iface that i found out if no ip present the user can enter one he can then choose to use prebuild images, build his own, or make advanced changes to kiwi-ltsp config file also inform user to set up network interface from yast2 lan module if it is not set up if no ip is present yes or we do it using ifconfig that doesnt stick on reboot will tell to set it up in yast ok, those are little details we can take care when doing testing right, i hope to have the configuration finished end of the week but this time it's not a promise, quite busy at the moment searching a flat and doing stuff for the U ah, you'd have to burn midnight oil, we own you for next few months :) the sooner we can test and provide feedback ;) i know you own me :) plan your time to give just about 10% - 15% for ltsp-build-client and ltsp-server-initialize part, most of your time would go in lts.conf management with client-server model it looks like it would take more effort than doing a stand alone app we said we are setting up a stand alone app at first, but design for client-server client-server is on my schedule in september ok, about the code, can you tell us what is in the repo now? in the repo there is just the terminal emulation window and the structure for the next modules are you commenting all the code? i want to it would be great if you can put a README file in there explaining what the module does, and links to various places where anyone interested may find info about the project okay will do anything else about the svn repo? lejo, this is the soc code repo ok, i'll have a look (should it build already?) not from my side, i will make a commit later today with the current standing The_Code, there isn't any activity since your first commit lejo: no ok, cool officially coding started a couple of days back :) monday cyberorg: it was my third commit :) btw, wish you all the luck for the happy coding and successful completion of the project :) The_Code, yup, third one actually now on the last point of today's agenda, what would you want us to test, what are the areas you need help? just made a commit with the python script and a first draft of the easy-ltsp.conf file so the python script can be tested for now just run the script? yes it should output something like eth1 10.0.0.254 i let the script handle everything concerning the ip stuff ok, would you post on ltsp-developers list about the tests you want other distros to run too? results should be consistent for everyone using ltsp gui for server configuration ubuntu is not using this module, so probably fedora and us for now the server configuration module is for kiwi-ltsp at least the one i am building right now ok, good starting place :) and as far as i understand https://fedorahosted.org/k12linux/wiki/InstallGuide no need to setup ip and iface does the script only test for eth0 ? right, so only we would be using this information lejo: no it tests for all interfaces and picks the first one that has no default route if there is more than one but it only tests for eth ifaces cyberorg: all other distros and the client-server part are on my schedule for the time after soc of course only if you want The_Code, ok, cool, what part you need help? we can request some experts to be here if required :) a gtk# expert would be great from time to time, saves time in reading the doc but i am quite fine right now but one thing am i allowed to write the kiwi-ltsp conf file without all the comments? ok, snorp in #kiwi has some experience with mono he is usually around during US day time cool The_Code, easy-ltsp.conf or /etc/sysconfig/kiwi-ltsp ? the /etc/sysconfig/kiwi-ltsp file Yast uses those comments the structure of /etc/sysconfig/kiwi-ltsp has to be exactly like it is now, open it in yast sysconfig editor, you'll know why fine including comment part will keep it this way you can sed just the values if all bases are covered we end today's meeting here good idea i am quite happy with the start and everything you've done so far