Great advice for everyone involved in open source. I will share this link with my teams.
I, too, have come to similar observations. Small, frequent, public commits show the community that you're engaged and listening to their feedback. If you have a set of specific goals for the project, post your improvements in a branch. That way consumers of your work can run the stable branch, other developers can participate with you in your development or feature branch. ASK for feedback on new features 'Hey, I added this ... what do people think?" That way you're iterating in development with your user community. When the new thing is ready for stable, it will reflect, not just your conception of "good" but what the community finds useful and intuitive. EVERY pull request is a opportunity to grow your contributor base. Foster and encourage newcomers to get involved.
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.
Great advice for everyone involved in open source. I will share this link with my teams.
I, too, have come to similar observations. Small, frequent, public commits show the community that you're engaged and listening to their feedback. If you have a set of specific goals for the project, post your improvements in a branch. That way consumers of your work can run the stable branch, other developers can participate with you in your development or feature branch. ASK for feedback on new features 'Hey, I added this ... what do people think?" That way you're iterating in development with your user community. When the new thing is ready for stable, it will reflect, not just your conception of "good" but what the community finds useful and intuitive. EVERY pull request is a opportunity to grow your contributor base. Foster and encourage newcomers to get involved.