[15:29] <manusheel> dipankar: Hi Dipankar.
[15:29] <dipankar> manusheel, Hello Sir
[15:29] <manusheel> dipankar: Ishan will be back in 5 mins. He is having his dinner.
[15:30] <dipankar> manusheel, no problem. I am just scanning my mail
[15:34] <dipankar> manusheel, http://lists.sugarlabs.org/archive/sugar-devel/2010-September/027203.html
[15:34] <dipankar> manusheel, Sir, would be great if you could explain the last para. :)
[15:35] <dfarning> dipankar, Sugar .90 will be released in a couple of day.... I was supposed to be today.
[15:36] <dipankar> dfarning, hello. How are you doing?
[15:36] <dipankar> dfarning, thanks for the info.
[15:37] <dfarning> dipankar, tomeu is asking that you re submitte that patch against the .91 development branch as soon as it is open.
[15:37] <dfarning> dipankar, doing fine.
[15:37] <dipankar> dfarning, ohk.
[15:37] <dfarning> dipankar, are you familiar with the release process and cycles?
[15:39] <dipankar> dfarning, I think yes. But would like to know in detail..
[15:40] <dfarning> dipankar, I'll send an email to sugar devel in a couple of hours explaining the process.
[15:42] <dipankar> dfarning, that will be great! Thanks a lot
[15:42] <dipankar> :)
[15:42] <manusheel> dfarning: That would be great. Thank you.
[15:42] <dipankar> ishan, hi. What all did you cover last night?
[15:43] <ishan> dipankar, nothing much
[15:43] <dfarning> dipankar, manusheel time based releases are rather strange compared to traditional releases.
[15:45] <manusheel> dfarning: Indeed.
[15:45] <dipankar> ishan, lets continue then.
[15:46] <ishan> sure
[15:46] <dipankar> ishan, we have to create a new palette
[15:46] <ishan> yes
[15:46] <dipankar> for displaying the volume status bar.
[15:46] <dipankar> the code is already there in JournalPalette(), we can use that I guess
[15:47] <ishan> dipankar, back in 5 mins
[15:49] <manusheel> dipankar: Right.
[15:49] <manusheel> It is in JournalPalette().
[15:50] <dipankar> yes sir
[15:50] <manusheel> dipankar: Can you start adding the code? I'll ask Ishan to check this soon.
[15:50]  * ishan is back
[15:50] <dipankar> manusheel, I am trying sir
[15:50] <ishan> dipankar, sir did you checked the file which i sent you yesterday
[15:50] <manusheel> dipankar: Ishan is back. So, you can coordinate.
[15:51] <manusheel> ishan: Can you send me the meeting logs?
[15:51] <dipankar> manusheel, ishan: Lets call our new palette 'JournalVolumePalette()
[15:52] <dipankar> '
[15:52] <dipankar> alsroot, ping
[15:52] <manusheel> dipankar: Sure.
[15:52] <ishan_> dipankar, sure
[15:52] <alsroot> dipankar: pong
[15:53] <dipankar> alsroot, can the new Palette be made such that it doesn't require any argument?
[15:54] <alsroot> dipankar: why not, Palette class doesn't require any arguments (there are deprecated ones but they are optional)
[15:55] <dipankar> alsroot, But I see JournalPalette constructor calls the BasePalette.__init__(self, home_activity)
[15:55] <dipankar> constructore
[15:56] <dipankar> * I don't like this arguments things :P
[15:56] <alsroot> dipankar: BasePalette is child class, if you don't need it just use basic Palette class
[15:57] <dipankar> alsroot, ohk.. just like the VolumePalette() ?
[15:57] <alsroot> dipankar: yup
[15:58] <dipankar> ishan, I think I got what alsroot was initially trying to say. (Using VolumePalette() for code)
[15:58] <dipankar> alsroot, sorry it took sometime for me to figure it out
[15:58] <ishan_> dipankar, +1
[15:59] <dipankar> ishan_, Lets try doing one thing.
[16:00] <dipankar> ishan_, first try creating a Palette using VolumePalette()
[16:00] <dipankar> palette = VolumePalette('/')
[16:00] <ishan_> dipankar, sure
[16:00] <dipankar> in JournalButto
[16:01] <dipankar> that will give us the idea what we can start omitting.
[16:01] <dipankar> (Reverse Engg. :P )
[16:02] <ishan> dipankar, you are basically refering to calling volumepalette from Journalbutton
[16:02] <ishan> right?
[16:03] <ishan> dipankar, or are you talking abt creating a new class in under journal button for creating new palette having volumepalette features
[16:03] <dipankar> ishan, the first one. Calling VOlumePalette() in JournalButton
[16:03] <ishan> dipankar, okay
[16:04]  * dipankar is testing the palette=VolumePalette('/')
[16:06]  * dipankar is getting nice error :P
[16:10] <ishan_> dipankar, it seems to show no error when we pass self as argument only
[16:10] <dipankar> ishan_, but is it working?
[16:11] <ishan_> dipankar, next problem we get is about self.props.secondary_text = mount.get_root().get_path() defined in volumepalette
[16:11] <ishan_> according to logs
[16:12] <dipankar> ishan_, yup
[16:12] <dipankar> ishan_, I think I got a method.
[16:12] <ishan_> dipankar, great
[16:13] <dipankar> ishan_, If you look at code for BasePalette in Palettes.py
[16:13] <dipankar> no argument is passed in Palette.__init__()
[16:14] <ishan_>     def __init__(self, home_activity):
[16:14] <ishan_>         Palette.__init__(self)
[16:16] <dipankar> ishan_, we need just this part:
[16:16] <dipankar> self._free_space_label.props.label = _('%(free_space)d MB Free') % \
[16:16] <dipankar>                 {'free_space': free_space / (1024 * 1024)}
[16:16] <dipankar> in VolumePalette.
[16:16] <ishan_> dipankar, yes along with the bar
[16:16] <dipankar> ishan, manusheel : I am gong for dinner
[16:17] <dipankar> meet you soon
[16:17] <ishan_> dipankar, sure
[16:17] <ishan_> meanwhile i will try to work it out
[16:23]  * ishan_ is away for 10mins
[16:38]  * ishan is back
[16:38] <manusheel> ishan: Hi Ishan.
[16:38] <ishan_> manusheel, hi sir
[16:38] <manusheel> ishan_: Any help needed on the issue/
[16:38] <manusheel> ?
[16:39] <ishan_> manusheel, we are still trying to figure out the code to be written for the journal button
[16:40] <manusheel> ishan_: Ok.
[16:41] <manusheel> ishan_: Can you work on it independently for the time being. It might take Dipankar sometime to join back.
[16:41] <ishan_> manusheel, sir already doing that
[16:47] <manusheel> ishan_: sure.
[16:52] <ishan> manusheel, finally something able to display the status bar but it still doesnt shows the size sir
[16:56] <manusheel> ishan: Ok.
[16:57] <manusheel> That is unfortunate to hear. Which function are we calling for the size?
[17:04] <ishan_> still trying to figure out
[17:06] <manusheel> ishan_: Sure.
[17:55] <mukul> hi manusheel sir
[17:55] <manusheel> mukul: Hi Mukul.
[17:55] <mukul> manusheel sir
[17:56]  * dipankar is back
[17:56] <manusheel> mukul: Can you tell me what all issues are we facing in the bug?
[17:56] <ishan> dipankar, sir bug solved
[17:56] <mukul> i am working on 484 wherein it seems transfer of files bw 2 users on a network is being talked about
[17:56] <manusheel> dipankar: Hi Dipankar. Ishan did a great job.
[17:57] <manusheel> mukul: Sure. Let me have a quick look on it again.
[17:57] <dipankar> ishan, thats geat
[17:58] <dipankar> ishan, what is the solution?
[17:58] <ishan> dipankar, sir coudnt have happened without your help
[17:58] <ishan> dipankar, just posting git diff
[17:58] <dipankar> ishan, how?
[17:58] <dipankar> :P
[17:58] <ishan_> alsroot, dipankar check http://pastebin.com/23c0wrTJ
[17:59] <manusheel> mukul: Did we see the cancel option?
[17:59] <mukul> yes
[17:59] <mukul> only sumtimes though
[17:59] <manusheel> mukul: So, how did we reproduce this issue?
[18:00] <ishan_> alsroot dipankar: any pointers /suggestion on the naming part
[18:00] <mukul> i had taken shan's help yesterday. exact issue is nt yet reproduced. asked him to be present at the same time on sugar,then added him friend then sent a file to him.
[18:02] <manusheel> mukul: Ok.
[18:03] <mukul> manusheel sir: since it seems a network issue i would need someone whom I can test with.
[18:03] <manusheel> mukul: So, this issue was in reference to collaboration.
[18:03] <mukul> manusheel sir : This is what I suspect.
[18:03] <manusheel> mukul: You can test this with Dipankar.
[18:03] <mukul> #  summary  changed from file transfer: when a transfer finishes successfully, invitations still display a Cancel option to successful file transfer: offer to open Journal and to open activity
[18:04] <manusheel> mukul: Add a comment over there.
[18:04] <manusheel> mukul: That is at the test track item.
[18:04] <alsroot> ishan_: just minor issues, why not to rename NewJournalPalette to something like JournalButtonPalette (since it is not new palette), also better to avoid redundant adding/removing spaces like in lines 22
[18:04] <mukul> manusheel sir: This was what was one of the comments at the bug ticket. So i guess, it is a netowrking issue.
[18:05] <ishan_> alsroot, sure
[18:05] <mukul> and I see a Cancel button too but I couldn't make out how a file was being transferred if at all it was transferred.
[18:05] <alsroot> ishan_: also there are bunch of commented lines
[18:06] <mukul> dipankar, Hi
[18:07] <dipankar> mukul, hey hi
[18:07] <mukul> dipankar, could you help me test 484
[18:07] <mukul> dipankar, it seems a networking issue.
[18:07] <dipankar> test 484?
[18:07] <dipankar> mukul, ^^
[18:07] <mukul> manusheel sir: What should I comment?
[18:08] <mukul> SL # 484: File transfer
[18:09] <dipankar> mukul, just a sec
[18:10] <dipankar> mukul, well, you asked me this a couple of days back. I am not getting what the bug is saying.. :(
[18:11] <dipankar> mukul, is it from a pendrive to journal
[18:11] <dipankar> ?
[18:11] <mukul> dipankar, Yeah sir. No problems. I guess I now know what they mean by File transfer. They mean file transfer on a network to a buddy using Send To. I want to reproduce it.
[18:15] <mukul> dipankar, does neighbourhood not work on sugar-jhbuild?
[18:16] <dipankar> mukul, I am unable to see anybody on neighbourhood in jhbuild
[18:16] <dipankar> can anyone confirm this.
[18:16] <dipankar> ?
[18:16] <mukul> dipankar, same here. Let us test on sugar-emulator
[18:16] <dipankar> ishan_, great work I must say.
[18:16] <ishan_> dipankar, thank you
[18:16] <dipankar> sure
[18:17] <dipankar> mukul, I am on neighbourhood
[18:18] <ishan_> alsroot, dipankar : check http://pastebin.com/qAMjgibh
[18:19] <dipankar> alsroot, ishan_ , I would suggest defining the _new_ palette in graphics/palettes.py.. what say?
[18:19] <dipankar> this way we may do away with additional importing.
[18:19] <dipankar> (in volumestoolbar.py)
[18:20] <ishan_> dipankar, nice
[18:20] <dipankar> mukul, I can't see you. Are you there on sugar-emulator?
[18:20] <alsroot> dipankar: but JournalButtonPalette is in local class for sugar shell..
[18:21] <ishan_> alsroot, +1
[18:21] <mukul> I can see you.
[18:21] <ishan_> alsroot, it is fine now?
[18:21] <dipankar> alsroot, how about including it with from jarabe.view.palettes import VolumePalette
[18:21] <dipankar> s/ 'from jarabe.view.palettes import VolumePalette'
[18:21] <mukul> dipankar, I made you a friend and then sent a file too
[18:22] <dipankar> alsroot, oops I accidentally wrote graphics/palette.py.
[18:22] <alsroot> ishan_: there are pep8 issues, you can check it using pylint/pep8.py but the problem that the rest of volumestoolbar.py also doesn't conform pep8
[18:22] <dipankar> it should be view/palettes.py
[18:23] <ishan_> alsroot, didnt get you
[18:23] <alsroot> dipankar: well, VolumePalette is journal related code not shell specific
[18:23] <ishan_> alsroot, okay got it
[18:25] <dipankar> alsroot, what i meant was, define the new palette class in palettes.py where other palettes are defined, and then include using, 'from jarabe.view.palettes import VolumePalette, newPalette'
[18:26] <dipankar> mukul, neither of them is happening
[18:26] <alsroot> dipankar: at the end it will depend on what maintainer thinks, in my mind better to avoid messing shell code and journal
[18:27] <dipankar> alsroot, ohk. Then I agree with you
[18:27]  * ishan_ is away for 10mins
[18:27]  * dipankar doubts whether the 'add as friend' works
[18:28] <mukul> I could do that. But then if i am making you a friend and sending a file to you and you don't get to know about it. What is the use?
[18:28] <mukul> dipankar, It works partially
[18:28] <dipankar> manusheel, alsroot, mukul : can you please check one thing? I need you to add me as your friend from neighbourhood view in sugar
[18:30] <manusheel> dipankar: Sure.
[18:30]  * alsroot can't, rebuilding tp
[18:31] <dipankar> alsroot, ok
[18:33] <dipankar> manusheel, mukul : how come I am not getting any invitation?
[18:34] <mukul> dipankar, exactly. i dont' get it
[18:36] <dipankar> mukul, I think telepathy is messed up at some place.
[18:43] <mukul> dipankar, +1
[18:51] <mukul> dipankar, Please check in your journal whether any new entry exists called as tamyblock.py
[18:52] <dipankar> mukul, no.
[18:52] <mukul> dipankar, Please check sthing unusual in your frames.
[18:53] <dipankar> frames?
[18:53] <dipankar> * I am going through telepathy-gabble.log
[18:53] <mukul> dipankar, I mean the borders that appear when you hover your mouse near an edge.
[19:05] <dipankar> mukul, what is the problem?
[19:06] <mukul> dipankar, I wanted to ensure whether you have received the file coz here it stopped showing the cancel button but instead showed the dismiss button which is an indication that the transfer was complete.
[19:08] <dipankar> mukul, no. no file received
[19:10] <dipankar> dfarning, ping.
[19:10] <dfarning> dipankar, yes
[19:10] <dipankar> dfarning, just wanted to ask whether the Sugar on Ubuntu for maverick is accepted or not..
[19:11] <dipankar> dfarning, If I am not wrong, Maverick will be released in October.
[19:12] <dfarning> dipankar, yes it has.  neeraj is managing the packages.  it will be release in oct 10.
[19:12] <dipankar> dfarning, thats great! Thanks for the info
[19:14] <dipankar> all, please add the bug info here : https://wiki.ubuntu.com/Sugar/Tasks/BugBashing
[19:15] <dfarning> dipankar, the sugar on maverick release will be based on sugar .88.  becasue it was too complicated to try to fit sugar .90 released with in the next couple of days onto maverick relesed on oct 10.
[19:15] <dipankar> dfarning, ok. So in 11.04, Sugar .90 will be fitted?
[19:16] <dfarning> dipankar,  for the next ieteration of ubuntu released in april 4/11 we will use try to use sugar .92.
[19:16] <dfarning> dipankar,  that way we get the latest bug fixes.
[19:16] <dipankar> dfarning, .92! thats cool!
[19:17] <dfarning> dipankar, it was just too macy moving pieces for our first release :)
[19:17] <dfarning> many
[19:17] <dipankar> dfarning, sugar is very very fast developing!
[19:17] <dfarning> dipankar, this time we are still learning.... next time we will be going full speed.
[19:18] <dipankar> dfarning, yay!
[19:20] <dfarning> dipankar, I said that I would write a email about the release process.... the main idea is that time based release are like a train schedule.  There are literally 1000s of projects all working interdependently.... but trying distribute various software to users.
[19:21] <dipankar> dfarning, ohk
[19:22] <dfarning> dipankar, if an individual person(or patch) is late. it can catch the next train.   but if a train is late it can cause the entire system to fall behind.
[19:22] <dfarning> dipankar, in particular we are interested in the ubuntu and fedora releases.  We are trying to have our stuff ready for them.
[19:23] <dipankar> dfarning, okk.
[19:24] <dfarning> dipankar, but we are also dependant on everything upstream.... I am sure you have seen talk about the move to gtk3.  basically gnome is making a refactoring.  so sugar will have to also follow suit and do some refactoring to match.
[19:25] <dfarning> dipankar, then downstream we have other deployment which various releases of dextrose of olpc releases.
[19:25] <dfarning> deployments which use
[19:25] <dfarning> and
[19:25] <dfarning> other olpc releases.
[19:27] <dipankar> ohk.
[19:28] <dfarning> dipankar, I am often talking about engineering trades offs.  the big trade off in software is the pace of releases.  developers like very fast releases.  6 months is pretty common becase it is very easy for a developer to updates his machine.
[19:28] <dipankar> dfarning, ok..
[19:29] <dfarning> dipankar,  on the other hand large scale users like slow and stable releases.  it is very hard to update the 700,000 xo which have been deployed in UY.
[19:30] <dfarning> dipankar, in general school prefer a 5 year release cycle!
[19:31] <dipankar> dfarning, so there are two groups : large and developer
[19:32] <dipankar> large are the normal users
[19:32] <dipankar> and developers are, well... super-users
[19:34] <dfarning> dipankar, yes in general it is easier to think of users as on a spectrum from developer to deployment.
[19:35] <dfarning> developers are very frequest updaters -- many use jhbuild which can be updated several times per day
[19:35] <dfarning> to deployments which are very hard to update.
[19:36] <dipankar> ohk
[19:36] <dipankar> manusheel, I have sent the patch (modified)
[19:37]  * dipankar likes the system of peer review
[19:38] <dipankar> dfarning, manusheel : I think I should be heading to bed now. Its late.
[19:38] <dfarning> dipankar, so back to the train anology..... in order to be useful trains should run often and 24 hours pre day..... even though most users will ride on a couple of rush hour expresses:)
[19:38] <dfarning> dipankar, good night.
[19:40] <dipankar> dfarning, the analogy is better said by subways :P ;)
[19:40] <dipankar> dfarning, goodbye. see you tomorrow