►
Description
Pipeline-Authoring Sig Weekly Meeting for February 28, 2020
Agenda:
- Continued work on personas (action items assigned)
- Open items
A
Hello,
everybody.
This
is
the
Jenkins
pipeline
authoring
sync
meeting
for
February
28
2020.
This
is
the
Americas
meeting.
My
name
is
Mark
E
welcome
everybody.
I
am
going
to
drop
a
lazy
link
to
the
notes.
If
you
could
just
go
in
there
and
add
who
you
are
so
we
just
keep
a
record
of
attendance.
I've
also
put
that
in
the
getter
channel.
A
B
B
Alrighty,
so
let's
see
your
last
time,
actually
you
don't
have
to
do
and
just
have
people
can
say
their
names
and
say
hello,
I,
I
will
start
off
and
I
actually
know
I'll
just
introduce
a
couple.
People
that
to
start
with
Devon
and
Karl
are
here
from
cloud
peas.
We
work
together
on
the
pipeline
team
at
cloud
bees,
so
they're
also
joining
us
today
and
Mark
is
back
again
also
here
from
doing
evangelism.
Now
right.
B
B
B
E
B
So
last
time
we
were
talking
about
personas
and
looking
at
what
we
were
going
to
how
they
could
help
us
focus
our
next
steps.
We
were
gonna
take
some
time
to
look
over
the
five
personas
that
we
had
and
see
what
we
could
glean
from
them
and
map
them
to
mark
Mark
II
was
talking
about
mapping
them
to
the
McTeer
doc.
C
B
D
B
A
A
Did
not
get
a
chance.
I
also
have
another
action
item
so
I'm
in
our
in
the
zoom
chat.
I
put
a
link
to
the
maturity
model,
as
well
as
to
the
personas
doc.
I
have
two
action:
ID
three
action
items
I
believe
I
need
to
add
my
questions.
Cuz
they're,
not
there
I
needed
to
also
do
the
mapping
to
the
maturity
model
and
I
have
the
comms
that
I'm
still
working
on.
So
we
last
talked
oh.
A
Blog
post
email
to
the
cig
mailing
list
about
what
we're
up
to
that
way.
We
can
keep
sort
of
generate
and
a
Twitter
post,
so
we
can
generate
more
buzz
and
see
if
people
want
to
come
and
join
so
I
have
started
that
drought
I
will
probably
be
able
to
share
it
with
the
team,
because
I
do
want
to
have
everybody's
input
and
buy-in
before
we
send
that
out.
A
So
I
will
have
that
probably
out
I
would
say
by
let's
say
by
Monday,
definitely
before
our
next
meeting,
because
what
I
would
like
to
do
is
finalize
that
on
our
next
meeting
and
everybody
gives
a
+1
to
it
and
then
we
get
that
sent
out.
I
will
be
full
transparency
on
why
I
was
doing
that
going
through
meeting
a
bunch
of
people.
The
last
week
and
a
half
I
have
been
stabbed.
Solutely
swamped,
oh
yeah,.
B
A
A
B
A
Do
think
before
we
move
any
further,
we
need
to
close
this
out.
I
think
yeah,
yeah
I,
don't
want
to
spend
a
lot
of
time
like
I.
Think
we've
spent
the
last
two
or
three
meetings
sort
of
going
over
and
that's
all
super
good,
but
I
do
think
we
need
to
close
this
portion
out
or
at
least
get
the
MVP
zero
out
into
the
world.
Yeah.
B
Well,
the
point
of
this
is
that
we
have
a
partly
it's
that
we
have
a
focusing,
but
also
so
that
we're
so
that
we
all
have
a
common
base
from
which
to
discuss
right.
So
the
word
is
that
we're
talking
from
the
same
talking
the
same
language,
and
so
if
we
we
could
sit
around
for
for
another
couple
weeks,
figuring
out
our
language
and
it
doesn't
necessarily
get
us
anywhere.
So
exactly.
B
A
B
A
A
B
Post
the
I
think
the
person
who's
most
interested
I
heard
the
most
from
is
Oleg,
so
I
think
we
should
probably
just
post
the
action
item
in
the
and
and
the
link
to
the
personas
in
the
Gator
channel,
so
that
people
can
work
asynchronously
so
that,
basically,
we
can
be
in
the
process
of
closing
this.
By
that
the
time
the
the
EMEA
meaning
rolls
around
and
then
really
close
it
on
the
next
day,
so
that
that
so
that
it
won't
hit
the
round
ground
running
from
there.
So.
A
B
B
B
B
There's
that
alright
comms
Marquis
email
end
of
day
day,
I
guess
I
should
ask
if
people
that
are
joining
us
had
any
specific
topics
that
they
wanted
to
bring
up
today
or
if
you're
just
joining
to
be
part
of
the
discussion
and
anything
do
that
anything
that
was
old
business.
We
have
a
couple
action
that
isn't
there
is
there
a
new
new
business.
B
C
B
B
A
D
B
B
Cool
so
potentially
mentors
for
anyone
that
isn't
already
familiar
with
us.
The
idea
here
is
to
instead
of
having
pipeline-
and
this
is
just
declarative,
pipeline
right-
sure,
right
yeah-
for
declare
of
pipeline
instead
of
doing
it
in
groovy
having
a
Hamel
version
of
it,
Emel
syntax
that
up
to
at
least
up
to
a
certain
point,
is
y
mo
and
then
as
some
Groody
in
some
spot,
because
eventually
you
have
there's
evaluations
that
are
gonna
require
groovy.
But
the
question
is
how
much
we'll
see
I.
A
D
B
B
D
C
December
we
had
a
webinar
with
with
folks
from
t-mobile
who
presented
their
poet
framework.
That
does
basically,
this
kind
of
thing
with
pipeline
is
Djamel
and
then
in
January
we
had
a
webinar
with
the
people
from
oh
dear.
How
embarrassing
Booz
Allen
Hamilton,
who
have
an
alternate
technique
for
doing
pipeline,
is
yeah
Mille,
where
they
have
much
higher
level
concepts.
It's
not
just
pipeline.
As
ya
know,
they've
got
a
much
much
bigger
concept
that
both
of
those
are
using,
but
don't
don't
forget
them.
Yeah.
B
Mark
could
you
you
just
mentioned
those
two:
could
you
post
the
paste
the
links
in
under
the
related
presentations
here,
I
will
just
cuz
I
think
anyone
that's
wanting
to
get
familiar
with
kind
of
the
technology
in
this
area
would
want
to
take
a
look
at
that
thanks
a
lot
and
there
there
is
an
IDE
tools.
Jeff
I
see
a
vyas
code.
I
do
yeah.
C
Well,
so
so
there
was
a
there
was
a
community
bridge
project
that
just
concluded.
That's
what
I'm
thinking
that's
Slaten
Nunez
did
and
just
presented
that
in
a
webinar
in
the
last
few
days,
along
with
a
presentation
by
Tim,
Jack,
home
yeah
and
those
are
both
recorded
as
well.
So
I
like,
if
you
put
those
in
I,
can
paste
links
into
there
as
well,
when
I
find.
B
B
Yes
far
as
writing,
the
like
saying
it
like
having
each
person
kind
of
take
a
each
of
us,
take
one
one
persona
that
that
thought:
the
majority
that
gosh
I
hear
the
crack
like
well
you're,
just
filling
these
out.
Okay,
you
were
just
doing
that.
Okay
I
was
like.
Did
they
just
suddenly
appear?
No
they've
been
working;
okay,
so
yeah
yeah.
B
E
B
B
D
E
A
B
B
B
C
B
B
B
Ask
I
am
happy
to
ask
questions
and
I
can
even
type
the
questions
that
I
asked
you
back
no
problem
and
the
the
Lisa
personas,
that
is
the
sort
of
the
long
term
contributor,
already
knows
a
ton
about
Jenkins,
and
this
just
like
sort
of
think
about
what,
as
a
long
term
trigger
what
kind
of
questions
do
you
ask
these
days
as
I
said
a
lot
of
this,
this
persona
actually
probably
needs
some
filling
out
to
just
as
I'd
like
hey.
This
is
more
I.
B
Think
what
we're
gonna
end
up
with
in
this
persona
is
finding
that
there's
there's
things
to
be
done
here,
but
they're,
they're,
much
broader
and
more
I
would
say
ephemeral,
they're
sorta
like
well.
We
need
to
make
it
easier
for
people
to
write
plugins
or
how
to
like,
make
it
easier
for
for
people
to
add
steps
or
whatever
they're,
much
sort
of
deeper
technical
issues
right
or
questions.
C
Accepted
laughter,
yeah
I
was
just
just
I
just
asked
some
of
those
kind
of
questions
in
lists
not
long
ago.
Hey.
How
do
I
write
a
unit
test
when
I'm
trying
to
add
add
symbols
to
a
plugin
that
I
maintain
right?
How
do
that?
How
do
I
assure
that
the
symbols,
I
added,
make
sense,
etc,
etc?
So
things
that
that
are
a
developer,
centered
plug-in
developer
Center
yeah
I
can
have.
B
B
B
A
Think
that
once
we
get
the
personas
done
and
we
have
them
sort
of
mapped
on
how
how
they
look
in
the
maturity
model
and
I
didn't
think,
then
we
should
start
to
maybe
plan
out
what
we
want
to
do
like
yeah.
Do
we
want
to
start
trying
to
go
through?
You
know,
I,
don't
know
if
we
go
through
JIRA
tickets
and
look
at
what
people
are
saying
out
there
and
start
to
match
that
to
maybe
features
and
things
like
that,
or
maybe
we'll
have
community
feedback
from
the
communications
that
go
out
well,
really.
A
What
I'd
like
to
do
is
start
to
figure
out
what
the
what
we're
going
to
start
working
towards
what
features
are
we
gonna
start
building?
What
are
we
okay,
and
that
may
be
a
time
where
we
start
talking
about
what
is
the
documentation?
That's
out
there
to
to
achieve
these
certain
things
and
do
me
achieve
the
fixing
or
making
sure
documentation
is,
is
leading
to
the
right
avenues
or
paths.