From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Talel BELHADJ SALEM <bhstalel@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] Yocto Tasks Detailed Diagram Proposal
Date: Fri, 27 Oct 2023 10:17:19 +0200 [thread overview]
Message-ID: <acba70be-9670-4ff3-a0f0-bb13add4559a@bootlin.com> (raw)
In-Reply-To: <CAOgG7m0eQPFhnrmXd8GhbZJJEf_0dDRAj6Vpthh-NOtVPbZAjg@mail.gmail.com>
Hi Talel
On 20.10.23 at 20:03, Talel BELHADJ SALEM wrote:
> Hello Michael,
>
> If I understand correctly:
>
> * The diagram is correct and I only need to:
> * Change the font
>
Right!
>
> * Remove the color coding indication (Should I keep the coloring as
> well ? Or make everything with 2 colors at max?)
>
Just think about colorblind people, for whom red and green look the
same, for example. So, you could use up to 3 types of colors actually:
bright (like white), dark (like black) and an intermediate one, so that
the 3 colors can be distinguished on an e-ink display or by colorblind
people.
That's what I tried to do with
https://docs.yoctoproject.org/_images/releases.svg
> * Complete the section content and append the diagram and submit the
> patch
>
Right! Thanks in advance :)
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-10-27 8:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 17:13 Yocto Tasks Detailed Diagram Proposal Bel Hadj Salem Talel
2022-11-01 15:42 ` [docs] " Michael Opdenacker
2023-06-22 9:08 ` Quentin Schulz
2023-06-22 11:34 ` BELHADJ SALEM Talel
2023-10-17 18:56 ` BELHADJ SALEM Talel
2023-10-19 14:29 ` [docs] " Michael Opdenacker
2023-10-20 18:03 ` Talel BELHADJ SALEM
2023-10-27 8:17 ` Michael Opdenacker [this message]
2023-10-27 12:18 ` Talel BELHADJ SALEM
2023-10-27 15:02 ` Michael Opdenacker
2023-10-27 15:31 ` Talel BELHADJ SALEM
[not found] ` <178FE2DDDBFED311.11247@lists.yoctoproject.org>
2023-10-27 7:27 ` Talel BELHADJ SALEM
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=acba70be-9670-4ff3-a0f0-bb13add4559a@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bhstalel@gmail.com \
--cc=docs@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox