[00:24] <bernie> dfarning: go to a classroom and you will cry twice
[00:24] <bernie> dfarning: before you try to fix _any_ sugar-specific bug, make sure you apply all our patches
[01:18] <lfaraone> dfarning: i'll be online for a few more minutes, I think I'll tackle https://bugs.launchpad.net/ubuntu/+bug/601219 , it seems to be a trivial fix.
[01:59] <lfaraone>  /j #sugar
[02:52] <dipankar> dfarning, Hello.
[02:53] <dfarning> dipankar, good morning?
[02:53] <dipankar> dfarning, yeah! How was your day?
[02:54] <dfarning> dipankar, It was very good.  we had several valuable discussion after you went to sleep.
[02:54] <dfarning> are you felling better today?
[02:54] <dipankar> dfarning, yeah. I am fresh now.
[02:55] <dfarning> dipankar, nice.
[02:55] <dipankar> dfarning, did you get a chance to go through Luke's email (via mailing list)
[02:57] <dfarning> dipankar, the one about testing sugar on ubuntu?
[02:57] <dipankar> dfarning, no. The one about 'the activities getting installed in wrong directory'
[02:58] <dipankar> brb in 10
[02:59] <dfarning> dipankar, yes, found it.
[03:09] <dipankar> dfarning, where is the source of log-viewer-activity? I am unable to find it.
[03:12] <dfarning> dipankar, just the tarball alone? or packaged for debian or ubutu?
[03:12] <dipankar> dfarning, like the other packages have a src folder. I don't seem to find it anywhere.
[03:14] <dfarning> dipankar, are you looking in the source package we were looking at yesterday
[03:15] <dfarning> if so, it is in the Log.activity dir.  there are only 3 .py file in the whole activity
[03:17] <dipankar> dfarning, ok. where is the script file that copies the activity into the destinate folder
[03:17] <dipankar> ?
[03:19] <dfarning> dipankar, this package which we grabbed from ubuntu is using a slightly differenet packaging method
[03:20] <dfarning> it is using debhelper.  you can see that in the control file as:
[03:20] <dfarning> #!/usr/bin/make -f
[03:20] <dfarning>   
[03:20] <dfarning> include /usr/share/cdbs/1/rules/debhelper.mk
[03:20] <dfarning> include /usr/share/cdbs/1/rules/simple-patchsys.mk
[03:21] <dfarning> dipankar, it stick everything in the package into the destination in the debian install file.
[03:21] <dipankar> dfarning, Actually I somehow deleted the control file. :( I guess I will try regenerating it.
[03:22] <dipankar> dfarning, ok.
[03:23] <dfarning> part of packaging this activity will be adapting it to meet the style used for the rest of the sugar on ubuntu activities
[03:24] <dfarning> dipankar, this was last touched in 2007:)
[03:24] <dipankar> dfarning, wow! Such long time back.
[03:26] <dfarning> dipankar, so to package this activity i would start by using another simple debain activity that you know is done correctly and modify it as needed.
[03:27] <dipankar> dfarning, ok.
[03:28] <dfarning> dipankar, or have you looked at the contributing a new package on the page http://wiki.debian.org/Sugar/GettingStartedGuide
[03:31] <dfarning> dipankar, ahh very cool lfaraone has set up a very nice skeleton as he refers to in the getting started guide.
[03:33] <dipankar> dfarning, I agree with you lfaraone _has_ mentioned things clearly there.
[03:34] <dfarning> dipankar, the reason I suggested looking for a package we know works was to a the 'skeleton.'  but lfaraone did that for us all ready.
[03:39] <dfarning> dipankar, one thing I am unclear about is how to push a package to aloith.  Normally you have to define the url of the remote dir.
[03:39] <dfarning> is that done for us in this case?
[03:39] <dipankar> dfarning, was going through logs, So I guess we can work on sugar-logviewer-activity with Luke's 'skeleton'
[03:40] <dfarning> dipankar, +1
[03:41] <dipankar> dfarning, yes the push should be to the ailoth ssh, in other words the git repo that you created at alioth.
[03:42] <dfarning> dipankar, ok I got it -- http://git.debian.org/git/collab-maint/
[03:43] <dipankar> dfarning, + the git repo directory. like 'sugar-logviewer-activity/' after that
[03:44] <dfarning> dipankar, do you have authority to push to collab-maint on aloith?
[03:45] <dipankar> dfarning, yeah, you just need to add your ssh key in your alioth account.
[03:45] <dipankar> after that you can push the changes.
[03:48] <dfarning> dipankar, ok got it, then after you have completed your final push, you send an email to the list asking for someone to review and sponsor the package?
[03:49] <dipankar> dfarning, yes. If they like it they will accept the packages. :)
[03:50] <dfarning> dipankar, lets go for it:)  we can package it together. i'll do every thing accept the push and file the ITP bug:)
[03:50] <dipankar> dfarning, there is a doubt though. Will the git repository that I have created in alioth will be used by Ubuntu?
[03:51] <dfarning> dipankar, we will worry about that later:)
[03:52] <dipankar> dfarning, nice...
[03:53] <dipankar> dfarning, okay now that we have got a fine idea of git working, I guess we have to wait for Luke to tell more details
[03:54] <dfarning> dipankar, first step looks like filing a ITP.  Yep.... lets stumble through and have some question ready when he is available:)
[03:55] <dipankar> dfarning, ITP? :(
[03:56] <dfarning> dipankar, an ITP is an Intent To Package.  we want to let everyone know that we are working on this package.
[03:57] <dfarning> near the bottom of the getting started page is a link how to file a ITP.\
[03:58] <dipankar> dfarning, But I guess thats after uploading the packages.
[03:59] <ankur> dfarning,  good morning
[03:59] <dfarning> dipankar, actually you want to get in the habit of doing that first so others know what you are working on and don't start working on the same package.
[04:00] <dfarning> ankur, good morning:) did you switch computers?  You nickname is much shorter:)
[04:01] <ankur> no, i just chose a different nick name. :)
[04:01] <dfarning> dipankar, I just checked and version 23 at http://download.sugarlabs.org/sources/sucrose/fructose/Log/Log-23.tar.bz2 is the most recent tarball.
[04:02] <dfarning> ankur, what do you have scheuled for this morning?
[04:04] <dfarning> ankur, if you have some debugging to do alsroot is in #sugar and might be able to get you started.  he is in europe so he is either up really early or really late:)
[04:04] <dipankar> dfarning, I think ankur and me have to work on the bugs that you found out
[04:04] <dipankar> dfarning, manu Sir sent and e-mail regarding that
[04:05] <dfarning> dipankar, cool go for it. we can package later.  I actually just packaged the log-viewer according to the instructions and it worked:)
[04:07] <dipankar> dfarning, right on! that quick?
[04:08] <dfarning> between our discusion and luke's instructions it is pretty easy:)
[04:08] <dfarning> dipankar, which surprised me:)
[04:08] <dipankar> dfarning, what all changes did you make?
[04:09] <ankur> dfarning,  my net connections is giving me jitters .
[04:09] <ankur> manu sir sent a email last night regarding regarding some bugs, i guess i should start working on it .
[04:10] <dfarning> dipankar, just the stuff luke listed. the dependencey were all the same as in the skeleton.
[04:11] <dfarning> ankur, I see you are fading in and out.  do you want to start with the network bug with dipankar?
[04:12] <ankur> dfarning,  i would be glad to do so
[04:12] <dipankar> dfarning, ankur is having trouble with internet.
[04:13] <dipankar> lemme check when alsroot will be free..
[04:14]  * alsroot is all time open for questions
[04:14] <dfarning> dipankar, ankur -- great. I am going to write an QA plan while you get the process started.  I'll be back in about 30 minutes.
[04:15] <dipankar> alsroot, I got it :)
[04:15] <dfarning> alsroot, :)
[04:15] <dipankar> dfarning, ok.
[04:16] <dipankar> alsroot, I have to run the checks on system for the bug. How about I contact you in 15 minutes?
[04:16] <alsroot> dipankar: ok
[04:29] <dipankar> alsroot, my first problem is I am unable to see anybody on neighbourhodd
[04:29] <dipankar> *neighbourhood
[04:29] <alsroot> dipankar: can you make Chat shared or it fails to share?
[04:31] <dipankar> alsroot, I am unable to find the chat-activity
[04:31] <alsroot> dipankar: ok, what you have for `ps aux | grep telepa`?
[04:35] <dipankard> alsroot, dipankar@dipankar-desktop:/usr/bin$ ps aux | grep telpa
[04:35] <dipankard> dipankar  1660  0.0  0.0   3320   792 pts/0    S+   09:03   0:00 grep --color=auto telpa
[04:37] <alsroot> dipankard: could you enable all debug output http://wiki.sugarlabs.org/go/BugSquad/Get_Logs#Enabling_Sugar_debug_logging and pastebin presenceservice.log and shell.log
[04:37] <alsroot> and also telepathy*.log
[04:38] <alsroot> dipankard: and you need to restart sugar after setting up debug
[04:38] <dipankard> alsroot, I am running an emulator on Ubuntu
[04:39] <alsroot> dipankard: then, just restart it
[04:39] <dipankard> alsroot, also I guess I have all debug files generated
[04:41] <dipankard> shell.log : http://paste.ubuntu.com/458974/
[04:43] <dipankard> alsroot, presenceservice.log is empty
[04:44] <alsroot> dipankard: that means you didn't uncommented all lines in debug file http://wiki.sugarlabs.org/go/BugSquad/Get_Logs#Enabling_Sugar_debug_logging
[04:44] <dipankard> alsroot, ohk. then I will do that and join in a couple of minutes
[04:55] <dipankard> alsroot, ok done
[04:56] <dipankard> alsroot, the presenceservice.log : http://paste.ubuntu.com/458980/
[04:57] <dipankard> alsroot, the telepathy-gabble.log: http://paste.ubuntu.com/458981/
[04:58] <dipankard> alsroot, the telepathy-salut.log :
[04:58] <dipankard> http://paste.ubuntu.com/458983/
[05:00] <alsroot> dipankard: was sugar-emulator stopped before you got logs?
[05:00] <dipankard> alsroot, yes. I closed and then took the logs out
[05:01] <alsroot> dipankard: you need to take logs when sugar-emulator is running, otherwise logs contain bunch of exit related stuff
[05:01] <dipankard> ohk..
[05:04] <dipankard> alsroot, what can be the possible error?
[05:05] <alsroot> dipankard: dunno, at least if there is no either telepathy-gabble nor telepathy-salut in `ps` it should be something network related
[05:06] <dipankard> alsroot, This is strange. Before I registered I used to see a lot of sugar users
[05:07] <dipankard> alsroot, now not a single user. This is not possible that each time I enter neighbourhood view no user is online
[05:07]  * alsroot didn't touch registering related code and dunno how it works
[05:08] <dipankard> ok.
[05:09] <dipankard> alsroot, can you see other sugar users in 'nieghbourhood view'
[05:12] <alsroot> dipankard: nope, /me tries to investigate, it could be that jabber server is offline
[05:14] <alsroot> dipankard: looks like I also can't connect to jabber.sugarlabs.org
[05:14] <dipankard> ohhk.
[05:14] <dfarning> dipankar did we lose ankur due to network issues?
[05:15] <dipankard> dfarning, ankur is off for breakfast
[05:16] <alsroot> dfarning: anyway, sugar should fallback to salut backend (like it does in my case), and e.g. sharing should work in activities -- could you check if any activity can start sharing
[05:16] <alsroot> dfarning: sorry, dipankard
[05:16] <dfarning> dipankard, thanks
[05:17] <dipankard> alsroot, ok let me check
[05:19] <dipankard> alsroot, strange no activity is coming on neighbourhood. they earlier used to
[05:19] <alsroot> dipankard: do you have telepathy-salut in `ps`?
[05:20] <alsroot> in `ps aux`
[05:20] <dipankard> alsroot, how do I check ? :P
[05:20] <alsroot> dipankard: in Terminal, type "ps aux | grep telepathy-salut"
[05:21] <dipankard> dipankar  1816  0.0  0.0   3320   792 pts/0    S+   09:51   0:00 grep --color=auto telepathy-slaut
[05:21] <dipankard> alsroot, ^^
[05:21] <alsroot> dipankard: hmm, it's already not only jabber server issue..
[05:22] <alsroot> dipankard: could you: restart sugar, not closing sugar-emulator, pastebin logs once more
[05:24] <dipankard> http://paste.ubuntu.com/458988/
[05:25] <dipankard> http://paste.ubuntu.com/458989/
[05:26] <dipankard> http://paste.ubuntu.com/458990/
[05:27] <dipankard> http://paste.ubuntu.com/458991/
[05:27] <kandarpk> dipankard: Hi
[05:27] <dipankard> kandarpk, hi sir goodmorning
[05:27] <kandarpk> good morning
[05:28] <kandarpk> dipankard: do you know how to access control panel as mentioned by manu sir in the mail ?
[05:29] <dipankard> kandarpk, its just the settings option , when you right click on the XO guy
[05:29] <alsroot> dipankard: and there is no telepathy-salut in "ps aux | grep telepathy-salut"?
[05:29] <dipankard> i found on alsroot
[05:29] <dipankard> dipankar  1816  0.0  0.0   3320   792 pts/0    S+   09:51   0:00 grep --color=auto telepathy-slaut
[05:30] <alsroot> dipankard: it's just an echo of your `ps` command, not telepathy-slaut itself
[05:31] <dipankard> alsroot, ok.
[05:31] <alsroot> dipankard: looks like telepathy-slaut died, could you pastbin telepathy-salut.log once more
[05:31] <kandarpk> dfarning: around ?
[05:31] <dfarning> kandarpk, good morning.
[05:31] <kandarpk> good morning
[05:32] <dipankard> alsroot, http://paste.ubuntu.com/458994/
[05:32] <dfarning> kandarpk, what to you have scheldaled for this morning?
[05:32] <kandarpk> dfarning: there's a bug in sugar
[05:32] <kandarpk> even though I do not have a 3g modem, there is an icon to set up a 3g modem
[05:33] <kandarpk> dfarning: any pointers ?
[05:34] <dipankard> everyone: there is an important bug to be fixed in neighbourhood view
[05:34] <dipankard> bug: Can't find other Sugar Users in 'Neighbourhood View'
[05:34] <dfarning> kandarpk, I have no idea on this one.  It would seem to me that sugar should do some sort of hardware detection before showing the incon in the control panel.
[05:35] <kandarpk> dfarning: exactly
[05:35] <dipankard> situation: We cannot find anybody. If running on laptop we can only see the wifi access points
[05:36] <alsroot> dipankard: maybe tp-salut exits unexpectedly, could you add "export PRESENCE_SERVICE_DEBUG=disable-gabble" to ~/.sugar/debug, just in case call "killall python2.6", start sugar, you should see "telepathy-salut" in "ps aux | grep telepathy-salut"
[05:36] <kandarpk> dfarning: will try to resolve this issue later
[05:37] <dfarning> kandarpk, but since sugar was originally written for a specific piece of hardward  (the XO) I don't know what sort of detection mecainism is in place.
[05:37] <kandarpk> dfarning: Ok, now I now some reason for this issue
[05:37] <dfarning> kandarpk, when you are ready to work on it I would suggest pinging bernie, tomeu, alsroot, or sible upstream
[05:39] <dipankard> alsroot, I have to reboot I guess
[05:39] <kandarpk> dfarning: dipankard and alsroot are working on neighbourhood issue, joining them, will ping them when it gets resolved
[05:39] <kandarpk> *them=bernie, tomeu, alsroot, sible
[05:40] <kandarpk> dfarning: what should happen on starting neighbourhood ?
[05:41] <dfarning> kandarpk, sounds good.  alsroot is very good:)
[05:41] <dfarning> kandarpk, Are you asking about the issues alsroot and dipankar are working on?
[05:41] <kandarpk> dfarning: yes
[05:42] <kandarpk> dfarning: do not know what is the expected behaviour
[05:42] <kandarpk> dfarning: will be back in 2 min.
[05:44] <dfarning> kandarpk, I think the one they are working on is that the system sugar uses for sugar desktops to comunicate is not running/starting correctly.
[05:44] <dipankard> alsroot, bingo! dipankar  1416  0.0  0.3   9208  3492 ?        S    10:13   0:00 /usr/lib/telepathy/telepathy-salut
[05:44] <dipankard> dipankar  1498  0.0  0.0   3324   876 pts/0    S+   10:14   0:00 grep --color=auto telepathy-salut
[05:45] <alsroot> dipankard: is sharing working in activities ?
[05:46] <dfarning> kandarpk, the expected behavior is that when a network is available to sugar there will be several other users visiable on the 'group' view.
[05:47] <dipankard> alsroot, nope
[05:47] <alsroot> dipankard: you mean you don't see shared icons in F1 view?
[05:48] <dipankard> alsroot, yes thats what's happening : I only see myself in neighbourhood view
[05:48] <dipankard> alsroot, I ran the 'maze-activity'
[05:48] <dfarning> kandarpk, --  dipankard and alsroot are exploring why no one else is visable.  this system is part of the 'presence-service' stack.
[05:49] <alsroot> dipankard: but afaik maze doesn't support sharing, could you try to share other activities e.g. TA, Browse, Chat
[05:50] <dipankard> alsroot, now the function keys are not working!
[05:51] <dfarning> kandarpk, in this case it appears that something is wrong with telepathy-salut -- see http://linux.die.net/man/8/telepathy-salut
[05:53] <dipankard> alsroot, now this is really weird : I don't find browse, chat eactivities
[05:54] <alsroot> dipankard: what about Calculate?
[05:55] <dipankard> alsroot, nope! What is wrong!
[05:57] <alsroot> dipankard: do you still have salut in `ps`? it could die
[05:58] <dipankard> alsroot, it is still there
[05:58] <alsroot> dipankard: what about "avahi" in `ps`?
[05:59] <dipankard> avahi      547  0.0  0.1   2924  1596 ?        S    10:10   0:00 avahi-daemon: running [dipankar-desktop.local]
[05:59] <dipankard> avahi      552  0.0  0.0   2924   544 ?        Ss   10:10   0:00 avahi-daemon: chroot helper
[05:59] <dipankard> dipankar  1825  0.0  0.0   3324   860 pts/0    S+   10:29   0:00 grep --color=auto avahi
[05:59] <alsroot> dipankard: what `route -n` says?
[06:01] <dipankard> Kernel IP routing table
[06:01] <dipankard> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
[06:01] <dipankard> 10.0.2.0        0.0.0.0         255.255.255.0   U     1      0        0 eth0
[06:01] <dipankard> 169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
[06:01] <dipankard> 0.0.0.0         10.0.2.2        0.0.0.0         UG    0      0        0 eth0
[06:01] <alsroot> so, default route is set..
[06:02] <dipankard> yup. I have DHCP
[06:02] <dipankard> oops wrong statement I guess
[06:03] <kandarpk> dfarning: *going through the link provided
[06:07] <alsroot> dipankard: could you install Chat http://activities.sugarlabs.org/en-US/sugar/downloads/file/26269/chat-66.xo it will be easier to investigate problem -- and try to share it and pastebin telepathy-salut.log
[06:10] <dfarning> kandarpk, the upstream to sugar ( and gnome ) for the telepathy stack is a company called collabora which tomeu works for -- http://www.collabora.co.uk/projects/telepathy/
[06:10] <dipankard> alsroot, It is not installing only :(
[06:11] <alsroot> dipankard: you mean after uploading chat-66.xo to the journal, you can't launch Chat?
[06:12] <dfarning> I need to get to bed so I can be productive in the morning.  good night.
[06:12] <alsroot> ..by clicking on journal entry with chat-66.xo
[06:12] <dipankard> I used 'sugar install-activity chat-66.xo' from terminal in sugar
[06:12] <dipankard> dfarning, good night :) See in 8 hours
[06:12] <dipankard> dfarning, *see you in 8 hours
[06:13] <kandarpk> dfarning: telepathy provides libraries to provide a layer of abstraction for communication based applications ?
[06:13] <alsroot> dipankard: try this "copy-to-journal -m application/vnd.olpc-sugar <fs-patht-to-xo>"
[06:14] <alsroot> ..from Terminal
[06:17] <dipankard> alsroot, o/p : created as <some key-kind of number>
[06:18] <dipankard> alsroot, shared it.
[06:20] <alsroot> dipankard: you see Chat icon in F1 view?
[06:20] <dipankard> alsroot, no :(
[06:21] <alsroot> dipankard: did you ge "Onnline..." alert in Chat after changing sharing scope?
[06:21] <dipankard> alsroot, nope.
[06:22] <alsroot> dipankard: could you pastebin telepathy-salut.log and presenceservice.log once more
[06:24] <dipankard> http://paste.ubuntu.com/459004/
[06:24] <dipankard> http://paste.ubuntu.com/459006/
[06:24] <dipankard> alsroot, ^^
[06:25] <alsroot> oops, first one says that salut has stopped, do you have it in `ps`?
[06:25] <alsroot> dipankard: ^
[06:26] <ankurkhurana_> dfarning, my power is off, so currently i was working on my backup power. I will be working till it goes or my power comes back. hello alsroot
[06:26] <alsroot> ankurkhurana_: hi
[06:27] <dipankard> alsroot, its still running
[06:28] <alsroot> dipankard: hmm, something weird
[06:28] <alsroot> dipankard: could you reproduce this issue in the same network but from different env?
[06:28] <dipankard> ankurkhurana_, Don't use computer on inverter. Its not good.
[06:28] <dipankard> alsroot, like?
[06:29] <alsroot> dipankard: I mean from different box
[06:29] <dipankard> alsroot, different env?
[06:29] <dipankard> alsroot, how do i do that?
[06:29] <kandarpk> dipankard: you can let me know the steps
[06:29] <kandarpk> if not very involved
[06:30] <alsroot> dipankard: e.g. from VM..
[06:30] <dipankard> kandarpk, to reproduce the bug?
[06:30] <dipankard> alsroot, I am running on vm :)
[06:30] <dipankard> *  oracle virtual box
[06:31] <kandarpk> dipankard: that is what alsroot has asked you, I believe
[06:31] <kandarpk> *power cut
[06:31] <kandarpk> will be back soon
[06:32] <alsroot> dipankard: anyway, let me try to reproduce it in my env, what sugar you are using? is there dvd iso to check
[06:32] <alsroot> ..to install
[06:32] <dipankard> alsroot, I am using packages ' ubuntu-sugar-remix'
[06:33] <alsroot> dipankard: is there ubuntu-sugar-remix isos?
[06:33] <dipankard> yes, but i think they are not upto date. afaik
[06:36] <dipankard> alsroot, how about jhbuild?
[06:36] <alsroot> dipankard: I already have recent sugar, the problem is in not in sugar itself but in telepathy I guess
[06:37] <alsroot> and in ubuntu's telepathy
[06:38] <dipankard> ohk alsroot
[06:38] <alsroot> dipankard: btw can you check this issue in native env i.e. out of VM?
[06:39] <dipankard> alsroot, I have set this test machine on Desktop Virtual Box (inside windows)
[06:41] <dipankard> alsroot, I checked on sugar-jhbuild, there I can share activities but nobody is visible
[06:42] <alsroot> dipankard: better to download recent soas or ubuntu-sugar-remix images and boot from them
[06:43] <alsroot> dipankard: it could be even VirtualBox issue
[06:43] <alsroot> or issue that can be reproducible only in VirtualBox
[06:43] <dipankard> alsroot, I have a very slow internet connection (512 kbps)
[06:44] <dipankard> It will take sometime
[06:45] <alsroot> dipankard: if you will decide to download soas, I guess http://spins.fedoraproject.org/soas/#downloads contains links to recent images
[06:46] <alsroot> dipankard: btw maybe you have an XO?
[06:46] <alsroot> there are 0.88 based images
[06:47] <dipankard> alsroot, now XO right now :)
[06:47] <dipankard> *no XO
[06:48] <dipankard> alsroot, I am downloading the recent image from the test sever
[06:48] <dipankard> of USR
[06:49] <alsroot> dipankard: will, it will be useful to check if sugar (not)works fine out of VirtualBox before falling to not trivial TP investigation
[06:49] <alsroot> s/will/well/
[06:50] <dipankard> alsroot, let me ask ankur
[06:50] <dipankard> ankur
[06:50] <ankur> dipankard,  i was not able to install either calculate activity or chat .Can you suggest a way to install a activity that support sharing.Pardon me if somebody asked the question.I am having network prob and irc logs are not updated realtime. in synaptic package manager chat is for .86 , not available for .88.
[06:50] <ankur> yes dipankard
[06:51] <kandarpk> dipankard: anything conclusive yet ?
[06:51] <dipankard> copy-to-journal -m application/vnd.olpc-sugar <fs-patht-to-xo>
[06:53] <ankur> alsroot, i am working in dual boot system, and I am having same problem as dipankar.So i guess that is not due to virtual box
[06:53] <dipankard> kandarpk, sir, you are running USR on virtual box or direct installed?
[06:53] <kandarpk> dipankard: running Debian right now
[06:54] <kandarpk> but have USR as a dual boot
[06:55] <dipankard> kandarpk, can please you check out if in neighbourhood you are able to share any activity?
[06:55] <dipankard> ankur, we are unable to view other users
[06:55] <kandarpk> dipankard: how do I share an activity there ?
[06:55] <kandarpk> dipankard: same here
[06:56] <kandarpk> there are no users when I open neighbourhood
[06:56] <dipankard> kandarpk, first download the chat activity : http://www.collabora.co.uk/projects/telepathy/
[06:56] <alsroot> ankur: do you have neighbourhood issue in USR?
[06:56] <dipankard> copy-to-journal -m application/vnd.olpc-sugar <fs-patht-to-xo>
[06:57] <kandarpk> dipankard: I think it is already installed
[06:57] <kandarpk> let me check
[06:57] <dipankard> kandarpk, I didn't have it :P
[06:58] <ankur> alsroot, i have USR iso intalled in virtual box, so i guess i have to check that.Are you asking me to check in vm or my native ubuntu?
[06:58] <dipankard> alsroot, download is under process: As soon as it is done, I will boot from it.
[06:58] <alsroot> ankur: will be useful in both
[06:58] <kandarpk> dipankard: I do have it, but don't know how to use it
[06:59] <kandarpk> *the chat activity
[06:59] <kandarpk> dipankard: starting the activity does not show any options
[07:00] <kandarpk> except for a bar on the top
[07:00] <dipankard> kandarpk, in chat activity: when you run it , it will prompt a notification "Online/Offline"
[07:00] <kandarpk> dipankard: it did, and a count down of 3 sec
[07:00] <dipankard> kandarpk, then select the circle with a single dot "its in the centre f the bar"
[07:01] <dipankard> then you will get two options "a circle with a single dot/ a circle with many dots on periphery"
[07:01] <dipankard> single represents 'private mode'
[07:02] <dipankard> many dots represent 'shared mode'
[07:02] <kandarpk> dipankard: got it
[07:02] <kandarpk> dipankard: selecting circle with many dots do not show other users
[07:03] <alsroot> kandarpk: do you see Chat icon in F1 view?
[07:03] <dipankard> kandarpk, switch to neighbourhood mode first 'F1'
[07:03] <kandarpk> dipankard: yes, there is a chat icon
[07:04] <alsroot> kandarpk: are you on USR in VB?
[07:04] <kandarpk> alsroot: Using sugar-emulator on Debian
[07:04] <kandarpk> installed as a dual boot
[07:04] <dipankard> good we have a Debian env too :)
[07:05] <alsroot> dipankard: so, it is not USR issue, it could be either VB or your-network-env issue then
[07:05] <alsroot> oops, it was debian in kandarpk's env
[07:06] <alsroot> kandarpk: i said you have USR in dual boot, could you try the same in USR?
[07:06] <kandarpk> alsroot: sure
[07:06] <kandarpk> I'll reboot now
[07:06] <dipankard> guys I am off for 30 minutes :) Have some work.
[07:21] <kandarpk> alsroot: Sugar on USR isn't working as well as it did on Debian
[07:21] <kandarpk> terminal in Sugar isn't reading input
[07:25] <alsroot> kandarpk: you can try a workaround (since we are trying to check only sharing issue, not terminal:), stop sugar, call copy-to-journal command, later in sugar you should see .xo journal item, so you can click it to launch
[07:26] <kandarpk> alsroot: "copy-to-journal -m application/vnd.olpc-sugar <fs-patht-to-xo>"
[07:26] <kandarpk> what is "<fs-patht-to-xo>" ?
[07:27] <alsroot> kandarpk: it was path to downloaded chat.xo, but maybe you already have Chat
[07:27] <kandarpk> alsroot: chat isn't installed in USR
[07:27] <kandarpk> http://activities.sugarlabs.org/en-US/sugar/downloads/file/26269/chat-66.xo
[07:28] <alsroot> kandarpk: yup, it should work in USR
[07:28] <kandarpk> Ok
[07:32] <kandarpk> alsroot: same problem in USR
[07:32] <kandarpk> no user detected in neighbourhood
[07:32] <alsroot> kandarpk: but  can you see Chat icon?
[07:32] <kandarpk> alsroot: yes, its there
[07:34] <alsroot> kandarpk: you can't see users because it seems that jabber.sl.o is offline, dipankard has different issue, in his case even Chat didn't appear
[07:35] <kandarpk> alsroot: ok, so I am in a better position, if we can say that
[07:35] <alsroot> kandarpk: I also can see no one in F1 view, and errors in log while connecting to jabber.sl.o
[07:36] <kandarpk> Ok.
[07:36] <alsroot> kandarpk: so, look like dipankard's issue is specific to his environemnt, possible windoz-virtualbox-telepathy
[07:38] <kandarpk> alsroot: most probably
[07:39] <kandarpk> alsroot: should pressing F1 key take me to F1 view ?
[07:39] <kandarpk> because it is not doing so
[07:40] <alsroot> kandarpk: at least should, but if you are running sugar-emulator.. some people reported about keyboard issuse that are Xephyr related
[07:40] <kandarpk> Ok.
[07:41] <alsroot> silbe on #sugar did some work for switching to vnc, but dunno about status
[07:43] <kandarpk> I should try running sugar-session
[07:43] <kandarpk> *will be back
[07:46] <kandarpk> alsroot: you were right, Function keys worked in Sugar-session
[07:58] <kandarpk> bernie: around ?
[08:33] <dipankar> alsroot, checked the new usr iso
[08:33] <dipankar> alsroot, internet is not working on it
[08:34] <kandarpk> dipankar: can you let me know how to use git ?
[08:34] <dipankar> kandarpk, he he.. you are still after that!
[08:35] <kandarpk> dipankar: we need to learn it in a day or two.
[08:35] <dipankar> kandarpk, Ok I will definitely tell you, but what happened to the neighbour hood view bug?
[08:36] <alsroot> dipankar: kandarpk checked neighbourhood issue in his USR and works fine (except that sugar cannot connect to jabber.sl.o) i.e. Chat icon appear in F1 view, so looks like issue is specific to your case
[08:36] <kandarpk> dipankar: chat icon was being displayed
[08:38] <dipankar> alsroot, I also checked it on USR's new iso. Activities are displayed on the 'F1' view
[08:38] <alsroot> dipankar: so, it could be just "VirtualBox under Windows" issue
[08:39] <dipankar> alsroot, any idea why we are unable to connect to the server? Is it same for everyone then?
[08:39] <dipankar> ok
[08:39] <dipankar> kandarpk, You got the idea of using git I guess last night.
[08:40] <alsroot> dipankar: dunno, kevix on #sugar managed to connect, just still no lick in my case
[08:40] <alsroot> dipankar: anyway, looks like it is server side problem
[08:40] <dipankar> alsroot, ok. That clears some doubts.
[08:40] <kandarpk> dipankar: I can use clone, branch, add, commit, pull
[08:41] <dipankar> kandarpk, then you are ahead of me :P
[08:41] <dipankar> kandarpk, I only tried my hands on the logviewer activity.
[08:42] <dipankar> *also I am yet to do branch and merger
[08:42] <kandarpk> dipankar: Ok.
[08:42] <kandarpk> no worries
[08:42] <kandarpk> dipankar: but let me know the steps that Luke told you
[08:43] <dipankar> kandarpk, here is the detailed guide: http://wiki.debian.org/Sugar/GettingStartedGuide;
[08:43] <kandarpk> it involves ssh ?
[08:43] <kandarpk> was a bit confusing there
[08:43] <dipankar> kandarpk, Luke told me the section 'Contributing a new package'
[08:44] <dipankar> kandarpk, which part in ssh was confusing?
[08:44] <kandarpk> git push ssh+git://git.debian.org/git/collab-maint/sugar-memorize-activity.git master
[08:44] <kandarpk> do we need to set up our ssh keys with the repo ?
[08:46] <kandarpk> dipankar: I mean how do I submit changes ?
[08:46] <dipankar_> kandarpk, got disconnected.
[08:47] <dipankar_> kandarpk, can you please send the part again
[08:47] <kandarpk> yeah
[08:47] <kandarpk> git push ssh+git://git.debian.org/git/collab-maint/sugar-memorize-activity.git master
[08:48] <kandarpk> do we require to have our ssh keys synced with Debian repo ?
[08:48] <kandarpk> *not synced
[08:48] <kandarpk> but is there anything we need to do before pushing
[08:49] <dipankar_> by now you would have added the ssh key?
[08:49] <dipankar_> I guess
[08:49] <dipankar_>  to your alioth account
[08:49] <kandarpk> nope
[08:50] <dipankar> so you need to register your ssh key with alitoh account before pushing anything
[08:53] <kandarpk> dipankar: where do I do that ?
[08:54] <kandarpk> couldn't find it
[08:54] <dipankar> kandarpk, log into your alioth acoount
[08:54] <kandarpk> yeah
[08:54] <kandarpk> then ?
[08:55] <dipankar> on the top right corner click on 'my account'
[08:55] <kandarpk> I am there.
[08:55] <kandarpk> under my acc.
[08:55] <dipankar> scroll all the way down on the page
[08:56] <dipankar> there you will find : shell keys
[08:56] <dipankar> * Shell Account Information
[08:56] <dipankar> Shell box:
[08:56] <dipankar> SSH Shared Authorized Keys: 0
[08:56] <dipankar> Edit Keys
[08:56] <kandarpk> cant find it.
[08:56] <dipankar> click on 'Edit keys'.
[08:57] <dipankar> hmm.. thats weird. are you here : https://alioth.debian.org/account/
[08:58] <kandarpk> yes
[08:59] <dipankar> Search for this on the page : 'Shell Account Information'
[09:00] <dipankar> 'Cntrl + F' on the page
[09:00] <dipankar> kandarpk, I am going for lunch. Will be back in 15 minutes
[09:00] <kandarpk> not found :(
[09:00]  * dipankar is away: I'm busy
[09:11]  * dipankar is back (gone 00:10:40)
[09:11] <dipankar> kandarpk, thats really weird
[09:12] <dipankar> kandarpk, are you on the page : My Personal Page?
[09:12] <kandarpk> dipankar: My Page
[09:13] <dipankar> kandarpk, I am on 'My Personal Page'
[09:14] <kandarpk> I cant see 'My Personla Page' anywhere
[09:14] <kandarpk> got htere
[09:14] <kandarpk> *there
[09:14] <kandarpk> What to do now ?
[09:15] <dipankar> click on 'Account Maintenance'
[09:16] <kandarpk> Nothing for shell keys here
[09:17] <dipankar> I am unable to receive anything from anybody :(
[09:18] <kandarpk> mailing you @gmail
[09:19] <dipankar> kandarpk, please follow this page: http://wiki.debian.org/Alioth/SSH
[09:19] <dipankar> ^^ nice guide
[09:20] <dipankar> kandarpk, what is the .tar for btw?
[09:20] <kandarpk> the page
[09:21] <kandarpk> which contains no option for ssh key
[09:23] <dipankar> Thats really weird. My page shows a 'FORGE' Logo whereas yours is a little bit different.
[09:23] <kandarpk> you need to extract the tar to see them
[09:24] <dipankar> ^^ saw them :)
[09:25] <dipankar> kandarpk, see if you can access this page directly: https://alioth.debian.org/account/editsshkeys.php
[09:27] <kandarpk> how do I submit the key here ?
[09:27] <kandarpk> it only has a text bow
[09:27] <dipankar> finally. :)
[09:27] <kandarpk> :)
[09:28] <dipankar> copy your ssh key from the ~/.ssh/
[09:28] <kandarpk> put the contents of id_rsa.pub in it ?
[09:28] <dipankar> yes
[09:28] <dipankar> right on
[09:30] <kandarpk> Done
[09:30] <kandarpk> thanks
[09:30] <dipankar> no problem. Now you can push the changes.
[09:30] <dipankar> but remember, the changes will be accepted by the master only.
[09:30] <kandarpk> where will the changes go to ?
[09:31] <kandarpk> master only ?
[09:31] <dipankar> the changes will go (pushed) to the git repository of the package at alioth
[09:31] <dipankar> master : the one who controls the git repository
[09:31] <kandarpk> Ok.
[09:32] <kandarpk> If they are accepted, they will be uploaded to Debian repo ?
[09:32] <dipankar> now thats where I am stuck. Luke left before explaining that to me :)
[09:32] <kandarpk> Ok.
[09:33] <dipankar> In my opinion Debian Repo _are_ git repos only, but the accepted ones
[09:33] <dipankar> *git repos at alioth
[09:33] <kandarpk> hmmm
[09:34] <kandarpk> and the process of building and pushing is same as
[09:34] <kandarpk> mentioned here :
[09:34] <kandarpk> http://wiki.debian.org/Sugar/GettingStartedGuide
[09:35] <dipankar> Yes. Luke explained me the 'contributing a new package'
[09:35] <kandarpk> Ok.
[09:36] <dipankar> David already got that. :)
[09:37] <dipankar> he himself tried out the whole process
[09:37] <kandarpk> thats what I will end up doing
[09:40] <dipankar> :P
[09:41] <dipankar> David also told we should know this much right now
[09:41] <dipankar> when Luke comes back, he will carry further
[09:41] <kandarpk> Ok.
[12:11] <dfarning> good morning
[12:11] <kandarpk> dfarning: good morning
[12:11] <kandarpk> dfarning: had a good sleep ?
[12:15] <dfarning> yes, thank you.  I read backlog it looks like you made good progress.
[12:16] <kandarpk> dfarning: having issues with downloading
[12:16] <dfarning> kandarpk, a network issues?
[12:17] <kandarpk> dfarning: yes, but now its working
[12:17] <kandarpk> how did you know about it  ?
[12:18] <dfarning> kandarpk, network issues seem quite common in New Delhi
[12:19] <kandarpk> dfarning: No, just apt-get wasn't working
[12:19] <kandarpk> everything else was fine
[12:19] <kandarpk> there was some error like
[12:19] <kandarpk> *could not resolve
[12:19] <kandarpk> something
[12:20] <dfarning> kandarpk, that generally means that apt-get was unable to solve a  dependency.
[12:21] <kandarpk> but it worked fine now
[12:21] <kandarpk> minutes ago, I could not even update the system
[12:22] <dfarning> it is likely that it was a temporary issue.  cause by delays in the files being pulled through the ubuntu download network.
[12:23] <kandarpk> hmmm
[12:23] <dfarning> As you saw the best solution is to wait a couple of hours until things settle down.
[12:30] <dfarning> manusheel, good morning.  I looks like kandarpk and dipankar had a very productive debug session.  It was particularly valuable because network issues represent over half of the problems reported from the field.
[12:30] <dipankar> dfarning, good morning.
[12:31] <dfarning> manusheel, and if a teacher has a network issue they often give up becuase they can't figure out how to sovle it in a reasonable amount of time.
[12:31] <manusheel> dfarning: Good morning David.
[12:31] <manusheel> dfarning: I am very happy to hear from you on this aspect. I just had a telephonic conversation with Kandarp, and he was very happy to work on this exercise too.
[12:31] <manusheel> dfarning: Absolutely agree.
[12:31] <dfarning> dipankar, good morning.  looks like you had a good day with alsroot.
[12:32] <manusheel> dipankar: Good morning.
[12:32] <dipankar> manusheel sir: Its evening here!
[12:32] <manusheel> dipankar: Sorry. It seems like it is always morning for me.
[12:33] <manusheel> dfarning: Yes, I didn't get a chance to sleep last night. And, in the morning was in a meeting with JS developers.
[12:33] <dipankar> dfarning, alsroot helped a lot. More over he found a problem with running usr on Vb.
[12:34] <manusheel> dfarning: However, I am feeling fresh now. Meetings came along well.
[12:34] <manusheel> dipankar: Can you elaborate on the issue?
[12:34] <dipankar> sure,
[12:34] <dfarning> manusheel, when thinking about bug priorities it might be valuable to bump up network related issues because they represent an very high obstacle for teachers.
[12:35] <dipankar> The issue is:
[12:35] <dfarning> manusheel, you work too hard:)
[12:35] <manusheel> dfarning: David, absolutely. I like your plan. You focus on very core issues, which is important.
[12:36] <dipankar> in neighbourhood view we can't find any user online. on Virtual Box, I cannot even share an activity
[12:36] <manusheel> dfarning: Network issues are critical to solve. Can you point us to a resource from where we can get a clarity on the issues posted on network management front.
[12:37] <manusheel> dipankar: Yes, interesting.
[12:37] <manusheel> dipankar: Did we arrive at a good conclusion on this ?
[12:37] <dipankar> We tried on both Debian, Ubuntu 10.4, and USR -- separate envs
[12:38] <dipankar> on all we were able to share activities
[12:38] <dipankar> but could not find other users
[12:38] <dfarning> manusheel, luckily:) tomeu is employed by collabra the upstream maintainter of the telapthy stack and lfaraone helps maintain the network manager for debian.  So you have two experts on hand:)
[12:39] <manusheel> dipankar: Did you discuss this with alsroot and tomeu on how to arrive at a good conclusion on this?
[12:39] <dipankar> possible issue is with server down: try opening jabber.ubuntu.com
[12:39] <dipankar> oops sorr
[12:39] <manusheel> dfarning: That is great to hear. Thanks for informing me. I am very happy to hear that Tomeu is working with Collabora.
[12:39] <dipankar> *sorry wrong site
[12:39] <manusheel> Collabra*
[12:41] <dipankar> I consulted with alsroot only
[12:42] <manusheel> dfarning: Dafydd and Morgan are good friends in Collabra. It would be great to have Tomeu maintain the telepathy stack.
[12:43] <manusheel> dipankar: What did we arrive at?
[12:43] <dfarning> manusheel, very nice.
[12:44] <dipankar> manusheel, Sir, That the server is down
[12:49] <dipankar> manusheel, dfarning , The iso at the 140.186.70.115/seeta/output/ has some problem
[12:51] <dipankar> I am taking an half an hour break. Have been online whole afternoon
[12:51] <dfarning> dipankar, it looks very widespread.
[12:51] <dfarning> enjoy
[12:51] <dipankar> thanks David :)
[12:51]  * dipankar is away: I'm busy
[12:52]  * dipankar is back (gone 00:00:32)
[12:52]  * dipankar is away: I'm not here
[12:57] <kandarpk> *will be back in 10 min.( need to boot windows )
[13:40] <kandarpk> dfarning: I am not able to execute:
[13:40] <kandarpk> wget -P ..  http://download.sugarlabs.org/sources/honey/Colors/Colors!-15.tar.bz2
[13:40] <kandarpk> ERROR: 404 not found
[13:40] <kandarpk> http://pastebin.org/382764
[15:51] <dfarning> kandarpk, were you able to solve your problem?
[15:51] <kandarpk> dfarning: no
[15:51] <kandarpk> same error is being reported
[15:51] <dfarning> kandarpk, which activity are you working on?
[15:52] <kandarpk> dfarning: I ran the command in terminal
[15:52] <kandarpk> it was there on the starters guide
[15:52] <kandarpk> for git
[15:53] <kandarpk> http://wiki.debian.org/Sugar/GettingStartedGuide
[15:54] <dfarning> the path  http://download.sugarlabs.org/sources/honey/Colors/Colors!-15.tar.bz2 is for the activity color
[15:54] <dfarning> just a moment I will try
[15:57] <dfarning> kandarpk, are you gettin an error like
[15:57] <dfarning> wget -P ..  http://download.sugarlabs.org/sources/honey/Colors/Colors!-15.tar.bz2
[15:57] <dfarning> wget -P ..  http://download.sugarlabs.org/sources/honey/Colors/Colorscd temp/.tar.bz2
[15:57] <dfarning> --2010-07-04 09:56:52--  http://download.sugarlabs.org/sources/honey/Colors/Colorscd
[15:57] <dfarning> Resolving download.sugarlabs.org... 140.186.70.53, 2002:8cba:4635::1
[15:57] <dfarning> Connecting to download.sugarlabs.org|140.186.70.53|:80... connected.
[15:57] <dfarning> HTTP request sent, awaiting response... 404 Not Found
[15:57] <dfarning> 2010-07-04 09:56:52 ERROR 404: Not Found.
[15:57] <dfarning> --2010-07-04 09:56:52--  http://temp/.tar.bz2
[15:57] <dfarning> Resolving temp... failed: Name or service not known.
[15:57] <dfarning> wget: unable to resolve host address `temp'
[15:57] <dfarning> dfarning@y650:~/color-15$
[15:58] <kandarpk> http://pastebin.org/382764
[15:58] <kandarpk> Its very similar
[15:59] <kandarpk> but last 2-3 lines aren't there
[15:59] <kandarpk> nothing like `temp'
[16:01] <dfarning> kandarpk, try  wget -P ..  'http://download.sugarlabs.org/sources/honey/Colors/Colors!-15.tar.bz2'
[16:02] <dfarning> i think you need to quote anything with a ! mark init.
[16:02] <dfarning> s/init/in it/
[16:02] <kandarpk> This time it says permission denied
[16:03] <dfarning> kandarpk, what dir are you in?  do you have permission to write to the parent dir of your current dir.
[16:04] <kandarpk> dfarning: done
[16:04] <kandarpk> you were right
[16:05] <kandarpk> was in ~
[16:05] <dfarning> kandarpk, when in doubt about command try looking and the man page with 'man wget'
[16:06] <dfarning> the -P flag tells wget where to put the downloaded file.  '..' means parent.
[16:06] <kandarpk> hmmm
[16:06] <kandarpk> dfarning: I should have
[16:07] <kandarpk> dfarning: have you gone through this guide ?
[16:07] <kandarpk> the steps mentioned there ?
[16:08] <dfarning> kandarpk, I don't know the exact rules for when to use quote:(  but when ever I see a weird character like ! causing a string to change I try quoting the string
[16:09] <dfarning> kandarpk, yes dipankar and I went though it this morning.  but we used a different activity... log viewer I think
[16:10] <kandarpk> dfarning: here, we only are adding Debian specific "Debian" folder
[16:10] <kandarpk> to push it into debian, right ?
[16:10] <kandarpk> no need to change any source code as the package is already in working state
[16:11] <dfarning> kandarpk, are you asking in reference to the initial_debianization.tar.gz file?
[16:11] <kandarpk> or apply patches to it ...
[16:12] <kandarpk> dfarning: yes
[16:12] <dfarning> yes, there is no need to patch as everything works.
[16:13] <dfarning> the debian folder contains all of the packaging data
[16:14] <kandarpk> dfarning: this activity tells us how to configure a package so that it can be pushed to debian ?
[16:15] <neeraj_> dfarning: I am also learning abt git.. should I follow the same step as kandarpk is following or I should try another activity..
[16:15] <dfarning> kandarpk, rather than create those files from scratch every time ( which is prone to result in bugs) we use the skeleton that lfaraone made and modify it to meet our specific needs
[16:15] <dfarning> neeraj_, please try going throug the same tutorial.  that way we can all help answer eachothers questions.
[16:16] <kandarpk> neeraj: try the same activity for now
[16:17] <kandarpk> neeraj: if we'll have some time, we'll try it on some other package as well
[16:19] <neeraj> kandarpk, k doing so
[16:20] <neeraj> Now I should run git init in color15..
[16:23] <dfarning> neeraj, yes
[16:24] <neeraj> k.. done till pristine cmd
[16:25] <neeraj> git-import-orig --pristine-tar -u ''15'' ../Colors!-15.tar.bz2
[16:39] <kandarpk> dfarning: it was all about generating the Debian folder
[16:39] <kandarpk> according to the package
[16:40] <dfarning> kandarpk, yes all of the orginal source will stay the same unless we find a bug (while we test)
[16:41] <kandarpk> dfarning: how did it check for dependency ?
[16:41] <kandarpk> my package was in a different directory
[16:41] <kandarpk> corol-15 had only Debian in it
[16:41] <kandarpk> *color
[16:44] <dfarning> normally to test for build time and run time dependancies, you just try building and running the package.... and looking for error messages about missing libs of modules.
[16:44] <dfarning> kandarpk, In this case I just knew from experience that the dependancies were all there.
[16:50] <kandarpk> dfarning: even if I had not downloaded color-15!, wouldn't the control file have the same structue ?
[16:52] <kandarpk> after running DEB_MAINTAINER_MODE=1 fakeroot debian/rules clean
[16:53] <dfarning> kandarpk, The structure of the control will remain the same for most simple activities.
[16:58] <dfarning> kandarpk, I just sent a email to olpc-debian asking for guidance on howto push our work to alioth for review.
[16:59] <kandarpk> dfarning: Ok, we can now start considering pushicng the packages
[17:00] <kandarpk> s/pushicng/pushing/
[17:00] <neeraj> dfarning, in that guide its written that we re-generate control file using control.in
[17:00] <dfarning> kandarpk, yes, but I don't know that step yet:(
[17:00] <dfarning> neeraj, yes that is correct.
[17:00] <neeraj> and after that its written that we add certain dependency in control file..
[17:01] <neeraj> why is that.. shouldn't we first add dependency and then re-generate control file..
[17:02] <dfarning> neeraj, you are correct, we should edit control.in before we regenerate the control file.
[17:07] <neeraj> dfarning, kandarpk in control.in , Depends field has:= ${shlibs:Depends}, what does this type of notation signifies..
[17:07] <neeraj> I mean last time when I dropped some dependency there was only name.. like "python"
[17:08] <dfarning> neeraj, in bash $ indicates a variable.
[17:08] <dfarning> neeraj, in these packages the various dependancies are set in the rules file.
[17:13] <dfarning> neeraj, did that make sense?
[17:14] <neeraj> didn't exactly got the last line..
[17:14] <neeraj> hmm on guide Read debian/control. In debian/control.in, add beyond @cdbs@ the other things you need to build the package. For Colors!, we read in INSTALL that we need to add swig, gtk2-devel, python-devel, gstreamer-devel, pygtk2-devel
[17:15] <neeraj> Now I have to add these dependency in control.in file as per the guide..
[17:16] <neeraj> Should I just add these in Depends: filed as it is (swig, gtk2-devel, python-devel, gstreamer-devel, pygtk2-devel)
[17:16] <kandarpk> neeraj: the @cdbs@ in control.in checks the rules file to generate dependencies
[17:16] <neeraj> ok
[17:16] <kandarpk> if something's missing in rules you need to add that
[17:16] <kandarpk> dfarning: is it correct ?
[17:16] <neeraj> hmm.. you mean extra dependencies in control.in file
[17:17] <kandarpk> yes
[17:17] <neeraj> as control.in file will add the dependency acco to the rule file
[17:17] <neeraj> kandarpk, k.. :)
[17:18] <kandarpk> waiting for dfarning to confirm that...
[17:18] <dfarning> kandarpk, yes, if the dependancies are not automatically inculded via either @csbs@ substitution var or the ${shlibs:Depends} var you will add them by hand in the control.in file
[17:19] <kandarpk> dfarning: that means debian requires control.in as well as control in its packages
[17:20] <kandarpk> whereas Ubuntu required only control to be there
[17:22] <dfarning> kandarpk, both debain and ubuntu only use the control files when actually building the packages.  As packages we often use *.in to dynamically regenerate things like the control file while we are creating the package.
[17:23] <dfarning> s/as packages/as packagers/
[17:24] <kandarpk> dfarning: so shouldn't the extra dependencies which were missed out added to control file instead of control.in ?
[17:24] <neeraj> Depends: ${shlibs:Depends}, ${python:Depends}, swig, gtk2-devel, python-devel, gstreamer-devel, pygtk2-devel
[17:24] <neeraj> control.in.. is it correct way?
[17:25] <kandarpk> dfarning: or is it that after adding the missing dependencies, we regenerate the control file ?
[17:25] <dfarning> kandarpk, yes, I mispoke.... as human packagers we work with the files that end in *.in
[17:30] <kandarpk> dfarning: still not clear
[17:31] <kandarpk> we first add dependencies to control.in by looking at the missing dependencies in control, and then regenerate control ?
[17:32] <neeraj_> kandarpk sir, Generally we add these dependency after looking at install/read me file..
[17:33] <neeraj_> just see the install file in color15 :)
[17:33] <neeraj_> My be later we might/remove dependency for bug fixing and all
[17:33] <kandarpk> neeraj_, Ok.
[17:34] <dfarning> kandarpk, yes.  And it can also be an iterative process of modify control.in, regenerate control, test build, test run.... until every thing is correct.
[17:35] <kandarpk> dfarning: ok, really dynamic !
[17:37] <dfarning> kandarpk, yes, getting the dependencies right is often the hardest part of packaging.
[17:38] <kandarpk> dfarning: it surely is.
[17:39] <kandarpk> dfarning: its quite often that a dependency breaks a package
[17:40] <dfarning> kandarpk, yes that is correct.  It is usually caused when the author of a program we are packaging uses a different version of a lib dependancy then is available in the distro we are working with.
[17:41] <kandarpk> hmmm
[17:44] <dfarning> kandarpk, check out xulrunner in synaptic... ubuntu lucid ships 3 separate versions of the library because of dependency issues.
[17:46] <kandarpk> dfarning: Ok.
[17:47] <kandarpk> dfarning: does Sugar too faces such problem on Debian and Ubuntu ?
[17:48] <dfarning> kandarpk, sugar itself is pretty good.  The developers work pretty well to stay in sync with gnome.
[17:49] <dfarning> kandarpk, but the package browse does not work becase of xurunner issues.
[17:49] <kandarpk> Ok.
[17:50] <dfarning> kandarpk, rather than fix the xulrunner issues which are pretty deep ... we are moving browse to use webkit rather than xulrunner.
[17:51] <kandarpk> dfarning: hmmm, that seems a bit easier to implement
[17:51] <kandarpk> as studying xulrunner will take some time
[17:51] <dfarning> kandarpk, when browse was orginally written, xulrunner was the best choice.... but now that google has somewhere around 80 developers working on webkit, it is making fantastic strides.
[17:55] <kandarpk> google is causing many to change the technology being used
[17:55] <dfarning> kandarpk, yes it is and interesting dynamic
[17:56] <dfarning> kandarpk, google is still the primary funder for mozilla... yet google is creating it's own engine and browser.
[17:57] <kandarpk> maybe thats because they took a lot of codes available from mozilla
[17:58] <kandarpk> anyways, shall we work on resolving a bug ?
[17:58] <dfarning> kandarpk, sure which one?
[17:58] <kandarpk> even though I do not have a 3g modem, there is an icon to set up a 3g
[17:58] <kandarpk> modem -- should do hardware detection prior to showing icon.
[17:59] <kandarpk> dfarning, I have a point to add here
[17:59] <dfarning> kandarpk, yes?
[18:00] <kandarpk> in USR, the emulator show a cable connection that of the internet
[18:00] <kandarpk> but in Debian there was no such icon
[18:00] <kandarpk> in bottom right corner
[18:00] <kandarpk> even though the internet works fine
[18:02] <dfarning> kandarpk, networking is probably going to be our biggest problem.
[18:02] <kandarpk> dfarning: yeah, that is what you said before as well
[18:03] <dfarning> kandarpk, both debian and ubuntu use network manger to manage their networks see -- http://projects.gnome.org/NetworkManager/
[18:03] <dfarning> kandarpk, so it will reguire a good understanding of how network manager and sugar work together.
[18:06] <kandarpk> dfarning: the network manager detects the hardware being used ?
[18:06] <dfarning> kandarpk, I would suggest asking alsroot or bernie about the 3g modem situation.  I think it will lead to a better understanding of the how sugar manges the network.
[18:07] <kandarpk> Ok.
[18:07] <kandarpk> alsroot, around ?
[18:07] <kandarpk> bernie, around ?
[18:07] <alsroot> not /me since I dunnot nothing about 3g support ?
[18:08] <kandarpk> alsroot: Ok.
[18:10] <dfarning> kandarpk, looks like there is good background reading at http://live.gnome.org/NetworkManager
[18:14] <dfarning> manusheel, do you have a minute?
[18:14] <bernie> kandarpk: btw, I'm around now
[18:15] <bernie> kandarpk: for networking, ask tch on #sugar, he's the person that knows best. along with tomeu
[18:18] <manusheel> dfarning: Sure.
[18:18] <kandarpk> bernie: thanks
[18:18]  * dfarning thinks bernie is just having too much fun arguing about esoteric details of email:)
[18:18] <dfarning> manusheel, I think everybody has a good start in understand git and packaging via alioth.
[18:19] <manusheel> dfarning: We can talk.
[18:19] <manusheel> dfarning: I was preparing the e-mail for tomorrow's tasks. Adding resources.
[18:19] <dfarning> manusheel, great, I will wait for you email.
[18:19] <manusheel> dfarning: That is good news. So, we can push the activity packages to alioth now.
[18:20] <kandarpk> * will be back after logging into USR
[18:21] <manusheel> dfarning: Sure, it will take me 5 more minutes.
[18:21] <dfarning> manusheel, very close.  we can create the activites.... but we must clarify how to push them to alioth.  lfaraone can probobly help with that pretty quickly.
[18:21] <dfarning> manusheel, once they are pushed jonas or lfaraone will have to review them and submitte them to the build system.
[18:22] <manusheel> dfarning: Great. I think Luke will come at IRC for a while too.
[18:23] <manusheel> dfarning: Yes, it will be great if Luke or Jonas can review and submit them once we send them for approval.
[18:23] <dfarning> manusheel, because the ppa was our sandbox every thing we uploaded was automatically build.  Now that we are working in debian proper a DD or DM will have to review our work.
[18:23] <dfarning> manusheel, +1 i think we are very close.
[18:24] <lfaraone> dfarning: er, I don't maintain Network Manager.
[18:24]  * lfaraone will be back, rebooting his laptop.
[18:25] <dfarning> lfaraone, I thought I thought that was one of the packages you were working on to get your DD?
[18:25] <lfaraone> dfarning: no, sorry. NM == new maintainer process.
[18:27] <dfarning> lfaraone, :) opps,  I remember thinking the other day it was very very lucky that you were reviewing the NM documentation for your DD:)
[18:29] <manusheel> dfarning: Great. That is neat to hear.
[18:30] <dfarning> lfaraone, when you get a chance can you review the process for creating a repo on aloith and push to it,  I think both dipankar and kandarpk have activities which are ready for review.
[18:31] <manusheel> kandarpk and dfarning : Let us understand how we can push packages to Alioth.
[18:32] <kandarpk> manusheel sir: sure sir, thats what we still don't know
[18:32] <manusheel> dfarning: I think that is one important process where we need a confirmation on our steps.
[18:32] <manusheel> kandarpk, lfaraone: Can you discuss this part now?
[18:33] <manusheel> dfarning: Thank you for mentioning this aspect to me. Very important to understand the set of steps for this process completely.
[18:35] <kandarpk> lfaraone: I went through the documentation of git packaging starts guide
[18:35] <dfarning> manusheel, +1 uploading to aloith is the first time we are working outside our own machines or the ppa sandbox.  It is a big step.  The packages will have to meet the QA neceessary to be released to millions of users:)
[18:35] <kandarpk> and generated the control file
[18:37] <manusheel> dfarning: Absolutely. That is indeed a very important step.
[18:37] <lfaraone> Okay.
[18:37] <kandarpk> lfaraone: but generating the control file didn't require any packages
[18:38] <kandarpk> lfaraone: whose dependency did it check then ?
[18:38] <dfarning> manusheel, kandarpk I am going to lunch... hopefully lfaraone can show kandarpk and kandarpk show me tomorrow:)
[18:38] <manusheel> dfarning: I am interested in seeing how this activity comes along.
[18:38] <kandarpk> dfarning: :)
[18:38] <manusheel> dfarning: Sure.
[18:38] <lfaraone> kandarpk: did what check?
[18:39] <kandarpk> lfaraone: the control.in file checks for dependency of the package, right ?
[18:39] <kandarpk> and lists them in control file
[18:39] <lfaraone> kandarpk: the control file, generated from control.in, lists the dependencies.
[18:40] <lfaraone> kandarpk: CDBS determines the dependencies programmatically, using the contents of the debian/rules file.
[18:40] <lfaraone> manusheel: I think I went over the process of creating a new repository and pushing up to it with Dipankar.
[18:40] <kandarpk> lfaraone: whose dependency are we testing here ?
[18:41] <lfaraone> kandarpk: we're not testing anything at this stage, but we are determining the dependencies of the package.
[18:41] <lfaraone> kandarpk: dpkg checks that the dependencies are present when building the binary package.
[18:42] <lfaraone> manusheel: it's outlined fairly clearly at http://wiki.debian.org/Alioth/Git in "creating a repository" and "Accessing repositories", I think.
[18:42] <kandarpk> lfaraone: that is a bit confusing for me
[18:43] <lfaraone> manusheel: why did you assign sugar-logviewer-activity to neeraj when dipankar had already started work on it? (ref: http://git.debian.org/?p=collab-maint/sugar-logviewer-activity.git;a=summary )
[18:43] <kandarpk> lfaraone: when I generated the control file, there was no package in the directory having debian folder
[18:43] <lfaraone> kandarpk: which?
[18:44] <lfaraone> kandarpk: you were in a directory which contained the debian folder and the unpacked activity source, right?
[18:44] <kandarpk> lfaraone: the activity source was in the parent directory, not in the same as debian was
[18:45] <kandarpk> *where debian was
[18:46] <kandarpk> lfaraone: still control had some dependencies listed
[18:47] <lfaraone> kandarpk: yes, it bases them off what we put in the rules file, along with additional deps if it can determine them.
[18:47] <lfaraone> kandarpk: if it can't, it just assumes there aren't any.
[18:49] <kandarpk> lfaraone: it means there is a small set of dependencies which are always listed in the control file ?
[18:50] <lfaraone> kandarpk: well, your package needs to have CDBS and debhelper at the very least, and python, and sugar.
[18:51] <lfaraone> kandarpk: but not all packages use CDBS, or python, or sugar. Some don't even use debhelper :)
[18:53] <kandarpk> lfaraone: so, the rules file is written in such a way that it will assume that the packages depends on sugar,CDBS, Python, and some other minimum requirements ?
[18:53] <kandarpk> after listing these packages it will try to find other dependencies ?
[18:54] <lfaraone> kandarpk: yes. but usually it's not good at that, you'll need to test the package to ensure you have all the proper build dependencies.
[18:57] <kandarpk> lfaraone: hmmm, that is by listing other dependencies in control.in, generating control again, building the package
[18:57] <kandarpk> and continueing in such manner
[18:57] <kandarpk> until the package gets successfully compiled ?
[18:58] <kandarpk> build rather
[19:01] <lfaraone> kandarpk: yes.
[19:01] <manusheel> lfaraone: My apologies.  Had to attend a conference call. Just came back. Going through the logs.
[19:02] <lfaraone> kandarpk: if you use pbuilder, it'll create a "blank slate" to attempt to automatically build your package each time so you can ensure your deps are right.
[19:03] <kandarpk> lfaraone: thanks, that was helpful.
[19:03] <lfaraone> kandarpk: see http://www.eyrie.org/~eagle/software/scripts/git-pbuilder.html among other things.
[19:03] <lfaraone> manusheel: I had some additional comments on your assignment list which I sent by email, I'll merge it into http://wiki.debian.org/Sugar/tasks if you don't mind.
[19:04] <manusheel> lfaraone: That is a mistake from my side. I'll assign sugar-logviewer activity to Dipankar.
[19:04] <manusheel> lfaraone: Sure, absolutely.
[19:04] <lfaraone> manusheel: no worries.
[19:05] <lfaraone> kandarpk: by the way, what's your last name?
[19:05] <manusheel> lfaraone: Thank you. I'll be re-sending the e-mail to our team list with that change.
[19:05] <kandarpk> lfaraone: kaushik .
[19:06] <kandarpk> lfaraone: thats why a k there
[19:06] <manusheel> lfaraone: Let us assign sugar-logviewer activity to Dipankar.
[19:06] <manusheel> lfaraone: Any other pointers/changes that you would like to recommend in the new e-mail that I am drafting.
[19:07] <lfaraone> manusheel: I'm already handling terminal, and Matthew Gallagher (external of us) was working on TurtleArt.
[19:09] <manusheel> lfaraone: So, I'll add Kandarp's name along with your name in the terminal activity. Will that be alright with you? Please let me know. If not, me and Kandarp will be absolutely fine with it.
[19:11] <lfaraone> manusheel: I'm not sure what you mean by that. I just didn't want us to be duplicating work, and I'm pretty much done with terminal.
[19:11] <kandarpk> lfaraone: how is debcommit different from git-commit ?
[19:12] <dfarning> manusheel, one of the reasons for including several packages which are being worked on is to show the communication challenges of working in a distributed environment and the values of the ITP:)  Unless one has first hand experienced the pain of spending several days working on something only to find out that someone else has already done it, things like ITP bug seem like busy.
[19:12] <lfaraone> kandarpk: oh, the tutorial says use debcommit, ignore that for now. I should remove that since we're not doing that with git.
[19:13] <manusheel> lfaraone: Ok. Sure, Luke. You are right. Having two people maintain the same activity is not productive.
[19:13] <lfaraone> kandarpk: debcommit automatically calls on git-commit using the contents of the changelog. We want to do that the other way around, generate debian/changelog from the contents of the git messages, but the guide does not cover that right now.
[19:13] <kandarpk> lfaraone: we can ( and should ) use git-commit ?
[19:14] <lfaraone> manusheel, dfarning, we also might want to consider that we might not wish to port over all the Sugar activites in Ubuntu.
[19:14] <lfaraone> kandarpk: yes.
[19:14] <lfaraone> manusheel, dfarning, since I don't think all of them have been up to date.
[19:14] <lfaraone> manusheel, dfarning, if the lastest upstream version of them doesn't work in sugar, we shouldn't ship them.
[19:15] <lfaraone> unless we believe they are of a great pedagogal importance or something :)
[19:15] <manusheel> lfaraone: Absolutely. Completely agree. However, we should check on such activities, and contact their respective authors about it.
[19:15] <lfaraone> Makes snese.
[19:16] <manusheel> lfaraone: We'll work on arriving at this list. Will start contacting the activity authors.
[19:16] <dfarning> lfaraone, I grabbed the list I sent manusheel from http://wiki.debian.org/Sugar/tasks .. wasn't that the the table you just created based on the SoaS list.
[19:17] <lfaraone> dfarning: the top table are "all the activities in Ubuntu that are not in Debian". I marked those in SoaS with an "X" in the "In SoaS" column.
[19:18] <lfaraone> dfarning: the lower table is composed of SoaS activities that are not in Ubuntu *or* Debian at the moment.
[19:18] <lfaraone> Apologies if it was unclear.
[19:19] <dfarning> lfaraone, I just read too fast:(
[19:20] <dfarning> lfaraone,  I'll let you and manusheel worry about the actual package list.
[19:23] <manusheel> dfarning: Thank you.
[19:23] <manusheel> lfaraone: Wish to ask you if you would like me to add any other activity.
[19:23]  * dfarning thinks lfaraone is trying to rile me up by suggesting that we make technical decisions for pedagogical reasons.... or pedagogical decisions for technical reasons:)
[19:24] <manusheel> lfaraone: I hope the list of activities that I covered in the memo were good for now.
[19:24] <manusheel> dfarning : Interesting :-)
[19:24] <lfaraone> dfarning: I think we should package activities that showcase what Sugar can do.
[19:26] <lfaraone> dfarning: it's up to you which those are.
[19:26] <lfaraone> dfarning: For sure, I think that porting these Ubuntu packages to Debian is useful taskbuilding.
[19:27] <dfarning> lfaraone, +1 package what _works_ and what shows what sugar can do.  We are still in the prototype and learning phase.
[19:28] <lfaraone> dfarning: yep. I'm sure that for example fixing https://bugs.launchpad.net/bugs/601242 can be solved through a new upstream version.
[19:29] <lfaraone> dfarning: I think it'll be really great once we have everyone's work on git, since we'll be able to easily audit the result and help solve problems that way.
[19:38] <manusheel> dfarning, lfaraone: My apologies. Got logged out of IRC.
[19:39] <manusheel> lfaraone: Can you please send me what you wrote in reference to my questions? Thank you.
[19:39] <lfaraone> manusheel: http://sprunge.us/EQQA
[19:40] <bernie> kandarpk, dfarning: we have a confcall with adam holt on the 3G status at 4pm EST
[19:40] <bernie> kandarpk, dfarning: if you want to join in, I can forward you the details
[19:41] <manusheel> lfaraone, dfarning: Final draft ready at my end. Sending it across.
[19:42] <manusheel> lfaraone, dfarning: Appreciate your feedback. Thank you.
[19:42] <manusheel> bernie: I would like to join too.
[19:42] <kandarpk> bernie: I wont be available then
[19:43] <kandarpk> :(
[19:43] <manusheel> kandarpk: I'll share the meeting points with you. Kindly send me the list of questions that you would like me to ask.
[19:44] <manusheel> kandarpk: Yes, you need to take rest, and sleep on time. You have been working all day long.
[19:44] <kandarpk> manusheel sir: its very hard to think about the questions without knowing much about the issue
[19:44] <kandarpk> manusheel sir: I'll be here for another hour, I think
[19:44] <bernie> manusheel: forwarding the info to you too
[19:45] <manusheel> kandarpk: Sure.
[19:46] <manusheel> bernie: Thank you.
[19:46] <lfaraone> manusheel: no such mail has arrived.
[19:46] <kandarpk> bernie: thanks for asking :)
[19:46] <lfaraone> oh, you shared it via google docs without notifying.
[19:48] <manusheel> lfaraone: You'll receive the e-mail in some seconds. Network has been slow today in Delhi. Heavy thunderstorms here.
[19:48] <manusheel> lfaraone: Will be adding the tasks in google docs.
[20:30] <manusheel> kandarpk: Will we be comfortable packaging the first set of activities tomorrow?
[20:32] <kandarpk> manusheel sir: If pushing the packages is not a very involved task, we can do that
[20:33] <manusheel> kandarpk: Great. Glad to hear.
[20:34] <manusheel> kandarpk: I'll ask everyone to study todays' meeting logs too.
[21:07] <kandarpk> dfarning: around ?
[21:07] <kandarpk> lfaraone: around ?
[21:08] <lfaraone> kandarpk: sure.
[21:09] <kandarpk> lfaraone: are the packages that we are required to build for debian need to be downloaded from sugarteam's PPA ?
[21:09] <kandarpk> sugarlabs has outdated version of read
[21:11] <lfaraone> kandarpk: Sugar Labs does?
[21:12] <kandarpk> http://download.sugarlabs.org/sources/sucrose/fructose/Read/
[21:12] <lfaraone> kandarpk: er, looks like read is already packaged in Debian, we can probably skip it: http://packages.debian.org/unstable/x11/sugar-read-activity-0.86
[21:20] <kandarpk> lfaraone: ok.
[21:26] <manusheel> lfaraone: Thank you for the pointer.
[22:16] <dfarning> lfaraone, how do you think things will go working on the activities for debian?
[22:17] <lfaraone> dfarning: I think the existing activities will not be a problem. Others, will be.
[22:17] <lfaraone> dfarning: most of the SoaS activities are not pure-python.
[22:17] <lfaraone> dfarning: for Physics, for example, I have to create three new packages.
[22:18] <dfarning> lfaraone, arggg.... so much for no external dependancies:(
[22:18] <manusheel> lfaraone: Can you recommend a strategy on arriving at a good solution. The idea is to minimize the overhead.
[22:18] <lfaraone> dfarning: the "no external deps" are just bundled in the upstream tarball. which means I have to create a new, clean DFSG-repack of the original tarball so we can legally ship it.
[22:20] <dfarning> lfaraone, yah... been watching that.... it looks a lot like a three card monty:(
[22:20] <lfaraone> dfarning: je ne sais pas.
[22:23] <dfarning> lfaraone, do you have an easy activity for me to work on this afternoon.
[22:23] <lfaraone> dfarning: from scratch?
[22:24] <lfaraone> dfarning: well, how hard could xoirc be?
[22:24] <dfarning> lfaraone, ok I'll try it.
[22:28] <lfaraone> I really want to kill upstream right now. Since s-physics-a embedds python-box2d. So I had to repack the tarball to exclude it. Now, I have to package pybox2d since it isn't packaged yet but pybox2d only has zip releases and they themselves bundle the C box2d.
[22:31] <dfarning> lfaraone, manusheel looking forward ... once we have a good feel for ubuntu on debian should we shift emphasis to working directly on the 10.10 packages.  Or start pushing patches against 10.04 in universe.  I would like to start moving away from the PPA:)
[22:35] <manusheel> dfarning: Yes, we can shift to 10.10 once we have Sugar on Debian ready. lfaraone, any hidden issues that we are missing?
[22:38] <manusheel> dfarning: On a separate note, Ankur gave me a telephonic call today. His place suffered from a blackout throughout the day due to heavy thunderstorms in Delhi.
[22:38] <manusheel> dfarning: Ankur will be coming today to work.
[22:39] <manusheel> He'll make arrangements as informed to me.
[22:39] <dfarning> manusheel, sounds like you are having a down pour.
[22:40] <manusheel> dfarning: :-) Very heavy rains.
[22:40] <manusheel> Down pour indeed.
[22:42] <dfarning> manusheel, based on https://wiki.ubuntu.com/MaverickReleaseSchedule we can shoot for syncing up with the ubuntu for the 1st week of their release development iteration two.
[22:44] <manusheel> dfarning: Sure. We should start the release development iteration 2 planning.
[22:45] <manusheel> dfarning: Any pointers on how you would like us to proceed?
[22:46] <dfarning> manusheel, I was also thinking about the areas of functional expertise.... we might want to shift someone to networking:)
[22:48] <manusheel> dfarning: Right, David. I am planning to get one developer full time on networking starting this month.
[22:48] <manusheel> dfarning: The developer will be working with Tomeu and the collabra dev team.
[22:50] <manusheel> dfarning: Not interested in shifting Dipankar/ Neeraj/ Kandarp and Ankur full time into networking. They are working on core OS areas at this juncture.
[22:51] <manusheel> dfarning: Can you prepare a set of goals and tasks that will be required to be accomplished by the developer in this stream? I'll make plans accordingly.
[22:51] <manusheel> dfarning: Our core team members will continue to work on core OS areas.
[23:06] <manusheel> dfarning: Please let me know your thoughts on it.
[23:07] <dfarning> manusheel, sorry I got company.
[23:07] <manusheel> dfarning: Absolutely fine.
[23:07] <manusheel> We can talk sometime soon.
[23:08] <dfarning> I'll email as soon as I can:)  I have a one year, old a two year old, and a dog visiting.
[23:08] <dfarning> thanks
[23:10] <manusheel> dfarning: Sure. Thank you. Looking forward to your memo.