IRC logs of #tryton for Monday, 2016-05-16

chat.freenode.net #tryton log beginning Mon May 16 00:00:02 CEST 2016
-!- fwiesing(~fwiesingX@194-208-177-133.tele.net) has joined #tryton01:56
-!- niki(~niki@0x3e2c87a1.mobile.telia.dk) has joined #tryton02:51
-!- smarro(~sebastian@181.16.7.104) has joined #tryton04:44
-!- kstenger1(~karla@r167-56-234-127.dialup.adsl.anteldata.net.uy) has joined #tryton05:05
-!- niki_(~niki@0x3e2c862f.mobile.telia.dk) has joined #tryton06:33
-!- frispete(~frispete@p54A9084D.dip0.t-ipconnect.de) has joined #tryton07:40
-!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton09:20
-!- ccaz(~ccr@ax313-1-82-66-159-99.fbx.proxad.net) has joined #tryton09:26
-!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton09:40
-!- nicoe(~nicoe@2a02:a03f:309a:fe00:ee55:f9ff:fe7b:f7ac) has joined #tryton10:05
-!- smarro(~sebastian@181.16.7.104) has joined #tryton12:53
-!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton13:02
-!- mariomop(~quassel@181.90.94.79) has joined #tryton13:02
-!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton13:54
-!- mariomop(~quassel@181.90.66.160) has joined #tryton14:21
-!- smarro(~sebastian@181.16.7.104) has joined #tryton14:38
-!- lukio(~lukio@186.19.70.16) has joined #tryton15:24
-!- bvillasanti(~bvillasan@190.105.80.94) has joined #tryton16:14
-!- smarro(~sebastian@181.16.7.104) has joined #tryton16:50
-!- JosDzG(~Thunderbi@fixed-188-72-187-188-72-36.iusacell.net) has joined #tryton17:13
-!- pokoli(~pokoli@2001:41d0:1:9acb::1) has joined #tryton17:19
-!- silwol(~silwol@80.66.37.182) has joined #tryton17:49
-!- shrox(~shrox@103.255.36.42) has joined #tryton17:51
-!- lukio(~lukio@88-38-16-190.fibertel.com.ar) has joined #tryton18:25
-!- kstenger(~karla@r186-54-21-185.dialup.adsl.anteldata.net.uy) has joined #tryton18:31
shroxkstenger: Hi! I have a question. Will I be pushing the code that I write for GSoC daily to any repo?18:38
kstengershrox: no, I think you should be using the review, and update it whenever you have changes, so you receive comments back from us. This is the usual flow in Tryton, and I see no reason why it would be different for GSoC18:40
kstengershrox: if a review is accepted, then it will be pushed to the main repo18:40
kstengershrox: so you may actually have to work on different reviews, depending on the tasks you can divide your work in18:41
shroxkstenger: Ah, okay. I was confused because my project I feel is somewhat independent from relatorio/tryton. It will only need to be incorporated with the two after my main project is finished. But I think I know get what you mean.18:43
kstengershrox: actually what you will be working on is just like any patch to any of those repositories, so it makes no difference, since you can upload the reviews as many times as you want, and it is even better because you can get comments back in-line.18:44
kstengershrox: my only doubt is if you should do a daily update.18:45
kstengershrox: I think it's maybe too much, but I'd like other mentors opinion on that18:47
shroxkstenger: Okay. My concern was the repo. I will have a look at relatorio's repository and upload a test review so that I don't have any confusions after the 23rd. Thanks!18:59
kstengershrox: ah, yes, basically your patch should be finally applied for the relatorio repo. So you should work on a copy of it, and upload this review with the right title indicating the repo name in it.19:02
shroxkstenger: Yup.  So I can make another folder in the relatorio repo and work entirely inside it, right? Upload the reviews for the code in that one folder?19:04
kstengershrox: no, don't make another directory, just clone the repository and make your changes in it, then upload with hg review19:04
shroxkstenger: But I think I will be beginning from scratch, in the sense, that I will not be using the existing codebase of relatorio until the towards the end. So the changes that I make will be in a new file that I create.19:06
-!- lukio(~lukio@186.19.70.16) has joined #tryton19:06
kstengershrox: so create the file in the right directory, use 'hg add <your file>' and then you can upload the review. This way it will be easier for you to start doing tests asap. And we all understand what is actually going on19:09
shroxkstenger: What would the right directory be? There is only a templates and tests folder. https://hg.tryton.org/relatorio/file/tip/relatorio19:21
kstengershrox: 'hg clone http://hg.tryton.org/relatorio'  This will create for you a copy of the current development version of relatorio in a directory called relatorio under your current directory19:22
kstengershrox: I meant https19:23
kstengershrox: 'tip' is just the default name mercurial gives to the latest commit19:24
kstengershrox: the name of the changeset you are browsing appears when you use the web browser, it will not appear after you clone19:26
shroxkstenger: Yes. I mean, let's say I'm creating a file sample.py. So where in the relatorio directory would I make it? Would it be in relatorio/relatorio or relatorio/relatorio/newfolder19:26
kstengershrox: inside of your cloned repository, I think it should be in relatorio/templates/ in paralel to opendocument.py and pdf.py19:29
shroxkstenger: Okay. This was my question. Sorry for the confusion and thanks for the answer :)19:30
kstengershrox: no problem, ask whatever you need to19:30
-!- nicoe(~nicoe@2a02:a03f:309a:fe00:ee55:f9ff:fe7b:f7ac) has joined #tryton19:31
-!- bvillasanti(~bvillasan@190.105.80.94) has joined #tryton19:37
-!- nicoe(~nicoe@239.90-247-81.adsl-dyn.isp.belgacom.be) has joined #tryton20:52
-!- perilla(~perilla@corp-190-57-169-210-cue.puntonet.ec) has left #tryton22:09
-!- apostatize(~visavis@unaffiliated/apostatize) has joined #tryton22:32
-!- lukio(~lukio@186.19.70.16) has left #tryton22:43

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!