►
From YouTube: AsyncAPI SIG meeting 40 (January 19, 2021)
Description
This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #40.
Attendees:
Łukasz Górnicki
Fran Méndez
Maciej Urbańczyk
Clemens Vasters
Dale Lane
Lorna Mitchell
Barbaño González
Zoltan Simon
Ben Gamble
Agenda & Notes: https://github.com/asyncapi/asyncapi/issues/474
Chat:
00:06:25 Fran Méndez: brb
00:09:45 Lukasz Gornicki: https://github.com/asyncapi/asyncapi/issues/432
00:18:52 Maciej Urbańczyk: https://github.com/asyncapi/shape-up-process/issues there are issues in current cycle :)
00:19:08 Fran Méndez: https://shapeup.asyncapi.io/cycles/6301193
00:22:45 Lukasz Gornicki: https://docs.google.com/document/d/11g0ezAvrZGRYhe5NEV4fOq4zAnLQPmOow0egxgSokUs/edit?usp=sharing
00:57:30 Fran Méndez: https://github.com/cloudevents/spec/blob/v1.0.1/community/GOVERNANCE.md
01:00:04 Clemens Vasters: https://github.com/cloudevents/spec/blob/v1.0.1/primer.md#qualifying-protocols-and-encodings
01:04:26 Lukasz Gornicki: https://github.com/asyncapi/shape-up-process/issues/38
A
Okay
recordings
recording
started
hello
good
morning:
it's
our
open
public
meeting
session
for
apac
epic
friendly
session,
which
means
it's
super
early
for
people
I
mean
even
for
me,
it's
early
which
is
9am
for
me.
So,
but
even
though
we
have
many
people,
so
awesome
welcome
to
olivia,
and
I
think
we
have
at
least
two
new
people.
I
think
I'm
not
sure.
If
clemens
did
you
join
me
before.
B
B
Cubase
message
broker
we
own
azure
event,
hubs
which
is
a
high
scale
event
streaming
engine
with
downstream
services,
also
in
or
near
our
team,
in
the
form
of
hdinsight
for
analytics,
which
also
hosts
the
kafka
service
and
azure
stream
analytics,
as
well
as
azure
synapse,
that's
all
in
our
world,
and
then
we
have
azure
event
grid,
which
is
a
a
push-based
event
broker
for
discrete
events,
that's
implementing
cloud
events
and
then
we
also
have
the
relay
and
then
then
around
this
we
have
numerous
other
messaging
services.
We
have
the
azure
queue.
B
B
Because
not
everybody
has
a
use
case
for
mkp
frankly,
but
tying
it
all
together
and
tying
it
into
the
application.
Building
a
kind
of
contract
model
for
the
application
is
something
that
is
is
kind
of
sitting
at
a
layer
just
yet,
above
that.
All
of
that
and
that's
something
where
you
guys
have,
I
think,
plugged
all
and
so
we're
interested
in,
seeing
whether
and
how
we
can
go
and
and
help
with
that
and
also
then
build
something
that
can
can
you
know,
integrate
async
api
with
the
products
that
you
have.
A
Awesome
sounds
awesome,
so
definitely
I'm
I'm
the
most
interested
with
cloud
defense
here,
because
we
we're
getting
a
lot
of
questions
from
people
like
how
we
can
use
both
okay-
and
I
mean
we
have.
We
had
some
ideas,
there's
even
one
blog
post
from
the
front
where
one
explains
how
that
could
be
done,
how
it
could
be
accomplished,
but
I'm
gonna
send
you
a
link
to
a
issue
created
by
fran,
where
he
explores
how
we
could
even
more
natively
support
club
events.
C
Yeah,
so
I
think
we
have
to
right
we
have
to
because
I
mean
I
keep
seeing
more
and
more
people
using
async
api
plus
cloud
events.
You
know
class
other
technologies
right,
so
it's
like
we
we
we
have
to
do
it,
it's
like
if
we
have
to
change
something
amazing
kpis,
so
I
I
tend
to
to
see
things
from
the
perspective
of
the
user
instead
of
from
our
perspective
as
authors,
because
it's
like
it
doesn't
fit
so
well
with
the
sync
api.
Imagine
that
it
doesn't
fit
so
well
with
the
10k.
C
D
C
C
B
So,
if
you
look
at
it
as
a
transport
per
se,
that's
probably
the
same
as
way
of
looking
at
it.
So
if
you
want
to
talk
cloud
events
and
you
want
to,
then
you
get
all
the
benefits
of
of
using
it
of
of
having
its
its
transport
bindings
with
it
and
and
there's
obviously,
a
combination
that
you
can
define
of,
but
it
tries
to
stay
out
of
the
way
of
of
what
you
usually
do
with
those
transports.
It
basically
just
defines
if
you
have
a
cloud
event.
B
This
is
how
you
fold
it
onto
on
top
of
an
http
message,
but
then
there
might
be
extra
things
you
do
with
an
http
message,
which
then
are
contributed
from
from
from
open
from
async
api
or
mkp.
So
there
is
a
there's
a
there's
effectively.
You
have
the
cloud
event.
You
explode
that
onto
an
mqp
message
and
then
back
the
extra
things
you
may
want
to
do
with
with
async
api,
which
I
tried
hard
to
defend
the
mode
on
to
not
seep
into
cloud
events.
B
My
feeling
for
cloud
events
was
that
it's
not
appropriate
to
go
so
far
to
create
relationships
between
services
in
cloud
events,
because
cloud
events
is
really
about
the
event
delivery
and
not
thinking
about
how
the
greater
application
we
think
about
it.
But
I
think
that's
something
that's
in
scope
for
for
async
api,
so
there's
a
there's.
A
line
here
that
is,
is
defined
effectively
by
the
principles
of
of
cloud
events
of
what
it
does
and
what
it
doesn't
do
and
and
then
I
think
open.
I
keep
saying
open
about
async
api.
B
A
So
just
say:
follow
up
I've
sent
you
a
link,
I
mean
to
everyone
in
the
chat
to
this
issue
where
there's
this
discussion
about
native
support
for
cloud
events.
So
if
you
have
time
and
some
opinion
to
share
there
later,
then
please
do
so.
I
know
as
well.
It's
your
first
time
on
the
meeting.
Did
I
pronounce
your
name
correctly?
A
E
D
Changed
jobs
at
the
beginning
of
january
now
working
for
iphone
we're
a
cloud
data
hub,
so
we
deploy
things
to
clouds
and
things
include
kafka,
so
suddenly
boom
async
api,
so
I'm
kind
of
on
boarding
with
kafka
and
I'm
boarding
with
a
lot
of
the
ops
side
of
it.
But
most
of
you
know
me
from
async
api
community.
D
So
I'm
going
to
bring
all
that
goodness
over
and
try
to
encourage
our
users
to
know
how
they
can
async
api
with
our
kafka
and
I'm
just
like
there's
a
load
of
kafka,
connect
and
things
and
stuff
and
schema
registries
and
whatever
so
I'm
in
I'm
like
deep
into
a
new
world.
So
I'm
here
you
know
me,
but
I
have
a
new
context
now.
A
A
Welcome
welcome.
Welcome,
so
does
anyone
have
any
questions,
anyone
anything
to
add
before
we
jumped
into
the
agenda,
because
I
have
only
one
item
in
agenda,
probably
something
additional
that
I
will
ask
from
or
actually
I
will
ask
first
so
do
you
want
to
add
that
we
are
starting
that
we
started
actually
new
cycle?
Maybe
because
I
didn't
put
it
in
the
agenda
and
I
didn't
ask
yesterday.
C
Yeah,
it's
just
a
few
words.
So
for
those
who
don't
know,
we
work
in
cycles
of
six
six
weeks
and
and
then
we
stop
for
two
weeks
where
we
contribute
to
other
open
source
projects
or
or
fix
backs
or
exam
kpi.
So
that's
how
we
work
happy
to
to
tell
more
about
it.
I
don't
want
to
explain
the
whole
thing
again
here,
but
this
six.
So
yesterday
we
started
a
new
six
week
cycle
and
we
we
bet
that
because
that's
that's
how
we
call
it.
C
C
Code
generation,
okay,
so
it's
actually
not
code
generation,
it's
more
about
data
model
generations,
so
you
know
from
code
generation
the
hardest
part
for
everyone
is
to
generate.
You
know
like
java
pojos
on
go
or
you
know,
data
types.
If
you
want
that's
the
hardest
part,
usually
so
so
we
want
to
to
take
this
complexity
ourselves.
C
So
people
don't
have
to
take
this
at
this
complexity
and
and
well,
matcha
and
jonas
are
are
working
on
this
now
and
in
six
weeks
we
should
have
something
if
they
managed
to
accomplish
the
bet
so,
which
I
think
will
and
yeah.
So,
oh
yeah,
you
already
shared
thanks
magic,
so
well,
actually
yeah,
I'm.
What
I'm
saying
is
more
like
a
nice
view
of
of
the
current
progress
and
yeah,
just
at
the
end
of
the
cycle,
we'll
have
more
a
better
way
to
generate
data
models
in
in
various
languages.
C
F
C
C
A
Thank
you
and
the
second
topic
something
from
my
side.
So
we
a
bit
of
context.
So
you
not
sure
if
you
know
last
last
year
during
the
october
fest,
the
oktoberfest
is
this
even
sponsored
by
digitalocean,
where
you
have
one
month
in
october,
where
people
can
contribute
to
open
source
and
we
engaged
with
this
event
pretty
strongly.
Let's
say
we
prepared
a
lot
of
issues
and
we
like
we
helped
a
lot
of
people
with
the
within
the
event.
A
We
got
a
lot
of
contributions
and
few
people
mentioned
to
us
that,
because
of
the
level
of
our
engagement
and
how
we,
how
helpful
we
were,
they
suggested
that
we
should
actually
try
google
summer
of
code,
like
I
said,
an
organization
apply
to
be
part
of
the
of
the
event
and
yeah
we
decided
to
do
it.
We
will
have
we'll
offer
two
mentors
so
we'll
apply
for
two
student
positions
in
general.
A
I
will
not
go
too
much
into
details
of
what
google
summer
of
code
is
it's
pretty
known
event,
but
if
you
want,
I
can
just
shed
some
light
on
it,
but
I'm
I'm
talking
about
this
because
we
want
to
do
it
not
just
like
alone
us
like
me,
front
or
magic,
just
think
about
ideas.
We
would
like
to
grab
the
ideas
for
good
tools
for
us
and
api
from
the
community
as
well.
So
I'm
gonna
share
with
you
a
link
to
the
google
doc
document
which
is
available
for
anyone
for
edit.
A
I
hope
nobody
will
troll
us
and
remove
at
some
point
of
time
all
the
ideas
but
yeah.
I
think
it's
a
it's
good
approach
to
just
fully
open
the
document
and
if
you
for
the
couple
of
next
weeks
have
some
ideas,
because
we
don't
have
to
provide
in
the
initial
applications
or
the
ideas
over
time,
if
you
think
about
some
tool-
and
you
see
that
the
core
team
doesn't
have
time
to
implement
it,
because
we
have
different
focus,
but
maybe
some
someone
from
google
summer
of
code.
A
If
we
of
course
get
accepted,
maybe
would
pick
it
up.
Then
just
show
your
idea
here.
Please
just
explain
a
bit.
What
you
are
thinking
about.
It
can
be
even
the
most
crazy
idea,
like
the
one
I've
thought
about.
I've
picked
up
a
chatbot
and
please
put
your
contact
name,
and
it's
don't
worry,
it
doesn't
mean
you're.
Gonna
have
to
be
a
mentor
for
the
participants.
A
C
B
G
A
H
H
G
H
G
B
Just
we
had
because
we
had
that
same
discussion
in
in
cloud
events,
make
take
a
good
look
again
at
the
google
summer
of
code
conditions
and
terms
and
conditions,
because
somewhere
in
section
8
is
a
section.
8
reveals
that
the
actual
purpose
of
the
google
summer
code,
because
google
hr
is
google
recruiting,
is
entitled
to
use
all
the
data
that
has
been
submitted
there
to
use
for
recruiting
and
to
contact.
Everybody
who's
been
involved
in
this,
just
just
so
that
you
know.
A
B
Yeah,
but
we're
having
reservations
because
governance,
governance,
governance
is
per
project
in
the
cncf
the
cncf
has
well,
and
the
linux
foundations
have.
When
it
comes
to
governance,
no
principles
whatsoever:
you
can,
you
can
show
up,
and
you
can
you
can
say
we're.
Gonna
run
this
project
as
a
total
dictatorship,
and
the
linux
foundation
will
probably
be
okay
with
it.
A
D
C
Okay
yeah,
so
in
my
in
my
opinion,
I
think
right
now
because
of
capacity
basically,
so
it's
we.
We
are
not
able
to
do
everything
that
we
wanted
to
do.
We've
been
dedicating
too
much
lightly
to
code
and
not
so
much
to
the
spec,
but
that's,
like
you
know,
that's
kind
of
like
it's
like
kind
of
a
roller
coaster
right
so
from
time
to
time.
What's
going
to
happen?
C
Is
that
we're
going
to
dedicate
more
to
the
spec
and
less
code
so
right
now
we're
focusing
on
creating
these
reference
implementations
that
are
good
enough
for
the
user
to
use
with
the
current
spec,
but
since
our
partnership
with
with
postman
now,
we
we
will
now
have
enough
with
enough
people
right
enough
people
to
work
on
the
on
the
spec
plus
the
toilet.
So
there
will
be
some
people
working
full
time
on
the
spec.
C
Okay,
at
the
very
least
three
people
at
the
very
least
full-timer,
then
you'll
have
some
people
who
are
not
from
poznan,
obviously
working
on
the
spec
whenever
they
can
and
that
and
that's
fine
so
that
I
think
that's
that's
great
and
the
way
we're
gonna
do.
This
is
that
we're
gonna
separate
the
spec
from
the
tooling
right,
we're
gonna,
separate
it
into
a
new
into
a
new
committee.
C
If
you
want,
whenever
we
set
up
things,
there
will
be
a
committee
for
the
spec
and
accounting
for
the
tooling
and
and
the
committee
of
the
spec
will
be
independent
from
from
the
tooling
one,
so
so
development
on
the
spec
is
going
to
happen
separately,
but
in
a
coordinated
way
of
course.
Okay,
so
so
yeah.
B
There
are
different
licensing
concerns
around
specs
than
they
are
for
code,
and
so,
if
there
is
an
open
source
project
is
something
we
treat
differently
and
we
have
to
treat
differently
from
from
pure
spec
projects,
because
there
is
in
pure
spec
projects
which
are
really
about
interoperability
and
which
are
really
about.
You
know
agreeing
on
what
the
wire
looks
like
independently
independent
of
what
the
implementation
looks
like.
B
There
are
more
patent
concerns
that
may
that
and
and
other
things
that
may
seep
into
the
story
than
than
when
you
have
a
concrete
implementation.
So
we
have
we
have
seen.
I
have
personally
seen
scenarios
where,
when
you
talk
about
implementation,
independent
specifications
and
and
doubtlessly
we
have
one
here,
because
that's
the
interest
that
people
have
in
ac
api
is
really
like.
B
They
also
introduce
new
methods
of
like
patentable
methods
of
doing
certain
things,
and
that's
because
the
world
works
this
way
and
well
so
so
code
is
usually
subject
to
copyright
and
specs
are
not
so
the
way.
Well,
they
are
subject
to
copyright,
but
the
the
methods
you
can
go
past.
You
can
patent
the
methods
that
are
defined
in
those
specs.
You
can't
patent
the
code.
B
G
B
And-
and
I'm
not
saying
anything
right
so
so
I'm
just
so
I'm
I'm
just
saying
I'm
just
saying
that
happened.
So
this
is
why
this
is
why,
in
spec
world,
you
have
these
these
rand
and
efran
terms,
and
you
have
agreements
that,
yes,
that
what
I
just
that,
what
I
just
said,
you'd
never
do
et
cetera,
et
cetera,
et
cetera.
So
that's
that's
why
that
gets
a
little
bit
more
difficult
from
our
perspective
and
I,
as
working
at
microsoft,
I
have
to
walk.
B
B
Also
to
maybe
you
know,
discuss
what
the
what
the
terms
are,
because
we
we
are
pretty
insistent
on
having
that
all
clean
right.
We
we've
we've
co-founded
several
of
these
open
source
or
open
standards
organizations
we
have
folks
who
are
kind
of
on
the
top
of
the
world
in
in
kind
of
organizing
those
things
and
they'll
they'll
they're
generally
generally
involved
in
these
matters.
And
it's
that's
that's
what
happens
so.
C
If
everything
continues
the
same
way
as
it's
going,
it's
probably
gonna
happen
pretty
soon
and
the
reason.
The
reason
is
that
I'm
saying
this
is
that
it's
going
to
be
so
the
spec
is
going
to
be
separated
into
into
a
separate
foundation.
If
you
want,
in
the
case
of
linux
foundation,
it's
called
joint
development
foundation,
which
is
a
it's
a
foundation
only
for
specs
and
and
whoever
wants
to
contribute
to
spec
needs
to
science
and
papers
before
they
do
it
so
the
papers
that
clemens
was
mentioning
like.
D
C
B
So
so
so
that
path
is
harder
with
the
linux
foundation,
I'll
I'll
just
they
they.
I
have
a
bit
of
insight
because
we
had
the
we
had
the
same
discussion
about
cloud
events
and
eventually
somehow
it
didn't
end
up
in
that
in
that
in
that
foundation
that
that
was.
That
was
a
branch
that
was
somewhat
recently
resurrected.
B
If
you
really
want
this
to
become
a
capital
as
standard
and
also
then
go
on
the
iso
path
and
then
oasis
might
be
the
better
place.
Oasis
is
from
a
process.
Perspective
oasis
has
a
lot
tighter
processes
and
has
kind
of
pre-built
processes
which
the
linux
foundation
doesn't
have
in
that.
In
that
stringency,
there
is
a
lot
more
process
in
oasis
and
oasis
is
also
as
an
organization
much
stricter
in
heat
on
who
can
who
can
participate
in
the
linux
foundation.
B
You
are
generally
like
they
give
you
the
bylaws
in
that
particular
branch
that
you're
looking
at,
but
otherwise
you
are
fairly
liberal.
You
can
be
fairly
liberal
in
how
you
run
your
project,
because
the
linus
foundation
generally
has
the
the
the
the
attitude
of
not
reigning
into
what
you
run,
but
from
a
legal
perspective,
just
to
be
super
safe
on
on
rights
and
isolation
in
terms
of
patent
claims,
etc.
B
B
C
So
I
I
wasn't
mentioning
explicitly
just
because
we
want
to
to
become
an
iso
standard
or
anything.
This
was
just
like
a
like
an
ad
like
if,
as
an
example
that
the
path
can
be
there
right,
like
can
can
be
chosen
like
it's
not
at
least
from
my
perspective.
It's
not
our
goal
to
become
an
isis
standard.
Okay,
it
will,
it
will
be
cool.
C
D
C
Now
so
so
the
spec
is
under
my
name
and
that's
not
neutral.
So
that's
why
we're
making
this
move
and
we
want
to
make
it
more
neutral.
We
want
to
form
a
company
or
various
committees,
so
it's
more
neutral
right
over
time
and
and
then
useful
for
the
user.
I
honestly
don't
care
if
it's
a
nice
standard
or
whatever
it
is
just
so
it's
like
this.
G
But
yeah
that's
not
the
goal,
but
I
think
I
just
I
think
the
two
messages.
Sorry,
I
think
the
two
message
is
important
here:
what
you're
just
saying
that
that
that
formalized,
some
sort
of
formalization
from
your
perspective
or
big
corporate
perspective
is
important
and
what
what
friend
is
saying
right
now
is
we
be
a
testing
api
is
on
the
way
on
the
on
right
now
in
the
rapid
way
to
some
kind
of
formalizing
that
kind
of
things.
G
The
format
I
don't,
as
I
hear,
is
not
just
not
decided
yet
so,
which
way-
and
I
think
it's
really
great
to
hear
this
insight-
I
mean
that's,
that's
that's
enlightening.
What
are
the
differences?
I
think
for
you
guys
also
that
that
hearing
that
someone
has
bonded
somebody
bent
to
this
path,
so
we
don't
have
to.
We
don't
have
to
do
it
again.
Yes,
so.
D
G
That's
the
most
important,
so
these
kind
of
points
and
yes
and
then
these
are
just
a
chain
of
decision
points
like
eyes
or
no
ties
or
whatever
I
don't
know,
but
but
the
most
important
from
what
I
understand
from
that
one.
If
and
everybody
says
that
it's
anyway,
how
we
form
it
there
is
a
spec
here.
So
that's
what
which
makes
this
thing
very
interesting,
and
if
it's
a
spec
there
are
some
legal
legal
consequences,
as
you
mentioned,
that
that
needs
to
be
cleared
out
to
be
really
useful.
G
G
B
B
So,
ultimately,
that
decision
is
really
with
you
and
not
neither
choice
will
make.
It
will
make
a
material
impact
on
on
whether
we
can
contribute
or
not,
yeah,
that's
great
too
so
right
now
so
right
now
the
project
as
the
project
as
it
stands,
that's
difficult
for
us
to
go
and
engage
because
it's
it's
your
it's
your
thing.
C
C
D
C
I
D
C
What
was
I
saying
so
I
was
yeah.
I
was
saying
that
that
well,
that
did
this.
This
could
be
seen.
If,
if
we
continue
this
path,
then
it
could
be
saying
that
oh,
this
is
a
postman
project
and
pass
money
is
manipulating
the
direction
of
the
project
and
blah
blah
blah.
You
know
so
to
remove
all
these
all
these
things,
that's
why
we
we're
going
to
a
into
a
foundation
right,
so
so
yeah.
So
that's.
C
D
I
definitely
think
it
so.
I
haven't
really
introduced
my
employers
to
async
api,
yet
I
mean
you
know,
because
I
can
just
write
some
blog
content
and
start
to
be
part
of
the
ecosystem
and
see
if
any
of
our
users
start
showing
up
and
asking
questions.
I
think
it
is
important
that
we
have
lots
of
different
people
using
it.
We
used
it
a
little
bit
from
mqtt
and
was
completely
confused
and
you
helped
me
with
it
that
time
so.
D
So
I
think
both
those
things
both
the
corporate
diversity,
but
also
the
technology
diversity.
Both
those
things,
I
think,
are
quite
important,
but
yeah
I
mean
I'm
a
spec
contributor
to
open
api
without
holding
any
formal
position
there
like
they
have
a
process
where
you
say
I'd
like
to
do
this
and
they
say
well
we're
not
calling
it
that
and
once
they've
like
said,
is
your
tag
name.
Then
your
change
gets
accepted
so,
and
I
found
that
okay
glacial,
but
standards
can
be
a
bit
slow
right,
but
it
was.
D
It
was
good
and
there
were
lots
of
different
people
representing
lots
of
different,
often
conflicting
points
of
view,
and
I
thought
that
was
quite
healthy.
So
I
kind
of
aspire
for
this
project
to
have
the
same
visibility
and
then
the
same
engagement.
I
think
we're
at
the
visibility
stage
right
now,
though,.
G
I
think
I
think
it's
very
important
that
that
many
mentions
here,
I'm
I'm
I'm
working
in
the
corporate
world.
You
can
say
that
so
my
history
is
consulting
and
architecting
and
working
with
these
kind
of
standards
and
as
I
mentioned
to
friend
that
in
this
year
I
would
like
to
do
more
contribution
for
you
guys.
So
I
try
to
try
to
allocate
my
private
time
for
that,
but
but
from
the
other
side
I
have
to
say
that
I
totally
agree
with
that.
G
That
clearance
is
very
necessary
so
because,
if
we
and
one
thing
it's
useful
for
developers,
but
the
developers
are
sitting
at
corporates
and
that
corporates
there
is,
there
is
an
imminent
question
when
you
are
using
a
spec
or
a
code
or
something
yes,
there
is
always
an
open
source
initiative
declaration
how
we
use
open
source,
how
we
use
this
hobby
users.
That's
that's
a
question
because,
because
you
know
that's
legal,
I
mean,
and
then
we
have
to.
We
have
to
serve
the
customers
and
the
customers.
Also
asking
I
I'm
secure
to
use
this
standard
respect.
G
So,
for
example,
let's
say
it's
a
health
care
application
and
then
then
everything
just
stops
because
some
legal
make
a
season.
This
is
order
on
the
whole
software
and
then
the
whole
hospital
have
to
stop.
Because
of
that.
So
these
questions
I
mean
so
when
it's
just
a
hobby
code
and
hobby
project,
it
doesn't
matter.
I
don't
care.
Also,
my
in
private
life.
It's
just
good.
You
know
we
share
that
kind
of
noisy
approach,
that
everything
is
open
and
free,
but
but
when
it
comes
to
you
know
yeah
production.
G
I
would
say
that
it's
very
important.
So
for
that
one
I
think
it
would
be
nice
if
we
can,
if
we
can
have
some
kind
of
roadmap
again,
like
you
just
introduced
this
six
weeks,
life
cycle
for
the
code
to
something
about
how
this
goes
so
so
also
providing
some
kind
of
security
for
like
clemens
that,
okay,
that's
that's!
That's
that's
happening,
so
we
don't
just
talk
about
it,
but
okay,
that
is
happening.
So
it's
not
like
the
ending
up
in
a
scenario.
It's
it's.
G
People
are
understanding,
as
you
say,
that
visibility
or
recognizing
there's
a
postman
thing,
but
people
understand
that
this
is
not
a
postman
thing.
This
is
something
as
you've
wronged.
France
says,
put
it
it's
a
community
thing,
it's
an
open
thing.
I
think
it's
a
very
imp.
It's
a
it's
an
important
message.
G
You
have
to
be
out
and
repeat
it,
because,
because
that
that
could
cause
confusion
and
and
it's
important
for
the
corporates,
I
would
say
that
when
the
real
real
world
usage
that
it's
clear
and
there
is
a
path
for
it-
so
it's
not
necessary
has
to
be
done.
It's
very
important,
no
premature
optimization,
but
it
has
to
be
a
roadmap
for
that.
G
G
D
C
C
C
C
C
To
commit
to
any
specific
date
but
like
I
would
like
to
reinforce
the
mosque,
probably
because
there
are
things
that
don't
depend
on
me
right
so
so
I
want
to
say
that
this
must
probably
happen
next
month.
I
mean,
if
you
tell
me
most
probably,
is
it's
happening
even
this
month
I
will
say
but
yeah
like
let's
say
this
is
the
in
this
quarter.
It's
gonna
happen
in
this
quarter
for
sure.
G
G
C
I
have
some
things
mixed,
so
actually,
in
my
to-do
list
I
have
I
have
it
prioritized
by
high
priority
medium
priority
low
priority
right
and
my
top
priority
right
now
is
host
projecting
open
source
software
foundation.
Great
this
is
this.
Is
that
until
this
is
done,
I
will
not
continue
with
anything
else.
So
so
that's
my
whole
thing
right
now,
my
whole,
my
I'm
dedicating
my
whole
time
to
this
and
and
hiring
of
course,
hiring
for
or
working
on,
the
on
the
spec
and
working
on
the
tooling
as
well.
C
B
Right
time
to
show
up
here,
yeah,
because
that
that
is
a
prerequisite
more
or
less
for
us
to
engage
in
if
you,
if
you're
as
soon
as
you've
so
you're
solved,
that
I
can
go
and
write,
write
down
the
standards
decision
record
as
it's
called
and
then
we
can.
We
can
engage
that's
already
something
that
I
mean.
That's
a
decision
that
I
can
make,
and
so
I
said
we're
interested
but
you're
just
fulfilling
the
prereqs.
So
that's
great.
A
A
Highest
priority
for
me
for
the
governance.
I
I've
moved
my
priorities
that
now
I'm
like
my
main
thing
is
to
research,
how
we
can
shape
up
the
open
governance
model
here
yeah.
So,
if
you
have,
from
your
past
experience
working
on
other
communities
knowing
their
governance
models,
if
you
know
some
areas
that
we
should
not
go
to
just
you
can
offline
right
to
me
private.
To
the
like.
B
I
would
recommend
that
you
that
you
take
a
look
at
the
the
rules
of
cloud
events,
because
that
is
there's
a
community
section
in
the
cloud
events
repo
and
that
has
been
working
exceptionally
well.
It's
probably
the
most
functional
multilateral
working
group
that
I
know
that
is
in
large
part,
really
owed
to
the
most
excellent
leadership
of
doug
davies
from
ibm
who's
been
leading
this
with
a
calm
hand
and
who's
been
doing
all
the
political
negotiation
that
needed
to
be
done.
B
B
So
it's
in
github
under
cloud
events
spec
and
there
in
the
community
folder
there
are
the
governance
rules,
how
we,
how
we
operate
and
how
we
think
about
prs,
etc,
and
I
can
probably
ask
doug
to
have
a
meeting
with
with
you
guys
with
me
to
share
some
best
practices.
If,
if
you
guys
were
interested
because
doug
would
certainly
be
open
to
that.
C
B
B
B
B
That
again
there
we
go
so
there's,
there's
prior
art
that
we're
referring
to.
So
this
is
effectively
the
the
the
overview,
if
you
will
the
primer,
but
then
the
history
where
we've
come
from,
and
then
this
qualifying
protocol
section
is
about
how
we
think
about
interoperability.
Those
are
our
interoperability
principles,
for
instance,
so
that
we
are
not
a
forum
where
a
single
vendor
can
go
and
just
anchor
their
proprietary
products
in
right.
B
That
was
that
was
very
important
to
us,
so
that
nobody
just
shows
up
and
says,
hey
we're
an
open
forum,
but
we
have
never
published
our
wire
protocols
and
so
therefore,
here's
a
way
how
we
can
go
and
wire
in
our
our
proprietary
stuff
right
and
because
that's
not
the
goal
of
these
of
these
abstractions.
The
goal
is
to
further
interrupt
and
not
to
enable
open
washing
of
proprietary
products.
B
Good
point
right,
yeah,
so
that's
fine,
and
so
that
was
a
that
was
a
long-fought
thing
to
to
make
sure
that
we're
really
we're
really
open
and
you'll.
If
you
read
through
this,
then
you'll
find
that
there
are
a
few
even
open
source
projects
which
are
hard
at
the
edge
of
of
being
eligible
for
this
or
not
because
they're,
not
following
openness
principles.
I
I
have
a
mission,
and
that
is
make
everything
talk
with
open
standards
and
based
on
open
standards
that
are
vendor
neutral
and
project
neutral.
B
B
C
Awesome
thanks
for
watching.
So
what
I'm
reading
from
this
conversation
here
today
is
that
we
need
to
communicate
better
our
plans.
Maybe
so
that's
that's
what
I'm
reading
here!
We
always
try
to
be
as
much
transparent
as
possible,
so
this
is.
This
is
probably
our
biggest
gap
in
transparency,
so
so
yeah
message
received
or
ack
right.
C
I
can
say
so
we'll
we'll
try
to
make
it
more
transparent
in
terms
of
what's
the
roadmap
or
how
the
roadmap
looks
like
and
what
we're
working
on
right
now,
because
we're
trying
to
to
be
transparent
with
this
website
that
I
share
this
place
in
kpa
shape
up,
which
is
what
we're
working
on
right
now,
but
it
doesn't
include
what
ucas
and
I
are
working
on
right
now,
so
so
yeah.
So
that
would
be
great
as
well
yeah.
It
could
be
transparent
on
that
on
that
front
as
well.
A
A
A
C
C
Just
you
find
it
there
right
so
yeah,
and
that
will
be
fine,
because
the
website
is
also
on
github.
So
also
the
website
is
also
open
source,
so
yeah
and
part
of
the
project,
as
well
like
any
other
product
like
like
any
other
code
or
spec
or
anything
so
yeah
cool,
cool,
great
chat.
Today,
thanks
a
lot.