Joshua Großmann wrote:

I thought you guys forked redmine cause its long release interval, but yours isn't even better, is it? When did the new major version finished?

Shorter release intervals are a goal we're trying to pursue, not the reason we forked.

Well, versus redmine has chiliproject lesser plugins, right?

Probably, though I fail to see the connection.

I asked this because i migrated from redmine to chiliproject, but now im frightened and think about that chiliproject does really have future

We've stalled indeed, there are multiple reasons for this and I hope to be able to blog about it to inform everyone, but we're in for the long run.

(for the open source community).

Again, I fail to see the connection. Work we do on ChiliProject in our free time is and will remain open source, we don't have control over what happens with what we do on company time, but for those I know of it's not been on the core much anyway.

Feel free to continue asking if I didn't address your concerns :-)

Hi Felix, thanks for all the great work of you and Eric.

Maybe it's a good time to try to attract more contributors to the project and delegate some responsibilities.

We have right now 42 pull requests waiting for a review. There are many features people really need and that are right now available on Redmine and also some of them already on a pull request just waiting for a merge/review.

Have to chime in that I strongly share Joshua's concerns, if not his not-so-friendly tone ;)

We switched our company infrastructure to Chili with the understanding that there was a strong committed team to moving it forward and past Redmine. The projects have now diverged, and Chili seems mired with no progress while Redmine is innovating and launching new versions almost monthly. Most alarmingly, is the silence from the Chili team.

Lots of people counting on Chili at this point gang, we at least need an update other than "trust us, we'll get to back to this project soon".

Hi,

I've the same concerns - the development of Chili stalled and only seldom an external pull request finds it's way into the master - so currently Redmine is (sadly) much more innovative and has many functions, Chili is missing (due to the lack of reviewing+accepting pull requests).

So, why do the Chili developers not open their team for further devs? Why is here no open communication?

Currently it seems, that the new team does the errors of the old team (again).

Please react NOW, please don't let further weeks pass by before reacting - otherwise Chili could pass away as fast as it's founded.

If there's no further development the next 4 weeks, than I'll move back to Redmine - because many very important functions are available to Redmine for months, while Chili even doesn't know, if these often demanded functions (multi scm, editable gantt...) ever will be adapted.

Just my 2 cents.

Chris

PS: Reviewing the project activity only Felix seems to work on Chili currently - so: Felix, thanks for your hard work - I really appreciate that!

Gabriel Mazetto wrote:

Maybe it's a good time to try to attract more contributors to the project and delegate some responsibilities.

Sure, Andrew's been doing terrific work on the Prototype to jQuery switch for example, and I've been thinking about taking him into the team.

We have right now 42 pull requests waiting for a review. There are many features people really need and that are right now available on Redmine

Then use Redmine. It's the same as with all tools, use the one best suited to your use-case.

and also some of them already on a pull request just waiting for a merge/review.

Waiting for a review, probably, waiting for a merge, I doubt it. Sorry to be blunt here, but one of our gripes with the current codebase is the huge amount of technical debt that comes with it, just merging code "because it's there" won't make it better. Similarly, another gripe is the feature creep and the insanely complicated and spread all over the place configs for almost everything, again, just "merging stuff" won't make it better.

Lev Tsypin wrote:

We switched our company infrastructure to Chili with the understanding that there was a strong committed team to moving it forward and past Redmine.

Forward yes, past Redmine would mean that we compare ChiliProject to Redmine. We (or at least I) don't. Redmine is part of ChiliProject's history, that's all it is to me.

The projects have now diverged, and Chili seems mired with no progress

We have lives and have been caught in them, and I hope I was able to answer everyone who asked for it.

Most alarmingly, is the silence from the Chili team.

I had thought about writing a blog post about it but decided against it back then. If you guys are interested in this sort of things, we can try to post more about them.

while Redmine is innovating and launching new versions almost monthly.

Again: if Redmine better suits your use-case, don't use ChiliProject, it's as simple as that. (if you want to discuss those features, feel free to contact me on IRC (thegcat) or open a new forum thread).

Lots of people counting on Chili at this point gang, we at least need an update other than "trust us, we'll get to back to this project soon".

Another thing that's been lurking in the back of my head, I see I should get it out of there, thanks for saying it out loud :-)

@Felix: I can understand that you're annoyed and frustrated about the situation - we (users) are, too.

So please enlighten us about the current situation, as far as possible and reasonable.

Even this discussion shows that Chili has users who cope about the development and future of this project.

Therefore statements like "ah, than go back to hell (ehm: Redmine)" ;-) just increase the already growing frustration on both sides.

If there's more we (users) can do, please don't hesitate to ask for help.

I'm feeling sorry that I currently can't help coding so much (C++ programmer), but I'm still learning Ruby and hope to support you in the not so far future.

Keep the projekt running and keep the communication with the users.

