I've been pretty lucky so far I think. I haven't come across 'the worst' I think.
I've been really happy with it all. I sometimes take breaks, and I know I can because there are other maintainers besides me, we all help each other!
The hardest are the big features and changes, the ones that will be breaking people's setup of disrupt their workflow... We don't want to do any harm, but also don't want to end up with a over-complex codebase with tons of backwards compatibility and hacks.
Mistakes are made and they have to be corrected in software.
The hard part in any software is the clear and friendly communication between humans.
It's hard to prioritize different feature requests and bug fixes.
Up until very recently, we are all volunteers, and most of us still are. We take time out of our lives to make sure Storybook works as intended.
Sometimes on GitHub issues, we get requests demanding that a bug be fixed and not ignored or put off until a later date. We mean no harm and many times we do need to prioritize other things over fixing a bug for an edge case. As always, pull requests are welcome.
Sometimes, I see people asking questions in IMO inappropriate way. For example, requesting things to be fixed or being rude about lack of documentation.
They probably hardly understand what an open source project is =)
So for me, the hardest part is seeing these posts/issues. I always have a strong desire to reply with this great article:
For me, I hate the guilty feeling when a community member does a lot of work on a contribution and I don't have the bandwidth to turn it around right away. Here's a recent example of a contribution that needs feedback from the community, a partial rewrite of the React Native storybook that shows addons on the device:
What's the hardest/worst part about maintaining OSS? How will that change with going full-time?
I've been pretty lucky so far I think. I haven't come across 'the worst' I think.
I've been really happy with it all. I sometimes take breaks, and I know I can because there are other maintainers besides me, we all help each other!
The hardest are the big features and changes, the ones that will be breaking people's setup of disrupt their workflow... We don't want to do any harm, but also don't want to end up with a over-complex codebase with tons of backwards compatibility and hacks.
Mistakes are made and they have to be corrected in software.
The hard part in any software is the clear and friendly communication between humans.
It's hard to prioritize different feature requests and bug fixes.
Up until very recently, we are all volunteers, and most of us still are. We take time out of our lives to make sure Storybook works as intended.
Sometimes on GitHub issues, we get requests demanding that a bug be fixed and not ignored or put off until a later date. We mean no harm and many times we do need to prioritize other things over fixing a bug for an edge case. As always, pull requests are welcome.
Sometimes, I see people asking questions in IMO inappropriate way. For example, requesting things to be fixed or being rude about lack of documentation.
They probably hardly understand what an open source project is =)
So for me, the hardest part is seeing these posts/issues. I always have a strong desire to reply with this great article:
hackernoon.com/i-thought-i-underst...
For me, I hate the guilty feeling when a community member does a lot of work on a contribution and I don't have the bandwidth to turn it around right away. Here's a recent example of a contribution that needs feedback from the community, a partial rewrite of the React Native storybook that shows addons on the device:
github.com/storybooks/storybook/pu...
My biggest hope is that I can have more bandwidth to help shepherd great work like this into the project more quickly.