Maintaners Wanted

[wfleming]

This engine has unfortunately fallen behind both ember-watson & Code Climate's spec. Our team does not use Ember, and hasn't had time to keep up on this engine. If you're interested in helping modernize & maintain this engine, please comment here or get in touch with us at hello@codeclimate.com!

[timiyay]

I'm currently reviewing our trial version of Code Climate, using it for one of our Ember apps, so I'll hopefully be able to form an opinion on this, and post here.

In the meantime, I would suggest Code Climate should remove (or mark as 'beta' or 'community support only') their advertisements of Ember support:

• on the homepage (https://codeclimate.com/)
• on the engines page (https://codeclimate.com/engines#ember-watson)
• in the docs list of supported frameworks (https://docs.codeclimate.com/docs/programming-languages-frameworks)
• in the docs page for Ember (https://docs.codeclimate.com/docs/watson)

As a potential paying customer, I would expect this type of maintenance to be provided by CC, if they're advertising it. If this maintenance is being pushed onto me anyway, then I might as well integrate watson into my CI flow in other ways. The main appeal of CC is that I don't have to think about such things.

[leftees]

Hey @timiyay -

Thanks for taking the time to share that feedback and suggestion with us. First, I'm sorry to hear that we haven't met your expectations -- that's certainly not the experience we want to provide.

The goal when releasing our engines-based analysis was to allow for any developer to have support for their language of choice. However, this definitely presented a challenge to our small team when it came to maintaining and supporting the various engines that we've made available as there are already many and the list is growing. With that in mind, we have a number of engines that have been built and are continued to be supported by our team and a number of engines that are being maintained by developers in the community. In this case, we hope to gain help from other developers in the open-source community to help make contributions to this engine so it can continue to improve and better serve Ember users.

That said, though, we're actively working on how to better communicate the state of engines to our users and how to improve our cooperation with maintainers. Your suggestion of making these distinctions clearer in docs, as well as on our homepage is a good starting place, so we'll definitely keep that in mind as we decide what changes to make. To start, we already have those separated here: https://docs.codeclimate.com/docs/list-of-engines.

Thanks again for sending over those suggestions. Let us know if you have any other questions, or if there's anything else we can help with.