Add STYLE_GUIDE.md #202

Open
opened 2025-04-06 18:08:10 +02:00 by ace-dent · 6 comments
Member

We should start to provide a style guide for contributors, ideally in a /docs folder.
It should be linked to from CONTRIBUTING.md.
Attached is a draft, standardising the file header.

If the Guide reaches acceptance/approval, it can also be the basis for introducing CI checks.

Edit: 7-Apr-2025 - Minor tweaks to example file.

We should start to provide a style guide for contributors, ideally in a `/docs` folder. It should be linked to from `CONTRIBUTING.md`. Attached is a draft, standardising the file header. If the Guide reaches acceptance/approval, it can also be the basis for introducing CI checks. Edit: 7-Apr-2025 - Minor tweaks to example file.
ace-dent added the
Kind
Documentation
Priority
Medium
labels 2025-04-06 18:26:41 +02:00
ace-dent added
Priority
Low
and removed
Priority
Medium
labels 2025-04-06 18:45:03 +02:00
Owner

@ace-dent You can formalize this in PR.

@ace-dent You can formalize this in PR.
Author
Member

@mxlgv - I no longer have the ability to create PRs on Gitea. Perhaps you can incorporate into your open PR?

@mxlgv - I no longer have the ability to create PRs on Gitea. Perhaps you can incorporate into your open PR?
Owner

@mxlgv - I no longer have the ability to create PRs on Gitea. Perhaps you can incorporate into your open PR?

@ace-dent Is this a technical problem?

> @mxlgv - I no longer have the ability to create PRs on Gitea. Perhaps you can incorporate into your open PR? @ace-dent Is this a technical problem?
Owner

If you are well versed in licensing, your help would be helpful. I'm very bad at this. For example, I don’t know what to do with new applications. Do I need to add authorship or should everything be an abstract “KolibriOS team”. I also don’t understand in what case a person can add his own copyright to an existing one. Where is the line between fixing a bug and adding some major functionality?

If you are well versed in licensing, your help would be helpful. I'm very bad at this. For example, I don’t know what to do with new applications. Do I need to add authorship or should everything be an abstract “KolibriOS team”. I also don’t understand in what case a person can add his own copyright to an existing one. Where is the line between fixing a bug and adding some major functionality?
Author
Member

I think the Copyright attribution should actually be KolibriOS contributors (e.g. Am I in the 'team'?!).
The use of SPDX-FileCopyrightText is more correct... but if the community strongly prefers standard Copyright lines, thats ok by me.
When to add one's own details to the copyright is a grey area. Lots of resource available online that discuss this. Ultimately I'd suggest we avoid adding more individuals than necessary. If I was writing an app in user space from scratch, I might reasonably want some direct attribution.

I think the Copyright attribution should actually be `KolibriOS contributors` (e.g. Am *I* in the 'team'?!). The use of `SPDX-FileCopyrightText` is more correct... but if the community strongly prefers standard `Copyright` lines, thats ok by me. When to add one's own details to the copyright is a grey area. Lots of resource available online that discuss this. Ultimately I'd suggest we avoid adding more individuals than necessary. If I was writing an app in user space from scratch, I might reasonably want some direct attribution.
Owner

I think the Copyright attribution should actually be KolibriOS contributors (e.g. Am I in the 'team'?!).

I believe, you are free to put either your own copyright or the KolibriOS Project Team copyright. If you decide to describe your code as the code by KolibriOS Project Team then you are considered a part of the team. We can't and shouldn't force people to replace their name with something like 'KolibriOS blah blah'. If a developer implements a feature they should be allowed to put their name on it, I believe.

> I think the Copyright attribution should actually be `KolibriOS contributors` (e.g. Am *I* in the 'team'?!). I believe, you are free to put either your own copyright or the KolibriOS Project Team copyright. If you decide to describe your code as the code by KolibriOS Project Team then you are considered a part of the team. We can't and shouldn't force people to replace their name with something like 'KolibriOS blah blah'. If a developer implements a feature they should be allowed to put their name on it, I believe.
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KolibriOS/kolibrios#202
No description provided.