Scoundrel on Nostr: You know, I think that pull requests are the wrong way to do open source projects. ...
You know, I think that pull requests are the wrong way to do open source projects. Instead, I think people should just perform hard forks implementing whatever features or fixes they feel like.
That way anyone who wae especially interested in the feature can be told to just try it out, and that way the maintainers won't have any obligation to respond to the contribution until they are specifically interested in implementing it. Additionally, maintainers won't have to scrounge through the code for any potential problems, or hope the outside coder comes back and fixes all those problems in the exact way you want them to. Instead, maintainers can just ditch the other person's code entirely in favor of re-implementing it themselves, piching and choosing the code they bother to read or steal.
I've contributed to open source before, and it was absolutely exhausting pouring my heart and soul into a pull request that the maintainer simply couldn't afford the time to look at. My most exciting moment from that has got to be when a random user saw what I was doing and just said "hey, I want to use those features NOW. How do I install them?"
If I ever start an open source project, I'm going to make my position clear. I'm going to encourage programmers to advertise their forks on my page, and encourage users to browse through the forks for ones that they are interested in. I won't need a single contribution guideline, because new contributions would never impose any kind of cost on me or the users.
That way anyone who wae especially interested in the feature can be told to just try it out, and that way the maintainers won't have any obligation to respond to the contribution until they are specifically interested in implementing it. Additionally, maintainers won't have to scrounge through the code for any potential problems, or hope the outside coder comes back and fixes all those problems in the exact way you want them to. Instead, maintainers can just ditch the other person's code entirely in favor of re-implementing it themselves, piching and choosing the code they bother to read or steal.
I've contributed to open source before, and it was absolutely exhausting pouring my heart and soul into a pull request that the maintainer simply couldn't afford the time to look at. My most exciting moment from that has got to be when a random user saw what I was doing and just said "hey, I want to use those features NOW. How do I install them?"
If I ever start an open source project, I'm going to make my position clear. I'm going to encourage programmers to advertise their forks on my page, and encourage users to browse through the forks for ones that they are interested in. I won't need a single contribution guideline, because new contributions would never impose any kind of cost on me or the users.