On 27/01/2020, 14:12, "George Dunlap" wrote:
I have drafted an explicit policy on what is (generally) required to
check a patch in. It's been through several rounds, and v4 has been
acked [1].
I've had informal assent from all committers, but just to dot all our
i's a
Dear community members,
The CfP and Registration for the Xen Project Developer & Design Summit has been
open for a week. This is a quick reminder that the CfP for talks closes on
March 6th.
Information about the CfP can be found here:
https://events.linuxfoundation.org/xen-summit/program/cfp/
> On 23 Jan 2020, at 05:31, Bobby Eshleman wrote:
>
> On Wed, Jan 22, 2020 at 04:27:39PM +0000, Lars Kurth wrote:
>>
>> You should also leverage the developer summit: see
>> https://events.linuxfoundation.org/xen-summit/program/cfp/
>> <https://events.li
> On 22 Jan 2020, at 14:57, Andrew Cooper wrote:
>
> On 22/01/2020 01:58, Bobby Eshleman wrote:
>> Hey everybody,
>>
>> This is an RFC patchset for the very beginnings of adding RISC-V support
>> to Xen. This RFC is really just to start a dialogue about supporting
>> RISC-V and align with the
On 21/01/2020, 21:29, "Rich Persaud" wrote:
On Jan 21, 2020, at 15:58, Marek Marczykowski-Górecki
wrote:
>
> On Wed, Jan 15, 2020 at 04:57:29PM -0500, Rich Persaud wrote:
On Jan 14, 2020, at 21:42, Marek Marczykowski-Górecki
wrote:
>>> Since we have those generate
Apologies,
some of the links I added for convenience do not work
> It should be read in the following order
The correct links are
*
http://xenbits.xenproject.org/gitweb/?p=people/larsk/code-of-conduct.git;a=blob;f=code-of-conduct.md;hb=refs/heads/CoC-v5
*
http://xenbits.xenproject.or
Hi all,
for some time now we have been discussing the Xen Project Code of
Conduct. The most recent set of feedback has been primarily around
minor language issues (US vs UL English, etc.), which indicates to me
that the proposal is ready to be voted on
The final version which addresses all the l
I should have added more people to this change. The issue without this fix is
that entries such as
L: xen-devel
break get_maintainer.pl and thus add_maintainers.pl
Lars
On 10/01/2020, 21:19, "Lars Kurth" wrote:
From: Lars Kurth
Prior to this change e-mail addres
On 15/01/2020, 10:47, "George Dunlap" wrote:
On 1/13/20 9:21 PM, Lars Kurth wrote:
>
>
> On 13/01/2020, 19:54, "George Dunlap" wrote:
>
>
> > On Dec 30, 2019, at 7:32 PM, Lars Kurth
wrote:
On 13/01/2020, 19:54, "George Dunlap" wrote:
> On Dec 30, 2019, at 7:32 PM, Lars Kurth wrote:
>
> From: Lars Kurth
>
> This guide covers the bulk on Best Practice related to code review
> It primarily focusses on code review inter
From: Lars Kurth
Prior to this change e-mail addresses of the form "display name
" would result into empty output. Also see
https://lists.xenproject.org/archives/html/xen-devel/2020-01/msg00753.html
Signed-off-by: Lars Kurth
---
CC: jgr...@suse.com
---
scripts/get_maintainer.pl | 2
Cooper
>> Cc: George Dunlap
>> Cc: Ian Jackson
>> Cc: Jan Beulich
>> Cc: Julien Grall
>> Cc: Konrad Rzeszutek Wilk
>> Cc: Stefano Stabellini
>> Cc: Wei Liu
>> Cc: Lars Kurth
>>
>> Should there be other maintainers apart from myse
On 08/01/2020, 16:52, "Jürgen Groß" wrote:
Just had a chat with Lars on IRC, which might be of common
interest (and Lars asked me to post it to xen-devel):
(17:00:16) juergen_gross: lars_kurth: any idea why
./scripts/add_maintainers.pl would add a "Cc:" without a mail add
maintainer.
[1] See C.2 at
https://cryptpad.fr/pad/#/2/pad/edit/ERZtMYD5j6k0sv-NG6Htl-AJ/
[2] https://keepachangelog.com/en/1.0.0/
Signed-off-by: Paul Durrant
Thank you Paul
Exactly what I was looking for
Reviewed-by: Lars Kurth
___
Hi all,
the deadline for GSoC mentoring orgs is approaching again and I think there is
a good chance we might get in (usually we get in every 3 years and the last
time we got in in 2020). We do however need to get
https://wiki.xenproject.org/wiki/Outreach_Program_Projects into a decent state
P
On 07/01/2020, 08:23, "Durrant, Paul" wrote:
> -Original Message-
> From: Andrew Cooper
> Sent: 07 January 2020 00:26
> To: Lars Kurth ; xen-devel de...@lists.xenproject.org>
> Cc: Rian Quinn ; Daniel P. Smith
> ; Doug Golds
Dear community members,
I hope you all had a restful holiday period and a Happy New Year!
Please send me agenda items for this Thursday's community call (we agreed to
move it by 1 week) preferably by Wednesday!
A draft agenda is at
https://cryptpad.fr/pad/#/2/pad/edit/ERZtMYD5j6k0sv-NG6Htl-A
On 06/01/2020, 07:25, "Jürgen Groß" wrote:
>+## Issue: Small functional issues
>+
>+The most common area of disagreements which happen in code reviews, are
>+differing opinions on whether small functional issues in a patch series
have to
>+be resolved or not before the cod
From: Lars Kurth
This guide covers the bulk on Best Practice related to code review
It primarily focusses on code review interactions
It also covers how to deal with Misunderstandings and Cultural
Differences
Changes since v3
* Fixed typo
Changes since v2 (added in v2)
* Fix typos
* Extended
From: Lars Kurth
This document is a portal page that lays out our gold standard,
best practices for some common situations and mechanisms to help
resolve issues that can have a negative effect on our community.
Detail is covered in subsequent documents
Changes since v3
- Also changes the TODO
From: Lars Kurth
This series proposes a concrete version of the Xen Project
CoC based on v1.4 of the Contributor Covenant. See [1]
Closing the discussion
==
I think we are at the point where we are ready to publish our guidance.
Feedback has been minor since the last version
From: Lars Kurth
This document highlights what reviewers such as maintainers and committers look
for when reviewing code. It sets expectations for code authors and provides
a framework for code reviewers.
Changes since v3
* Added example under *Workflow from a Reviewer's Perspective* se
From: Lars Kurth
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen-...@lists.xenproject.org
Cc: win-pv-de...@lists.xenproject.org
Cc: mirageos-de...@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 76
From: Lars Kurth
This guide provides Best Practice on identifying and resolving
common classes of disagreement
Changes since v3
* Fixed broken http link (typo)
Changes since v2 (added in v2)
* Fix typos
* Add section: "Issue: Multiple ways to solve a problem"
* Changed line wrap
From: Lars Kurth
No content changes
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen-...@lists.xenproject.org
Cc: win-pv-de...@lists.xenproject.org
Cc: mirageos-de...@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 62
From: Lars Kurth
Specific changes to the baseline:
* Replace list of positive behaviors with link to separate process
* Replace maintainers with project leadership
(except in our pledge where maintainers is more appropriate)
* Add 'of all sub-projects' to clarify scope of Co
> On 19 Dec 2019, at 09:56, Jan Beulich wrote:
>
> On 18.12.2019 18:09, Lars Kurth wrote:
>>
>>
>> On 18/12/2019, 14:29, "Julien Grall" wrote:
>>
>>Hi Lars,
>>
>>On 12/12/2019 21:14, Lars Kurth wrote:
>>> +
On 18/12/2019, 14:29, "Julien Grall" wrote:
Hi Lars,
On 12/12/2019 21:14, Lars Kurth wrote:
> +### Workflow from an Author's Perspective
> +
> +When code authors receive feedback on their patches, they typically
first try
> +to c
ancillary files, and adjust COPYING to match.
Signed-off-by: Andrew Cooper
---
CC: Ian Jackson
CC: Wei Liu
CC: Lars Kurth
This wants backporting to 4.13 as soon as practical.
Reviewed-by: Lars Kurth (lars.ku...@citrix.com)
Hi all,
now that 4.13 is out of the way I wanted to get the CoC discussion closed - see
https://lists.xenproject.org/archives/html/xen-devel/2019-12/threads.html#00926,
which means I need ACKs or final suggestions. The next step would be to
publish it on the website.
However, I have also been
> +Xen-Version: 4.13
> +Initial-Release: 2019-12-18
> +Supported-Until: 2021-06-18
That looks good to me: 18 months
> +Security-Support-Until: 2022-12-18
That looks good to me: 36 months
Reviewed-by: Lars Kurth mailto:lars.ku...@citrix.com>>
Regards
Lars_
From: Lars Kurth
This guide provides Best Practice on identifying and resolving
common classes of disagreement
Changes since v2 (added in v2)
* Fix typos
* Add section: "Issue: Multiple ways to solve a problem"
* Changed line wrapping to 80 characters
* Replaced inline style
From: Lars Kurth
This guide covers the bulk on Best Practice related to code review
It primarily focusses on code review interactions
It also covers how to deal with Misunderstandings and Cultural
Differences
Changes since v2 (added in v2)
* Fix typos
* Extended "Verbose vs. terse&quo
From: Lars Kurth
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen-...@lists.xenproject.org
Cc: win-pv-de...@lists.xenproject.org
Cc: mirageos-de...@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 76
From: Lars Kurth
This series proposes a concrete version of the Xen Project
CoC based on v1.4 of the Contributor Covenant. See [1]
It tries to address all elements in the v2 review, which raised
a number of hard questions. One of the main outstanding items
were good examples for cover letters
From: Lars Kurth
Specific changes to the baseline:
* Replace list of positive behaviors with link to separate process
* Replace maintainers with project leadership
(except in our pledge where maintainers is more appropriate)
* Add 'of all sub-projects' to clarify scope of Co
From: Lars Kurth
This document highlights what reviewers such as maintainers and committers look
for when reviewing code. It sets expectations for code authors and provides
a framework for code reviewers.
Changes since v2 (introduced in v2)
* Extend introduction
* Add "Code Review Wor
From: Lars Kurth
This document is a portal page that lays out our gold standard,
best practices for some common situations and mechanisms to help
resolve issues that can have a negative effect on our community.
Detail is covered in subsequent documents
Changes since v2 (introduced in v2
From: Lars Kurth
No content changes
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen-...@lists.xenproject.org
Cc: win-pv-de...@lists.xenproject.org
Cc: mirageos-de...@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 56
And this time with the correct list. Really despairing with Outlook which keeps
adding random old contacts to my address book and puts them in front of
frequently used entries (sigh)
From: Lars Kurth
Date: Wednesday, 11 December 2019 at 10:31
To: "xen-de...@lists.xensource.com" ,
&q
> On 9 Dec 2019, at 11:02, Lars Kurth wrote:
>
>
>
> On 06/12/2019, 09:51, "Jan Beulich" <mailto:jbeul...@suse.com>> wrote:
>
>On 06.12.2019 00:41, Lars Kurth wrote:
>> I propose to add the following section to code-review-guide.md
>&g
On 06/12/2019, 09:51, "Jan Beulich" wrote:
On 06.12.2019 00:41, Lars Kurth wrote:
> I propose to add the following section to code-review-guide.md
>
>
> ## Problematic Patch Reviews
>
> A typical waterfall software development pr
> On 6 Dec 2019, at 14:21, Andrew Cooper wrote:
>
> On 03/12/2019 09:17, George Dunlap wrote:
>>
>>> On Dec 2, 2019, at 5:01 PM, Konrad Rzeszutek Wilk
>>> wrote:
>>>
>>> On Mon, Dec 02, 2019 at 03:55:04PM +, Andrew Cooper wrote:
On 02/12/2019 15:53, Konrad Rzeszutek Wilk wrote:
>>>
From: Lars Kurth
Date: Thursday, 28 November 2019 at 19:39
To: Rich Persaud
Cc: 'Jan Beulich' , "lars.ku...@xenproject.org"
, Stefano Stabellini ,
"xen-...@lists.xenproject.org" ,
"minios-de...@lists.xenproject.org" ,
"committ...@xenproject
Hi all,
the minutes are at
https://cryptpad.fr/pad/#/2/pad/view/T-vK-ZiXDrnpve64l4hvP+evA5najcmoxOOVJ8TGeBs/
and attached
There were a few items, where the connection was bad and where I am missing
things
ACTIONS and everything important are marked in red
The next meeting is on Jan 9, not Jan 2
x27;t have a data
connection via 4G either. In any case, this is just a quick note: most likely
all will work as usual.
Best Regards
Lars
On 03/12/2019, 06:21, "Lars Kurth" wrote:
Correction: the meeting is this Thursday, the 5th
Apologies for the typo
Lars
On
Correction: the meeting is this Thursday, the 5th
Apologies for the typo
Lars
On 02/12/2019, 20:05, "Lars Kurth" wrote:
Dear community members,
please send me agenda items for this Friday’s community call (sorry for the
late notice, I was on PTO last week). A draft ag
Dear community members,
please send me agenda items for this Friday’s community call (sorry for the
late notice, I was on PTO last week). A draft agenda is at
https://cryptpad.fr/pad/#/2/pad/edit/PCtBphoXkCTiXABJ8cdL0KuZ/
Please add agenda items to the document or reply to this e-mail
@Juerge
On 28/11/2019, 12:50, "Stefano Stabellini" wrote:
On Thu, 28 Nov 2019, Jan Beulich wrote:
> On 28.11.2019 01:56, Stefano Stabellini wrote:
> > On Thu, 26 Sep 2019, Lars Kurth wrote:
> > I think a good recommendation would be for the contributor to
On 28/11/2019, 12:12, "Rich Persaud" wrote:
On Nov 28, 2019, at 05:12, Jan Beulich wrote:
>
> On 28.11.2019 01:54, Stefano Stabellini wrote:
>>> On Thu, 26 Sep 2019, Lars Kurth wrote:
>>> From: Lars Kurth
>>>
>>
On 27/11/2019, 18:56, "Stefano Stabellini" wrote:
On Thu, 26 Sep 2019, Lars Kurth wrote:
> From: Lars Kurth
>
> This guide provides Best Practice on identifying and resolving
> common classes of disagreement
>
> Signed-off-by: L
From: Rich Persaud
Date: Thursday, 28 November 2019 at 12:21
To: Lars Kurth
Cc: 'Jan Beulich' , "lars.ku...@xenproject.org"
, Stefano Stabellini ,
"xen-...@lists.xenproject.org" ,
"minios-de...@lists.xenproject.org" ,
"committ...@xenproject
On 27/11/2019, 19:06, "Stefano Stabellini" wrote:
On Fri, 27 Sep 2019, Jan Beulich wrote:
> On 26.09.2019 21:39, Lars Kurth wrote:
> > +### Verbose vs. terse
> > +Due to the time it takes to review and compose code reviewer,
reviewers often adopt a
On 27/11/2019, 18:57, "Stefano Stabellini" wrote:
On Thu, 26 Sep 2019, Lars Kurth wrote:
> From: Lars Kurth
>
> This guide covers the bulk on Best Practice related to code review
> It primarily focusses on code review interactions
> It als
On 28/11/2019, 07:37, "Jan Beulich" wrote:
On 28.11.2019 14:06, Lars Kurth wrote:
> I can certainly add something on the timing , along the lines of
> * For complex series, consider the time it takes to do reviews (maybe
with a guide of LOC per hour) and give
On 28/11/2019, 04:09, "Jan Beulich" wrote:
On 28.11.2019 01:54, Stefano Stabellini wrote:
> On Thu, 26 Sep 2019, Lars Kurth wrote:
>> From: Lars Kurth
>>
>> This document highlights what reviewers such as maintainers and
committers look
On 29/10/2019, 12:41, "Stefano Stabellini" wrote:
On Tue, 29 Oct 2019, Julien Grall wrote:
> On 28/10/2019 21:43, Stefano Stabellini wrote:
> > On Mon, 28 Oct 2019, Julien Grall wrote:
> >> Hi,
> >>
> >> On 25/10/2019 11:31, Jan Beulich wrote:
> >>> All,
> >>>
On 25/11/2019, 09:10, "Jan Beulich" wrote:
All,
the 4.12.2 stable release is due in about 2 weeks time. Please point
out backporting candidates that you find missing from the respective
stable trees.
Jan
Hi all:
I ran the XSA scripts and all is fine. BreaT
Adding,
Artem as this is potentially of interest to the FuSa group?
Lars
> On 14 Nov 2019, at 13:33, Jeff Kubascik wrote:
>
> Hello,
>
> I'm working on a port of a RTOS (RTEMS) to Xen on ARM, and came across an
> interesting finding in how Xen emulates the physical timer on ARM.
>
> In testin
On 15/11/2019, 05:26, "Durrant, Paul" wrote:
> -Original Message-
> From: Lars Kurth
> Sent: 07 November 2019 22:30
> To: xen-devel ; Juergen Gross
>
> Cc: committ...@xenproject.org; Durrant, Paul ; Brian
> Woods
On 12/11/2019, 11:10, "Stefano Stabellini" wrote:
On Tue, 12 Nov 2019, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [Xen-devel] [PATCH] Introduce a description
of a new optional tag for Backports"):
> > Should we describe the Fixes: tag as well? These would have a similar
On 11/11/2019, 11:03, "Stefano Stabellini" wrote:
On Mon, 11 Nov 2019, Lars Kurth wrote:
> On 11/11/2019, 08:12, "George Dunlap" wrote:
>
> On 11/8/19 7:09 PM, Stefano Stabellini wrote:
> > Signed-off-by: Stefano Stabellini
On 11/11/2019, 08:12, "George Dunlap" wrote:
On 11/8/19 7:09 PM, Stefano Stabellini wrote:
> Signed-off-by: Stefano Stabellini
> CC: jbeul...@suse.com
> CC: george.dun...@citrix.com
> CC: jul...@xen.org
> CC: lars.ku...@citrix.com
> CC: andrew.coop...@citrix.com
Hi all,
minutes are attached or at
https://cryptpad.fr/pad/#/2/pad/view/7l3a4mhZTU4xs0GE415OXiAj0ScKl39xdQ9wm0cwASs/embed/present/
Regards
Lars
On 07/11/2019, 07:24, "Lars Kurth" wrote:
Hi all,
quick reminder re agenda items. What I have so far is at
https://cryptpad.
Dear Community Members,
Juergen will be stepping down as Release Manager after Xen 4.13 has been
delivered, following the 4.11 and 4.12 release. Release managers prior to
Juergen were Julien Grall, Konrad Wilk, Wei Liu and George Dunlap. We are
looking for active community members to follow in
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 v
23:00 - 01:00 CST (Beijing)
Further International meeting times:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=11&day=7&hour=16&min=0&sec=0&p1=224&p2=24&p3=179&p4=136&p5=37&p6=33
Best Regards
Lars
On 07/11/2019, 07:24,
ics such as state of XSM, DomB
proposal as a secure means to start an L0/L1 configuration, KCONFIG for L0
version of Xen, etc.
Citrix will host, but others are welcome to join (please contact Lars for
logistics)
Feel free to request additional items
Regards
Lars
On 04/11/2019, 05:37, &qu
Dear community members,
please send me agenda items for next week’s community call. A draft agenda is
at https://cryptpad.fr/pad/#/2/pad/edit/SkeU+Z5J9WIIU9ZsXlojiXcQ/
Please add agenda items to the document or reply to this e-mail
Note that I am on PTO today and tomorrow
Last month’s minutes
Hi all,
I am wondering whether we should tag livepatch-build-tools.git with Xen releases
Best Regards
Lars
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 24/10/2019, 12:22, "Wei Liu" wrote:
On Thu, Oct 24, 2019 at 01:13:13PM +0200, Jürgen Groß wrote:
> On 24.10.19 13:06, Wei Liu wrote:
> > Blktap2 is gone.
> >
> > Signed-off-by: Wei Liu
> > ---
> > CONTRIBUTING | 1 -
> > 1 file changed, 1 deletion(-)
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 Oc
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. manua
for a long time.
Best Regards
Lars Kurth
Xen Project Community Manager
Chairman of Xen Project Advisory Board
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
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:
>>>
>>
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
> > * Hypercal
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
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.
>
> Wha
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)
* http://xenbits.xen.org/docs/sphinx-unstable-staging/ (CC
> On 7 Oct 2019, at 11:01, Ian Jackson wrote:
>
> Hi. Thanks for the message.
>
> Just one thing I wanted to reply to in your mail:
>
> YOUNG, MICHAEL A. writes ("Re: [Xen-devel] [PATCH] read grubenv and set
> default from saved_entry or next_entry [and 1 more messages]"):
>> On Wed, 11 Sep
On 03/10/2019, 21:56, "Andrew Cooper" wrote:
Creative Commons is a more common license than GPL for documentation
purposes.
Switch to using CC-BY-4.0 to explicitly permit re-purposing and remixing of
the content.
Signed-off-by: Andrew Cooper
Reviewed-by:
On 03/10/2019, 21:59, "Andrew Cooper" wrote:
Put together an introduction page for the Sphinx/RST docs, along with a
glossary which will accumulate over time.
Signed-off-by: Andrew Cooper
Reviewed-by: Lars Kurth
There were a few minor improvements which could
On 03/10/2019, 21:56, "Andrew Cooper" wrote:
Sphinx, its linters, and RST modes in common editors, expect 3 spaces of
indentation. Some bits already conform to this expectation. Update the
rest to match.
Signed-off-by: Andrew Cooper
Reviewed-by:
https://global.gotomeeting.com/install/133463709
Regards
Lars
On 27/09/2019, 14:56, "Lars Kurth" wrote:
Hi all,
the proposed agenda is in
https://cryptpad.fr/pad/#/2/pad/edit/4FGEw81flPUiivkjkuvQJ-CK/embed/present/and
you can edit to add items
Alternatively, you can rep
On 07/10/2019, 13:29, "Andrew Cooper" wrote:
On 07/10/2019 13:01, Lars Kurth wrote:
>
> On 03/10/2019, 21:56, "Andrew Cooper" wrote:
>
> Creative Commons is a more common license than GPL for documentation
purposes.
> Swit
On 03/10/2019, 21:56, "Andrew Cooper" wrote:
Creative Commons is a more common license than GPL for documentation
purposes.
Switch to using CC-BY-4.0 to explicitly permit re-purposing and remixing of
the content.
Signed-off-by: Andrew Cooper
---
CC:
On 07/10/2019, 12:06, "George Dunlap" wrote:
On 9/26/19 8:39 PM, Lars Kurth wrote:
> From: Lars Kurth
>
> Signed-off-by: Lars Kurth
> ---
> Cc: minios-de...@lists.xenproject.org
> Cc: xen-...@lists.xenproject.org
> Cc: wi
On 07/10/2019, 10:01, "Wei Liu" wrote:
On Mon, 7 Oct 2019 at 09:13, Lars Kurth wrote:
>
>
>
> On 04/10/2019, 09:57, "Wei Liu" wrote:
>
> On Thu, Oct 03, 2019 at 04:12:30PM +, Lars Kurth wrote:
>
On 04/10/2019, 09:57, "Wei Liu" wrote:
On Thu, Oct 03, 2019 at 04:12:30PM +0000, Lars Kurth wrote:
> Specifically
> * xen.org to xenproject.org
> * http to https
> * Replaced pages where page has moved
> (including on xen pages
Specifically
* xen.org to xenproject.org
* http to https
* Replaced pages where page has moved
(including on xen pages as well as external pages)
* Removed some URLs (e.g. downloads for Linux PV drivers)
Tested-by: Lars Kurth
Signed-off-by: Lars Kurth
---
docs/man/xen-pci-device-reservations
Hi all,
the proposed agenda is in
https://cryptpad.fr/pad/#/2/pad/edit/4FGEw81flPUiivkjkuvQJ-CK/embed/present/and
you can edit to add items
Alternatively, you can reply to this mail directly
Agenda items appreciated a few days before the call: please put your name
besides items if you edit the
> On 9 Sep 2019, at 15:44, Lars Kurth wrote:
>
> Hello everyone,
>
> Olivier had posted an RFC for this proposal on xen-devel@- see
> https://xen.markmail.org/thread/ermnrb3ps3okvnjr
> <https://xen.markmail.org/thread/ermnrb3ps3okvnjr>
>
> The propos
On 27/09/2019, 11:17, "Lars Kurth" wrote:
On 27/09/2019, 10:14, "Jan Beulich" wrote:
On 26.09.2019 21:39, Lars Kurth wrote:
> +### Verbose vs. terse
> +Due to the time it takes to review and compose code reviewer
On 27/09/2019, 10:14, "Jan Beulich" wrote:
On 26.09.2019 21:39, Lars Kurth wrote:
> +### Verbose vs. terse
> +Due to the time it takes to review and compose code reviewer, reviewers
often adopt a
> +terse style. It is not unusual to see review comments su
On 27/09/2019, 09:59, "Jan Beulich" wrote:
On 26.09.2019 21:39, Lars Kurth wrote:
> +### Express appreciation
> +As the nature of code review to find bugs and possible issues, it is
very easy for
> +reviewers to get into a mode of operation where the p
From: Lars Kurth
This series proposes a concrete version of the Xen Project
CoC based on v1.4 of the Contributor Covenant. See [1]
It contains *ALL* the portions I was still going to add.
I spent a bit of time on word-smithing, but I am not a native English speaker
So there is probably time for
From: Lars Kurth
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen-...@lists.xenproject.org
Cc: win-pv-de...@lists.xenproject.org
Cc: mirageos-de...@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 76
From: Lars Kurth
Specific changes to the baseline:
* Replace list of positive behaviors with link to separate process
* Replace maintainers with project leadership
(except in our pledge where maintainers is more appropriate)
* Add 'of all sub-projects' to clarify scope of Co
From: Lars Kurth
This guide covers the bulk on Best Practice related to code review
It primarily focusses on code review interactions
It also covers how to deal with Misunderstandings and Cultural
Differences
Signed-off-by: Lars Kurth
---
Cc: minios-de...@lists.xenproject.org
Cc: xen
From: Lars Kurth
This document is a portal page that lays out our gold standard,
best practices for some common situations and mechanisms to help
resolve issues that can have a negative effect on our community.
Detail is covered in subsequent documents
Signed-off-by: Lars Kurth
---
Cc: minios
1 - 100 of 497 matches
Mail list logo
