From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 59D17C433EF for ; Wed, 25 May 2022 01:43:23 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id D7519164F; Wed, 25 May 2022 03:42:31 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz D7519164F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1653443001; bh=9A8ThEC2ErIIFJecu8bCQUpO5CaNPlxjrrFQe5WZQrk=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=XgvUO6xgFY9SwJ6fzl3+2VjBWYvB/Oaugn6ABn5NkvB5ZxYN2B6X4L2XN/w31bvWq QN5xCUneQc0KidDBiic8jkok5Jh40jTPMlO1AQ7nAUf2LUZYZJMervguKa1dUMeqlZ a0MVBr0Rfdl1EDQR8Ko/vachAuJxIH5itHsS+EMA= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 570E8F80169; Wed, 25 May 2022 03:42:31 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 3A788F8016D; Wed, 25 May 2022 03:42:29 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id DFA12F800D0 for ; Wed, 25 May 2022 03:42:18 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz DFA12F800D0 Authentication-Results: alsa1.perex.cz; dkim=pass (2048-bit key) header.d=sakamocchi.jp header.i=@sakamocchi.jp header.b="HzrsVesv"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="JZ0OjPIK" Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 2D9BC320092A; Tue, 24 May 2022 21:42:14 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 24 May 2022 21:42:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sakamocchi.jp; h=cc:cc:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1653442933; x=1653529333; bh=aK P2MtBf5wJ3Hxavvnk5ztlpYWleHN1j8hVNDSToJ/Y=; b=HzrsVesvfM11shZsnj ojnDWz/1E5McA4o3n/rbY0yQUFAu4ttblmcwqT4PHZDkAobRsKEWb2KFJTJONemT /VreibCtbXyem7ukRf01xQhfUSyrNN7eT2kL5pdGLZ7c9+PjHR/E2gdnUebKTMQn Mzkfb1WjfSD2BIIJV7VntgtiX4UZMyqwzNwKNUKAanUFUfz7lRhJPTnJ3CzxcuOk rmpqudh/ieG9AnO4GRoduY3WzOqE+PCC0/zS5wRgAiLej8AffPQtZ2RF98QMLwW6 maSw6cHi40Q8Vj/hSZM5GepMgQQRNPIUgfYCWN/Xze6xU7Rm/KGJjM98bh91Y2jw zW2g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1653442933; x=1653529333; bh=aKP2MtBf5wJ3Hxavvnk5ztlpYWle HN1j8hVNDSToJ/Y=; b=JZ0OjPIKsLHZwBxy2G/oUdDyiCvNR4FHFcw1cblfdzk1 JlOO0J3ygO/qd7XCgRHynt67gsBVsRBUnL9jme8PSa2ZHy/DRfXYysJ688khHBia 7TG5rkOKINi6lgmSQfB+2EA+hOPMvzs2qQLYQQ685hCPV7l3p6CcPbGMc3FZQ4eq MuEbjdXMJA20mrRUsTzeH5wuLnuTQSgHBlsjrWpkM24r4m22dUy2VljXagaNfQxp oo5VGX0Yawe9AQyKEtn1DgFEp9wAtEr6xbR28cWwFVgFpbz3FhnGSj99s79cXTHA 3kXBA8fQwnts5kvSWkPvoNX8QYFMy7T6B9ZDWGKlrQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeeggdeglecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenog fuuhhsphgvtghtffhomhgrihhnucdlgeelmdenucfjughrpeffhffvvefukfhfgggtuggj sehttdertddttddvnecuhfhrohhmpefvrghkrghshhhiucfurghkrghmohhtohcuoehoqd htrghkrghshhhisehsrghkrghmohgttghhihdrjhhpqeenucggtffrrghtthgvrhhnpedu jeeiiedtveekgeehveevvefgkeetteduffdukedvledvudehudeujedvkeeugfenucffoh hmrghinhepghhithhhuhgsrdgtohhmpdhgihhthhhusgdrihhonecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepohdqthgrkhgrshhhihesshgrkh grmhhotggthhhirdhjph X-ME-Proxy: Feedback-ID: ie8e14432:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 May 2022 21:42:11 -0400 (EDT) Date: Wed, 25 May 2022 10:42:08 +0900 From: Takashi Sakamoto To: Jaroslav Kysela Subject: Re: Request for setup of new repositories Message-ID: Mail-Followup-To: Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org References: <7d90c47a-ce1a-d9d7-ba8a-e794f20487cb@perex.cz> <14235475-bd6b-4b86-61f4-8c2aa7f95838@perex.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Takashi Iwai , alsa-devel@alsa-project.org X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Tue, May 24, 2022 at 02:36:19PM +0200, Jaroslav Kysela wrote: > On 24. 05. 22 13:25, Takashi Sakamoto wrote: > > 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 for this idea. I just noted that github allows to specify a branch > for the git pages (github.io). Do you think that a 'doc' or 'docs' branch in > the separate source repos will be sufficient for your work? It may be more > logical than having a common doc repo (logical URLs) and things (source and > generated pages) will not mix together. Thanks for the suggestion. Indeed, we can choose the way to put documentation to specific branch in the repository. I've already investigated the way then had complexed feeling. ...To be honest, I'd like to avoid it, as much as possible, in a point of the essential concept in source control management. The branching idea forces to put several histories disconnected each other into one repository. It's surely available technically, however I feel sort of awkward somehow. (I think I'm enough conservative when using tools. I feel something shooting myself in the foot when doing it. It perhaps comes from my experience under UNIX-like environment...) The separated common repository for documents had room for integration of documentation. For example, I can put library documentations as well as overview page for included software such like Rust crates. It's flexible and logical in a view of top level of software stack. Thanks Takashi Sakamoto