12:09:54 #startmeeting 12:09:54 Meeting started Mon Dec 29 12:09:54 2014 UTC. The chair is zack. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:09:54 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:10:03 #topic debsources - next OPW meeting 12:10:12 sophiejjj: next meeting this Friday, usual time, is good for you? 12:10:22 yes. 12:10:31 #agreed next meeting Fri, Jan 02, usual time 12:10:34 great! 12:10:38 that was easy :) 12:10:44 #topic debsources - weekly review 12:10:56 let's start from the first item 12:11:03 test coverage >= 85% 12:11:11 what's the status there? 12:11:20 no progress yet. 12:11:38 well, we did integrate one patch increasing test coverage 12:11:40 that's progress! 12:11:51 but we're still far from 85%, right? 12:12:00 yes. 12:12:09 ok, let's move the item to next week, then? 12:12:17 far from, guess about 80. 12:12:36 yeah. I am ok with that. 12:12:46 great, please move the item --- i've created a list for next week 12:13:04 done 12:13:20 do you need help with this item? AFAICT you got how it works and already made progress 12:13:29 but if there is anything blocking you, please let me knwo 12:13:34 sure. 12:13:42 ok, next item was #761121 12:13:45 I just think it's kinda delicate a thing. 12:13:55 (symlink within same package) 12:14:00 previous bugs, I have an idea, it's mainly about fixing a thing. 12:14:23 for test coverage, I have to construct the base components. 12:14:43 i.e., in the patch submitted, I have to construct a Flask instance first. 12:14:52 yes 12:14:59 not very beautiful code I think, (or to say, ugly), but I have no other idea. 12:15:03 but that is something that will vary on a case by case basis 12:15:15 I mean, different non-tested lines, will require different "hacks" 12:15:25 yes. some self.app.get() test needs little modification. 12:15:50 ok, just keep the patches coming, we'll decide on a case by case basis 12:15:59 en. 12:16:13 let's move to the symlink issue 12:16:20 for the symlink 12:16:22 I understand the patch is ready, but the test is missing, right? 12:16:24 I have a rough idea. 12:16:27 no. 12:16:51 I am in the progress of make flask show the link destination. 12:16:59 ah, that's great, but wait 12:17:17 wait? 12:17:18 i'm talking about #761121 allow symlink within same pkg 12:17:27 yes. I am referring to that. 12:17:35 are you saying the "lang" bug? 12:17:38 well, but showing the symlink destination is a different feature 12:17:44 ok. 12:17:47 no, I'm talking about the bug above 12:17:53 you sent us a patch for that, but it has not been merged yet 12:17:54 I will then make it a separate patch. 12:18:01 yes. 12:18:10 ok, then please send over the final version of the symlink patch 12:18:23 showing the destination of a symlink in the ls-l output should be a separate commit 12:18:33 sure. (I will make up the test after the meeting) 12:18:38 ok 12:18:41 regarding the test 12:18:57 I think *I* should change the testdata, because it is in a separate git repo, and kinda complicated 12:19:10 nods. 12:19:18 so, if that is OK with you, I will include in the testdata the make file which shows the issue, and let you know when it is done 12:19:29 that's cool! 12:19:47 ok, please move the symlink item to next week, I'll add a item for me to do change the test data 12:20:00 done. 12:20:31 ok 12:20:45 would you like to add a separate card for showing the destination of symlinks in ls -l output? 12:20:53 (if you plan to work on that this week, it should be a separate item) 12:21:11 * sophiejjj goes to add the card. 12:21:55 done. 12:22:26 ok 12:22:41 given that we need to change the test data also for testing the language override bug 12:22:56 I've added an item for me to include also that package in the test data, it is easier to change the test data only once 12:23:06 yes. 12:23:18 so, let's move to that bug: #761861 override detected language type 12:23:21 what's the status there? 12:23:35 the testdata is missing. 12:23:43 ok, so let's proceed as above, that is: 12:23:54 please send us the final version of the patch, without the test 12:24:00 when the testdata is ready, we will add the test 12:24:05 but in the meantime, let's integrate the fix 12:24:13 sure. 12:24:24 but please test it by hand one last time before sending it to us ;-) 12:24:34 got it. 12:24:39 can you move the card to this week? 12:24:52 done. 12:24:56 great 12:25:01 so the last one is "make test" 12:25:06 and I think it is now blocked on me 12:25:14 I'll check the backtrace you sent me 12:25:41 (which is a ready a TODO of mine under "Infrastructure") 12:26:00 I am not quite familiar with psql 12:26:12 so kinda stuck today and plus the high latency... 12:26:18 that's OK, I just didn't know that 12:26:29 if you're unfamiliar with psql commands, it's better for me to debug the issue 12:26:39 you can make more useful use of your time by developing on your machine in the meantime 12:26:57 that's cool. 12:27:22 more generally, if you end up working on stuff you don't like, do not hesitate to let me know, we can decide together how to better spend your time 12:27:43 thanks! 12:27:48 so, weekly review on stuff I had to do: 12:27:57 - the upgrade of sor to testing is now done 12:28:17 - the DB issue has been debugged (but has now reemerged and is now on my TODO for this week) 12:28:29 - I've sent you a draft specification of copyright.d.n 12:28:37 yes. 12:28:45 I think that was all on my part 12:28:59 what was *all* on your part? 12:29:23 I mean, the above was the stuff I planned to do since last time we had a meeting 12:29:58 would you like to pick some other item from backburner for this week? 12:30:26 let me have a look 12:30:31 I would love if you could start looking into copyright.d.n 12:30:41 so feel free to propose an action related to that, which is small and doable this week 12:32:04 setup the basic app strucuture? 12:32:29 sophiejjj: sounds good to me 12:32:56 should it be a managed in a separate git repo? 12:33:02 ah, good question 12:33:07 cuz it's quite volatile ? 12:33:33 it is, but I suspect we will have to refactor stuff in Debsources, so it's probably better to use the same repository 12:33:44 for instance, we really want to reuse all the navigation/search part 12:34:02 using different repositories will make things more difficult, for no good reason IMO 12:34:05 yes. just in debsouces, git ignore the copyright.d.n stuff. 12:34:18 oh. no 12:34:29 that will make things complicated if something in debs need changed. 12:34:59 just develop it in the same Git repository, using the structure recommended by Flask blueprints 12:35:06 got it. 12:35:09 (which I *think* will force you to use a separate sub-directory) 12:35:25 matthieu will be able to help with that, I think, so feel free to ping him via email if you get stuck 12:35:32 sure. 12:35:36 please add a card for this 12:36:14 done. 12:36:30 oh, and I think you should also blog about your progress :) 12:36:38 it's ~2 weeks since the last time, and OPW kinda requires that 12:36:59 for at least a 2week frequency? 12:37:14 yep 12:37:20 got it. 12:37:32 #topic debsources - misc 12:37:38 I think we're good for this week plan 12:37:43 anything else you'd like to discuss? 12:37:57 currently not. 12:38:08 are you still in holiday? 12:38:14 kind of 12:38:29 last day in Italy, I'll go back to Paris tomorrow 12:38:38 you italian? 12:38:44 but I've already started to work on my backlog 12:38:53 yep (dual italian/french actually) 12:39:10 how's the weather in it? 12:39:13 Last I checked Bologna was entirely on Italian ground. 12:39:29 wait a sec, let's move to chit-chat after ... 12:39:29 I was in beijing last week, freaking cold..... 12:39:30 #endmeeting