All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <richard.purdie@linuxfoundation.org>, <docs@lists.yoctoproject.org>
Cc: "Richard Purdie via lists.yoctoproject.org"
	<richard.purdie=linuxfoundation.org@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v2] governance: Add start of project history and leadership sections
Date: Wed, 04 Nov 2026 14:30:03 +0100	[thread overview]
Message-ID: <DMMGODYYKIMC.3BQCIELWD0FVP@bootlin.com> (raw)
In-Reply-To: <20261102141947.594561-1-richard.purdie@linuxfoundation.org>

Hi,

Thanks, the added dates do help realizing when things happen. I'll merge it to
master-next with the following formatting changes:

diff --git a/documentation/governance/history.rst b/documentation/governance/history.rst
index fa26b9f8c..6c6096c1f 100644
--- a/documentation/governance/history.rst
+++ b/documentation/governance/history.rst
@@ -168,20 +168,20 @@ OpenEmbedded. There were often changes talked about at many of the OE
 developer meetings (OEDEMs) but where the developers had not been able to
 find time/resources to make them happen.
 
-- ``fakeroot`` was swapped for ``pseudo``, donated from Wind River
+-  ``fakeroot`` was swapped for ``pseudo``, donated from Wind River
 
-- The concept of `sstate` was developed (August 2010) meaning incremental
-  builds became possible and output could be removed from the build directory
-  structures.Initial versions of this were known as "packaged staging" as
-  initially package manager involvement was assumed but this was eventually
-  discounted.
+-  The concept of `sstate` was developed (August 2010) meaning incremental
+   builds became possible and output could be removed from the build directory
+   structures. Initial versions of this were known as "packaged staging" as
+   initially package manager involvement was assumed but this was eventually
+   discounted.
 
-- The separate staging and target installs were combined.
+-  The separate staging and target installs were combined.
 
-- Automated testing was developed based on buildbot (python based to match
-  the core developers skillset) creating the "Autobuilder" project.
+-  Automated testing was developed based on Buildbot (python based to match
+   the core developers skillset) creating the "Autobuilder" project.
 
-- Support for RPM packages were added (2008-2010) with a switch to RPM v5.
+-  Support for RPM packages were added (2008-2010) with a switch to RPM v5.
 
 Most of the project's budget focused either around Autobuilder /
 infrastructure costs (including a full time sysadmin) or on advocacy and
@@ -279,16 +279,16 @@ to focus on this was formed with the aim of writing a new participation
 agreement for members. There were multiple things people wanted to achieve
 including:
 
-- Officially recognise the special relationship with OpenEmbedded.
+-  Officially recognise the special relationship with OpenEmbedded.
 
-- Have oversight of Richard Purdie's decision making.
+-  Have oversight of Richard Purdie's decision making.
 
-- Creation of a Yocto Project TSC to make technical Yocto Project decisions.
+-  Creation of a Yocto Project TSC to make technical Yocto Project decisions.
 
-- Formalise the project member benefits.
+-  Formalise the project member benefits.
 
-- Align the project with known Linux Foundation best practise governance and
-  charter documents.
+-  Align the project with known Linux Foundation best practise governance and
+   charter documents.
 
 These changes included the formation of the Yocto Project TSC which first
 met in June 2019. The TSC became necessary since the project was now

Antonin

      reply	other threads:[~2026-11-04 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 14:19 [PATCH v2] governance: Add start of project history and leadership sections Richard Purdie
2026-11-04 13:30 ` Antonin Godard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DMMGODYYKIMC.3BQCIELWD0FVP@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie=linuxfoundation.org@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.