Hi. [I'm not sure I've thought about all this with sufficient care (and surely didn't make enough progress towards hacking... so many mails and meetings accumulating, difficult to hack ;), still...]
Some comments on previous discussions, and sorry for the bad TO+CC headers. I think there may be a need for a quite generic python client lib for bugtrackers, which would have plugins or subclasses fitting different bugtrackers. This would help for instance for the development of tools like bts-link, which will be a client of several bugtrackers (among them, the DBTS of course). Development of such a library shouldn't be too much Debian-centered, IMHO. Still, the DBTS client part may be developped in the frame of something like python-debian... For instance, the bicho [1] project of the nepomuk [2] project have or are developing client libs in Python for bugzilla these very days. So I don't know... maybe after a python-bugtracker-client project would fit better ? ;) OK, I'm just trying and zoom out of Debian a little bit, but I assume we now have the means with distributed bugtrackers and various other technical bits, to develop things wherever they would be lying. Still the question of a best forum to discuss that stays to be resolved, IMHO. Maybe the Helios project [3] could propose such a generic "python-bugtrackers-client-lib" list for discussing general non Debian-related API and stuff ? I'll provide other more focused (and DBTS related) responses later. Hope this helps anyway. Regards, [1] bicho : http://tools.libresoft.es/bicho [2] nepomuk and bugs : http://nepomuk.linbox.org/ [3] helios WP3 : https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web Le mercredi 17 décembre 2008 à 10:58 -0300, Gustavo R. Montesino a écrit : > Em Qua, 2008-12-17 às 13:22 +0100, Bastian Venthur escreveu: > > Hi, > > > > just a quick question. Are the debianbts-python bindings supposed to go > > into an extra package, will we reuse python-debianbts or is it supposed > > to go into python-debian? Depending on the answer we can open or use the > > appropriate mailinglist. > > > I'm open to suggestions there, but I believe it can be integrated on > python-debian. If no one objects, I think the right place for the > technical discussion would be the pkg-python-debian-discuss ml. > > > Anyways to make a start the discussion, here's what debianbts uses as > > datastructure for a single bugreport. It fits the needs of reportbug-ng > > so far, but maybe not others. Feel free to discuss: > > The current bug class of btsutils tries to separate the usertags in a > separete field from the tags. It also has a forwarded field, which kept > the URL the bug was forwarded to (or whatever the maintainer set on > forwarded) and an url field, which I don't remember why I had added, as > it is easy and inexpensive to compute on-the-fly with the bug number... > > > > -- Olivier BERGER <olivier.ber...@it-sudparis.eu> http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org