►
From YouTube: CDF SIG Interoperability Meeting 2020-05-28
Description
SIG Interoperability 20200528 145730
A
A
A
D
A
A
Probably
have
time
for
additional
topics
as
well.
So
if
you
want
to
bring
up
anything,
please
feel
free
to
add
it
to
agenda
and
medium.
Take
it
doing
time,
I
think
the
agenda
is
action.
Item
review,
I
think
we
have
two
action
items
from
last
meeting
and
then
we
have
quick
announcement.
Rancic
co-chair,
followed
by
cig
load,
map,
discussion
and
I
see.
A
A
So,
as
I
mentioned,
the
co-chair
we
had
Christie
had
some
other
commitments
and
she
excused
herself
from
a
co-chair
position
and
then
we
had.
We
opened
up
two
nominations
again
in
18th
of
May
and
tres
nominated
Kara
as
the
co-chair
and
this
Monday
few
days
ago
and
Cara
I
see
you
accepted
the
nomination.
So
thank
you
for
that,
and
perhaps
you
want
to
introduce
yourself
to
the
rest
of
the
team.
Yes,.
E
A
Going
on
welcome
so
this
will
really
help
it's
it's
yeah,
it's
fun
things,
but
at
the
same
time
you
know
it's.
Sometimes
it
came
becomes
difficult
to
know
how
to
community
hit
the
organizing
thing.
So
thanks
a
lot
again
so
I
think
we
are
done
with
that,
because
no
nation
period
ended
12:00
UTC
during
today,
and
Cara
was
the
only
nominee,
so
we
have
Cara
as
co-chair
and
we
will
have
committed
to
round
things
to
things
and
the
next
topic.
F
If
I
could
jump
in
I
see
lots
of
new
people
on
the
call
which
is
awesome.
So
it's
wondering
if
we
could
spare
maybe
a
couple
of
minutes
just
for
folks
to
say
hi,
and
so
we
kind
of
reintroduce
ourselves
or-
and
the
new
folks
can
also
say
what's
of
interest
or
is
here
to
learn
or
interested
in
a
particular
topic.
I'd
love
to
yeah
just
say
hello
to
everybody.
Yeah.
G
Hi
I'd
see
jarabe
I'm,
a
software
engineer,
goo
goo
I'm
here
representing
the
tech
22
yeah,
which
is
like
a
project
as
part
of
CDF
and
I'm.
A
software
engineer
at
Google,
as
Chen
Han
said.
If
I
show
you
where
we're
from
I'm
originally
from
Kenya
but
spent,
went
to
college
in
Boston
and
kindly
leaving
New
York.
A
H
Everybody
Robby
LACMA
and
I
work
at
harness
I
brother
evangelism
programmer
harness
very
excited
to
be
here.
This
is
actually
my
first
Linux
Foundation,
cig,
I
actually
didn't
know
what
a
cig
stood
for
until
recently,
so
very
excited.
The
joy
I
represent
hard
as
I
live
in
the
Atlanta
area,
from
Atlanta
Atlanta
and
all
things
the
lattice
they're
very
excited
to
be
participating.
A
I
A
Maybe
we
can
move
to
the
secret
map
if
there
is
no
other
topic
to
bring
up
quick
one.
So
I
want
to
start
again
with
thanking
Tracy
king
of
this
I
think
it
was
a
month
or
two
months
ago,
Tracy
took
this
all
run,
started
the
document
on
Google
Docs,
with
some
initial
ideas
and
since
we're
having
meeting
for
a
while
now-
and
there
are
few
common
areas
that
are
appearing
based
on
the
conversations
we've
been
having
within
the
Sikh
and
based
on
the
presentations.
A
A
So
because
of
that,
I
put
some
use
cases
that,
based
on
what
we
have
been
experiencing
within
Erickson
or
across
different
of
source
communities,
followed
by
some
of
the
areas
which
we
can
perhaps
start
talking
about
and
perhaps
start
working
on,
and
then
a
proposal
on
how
we
can
work
on
those
things.
Perhaps,
by
creating
work
streams
and
asking
interest
people
in
to
join
those
work,
streams
and
drive
the
topic
forward
and
perhaps
reach
out
to
other
communities,
either
hosted.
A
J
A
F
And
I'm
happy
to
say
a
bit
more
about
the
go
SEM,
which
I
think
could
be
a
very
kind
of
specific
thing
that
we
we
work
on
or
we
drive
for
in
in
this
group
and
find
find
the
right
people
to
get
involved.
So
if
you
click
on
the
link
and
I'll
just
say
a
bit
more
of
what
this
is
so
go
SEM,
so
the
SEM
is
current
source
code
management
was
originally
a
library
that
was
part
of
the
drone.
F
I/O
project
and
drone
is
another
CI
CD
tool,
but
this
library
was
pretty
useful
and
the
Jenkins
ex
folks,
forked
it
for
use
in
Jenkins
X,
and
then
they
created
a
few
enhancements.
They
had
a
readme
and
some
other
features
and
Tecton
also
is
interested
in
using
it.
The
functionality
is
that
it
lets
you
connect
up
to
different
source
code
management
and
it
kind
of
fits
under
the
whole
for
those
familiar
with
Jenkins
X
architecture.
F
This
project,
the
lighthouse
project,
which
is
to
give
you
know
proper
integration
regardless
or
whether
you
use
a
kind
of
github
or
bitbucket
or
whatever
it's
the
standardized
way
of
just
being
able
to.
Let
any
tool
connect
into
that.
So
we
try
to
see
what
the
drone
folks
wants
us
to
do.
So
Christy
submitted
this
issue.
We
didn't
hear
back,
but
regardless
we
were
thinking
about
how
we
could
have
a
shared
place
that
both
Jenkins
X
and
Tecton
could
use.
So
is
that
putting
it
under
Tecton?
F
Is
it
that
put
it
under
Jenkins,
X
or
what's
emerging
is
sort
of
saying?
Should
we
have
a
CDF
set
of
libraries
as
kind
of
a
standalone
project
or
library
would
probably
be
a
better
description?
It's
not
something
you
can
use
itself,
but
this
would
be
kind
of
blocks
that
different
projects
could
you
and
we
would
encourage
a
lot
of
projects
in
CDF
to
to
use
them
rather
than
having
their
own
implementations
so
yeah?
Well,
I.
F
A
A
A
K
Can
just
say
emitter
I
think
also.
This
sounds
like
a
very
good
thing
in
interoperability
area.
It's
not
really.
Maybe
interoperability
between
see
I
see
a
little
spot
between
SCM
systems
done
in
this
case,
but
I
was
thinking.
What
is
the
backend
interface
then,
from
this
go
SEM
to
the
Jenkins,
X
and
Tecton
and
and
Rowan?
Is
that
some
common
interface
as
well
or
is
that
coodinator
series
or
how
is
that
interface
managed?
Do.
F
F
Agree
and
I
think
this
kind
of
leads
into,
and
maybe
we
need
to
invite
Andrew
Bayer
along
one
of
the
authors.
It
leads
into
the
whole
like
again,
there's
a
proud
to
Lynne
the
community's
land
and
then
Jenkins
excess,
it's
kind
of
evolution
of
that
which
is
a
lighthouse
project
and
maybe
that
something
as
well
that
I
think
that
covers
all
the
the
web
hooks
as
well
having
just
a
common
way
to
do
that.
So
it
is
a
fixed
APR,
a
I
believe.
A
F
A
I'm
typing
here
three,
so
you
can
fix
the
names,
Kristy
and
James
links
correctly.
Okay,
this
course
yeah,
okay,
I,
think
we
I
I,
hear
some
agreement
on
this
topic
like
we
are
talking
on
go
SCM,
especially,
but
it's
kind
of
falls
under
this.
Identifying
and
coordinating
work
on
usable
libraries
so
and
go
STM
could
be
the
first
one
in
this
area
which
can
pave
way
for
other.
You
know
common
libraries,
investigation
and
so
on.
F
A
A
I
was
thinking
like
that
could
be
the
one
of
the
work
items
for
this
work.
Streams
to
you
know
work
on
a
proposal.
Okay,
we
have
this
go
a
cm
here.
It
falls
under
this
category
or
area,
and
we
believe
it
should
be
done
this
way:
okay
under
Techtron
under
CDF
as
a
separate
repo
and
alone
project,
and
then
that
proposal
could
be
discussed
within
the
city
as
well
and
then
highlights
to
take
committee.
Perhaps.
F
A
F
Yeah
I
could
kick
off
a
document
and
just
put
kind
of
the
headlines
in
and
then
maybe
get
everybody
to
help
flesh
out
different
sections.
So
the
folks
are
familiar
with
it
can
detail
what
the
interfaces
look
like
and
what's
a
good
way
to
limit
and
just
have
everybody
else,
ask
ask
the
right
questions
and
make
sure
it
makes
sense
and.
A
B
Project
as
something
that
they
needed,
which
is
very
common,
lots
of
lots
of
organizations
develop
libraries
that
may
not
be
under
their
privy,
but
they
need
it
anyway
and
they
say
put
it
under
the
organization
and
get
up,
but
from
a
just
functional
area.
Does
it
even
fall
under
continuous
delivery,
see
ICD
I.
K
K
B
B
B
H
Would
it
be
I
agree
with
ramen
right
like
not
to
be
the
one
walking
to
votes?
This
is
my
first
meeting,
but
I
was
curious
where
you
know
where
we
draw
the
line
in
the
sand
right,
maybe
I'm
just
reading
over,
like
the
like
the
state
court
or
the
portion
of
the
document.
Maybe
it's
like
how
things
enter
the
pipeline
right?
Wait
because
there's
lots
of
ways
how
you
trigger
things,
there's
lots
of
ways
how
you
go
about
executing
things.
H
So
every
tool
does
differently,
like
artists
have
specific
ways
that
it
you
know,
needs
to
interact
with
the
SCM
provider.
Is
that
what
we're
kind
of
gardening,
for,
like
interoperability
like
get
that
low
of
a
level
or
I
think
without
what
you're
getting
at
Rama?
Nor
am
I
off
the
mark?
What
you
were
hinting
at
anything
though?
H
B
I'm,
having
been
in
this
industry
a
long
time,
I'm
always
you
know,
I
always
have
an
ear
or
my
both
ears
out
for
scope
creep.
It's
something
that
just
kind
of
it
raises
flags
with
me.
What,
when
I,
what
I
see
things
are
that
may
not
necessarily
belong
to
a
particular
thing:
I'm
working
on
start
to
creep
in
we
I
mean
if
we,
if
we
use
that
as
the
bar
there's
lots
of
things,
I
mean
that
there's
the
image
building
there
is
the
access
to
various
other
systems.
That.
F
I
think
it's
very
worthwhile
and
and
I
think
it's
good
to
have
the
discussions
and
yeah
welcome
the
rocking
the
boat
as
well
Ravi
in
some
ways
like
I
know,
when
the
talk
started
off
the
Charter
was
to
embrace
the
software
delivery
lifecycle
and
and
that
you
know
as
a
remit
its
way
to
do
broad
like
we're
not
going
to
say.
Okay,
let's
have
every
kind
of
IDE
integration
we
could
have
or
certain
things
which
you
I
would
say.
F
Clearly
like
are
less
obvious
fits,
but
actually
the
examples
you
gave
of
things
like
Kanak,
oh
I
would
say:
yes
if
they
isn't
a
place
and
there's
a
need
that
it
fails
for
for
the
projects
that
are
pre-existing
here.
Then
then,
that's
that's
a
good
starting
point
or
that's
a
good
way
to
do
it
and
I,
don't
think
the
industry
is
clean-cut
as
to
have
you
know,
source
control,
management
foundation
or
you
know
people
say
well.
A
Okay
contains
the
foundation,
but
at
the
same
time,
surrounding
ecosystem,
and
that
is
one
of
the
reasons
why
I
include
this
the
bullet
point
just
above
the
NGO
SCM,
because
even
though
we
might
have
Jenkins
pinnacle,
we
are
interacting
interfacing
with
other
tools
that
are
required
for
us
to
build
up
the
pipelines
and
yeah.
It's
right
that
very
well.
We
should
put
the
line,
but
it's
not
not
sometimes
that
easy.
A
No
and
almost
all
times
we
have
to
put
our
own
fixes
around
these
things
to
make
them
work
or
talk
in
certain
way
and
again,
if
I
speak
as
a
user.
This
is
a
problem
we
are
facing
on
a
daily
basis,
especially
the
teams
adopting
new
tools
and
new
ways
of
doing
like
some
teams
used
apply.
Other
teams
use
get
it,
and
that
brings
that
problem
into
see.
I
see
the
domain
when
you
start
building
up
pipelines.
B
And
just
just
once
again,
just
following
on
with
the
devil's
advocate:
oh
gee,
if
I'm
a
goal
developer,
I
can
totally
see
that
I
would
need,
go
SEM
or
library
like
it
to
access
other
various
sen
s--.
You
know
independent
of
in
whether
or
not
it
runs
in
a
CD
pipeline.
It
is.
It
is
a
library
to
access
very
assessment
if
I'm
ago,
developer
and
a
story
period
and
I
can
totally
see
this
kind
of
a
library
coming
out
of
the
drone
organization
and
github
and
going
into
the
NGO
organization
under
the
NGO
organization.
B
As
a
library,
in
fact,
that's
what
it
sounds
like
where
it
belongs,
and
we
could
say
the
same
thing
about
all
all
the
various
other
things
is
that
also
get
accessed
during
a
CD
workflow,
as
I.
Think
of
all
the
authentication
mechanisms.
How
many
of
those
are
there?
We
could
go
on
for
days
coming
up
with
things
that
that
CD
pipelines
access
and
use,
so
just
just
bringing
up
the
you
know,
just
making
sure
making
sure
we
keep
our
focus
on
continuous
delivery
type
of
functionality.
B
You
know
Tecton
is
very
clear:
Jenkins
X,
that's
very
clear,
spinnaker,
very
clear,
there's!
No!
These
are.
These
are
CD
orchestration
engines,
there's
no
other
place
where
you
live.
In
fact,
that's
why
CDF
won,
but
all
the
ancillary
things
that
touch
CD,
workflows,
I,
just
caution
against
a
scope
group.
That's
all.
A
And
that
was
great
point
but
yeah,
but
this
could
be
an
item
for
the
team.
Do
you
know
like
its
focus
area?
If
we
agree,
this
could
be
a
focus
area
first
place,
so
you
know
come
up
with
that
type
of
know.
Input
as
well.
Maybe
with
one
of
the
outcomes
could
be
I.
It
doesn't
belong
here.
We
we
should
be
careful
about
what
we
are
know
bringing
in
and
so
on.
Just.
K
A
comment
from
me
again
actually
can
kind
of
agree
now
to
I
mean
I
didn't
say
that
it
was
a
library
at
first.
So,
as
you
say,
it's
it's
really
a
go
library,
so
it's
only
intended
to
be
used
by
co-developers
that
develop
other
go
tools.
I
thought
it
was
modest
of
a
standalone
micro
service
that
you
can
deploy
in.
You
could
be
near
this
environment
and
then
interface,
whatever
tool
in
your
cabinet,
this
cluster
from
there
using
ordinary
micro
service
interfaces.
K
L
A
Yeah
well,
I
won't
take
us
back
to
top
level.
This
actual
item
go.
Sem
was
an
example
of
that
area.
So
I
think
we
made.
We
may
still
want
to.
You
know.
Look
at
this
area
as
like
identifying
and
two
different,
reusable
libraries,
perhaps
see
our
CD
domain.
Question
may
not
be
best
example
for
that
area,
but,
like
I
just
want
to
ask
open
about
this
like
an
area
should
we
have
this
as
an
area
to
focus
as
part
of
our
roadmap
and
perhaps
call
people
to
join
and
drive
this
topic.
A
Okay,
then
yeah,
we
let
it
stay
there,
and
then
we
can
revisit
this
topic
doing
next
meeting,
perhaps
after
people
some
time
to
think
on
this
and
I
won't
talk
about
some
other
areas
include
here,
perhaps
starting
with
the
first
one,
despite
my
standardization
and
languages.
Actually,
this
was
this
came
up
when
we
first
proposed
to
seek
to
CDF
and
I.
If
I
remember
it
correctly,
it
was
from
Tom.
A
H
Why
I
think
it
makes
perfect
sense
right
like
because
I
again
like
what
I
read
a
high-level
about
the
signals,
interoperability
and
like
any
sort
of
standard,
like
you
know
each
one
of
our
tools
that
are
very
different,
even
in
the
verbage
right?
What
got
me
excited
was
like
that
chart
that
someone
had
about
like
hey,
even
call
the
pipeline
workflow
trigger.
We
all
call
it
different
things.
Instead
of
trying
to
standardize
I,
don't
think
that'd
be
pretty,
it
substantially
come
up
with
some
sort
of
standard,
but.
A
Let
me
keep
it
is
this
and
then
you
can
use
it
as
well
and
all
the
reason
why
we
like
why
we
have
these
areas
would
basically
like
to
find
who
might
be
interested
in
working
in
this
area,
so
I
reached
out
tongue.
He
was
unable
to
join
to
this
meeting,
but
I
will
keep
bugging
him
because
he
is
the
first
one
to
bring
this
topic
up.
Perhaps
he
can
reach
out
to
community
and
see
if
anyone
else
is
interested
on
this
area
and
see
what
happens
and
the
second
area
include
in
the
roadmap.
A
K
Yeah
again
in
Italy,
coming
from
from
the
aphid
community
and
I
presented
a
field
some
time,
though,
it's
all
about
events,
of
course,
I'm
interested
in
in
event
handing
here,
but
it's
it's,
maybe
both
event-driven
clcd,
but
maybe
even
more
the
bullet
that
I
added
later
on
there.
The
pipeline
date
of
traceability,
initialization,
which
is
one
solution
to
that,
could
be
to
use
events
so
yeah.
Of
course,
I
would
be
interested
to
to
talk
more
to
people
about
how
events
could
help
us
in,
inter
preventive
between
CCD
tools,
yeah.
H
That's
not
really
interesting
right,
like
a
lot
of
times,
at
least
from
my
experience.
An
event
might
be
like
an
SEM
hook
like
something
is
kicked
off,
but
you
have
to
start
it,
but
no
events
might
be
if
we're
looking
to
expand
our
horizons
right.
Like
hey,
there's,
system
events,
so
we
can
capture
the
kickoff
a
pipeline
or
other
type
of
events.
Then
you
know
some
sort
of
SEM
abet.
H
K
One
aspect
is
driving
the
flow,
as
he
said,
triggering
the
flow
or
the
pipeline
or
the
workflow
or
you
call
it.
So
that's
one
aspect
of
it,
but
the
other
aspect
is
done.
Collecting
data
from
the
pipeline
to
be
used
for
measurements
or
traceability
of
Association
or
whatever
so
have
a
common
format
of
providing
data
to
some
external
consumer,
or
it
could
be
a
consumer
within
the
cluster
as
well.
If
you
like,
of
course,
but
well,
yeah
I
would
like
to
discuss
that
more.
H
It's
pretty
important
like
maybe
we
could
rename
it
like
I
just
thought.
Events
were
like
triggering
stuff,
but
that's
again
we
all
captured
it
in
a
different
way.
We
all
expose
data
like
all
tools
in
a
different
way,
so
maybe
the
standardization
of
output
I'm
not
sure
a
good
name
for
it,
but
yeah
I,
like
it
I
like
the
top
and.
K
And
I
what
I
would
like
to
focus
on
is
the
pipeline
data
itself,
and
not
maybe
I
mean
we
shouldn't
really
compete
with
the
primitives
or
other
metering
engines
or
such
because
I
think
there
are
perfect
frameworks
there
already
for
that
kind
of
data.
Maybe
we
could
interface
those
those
data
sources
with
these
kind
of
events
or
something
like.
B
It
makes
it
makes
total
sense
event.
Event.
Processing
and
management
is
something
that
I
don't
care.
What
you've
done,
I,
don't
care
what
kind
of
system
you've
written
if
it's
more
than
ten
lines
of
code.
All
of
a
sudden,
you
start
to
think
about.
Oh
gee.
Do
I
need
to
tell
do
I
need
to
tell
other
or
other
processes
interested
in
something
that
happens
in
in
my
code,
and
the
answer
is
almost
always
yes,
and
how
do
you
do
that
in
a
very
decoupled
way?
B
Well
through
events,
and
so
it's
just
such
a
fundamental
pillar
of
of
any
source
of
any
sort
of
workflow
processing,
so
yeah,
absolutely
and
I,
and
two
Mills
point
it's
it's
actually
more
than
just
data
that's
produced
during
a
pipeline.
There
are
just
so
many
various
systems,
especially
in
enterprise
workflows
that
are
interested
in
things
that
happen
in
a
pipeline
and
they
want
to
hear
about
it.
And
it's
not
just
data
it's.
They
want
to
know
that
this
XYZ
happened
and
they
want
to
do
something
when
X
Y
Z
happens,
and
so
it
is
fundamental.
L
A
K
H
Yeah
like,
if
you
have
a
common
data
format
like
you,
can
do
a
lot
right,
you
can
encompass.
All
of
that.
Let's
see
we
came
up
with
some
sort
of
common
format
to
extract
data
like
if
this
is
the
Cir
in
performing
the
CD
system
receives
that
data.
It
can
react
in
a
different
way
versus
it
exporting
the
data.
So
there's
a
lot
there's
a
lot
of
art
of
the
possible
there,
which
is
pretty
exciting
right.
So
maybe.
A
A
It's
kind
of
that
way.
You
know
it's
like
we
may.
We
don't
have
to
you,
know
app
or
agree
on
things.
People
just
shown
interests
and
they
can
at
least
come
together
as
if
they
know
who
is
interested
in
specific
area,
and
then
we
can
take
this
discussion
again
during
tonight's
meeting
and
then
discuss
how
to
you
know,
move
forward.
A
F
And
I
believe
just
in
terms
of
process
I
know,
Dan
Lawrence
is
pretty
interested
in
maybe
kicking
off
some
kind
of
interoperability
summit,
making
sure
representatives
from
the
city
of
projects
are
there
and
I
think
this
could
help
inform
the
areas
that
get
focused
on
or
how
we
prioritize
the
different
things.
Perhaps
just.
A
A
E
A
A
Yeah
I
believe
in
community
so
again
the
event-driven
stuff.
It's
obvious.
There
are
multiple
people
that
are
interested
in
that
area.
Maybe
they
can
take
the
lead,
come
up
with
some
way
of
working
and
presented
doing
the
upcoming
meeting,
and
then
we
take
it
from
there
rather
than
trying
to
make
up
saying
you
know,
process.
J
A
A
Can
you
add
to
the
document
andreas
directly,
so
you
can
said
that
better
than
yeah
sure,
yes
yeah
so
Tracy
I
want
to
come
back
to
that
interval
summit
topic
because
I
missed
the
technical
committee
meeting
last
week
and
when
I
see
in
the
topic
there
wasn't
too
much
details
about
it.
Can
you
summarize
yeah.
F
I
think
it's
they
had
been
an
original
plan
down.
Lawrence
was
trying
to
drive
for
a
physical
face-to-face,
but
that
was
pre
Koga
days.
So
now
I
think
in
some
ways
it
does
become
easier,
but
I
think
he's
trying
to
work
out
how
to
get
the
project
leads
together
to
talk
about
interoperability
and
how
to
structure
that
and
yeah
all
I
know.
Is
he
reached
out
to
a
couple
of
us
just
to
say?
F
Would
you
like
to
help
organize
so
and
that's
as
far
as
it's
gone,
so
I
think
the
first
thing
we'll
do
is
probably
get
a
few
people
together
come
up
with
some
commitment
and
a
broad
timeframe
and
then
open
it
up
to
two
other
folks
to
to
see
how
we
structure
it.
Oh
I,
don't
know
she
did
a
bit
like
an
unconference,
perhaps.
A
Okay,
yeah
time
we
can
reach
out,
but
we
can
maybe
take
this
topic
again
doing
take
committee
meeting
next
Tuesday
state
our
interest.
I
see
you
know
we
have
people
interested
in
this
topic
and
creating
to
us
in
any
conversations
or
when
the
summit
happens
even
before
it
happens.
Perhaps
in
planning
phase.
F
B
B
J
B
K
F
H
K
K
A
K
J
L
K
Actually,
all
of
them
were
kind
of
interesting
to
us,
maybe
or
the
city
is
the
most
interesting
but
but
to
me
or
events
is
very
interesting
as
well.
Maybe
I'll
grow
lots.
It's
interesting,
it's
more,
no,
more
similar
to
spinach
already
or
those
use
cases.
So
I
guess
a
little
bit
of
all
I
guess.
Yeah.
L
K
L
F
K
F
Guess
the
other
thing
is
whether
there's
also
interest
at
all
in
any
of
the
Tecton
based
platforms.
Knowing
that
we've
got
g2
IQ
I
know,
we've
got
some
folks
from
puppets
in
the
community
as
well,
so
just
depending
on
what
we
want
to
see
in
what
we
feel
is
useful
things
like
that
could
be
of
interest
just
to
see.
If
you
know,
are
we
all
kind
of
doing
the
same
things
in
slightly
different
ways
or
yeah.
A
A
I
I
did
it's
regarding
your
guys's
interoperability.
Podcast
I
just
wanted
to
give
a
quick
update
on
your
guys's
performance
in
the
first
two
weeks,
so
you
guys
had
a
hundred
and
one
downloads
and
I'd
love
it.
If
you
guys
have
more
topics,
so
we
can
get.
Maybe
like
a
follow-up
like
interoperability.
Podcast
number
two,
maybe
we
discuss
maybe
go
into
more
detail
about
the
roadmap
or
we
talk
about
the
rosetta
stone.
So
if
you
guys
are
interested,
please
reach
out
to
me,
but
yes,
congratulations.
You
guys
did
really
well.
A
So
thanks
for
that
Jackie
and
everyone,
if
you
have
ideas
about
podcast
ideas
about
the
interoperability
area
or
the
focus
areas
you're
talking
about
like
you
went
to
a
CI,
CD
and
so
on,
please
reach
out
to
Jackie,
and
then
we
continue
pushing
this
area
forward,
but
yeah
we
have
three
left.
So
if
there
is
no
other
topic
to
bring
up,
I
won't.
Thank
all
of
you
again
for
joining
this
week's
meeting.