From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: perex@perex.cz
Cc: alsa-devel@alsa-project.org
Subject: Move ownership for repositories in Github related to gobject-introspection
Date: Wed, 17 Jun 2020 17:01:14 +0900 [thread overview]
Message-ID: <20200617080114.GA265611@workstation> (raw)
Hi Jaroslav,
Now I'm going to prepare for official release of alsa-gobject v0.1.0.
At the same time, Rust binding is also OK to be released. Currently It's in
my private repository[1] but I think it better to put under alsa-project
project account in Github.
Github supports transferring ownership, and this time I'd like to utilize the
feature if you don't mind it. After transferring. some arrangement for the
repository are perhaps required; e.g. to put it to 'gobject-introspection'
team[3]. Would I ask it to you?
Additionally, I'd like to move repositories for libhinawa[4][5][6] as well,
which is required to make up control service in user space for devices
supported by ALSA firewire stack[7].
[1] https://github.com/takaswie/alsa-gobject-rs/
[2] https://help.github.com/en/github/administering-a-repository/transferring-a-repository
[3] https://github.com/orgs/alsa-project/teams/gobject-introspection
[4] https://github.com/takaswie/libhinawa
[5] https://github.com/takaswie/libhinawa-docs
[6] https://github.com/takaswie/hinawa-rs
[7] https://mailman.alsa-project.org/pipermail/alsa-devel/2020-June/168550.html
Regards
Takashi Sakamoto
next reply other threads:[~2020-06-17 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 8:01 Takashi Sakamoto [this message]
2020-06-17 11:15 ` Move ownership for repositories in Github related to gobject-introspection Jaroslav Kysela
2020-06-17 12:57 ` Takashi Sakamoto
2020-06-17 13:07 ` Jaroslav Kysela
2020-06-17 13:17 ` Takashi Sakamoto
2020-06-17 14:57 ` Jaroslav Kysela
2020-06-17 22:29 ` 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=20200617080114.GA265611@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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