Make PRs, not issues

When contributing to open source, submitting a pull request (PR) is often more effective than just opening an issue. While raising issues is important, a PR demonstrates your idea in action and makes it easier for maintainers to review and understand your proposal.

Of course, preparing a PR takes more time and effort than simply describing a problem or suggestion. If you report a bug, maintainers are likely to fix it. But if you’re proposing a new feature or API, submitting a PR greatly improves the odds that your idea will be implemented. Without a PR, it’s much harder for maintainers to prioritize or visualize your suggestion. And in my experience(features in ruby gems) most of the time they ask for a PR.

Summary

If you want something to change in an open source project, and you have the ability, make a PR. Your contribution will be more visible, actionable, and likely to be accepted.