test suite reviews and discussions
 help / color / mirror / Atom feed
* [RFC] DTS Commit Policies
@ 2022-01-12 15:08 Owen Hilyard
  2022-01-17 12:23 ` Juraj Linkeš
  0 siblings, 1 reply; 3+ messages in thread
From: Owen Hilyard @ 2022-01-12 15:08 UTC (permalink / raw)
  To: dev, dts

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

Hello Everyone,

The DTS Working Group wanted to let everyone give feedback 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.

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=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon

[-- Attachment #2: Type: text/html, Size: 886 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [RFC] DTS Commit Policies
  2022-01-12 15:08 [RFC] DTS Commit Policies Owen Hilyard
@ 2022-01-17 12:23 ` Juraj Linkeš
  2022-01-18 14:30   ` Owen Hilyard
  0 siblings, 1 reply; 3+ messages in thread
From: Juraj Linkeš @ 2022-01-17 12:23 UTC (permalink / raw)
  To: Owen Hilyard, dev, dts

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]



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

Hello Everyone,

The DTS Working Group wanted to let everyone give feedback 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.

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=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon

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-subject-line

[-- Attachment #2: Type: text/html, Size: 5869 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] DTS Commit Policies
  2022-01-17 12:23 ` Juraj Linkeš
@ 2022-01-18 14:30   ` Owen Hilyard
  0 siblings, 0 replies; 3+ messages in thread
From: Owen Hilyard @ 2022-01-18 14:30 UTC (permalink / raw)
  To: Juraj Linkeš; +Cc: dev, dts

[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]

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š <juraj.linkes@pantheon.tech>
wrote:

>
>
>
>
> *From:* Owen Hilyard <ohilyard@iol.unh.edu>
> *Sent:* Wednesday, January 12, 2022 4:08 PM
> *To:* dev <dev@dpdk.org>; dts@dpdk.org
> *Subject:* [RFC] DTS Commit Policies
>
>
>
> Hello Everyone,
>
>
>
> The DTS Working Group wanted to let everyone give feedback 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.
>
>
>
> 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=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon
>
>
>
> 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-subject-line
>

[-- Attachment #2: Type: text/html, Size: 5023 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-01-18 14:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-12 15:08 [RFC] DTS Commit Policies Owen Hilyard
2022-01-17 12:23 ` Juraj Linkeš
2022-01-18 14:30   ` Owen Hilyard

test suite reviews and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dts/0 dts/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dts dts/ http://inbox.dpdk.org/dts \
		dts@dpdk.org
	public-inbox-index dts

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dts


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git