public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: Request for setup of new repositories
Date: Tue, 24 May 2022 20:25:13 +0900	[thread overview]
Message-ID: <YozAmQFZ3LhqQoZN@workstation> (raw)
In-Reply-To: <b6e986d0-b594-4543-ae63-e08e88ad3418@www.fastmail.com>

Hi Jaroslav,

On Thu, May 05, 2022 at 09:49:52PM +0900, Takashi Sakamoto wrote:
> At present I prefer separated pages from source since the pages can be
> generated from the source, however as you say the inclusive way is worth
> to reduce repository maintained by the project. I test the idea later in
> my libhinoko repository. When it looks well, I'll request you for
> configuration change.

I'd like to fix the issue for the URL of documentation before releasing
libhitaki since I put the URL to configuration for gi-docgen.

I'm investigating to put the documentation into the same repository
where source is maintained, however I prefer to separate the two into
different repositories. Then I suppose it good to put several
documentations into one repository rather than maintaining them in
different repositories.

At present, three repositories are maintained for documentations:

* https://github.com/alsa-project/alsa-gobject-docs
* https://github.com/alsa-project/libhinawa-docs
* https://github.com/alsa-project/libhitaki-doc

Let us consolidate them in one repository. For example, by referring to
team name:

* https://github.com/alsa-project/gobject-introspection-docs/

The documentations are expected to be public under below URL:

* https://alsa-project.github.io/gobject-introspection-docs/alsa-gobject/
* https://alsa-project.github.io/gobject-introspection-docs/hinawa/
* https://alsa-project.github.io/gobject-introspection-docs/hitaki/

I'd like to ask your opinion about the idea.


Thanks

Takashi Sakamoto

  parent reply	other threads:[~2022-05-24 11:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 13:20 Request for setup of new repositories Takashi Sakamoto
2022-04-26  7:23 ` Jaroslav Kysela
2022-04-26 11:38   ` Takashi Sakamoto
2022-04-29  2:29     ` Takashi Sakamoto
2022-05-05 11:41       ` Takashi Sakamoto
2022-05-05 12:10         ` Jaroslav Kysela
2022-05-05 12:49           ` Takashi Sakamoto
2022-05-05 12:59             ` Jaroslav Kysela
2022-05-06  8:56               ` Takashi Sakamoto
2022-05-24 11:25             ` Takashi Sakamoto [this message]
2022-05-24 12:36               ` Jaroslav Kysela
2022-05-25  1:42                 ` Takashi Sakamoto
2022-05-25  6:37                   ` Jaroslav Kysela
2022-05-26 12:58                     ` Takashi Sakamoto
2022-05-26 13:35                       ` Jaroslav Kysela
2022-08-05 10:26                         ` Takashi Sakamoto
2022-08-05 10:42                           ` Jaroslav Kysela
2022-08-05 10:58                             ` Takashi Sakamoto
2022-08-27  3:43                               ` Takashi Sakamoto
2022-08-27  5:29                                 ` Jaroslav Kysela
2022-08-27  8:27                                   ` Takashi Sakamoto

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=YozAmQFZ3LhqQoZN@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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