From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Keyon Jie <yang.jie@linux.intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
arnd@arndb.de
Subject: Re: Audio miniconference schedule
Date: Sun, 21 Oct 2018 11:46:15 +0200 [thread overview]
Message-ID: <s5hh8hftyxk.wl-tiwai@suse.de> (raw)
In-Reply-To: <ead8299e-15a9-b68e-9ad1-7635dfdfecf6@perex.cz>
On Sun, 21 Oct 2018 10:12:30 +0200,
Jaroslav Kysela wrote:
>
> Hi all,
>
> any news about the remote participation? Could I join?
I'm seeing your name on the machine now. Do you hear us?
We're in a coffee break, and waiting for your attend.
Takashi
>
> Thanks,
> Jaroslav
>
> Dne 19.10.2018 v 18:14 Jaroslav Kysela napsal(a):
> > Dne 19.10.2018 v 16:35 Charles Keepax napsal(a):
> >> On Thu, Oct 18, 2018 at 06:44:14PM +0100, Mark Brown wrote:
> >>> On Thu, Oct 18, 2018 at 01:53:08PM +0800, Keyon Jie wrote:
> >>>
> >>>> Is it possible to set up network meeting that any hobbies can dial in and
> >>>> join in remotely?
> >>>
> >>> I would assume so, I'm pretty sure it's standard technology in Cirrus,
> >>> though we'll have to see how well it works in practice (these things are
> >>> always a bit "fun"). We hadn't planned anything yet though.
> >>>
> >>> I'd guess that probably the safest thing would be if one of the Intel
> >>> people has a laptop with whatever conferencing software you usually use
> >>> internally they can bring that in and call you, or at least message with
> >>> you about getting stuff set up if we set some other solution up.
> >>
> >> Yeah it will probably have to be Lync if we are setting it up
> >> with Cirrus stuff, but should be do-able.
> >
> > Hi all,
> >
> > I would recommend to use a browser like services like
> > http://bluejeans.com/ or https://www.gotomeeting.com/ . Both seem to be
> > really usable and there is no requirement to install a special client
> > application to join.
> >
> > Thanks,
> > Jaroslav (who is not able to participate physically this year)
> >
>
>
> --
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
>
next prev parent reply other threads:[~2018-10-21 9:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 19:58 Audio miniconference schedule Mark Brown
2018-10-05 10:20 ` Charles Keepax
2018-10-05 11:44 ` Mark Brown
2018-10-14 5:50 ` Patrick Lai
2018-10-15 10:24 ` Mark Brown
2018-10-16 20:48 ` Mark Brown
2018-10-16 21:16 ` Takashi Iwai
2018-10-17 19:12 ` Mark Brown
2018-10-18 5:53 ` Keyon Jie
2018-10-18 17:44 ` Mark Brown
2018-10-19 3:06 ` Keyon Jie
2018-10-19 14:35 ` Charles Keepax
2018-10-19 16:14 ` Jaroslav Kysela
2018-10-21 8:12 ` Jaroslav Kysela
2018-10-21 9:01 ` Charles Keepax
2018-10-21 9:46 ` Takashi Iwai [this message]
2018-10-18 10:12 ` Takashi Sakamoto
2018-10-24 7:16 ` Takashi Iwai
2018-10-24 7:30 ` Jaroslav Kysela
2018-10-24 7:33 ` Takashi Iwai
2018-10-24 8:11 ` Vinod
2018-10-24 8:51 ` Jaroslav Kysela
2018-10-24 10:08 ` Vinod
2018-10-24 10:24 ` Mark Brown
2018-10-24 10:16 ` Charles Keepax
2018-10-18 17:55 Mark Brown
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=s5hh8hftyxk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=yang.jie@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.