Skip to content

[WIP] Open Source Development Best Practices base for discussion #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
+1,052 −0
Open

[WIP] Open Source Development Best Practices base for discussion #16

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
9c97aa6
First commit to trigger discussion in the working group
pahmann Aug 26, 2024
2c8142b
Added content and references from the original proposal in systems WG…
pahmann Aug 27, 2024
a66669d
Taking in sections from the gdoc objective
pahmann Sep 2, 2024
270793b
Add illustrations
pahmann Nov 11, 2024
b8973c5
Add literature and figures into process readme
pahmann Nov 12, 2024
d785373
Fix wrong alt-text for image
pahmann Nov 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions Documentation/processes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Introduction

# Literature and references for open source development process

## Linux Kernel

Copy link
Collaborator Author

@pahmann pahmann Aug 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments from Systems WG meeting.

What are the kernel development processes which map towards quality aspects.
Process clear how to change the runtime code.

What is the Kernel specification. To what extend it documented (man pages, guidelines, doc header, kernel contribution guideline, ...)

Proposal:
Start looking at the guideline. (There are guidelines on the documentation.)
But the guideline may not be very well met.
After gap identification we can consider to improve it.

## From academia

# Code first/centric development process

## Ideation phase

## Requirements and change management
![Change request open source flow](process-model.drawio.svg)


# Typical Work products from traditional standards

## Open Source projects with standard compliance (argumentation)

### Open source projects under foundations

- Zephyr project [add link]
- Xen project [add link]
-

### Examples from "Company owned" open source projects

- L4Re (originator Kernkonzept GmbH) [product page](https://www.kernkonzept.com/l4re-operating-system-framework/)
- ThreadX (originator Microsoft, now under Eclipse) [project page](https://threadx.io/)
-

### Standards/Initiaives supporting code first and CI/CD driven development

- ISO/PAS 8926 [add link]

# Best practices and examples from open source projects

Remark: This work has its origin in the [Systems WG development process wiki](https://github.com/elisa-tech/wg-systems/wiki/Systems-WG-development-process)
Loading