4 ms·

Possibly a big mistake to make this post, but I've written my own code of conduct template, which I use on my projects (mostly since snyk, github and similar sc

• asylteltine 3y ago
  [dead]
• Benanov 3y ago
  Applause for "people who solely make code of conduct complaints are not contributors"
• johnklos 3y ago
  That's both ambitious and a little daring. One place where I disagree is in the "skill discrimination" section. If you look up the definition of the word "discrimination", you'd see that it probably means something different (in common use) than what you intend. I'd be fine with agreeing that volunteers are not obligated to put energy in to low quality / low energy contributions, but saying explanations aren't required is unhelpful. "It's low quality code" is plenty of explanation. What you've written suggests that contributions can be rejected because of previous instances of low quality / low effort, without explanation, and that does nothing to further a project. A technical, if short, explanation is always a good idea.
  • LtWorf 3y ago
    I've had people who send a pull request that has 1 commit, changes 2000 lines and fails all the tests and expect me to merge it and spend the time myself to fix that mess. I've tried to explain kindly why I reject and what to change… but results were poor. The code of conduct doesn't forbid to try, it just doesn't punish giving up.
    • asylteltine 3y ago
      [dead]
• peterfirefly 3y ago
  That's the first sensible code of conduct I have ever read :)