►
From YouTube: Jenkins Advocacy and Outreach SIG for 2020 04 09
Description
Discussed CDF Ambassador program, the Jenkins comic strip, Jenkins Roadmap, and onoing efforts with LinkedIn social account
A
B
B
So
if
folks
do
have
specific
agenda
items
which
you'd
like
to
discuss,
please
let
me
know
otherwise:
Alissa
has
gone
ahead
and
put
one
item
in
there,
but
I'm
not
sure
she's
able
to
attend
and
yeah
we'll
go
ahead
and
look
at
past
actions.
So,
first
of
all
any
pressing
issues.
People
would
like
to
use
this
time
to
discuss
a
focus
on
I.
Don't.
A
Have
a
pressing
issue:
I
do
have
an
update
on
two
items.
Baking,
though
at
the
end
or
I
can
do
them
now.
What
are
the
topics?
The
first
topic
is
in
regards
to
the
documentation
for
describing
the
voucher
use
and
distribution.
I
have
not
completed
that.
That
is
on
my
list
to
do.
Okay,
let's
work
is
just
drown
me
a
little
bit
this
week
and
secondly,
there
is
a
CDF
ambassador,
update,
I
thought.
I'd
just
update
the
team
about
Oh
actually.
B
B
This
one
is
still
to
do.
That's
fine.
The
zoom
accounts
I'll
put
a
note
that
I
have
done
some,
it's
kind
of
a
done
inner
to
do.
Let's
say:
ongoing
Tracy
highlighted
zoom
problem,
stay
working
with
CDF
ticket
solution
and
will
say
mark
to
find
a
meeting
which
only
works
until
mark
can
attend.
A
meeting.
I
guess
mark
will
always
be
there
right,
I'm,
just
looking
for
other
to
dues
and
ji-suk
I
believe
the
Jenkins
XD
suck.
This
action
here
was
resolved.
B
I
understand
there
was
a
discussion
last
Friday
and
things
are
resolved
and
it's
all
very
positive,
and
actually
we've
got
a
bunch
of
people
stepping
forward
to
be
support
mentors.
So
that's
good,
okay,
I'm
gonna
leave
that
there
for
to
do
certainly
the
ones
I
could
pick
out
easily
okay.
So
let's
go
on
to
the
topic
of
CDF
ambassadors
and
Maki.
A
B
A
B
Perfect,
so
just
going
back
to
the
Ambassador
Program
I
believe
there
was
also
a
review
of
the
cdf
program.
We
jackie
invited
a
number
of
project
folks
from
spinnaker
and
screwdriver
and
jenkins
and
other
projects
to
just
review
the
outline
for
the
ambassador
program.
One
of
the
things
that
will
come
out
of
that
is
will
have
a
github
repository
set
up
similar
to
CN
CF,
which
will
outline
the
the
process
for
ambassadors.
You
know
how
often
they
do
them,
how
which
people
they're
looking
for
all
the
kind
of
nitty-gritty
process
around
that.
B
And
the
other
thing
we
talked
about
was
making
sure
that
this
ambassador
program
run
by
CDF
is
becomes
the
successor
to
the
Jenkins
Ambassador
Program
and
specifically,
we
sort
of
said
you
know,
if
any
project
from
the
CDF
ambassadors
from
the
whole
pool.
If
there's
a
subgroup
of
those
people
who
we
consider
experts
in
Jenkins,
then
that
list
of
people
would
go
to
the
Jenkins
board.
B
They
would
give
a
thumbs-up
and
then
sort
of
annoying
them
with
the
the
Jenkins
status
as
such,
and
then
they
would
have
special
benefits,
perhaps
in
the
Jenkins
community,
which
would
be
being
invited
to
specific
meetings
or
when
we
go
back
to
having
events
trying
to
get
them
passes
or
discounts
or
whatever
in
inviting
them
as
speakers.
So
it
would
just
be
like
an
extra
level
and
then,
similarly,
you
could
do
the
same
for
Tecton
or
you
could
do
the
same
for
spinnaker.
B
So
I
think
the
next
action
there
is
to
get
that
list
from
CDF
to
the
Jenkins
board
and
just
have
them
officially
sort
of
say
this
is
good
and
then
just
communicate
to
the
Jenkins
community.
Hey
remember
that
ambassador
program:
this
is
now
the
set
of
Jenkins
ambassadors,
and
maybe
we
could
do
some
publicity
around
that
some
blog
posts-
yes,
some
tweets.
So
what?
If
folks
think
about
any
communication,
we
need
to
do
in
that
front.
I.
A
B
Okay,
yeah.
That
sounds
good.
So
let's
leave
this
as
an
ongoing
topic
for
these
meetings.
Let's
say
the
next
step
is
I'm
working
with
Jackie
and
the
project
outreach
at
CDF
to
get
some
of
the
the
repos
and
some
more
things
set
up
and
then
maybe
in
a
couple
of
weeks
there
should
be
enough
sort
of
public
links
and
things
that
we
can
then
put
together
that
blog
post
and
just
talk
about
how
this
is
going
to
be
the
the
new
program.
B
Yeah,
so
I
can
show
you
what's
there
now,
so
there's
a
repo,
and
it
is
at
the
moment
we're
still
focused
on
the
newsletter
I.
Don't
think,
we've
broken
that
out
into
more
things.
So
that's
still
the
intention,
but
the
newsletter
page
here
captures
the
the
topics.
So
actually
this
month
we
bumped
the
names
of
the
months
at
this
month
in
April
were
collecting
interoperability.
B
I
would
very
much
so
so
if
you
like,
a
very
beginning
thing
propose
a
talk
on
something
ml,
ops
and
Jenkins,
and
then
we
can
start
also
pulling
deciding
I,
think
Jackie's
pull
together
a
webinar
or
a
crowd
chat,
which
would
be
a
set
of
experts
or
kind
of
people
who
could
lead.
It's
not
experts,
actually
the
opposite
of
experts
but
knowledgeable
folks,
who
could
lead
a
discussion
and
engage
people
to
do
some
peer
to
peer
sharing?
B
C
B
B
B
B
C
B
B
D
Yeah,
it
was
just
to
say
that
Oleg
has
done
a
brilliant
job
of
this
is
me
being
a
poor
approximation
for
Oleg.
Summary
he's
done
a
brilliant
job
of
collecting
and
presenting
roadmap
ideas
here
in
this
draft
of
the
roadmap
on
Jenkins
that
I.
Oh,
it's
reachable
through
the
governance
and
structure
link
at
the
bottom
of
the
page.
One
of
the
pages
from
that
page
is
the
roadmap.
D
So
you
pick
structure
and
governance
in
the
the
in
the
under
the
project
column
at
the
very
bottom
there
in
structuring
governance,
it's
not
yet
on
the
jumbotron
I
think
we'd
want
some
more
time
to
refine
and
evolve,
but
before
we
highlight
that
it's
to
a
much
broader
audience
right
now,
it's
just
a
very,
very
good,
working
working
prototype,
showing
evolution
and
thought
processes.
We
got
lots
of
people
contributing
in
many
different
ways
right.
B
How
would
you
use
it?
What
are
the
pros
and
cons
of
each
platform
and
then
building
on
that
saying?
Can
we
offer
them
platforms
to
use
for
free?
So
maybe
people
don't
have
to
pay
for
them?
Can
we
figure
out
the
zoom
thing?
Make
that
accessible
or
even
put
platforms
like
crowdcast?
Can
we
share
them
in
some
way,
and
you
know
just
try
and
help
with
the
heavy
lifting,
so
folks
can
focus
on
the
content
and
focus
on
the
people.
B
So
we
might
see
some
more
from
CDF
I
think
either
a
webinar
about
it
or
a
general
meter
with
meetup
organizers
to
do
a
joint
brainstorm
and
possibly
get
some
folks
who
are
really
doing
this
in
a
very
top-notch
way
to
come
along
and
help
like
with
advance
streaming
stuff
and
I'm
hearing
like
we're
getting
into
gamer
level,
goodness
stuff
that
we
could
potentially
do
that
could
be
pretty
exciting.
I
went
along
I
think
the
cloud
native
had
a
recent
virtual
event
and
they
had
some
pretty
slick
things
happening
there,
so
they.
A
A
B
B
D
All
like
reactivated
the
Jenkins
or
gained
control
of
the
Jenkins
LinkedIn
account,
and
as
part
of
that,
we
decided
hey.
Let's
try
an
experiment,
so
I
wrote
an
article
on
LinkedIn
haven't
written
one
of
those
I
think
in
a
very
long
time,
and
it
was
inviting
people
to
come
help
mentor
with
the
get
plugin
in
google
Summer
of
Code.
The
the
article
had
87
views,
not
a
huge
volume,
but
some
views
and
lots
of
interesting
traction
on
Twitter
thanks
to
O'lakes,
having
shared
it
on
LinkedIn,
so
did
I
get
what
I
ultimately
wanted.
B
B
Okay,
so
that
reminds
me
I'm
going
to
add
another
item
here,
which
is
we
talked
about
the
Twitter
calendar
I
think
we
had
a
bit
of
this
in
the
mailing
list,
so
I
had
this
talk
and
I
didn't
know
if
we
did
want
to
update
it,
to
use
it
as
a
way
to
schedule,
schedule
tweets
and
in
until
we
get
our
fall
kind
of
Doc's
as
tweets,
but
a
way
to
be
aware
of
what
other
people
are
scheduling
a
right
overlap,
but
when
I
had
originally
planned,
it
I
think
I
had
this
idea
that
you
know
in
a
build-up
to
an
event
or
for
big
news.
B
You
might
want
the
tweets
to
go
out
three
or
four
times
across
a
couple
of
months,
so
I
would
just
copy
it
and
I'd
paste
it
across
different
dates
and
say
here
here
here
and
here
we're
gonna
have
that
and
then
just
to
make
sure
other
people
weren't
doing
the
same
thing.
I
thought
that
was
a
way
to
avoid
clashing.
So
what,
if
folks
think
do
we
want
to
use
this?
Is
it
too
heavy
way?
Should
we
just
I.
D
So
my
problem
is
I'm,
I'm,
really
fine,
I'm
fine,
it's
seeing
this,
but
really
terrible
it
actually
actively
using
and
implementing
it.
It
will
do
me
no
harm,
but
I
tend
rather
to
periodically
just
go
in
and
and
retweet
something
from
the
Jenkins
account
that
I
think
makes
sense
or
after
a
discussion.
So
so
this
looks
great
to
me.
Unfortunately,
my
past
behavior
shows,
while
it
looks
great
I-
probably
won't
do
a
lot
with
it.
Yeah
yeah.
B
I
wouldn't
expect
people
if
you're
just
retweeting,
really
good
tweets
I,
wouldn't
expect
you
to
necessarily
put
them
in,
but
I
think
this
is
more
hey.
I've
got
this
plan.
I
want
to
promote
this
specific
thing,
like
let's
say
we
throw
in
the
road
map
like
how
many
times
we
could
talk
about
the
road
map
repeatedly.
So
maybe
we
think
once
and
we
schedule
it
well.
D
A
Think
we
should
change
our
habits
in
in
what
I
think
you're
saying
mark
and
please
correct
me
if
I'm
wrong,
I,
don't
think
we
should
change
our
habits
in
the
sense
of
if
we
know
there's
good
content
or
you
know
if,
if
Mark
you
tweet,
something
out
that
you
know
is
good
and
you
want
it
to
be
retweeted
from
the
Jenkins
account
I.
Don't
think
we
need
to
schedule
things
like
that.
I
think
those
are
definitely
good
to
keep
going
and
I.
A
B
B
I'm
gonna
create
this
one
for
the
next
three
months.
I
encourage
folks
to
go
in
and
put
tweets
in,
but
what
we
could
do
also
is
every
advocacy
and
outreach
sig.
We
could
do
a
quick
review
of
it
and
we
could
say:
hey
all
these
cool
things,
let's
share
Jolene
tweets
and
then
so
we
are
all
looking
at
it
at
these
meetings,
then,
maybe
that's
just
a
nice
way
to
get
some
eyes
on
it
and
make
sure
we're
not
flashing
or
we're
not
kind
of
just
doing
anything.
We
shouldn't
be
with
respect
to
each
other.
B
Yeah
I
think
that's
a
great
idea.
Okay,
so
let's
just
fill
this
out
all
the
way
through
to
end
of
June,
which
is
so
yeah.
If
anyone
wants
to
go
put
in
tweets
and
then
duplicate
them,
and
then
you
can
see
whether
they've
been
posted
or
scheduled,
please
go
ahead
and
do
that
and
I
might
do
a
few
on
the
roadmap.