KolibriOS/kolibrios
13
14
Fork 12
Code Issues 113 Pull Requests 16 Actions Projects 1 Releases Wiki Activity

Docs: Added licensing to contributing guide #198

Open
mxlgv wants to merge 1 commits from add-license-file-header-to-guide into main
pull from: add-license-file-header-to-guide
merge into: KolibriOS:main
Conversation 4 Commits 1 Files Changed 3 +12 -1
3 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
CONTRIBUTING.md
View File

@@ -66,6 +66,17 @@ to the end commit message body on a new line.
Use **rebase** to keep your branch up to date.
## Licensing
For new source code files and for existing ones without a license, you need to add the following header to the beginning of the file:
Sweetbread commented 2025-04-15 17:29:24 +02:00
Review
Copy Link

What does "need" mean? SHOULD or MUST I do?

What does "need" mean? SHOULD or MUST I do?
ace-dent commented 2025-04-15 22:12:42 +02:00
Review
Copy Link

Would you be more happy with wording I suggested in #202?

Would you be more happy with wording I suggested in #202?
```asm
; SPDX-License-Identifier: GPL-2.0-only
Sweetbread commented 2025-04-15 17:28:15 +02:00
Review
Copy Link

For what? There's LICENSE file already, so, by fraudulent, every file in this repo under GPLv2

For what? There's LICENSE file already, so, by fraudulent, every file in this repo under GPLv2
👍 1
dunkaist commented 2025-04-17 05:03:11 +02:00
Review
Copy Link

Each program can have its own licence. Sometimes even different files of a program can have different licences if compatible. For example, one kernel file can be GPL2-only while another GPL2+.

Each program can have its own licence. Sometimes even different files of a program can have different licences if compatible. For example, one kernel file can be GPL2-only while another GPL2+.
👍 1
ace-dent commented 2025-04-30 16:35:23 +02:00
Review
Copy Link

I would encourage new code to move towards more permissive licenses, where possible.

I would encourage new code to move towards more permissive licenses, where possible.
; Program - Brief description.
Sweetbread commented 2025-04-15 17:32:18 +02:00
Review
Copy Link

Description of what? Of a program? Should I add a description to each its file?

Description of what? Of a program? Should I add a description to each its file?
ace-dent commented 2025-04-30 16:36:22 +02:00
Review
Copy Link

Yes. Ideally a one line description, where appropriate.

Yes. Ideally a one line description, where appropriate.
; Copyright (C) 2011-2025 KolibriOS team
```
Be careful when setting copyright and date interval. Review the file's history to verify its origin.
## Conclusion
We hope this small instructions will help you to get familiar with KolibriOS contribution rules and inspire you to participate in the life of our project.

0
COPYING.TXT → LICENSE
View File

2
README.md
View File

@@ -1,6 +1,6 @@
# KolibriOS
[![License](https://img.shields.io/badge/License-GPL%202.0-green)](./COPYING.TXT)
[![License](https://img.shields.io/badge/License-GPL%202.0-green)](./LICENSE)
[![Build system](https://git.kolibrios.org/KolibriOS/kolibrios/actions/workflows/build.yaml/badge.svg)](https://git.kolibrios.org/KolibriOS/kolibrios/actions)
KolibriOS is a hobby operating system for x86-compatible computers, which is currently being developed by a small but passionate team of enthusiasts.