►
From YouTube: Foundational Infrastructure Working Group [Nov 18, 2021]
Description
Recording from the Cloud Foundry Foundational Infrastructure Working Group call held on 18th November 2021.
Attendees:
‣ Ruben Koster
‣ Beyhan Veli
‣ Benjamin Gandon
‣ Ram Iyengar
Agenda Items:
• [Beyhan] Seems to be stuck and the bot will close it. Let’s discuss how to proceed with issues in this state https://github.com/cloudfoundry/bosh/issues/2331
• How to deal with issues:
\_Inbox - 7 days to ping tech leads
\_Discussion - 14 days to close
\_Prioritized (someone should be assigned to the issue at this point) - after 14 days bot should start pining the assigned person?
\_Open for Contribution - 30 days to close
\_Closed
• Change default branch of bosh-linux-stemcell-builder to bonic/master
A
A
B
A
A
They
could
use
job-specific
properties
right.
The
problem
is
that
bosch
uses
global
properties.
Is
there
something
with
a
proxy
an
ops
file
yeah?
So
I
think
they
are
using
just
pro
file
right
this,
and
this
sets
it
globally,
so
if
they
would
set
it
instead
for
the
jobs
they
want
to
use
a
proxy
for,
then
they
don't
have
this
issue.
A
A
Here
it's
just
they
all
all
the
jobs
use
the
same
properties,
they
are
not
scoped
and
because
they
are
set
using
this
globally
right,
not
sculpt
under
a
job
they
are
picked
up,
but
if
you
would
set
them
under
a
job
so
under
job
name
only
for
the
director.
So
if
you
only
want
to
use
it
for
the
director
right,
you
would
only
set
it
for
the
director
and
not
have
it
configured
for
the
help.
Monitor-
and
you
wouldn't
have
this
problem,
but
I
can
respond
to
that.
I
thought.
A
B
But
I
wanted
to,
in
general
to
discuss
issues
for
ps.
I
would
like
to
that.
We
close
that
issues
appears
by
having
a
decision
whether
we
would
like
to
get
contribution
for
that.
We
don't
think
that
is
something
good
to
do
with
bosch,
just
letting
the
bot
causing
the
them
is
not
so
polite
for
the
people
who
actually
wanted
something.
A
A
B
A
A
A
Yeah
like
like,
we
have
with
pull
request.
I
think
that
would
be
ideal.
Currently
I
don't
have
issues
in
here
yet
and
I'm
still
figuring
out
technically
how
we're
gonna
I
mean
creating
the
issues
is
not
a
problem,
but
you
only
have
like
one
status
field
and
I
think
we
want
different
statuses,
for
we
have
different
states
or
something
for
for
an
issue.
A
A
A
So
we
have
inbox
yes,
and
how
do
we
wanna?
Do
we
want
to
assign
an
issue
to
someone
I
mean?
That's
also
the
question
right
because
so
we
haven't,
we
have
agreed,
I
think,
as
a
working
group,
that
the
people
in
the
working
group
are
to
commit
their
time
to
review,
to
review,
pool
requests.
But
triaging
issues
I
don't
know
like-
is
that
something
we
want
to
divide
between
the
people
that
are
like
is
that
something
people
have
signed
up
for.
A
A
An
issue
can
also
be
like
more
of
a
help
thing
right,
so
you're,
basically
helping
the
community,
which
is
nice,
but
it's
also
a
big
investment
in
time
and
there's
like
for
the
company
that
is
paying
the
person
doing
that
work.
There's,
maybe
not
it's
it's
less
clear.
What
the
result
is
or
something
does
that
make
sense,
yeah.
B
B
A
Yeah,
but
I'm
like
there's
still
a
lot
of
back
and
forth
right,
there's
still
like
a
lot
of
discussion,
sometimes
right,
because
it's
not
clear
what
the
issue
is
or
that's
missing
information
right.
So
it's
basically
debugging
well
with
a
pull
request.
People
have
done
the
debugging
and
it's
like
codes
right.
You
can
easily
it's
less
vague
or
more
concrete
or
something
issues
can
be
really
broad.
A
So
so
one
idea
I
had
initially
was
to
just
make
sure
that
we
forward
all
the
issues
into
the
proper
slack
channels
right
because
there's
a
bigger
audience
in
there
and
then
people
can
respond
if
they
want
to.
But
then,
if
we,
if
we
go
the
route
of
like
having
it
on
a
ganban
style
board
like
in
a
project
right,
then
it
feels
more
like
we
have
to
do
something
with
all
these
things
and
that's
nice
for
the
community,
but
there's
also
quite
a
big
cause.
A
D
D
C
D
A
So
that
that's
a
bit
of
the
thing
I'm
scared
for
like
this
could
be
like.
We
have
lots
of
repos,
but
I
I'm
also
not
sure
how
many
issues
we're
talking
about
like
so,
but
that's
why
I
like
the
boss
right,
because
the
bot
at
least
I
want
some
sort
of
exits
like
in
each
stage.
We
need
a
natural,
a
bot
that
just
ends
the
the
thing
without
a
person
paying
attention,
because
I
mean
that's
just
a
cost
thing.
I
guess
it's
like.
A
Otherwise
we
have
a
lot
of
overhead
of
having
to,
but
I
I
agree
that
it's
good
to
have
at
least
initially
a
person
look
at
it
right,
give
an
initial
response,
because
that's
welcoming
right
for
the
community
from
a
community
point
of
view,
so
we
can
try,
try
to
at
least
get
one
response
on
each
issue.
I
think
that's
a
good
like
goal
to
start
with
and
then
and
then
we
can't
move
things
in
like
open
for
contribution
so
inbox,
then
we
do
like
an
initial
response
and
then
who's
gonna.
A
Do
the
initial
response.
That's
that's
the
question
is
that
something
we
share,
so
we
assign
it
to
to
a
person
in
the
in
the
working
group
and
that
person
is
then
responsible
for
doing
in
a
response
or
it's
gonna
be
me
or
like.
Do
we
share
it
between
the
tech
leads,
I
mean
that's
also
an
option
that
they
and
I
just
try
to
keep
creep
up
with
those
I
mean
benjamin
you
as
a
a
reviewer.
Would
you
be?
Would
you
like
to
also
play
a
part
in.
D
The
well
actually
I
I'm
I'm
looking
at
those,
and
I
can
testify
for
that-
one
specifically
I've
seen
it
and-
and
I
haven't
understood
at
first
glance
what
was
important
about
it.
I
saw
someone
jumping
in
and
answering
so
I
said
right,
let's
move
on
to
and
focus
to
something
else
someone
is
is
already
taking
care
of
that
I
mean
I
I
everyone
cannot
count
on
me
alone
and
I
need
to
count
on
other
people
investing
their
time
either.
So
yeah,
that's
how
we
share
the
load.
A
D
A
D
We
sorry
yeah,
I
also
mean
we
don't
commit
into
implementing
every
idea
that
comes
around
when
people
have
their
id.
They
must
also
do
advocacy
about
about
those.
If
someone
comes
to
me
and
explains
the
the
importance
of
the
the
id
and
I
I
jump
into
it
and
say
yeah,
it's
a
great
thing,
maybe
I
I
I
I
gave
some
time
because
I
I'm
convinced
it's
it's
a
good
thing
for
perch
and
that's
that's
also.
Maybe
how
people
have
maybe
to
push
ideas
forward.
A
That
makes
sense,
so
what
I
was
thinking
is
like
we
could
have
like
a
list
of
the
issues
and
we
did.
We
have
something
with
like
a
last
a
column
with
last
activity
or
and
something
like,
maybe
a
number
of
comments.
So
it's
like
we
see
like
people,
can
just
like,
go
to
one
place
and
have
a
list
of
all
the
issues
in
our
working
group
and
then
just
go
over
them
and
comment
on
them,
and
then
we
can,
during
this
meeting
just
see.
Oh
go
briefly
over
that
list
and
see.
A
Oh
these
things
have
been
open
for
a
while
and
that
nobody
has
responded
to
them
right
and
we
can
do
it
that
way,
because
we
have
this
meeting
every
week.
So
we
could
make
that
like
a
thing
we
just
do
in
this
meeting,
so
we
we
let
it
happen.
Naturally,
people
comment
on
things
naturally,
and
we
just
make
sure
that
if
nobody
has
commented
in
a
week
or
something,
then
we
can
take
action.
B
D
It's
really
also
prioritizing
based
on
the
importance
I
I
for
this
specifically
about
no
proxy
thing
I
need.
I
would
need
someone
to
explain
me
why
it's
important
to
do
that,
and
I'm
also
asking
the
question
here
well.
Why
is
that
important,
possibly
in
these
proxy
settings,
getting
ignored
by
s
monitor
why.
D
A
E
D
A
A
A
A
So
some
company
has
decided
so
we
can
say,
like
we
assign
it
to
you
beyond.
If
it's
an
sap
thing
and
we
assign
it
to
me
if,
like
at
least
that
person
can
be
contacted
and
knows
and
can
check
in
the
other
backlog
of
the
company's
specific
backlog,
where
that
issue
is
right,
I
think
we
should
have
a
point
of
contact.
A
A
Yeah,
I
think
that
so
this
is
mostly
probably
a
bot,
so
I
will
put
this
into
the
proposal
we
have
for
the
bot
as
well.
You
know
at
the
foundation
or
at
the
toc
level,
but
we
can
start
with
this
ourselves
and
but
I
think
it
would
also
be
nice
to
to
have
like
a
an
overview
right
of
these
things
in
these
states.
A
A
A
A
A
D
A
A
A
We
have
had
a
few
pr's
the
last
few
days
as
we're
against
the
master
bench
which
didn't
make
sense,
and
I
mean,
like
I
think,
even
a
few
pr's
wouldn't
have
been
there,
because
people
would
just
start
building
bionic
and
everything
would
work
instead
of
having
to
try
to
build
master.
Also,
I
find
it
interesting
that
the
person
submitting
a
few
of
those
brs
was
actually
from
canonical.