linux-kernel - Re: [PATCH v4 15/20] docs: add Rust documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANiq72mLtvWJ5peSTpYQ8AeLEskga6Pda8Q7Daysv2pfycnyxA@mail.gmail.com>
Date:   Fri, 18 Mar 2022 14:12:09 +0100
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Akira Yokosawa <akiyks@...il.com>
Cc:     Miguel Ojeda <ojeda@...nel.org>, Jonathan Corbet <corbet@....net>,
        Alex Gaynor <alex.gaynor@...il.com>,
        Adam Bratschi-Kaye <ark.email@...il.com>,
        Boris-Chengbiao Zhou <bobo1239@....de>,
        Wu XiangCheng <bobwxc@...il.cn>, Daniel Xu <dxu@...uu.xyz>,
        Gary Guo <gary@...yguo.net>,
        Greg KH <gregkh@...uxfoundation.org>,
        Yuki Okushi <jtitor@...6.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Finn Behrens <me@...enk.de>,
        Michal Marek <michal.lkml@...kovi.net>,
        Michael Ellerman <mpe@...erman.id.au>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        rust-for-linux <rust-for-linux@...r.kernel.org>,
        Sven Van Asbroeck <thesven73@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Wedson Almeida Filho <wedsonaf@...gle.com>,
        Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH v4 15/20] docs: add Rust documentation

Hi Akira,

On Thu, Mar 17, 2022 at 3:50 PM Akira Yokosawa <akiyks@...il.com> wrote:
>
> As I see v2 15/20, the SVG figure is among other documentation updates.
> IIUC, this figure/logo was in PNG at first, but Jon suggested vector graphics.
> If this is the case, it deserves an individual patch with a changelog
> explaining why it is in SVG, where the Tux figure came from, what was the
> original PNG logo, who contributed the SVG conversion, etc.

Yeah, I can split the figure into another patch for the next round.
Though one could argue the same for other files -- do you prefer to
have more granular patches in general?

> I understand you did all the SVG work, didn't you?
> I don't think those many Co-developed-by tags apply to this figure.

Yeah, I made the logo, but I reused the SVG forms of both the Rust and
the Tux logos.

The Tux SVG conversion (from Larry Ewing's one) was done by Garrett
LeSage and IFo Hancroft, please see
https://lore.kernel.org/lkml/20220207014418.GA28724@kernel.org/ for
details on that one.

I will add these details to the split patch.

> I'm saying this because this figure/logo can be reused in other open-
> source projects on its own.  It would be worth clarifying its origin
> in the Git history as well as in COPYING-logo.

I think the Tux SVG logo would be the most useful for other projects,
which is why I submitted it to be added to the tree with the
permission of Garrett and IFo (see link above). I am not sure if other
open-source projects would need the Rust for Linux one, though, so it
sounds like a good idea. I am happy to split the patch, clarify the
origin and to add a `COPYING-logo` to the `Documentation/rust` folder
too (pointing to the main one at `Documentation/` maybe).

Cheers,
Miguel