From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Move ownership for repositories in Github related to gobject-introspection
Date: Thu, 18 Jun 2020 07:29:13 +0900 [thread overview]
Message-ID: <20200617222913.GA279571@workstation> (raw)
In-Reply-To: <3feba622-81f6-f2a6-b4dd-289d98f0aca2@perex.cz>
On Wed, Jun 17, 2020 at 04:57:22PM +0200, Jaroslav Kysela wrote:
> Dne 17. 06. 20 v 15:17 Takashi Sakamoto napsal(a):
> > On Wed, Jun 17, 2020 at 03:07:02PM +0200, Jaroslav Kysela wrote:
> > > > Thanks for your approval. Just now I transferred below four repositories
> > > > from my account to alsa-project account:
> > > >
> > > > * https://github.com/alsa-project/alsa-gobject-rs
> > > > * https://github.com/alsa-project/libhinawa
> > > > * https://github.com/alsa-project/libhinawa-docs
> > > > * https://github.com/alsa-project/hinawa-rs
> > > >
> > > > Fortunately I can select the 'gobject-introspection' team as destination
> > > > of the transferring, but I'm grant for read-only access. Would I request
> > > > you to grant my account Admin (or Writeable) right?
> > > >
> > > > And you made 'Hinawa' team and put libhinawa/hinawa-rs repositories into
> > > > it. But in my preference they're in 'gobject-introspection' team as well
> > > > as alsa-gobject repositories.
> > >
> > > I created new 'Hinawa' team and changed the priviledges for all new repos
> > > appropriately.
> > >
> > > If something is wrong, let me know.
> >
> > The half of libhinawa is an application of ALSA hwdep interface to
> > implement user/kernel interaction described in 'include/uapi/sound/firewire.h'[1].
> > (The rest is an application of Linux FireWire stack.)
> >
> > Furthermore, in a point of application of gobject-introspection and
> > abstraction to a kind of ioctl requests, libhinawa and alsa-gobject has
> > similar design. For me, it's convenient to put them into the same
> > 'gobject-introspection' team without adding the specific team.
> >
> > Would I request you to put all of them under 'gobject-introspection'
> > team, again?
>
> Ok, done, the 'GObject Introspection' team is member of 'Hinawa' team now.
Thanks for your arrangement. However, I would not expect the 'Hinawa' team
itself and I would like to continue to use 'GObject Instrospection' team only...
Would I request you to delete the 'Hinawa' team from 'alsa-project'
project, and put all of the repositories under 'GObject introspection' team
under 'alsa-project' project?
Regars
Takashi Sakamoto
prev parent reply other threads:[~2020-06-17 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 8:01 Move ownership for repositories in Github related to gobject-introspection Takashi Sakamoto
2020-06-17 11:15 ` 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 [this message]
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=20200617222913.GA279571@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