Re: Calling for agenda items: July 14th Xen Project FuSa SIG meeting

[Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>]

On Wed, 8 Jul 2020, Kate Stewart wrote:
> On Wed, Jul 8, 2020 at 12:47 PM Nathalie Chan King Choy <nathalie@xxxxxxxxxx> 
> wrote:
> 
>       Hi all,
> 
>        
> 
>       Calling for agenda items for next Tuesday’s Xen FuSa SIG call.
> 
>        
> 
>       Please note:
> 
>       Regarding the password and/or waiting room requirement that Zoom was 
> planning to roll out in July, that has been postponed
>       until September.  So, no change to the process for joining the Zoom 
> call at this time.
> 
>        
> 
>       Outstanding action items from prior calls. Please let me know if you 
> have updates in the status/completion of them:
> 
>        o  ISO 26262
>            o  Artem: Will reach out to David
>            o  Artem: Submit sessions on code/issue/feature archaeology & bug 
> tracker for Xen Summit
>        o  Tracking patch series
>            o  Stefano S: I can ask George about his take. Maybe can schedule 
> a special Community call before April to discuss issue &
>               patch tracking b/c may take a whole hour.
>            o  Artem: If not having an earlier Community call, start 
> discussion about issue & patch tracking on xen-devel
>        o  Doorstop
>            o  Stefano S: I can try to link w/ Doorstop
>        o  Fusa doc repository
>            o  Stefano S: Add links to documentation on how to use git in the 
> readme
>            o  Stefano S: Email Kate to see if she knows how Linux kernel has 
> solved reverse linking problem for kernel certification.
> 
> Not sure which reverse linking is being discussed...  V model to 
> requirements,   or linking of evidence to the standards clauses?    Can
> you please clarify? 

Hi Kate,

We were discussing how to link the documents to relevant code (e.g.
header files under xen.git) and the code to the documents under the
new separate repository.

At the moment we are working on documents for backware-compatible
interfaces that rarely change so it is a relatively easy problem to
solve because we don't expect many changes on the xen.git side.
However, if we were working on documents for interfaces that change more
often things would be different.

Eventually we came up with the idea of introducing a special header in
the document under the new repository with a "link" to the original
code, but we have no reverse link (no link from the code to the doc, but
again in these cases the code is not expected to change.)

See for instance:


.. #########################################################
.. version: $Id$
.. src: xen/include/public/vcpu.h@RELEASE-4.13.0
.. #########################################################


https://gitlab.com/xen-project/fusa/-/blob/master/hypercalls/runstate.rst