►
From YouTube: Kubernetes 1.12 Release Team Meeting 20180730
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
Hey
everyone
morning
or
evening,
wherever
you
guys,
are
welcome
to
the
fourth
one
twelve
release
needing
quick
housekeeping
notes.
If
you
guys
haven't
added
your
name
to
the
attendees
list,
please
do
so
and
I
can
paint
the
if
I
can
wait.
Okay,
there,
you
go
the
meeting,
notes
typing
the
link
to
the
meeting
notes
in
the
chat.
B
A
B
A
If
I
apologize
in
advance,
if
I
kind
of
run
this
all
messed
up,
but
it's
my
first
time
so
I
hope
you
guys
will
excuse
me
for
that,
so
we
can
get
started
before
going
over.
The
usual
updates
see
I
signal
bugs
and
feature
there.
We
wanted
there
were
a
couple
of
pieces
of
status
updates
that
we
wanted
to
run
by
the
release
team.
The
first
is
tomorrow
end
of
day.
Tomorrow
is
our
feature
freeze.
So
that's
our
first
calendar
deadline
that
we
are
hitting
so
by
by
tomorrow.
A
We'd
expect
all
the
features
that's
going
in
112
to
be
updated
in
the
Kay,
its
feature,
repo.
This
helps
us
get
stock
of
what
features
that
are
going
to
go
in
112
and
also
kind
of
get
a
handle
on
dogs
test
and
release
note
status
for
the
feature
later
in
the
call.
Maybe
we
can
get
an
update
from
Stefan
on
the
status
of
the
features
and
where
he
and
the
features
team
might
need
some
help.
A
So
that's
tomorrow,
Tim
sent
out
an
email
on
Friday
to
the
cig
leads
letting
them
know
that
the
freeze
is
coming
up
and
calling
for
some
action
on
their
part.
I'm,
assuming
we
will
send
out
another
broader
email
sometime
today
or
tomorrow
to
Cuban
and
his
staff
about
the
same
and
I
can
follow
up
with
Tim
I
can
follow
up
with
you
offline
Tim
about
that.
The
second
piece
of
update
is
our
alpha
cut.
That
is
so
tomorrow
end
of
day
tomorrow.
So
so
the
way
it
goes
is
I
believe
we
wait.
A
We
definitely
we
wait
on
the
CI
signal
to
be
green
before
we
can
go
on
with
a
cut,
but
that
said
considering
this
is
alpha
and
considering
that
we
would
be
going
over
a
new,
a
new
script
for
cutting
the
branch,
and
in
considering
that
this
is
the
first
time
a
non
Googler
will
be
doing
the
end-to-end
flow.
Tim's
preference
was
to
go
ahead
and
try
this
out
tomorrow,
provided
the
tests
are
not
super
broken
and
we
can't
cut
a
build
a
road.
A
So
the
idea
is,
we
will
still
go
ahead
and
cut
in
alpha
tomorrow
to
just
do
a
dry
run
of
the
script
and
see
how
things
go
and
verse
converse
it
will.
You
know
it
will
surface
newer
issues
that
kind
of
wants
our
attention
sooner
than
later,
so
we
still
want
to
go
ahead
and
cut
the
Alpha,
but
I
would
like
to
hear
from
maybe
jog
in
the
call
and
everybody
else
if
they
have
any
concerns
around
this.
A
C
A
D
Yo
so
as
far
as
signal
is
concerned,
I
would
say
this
address
is
currently
all
over.
This
would
be
yellow.
We
do
have
a
bunch
of
issues
that
were
raised
in
the
previous
week
that
we're
fixed,
and
there
are.
There
are
a
couple
of
issues
that
have
arisen
in
the
upgrade
side,
it
is
mostly
GCI.
Gkn
sticks
second
cementation
and
life
cycle,
and
it's
kind
of
similar
with
the
master
blocking
as
well.
D
A
D
A
D
E
D
Working
on
it
like
we
look
at
the
issue
that
all
that
is
raised
against
the
barium,
they
were
working
on
fixing
the
thing
I
think
they
thought
they
were
discussing
about
removing
the
test
or
something
like
that.
But
I,
don't
know
what
the
exact
damage,
but
right
now
I
would
say.
Is
that
the
update
from
neo
Knight?
Is
that
the
hope
they're
working
on
expressing
it
and
they
they
like
PRS?
Sorry,
there
was
a
PRN
dosing
issue
that
was
raised
for
1p
all
got
merged
and
another
issue
was
was
closed,
but.
A
D
E
Let
me
let
me
just
get
my
little
I
have
a
trained
speech.
I
have
a
dream
that
one
day
we
can't
cut
release
until
every
test
on
that
dashboard
called
release
master
blocking
history,
because
otherwise,
that
dashboard
is
filled
with
tests
that
are
actually
blocking,
and
that
makes
it
harder
for
us
to
automate
this
problem
away.
Yes,
no,
like
we
really,
let's
go
chase
this
down.
Yeah.
A
Yeah
I'm,
looking
at
master,
blocking
and
I,
say
yeah
I,
seven
said
the
cue
Backman
one
and
then
a
couple
of
GCI
and
GK's
things
that
are
just
failing
on
a
couple
of
just
continuously
so
I
think.
If
we
have
the
tracking
sheet
with
these
tests
and
the
issues
tracking
them,
it
will
kind
of
give
us
a
good
visibility
on
who
is
looking
into
that
yeah.
A
A
So
if
you
need
any
help
following
up
with
them
one
on
one
and
if
you
think
we
can
crowdsource
some
health
among
the
release
team,
okay,
more
than
happy
to
you,
know,
help
you
there
sometime.
So
if
you
need
help,
if
you
could
just
indicate
that
in
slack
or
in
the
tracking
sheet,
we
can
do
similar
to
what
you
guys
did
in
111
with
me
that
will
be
useful.
Yeah
yeah.
D
A
F
Can
you
hear
me
I'm,
awesome,
so
yeah?
So
as
of
the
last
time,
I
sent
out
an
email
regarding
features.
We
were
at
27
features
about
18
of
those
were
actively
tracks.
People
said
they
were
going
to
happen
and
nine
of
those
were
hey.
They
may
happen
so
since
then,
we've
we've
we've
kind
of
bumped
up
to
48
features,
so
that
is,
that
is
the
feature.
F
Inflation
that
happens
within
the
first
month
and
a
half
I
expect
that
to
go
down
within
the
next
three
weeks
or
so,
but
but
as
of
now,
that's
kind
of
where
we're
at
I
am
still
pinging
people
for
things
that
have
no
milestones
but
as
as
of
tomorrow,
where
I
feature
free.
So
anything
following
that
will
require
an
exception,
we're
doing
really
great
in
terms
of
feature
collection
just
from
the
perspective
of
of
getting
them
in
sooner
rather
than
later
and
being
really
Maggie
to
people.
So
so
thank
you.
A
F
Yes,
for
the
most
part
like
I,
you
were,
you
were
mentioning
before
for
the
most
part,
it's
it's
something
that
we
can
do
a
synchronously
I
think
posts
well
now
that
we're
in
a
much
better
place
prior
to
free
to
feature
phrase,
I'll
collate
a
list
of
issues
that
kind
of
have
no
status
on
them,
and
we
can.
We
can
go
out
to
the
SIG's
and
anything
that
way.
A
And
I
was
looking
at
the
feature
tracking
spreadsheet
Steven
and
it
looks
like
there's
good
information
on
dogs.
If
dogs
is
needed
or
not,
but
I
kind
of
don't
see
much
information
on
test
status
for
each
of
these
features
do
we
need
to
follow
up
with
six
on
that,
or
is
it?
Do
you
think
it's
a
little
too
early
for
them
to
figure
out.
F
Sorry
I
was
talking
to
me
so
yeah,
usually
in
the
first
month
or
so.
We
don't
have
good
signal
on
exactly
what
they're
deciding
with
the
tests
or
the
test,
maybe
referencing
something
from
prior
release.
So
we
can,
we
can
I
would
say.
Maybe
in
two
weeks
would
be
the
right
time
to
start
driving
that
down.
Okay,.
A
A
A
E
Yeah
so,
like
I,
have
this
broad
overarching
goal
to
reduce
the
number
of
kind
labels
to
the
magic
number,
seven
plus
or
minus
two,
but
the
things
that
are
specifically
relevant
to
this
team
right
now
or
I?
Finally,
cover
to
that
priority:
slash
failing
test
label,
so
there
are
only
what
five
priorities
now:
a
critical
urgent,
important,
soon
important
long-term
backlog
waiting
evidence.
So
that's
it
ordered
list
great,
no
more,
like
two
priority
labels
assigned
to
failing
tests.
E
Instead,
you
to
priority,
whatever
you
think
is
most
important
personally,
if
I
were
CI
signal,
I'd
mark
everything
as
critical
urgent,
because
if
ailing
test
is
probably
blocking
us
from
cutting
release
and
kind
failing
test
kind,
failing
test
means
the
test
is
consistently
failing.
Kind.
Flake
means
the
test
is
liking.
That
will
help
us
identify
those
two
different
kinds
of
failures,
but
failing
tests
are
probably
more
important
and
easier
to
troubleshoot,
so
you
should
go
after
those
first,
or
at
least
that
would
be
I,
have
recommendations,
I
linked
the
community
issue
in
the
doc.
E
D
E
E
Because
I
will
happily
work
that
my
goal
is
to
like
reduce
the
amount
of
nagging
that's
thrown
at
you.
I,
don't
know
this
is
the
meeting
to
do
it
by
the
way,
but
there
was
talk
of
like
is
that
milestone,
thought
that
goes
through
and
comments
on
every
issue
about
all
those
labels
being
super
super
correctly.
Is
that
actually
helpful,
or
could
we
reduce
toil
and
noise?
Please
turn
that
off
or
figure
out
how
to
do
that,
but
I
don't
want
to
find
track
us
on
that
today,
yeah.
A
A
So
next
up
I
think
that
brings
us
to
the
end
of
our
planned
updates.
Does
anyone
else
have
any
questions,
slash
concerns
or
updates.
F
So
from
my
side,
I'm
kind
of
trying
to
consolidate
some
of
the
documentation
in
cig
release.
So
at
this
point
now
that
we've
broken
into
the
role
handbooks,
there
is
also
some
documentation
kind
of
like
top-level,
that
should
be
reviewed
by
each
of
the
roles
so
like
the
features
lead
role.
That
information
is
no
longer
accurate
compared
to
what's
in
the
future,
is
role
handbook
right.
So
you
should.
You
should
be
working
to
consolidate
some
of
the
information
around
your
role.
F
So
take
a
look
at
the
readme
for
sig
sig
release,
slash
release
team,
slash
rate
right,
take
a
look
at
that
and
see.
If
any
of
your
stuff
is
inaccurate.
I've
opened
up
an
issue
in
cig
release.
In
addition
to
that,
we
had
some
discussion
around
milestone,
maintainer
and
what
we
should
be
doing
with
that
team
when
it
should
be
updated.
Who
should
have
access
to
it?
There's
also
a
PR
up
for
that
Erin
I'll
ping,
you
separately
just
a
for
you
to
take
a
look
at
that
and
kind
of
drop.
E
F
Perfect,
oh
right,
that's
kind
of
an
ask
from
you
to
the
ephemera
a
folder
within
sig
release.
If
any,
if
everyone
can
be
looking
at
the
ephemera,
folder
and
figuring
out
what
can
be
removed
and
actively
working
on
removing
it,
that
would
be
super
macaron,
happy
to
I'm,
pretty
sure.
A
G
A
E
H
E
There's
the
setting
you
can
use
to
prevent
it
from
kicking
you
into
full-screen
when,
after
somebody
shares
I
forget
where
it
is,
but
it's
maybe
my
favorite
feature
second
only
to
not
automatically
turning
on
the
camera
and
microphone
as
soon
as
you
join
a
meeting.
Yeah.
E
E
H
E
C
H
A
Okay:
let's
let's
wait
for
my
mo
minutes
and
if
moment
is
still
having
issues,
and
maybe
we
could
do
this
offline
and
then
just
post
a
video.
B
B
B
E
D
D
D
C
D
Branches
here,
fourth
master
block
a
massive
upgrade
and
all
the
other
kinds
of
tests
like
for
each
and
every
branch.
We
have
different
areas.
So
all
these,
like
confidence,
locking
locking
tests
or
you
can
every
version
like
when
we
cut
one,
not
one
two-
there
will
be
a
1.11
popping
and
stuff,
so
that
is
basically
filtering
based
on
editing.
So
was
he
a
signal?
I
would
say
this,
and
this
are
important
master
blocking
and
master
degree.
D
So
you
can
so
you
guys
can
see
that
there
are
a
bunch
of
tests
that
are
failing
here
and
and
passing
all
that
stuff.
So
so
each
of
these
is
is
a
category
of
tests,
so
the
conformance
tests,
for
example,
AWS
tests
and
stuff
of
that.
So,
for
example,
over
here
we
have
failed
to
test
grading
on
this
idk
and
it
actually
tells
you
what
our
failing
tests
in
the
overall
grade
itself.
D
So
this
is
actually
a
good
picture
where
you
can
without
going
into
the
actual
grid
itself,
you
can
go
ahead
and
tell
that
we
have
failing
tests,
which
we
need
to
look
into
so
I'd.
Look
at
this
one
too.
I
know
that
I
need
to
go
and
look
at
GCC
educators,
because
there
is
an
overall
failure,
so
tests
can
fail,
it
can
be.
Flaky
can
fail
a
number
of
times
and
stuff,
but
our
test
is
considered
failing
only
when
there
is
an
overall
figure
on
it.
D
So
you
can
see
where
that's
an
overall
failure
in
C,
wherever
the
failing
tests
there
is
over.
So
I
just
see
that
you
go
to
that
particular
tests.
Let's
say
I
go
to
GC,
idk,
plug-in
failure
and
you
have
the
grid
so
the
test
grid,
it's
actually
the
based
on
the
category.
So
we
have
various
categories
even
listed
up
here.
D
D
So
this
is
failing
on
6
scheduling.
You
can
see
that
it
actually
has
a
categorization.
In
most
cases,
you
will
be
able
to
tell
with
SiC
the
testers
by
just
looking
at
this.
There
are
cases
where
that
might
not
be
enough.
Some
tests
like
test,
for
example,
they
don't
tell
that
it's
a
particular
site.
So
in
those
cases
we
need
to
actually
dig
in
more,
but
usually
in
these
cases
you
just
look
at
this,
and
you
know
that
a
test
is
fearing.
So
that's
there.
I
can
look
at
this
grade.
D
D
D
This
basically
is
giving
you
the
actual
error
log
like
where
the
test
failed
in
cedar
logs
over
here.
So
this
test
is
had.
This
has
an
error
over
here,
coronial
earlier
so
this,
while
that
this
is
actually
helpful
for
the
person
who
is
going
to
actually
go
in
and
dig
into
the
issue
and
see
that
okay
I
need
to
find
out
what
the
test
failed,
the
tests
fail,
then
I
can
actually
fix
it.
So
this
is
one
of
the
places
where
you
can
get
actual
information
and
say
that
okay,
this
is
my
error.
D
D
So
you
can
actually
click
on
this
and
it
shows
you
the
logs
and
you
can
actually
actually
go
ahead
and
take
a
look
at
it
if
I
check
these
boxes,
but
if
I
want
to
see
the
corner
Locker
and
check
on
Kern
dot
log
over
here
and
it
will
show
the
log
as
well,
you
can
see
that
it
got
reloaded
and
it
is
gonna
show
you
the
Conan
logs
over
here,
so
I
can
actually
take
the
log.
The
rocks,
of
course,
are
the
most
important
things
in
debugging
any
issues,
so
you
just
observe
the
logs.
D
You
are
the
program
you
will
have
built
in
the
logs
correctly,
so
you
should
be
able
to
figure
out
what's
wrong
if
you've
done
your
login
correctly.
In
most
cases,
that's
helpful.
If
you
want,
we
can
take
a
look
at
more
logs.
You
can
also
take
out
a
full
log
of
every
part,
every
particular
entry,
and
you
can
also
go
for
the
timestamp.
We
get
considered
over
the
period
that
I
like
what
the
test
results
were.
Of
course
you
can.
You
can
actually
filter
stuff
here
right,
so
I
can
say.
D
A
D
For
you,
yes,
so
if
you
just
see
the
that's
a
job,
so
whatever
you
see
up
here
right,
that's
the
job
that
I
wanted
to
filter
by
and
I
just
taped
together
and
I
paste
again,
it
gives
me
the
overtime
charge
of
the
particular
test,
so
the
particular
job
I
can
actually
drill
down
further
I
can
say
which
test.
For
example,
let's
say
I
want
to
filter
finish.
D
This
effect
will
not
work
generally,
most
cases
it
works,
but
you
would
see
in
this
case
sometimes,
if
I
not
filter
correctly,
so
you
can
try
to
cut
down
the
string.
You
know
that
stuff
and
try
to
filter
I've
tried
it
with
this
one.
It
doesn't
work,
but
most
cases
you
will
see
that
you
actually
can
get
quite
clear
results
by
just
turning
on.
Fourth,
you
can
actually
use
you
on
the
failure
test
and
all
of
that
stuff,
so
this
actually
allows
you
to
see
a
gif.
D
D
So,
for
example,
you
can
see
that
there
is
test
trailer
here
that
had
that
happen
does
spike
here.
So
this
was
when
the
test
trail
and
which
test
failed.
You
can
you
can
see.
This
is
the
test,
that's
real
and
when
it
trail
so
and
which
was
a
job
that
it
failed
and
generally,
if
you
don't
specify
a
test,
it
will
just
take
it
as
test.
D
So
this
is
something
that
actually
helps
most
of
it
is
something
actually
helped
you
to
debug
this
like
we
can
actually
see
what
are
the
errors
that
are
occurred
and
when
they
occur
and
all
of
that
stuff
so
and
the
generally,
so
this
can
sometimes
help
you
to
actually
figure
out
where
it
failed.
So,
for
example,
there
is
it.
A
Couple
of
things
that
I
found
useful
here
when
I
did
111
was
model.
Could
you
just
scroll
up
to
the
top?
Please
yeah
I
I,
trying
to
use
this
more
to
see
the
trend
of
the
bugs
like.
When
did
it
start
failing
or
did
it
fail?
This
was
the
same
tests
are
flaky
during
previous
releases.
One
way
you
could
do
that
is.
There
is
a
date
text
box
mama
that
we
mix
right
there
yeah
okay.
Now
you
can
specify
that
the
date
range
where
you're
trying
to
look
for
failures.
A
So
basically,
if
you
give
it
it
snapshots
the
last
two
weeks
of
data
here
you
chose
the
previous
release.
It's
our
previous
older
date.
It's
going
to
snapshot
data
for
like
two
weeks
around
that
time,
so
that
was
super
useful
eh
podÃa
and
you
can
also
drill
down
based
on
the
sake
itself,
like
the
the
colored
boxes
on
top
some
ones.
You.
H
G
D
A
D
Okay,
so
basically
we
can
see
over
here
that
these
are
all
failures
in
upgrade,
so
upgrade
refers
to
both
upgrade
as
well
down
to
it.
So
you
can
see
here
that
dead
the
day.
So,
for
example,
there
is
sick,
instrumentation
failure
over
here
right,
so
this
basically
means
that
this
is
a
misc
failure
test.
So
if
you
don't
see
this
like,
if
you
see
only
an
overall
test
failure
on
a
skew
test,
failure-
and
that's
it
so
in
those
cases
it
is
very
likely
not
misguided
upgrade
is
probably
a
failure
from
the
testing.
A
H
A
D
Guess
like
this
is
the
question
was:
how
do
we
figure
out
the
desk,
rent
and
I?
Guess
that's
the
status
greater
than
the
trash
she
dies?
Well.
Mit
actually
helps
you
to
figure
out
stuff.
I
think
this
can
be
our.
This
is
definitely
about.
It
can
be
helpful
for
a
developer
to
go
and
take
into
issue
as
well.
So
think
there
is
something
that
needs
we
told
to
people
like
you
that
I
try
to
learn
how
to
use
it.
D
A
The
only
other
thing
that
I
wanted
to
show
not
related
to
test
for
itself
was
like
this.
This
actually
came
up
from
Mohammed
question
this
morning.
As
to
how
do
you
know
who
which
say
God
who
owns
like
a
test
change?
It's
not
this
particular
test
started
feeling.
How
do
we
know
who
to
assign
the
bug
to
one
way
moment?
Do
you
want
to
stop
sharing
I?
Can
try
sharing
my
pee
with
you
sure.
H
A
Can
you
all
see
my
screen
good,
so
this
is
what
I've
been
doing.
Maybe
there's
a
better
way
to
do
this.
If
so,
Aaron
or
whoever
knows
this,
please
let
me
know
okay
cool.
So
one
thing
this
morning
moment
was
asking
us
if
I
see
this
new
job,
this
new
job
here
failing,
for
example,
if
you
go
to
blocking
this
particular
one
he
wanted
to
know
who,
should
you
know
who
should
I
assign
this
issue
to
one
way
you
could
do?
A
That
is
if
this
is
not
very
clear,
like
it's
not
very
clear,
a
bit
sick
owns,
this
I
generally
go
to
brow,
config
so
prowess.
Our
is
our
continuous
testing
environment
that
we
use
for
the
assistance.
So
if
you
go
to
Kuban,
it
is
test
infra,
there's
this
under
browse
this
there's
a
folder
called
prowl
and
under
that,
as
a
conflict.
What
ya
know
this
is
like
this
huge
file,
chest
and
trans
now
sick
test
and
try
working
on
splitting
this
down
now
to
a
specific
sake,
so
it's
more
maintainable.
A
So
unless
that's
completely
done
you
until
that's
done,
you
can
still
go
to
a
test.
Interrupt
route,
config,
dot,
Yama
and
all
the
all
the
tests
continuous
test
runs.
They
are
defined
here
as
separate
blocks
so
generally,
what
I
do
is
I
just
look
at
the
blame
or
history
on
the
file
and
just
look
for
this
particular
job.
A
Yeah,
so
here
I'm
able
to
see
that
here's,
the
name
of
the
thing
this
was
added
by
say.
Whoever
last
touched
this,
maybe
that
person
has
no
is
not
really
responsible
with
the
failure,
but
at
least
I
know
where
to
go
and
I
know
where
to
start
my
tracking
from
if
you're
not
able
to
find
it
is
the
mapping
easily
here
yet
another
place
to
go.
Is
your
test
grade
config?
This
is
also
under
test.
Infra
tests,
great
conflict
at
llamo.
A
This
directly
corresponds
to
the
names
here
like
basil
test
you'll
be
able
to
find
it
you'll
be
able
to
find
one
block
here.
That
says
please
test,
and
there
are
many
more,
but
then
it
tells
you
like
here
it.
This
is
the
name
of
the
continuous
job
and
it
corresponds
to
this
particular
tab
in
test
grade
so
for
everything
you'll
find
like
a
mapping.
So
that
way
it's
easy
to
like
do
a
history
or
a
blame
on
that
and
then
look
at
who
you
can
go
and
at
least
start
talking
about
the
failures.
A
A
A
J
Quick
question:
what
was
the
other
tool
called
the
test
rush
thing?
Can
somebody
drop
a
link
to
that
in
to
the
document
please
or
and
and
then
I
have
a
second
question
for
the
test
grid
for
failing
tests
we
saw
before
the
the
actual
grid
elements
were
red,
and
then
we
saw
on
the
left
side,
the
name
of
the
tests,
I,
don't
know
over
all
and
others,
and
before
I
saw
that
only
a
couple
of
those
titles
were
read,
while
the
the
tests
themselves
seemed
to
be
well
read
all
the
way
down.
A
The
reverse
is
also
true.
Sometimes
it
the
test
will
get
fixed,
but
the
tab
will
still
remain
red
for,
like
few
runs
before
it
just
brings
it
out
of
the
failure.
State
I,
don't
know
exactly
how
many
runs
I
think
that's
also
configurable
in
just
the
conflict
but
yeah.
It's
just
a
visual
cue
of
if
it's
a
continuous
failure
or
flake.
I
I've
got
a
question,
so
how
would
a
new
contributor
get
involved
with
cig
release.
A
Okay,
I
was
a
new
contributor.
The
way
I
got
involved
was
a
I
started
at
Linda's
sake,
release
team
meeting
and
there's
a
slack
channel
the
sake
release
channel
that
you
can
join
where
we
talk
about
both
the
release,
team
items
and
also
general
sake,
release
Charter
and
work
items.
There
there's
also
bi-weekly
a
cig
release.
Meeting
that
happens,
Tuesdays
I
think
2
p.m.
PST.
A
If
you
go
to
the
cig
release,
github
page
you'll
find
links
to
the
weekly
meetings
through
slack
channel
to
our
calendar
and
everything
so
I
would
highly
encourage
our
joining
the
slack
and
then
seeing
what
might
interest
you
and
then
working
with
folks.
There,
Tim
or
Aaron
Steve,
and
anybody
else
has
more
insights
into
this.
F
Summed
it
up
pretty
well
we're
we're
up
at
all
hours
of
the
day,
honestly.
So
if
you're
hanging
out
and
sig
released
for
happy
to
give
you
more
information
on
slack
I
have
a
little
blurb
that
I
put
together
for
new
contributors
for
the
release
team,
specifically
that
I
can
link
you
to
sorry.
I
didn't
see
who
said
that
so
yeah.
I
Sure
I'm
actually
in
the
slack
channel.
So
if
you
could
tell.