►
From YouTube: Weekly Mac Shared Runners Sync - 2020/10/06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone.
So
let's
go
to
the
agenda,
I
don't
have
anything
to
report,
so
I
guess
we
can
start
with
your
point.
Two
darren.
B
C
A
C
Like
that's
a
really
complex
sort
of
platform
or
what,
however,
you
pronounce
because
I've
heard
like
10
different
pronunciations
of
that
word.
So
since
we
just
have
one
customer,
I
would
not
bother
with
it
for
now.
Just
add
it
to
the
backlog
and
every
time
someone
says.
A
Yeah
and
the
closed
beta
doesn't
seem
to
have
like
a
representative
enough
sample
of
customers,
so
probably
for
a
later
stage
would
make
more
sense
yeah.
In
terms
of
time,
I
haven't
actually
timed
it,
but
I
would
say
like
to
the
point
you
know
from
provisioning.
You
know
issuing
the
the
commands
to
being
able
to
log
in,
I
would
say,
like
30
seconds.
Currently,
that's.
B
A
Yeah
sure
I
don't
know
how
you
know
how
much
you're
familiar
with
the
arca
commands.
A
If
you
want,
we
can
stay
after
this
meeting
and
we
can
do
it
together.
Oh
that.
B
And
what
do
you,
what
steve
and
pedro,
do
you
think
I
feel
like
we
have?
I
feel
we
have
enough
for
the
closed
beta.
Do
you
guys
think
we
should
kind
of
close
the
close,
the
f?
That's
the
the
final
forms
at
this
point.
C
A
C
What
I
was
gonna
say
is:
it
depends
how
much
compute
we
have
what
we're
left.
If
we
have
the
capacity
to
handle
five
six
more
customers,
we
can
do
still,
because,
just
because
we
have
the
hardware,
so
it's
kind
of
not
sitting
around
like
as
long
as
we
reserve
some
hardware
for
our
ci
infrastructure,
because
right
now,
alas,
pedro
corrects
me,
it's
not
really
a
lot
of
maintenance.
From
our
end,
it's
kind
of
like
setting
it
up
once
I'm
kind
of
forgetting
it.
A
A
Far
people
haven't
like
come
with
problems
to
to
solve,
like
it's
mostly
done
through
brew
like
if
they
need
some
extra
software,
so
yeah
it's
hands
off
so
far,.
B
Okay,
that
makes
sense
to
me
so
what
I'll
do
is.
I
won't
make
any
changes
to
the
issue,
but
what
I'll
do
is,
as
we
get
new
requests,
if
it's
like
a
hobbyist,
I'm
not
going
to
get
them
in,
like
all
the
hobbies.
So
far
I
haven't
approved
them,
so
I'm
going
to
go
back
and
circle
back
so
I'll
I'll.
I
will
be
filtering
the
new
request
for
like
paying
gitlab
customers
that
way.
We
have
that
the
best
okay,
thanks.
B
I
have
a
next
point.
I
kind
of
moved
it
above
yours
because
steve
you
asked
about
when
do
were
still
in
this
meeting,
so
I
wanted
to
ask
about.
When
should
we
start
working
on
the
horoscope
and
knowing
that
we
have
so
many
different
things?
As
a
team
to
work
on?
B
C
That's
a
really
hard
question
to
answer.
I
would
say
that
is.
C
Like
what's
the
current
team's
priority
like
is,
for
example,
mac
os
open
beta,
more
important
than
the
umass
issue,
and
the
docker
machine
executor
supporting
container
optimized
os
and
things
like
that,
because
to
me
those
feel
more
important
than
open
beta.
But
again
this
is
up
to
you,
so
it
really
depends.
C
B
B
So
q4
is
what
also
we
get
the
dates
november
december
january.
C
B
Right
it's
november
till
january:
yes
right
it's
november
december
january,
so
anytime
in
that
time
from
theoretically
we
can
do
an
open
beta.
Now,
the
question
is:
if
we
plan
for
the
open
beta
like
say
in
the
last
month
of
q4,
which
is
january
so
which
means
that
say,
we
started
order,
scalar
work
in
january.
B
B
So
I'm
thinking,
if
we
plan
for
the
open
beta
on
the
back
end
of
q4,
so
it
gives
us
enough
capacity
to
do
the
things
you
mentioned
like
umass
container
optimized
right,
then
we
could
always
push
open
beta
at
the
back
end
of
q4,
maybe
even
if
things
don't
work
out
well
for
us
only
q1
and
then
push
ga
to
late,
q1
or
even
q2
right,
that's
kind
of
roughly
what
I'm
thinking,
because
in
me,
in
parallel,
I
know
we
haven't
had.
I
know
this
is
a
broad
discussion
for
the
wider
team.
B
C
C
Because
q4
is
quite
hard
right,
like
december,
is
kind
of
in
a
weird
mood
and
even
january
and
even
november,
for
divas
with
thanksgiving
and
all
that
so,
like
all
three
kind
of
bulbs
are
kind
of
jacked
up
right.
So
if
we
wanted
for
key
for
that,
probably
that
is
something
that
we
have
to
start
nowadays.
C
Like
the
pedal
to
the
metal
kind
of
thing,
but
like
having
some
reviews
of
these
being
done
on
it,
because
we
also
need
like
for
open
beta,
we
want
the
infrastructure
team
to
handle
the
deployment,
the
all
the
work
they
need
to
do
right
right.
C
So
maybe,
if
we're
gonna
plan
for
q4,
maybe
during
an
action
point
for
you-
is
to
reinvolve
the
infrastructure
team
and
see
if
they
have
capacity
for
this
in
q4.
Just
because
we
will
we
are
going
to
rely
on
them
to
deploy
the
runner
managers
on
the
kubernetes
cluster
and
so
on
and
so
forth
right.
C
So
we
we
would
need
their
help
to
handle
all
that
stuff.
Unless
we
want
to
do
it
like
I'm
more
hap,
more
than
happy
to
do
it
ourselves,
but
yeah,
okay,.
B
But
then,
to
your
point
and
then
to
your,
I
will
do
that
and
then
to
your
question:
if
we
were
just
kind
of
trying
to
be
very,
very
focused
in
terms
of
our
prioritization
right,
I
agree
with
you
what
I,
what
you
just
what
you
said
earlier
in
terms
of
priorities,
is
what
I
sent
to
elliot
so,
for
example,
the
allow
user
heavy
chart
change.
B
Then
umass,
the
container
optimize
thing,
those
three
things
have
to
get
done
and
there's
one
or
two
new
escalations
in
terms
of
bugs,
and
then
we
still
have
sticky
runners
and
variable
inside
that
available.
Yeah.
A
B
B
C
Yeah,
I
I
mean
it's
just
like
an
idea
like,
since
we
don't
really
have
a
lot
of
updates
recently,
but
yeah
I'm
more
than
happy
to
people.
If
we
want.
B
C
Awesome
so
just
to
make
sure
I'm
clear
regarding
the
autoscaler
work:
are
we
gonna
start
working
on
it
soon,
or
is
it
something
that
we're
gonna
respond
for
now
or
like?
How
are
we
gonna
do.
B
Okay,
so
I
wanna
leave
it
up
I'll
discuss
with
elliot,
make
sure
he's
on
the
same
page.
I
want
to
leave
up
to
you,
but
but
if
it
comes
down
to
like,
for
example,
I
know
you
steve
you're
doing
the
the
requirements
gathering
on
next-gen,
honest
gaming
right
so
you're
going
to
be
becoming
busy
with
that
here.
Let
me
just
present
I'll
just
drop
it
in
the
in
the
thing.
B
Okay,
sorry,
just
kind
of
copy,
let's
face
it
from
from
visual
studio.
So
this
is
what
I
was
pinging
elliott
last
week,
thursday
just
brainstorming
like
keeping
things
simple
right.
So
initially
I
was
thinking
fifteen
that
sticks
with
knockout
umass,
I'm
not
sure
if
that's
still
true,
so
I
was
actually
thinking
about
flipping
a
lot
of
user
in
the
13.6,
because
elliot
was
thinking
that
they
potentially
do
that.
First
right.
B
Right,
so
here's
how
I
was
so
kind
of
thinking
through
his
crying
like
396,
a
lot
of
users
like
the
big
thing
that
we
haven't
done
flipping
that
seven
new
math.
So
I
don't
know,
I
don't
want
to
speak
for
you
for
the
engineering
team,
knowing
that
we
might
want
to
try
to
wrap
up
new
masks
by
397.
Does
that
mean
someone
has
to
start
like
hacking
on
it
now
right
that
actually
happened.
C
B
I
am
forecasting
that
we're
not
trying
to
deliver
any
major
new
features
right
so
basically
giving
us
flexibility
in
38
and
39
like
hey,
we
might
have
a
customer
escalation
which
we
already
have
on
a
couple
of
bugs
right,
yeah.
The
other
thing
you
mentioned,
I
forget
which
one
the
beginning
of
the
coins,
that's
what
I
was
thinking
now
14-0.
I
got
a
little
bit
aggressive
on
thursday
right
where
I
said.
A
B
I
don't
think
we
can
deliver
sticky
runner
by
14.,
it's
probably
more
like
a
14,
so
that's
kind
of
what
I
was
kind
of
thinking,
and
so
this
is
kind
of
what
I'm
sharing
earlier
in
terms
of
him,
trying
to
understand
how
to
sequence
things
in
so
to
your
point,
it
really
depends
on
okay,
some
the
person
that's
doing,
allow
user
do
they
have
capacity
to
start
looking
autoscaler
and
should
they,
but
I
was
trying
to
be
very
how
should
I
say
it:
pest
not
pessimistic,
conservative
and
forecasting
what
we
deliver
in
terms
of
new
features
to
give
us.
A
B
B
C
To
happen
to
make
windows,
ga
it's
the
graceful
termination.
B
C
And
I
know
another
big
customer
just
asked
for
it
again
as
well
yeah.
So
let's
see
what
the
windows,
ga
epic
series.
C
Graceful
shutdown
and
the
windows
updates.
What
is
the
updates?
That's
right,
yeah,
because
so
right
now,
that
is
something
that
is
done
manually.
We
just
need
to
create
some
kind
of
scripts
to
automatically
update
windows,
so
yeah,
I'm
not
sure
it
doesn't
seem
to
be
here,
but
we
don't
want
a
set
of
idle
machines
on
windows
for
the
ga
to
consider
it.
Ga.
C
B
I
mean
I
can't
recall
the
conversation
on
that
one
to
maybe
dust
that
off
a
bit
all
right,
so
anyway,
let's
wrap
up
the
fourth
day.
This
was
my
initial
brainstorm.
I'm
going
to
review
this
with
elliott,
you
know
101
tomorrow,
and
then
I
was
going
to
suggest
him
that
maybe
in
our
monday
team
meeting
we
can
review
this
and
get
everybody
to
kind
of
like
be
on
the
same
page.
B
But
hey
does
this
make
sense,
and
then
we
need
to
adjust
stuff
and
again
I
was
trying
to
brainstorming
this
in
a
way
to
give
us
flexibility
to
handle,
which
I
know
happened,
the
escalations
on
certain
belts.
So
we
have
so
many
bugs
with
customer
labels
already
on
them.
That's
all
bugs.
You
know
we're
going
to
get
escalations
on
those.
C
Yeah
as
well,
and
it
would
be
nice
to
kind
of
finish
off
the
kubernetes
attach
execution
yeah
as
well.
I
know
georgie
has
been
kind
of
working
on
it
from
on
the
side,
not
on
the
side
like
from
time
to
time
when
he
has
time
but
like
it
would
be
nice
to
kind
of
call
it
a
project
done
yeah
and
that's
nice,
because
that
would
help
adoption
on
the
kubernetes
executor
as.
B
C
B
Know
if
yeah,
if
you're
asking
me
right
now,
if
what
the
business
will
say
well,
I
guess
openshift
would
have
to
go
first,
because
the
sales
reps
are
saying:
they've
got
over
60
million
and
opportunities
attached
to
the
openshift
stuff.
So
I'm
gonna
go
with
that.
C
Yeah
yeah
so
yeah
for
us
just
give
us
a
great
light
and
we'll
go
ahead
with
the
auto
scanner.
But
we
will
have
to
look
at
what
the
other
things
are
and.