From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Request for setup of new repositories
Date: Fri, 5 Aug 2022 19:26:38 +0900 [thread overview]
Message-ID: <YuzwXjaXXtufCTvo@workstation> (raw)
In-Reply-To: <edd3a849-13eb-9a21-963e-f8cc8deffe47@perex.cz>
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.
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2022-08-05 10:27 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
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 [this message]
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=YuzwXjaXXtufCTvo@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