Hi,

On Wed, Jun 17, 2020 at 01:15:30PM +0200, Jaroslav Kysela wrote:

Dne 17. 06. 20 v 10:01 Takashi Sakamoto napsal(a):

...

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].

Hi,

I have no objections against that proposal. I will try to configure the repositories when transferred to the alsa-project organization.

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.

Thanks

Takashi Sakamoto

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?

[1] https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/tree/include...

Thanks

Takashi Sakamoto

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