From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4B94FA034C; Tue, 18 Jan 2022 15:30:47 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CE10842720; Tue, 18 Jan 2022 15:30:46 +0100 (CET) Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com [209.85.161.50]) by mails.dpdk.org (Postfix) with ESMTP id C9C2C42720 for ; Tue, 18 Jan 2022 15:30:44 +0100 (CET) Received: by mail-oo1-f50.google.com with SMTP id b15-20020a4a878f000000b002dccc412166so6029928ooi.11 for ; Tue, 18 Jan 2022 06:30:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3ZRiSc5qC7jN/jMxZkI7UncXfeDfUNMZH+YBcXpwK98=; b=RzNmoKA2/Adp/0ahnPAQnbkEPbkdPFmE8kwT0G5p+EcYOG0aA/vg4Ihvf9YdYuwQbG 1BPDREY3GTPZkk3gr+iwBQHx5l3k3byDvn9m+H8MY/R43UEuxiUDkNBw+9NKI3c1SHa7 w8oz2aRvhRQqopURzykENL+A1/YZKEnzaBUWE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3ZRiSc5qC7jN/jMxZkI7UncXfeDfUNMZH+YBcXpwK98=; b=dVorBUbfUwZxgvEchDh5BoWcKK8bPscVYy+2zbjt4QUAou2uI247kq90HVylZemWhY lbB0TiKdOYt4R1G3aTfaO7//2yaD05StHtYzWQV9FzkFzRU9NxJ+SHkhcHYcR8hqS46r wJQuBXXNLQLqqddt4jobRhhfrIHJmlAwhxgoMiFrzah1FTlSYkzgwmBoiW+iX4SSGE+5 YRuIgIeP6Zm5XwLDmc7gY92bJ8SJRFha4KyQMn2LyrwK8VYOi1FzRB0QIvGEkYKRq8gO V5KPYkKVIEQaH6wh9MNzkrMpSWRNJp8pj91+Ytg8kMRKQkPFOQ8tzULWyCFRncwR/OYl h4vw== X-Gm-Message-State: AOAM532osHOpI80GKLRWF4baePKC314Ud/yITHDpNDxWnqcdQK5YgaZE WmLS6Xp2kktrzo8blORy+kyFz5sSbi81BhHFcLqcMw== X-Google-Smtp-Source: ABdhPJzVcP0rFY3q9oe9UbA2bXI2i8xcqKwVs6NLO+oxcYvMyJby+AUoHuhtYC1GfiW05rMcV3PvzFPQ9h4BthvvLyQ= X-Received: by 2002:a4a:accc:: with SMTP id c12mr4619591oon.92.1642516243770; Tue, 18 Jan 2022 06:30:43 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Owen Hilyard Date: Tue, 18 Jan 2022 09:30:08 -0500 Message-ID: Subject: Re: [RFC] DTS Commit Policies To: =?UTF-8?Q?Juraj_Linke=C5=A1?= Cc: dev , "dts@dpdk.org" Content-Type: multipart/alternative; boundary="0000000000003f859d05d5dc1d4f" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000003f859d05d5dc1d4f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Juraj, I think that both of those make sense. We should try to add those into the document next meeting. Owen Adding a link to the document here in case anyone doesn't want to go through the meeting minutes: https://docs.google.com/document/d/1G7_AEA-4MAd88bxjfP-IOcIy_6mnrMz3HCsUI8e= -NN4/edit On Mon, Jan 17, 2022 at 7:23 AM Juraj Linke=C5=A1 wrote: > > > > > *From:* Owen Hilyard > *Sent:* Wednesday, January 12, 2022 4:08 PM > *To:* dev ; dts@dpdk.org > *Subject:* [RFC] DTS Commit Policies > > > > Hello Everyone, > > > > The DTS Working Group wanted to let everyone give feedback on the propose= d > DTS commit policies. Please leave a comment with any feedback you have. W= e > will be reviewing feedback in the DTS Working Group meeting on January > 26th, at which point the comment period will close. > > > > The purpose of the commit policies is to help standardize the code that > makes up DTS, as well as help new additions meet community requirements, > such as avoiding breaking changes, ensuring runtime stability, and aiding > debugability. > > > > Owen Hilyard > > > > DTS Working Group meeting room: > https://armltd.zoom.us/j/97503259680?pwd=3DVVlmWnlnTXJkVGkwR2JOU3R3b3Vndz= 09&from=3Daddon > > > > I always like to follow the practices captured in this article: > https://cbea.ms/git-commit/ > > > > I think it also makes sense to be as close as possible to DPDK, so trying > to use what we can from their guidelines [0] would be a good start. > > > > Juraj > > > > [0] > https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-sub= ject-line > --0000000000003f859d05d5dc1d4f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Juraj,=C2=A0

I think that both of those= make sense. We should try to add those into the document next meeting.

Owen

Adding a link to the document here in cas= e anyone doesn't want to go through the meeting minutes:=C2=A0https://docs.google.com/document/d/1G7_AEA-4MAd88bxjfP-IOcIy= _6mnrMz3HCsUI8e-NN4/edit=C2=A0

On Mon, Jan 17, 2022 at 7:23 AM= Juraj Linke=C5=A1 <juraj.linkes@pantheon.tech> wrote:

=C2=A0

=C2=A0

From: Owen Hilyard <ohilyard@iol.unh.edu>
Sent: Wednesday, January 12, 2022 4:08 PM
To: dev <dev@dp= dk.org>; dts@dpdk.= org
Subject: [RFC] DTS Commit Policies

=C2=A0

Hello Everyone,

=C2=A0

The DTS Working Group wanted to let everyone give fe= edback on the proposed DTS commit policies. Please leave a comment with any= feedback you have. We will be reviewing feedback in the DTS Working Group = meeting on January 26th, at which point the comment period will close.=C2=A0

=C2=A0

The purpose of the commit policies is to help standa= rdize the code that makes up DTS, as well as help new additions meet commun= ity requirements, such as avoiding breaking changes, ensuring runtime stabi= lity, and aiding debugability.=C2=A0

=C2=A0

Owen Hilyard

=C2=A0

DTS Working Group meeting room:=C2=A0https://armltd.zoom.us/j/97503259680?pwd= =3DVVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=3Daddon

=C2=A0

I always like to follow the practices captur= ed in this article: https://cbea.ms/g= it-commit/

=C2=A0

I think it also makes sense to be as close a= s possible to DPDK, so trying to use what we can from their guidelines [0] would be a good start.

=C2=A0

Juraj

=C2=A0

[0] https://doc.dpdk.org/guides/contributing/patches.html#commit-messages-subje= ct-line

--0000000000003f859d05d5dc1d4f--