►
From YouTube: Platform Sync: 2021-06-30
Description
Meeting notes: https://bit.ly/38pal2Z
A
All
right
and
before
I
guess
we
get
too
deep
new
faces.
Do
we
want
to
do
some
introductions.
B
First,
guessing
on
the
new
face,
my
name
is
yusuf
I'm
currently
interning
at
salesforce
with
roku
yeah
and
I'm
working
with
parents.
C
Yusuf
is
working
on
adding
custom,
build
pack
support
for
build,
so
he's
been
playing
around
with
all
that
stuff,
and
I
see
he
there's
a
topic
under
one
of
the
future
agenda.
Things
for
talking
about.
A
C
B
B
A
All
right,
18,
note
takers,
any
volunteers
to
take
notes
for
this
meeting.
A
Crickets
crickets,
it's
all
right.
We
don't
have
to.
C
A
Sounds
good
yeah
yeah,
depending
on
how
fast
we
go
through
these
should
be
fairly
quick.
We
should
be
able
to
get
through
all
of
it
all
right,
so
status
updates
for
myself.
A
All
I
could
talk
about
is
a
little
bit
of
the
release
planning
part
where
I've
talked
to
david
who's
kind
of
the
owner
for
pac.
It
sounds
like
we're
we're
going
to
hold
off
on
the
release
a
little
bit.
I
think
the
anticipation
was
a
week,
which
means
that
we
would
try
to
go
to
feature
complete
this
week
and
release
next
week
still
kind
of
pending
on
that.
A
So,
like
that's
sort
of
a
little
bit
nebulous
because
there
are
a
set
of
changes
that
we
want
to
or
pull
requests
that
we
want
to
get
in
before
that
time,
but
that's
more
or
less
the
current
working
timeline
for
that.
A
A
Okay,
any
other
status
updates
on
the
platform
side.
A
C
No,
I
think,
last
week,
actually,
when
you
weren't
here
at
platform,
we
were
talking
about
some
of
the
project.
Descriptor
changes
and
we
didn't
want
to
bucket
them
into
point
20,
because
obviously
a
lot
of
that
stuff
is
feature
frozen
and
underway.
Is
there
a
process
for
when
the
0.21
milestone
and
stuff
gets
made.
A
No,
I
would
only
say
that
you
know
if
there's
sort
of
some
contention
with
the
maintainers
they
might
move
stuff
around,
but
at
this
point
feel
free
to
do
so.
Okay,.
A
Cool
all
right,
so
that
speaks
to
that.
The
next
item
is,
you
know
the
general
topic,
so
exposing
functionality
to
download
build
packs.
Yeah
wants
to
take
that
on.
B
Sure
yeah,
I
added
it
so
I'll
go
ahead
and
take
it
on
so,
as
terence
mentioned,
we're
exposing
custom
buildback
functionality
in
our
in
our
platform.
I
guess
our
builder
and
there's
this
broader
issue
that
was
opened
about
a
year
ago
about
exposing
that,
like
detection
downloading
package
logic,
instead
of
re-implementing
it,
since
a
lot
of
things,
might
change
I
opened
up.
So
I
think
extracting
the
downloading
logic,
for
our
use
case
is
a
little
bit
trickier
if
we
want
that
our
exposing.
B
That
is
a
little
bit
trickier
if
we
want
it
to
be,
if
we
want
to
refactor
like
the
existing
pack
methods,
like
add,
build
packs
builder
or
whatever,
to
use
that
download
build
pack
uri,
because
we're
trying
to
avoid
docker.
So
right
now
for
my
specific
use
case,
I'm
not
addressing
the
whole
issue,
but
I
opened
up
a
draft
pr
to
expose
specifically
the
extract,
build
packs
function.
B
That
issue
that
I
linked.
A
Okay
and
then
to
just
for
my
own
sanity
right,
so
the
idea
I
know
we've
we've
kicked
around
and
then
maybe
you
haven't
been
part
of
those
discussions,
but
we
kicked
around
the
idea
of
maybe
pack
moving
to
a
plug-in
system
where
you
know
you
have
different
executables,
that
kind
of
like
utility,
executables
right
and
this
being
potentially
one
of
them
where
you
could
download
build
packs
in
other
platforms
outside
of
pack.
A
A
All
right,
so
are
there
any?
I
guess,
questions
about
that
or
just
a
kind
of
general
announcement
that
this
is
happening
and
we
should
look
at
the
pr.
B
A
No,
I
think
it
aligns
very
well
with
you
know
again
the
direction
that
we're
going,
and
this
would
be
a
first,
a
good
first
stop
gap
to
enabling
that
functionality
and
then
extracting
it
even
further,
hopefully,
in
the
future
cool.
A
We
do
have
three.
Actually
two
one
of
them
is
in
draft.
It
looks
like
all
of
these
are
in
final
comment
period,
so
yeah
like
we,
those
should
be
merged.
In
this
week
I
was
gonna.
C
Ask
you
because
they're
in
fcp
last
week
do
you
need
help
merging
these
in
javier,
since
you're
assigned?
Do
you
have
access
and
permission
to
do
that?
Do
you
need
me.
A
I
know
I've
run
into
issues
in
the
past.
I
think
right
now.
It's
just
a
availability
or
capacity
right.
I
don't
know
terence.
If
you're
volunteering
to
mergerman
that'd
be
great,
but
if
not,
I
could
definitely
give
it
another.
Try.
C
A
Yeah
their
stp
period
shouldn't
have
been
that
long
ago,
yeah
yeah
cool.
I
mean
I
say
that
but
22
days,
that's
pretty
expensive
or
yeah
for
the
visual
one.
A
A
All
right,
I
think,
we're
done
with
the
rc's
moving
on
natalie.
I
believe
you
have
a
couple
topics.
D
I
think
the
first
one
that
I
added
you
could
just
remove
it,
because
it's
already
enclosed
by
anthony's
pr,
but
that
the
discussion
around
that
issue
sort
of
led
me
to
wonder
about
you
know,
is
there
a
view
of
the
priorities?
Sorry
is
the
review
of
the
priorities
for
the
platform
team.
How?
How
would
we
go
about
discovering
that.
A
D
A
Yes
and-
and
it's
a
little
unfortunate
that
david
isn't
here
to
speak
a
little
bit
more
about
that,
given
that
he
is
the
owner,
but
I
you
know,
feel
free
to
reach
out
to
him
with
the
sort
of
questions,
and
I
think
we
could
get
further
clarity,
especially
as
we
get
closer
to
the
release
date.
We
should
be
able
to
start
bumping
stuff
out
that
we
know
for
sure
isn't
going
to
be
able
to
make.
D
Good,
I
think
I
mean
I'm
also
thinking
about
those
like
you
know,
not
of
very
high
urgency,
but
still
maybe
high
importance.
You
know
things
like
build
quet.
You
know
that
wouldn't
necessarily
show
up
on
a
milestone,
but
how
would
someone
discover
that
that
is
something
that
we're
you
know
thinking
about.
Looking
at.
A
I
think
that's
really
hard
to
do
in
an
open
source
project
unless
you're
talking
about
specific
teams
right
because
again
it
goes
back
to
the
individual
contributors
and
their
commitment.
I
guess
you
could
say
to
being
actively
working
on
something
and
I'm
not
entirely
sure
that
that's
something
that
you
can
for
lack
of
better
words
and
force
on
anybody
right.
A
I
think
the
build
kit
stuff
might
be
an
exception
only
because
it
is
somewhat
tied
to
the
road
map,
and
I
know
that
there's
been
some
discussions
and
I
think
I
believe
you're
the
you're,
the
one
that
brought
it
up
about
potentially
having
better
visibility
into
the
higher
level
items
in
which
build
kit
would
fall
into
that.
And
then
in
that
particular
case
we
could
have
somebody,
that's
you
know
more
or
less
owner
or
assigning
or
assigned
to
that
sort
of
stuff
or
piece
of
work,
but
anything
more.
A
You
know
smaller
or
outside
of
the
roadmap.
I
realistically
don't
see
a
way
that
we
can
have
something
like
that.
A
As
an
example,
right
like
we
have
contributors
immortal
human
right-
I
don't
know
their
real
name
at
this
at
this
moment,
but
they
volunteered
for
some
doc
related
issues
right
it.
It
would
be
difficult
to
say,
like
on
a
day-to-day
basis
that
he
is
actively
working
on
it.
A
A
These
are
all
just
projections
of
my
opinions
and
perspective.
I'd
be
definitely
open
to
hearing
others
or,
if
there's
a
possible
solution
that
you
have
in
mind.
D
I
think
at
one
point
we
talked
about
you
know
what,
if
we
had
a
project
board
that
could
show
cross-cutting
stuff
related
to
the
roadmap
and
like
things
that
almost
made
it
onto
the
roadmap,
I
think
we
were
just
you
know,
trying
to
really
narrow
the
scope
and
then
the
other
thing
that
I
thought
of
which,
like
you
know,
maybe
it
would
be
easier
rather
than
maintaining
a
project
board
just
having
labels,
which
I
think
we
already
have,
that
specifically
relate
to
roadmap
items,
and
I
don't
know
just
I
find
myself,
you
know
losing
track
of
all
the
different
initiatives
and
things
that
we've
talked
about
and-
and
you
know
wanting
to
know,
what's
going
on
with
x
right
without
having
to
have
that
organically
spring.
D
A
The
only
thing
I
was
gonna
say
to
that
was
kind
of
reiterate,
like
I
think
road
map
things
that
almost
made
it
into
the
road
map
are,
are
things
that
are
possible,
but
I,
I
think
anything
lower
level
than
that
more
granular.
A
C
Yeah
I
mean
I,
I
guess
javier's
point
like
we:
don't
it's
not
a
company
like
we
don't.
C
I
mean,
I
guess,
to
some
degree
like
vmware,
pays
people
full
time
and
so
there's
some
degree
of
control
that
whoever
is
managing
those
people
have
over
what
they
prioritize
and
work
on,
but
generally
an
open
source
right,
like
people
will
work
on
what's
important
to
them
or
what
they're
inspired
to
do
or
make
time
for
whether
that's
through
work
like
yusuf
working
on
exposing
like
this
was
never
a
priority
right
for
pac,
but
if
he
opens
the
pr
and
it
gets
merged
in
it
will
happen
even
if
it
never.
C
You
know,
never
made
it
in
as
a
thing
that
we
need
to
put
into
a
milestone
right,
but
it's
a
thing
that
we
as
salesforce
want.
So
we
will
pay
someone
to
do
it
right
and
I
think
that's
the
kind
of
nature
of
some
open
source
stuff.
I
think
potentially,
the
thing
you're
asking
for
natalie
is
maybe
not
platform
specific,
but
you
probably
in
your
head,
know
the
stuff
and
implementation
as
a
maintainer
on
the
implementation
team
and
so
platform
is
probably
the
big
gap
there.
C
This
seems
to
me
to
be
more
of
a
like
broader
project,
ideally
like
what
you
want
is
something
at
a
broader
project
level
for
even
for
stuff
that
isn't
super
granular,
like
even
for
the
roadmap
stuff
of
like
being
able
to
kind
of
have
a
place
to
track
that.
I
think
this
was
like
basically
one
of
anthony's
like
ass,
multiple
times
of
like
how
can
I
come
into
this
project?
C
D
Yeah,
it's
also,
I
mean
maybe
right.
I
am
coming
from
an
angle
where
you
know
I'm
a
I'm:
a
vmware
employee
who's
paid
to
work
on
this
project
right.
So
in
some
sense,
when
I'm
asking
myself
what
should
I
work
on
my
personal
preferences,
you
know
I
they.
They
obviously
play
a
role,
but
I
I
want
to
work
on
the
things
that
are
most
important
to
the
project
that
will
most
help
the
project,
and
so
how
do
I
know
what
those
things
are?
D
Which,
as
you
said,
I
have
some
idea
right,
there's
different
places,
you
can
go,
there's
road
map,
you
can
go
to
the
roadmap,
but
then
the
roadmap
just
really
says
like
this
is
what
we
plan
to
do.
You
know
if
I
want
to
ask
like
okay:
well:
what's
what's
the
status
like?
Where
can
I
get
involved?
It
kind
of
drops
off
there
and
you
have
to
have
some
more
like
inside
knowledge
at
that
point
to
proceed,
which
again
I
I
do
have
I'm
just
trying
to
make
it
easier
for
myself
and
others.
C
Yeah,
no,
I
think
that's
a
fair
point.
It
may
be
worth
revising
this.
I
don't
know,
I
don't
know
if
you
want
to
pow
out
on
how
we
can
do
this
better
at
kind
of
a
broader
project
level.
To
me,
this
doesn't
feel
necessarily
specific
to
platform.
The
platform
is
a
player
in
this
space
for
sure,
as
a
sub
team.
A
Yeah,
I
wonder
if
it's
worth
re
revisiting
in
the
core
sub
team
meeting
or
core
team
meeting,
which
I
believe
is
coming
up
soon,
but
I
I
definitely
like
the
idea
of
the
board
for
the
road
map
and
items
that
almost
made
it
onto
the
road
map.
I
think
there's
some
questions
about
who
maintains
that
project
board
or
who
are
the
people
that
are
maintaining
that
project
board.
A
That
plus,
I
know
github
recently
released
a
bunch
of
improvements
to
issues
where
epics
can
create
or
spin
up
different
issues
and,
and
that
could
maybe
create
a
little
bit
of
a
better
organizational
aspect
to
more
granular
issues
and
overall
status
of
those
larger
stories.
So
maybe
all
that
kind
of
ties
in
to.
A
All
help
moving
on
linux,
download
stats.
D
Oh
yeah,
we
were
talking
about
this
in
slack.
I
just
wanted
to
surface
it
in
this
meeting,
because
I've
been,
you
know
recently
curious
about
what
are
the
stats
around
pac
downloads?
How
many
downloads
do
we
have?
D
And
you
know
from
what
I'm
seeing
you
know,
majority
of
our
users
are
on
linux
and
you
know
we
in
the
last
year
provided
alternative
ways
for
people
to
install
pack
on
their
linux
machine,
and
yet
I
don't
think
those
downloads
are
reflected
in
the
numbers
we
see
on
the
github
release
page.
So
I
would
love
to
have
a
more
accurate
picture
of
what
the
usage
is,
but
it
seems
like
it's.
Nothing
is
like
just
right
there
for
the
taking.
A
So,
what's
the
end
goal
of
of
seeing
the
download
stats.
A
Is
it
just
curiosity
or
is
there
something
more
to
it?
Is
it
more
analytical.
D
Yeah,
it's
yeah,
it's
kind
of
I
mean
it's
like
again.
This
is
sort
of
coming
from
the
maybe
the
vmware
mindset
of
right.
We
must
have
metrics
for
our
team
right.
So
this
is,
you
know,
just
kind
of
like
maybe
not
a
practice
like
practical
use
for
knowing
these
numbers,
but
it
is
nice
right
to
have
a
reflection
of
of
how
the
community
is
is
using
our
our
software.
A
Okay,
so
I
guess
where
I
maybe
want
to
take.
This
is
like
what
is
the
benefit
of
having
these
sort
of
metrics
right,
and
I
know
that
we've
added
analytics
to
our
our
home
page
or
our
marketing
site
doc
site,
whatever
you
want
to
call
it,
and
then
we've
added
or
had
you
know,
kind
of
this
idea
of
adding
metrics
to
things
like
the
tutorials
on
catacota
and
stuff,
like
that,
and
I
think
the
idea
of
of
those
metrics
do
kind
of
play
a
part
in
like
the
overall
health
of
the
project
and
the.
A
I
guess
the
way
that
I'm
trying
to
frame
this
is.
It
seems
like
the
things
that
you're
asking
for
are
maybe
not
just
valuable
for
vmware
but
valuable
for
the
overall
health
of
the
project
right,
and
so,
if
we're
able
to
frame
it
in
that
way
and
really
make
that
the
objective,
then
I
do
wonder
if
we
could
do
better
right
of
actually
satisfying
that.
C
A
So
recently
I've
been
looking
there's
a
chaos,
linux
foundation,
something
I
forget
what
it
is.
A
Yeah,
so
that's
kind
of
like
a
a
primer
for
it
right
so
like
chaos
with
two
s's
is
like
this
sort
of
I
don't
know
what
is
it
like?
A
committee
like
a
foundation
organization,
whatever
that
defines.
C
That's
like
a
working
group
thing
right
for
trying
to
do
project
health.
Yes,.
A
And
with
that
they
have
some
tooling.
I
think
one
of
the
things
that
I
posted
of,
like
the
linux
foundation,
providing
insights,
kind
of
leans,
a
lot
on
chaos,
and
I
guess
you
know
going
back
around
so
like
this
whole
idea
of
like
project
health
and
in
the
open
source
world
is
still
maybe
to
teren's
point
like
difficult
right.
It
does
require
some
some
effort
on
a
lot
of
parts.
A
I
personally
think
it's
it's
worthwhile,
but
I
also
think
that
there's
another
sign
which
might
be
a
little
bit
more
contentious,
which
is
if
we
wanted
to
have
more
accurate
numbers
right.
This
typically
involves
gathering
more
data,
which
some
of
that
data
might
require
some.
A
You
know
deeper
thought
right
so
like,
for
instance,
the
downloads
right,
so
we
can
go
through
all
these
pipelines
and
try
to
determine
what
the
download
numbers
look
like,
but
then
we
have
to
take
into
consideration
like
excluding
ci
pipelines.
That
might
be,
you
know,
inflating
those
numbers
for
one.
A
So
I
think,
like
a
quote-unquote,
more
accurate
way
of
getting
this
data
would
be
to
actually
get
it
from
the
pack
executable
itself
right,
and
this
isn't
foreign
there's
a
lot
of
clies
that
have
usage
metrics,
that
phone
home
right.
So
if
you
could,
if
we
can
get
some
sort
of
agreement
that
this
is
possible
or
that
we
want
this,
then
we
can
have
pac.
A
And
you
can
see
this
sort
of
idea
also
working
for
even
the
life
cycle
right.
There
are
internal
mechanisms
both
from
red
hat
and
from
the
docker
community
that
do
also
phone
home.
It's
just
about
a
file
and
whether
that
file
allows
you
to
kind
of
gather
analytics
or
not.
A
D
C
Closely,
I
mean
I,
I
think
that
stuff
makes
sense,
but
it
feels
I
think,
that's
like
a
not
small
undertaking
to
actually
do
the
due
diligence
and
effort.
I
think
if
we
want
to
do
it,
it
almost
feels
like
a
conscious,
either
prioritization
or
maybe
roadmap's,
not
the
right
thing,
but
it
almost
feels
like
a
thing.
We'd
want
to
do
consistently
project
wide.
To
your
point,
javier
right
like
like
we're
going
to
do
this
in
pack,
it's
not
just
pack
right
like.
C
I
think
we
want
to
have
some
type
of
consistency
across
both
pack
life
cycle
registry,
probably
to
some
degree.
That
would
look
different
too,
but
you'd
also
potentially
like
numbers.
There,
like,
I
feel
like
ben,
always
asks
it's
like
what
are
the
download,
metrics
or
whatever
for
full
packs,
but
you
know
getting
those
numbers.
I
think
our
insight
into
our
own
ecosystem
that
aren't
just
people
using
build
packs,
but
how
they're,
using
or
like.
C
Packs
they're,
using
and
and
kind
of
that
stuff
like
like,
there's
also
the
builders
right
like
like
there's
that
almost
feels
like
it
should
be
a
kind
of
task
force.
That's
made
of
people
from
the
various
kind
of
sub
teams,
kind
of
a
spear
kind
of
thing.
C
Yeah
I
mean
I'm
con,
I
I'm
in
favor
of
it,
but
I
think,
like
joe
has
mentioned
multiple
times,
it's
like
at
the
cost
of
what
right,
like
everyone,
has
a
limited
time,
there's
already
more
than
more
to
do
than
what
we
want
to
do,
which
I
guess
maybe
comes
back
to
natalie's
point
of
like
how
do
I
find
how
do
I
spend
my
time
to
do
the
most
impactful
thing
right
and
so
to
me.
That's
why
I
was
potentially
thinking
about
roadmap
thing.
It's
like,
I
think.
C
And
this
is
the
thing
we
want
to
prioritize
because
even
it's
like
for
the
chaos
stuff,
it's
like
it's
not
like
it's
a
thing
you
just
get
to
like
insert
into
your
thing
right,
like
you
have
to
look
and
like
like
it.
It
is
not
super
easy
to
even
like
figure
out
what
all
the
chaos
stuff
is
like.
It's
a
large
kind
of
initiative
and
there's
a
lot
of
things
there.
It's
not
like.
Please
just
blend
this
stuff
right
and
so
even
like
investigating.
C
That
is
like
a
non-trivial
task
right,
and
so
I
don't
know
it's.
I
think
we
want
to
do
it.
We
would
have
to
say
we
want
to
do
this
over
something
else
and
I
think
that's
probably
the
hardest
buy-in
than
convincing
people
generically.
It's
important
to
do
right.
A
Yeah
I
mean
to
me
I'm
thinking
like
this
seems
you
know
confined
enough
and
defined
enough
to
to
be
its
own
standalone
project,
where
maybe
we
could
leverage
some
of
the
mentoring
programs
to
get
some
work
in
done.
A
C
Yeah,
I
think
next
action
item,
at
least
in
my
mind,
is
probably
someone
needs
to
do
some
investigation
like
something
that
is
well
scoped
or
not
necessarily
well
scope,
but
scope
to
some
degree
of
like
what?
What
does
a
kind
of
mvp
initial
result
of
this
could
look
like
that's
the
thing
we
want
to
do.
D
Yeah
so-
and
I
mean
like
full
disclosure
right,
our
our
team
at
vmware
people
who
are
you
know,
dedicated
to
cnb
working
on
this
whole
time
right.
We
we
need
to
measure
something
right,
just
I
think
also
maybe
it's
like
the
mindset
right.
You
know
someone
who's
spending
their
whole
day,
working
on
c
and
d's
to
not
really
have
any
read
on.
D
You
know
well
as
the
stuff
that
we're
doing
is
it
doing
any
good
right,
like
that
kind
of
creates,
like
an
angst
that
just
having
any
metrics,
even
if
they're
imperfect,
I
think,
is
helpful.
For
so
we
are
planning
to
start
tracking
some
things
and
I
for
sure
we
can
share.
You
know
what
we,
what
what
it
is
that
we're
measuring
with
the
community,
and
so,
if
there's
value
in
that
and
there's
a
desire
to
take
it
further
that
you
know,
maybe
that
could
be
the
place
where
we
jump
off
from.
C
Yeah
I
mean
I'd,
be
happy
to
talk
to
you
more
about
this
offline.
I
know
I
I'm
personally
interested
in
some
of
the
stuff
on
the
salesforce
side
too,
the
because
you
know
we
we
also
invest
in
cb,
so
there
is
the
like.
I
want
to
be
able
to
expose
metrics
internally,
on
my
own
end,
to
continue
justifying
some
of
those
efforts
right.
So
there's
that
part
of
it
for
me
that
is
selfish
and
biased,
but
hopefully
means
benefits
the
project
of
continuing
to
put
more
people
hours
into
it.
C
Have
you
looked
into
the
cncf
dev
stats?
It
is
not
the
metrics.
I
think
that
you're
talking
about,
but
the
way
I
have
been
pitching
internally,
on
my
hand,
is
ultimately
like.
I
think,
you're
asking
about
measuring
impact
right,
like
measuring
impact
on
the
industry.
Measuring
in
fact,
like
the
investments
that
vmware
is
making
is
making
a
difference,
maybe
get
paraphrased
to
some
degree.
C
Right
and
I
know
for
me-
I've
been
leveraging
some
of
the
cncf
dev
stats
that
already
being
generated
for
us,
because
we
get
them
for
free
for
being
part
of
the
foundation,
so
they're
already
generating
a
lot
of
github
specific
metrics.
So
it's
not
going
to
be
like
the
pac
downloads
or
how
many
people
are
using
lifecycle,
but
you
can
measure
how
many
people
are
contributing
to
the
project
and
they
have
breakdowns
by
kind
of
company
to
some
degree
of
accuracy.
It's
actually
kind
of
crazy.
C
They
have
a
whole
thing
where
they
like
track
to
some
degree
like
who
is
associated
with
what
like
email,
addresses
and
github,
and
then
they
also
have
like
dates
of
like
when
people
leave
and
join
companies,
there's
only
a
table
for
that
that
they
track
and
ideally
about
so
I've
been
looking
to
this
heavily
because
the
metrics
that
I'm
trying
to
expose
are
what
contributions
are
coming
from,
basing
non-sales
force
and
non-vmware
like.
Are
we
making
enough
impact
that
other
people
are
also
contributing
to
the
project?
C
And
how
is
that
kind
of
growing-
or
I
guess
not
growing,
if
we're
doing
badly
over
time?
Right
so
like
what
contribution
are
we
getting
from
the
non-founding
companies.
D
Yeah,
those
are
exactly
the
kinds
of
questions
that
we're
asking
too
so
yeah
for
sure
it
would
be
great
to
to
you
know,
just
compare
notes.
We
are
also
looking
at
that
dashboard
and
find
value
in
it
also
find
you
know
some
ways
that
we'd
like
to
improve
it,
but.
C
Yeah,
I
guess,
let's
find
some
time
outside
of
here,
to
talk
more.
A
Cool
all
right,
so
I
think
that
takes
us
to
the
last
item,
or
that
was
the
last
time.
I'm
sorry,
is
there
any
last-minute
points
we
want
to
discuss.
C
I
have
to
bail,
but
I
know
natalie
brought
up
a
thing
from
last
time
that
she
didn't
bring
forward
again.
Maybe
it's
not
an
issue.
The
like
support
for
the
api
versions.
Is
that
a
thing
you
still
want
to
talk
about.
C
D
And
06,
like
people
who
want
to
take
advantage
of
report
tommle,
are
out
of
luck.
If
they're
pack-
users,
because
that
gets
you
know,
thrown
away
with
the
build
container,
and
so
you
know
to
what
extent
do
we
want
to
try
to
insert
in
that
insert
that
functionality
in
the
next
release
or
if
we
don't
have
it,
do
we
want
to
declare?
A
Yeah,
I
think
I
posted
my
opinion
somewhere
in
slack,
but
I
definitely
don't
agree
with
the
idea
of
supporting
a
platform
api
being
held
back
by
whether
a
certain
feature
is
exposed
to
the
end
user.
So
I
think,
from
from
my
perspective,
the
compatibility
with
an
api
version
is
simply
just
that
it's
compatibility
and
support,
not
the
potential
of
added
features,
if
that
makes
sense
right
so
like
the
report
table
isn't
exposed,
which
I
get
is
is
a
pretty.
A
You
know
highly
desirable
thing,
but
the
spec
itself
does
not
say
that
that
must
be
exposed
right,
and
so
by
that
nature,
if
you
had
nothing
or
like,
if
you
you
didn't
care
for
the
report
tamil
at
all
by
definition,
pakistan,
you
know,
supports
and
is
compatible
with
api
05
or
o6.
D
Okay,
that's
fine!
I
don't
I
I
don't
have
a
strong
opinion.
I
think,
and
even
the
person
who
wanted
this
functionality,
I'm
not
sure
how
like
important
it
is.
I
guess
maybe
we
can
make
an
issue.
I
I'm
happy
to
create
an
issue
on
pac
for
to
support
report
tunnel
and
people
can
thumbs
it
up
if
they
want
that
feature.
Does
that
sound
like
it.
A
Yeah,
I
think
that'd
be
a
great
action
item.
I
don't
know
if
that
was.
You
know
the
outcome
of
that
conversation
either.
I
know
it
sounded
like
he
just
wanted
a
snapshot
of
what
it
looked
like
and
anthony
was
able
to
provide
that,
and
you
know
we
heard
nothing
else,
so
that
might
have
just
been
it
right.
So
again
it
kind
of
goes
back
to
it
doesn't
sound
like
that
was
a
blocker
to
the
to
to
this
adoption
piece.
It
was
just
maybe
the
frustration
of
not
being
able
to
get
to
it
easily.
C
Yeah
I
mean
I,
I
still
think
it's
worth
creating
an
issue.
I
agree
with
javier.
The
spec
doesn't
say
I
think
report
tunnel
is
a
platform
civic
feature,
so
it
doesn't
say
how
the
platform
should
expose
it
or
if
it
should
at
all
right,
like
you
know,
on
the
salesforce
side,
for
our
build
system
we're
compatible,
but
we
aren't
exposing
anything
from
a
report-
columns
user,
but
if
it
is
a
thing,
people
want
because
it's
packed
and
that's
how
mozilla
interact
with
most
features
in
build
packs,
then
it
it
also.
C
If
I
recall
from
a
slack
conversation,
it
wasn't
like.
Oh
someone
just
needs
to
like
make
a
small
code
change.
It
was
just
like
how
can
we
even
actually
expose
this
thing
in
a
reasonable
fashion
right
so
but
yeah
I
mean
it
feels
like
a
feature,
and
I
don't
even
know
if
I
would
even
in
the
notes
when
we
support
0.5.68
like
we
don't
support,
report
time
or
whatever,
like
I
don't
even
know,
if
I
would
raise
it
to
even
that
level
right
like
it.
D
Is
this
helpful?
Thank
you
I'll,
create
the
issue
and
then
I'll
I'll
just
sit
back,
and
if
people
want
it
then
then
they
can.
They
can
add
their
comments.
A
That's
great
yeah,
I
know
I
know
it
opened
up.
You
know
kind
of
worms
of
like
other
conversations,
and
so
that's
to
me,
like
it
didn't
again
point
at
the
at
the
perspective
that
something
was
needed
immediately.
It
was
more
of
like
hey
there's
this
data
like
how
do
I
access
it
and
are
there
better
ways
to
access
it
right
so
yeah,
even
after
the
conversation
it
didn't
seem
like
there
was
a
here's,
the
quick
fix,
kind
of
thing,
but
yeah
we
could
discuss
it
in
the
issue
itself.