[15:06] <dipankar> lfaraone, hi, around?
[15:12] <lfaraone> dipankar: for a short while. what;s up?
[15:22] <dfarning> dipankar, how are you coming? any questions?
[15:25] <dipankar> dfarning, good. working on ticket #2289.
[15:26] <dfarning> dipankar, did you see you got a couple of reviews and suggestions on sugar-devel
[15:28] <dipankar> dfarning, looking at it :)
[15:35] <manusheel> ankur__: Hi Ankur.
[15:35] <manusheel> ankur__: Are you still working on Neeraj's machine?
[15:35] <ankur__> hi manusheel sir
[15:35] <dipankar> lfaraone, I need your help a bit in changing my account preferences at  :http://lists.sugarlabs.org/listinfo/sugar-devel
[15:35] <ankur__> yes sir
[15:36] <manusheel> ankur__: Ok.
[15:36] <dipankar> lfaraone, I want to change mailing type from 'batch' to 'mail per post'. Would be great if you could help me out
[15:38] <dipankar> dfarning, here : http://bugs.sugarlabs.org/ticket/2289
[15:40] <dipankar> dfarning, Sascha commented"
[15:40] <dfarning> dipankar, looking
[15:40] <dipankar> if all we're doing in TimeoutServerProxy is adding a parameter and we only have one trivial caller, why add a new class at all?
[15:40] <dipankar> +    def make_connection(self, host):
[15:40] <dipankar> +        host, extra_headers, x509 = self.get_host_info(host)
[15:40] <dipankar> +        conn = TimeoutHTTP(host, timeout=self.timeout)
[15:40] <dipankar> +        return conn
[15:40] <dipankar> Please combine the last two lines."
[15:40] <dipankar> dfarning, wish if you could provide a solution for this ^^
[15:41] <dfarning> dipankar,  return TimeoutHTTP(host, timeout=self.timeout)
[15:41] <dipankar> dfarning, that part is done :)
[15:41] <dipankar> dfarning, about removing classes
[15:41] <dfarning> dipankar, the first solution is just making a local variable which is not used.
[15:42] <dipankar> dfarning, how can we remove the classes when they are derived from base classes on purpose?
[15:43] <dfarning> dipankar, see http://lists.sugarlabs.org/listinfo/sugar-devel to modify your ML subscription
[15:45] <dipankar> dfarning, I through with that. Thanks :)
[15:47] <dipankar> dfarning, about replacing classes with functions? I can't get any solution to that part
[15:50] <dfarning> dipankar, I suggest talking to silbe on #sugar about that.  He might not have a good answer.... but can explain his thinking.  BTW asking specif questions is important..  Please give me pointers about .....? puts the preassure on the other person to solve your problem.  I think you will have more luck asking a specific question like, "how should I remove remore the class if it inherits from a parent class?"
[15:51] <dipankar> dfarning, ok.
[16:00] <dfarning> dipankar, please see http://www.catb.org/~esr/faqs/smart-questions.html it is the stand for communication on opensource projects.
[16:11] <ankur__> alsroot,  hi :)
[16:11] <alsroot> ankur__: hi
[16:13] <ankur__> i have worked on adding report bug button in  control panel  . till now we have added a reportbug folder in cpsection defining the icon name , class name and title in __init__ file. and in view.py file i have added these two lines to call apport bug reporting :
[16:13] <ankur__> from subprocess import call
[16:13] <ankur__> call(['ubuntu-bug', '-p','sugar-emulator-0.88'])
[16:14] <ankur__> can i procees with this ?
[16:14] <ankur__> *proceed/procees
[16:15] <alsroot> ankur__: why not, call should work
[16:17] <ankur__> now clicking on reportbug button in CP triggers apport , but it also shows the accept and cancel toolbar , which is not needed. i have tried to make amends but i was not successful. i tried making changes in gui.py files
[16:17]  * alsroot looks
[16:17] <ankur__> but i was able to achieve what i would have wanted . Can you suggest the part of code to target :)
[16:19] <ankur__> what i have tried to make is that clicking on reportbug button just triggers apport but does not show any option menu.It should just keep showing the main view of CP . we tried to add conditions using
[16:19] <ankur__> if option == reportbug : at various places .It seems that placement was not right .
[16:27] <alsroot> ankur__: I think right way would be add do-not-open-cp-frame feature, e.g. if view class wasn't setup, frameless mode will be enabled
[16:28] <alsroot> hmm.. we have only one CLASS in __init__, /me looks
[16:30] <alsroot> ankur__: if "action.py" is present in CP directory, it will be imported and initiated (somehow) instead of trying to import view.py and mmodel.py
[16:31] <alsroot> ankur__: see sugar/src/git/sugar/src/jarabe/gui.py:show_section_view
[16:33] <lfaraone> dipankar: did you figure out how to fix your mailing list problem?
[16:33] <dipankar> lfaraone, yes, thanks
[16:34] <lfaraone> dfarning: Mozillateam told me that I need to contact Mozilla for trademark clarification. While we're at it, should we fix the stylesheets + download manager intergr. extension, so I don't have to re-request permissions if we fix them in the future?
[16:34] <alsroot> ankur__: btw do you really not need component frame? I mean you can place there explanation text about bug reporting and one button to launch ubuntu-bug
[16:35] <dfarning> lfaraone, yes please.
[17:02] <dfarning> dipankar, ping
[17:02] <dipankar> dfarning, here
[17:12] <dfarning> dipankar, just wondering if you have any general sugar development of develoment process questions?
[17:13] <dipankar> dfarning, didn't get you :). development of development
[17:13] <dipankar> ?
[17:14] <dipankar> dfarning, The patch creation is a bit tougher than I thought :P
[17:15] <dipankar> dfarning, how do we add description in patch btw?
[17:15] <dipankar> dfarning, sascha said here: http://bugs.sugarlabs.org/ticket/2289#comment:3
[17:15] <dipankar> * description is missing
[17:16] <dfarning> development _or_ development process questions.
[17:17] <dfarning> dipankar,  to add a discription to a patch you need to include the description in the commit message.
[17:18] <dfarning> dipankar, the normal format for a commit message is one line summary, blank line, paragraph description.
[17:20] <dipankar> dfarning, thanks. on it
[17:21] <dfarning> dipankar, did i explain the difference between and review and an ack?
[17:22] <dipankar> dfarning, I don't think so. ack? I don't remember having any idea of it
[17:25] <dfarning> dipankar, ok the peer review process in sugar, as with most open source projects, is a best practice for writing good code.
[17:26] <dfarning> dipankar, on the other hand, to keep things sane most modules have one or at most two maintainers.  The maintains have the final desions to commit a patch.  So it is really their opinion that you _need_ to get.
[17:27] <dipankar> dfarning, I agree. :) Took those review in healthy sense. Also I didn't know the exact format of a patch. Thanks to sascha now I know that too.
[17:27] <dfarning> dipankar, only maintainers can 'ack' a patch.  see http://wiki.sugarlabs.org/go/Talk:Development_Team/Code_Review
[17:28] <dipankar> dfarning, :). Went through that. manusheel sent the link to me :)
[17:28] <dfarning> dipankar, +1 the list of module maintainers is at http://wiki.sugarlabs.org/go/Development_Team/Release/Modules
[17:30] <dipankar> dfarning, I somewhat feel that they have some control over the patching :)
[17:31] <dipankar> dfarning, after all they will be responsible for the working of the core module
[17:31] <dfarning> dipankar, so reviews are alot about the judgement and trust of the reviewer and the submitter.  If marco, tomeu, simon, or alsroot suggest something it is a good idea to listen.... If i suggest something please feel free to ignore me:)
[17:32] <dfarning> dipankar, +1 only a module maintainer can make the final decision to commit a path to the upstream git repository.
[17:34] <dipankar> dfarning, your opinions also matter.
[17:34] <dipankar> dfarning, btw, I have remade the patch: http://paste.ubuntu.com/489324/
[17:34] <dipankar> I hope sascha accepts it now
[17:36] <dfarning> dipankar, looks good.
[17:36] <dipankar> dfarning, thanks
[17:36] <dipankar> dfarning, its getting past dinner time here, and I haven't had dinner :(
[17:37]  * dipankar is off to dinner
[17:37] <dfarning> ok is you later.
[18:13] <manusheel> kandarpk: Hi Kandarp.
[18:13] <manusheel> kandarpk: Did you receive the steps on testing the code change in jhbuild?
[18:13] <kandarpk> manusheel sir: hello sir
[18:14] <kandarpk> manusheel sir: yes sir.
[18:14] <manusheel> kandarpk: Please check shell.log for finding the syntax error.
[18:15] <kandarpk> manusheel sir: ok
[18:15] <manusheel> kandarpk: ~/.sugar/default/logs/shell.log, sugar shell logs to this file
[18:21] <dfarning> kandarpk, how are you coming? any questions?
[18:34] <manusheel> dfarning: Kandarp will be back in a minute. His Ubuntu 10.10 is hanging badly.
[18:40] <dfarning> kandarpk, are you back?  network trouble?
[18:40] <kandarpk> dfarning: 10.10 doesn't work properly on my system :(
[18:40] <kandarpk> it just hangs
[18:40] <manusheel> kandarpk: Ubuntu 10.10 is under development, it seems.
[18:40] <dfarning> kandarpk, where does it hang?
[18:41] <dfarning> kandarpk, manusheel yep 10.10 will be release on oct 10
[18:41] <kandarpk> dfarning: the windows manager takes around 3-4 seconds to show folders
[18:42] <dfarning> kandarpk, did you just do a fresh install of 10.10
[18:42] <kandarpk> dfarning: yes
[18:45] <dfarning> kandarpk, try going to synaptic and making sure all of the development and testing repos are enabled and then tty to update the system.
[18:45] <dfarning> s/tty/try/
[18:45] <kandarpk> dfarning: sure.
[18:46] <dfarning> kandarpk, when running 10.10 you will want to run 'sudo apt-get update; sudo apt-get upgrade' every day
[18:54] <dfarning> kandarpk, is it still updating?
[18:54] <kandarpk> dfarning: working from Debian now.
[18:55] <dfarning> kandarpk, ahh.  I just waht to check to see if you have any general questions.
[18:55] <kandarpk> dfarning: ok
[18:55] <kandarpk> dfarning: installing jhbuild on Debian
[18:56] <kandarpk> will update 10.10 after that
[18:56] <dfarning> kandarpk, +1
[18:57] <dfarning> manusheel, I was wondering if we should add kandarpk to our daily status discussion?  We might need to reschedule it:)
[19:11] <manusheel> dfarning: Yes. We'll do that sometime. Right now, that would add too much work on Kandarp's side.
[19:11] <manusheel> dfarning: Would like him to focus on development work at this juncture.
[19:13] <dfarning> manusheel, +1
[19:28] <manusheel> kandarpk: Hi Kandarp.
[19:28] <kandarpk> manusheel sir: hi
[19:56] <kandarpk> dfarning, lfaraone : sugar-jhbuild depends on libsqlite3-dev
[19:57] <kandarpk> trying sudo apt-get install libsqlite3-dev gives
[19:57] <kandarpk> Err http://http.us.debian.org unstable/main libsqlite3-0 3.7.0.1-1
[19:57] <kandarpk>   404  Not Found [IP: 149.20.20.135 80]
[19:57] <kandarpk> Err http://http.us.debian.org unstable/main libsqlite3-dev 3.7.0.1-1
[19:57] <kandarpk>   404  Not Found [IP: 149.20.20.135 80]
[19:57] <kandarpk> Failed to fetch http://http.us.debian.org/debian/pool/main/s/sqlite3/libsqlite3-0_3.7.0.1-1_i386.deb  404  Not Found [IP: 149.20.20.135 80]
[19:57] <kandarpk> Failed to fetch http://http.us.debian.org/debian/pool/main/s/sqlite3/libsqlite3-dev_3.7.0.1-1_i386.deb  404  Not Found [IP: 149.20.20.135 80]