►
From YouTube: Brigade Community Meeting -- 2021-11-09
Description
A recording of the Brigade Community Meeting on 2021-11-09
A
Okay,
hello,
everybody-
it
is
tuesday
november
9th
to
the
brigade
community
meeting.
So
we
are
recording
and
posting
this
later
to
youtube
and
on
today's
agenda
we
are
going
to
be
talking
about
the
upcoming
v2
release.
We
have
a
checklist
that
we're
going
to
be
going
over
of
items
that
need
to
be
completed
in
order
to
release
v2,
so
we
are
pretty
much
done
with
development,
so
these
are
all
chores
really
when
it
comes
down
to
it.
So
I'm
going
to
share
my
screen
and
we
will.
B
A
A
A
So
I
believe
we'll
be
doing
that
today
we
do
have
to
test
and
release
v142
or
150
and
all
the
charts
that
go
with
them
before
we
do
the
v2
release.
This
was
bridget's,
wonderful
idea
that
that
we
really
want
2o
to
be
the
most
recent
thing
on
the
top
of
the
releases
page.
We
don't
want
to
release
2o
and
then
have
its
thunder
stolen
by
you
know
a
lesser
thing
such
as
142
or
150..
A
A
A
A
We
need
to
cut
new
version
of
the
brigade
sdk
for
javascript
that
has
to
be
transitioned
to
use
the
stable
apis
ahead
of
the
brigade
rc
release,
because
brigade
certain
components
of
brigade
depend
on
certain
components
of
the
brigade
sdk
for
js,
so
that
has
to
be
released.
First,
I'm
gonna
skip
over
some
of
these,
because
some
of
these
are
like
way
too
nitty
gritty
and
and
don't
need
to
really
be
discussed
in
depth.
Here.
A
Let's
see
we
do
need
to
then
eventually
after
beta
4
has
marinated
for
a
little
while
we
will
cut
the
rc
1..
The
only
changes
between
the
last
beta
and
rc
should
be
the
transition
from
using
the
beta
apis
to
using
the
stable
apis.
So
that's
really
all
that
that
should
be
changing,
we'll
of
course
update
examples
to
use
rc1
and
the
stable
apis.
A
All
the
examples
currently
use
the
beta
apis,
we'll
update
all
the
gateways
and
other
peripherals
to
also
use
stable
apis,
the
latest
version
of
the
sdk
etc,
and
we'll
obviously
blog
about
the
release
candidate.
Try
to
have
some
good
publicity
before
we
actually
go.
Ga
there's
a
lot
of
repository
maintenance
that
has
to
happen,
and
this
in
particular,
is
where
I
need
feedback
from
von
bridget.
Whoever
so
brigade
still
has
a
master
branch.
I
know
we're
getting
away
from
master
branches
and
moving
towards
using
main
branches.
A
A
A
The
correct
thing
to
do
is
probably
merge,
v2
into
master
rename
that
to
main
and
fork
well.
Actually,
we
should
fork
a
v1
branch
off
of
off
of
master
as
it
currently
exists.
That
would
be
the
right
thing
to
do
to
ensure
that
you
know
anybody
who
currently
has
you
know
master
checked
out.
Can
you
know
successfully
fast
forward
to
the
current
state
of
the
the
mainline
development
branch
now
the
thing
that
gives
me
pause
about.
A
All
of
that
is
that's
going
to
be
an
absolutely
enormous
merge,
and
I
I
mean
it
would
probably
be
tens
of
thousands
of
lines,
and
I'm
I
mean
I'm
not
gonna
pr
that
and
nobody's
gonna
review
such
a
pr.
So
I'm
almost
thinking
that,
if,
if
that's
the
approach
that
we
want
to
take
where
v2
gets
merged
into
master,
I
think
vaughn
and
I
should
probably
just
hop
on
together
so
there's
two
sets
of
eyes
on
it,
making
sure
there's
no
mistakes,
making
sure
that
there
is.
A
A
It
shows
you
v1
docs
and
I
believe,
there's
a
prominent
link
up
at
the
top
and
like
a
banner
that
says,
hey
our
v2
docs
are
over
here.
Well,
that
needs
to
switch
around
once.
V2
goes
ga,
so
it
should
defaults
to
the
v2
docs,
with
a
prominent
link
that
says
hey
if
you're
looking
for
the
v1
docs
they're
over
here,
there's
also
a
brand
refresh
underway
for
the
website
that
is
currently
incomplete.
C
A
Yeah,
so
so
you're
right
so
half
of
it
will
just
happen
automatically
when
we
get
the
branches
straightened
out
and
the
other
half
you
know
we'll
take
care
of.
This
is
also
a
good,
a
good
segue
good
time
to
mention
since
vaughn
mentioned
netlify,
that,
prior
to
yesterday,
all
of
our
static
websites
were
hosted
by
the
deus
labs,
slash
steel
thread,
netlify
account
and
as
of
yesterday,
we've
gotten
those
moved
over
to
the
cncf
netlify
enterprise
account
vaughn
and
ronan,
and
I
all
have
permissions
on
there.
A
So
we
can
still
do
everything
that
we
could
do
with
with
those
sites
before
it's
the
the
docs
the
static
website
and
the.
What
am
I
missing
the
blog,
so
we
can
still
do
all
the
things
that
that
we
used
to
do,
but
it,
but
it's
now
under
the
cncf
account
if
anybody
else
wants
access
to
that
bridget
or
karen.
Let
me
know
and
I'll
put
in
a
request
to
the
service
desk.
B
A
Me
a
lot
of
people
yeah.
There
is
a
way
of
of
managing
permissions
for
specific
sites,
and
apparently
I
think
this
was
an
oversight.
They
gave
me
more
permissions
than
that,
and
so
I'm
an
owner
of
all
sites,
so
maybe
I'll
open
up
a
service
desk
ticket
about
that
also
and
say:
hey.
You
gave
me
too
much
stuff
yeah,
so
that's
pretty
much
the
the
the
size
of
it
here
there
there's
another
section
here,
the
ga
section.
A
It's
really
just
a
repetition
of
some
of
what
we
saw
above
some
of
the
the
you
know,
machinations
that
we
have
to
jump
through
to
get
rc
out.
The
door
have
to
be
repeated
when
we
retag.
This
thing
is
as
ga,
so
so
that's
pretty
much
it.
This
is
our
checklist
and
I
pinned
this
at
the
top
of
the
issues
so
that
we
can
all
find
it
pretty
easily.
A
A
We
do
have
a
need
for
additional
maintainers
or
even
just
reviewers
people
who
you
know
from
the
community
who
are
willing
to
look
at
prs,
even
if
they
only
look
at
the
smallest
ones
and
the
most
trivial
ones.
It's
still
helpful
to
have
people
you
know.
Looking
at
those
things
to
to
keep
things
moving
along,
you
know,
vaughn,
for
instance,
is,
is
really
the
only
maintainer
other
than
me.
That's
especially
active
lately,
and
he
does
a
lot
of
code.
A
Reviews
really
appreciate
that,
but
he
also
has
you
know
other
other
fish
to
fry
right
now
and
other
things
that
he
needs
to
be
focusing
on.
So
I
really
do
want
to
try
to
find
ways
to
take
some
of
the
pressure
off
of
him
and
let
the
community
help
out
more,
especially,
as
I
said,
with
very
small
or
or
trivial
issues.
A
D
I
have
two
questions.
First,
one
is
going
back
to
like
youtube.
Currently,
the
calls
are
in
your
personal
zoom
and
I
had
asked
amy
about
it,
but
she
said
that
you're
already
running
them
on
zoom,
but
I
think
we
need
cncf
to
host
it
in
order
to
do
the
integrations
right
to
like
get
these
all
ported
to
youtube.
D
Do
you
want
to
do
that
from
your
personal
account
or
I?
I
personally
think
we
should
have
cncf
kind
of
set
up
some
framework
for
us
just
so
it's
not
tied
to
your
specific
account
because,
like
what,
if
you
can't
make
a
call
one
of
these
days
because
you're
certain
whatever
like,
I
think
we
should
yeah.
Oh.
A
D
Okay,
yeah
I
like
submit,
or
I
responded
to
the
last
ticket
I
submitted
and
then
like.
I
gave
amy
the
agenda
for
a
call
and
everything,
but
she
said
you
had
like
because
I
was
like
oh
yeah
like
we
don't
want
to
do
bevvy.
We
want
to
do
zoom
because,
like
we're
already
there
and
she
said
that
you
had
it
set
up,
but
I
don't
know
she
realized
that
that
was
your
personal
account.
D
A
I
don't
know
how
to
track
that
information
down
at
the
moment,
because
the
community
is
not
really,
unfortunately,
hasn't
been
interacting
with
us
very
much.
If
you
go
and
look
at
the
the
brigade
channel
in
slack
it's
it's
all
like
vaughn
myself,
caroline,
you
know
like
the
yeah,
it's
it's
like
shouting
into
the
void.
A
A
A
C
A
A
The
name
is
escaping
me
at
the
moment,
but
he's
a
a
computer
science
student
in
india,
and
I
believe
he
was
encouraged
for
the
sake
of
some
of
his
coursework,
to
find
some
interesting,
open
source
projects
and
contribute,
and
he
has
already
made
a
few
modest
contributions
and
he
has
mentioned
a
willingness
to
do
more.
So
I
think
he's
currently
on
vacation.
A
But
he
said
that
when
he's
back
he'd
like
to
to
tackle
some
more
of
the
the
things
that
are
labeled
as
good
first
issue,
so
that
is
encouraging
at
least
being
a
student.
I
don't
know
whether
he'll
be
able
to
allocate
the
kind
of
time
that
we
would
need
from
him
to.
You
know,
convert
him
to
a
maintainer,
but
you
know
we'll
certainly
do
everything
we
can
to
help
this
individual
get
started
as
a
contributor
and
and
maybe
get
him
reviewing
some
of
the
smaller
more
trivial
pr's
as
well.
D
D
So
we
could
try
looking
into
that
and
getting
more
involved
with
that,
especially
like
to
get
like
student
engagement,
and
things
like
that,
because
I
feel,
like
jumping
into
brigade,
is
probably
less
intimidating
than
like
jumping
into
like
kubernetes
and
things
like
that.
So
yeah
that
might
be
another
good
route.
It
might
not
be
anytime
relatively
soon,
but
worth
the
investment
down
the
line.
A
Yeah
and
and
the
thing
about
jumping
into
kubernetes
as
well.
This
is
this
is
worth
noting,
and
I-
and
I
don't
know
if
I
had
said
this
already
on
the
previous
call
or
not,
but
this
this
person
who's
been
helping
us
out
a
little
bit
had
no
prior
kubernetes
experience
and
he
was
able
to
follow
the
quick
start
and
set
up
brigade
on
a
kind
cluster
and
then
make
contributions
to
brigade.
This
is
somebody
who'd
never
used
kubernetes
before
so.
A
The
thing
that
I
think
is
really
cool
about
that
is,
it
was.
It
was
a
goal
for
v2
to
have
like
a
really
clean
abstraction
over
kubernetes
and
the
fact
that
this
guy
was
able
to
you
know,
come
up
to
speed
quickly
on
brigade
without
ever
having
used
kubernetes
before,
I
think,
is
a
little
bit
of
an
indicator
that
we
did
something
right
so
can
we
have.
A
A
C
Yeah
we
should
so
I
was
taking
notes.
We
should
find
out
what
the
more
details
on
that
list,
because
that
sounds
super
helpful
if
it
just
like,
because
you're
already
in
a
great
habit
camp
and
I'm
trying
to
do
the
same
of
labeling
issues
like
good
first
issue
or
chore
prs
kind
of
like
trying
to
attract
reviews,
but
so
yeah.
However,
we
can
bubble
those
up
to
whatever
kind
of
oss
list
that.
A
Controls
yeah,
I
try.
I
try
to.
I
try
to
advertise
those
issues
as
well.
You
know
it's
occurring
to
me
right
now
that
actually
it
would
be
a
really
good
use
for
brigade
itself
to
you
know,
have
a
little
script
that
goes
and
finds
everything
that's
labeled
as
like
chore
or
good,
first
issue,
or
whatever
on
you
know
like
a
nightly
basis
and
then
blast
it
out
to
slack,
although
oh
actually,
that
might
not
work,
because
I
don't
think
we
can
get
like
a
bot
account
for
the
cncf
slack.
A
A
A
A
Because
that
would
kill
a
few
birds
with
one
stone
right.
It
would
actually
be
a
really
neat
demo
for
brigade
to
show
you
know
like
I
could
whip
up
a
little
cron
gateway
or
something
that
just
like
triggers
an
event
nightly
and-
and
you
know,
compels
a
job
to
go
and
scan
for
good
first
issues
and
publish
them
somewhere.