On Thu, 7 Nov 2019, Lars Kurth wrote:
> Hi all,
>
> I have received informal advice
>
> On 21/10/2019, 06:54, "Artem Mygaiev" wrote:
>
> > Before we ask Xen FuSA contributors to invest in documentation to
> > be presented as legally-valid evidence for certification, we should
> >
Hi all,
I have received informal advice
On 21/10/2019, 06:54, "Artem Mygaiev" wrote:
> Before we ask Xen FuSA contributors to invest in documentation to
> be presented as legally-valid evidence for certification, we should
> ask a certified lawyer for their formal opinion on the
Hi Lars
On Thu, 2019-10-17 at 17:30 +, Lars Kurth wrote:
>
> On 17/10/2019, 18:05, "Rich Persaud" <
> pers...@gmail.com
> > wrote:
>
> On Oct 17, 2019, at 12:55, Stefano Stabellini <
> sstabell...@kernel.org
> > wrote:
> >
> > On Thu, 17 Oct 2019, Rich Persaud wrote:
> >>>
On 17/10/2019, 18:05, "Rich Persaud" wrote:
On Oct 17, 2019, at 12:55, Stefano Stabellini
wrote:
>
> On Thu, 17 Oct 2019, Rich Persaud wrote:
>>> On Oct 17, 2019, at 12:32, Stefano Stabellini
wrote:
>>>
>>> On Thu, 17 Oct 2019, Lars Kurth wrote:
On
On Oct 17, 2019, at 12:55, Stefano Stabellini wrote:
>
> On Thu, 17 Oct 2019, Rich Persaud wrote:
>>> On Oct 17, 2019, at 12:32, Stefano Stabellini
>>> wrote:
>>>
>>> On Thu, 17 Oct 2019, Lars Kurth wrote:
On 16/10/2019, 17:35, "Rich Persaud" wrote:
>> On Oct 15, 2019, at
On Thu, 17 Oct 2019, Rich Persaud wrote:
> On Oct 17, 2019, at 12:32, Stefano Stabellini wrote:
> >
> > On Thu, 17 Oct 2019, Lars Kurth wrote:
> >> On 16/10/2019, 17:35, "Rich Persaud" wrote:
> >>
> On Oct 15, 2019, at 08:27, Lars Kurth wrote:
> >>> ...
> >>>
> >>> My point really was
On Oct 17, 2019, at 12:32, Stefano Stabellini wrote:
>
> On Thu, 17 Oct 2019, Lars Kurth wrote:
>> On 16/10/2019, 17:35, "Rich Persaud" wrote:
>>
On Oct 15, 2019, at 08:27, Lars Kurth wrote:
>>> ...
>>>
>>> My point really was is that due to storing the files in git, we essentially
On Thu, 17 Oct 2019, Lars Kurth wrote:
> On 16/10/2019, 17:35, "Rich Persaud" wrote:
>
> > On Oct 15, 2019, at 08:27, Lars Kurth wrote:
> ...
> >
> > My point really was is that due to storing the files in git, we
> essentially do NOT today do this.
> > So we would need to
On 16/10/2019, 17:35, "Rich Persaud" wrote:
> On Oct 15, 2019, at 08:27, Lars Kurth wrote:
...
>
> My point really was is that due to storing the files in git, we
essentially do NOT today do this.
> So we would need to take extra action: e.g. manually or through tooling
> On Oct 15, 2019, at 08:27, Lars Kurth wrote:
> Hi Rich,
>
On 15 Oct 2019, at 02:58, Rich Persaud wrote:
> On Oct 11, 2019, at 07:11, Lars Kurth wrote:
>>> On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
On Thu, 10 Oct 2019, Lars Kurth wrote:
@Stefano: as you and I
Hi Rich,
> On 15 Oct 2019, at 02:58, Rich Persaud wrote:
>
>> On Oct 11, 2019, at 07:11, Lars Kurth wrote:
>>
>> On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
>>
>>>On Thu, 10 Oct 2019, Lars Kurth wrote:
>>>
>>> @Stefano: as you and I believe Brian will be spending time on
> On Oct 11, 2019, at 07:11, Lars Kurth wrote:
>
> On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
>
>>On Thu, 10 Oct 2019, Lars Kurth wrote:
>> * Would we ever include API docs generated from GPLv2 code? E.g. for safety
>> use-cases?
>> @Stefano, @Artem: I guess this one is for you.
On Oct 11, 2019, at 07:11, Lars Kurth wrote:
>
> On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
>
>>On Thu, 10 Oct 2019, Lars Kurth wrote:
>> * Would we ever include API docs generated from GPLv2 code? E.g. for safety
>> use-cases?
>> @Stefano, @Artem: I guess this one is for you.
>>
On Fri, 11 Oct 2019, Lars Kurth wrote:
> On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
>
> On Thu, 10 Oct 2019, Lars Kurth wrote:
> > * Would we ever include API docs generated from GPLv2 code? E.g. for
> safety use-cases?
> > @Stefano, @Artem: I guess this one is for you.
>
On Fri, 11 Oct 2019, Lars Kurth wrote:
> On 11/10/2019, 09:32, "Jan Beulich" wrote:
>
> On 10.10.2019 20:30, Lars Kurth wrote:
> > On 10/10/2019, 18:05, "Andrew Cooper" wrote:
> > On 10/10/2019 13:34, Lars Kurth wrote:
> > > Existing formats and licenses
> > > *
On 11/10/2019, 09:32, "Jan Beulich" wrote:
On 10.10.2019 20:30, Lars Kurth wrote:
> On 10/10/2019, 18:05, "Andrew Cooper" wrote:
> On 10/10/2019 13:34, Lars Kurth wrote:
> > Existing formats and licenses
> > * Hypercall ABI Documentation generated from Xen
On 11/10/2019, 02:24, "Stefano Stabellini" wrote:
On Thu, 10 Oct 2019, Lars Kurth wrote:
> * Would we ever include API docs generated from GPLv2 code? E.g. for
safety use-cases?
> @Stefano, @Artem: I guess this one is for you.
> I suppose if we would have a similar issue for
Hi Lars
On Thu, 2019-10-10 at 12:34 +, Lars Kurth wrote:
> * Possibly stuff such as
> https://urldefense.com/v3/__https://xenbits.xen.org/docs/unstable/support-matrix.html__;!K6dmGCEab4ueJg!lwAwYJi7cUkbX7CUXnOD9i7laj_9xcyafF714u6PO04tu0CYUKDHWBHAy2XD0mvEiA$
> (which is currently GPL-2,
>
On 10.10.2019 20:30, Lars Kurth wrote:
> On 10/10/2019, 18:05, "Andrew Cooper" wrote:
> On 10/10/2019 13:34, Lars Kurth wrote:
> > Existing formats and licenses
> > * Hypercall ABI Documentation generated from Xen public headers
> > Format: kerndoc
> > License: typically
On Thu, 10 Oct 2019, Lars Kurth wrote:
> * Would we ever include API docs generated from GPLv2 code? E.g. for safety
> use-cases?
> @Stefano, @Artem: I guess this one is for you.
> I suppose if we would have a similar issue for a safety manual
> I am also assuming we would want to use sphinx
On 10/10/2019, 18:05, "Andrew Cooper" wrote:
On 10/10/2019 13:34, Lars Kurth wrote:
> Hi all,
>
> following on from a discussion on IRC and on various other places, I
think we need to try and rationalize how we handle documentation.
>
> What we have now and what we
On 10/10/2019 13:34, Lars Kurth wrote:
> Hi all,
>
> following on from a discussion on IRC and on various other places, I think we
> need to try and rationalize how we handle documentation.
>
> What we have now and what we may get in future
> * http://xenbits.xen.org/docs/unstable/ (GPL-2)
> *
22 matches
Mail list logo
