12:00:14 #startmeeting 12:00:14 Meeting started Fri Jan 9 12:00:14 2015 UTC. The chair is zack. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00:20 sophiejjj: hi! 12:00:21 pfiou, just in time 12:00:23 hi! 12:00:31 matthieucan: that was timely, yes :) 12:00:34 #chairs matthieucan 12:00:36 #chair matthieucan 12:00:36 Current chairs: matthieucan zack 12:00:43 #topic debsources opw - next meeting 12:00:50 i 12:00:51 hi 12:01:06 is next week, same time, good for next meeting? 12:01:11 yes. 12:01:25 yes 12:01:28 #agreed next meeting next Fri, usual time 12:01:35 nice, that was easy! 12:01:40 #topic debsources opw - weekly review 12:01:50 let's go through this week's plans, as usual 12:02:00 1st item was: test coverage ≥ 85% (see #762951) 12:02:04 sophiejjj: status on that? 12:02:14 let me have a look 12:02:37 81% 12:02:51 better than last week! 12:02:55 almost there :) 12:02:58 ;) 12:03:10 sophiejjj: do you want to keep that as a task for next week? 12:03:15 sure. 12:03:20 I will move that. 12:03:27 ok, thanks 12:03:36 done. 12:03:41 next item: show the destination of symbolic links. make the format more of "ls -l" 12:03:46 that is done, right? 12:03:58 yes, it looks good! 12:04:05 yes. 12:04:11 amazing, please archive the item 12:04:24 next item: #761121 allow symlink within same pkg - add test for insecure links 12:04:29 done? 12:04:35 done. 12:04:40 \o/ 12:04:43 please archive 12:04:50 archived. 12:04:54 next! work out basic project structure for copyright.d.n 12:04:59 status? 12:06:03 in discussion, email thread about blueprints, etc 12:06:16 blueprints seems feasible. 12:06:18 for me it's not entirely clear what we'll do according to apps, etc 12:06:34 sophiejjj: any work done on your part that we haven't yet seen in email? 12:06:41 (on this specific item, I mean) 12:06:50 no. 12:07:08 just because of time issues, or is there any other blocker? 12:07:19 will we have a separate git repo for that? 12:07:36 matthieucan: I'll get to that in a minute 12:07:37 mainly time issues, I am writing a survey these days. 12:07:48 sophiejjj: uhm, ok 12:08:00 sophiejjj: but please, can you let us know in advance when you've other time commitment? 12:08:20 zack: yup. sorry. 12:08:39 it's OK, it's just better to know in advance, than discover afterwards :) 12:08:48 sophiejjj: how long do you still need for the survey? 12:09:52 till jan.20. But I can do debsources in the meantime. 12:10:51 ok, if you think it will take more than 1 day/week, please let us know, so that we can adapt OPW aims accordingly 12:10:58 (maybe via email, no need to discuss that during the meeting) 12:11:01 deal? :) 12:11:06 deal. 12:11:09 awesome! 12:11:23 so, I'd like to prioritize a bit the work on copyright.d.n for next week 12:11:36 can you please move the project structure item to next week? 12:11:47 then, I think we should discuss matthieucan's point about where to have the code 12:12:01 moved. 12:12:17 sophiejjj: does the blueprint stuff scares you and/or poses some problem? (if so, I can we can postpone it, while still working on the project structure) 12:12:40 it doesn't I think. 12:13:04 but it poses a different work-style. 12:13:10 so, how about start creating a dedicated page, rooted at APP/copyright, and start implementing there the main features? 12:13:27 I mean, I guess unlike the filling some stubs, it requires a totoal bottom-up of the code. 12:13:38 got it. 12:13:52 like package browsing would be /copyright/path/to/package/ 12:13:59 search /copyright/search/, etc. 12:14:12 it is up to you whether you use a blueprint or not 12:14:17 it would be *better* to do so, I think 12:14:19 this seems fair. Having a plugged blueprint on /copyright will definitely work 12:14:30 matthieucan: thanks, I was about to ask you :) 12:14:36 gotcha. 12:14:41 not having it will work as well, but it will mix both apps 12:14:55 sophiejjj: what do you think would be a minimal feature (or features) that you could implement during next week? 12:15:18 some examples could be: 12:15:25 should we discuss the db structure before? 12:15:32 listing the packages ? 12:15:39 matthieucan: I think we should use the same DB of the current app 12:15:58 matthieucan: a dedicated copyright table could be added later, in the meantime we can parse d/copyright on the flight, no? 12:15:59 zack: yes, but we'll need new tables/columns 12:16:00 like the way the frontpage of debsources? 12:16:09 zack: oh yes, sure 12:16:31 sophiejjj: ok, so that would be an item like "package browsing starting from /copyright/...", please add it to trello 12:16:46 sophiejjj: note, we do *not* want to see copy/paste code there, it should reuse the existing code for package browsing 12:16:55 got it. 12:17:09 hence moving stuff to a separate module, see email thread about that 12:17:10 so I may refactor the code in debsources. 12:17:15 didn't have time to file a bug yet 12:17:30 I've no idea whether the current browsing code can be reused as is or not 12:17:49 I think so, at least what's in models.py 12:17:51 IIRC 12:17:52 I think you two are in the best position to discuss that (via email would be better, I guess) 12:17:59 sure 12:18:14 matthieucan: in the mid term, it would be best to move that out of models.py though, right? 12:18:19 I will look into that, and will consult matthieucan if I have problems. 12:18:21 I mean, strictly speaking navigation != ORM :) 12:18:42 zack: yes, but they are implemented as methods of these objects 12:18:47 which still make sense :) 12:19:03 matthieucan: they are yes, I think they shouldn't :), but that's a different discussion 12:19:26 sophiejjj: I think it should also be doable to do a very basic rendering of machine-parseable debian/copyright file, once reaching a specific package/version 12:19:35 zack: yes, maybe we should have orm.py and models.py separately 12:19:48 sophiejjj: could be as stupid as "just dumping the file content", but only if the file is machine parseable 12:19:58 matthieucan: I think model is of the same semantics as orm. 12:20:00 sophiejjj: because that will give you a change of learning the debian.copyright Python API 12:20:19 zack: regarding the debian.copyright 12:20:32 sophiejjj: yes, but we reached a point where we have too many methods on our classes, and the orm becomes less clear 12:20:43 I'd like to learn more about the debian stuff, like the forthmentioned d.copyright in this OPW. 12:21:04 matthieucan: I got your point. Actually there was a bug about it, IIRC. 12:21:14 sophiejjj: there is, yes 12:21:23 I tried to do that. 12:21:56 and I didn't finish it, IIRC, the code is tangled together and cutting them through is somewhat laborious. 12:22:18 it is a bit, yes 12:22:31 let's see if having to reuse it for /copyright helps in actually having to do that 12:22:40 sophiejjj: you're right, we should probably use inheritance for app-specific classes, this shouldn't be too hard I think 12:23:01 sophiejjj: so, I've added 2 items that revolve around copyright.d.n, can you have a look and see if they make sense to you? 12:23:26 (then we should move to the next items of last week, I think) 12:23:41 yeah. 12:24:04 matthieucan: regarding the Git repo, I think that it makes sense to use the same one (at least for now, but also in the long term I think) 12:24:15 sophiejjj: great 12:24:49 zack: yes, it will be simpler. In that case it might be difficult to separate the apps, but that's not necessarily needed 12:24:58 ok, so let's move to next item 12:25:01 next item is: #761119 - suite-based navigation 12:25:12 there is a patch for sophiejjj, but I haven't had time to review it yet, unfortunately 12:25:20 (new semester starting, I'm a bit busy these days...) 12:25:26 me neither 12:25:35 matthieucan: do you think you can review sophiejjj's patch in the next few days? 12:25:46 zack: sure, before end of week-end 12:25:49 sophiejjj: that patch is only for the first part of the bug report, right? 12:25:52 yes. 12:25:53 matthieucan: awesome!, thanks a lot 12:26:04 I think much about the html should be accordingly modified. 12:26:11 #action matthieucan to review sophiejjj's 1st patch for #761119 12:26:26 sophiejjj: what html? 12:26:31 sophiejjj: please move the item to next week 12:26:53 like, the link to the corresponding /suite/prefix 12:26:56 matthieucan: I think she means the template, for implementing the *2nd* part of the bug 12:27:07 should it be a combo-box, or? etc. 12:27:17 zack: the first part. 12:27:23 oh, sorry then 12:27:32 O 12:27:42 first the user should be able to select the desired suite. 12:27:55 oh I see 12:28:06 second, for the returned result. 12:28:21 a new url_for should be added. 12:28:24 03Mattia Rizzolo 05master c2a458f 06jenkins.debian.net 10bin/ 10(6 files) reproducible: update links after apache change. strip the leading /userContent where possible 12:28:41 I'll live that to you two, do you think we can continue/finish that discussion via email? (I'm a bit short of time ATM) 12:28:50 I'll *leave* (sorry for the typo) 12:28:55 sophiejjj: feel free to modify the html where it's needed 12:28:55 now? 12:28:56 zack: sure 12:29:25 so last item was: #761083 - inject binary package metadata 12:29:32 sophiejjj: any progress on that? 12:29:39 I read the updater.py 12:29:48 the plan was to just *look* around and figure out were changes where needed 12:30:01 sophiejjj: awesome, you scared about it? :-) 12:30:02 so the stage, adding the packages. 12:30:10 and the stage, mapping the suite. 12:30:21 gc maybe, or maybe not. I am not sure. 12:30:29 yes gc as well 12:30:41 I guess the GC part can be left fo the DB 12:30:55 if the binary package entries reference the source package entry, they will automatically disappear 12:30:59 adding the source/mapping/binary should be done in the same sqlalchemy transaction 12:31:00 when the source package entries are removed from the DB 12:31:23 zack: with triggers? 12:31:34 matthieucan: no triggers, just plain referential integrity 12:31:43 (with CASCADE and the like) 12:32:01 we already use that for all plugin data, for instance 12:32:14 oh ok, sure 12:32:41 sophiejjj: in fact, the main part that will need work is: 12:32:53 - retrieving Packages file 12:32:56 - parsing them 12:33:11 got it. 12:33:13 - and session.add() to the tables that already exist the corresponding ORM entries 12:33:34 is there existing binaries files for me to play with? 12:33:39 sophiejjj: *if* you think you can give that a try next week, move the item to the appropriate list, *if not*, let's move it back to backburner 12:34:04 sophiejjj: yes, I can provide you one, with examples on how to parse it (the parser is already available in python-debian) 12:34:11 I think I shall move it to the backburner. 12:34:17 sophiejjj: ok, please do 12:34:35 I will first do the per suite. Since I've started on that. 12:34:36 I'll add a TODO item for me (for the future) to give you a sample Packages file and a parsing example 12:34:47 ok, great 12:34:51 looks like we're done with the weekly review 12:34:56 #topic debsources opw - misc 12:35:10 sophiejjj, matthieucan: anything else before we adjourn the meeting? 12:35:25 everything's fine with me :) 12:35:32 yes. fine with me, too. 12:35:41 wonderful, so... 12:35:43 #endmeeting