C3 HAS BEEN FORKED BY BILLBOARD.JS WHICH IS ACTIVELY MAINTAINED

[blazespinnaker]

Please add this to the readme, or come back and maintain. Either is perfectively acceptable, but burying the lead deep in the issues is a bit mean :)

[blazespinnaker]

#1965 for further info, not sure if there is something more recent.

Wish billboard gave more topline credit to c3. Truly a giant to stand on the shoulders of.

[GDFaber]

That's new to me, had no idea someone forked the project in 2017 and created somthing in parallel to C3.js, do you know what is the difference between the two? (apart from being more maintained at the moment)

[blazespinnaker]

It's a very impressive fork, but largely keeps the soul of c3 intact. Pretty much the answer to our concerns here.

One idea I would suggest is a reverse fork if the maintainer here is serious about coming back. I'd be happy to help with tests and prs.

If not serious about coming back, it really behooves the maintainer to highlight this fork. c3 has a lot of presence in the search engines.

[GDFaber]

It's a very impressive fork, but largely keeps the soul of c3 intact. Pretty much the answer to our concerns here.

One idea I would suggest is a reverse fork if the maintainer here is serious about coming back.

My thought exactly. What do you think, @kt3k?

[blazespinnaker]

One thought though, to bring maximum value to everyone concerned, it'd be good to maintain the project in a way that we can merge bug fixes and features back and forth between the projects. It's tricky, but I've seen it done successfully in other projects that have been reverse forked.

It will take a small degree of cooperation from the billboard folks, but as long as value is added to the ecosystem at large (rather than just simple rebranding billboard and constant merge backs) I really can't imagine why they wouldn't be.