►
Description
Meeting notes https://docs.google.com/document/d/1ushaVqAKYnZ2VN_aa3GyKlS4kEd6bSug13xaXOakAQI/edit
A
All
right
welcome.
Everyone
today
is
Wednesday
the
15th
of
February
2023,
and
this
is
the
cluster
API
project.
Meeting
cluster
API
is
a
sub-project
of
kubernetes
sigs
and,
as
such,
we
adhere
to
their
Community
guidelines,
which
essentially
means
for
this
meeting.
Please
raise
your
hand
if
you'd
like
to
talk
and
I
will
call
on
you
and
please
be
kind
to
each
other.
A
So,
at
the
beginning
of
every
meeting
we
like
to
take
some
time
to
welcome
new
attendees
to
the
community
or
to
the
meeting.
So
I
will
be
quiet
for
30
seconds
here
and
if
anyone
would
like
to
unmute
and
say
hello
or
raise
your
hand,
please
do.
A
All
right,
I
am
not
seeing
anyone
unmuting
so
I'm
guessing.
No
one
is
interested
in
saying
hello
right
now,
so
please
don't
forget
to
add
yourself
to
the
attending
list
and
yeah,
let's
get
into
our
agenda.
So
we
start
after
that.
With
the
open
proposal.
Readouts
I,
don't
know
if
we
have
any,
though
so,
yeah
there's
nothing
open,
I,
don't
know.
If
there's
anyone
who
wants
to
speak
on
any
of
the
stale
proposals,
I'm
guessing
not
but
I'll,
give
a
second
in
case
someone
is
here.
A
All
right,
I'm
not
seeing
any
hands,
go
up.
So,
let's
move
on
to
the
discussion
topics,
so
Fabrizio
you're
up
first
with
a
PR
to
add
support
for
kcp
remediation.
B
So
we
already
talked
about
this
a
couple
of
times
in
the
hour
when
there
was
The
Proposal
Amendment
Etc.
So
this
is
a
work
that
basically
make
an
amendment
to
how
we
do
kcp
Remediation
in
kcp
and,
more
specifically
intervala
law
kcp,
to
do
a
remediation
on
on
why
you
are
provisioning
your
cluster.
So
if
the
first
machine
fails
it
will,
it
will
throw
it
away
either
create
a
new
one.
B
If
the
second
machine
fails-
and
you
have
a
control
pane
of
three-
you
will
try
to
remediate
the
second
machine
and
so
on
and
when
you
are
up
to
three
machine,
which
is
your
site,
then
kcp
remediation
workers
us
today.
So
what
we
are
doing
is
that
we
are
adding
on
a
new
feature:
I
stand
in
the
capability
of
our
kcp
remedies,
so
the
pr
is
out.
We
had
a
a
bunch
of
review
I.
B
Thank
you
all
everyone
for
the
feedback,
especially
Stefan,
that
really
helped
to
to
bring
this
PR
near
the
finish
line,
and
what
what
I
really
would
like
to
focus
is
that
okay,
this
PR
the
code
is
not
difficult
to
read.
If
you
want
to
look
at
it,
but
what
is
super
interesting?
My
opinion
is
that
for
this
PR
we
basically
add
that
and
and
the
totally
revamped
how
we
are
doing
end-to-end
test
for
kcp
remediation.
B
Now
we
have
really
a
good
coverage,
and
so,
given
that
the
there
is
an
extensive
this
kcp,
we
know
it
is
dedicated,
but
this
is
the
control
plane,
but
we
have
an
extensive
unit
test
of
stuff
and
one
of
the
most
complex
and
and
fun
to
write
end-to-end
test
that
we
have
in
cluster
API,
so
yeah
I'm,
proposing
first
of
all,
I'm
asking
folks.
If
you
have
time,
please
take
a
look.
B
Second,
if
there
are
no
objection,
I
will
set
the
laser
consensus
for
merging
this
PR,
which
is
out
from
some
time
now,
and
so
we
can
have
as
much
as
possible
test
cycle
out
in
the
wild.
A
That
is
very
cool
to
hear
about
the
expanded
coverage
and
you've
got
me
extremely
curious
about
the
the
nature
of
the
end-to-end
testing.
There
I
think
you
sold
it
pretty
well.
Does
anybody
have
questions
or
comments
about
this
topic.
A
All
right,
I'm
not
seeing
any
hands,
go
up.
Thank
you,
Fabrizio
and
please
everyone
go
take
a
look
at
that
PR,
so
Stefan
you're
up
next
with
removing
the
V1
Alpha
3
and
V1
Alpha
4
API
versions.
Please
take
it
away.
Yep.
C
So
both
our
essential
topics
that
I
brought
up
like
two
weeks
ago
so
yeah,
but
let's
take
a
look
at
one
after
another,
so
that
is
just
about
that.
We
essentially
want
to
remove
the
v15
for
API
version,
API
types
and
all
that
kind
of
stuff.
C
We
had
a
few
discussions
and
we
also
sent
it
all
the
mailing
list.
Tweaks
I
mean
over
the
last
two
weeks
and
the
plan
would
be
what
you
can
see
here
now.
Essentially
with
104,
we
just
saw
an
announcement
with
1.5.
C
We
stopped
serving
v19
for
free,
nothing,
changes
for
view,
another
form
so
essentially
that
we
can
just
test
it
out
with
one
API
version,
then
with
v1.6
we
would
drop
v19
for
free
and
we
would
stop
serving
your
I4
and
before
not
seven
with
eventually
drop
you're
gonna
have
a
400
on
it
felt
on
the
issue
that
we
basically
have
consensus.
What
I
did
is
I
opened
a
PR
to
basically
formalize
this
plan
by
documenting
it
in
contributing
and
being
so
in
contributing
MD.
C
We
have
a
section
where
we
we
were
talking
about
which
versions
are
in
support
and
how
long
their
end
of
life
and
all
that
kind
of
stuff.
C
If
you
scroll
yeah
that
one
document
yep
so
I
opened
the
pr
to
document
what
our
plan
is
from
a
more
like
user
perspective
and
then
link
to
the
issue
and
what
I
would
like
to
do
is
essentially
set
a
lazy
consensus
on
that
PR
and
when
we
merged
at
PR.
We
have
essentially
agreement
on
that.
That's
what
we
want
to
do.
C
A
And
I
see
I
see
a
thumbs
up,
I'm,
not
seeing
any
thumbs
down
or
hands
up
so
I
guess
we'll
put
a
one
week:
lazy
consensus:
what
would
that
make
it
when's.
A
Yeah
all
right
cool,
so
please
people
take
a
look
and
if
not,
we
will
be
very
lazy
and
merge
it.
Next
week,
thanks
Stefan,
all
right.
You've
got
the
next
topic
on
removing
jobs
for
unsupported
release.
Bill
entrance
so.
C
Please
I
mentioned
two
weeks
ago:
we
sent
it
out
on
making
this.
We
had
this
issue,
it
feels
like
we
have
consensus
on
the
issue
and
I
hope
the
pr
for
it,
but
just
to
talk
about
a
topic
quickly,
so
that
issue
is
essentially
for
which
release
branches.
Are
we
running
intern
tests
or
nothing
tests
in
general,
but
the
main
part
is
end-to-enders,
and
the
proposal
is
that
we,
of
course
we
run
tests
for
all
our
supported
branches
and
then
we
run
tests
for
one
additional
release.
C
C
Basically,
just
all
you
have
some
weird
thing
that
we
have
to
do
in
the
emergency
release,
then
we
still
have
the
tests
around
and
we
can
actually
still
do
a
release
because
we
still
have
test
coverage.
That's
the
argument
for
waiting
like
essentially
four
months
longer,
yep
and
there
I
opened
a
PR
which
just
describes
that
as
some
sort
of
policy
I
think
it's
it's
almost
the
same
place
as
the
other
PR.
C
So
the
first
part
is
just
describing
what
we
would
test
and
the
second
part
is
just
I,
guess:
operationalize
it
in
all
these
tasks
that
at
a
certain
point
in
time
or
release
cycle,
we
also
drop
test
jobs
and
not
just
only
add
them.
Yeah.
A
A
D
A
Not
seeing
any
hands
going
up,
I
do
see
a
thumbs
up
and
yeah
I
will
Echo
what
is
being
said
in
the
comments
here.
Stefan.
Thank
you.
So
much
for
the
hard
work
here.
I
think
it's.
It's
awesome
to
see
these
documentation
bumps
as
well,
because
it
really
makes
it
clear
for
our
users
So
yeah.
Thank
you.
Thank
you.
So
much
all
right,
cool,
so
Fabrizio
release
Cadence.
Please
take
it
away.
Yeah.
B
Yeah
before
jumping
on
the
list,
Cadence
I
would
like
to
Echo
a
discussion
that
we
had
in
the
sorry
in
the
kubernetes
fig
leads
and
tech
leads
a
meeting
about
infrastructure
cost
of
kubernetes,
I
I,
don't
know
if
some,
if
every
one
of
you
is
aware.
B
Basically,
what
happened
in
elastia
is
is
that
kubernetes
is
a
project
that
started
a
big
effort
to
migrate,
some
of
the
infrastructure
which
is
coordinary,
p
Aid
by
Google,
to
to
cncf
owned
infrastructure
and
to
infrastructure
which
are
sponsored
by
other
companies
like
AWS,
etc,
etc.
These.
B
Longer
and
complex
process
process,
but
the
the
tldr
is
that
the
last
year
at
the
end
of
the
year,
basically,
the
the
project
was
required
to
go
and
ask
for
some
additional
finding,
because,
basically,
we
were
going
out
of
budget
and
it
happened
during
the
discussion
happened
during
kubicon
and
luckily
yeah.
B
We
found
a
company
that
provided
some
funding
to
reach
the
end
of
the
year
main,
the
main
or
the
biggest
source
of
cost
that
that
they
are
testing
for
folks
are
trying
to
address
is
the
cost
of
eager
traffic
for
the
images
download.
This
is
why,
if
you
are
aware,
they
implemented
the
migration
from
the
older
repository,
which
is
the
DCR,
the
kubernetesccr.io.
B
B
Last
so
in
last
week,
Tech
lead
meeting.
Basically
the
the
discussion
was
hey
guys.
We
are
looking
at
cost
that
a
spending
that
the
project
is
having
and
we
are
even
spending
more
than
last
year,
and
so
this
this
yeah
they
had
this
raised
the
set
the
attention
and
everyone
and
I
mean-
and
this
is
a
call
for
Action-
please
go-
make
sure
check
your
project
check
your
CI
check
your
automation
check,
whatever
you
are
telling
your
customers
to
do,
but
make
sure
that
we
we
as
a
community.
B
We
move
as
much
as
possible
folks
from
the
older
registry
to
the
new
registry.
So
basically
we
can
reduce
the
cost
of
kubernetes
infrastructure
and
we
can
keep
the
light
on
till
the
end
of
the
year,
and
these
are
this.
Was
there
was
a
strong
call
for
Action?
Please
everyone
do
whatever
you,
you
can
and
yeah
I
also
invited
to
look
at
the.
E
B
This
is
not
a
joke,
Stephen
an
early
vacation
they.
Basically,
if
you
don't
find
a
solution,
there
is
the
risk
that
kubernetes
some
sometimes
a
little
bit
earlier
than
November
does
not
have
a
money
to
run
tests,
and
so
you
don't
run
tests.
You
cannot
merge
PR
and
that's
mean
yeah.
That
means
that
the
the
latest
release
of
the
year
is
is
at
risk.
If
the
solution
is
not
addressing
so
please
everyone.
This
is
a
community.
B
Ask
let's,
let's
do
whatever
it
is
in
our
capability
to
to
shift
from
the
other
register
to
the
new
one
and
yeah
I.
Think
that
also
stopping
even
if
they
are
not
the
biggest
source
of
cost,
let
me
say
being
the
paying
attention
to
which
job
are
we
running,
especially
to
the
old
ones?
Stopping
them
to
run
is
part
of
the
yeah
doing
our
part
as
a
project
in
in
installing
this
bigger
issue,
Stephen.
C
That
plays
nicely
into
the
third
topic
that
I
had
like
three
weeks
ago
and
that
bring
up
next
week
is
essentially
that
we
Define,
which
kubernetes
releases
we
support
in
cluster
API
and
run
the
tests
accordingly,
because
we
still
are
running
tests
for
I,
don't
know
for
nine
different
releases
and
especially
the
old
releases
are
still
using
the
old
registry,
so
that
will
be
an
additional
win.
There.
B
Yeah
and
that's
a
good
one,
and
there
is
also
I
invite
also
everyone
and
I
can
also
search
for
it
and
copy
on
the
meeting
notes.
So
there
is
a
email
sent
to
the
kubernetes
developer
main
list
where
they
are
basically
telling
that
started
from
127
kubernetes
is
amazing:
will
stop
to
be
published
to
the
older
repositories
so
from
127
you
can
only
use
a.
B
The
new
registry
they
made
also
some
stats
on
on
the
on
which
version
customers
are
using.
As
expected,
we
have
many
users
that
are
still
an
old
version
and
what
which
are
already
out
of
support
from
a
couple
of
here,
and
so
it
is
also
under
discussion.
The
idea
of
stop
serving,
at
certain
point
with
some
some
policies
to
be
defined
to
stop
serving
images
for
old
kubernetes
version.
B
This
means,
if
you
want
to
use
two
people,
if
one,
if
people
want
to
use
all
the
kubernetes
version,
they
have
to
set
up
their
own
local
registry
with
the
and
call
it
kubernetes
easy.
Also,
so
this
this
serious
topic
yeah,
we
have
to
help
customers
to
move
to
more
recent
kubernetes
version
use
the
new.
B
A
B
A
Is
an
awesome,
Public,
Service
Announcement,
thank
you
for
breezy
and
I'm
just
going
to
try
to
call
as
much
attention
as
I
can
to
these
links.
So
anybody
anybody
and
everybody
who's
here
or
watching
this
later.
Please
review
this
material
just
to
make
sure
that
you're
aware
of
it,
and
also
if
you
manage
a
project
that
might
be
using
these
things
as
Fabrizio
was
saying
to
become
a
better
Community.
We
all
need
to
kind
of
take
part
in
this
and
and
look
out
for
our
bits
so.
E
A
Without
further
Ado
Fabrizio,
please,
okay.
B
So
moving
around
to
something
something
different
release
Credence
so
this
year
we
start
basically
with
the
release
team,
which
is
doing
a
great
job
and
we
also
said
decided
to
have
the
first
release
of
the
year
with
a
four
months
release
cycle
Okay.
So
what
I'm,
proposing
and
And
discussing
with
you
all
is
that
what
about
we
expanded
this
experiment
and
we
decided
to
have
to
continue
with
this
release.
Cadence
for
the
entire
2023.
B
That's
mean
that
this
year
we
will
have
three
copy
release,
which
is
which
nicely
why
I
think
this
is
a
good
solution.
First
of
all,
it
is
already
an
improvement
from
what
we
did
in
the
past.
In
the
past,
there
was
not
well-defined
risk
at
the
end
calendar,
and
usually
we
did
two
release
four
years
so
now
it
is
one
more
and
most
important.
It
is
ideal
predictable.
Second,
it
nicely
Italy
aligns
to
the.
B
Also
kubernetes
is
going
to
do
three
release
per
year
and
if
you
look
and
if
I
look
at
this,
it
seems
to
me
that
the
four
months
release
is
good
for
us,
as
maintainer
we
can
implement
the
meaningful
stuff.
Initially
is
good
for
the
release
team
because
they,
the
commitment,
is,
is
Meaningful
enough
and
at
the
same
time
it's
not
too
much
to
deal
with
it's
good
for
the
provider,
because
each
provider
basically
will
have
to
bump
a
copy
three
times
for
ear,
which
is
sustainable
and
yeah.
B
I
think
that
is
good.
Also
for
for
the
end
user.
So
question
is
opinions.
Mike
go
on
with
your
question.
A
Yeah
just
prepping
it
up
here
since
I.
Don't
really
have
a
raise
hand
feature
for
me,
but.
E
A
Like
I
think
this
is
I
think
this
is
really
cool.
It
would
definitely
be
helpful
and
I'm
very
curious
if
we
would
want
to
re
to
align
with
the
kubernetes
releases
and
I
say
this
partially.
As
you
know,
with
my
red
hat
on,
I
won't
go
grab
it,
but
you
know
we.
We
consume
cluster
API
Downstream,
and
so
we
we're
very
concerned
about
you,
know
doing
rebases
and
whatnot
and
I'm
I'm
wondering
if
we
move
to
this,
would
we
would
we
be
doing
the
same
thing
like
releasing
with
the
kubernetes
releases.
C
I
would
answer
them.
Your
point,
I
think
we
will
face.
I
mean
if
we
just
continue
doing
this
for
the
next
two
releases,
which
is
the
rest
of
this
year.
We
will
basically
align
to
kubernetes
yep,
so
I
think
they
were
planning
like
April
August
December.
C
We
are
currently
on
track
for
28th
March.
The
next
one
would
be
preliminary
date,
but
roughly
25th,
July
and
I
guess
the
last
one
is
like
end
of
November,
so
plus
minus
a
week
or
two
or
something
we
would
be
like
with
kubernetes
I.
Think
that's
not
too
bad.
C
It's
it's
probably
my
they're,
probably
nice
dates
in
a
sense
of
it's
not
like
during
Christmas,
or
something
like
that,
so,
which
is
probably
also
why
cumulators
might
have
ended
up
with
those
dates
and
I,
don't
know
what
other
restrictions
they
are
with
vocational
and
versus
usual
time,
certifications
are
and
stuff
like
that.
C
I
think
it's!
The
one
downside
is
like
the
I
think
it's
not
really
a
downside,
but
the
one
consequence
is
that
when
we
release
basically
at
the
same
time,
we
escalators
cluster
API,
minor
reset.co
release
can't
add
support
for
the
same
kubernetes
release,
because
it's
not
I
mean
it's
at
least
like
two
weeks
sooner
or
later
or
whatever.
C
But
you
can't
Implement
support
that
fast,
but
I
think
that's
actually
fine,
because
if
you
have
like
a
month
or
set
or
something,
then
we
have
to
super
rush
to
get
it
in
and
we
don't
really
have
a
lot
of
I
mean
if,
let's
say
cluster
API
would
be
always
released
a
month
after
coordinators.
We
always
have
that
month
to
get
stuff
in.
That
means.
Kubernetes
has
through
these
controller
and
master
reviews.
We
have
to
pick
it
up.
C
We
have
maybe
two
weeks
of
CI
and
then
it
also
restricts
your
options
regarding
flagging
those
sort
of
issues
as
Help
Wanted
issues
because
like
if
you
only
have
like
two
weeks
to
implement
something,
you
can't
really
open
it
up
to
the
whole
community
and
that
everyone
do
its
part
right
and
then
combined
with
the
current
suggestion
that
we
pick
up.
Support
for
new
companies,
releases
and
Patch
releases
I
think
that's
totally
fine
I
mean
what
what
we
probably
roughly
end
up
end
up
with.
A
Yeah,
that's
awesome.
Thanks
for
all
the
context
there
Stefan
Mike
you're
up
next.
F
Yeah
I
think
he
actually
covered
a
lot
of
what
I
was
going
to
say,
but
the
I
just
wanted
to
kind
of
plus
one
the
the
idea
of
waiting
a
little
bit
versus
doing
it
immediately
following
so
that
we
have
that
opportunity
to
bring
in
that
minor
release
into
it.
For
that
support,
if
we
tried
to
do
it
the
week
following,
would
we
have
enough
time
to
bring
in
that
new
version
support?
F
Because
then
we
would
end
up
having
four
months
of
not
having
support
for
that
new
version
of
kubernetes.
We
just
want
to
watch
out
for
that
possibility.
A
Yeah
great
great
concerns
Mike
and
thanks
for
sharing
your
opinion
too.
Does
anyone
else
have
thoughts
or
comments
or
questions
about
this
kind
of
release?
Cadence.
A
B
If
we
agree
what
we
can
do
is
we
can?
There
is
a
task
in
the
in
the
job
that
the
I
think
that
there
is
ADD
have
to
do,
which
is
basically
to
draft
the
plane
for
the
next
release
cycle,
I'm
a
right,
Stefan
eurology.
We.
C
Should
have
two
things:
I
think
which
are
related.
One
thing
is
yeah.
We
should
as
soon
as
we
have
some
sort
of
agreement,
we
should
write
the
new
timeline
for
the
next
release
by
the
way,
whoever
is
doing
that
I
have
a
draft,
so
you
don't
have
to
stop
from
scratch.
C
That's
that's
one
thing
and
the
other
thing
I
think
we
have
somewhere
to
do
very.
Basically,
he
wrote
after
1.4
we
should
discuss
the
release
Cadence
and
as
part
of
that
PR,
we
can
essentially
drop
that
to
do
and
move
it
over
to
I,
don't
know
in
2024
or
something,
and
then
we
have
a
PR
open.
We
can
get
approves
on
that
and
then
that's
a
decision.
C
B
So
since
there
is
no
objection,
my
suggestion
is
that
we
go
on.
We
open
a
PR
where
we
propose
basically
the
the
first
draft
of
the
calendar
for
the
next
cycle
and
we
amend
the
Hour
release
documentation
as
Stefan
suggesting.
So
then
we
can
basically
yeah
collaborate
on
the
pr
and
SQL
sensors
and
get
imagined,
and
it
will
be
done.
A
All
right,
I'm
not
seeing
any
hands
going
up
or
seeing
a
thumbs
up
online
yeah,
probably
the
best
thing
I
guess
is
yeah
make
the
pr
and
then,
if
we
have
objections,
we
could
bring
them
up
there
and
everything,
and
and
thank
you
to
Stefan
and
uviraj
as
well,
for
for
volunteering
to
help
out
okay.
So
that
brings
us
to
the
end
of
our
regular
discussion
topics
we'll
now
go
into
some
provider
updates.
Sorry,
maybe
maybe
I
misread
that
Stefan.
E
Yes,
just
a
very
quick
one,
our
end-to-end
test,
Suites
are
become
very
well
they've,
become
very,
very
unstable.
There's
lots
of
Reddit
test
grid,
it
seems
to
be
related
to
the
AWS
account
migration,
so
these
are
new
AWS
accounts,
which
is
causing
problems
for
our
end-to-end
tests
with
you
know
limits
and
things
like
that,
but
also
there's
some
issues
coming
from
boskos.
E
So
the
result
of
this
is
we're
all
focusing
on
getting
our
end-to-end
test
green,
which
means
we're
not
currently
reviewing
or
merging
any
other
changes
in
Kappa
until
we
get
green
again,
so
there
may
be
a
delay
if
people
are
have
have
changes
in
getting
those
in.
A
Great
thanks
for
the
update
and
yeah
sounds
like
a
little
bit
of
a
fire
drill
going
on
over
there.
Okay
Joe
you've
got
an
update
on
capoci.
Please.
G
A
G
So
we've
just
released
zero,
seven
zero
and
the
two
kind
of
big
things
is.
We
now
support
in
experimental
State,
the
managed
okay,
as
well
as
a
multi-tenant
management
cluster.
So
those
are
two
big
things
that
we've
been
working
on
for
a
little
while
and
sham.
Who
did
most
of
the
work
here
couldn't
be
here
today,
so
I
wanted
to
make
sure
we
announced
those
things.
A
Awesome
sounds
very
cool.
Thank
you.
Next
Jonathan
and
I
can
never
remember
what
this
one
stands
for,
but
for
CA,
aph
Oh,
wait!
Sorry
before
we
go
on
Fabrizio
I
see
raised
his
hand.
B
I
I
have
a
question
for
Joe
for
the
okay
support.
Are
you
aligning
with
the
discussion
on
going
on
on
the
managed
kubernetes
working
group.
G
Yes,
yes,
so
we
I
believe
as
well
as
I
want
to
say
it's
gcp
are
the
two
that
are
using
the
new
managed
kubernetes
proposal,
which
is
the
third
option
in
the
The
Proposal
there.
So
we're
doing
that,
and
also
we
are
a
part
of
the
managed
kubernetes
work
group.
Is
that
what
we're
calling
it
I
believe
so
trying
to
to
be
a
part
of
that
as
well.
So.
B
A
Cool
thanks:
okay,
now
Jonathan
caaph.
D
D
So
since
we
got
the
repo
set
up,
I've
been
working
on
setting
up
some
testing
for
jobs,
that's
still
kind
of
a
work
in
progress,
but
I
have
been
getting
some
issues
and
PR's
in
as
well
from
other
people
and
I
was
hoping
to
get
some
feedback
on
what
people
think
about
the
project
and
how
it's
working
so
far
as
well
as
looking
for
a
new
potential
contributors
and
maintainers,
because
currently
it's
just
me
driving
the
development.
D
A
Cool
thanks,
Jonathan
and
yeah
I
guess
like
for
any
for
anybody
watching
this
or
here
today,
or
maybe,
if
you
check
it
out
later
and
you're
interested
in
the
home
provider
yeah,
please
give
Jonathan
some
feedback
or
check
out
the
repo
or
open
an
issue
or
something
yeah
yeah.
D
For
sure
I
think
I
think
one
thing
I'm
really
curious
about
is
how
well
how
all
our
design
is
able
to
accommodate
people's
existing
add-on
flows.
So
you
know
we
sketched
out
the
design
and
that's
one
thing,
but
it's
also
another
to
see
if
hey
I
have
this
kind
of
setup
going
can
I
migrate
it
successfully
to
the
specs
you
designed
so
I
would
really
be
curious
about
how
that's
working
out
for
people.
D
D
A
Cool
well,
I,
guess
we'll!
You
know
we
send
our
shout
out
to
the
open
source
community
and
hopefully
we'll
get
some
something
back.
B
Just
saying
yeah,
it
will
take
time
some
time
to
get
contributor
on
your
project,
but
it
is.
It
looks
amazing
to
me
that
we
are
already
getting
some
issue,
but
yeah
I
think
that
we
can
do
something
to
help
you.
If
you
record
I,
don't
know
a
demo
and
a
call
for
Action.
We
can
add
this
to
the
sequest
recycle
playlist.
B
You
can
write
a
mail
to
the
mailing
list,
hey
guys.
This
is
where
we
are.
It
is
a
new
project.
We
we
seek
it
for
free
feedback
and
help,
and
so
you
can.
We
can
basically
start
beating
the
drama
little
a
little
bit
to
help
you
but
yeah.
If
you
have
a
team
or
something
that
we
can
spend
a
decade,
people
can
look
to
understand
what
the
project
is
quickly
without
doing
so
too
much
work.
This
will
help.
D
Yeah
for
sure
I
guess
on
that
you
know:
I
was
thinking
about
getting
image
published
to
the
registry
through
testing,
for
what
I
need
to
contact
somebody
to
get
the
URL
authorized
for
that,
or
would
it
just
be
enough
to
send
a
PR.
B
Top
of
my
mind
or
remember,
which
is
the
project
I,
think
that
you
can
ask
him
testing
for
our
channel
to
say.
Oh,
what
is
the
process
to
to
do
this
and
if
you
don't
find
someone
please
reach
out
and
I
will
try
to
help.
You
probably.
H
B
A
And
you
know,
thanks
for
breezy,
on
Richard,
for
bringing
up
these
suggestions.
You
know
yeah
I,
think
writing
blogs
and
demos
and
stuff
like
that.
Those
are
those
are
great
suggestions
and
a
good
way
to
promote
kind
of
the
usability
of
the
project
too.
So
awesome
awesome
to
see
the
community
kind
of
come
together
like
that.
H
Hey
thanks:
I,
don't
really
have
anything
to
add
to
what
I
typed
here
we
just
have
a
couple
More
or
Less
weekly
releases.
If
you
have
questions
about
that,
ask
me
now
or
join
us
at
the
office
hours
tomorrow
and
I
thought
I
might
mention.
Maybe
people
are
aware
of
this,
but
you
haven't
seen
our
friend
Jack
Francis
in
a
while,
because
they
have
a
new
baby
and
he'll
be
out
for
a
few
more
weeks.
A
couple
more
weeks.
A
Nice
well
I,
guess
transitive
congrats,
congrats
to
Jack
and
the
family.
A
B
There
is,
there
is
a
nice
query
posted
by
please
thank
you
Chris
for
this
that
people
can
use
for
searching
in
their
code
base
if
they
are
still
using
the
older
registry.
B
It
is
the
second
last
message
in
in
the
chat
yeah
very.
B
I
would
suggest
to
copy
this
in
the
in
the
meeting
notes
as
well,
because
yeah
it
could
have.
C
B
Yes,
just
paste
it
and
then
I
read
in
other
sub
comment.
A
Okay,
so
I
think
that
brings
us
to
the
end,
then
hope
I'm
just
going
to
check
the
new
messages
here:
okay,
I'm,
not
seeing
any
new
messages
or
hands
coming
up.
So
thanks
for
everybody
for
coming
out
good
meeting
and
I
guess
we'll
see
you
next
week.