[mylar-dev] Bug 160928: [connector] MKS Integrity

["Kristina Taylor" <Kristina.Taylor@xxxxxxx>]

URL: https://bugs.eclipse.org/bugs/show_bug.cgi?id=160928

I work on the integrations team at MKS, and I'm looking into the amount
of work required to create a connector between Mylar and our issue
repository, MKS Integrity.  I see in the bug report that one of the
developers on one of our other teams has already requested this. :) We
have an existing eclipse integration, which we are looking to improve.

A bit of background on our product: MKS Integrity is a combination of
workflow management (that's the issue repository side of things) and a
source code repository.  It combines to make a complete ALM solution,
minus the IDE.  We have 4 interfaces to the system: Swing GUI, Web UI
(including a URL-based method of accessing specific issue(s)), CLI, and
API.  I've already determined that we meet all of the requirements
listed at http://wiki.eclipse.org/index.php/Mylar_Integrator_Reference
It also appears as though your basic web integration will already work
directly with our web UI.

Now, all that being said, I have some questions:
1) Does the integration need to be released as a part of your product,
or can it be part of our existing eclipse integration?
2) We currently have our own version of an Eclipse Task list, called
"MKS Worktray".  It has the ability to create new issues, edit issues,
run a query, and deal with change packages.   How much of this
functionality would we be able to integrate via "rich editing"?  Can
Mylar connectors be organized so that our UI would be called when a user
tries to edit a task?
3) What level of effort (# of developer days) do you think would be
required for a reasonably proficient Java developer already familiar
with Eclipse?

That's all I can think of right now.  Thanks!

Kristina Taylor
Software Developer, MKS Inc.
Waterloo, ON, Canada