12:00:39 #startmeeting 12:00:39 Meeting started Fri Jan 30 12:00:39 2015 UTC. The chair is matthieucan. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00:42 lol. 12:00:53 #topic debsources OPW - next meeting 12:00:59 agreed for next week? 12:01:03 en. 12:01:10 I think zack will be here 12:01:42 zack is FOSDEM now? 12:01:42 #agreed next meeting next Friday, usual time 12:01:48 yes 12:02:23 anything else before the weekly review? 12:02:34 nothing. ;) 12:02:39 great 12:02:50 #topic debsources OPW - weekly review 12:03:02 blog post 12:03:07 it's done 12:03:14 you can move it :) 12:03:29 done. 12:03:34 cool 12:03:45 suite info on /foo's 12:03:50 is this merged and deployed? 12:03:57 I think yes. 12:04:11 perfect :) 12:04:37 I will archive it. 12:04:48 done. 12:04:50 thanks 12:04:53 anything new with test coverage? what's the current status? 12:05:01 nothing new. 12:05:07 around 81% IIRC. 12:05:27 ok, postponed to next week? or backburner? 12:05:41 backburner, since the restructure? 12:05:58 I've moved it. 12:06:01 agreed, there is a lot to do with c.d.n ! 12:06:16 shall we create a list for the next week? 12:06:25 definitely 12:06:41 are you doing it already or should I create it? 12:06:51 I am trying to do that,,, 12:06:56 or you do it, thanks. 12:07:44 cool, seems to work fine :) 12:08:01 haha. cool. hello. 12:08:12 so let's move on to c.d.n 12:08:15 yup. 12:08:18 I've some questions. 12:08:25 was I clear enough in the email thread from yesterday? 12:08:27 yes, sure 12:08:40 * sophiejjj still is not sure about that. 12:09:15 what do you mean by "I propose to have 2 apps"? 12:09:27 is the app the "Flask app" ? 12:09:47 by "app" I mean a classic Flask app structure, with views/templates/static files/etc 12:10:00 aha. 12:10:01 2 apps = debsources + copyright 12:10:13 and not a third one, because we only need something to plug the blueprints 12:10:16 I was saying, one app with two blueprints. 12:10:33 app=blueprint in my mind, actually 12:10:41 I remember you once said, one app with two blueprints, one app with one blueprint(c.d.n) 12:10:42 ok, sorry for the misunderstanding 12:10:53 hm 12:11:01 I see 12:11:04 ok. so shall we make it clear, app = flask_app, and blueprint is just blueprint? 12:11:16 it was about copyright.debian.net, and s.d.n/copyright 12:11:23 yes 12:11:40 it depends if we want the same on c.d.n and s.d.n/copyright 12:11:48 IIRC, there was no consensus about that 12:12:08 since you are saying it, I am confused about s.d.n/copyright 12:12:25 It doesn't need the browsing functionality I think. 12:12:41 it would be the copyright blueprint, integrated to the current debsources infra 12:13:02 yes, but it would need the links to the browsing in the interface 12:13:15 buxy: before i forget: thanks from me too for merging pabs reproducible patches! also the layout looks fine now in wheezy konqueror so i think i will replace the PTS links from jenkins+piuparts to point to the new tracker soon. IOW: if i havent done so by next tuesday, feel free to remind me :-) (and sorry to shout this in the meeting! i'm glad you have them here! /me travels thats why...) 12:13:26 en. that's a must. but I am wondering what functionality should the "copyright blueprint" support. 12:14:23 we're definitely not clear about what we want with "copyright" w.r.t. what debsources does 12:14:28 what we can do in the meantime 12:14:56 matthieucan: but if "copyright" doesn't need browsing, then we *don't need" the re-structure. 12:15:07 is implement e.g. the debian/copyright file dump, because this won't be lost work, whatever we choose for the browsing/searching functionalities and friends 12:15:26 there is still a bit of restructure 12:15:27 matthieucan: yes. but a problem is, what about the html/css stuff. 12:15:34 for that for instance 12:15:45 this should be moved to something like a library 12:16:07 ennn. 12:16:08 "something like", because they are not classical importable "functions", but rather a collection of templates 12:17:20 matthieucan: well I think, if I remember correctly, "dumping" is already done, the "dumping" we are referring to is more about rendering. 12:17:40 which is more related with the html/css, and the web logic, instead of the library thing. 12:18:15 by dumping, are we talking about the third card in the trello list of this past week? 12:18:31 yes. 12:18:49 where has this been done? 12:18:51 like source file rendering, but with no highlight.js. 12:18:57 oh I see 12:19:17 just showing the content, so it's more of a web stuff. not the lib. 12:19:40 zack said there is a parsable for the copyright file already. 12:20:02 matthieucan: do you think a "c.d.n" really important? 12:20:14 isn't "s.d.n/copyright" enought? 12:20:23 s/enought/enough/ 12:20:30 I don't know that, this is zack's idea and initiative 12:20:31 but 12:20:34 what we could do 12:20:56 yes. we could do. 12:21:24 and I think "restructruing" is just a labor work, since we already have the code, so just a matter of time. 12:21:29 is to implement the copyright related features in a module, integrate all of this in debsources, without blueprints, and create a new flask app to have another, lighter, interface for s.d.n 12:22:16 this would not be too complicated, wouldn't need too much refactoring, but is not the most beautiful solution when it comes to software patterns 12:22:28 yes. 12:22:35 I think we should (re)begin a mail thread with zack about that 12:22:55 I think it all depends on what "c.d.n" will be like. 12:23:16 if it's what zack described in the specification, I think it's worth doing. 12:23:25 I imagined it as the subset of features present in debsources and related only to copyright 12:24:00 en. I am just scared about the "browsing/searching" 12:24:07 since debsources is mostly about that. 12:24:22 and with the "browsing/searching", c.d.n is like a *copy* of s.d.n 12:25:04 we may delegate the browsing/searching to debsources, a bit like codesearch.debian.net delegates the "viewing" part to debsources 12:25:15 haha. 12:25:40 that's what "s.d.n" behaves, a link will be added in the packge page, delegating to "copyright" 12:25:57 and the other way around: debsources delegates code pattern search to codesearch.debian.net 12:26:06 en. 12:26:26 matthieucan: so my point is, "s.d.n" and "c.d.n" has too much funcionality overlapped. 12:26:29 this pattern is another solution we'd have to discuss more deeply if we go for it 12:26:37 for sure 12:27:11 and about the "delegation" you just mentioned. 12:27:31 so when you arrive at "c.d.n", what will happen? 12:28:56 matthieucan: there? 12:29:39 this is discussable, but one might search for a package, seeing the results on s.d.n/search?option=copyright, so debsources is aware of that and creates links to redirect the user to s.d.n in the results list 12:30:00 this is not that cool, seen like that 12:30:15 hm 12:30:24 en. that's one solution. 12:30:55 what we should do is: 12:31:16 create two lists: features of c.d.n, features of s.d.n/copyright 12:31:25 see what exactly overlaps 12:31:30 en. 12:31:53 well. zack will have more words to say on that ? ;) 12:32:43 ok, what about adding a card in trello for that week: make a sum-up of the options we have, of the features we want in both apps/blueprints/whatever, and discuss this with zack via email? 12:32:58 ok. I will add that. 12:33:11 I definitely need a clear one-screen picture of this :) 12:33:14 great! 12:33:57 done. 12:34:20 cool 12:34:40 so, did you actually write code related to copyright yet? 12:35:02 I wrote, but gave up quickly though. 12:35:21 and then I sent you the emails. 12:35:30 ok 12:35:36 do you use a distant git repo? 12:35:47 aha. 12:35:58 I will setup one on bitbucket, is that OK? 12:36:06 because we'll need a branch access to test your code, since email-patches won't scale in case of a big refactoring with many patches 12:36:09 bitbucket is perfect 12:36:27 hg is more perfece. ;). 12:36:44 hahaha, try to convince zack :D 12:37:10 anything else related to copyright? 12:37:36 I've some confustion about the details of re-structure. 12:37:55 but I think I maybe write it in email? 12:38:28 yes, a sum-up of the situation will help us a lot I think (at least me :/) 12:38:49 ;) 12:38:58 alright 12:39:02 what about reading/learning? 12:39:08 what? 12:39:11 did you play with debian-python? 12:39:15 the trello card 12:39:24 haha. 12:39:25 python-debian* 12:39:30 zack never asked me that list. 12:40:07 it's a parallel thing if I'm not wrong, not a deliverable :) 12:40:24 keep it in mind, it will be useful for c.d.n 12:40:29 yep. 12:40:39 nothing complicated, just using library functions related to debian packages 12:40:54 let's let that card there 12:41:07 moved. 12:41:21 oh, great 12:41:24 I'd like to move the copyright cards from that week 12:41:43 which one? 12:41:48 maybe create a category for copyright, so we keep the cards for when we'll have solved our problems 12:42:01 good idea! 12:42:23 I just renamed. 12:42:49 well done 12:42:58 I am always curious. 12:43:05 about? 12:43:19 so in deployment, we use apache+wsgi+python? right? 12:43:33 we replaced wsgi with fcgi 12:43:36 but yes 12:44:00 fastcgi is compatible with wsgi specificaiton? ( I am not familiar with that) 12:44:37 no, we have both configurations in debsources/etc 12:45:13 if you want to know more about deployment, you can read the etc files, or check my docker conf for debsources: https://github.com/matthieucan/Dockerfiles/tree/master/debsources 12:45:31 aha. from my place, the speed is rather quick. Is the server powering debsources super cool or just python can handle that? 12:46:20 what speed do you mean? if it's about searching for instance, the postgresql indexes do the trick 12:46:29 but the server and python are super cool indeed ;) 12:46:40 aha. indexes. that makes sense. 12:46:54 models.py if you're curious about that 12:47:03 cuz we don't cache the result, we visit the db upon request. 12:47:12 so I was concerned about the performance. 12:47:37 we talked about using varnish once, I don't know what happened since then 12:48:01 the browsering-experience is quite good now. 12:48:13 any statistics on IP/PV ? 12:48:30 pv? 12:48:57 page viewed per day. 12:49:06 and ip per day. 12:49:28 we use analog for the http stats, but they are not public. Ping zack to know more about that :) 12:50:02 lol. 12:50:11 did we end the bot? 12:50:27 #topic - debsources OPW - misc 12:50:32 anything else? 12:50:45 nothing atm. 12:50:57 alright 12:51:00 #endmeeting