Tijs,
If my name has any relevance for you, then here it is: Cristian, I am the one who posted to JIRA the issue ACT-1745. Or kyphi, if you read on the left of my posts…
I would love to contribute to Activiti, but my time is super limited. Besides, I have no experience writing Eclipse plugins, it was never something I needed to do. Even if I wanted to contribute to Activiti engine only, in order to change the code I need to fully understand it first, which requires time. On the other hand, I am pressured in my current position to implement systems which could use Activiti as a tool related to BPM. I considered that even a modest contribution like mine, by posting issues to Activiti JIRA and/or forums is still more than nothing. That also took time, it does not happen instantly. I am rather a tester of your tools who gives feedback to the guys who know the Activiti internals in detail. I don't have your wingspan in Activiti, I know parts of it only. The vision is in your head and Joram's and others'. When I post the bugs and others in JIRA or forums, I do it to help improve Activiti, it's nothing against you or Activiti. I would like Activiti to succeed. Once I invested time in any product, I have a co-interest in its success. Otherwise, my investment is hurt, at least partially.
I think delaying the fixing of basic things delays the serious adoption of Activiti or even makes people look for alternatives. I know there are lots of issues and every issue reporter may subjectively think their reported issue is the most important, but I think it's objective to think that basic things should come first. I have found some other issues and I have some suggestions which might be convincing or not so convincing. I will try to post those as well on the forum or in JIRA. WOuld you encourage me to do that? It shouldn't be all or nothing, I try to give back as much as I can…
Me