►
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).
A
A
I
want
to
share
this
all
right.
You
got
the
the
dock
on
the
screen
and
you
know
we
abide
by
the
cncf
code
of
conduct
or,
as
we
always
as
we
said,
be
excellent
to
one
another.
B
Yeah,
it's
very
formal,
yeah
yeah
one
was
I,
was
going
to
raise
some
PRS
to
move
back
to
use
in
the
proud
lease
notes,
plug-in
the
main
reason
being
currently.
We
we
originally
used
the
release,
notes
plugin
for
prowl,
and
then
we
changed
to
to
you
know
using
the
the
GitHub
clients
to
generate
those,
because
it
gives
you
that
nice
little
bit
at
the
bottom.
That
says
you
know
Daniel
made
his
first
contribution
with
this
change.
B
The
problem
with
that
is,
it
doesn't
allow
us
to
annotate
the
the
PRS
in
any
way
with
action
needed
which,
when
it
comes
to
generating
the
the
release,
notes,
we
I
think
we
lose
a
lot
of
context
and-
and
we
don't
report
stuff
to
the
user
and
actions
and
things
that
need
to
be
aware
of
so
I.
Think
if
we
move
back
to
the
the
prior
release,
notes
plug-in
that
basically
means
that
every
every
PR
you
have
to
explicitly
say
you
know
there
is
nothing
that
is
worthy
of
a
release.
B
B
B
A
A
B
So
they're
normally
a
bit
right
at
the
top.
That
says,
maybe
it's
just
a
little.
A
B
Let
me
so
we
did
try
and
style
it,
so
it
was
basically
like
the
hittings
were
the
same,
pretty
much.
A
B
See,
let
me
have
a
look:
okay
been
a
while,
it's
been
a
while
since
so.
If
we
get
back
to
well.
A
B
B
I
I,
probably
so
it's
where
someone
makes
a
change,
and
you
know
the
user
needs
to
be
aware
of
something.
So
these
are
all
coming
from
like
the
pr
titles
and
there's
no
way
for
say
me
as
a
an
author
of
a
change
to
explicitly
say:
Hey
you
here,
we
go
all
right,
I,
send
you
this
one
in
the
chat
window.
B
Yeah
these
will
just
be
generated.
So
if
we
go
to
I,
don't
know
one
of
the
one
of
the
changes.
B
A
B
A
Well,
yeah,
let's
so
I
guess
one
one
question
that
I
have
is:
is
it
possible
to
combine
the
two
or
is
it
just
a
very,
very
different
process
of
creating
the
the
release
notes
that
is?
Could
we
could
we
ask
prow
to
generate
the
release?
Notes
then
feed
that
in
some
way
to
the
GitHub
client,
I,
don't
know
if
we
use
the
CLI.
B
Good
thing:
yeah,
we
used,
we
use
CLI
in
the
yeah,
we
do
yeah
I,
guess
it's,
because
it
is
possible,
I,
guess
the,
so
they
both
try
and
generate
the
you
know
this
what's
changed
as
well,
that
the
bug
fixes
and
categorize
it,
but
we
we
could
combine
the
two
to
get
the
you
know
the
bit
at
the
bottom.
Saying:
hey
Richard
made
his
first
contribution,
because
previously
we
just
did
that
thanks,
section
down
the
bottom
there,
which
didn't
really
call
out
anyone
for
making
their
first
contribution,
yeah.
A
Yeah
I
mean
I
I
do
like
the
this
is
the
I
guess
the
prow
output
and
you
know
it's
missing
the
Emojis,
but
but
otherwise
it
seems
to
You
Know
cover
cover
everything
that
we
need,
so
yeah,
I,
don't
I,
don't
have
any
objections.
I
think
that
that
it's
it's
much
more
useful
for
for
everyone
to
or
for
for
that
information
from
the
release
notes
to
automatically
get
inserted
into
into
the
release
notes,
that's
very
important,
very
useful,
so
yeah.
A
B
B
A
A
A
B
Worthy
of
contribution,
Upstream.
A
To
I
see
to
compose
the
list.
B
A
Do
you
do
you
know
precisely
what
to
do
to
switch
it
back?
Do
you
want
to.
B
B
So
it's
a
couple.
This
is
like
a
multi-stage
process.
So,
oh
so
first
we
have
to
enable
the
plugin
and
test
info.
So
I
can
add
that
back
in
then
we
have
to
update
our
PR
templates
to
include
the
release
notes
code
section.
Oh.
B
B
Because
it
won't
kind
of
release
Branch,
what
was
it
when
we?
So
when
we're
trying
to,
because
how
it
works
is
it
tries
to?
It,
compares
the
difference
between
the
previous
release
tag
and
the
the
new
release
tag
to
get
that
list
of
things
that
have
changed
and
when
they're
on
different
branches,
which
they
might
be
because
we're
kind
of
new
release
branch.
B
Then,
if
we
find
that
it
actually,
it
puts
a
load
of
duplicate
entries
in
there
and
the
release.
Notes,
which
I
guess
is
a
failure?
Probably
now
how
we
structure
our
releases.
But.
B
Yeah
official
yeah
yeah
I
can
I'll
come
up
with
this,
the
the
tasks
okay
and
then
but
yeah.
Could
it
be
good,
just
yeah
share
the
knowledge?
Wouldn't
it
aware
of
these
things.
B
So
it's
like
quite
a
issue
then
with
the
tasks
and
what
needs
to
be
done
in
the
various
repos
and
then
we
can.
A
Sure,
and
if
you,
if
there's
an
if
there's
an
issue
or
a
PR,
where
we
changed
yeah
from
proud
to
GitHub,
if
you
could
link
that
that
would
be
helpful
because
it
would
probably
that'll
probably
explain
a
lot
of
what
we
need
to
change
back.
Yeah.
A
Sometimes
it's
okay
I
can
just
find
that
information
by
doing
a
the
good
history
of
a
specific
file,
but
having
the
yeah
yeah
cool.
A
A
Yeah,
what
about
the
the
LFX
mentorship
program.
B
Yeah,
it
really
is
there's
more
people
here,
it's
just
I
see
if
anyone
was
interested
in
being
a
co-mentor.
This.
A
Is
what's
the
X?
This
is
Linda
Linux
Foundation.
B
A
A
And
how
does
this?
How
does
this
work
is
this
like,
like
Google
summer
of
code,
someone
someone
submits
and
then.
B
Yeah
so
yeah,
so
basically,
projects
like
Kappa
will
submit
a
project
to
oh
I,
see
and
that
that
project
has
to
has
to
have
an
issue
in
in
the
project,
repo
and
a
defined
sort
of
goal
and
deliverable.
And
then
then
people
are
interested
in
it
then
sort
of
submit
applications
and
they
have
like
a
two-week
period
to
submit
applications.
And
then
people
are
going
to
be
the
mentors
and
then
review
the
applications
and
then
select
people
for
it.
Okay,
but
yeah.
They
have
to
yeah.
You.
B
People
just
don't
write
enough,
they
just
say
I
want
to
work
on
it
and
whereas
a
lot
of
other
people
say
I
want
to
work
on
it.
For
these
reasons,
this
interests
me
and
and
stuff
like
that.
So,
okay,
that
always
helps
but
yeah
it's
we
did
it
on
Kap
G
in
the
summer
last
year,
okay-
and
that
was
it-
was
quite
good.
Okay,
actually,
some
of
the
people.
You
know
that
were
mentored,
have
continued
on
and
stayed
contributing
to
to
Cappy
in
general.
B
So
it's
a
good
way
to
a
good
way
to
get
it.
Your
contributors.
B
So
yeah
I
guess
I
did
there's
a
couple
of
issues.
Well,
there's
one
issue
that
sort
of
comes
to
mind
which
we've
had
open
for
a
while,
which
is
around
adding
open,
Telemetry
and
profiling
to
to
Kappa,
is.
B
Yeah,
so
I
was
thinking
that
open,
Telemetry
and
basically
profile
of
pp,
Prof
endpoint.
A
A
Actually,
I'm
not
sure.
How
is
that
going
a
lot
or
well.
A
A
B
A
B
There
is
one
complication,
though
yeah,
so
when
we
did
this
on
cap
G,
the
cncf
allowed
us
to
add
the
mentees
to
a
cncf
gcp
account
so
that
you
know
so
the
mentees
didn't
have
to
have
their
own
gcp
account.
B
So
I
get
to
find
you
know.
Cncf
does
have
AWS
accounts,
because
you
know
we
use
them
for
brow
and
things
like
that,
but
I've,
yet
to
find
a
similar
thing
that
the
mentees
could
use.
So
that
may
be
a
slight
problem.
B
A
B
B
Yeah,
some
of
the
things
to
do
is
try
and
find
some
people.
B
A
Okay,
yeah,
for
so
for
mentoring,
depending
on
where
so
did
were
there
any
issues
with
time
zones
for
you
know
for
cap
G,
let's
say
last
last
summer.
B
Good
overlap,
but
I
guess
for
someone
in
California,
for
example,
is
a
big
it's
quiet.
Now,
it's
quite
a
different
time
zone.
Isn't
it
yeah.
B
A
B
Okay,
yeah,
hey
mentors
can
be
changed
as
well.
You
know
if
all
of
the
applications
are
from,
let's
say
India
again
or
that
were
selected,
then
you
know
we'd
have
to
find
someone
more
more
suitable
time
zone
to
help.
Okay.
A
B
A
Oh
I
can't
put
it
in
there,
it's
fine,
so
this
is
this
is
I
see.
This
is
from
last
summer.
B
A
A
Okay,
so
I'm
not
familiar
with
the
open
Telemetry
or
the
Chief
Prof
ideas,
I
I
know
a
little
bit,
I
mean
I,
know,
I,
know,
I
I
know
the
concepts
Concepts
a
little
bit,
especially
I,
think
people,
profit
I,
think
I've
I've
done
that
before,
but
maybe
not
in
a
in
a
large
project.
Just
a
small
kind
of
example
for
myself.
A
B
Yeah,
that's
there's
examples
out
there
as
well,
so
like
for
the
on
the
local
celebrity
side,
see
I've
already
put
open
Telemetry
in.
B
There
is
yeah,
there's
prior
art
that
we
can.
We
can
look
at
or
the
mentees
can
look
at.
Okay,
I,
don't
think
they've
got
PP
Prof,
but
I
could
be
wrong.
A
B
A
Okay,
well,
I
guess
we
can
continue
this
thread
on
on
slack
yeah.
A
Okay,
I,
don't
have
anything
else,
we
could.
We
could
do
a
little
bug,
triage,
I,
guess
I
could
stop
stop
recording
now,
yeah.