Hi. Travis Brown <[email protected]> writes:
> One key component of global distributed bug tracking (as opposed to > project distributed but tracking ala DVCSes) is the ability to move bugs > from one system to another. I've been looking into existing but > interchange formats and haven't found anything suitable. The closest > I've seen is discussed here [0], but it isn't fully fleshed out and I'm > adverse to using XML because it provides too many avenues to divergence > between customizations. Have you considered OSLC-CM (Open Services for Lifecycle Collaboration Change Management) specifications [2] ? I think it *is* indeed the most advanced proposed standard for representation of bugs (Change Management resources include bugs). It has already seen quite a lot of proprietary implementations, but also a few free software ones (including some we contributed). It even supports representation as JSON (looking like [4]) even though one might prefer a more generic JSON-LD representation (if that's on the roadmap of OSLC-CM > 2.0). I think it would be *muuuuuch better* to build on top of OSLC-CM than reinventing a // wheel... but maybe it won't suit your needs. WRT distributed bug tracking systems, we've even started adding some OSLC-CM support to SD [3], but the effort is stalled currently. I think I'll add such a pointer into Lars' blog comments to avoid people missing the OSLC-CM specs. Hope this helps. Best regards, > > [0] http://blog.liw.fi/posts/bug-exchange-format/ > [1] http://travisbrown.ca/projects/bug_interchange.txt > [2] http://open-services.net/bin/view/Main/CmSpecificationV2 [3] https://github.com/arroway/SD [4] http://open-services.net/bin/view/Main/OSLCCoreSpecJSONExamples#Resources -- Olivier BERGER http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) _______________________________________________ dist-bugs mailing list [email protected] http://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
