Thank you so much for posting this! It's not often we hear the story behind the person maintaining an open source project. Open source does require you to have an open and humble mindset. As funny as it sounds, we need to learn that it is scary for both the person receiving the issue and the person filing the issue!
Really, don't feel pressured to implement 'x' feature(s) so that you can be the 'best' framework in your niche. Just take your time in picking up the good bits that you like. Try to learn as much from the failures of other open source projects and not just their successes. Building a healthy community is not easy and it's something you learn as you go along. This open source guide might be of help.
At the end of the day, you never know who will be using your code or what it will be used for. Which is quite a scary thing! Definitely take a break if you need to, have a long weekend if necessary. It really helps to see your code with a fresh perspective after long breaks. Who knows? Maybe you'll spot a way to make it easier for others to contribute and ease your workload :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you so much for posting this! It's not often we hear the story behind the person maintaining an open source project. Open source does require you to have an open and humble mindset. As funny as it sounds, we need to learn that it is scary for both the person receiving the issue and the person filing the issue!
Really, don't feel pressured to implement 'x' feature(s) so that you can be the 'best' framework in your niche. Just take your time in picking up the good bits that you like. Try to learn as much from the failures of other open source projects and not just their successes. Building a healthy community is not easy and it's something you learn as you go along. This open source guide might be of help.
At the end of the day, you never know who will be using your code or what it will be used for. Which is quite a scary thing! Definitely take a break if you need to, have a long weekend if necessary. It really helps to see your code with a fresh perspective after long breaks. Who knows? Maybe you'll spot a way to make it easier for others to contribute and ease your workload :)