You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are various ways of working together and organising open-source projects. The one I believe in most is the "someone else has to merge your PR" rule. (assuming the basics like automatic tests etc are covered)
This creates a bit of a challenge for new projects, because often there is only one or two people ... a popular way around it is to offer to bestow the privilege of merging PRs on anyone who has a PR merged. I can imagine all sorts of ways that this could go wrong or lead to stress etc but in my (limited) experience it works well in practice.
If there is no objection voiced here I will start following this for all future PRs. I wouldn't broadly advertise it, just ask people when their first PR is merged.
The text was updated successfully, but these errors were encountered:
There are various ways of working together and organising open-source projects. The one I believe in most is the "someone else has to merge your PR" rule. (assuming the basics like automatic tests etc are covered)
This creates a bit of a challenge for new projects, because often there is only one or two people ... a popular way around it is to offer to bestow the privilege of merging PRs on anyone who has a PR merged. I can imagine all sorts of ways that this could go wrong or lead to stress etc but in my (limited) experience it works well in practice.
If there is no objection voiced here I will start following this for all future PRs. I wouldn't broadly advertise it, just ask people when their first PR is merged.
The text was updated successfully, but these errors were encountered: