►
From YouTube: SheCodeAfrica Contributhon Retrospective 2021 05 07
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
Thanks
everyone:
this
is
the
chico
africa
contributor
on
retrospective.
It's
the
7th
of
may
2021
we're
going
to
discuss
and
identify
things
that
went
well,
things
that
went
poorly
and
what
we
can
do
in
our
next
event
like
this
to
assist
it
to
go
better
thanks
to
all
of
you
for
being
part
of
it.
Thank
you
for
being
being
active
and
participating
in
the
jenkins
project.
A
A
So
this
is,
we
see
comments
from
cynthia
from
sharon
from
au
ninja
from
angelique.
I
know
we've
got
comments
from
kristen
in
here
and
from
others,
so
very,
very
grateful
for
those.
I
think
what
we
should
do
today
is
take
this
left-hand
document,
and
my
proposal
is
I'm
going
to
make
this
bigger,
so
we
can
read
it
together.
A
A
Okay,
so
so
here
are
some
of
the
the
new
contributor
obstacles,
and
here
are
some
of
the
mentor
obstacles
and
some
of
the.
What
could
we
do
better
topics?
So
I
think
what
we
ought
to
do
is:
let's,
let's
take
a
brief
moment.
Would
one
or
more
of
you
be
willing
to
share
obstacles
you
encountered
as
a
new
contributor
or
topics
that
you
think?
Let's
be
sure
we
address
this
in
our
retrospective
on.
A
Maybe
what
we
could
do
is
have
you
go
first
and
then
we'll
take
actually
no,
let's
how
about
we
go
in
the
order
of
text
here.
So
sharon
will
ask
you
to
go
first,
then
esther
and
then,
if
lucy's
with
us,
we'll
have
her,
do
it
then
online
and
then
cynthia
and
please
be
relatively
brief.
We
want
to
hear
your
voice,
about
which
things
do
you
think
we
should
focus
on
in
this
retrospective
to
help
us
improve?
A
A
A
A
Okay,
so
sharon-
you
may
have
an
audio
problem
rather
than
lose
time.
How
about
esther?
Would
you
be
willing
to
go
next
and
and
give
us
just
your
your
insights,
your
recommendations,
things
that
that
you
would
like
to
highlight
either
from
the
text
we
have
here
or
something
that's
come
to
you
since
then,.
C
Nothing
nothing
new,
except
the
things
that
I
already
said
before,
so
I
had
an
issue
with
jenkins
restart
and
apart
from
that,
I've
said,
my
main
obstacle
was
understanding
to
jenkins.
So.
C
D
A
E
A
F
On
my
side
about
the
obstacles
that
I
had
okay,
definitely
this
was
my
first
two
pencils
projects
and
yeah.
I
was
having
also
other
things
that
I
was
doing
besides,
so
the
challenges
that
I
had
initially
were
mostly,
I
remember
the
first
few
weeks.
I
think
the
second,
the
first
one
I
had
an
issue
with
installing
things
and
all
those
the
things
that
were
supposed
to
install
for
everything
to
run.
F
D
F
Well,
this
was
quite
a
challenge
to
me
by
the
way
it
was
the
fact
that
the
time
difference,
but
yet
yes,
it's
understandable,
but
then
I
had
it
was
really
so
bad
on
my
side,
because
some
meetings
I
used
to
like
they
used
to
happen
very
late
in
the
night
like
quite
late
here,
so
I
was
finding
it
very
hard
for
me
to
join
up
because
maybe
then
any
just
something
seems
to
happen.
I
don't
know
it
was
a
challenge.
A
Thank
you.
So
it
was.
There
was
a
scheduling
thing
and,
and
I
in
in
some
summaries,
I
had
not
captured
that
one.
So
let
me
put
that
there
are
improved
communications
by
identifying
times
that
each
participant
can
be
mentored,
so
we
had
tried
a
different
way
to
try
the
approach
of
of
a
combined
meeting
where
everyone
could
be
mentored,
and
that
meant
that
there
were
times
when
you
couldn't
attend
thanks,
good
insight.
G
F
E
A
H
Was
yeah
good
day,
everyone
hi
everyone
to
add
to
what
my
development
is.
I
said,
okay
on
my
own,
my
own
end,
I
didn't
really
have
much
challenges,
probably
because
I
used
ios,
yes,
because
it
was
much
pretty
much
straightforward.
Yes
and
I
also
used
blue.
So
everything
was
just
straight
forward.
Yes,
and
the
only
challenge
I
had,
which
I
pointed
out
on
the
documents,
was
the
fact
that
they
appear
some
of
the
pairs.
I
raised
the
maintainers.
H
We
are
not
nearby
to
review,
so
I
would
actually
suggest,
if
it's
possible
to
to
maybe
a
lot
or
let
these
these
other
maintainers.
Let
them
know
give
them
the
awareness
that
there
will
be
some
peers
from
so
so
so
people,
so
they
will.
H
They
will
be
aware,
because
I
I'm
not
sure
they
were
away
that
was
supposed
to
contribute
to
to
their
to
their
plugins
yeah,
so
if
they
will
be
informed
before
we
start
or
maybe
when
we
start
or
if
that's
not
possible,
if
we
can
strictly
work
on
on
plugins
that
are
managed
by
cloud
base
that
we
have
their
maintainers
available,
that
could
that
could
actually
quickly
help
us
to
reveal
that
would
be
better
yeah.
So
does
that
amount?
A
Excellent,
so
I
tried
to
capture
that
in
let's
see
here,
it
was
increase,
pull
request,
review
and
merge
pace
by
not
selecting
plugins
unless
the
maintainers
have
agreed
to
a
prompt
review.
So
that
was
a
mistake
that
that
we
made.
I
use
the
prioritization
exercise
to
prioritize
the
plugins
with
the
most
comments,
but
then
failed
to
ask
the
maintainers.
A
Will
you
commit
to
review
promptly
and
even
worse?
In
your
case,
one
one
team
of
maintainers
has
has
had
ongoing
challenges
for
us
in
general.
Are
we
put
you
on
the
artifactory
plugin
and
we've
struggled
with
it
in
the
past?
So
so
I
we
really
did
not
give
you
the
best
chance
for
success
by
doing
that,
and
yet
you
did
did
wonderful
work
on
it
good.
Yes,
thank
you.
G
Yeah
thanks,
I
actually
feel
like
they've
seen
everything
I
was
going
to
also
mention
about
chord
reviews,
but
also
I
had
challenges
with
some
the
meetings
that
were
having
on
friday
evening.
Sometimes
they
were
taking
long
which
were
affecting
the
people
that
I
stayed
with
because
they
had
to
sleep.
So
I'm
not
sure
if
it's
possible,
you
know
to
have
them
actually.
This
time
works
for
me
wrong,
but
I'm
not
sure
with
other
mentees
but
yeah.
G
It
would
have
been
better
to
just
have
it
earlier
so
that
in
case
it
takes
longer,
then
it
would
be
fine
yeah,
that's
what.
A
Good,
so
so
my
interpretation
of
that
was,
let's
see
we
had
it
here,
which
was
not
just
root
mentoring.
We,
the
the
attempt
to
use
group
mentoring,
was
an
attempted
efficiency
that
I
suspect
we
could
have
achieved
the
same
results
by
having
one-on-one
mentoring
with
one
of
the
mentors
and
each
individual
without
doing
a
large
group
meeting.
You
know
good
point
all
right,
so.
D
Yeah,
I
think
we
originally
thought
that
this
would
be
something
they
could
do
more,
maybe
collaboratively
or
maybe
even
just
kind
of
have
like
sessions
where
we
all
kind
of
it's
more
like
a
hackathon
than
you
know,
then
it
ended
up
being
being
like
you
know,
because
it's
so
hard
to
coordinate
to
coordinate.
You
know
multiple
time
zones
and
you
know
multiple
more
people,
the
harder
it
is
to
find
a
good
time.
But
you
know
everyone,
it's
it's.
You
end
up
finding.
You
know
the
average
time
which
means
it's
like
only
okay.
D
You
know
it's
only
okay
versus
maybe
the
best
like
the
best
time.
So
maybe
it's
we
could
work
on
maybe
doing
more
things
asynchronously
and
then
try
to
focus
one-on-one.
I
yeah,
I
think
we
had.
We
thought
it
was
going
to
be
more
hackathon-ish
than
it
ended
up
being
so.
A
Right
right,
your
point
is
good
about
more
async
work.
I
wonder
if
what
we
ought
to
consider
is,
should
we
say
we'll
do
one
one
group
meeting
a
week,
because
I
think
I
think
there
are
some
things
we
need
in
a
group
meeting.
The
the
group
meetings
that
started
the
week
were
helpful
to
set
framework
to
to
set
expectations
to
do
process
questions,
but
then
the
technical
sessions
should
probably
be
individual
focused
with
others.
Welcome
to
attend
anyone
can
attend,
but
we'll
do
focus
on
an
individual.
D
I
mean
mark,
I
love
this
session
where
you
basically
went
through
and
you
know
you
started
like
you
built
jenkins
core
from
scratch.
I
mean
that
was
kind
of
nice
and
that's
a
good
thing
to
have
in
a
group
session
as
well
too,
because
it's
it's
just
everything
all
together
and
we
could
ask
questions
and
we
could
look
at
stuff.
I
thought
that
was
nice,
but
it
was
hard
for
me
personally
to
go
to
things
on
monday.
A
D
A
So
so
what
do
you
think
of
this
idea
if
we
were
to
identify
themes
for
meetings
and
say
this
meeting?
Is
a
group
training
session
we're
going
to
share
we'll?
Do
the
recording
we're
going
to
to
focus
on
things
that
we
think
everyone
needs
to
know
or
have
things
that
are
instead
an
individual
mentoring
session
where
you're
welcome
anyone
is
welcome
to
attend,
but
we're
focusing
on
mentoring
for
this
person.
A
Okay,
so
all
right,
I'm
gonna,
I'm
gonna,
assume
I
assume
yes
kristen,
so
that
that
idea
might
be
feasible
good.
So
now,
now
the
there
was
a
comment
on
more
async
work
and
I
think
that's
a
theme
that
we
might
want
further
exploration
on.
It's
something
that
I
hadn't
seen
many
comments
on
in
the
feedback,
but
was
curious.
If
there
are
ideas
of
ways
we
could
have
done
this
more
asynchronously
for
for
better,
better,
better
results
in
the.
A
A
Okay,
so
now
I
wanted
to
look
at
some
other
topics.
The
obstacles
encountered
by
mentors-
and
here
mostly
I'm
looking
for
feedback
from
our
participants
from
the
mentees
on.
If
some
of
these
were
particularly
important,
would
have
been
particularly
valuable
to
and
others
less
so
so
could
each
of
you
look
at
this
list
and
and
for
instance,
give
choose
one
or
two
that
you're
ready
to
say.
Oh
yes,
that
could
have
helped
so
here's
one
on
early
morning
meetings.
Well,
so
I'll!
A
A
So
what
I
would
like
each
each
of
each
of
you
as
as
participants
to
look
at
this
list
of
obstacles
experienced
as
mentor
and
what
could
we
do
better
to
see
if
there
are
things
in
there
that
I
might
have
missed
of
oh,
we
should
do
that
so
onigne,
one
that
you
highlighted
was
interact
with
more
people
in
the
community
and
and
that's
one
I
think,
may
need
more
discussion.
How
could
we
achieve
that?
That's
the
kind
of
thing
that
I'm
looking
for
this
phase
of
our
discussion
so
review
these
sections.
A
Okay,
so
where
is
the
chat
window
chat,
chat,
chat
here
we
go
okay,
so
here's
the
document
and
what
look
at
obstacles
experienced
as
mentor
and
at
what
could
we
do
better
and
give
give
insight
so
well,
one
that
oleg
had
noted
here,
as
is
promotional
things
that
I
had
not
captured.
How
do
we?
How
do
we
assure
that
more
people
are
aware
of
this
know
about
it
and
are
ready
and
willing
to
help?
D
A
A
G
Summary,
okay,
so
from
what
we
could
do
better,
I
think
it
it's
the
same
thing
when
you
measure
end
of
interacting
with
other
people,
maybe
having
I
don't
know
icebreakers,
I
feel
like
it
helps
a
lot
just
know
the
people
that
you're
with
also
as
mentioned,
maybe
having
like
a
theme
for
each
meeting
that
we
we
we
get
to
have
maybe
say
that,
oh
today,
we're
going
to
learn
this
this
thing
or
maybe
we're
going
to
learn
about
code
reviews
we're
going
to
learn
about
some
git
commands.
G
I
think
it
will
be
good
just
having
some
mentoring
session
yeah
with
like
a
topic
yeah.
That
would
be
good
yeah.
I
think
that's
it
for
me.
C
Well,
interaction
between,
I
think,
christian's
observation,
interaction
between
participants
and
mentors
and
guidance
on
how
to
research
topic
and
step.
So
I
think,
what's
up,
I
think,
cynthia.
I
remember
what
she
said
about
when
having
the
meetings
you
could
choose
something
to
learn
something
specific
to
learn:
yeah.
That
would
be
great.
A
C
C
Yeah
I
I
said
I
wrote
that
because
I
figured
that
sometimes
I
spent
too
much
time
on
one
thing
and
that
I
was
not
really
well
moving
at
the
fast
pace
and
moving
forward
so
to
speak.
So
I
just
made
me
fall
back
in
a
way,
so
it
was
a
way
for
me
to
know
that.
Okay,
at
the
end
of
the
week,
what
I
should
have
achieved,
then
that
would
be
that'll
be
beautiful.
C
A
A
A
F
Yeah,
it's
okay,
so
on
my
side,
mine
is
more
repetition,
whatever
my
colleagues
are
just
saying
so
first
I
feel
like
there
was
very
minimal
interactions
between
the
mentees
and
their
mentors.
So
something
will
be
done
about
that
then
to
about
their
yeah
timeline
for
the
task
within
we
should
maybe
we
should
have.
There
should
have
been
goals.
F
One
is
not
able
to
to
to
to
go
beyond
whatever
the
same
goal.
Then
they
can
be
helped
like
a
solution
can
be
can
be
found
for
that,
then
I
was
also
feeling
like.
Maybe
the
whole
whole
program
would
have
taken
longer,
because
within
the
first
few
weeks
most
of
us
use
the
time
to
even
familiarize
themselves
with
whatever
we
were
supposed
to
do
so
maybe
time
will
be
taken
much
longer
so
that
we
get
to
people
get
to
settle
and
work
with
them.
F
A
A
A
Okay
and
that's
when
I
had
not
captured
so
I
for
me
the
this
okay
consider
a
longer.
H
Okay
yeah,
so
just
like
I
mentioned
personally
I
I
love
meeting
people,
I
love
networking,
so
I
I
feel
okay
on
this
live
channel,
we're
all
added
to
there
is
a
general
channel
there.
That's
the
cdf
slack
channel.
H
If,
if
we
actually
introduced
okay,
because
I
feel
we
were
just
isolated
in
one
in
one
group
like
that-
and
nobody
knows
that
this
set
of
persons
are
existing
here.
So
I
feel
if
there
was
a
little
bit
of
introduction.
H
Oh
this,
there
are
some
guys
there
that
are
here
to
do
this
and
they
welcome
us,
and
maybe
we
introduce
ourselves
it's
a
large
community,
so
I
feel
it
it
will
give
us
a
bit
of
sense
of
belonging
and
also
we
could
meet
people
there.
We
never
can
tell.
So
that's
that's
for
my
own
and
if
there
is
a
way
you
you
can
consider
trying
to
to
introduce
us
to
the
large
community
yeah,
that's
it.
A
And,
and
that
one
for
me
is,
is
a
challenging
one,
so
I
wanted
to
take
some
notes
there,
because
the
the
jenkins
developers,
I
would,
I
would
say
they-
don't
have
a
chat
channel
that
is
heavily
used
by
jenkins
developers,
a
single
chat
channel.
What
they
have
is
a
mailing
list.
A
And-
and
so
that's
a
it's
an
interesting
challenge
right,
so
they
they
we
even
on
gitter.
We
don't
have
a
single
chat
channel,
that's
dedicated
to
it
right.
It's
really!
There's
a
configuration
is
code
plug-in
channel.
There's
a
git
plug-in
channel.
There's
there's
a
there
are
several
others
like
that.
The
cloud
native
group
chats
on
on
chat,
cdf
chat,
kristen
go
ahead.
D
Yeah
and
it's
like
I'm
not
even
I
don't
know,
mark
myself,
like
I
don't
even
know
of
a
slack
channel
for
jenkins,
I
actually
was
ironic,
is
like
I
know,
of
irc.
D
If
you
wanted
to
go
really
retro
with
everything,
there
is
irc
for
jenkins.
But
again
it's
not.
Everyone
is
on
there
and
it's
going
to
be
because
it
is
irc
and
it
it's
going
to
be
more
of
like
there's.
The
the
general
jenkins
channel,
at
least
to
me,
is
sometimes
more
like
user
questions
versus
developing
or
like
using
jenkins
versus
like
jenkins
development.
D
So
it
is
a
little
bit
harder
to
find
everyone,
but-
and
so
it
is
usually
easier,
like
rick
was
saying
to
find,
like
the
individual
slack
chat
channels
based
on
what
you're,
based
on
different
pieces.
But
if
you
or
I
guess,
if
there
was
a
general
question,
it
would
just
be
in
the
user's
channel
and
someone
would
be
able
to
jump
in
and
help
but
yeah
it's
it's.
I
think
I
don't.
You
know
different
open
source
projects
operate
in
different
ways,
and
this
is
just
kind
of
how
jenkins
operates.
A
Yeah
so
well,
so
I
wondered:
should
we
have?
Should
we
have
introduced
the
the
team,
the
project
to
the
developer
mailing
list
at
the
start,
and
that
way
we
at
least
could
have
had
assured
that
each
of
the
participants
was
invited
to
and
participate
in
the
developer
mailing
list.
The
challenge
is
the
developer.
Mailing
list
has
a
relatively
high
expectation
of
deeply
technical
content
being
placed
there,
and
my
worry
initially
why
we
didn't
use
the
developer.
A
D
True,
that's
a
good
point.
Sometimes
it
can
be
very
technical
on
that
list
or
it's
talk.
Yes,
but
it
might,
it
might
be
maybe
do
like
in
just
a
general
introduction
thread
and
just
as
because,
even
like
the
google
summer
of
code
has
its
own
list,
which
is
what's
difficult
there,
but
you
could
just
do
it
hey.
D
A
I
think
so
yeah
so
announce
announce
would
feel
really
good
and
that
would
have
at
least
introduced
online
to
and
and
cynthia
and
esther
and
and
lucy
and
sharon
to
the
jenkins
community
and
to
the
developer
community.
Specifically,
so
that's
very
good,
all
right
sharon,
sorry
that
we
haven't
heard
from
you.
Could
you
try
unmuting
and
let's
see,
if
we'd
love,
to
hear
from
you?
If,
if
your
audio
is
working.
I
Okay,
hi
everyone.
Sorry,
I
had
some
technical
issues
at
the
start,
but
I
would
like
to
say
that
the
entire
experience
was
good.
I
appreciate
what
you
did
for
us
like
helping
us
through
the
process.
For
me
I
think
I'll
just
say.
Like
the
rest,
I
I
spent
a
lot
of
time
at
the
at
the
beginning
of
the
tasks,
not
knowing
that
it
was
much
easier
that
I
could
have
moved
forward.
A
I
A
A
Okay,
good
all
right,
interesting,
thank
you.
Okay,
all
right!
Anyone
else
have
have
insights
or
things
that
we
may
have
missed
on
this
I
wanted
to
before.
We
conclude
our
session
go
through
the
proposed
actions
and
then,
let's
see
if
if
we
miss
something
in
the
proposed
actions,
where
you
say
no,
this
is
something
oh.
We
should
have
done
it
and
and
we'll
then
add
those
as
well.
A
Okay,
okay,
good!
Then
then,
what
what
I
put
as
improvement.
So
I've
tried
to
frame
these
improvement
actions
as
a
goal
and
an
action.
So
I
think
the
goal
is
to
improve
communications
and
one
technique
is
in.
The
task
list
require
a
chat
posting
from
every
participant
and
every
mentor
at
the
start
of
the
project.
A
It
may
seem
sort
of
sort
of
minor,
but
it
was
really
quite
awkward
that
one
of
you
actually
one
mentor
and
one
participant
didn't
get
into
the
into
the
chat
channel
until
several
weeks
late,
because
we
just
didn't
do
this
so
so
sorry,
and
and
thank
you
for
your
patience
with
that
mistake,
then
to
use
to
take
cynthia's
suggestions,
introductions
at
the
start
of
meetings,
icebreakers
to
assure
we
know
each
other.
So.
A
H
H
I
feel
that's
okay,
it's
because
it's
it's
look.
It
will
sound
like
stand
up
yeah!
It's
it's!
Okay!
For
me,.
A
Okay,
all
right
so
so
yeah,
that
is
a
sort
of
a
mini
stand-up
right.
It
is
a
stand-up
status,
yeah
good
good
way
of
describing
it.
Thank
you,
okay
and
then
identify
times
when
individual
participants
can
be
mentored.
I
think
we've
heard
that
from
several
people.
That's
that's
a
good
way
to
avoid
avoid
having
a
problem
with
multiple
people
not
being
able
to,
or
one
or
more
people,
not
being
able
to
attend
a
group
session.
A
A
Include
topics
of
interest,
so
so
should
we
identify
common
topics
to
consider
for
group
group
training
so,
for
instance,
git
operations
using
git
effectively.
I
think
oleg
had
done
a
good
session
on
that
or
or
using
compiling
jenkins.
That
was
one
that
I
think
I
did
jenkins
core
and
a
jenkins
plug-in.
A
Then
next
proposal
was
decreased
participant
startup
time
by
including
self-paced
training
courses
in
the
task
document.
So
my
thought
was,
you
shouldn't
need
to
start
the
self-paced
training
until
the
project
begins,
because
the
project
was
instead
intended
to
be
specific
time,
but
this
could
have
been
one
of
your
first
things.
Instead
of
us
just
telling
you
oh
do
this
little
tutorial,
we
could
say:
take
this
self-paced
training
course
accepting
that
you
may
only
get
through
part
of
it.
A
Okay,
then,
the
next
piece
was
increase,
pull
request,
review
and
merge
pace
by
only
selecting
plug-ins
that
we
have
maintainers,
who
have
agreed
to
promptly
review
and
ask
the
each
sub
committer
each
submitter
to
at
reference,
all
I
shouldn't
say:
reviewers
all
mentors
in
each
pr.
That
was
one
where
esther
had
submitted
some
pull
requests,
and
I
was
the
only
one
and
I
dropped
the
ball.
I
failed
to
do
what
I
should
have
done
and
if
we
mention
all
mentors,
there's
a
better
chance,
someone
else
will
be
able
to
help.
H
A
Yeah,
I
I
thought
that
pull
request.
Submitters
didn't
have
permission
to
add
a
label
in
general,
so
I
I
I
like
the
idea
I
think
it
would
be.
It
would
be
good
to
have,
and
maybe
that's
a
a
an
even
better
idea
on
nine
is
create
a
github
report
that
shows
all
participant
pull
requests
to
all
jenkins
repos
with
that,
because
I
I
don't
think
I
don't
at
least
kristen.
Can
you
help
me
there?
I
think
that
labeling
of
a
github
pull
request
requires
that
I
have
write
permission
to
the
repository.
A
A
A
D
D
I
think
that
actually
like
onignae,
like
cynthia,
you
guys
started
doing
that
later,
and
that
was
incredibly
helpful
because
I
was
like
oh
okay
now
I
can
see
that
there's
a
pull
request
and
or
it's
it
helps
me
at
least
at
least
for
me.
It
was
like
super
helpful
when
that
was
happening,
because
it
allowed
me
to
be
able
to
see
oh
there's
something
new
right
now
I
can
go
make
sure
I
don't
miss
it
because
in
github
you
can,
if
especially
if
we
weren't
tagged
explicitly.
D
D
But
for
me
at
least
like
it
gets
mixed
in
with
things
that
I'm
reviewing
for
work
or
other
pieces,
that
you
know
other
open
source
projects
and
I'm
not
sometimes
as
good
about
checking
that,
but
if
it
was
like
a
in
email
or
like
you
know
where
I'm
added
and
I
can
see
it
to
my
email
or
in
the
github
or
the
sorry,
the
slack
channel.
It
was
very
easy
for
me
to
go.
Oh
okay,
I
really
I
need
to
make
sure
I
can
review
this.
D
I
noticed
like
pretty
much
like
anjalik
meg
mark.
You
were
all
real
oleg,
all
really
good
about
yeah.
As
soon
as
something
went
in
that
channel
people
were
responding
very
quickly
and
sometimes
even
when
I
went
it's
like
oh,
I
just
saw
this
and
I
clicked
it
was
already
reviewed,
which
was
very
helpful,
so
good.
D
A
A
A
A
A
And,
and
that
feels
like
a
really
healthy
thing
and
weekly
goals
now,
how
would
you,
as
participants
have
dealt
with
if
I
had
done
a
bad
job
of
defining
the
weekly
goals
and
said,
I
think
the
first
three
tasks
should
be
completed
in
a
week?
Would
that
would
that
have
been
destructive
to
your
your
feeling
of
accomplishment?
Would
that
have
been
demotivating?
A
E
Yeah,
I
think
it's
kind
of
like
a
50
50
thing,
because
on
the
other
hand,
if
you
set
goals,
then
you
might
kind
of
rush
participants
and
they
might
end
up
not
really
gaining
anything,
because
all
they
just
want
to
do
is
finish
their
goals
and
they're,
not.
You
know,
really
getting
a
feel
of
the
platform,
but
then,
on
the
other
hand,
it
could
help
them
be
focused.
E
A
Goals
should
include
what,
if
we
said,
goals
should
include
communication
goals
and
interaction
goals,
not
just
code
accomplishment
goals,
because
one
of
the
things
that
oleg
reminded
me
of
when
we
started
was
that
the
the
bigger
picture
goal
of
this
project
was
not
to
improve
jenkins
pipeline
help.
The
bigger
picture
of
this
goal
was
to
have
add
five
new
people
who
were
more
comfortable
contributing
to
open
source
projects.
A
A
Okay,
great
all
right
so
remember
the
project
goals
the
she
code,
africa
goals,
not
just
the
jenkins
project
goals
right,
because
the
the
chica
africa
goals
are
are
a
bigger
picture.
Good,
okay,
consider
a
longer
project
duration.
So
this
one
I'm
leaving
here,
but
I
have
to
acknowledge
that
I
think
we
chose
exactly
the
right
duration
for
this
one,
because
we
avoided
a
collision
with
google
summer
of
code.
A
If
google
summer
of
code
starts
for
me
in,
I
think
less
than
a
week
now
it
may
be
no
it's
10
days
and
that
will
take
take
me
away,
so
I
wouldn't
have
been
able
to
mentor.
So
if
this
project
had
been
declared
to
be
two
months,
I
would
have
had
to
say
no
and
the
project
wouldn't
have
happened
so
so
this
one
I'm
I'm
leaving,
but
but
it's
a
compromise
with
need
to
to
not
lose
mentors,
because
we
lengthen
the.
A
A
A
I
was
assuming
it
was
with
the
mentors
good
question.
What
what
would
you
recommend
as
a
group,
so
I
thought
that
this
was
prepare
and
share
in
each
group
meeting
but
you're
right
that
that,
if
we,
if
you
did
it
just
as
mentees
you
could
you
could
do
it
probably
at
much
broader
range
of
times
than
than
we
could,
because
of
my
distance
from
you
in
time
zone
and
kristen's
distance
from
you
in
time
zone.
A
D
Sure-
and
I
can
even
probably
like
what
would
be
helpful,
especially
if
you
all
are
talking
post
something
on
the
slack
channel,
I'm
not
very
into
like.
D
Almost
over
communicate
because
I
think
I
put
in
a
lot
of
things.
Sometimes
it
was
hard
to
it
felt
like
it
was
hard
to
track
where
everyone
was
and
so
yeah
meet
up.
You
can
all
talk
to
each
other,
and
actually
that
would
probably
be
really
great
because
then,
if
you
have
any
questions,
it
might
be
faster
to
ask
someone
else
is
working
on
something
rather
than
wait
until
you
know,
one
of
us
is
available
or
just
if
it's
over
the
weekend,
just
post,
but
yes
just.
D
D
Enough,
like
I
know
it's
sometimes
it
could
be.
You
know
intimidating
or
anything,
but
it's
like
if
you
we're
all
here
to
if
you
have
a
question
just
ask
or
if
you
you're,
blocked
by
something
or
confused
we're
here
to
help
so
yeah
the
results
that
status
we
didn't
give
you
posted
or
just
kind
of
this
is
what
I'm
working
on
today
or
oh,
oh,
it's
like!
Oh,
I
wasn't
planning
on.
I
have
you
know
something
else
is
happening.
D
I
wasn't
planning
on
working
today,
but
maybe
check
in
tomorrow
and
then
that
way
everyone
kind
of
know
where
everyone
is
and
maybe
kind
of
even
enables
a
little
bit
more
so
again,
so
we're
also
not
fighting,
for
you
know
middle
of
the
night
trying
to
have
a
meeting
together
forever.
A
D
Either
middle
of
y'all's
night
or
like
middle
of
our
night,
it's
just
it
maybe
helps
a
little
bit
more
for
it
doesn't
hurt
to
over
over
share,
especially
if
you're
in
our
channel,
if
you're,
because
we
all
want
to
help
each
other.
A
A
All
right
thanks,
very
much
look
forward
to
seeing
you
in
the
future.
Thank
you.
Everyone,
a
requ,
a
copy
of
the
recording
and
a
summary
will
be
included
in
a
blog
or
a
link
known
link
to
the
recording,
won't
be
included
in
the
blog
post,
I'm
preparing
a
blog
post
that
will
summarize
the
retrospective
and
what
we
learned
highlight
some
of
your
results,
etc.
I'll
probably
mention
each
of
you
in
the
blog
post,
pull
requests
so
that
you
can
then
review
it
and
give
comments.
A
I
hope
to
get
that
blog
post
done
today
or
tomorrow.
I
would
love
to
have
your
review
before
start
of
my
day
monday,
because
I'll
probably
set
my
goal
to
to
post
the
blog
post
to
jenkins.io
monday.
The
is
that
the
10th
monday
monday
may
10th
so
I'll
I'll.
Let
you
know
that
the
blog
post
is
out
there
and
would
love
to
have
your
feedback.
Thank
you.
Everyone.