| *** mlncn has quit IRC | 00:02 | |
| *** mlncn has joined #npoacct | 00:05 | |
| *** mlncn-agaric has joined #npoacct | 00:07 | |
| *** mlncn has quit IRC | 00:10 | |
| *** mlncn-agaric has quit IRC | 00:11 | |
| *** mlncn-agaric has joined #npoacct | 00:11 | |
| *** benjamin-agaric has joined #npoacct | 00:14 | |
| *** mlncn-agaric has quit IRC | 00:17 | |
| *** benjamin-agaric has quit IRC | 00:22 | |
| *** benjamin-agaric has joined #npoacct | 01:22 | |
| *** garrison has quit IRC | 01:46 | |
| *** benjamin-agaric is now known as mlncn | 02:49 | |
| *** garrison has joined #npoacct | 04:13 | |
| *** mlncn has quit IRC | 05:22 | |
| *** bkuhn is now known as bkuhnIdle | 05:46 | |
| *** garrison has quit IRC | 06:25 | |
| *** tgnit has quit IRC | 15:06 | |
| *** tgnit has joined #npoacct | 15:38 | |
| *** bkuhnIdle is now known as bkuhn | 16:12 | |
| tgnit | bkuhn: greetings! | 16:43 |
|---|---|---|
| bkuhn | Greetings, tgnit ! | 16:44 |
| bkuhn | I just got back from OSCON yesterday mornign! | 16:44 |
| bkuhn | I see I have an email from you, which I admittedly haven't read, but I saw tbm suggested it be moved to the mailing list. | 16:44 |
| bkuhn | Has the discussion now moved there? | 16:44 |
| bkuhn | tgnit: I have to go idle for a bit. I'm still in the same room (my apartment is basically one room) but I'm cooking breakfast for my wife, so I won't be terribly responsive for an hour or two. | 16:47 |
| tgnit | bkuhn: yes, we are discussing there, but it is a status update so i will prefer to discuss with you ! | 16:49 |
| bkuhn | Understood. When are you going offline today? | 16:50 |
| tgnit | bkuhn: you proceed, have a happy time cooking :) | 16:50 |
| tgnit | no | 16:50 |
| tgnit | i am online for next few hours | 16:51 |
| tgnit | bkuhn: after next 3-4 hrs | 16:51 |
| *** tgnit has quit IRC | 17:14 | |
| *** tgnit has joined #npoacct | 17:24 | |
| bkuhn | tgnit: So, first of all, I am impressed at the way you're handling the email thread with John and Martin | 18:33 |
| bkuhn | tgnit: Seriously, you deserve a compliment: your writing on the list reads like a professional Free Software developer's would. I am very impressed. | 18:33 |
| bkuhn | But, your question is a good one: | 18:33 |
| bkuhn | This feature is very complicated. The new point that you all got to yesterday that we need to have the rounding option based on commodity type is likely the right approach. | 18:34 |
| bkuhn | I agree with what you're hinting at: it could easily take you the rest of your GSoC time to try to get this right, and even then, there might not be enough time. | 18:34 |
| bkuhn | So ultimately, we have a decision to make about how your final time is spent. | 18:34 |
| bkuhn | Do you have an opinion on that? | 18:34 |
| tgnit | bkuhn; thanks for the compliment :), i am too much into this feature and whenever try something new, i feel i am really close. | 18:38 |
| bkuhn | tgnit: Some problems can be "addictive" like that. Like gambling: you always feel you're "just about" to win. | 18:38 |
| bkuhn | But, my read on this is that if we keep digging here, we've spent the rest of your GSoC time on it. | 18:39 |
| bkuhn | This doesn't necessarily bother me, but I'd like your input on what you'd like to do: would you rather do that or work on tests? | 18:39 |
| tgnit | bkuhn: you are right, it can take time longer than expected. | 18:39 |
| bkuhn | I don't think it's as close as you think. | 18:39 |
| bkuhn | I suspect you have another few days of time discussing in more detail with John. I suspect when you go and try to implement the per-commodity version of what you've done, John will have a lot of comments that will come back and indicate a redesign. | 18:40 |
| tgnit | bkuhn: i got you, so i think it is better to move on | 18:40 |
| bkuhn | It may take up to a week to understand his comments, etc. | 18:40 |
| bkuhn | tgnit: before you decide that: Note that you will learn a lot if you push this further. | 18:40 |
| bkuhn | So, while you'll learn a good things about test writing and test suites in the last few weeks if you switch tasks completely now. | 18:41 |
| bkuhn | .... you may miss out on what you might learn about more advanced problem-solving in a Free Software community. | 18:41 |
| bkuhn | My decision would be heavily influenced by what skills would likely be most useful to you. | 18:41 |
| tgnit | bkuhn: what is your opinion? | 18:42 |
| bkuhn | I don't have a strong opinion. | 18:42 |
| bkuhn | I worry that if you don't finish this feature, no one else will pick it up. | 18:42 |
| bkuhn | Because, ultimately, tbm and I have various work-arounds we've been using to avoid the rounding problems... | 18:42 |
| bkuhn | ... so it's not urgently needed. | 18:42 |
| bkuhn | So if you abandon that work now, we won't get that feature for possibly years, frankly. | 18:43 |
| bkuhn | However, | 18:43 |
| bkuhn | I'm also annoyed that there isn't a larger test suite for ledger-cli. | 18:43 |
| bkuhn | Thus, I'm very ambivalent. | 18:43 |
| tgnit | then i think i will like to continue with it and finish it irrespective of gsoc. | 18:43 |
| bkuhn | That's why I leave it to you to judge what skills you'd like to develop with your remaining time. | 18:43 |
| bkuhn | tgnit: That definitely changes things: if you're willing to see this feature through AFTER GSoC, then it's *definitely* worth the time for you to spend your time on it. | 18:44 |
| tgnit | bkuhn: is it fine if i write fewer tests than expected? | 18:44 |
| bkuhn | tgnit: but you must consider how your motivation will change: We talk a lot in Free Software about volunteerism, etc., but even those of us, who, like me, believe deeply in volunteering our time to make projects better... we all still admit that sometimes, when you're not being paid, it's tough to get motivated. | 18:45 |
| bkuhn | ... And no one would blame you if you stopped after GSoC ended. | 18:45 |
| bkuhn | So, you should think about that factor of motivation and ability to transition paid work to volunteer work in your assessment of continuing. | 18:45 |
| bkuhn | I've met many people who intended to keep volunteering after their paid time ended (both in GSoC and in other contexts)... rarely does it happen, frankly, even with the best people. | 18:45 |
| bkuhn | So, think that issue over for a few days. | 18:45 |
| tgnit | bkuhn : i understand, also after gsoc i am going to pick a job | 18:46 |
| bkuhn | Right. | 18:46 |
| bkuhn | which of course changes your available time. :) | 18:46 |
| bkuhn | tgnit: As for tests, yes, if you are making real progress on the feature and keep posting to the mailing list and discussing it with johnw and tbm, then I'm ok with you writing fewer tests. | 18:46 |
| bkuhn | But, in the event that you *don't* finish the feature, it's now more important than ever that your work be publicly documented and discussed on the mailing list. | 18:47 |
| bkuhn | We're not going to decide pass/fail based on whether this feature gets finished: I recognize that it's difficult and I will be impressed at this point if you get it merged upstream before the end of GSoC. | 18:47 |
| tgnit | bkuhn: towards the end, i will document more things publicly, meanwhile i comment on code and commits | 18:48 |
| bkuhn | But if you continue with working on the feature and it doesn't complete by "pencils down" time, then you need to have something to show for your work. That material will be your mailing list thread and your own git repository with all your attempts. So you need to have lots of that for me and tbm to make a final review. | 18:48 |
| bkuhn | Great, I think you understand. | 18:48 |
| bkuhn | Give a few more days to work and think, let's talk again on (my) Monday (morning) about this. | 18:49 |
| bkuhn | and see how you're feeling about it then. | 18:49 |
| bkuhn | And make a final decision about the rest of your GSoC at that point. | 18:49 |
| bkuhn | tgnit: does that sound like a good plan to you? | 18:49 |
| tgnit | bkuhn: there are lot of things which ends in error so they are not in the commits, i made sure that whatever i commit compiles | 18:50 |
| tgnit | bkuhn: got it, its good | 18:50 |
| bkuhn | Great, let's chat again Monday, then. | 18:50 |
| tgnit | and errors and learning have taken more time, i am unsure how you will feel about it. so its better i get it reviewed by you regularly. | 18:51 |
| bkuhn | Agreed. I'm sorry I've done less code review than I would have liked of your work. If you want to submit a bunch of URLs of comments/commits that you specifically want my review of on Monday, then please do. | 18:51 |
| tgnit | bkuhn: ok, one good news, i fixed the code coverage problem, the option ledger earlier had is working fine now | 18:52 |
| tgnit | bkuhn: sure, see you around on Monday | 18:53 |
| tgnit | bkuhn: :) | 18:53 |
| *** tgnitidle has joined #npoacct | 19:36 | |
| *** tgnit has quit IRC | 19:39 | |
Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!