That said, it's not always that swift... For instance, I've created a pull request in Vuejs fixing an infinite loop bug in the template compiler (symptoms: compilation blocked indefinitely, 100% CPU usage... not something that can be ignored, I thought).
I had a hard time making my issue not being discarded, and two years later, the bug is still present, and the fix has not even been reviewed ever since.
I'm not being bitter, I actually dont care, but just to tell: Making yourself heard while contributing to large projects can also be a challenge, even (especially?) for small fixes 🤔 (I had other, less stereotypical, experiences).
I totally agree with this, I have also had a wide range of responses to Issues and PRs from different projects. I have seen everything from the good experiences with Node.js, to other projects where I get massive pushback on reasonable changes, to radio silence for years. A lot can depend on the project's governance style and how the maintainers see your specific issue.
You are correct that in larger projects it can be really tough to have your issue seen as important, especially if there is trouble reproducing it or a lack of community support behind it.
I appreciate this take on the Open Source world, thank you for adding your experiences.
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.
Nice :)
That said, it's not always that swift... For instance, I've created a pull request in Vuejs fixing an infinite loop bug in the template compiler (symptoms: compilation blocked indefinitely, 100% CPU usage... not something that can be ignored, I thought).
I had a hard time making my issue not being discarded, and two years later, the bug is still present, and the fix has not even been reviewed ever since.
I'm not being bitter, I actually dont care, but just to tell: Making yourself heard while contributing to large projects can also be a challenge, even (especially?) for small fixes 🤔 (I had other, less stereotypical, experiences).
I totally agree with this, I have also had a wide range of responses to Issues and PRs from different projects. I have seen everything from the good experiences with Node.js, to other projects where I get massive pushback on reasonable changes, to radio silence for years. A lot can depend on the project's governance style and how the maintainers see your specific issue.
You are correct that in larger projects it can be really tough to have your issue seen as important, especially if there is trouble reproducing it or a lack of community support behind it.
I appreciate this take on the Open Source world, thank you for adding your experiences.