►
From YouTube: Brigade Community Meeting -- 2022-03-01
Description
A recording of the Brigade Community Meeting on 2022-03-01
A
All
right,
hello
and
welcome
to
the
march
1st
2022
occurrence
of
the
brigade
community
meeting
I'm
going
to
share
my
screen.
If
you'll
give
me
a
moment.
A
A
All
right-
and
it
looks
like
vaughn-
has
already
volunteered
to
take
notes,
so
thank
you.
Vaughn,
there's
not
too
much
to
cover
today
lots
of
good
news,
though
so
the
first
thing
is
the
release
of
brigade231.
A
I
have
a
pending
blog
post
about
this,
so
I
just
need
actually
any
of
karen
vaughn
or
bridget
to
review.
I
think
you
all
have
the
power
to
approve
that
the
important
thing
about
two
three
one,
this
I've
never
been
so
excited
about
a
patch
release
before
it
installs
faster
and
much
more
smoothly
than
any
previous
version.
A
It
would
try
to
connect
and
it
would
fail
it
would
crash,
but
we
don't
care
because
kubernetes
restarts
things
right
well,
while
the
api
server
is
going
into
a
crash
loop
back
off,
we
have
two
other
micro
services,
the
scheduler
and
the
observer
waiting
on
the
api
server
to
be
available.
A
So
it
too
is
going
into
your
or
they
two
are
going
into
a
crash
loop
back
off
and
you
just
end
up
with
this
rat's
nest
of
progressive
back
offs,
and
it
can
unfortunately
take
several
minutes
for
all
the
flapping
to
stop
and
for
things
to
stabilize.
A
So
what
we've
done
in
2-3-1
is
we
have
each
of
the
individual
components
block
internally
for
a
longer
period
of
time,
waiting
for
their
network-bound
dependencies,
so
we
are
slower
to
crash
and
therefore
we
avoid
crash
loops
and
everything
just
comes
up.
The
whole
system
as
a
whole
comes
up
much
faster
with
no
flopping,
so
we're
pretty
excited
about
that.
A
Hopefully,
the
faster
and
smoother
installation
time
makes
it
a
little
bit
easier
for
new
brigadiers
to
get
started
so
pretty
exciting
status
update
on
brigade
in
five
minutes,
I've
been
meaning
for
a
while
to
film
the
third
episode,
the
topic
of
which
will
be
authorization.
A
It
hasn't
gotten
done
because
for
various
reasons,
my
children
have
been
around
a
lot
lately
and
it
is
very
hard
to
film
something
with
the
children
around
today
is
the
first
day.
I've
really
had
the
house
to
myself
and
quiet,
and
I'm
not
going
to
get
to
it
today,
but
I'm
hoping
that
tomorrow
is
a
good
day
for
that
the
kron
event
source.
We
cut
an
rc
of
it.
I
think
that's
going
to
go
ga
by
the
end
of
the
week.
A
The
rc's
already
been
out
there
for
at
least
a
week,
so
that
should
be
ga.
By
the
end
of
the
week
we
have
the
brigade
dashboard,
formerly
kashti,
tng,
it's
really
just
an
early
prototype
at
the
moment,
but
it
had
been
living
in
my
own
github
account.
It
has
now
moved
over
to
the
brigade
core
org
and
we
have
all
of
the
usual
automation
and
branch
protections
and
all
of
that
fun
stuff
set
up
so
now
we're
in
a
good
place
to
start
getting
contributions
from
the
community.
A
If
anybody
wants
to
work
on
that-
and
unlike
most
of
our
other
components,
that's
all
front-end
stuff,
it's
typescript!
It's
react.
You
know
things
that
the
maintainers
don't
have
a
lot
of
bench,
strength
with
at
the
moment
at
least
I
don't.
I
know
enough
to
be
dangerous
with
with
react.
A
So
it's
in
a
good
place
now
to
start
getting
contributions
from
anybody
else
who
might
be
interested
a
quick
update
on
documentation.
We
had
a
few
people
volunteer
to
work
on
portuguese
translation
of
the
docs.
We
also
had
somebody
step
forward
and
volunteer
to
do
a
hindi
translation
of
the
docs.
A
So
what
I
have
done-
and
I
did
this
you
know
unilaterally-
and
I
apologize-
and
I
will
beg
forgiveness
from
fellow
maintainers
if
this
was
a
bad
thing
to
do,
but
I
created
separate
repos
for
each
translation
and
I
did
make
the
people
who
volunteered
to
work
on
those
the
maintainers
of
just
those
repos.
So
they
don't
have
the
right
bit
anywhere
else.
They
only
have
the
right
bit
on
those
specific
repos.
A
I
also
have
a
pr
open
that
shows
how
we
would
it's
a
draft
at
the
moment,
but
it
shows
how
we
would
integrate
those
translations
into
our
docs
site
and
the
basically
what
it
is
is
we
would
consume
them
as
git
sub
modules,
so
it
all
works
very
nicely,
but
we'll
wait
until
the
content
is
ready
before
we
actually
merge
that
pr.
A
Last
and
certainly
not
least,
we
had
proposed
three
projects
for
the
google
summer
of
code
and
we've
had
quite
a
few
people
already
come
forward
and
say
that
they
would
like
to
work
on
those
projects.
I
don't
think
that's
how
it
works.
I
think
there's
a
formal
application
process
and
I
keep
trying
to
remind
people
of
that.
So
I've
gone
back
and
added
to
the
relevant
issues.
Big
bold
banner,
with
a
warning.
A
You
know
icon.
That
says:
please
don't
work
on
this
until
you
are
formally
paired
with
us
through
gsoc
22,
but
the
nice
thing
is
there.
There
are
people
who
want
to
work
on
this
with
us,
so
very
excited
about
that.
A
That's
all
that
was
on
the
agenda
for
today.
So
we'll
open
it
up
to
the
floor.
If
anybody
has
anything
that
they
want
to
say
or
ask
about,
and
it's
also
a
good
time
to
mention
that
everybody
is
welcome
to
edit
the
agenda.
If
you
ever
have
anything,
you
want
to
talk
about,
feel
free
to
pop
into
that
document
and
add
it
in
advance
so
that
it
doesn't
get
overlooked.
B
So
I'm
I'm
wondering,
do
you
and
I
haven't,
I
will
apologize
and
say
I
have
not
read
the
guidelines
yet,
but
I'm
wondering
do
we
have
specifics
to
help
people
understand
how
much
they
need
to
translate
before
we
can
start
getting.
At
least
some
translations
live
on
the
website.
A
We
we
do
not,
we
do
not
at
the
moment,
so
this
is.
We.
B
A
Yeah,
that's
that's
a
really
good
suggestion,
so
I
will
reach
out
to
people
who
have
volunteered
for
that,
and
you
know
make
sure
that
they
know,
for
instance,
hey.
Why
don't
you
start
with
the
quick
start
and
the
design
document,
or
something
like
that,
because
that
would
that
would
really
get
most
people
over
the
hump
so
to
speak.
So
if
they
start
with
those
high
value
docs,
that's
it
would
be
great
to
have
those
sooner
rather
than
later.
A
A
Also,
interestingly,
carolyn
asked
me
what
my
plan
was
for
how
we
might
keep
those
translations
up
to
date
as
the
english
language,
docs
change,
and
my
answer
to
that
was
well
we'll
use
brigade.
So
so
what
I
intend
to
do
is
we
will
so
we
will
listen
for
merges
of
pull
requests
that
touched
the
english
documentation
and
when
we
detect
those,
we
will
open
a
new
issue
for
each
translations.
Repository
linking
back
to
the
to
the
original
english
change
and
asking
hey,
please
make
the
equivalent
change
in
in
language
x.
B
Awesome,
I
have
one
other
quick
question,
a
point
of
order
of
something
we
talked
about
some
meetings
ago.
B
A
Will
be
archived
eventually,
those
are
those
have
to
do
with
brigade,
v1
and
brigade.
V1
makes
some
assumptions
about
the
name
of
your
primary
branch,
so
being
that
they
are
meant
to
be
used
with
brigade
v1.
I
don't
think
that
we
can
change
those,
but
when
the
support
window
for
v1
ends,
I
believe
those
repositories
will
be
archived.
A
B
I
mean
I'm
I'm
looking
to
hear
from
some
of
the
new
members
on
the
call
as
well,
who
are
having
at
least
I
haven't
seen
on
as
many
calls
I'd
love
to
hear
about,
you
know
felipe
pratesh.
What
are
you
thinking?
What
what
are
you
going
to
jump
into
next.
C
Okay,
hello,
folks,
myself
pratish,
I'm
a
junior
student
from
india
pursuing
like
bachelor's
now
and
since
a
couple
of
days,
I've
been
exploring
brigade
and
the
brigade
dashboard
actually
caught
my
attention
because
I
have
been
building
stuff
with
react
and
since.
C
Five
years
or
so
so
that
actually
the
dashboard
next,
if
there
are
some
available
issues
and
also
I
was
going
through
the
documentation
and
basically
I'm
like
exploring
all
the
new
tools
in
the
cloud
native
community.
So
before
brigade
I
was
exploring
argo
project
to
automate
the
stuff,
and
that
was
pretty
interesting
and
I
came
across
brigade.
So
I'm
thinking
of
trying
this
out
next.
A
Excellent
glad
to
have
you
glad
to
have
you
on
board.
B
A
Yes
and
I'll
and
I'll
be
adding
a
lot
more
of
those
in
the
coming
days.
Backlog
grooming
is
a
thing
that
I'm
going
to
be
focusing
on
later
today
and
tomorrow,
so
there
will
be
a
lot
more
of
those
good
first
issues
coming.
D
Should
we
give
intros
okay
I'll,
go
I'm
karen?
I
am
the
community
manager
for
brigade,
so
I
also
work
with
ken
at
microsoft
and
I'm
a
pm.
So
if
there's
anything,
that's
community
related
things
that
touch
like.
I
guess,
like
our
social
media
events,
swag
stickers,
if
you
want
stickers,
let
me
know
things
like
that.
I
would
be
the
person
you
can
reach
out
to
and
I
am
based
in
san
francisco.
A
And
hey:
if
anybody
wants
to
make
some
big
contributions,
karen
can
do
better
than
stickers
too.
She's
got
some
really
cool
swag.
B
That's
awesome,
I
don't
have
any
cool
swag
and
I'm
not
based
in
san
francisco,
I'm
based
in
minnesota.
We
have
a
lot
of
snow.
I
could
send
you
some
snow,
there's
lots
of
it,
it's
very
cold,
it
might
melt,
I
don't
know,
and
I'm
also
a
pm
on
the
same
team
as
karen
and
every
once
in
a
while.
I
make
it
to
this
call.
My
goal
is
always
to
give
kent
a
list
of
extra
things
to
do,
because
why
not.
E
I
can
quickly
introduce
myself
I'm
located.
My
name
is
vaughn
located
in
boulder
colorado,
I'm
another
maintainer
on
most
of
the
brigade
core
could
bases.
I
definitely
try
and
pitch
in
for
pr
reviews.
Docs
reviews
things
like
that.
I'm
not
coding
as
actively
in
the
code
base
as
kent
is,
but
I'm
around.
D
I
was
gonna
ask
like
with
felipe:
I'm
pretty
sure.
Are
you
like,
because
we,
I
don't
were
they
here
last
week.
I
just
wanted
to
make
sure
that
they
know
that
the
meetings
are
offset
and
that,
like
the
other
ones,.
A
Oh
yeah,
that's
I
felipe.
I
think
you
were
here
last
week,
yeah
it
was
it.
It
was
at
a
different
time
last
week.
What
we're
doing
is
we're.
We
have
people
interested
in
a
lot
of
different
time
zones,
so
we're
kind
of
flip-flopping
the
meetings
where
one
occurrence
will
be
at
11
a.m-
pacific
and
the
next
will
be
at
1
pm
pacific
and
they
switch
back
and
forth.
So
today's
was
11
a.m.
Pacific,
the
next
one
will
be
1
p.m,
pacific
and
we
get
different
faces
showing
up
at
at
the
2..
A
In
fact,
the
last
one
was
our
best
attended
one
yet,
and
that
was
the
later
one.
It
was
a
little
harder
for
us
people
to
make
it
to
that
one,
but
I
think
we
had
some
brazil
folks,
some
australian
folks,
so
yeah,
maybe
eventually
we'll
figure
out
one
time
that
works
for
everybody,
but
we
haven't
yet.
C
So
like
right
now,
it's
11
p.m.
Pst
is
12
30
a.m,
ist.
So
I
don't
think
I'll
be
able
to
make
it
on
1
pm
phd.
But
if
I'm
working
on
something
I'll
be
able
to
update
it
on
slack.
A
C
Oh
actually,
I'm
like
pretty
active
in
kubernetes
lag
because,
like
I've
been
open,
sourcing
and
kubernetes
since
the
past
six
months.
Maybe
so
I
did
a
couple
of
code
contributions,
but
right
now
I'm
with
six
contributes
which
actually
does
work
for
the
contributor
experience
to
improve
the
experience
as
well
as
I'm
also
on
youtube
admin
for
kubernetes
youtube
channel.
So
I
manage
this
stuff,
so
yeah
I'll
be
available
on
slack
anytime.
E
A
All
right:
well,
everyone
have
a
wonderful
day
and
this
recording
will
be
posted
on
our
youtube
channel.
Once
I'm
able
to
download
it
all
right,
see
you
all
on
the
internet,
thanks
bye,.