Re: [Xen-devel] Xen ARM community call Tuesday 13th February 5PM UTC

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

>     As we do not have Jira access, it would be better to do it on Wiki or     
>  "something else".
The project has Jira access and can give selected community members write access
Read access is not an issue
Lars

On 06/02/2018, 11:22, "Artem Mygaiev" <artem_mygaiev@xxxxxxxx> wrote:

    Hi Lars
    
    As we do not have Jira access, it would be better to do it on Wiki or 
    "something else".
    
      -- Artem
    
    On 06.02.18 12:53, Lars Kurth wrote:
    > Adding Rich
    > 
    >> I think it would be hugely beneficial if there could be an open
    >> repository of information that describes in clear terms what the
    >> specific engineering items are which are needed to make Xen viable for
    >> assessment towards safety certification.
    > Very good idea
    > 
    > If there is agreement, I can volunteer to set up such a repository: 
options for tracking are
    > *Our Atlassian Jira instance (maybe a new area specifically for this 
purpose)
    > * Wiki page
    > * Something else
    > 
    > Lars
    > 
    > On 06/02/2018, 10:26, "Robin Randhawa" <robin.randhawa@xxxxxxx> wrote:
    > 
    >      Hi Julien.
    >      
    >      Thanks for looping me in.
    >      
    >      On Tue, 2018-02-06 at 10:11 +0000, Julien Grall wrote:
    >      > Hi all,
    >      >
    >      > I would suggest to have the next community call on Tuesday 13th
    >      > February
    >      > 5pm GMT. Does it sound good?
    >      
    >      I'm out of office from the 8th to the 16th unfortunately.
    >      
    >      > Do you have any specific topic you would like to discuss?
    >      
    >      From my side:
    >      
    >      I've spoken to a fair number of folks on the To list here in 1-1
    >      discussions about this.
    >      
    >      I think it would be hugely beneficial if there could be an open
    >      repository of information that describes in clear terms what the
    >      specific engineering items are which are needed to make Xen viable 
for
    >      assessment towards safety certification.
    >      
    >      I'm not a Xen expert by any measure but off the top I recall that one
    >      item was the task of removing the reliance on the Linux kernel for
    >      Dom0.
    >      
    >      I am certain there are more.
    >      
    >      The motivation behind this is to spur folks into acknowledging the
    >      technical work that remains to be done. Whether that work then 
happens
    >      behind closed proprietary doors to generate value or in the open is 
an
    >      implementation detail.
    >      
    >      If nothing else - it would definitely act as an accelerator.
    >      
    >      Personally, I would be thrilled if there was enough momentum to 
openly
    >      massage Xen into the shape that I allude to. If that takes things 70%
    >      ahead with the remaining 30% done by misc Xen commercial entities as
    >      their differentiation value add - that's a huge bonus for the 
ecosystem
    >      and for the future of Xen.
    >      
    >      Thanks!
    >      Robin
    >      
    >      
    >      IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
    >      
    > 
    

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel