public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: BELHADJ SALEM Talel <bhstalel@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] Yocto Tasks Detailed Diagram Proposal
Date: Thu, 19 Oct 2023 16:29:45 +0200	[thread overview]
Message-ID: <5c668a44-d9e3-4ca2-ad1d-e42730c76530@bootlin.com> (raw)
In-Reply-To: <29645.1697569015596670723@lists.yoctoproject.org>

Hi Talel

On 17.10.23 at 20:56, BELHADJ SALEM Talel wrote:
> Hello,
>
> Returning to the detailed diagram proposal,
>
> I have created another one that is more and more detailed using 
> draw.io, I tried inkspace but it seems really to deal with.


This one looks good. I opened it in Inkscape and I can open it and edit 
it, which is what matter most.

A minor issue though. I can see in your PNG export that you are using 
"fancy" fonts, and I don't have them on my Linux box, and we probably 
don't either on the autobuilder machine which compiles the docs. 
However, this should be fixable. You could look at the fonts I used on 
https://docs.yoctoproject.org/_images/releases.svg and you/we could 
probably use those or similar ones.

>
> If this SVG file fine and accepted we can move on with it, otherwise, 
> what is the solution for this ? Should I try to take more time to 
> adapt it to inkscape and following the SVG template or someone can 
> help me with this ?


Actually, the style of the SVG template should be updated. I liked the 
style of your original diagram and I must confess it influence me for 
https://docs.yoctoproject.org/_images/releases.svg :)

This being said, we should be careful not to convey too much meaning 
through colors, and keep in mind colorblind people and readers on e-ink 
(grayscale) displays. Accessibility is important and this is something 
you could improve  in the version you've just submitted. The first 
version was almost perfect with respect to this. All we need is manage 
to import it properly with an Open Source editor like Inkscape.


>
> After dealing with that, I am planning to suggest adding a new "6.5 
> Tasks Map" in ref-manual/tasks and for the recipes example in the 
> diagram I will put their content in that section before introducing 
> the diagram.
>
> What do you think?

It sounds great! I'll be happy to help if I can.
Thanks in advance,
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2023-10-19 14:29 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         ` Michael Opdenacker [this message]
2023-10-20 18:03           ` [docs] " Talel BELHADJ SALEM
2023-10-27  8:17             ` Michael Opdenacker
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=5c668a44-d9e3-4ca2-ad1d-e42730c76530@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