Re: Moving udd to django

2011-12-13 Thread James Westby
On Tue, 13 Dec 2011 09:11:36 +0100, Vincent Ladeuil vila+...@canonical.com wrote: 3. It would also allow for starting to move udd to an SOA, or at least make it easier. Not a concern for udd so far. Actually I'd like to turn add_import_jobs in to a separate service, as it

Re: Moving udd to django

2011-12-13 Thread Martin Pool
I think switching from batch html, handcoded sql and ssh access to higher-level alternatives would be well worth while and Django seems like a good choice. +1 from me, and also on the specific incremental changes. I agree with James, and disagree with Vincent, about bringing these changes in to

Re: Using lp:udd beyond its original purpose

2011-12-13 Thread Martin Pool
There are two big changes that aren't necessary for us, but would help a lot:  1. Decouple lp:udd from the package-import.canonical.com production deployment  2. Split the package scanning and the branch importing parts of lp:udd into separate projects That sounds good to me, especially #1.