►
From YouTube: [SIG ContribEx] BiWeekly Meeting for 20220119
Description
[SIG ContribEx] BiWeekly Meeting for 20220119
A
A
C
D
Okay,
so
updates
I
missed
the
last
in-person
meeting,
but
basically
we're
not
gonna
actually
have
the
meeting
till
february.
I
have
not
started
the
planning
process
just
yet,
and
you
can
kind
of
see
me
on
my
camera.
I'm
I've
not
started
the
planning
process
just
yet.
So
if
there's
anybody
who
would
love
to
kind
of
host
the
first
one
in
february
that'd
be
great
and
we
can
talk
through
what
you
need
and
how
you
would
like
to
do
that.
D
But
basically,
I
think
we're
still
going
to
try
focusing
on
the
big
overarching
concerns
of
the
project.
So
we'll
probably
talk
about
the
k-dev
migration
and
just
like
what
happened,
what
it
was
like,
maybe
like
a
little
bit
of
a
retro
on
that
that
would
be
great
any
current
caps
that
are
out
there
and
then
those
are
like
the
two
big
topics
I
was
thinking
of.
But
if
there's
anybody
who
wants
to
volunteer
any
other
topics,
I
believe
the
sheet
is
still
up.
D
A
D
D
C
C
D
A
C
Yes,
okay,
I
think
we
should
start.
I
actually
planning
doing
roadmap
planning
for
mentoring
and
some
of
the
mentees
are
helping
out
as
well
with
that
and
I
plan
on
kicking
up
new
meet
our
contributors
once
we've
done
at
least
one
to
two
community
meetings,
so
I'm
dependent
on
the
community
meetings
kicking
off,
because
I
think
the
higher
priority
is
community
meetings
right
now.
C
C
A
C
I
would
like
to
start
an
outreachy
request
for
rob
scott,
so
I'm
gonna
set
an
issue
for
that
as
well,
so
I
will
get
with
rob
to
talk
about
gateway
api
and
get
them
an
outreachy
and
at
least
it
at
least
brews
up
a
lot
of
a
lot
of
support
in
the
area
that
they're
looking
for.
So
I'm
gonna
stop
that
issue
today.
I've
got
it
on
on
my
planning
tracker
right
now.
A
C
A
A
C
D
B
C
B
C
C
C
It's
all
documented
in
the
mentoring
in
the
mentoring,
repo
look
under
group
group
mentoring
because
we,
I
definitely
need
more
coordinators
for
this,
and
it
is
impactful
and
it
is
visible
and
like
we,
I
literally
we
just
grew
10
chairs
from
this
initiative
last
year.
That's
a
lot
so
yeah,
so
I
definitely
need
to
figure
out
how
to
make
this
more
of
a
program
and
less
of
a
paris.
A
C
C
C
A
A
F
Basically,
right
now
need
to
figure
out,
what's
captured
in
issues
in
the
repo
presently
and
what's
missing,
so
that
we
can
attack
this
from
more
systematic
perspective,
as
opposed
to
you
know,
responding
to
the
pain
point
and
then
yeah
I'm
going
to
work
through
what
some
of
the
capabilities
are
of
zoom
and
of
some
of
the
proposed
solutions
that
petition
I
have
been
working
on
oops.
I
was
going
to
paste
that,
but
that's
not
the
right
thing
in
the
register
so
and
put
it
in
there
later,
but
yeah.
F
D
A
F
B
A
B
B
Sorry
I
forgot
to
mention
that
it
was
this
month:
okay,
yeah
that
went
live
last
week
last
thursday.
I
think
sorry
yeah
time
is
ephemeral
right,
like
I
had
a
hard
time
remembering
if
I
had
told
in
the
last
meeting
that
the
twitter
automation
was
fixed,
so
I
just
said
it
anyway,
so
yeah
other
blogs
in
progress.
There's
a
multi-cluster
blog
dejuan's
working
on
trying
to
figure
it
out.
B
A
B
G
B
C
G
I
I
was
thinking
marketing
yeah
as
marketing.
We
have
to
make
any
specific
arrangements
for
the
coms
or
like
we
need
to
have
some
document
or
something
so
that
we
are
prepared
for
now,
because
things
will
get
over
after
one
or
two
weeks
with
the
kind
of
set
of
ps
and
everything
that
is
lined
up
to
come.
B
C
C
C
A
A
C
C
I'm
all
I'm
also
going
to
start
coming
to
more
marketing
meetings
too,
because
the
other
thing
is
annual
reports
are
just
starting
to
kick
up
and
there's
not
much
that
you
all
need
to
to
help
out
with
there.
At
this
point
I
mean,
except
for
like
you
know,
maybe
some
cheerleading
things
to
some
cigs,
but
nothing
serious,
but
the
not
that
it's
not
a
problem,
but
the
problem
that
we
had
last
time
was:
okay,
we've
got
this
gigantic
report.
C
It's
going
to
be.
You
know,
like
everything
on
that
summary
needs
some
kind
of
outreach
right,
so
I'll
probably
come
to
this
friday's
marketing
meeting,
and
we
can
do
like
a
deep
dive
on
like
what
parts
of
the
summary
need.
Outreach
and
stuff
like
that
and
I'll
talk
to
y'all,
then
about
about
like
what's
what's
coming
up,
but
that's
just
something.
That's
on
your
horizon.
So
that's
like
that's
like
a
beginning,
q2
thing.
C
D
B
B
C
G
Yeah
last
time
it
was
just
a
talks
file
where
we
use
tags
to
carry
out
the
tweets
this
time,
let's
try
out
like
some
efficient
way,
because
last
time
what
I
observed
is
you
know
many
people
do
reached
out,
but
you
know
sometimes
it
was
just
cool
like
we
were
too
late
to
resonate
and
the
work
would
have
got
done
by
the
time
we
put
out
the
tweet.
So
this
time,
let's
be
particular
about
that.
C
Yup
and
that's
exactly
why
I
want
to
try
to
start
us
like
much
sooner
than
last
time,
so
it
would
be
good
if
we
could
have
everything
annual
report
like
done
by
june
or
july.
Like
last
time.
I
think
we
started
in
june
and
july
so
so
yeah.
It
would
be
good
if
we
like
by
the
the
half
of
this
year.
We
were
completely
done
and
like
hands
were
wiped
with
all
annual
report
activities.
A
A
Those
ones
are
google
docs
just
to
get
sort
of
the
any
sort
of
major
changes
out
of
the
way
there
before
it's
opened
as
a
pr
and
ideally
like,
if,
if
you
have
some
time
either
later
today
or
early
tomorrow,
for
the
at
least
the
comms
ones,
that
would
be
really
appreciated.
It's
pretty
much
my
to-do
personally
for
this
afternoon.
A
A
A
A
I
A
I
like
no,
we
we
did
that's,
probably
why
we
did
the
major
like
we
let
it
sort
of
soak
for
like
two
months
with
the
old
one.
I
have
like
searched
for
previous,
like
open
issues
and
or
the
comments
from
the
bot
regarding
consistent
issues
right
now,
and
it's
pretty
low,
it's
mostly
from
new
contributors
that
have
signed
the
old
cla,
but
the
database
sync
hasn't
happened.
I
A
The
next
thing
is
that
there
is
a
the
open
pr
for
flipping
it.
I
linked
it.
There
myself,
kristoff
and
other
people
have
taken
a
look
at
it,
one
of
the
actual
key
differences
in
the
pr
and
which
I
don't
know
if
it's
in
the
pr
right
now,
but
one
of
the
comments
is,
we
are
probably
going
to
remove
our
bot's
message
on
every
like
any
time
it
comes
up
as
like
cli.
A
J
J
Okay,
so
there
were
a
few
things
that
I
was
thinking
about
for
the
past
couple
of
weeks
that
I
mainly
wanted
to
float
by
you
folks
and
see
what
you
think
so
recently
in
kk.
A
lot
of
issues
you
might
have
noticed
that
are
open
are
mostly
along
the
lines
of
support
and
not
really
bugs
or
feature
requests
for
the
project
itself.
That's
one
kind
of
majority
of
issues
that
are
being
opened.
J
Another
kind
is
these
aren't
as
many,
but
you
we
still
get
quite
a
few
of
them.
That
is,
in
terms
of
issues
opened
against
verses
that
are
no
longer
supported.
So,
for
example,
issues
are
opened
against
versions
such
as
1.16
and
1.171,
even
1.19
right,
which
is
the
latest
version
which
went
out
of
support.
J
J
They
try
and
answer
it
as
much
as
possible,
and
then
it
kind
of
fizzles
out
and
the
triage
bot
or
reaps
it
if
necessary,
or
if
the
author
knows
about
how
to
handle
it,
then
they
put
like
a
life
cycle
frozen
and
it
just
stays
there
forever.
I
know
for
a
fact
that
node
effectively
and
like
very
actively
closes
support
issues
that
come
up
unless
they
are
of
like
a
lot
of
significance
to
the
community.
D
J
Thing
that
I
was
thinking
of
was
if
a
kind
support
label
is
put,
or
maybe
a
new
label
is
introduced
to
signify
some
form
of
support,
request
that
automatically
triggers
a
30-day
period
and
the
author
is
notified
when
the
label
is
applied,
so
you
say
kind
support
and
the
bot
says
that
hey.
This
is
a
support
request
by
default.
J
Yeah
plugin
yeah
yeah
so
like.
If,
if
if
a
label
is
put
like
kind
support,
that
automatically
starts
a
30-day
period
of
fixed
30-day
period
post-which,
it
will
be
closed
because
some
issues
also
get
help
for
support
on
the
issues
page
itself
and
also
the
bottle
would
mention
that
if
it
is
closed,
this
is
how
you
can
reopen
the
issue
like
there's.
No
one
stopping
them
from
reopening
it,
but
basically
like
rotting
should
not
like
the
whole
imagery
around
support
issues
and
rotten.
J
That
was
one
thing.
Another
thing
was
the
same
logic,
but
for
like
issues
for
out
of
supported
versions.
So
there
is
a
triage
label,
not
reproducible
slash.
So
there
is
a
trials
level,
not
reproducible.
Maybe
we
can
add
another
one
saying
outer
support
that
again
triggers
like
the
same
30-day
period,
but
it
tells
them
by
linking
the
version
skew
policy,
and
how
do
you
reopen
it
if
it
is
closed
and
so
on
and
so
forth?
Right,
but,
like
then
again
it
has
considerations
of
like
who
can
actually
apply
this
level.
J
You
would
need
the
similar
constraints
for
okay
to
test.
As
for
let's
say,
this,
new
label
called
triage
out
of
support
type
of
thing,
but
like
these
were
like
two
things
that
I
was
mainly
thinking
about
for
the
past
few
days,
and
I
wanted
to
like
float
it
here
before.
I
open
an
issue
on
tests
and
stuff
to
mainly
see
if
it's
discussed
before
and
like
if
it's
even
worth
putting
effort
into.
A
J
D
A
A
I
I
J
For
what
it's
worth
from,
what
I've
seen
in
like
so,
I
spend
like
around
30
minutes
every
day,
just
going
through
issues
and
like
making
sure
that
relevant
at
least
the
minimally
relevant
labels
are
there.
So
at
least
from
what
I
see
for
eol
issues,
folks
from
almost
all
six,
they
ask
if
it's
reproducible
very
rarely.
It
happens
that
they
actually
provide
insight
into
whether
this
is
actually
reproducible
in,
like
the
current
supported
version.
J
D
D
C
D
A
J
A
I
I'm
I'm
not
saying
like
do
that
as
an
alternative,
or
anything
like
that
I
do
like
my
gut
is:
is
it's
at
least
worth
bringing
up
to
the
broader
community?
One
problem
we
have
historically
seen
is
like
there
there's
other
sort
of
commands
and
things
like
that,
but
they
tend
to
not
be
used
by
like
a
wider
by
the
community
at
large.
A
So
we
would
like,
if
we
did
launch
something
like
this,
we
would
want
to
make
sure
that,
like
the
other,
like
groups
know
that
they
exist,
so
that
might
be
a
like
engage
upstream
marketing.
You
know
group
and
that
actually
would
be
a
great
thing
for
the
community
meeting.
You
know
as
we
we
dive
back
in
so
like
just
something
to
keep
on
the
radar
when
potentially
implementing,
proposing
and
implementing
the
solution.
J
A
I
J
A
I
think
product
2
is
like
not
all
sigs
triage
the
same
and
a
lot
of
times,
there's
stuff
that
is
just
left
open,
yeah.
So
that's
where
having
potentially
alternate
messaging
instead
of
just
saying
rotten,
you
know
would
be
better
and
a
lot
of
time
like
we
have
the
like.
The
support
request
thing.
I
think
actually.
I
The
folks
in
the
release
team
had
the
impression
that
those
prs
would
also
continue
to
carry
a
separate
release,
notes
tag
which
they
don't
and,
and
that
broke
a
tool
I
believe
that's
already
been
fixed.
I
just
don't
know
whether
or
not
anybody
else
has
any
tools
that
look
for
the
release,
notes,
tag.
A
I
I
A
F
D
D
C
F
C
Honestly,
everyone
in
this
room
right
now
that's
working
on
anything,
that's
contributor,
experience
related,
fill
out
all
of
the
cfps
for
all
of
the
open
source
conferences
get
the
good
word
out
as
to
what
goes
on
here
right
like
so.
No,
we
don't
do
anything
as
a
group
for
that
event,
but
you
should
absolutely
sing
to
your
heart
sing,
sing
your
heart
out.