►
From YouTube: 2021 03 08 Docs Office Hours
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
Welcome
to
jenkins
doc's
office
hours,
it's
the
8th
of
march.
Let's
look
at
the
agenda,
so
she
code
africa
contribute
on
coming
in
april.
I
need
some
discussion
site
search,
docs
roadmap
inventory
and
I've
got
one
that
we
may
want
to
take.
A
look
at.
I
haven't
looked
at
the
data
myself,
but
I
owe
the
the
community
a
summary
of
the
contributor
summit
retrospective
for
tomorrow's
governance
meeting.
So
that'd
be
interesting.
It
may
be
worth
looking
at
that
I'll
see.
A
If
I
can
find
it
and
I
I
it
would
be
completely
unvarnished
and
the
danger
is
if
someone
said
something
really
harsh
they
may
not
want
it
recorded.
So
let
me
do
a
quick,
quick
look
just
to
see
if
that's
a
safe
thing
here
we
go
summit
retrospective.
First,
okay,
we've
only
received
11
responses.
So
that's
not
that
many
responses
and
good.
A
A
All
right,
so
the
sheet
code,
africa,
contributes
on
not
much
change
since
last
time.
I
have
not
heard
anything
on
sponsorship
yet
to
finalize
it.
I've
reminded
alyssa
tong
that
that
we're
we're,
depending
on
that
and
I
think
she's
going
to
do
some
further
work
there
to
try
to
get
that
sponsorship.
C
A
I've
got
to
submit
the
the
application
that
will
be
several
days
yet
before
I
do
it
computing
resources.
We
know
about
and
skills
required.
A
What
we
need
now
is
a
separate
document
with
a
list
of
project
ideas
and
mentors
with
project
ideas
and
mentors,
and
on
this
one
mega,
I
think
you're
still
willing
to
be
a
mentor
if
it's
early
in
the
morning,
africa
time.
C
A
A
Right
understood,
so
that's
that's
really.
The
extent
of
that
topic
now
next
topic
for
me
was
site
search,
and
I
haven't
looked
at
the
latest
metrics
because
I
don't
quite
know
how
to
get
to
those
metrics.
But
what
you
can
see
here
here
is
there
really
is
a
search
and
it
works
all
right,
and
so,
when
we
say
pipeline
now,
it's
currently
biased
a
little
bit
towards
the
extension
points.
Documentation
because
there's
so
much
content
in
them,
but
that's
actually
relatively
low
value
to
our
readers.
A
So,
but
you
can
see
that
the
words
appear,
it
finds
them
and
there's
a
tutorial.
Okay,
extending
jenkins.
So
there's
a
developer
tutorial.
If
we
look
at
tutorial
here,
there's
a
tutorials
overview,
so
so
the
the
site
search
is
working
and
it's
much
better
than
not
having
any
site
search.
The
challenge
is
things
like
this
one.
If
I
search
for
get
here,
the
the
results
that
come
back
or
github
are
all
about
the
extension
points,
and
oh,
not
all
about
that's
good.
A
C
A
We
haven't,
and
I
don't
know
that
we
know
how
yet
to
change
the
the
prioritization,
because
those
extension
pages
while
interesting
for
a
developer
are
not
terribly
useful.
It's
they're,
they're
less
interesting,
for
instance,
than
even
the
pipeline
steps
reference.
You
can
see.
Here's
an
example.
Yes,
this
is
an
implement.
An
extension
point
has
no
known
implementations
no
way
should
that
be
top
of
the
page
lists
for
github.
There
are
lots
more
interesting
things
on
this
thing
than
that.
A
A
But
the
algolia
search
is
fast.
It's
the
suggestions
that
they
offer
are
actually
quite
good.
Let's
see
if
we
do
help
yeah,
so
I
mean
you
just
see
they
they
get
it
right
to
you
and
it
appears
in
context.
So
we
just
need
to
find
ways
to
to
tune
which
pages
are
returned
so
that
we
can
say
that
extension
points
are
the
lowest
priority
page
to
return.
A
A
A
A
A
I,
let's
see
like
with
credentials
yeah.
I
don't
think
you'll
find
that
here.
C
A
A
In
the
in
the
body
of
the
page.
A
B
C
A
C
But
it
but
remember
when
I
think
you
filed
something
for
yourself
that
jack
coco
or
whatever,
with
code
coverage
when
you
search
for
code
coverage,
it
didn't
find
it.
So
I
wonder
if
there
is
something
wrong
or
something
weird
about
this,
that
actual
plugins
documentation.
A
I
I
would
be
surprised,
but
let's
see
if
code
coverage
interesting
yeah.
So
there
is
the
there's
the
phrase
code
coverage
report
dot
cover,
but
it's
not
in
the
top
five
chosen
yeah
and
I
I
don't
think,
there's
anything
particularly
wrong
other
than
it's
the
the
changes
that
I'd
submitted
as
a
pull
request
have
not
yet
been
released.
Yeah,
okay,.
C
A
C
C
A
A
B
C
Do
we
yeah
to
see
if,
and
so,
if
I
would,
is
there
something
other
way
I
could
search
for
that
would
put
that
up
at
the
top
and
does
it
sure.
A
A
Let's
see,
what's
the
I
think
it's
called
find
bugs,
let's
see
if
it
exists,
yeah,
oops
nope,
so
fine
bugs
may
have
already
been
how
about?
Let's
just
look
for
the
redeprecated
okay,
so
here's
one
this
plugin
has
been
marked
as
deprecated.
A
A
A
A
A
List
of
the
plugin
for
adoption
on
the
plugin
site,
so
here
it
is,
and
this
oh,
oh
right!
Okay,
it's
looking
for
labels
adopt
this
plugin,
whereas
if
I
type
that
in.
A
A
I
offered
to
adopt
one
just
recently
myself
and
there
are
others
who
have
been
doing
adoption
exercises
or
have
been
offered
to
adopt.
So
yes,
absolutely.
A
I
I
think
the
for
me
at
least
I
think
the
decision
is
done.
This
has
been
such
a
positive
experience.
I
cannot
imagine
us
now.
I
have
not
checked
the
chinese
side.
That's
an
interesting
one
to
check.
Okay,
the
chinese
site
does
not
yet
integrate
the
algolia
search,
and
I
assume
that
they'll
they
may
need
some
additional
help
to
do
that.
Integration.
I
haven't,
I'm
not
skilled
in
chinese,
don't
know
how
to
check
it
so.
A
A
A
C
C
B
A
So
great
okay,
so
I
think
we've
got
that
piece
settled.
It's
assumed
we're
continuing
with
algolia.
C
A
A
A
C
A
I
don't
well,
I
guess:
we've
got
some
possible
approximations
in
the
in
the
google
page
statistics,
but.
C
Not
really,
let
me
I
just
I'm
thinking
about
this
and
at
the
same
time,
of
course,
we
want
to
modularize
our
training
materials,
which
I
have
mixed
feelings
about,
but
it's
obviously
sank
or
saying
projects
always
looking
at
it.
So
I'm
looking
at
our
the
pipeline
materials
right
now
and
I'm
saying
if
I'm
brand
new
to
jenkins
and
I'm
trying
to
write
a
pipeline,
our
training
and
I've
looked
at
the
jenkins
stock
and
it's
pretty
much
the
same
thing.
All
the
pieces
are
there,
but
there's
nothing
that
actually
tells
me
how
to
do
the
content.
C
It's
pretty
good
on
how
you
get
it
configured
and
get
started
with
it,
but
just
to
say
you
know,
you're
going
to
have
a
bunch
of
steps
now,
if
you're,
using
maven
or
gradle,
or
something
maybe
mostly
or
scripts,
that
you've
written
it
may
be
a
bunch
of
sh
or
bat
scripts,
steps
that
just
call
all
this
other
stuff
or
here's.
These
steps
that
interface
with
other
software
and
there's
nothing
that
sort
of
paints
that
big
picture-
and
I
suppose
I
mean
it,
took
me
a
long
time-
I'm
starting
to
see
it
now.
C
But
I've
been
rereading
this
stuff
for
three
years
and
it's
like
pedagogically,
I'm
realizing.
We
just
a
few
quick
sentences
might
guide
their
brains
faster,
but
then
it
may
be
that
if
I'm
the
sort
of
person
who
knows
enough
to
do
a
pipeline
that
this
is
all
just
obvious,
I
have
the
reference,
but
you
know,
but
we
don't
we
sort
of
say
well,
here's
the
steps
reference,
but
I
even
I
went
back
and
noticed
like
at
the
very
beginning
we
say
junit
and
we
don't
actually
hit
them
over
the
head.
C
Junit
jun,
it's
a
third
party,
it's
some
other
software
and
there
is
a
plug-in
for
junit
in
june.
It
you
get
all
this
stuff
and
links
to
it.
You
know,
let's
go
look
at
it
and
now,
let's
call
it
with
blue
ocean
etc.
C
So
I
don't
know
if
we
need
that,
and
I
mean
for
the
training,
I
think
we
definitely
need
it
if
they're
bothering
to
train
we'll,
take
them,
but
from
the
documentation.
Do
we
and
there's
all
those
tutorials,
but
those
are
all
very
sort
of
specific
cases
and
again
I'm
not
seeing
the
big
picture
of
you
know
here's
steps
and
can
I
know
darren's
made
a
lot
of
passing
like
when
you're
talking
about
conversions.
A
C
So
I
don't
know
if
there
is,
if
there
is
work
to
be
done
on
that
or
if
that's
just
the
anal
retentive
writer,
who
doesn't
know
enough
to
recognize
that
what
we
have
is
brilliant,
so
so
there.
But
I
do
have
that
thought
and
and
another
one
that
I'm
feeling-
and
this
is
both
for
me-
for
the
training
in
this.
A
C
It's
one
of
those
things
where
they
do
kind
of
intertwine,
rather
a
lot,
because
I,
if
I'm
a
pipeline
developer,
it
may
be
that
I'm
going
to
tell
my
administrator
to
set
me
up
some
agents
that
have
these
capabilities
and
put
a
label
on
it
and
I'm
just
going
to
call
those
or
it
may
be
that
in
my
pipeline.
I
want
to
call
docker
and
tell
it
what
to
put
in
mine
or
whatever.
C
But
I
see
nothing
that
puts
that
all
together,
I'm
still
trying
to
figure
out
all
of
it
and
that
there
are
all
these
different
types
of
agents,
all
that
work,
but
different
pros
and
cons
and
ease
and
complexity
and
who
and
then
permissions
who
do
you
want
to
be
able
to
create
and
destroy
agents
and
kubernetes
agents
versus
docker
agents?
And
I
don't
know
if
that's
a
project,
because
I'm
sort
of
you
know
trial,
ballooning
here
and
you
know
once
again
parasitic
on
your
brain.
C
C
A
C
C
A
Good,
thank
you
yeah,
so
I
don't.
I
don't
have
any
any
great
insights
that
I
think
you're
right
it
would
be.
It
would
be
wonderful
to
have
links
from
inside
those
pipeline.
Step
pages
to
the
thing
that
they
are
supporting.
Your
example
with
junit
is
okay
here
is
here,
is
a
link
to
the
junit,
a
good
junit
tutorial
that
will
take
you
through
things
related
to
unit
testing
in
java,
right
and
and
oh
you're
doing
coverage.
Now
here's
a
link
to
a
somebody
else's
tutorial
on
coverage
and
oh
you're,
reporting
coverage.
C
A
C
Tutorials
is
just
something:
well,
I
don't
see
anything
in
jenkin
I
mean
I've
got
my
little
soapbox
sermonette
in
jenkins,
fundamentals,
which
I
think
nobody's
reading,
but
about
how
important
testing
is
in
all
the
different
levels,
but
I
don't
mention
test
code
coverage.
C
C
User
testing,
which
you
can't
really
automate,
but
even
something
like
you
know
all
of
this
stuff,
I
don't
mention
code
coverage
and
even
even
something
that
briefly
says
you
want
to
test
for
code
code.
You
want
to
check
for
your
code
coverage
and
here's
here
are
the
plugins
that
can
do
that
here
or
even
just
you
know,
a
list
of
plugins.
If
you're
trying
to
improve
your
testing,
here's
some
things
that
might
help
you
there's
like
sort
of
none
of
that
put
together
material.
It's
all
there.
A
C
And
that's
because
I
you
know
busted
myself
after
writing,
that
about
how
you
need
to
do
all
this
different
testing,
then
the
sample
the
simple
pipeline
they
start
out
with
is
build
test,
deploy
right,
so
we're
not
reinforcing
that
and
I
you
know
it
really
should
have
several
test
stages
to
it.
Right.
A
C
Right,
yes,
if
it
passed
yeah,
I
I
can
remember
we
used
to
like
take
junior
people
and
they
who'd
you
and
then
we'd
give
them
a
code
review
with
one
of
the
really
good
people
and
some
of
them
would
walk
out.
I
would
say:
that's
a
total
waste
of
time.
It
builds
if
there's
no
compiler
errors.
You
know
why
do
I
have
to
worry
about
all
this
crap
others
would
come
out
and
say
I
will
take
any
assignment.
That
lets
me
work
more
with
this
person.
C
I
want
to
know
what
he
knows
and
those
are
the
people
we
kept.
Obviously,
but
I
think
there's
just
little
things
that
we
could
do
to
reinforce.
We
really
mean
this,
you
know
or
to
start
to
see
the
you
know
things
like
well,
there
may
be
when
you
deploy
it
to
a
staging,
you
might
have
separate
tests
that
you
would
run
on
the
staging
server.
A
C
A
Well,
and-
and
there
are
really
cool
additive
stories
right-
there's
the
hey-
we're
gonna
do
build
test,
deploy
build
test.
Deploy
is
great,
that's
that's
really
great,
but
now
you
may
be
in
an
environment
where
the
test
phase
is
becoming
too
long
and
you
or
or
you
have
production,
specific
tests
or
staging
specific
tests.
How
do
you
do
that?
Oh,
what?
If
I
need
to
test
web
pages
using
using
selenium
okay?
A
C
A
C
Have
a
very
evocular
commentary
that
goes
down
them
about,
what's
done
there
and
why
it's
done,
and
you
could
instead
do
it
this
way,
but
that
would
have
the
following
drawbacks
or
or
even
say
a
better
way
of
doing.
This
might
be
right,
but,
and
that
might
be
in
terms
of
our
audience,
that
might
be
a
better
learning
path.
If
we
could,
you
know
if
there
was
a
way
to
make
it,
so
it
was
very
nice
and
readable.
A
Right
so
things
like
this,
where
we
say
hey
here's
this
thing:
yes,
it's
public,
but
you
know
it
works,
and
this
is
how
it
feels,
or
you
had
asked
about
plug-in
adoption.
So
I
had
just
adopted
this
one
elastic
axis
plug-in.
I
think
there
we
go
so
here
it
is.
I
just
adopted
this
one
and
here
are
its
tests.
All
84
of
them
here
are
the
artifacts
it
created
built
here
are
the
changes
that
came
in
this
one
was
a
change
from
daniel
and
if
we
look
at
the
poll
requests
I
mean
it's.
A
A
Nothing
wrong
with
it
if,
in
this
case,
the
way
the
jenkins
project
thinks
about
it
is
is
the
build
phase,
is
run
maven,
clean
verify
and
what
maven
thinks
about
is
when
I'm,
when
I
run
verify.
I
run
all
of
the
pieces
of
that
that
preceded
that
step,
and
that
includes
all
the
testing
everything
so
this
this
is
well
suited.
This
particular
structure
is
well
suited
to
maven
projects,
because
the
build
thing
just
says,
verify
and
verify
runs,
for
instance,
the
coverage
report,
and
it
runs
so.
A
C
A
A
A
Yeah,
so
now
now
this
one
does
this:
this
pipeline
definition
still
has
a
weakness
in
that
it
does
not
show
some
of
the
cool
information
that's
already
included
here.
It
mentioned
coverage
and
here's
the
coverage
report,
but
the
pipeline
definition
or
the
the
blue
ocean
interface
is
not
showing
that
coverage
report.
A
B
C
A
C
A
Well,
the
make
is
a
good
good
choice
there
with
make
we've
got.
We've
got
examples
that
we,
where
we
use
make
in
the
jenkins
project
actually
like
the
docker
images,
are
built
with
make
and
and
those
docker
images,
let's
see
if
we
can
find
them
the
main
using
make
to
build
the
docker
image
is
actually
quite
effective.
It
works
really
well
because
we're
not
doing
anything.
That's
java,
specific,
so
maven's,
not
a
great
choice.
C
A
And
so
using
a
docker
image
or
or
here
the
another
example
for
you
and
me
jenkins.io,
the
page
generation
of
the
creation
of
our
website
is
done
with
make
all
right.
And
so,
when
we
look
at
this
thing
in
blue
ocean,
we'll
see
a
clean,
a
check
out
a
build,
an
archive
and
in
the
build
what
you'll
see
is
make
make.
B
A
A
C
A
A
Right
this,
this
one
is
if,
if,
if
I
were
building
some
c
code-
and
I
didn't
have
any
tests
running
I'd-
be
worried
right
because
that's
that's
scary,
yeah.
If
I'm
compiling
code
to
put
into
an
embedded
device
or
compiling
code
to
include
into
a
product
I'm
shipping,
I
want
some
tests
that
tell
me
that
it's
working.
C
Right
I've
got,
I
haven't
gotten
deep.
I
still
don't
know
what
I'm
doing,
but
tammy
and
ben
walding
have
got
when
when
you
build
this
stuff
into
antora
there's
the
actual
test
you
know
doesn't
build
and
stuff
and
then
they've
got
all
these
recommendations
and
they
are
testing
for
all
sorts
of
stuff
in
the
docs.
C
That
is
right
now
it's
sort
of
a
pain
in
the
butt
but
like
they're
using
sentence
case
for
the
titles.
I
think
they
test
for
that
yeah
and
they're
testing.
If
they
get
anything
that
looks
like
it
should
be
an
abbreviation
but
can't
resolve
you
know
so
you
get
it
doesn't
stop.
It
doesn't
break
your
build,
but
it's
doing
a
lot
more
documentation,
testing
stuff.
It's
kind
of
interesting.
A
C
A
Static
analysis
is,
is
commonly
used
for
things
like
well
in
in
the
in
the
in
the
java
world.
Static
analysis
is
done,
oops
wrong,
one
in
the
java
world
static
analysis
is
done
with
things
like
spot
bugs,
where
what
it
does
is
it
will
look
at
the
generated
byte
code
and
and
give
hints
hey
there.
Are
this
many
warnings
from
spot
bugs?
So
here?
A
If
I
look
this
one,
it
looks
like
it's
not
showing
me
the
spot,
bugs
output.
So
let
me
use
a
different,
a
different
jenkins
instance,
but
here
let's
look
at
this
one
where
we
see
here
notice,
this
one
has
check
style
warnings.
A
Yes,
here
we
go
check
style,
java,
spot
bugs
warnings,
and
it
tells
me
hey.
There
are
none
in
this
build
and
it
ran
them
and
I
could
okay,
I
work
hard
to
keep
no
warnings
here.
Let's
look
at
one
that
has
a
bunch
of
warnings,
and
this
lets
me
navigate
with
the
warnings
ng
plug-in
to
see
types
of
issues,
categories
of
issues-
so
hey
there
are
this
many.
C
A
C
A
Right
right
I
mean
there's,
there's
an,
although
I
I
think
there,
the
the
danger
is,
and
it
probably
highlights
we
should
reconsider
something
like
liam
newman's
pipeline
minute,
videos
right
or
jenkins,
minute
videos
where
a
two-minute.
A
A
And,
oh,
this
is
possible
and
it's
possible
with
these
steps,
and
then
they
go
looking.
How
do
I
get
there
and
right?
This
is
a
good
example
of
wow.
How
do
I,
how
do
I
add
check
style,
checking
to
my
project?
How
do
I
add
other
forms
of
of
of
checks
like
coverage
reporting?
Okay,
this
one
is
one
that
I
use
because
it
helps
me
see.
C
A
That
would
be
a
very
good
thing
for
somebody
to
have
for
code
review
right
right.
This
is
it's
a
good
help.
It
really
is
it's
it's
much
more
convenient
to
be
able
to
say,
hey
which
statements
have
I
missed,
maybe
they're
not
important,
and
I
don't
need
to
test
them
with
automation,
but
if,
if
I
can
test
them
with
automation-
and
they
are
important-
it's
good
to
know.
C
A
A
C
A
C
But
let's
take
a
step
up
from
there
figuring
out
that
there
are
30
different
things
that
I
might
be
looking
for
to
test
my
code
and
here's
the
tools
that
you
can
use
to
help.
Here's
what
they
mean
even
give
me
a
number.
I
mean
if,
if
I'm
testing
30
of
my
code,
how
confident
am
I
that
it's
good
right.
C
I
mean
obviously,
if
it's
100
but
and
they're
good
tests,
the
if
I'm
used
now
do
I
need
to
do
code
coverage
if
I'm
building
with
maven.
A
A
C
A
Right
and,
and
that
big
picture
is,
is
a
software
education
right,
the
big
picture,
certainly
it's
it's
very
valuable
for
us
to
share
hey
here's,
here's
how
you
do
code
coverage.
Why
should
you
do
code
coverage
and
what
are
the
compromises
that
you're
making?
If
you
choose
to
report
coverage
and
care
about
it,
those
those
are
are,
I
think,
higher
level
concepts
than
we're
particularly
ready
to
dig
too
much
into.
C
A
C
C
C
Or
something
I
don't
know,
or
even
I
mean
I
can
almost
envision
a
team
project
and
it
might
even
be
for
your.
She
codes
africa
because
I
think
they're
working
together
closely
and
they
are
they're
they're,
not
as
interested
in
the
strict
content
of
the
documentation.
I
suspect,
probably
not
right,
but
for
a
group
of
them
together
to
work
and
get
this
sort
of
put
some
glue
on
all
the
testing
material.
C
Yeah,
I
don't
know
that
idea
because,
as
I
say
there,
you're
sitting
here
and
there's
like
I
didn't
know
that
was
there,
but
that's
good,
that's
good!
You
know
if
I
knew
to
look
there.
C
If
I
don't
even
I'm
not
positive,
I
know
what
check
style
is
for,
but
if
I
knew
I
needed
a
check
style
and
I
looked
at
that,
it
all
starts
to
fall
in
place.
I'm
kidding
because
what
I
think
what
I
think
is
that
we
have
an
awful
lot
of
facilities
in
jenkins
that
are
under
utilized,
because
people
don't
know
about
them
right.
C
So
yeah
and
again
with
agents,
I
suspect
that
most
people
early
on
figure
out
one
way
to
do
agents
and
they
do
everything
in
their
shop.
That
way,
you
know
they
never.
I
mean,
I
think.
If
you
know
say
you
have
a
big
shop
with
lots
and
lots
of
projects.
You
probably
need
different
types
of
agents.
You
know
some,
you
want
static.
Some.
You
want
ephemeral
right,
you
know
some,
you
want
to
be
docker,
maybe
some
you
don't
want.
I
don't
know,
maybe
everything
should
be
docker
and
then
there's
the
kubernetes
wrinkle
and.
A
C
Exactly
and
there's
no
easy
way
for
me
to
see
these
are
all
my
options
and
at
a
high
level,
these
are
the
pros
and
cons
of
each
one,
and
I.
C
C
Get
tainted
but
there's
no
place
else.
That's
saying
what
the
advantage
of
it's
implied
in
a
couple
of
places,
because
if
you
keep
re-running
the
same
pipeline
on
the
same
agent,
you're
going
to
pick
up
a
lot
of
performance
because
it
doesn't
have
to
rebuild
everything.
A
Right,
yep,
the
caching,
you
know
the
caching
impacts
can
be
quite
positive.
Yeah.
C
Yeah
even
questions
about,
let
you
know,
let's
say
I
can
run
agents
either
on
docker
on
regular
cards
or
kubernetes.
What
kind
of
agent
is
better
on
each?
What
are
the
advantages
of
kubernetes
agents
over
docker
agents.
A
Right
and
yes,
and
and
that's
well
and
to
to
take
the
counter,
how
do
you
overcome?
How
do
you
best
tune
for
or
overcome
any
limitations?
Yes,
kubernetes
kubernetes
agents
and
docker
agents,
biased
towards
being
ephemeral,
but
maven
and
java
builds
really
benefit
highly
from
a
local
cache
of
of
dependencies.
A
A
A
C
A
A
What
was
your
overall
impression
with
one
being
worst
and
five
being
best
and
six
of
ten
gave
us
five.
Four
of
four
of
ten
gave
us
four.
So
between
the
fours
and
the
fives
we've
we
were
well
perceived
right
then,
which
thing
was
which
thing
was
most
attended
by
the
people
who
responded
was
the
opening
session
second
place
the
closing
session?
Okay,
those
are
good
that
says
that
they
didn't.
A
They
didn't
join
us
and
then
not
come
back
three
of
them,
weren't
able
to
attend,
closing
the
attended
opening,
but
then
tracks
good
and
good
involvement,
and
then
key
highlights
so,
which
session
was
most
valuable
in
this
case,
opening
session
was
most
valuable
closing
session.
Second,
okay,
that's
good.
C
A
A
Oh
right
and
and
that's
true-
and
I
that's
a
good
piece
of
data
that
I
can
actually
gather,
is
go
look
at
the
view
counts
on
our
session
recordings,
because
we've
got
that
data
in
in
the
youtube
account.
That's
a
good
one
I'll
do
that.
Thank
you
for
suggesting
it,
because
the
contributor
summit
playlist
has
all
of
the
videos
in
it.
For
instance,
170
views
of
the
opening
session,
which
is
not
bad
whoa.
A
To
the
survey
but
170
views
of
the
opening
session
is
pretty
good,
so
that's
not
a
not
a
bad
thing.
You
know
it's,
it's
not
as
good
as
some
of
our
other
videos,
like
the
the
video
that
we've
embedded
on
the
jenkins
website
on
the
top
level
page.
A
That
one
is,
has
17
000
views
since
december
11th
when
we
uploaded
it
so
so
we
clearly
are
not
over
achieving
in
terms
of
number
of
people
who
are
watching
our
our
recordings
of
status
sessions.
C
Right
but
but
it's
also,
you
know
it's
a
smaller
unit
that
are
interested
in
the
status
too.
That's
right,
so
cool,
okay,
you
were
gonna,
go,
go,
go.