File header comment suggestions (copywrite, license)

[natebass]

I am wondering if I should add a comment at the top of each file in https://github.com/Project-ACT/be-graph-local-py and what it should contain.

As an example, Project-ACT/ov-tessellation includes at the top of each file:

• Copyright (C) 2024 Project-ACT
• This file is part of ov-tessellation.
• Short description that ov-tessellation is licensed under GPL
• Short description of warranty
• Link to GPL

Should every file have a copywrite to Project-ACT?

If you wanted to get specific to a person, can a file have a copywrite to the individual person? I remember hearing that you could grant access to your own code explicitly to a repository. The project license would still apply because it follows with "This project is apart of be-graph-local" ⤷ "be-graph-local is licensed under the GPL".

If there are individuals with their own copywrite, would we have to list them all in a CONTRIBUTORS file?

[DanHugoDanHugo]

Please see
https://www.gnu.org/licenses/gpl-howto.html

Some licenses require inclusion of the license text (GPL…), others are less stringent. The exciting world of intellectual property.

Always check the Contributing Guidelines for any particular organization/repository concerning specifics, especially assignments and grant-backs.