Hello Paul, CC'ing James Westby and keeping fullquote for him. Paul Wise [2011-07-07 13:26 +0200]: > I noticed launchpad-work-items-tracker and status.l.o/status.u.c and was > wondering how flexible it is and how closely tied to launchpad it is? > Since Debian doesn't use launchpad we would need the possibility to > replace the data collection and storage. Right now it is able to pull WIs from Launchpad Blueprints (our primary method), Launchpad bug collections (i. e. anything you can express in terms of a search query, like "all bugs on project foo with tag bar), or wiki pages. In principle, it can be taught to pull from other data sources, of course. The transition tracker and Debian bugs would be natural data sources. Since I wrote it, James Westby has refactored the code completely, with some more abstractions, and using python-storm. He can probably explain better than me now which parts need to be changed (I'd be interested in that as well :) ). > I think that work-items-tracker could be useful in Debian too, for > example the release team's release goals or in the DEX project for the > work on merging Ubuntu changes into Debian. Possibly different teams > would want to be able to setup instances too. > > For the release team, I guess the data backend bits would be some flat > files, the Debian bug tracker and release team usertags. > > For DEX I guess Nathan Handler can comment, since he is doing a GSoc > project that will be used to track merges from derivatives. > > Also, I can't find any license or copyright information in the source > code (trunk) but the launchpad page says GPLv3, could you add license > and copyright information to the source too? Indeed. Committed. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Attachment:
signature.asc
Description: Digital signature