From: Jani Nikula <jani.nikula@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: Pawel Sikora <pawel.sikora@intel.com>,
igt-dev@lists.freedesktop.org,
Petri Latvala <adrinael@adrinael.net>,
Arkadiusz Hiler <arek@hiler.eu>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
Bhanuprakash Modem <bhanuprakash.modem@gmail.com>,
Karthik B S <karthik.b.s@intel.com>
Subject: Re: [PATCH i-g-t v10 0/5] Establish MkDocs Documentation Framework for IGT GPU Tools
Date: Wed, 08 Oct 2025 11:07:00 +0300 [thread overview]
Message-ID: <4bf159d87af719a5c820f32e5430ea252ff06e3a@intel.com> (raw)
In-Reply-To: <87ldlme8oc.wl-ashutosh.dixit@intel.com>
On Tue, 07 Oct 2025, "Dixit, Ashutosh" <ashutosh.dixit@intel.com> wrote:
> On Wed, 10 Sep 2025 01:26:23 -0700, Jani Nikula wrote:
>>
>> On Tue, 09 Sep 2025, Pawel Sikora <pawel.sikora@intel.com> wrote:
>> > Dear Maintainers,
>> >
>> > I am submitting a series of patches to introduce a comprehensive
>> > documentation framework for the IGT GPU Tools project using MkDocs.
>>
>> There's been a lot of iterations in fairly quick succession, and I have
>> yet to see any comment from maintainers wrt my feedback [1].
>>
>> I'd rather see a clear statement "yeah let's go with MkDocs" than just
>> having this gradually happen without a conscious decision.
>
> I will take a slightly different approach to this. I think Jani has a valid
> point and if this effort were starting today, I'd say go with
> sphinx/rst. But as far as I see, this series has required significant
> effort to get to this point and is almost ready to merge.
I don't think it had taken a significant effort by the time I first
brought this up, and I kind of expected to get feedback from the
maintainers *before* a lot more effort had been put into it.
And now it looks like what I feared, it just gradually happened and
nobody stood up and made a decision.
BR,
Jani.
>
> I don't know how much time/effort it will take for a similar sphinx based
> solution (Pawel would you know?), but given where we are, it seems we
> should just merge this (since this would provide some missing documentation
> immediately). And then if we think we need a sphinx based solution and
> someone can be found to do that, they can switch the documentation to the
> sphinx based solution later.
>
> I want to elicit Pawel's feedback in particular, since he is the one doing
> this work.
>
> Thanks.
> --
> Ashutosh
>
>
>>
>> Cc: Everyone from MAINTAINERS.
>>
>>
>> BR,
>> Jani.
>>
>>
>> [1] https://lore.kernel.org/r/3d83d59669d62f004a507a25510b21f9bd273410@intel.com
>>
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-10-08 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 11:27 [PATCH i-g-t v10 0/5] Establish MkDocs Documentation Framework for IGT GPU Tools Pawel Sikora
2025-09-09 11:27 ` [PATCH i-g-t v10 1/5] docs: Set up MkDocs for documentation site Pawel Sikora
2025-09-09 11:27 ` [PATCH i-g-t v10 2/5] docs: create symlinks for NEWS/MAINTAINERS/CONTRIB Pawel Sikora
2025-09-09 11:27 ` [PATCH i-g-t v10 3/5] docs: rename cross-building.txt to .md Pawel Sikora
2025-09-09 11:27 ` [PATCH i-g-t v10 4/5] docs: Initialize MkDocs documentation structure Pawel Sikora
2025-09-09 11:27 ` [PATCH i-g-t v10 5/5] gitlab-ci: Add MkDocs documentation support Pawel Sikora
2025-09-09 22:09 ` ✓ Xe.CI.BAT: success for Establish MkDocs Documentation Framework for IGT GPU Tools (rev10) Patchwork
2025-09-09 22:24 ` ✓ i915.CI.BAT: " Patchwork
2025-09-10 3:48 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-10 8:26 ` [PATCH i-g-t v10 0/5] Establish MkDocs Documentation Framework for IGT GPU Tools Jani Nikula
2025-10-07 20:52 ` Dixit, Ashutosh
2025-10-08 8:07 ` Jani Nikula [this message]
2025-10-09 15:08 ` Kamil Konieczny
2025-10-09 20:48 ` Dixit, Ashutosh
2025-10-09 8:51 ` Pawel Sikora
2025-09-10 10:14 ` ✗ i915.CI.Full: failure for Establish MkDocs Documentation Framework for IGT GPU Tools (rev10) Patchwork
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=4bf159d87af719a5c820f32e5430ea252ff06e3a@intel.com \
--to=jani.nikula@intel.com \
--cc=adrinael@adrinael.net \
--cc=arek@hiler.eu \
--cc=ashutosh.dixit@intel.com \
--cc=bhanuprakash.modem@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@intel.com \
--cc=pawel.sikora@intel.com \
/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