[02:21] <lfaraone> btw, i wont be on lter
[04:17] <kandarpk> dfarning: hi
[13:12] <kandarpk> dfarning: good morning.
[13:12] <dfarning> kandarpk, good morning .... we lost you for a while:)
[13:12] <kandarpk> dfarning: fitness problem :(
[13:14] <kandarpk> dfarning: the latest tarball of s-speak-a isn't available at http://download.sugarlabs.org/sources/honey/Speak/
[13:14] <kandarpk> any other place I can look for it ?
[13:14] <dfarning> kandarpk, I recommend that each documenter set up there own local jhbuild and builddoc set up.
[13:15] <kandarpk> dfarning: Ok, that is something which can yield long term benefits
[13:15] <dfarning> kandarpk, did you look on aslo for the development information? it might have a another page listed there.
[13:15] <kandarpk> dfarning: the model is very similar to git.debian.org
[13:15] <bernie> 'morning
[13:16] <kandarpk> bernie: Hi :)
[13:16] <kandarpk> good morning
[13:16] <dfarning> kandarpk, it take me about and hour to prepare a patch:(  But working with the developers here it takes them a couple seconds:)
[13:17] <kandarpk> dfarning: Great.
[13:19] <dfarning> kandarpk, yes the usage of git with the sugar packages is same as with git.debian.org.... That is why we spend all that time learning git.
[13:19] <dfarning> bernie, are you around?
[13:20] <kandarpk> dfarning: I meant the model we are thinking of, for documentation
[13:21] <dfarning> kandarpk, yes when creating the documentation you will be working with the core sure packages and adding docstrings to those packages.
[13:26] <bernie> dfarning: yep
[13:51] <kandarpk> dfarning: do you have anything for me to work on ?
[14:00] <dfarning> kandarpk, sorry my computer stopped beeping at me:(
[14:00] <dipankar> hello dfarning , a very good morning
[14:00] <dfarning> dipankar, good morning.
[14:00] <kandarpk> dfarning: np.
[14:02] <kandarpk> dfarning: just that I am logged into windows now.
[14:02] <dfarning> kandarpk, I guess a high priority would be setting up your local document build system. And figure out how to modify the docstrings and create patches
[14:02] <dfarning> dipankar, good morning
[14:02] <dipankar> dfarning, how are you?
[14:03] <dipankar> at Paraguay?
[14:03] <kandarpk> dfarning: when we push changes, only patches are submitted to git, isn't it ?
[14:04] <dipankar> kandarpk, hi
[14:04] <dipankar> kandarpk, I don't think so
[14:04] <kandarpk> dipankar: Ok.
[14:04] <dipankar> kandarpk, I think we need to submit the whole modified code too.
[14:05] <kandarpk> dipankar: by the way, how are you doing now ?
[14:06] <dfarning> kandarpk, yes.  technically a commit is just a diff(patch)
[14:06] <dipankar> kandarpk, I am doing good. ^^ Here's your answer
[14:06] <dipankar> I was wrong I guess :)
[14:06] <dipankar> dfarning, but we upload all the files. oops, thats the mistake.
[14:07] <bernie> http://www.newartisans.com/2008/04/git-from-the-bottom-up.html
[14:07] <dfarning> dipankar, things are going well.
[14:07] <dipankar> ohk, when we use git push, it sends only the changes up to the repo. That must be it then.
[14:07] <bernie> dipankar, kandarpk: there's a pdf linked in that page. it's a very good reading about how git "thinks"
[14:08] <kandarpk> bernie: thanks
[14:10] <kandarpk> dfarning: users can clone the source, make changes and push it back.
[14:10] <dipankar> bernie, thanks a lot.
[14:10] <dfarning> kandarpk, Yes.
[14:10] <bernie> dipankar: yup. push sends one or more commits (~= patches) to a remote repo... no merges are possible on the remote side, so the stuff you send needs to be based directly on top of what the remote end has.
[14:11] <kandarpk> dfarning: so they only require to know how to test patches they apply
[14:11] <dipankar> bernie, Thanks again. How are you doing btw? How's your project coming along?
[14:12] <dfarning> kandarpk, who are the they in you above sentance.
[14:13] <kandarpk> dfarning: the users who want to add patches
[14:13] <bernie> dipankar: dfarning arrived here a few days ago... the uruguayans arrived a little earlier... we're all working together on completing Dextrose (which is the new name of F11-0.88)
[14:14] <bernie> dipankar: well, admittedly, we've been a little unfocused lately... meeting new people, show them the deployment, discuss strategy... we need to do more technical work next week
[14:15] <dipankar> bernie, I didn't know you and dfarning are meeting :). I am sure you guys can come over these problems easily
[14:16] <dfarning> kandarpk, yes the developer needs to know how to clone a repo(code), modify the code, test the modification, and either push or make a patch.
[14:18] <bernie> dipankar: we're nearing release, so only the hard problems are left :-)
[14:19] <dipankar> bernie, Best of luck with that :)
[14:26] <dipankar> kandarpk, I need your help with debian/rules file
[14:26] <dipankar> kandarpk, my log activity didn't work on 0.84 as you tested.
[14:26] <kandarpk> yeah
[14:27] <dipankar> so now I need to change the debian/rules accordingly. [http://lists.alioth.debian.org/pipermail/debian-olpc-devel/2010-July/002600.html]
[14:27] <dipankar> but it seems the rules file was very different.
[14:28] <dipankar> just a sec I will link the debian/rules
[14:31] <dipankar> kandarpk, here it is: http://git.debian.org/?p=collab-maint/sugar-log-activity.git;a=blob;f=debian/rules;h=ea5e9a66489c8ad5064a7de8fd6fb4fc1dcb6535;hb=HEAD
[14:31] <dipankar> kandarpk, except for line no. 5 there is nowhere else mentioned about DEB_SUGAR_BRANCHES in the file, pretty weird
[14:31] <kandarpk> Oh
[14:32] <dipankar> could just help with that?
[14:32] <dipankar> I am stuck with this portion only
[14:34] <kandarpk> dipankar: trying to see if I can help
[14:34] <dipankar> kandarpk, thanks very much
[14:42] <kandarpk> dipankar: I think after restoring debian/rules to the original state, you need to rename the activity by adding -0.86
[14:42] <kandarpk> in rules and control.in
[14:43] <kandarpk> dipankar: that is sugar-log-activity-0.86
[14:43] <dipankar> ohk
[14:44] <dipankar> kandarpk, but here it mentions something else I guess (I may be wrong though :))
[14:44] <dipankar> If it works in 0.86 and above, for example, restore your debian/rules
[14:44] <dipankar> file to it's original state. Change "DEB_PYTHON_SUGAR_PACKAGES" adding
[14:44] <dipankar> "-0.86" to the end. Change the binary package name in debian/control.in
[14:44] <dipankar> adding "-0.86" to the end.
[14:45] <dipankar> Luke has mentioned to add -0.86 in the DEB_PYTHON_SUGAR_PACKAGES
[14:45] <kandarpk>  DEB_PYTHON_SUGAR_PACKAGES = sugar-log-activity
[14:45] <dipankar> oops
[14:45] <dipankar> ohk :) got it
[14:45] <kandarpk> your rules file says ^^
[14:45] <dipankar> *thats sickness has raptured my attention.
[14:46] <dipankar> sorry to trouble you kandarpk :(
[14:46] <kandarpk> dipankar: I often do that when asking for help.
[14:46] <kandarpk> dipankar: np
[14:48]  * dipankar is taking a 5 min break.
[14:48]  * dipankar is away: Be Right Back
[14:53] <manusheel> kandarpk: Hi Kandarp.
[14:53] <manusheel> Around?
[14:53] <kandarpk> manusheel sir: hello sir
[14:55] <manusheel> kandarpk: How is Speak activity packaging coming along?
[14:56] <kandarpk> manusheel: sir, its latest tarball isn't available.
[14:57] <kandarpk> latest version is 16 and tarball available has version 11 if I remember correctly
[14:57] <manusheel> kandarpk: Ok, that is unfortunate.
[14:58] <kandarpk> manusheel: sir, I was waiting for Luke to know if we can generate the orig tarball ourself
[14:58] <kandarpk> manusheel: but I don't think thats possible
[14:58] <manusheel> kandarpk: Let us send an update on not been able to package Speak activity, and possible suggestions on how we could expedite the generation of tarball.
[14:58] <kandarpk> else he would have told before
[14:59] <manusheel> If not by ourself, then by the Sugar activity team.
[14:59] <kandarpk> ok.
[15:02]  * dipankar is back (gone 00:13:47)
[15:03] <manusheel> Kandarpk: Did you look at the 4 steps suggested by David?
[15:04] <kandarpk> manusheel sir: yes sir, we discussed about it a little while ago
[15:05] <manusheel> kandarpk: Can you try to do that process today?
[15:06] <kandarpk> manusheel sir: I am not very clear with the scheme.
[15:06] <manusheel> kandarpk: What all things are we not clear with?
[15:06] <manusheel> Let us ask David about it.
[15:06] <kandarpk> manusheel sir: can't we just clone jhbuild, make changes and push it back
[15:08] <kandarpk> dfarning: Around ?
[15:08] <manusheel> kandarpk: I am not sure we can do it like this.
[15:09] <kandarpk> manusheel sir: are some permissions required to push into git repo of jhbuild ?
[15:10] <manusheel> kandarpk: I suspect.
[15:11] <kandarpk> manusheel sir: Ok, then we'll need to follow the steps suggested by David.
[15:12] <manusheel> kandarpk: Yes, we should follow the steps.
[15:12] <manusheel> Let us try and see if there are any errors.
[15:12] <manusheel> Or issues.
[15:14] <kandarpk> manusheel sir: I don't have much knowledge of git-format-patch. Rest all is quite clear.
[15:15] <manusheel> kandarpk: I would like you to search and read on it. Let me send you the resource.
[15:18]  * lfaraone waves.
[15:20] <lfaraone> kandarpk: well, you can do the same thing with speak as we did with other activities for which there are no upstream tarballs, use git snapshots.
[15:20] <dipankar> hey lfaraone good morning.
[15:20] <lfaraone> and ask alsroot nicely to make tarballs. :)
[15:21] <kandarpk> lfaraone: better late than never.
[15:22] <dipankar> lfaraone, I finally am through with the checking of log-activity. Its working for 0.86 and 0.88 only. here is the repo : http://git.debian.org/?p=collab-maint/sugar-log-activity.git;a=summary
[15:22] <lfaraone> dipankar: cool.
[15:23]  * alsroot can release Speak tarball, if there is such need
[15:23] <manusheel> alsroot: Please do so.
[15:23] <kandarpk> alsroot: Please release
[15:23] <manusheel> Thank you.
[15:26] <lfaraone> alsroot: that'd be awesome, thanks.
[15:27] <dipankar> lfaraone, I would like you to review that : sugar-log-activity.
[15:27] <lfaraone> dipankar: okay, mark it in the wikipage.
[15:28] <dipankar> lfaraone, I think I have rectified all things.
[15:28] <dipankar> ohk
[15:28] <alsroot> done, http://download.sugarlabs.org/sources/honey/Speak/Speak-16.tar.bz2, it has bundled "toolkit" dependency but better to leave it as-is, toolkit was rewritten in vala and will be accessible later as polyol
[15:29] <manusheel> kandarpk: Please have a look at http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html
[15:29] <kandarpk> alsroot: thatks a lot.
[15:29] <kandarpk> *thanks
[15:30] <alsroot> np
[15:36] <manusheel> kandarpk: Did you get a chance to look at git-format-patch?
[15:37] <manusheel> The link that I had send.
[15:37] <kandarpk> manusheel sir: sir, will do that in 5 min.
[15:40] <manusheel> kandarpk: Sure.
[15:44] <dipankar> lfaraone, done
[15:45] <dipankar> lfaraone, I have changed the wiki page: http://wiki.debian.org/Sugar/tasks
[15:45] <dipankar> *modfied
[15:49] <kandarpk> manusheel: sir, I think I understand what needs to be done
[15:50] <kandarpk> regarding git format-patch
[15:51] <kandarpk> *switching to USR.
[15:57] <lfaraone> dipankar: in  log, you found that it didn't work in 0.84, right?
[15:57] <lfaraone> dipankar: if so, please talk to neeraj about renaming the actiivty to sugar-log-activity-0.86.
[15:57] <dipankar> lfaraone, actually I sent it over to Kandarp for checking.
[15:58] <dipankar> and he reported me that it is not working on 0.84
[15:58] <dipankar> lfaraone, did I do something wrong?
[15:58] <dipankar> I am not getting 'where' to rename activity?
[15:58] <lfaraone> dipankar: well, if an activity does not work in 0.84, the activity shoul d have -0.86 appended. If it didn't work in 0.86 or 0.84, it should have -0.88 appended to the name. for ex, see what neeraj did with write.
[15:59] <dipankar> ohk.
[16:01]  * lfaraone is looking at etoys.
[16:10] <kandarpk> lfaraone: git init isn't creating branch master
[16:11] <lfaraone> kandarpk: what do you mean? "git init" will initialize a git repository with a master branch.
[16:11] <kandarpk> lfaraone: git branch gives nothing
[16:11] <dipankar> lfaraone, I think I have done that step in renaming the package in debian/rules
[16:11] <kandarpk> lfaraone: some package missing ?
[16:12] <lfaraone> kandarpk: because you're on master by default.
[16:12] <kandarpk> lfaraone: how do I list the branches ?
[16:13] <dipankar> lfaraone, here is the debian/rules. line no. 6 http://git.debian.org/?p=collab-maint/sugar-log-activity.git;a=blob;f=debian/rules;h=5151f39fdd41e9f31d82a1c4dff01ec79a90bb21;hb=89893508c370cf5c27a6eb69fecf4bd72920f3e3
[16:14] <kandarpk> bernie: around ?
[16:14] <lfaraone> kandarpk: "git branch", but you won't see anything until you commit.
[16:14] <kandarpk> lfaraone: Ok.
[16:23] <bernie> kandarpk: yup?
[16:23] <bernie> kandarpk: what lfaraone said
[16:23] <bernie> kandarpk: "git branch -a" to see also the remote ones
[16:23] <kandarpk> bernie: thanks
[16:24] <bernie> kandarpk: normally, when you clone a remote repo called foo, you get many branches foo/bar, foo/baz...
[16:24] <bernie> kandarpk: that's the meaning of "origin/master". it's the "master" branch on the "origin" remote repo.
[16:27] <kandarpk> bernie: can we straightaway push changes to git repo of sugar-jhbuild ?
[16:28] <bernie> kandarpk: you first need to replace the remote url in .git/config
[16:28] <bernie> kandarpk: there's a command-line tool "git remote" to edit remotes, but I find it easier to directly edit the config file.
[16:29] <bernie> kandarpk: the remote url you'll find is of rhe git://... kind
[16:29] <bernie> kandarpk: that's the read-only git protocol which can't be used for pushing
[16:29] <bernie> kandarpk: if you go to the repository page on git.sugarlabs.org, you'll find what the correct push url is supposed to be
[16:30] <bernie> kandarpk: you'll see the push url *only* if you are logged in and you happen to be one of the authorized committers.
[16:30] <bernie> kandarpk: what repo is this?
[16:30] <kandarpk> bernie: Ok.
[16:30] <kandarpk> bernie: git://git.sugarlabs.org/sugar-jhbuild/mainline.git
[16:30] <kandarpk> bernie: it contains the source codes for various sugar modules
[16:31] <kandarpk> and more
[16:31] <bernie> kandarpk: then you could ask silbe for access... but normally one does not directly commit to a repository until he/she becomes a maintainer of the project.
[16:31] <bernie> kandarpk: that's a different mindset from cvs and svn...
[16:31] <kandarpk> bernie: I only wanted to confirm this
[16:31] <kandarpk> bernie: that ordinary users don't push their changes
[16:32] <kandarpk> bernie: thanks
[16:35] <bernie> kandarpk: yep
[16:35] <bernie> kandarpk: there's a BUT though...
[16:39] <kandarpk> bernie: ?
[16:39]  * dipankar says good bye to all.
[16:49] <manusheel> kandarpk: Ok, great.
[16:49] <manusheel> What needs to be done?
[16:49] <manusheel> Can you share your approach?
[16:52] <kandarpk> manusheel sir: Sir, creating patches is quite easy
[16:52] <kandarpk> manusheel sir; 1) clone the repo
[16:53] <manusheel> kandarpk: Ok. Did you read about git-format-patch, the link that I had send?
[16:53] <kandarpk> 2) copy master into some new branch
[16:53] <bernie> kandarpk: back
[16:53] <kandarpk> 3) make changes in new branch
[16:53] <kandarpk> 4) git format-patch master
[16:54] <manusheel> kandarpk: Neat.
[16:54] <kandarpk> manusheel sir: it will create a patch of changes b/t master and new
[16:54] <kandarpk> manusheel sir: http://paste.ubuntu.com/468492/
[16:55] <kandarpk> changes in activityservice.py and activity.py
[16:55] <manusheel> Yes, I saw that.
[16:56] <bernie> kandarpk: that's a good workflow
[16:56] <manusheel> kandarpk: So, have we submitted the patch?
[16:56] <kandarpk> bernie: thanks
[16:57] <bernie> kandarpk: you can also _not_ do a separate branch until you find out you need it
[16:57] <kandarpk> manusheel sir: No.
[16:57] <kandarpk> bernie: we need other users to submit changes
[16:57] <bernie> kandarpk: you get a local branch for free when you clone. "origin/master" gets implicitly branched into the local "master" branch
[16:58] <kandarpk> bernie: Ok.
[16:58] <bernie> kandarpk: btw, I mentioned an alternative to push earlier...
[16:58] <bernie> kandarpk: here it is:
[16:58] <bernie> kandarpk: gitorious lets *any* logged in user create clones of any repository
[16:59] <kandarpk> bernie: yes.
[16:59] <bernie> kandarpk: once you've created your own clone (jhbuild-kandarkpk, jhbuild-seeta or jhbuild-ubuntu), you can push to it
[16:59] <bernie> kandarpk: then, you can request merge with mainline (or any other clone)
[16:59] <bernie> kandarpk: that's an interesting workflow promoted by these new distributed forges such as gitorious and github.
[17:00] <bernie> kandarpk: I like more the workflow of sending patches with git-format-patch + git-send-email and get them reviewed on the mailing lists.
[17:00] <bernie> kandarpk: because all these inter-branch merges are likely to go unnoticed by the majority of the community
[17:01] <bernie> kandarpk: and one important factor in open source development is to make everyone aware of what the others are doing so they can learn from each other.
[17:01] <kandarpk> bernie: Nice.
[17:01] <bernie> kandarpk: for the same reason, reviews done in bug trackers are anti-community.
[17:01] <kandarpk> bernie: Ok. Great.
[17:02]  * bernie gets into the shower
[17:02] <bernie> :-)
[17:02] <kandarpk> bernie: thanks a lot.
[17:02] <kandarpk> bernie: still there ?
[17:05] <kandarpk> manusheel sir: the patch doesn't have anything substantial in it.
[17:08] <manusheel> kandarpk: Ok.
[17:08] <manusheel> kanarpk: Can you document this workflow with a sample example?
[17:09] <manusheel> kandarpk: It is important for us to recognize that this workflow works.
[17:11] <kandarpk> manusheel sir: sure.
[17:11] <manusheel> kandarpk: Great. Please share the expected output at every step.
[17:12] <manusheel> kandarpk: Again, prepare the steps, expected output and commands from a perspective of encouraging patch submissions from the community.
[17:13] <manusheel> Try to make it for a user with a basic familiarity with Linux. This strategy will be helpful for us towards getting maximum patch submissions committed.
[17:15] <kandarpk> manusheel sir: Ok.
[17:16] <manusheel> kandarpk: Thanks Kandarp.
[17:16] <kandarpk> manusheel sir: I'll need to include steps for working on sphinx as well ?
[17:17] <kandarpk> that will be required for testing changes locally
[17:17] <manusheel> kandarpk: Yes. Please do. You can take references from the document prepared earlier.
[17:17] <manusheel> That would expedite process.
[17:17] <kandarpk> manusheel sir: One problem.
[17:17] <manusheel> kandarpk: Ok, please go ahead.
[17:18] <kandarpk> manusheel sir: how will users be able to get the rst files prepared by us.
[17:18] <kandarpk> for testing locally they'll need that to create something similar to nline version
[17:19] <kandarpk> *online
[17:20] <kandarpk> but there is an online resource available to see how the docstring will look in HTML format after conversion.
[17:20] <kandarpk> manusheel sir: ^^
[17:20] <manusheel> kandarpk: Ok, interesting question.
[17:21] <kandarpk> manusheel sir: http://www.tele3.cz/jbar/rest/rest.html
[17:22] <kandarpk> manusheel sir: I think the user here would only like to see if his docstring will be correctly converted into HTML or not
[17:22] <kandarpk> creating a complete website look-alike wont be required
[17:22] <manusheel> kandarpk: I don't think users will be able to get the rst files prepared by us. Yes, they'll need to use this tool to preview the correct conversion of their docstrings to HTML.
[17:23] <manusheel> kandarpk: Yes, that is more than good for them and us.
[17:23] <manusheel> They should be able to see their docstrings getting converted to HTML.
[17:26] <manusheel> kandarpk: I think it should be easy for us to see their submissions, and revisions, wherever possible.
[17:32] <kandarpk> manusheel sir: Ok.
[17:32] <kandarpk> manusheel sir: so, we should isolate the user from the process of using sphinx ?
[17:53] <kandarpk> lfaraone: for how long will you be around ?
[17:53] <lfaraone> kandarpk: about 5 minutes.
[17:54] <kandarpk> lfaraone: Oh, not much time left then.
[17:54] <lfaraone> kandarpk: what can I do for you?
[17:55] <kandarpk> lfaraone: Jonas wanted one of us to add README.source to sugar wiki
[17:55] <kandarpk> lfaraone: so I thought if I could send it to you first for review
[17:55] <lfaraone> kandarpk: right, I can do that, since it'll be hard to track down the right version.
[17:55] <lfaraone> kandarpk: sure. I'll reply to you by monday on tha.
[17:57] <kandarpk> lfaraone: do I need to reply on the mailing list ?
[17:57] <lfaraone> kandarpk: well, you might as well post it to the wiki, we can always edit it later.
[17:58] <kandarpk> lfaraone: Ok.
[17:59] <kandarpk> *will be back in 2min.
[18:02] <kandarpk> lfaraone: sugar-emulator is crashing on my system as well
[18:02] <kandarpk> on installing python-gi
[18:02] <lfaraone> kandarpk: cool, thanks.
[18:04] <kandarpk> lfaraone: I am using README.source from core sugar
[18:04] <lfaraone> kandarpk: sure.
[18:10] <lfaraone> kandarpk: by the way, when you finish working on a bug and uplaod a new patch  (like in https://bugs.edge.launchpad.net/ubuntu/+source/sugar-connect-activity/+bug/609249) you should set it back to "confirmed" or "new" from "incomplete" and unassign yourself.
[18:11] <kandarpk> lfaraone: Ok.
[18:14] <kandarpk> lfaraone: reset-upstream-to-v87
[18:14] <kandarpk> what should I replace v87 with something general ?
[18:16] <lfaraone> kandarpk: not sure what you mean, but I have to go.
[18:16] <lfaraone> it's j ust a branch name, so it doesn't matter what you call  it.
[18:17] <kandarpk> lfaraone: I mean, writing something like v.VERSION_NUMBER
[18:17] <lfaraone> sure.
[18:18] <kandarpk> lfaraone: thanks.
[18:19] <manusheel> kandarpk: Yes, the user might not be interested in Sphinx like us.
[18:19] <kandarpk> manusheel sir: Ok.
[18:19] <manusheel> kandarpk: However, we should keep in mind that we should have an option for that too.
[18:19] <manusheel> Never know, who want to indulge in that :-)
[18:20] <kandarpk> manusheel sir: for that all our files should be accessible online.
[18:27] <manusheel> kandarpk; Ok, then let us take that part later.
[18:27] <manusheel> First, let us concentrate on the workflow, where they are not online.
[18:27] <manusheel> However, please add a small section on this part too.
[18:28] <kandarpk> manusheel sir: Fine.
[18:31] <manusheel> kandarpk: Great.
[18:32] <manusheel> So, let us try to generate a sample implementation using the 4 steps.
[18:32] <manusheel> Hope it works out well.
[18:54] <manusheel> kandarpk: Please take screenshots, and copy paste outputs wherever possible.
[18:54] <manusheel> We'll put it at the wiki.
[18:54] <kandarpk> manusheel sir: of the HTML pages ?
[19:00] <manusheel> kandarpk: Output per step.
[19:00] <kandarpk> manusheel sir: Ok.
[19:01] <manusheel> That is we write a command at the terminal, and we get this "...." as the output.
[19:01] <manusheel> kandarpk: Great work.
[19:01] <kandarpk> manusheel sir: as suggested by Jonas, I've added README.sources at :
[19:01] <kandarpk> http://wiki.debian.org/Sugar/README
[19:02] <manusheel> kandarpk: Neat.
[19:03] <manusheel> Yes, can you send an update e-mail to the team about this.
[19:03] <manusheel> That should be very helpful.
[19:03] <manusheel> We should also reply on Debian olpc mailing list about it.
[19:06] <manusheel> kandarp, this is very neat.
[19:07] <manusheel> Do send an e-mail on olpc debian mailing list.
[19:08] <manusheel> kandarpk, neeraj: Did you get a chance to review jigsawpuzzle?
[19:09] <kandarpk> manusheel sir: no sir. Shall I review it now ?
[19:10] <neeraj> *seeing it now
[19:11] <manusheel> kandarpk: after, we complete the sample implementation.
[19:11] <manusheel> neeraj: you can review it now.
[19:11] <neeraj> manusheel sir, doing that
[19:15] <neeraj> manusheel sir, acco to lfaraone review on tasks http://lists.alioth.debian.org/pipermail/debian-olpc-devel/2010-July/002682.html, Ankur has made the changes..
[19:16] <neeraj> manusheel sir, As far as I can see he has made changes correctly. There might be just one redundant line in the last of debian/copyright, o/w all changes seems to be fine..
[19:17] <manusheel> neeraj: ok, great.
[19:18] <neeraj> kandarpk sir, please confirm > acco to luke review on tasks http://lists.alioth.debian.org/pipermail/debian-olpc-devel/2010-July/002682.html, Ankur has made the changes..
[19:19] <kandarpk> neeraj: just 5 min.
[19:20] <neeraj> kandarpk: np.. take ur time
[19:39] <kandarpk> manusheel sir: git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git
[19:39] <kandarpk> isn't getting the source
[19:40] <manusheel> kandarpk: Interesting.
[19:40] <manusheel> What is the error?
[19:41] <kandarpk> manusheel sir: some folders are missing
[19:42] <kandarpk> manusheel sir: till now, I was working on the sugar-jhbuild folder I had used to install sugar
[19:43] <manusheel> kandarpk: Ok.
[19:43] <manusheel> Can you copy paste the logs?
[19:43] <manusheel> kandarpk: We should touch base with alsroot and bernie about it.
[19:44] <kandarpk> manusheel sir:
[19:44] <kandarpk> ls
[19:44] <kandarpk> config	debian	sbuildbot  scrils
[19:44] <kandarpk> config	debian	sbuildbot  scripts  sjhbuild  sugar-jhbuild  sugar.jhbuildrc
[19:44] <kandarpk> pts  sjhbuild  sugar-jhbuild  sugar.jhbuildrc
[19:44]  * alsroot is not using jhbuild, so can't help with it
[19:44] <kandarpk> wait
[19:44] <kandarpk> --------------------------------
[19:45] <kandarpk> ls
[19:45] <kandarpk> config, 	debian,	sbuildbot,  scripts,  sjhbuild,  sugar-jhbuild,  sugar.jhbuildrc.
[19:45] <kandarpk> this is what I got on cloning
[19:47] <kandarpk> manusheel sir: contents of jhbuild-folder I already had
[19:47] <kandarpk> ls
[19:47] <kandarpk> config,	debian,	install,  jhbuild,  sbuildbot,  scripts,  sjhbuild,	source,	sugar-jhbuild,  sugar.jhbuildrc.
[19:48] <manusheel> kandarpk: Ok.
[19:49] <manusheel> alsroot: Thank you for letting us know.
[19:49] <manusheel> Appreciate it.
[19:50] <manusheel> kandarpk: I see.
[19:50] <manusheel> Lot of folders are missing.
[19:50]  * alsroot uses gentoo instead of jhbuild :)
[19:50] <kandarpk> manusheel sir: the size has reduced from 426 MB to 2MB
[19:51] <manusheel> alsroot: Ok :-) Whom can we touch base on jhbuild.
[19:51] <manusheel> kandarpk: That is a massive decrease.
[19:52] <alsroot> manusheel: silbe on #sugar is a jhbuild maint, but looks like he is offline these days
[19:53] <manusheel> alsroot: Kandarp does not get all the folders on cloning jhbuild from the mainline git. It seems some issues. Ok, will touch base with  Sascha Silbe. Thank you for the pointer.
[19:54] <manusheel> kandarpk: Let us write an e-mail to Sascha and Bernie on this issue.
[19:54] <manusheel> They should be able to help here.
[19:54] <manusheel> kandarpk; In the meantime, let us focus on 2 MB clone.
[19:54] <manusheel> Move with the next steps to see the things in action.
[19:56] <kandarpk> manusheel sir: the source is missing
[19:57] <manusheel> kandarpk; Ok.
[19:57] <manusheel> We cannot proceed ahead then.
[19:57] <kandarpk> manusheel sir: there isn't much to do
[19:58] <manusheel> kandarpk: Let us see if Bernie is around, and can help us on this.
[19:58] <manusheel> bernie: Hi Bernie. Around?
[19:58] <kandarpk> manusheel sir: I've run the other step on the jhbuild folder I already had
[19:59] <manusheel> kandarpk: Ok, how did it come along?
[20:00] <kandarpk> manusheel sir: sir, the patch file I generated was using the steps we had discussed
[20:03] <manusheel> kandarpk: Great. That is neat.
[20:03] <manusheel> kandarpk: Can we complete the next 2 steps using that patch?
[20:04] <manusheel> kandarpk: Wish to see the missing gaps in the 4 steps.
[20:05] <kandarpk> manusheel sir: I didn't get what steps are missing ?
[20:05] <kandarpk> manusheel sir: we only need to submit the patch, isn't it ?
[20:08] <manusheel> kandarpk: We are also the reviewers of the patch, and see their conversion to HTML.
[20:08] <manusheel> I.e. docstrings to HTML.
[20:11] <kandarpk> manusheel sir: we'll need to generate HTML using patch file ?
[20:19] <kandarpk> manusheel sir: I'll leave now.
[20:20] <manusheel> kandarpk: Sure.
[20:20] <manusheel> Please take rest.
[20:20] <manusheel> We have a meeting tomorrow.
[20:20] <kandarpk> manusheel sir, neeraj : good night
[20:20] <manusheel> kandarpk: Please send an e-mail To Bernie.
[20:20] <manusheel> And Sascha.
[20:21] <manusheel> "Sascha Silbe" <sascha-ml-ui-sugar-devel@silbe.org>,
[20:21] <kandarpk> manusheel: Ok.
[20:21] <neeraj> kandarpk sir, good night
[20:21] <manusheel> kandarpk: I'll send you his sugarlabs id.
[20:22] <manusheel> Sascha Silbe <silbe@sugarlabs.org>
[20:22] <manusheel> kandarpk: This is the e-mail id for sugarlabs.
[20:23] <kandarpk> manusheel sir: Ok.
[20:25] <manusheel> kandarpk: Great. Please send them an e-mail on jhbuild issue.
[20:25] <manusheel> kandarpk: Good night.
[20:25] <kandarpk> manusheel sir: good nihgt sir
[20:26] <manusheel> kandarpk: See you tomorrow.
[20:26] <kandarpk> manusheel sir: :)
[21:07] <Ian_Daniher> What part of the ubuntu-sugar-remix package from the PPA requires compiz?
[22:05] <lfaraone> Ian_Daniher: I'm not sure. Why do you think it does?
[23:26] <Ian_Daniher> lfaraone: because I installed USR from the PPA on an ubuntu-netbook-remix install and it pulled compiz as a depend.
[23:27] <lfaraone> okay, no idea.