All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 00/10] New LTP documentation
Date: Thu, 21 Mar 2024 09:25:59 +0100	[thread overview]
Message-ID: <20240321082559.GA535362@pevik> (raw)
In-Reply-To: <20240320-new_website-v1-0-79b603c8aea1@suse.com>

Hi Andrea,

> The new LTP documentation is meant to use Sphinx as the main
> documentation framework, with ReconStructedText as the main language.
> All the conversion has been done step-by-step, each chapter at time,
> updating english syntax and fixing typos. There are minor improvements,
> but overall the structure is the same.

> C / Networking / KVM API are not documented yet, because they will be
> probably integrated in the LTP library. C API documentation is already
> on going, but the others not.

> For a demo, please take a look at:

> https://ltp-acerv.readthedocs.io/en/latest/index.html

Out of curiosity, we need to register LTP on readthedocs.io.
Then we need GitHub Action hook (including some secret for auth) for publishing.
Correct?

https://docs.readthedocs.io/en/stable/guides/setup/git-repo-manual.html

I guess you now deploy to your fork manually, otherwise you would add GitHub
Action config in the patchset.

Also, what I like (for the future) offline formats (PDF, ePub, HTML) are
supported:

https://docs.readthedocs.io/en/stable/downloadable-documentation.html

Also, I would prefer when this merged it would actually replace the old github
docs (otherwise we maintainers endup maintaining both - getting fixes for both).
E.g. in the final version first deleting the old docs + github update hook.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2024-03-21  8:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 16:20 [LTP] [PATCH 00/10] New LTP documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 01/10] Add the new basics documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 02/10] Add new mailing list setup documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 03/10] Rewrite writing tests guidelines documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 04/10] Refactor patch review " Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 05/10] Refactor LTP release procedure documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 06/10] Refactor debugging documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 07/10] Refactor LTP library guidelines documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 08/10] Refactor build system documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 09/10] Refactor test case tutorial documentation Andrea Cervesato
2024-03-20 16:20 ` [LTP] [PATCH 10/10] Introduce kernel-doc API support Andrea Cervesato
2024-03-21  8:25 ` Petr Vorel [this message]
2024-03-21  8:46   ` [LTP] [PATCH 00/10] New LTP documentation Andrea Cervesato via ltp
2024-03-21  8:56     ` Petr Vorel
2024-03-22 10:49       ` Wojtek Porczyk
     [not found]       ` <Zf1htmFkRl8BIFOX@invisiblethingslab.com>
2024-03-22 10:56         ` Andrea Cervesato via ltp

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=20240321082559.GA535362@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.