-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.01.2013 01:14, schrieb W. Trevor King: > On Fri, Jan 18, 2013 at 01:02:01AM +0100, Gerhard Killesreiter > wrote: >> Has the possibily to create a bridge between BE and other bug >> trackers been considered? I am thinking of redmine, mantis, >> github, ... >> >> Ie, I could download and commit the bugs for my project using BE, >> go offline, work, and sync everything when I have a connection >> again? >> >> Feasible or crazy? > > You might want to look at Niall's BEXML [1], although I think he's > been busy on other things for the past few months.
It seems to only do pull in its current state. I would want to have push too. > As far as support in the BE trunk, the difficulty will probably be > in mapping abstractions between the various external trackers and > BE's internal view of what constitutes a bug. I agree, I notice for exammple that "be show --xml" does not show bug history for status changes. How extensible is BE in this regard? Could I for example rename the severity tag-names? or status tag names? > If you're only interested in having a private offline store of an > online bugtracker, your BE-side representation is not really > important, and it shouldn't be too difficult to do. If you want > something that you could commit to your repository as more > BE-native, it will probably be more difficult. more difficult but also more worthwhile. In the other case I could simply save html dumps. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlD4mHsACgkQfg6TFvELooQOdQCgvoBUFBDXyXlFyneiC9Vis/Ir kG0AnA5ehROKtDGQTc1cvA21moP0eqSe =6txV -----END PGP SIGNATURE----- _______________________________________________ Be-devel mailing list Be-devel@bugseverywhere.org http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
