Bugzilla extension development help needed in supporting OSLC specifications

[Steve Speicher]

Spending too much time with your family? Not enough to do during the
weekends?

I was looking for some help in converting our initial implementation of OSLC
[1] support in Bugzilla [2] into a proper Bugzilla extension [3].  By doing
this, it would help Bugzilla to easily link to other repositories (or even
other instances of itself) by adopting the OSLC change management
specification [4].  Unfortunately we don't have that much experience with
Bugzilla and its extension development.  The approach we took in our OSLC
adapter for Bugzilla [2] was to put a front-end to Bugzilla using
Servlets/JSPs, j2bugzilla and XML-RPC.  The reason for this approach was: a)
we know these technologies better and b) it was the basis for a common
pattern we see when initially adopting OSLC and used it for some training
materials.

Feel free to either contact me or we can discuss in [3]

[1] - http://open-services.net
[2] -
http://open-services.net/pipermail/oslc-core_open-services.net/2011-May/000982.html
[3] - https://bugzilla.mozilla.org/show_bug.cgi?id=519177
[4] - http://open-services.net/bin/view/Main/CmSpecificationV2

-- 
- Steve Speicher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20110622/4dead497/attachment.html>