12:13:38 <buxy> #startmeeting
12:13:38 <MeetBot> Meeting started Wed Sep 18 12:13:38 2013 UTC.  The chair is buxy. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:13:38 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:13:40 <mlalic> buxy: No problem
12:13:51 <buxy> #topic review of last week
12:14:49 <buxy> mlalic: so how did the last week go?
12:15:48 <mlalic> Very nice I'd say. All stories are complete, all side tasks which popped up in the mean time too. The only part that's not done is forbidding accounts with an associated @debian.org email to log in with a PTS-specific password
12:16:01 <mlalic> For that I first have to factor out the accounts app
12:17:10 <mlalic> Simply writing that hook is negligible amount of work.
12:18:03 <buxy> you mean that's the only part of "login via sso.debian.org" that's not finished?
12:18:23 <mlalic> Yes
12:18:36 <buxy> great!
12:19:18 <mlalic> Login, automatic account creation, pulling basic info from LDAP, all done...
12:19:45 <buxy> did you test it with a local instance of DACS?
12:21:05 <mlalic> No, only the automatic unit tests.
12:21:36 <buxy> BTW, the meeting must be over at 15:30, because I have another meeting around that time.
12:21:36 <nthykier> Is there any trick to logging into pts.debian.net via the debian SSO?  (E.g. do you have to register first?)
12:22:00 <buxy> nthykier: nope, that's the "automatic account creation" he was referring to
12:22:03 <mlalic> nthykier: The feature isn't deployed it, as it was developed during the last iteration
12:22:09 <nthykier> ah
12:23:45 <buxy> mlalic: do we now use the system wide libraries on pts.debian.net?
12:23:52 <mlalic> Yup
12:24:27 <buxy> good, the other action items from last week should be done if I recall corre
12:24:37 <buxy> correctly from the pushes I saw
12:25:02 <mlalic> Yes, they are
12:25:30 <mlalic> Plus the change to require confirmation from users that a team owner adds to the team before they can receive team-related email
12:26:09 <buxy> right
12:26:31 <buxy> mlalic: themill posted this this morning, I haven't looked into it. http://paste.debian.net/plain/42330
12:27:08 <buxy> I'm not even sure if the first is a bug or not.
12:27:31 <buxy> the second point is more an idea of improvement (that probably also affects the current PTS)
12:28:49 <mlalic> buxy: The first one isn't on our side, really
12:29:45 <mlalic> The excuses are simply pulled from ftp-master and displayed in the panel
12:29:58 <buxy> ah the bug is tagged pending, that's why it's not listed
12:30:06 <buxy> so it's not a bug really
12:31:46 <buxy> #topic planning of the remaining days
12:32:08 <buxy> mlalic: so what do you expect to do in the next few days?
12:32:43 <mlalic> Firstly, completely extract the accounts email app (which includes fixing any email fields to reference a common model)
12:33:57 <mlalic> After this, the two high priority cards in the backlog: single package name model and south should be doable too
12:34:46 <buxy> mlalic: do you think you can handle the mass renaming if we pick a final name today?
12:36:20 <mlalic> Hmm, I really am not sure on that one. It's not just code that is affected, but comments, documentation too...
12:39:09 <mlalic> I can make my best effort on it, but even if it's not done by the weekend, I wouldn't mind doing it sometime next week, no matter that GSoC will be over.
12:40:33 <buxy> ok, that would be cool
12:42:28 <buxy> we're going for a "lightweight change", it's the "Distribution Package Tracker" for a start, but the "package" is only in the documentation
12:43:41 <mlalic> So what should the top-level python package name be then? dt?
12:43:44 <buxy> i.e. the package name will be "distro-tracker", the service URL will be tracker.debian.org, and the real name will be "<Vendor> Package Tracker"
12:44:55 <buxy> that's the hard question, zack was advocating for "debtracker", it's okay-ish but I'd prefer if we kept it to a 3 letter acronym because it's used everywhere even as prefix of settings, etc.
12:45:55 <mlalic> Wait, so the real name doesn't reference "distribution"? From what you first said, I thought it'd be "<Vendor> Distribution Tracker"...
12:46:51 <buxy> either "dmt" for "Distribution M{eta,ulti} Tracker" or "dwt" for Distribution Wide Tracker
12:47:00 <buxy> yeah, consistency is hard :)
12:47:23 <buxy> right, distribution == vendor in some ways
12:47:33 <mlalic> Right, right, got it
12:48:06 <mlalic> As for the acronym, Meta kind of looks best out of those options to me.
12:50:59 <buxy> yeah, and it can also be "Mega" :-)
12:52:50 <mlalic> Anyway, I'll check with you once more before I do the rename then :)
12:53:33 <buxy> By hardcoding "Package" only in the real name we use a name that's consistent with the current service and that correctly refers to the main purpose of the service right now. In the future that name can still be used to refer to the part of "distro-tracker" that mainly deals with packages subscriptions while the rest can use something else.
12:55:43 <buxy> mlalic: I have updated the user story with the outcome of this discussion for now
12:56:21 <buxy> dmt.* DMT_* for the python code
12:56:42 <mlalic> The reasoning seems sound.
12:56:43 <mlalic> Got it
12:58:29 <buxy> I think "dmt" is free on pypi.python.org
13:01:05 <buxy> mlalic: if you want to save a bit of time and skip the deployment until you're over with the remaining changes, I'm ok with it, but it it doesn't take long, feel free to do it anyway
13:02:54 <mlalic> buxy: Probably the trickiest part is the sso integration... What was the final decision on whether we can do it from pts.debian.net?
13:03:59 <buxy> there was no final decision
13:04:09 <buxy> zobel: ^
13:04:34 <buxy> is the restriction on the DACS side or on the browser side?
13:08:12 <buxy> mlalic: I must also check with DSA (probably file an RT ticket) to get tracker.debian.org setup
13:10:21 <buxy> I uploaded the python-django-jsonfield backport last week, so it should hit wheezy-backports soon
13:11:46 <buxy> #topic misc questions
13:11:49 <mlalic> I've subscribed to the package on pts.d.n so I should see it :)
13:12:58 <buxy> mlalic: any other question? feel free to interact with zobel directly to know what it involves to have sso.debian.org work with pts.debian.net
13:13:23 <mlalic> The only thing I've got for now is about the name of the two apps that are going to come out of accounts
13:13:23 <buxy> zobel@debian.org if he doesn't reply here
13:13:32 <mlalic> I was thinking accounts and profiles?
13:13:41 <mlalic> accounts being the generic one, obviously
13:14:02 <buxy> mlalic: what about putting the accounts next to pts^Wdmt
13:15:03 <mlalic> And then DMT specific functionality stay in dmt.accounts?
13:15:38 <buxy> django_email_accounts ?
13:16:09 <buxy> + dmt.accounts would be ok I think, yes
13:16:52 <mlalic> This sounds good to me too
13:22:03 <buxy> ok, then I think we're set
13:22:19 <buxy> the final run! :)
13:22:32 <mlalic> Yes :)
13:23:28 <buxy> At least I'm quite confident that this GSOC project will be much more successful than the last one I mentored: https://wiki.debian.org/DWTT
13:24:12 <mlalic> Hehe, I'm glad to hear that :)
13:24:39 <buxy> and now we will have the possibility to implement something similar in the generic package tracker
13:24:44 <buxy> Ok I must go.
13:24:49 <buxy> #endmeeting