Release-Checklist icon indicating copy to clipboard operation
Release-Checklist copied to clipboard

Update discussion of adding a CONTRIBUTING.md file

Open robrwo opened this issue 7 months ago • 3 comments

The discussion about CONTRIBUTING.md is about code style consistency.

This is fairly minor.

More important issues to discuss in a how-to-contribute document are:

  • Users should be required to identify where code has come from (written by them, based on other software, generative AI or other tools).
  • Will code created using generative AI be accepted?
  • If the code is based on other software, are there license restrictions?

robrwo avatar Apr 21 '25 14:04 robrwo

I agree that these should also be noted, but I disagree that these are more important.

It is extremely hard to contribute to inconsistent code, which might be a reason for patches to linger till the end-of-time. Inconsistent code also causes unneeded forks

I will add your notes though

Tux avatar Apr 22 '25 06:04 Tux

Do you have a suggestion to reflect those license issues in https://github.com/Tux/Release-Checklist/blob/master/Checklist.md#license?

Tux avatar Apr 22 '25 08:04 Tux

If code (even part of the code from a patch, or a snippet that you have used) is based on other software, does that software have a compatible license?

If code (even part of the code from a patch or snippet that you have used) is AI-generated, then is it compatible with your license? Note discussion in the Servo project about this https://book.servo.org/contributing.html

robrwo avatar Apr 22 '25 09:04 robrwo