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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53f52975-98d0-dbb3-9781-0366143f2dd0@linuxfoundation.org>
Date:   Tue, 31 Jan 2023 12:20:13 -0700
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Jonathan Corbet <corbet@....net>,
        Thorsten Leemhuis <linux@...mhuis.info>
Cc:     sshefali021@...il.com, kstewart@...uxfoundation.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH v2] docs: add workload-tracing document to admin-guide

On 1/30/23 16:52, Jonathan Corbet wrote:
> Shuah Khan <skhan@...uxfoundation.org> writes:
> 
>> On 1/28/23 01:35, Thorsten Leemhuis wrote:
>>> Adding another section that doesn't seem to a be a good fit feels a bit
>>> like "making things worse than better".  So wouldn't this maybe be a
>>> good opportunity to create a totally new top-level section for
>>> application developers and system integrators, even if it's tiny for
>>> now? The audience is likely big enough to justify that -- and the topics
>>> are likely different enough, too (of course sometimes there will be
>>> overlap, as always). Any maybe it will help to bring other stuff over
>>> from admin guide that is more targeted for application developers and
>>> system integrators, which will help to get more structure into the
>>> admin-guide.
>>>
>>
>> I like the idea of creating a new top-level section for application developers
>> and system integrators. I foresee this section growing and also we can look
>> at other documents that are a good fit under this category and move them over.
>>
>> Jon, Thoughts on this.
> 
> The fit with the admin guide caught my attention as well, but I didn't
> immediately have a better place to suggest.  I am somewhat resistant to
> creating another top-level directory; I really want to have *fewer* of
> them.  I certainly don't want to create one for a single document.  My
> inclination would be to leave it where it is for now; we can always
> revisit this if it turns out we have a lot of material that justifies a
> new book.
> 

Makes perfect sense. I didn't want to suggest a new top level for the same
reasons. For now I will send v3 keeping it in the same location.

I will take a pass at the existing documents under admin-guide and in other
places to see if others could be grouped under a top-level as suggested by
Thorsten

thanks,
-- Shuah

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