-
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
A new community driven Chart.js? #885
Comments
@adrianandreias Recently a number of collaborators have joined @nnnick in helping to maintain Chart.js. We've spent a fair bit of time so far working through the issue backlog and releasing a If you're interesting in helping out, please let myself, @nnnick, @tannerlinsley, @jakesyl, @fulldecent or @derekperkins know. |
Duplicate issue, see #795 #356 #821 #833 #505 :-) This project is definitely alive and is now more decentralized. This is evidenced by your expanded team of project "members" above. In general our goal is to improve the release process so that we can develop in parallel rather than in series. To that end, we have a 1.1 milestone that is focused: |
8257171 it would seem this project is fairly active, i've added a new clause to the COLLABORATING file to make it more clear how to become a collaborator |
Would it make sense to create a community-driven Chart.js fork?
I see a lot of issues hanging and not much activity on this project.
I need two things that turn me away from using Chart.js. These are very basic features which I think make sense to be in the core:
@nnnick has done a nice job with Chart.js but he looks pretty busy right now.
I, my self, must admit that I don't have much hours to put into this project, but browsing through pull requests and issues looks like a number of people could contribute.
What do you all think?
The text was updated successfully, but these errors were encountered: