►
From YouTube: ONNX Edge WG meeting 20190404
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
To
the
point
that
pissant
made
a
deal
so
first
of
all
this
night,
you
asked
what
we
showed
so
minion
was
thing
showing
the
presentation
that
we
had
on
day.
That's
right,
walking,
group
and
I
think
it's
a
good
idea
that,
on
under
the
walking
group,
a
repo
under
the
edge
directory.
The
first
read
me:
there's
a
readme
this
with
me.
We
can
definitely
write
down.
A
A
B
You
know,
as
I
said
you
know,
each
meeting
will
capture
who
attended
and
so
on
so
that's
end.
The
video
be
recording
so
I'm,
guessing
you'll
publish
recordings
in
the
same
people
here,
okay,
so
okay,
so
again
what
the
ball
first
said,
what
offer
said
was
that
what
I
was
showing
it?
These
are
the
slides
from
the
workshop
just
to
kind
of
for
people
who
didn't
attend
to
attend
the
session,
so
they
could
see,
but
you
know
what
was
presented
and
all
that
and
which
is
fixed
and
and
so
that's
the
body
so
now
I'm.
B
Moving
to
the
next
item
on
the
agenda
we
discussed
with
with
governance
and
and
maybe
flushed
out
what
we
discussed
in
the
workshop
talked
about
some
logistics
updates
about
like
future
meetings
and
in
a
survey
that
was
posted
now.
One
of
the
kind
of
discussion
points
in
that,
let
me
switch
to
this
was
posted
over
can
be
provided
abstract
and
we
would
like
to
finalize
the
statement
of
work
for
the
working
group.
So
we
have
goals.
B
B
Expand
on
the
software
work
from
the
workshop
and
the
document
was
was
posted
here
and
I
would
like
quick,
quick
comments
unless
anybody
had
a
chance
to
look
at
it,
but
also
our
goal
is
because
you
know
there
is
a
good
document
put
up
by
you
down.
We
are
only
we
felt
like.
Oh,
this
should
be
kind
of
folded
into
the
statement
of
work
document,
so
basically
there's
lots
of
material
there.
That
belongs
to
be
thanked
to
statement
of
work,
and
so
that
is
also
the
the
idea
here.
B
B
A
I
by
the
way,
I
transformed
Adams
earlier
document
into
APR
using
the
markdown,
the
working
group
repo,
so
there's
a
new
PR,
you
guys
should
be
able
to
see
I
think
we
can
either
just
you
know,
patches
the
the
s
o
W
paragraphs
like
as
patches
into
their
PR,
or
we
can
do
another
one
and
then
combine.
You
know
either
way
works
for
me.
So
this
this
is
the
one
yeah
yeah
yeah.
So
Martin
is
a
little
bit
easy
easier
to
review,
but
Google
Doc
definitely
easier
to
like
edit
and
yeah
I.
C
C
A
B
A
C
C
C
A
C
B
Guess
I
would
I
would
I
would
say:
let's,
let's
pick
pick
a
method
and
stick
with
it.
I
know
is
that
for
the
reviews,
I
really
think
that
Google
Doc
is
more
elegant
and
more.
You
know
flexible
to
collect
comments
and
then
once
we
have
something
that
is
fairly
reviewed,
I
think
then
it
can
be.
It
becomes
document
that
is
part
of
the
of
the
github,
and
you
know
we
get.
We
get
the
PR
we
got.
B
A
B
C
Just
before
that,
maybe
another
thing
about
how
to
comment
or
edit
so
right
now,
I'd
be
I,
made
a
document
so
that
anybody
can
put
comments.
I
already
see
that
a
few
people
are
no
green,
so
you
can
put
comments.
I
can
allow
anybody
to
add
to
edit
anybody
who
has
the
link
can
edit
I
didn't
know
if
I
want
to
do
that,
not
to
have
people
editing
on
top
of
the
other,
but
what
we
can
do
maybe
is
to
open
it.
Instead
of
commenting,
you
can
actually
direct
me
modify
the
text.
C
B
B
You
know
updating
comments
and
all
that
stuff
I
think
it's
gonna
be
more
control
versus
opening
document
for
anything,
but
obviously
everybody
can
comment
right
and,
and
that
gives
little
bit
more
structure
and
control.
I,
don't
know
what
the
others
think.
So
that's
why
I
see
also,
for
example,
in
Howard's
document
that
he
shared
before
meaning.
A
B
C
C
C
Anyways
right
now,
the
sections
that
exist-
I'll,
purpose,
scope,
organization,
deliveries
and
exit
criteria
and
milestones.
These
are
to
the
top
11,
the
sections
which,
let
me
briefly
describe
the
purpose,
and
then
we
can
I'd
be
happy
to
heal.
If
you
would
like
to
add
more
sections,
so
purpose
is
at
the
high
heaven
presenting
what's
the
goal
of
the
work
that
were
going
to
do
scope.
C
He
wants
to
briefly
describe
the
things
that
are
going
to
be
handled
it
more
in
a
thinking
of
domain
and
in
how
the
work
is
done.
It's
not
me
extending
if
you
think
about
it.
The
scope
organization
is
a
typical
third
chapter
that
talks
about
how
things
are
going
to
happen,
move
what
we
combed
in
the
meeting.
These
logisitics.
C
C
B
If
something
needs
to
be
specifically
communicated
with
six,
then
then
there
has
to
be
I
guess
we
are
creating
the
suggestions
and
requirements
for
six
right
at
some
level.
So
if
it's
requirement
for
sync
to
to
act
on,
then
it
needs
to
be
part
of
the
execute
area.
I
think
otherwise
it's
just
like
goes
nowhere,
but
I
mean
it's.
Maybe
subtlety
I
mean
video.
We
can
update
this
as
we
go.
B
Obviously
it's
not
maybe
we
should
be
fairly
agreed
at
the
beginning,
but
I
don't
think
this
is
the
document
that
is
cast
in
stone
at
start
off,
I
mean
it
could
expand
right
as
well
as
as
time
goes
at
least
my
view,
but
we
need
to
have
some
kind
of
agreement
about
that
about.
You
know
where
do
we
go
from
here
and
what
are
they,
our
deliverables
milestones
and
all
that
stuff?
If
you
would
like
to
meet
so?
Oh.
C
So
maybe
just
talking,
first
of
all
about
the
chapters
maybe
to
heal,
for
mothers
from
how
you
don't.
If
you
see
any
thing
that
you
would
like
to
see
in
additional,
if
I
look
at
the
document
that
you
created,
for
example,
that
talked
about
these
use
cases,
it's
something
that
my
view
formed
into
the
scope
and
into
the
deliveries.
So
I
can
see
a
directory.
You
can
already
placed
some
of
it.
C
B
B
C
B
So
guys,
what
do
you
think
I
mean
our
proposal
from
the
working
group
session
and
the
workshop
was
that
we
define
these
edge
profiles,
which
is
really
a
subset
of
onyx
set
and-
and
you
know
so
that
we
can
tie
that
these
these
edge
profiles
to
to
compliance-
and
you
know
how
do
you
say
you
know
so
people
can
say:
I
am
onyx
edge
profile,
one
compliant
whatever
something
like
that
right
and-
and
that
is
really
what
this
in.
Your
in
a
nutshell,
describes.
B
B
I
agree
so
I,
just
like
maybe
put
a
little
bit
color
and
flavor
to
what
was
discussed
right
in
the
workshop
and,
and
so
we
are
following
up
on
our
proposal
from
the
workshop
that
we
define
is
profiles
so
now
actually
big.
Looking
at
what
Howard
shared
before
the
meeting,
it
seems
like
days
also
proposal
there
from
our
that
we
define
onyx
runtime
for
edge
profile,
sort
of
big
and
or
onyx.
What
do
you
call
it
onyx
edge
runtime
on
its
runtime,
French,
okay
and-
and
so
this
is
something
that
we
need
to
discuss.
B
A
Okay,
so
a
perper
SW
document
I
think
overall,
our
vision
are
aligned,
so
the
the
profile
mentioned
here
is
very
similar
to
the
scenario
concept
we
we
talked
about
so
in
a
higher
level.
I
would
suggest
to
add
one
section
to
describe
related
working
group
and
six,
so
we
don't
need
to
carry
into
very
specific,
because
this
is
only
as
a
so
W
document.
So
we
we
just
list
out
possible,
related
onyx
working
groups
and
six
that
to
the
edge
working
group.
A
So,
for
example,
a
conversation
working
group
might
be
one
and
also
our
team
is
working
on
setting
up
a
model
zoo
CI
for
next,
so
that
would
also
related
to
the
compliance
piece
of
the
puzzle.
You
guys
mentioned
in
the
scope,
which
we
agree
will
be
very
important,
so
I
would
suggest
we
just
add
another
session,
very
short
session,
section
related
working
group
and
six
and
okay,
just
lease
them
and
yeah
leave
out
the
details
like
how
we're.
D
A
A
B
C
C
A
D
B
So
I
guess
this
is
something
that
I
would
need
to.
We
need
to
kind
of
establish
regular
touch-up
in
between
chairs
I
would
say,
then
to
make
sure
that
they
are
aware
of
what's
going
on
in
in
our
group
right,
and
so
we
need
to
identify
this
working
group.
So
we
want
to
kind
of
be
in
touch
with
nine,
six
and
so
I
think
quantization
is,
it
clearly
seems
like
one
of
them,
at
least
from
from
what
we
discussed
in
the
past,
but
then
compliance
is
another
one
right.
A
Another
suggestion
is
for
deliverables
or
deliveries.
I
think
we
can't
categorize
into
like
two
areas.
So
one
day's
document
you
know
will
define
all
the
profiles
scenarios
whatever
and
the
other
kind
of
deliver
book
could
be
like
code,
but
I
don't
think
we
should
restrict,
restrict
li,
define
anything
in
that
so
w,
so
it
could
be
just
any
necessary
implementation
of
the
say
profile
or
so
so
we
just
point
out
that
there
might
be
some
code
produced
by
by
the
working.
Maybe.
A
C
So
the
point
of
contributing
code
was
kind
of
unclear
to
us
in
the
in
the
governance.
More
than
that,
the
Facebook
and
Microsoft
presented
I
think
the
ideal
is
a
working
group
doesn't
own
code
but,
as
you
just
said,
it
doesn't
work
who
does
form
suggesting
code
that
can
be
adopted
by
some
sick
yeah.
A
Yeah,
so
from
like
other
open-source
communities,
past
experience,
so
basically
it's
like
the
folks
from
this
working
group
will
develop
code
in
like
I'm,
sorry
upstream
project,
it's
kind
of
that
relationship,
so
the
working
group
doesn't
own
the
code
per
se.
It's
the
people
from
the
working
group
that
knows
the
problem
that
will
help
develop
the
code
and
implement
the
code
whatever
in
the
upstream
project,
was
seek
or
or
whatever
yeah.
D
B
B
So
listen
so
they
are
five
minutes
away
from
the
Reno
meeting,
because
I
did
shorten
it
by
five
minutes
because
of
our
other
engagement
me
or
not,
for
I
have
to
go.
I
would
like
to
end
so
now
on
the
structure.
The
goal
of
this
was
to
kind
of
make
sure
that
structure
captures
all
that
you
own
so
I
think
collaboration
is
very
good.
One,
so
I
think
could
be
conclude
that
in
general,
this
group,
just
this
attending
this
meeting,
agrees
on
this
structure
S&W
and
then
as
an
action
item.
A
B
B
A
B
C
B
A
B
C
B
Good
right,
yeah,
okay,
how
about
this
I
mean
I
was
I
was
thinking
that
maybe
this
is
a
bit
going
in
a
different
direction,
but
you
know
I
started
this
meeting.
Isn't
every
meeting
will
have
its
MB?
So
why
don't
I,
just
published,
MB
or
reek
Weber
is
publishing
agenda,
publishes
the
document
for
the
next
meeting
and
puts
agenda
proposal
in
there,
and
then
people
can
directly
I
guess
comment
to
the
to
the
to
the
document.
I
guess
sure
and
then
in
the
same
document
you'll
also
have
will
be
updated
to
into
a
meeting
minutes.