4 ms·
Most open source projects have not just the final source published, but also all communication for patches, features and their relevant discussion. That could
by koolba 3y ago
Most open source projects have not just the final source published, but also all communication for patches, features and their relevant discussion.
That could be on GitHub, a traditional mailing list, or some other hosting platform.
You can’t tell in advance how your work will be received, but you can empirically tell how others work has been received. And even compare the communication styles.
And it’s not rocket science that well reasoned patches, with tests, splitting out separate commits, explaining the reason for the change would be better received than a typo laden one-liner, “I needz it”.
It’s up to the submitter to match the flow of the project.
- keybored 3y ago> And it’s not rocket science that well reasoned patches, with tests, splitting out separate commits, explaining the reason for the change would be better received than a typo laden one-liner, “I needz it”. I said makes an effort. You can implement a novel feature (and well) and get it rejected.
- koolba 3y agoI’m saying without writing any code I can already tell, within a reasonable level of confidence, if a patch would be accepted by looking through past contributions. You’re not working in a vacuum.