this post was submitted on 02 Jul 2024
88 points (81.4% liked)
Technology
37734 readers
347 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It would've taken less time to merge this than the original comment denying it took to write.
And then everyone will make those whitespace PRs because they want to say they have contributed in XYZ big name projects in their CVs. I don't see why we should encourage those people.
If you genuinely find a white space problem in a project go ahead and submit a patch, by all means. Let the other devs focus on more pressing problems.
Let's agree to disagree
Having devs outside of the project submit fixes for minor issues that don't require intimate knowledge of the project itself is spending dev effort better than having the project devs themselves have to do it.
Having people really outside of the project to commit to the repo is a bad idea to begin with. If you don't plan to contribute by code then just don't contribute at all.
They aren't commiting to the project, they're submitting pull requests. Totally different.
Ya. I mean their commits shouldn't be merged to the repo. They can of course commit whatever they want to their own fork.