We’ve been working on modeling bug reports properties for quite a long time, but never managed to stabilize an ontology specification. Better late than never, here’s our first proposed draft and our request for comments :
More details in the helios project’s blog :
I’ve been working on implementing a (my first) plugin for Mantis to provide OAuth support in Mantis.
I now have a first 0.5 version that may be tested. More details here.
Nest step will be to try and use it for the OSLC-CM REST server add-on for Mantis, to allow clients to connect to the REST API using OAuth Access Tokens.
The Helios project is gradually going more open, as we start releasing and committing in the open into a SF.net project (heliosplatform).
Among the tools offered by SF.net we will use a blog (wordpress), the wiki (mediawiki) and the SVN, for a start.
The project’s SVN repo will be populated with all components we have developed, as we progressively switch our SVN hosting. The first piece we have committed is the Mantis OSLC REST server module.
OSLC-CM V1 is a proposed standard for REST APIs of bugtrackers, and in our seek for more interoperability in the bugtracker space, we’ve been very interested in it.
OSLC-CM is quite young and only so far implemented in proprietary tools (although elaborated in an open way) on the server side, and as we believe in FLOSS, we’ve started trying to implement basics of server side plugins for a few bugtrackers.
In addition to a demo server that’s simulating the behaviour of a bugtracker, we have started implementing a Mantis plugin and FusionForge and Codendi trackers add-ons (all PHP and based on Zend framework, see this project on picoforge). All are very basic, but we hope they will be the basis for future OSLC-CM compatible servers in these tools.
At the same time we’ve been experimenting with the code already published in Mylyn to support OSLC-CM on the client side. Not everything is public yet in Mylyn, as the elements that have been developped for some connectors of Tasktop to the proprietary tools are being ported to the open source code of Mylyn.
We have thus been able to use the Junit tests classes of Mylyn and tweak them in a way to connect to an instance of the demo server for Mantis (including handling some Basic auth), and be able to retrieve the first bugs descriptions 🙂
Now that this works, we’ll try and add some Java code (maybe reusing Mylyn client libs) to doc4 (being developped as part of Helios) in order to start linking doc4 and Mantis so that this can be used in the Helios platform. This may involve mixing code of XWiki and Mylyn… hmmm… well, we’ll see.
Next steps may be also to try and implement a connector in Python that might be used in tools like bts-link.
Then whichever Python or Java client libraries we have, will allow us to use them inside FetchBugs4.me to connect and harvest bugs of OSLC-CM compliant bugtrackers eventually.
Lots of interesting developments ahead. Stay tuned.
We’re working on implementing a demo/test server for the OSLC-CM V1 protocol, in order to help test client tools.
We’ve released (under a BSD license) a first 0.1 preliminary version that only supports GET queries, that’ll lead the way to an expected complete demo server of OSLC-CM V1 when the 1.0 version will be finished.
At the moment, it will only provide a minimal REST implementation of a PHP server using zend, and will produce JSON or XML/RDF views of fictionnal bugs contructed out of contents of a CSV file.
More details may be found at : https://picoforge.int-evry.fr/cgi-bin/twiki/view/Oslc/Web/, whereas the code is in the Download page there.