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 315AEC00140 for ; Fri, 5 Aug 2022 11:00:07 +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 72C87857; Fri, 5 Aug 2022 12:59:15 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 72C87857 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1659697205; bh=LssB9q3XMKoQ7EQVGAPiqx6YyVoJ1gOAG2EdUpuUblc=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=kilpbWtAj9Z3WysLsrC5LwoTDMwpJuMyDG+/Rr53GQBUvpfUoSRsfqDdRUR72pMVp MmE1zFvB6rzjoT3FzwDexOp9ArxDCYWHa4lAoUGq179hDdZUyGhrvFnKTWQA5n/bL7 EVvlihSL5qBJUkDrS+3ik+fvibhAcwEdQ9Q4TJ2c= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 0311FF80238; Fri, 5 Aug 2022 12:59:15 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id D0EE3F8025A; Fri, 5 Aug 2022 12:59:13 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 6B79CF8012F for ; Fri, 5 Aug 2022 12:59:02 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 6B79CF8012F Authentication-Results: alsa1.perex.cz; dkim=pass (2048-bit key) header.d=sakamocchi.jp header.i=@sakamocchi.jp header.b="Ib4Ih7Fs"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="MtgfGA2y" Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C92EC5C0175; Fri, 5 Aug 2022 06:59:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 05 Aug 2022 06:59:00 -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=fm3; t=1659697140; x=1659783540; bh=J9 jqBL02tSkO0UyBxOMMW/ul/aSlaa4FpaM0KMvv7Wk=; b=Ib4Ih7FsTNSWuIQOUb NDk3bCJkYf4SIktyRZVWRwTPmn7RXCYUlCGvKFDVDjuXWViGD9o9UabtwSHNir/Q Uyy78iUzSQYhpMkc3KHTqGKBlfkKTK3HvqjL57fSYzORpWE6tNxLeaV3BZVx2LUJ nSXRLyfI9WzRVzvsuDeOzRwO3KKgx9KOox80BiLJG8EKxm8oNwE+d4q2r2trbfbf 5uKSO7Rv611t0q9HD3P5AgKzlLiKsq7Z+mHKHe9RmuBaolJC5hhZat+JSBf5ONaJ qNZDnIC2qZE71aZhZVbsdW4li1Qx0/cSbnA0T5e0DjzktO3yIL9w9a57IbpAxns9 R3TQ== 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= fm3; t=1659697140; x=1659783540; bh=J9jqBL02tSkO0UyBxOMMW/ul/aSl aa4FpaM0KMvv7Wk=; b=MtgfGA2ykRRQA/ic6Em9KkvQU+GCH73Y4y+n6NLMZB85 Q0iDElVDOX0qCCFLpx2Mas/3q9l6wkeK/AYzs1eIicnVMdUrQZogJ6B6VtqW2U2L zKhNLklawb51/oaLgoVwtRfRwxcsbzGXv2r4eMY7ifeOiQ74g/IFg9J2rPvqwanP xotozlVWXUOJwIBcJpAJE8xvV6ATcepJ7zDVqg+6eJrYdR9rEEgZMXPEyao1fOFe aoNftb3BVYBy8iO16XFhLPLDYXJn03KRlSNGYi5l84oBHTo/L2I2X5mgoyUZg8/X dFlSjvlEfSBFU46BSpOZqYuizGw3Heq9+jRvnvc6lg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdefuddgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne goufhushhpvggtthffohhmrghinhculdegledmnecujfgurhepfffhvfevuffkfhggtggu jgesthdtredttddtvdenucfhrhhomhepvfgrkhgrshhhihcuufgrkhgrmhhothhouceooh dqthgrkhgrshhhihesshgrkhgrmhhotggthhhirdhjpheqnecuggftrfgrthhtvghrnhep veeihfettefhfedtheeuvddvudekjeeflefhudekjeefjeehhfefveeihefhhfevnecuff homhgrihhnpehgihhthhhusgdrtghomhdpghhithhhuhgsrdhiohdprhhushhtqdhlrghn ghdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehoqdhtrghkrghshhhisehsrghkrghmohgttghhihdrjhhp X-ME-Proxy: Feedback-ID: ie8e14432:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 Aug 2022 06:58:59 -0400 (EDT) Date: Fri, 5 Aug 2022 19:58:56 +0900 From: Takashi Sakamoto To: Jaroslav Kysela Subject: Re: Request for setup of new repositories Message-ID: Mail-Followup-To: Jaroslav Kysela , ALSA development , Takashi Iwai References: <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 development 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 Fri, Aug 05, 2022 at 12:42:59PM +0200, Jaroslav Kysela wrote: > On 05. 08. 22 12:26, Takashi Sakamoto wrote: > > Hi Jaroslav, > > > > I apologize to be late for reply to the message, but I'm under heavy load > > to publish Rust crates recent few months. > > > > On Thu, May 26, 2022 at 03:35:40PM +0200, Jaroslav Kysela wrote: > > > On 26. 05. 22 14:58, Takashi Sakamoto wrote: > > > > Later I'd like to use Jekyll backend of github pages[1]. Would I ask you > > > > to grant my privilege in the repository so that I can add configuration > > > > for it? I think the same privilege set in libhinawa-docs is enough. > > > > > > It seems that it's just a configuration file which is stored in the > > > repository, so the standard github pages setup should be sufficient. > > Indeed. I can publish github pages with Jekyll backend with the concise way > > just to put `_config.yml` and markdown files without such privilege. > > > > > Anyway, I made you as maintainer of this gobject-introspection-docs repo, so > > > you should do more changes in it, if you like. > > Thanks for your arrangement, however I can see my privilege in repository > > settings just for archived alsa-gobject-docs... > > > > * https://github.com/alsa-project/alsa-gobject-docs/ > > > > Anyway I'm not so eager to have the privilege now since it's enough at > > present. > > > > > > By the way, now I published 30 Rust library crates in crates.io, > > enumerated in this page: > > > > * https://alsa-project.github.io/gobject-introspection-docs/crates.html > > > > Currently I'm an owner of the crates, while I'd like to prepare the > > possibility to grant ownership to the other developers for future > > accident. Then I'm investigating to use "team" owner feature of crates.io > > service. > > > > For the feature, the service of crates.io needs to query team membership > > in github.com, but the service should be permitted it by github service. > > > > * https://doc.rust-lang.org/cargo/reference/publishing.html#github-permissions > > > > According to the above document, the way to grant the permission seems > > to be either to remove crates.io from the blacklist or add crates.io to > > the whitelist of organization's third-party access page. > > > > If you, organization manager, don't mind OAuth access from crates.io, I'd > > like to request it via my github account. I guess that alsa-project > > organization currently has no effective configuration to third-party > > application access policy. When I requested it, you can see something > > new in the page of policy, then I'd like you to grand the access. When > > granted, I will operate settings for the crates to add team owner. > > It seems that 'maintainer' priviledges are not enough - changed to 'admin' > for your account in the gobject-introspection-docs repo. Thanks for your kindness. I can now see settings page itself and many items in it. > I have no objections for the OAuth access from crates.io . Ok. Just now I sent the request to organization. I'm waiting for the acceptance notification. Thanks Takashi Sakamoto