►
From YouTube: Working Group: 2022-05-24
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
A
A
A
So
we'll
start
by
the
health
check,
the
obviously
for
a
health
checker
buildback.
C
Sorry,
digital,
I
can't
see
the
share.
I'm
not
sure
why,
but.
A
D
C
A
A
Well,
I
don't
be
here
frankie
nor
daniel,
but
this
one
comes
from
one
issue:
yeah
one
issue
I
created
and
it
has
to
that
right
now,
when
users,
this
is
true
for
most
of
the
repos
not
for
for
all
of
them,
but
most
of
the
bill
pack
reports.
If
a
user
creates
an
issue,
the
the
template
is
mainly
for
a
bug
report
and
it
asks
a
lot
of
questions
for
for
a
bug
report,
but
nothing
if
the.
If
the
user
wants
to
file
a
feature
request
or
report
a
security
vulnerability.
A
A
A
And
unfortunately
I
don't
see
frankie
here
but
yeah,
it's
it's
recording
jellyfish.
I
don't
know
if
anyone
else
from
team
would
like
to
comment
on
this
proposal.
B
I
think
this
is
a
pretty
basic
rfc,
explaining
how
we
will
shipbuilders
to
accommodate
for
the
new
set
of
jellyfish
stacks
that
are
coming
out
so
yeah
give
it
a
read.
If
you
have
any
questions
or
want
to
add
anything,
you
guys
let
frankie
know.
A
Okay,
right
now
for
for
cmv
update,
rob
recently
shared
a
report
that
the
cmb
community
shared
a
user
survey
for
the
last
year.
I
find
it
really
interesting.
There's
a
lot
of
insight
there.
I
suggest
that
in
case
you
haven't
done
so
check
it
out.
Read
it,
and
probably
we
will
start
a
discussion
about
this,
because
I
see
that
there
are
some
lessons
we
can
apply
from
there
from
this
report.
A
It's
interesting
for
me
to
find
the
biggest
frustration
is
that
buildbacks
are
not
used
widely
enough
in
this
industry.
An
adoption
issue,
yeah,
there's
a
ton
of
information
here,
so
we
we
suggest
that
you
you
give
it
a
read
and
probably
at
the
next
meeting,
we
will
discuss
it
even
better
unless
you'll
want
to
comment
something
around
the
survey
right
now,.
A
Next
one
in
terms
of
project
update,
I
I
wanted
to
use
some
of
the
time
or
probably
the
remaining
time
of
this
session,
to
share
with
you
all
the
results
of
an
assessment
that
I've
been
running
with
the
pacquiao
project
and
that
explain
most
of
the
issues
that
I've
been
creating
so
far
so
yeah,
I
don't
like
powerpoint
either,
but
this
is
what
I
have
handy
to
to
show
you
briefly
the
results,
yeah,
first,
that
we
need
to
say
that
this
is
one
of
the
things
we
do
in
the
community
engagement
team
for
projects
that
are
initiated
or
maintainer
maintained
by
vmware,
or
that
has
at
least
one
vmware
maintainer.
A
We
used
to
run
assessments
against
a
set
of
guidelines
or
best
practices
for
the
health
of
an
open
source
community.
So
this
is
not.
This
doesn't
have
any
commercial
implication.
It's
it's
just
having
metrics
for
the
engagement
of
the
community
and
the
health
and
growth
of
this
community,
because
we
all,
if
you
ask
a
open
source,
maintainer
or
a
a
bunch
of
open
source
maintainers,
they
all
want
to
grow
the
community.
A
But
the
first
step
is
to
measure
appropriately
the
the
kind
of
metrics
are
relevant
and
also
to
establish
a
plan
to
increase
in
engagement
and
and
help
users
be
successful
with
the
project.
So
these
guidelines
are
public.
I
will
I
will
share
with
you
the
link
in
a
bit,
but
it's
under
the
vmware
tensor
repo.
You
will
find
there.
The
community
engagement,
repo
and
all
these
work
is
public.
A
Is
there
we
have
six
domains
measuring
project
maturity,
viability,
the
growth
itself
of
the
community,
the
diversity
of
the
community,
how
the
maintainers
are
being
able
to
to
cop
up
with
the
load
of
issues
prs
and
all
that
and
in
general
user
engagement.
So
these
are
the
six
domains.
I
won't
go
any
deeper,
I'm
just
probably
providing
a
summary,
because
most
of
these
work
have
to
be
done
asynchronously,
but
I'm
here
to
share
with
you
all
a
summary
of
the
findings.
A
So
what's
working
well
when
compared
with
this
baseline,
what
what's
working
well
in
the
project,
the
content
of
the
documentation
itself,
I
mean
this
project
has
several
getting
started
guides.
A
It
has
a
good
reference
and,
and
most
of
the
documentation
content
is
deep
enough
to
help
users,
but
there
are
some
opportunities
to
improve
there
that
I
will
share
with
you
in
a
bit
also
the
fact
that
this
team
works
mostly
in
the
open.
It's
it's
pretty
good.
This
is
a
challenge
not
only
at
vmware
but
at
many
other
companies
maintaining
open
source
projects.
A
Sometimes
it's
really
hard
to
break
a
culture
of
working
working.
You
know
in
closed
source
and
making
decisions,
and
you
know
behind
the
walls
and
not
communicating
enough,
but
this
team
works
differently
and
they
usually
start
in
the
open
and
yeah
kudos.
For
that
this
is.
This
is
great.
It
sometimes
is
the
hardest
part
of
helping
a
community
group
and
finally,
adoption
from
what
we
can
see.
There's
a
good
number
of
organizations
using
pacquiao
bill,
packs
out
there
who
are
them
and
what
they
are
doing
with
the
project.
A
We
are
not
sure,
that's
part
of
the
action
plan,
but
we
have
seen
many
interactions
in
yeah
and
select
channels
in
events,
etc.
That
leads
us
to
complete
clue
that
there
are
many
organizations
using
actually
using
pacquiao
buildbacks.
So
that's
fine.
What
what
needs
to
be
working
on
a
little
bit
better
is,
for
example,
the
release.
Note
completeness
we
already
started
a
discussion
on
this
there's
an
issue
for
that
I
will.
I
will.
A
I
will
show
you
by
the
end
of
the
session,
how
we
are
continuing
the
conversation
here,
but
it's
trying
to
find
a
balance
between
providing
more
human,
readable
information
in
release
notes,
but
avoiding
having
to
write
release
notes.
You
know
from
scratch
by
him
for
every
release
for
every
wheelback.
A
That's
that's.
One
of
the
findings
also
a
way
to
provide
recognition
for
contributors
beyond
just
the
shoutouts
in
the
release
notes
a
consistent
way
to
publicly
recognize
the
many
contributions.
This
project
receives
different
kind
of
contributions,
not
only
code
and
also
to
work
more
on
the
non-code
contributions
from
what
is
non-code
well,
mostly
content
in
terms
of
blog
posts,
presentations
at
events,
screencasts,
etc.
A
A
So
all
the
efforts
on
spreading
the
word
about
the
project
are
are
key
for
for
the
health
of
this
community.
So
far,
any
question
is
this
clear
enough.
A
Yeah,
otherwise,
let
me
know
okay
yeah,
so
there
are
some
things
here
in
terms
of
project
maturity.
A
There
are
some
guidelines
that
again
are
public
but
summaries
that
there
are
some
improvements
to
the
readme
that
I
already
put
in
a
story
in
an
issue,
for
example
a
reference
to
the
code
of
conduct
by
the
cloud
foundry
foundation
and
and
one
that
that
is
important
at
least
for
for
a
new
user
like
myself,
is
that
if
I
go
to
read
me
the
global
readme
of
the
pocket
organization
or
the
readme
of
any
bill
pack,
I
don't
find
a
link
or
a
reference
to
the
getting
started
guy
and
for
for
the
adoption
of
the
project.
A
It's
really
important
to
to
find
a
smooth
way.
So
users
are
exploring
the
project
just
evaluating
the
project.
They
they
find
it
easy
to
to
just
get
started.
You
already
have
the
content
there.
You
already
have
a
project
already
have
a
pretty
good,
getting
started
guide,
not
much
better
than
most
other
projects,
but
but
it's
not
referenced
here
right.
So
there's
already
a
story
for
that.
We'll
keep
working
on
this,
but
it's
part
of
the
findings
usually
projects
here.
A
Are
you
know
our
launch
and
there's
a
blog
post
that
that
goes
with
the
the
announcement?
We
we
only
found
the
blog
post
at
the
medium
pacquiao,
build
packs,
account
or
space.
I
don't
know
how
it's
called
medium,
so
we
will
explore
explore
how
how
to
have
this.
D
A
Content
hosted
that
the
pacquiao
block
itself,
you
know
the
the
initial
blog
post
that
explained
what
is
the
project
and
what
does
it
do
and
how
it
helps.
So
it's
really
useful
yeah
the
again
the
issue
template
you
saw
that
it's
already
in
the
works,
the
governance
stock.
If,
if
we
read
right
now
the
the
government
stock
it
it
will
let
one
to
think
that
to
be
able
to
contribute
anything
to
the
project,
you
need
to
pass
through
an
election
process.
A
So
this
is.
I
think
this
is
already
fixed.
If
you
see
right
now,
I
mean
because
I
don't
have
enough
time
here,
but
if
you
go
to
the
cover
already
sharing
my
screen
here,
it
would
be
kubernetes
doc,
real
quick.
You
will
see
that
there's
already
a
definition
of
rules.
Oh
no,
it's
not
merged
there,
but
it's
in
the
word.
A
There's
there's
a
pr
in
the
works
to
yeah
to
clarify
that
anyone
can
participate
in
the
project
because,
right
now,
if
you,
if
you
see
there,
it
says
that
the
contributor
has
to
make
regular
contributions
at
it,
has
to
be
nominated
or
self-nominated
and
must
be
elected.
A
So
we
need
to
give
a
space
for
casual
contributions
and
that's
the
the
message
of
this
one,
all
right:
a
style
guide.
We
need
to
document
the
style
guide
we
are
using
for
docs
that
will
help
external
contributors
to
help
with
documentation.
Eventually,
we
need
to
work
on
a
public
list
of
adopter
organizations.
A
This
is
something
that
I
will
be
leading
and
probably
finding
help
from
the
pmt
and
most
of
the
talks.
Events
content
out.
There
dates
to
the
launch
to
two
years
ago
or
one
year
ago,
so
we
need
to
work
on
a
content
plan
and
I
will
share
with
you
in
a
bit:
okay
in
terms
of
contribution
to
open
source
related
open
source
project.
In
summary,
according
to
the
cmv
public
stats,
the
majority
of
contributions
to
the
cnb
project
comes
from
pivotal
or
vmware
accounts.
A
Even
this
account
here
that
it
says
avalyn
juan
bustamante
he's
a
vmware
employee,
probably
he's
using
his
previous
github
account,
but
most
of
the
recent
contributions
to
the
cmv
project
comes
from
vmware
employees.
So
that's
that's
good!
That's
positive
in
terms
of
upstream
contributions.
A
Well,
the
openness
of
best
practices,
the
open
source
security
foundation
now
maintains
a
baseline
of
best
practices
that
cover
most
of
the
stuff
in
terms
of
security
quality
for
infrastructure.
Let
me
share
with
you,
so
we
have
here
a
profile
already
created
for
paquetto
build
packs.
A
You
will
see
here
that
there
are
six
domains
of
best
practices
for
several
things.
In
summary,
this
is
what
the
linux
foundation
thinks.
In
this
case
the
opens
or
security
foundation
things
it's
the
baseline
of
what
an
open
source
project
should
have,
and
we
we
are
to
complete
most
of
this
information.
I'm
sure
that
most
of
these
features
are
already
in
place
for
the
project.
A
This
is
the
goal
so
far,
silver
and
gold
criteria
requires
even
more
stuff,
but
right
now
it's
only
to
achieve
the
passing
level
right
and
for
that
we
need
to
reach
100
100.
We
we
don't
need
to
do
everything
here,
but
we
need
to
document.
If
we
are
not
doing.
I
don't
know
if
you
are
not
using
ci
cicd
for
example,
why
why
we
are
not
doing
right,
so
this
is
good
for
for
adoption.
It
helps.
D
A
Exploring
out
there
the
project
to
have
the
confidence
to
deployed
in
their
use
cases
all
right,
regular
release,
cadence.
A
This
is
one
of
the
key
metrics
for
most
open
source
projects
here,
but
we
are,
we
decided
that
probably
doesn't
apply
for
pacquiao,
because
we
have
a
bunch
of
different
build
pack
communities
here
and
that
we
just
cannot
enforce
a
regular
release
cadence
for
for
the
project,
it
probably
doesn't
apply-
and
that's
true
for
other-
let's
say
umbrella
projects
here,
like
kerbel,
which
is
cannot
enforce
regular
release,
skills
roadmap
quality,
it's
improving
by
a
lot,
not
not
only
because
it's
built
in
the
public
and
communicated,
but
the
fact
that
we
will
be
following
it
up
during
regular
meetings
publicly
that
that's
certainly
something
that
makes
the
difference,
because
one
thing
is
to
you
know,
build
a
roadmap
and
put
it
in
the
repo.
A
Another
thing
is
to
make
sure
that
we
are
following
in
three
years,
so
yeah
that
that's
good
documentation.
In
summary,
documentation
is
fine,
but
we
didn't
want
to
arrive
to
conclusions
there,
just
because
of
probably
a
user
like
myself,
I'm
not
an
experienced
developer.
There
are
some
things
that
probably
I
don't
fully
understand
so
for
this
we
would
like
to
propose
and
explore,
and
probably
with
the
help
of
the
pm
team,
formal
user
research
exercise.
A
What
is
that
we
will
find
a
set
of
users,
a
subset
of
the
user
community,
that
that
would
like
to
contribute
feedback
and
with
with
clear
goals,
and
we
will
focus
on
a
specific
section
of
the
documentation
or
or
or
the
site
itself,
and
and
we
will
collect
specific
and
actionable
feedback,
because
one
thing
is
to
ask
a
user
hey.
What
do
you
think
about
docs
yeah
I
like
them
or
or
not
whatever,
but
a
totally
different
thing?
And
that's
been
my
experience
so
far
with
another
project.
A
A
Nope,
okay,
yeah
growth
of
community,
again
role,
definitions,
the
casual
contributors
role,
that's
in
the
works,
you
have
a
well-defined
path
to
maintainership
right
there
in
the
governance
stock
for
a
user.
Besides
the
casual
contributions,
it's
pretty
clear
what
is
needed
to
go
from
you
know
from
everyone
to
core
contributor
to
maintainer
and
what
are
their
responsibilities.
So
that's
good,
and
there
is
a
slightly
positive
trend
in
terms
of
continually
on
boarding
new
contributors.
This
is
the
graph
from
the
last
six
months
in
terms
of
contributions.
All
these
metrics
are
public.
A
Are
there
at
the
insights,
linux
foundation
instance?
I
just
downloaded
them,
so
we
see
a
slightly
growing
trend
and
one
of
the
key
metrics
for
success
here
will
be
to
to
keep
that
pace
or
even
to
increase
the
pace
of
contributor
growth
and
not
only
grow
by
the
diversity
of
contributions,
in
terms
of
not
only
you
know,
vmware
employees
or
or
etc,
but
to
recreate
or
to
have
contributions
for
from
more
organizations
and
not
only
in
terms
of
code.
This
is
only
code
contributions
right,
but
but
this
is
good.
A
Okay,
yeah!
Well,
the
distribution
of
work
has
to
do
with
again
of
all
the
things
that
need
to
be
done
to
maintain
the
project.
Mostly
right
now
is
it's
maintainer
driven.
There
are
not
much
stuff
that
the
communities
right
now
we
we
are
ready
to
delegate,
for
example,
docs
in
the
future.
We
could
have
a
documentation
working
group
with
with
folks
from
the
community
helping
with
docs,
but
for
that
we
need
first
to
document
the
style
guide
and
some
other
stuff.
A
So
right
now
it's
mostly
maintainer
driven,
but
the
plan
is
to
change
that
in
the
future
to
to
distribute
more
the
load
of
maintaining
and
growing
the
project
decision
distribution.
Well,
the
the
thing
with
open
source
is
that
muscle
decisions
are
still
central.
I
mean
think
on
the
linux
itself.
The
only
person
with
merch
permissions
is
linus
terribles,
so
it's
pretty
centralized.
A
A
A
I
will
explore
how
to
improve
this
with
the
cfl
marketing
folks,
and
also
you
use
heavily
discussions
which,
which
is
great
the
newsletter
we
we
have
the
the
mailing
list,
but
I
I
haven't
started
to
build
a
newsletter
because
I
I
would
like
to
to
build
it
collectively.
You
know.
A
It's
hard
to
find,
I
mean
there
are
many
things
that
are
new,
but
I
need
to
go
through
several
slack
channels,
places
etc.
So,
probably
having
I
don't
know
if
an
issue
for
every
edition
of
the
newsletter
could
help
with
for
anyone
that
could
contribute
there
hey.
This
is
new.
Just
make
sure
that
in
the
newsletter
that
could
help
I
will.
I
will
create
a
story
for
this
and
also
to
find
agreement
on
or
consensus
on
what
will
be
the
cadence
once
every
two
weeks
once
every
month,
etc.
A
What
will
make
sense
for
the
thing
that
yeah
newsletter
is
definitely
helpful.
A
A
A
A
A
A
So
but
yeah
right
now
in
terms
of
prs,
is
mostly
vmware.
A
Yeah
non-code
contributions:
this
is
the
inaugural
blog
post,
the
the
first
blog
post
that
describes
what
is
a
project
and
it's
it's.
It's
a
really
good
one
we'll
try
to
see
how
what
we
can
do
with
this
content,
to
make
it
more
visible
and
because
medium
has
a
paywall
but
yeah.
Most
of
this
content
dates
to
2020.
A
In
terms
of
attentiveness
of
maintainers,
yeah,
well
and
recognition
of
contributors,
we
need
to
make
sure
that
I
mean
contributing
to
open
source.
It's
it.
It
has
a
lot
to
do
with
intrinsic
motivation.
You
know
users
out
there
find
meaning
find
it.
There
is
meaningful
for
them
to
contribute
to
this
project,
and
probably
it
helps
with
professional
recognition,
but
certainly
there's
also
the
need
for
external
or
extrinsic
recognition.
A
A
So
this
is
what
I
call
the
contributor
of
the
month
initiative
and
I
will
share
real
quick
here,
the
story
for
this,
because
I've
I've
been
running
similar
initiatives
in
the
past
and
and
it's
and
it's
pretty
good
because
most
of
the
times,
people
contributing
to
the
project
to
an
open
source
project
are
not
expecting
anything
in
return.
A
A
So
the
plan
is
to
recognize
three
types
of
contribution:
code:
the
masculine
one
content,
anyone
who
writes
a
blog
post
or
create
a
presentation
or
a
podcast
whatever
with
keto
wheel,
packs
and
a
community
advocate
someone
who
joins
the
meetings.
A
I
just
need
to
tweak
it
to
fit
the
all
duplicated,
rippers
and
plans
to
write
a
blog
post
with
all
the
details
and
a
clear
and
transparent
election
process,
and
I'm
already
working
with
the
swat
provider
to
have
all
these
swag
bundles
for
for
contributors
and
also
to
the
first
meeting
of
the
month.
We
will
add
it
to
the
agenda
to
provide
also
a
shout
out
a
public
shout
out
for
for
top
contributions
from
last
month.
A
Yeah
you,
you
run
retrospectives,
it's
it's
not
feasible
to
run
recently,
retrospectives
for
all
the
build
pack
releases,
so
yeah
they're,
they're
they're,
fine.
My
experience
with
with
other
projects
here
is
that
sometimes
it's
also
useful
to
including
the
retro
content,
not
only
specific
release,
but
in
general
how
the
project
is
doing.
A
You
know
the
the.
How
can
we
improve
the
way
we
are
working?
So
this
is
also
useful
again
release.
Note
completeness
this
is
already
in
the
works.
There's
a
story
for
that
and
transparency.
It's
it's
never
done!
You
know.
Transparency
in
open
source
is
never
done,
it's
always
improving,
but
you
do
a
really
good
job
on
this.
A
Oh
yeah,
attentiveness
of
my
interiors,
this
is
for,
for
the
overall
pacquiao,
build
packs
repos.
You
know
the
majority
of
the
times.
The
prs
remain
open
for
almost
15
days.
That
that
is
is
not
good.
It's
not
bad!
It's
just
what
it
is,
because
some
peers
need
a
lot
of
discussion,
need
approvals,
etc.
Life
happens.
So
that's
just
more
information.
A
This
is
not
tied
to
any
metric.
This
is
just
information
that
I
I
wanted
to
bring
here
all
right
and
finally,
the
user
community
engagement,
user
training
material.
I
mean
again
this
all
ties
back
to
the
formal
user
research
exercise,
because
my
impression
this
only
my
impression
is
probably
that
a
step-by-step
approach
could
be
useful.
I
mean
how
to
get
started
and
how
to
use
this
build
pack
for
a
specific
language.
A
You
already
have
this
in
the
getting
started
guide,
but
probably
we
need
to
connect
it
better
and
also
try
to
have
content
for
those
who
learn.
By
doing
I
wanted
to
propose
build
a
katakura
tutorial,
but
katakura
is
is
being
shoot
down,
so
probably
another
other
alternative
to
have
a
sandbox
environment.
So
folks
can
learn
and
try
out
there
will
be
useful
and
yeah
well.
The
process
for
bug
reports,
file,
feature
request
mainly
needs
the
issue
template
that
it's
already
in
the
works
and
meetings.
A
But
it's
from
what
I
can
see.
It's
mostly
focused
on
contributions,
contributors,
people
willing
to
discuss
rfcs,
I
mean
contributors,
but
we
don't
have
a
meeting
or
a
synchronous
space
for
users
for
folks,
just
adopting
bill
packs
not
interested
on
building
a
new
stack
or
a
new
build
pack
just
trying
to
use
it
instead
of
docker
files
etc.
A
So
in
in
the
story,
I'm
proposing
to
to
have
a
monthly
user
meetup
where
we
could
have
content
specifically
gear
for
adopting
users
and
for
for
them
to
bring
questions,
and
that's
that's
one
of
the
proposals.
I
mean
I'm
not
a
fan
of
a
bunch
of
meetings,
but
certainly
a
a
synchronous
space.
A
I
don't
know
once
per
month
for
users
could
be
helpful.
You
know
previous
r
for
this.
I
I
I
used
to
be
also
part-time
community
manager
for
the
backstage
project
and
they
have
they
have
yeah
contributor,
meetup
and
user
meetup.
It's
totally
different
content
and
yeah.
It's
it's
pretty
useful
for
especially
for
users
to
find
a
space
where
to
ask
questions
directly
to
the
team.
A
So
I
plan
to
put
all
this
all
of
this
into
a
blog
post,
where
you
can
track
the
issues
where
you
can
track
what
we
plan
to
do
with
the
findings
and
in
the
issues
you
can
comment
and
know
that
so
far,
any
question
comment
observation.
C
I
was
just
curious
about
the
the
meeting
she
mentioned
just
now.
I
know
it
was
just
a
proposal,
but
I
wondered
if
there
is
already
evidence
of
folks
who
would
probably
show
up
to
that
kind
of
meeting
or.
D
A
Yeah
well
again,
it's
it's
not
a
formal
research
that
led
me
to
think
this.
I
just
observe
what's
happening
in
the,
for
example,
in
the
slide
channels,
most
of
the
times
is
user
questions
and
and
yeah.
I'm
thought
I'm
fan
of
asynchronous
communication
more
than
synchronous,
but
having
a
yeah
recurring
space,
probably
not
not
so
frequent,
but
a
recurring
space
where
they
can
bring
questions
or
we
can
gather
the
most.
You
know
the
frequently
asked
questions
and
hey.
B
A
How
to
do
this
specific
task
right
now,
where
we
can
also
provide
enablement
and
yeah
learning
for
for
the
user
community
could
be
helpful.
We
will
only
know
this
if
we
do
it,
but
it
could
be
helpful
just
by
observing
most
of
the
interactions
and
slack
channels
which
are
basically
user
questions
so
yeah.
That's
that's
the
source
of
the
idea.
Gotcha
thanks.
A
So
yeah
yeah,
all
this
is
being
put
into
an
into
an
actual
plan,
don't
judge
by
the
timeline
here.
All
these
school
changes
just
is
just
an
estimation
of
of
where
these
improvements
from
the
project
could
land.
A
The
truth
is
that
the
action
plan
that
is
coming
out
of
these
findings
has,
you
know,
has
a
it's
planned
for
for
the
second
half
of
this
year
and
it
will
take
at
least
the
second
half
of
2022
to
execute,
to
observe
and
to
have
a
new
measurement
of
what
is
working,
what
what
which
of
these
ideas
is
working
well
and
on
the
ones
that
are
not
working?
Well,
because
we
do
this
every
six
months,
every
six
months
we
run
an
assessment.
A
All
this
is
most
of
this
is
already
in
in
stories
and
will
be
put
into
single
blog
posts
where
you
can
have
the.
Why
and
how
to
follow
up,
but
yeah.
We
need
your
help.
You
know
all
of
this
cannot
be
done
by
a
single
person.
I
just
can't
do
this
by
myself,
so
we
will
need
your
help
to
run
most
of
these
initiatives
and
also
feel
free
to
say
no
to
correct
me.
If
you
think
some
of
the
ideas
are
totally
nonsense.
A
Just
to
finalize
here
is
the
actual
content
calendar,
not
exactly
a
plan,
but
it's
a
calendar
where
we
have
most
of
the
events
where
pacquiao
will
be
a
good
fit
and
that
have.
A
We
could
be
no
problem.
Okay,
thank
you
cool,
so
yeah,
good
news,
kubecon
north
america
deadline
was
moved
one
week,
so
now
it's
june
3rd,
which
makes
a
lot
of
sense.
So
we
have
some
events
here,
open
source
summit.
Europe
will
be
also
a
really
good
one
and
they
have
a
good
track
of
of
tutorials,
and
so
so
we
can
propose
there
and
we
know
there's
a
big
pocketable
banks
community
in
europe.
A
A
So
we
can
distribute
the
load
again,
distribute
the
the
yeah,
all
the
let's
say
they
work
to
spread
the
the
gospel.
The
word
about
pacquiao
in
different
events
throughout
the
world
and
in
different
communities,
specific
language
communities
like
net
java
and
many
others,
and
there
are
already
some
proposals
being
prepared
and
that's
also
the
same
for
spring
one.
A
There
are
some
some
proposals
already
in
the
works,
so
yeah
I'll
be
following
up
helping
as
much
as
I
can
to
to
coordinate,
to
support
all
the
efforts
to
put
content
out
there
and
make
sure
that
the
community
and
developers
out
there
know
that
pacquiao
will
packs
it's
really
helpful
for
them
and
how
to
use
it
and
yeah.
That's
that's
part
of
the
action
plan
so
far
any
questions
any
concern.
A
B
Would
you
be
able
to
share
the
link
to
the
spreadsheet
that
you
were
just
sharing.