c3js roadmap and billboard.js

[ataft]

I posted a similar message in the Google groups, but didn't get any response, so am posting here.

Last year, C3.js was declared un-maintained, so someone forked it and started putting in a tremendous amount of work, creating billboard.js. At this point, C3 had nearly zero commits over an entire year AND the person who forked it asked about it's status numerous times with no response. Right after the Billboard release, we started to see some commits on C3. However, Billboard is a lot more active, plus it's been brought up to date with things like ES6 and Webpack. Also, it only takes a couple minutes to migrate from C3 to billboard.

However, it seems that having both Billboard and C3 projects active will split the community and lead to neither surviving in the long run. Can the owners of both projects make sure this doesn't happen? Why not put all efforts into one project and close the other?

[blazespinnaker]

There's nothing wrong with maintaining two projects as long as nobody does something truly truly silly like make it hard to merge back and forth. That would definitely harm both projects and the underlying community.