Join forces with redmine-mylyn-connector devs?

[jekkel]

On the redmine side we're currently using the fork made by danmunn (https://github.com/danmunn/redmine_mylyn_connector) which adds redmine 2 compatibility. On the other hand I recognized that you're active on the backlogs plugin issue list (I assume by checking things for issue #7), which is a plugin also heavily used in my company. So we would really appreciate any further development in that direction.

So a question arises: How do you think about joining the both efforts? That way we have both sides of the communication under active development and maybe things that the backlogs plugin maintainers are not able (or not willing) to add to the REST service can easily be added by danmunns plugin.

I saw that issue #2 already proposed some kind of collaboration but focuses on the eclipse side of things and since the issue is already closed I wanted to give it another spin while focussing on the redmine API side.

If I got things wrong and the aforementioned redmine plugin is not needed for the eclipse plugin to work I appreciate clarification on this.

Thanks in advance!

[awilkins]

AFAIK you need the Redmine end for the Mylyn end to work (and IMHO the projects are really confusingly named - the convention for Mylyn is to call the client-side part a connector, and the convention for Redmine is to call the server side part a plugin - but this is transposed!)

From my POV I think both ends of the Mylyn / Redmine connector / plugin project could benefit from being in the same tree - this would make version compatibility matching easier, and let people get all the working parts from a single clone.. but it does have implications for installing the plugin on Redmine, where the procedure is just to clone the repo into place. Perhaps this is a case for using submodules... but I don't have any experience of that, and hear horror stories about it.

Support for the backlogs plugin would also be really nice - there's already some bugs in the Mylyn end that really frustrate me from that perspective (like the thing where "Estimated time" can't be null in the Mylyn client, so it sets it to "0" regardless of whether you actually want an estimate in that ticket), but I don't have an opinion yet as to whether we support that with separate plugins, or configurable support in the main body of the code.