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
(Still) Looking for contributors - a Recharts Status Update #3407
Comments
I am a pretty new developer, but my focus has mostly been CSS/React up to this point with some Java and Python sprinkled in. What could someone like me do to contribute? I find this library interesting because I have degrees in math/stats. Fair warning, I haven't practiced much of either in about 10 years... so, I could probably help with that end of things but I'd need very specific direction and then a little time to grease the wheels. Otherwise, what else is there for someone with not a ton of experience? |
@TheHumanistX sweet! I think someone with some math background is a huge help, I hate math 😂. I need to tag more issues with "good first issue", but helping with the docs is always good (and will help get you familiar with the library). We're still in progress of moving the website over to storybook. I'll tag and create a few issues today. |
Hi @ckifer, is there a roadmap or some kind of plan on what the maintainers are going to work on? I would like to be involved in becoming a contributor but I need to know what is expected from contributors. |
@ckifer Just tag me when you have some things ready you think maybe I could help with. I have never contributed to a project before so this may take a second for me to understand and get used to. |
@GasimGasimzada no there isn't currently a coherent roadmap at the moment. Myself and @nikolasrieble can work on putting that together - we know direction, but exacts are squishy. We would like to move towards a 3.x release which contains many of the breaking changes we currently have pending. That release would ideally include a subset of these things (on mobile, will link issues later):
Overwhelmingly my goal is: make this project more robust and easier to maintain. Right now it is fragile and difficult. |
Thank you for the brief information. Could you count me in to contribute? |
Hey @ckifer, I hope you are doing well. Please count me in. I am a junior dev but would love to help in any way possible. |
The more the merrier, welcome! |
For what it is worth, I tried to summarise our current initiatives with a bit more detail. |
@nikolasrieble I can work on the docs. I have experience with that. Not so confident with open-source code at the moment. |
@abdnafees We would love feedback on our storybook. There are also quite a few open issues with storybook. You could help with reviewing the existing documentation, improving it, creating issues, or right away adding stories to finish the first milestone for a complete documentation in storybook. |
@nikolasrieble Got it, I will get started right away. |
…charts#3407)-new-steps-in-contribution-md # Conflicts: # CONTRIBUTING.md
Hello @ckifer, can I join in right now. Can pick anything |
Hi @o0vO you can join any time! Please start by looking into open issues that are tagged good first issue Other than that, we need help all across the board: Responding to issues, helping user reproduce, extending documentation and reviewing PRs. |
Hi all,
Going to pin this as a new issue out of the old one: #1833
We've figured some things out since then! First of all, thanks to the creator of recharts @arcthur for helping us get the project into the hands of more contributors and maintainers. We want to help recharts to be better, fix bugs, implement features, increase documentation, etc. We couldn't do that with very much velocity without communication, without direction, or without access.
We now have a recharts Slack channel for communication between those who are collaborating or wish to help collaborate on the project: Join here - this is a contributors slack channel, please don't use the slack channel for issues
Secondly, thanks to those who have joined as interested or invested members of the community - nothing can happen without individuals willing to put in time and effort to manage the community, manage issues, dive into bugs, update documentation, etc. Huge shoutouts to the following:
...And many more
We've accomplished a few minor released and bug fixes. Notably:
victory-vendor
All that said we still need help! All/most of us are contributing to this library because we either like it and have used it in the past, or are currently using it for day jobs. Any contributions, suggestions, bug deep dives, performance profiles, documentation fixes/improvements, etc. are greatly appreciated by the community.
If you want to help us please join the slack.
Cheers!
Edit 8/9/2023 - status remains the same, please please consider contributing if you are a heavy user of the project
Edit 3/19/2024 - status remains the same, need more long-term contributors. Work has begun on 3.x
The text was updated successfully, but these errors were encountered: