Hi all,
we are applying for GSoC again this year
I noticed that http://canopy.mirage.io/tags/help%20needed is totally stale.
Can you please update this and also update it in such a way that
a) The list of mentors is clear, e.g. use a format like
Mentor: name, email address: , IRC handle:
b)
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
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:
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/
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:
> 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
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
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
*
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
*
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
*
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
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
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
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
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 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 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
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
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 m
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
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
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
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
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
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
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 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
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-devel@lists.xenproject.org
Cc: committ...@xenproject.org
---
code-of-conduct.md | 76
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* section
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
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
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
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* section
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 CoC
* Rename
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
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 CoC
* Rename
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
> 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 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 cl
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 cl
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 cl
ry 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) - from a l
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 s
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
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
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 s
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-devel@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
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
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 CoC
* Rename
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
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
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 CoC
* Rename
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.
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 devel
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 devel
> 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.org"
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
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 02/1
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 dr
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
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
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
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
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 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
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
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.org"
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.org"
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 ado
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 ado
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
> I
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 ado
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
> I
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
> I
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, 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, 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 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 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
1 - 100 of 1429 matches
Mail list logo
