-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Active fork of Chart.js? #795
Comments
This project is based on chartjs: https://github.com/FVANCOP/ChartNew.js/ - what version, I don't know, but it seems active. |
It looks like it's based on a pre-1.0 version. |
@nnnick last responded to an issue 9 days ago so it's not that inactive,hopefully when he gets on he'll appoint some admins or something... |
Yeah, I saw that, but it was a month before that to the previous comment, and 3 months since the last commit. I totally understand getting busy, so I don't want this to sound like I don't appreciate everything @nnnick has done. With 12.5k stars, it seems like there could be a much stronger community, whereas the current commit history shows essentially nobody but nnnick. With 99 active PRs, there are certainly enough active people wanting to contribute. I believe this library blows away https://github.com/mbostock/d3, but only if it continues to be developed. |
yep, but I'm sure with us bringing these issues to his attention, he'll do something adding collaborators shouldn't take long |
I also don't think sending him an email would hurt: hello@nickdownie.com |
i've been updating my own fork based on stackoverflow questions/things i wanted included -https://github.com/leighquince/Chart.js |
This is alive and well. Some leadership has been delegated and things are moving ahead more quickly. Thank you for your concert. A major effort right now is creating test cases for all Issues. This will help us quickly sort things out and get ready for v1.0! Please feel free to help with this! |
Does anybody know if this project is still maintained? or whether there is an updated fork somewhere?
The text was updated successfully, but these errors were encountered: