Hi Lukas,
And I will not have time for write-up of this conclusion of this email thread before and
during the workshop. I have enough action items from this email thread to have a
productive week of writing.
In the context of the "White Paper" topic that we have in the Sync telcos, maybe we (you)
should consider just what we ultimately want to do with this discussion and those that follow.
Will this be published to the Linux Community, or the public at large?
Should it be available in html format for inclusion in a website or a wiki and/or in pdf for publication?...
Or should it be a publication in some journal?
At least I'd suggest that you start a separate document for the (general, user?) development process.
Cheers
John
PS... and maybe you could answer on that thread and describe your publication use case, hint, hint....
Mit freundlichen Grüßen / Best regards
John MacGregor
Safety, Security and Privacy (CR/AEX4)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +49 711 811-42995 | Mobil +49 151 543 09433 | John.MacGregor@...
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller
-----Original Message-----
From: Lukas.Bulwahn@... <Lukas.Bulwahn@...>
Sent: Freitag, 15. Mai 2020 08:23
To: MacGregor John (CR/ADT4) <John.MacGregor@...>
Cc: development-process@...
Subject: AW: [development-process] "Pseudo-DIA" between the Linux Kernel
Development Community and its Users - 2/5 We're talking about an Operating
System here
Hi John,
Yes, but there is an interface between the downstream integrator and
the kernel community (between 1. and 2.&3.). Is a DIA needed for
that or
something else?
(See discussion above).
If we resolved the one point above, we have enough material to
document this email thread in report form, and see where it fits
into the description of a reference process.
I think we're d'accord for this thread. I might want to revisit
exactly what a DIA is, but I'd foreseen that for the 5th veil.. where
the DIA is standing in all its beauty in front of us....
Hopefully I'll remember it then. On to the 3rd veil, although I'm not
sure that it makes sense before the workshop.
And I will not have time for write-up of this conclusion of this email thread before and
during the workshop. I have enough action items from this email thread to have a
productive week of writing.
I would love to see at least short "Acked-by: XYZ <xyz@...>" from some
others on the mailing list that we document the development process at large and
the interfaces and scope is valuable, and roughly correct to their understanding.
Lukas
