Project maintenance

[cadavre]

Hi,
I'm CTO of Jazzy Innovations company, based in Poland. Our company is using plato in several JS projects to track code quality over time. It's a great tool but we find more and more cases when it would be lovely to have plato extended here and there.

My question to @jsoverson (I blamed you on "Needs maintainer" entry in README :p) is: what are your expectations on maintenance of this library? I was thinking about making this project go forward with our team, we want to keep it open-source of course.

My question to community is: would you like to have this lib maintained? What are you missing or what you'd like to have changed?

Maybe there's already another tool to use? Or another fork of this lib which is growing and have potential?

[tomhicks-bsf]

I'm also interested in maintaining this. Our needs are really to do with support for larger projects, such as:

• aggregate values through a directory structure for project overview
• search for files
• export different formats (e.g. HTML as now, JSON) so we can use different reporters and open up/separate the visualisation side of things
• pass history to CLI, so we don't have to keep history either in git or build server or whatever
• support for JSX out of the box (sorry it feels dirty, but it's so damn common these days)
• support for custom evaluators (essentially a plugin system)
• constraints for CI integration (fail if a file is particularly unmaintainable for example, or if overall project maintainability reaches a threshold)

[gabrielcsapo]

I would definitely contribute if someone was actively maintaining

[sradevski]

If you look under the forks of plato, you will see that there is a more recent, maintained version of the tool: https://github.com/the-simian/es6-plato. I haven't tried it out yet, but it is worth looking into it.

[eshinn]

There are a few things I'd like to see:

1. The ability for it to see () => {} functions. As it stands right now, unless the word function is used, I can't see what exactly the cog icons are pointing to.
2. The ability to use non .js file extensions (ex: .jsx, .sh, no-ext)

@sradevski - Respectfully, I took a look at the repo you mentioned (as well as the one it's forked from) and neither seem to have a release later than 2014.

[sradevski]

@eshinn Yeah, it seems that is true for the releases, but there are recent commits and I just judged based on that. I will try it out when I find the time and let you know if it is any good.

[zephraph]

@es-analysis could we get some more contributors added to the organization? I'd be willing to contribute, along with a few individuals above.

[sradevski]

I tried the fork https://github.com/the-simian/es6-plato and it works great! The last release on npm was 4 months ago, and there are no open issues with the project. I ran it on 2 of my React projects and it worked without any problem. I suggest you to look into it.

[jsoverson]

@zephraph this project needs a new maintainer, not just a few contributors. I can offer no time at all.

If someone wants to be the new maintainer, then submit a PR that incorporates any of the existing pull requests + new changes required and I'll add them to the group and give them publish access on npm.

[gabrielcsapo]

@jsoverson it might make sense to ping @the-simian to see if will merge this changes into the main project?

[the-simian]

Sorry, I've wanted to do this for some time, but I've been really overwhelmed. I've gotten my fork stable, and working, and I've fixed issues at they have come up, but I've been having a hard time to find time to make a possibly difficult PR (there could be a lot of merge conflicts at this point).

I appreciate the ping, I'll do it when I can, but I've had a challenge finding time to re-integrate to this one. I think that's a big job

[jjpatel361]

So is this project maintained? or there are other forks actively maintained and updated.
@the-simian are you actively maintaining this project.

[the-simian]

@jjpatel361 I am maintaining es6-plato right now, and I keep it up to date. I've not merged it into this projected mainly because I've heavily refactored the code to be simpler and I've added a lot of important things over time, its diverged enough

At some point I'd like to merge it all back in. I think since I forked some time ago, this project did add back in some es6-compatibility and stuff, but I havent taken the time to analyze all the updates since I forked.

SO the short answer is : I am actively maintaining my branch. The project lead here did make me a contributor and I've unfortunately not taken advantage of that yet and pulled the efforts i've made back into this 'more popular' repo.

[typhonrt]

Just a note... I have updated the underlying complexity reporting module, typhonjs-escomplex to 0.1.0. I've moved to Babel parser and all of the latest edge JS code should work. Bonus is that Typescript is now supported as well. I'll be submitting a PR soon to plato with the updates necessary. Some of the report structure has changed, so I'll be glad to do the update. @jsoverson Plato lives! ;P

[DanielRuf]

What is the current status?

[the-simian]

@DanielRuf Speaking for myself, I'm still maintaining es6-plato atm. Over time I've done so much refactoring here and there its been hard to consider re-merging into plato. I currently keep that up to date, handle its issues and so on. Right now a lot of folks are using that, myself included so I'm keeping the wheels on the bus on that front.