[WIP] Open Source Development Best Practices base for discussion #16
Conversation
Signed-off-by: Philipp Ahmann <[email protected]>
| # Literature and references for open source development process | ||
|
|
||
| ## Linux Kernel | ||
|
|
There was a problem hiding this comment.
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.
… wiki Signed-off-by: Philipp Ahmann <[email protected]>
|
Input from https://github.com/elisa-tech/wg-systems/wiki/Systems-WG-development-process should be reflected also in this PR work. |
Signed-off-by: Philipp Ahmann <[email protected]>
Signed-off-by: Philipp Ahmann <[email protected]>
pahmann
force-pushed
the
pahmann-oss-dev-process-draft
branch
from
584a82d to
270793b
Compare
Signed-off-by: Philipp Ahmann <[email protected]>
Signed-off-by: Philipp Ahmann <[email protected]>
There was a problem hiding this comment.
As discussed in last week meeting, ISO-PAS 8926 is not an example of Good Practices standardization but it is effectively an annex to the ISO 26262 2nd ed. and hence it should be eventually mentioned in the last row.
Instead of ISO-PAS 8926, in that row, I think we can put "A guide to the Kernel Development Process"[1], that is the de-facto process used to develop the Linux Kernel today
[1] https://docs.kernel.org/process/development-process.html
Thoughts on open source development best practices.