From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Restart alsa-gi project as alsa-gobject project
Date: Sat, 28 Dec 2019 13:30:50 +0900 [thread overview]
Message-ID: <20191228043049.GA23459@workstation> (raw)
In-Reply-To: <7a871b7b-a36d-db9c-5b40-ccfdc2373400@perex.cz>
Hi Jaroslav,
On Wed, Dec 25, 2019 at 12:11:29PM +0100, Jaroslav Kysela wrote:
> > For alsa-gobject repository, I file two PRs for improvements:
> > * https://github.com/alsa-project/alsa-gobject/pull/1
> > * https://github.com/alsa-project/alsa-gobject/pull/2
> >
> > I'm glad if you grant these requests and merge. Or would I
> > merge them by myself? I think that we have no concrete policy
> > to maintain the repository.
>
> Could you keep to maintain this repository? You should have all rights set
> on github.
Thanks for your arrangement. I merged the PRs.
Well, now I'm working for userspace services to add/maintain control
elements for sound cards bound to audio and music units on IEEE 1394
bus. The services listen application's events from ALSA control character
device to control internal DSP on the units. The services are programmed
with libraries of alsa-gobject and libhinawa by Rust languages. For
this work, I generate Rust crates for these libraries by gtk-rs/gir[1].
Next year, I'd like to add repositories for the crates, listed
below:
* alsa-gobject-rs-sys
* sys crates for libraries in alsa-gobject
* alsactl-rs
* safe API crate for libalsactl0
* alsaseq-rs
* safe API crate for libalsaseq0
Additionally, I'll push libhinawa v2 release to GObject Introspection
team of github.com/alsa-project and corresponding Rust crates. Thus
below repositories will be added:
* libhinawa
* hinawa-rs-sys
* sys crate for libhinawa2
* hinawa-rs
* safe API crate for libhinawa2
I'm glad if you accept my proposal for the above repositories next year.
Have a great holidays.
[1] https://github.com/gtk-rs/gir
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-12-28 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 8:04 [alsa-devel] Restart alsa-gi project as alsa-gobject project Takashi Sakamoto
2019-12-04 0:33 ` Takashi Sakamoto
2019-12-04 9:10 ` Jaroslav Kysela
2019-12-04 13:34 ` Takashi Sakamoto
2019-12-13 11:17 ` Jaroslav Kysela
2019-12-14 16:52 ` Takashi Sakamoto
2019-12-18 19:20 ` Jaroslav Kysela
2019-12-22 8:04 ` Takashi Sakamoto
2019-12-25 11:11 ` Jaroslav Kysela
2019-12-28 4:30 ` 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=20191228043049.GA23459@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;
as well as URLs for NNTP newsgroup(s).