Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>
Cc: <docs@lists.yoctoproject.org>, "Yoann Congal" <yoann.congal@smile.fr>
Subject: [blacksail] Pull request
Date: Fri, 06 Nov 2026 10:38:19 +0100	[thread overview]
Message-ID: <DMO101LT9IJI.3KQ38SPPEJ2PJ@bootlin.com> (raw)

The following changes since commit 64607e243b13b3d81e91af9a9bed72fb9ee0fd0e:

  ref-manual/release-process.rst: add textual legend (2026-10-23 09:45:16 +0200)

are available in the Git repository at:

  git@push.yoctoproject.org:yocto-docs blacksail-next

for you to fetch changes up to 28a708ecb3c2ce1669094f9f4c1bdcbc28438bcc:

  governance: Add start of project history and leadership sections (2026-11-06 10:10:29 +0100)

----------------------------------------------------------------
Antonin Godard (6):
      AGENTS.md: add file
      AGENTS.md: tell the agent about conventions and standards
      theme_overrides.css: rework admonition colors
      standards.md: update our admonitions encouraged usage
      standards.md: recommend Nimbus Sans instead of Nimbus Roman
      docs-wide: convert diagrams that use Nimbus Roman to use Nimbus Sans

Lee Chee Yang (1):
      migration-guide: add release notes for 5.0.21

Paul Barker (1):
      contributor-guide: Adopt new AI-Assisted Contribution Policy

Richard Purdie (3):
      ref-manual/faq: Add entry about emails on patch merging
      ref-manual/faq: Add entry about github pull requests
      governance: Add start of project history and leadership sections

 AGENTS.md                                          |  70 ++
 .../ai-assisted-contribution-policy.rst            | 199 ++++++
 documentation/contributor-guide/index.rst          |   1 +
 documentation/contributor-guide/submit-changes.rst |  50 --
 documentation/governance/history.rst               | 343 ++++++++++
 documentation/governance/index.rst                 |  14 +
 documentation/governance/leadership.rst            |  79 +++
 documentation/index.rst                            |  10 +
 documentation/migration-guides/release-5.0.rst     |   1 +
 .../migration-guides/release-notes-5.0.21.rst      | 709 +++++++++++++++++++++
 documentation/overview-manual/svg/git-workflow.svg |  30 +-
 documentation/ref-manual/faq.rst                   |  55 ++
 documentation/sphinx-static/theme_overrides.css    |  45 +-
 documentation/standards.md                         |  14 +-
 documentation/template/template.svg                |  40 +-
 15 files changed, 1557 insertions(+), 103 deletions(-)
 create mode 100644 AGENTS.md
 create mode 100644 documentation/contributor-guide/ai-assisted-contribution-policy.rst
 create mode 100644 documentation/governance/history.rst
 create mode 100644 documentation/governance/index.rst
 create mode 100644 documentation/governance/leadership.rst
 create mode 100644 documentation/migration-guides/release-notes-5.0.21.rst

             reply	other threads:[~2026-11-06  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  9:38 Antonin Godard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-23  7:57 [blacksail] Pull request Antonin Godard
2026-10-15 13:56 Antonin Godard

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=DMO101LT9IJI.3KQ38SPPEJ2PJ@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=paul@pbarker.dev \
    --cc=yoann.congal@smile.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox