I've seen a lot of advocacy that programmers should be responsible for their programs similar to how civil engineers are responsible for their bridges.
So that would mean you shouldn't eg. as a kernel maintainer, merge a new filesystem until you're certain it won't destroy user data.
But that's a very high bar - it takes a lot of time, effort, and skill to make a filesystem like that. And many contributors may get discouraged before they get there.
Isn't that gatekeeping?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.