-
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
Financial chart #4172
Comments
@etimberg what do you thing to start normalizing the name of chart repositories (as we did for plugins) and create the fork under the following name: |
@simonbrunel I like that idea since it matches what we did for plugins. In terms of moving this under the org, would it be best to fork it into the org, or just transfer the repo? |
Transfer the repo seems better! |
I'm happy to transfer the repo. I will need permissions to create repositories in the chartjs organization in able to do so Chart.BarFunnel.js and Chart.smith.js both depend on Chart.js 2.4.0. I can't easily tell what version Chart.LinearGauge.js is depending on because it doesn't utilize gulp & npm like the others (chartjs/Chart.LinearGauge.js#6) So right now basically the pattern is that charts use the |
Agree, we should align other 2.x chart repository names. We can start with yours in |
I sent you guys invites to the repo, but I don't think it'll allow you transfer rights. I think the only way will be to at least temporarily give me more rights in the |
I think |
Thanks. Closing this as done. Chart lives here now: https://github.com/chartjs/chartjs-chart-financial |
I've been developing a financial chart here: https://github.com/benmccann/Chart.Financial.js
@etimberg mentioned that he'd be open to having it live under the chartjs group
I want to finish up some things before I publish the initial version to npm. However, I was wondering if you could create a fork under the chartjs group in the meantime while I work on polishing it up
The text was updated successfully, but these errors were encountered: