Post ATIovXTGbMYMUT2tdo by silmathoron@floss.social
 (DIR) More posts by silmathoron@floss.social
 (DIR) Post #ATIovXTGbMYMUT2tdo by silmathoron@floss.social
       2023-03-05T09:58:55Z
       
       0 likes, 2 repeats
       
       Are there best practices to list contributors to an open-source project?Like a basic CONTRIBUTORS file?And (how) do you differentiate between authors and contributors, especially for copyright notices in the file headers, do you use a "copyright: {package_name} authors/contributors" that refers to that author/contributor list?How does this interact with tools like a Developer Certificate of Origin?#FOSS #FLOSS #REUSE #license #fediQuestion #askFedi #DCO
       
 (DIR) Post #ATIovYE3nNz2pawGZs by strypey@mastodon.nzoss.nz
       2023-03-05T10:29:04Z
       
       0 likes, 0 repeats
       
       @silmathoron>  do you differentiate between authors and contributors, especially for copyright noticesIANAL but as I understand it, whoever writes each piece of code is its author and holds the  copyright, unless and until they reassign that copyright (eg to a legal person acting as steward of the project). AFAIK Linux doesn't require copyright assignment for kernel contributions, so maybe see how they do their copyright notice?