A simple note on the roadmap "projekt delayed due to xyz, next release schedule in one/two months..." would increase the trust of the users (like me).

And again: You (Felix and the whole CP team) do/did a great job!

Viele Grüße aus dem Hohen Norden (wo heute gearbeitet wird) ;-)
Chris

Chris Dähn wrote:

See the other answers above for the things I haven't answered here.

Why is here no open communication?

We have pretty open communication on IRC and/or Twitter, for IRC at least there are logs. As I said above "it sucks" doesn't help, so let me ask you directly: what kind of communication would you be interested in, and on what platforms. We had decided against a mailing list way back then for example, if that's something people are more comfortable with it's a least something I'd be willing to consider again.

Currently it seems, that the new team does the errors of the old team (again).

We're painfully aware that not all works as good as we had expected, this has different reasons I hope to be able to elaborate on in the next few weeks.

Let me ask you again to be more specific though. This is the first open source project I am in the lead team of, the second open source project I'm involved at all. I won't pretend I know it all. If you tell me/us what specific things you think could/should be improved, we can discuss ways to do it (hint: I don't think adding more devs/merging code just because "it's there" is a good idea), this should go in other threads then though.

Please react NOW, please don't let further weeks pass by before reacting - otherwise Chili could pass away as fast as it's founded.

I'm sorry if I got the wrong impression, but if you're so interested in the community, complaining won't help anyone :-) I'll take constructive criticism any day though!

If there's no further development the next 4 weeks, than I'll move back to Redmine - because many very important functions are available to Redmine for months, while Chili even doesn't know, if these often demanded functions (multi scm, editable gantt...) ever will be adapted.

Again, if Redmine suits your needs better, use it. We don't owe you anything, you don't owe us anything either.

Chris Dähn wrote:

@Felix: I can understand that you're annoyed and frustrated about the situation - we (users) are, too.

To be honest, I'm rather stressed that I haven't been able to do as much as I would have like rather than annoyed or frustrated, but oh well :-)

So please enlighten us about the current situation, as far as possible and reasonable.

I'll try, here is probably not the right place though.

Even this discussion shows that Chili has users who cope about the development and future of this project.

Indeed, thank you for that :-)

Therefore statements like "ah, than go back to hell (ehm: Redmine)" ;-) just increase the already growing frustration on both sides.

No, this is not how I meant it. I really mean it when I say to use the right tool for the right job. Regarding the private issues for example, we think the current Redmine solution is a terrible solution because it's not generic and IIRC required many of the stuff pertaining to issues to be touched. It also took a few iterations to stabilize, which was probably somewhat related to the previous point. If you need private issues though, Redmine has them now, we will probably come around to them too, but after some other things we consider more important, my conclusion would be to use Redmine because it fits my need (private issues) better.

Don't get me wrong, I like that people use ChiliProject, but I dislike trying to use a hammer as a screwdriver more ;-)

Keep the projekt running and keep the communication with the users.

OK, this was posted before my response to you, but if you think the communication could be improved, I'd love to hear your suggestions :-)

A simple note on the roadmap "projekt delayed due to xyz, next release schedule in one/two months..." would increase the trust of the users (like me).

That was one of the reasons to not add to many future versions, in the roadmap and only commit "ready" features to them. It doesn't seem to have worked out so well though :-/

And again: You (Felix and the whole CP team) do/did a great job!

Thanks :-)

Viele Grüße aus dem Hohen Norden (wo heute gearbeitet wird) ;-)

IIRC die Berliner auch, ich bin heute allerdings etwas südlicher unterwegs, bewölkte Grüße zurück :-)

And I'm sorry if I seem rough to some, we're not compensated for the work we put in here, we most of the time just talk in the team if at all about the "guilt" of not being able to do as much as we've planned, and as I said we're still learning the whole "lead an open source project" (regardless of the no one owing anyone anything issue), it's been a straining last few months for us :-)

Well I'm not even a real developer and don't know rails that well but I have a few comments about some of the changes which are going on from a plugin perspective. So I took a redmine plugin and it runs fine on Redmine but fail on CP. Reason ... field name changes. Ok if that's all it takes to migrate a plugin that's fairly easy but that means as far as I know plugins written for Redmine won't work on CP. Now if some one can tell me an easy way to be able to support both I'll be happy. But was the field name changes absolutely necessary? And trying to track this back as to why in the documentation I haven't figure out yet.

FYI - this weekend I will be releasing work_time for Chiliproject! Looking for a tester or two before I release it too!!!

Sorry for my "not-so-friendly tone", maybe it sounds as like this. Well, i indeed respect your work, but your promotion (and reasons why you forked redmine) doesn't correspond to the facts?!
I think we understand your reasons why you can't develop on chiliproject anytime, but for the community it is a obligatory point to update the software regularly, isn't it?

Thats why i will move back to redmine, as you (Felix) suggested. But i really hope, that this project has a future some day..

Regards,
josh