►
From YouTube: Kubernetes Community Meeting 20180802
Description
This is our weekly community meeting, for more information check this page: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
A
Alright,
hello,
everyone:
this
is
the
kubernetes
community,
meaning
for
August,
2nd
2018,
I'm,
Sally,
Ross
I'll
be
the
moderator
for
today.
As
a
quick
reminder,
this
is
recorded
and
will
be
made
publicly
available.
So
don't
say
anything
that
you
wouldn't
want
your
grandparents
to
hear
also
as
a
quick
request.
If
anyone
would
like
to
volunteer
to
take
notes,
that
would
be
very
much
appreciated.
B
B
Criticism,
Greek
and
criticism
kind
of
Griffis,
so
good
face
is
a
is
like
an
API
spec
for
various
container
like
metadata
and
criticism
to
kind
of
create
policies
on
top
of
this
metadata.
So
the
kind
of
the
goals
for
critici--
to
test
assertions
before
you
deploy
containers,
so
people
can
kind
of
make
certain
like
signatures
or
requirements
on
containers
that
they
want
deployed
and
critical
will
like
act
on
them.
B
What
we're
gonna
kind
of
demo
it
it
is,
is
a
this
vulnerability
scanning
component
of
kritis,
so
that
kind
of
operators
of
a
cluster
can
verify
that
anything
in
your
cluster
has
like
an
appropriate
level
of
permissions
that
you've
scoped.
So
you
can
say
I
don't
want
any
critical
vulnerabilities
in
my
cluster
and
kritis
will
on
each
just
deployed
check
with
like
a
CV
database,
provided
like
it's
gonna,
be
a
good
face
interface.
Currently,
it's
in
the
demo.
It's
based
on
the
container
analysis.
B
Api,
that's
in
DC,
but
like
we're,
gonna
get
like
its
design.
You
built
on
top
of
your
face
and
also
kritis
like
has
a
kind
of
cron
are
like
a
controller.
That's
kind
of
continuously
running
monitoring
the
images
that
are
deployed
to
make
sure
that
nothing
gets
gets
too
out
of
sync,
and
also
chris,
is
entirely
open-source
three
posts
available.
B
Now
we
haven't
done
like
an
official
release,
but
it's
agra
face
kritis
for
all
the
stuff,
a
we're
gonna
demo
here
so
kind
of
like
the
way
that
what
kritis
operates
on
is
it
has
a
set
of
CRTs.
So
the
one
that
we'll
talk
about
today
is
this.
This
image
security
policy
and
this
image
screw
Tea
Party
ISP,
is
kind
of
how
you
can
figure
kritis
for
the
level
for
the
vulnerability
piece.
B
So
we
kind
of
talk
through
some
of
the
components
here,
but
when
you
so
you
deployed
kritis
on
your
cluster,
you
can
specify
a
whitelist
of
images.
So
these
are
images
that
will
kind
of
get
a
pass
through,
regardless
of
like
the
state
of
the
vulnerabilities
that
they
have.
So
this
supports,
like
using
tags
or
like
fully
a
full
digest
and
all
to
talk
more
about
it
later,
but
any
image
that
isn't
whitelist
requires
a
digest.
The
way
that
that
kritis
is
designed.
B
So
we
have
like
tools
to
make
sure
that
they
kind
of
go
and
update
all
of
your
your
container
images
to
be
based
on
top
of
digest.
It's
like
it'll,
it'll,
retag
everything
for
you
using
digest
instead
of
tags,
then
you
can
specify
like
your
this.
The
kind
of
vulnerabilities
you'll
accept
in
your
cluster
so,
like
maybe
you'll
you'll,
have
a
high
tolerance
which
would
block
out
all
critical
vulnerabilities,
maybe
have
a
low
tolerance
which
will
block
out
anything
from
low
to
high,
and
you
call
so
whitelist
CBE's
independently.
B
So
if
there's
certain
known
vulnerabilities
that
you
find
within
your
cluster,
you
can
allow
those
so
yeah.
Now
it's
so
you
go
to
the
demo
already
just
gonna
see
it
go
then
alright,
so
here
I
just
went
in
salted,
but
so
criticism
like
currently
it's
a
single
home
chart,
so
I've
deployed
this
on
a
cluster
I
just
wanted
to
make
sure
everything's
working,
I,
I
added
an
ISP
and
I
can
do
the
rest
now.
B
But
so
essentially,
I
have
installed
a
career
sonic
on
a
cluster,
and
with
that
it
looks
like
is
we
have
our
the
one
like?
This
is
the
the
hook
that's
running
so
so
this
will
so
like
the
components
here
are:
there's
a
validating,
lipid
configuration,
that's
gonna
with
these
two
are
called
so
one
is
so
on
any
create
or
update
or
pods,
and
the
question
one
is
on
clear,
update
of
deployments
in
a
cluster.
B
B
And
as
you
can
see
so
like
it
kind
of
critters,
comes
back
and
says
that
the
deployment
was
denied
because
it
found
violations
and
I
mean.
Maybe
it
makes
sense
to
kind
of
show
those
here,
but
from
the
the
logs
that
there's,
like
a
bunch
of
owner
abilities
on
this
image,
that
you
can
kind
of
inspect
and
see
what
what
happened
there,
but
so
that's
kind
of
like
the
base
level
of
how
criticism
sign
also
so
so
right.
B
There
that's
kind
of
like
denying
pods
that
have
vulnerabilities
and
the
way
that
that's
done
is
currently
is
using.
Sorry,
it's
like
hard
for
me.
This
screen-sharing,
it
kind
of
looks
like
the
the
gtp
is
right
right
now,
it's
container
house,
but
essentially
like
you,
would
need
to
point
image.
It
scans
them
vulnerabilities
and
then
so
these
like
critical
booms
here.
This
is
a
kind
of
what
its
operating
on
all
right.
So
let's
go
back
to
the
demo
area.
So
here
we
also
have
some
other.
B
B
But
so
to
kind
of
get
around
this
like
so
we
need
to
play
a
pod
with
kritis
integers
have
to
be
fully
qualified
with
digest.
This
is
necessary
because,
like
tags
can
change
and
criticize
get
the
right
one
information
for
something
that
is
like
a
tag
on
it.
So
we
have.
This
resolves
tag,
cube
control,
plugin.
B
So
here,
if
I,
you
can
directly
apply
this
to
the
pod
I'll,
just
kind
of
show
you
what
so
I
don't
feel
like
if
week
at
this,
the
pod
had
the
tag
digest,
but
then
this
will
go
in
and
rewrite
your
Yambol
so
that
it
has
the
appropriate
digest
on
it.
So
if
I
were
to
still
deploy
with
the
digest
like
in
my
SPE,
this
is
so
like
that
just
kind
of
it'll
deny
anything
that
doesn't
have
that.
B
B
B
C
B
Now,
there's
gonna
be
a
blog
post
posted
on
August
13th
talking
about
kind
of
what
the
scope
of
criticism,
what
we
kind
of
see
going
forward
and
like
along
with
that,
what
were
the
first
official
release
of
kritis
and
that
will
be
packages
a
single
helm
chart
that
you
can
deploy
so
hopefully
that'll
be
simple
for
people
to
try
so
coming
soon.
I'd
mentioned
currently.
B
Criticisms
ECP,
but,
like
the
reason
we're
just
waiting
until
your
face
is
integrated
into
claire,
then
it
should
be
simple,
as
like
container
now
say
p
as
base
of
a
graph
a
is
to
integrate
that
as
well,
and
we're
also
working
on
the
idea
of
the
authorization
peace
with
attestation.
So
like
these
kind
of
having
these
custom
policies
that
are
built
around
this
concept
of
attestation.
There's
there's
links
here
once
I
share
the
slides
you
can
kind
of
investigate
more.
B
B
B
B
So
I
don't
know
much
about
forty
years,
but
I
can
definitely
look
into
it.
I'm
not
familiar
with
not
familiar
with
forty
years,
but
definitely
worth
like
investigating
more
than
that.
I'm
not
I'm,
not
quite
sure,
and
then
notary
I
think
it's
it's
a
bit
different.
So
with
kind
of
like
the
off
piece,
I
can
definitely
see
like
it
definitely
has
a
similar
gold
Tony.
B
This
is
kind
of
designed
to
be
like
native
to
it's
kind
of
Cuba
minetti's
deployments,
so
we
kind
of
have
like
a
really
good
experience
there
with
how
you
can
install
it
in
the
primitives
that
operates
on
and
making
sure
that
nothing
has
ever
blocked
like
you
can
imagine
if,
if
you're
running
these
like
pods
somewhere
and
there's
other
like
add-ons
or
something
being
running
in
your
destination,
making
sure
that
nothing
bad
ever
happens
to
your
cluster
edge
because
of
how
you
set
up
your
eyes,
pee
stuff,
all
right.
So
many
other
questions.
B
A
E
Everybody,
so
one
thing
to
note,
first
of
all,
is
that
our
feature
freeze
passed
this
week
on
Tuesday
and
just
kind
of
the
the
standing
reminder.
This
isn't
like
implementation
for
user
code.
Freeze
that
comes
later
in
the
cycle.
This
is
just
a
feature.
Definition
freeze
where
we're
collecting
information
on
what
is
to
come.
The
code
freeze
is
not
until
September
4th,
so
the
almost
5
weeks
away,
then
the
other
thing
just
to
mention
to
folks
is
that
we
cut
our
alpha.
E
It
finally
came
out
yesterday
it
was
a
slightly
delayed
and
you
may
have
also
seen
on
the
1.11
branch.
A
few
hiccups
there's
a
really
a
significant
change
going
on
right
now.
Kind
of
this
is
this
last
month,
or
so,
where
the
mechanics
of
the
process
for
releasing
the
actual
turning
the
crank
and
doing
the
build
doing
the
release,
publishing
things
out
onto
the
web.
That
mechanism
is
changing
significantly
such
that,
instead
of
requiring
a
Google
employee
to
run
it
now,
a
community
member
can
so.
E
This
is
a
really
huge
transition
and
we're
working
out
some
kinks,
but
I
think
it's
really
coming
together
and
expect
now
going
forward
that
the
beta
release
for
1.12
should
be
in
good
shape.
From
that
perspective,
and
in
the
the
minutes
there
is
a
link
bit
the
gates,
1
1
2,
release
info.
If
you
want
more
information
on
where
we
are.
A
E
D
D
Obviously,
caps
are
designed
to
be
an
ongoing
discussions
if
you
have
any
more
feedback
to
flay
reach
out
with
them,
so
it
looks
pretty
similar
to
what
you'd
see
in
dynamic
admission.
Today
you
have
the
ability
to
configure
a
lot
of
the
web
hook
options.
Some
of
those
are
left
for
the
API
server
flags
I.
You
can
have
multiple
definitions
of
this,
so
you
would
have
a
policy
linked
to
back-end.
They
can
exist.
I.
D
Just
sent
out
to
different
web
folks,
here's
an
example:
the
animal,
it's
pretty
basic
couple
user
tours
retargeting.
It
is
cluster
admin
that
wants
to
quickly
apply
auditing
to
cluster
B,
wants
prevent
privilege
escalation.
So
one
of
the
ways
we're
doing
that
is,
you
can
still
set
the
only
configuration
through
the
runtime
flags
that
can
never
be
tampered
with.
It
is
also
dated
by
a
runtime
flying
in
general,
which
is
just
dynamic
configuration.
So
you.
D
On
and
off
you
don't
feel
comfortable
with
it
on
your
cluster
Canaries
developer.
That
wants
to
just
drop
in
extensions
that
you
utilize
a
lot
of
data
closer
at
man
with
multiple
auto
policies
that
send
out
to
independent
auditing
facilities,
I
developer
that
may
want
to
just
turn
up
auditing
on
a
certain
area
of
the
application
I
to
quickly
debug.
D
What's
going
on
with
what
they're
building
a
couple
of
notes,
as
we
were
going
into
this
advance
on
a
he's
moving
into
GA
and
112,
so
we're
doing
a
lot
of
work
to
make
sure
we
don't
affect
the
GA
release
that
and
just
make
sure
it's
properly
a
feature.
Gated
policy
enforcement.
This
this
is
a
pretty
big
change
to
the
current
audit
pipeline.
D
D
Aggregated
servers,
we
just
work
off,
basically
the
same
objects
and
they
only
watch
four
types:
they
care,
abouts,
privilege,
escalation,
beefs,
already
kind
of
talked
about
weak
resources
I.
This
is
something
we
need
to
probably
do
a
little
documentation
on,
which
is
basically,
if
I,
apply
or
give
someone
the
rights
to
apply
an
audit
policy.
If
they
can
write
themselves
a
policy
that
would
allow
them
to
read
all
the
secrets
and
the
closer
or
really
any
data
and
the
closer.
So
we
need
to
make
make
sure
it's.
D
At
least,
you
know
communicated
that
this
is
a
cluster
admin
level
privilege
and
that's
part
of
why
we
have
the
runtime
flag
as
well
the
gate.
It's
because
some
closer
happens
may
not
be
comfortable
with
it.
Now
largely
it
mitigates
that
concern
so
we're
shooting
for
alpha
and
112
and
beta
and
113
and
yeah.
That's
if
you
have
any
questions,
definitely
feel
free
to
reach
out.
Like
I
said
we
just
nerves
this,
but
it's
kind
of
an
ongoing
ongoing
document.
If
there's
any
features
you
might
see
going
forward
definite
reach
out
to
us.
Thank
you.
C
Alright,
pile
on
to
that
Kevin.
Okay,
if
I
can
Sally
okay,
one
of
the
reasons
I
particularly
am
interested
in
dynamic
audit
log
configuration
is
because
it
may
be
one
way
to
allow
us
to
collect
API
coverage
of
our
system
level
tests
right
now
you
don't
like
when
you
stand
up
a
cluster,
you
can't
actually
change
the
audit
policy
at
all,
so
we
really
want
to
be
able
to
for
any
given
cluster.
Like
turn
on
an
audit
log,
go
get
the
audit
log
and
use
that
to
compute
API
coverage,
so
this
is
super
exciting
stuff.
A
F
All
right,
can
you
guys
see
that
yep
awesome
all
right,
so
sig
UI
for
those
of
you
that
don't
know,
sig
UI
is
essentially
kubernetes
dashboard.
So
there's
that
there's
a
new
release
coming
up
soon,
probably
in
the
next
two
to
three
weeks.
The
main
things
of
note
a
lot
of
bug,
fixes
that
have
been
coming
in
and
we're
updating
the
version
of
client
go
and
a
couple
other
go
dependencies.
F
That'll
move
the
ball
forward
when
it
comes
to
our
compatibility
matrix
because
we
try
to
perversion
of
the
dashboard
hit
three
versions
of
kubernetes,
so
the
last
version
of
kubernetes
is
a
current
one
in
the
future
one,
it
actually
mirrors
client
go
and
that's
actually
what
we
version
again.
So
when
the
new
release
comes
out
right
now,
the
current
release
is
one
eight
three,
the
new
version
of
the
dashboard
should
be
1.10,
because
that's
the
version
of
client
go
we're
going
with
so
the
big
thing.
F
The
thing
that
we've
been
working
on
the
most
is
actually
migrating.
Angular.
The
current
version
of
angular
is
angular.
One
I
hear
that's
outdated,
we're
moving
to
angular
six.
That's
actually,
you
know
new
and
supported.
It
is
involved
completely
rewriting
the
dashboard
front-end
from
scratch.
This
alone
is
a
Herculean
effort.
F
That's
been
done
by
very
few
people
and
we
have
to
bless
them
and
thank
them,
but
unfortunately
we're
in
a
split
brain
state,
because
we
have
a
lot
of
effort
going
towards
this
angular
migration,
but
we're
also
still
doing
a
bunch
of
bug
fixes
on
angular
1
and
the
go
packages
behind
everything
so
we're
actually
going
to
rip
the
band-aid
off
after
the
current
or
the
upcoming
release,
we're
going
to
achieve
as
much
feature
parity
as
possible
in
the
angular
migration
and
then
cut
a
release.
So
it's
all
on
the
new
angular
version.
F
This
might
mean
that
there
are
a
couple
features
that
aren't
working
that
were,
but
almost
all
of
the
basic
functionality
that
you're
used
to
will
be
there
and
then,
once
once,
we've
merged
the
brains,
we'll
just
go
through
and
start
patching
things
as
issues
come
in
on
the
horizon.
A
lot
of
people
are
asking
about.
Oauth
2
is
authentication
against
the
dashboard.
Some
people
have
asked
if
they
can
work
on
PRS.
We
hear
you
if
you
want
to
work
on
that.
Please
submit
that
and
we'll
look
at
it.
F
We
also
want
to
simplify
pulling
docker
images,
because
a
lot
of
people
are
having
trouble
if
they're
running,
say
I'm
raspberry
PI's.
They
have
to
specify
the
arm
version
of
the
image
and
then
there
we're
really.
You
know
we're
releasing
multiple
different
architectures,
so
let's
just
make
it
a
multi
architecture
manifest
and
push
that
up.
So
you
won't
have
to
specify
your
architecture
and
also
a
blog
post
came
out
recently
showing
22,000,
insecure
dashboards.
F
We
want
to
try
and
address
that.
That's
something
that
we're
talking
about
internally
things
as
simple
is
along
the
top
of
the
dashboard:
hey,
you
might
be
running
it.
Your
dashboard
might
be
running
insecure.
You
should
mitigate
this
or
hey.
Your
dashboard
is
running.
Is
you
know
the
cube
admin
role?
Are
you
sure
you
want
to
do
that?
F
So
that's
kind
of
the
long
story,
short
version
of
how
things
are.
There
was
a
sort
of
a
staff
shortage
a
few
months
ago,
and
then
things
are
starting
to
ramp
up
so
you're
gonna
see
a
bunch
more
movement.
This
is
actually
what
the
angular
migration
looks
like.
You
also
notice
that
it
has
a
dark
theme,
we're
working
on
both
a
dark
theme.
The
normal
light
theme
that
you
used
to
and
in
the
future
and
in
the
future
you'll
be
able
to
actually
customize
your
CSS.
F
So
you
can
do
things
like
you
know
slightly
brand
it.
So
that's
good!
As
always,
if
you
want
to
contribute,
this
is
the
repo
that
we
live
in.
The
main
things
were
working
on
again.
Are
that
angular,
JS
migration,
lots
of
bugs
have
been
coming
in
so
triaging
those
and
then
feature
discovery,
because
dashboard
I
think
has
a
lot
of
room
to
grow.
As
Kelsey
said,
you
know,
you're
not
going
to
be
using
cube,
cuddle
to
really
interact
with
the
kubernetes
I
think
a
lot
more
people
can
start
interacting
with
the
dashboard.
F
Once
we
start
doing
things
like
supporting
custom
apps
in
it
and
plugins
so
also,
we
are
always
in
slack
and
we're
fairly
responsive
and
just
so
everyone
understands
I
really
have
no
idea
what
I'm
doing
and
I
also
have
to
have
a
meme
and
every
single
thing
that
I
do.
So.
That's
me
any
questions
or
comments.
A
A
G
Hey
I,
don't
have
any
slides
so
I'll
make
some
after
this,
because
I
just
signed
up
to
do
this
update
so
don't
have
time
to
make
a
slide
deck,
but
couple
of
high-level
updates
for
the
the
sig
we
recently
had
our
Sikh
charter
approved.
So
now
we
have
an
official
sig
charter
that
codifies
a
lot
of
things
that
have
MIT
that
are
kind
of
going
to
feed
into
the
next
set
of
updates.
G
So
first
we
have
a
switch
in
our
SiC
chairs,
so
Erin
from
Microsoft
and
VA
from
Google
have
stepped
down
and
they've
been
replaced
by
Carolyn
from
Microsoft
and
Michael
from
from
Google.
So
the
Sikh
charter
kind
of
over,
like
lions
out
how
does
the
chair
maintenance
is
going
to
go
on
and
also
how
we're
going
to
bring
on
new
contributors?
G
So
we
along
that
line
we're
working
actively
to
improve
the
contributor
experience
and
service
catalog
that
is
being
handled
by
a
couple
of
things.
We've
implemented
some
good
guidance
on
like
what
a
good
PR
should
look
like.
We've
been
active
in
labeling
issues,
with
like
good,
first
issue
and
other
things
to
solicit
new
contributors
to
come
in
we're
also
moving
to
prowl
thanks
to
the
Sikh
testing
team.
This
made
it
a
lot
easier
for
us
to
handle
reviews
quicker,
handle
automated
testing
and
retesting.
G
When
we
have
test
flakes
things
like
that,
and
then
the
last
update
I'll
give
is
that
we
have
a
couple
of
new
features
that
have
landed
fairly
recently.
Not
all
of
them
have
been
on
gated
yet,
but
some
of
the
capabilities
are
providing
are
allowing
you
to
use
service
catalog
in
a
more
kubernetes
way,
I
guess
before
we
had
kind
of
scoped
everything
at
the
cluster
level,
and
it
didn't
really
fit
into
how
you
might
want
to
use
your
cluster
with
namespaces
in
our
back.
G
So
we
have
recently
introduced
namespace
broker
resources,
so
you
can
do
things
like
register
a
broker
inside
of
a
single
namespace
and
then
use
our
back
to
correctly
limit
who
can
provision
what
services,
along
with
that
we've,
also
introduced
some
catalog
restrictions.
So
if
you're,
a
cluster
admin,
you've
got
like
five
different
teams
want
to
use
brokers.
You
can
limit
which
services
get
exposed
into
those
namespaces,
so
you
have
better
control
over
what's
being
provisions,
we're
also
working
right
now,
actively
on
defining
a
higher
level
abstraction
that'll
allow
you
to
find
default
types.
G
G
So,
if
I'm,
a
developer,
building
a
service
and
I
want
to
use,
Service
Catalog
I
still
need
to
know
a
little
bit
more
than
just
I
need
my
sequel
or
I
just
need
Postgres,
so
we're
working
towards
providing
default
type
so
that,
as
a
cluster
administrator
I
can
say
here
is
what
my
sequel
should
look
like.
Here's.
What
Postgres
should
look
like
so
then,
as
the
service
developer,
you
can
just
say:
I
need
my
sleep,
oh
and
Postgres,
and
the
provisioning
will
happen
for
you
automatically
cool.
G
H
A
Awesome
look
forward
to
seeing
people
there,
alright,
so
I
apologize.
If
there
were
any
shoutouts
that
were
listed
in
the
shadow
it's
channel,
it
looks
like
they
did
not
get
populated,
so
I'll
give
some
time
for
people
to
populate
those
and
flip
over
to
our
Stack
Overflow
top
users.
So
at
the
end
of
the
month
we
collect
the
top
users
with
Stack
Overflow
answering
through
these
related
questions.
So
thanks
to
Jack
storm
matthew,
elk,
daniel
nicola
ben
david
maze,
constantine
boostin,
bas
von
see
michael
house
and
blouse
const
and
Marcin
Ramos.
A
All
right,
it
looks
like
we
got
some
shout
outs
populated
so
thanks
to
MHB
for
his
efforts,
working
with
sync
testing
to
get
the
service
catalog
all
hooked
up
to
prowl
and
tied
thanks
to
chief
pepper
Duffy
and
the
elder
and
Rdio
dev
for
great
responses
and
their
time
on
me.
Our
contributors
yesterday,
thanks
to
neo,
lit
one
two.
Three
four
quick
responses
is
status,
updates
for
failing
CI
tests,
requestor
life
cycle
and
many
things
to
IMET,
for
quick
reviews
with
changes
to
kubernetes
the
kubernetes
examples
repeal
and
be
sure.
A
C
Actually,
I
got
one
more
just
to
kind
of
jump
the
gun
a
little
bit.
This
is
sort
of
release,
112
related,
but
we're
gonna
turn
off
the
milestone.
Maintainer
Lunger,
it's
part
of
my
mission
to
get
you
a
bunch.
Kids,
that's
one
of
the
things
we've
just
rather
not
port
to
prowl.
So
if
you're
not
familiar
with
it,
it's
the
thing
that
every
time
you
open
an
issue
and
try
to
get
it
added
said
the
latest
really
smiles.
C
Then
you
get
yelled
at
for
not
having
kind
priority
or
sake
labels
on
your
issue,
because
the
release
team
really
wants
that
and
we're
gonna
try
and
find
ways
to
improve
and
motivate
people
to
improve
labeling
hygiene.
But
we
found
that
the
bot
generates
a
lot
of
noise.
So
I
know
the
release.
Team
is
super
happy
about
this
because
suddenly
they're
not
going
to
get
notified
every
day
on,
like
50
different
issues,
but
I
think
contributors
might
find
that
they're
gonna
get
yelled
at
a
lot
less
by
a
bot.
C
But
please
do
be
a
lot
more
forgiving
to
issue
maintainer,
x'
or
bug
triage
leads
from
the
release.
Team
I
know
going
to
various
dangers,
one
of
them
Jeremy
Rickard,
and
a
couple
of
there
are
acting
as
shadows.
So
if
humans
start
pinging,
you
directly
about
your
issues
a
little
more
often
than
maybe
you
were
used
to
it's,
because
we
turned
off
a
bot
to
try
and
save
people's
family.
I
Hi
everyone
in
Paris
for
all
pink
chairs
team
leads
and
everyone
that
runs
a
zoom
meeting.
You
have
male
in
the
Sigma
distro.
It's
very
important
that
you
understand
this
information,
also
to
those
who
are
interested
in
getting
involved
with
interview
experience
activities.
They
are
looking
for
plenty
of
new
contributors.
We
have
tons
of
activities
going
on
right
now,
lots
of
stuff
going
on
our
mailing
list,
joiner
meeting
things
like
a
new
contributor
site
communication
platform,
consolidation,
moderation,
etc.
So
please
join
us.
Thank
you.