►
Description
On-boarding session for k8s-ingra-wg newcomers which happened October 24 2019
A
A
B
C
E
F
F
G
H
I
J
K
A
M
G
O
A
Q
R
S
U
V
V
Y
N
Z
AA
Z
B
E
Hi
I'm
honored
I'm,
a
software
engineer.
I
work
at
a
hedge
fund,
I've
been
using
kubernetes
for
a
little
over
three
and
a
half
years
now,
I've
been
contributing
sporadically
to
some
of
the
networking
projects
in
the
cloud
foundation
like
metal,
lb
and
externally
NS
I'm
here
because
of
Tim's
tweet
asking
for
help
with
the
intra-group
just
trying
to
see
how
I
can
help.
A
A
AC
Everyone,
this
is
amazing
and
overwhelming
I
can't
believe.
We've
got
76
people
now
on
the
call,
and
even
if
you
count
out
Bart
and
dims
and
George
and
myself,
we've
still
got
way
more
people
than
I
know
what
to
do
with.
So
thank
you.
Everybody
who's
coming
here,
literally
from
all
around
the
world.
This
is
this
is
incredible.
I
think
it's
worthwhile
to
go
into
a
little
bit
of
the
history
of
how
we
got
to
where
we
are
so
you
can
understand
the
sort
of
things
we're
talking
about
under
this
workgroup.
AC
So
when
we
started
this,
this
kubernetes
thing
we
realized
we
needed
a
place
where
we
can
store
our
are
the
images,
the
docker
images
that
we
were
producing.
So
first,
we
created
a
docker
hub
account
and
we
pushed
all
our
images
up
to
docker
hub
and
then
we
realized
that
that
wasn't
reliable
enough
and
we
needed
more
control
over
what
was
going
on.
So
we
created
a
this
was
all
mostly
Googlers.
AC
At
the
time
we
created
a
cloud
registry,
Google
GCR
for
our
container
images,
and
we
started
pushing
all
our
stuff
there
and
for
a
long
time
that
was
okay,
because
it
was
mostly
Googlers
working
on
the
project
or
at
least
every
subsystem
in
the
project
had
Google
people
working
on
it.
So
it
was
totally
okay
for
us
to
say
well.
AC
Only
Googlers
can
push
to
the
repo,
because
that
was
just
the
way
it
work
and
then,
as
the
project
grew
up,
we
realized
we
needed
other
little
things
like
a
website,
and
so
we
created
a
website
and
we
of
course
decided.
We
were
going
to
run
our
website
on
kubernetes.
So
we
spun
up
a
cluster
and
started
running
our
website
via
nginx
and
some
static,
config
and
other
stuff.
AC
Along
with
the
website,
we
decided
we
wanted
a
bunch
of
vanity
domains,
short
short
things
so
code
that
cait's,
that
io
and
those
sorts
of
things
that
let
people
have
nice
short
cute
urls
to
take
them
to
places.
So,
like
I,
don't
know
if
everybody
knows
this,
but
like
PR
dot
Kate's
that
IO
slash
number
will
take
you
the
right
PR
on
ginno,
and
so
we
started
accumulating
those
things.
And
then,
of
course,
we
wanted
to
have
go,
get
work
so
go
get.
AC
AC
We
want
to
have
more
people
from
more
areas
with
more
backgrounds
we
want
to.
We
want
to
be
able
to
have
these
services
be
available
today.
Do
you
know
what
happens
if
cait's
dot
IO
goes
down?
It
means
nobody
can
go,
get
kubernetes
anymore
and
who
gets
paid
for
it.
Anybody
know
I,
think
I,
know
I.
Do
anybody
else,
nope,
nope
I
think
it's
pretty
much
just
me.
That
is
not
a
tenable
situation
for
something
that
is
as
widely
used
as
this.
AC
AC
There's
got
to
be
more
people
out
there
who
want
to
help
us,
and
so
I
opened
my
mouth
on
Twitter,
and
here
you
all
are,
which
is
just
amazing.
I
I
can't
express
how
overwhelmed
I
am
by
having
everybody
here
so
I
hope
that
gives
you
just
a
little
picture
of
the
sorts
of
things
we're
talking
about
I
expected
over
time.
The
number
of
things
in
this
category
will
actually
grow
and
the
diversity
of
them
will
grow.
We've
already
got
some
things
that
run
in
gke
clusters.
AC
We've
got
stuff,
that's
running
in
managed
services
and
I
think
we'll
continue
to
to
figure
that
out
as
we
go,
and
so
the
sort
of
work
that
we
need
to
do
here
is
really
the
production
readiness
work,
it's
the.
How
do
we
know
this
thing's
ready?
How
do
we,
you
know?
How
do
we?
How
do
we
believe
that
it's
secure
right?
Have
we
collectively
looked
at
these
things
and
tried
to
think
adversarially
and
and
try
to
attack
our
own
systems
and
figure
out
if
we're
actually
safe?
AC
If
something
goes
down
on
a
weekend,
who's
willing
to
sign
up
to
help
right
and
while
I
will
never
sign
anybody
for
this
group
up
without
asking
I
hope
that
I
can
count
on
on
some
of
you
all
overtime
to
help
carry
this
load
I
think
it's.
What
is
the
old
saying
many
hands
make
light
work,
so
I
think
we
can
make
this
happen.
Anybody
have
questions
about
the
sort
of
stuff
that
we're
talking
about
with
this
infrastructure.
A
AC
A
AC
So
I
took
a
quick
pass
through
our
issues,
so
everybody
that
the
home
of
most
of
this
work
is
github.com
/,
kubernetes,
/
gates
do
for
historical
reasons.
That's
where
most
the
the
code
and
config
that
we're
talking
about
lives,
that's
where
our
issues
live.
So
I
took
a
quick
pass
through
all
the
issues
yesterday,
with
an
eye
towards
you
know,
updating
them,
making
sure
that
they
were
pragmatic
and
in
fact,
actually
they
don't
look
that
bad,
so
current
state
of
the
world.
AC
AC
We
have
established
the
new
registry
we
have
in
the
process.
Linus
here
to
my
left
is
working
on
a
promoter
robe
which
will
basically
what
we
want
to
do.
Is
we
have
these
staging
to
the
chat?
No,
we
do
not
have
a
private
registry,
we'll
talk
about
private
in
a
minute.
The
we
want
to
give
all
the
sub-project,
so
kubernetes
is
actually
a
collection
of
you
know
hundreds
of
sub
projects
right
and
we
want
to
give
every
sub
project
a
place
where
they
can
work
on
their
own.
AC
They
can
push
their
own
images
and
test
stuff
and
try
things
and
when
they
decide
that
you
know
of
all
their
trials,
this
one
is
the
good
one
they
can
promote
that
to
production,
but
I
don't
want
to
give
humans
individual
access
to
the
production
repository
as
we're.
Looking
at
this
with
security
I,
so
Linus
has
written
a
robot
that
will
do
the
promotion
for
us,
so
basically,
we've
got
a
get
manifest
and
I
can
give
so,
for
example,
the
cluster
API
folks
right
they
have
a
handful
of
these.
AC
What
we
call
staging
repos,
they
can
push
and
work
within
the
staging
repos
they
can
test
to
their
heart's
content
and
when
they
ready
they've
got
an
image
that
they
think
is
a
good
one.
They
file
a
pull
request
against
those
kate's
that
IO
repo
in
a
specific
place
that
says,
I
want
to
promote
from
repository
X
at
hash,
Y
and
I
want
to
move
it
to
production.
AC
I
want
to
call
it
Z
and
the
bots
will
wake
up
when
that
thing
merges,
and
it
will
actually
move
that
image
across
and
it's
cool
because
now,
like
only
four
people,
have
access
to
the
production
repository,
but
it
doesn't
have
to
be
Googlers.
So
now
we
have,
you
know:
Dimon's
has
access
to
the
production
registry.
So
if
something
goes
wrong
we
have
people
who
can
actually
fix
it,
but
for
the
most
part,
its
automated
and
so
we're
pushing
on
this
and
again
classic
80/20
problem.
AC
The
20%
of
the
solution
or
80%
of
the
solution
was
easy
and
now
we're
doing
the
security,
and
we
had
two
security
audit
internally
and
we
found
a
bunch
of
things
that
are
wrong.
So
Linus
has
been
slaving
away
on
this
more
or
less
by
himself
and
here's
a
place
where
I
feel
like
we
could
use
more
help.
More
people
review
people
to
review
it,
people
to
work
on
it.
AC
Those
sorts
of
issues
need
need
help.
So
that
was
our
first
big
thing.
It's
actually
one
of
the
biggest
things
that
cost
money
to
the
Google
account
like.
We
don't
actually
spend
it's
funny
money
internally,
but
it's
one
of
the
biggest
single
line
items
when
you
look
at
the
breakdown
and
I
think
that
that
belongs
in
community
space.
It's
actually
really
interesting
from
a
from
a
statistics
point
of
view
how
many
images
are
pushing
the
second
set
of
tasks
is
things
that
run
on
a
cluster.
AC
So
internally
we
have
a
couple
of
gke
clusters
that
we
use
to
run
utilities
things
like
GCS
web
things
like
the
case
that
IO
nginx
redirector
and
we
want
to
move
those
into
community
space.
So
we
now
have
a
cluster
which
we
call
AAA
and
that
cluster
is
ready
to
start
moving
these
workloads
in
now,
unfortunately,
to
touch
the
old
cluster,
you
have
to
be
a
Googler,
but
most
of
the
configs
are
checked
in
to
get
so.
AC
We
can
actually
move
these
things
over
to
the
new
cluster
fairly
easily,
but
80/20
moving
things
over
is
easy,
where's,
the
monitoring,
where
is
the
alerting
who's
carrying
the
pager
for
each
of
these
things?
If
GCS
web
goes
down,
it's
probably
not
a
huge
deal
but
I'd
like
to
know
about
it,
because
it
will
affect
all
of
the
test
dashboards
and
when
you
click
on
a
test
result,
it
will
take
you
to
GCS
weapon,
that's
dead.
We
have
a
problem.
AC
Another
classic
example
was
nice
like
SSL
certificate
management
right,
we
run
certain
manager
and
thanks
to
James
who
I
saw
in
the
list
here
somewhere
for
shoulder
surfing
with
me
yesterday.
To
help
me
update
it
right,
like
I,
don't
have
the
content
somehow
to
do
that
so
getting
community
people
to
help
with
these
things
is.
P
If
the
sounds
really
exciting
and
I
think
we
were
all
wanting
to
dive
in
and
help
I'd
love
to
hear
your
thoughts
and
Linus's
thoughts
on
how
we
can
harness
the
power
of
all
seventy
six
of
us
and
work
in
parallel,
so
that
we
maximize
our
effort
into
us.
You
said
many
hats
make
like
pork,
I'm
thinking,
because
you're
saying
that
this
there's
two
themes,
there's
one
I
move
things
into
an
account
that
can
be
shared
with
everyone.
Another
one
that
you
mentioned
is
go
through
the
security
review
and
complete
action
item
through
the
security.
P
Are
you
I'm
thinking?
We
can
create
different
streams
to
fork
and
plan
and
then
distribute
the
work
and
perhaps
track
that
over
github
with
labels,
so
that
we
don't
step
on
each
other's
toes
totally
note
for
the
migration
I
was
hoping
we
can.
We
can
get
a
plan
for
the
migration
and
for
the
security
I
was
thinking.
P
A
What
do
you
mind?
This
idea
sounds
great,
but
let's
move
like
ideas
about
how
to
solve
some
of
the
problems
to
our
like
a
be
weekly
meetings
and
because
we
all
are
also
thinking
about
how
to
properly
split
the
work
and
how
to
actually
give
the
people
information
about
the
state
of
everything
and
about
gets
the
highest
amount
of
feedback
and
help
from
people.
So
let's
do
have
team
something
else
to
say
about
this
topic
or
I.
AC
I'm
sure
Justin,
I,
don't
of
Justin's
here-
is
to
me
too
many
boxes
on
the
screen,
but
Justin
I
volunteer
to
do
the
same
thing
with
respect
to
some
of
the
billing
work
and
there's
others
right.
There's
things
that
we
haven't
even
opened
the
door
to
yet
because
we
don't
have
enough
people
to
work
on
and
we
wanted
to
focus
so
once
we
have
more
bandwidth
available,
we
can
actually
start
exploring
other
things
in
parallel.
So.
A
Exactly
like
Tim
said
the
ID,
there
is
like
an
idea
which
we
will.
It
would
be
evolving
during
the
next
like
a
few
very
close
weeks,
and
the
good
place
is
to
have
to
be
actually
on
our
slack
channel
and
in
our
group.
So
if
you
are
not
there,
yet
it's
really
good
time
to
do
so,
because
we
are
exactly
in
the
process
of
figuring
out
how
to
do
it
best.
A
So,
let's
hear
a
little
bit
about,
because
I
asked
some
of
you
to
prepare
me
some
short
videos
and
we
will
use
probably
in
the
future
this.
So
let's
hear
us
all
hi
everyone.
My
name
is
Bart
and
I'm.
Open-Source
engineer
on
VMware,
as
you
can
see,
I
am
the
host
of
our
today's
important
session.
I
would
love
to
suggest
you
to
not
hesitate
about
asking
questions
and
giving
us
suggestions.
A
AE
AF
Hello:
everyone,
my
name,
is
Christophe
liquor
and
I'm,
an
SRE
with
Red,
Hat
and
I've
been
involved
with
kubernetes
project
for
about
four
years
now:
I'm,
a
technical
lead
for
cig
contributor
experience,
I'm
a
member
of
the
crew
brandy
steering
committee
and
I've
been
around
this
infrastructure
working
group
since
its
inception,
I'm
involved
with
pretty
much
everything
we
do,
but
in
particular
cluster
management,
DNS
and
anything
get
up
related.
Thank
you
all
for
showing
interest
and
I
hope
to
meet
all
of
you
soon.
AB
AB
AG
Those
things
as
well
thank
you,
hello
and
welcome
to
The
Imaginarium
in
New,
Zealand,
I'm,
Tippi
hacker,
and
this
is
my
little
finger.
What's
your
favorite
thing
about
America,
robots
and
drones,
we
do
a
lot
of
robots
and
drones
and
we
have
a
forest
of
plenty
with
lots
of
trees
and
and
a
cool
set
of
food
to
be
great
here,
but
we
also
work
on
the
definition
of
what
kubernetes
is
and
we
love
pairing
with
others
rather
than
by
ourselves.
AG
AH
Hey
I'm
James
Donnelly
I'm,
based
out
of
the
UK
I
work
on
the
Salinger
project
day
today
and
I
help
to
maintain
a
certain
mansion
deployment
in
the
communities.
Repository
I
work
with
instigate,
guide
machinery,
some
testing
and
help,
and
pro
so
I
can
help
out
with
any
automation
and
control.
The
related
questions,
hey.
M
Everyone
I'm
from
India
I,
walk
on
the
publishing
boards,
that
is
about
as
responsible
for
copying
code
from
the
staging
Reapers
API
machinery.
Api
client
go
in
the
main
urban
areas,
people
to
their
own
individual
publisher.
Does
this
by
working
with
capes
in
France,
so
I
maintain
that
with
reviewing
the
ARS
for
setting
up
GC
our
station
vehicles
and
DNS
domains,
hi.
AE
I'm,
a
software
engineer
in
VMware
is
open
source
technology
center
and
I
work
on
kubernetes
and
one
of
the
co-chairs
of
signaling
store,
we're
working
to
modernize,
streamline
and
improve
quality
on
the
kubernetes
release.
Population
I'm
also
one
of
the
co-organizers
in
the
working
group
LTS
over
exploring
the
details
of
how
the
community
was.
We
support
those
releases
for
our
communities
project
end
users
and
I'm
active
in
state
contributed
experience
because,
and
my
type
was
still
working
in
open
source
software.
AE
AI
Everyone
I'm
like
a
grocer
from
a
collapse
which
is
an
open
source
research
lab
and
we
try
to
help
communities
and
currently
help,
or
at
least
try
to
help
I
in
the
working
group.
So
we're
cooling
in
the
process
and
Bart
as
he
basically
jumped
in
to
help
I
invited
everybody
and
like
get
more
people
introduced
it's
a
process.
So
from
my
own
experience,
I
can
only
say:
ask
the
questions
you
feel
like
one.
AI
A
AJ
So
my
name
is
Linus
Carver,
hello,
everybody
I've
been
working
basically
on
the
image
promotion
like
process,
but
whatever
you
want
to
call
it
for
the
past.
I
can't
remember
when
it's
been
quite
a
while,
but
hopefully
I
can
offload
some
of
that
work
in
the
near
future.
So
I
look
forward
to
that.
Yeah.
A
Thank
you
so
they're,
also,
very
of
course,
you
so
team
who
have
to
leave
us,
but
very
often,
there's
also
like
a
from
CN
CF
and
Justin
and
Erin
from
both
of
them
from
Google
and
with
that.
Let's
end
this
introduction
session
and
this
interaction
part
of
our
onboarding
and
I'm,
giving
the
voice
for
Dame's,
who
will
like
briefly
introduce
the
kubernetes
as
a
project
and
what
you
need
to
do
to
start
actually
contributing
Mike
is
your
steams.
AB
A
AB
Good,
thank
you.
So
can
you
all
see
my
screen?
Okay,
okay,
so
a
quick
tour
of
the
community
just
to
get
people
started.
I
know.
There's
people
who
have
worked
on
several
curators
ers
and
issues
and
stuff
like
that
here
as
well,
but
I
just
want
to
make
sure
that
everybody
gets
to
the
same
point:
we'll
go
through
some
of
the
some
of
the
things
quick
quickly.
Here's
a
cat,
we
love
using.
AB
AB
So,
overall,
community
organization,
we
do
have
a
code
of
conduct
that
part
mentioned.
When
we
got
started.
We
basically
would
be
the
Cuban
artists.
Project
itself
is
run
by
the
steering
committee.
The
steering
committee
essentially
delegates
most
of
the
responsibilities
to
various
SIG's.
The
SIG's
are
special
interest
groups
and
they
have
working
groups
and
committees
for
doing
different
things.
AB
So,
if
you
don't
know
who
to
talk
about
some
piece
of
code,
then
you
in
that
directory
go
look
at
the
owners
file
and
if
there
is
no
owners
file
go
to
the
directory
parent
directory
and
you
know,
go
up
the
chain
and
you'll
find
the
owners
directory
and
you
will
have
a
list
of
people.
You
will
have
a
list
of
reviewers
and
approvers.
So
those
are
the
people
who
are
responsible.
So
this
is
this
works
in
a
few
ways.
AB
We
look
at
the
owners
files
to
assign
issues
and
pr's
to
review,
and
things
like
that.
So
that's
what
we
use
it
for
topic
area
organization,
so
I
already
pasted
a
link
in
the
chat,
but
here
here
it
is
as
well.
We
do
have
slack.
We
have
the
Google
Groups,
we
have
zoom
meetings,
we
have
a
YouTube
playlist.
If
you
want
to
go
look
at
the
discussions
that
happened
before
we
do
have
the
code
issues
and
peers.
We
have
some,
you
know,
queries
that
we
can
use
and
labels
that
we
use
on
the
PR.
AB
AB
So
if
you
have
a
question,
just
use
the
Google
group
or
slack
and
don't
expect
an
answer
immediately,
even
on
slack,
you
know,
because
there
might
be
people
doing
other
things
so
always
formulate
a
full
question
and
leave
the
question
instead
of
saying,
can
I
ask
about
something,
just
ask
what
you
need
to
ask
and
some
some
ones
will
hopefully
respond
back.
You
know
when
the
time
is
convenient.
AB
We
do
have
zoo
meetings.
Please
come
join
us
look
at
the
YouTube
and
there
are
issues.
So
we
do
have
a
Google
Doc,
which
has
meeting
notes
from
every
meeting,
so
that
might
be
e,
so
the
Google
Doc
might
be
easier
to
quickly
go
over
and
if
you
need
access
to
the
Google
Doc
then
join
the
Google
Group,
so
you'll
have
access
to
the
doc.
AB
AB
So
the
most
important
thing
on
the
PRS
is
make
sure
you
sign
the
CLA.
Otherwise
the
bot
is
going
to
complain
that
you
don't
have
a
CLA
and
is
if
you
are
new
here.
One
of
us
has
to
do
an
okay
to
test
combat
command
so
that
the
label
goes
away
and
the
test
run.
And,
of
course,
if
you
have
any
trouble
with
the
PRS
and
things
like
that,
just
bring
on
slack
and
you
will
get
an
answer.
We
do
have
lots
of
repositories
across
the
org.
AB
You
know
the
main
one
we
work
off
is
the
kids
dot
IO
and
we
use
prowl.
We
don't
have
to
deal
with
proud
too
much
right
now,
but
then
there'll
be
a
time
when
we
will
need
people
who
can
stand
up
an
instance
of
prowl
and
try
to
do
other
things
related
to
prowl
very
very
soon.
So
if
you
like,
if
you
like-
that
kind
of
automation
stuff,
you
know,
learning
prowl
will
be
a
really
good
place
to
start
so
continuous
integration.
AB
AB
So
there's
a
mixture
of
different
kinds
of
tests
and
we
do
have
some
amount
of
tests
for
the
kids
that
are
you,
but
what
we
eventually
have
to
do
is
make
sure
that
we
run
all
these
continuous
integration
tools
in
the
triple
a
cluster
that
Tim
mentioned.
So
if
you're
interested
in
you
know,
the
testing
infrastructure
and
stuff
like
that,
you
know
tested
is
a
good
place
to
start.
How
do
you
run
tests
played
on
your
own
that
kind
of
stuff?
Okay,
so
group
learning
suggestions,
oops
yeah.
AB
So
what
what
we
are
thinking
here
is.
We
will
divide
us
ourselves
up
into
smaller
chunks,
hopefully
so,
like
dimension,
there's
a
lot
of
knowledge
that
is
not
yet
written
down,
so
we
could
start
by
writing
down
stuff.
You
know,
ask
any
questions.
You
know
that
you
can
think
of
and
try
to
leave
a
note
for
the
next
person
who's
going
to
come
along
and
at
the
same
time
we
should
come
up
with.
You
know
things
that
we
can
achieve
and
divide
that
up
into
issues
and
you
know
start
giving
up
the
work
that
way.
AB
So,
yes,
we
do
have
a
stand
up
meeting
for
different
topic
areas.
So
if
you
go
through
the
Google
Doc,
you
will
get
an
idea
of
what
are
the
different
aspects
that
we
are
talking
about
on
a
weekly
basis.
So
so
you
will
be
able
to
figure
out
help
figure
out.
What
are
the
areas
that
you
will
be
interested
in
it's?
It
would
be
important
to
know
that,
so
we
can
pair
you
up
with
the
right,
the
right
mentor
and
you
will
have
a
small
group.
AB
A
AB
We
have
a
contributor
guide,
developer
guide.
These
are
all
things
that
you
need
if
you
want
to
go
beyond
our
little
working
group
and
work
on
the
main
KK
project
and
things
like
that,
but
eventually
we
we
are
serving
the
needs
of
the
lots
of
people
who
contribute
to
Cuban
artists
on
a
you
know
ongoing
basis
and
we
are
trying
to
make
their
life
simpler
and
easier.
AB
A
You
James
for
a
nice
presentation
and
the
next
topic
was
to
where
to
find
out
like
help
and
information
and
actually
I
can
skip
it,
because
beans
already
told
that
the
best
place
is
to
use
our
select
channel
and
also
our
Google
group,
as
Dean
said.
Don't
worry
if
people
are
not
responding
immediately,
because
very
many
people
from
our
group
is
like
a
lot
on
their
plates,
so
be
patient
and
sometimes
don't
worry
about
just
poking
sometime.
A
M
Everyone
I
just
wanted
to
add
a
few
quick
words
about
some
general
tips
that
you
can
keep
in
mind
so
that
you
have
a
smooth
contribution
process,
especially
since
kubernetes
is
such
a
huge
project.
So,
firstly,
this
might
sound
cliched,
but
please
feel
free
to
ask
questions.
I
know
this
has
been
said
before,
but
there
are
no
stupid
questions
and
we're
not
going
to
charge
you
at
all.
M
If
you
can
keeping
track
of
what
goes
on
in
the
mailing
list
and
the
KH
dot,
IO
repo
and
get
health,
you
don't
have
to
spend
too
many
hours
on
it,
just
subscribe
to
the
mailing
list
or
check
out
the
repo
in
between,
so
that
we
see
you
and
know
that
you
are
interested
in
this
and
that
you'd
like
to
stay
involved
with
the
community
and
overtime
that
it's
safe
to
give
you
access
to
manage
certain
projects.
This
is
also
a
very
good
way
to
understand.
M
Who
is
who,
in
this
working
group,
you
also
saw
the
video
and
what
they
are
working
on
and
also
places
that
you'd
like
to
work
on
as
well.
Now,
let's
say
that
you've
decided
what
you
want
to
work
on,
and
you
have
an
idea
that
you'd
like
to
discuss
so
usually
the
process
that
it's
like
I'd
said
us
to
follow
is
that
you
start
out
on
slack
to
get
an
early
feedback
about.
It
also
doesn't
have
to
be
synchronous
at
all.
It
can
definitely
be
asynchronous.
M
M
So
they
got
a
lot
of
github
notifications
and
they
could
lose
this
issue
or
your
PR
for
that.
So
it's
always
good
to
ping
them
on
slack.
If
you
don't
get
a
response,
we
also
have
the
PR
reviews
channel
on
slacks.
If
you
don't
know
which
channel
to
post
your
PR
on
or
your
link
on,
you
can
also
do
that
and
some
we
can
find
your
additional
reviews
for
this
working
group.
You
can
just
post
the
PR
or
your
issue
link
on
the
working
groups
up
channel
yeah
I.
M
Don't
want
to
take
up
too
much
time
because
I
wanna
save
time
for
questions,
so
I
would
just
say
that
we're
very
open,
we're
very
friendly
and
we're
gonna
try
to
help
you
as
much
as
fast
as
possible.
So
yeah.
Please
ask
us
as
many
questions
as
you
can
and
if
you
see
any
places
where
we
can
improve
our
processes
or
documentation,
also
feedback
yeah.
That's
all
I've
cut
over
to
you
that
very.
A
X
Can
I
start
yeah
sure,
okay,
just
one
question
because
I
mentioned
at
the
beginning,
I
working
as
a
DevOps
consultant.
That
means
my
work
is
mostly
Fiori
de
and
hands-on.
So
my
question
is:
do
you
have
any
priorities
or
preferences
from
people
or
techs
Kia's?
For
example,
you
want
to
people
in
telephone
for
the
infrastructure
school
or
something
like
that
or
or
how?
How
it,
how
it
works
is
that
is
my
first
open
source
and
community
driven
stuff
and
I.
AB
AB
These
are
the
services
that
we
need
to
run
and
we
know
how
they're
configured
right
now
and
we
know
how
it
stood
up
right
now
and
how
it
works
right
now
we
need
to
automate
when
we
move
a
service
from
where
it
was
running
right
now
to
the
new
place
where
it
needs
to
run.
We
are
going
to
take
the
chance
to
make
sure
that
it's
automated
simple
example
would
be
like
the
publishing
part
in
technique
dimension
right,
so
it
is
currently
running
in
one
spot.
AB
Then,
when
we
run
it
in
the
community
cluster,
then
how
do
we
make
sure
who
has
access
to
the
secrets
for
the
github
account?
Who
who
can
refresh
just
the
container?
That
is
running
because
you
know
often
it
fails
and
it
falls
and
falls
apart
when
there
is
new
branches
being
cut
or
when
there's
new
code
that
is
getting
merged
in
KK,
so
who
takes
care
of
the
bottom,
a
daily
basis
who
changes
the
code?
Who
has
access
to
the
secrets?
AB
P
AB
Have
to
divide
up
the
whole
space
into
smaller
groups
right,
one
group
would
I
think
Nicholas
and
list
X.
We
are
talking
about
this
also,
so
one
is,
for
example.
This
is
the
image
promotion
process,
so
image
promotion
process
where
it,
where
is
it
current
status?
What
are
we
plan?
What
is
currently
being
planned
and
worked
on?
What
do
we
need
to
do
in
the
future
and
then
how
do
we
migrate
from
the
existing
infrastructure
to
the
new
infrastructure?
So
this
will
be
a
smaller
group
of
people.
What.
A
I
would
like
just
to
add
is
that
we
didn't
manage
to
divide
it,
yet
we
are
in
the
process
currently.
So
in
a
few
days
we
will,
and
maybe
even
tomorrow,
I
will
put
something
the
suggestions
to
split
the
work
into
a
smaller
triangle
and
then
probably
there
will
be
some
already
mentors
who
will
take
this
and
you
could
definitely
right
there
if
you
want
to
put
your
efforts
into
some
particular
space,
but
for
that
there
is
a
very
important
thing.
We
really
need
the
contact
for
you
and
so
just
a
reminder.
AB
I
P
P
The
people
on
the
call
who
want
to
help
I
guess
what
we're
saying
is.
We
are
going
to
split
the
work
into
work
areas
because
we
haven't
done
that
yet
and
we
want
to
chat
with
you
again
once
we
have
these
bodies
of
work
identified
so
that
you
can
pick
which
type
of
word
you
feel
more
affinity
towards.
So
does
that
work
very?
Very
yes!.
A
P
U
AB
P
Think
you
have
a
really
new
question.
That
is,
we
want
to
keep
a
single
and
we
will
clarify
that
during
our
next
meeting
you
mainly
use
the
Google
Groups
mechanism
to
communicate.
So
if
we
need
to
give
a
shout
out
and
tell
people
hey,
these
are
the
latest
news
right
and
we
want
to
track
our
work,
I
believe
through
github
issues,
so
that
wasn't
clearly
the
limit
their
responsibilities
and
what
you
want
to
expect
from
the
google
group
and
then
the
github
issue
right
Google
is
like.
P
Maybe
you
have
a
question,
so
you
shout
out
to
everybody
and
like
who
can
help
me
and
they
get
help
this
year
would
be
like
I'm
working
on
this,
so
that
people
know
this
is
what
you
grab.
I
would
love
for
us
to
sync
again
next
week,
ones
that
we
do
as
part
and
DIMMs
said,
and
we
have
identified
the
different
bodies
of
work
and
the
mentors,
and
now
we
can
start
making
concrete
or
I
guess
we
can
start
taking
action
right
now.
We
have
a
lot
of
work,
but
it
would
be.