►
From YouTube: SheCodeAfrica 2021 04 30 PM
Description
Final mentoring session and initial retrospective on the SheCodeAfrica Contributhon held during April 2021. See the retrospective notes at https://docs.google.com/document/d/1xhmEtwYIlGuuKtwn6Ek8DWyBEkPFA5q8CfWRRL7xZ9U/edit#heading=h.jc1sy5a7e8nj
A
B
C
A
A
A
C
E
D
D
A
A
F
A
All
right
so
welcome
to
the
concluding
session
for
our
chico
africa
contributon,
a
reminder
that
we
adhere
to
the
jenkins
code
of
conduct.
It's
april
30th
2021.
We
are
nice
to
each
other,
we're
kind,
considerate
and
decent
and
good,
don't
be
rude,
don't
be
crude,
etc,
all
right.
So
what
I'd
propose
is,
let's
talk
about
the
end
of
the
project.
What
worked
well,
what
didn't,
etc?
Get
some
retrospective
feedback
talk
about.
F
E
No,
I
can't
really
think
of
anything
right
now.
I
think
kind
of
similar
to
what
meg
was
saying.
I
really
want
to
hear
what
we
can
do
better
or
how
we
can
help
and
currently
kind
of
talk
about,
maybe
continuing
on
with
certain
things
or
like
what
can
we
do
to
help
push
through
this?
Maybe
the
pull,
requests
and
stuff
that
we're
not
accepted
at
the
time
and
just
kind
of
like
helped
get
that
finished
like
get
us
over
the
finish
line.
A
Great
okay,
yes,
all
right,
so
what
I
propose
is:
let's,
let's
give
voice
to
to
each
of
our
each
of
those
who's
here
with
us,
so
I'm
going
to
stop,
sharing
and
just
take
notes
and
esther.
I
think
you
were
first
in
the
meeting.
Would
you
like
to
tell
us
both
or
maybe
what
we
could
do?
Is
you
start
you
unmute
and
we'll
ask
you
some
questions
and
get
some
insights
from
you.
A
So
so
what
we
were
thinking
is
if
you'd
be
okay,
if
meg
and
kristen-
and
I
just
asked
you
some
questions
to
help-
help
understand
what
we
might
do
to
make
the
experience
better
for
you,
what
things
would
be,
what
things
worked?
Well,
what
things
didn't
and
we'll
do
this
with
each
of
the
people
in
turn,
so
that
so
we
get
some
hints.
So
one
of
the
things
that
I
think
was
well,
how
did
you?
How
did
you
overcome
some
of
the
technical
challenges
you
encountered?
G
The
questions
were
technical,
some
of
them.
However,
I
was
able
to
to
make
more
research.
I
was
able
to
stop
the
internet.
I
actually
to
be
honest
with
you.
I
had
had
sleepless
nights
because
I
I
needed
to
get
things
right,
so
I
had
to
keep
like
while
working,
I
could
have
hundreds
of
tabs
open,
because
I
I
keep
looking
out
for
for
help
and
also
for
information
that
I
need
to
work.
So
it
wasn't
really
easy
what
you
could
have
done.
G
You
actually
did
what
you
were
supposed
to
do
because
on
the
task,
the
tax,
the
the
documents
where
they
they
were
really
helpful.
The
steps
in
the
documents
were
helpful.
The
only
thing
was
the
fact
that
we
needed
to
do
more
research.
Yes,
we
needed
to
do
more
research
and
I
actually
did
like
many
research.
I
watched
youtube
videos.
I
looked
at
documentation
yeah,
so
that's
it.
A
Meg's
question
I
thought
was
a
good
one
is,
would
it
would
it
be
better
if
we
started
the
session
with
an
introduction
that
showed
and
maybe
recorded,
even
the
steps
to
do
that?
Those
initial
tasks,
because
the
tests
were
pretty
pretty
detailed,
but
I
assume
there
were
things
you
bumped
into
that
were
really
complicated
that
you
that,
as
you
said,
caused
you
sleepless
nights,
and
if
there
are
things
we
could
do
to
help
reduce
sleepless
nights
and
have
a
better
have
a
good
experience.
G
A
Great,
thank
you
thanks
very,
very
much,
and
maybe
what
we
do
is
meg.
Are
you?
Okay?
If
I
think
what
we
do
is,
let's
rotate
the
same
question
through
each
of
the
each
of
the
participants
and
then
we'll
come
back
for
more
questions.
Would
that
be
okay?
I
like
that?
Okay,
so
cynthia
sure,
oh
no
esther,
we
had
said
you
would
be.
Second
esther.
Are
there
things
that,
where
you
encountered
technical
problems
and
if
we'd
done
something
different,
we
could
have
reduced
your
technical
problems.
C
Okay,
so
the
technical
problems
that
I
had
were
not
really,
I
think,
not
really
problems
that
you
can
foresee,
because
I
think
the
only
technical
problem
that
I
had
with
jenkins
was
the
whole
research
issue
which
I
figured,
but
I
think
what
could
have
gone
better
would
be
some
like.
I
already
decided
my
article
some
helpful
links
to
documentation.
C
That
would
introduce
jenkins
and
all
that,
because
I
felt
like
like
it
was.
It
was
cool
and
I
understood
the
tasks
and
the
steps
and
all
that,
but
I
kind
of
just
jumped
into
downloading
java
and
maybe
and
all
that,
and
I
didn't
really
understand
what
any
of
them
did.
But
I
was
just
following
this
steps
so
and
it
was
during
when
we
had
to
start
creating
pipelining
all
that
that
I
know
how
to
I
started
going
through
the
documentation.
A
Very
good,
so
so
in
in
your
case,
if
we
had
provided
as
say,
for
instance,
as
links
in
that
step,
links
to
documentation
or
videos,
because
because
many
of
them,
in
fact,
some
of
them
even
have
entire
courses
around
some
of
those
topics
right
the
when
we
had
you
create
an
initial
pipeline,
truly
there's
a
full
day
course
that
I've
taught
in
the
past
on
how
to
do
that
kind
of
thing.
So
I've
spent
eight
hours
in
a
classroom
teaching
people
what
we
described
as
one
or
two
lines.
So
so
absolutely
that's!
A
A
G
A
A
H
B
Oh
okay,
I
I
think
the
so
maybe
the
internet
connection
was
the
biggest
one.
I
don't
know.
If
I
can
say
it
was
a
technical
issue,
but
yeah
like
attending
some
meetings
was
so
hard
for
me,
like
I
had
to
reload
every
time,
but
I
think
it's
on
my
side,
that's
something
I
should
work
on.
Also
when
making
like
there
was
a
pull
request.
B
B
It
looks
like
I
have
to
close
it,
so
maybe
it
would
have
been
better
to
yeah,
like
communicate
with
other
contributors
to
just
make
sure
they
know
what
the
what
we
are
doing
or
maybe
schedule
something
that
we
should
have
done
before
yeah,
I
think
hotel
for
the
quad
review.
It
was
kind
of
yes
again.
Some
contributors
were
not
that
fast
to
give
their
review
or
they
left
some
review
and
never
came
back
to
to
just
see
the
status
of
the
pr
so
also
that
would
have
been
better.
B
So
apart
from
that,
I'm
really
happy
for
the
for
the
documents
that
you
provided
us
at
the
beginning.
It
was
really
helpful.
It
was
clear
so
yeah
you
just
had
to
like,
as
when
you
say,
do
some
research
on
how,
like
the
behaviors
of
some
arguments,
called
examples
which
was
really
fun.
On
my
on
my
side,
I
learned
a
lot.
I
was
reading
other
people's
articles
using
stack
overflow
yeah.
Thank
you
so
much.
A
Thank
you
so
you
mentioned,
and
I'm
I'm
now
curious,
because
we've
seen
it
before
sometimes
internet
issues
get
in
the
way
when
we're
trying
to
do
these
multi-continent
experiences
right
here.
I
am
sitting
in
colorado
in
the
united
states
and
you're
you're
at
an
ocean
and
a
continent
away
from
me.
So
so
that's
that's
no
shock.
B
Not
not
really,
I
really
love
the
meetings,
so
I
wouldn't
say
that
that
one
should
stop,
but
like
for
other
meetings
that
I
usually
have
with
other
people,
I
use
google
meet
and
it
really
work
for
me.
Well,
so
I
don't
know
why
zoom
is
always
the
problem
on
my
side,
so
I
would
prefer
zoom
or
I
don't
know
also,
but
I
don't
think
it's
like
a
video
call
would
be
better
for,
like
a
group
of
people,
but
google
meet
was
yeah.
A
Good,
okay
and
and
meg,
and
I
and
kristen,
actually
all
three
of
us
have
access
to
google
meet
very
readily,
so
good
insight.
I
didn't
maybe
one
of
the
things
we
ought
to
put
on
our
list
meg
is
that
we
intentionally
test
and
do
it
do
the
first
meeting
half
in
zoom
and
then
everybody
drops
off
and
try
half
and
google
me
yeah.
F
F
G
A
Okay-
and
it
may
be
that
that
the
google
meet
infrastructure
is
just
better
in
africa
than
the
zoom
infrastructure-
I
I
truly
don't
know,
but
I
think
it's
it.
That
would
be
quite
believable
right.
It
could
be
that
they've
just
got
better
equipment
there
than
zoom
does
good.
Thank
you
very
good
insight.
H
A
Yeah
so
schedule
the
first
meeting
to
include
both
so
now
to
to
reinforce
that
one
of
the
comments
from
one
of
the
mentors
was
hey.
Sometimes,
audio
was
poor,
and
one
of
the
things
we
need
to
remind
mentors
is:
please
don't
turn
on
your
video
camera,
because
it
makes
the
whole
experience
worse
for
those
who
are
remote
right.
Those
who,
who
maybe
already
have
a
connection
that
isn't
great
using
video,
now
makes
it
even
worse.
G
A
G
A
Good
good
point,
and-
and
that's
where
so,
your
note
was
that
in
google
in
google,
hangouts
or
google
me,
we
may
not
be
able
to
record
the
the
nice
thing.
There
is
that's
that
meg
kristen
and
I
have
access
to
a
google
meet
account
that
can
record
so
we
could
overcome
that
because
cloudbees
provides
us
google
meet,
so
we
could.
We
could
do
that.
So
very
good.
Thank
you
because
I
think
I
think
recording
the
sessions
has
been
helpful.
A
A
A
A
E
Sure
it's
all
good,
that's
going
to
bring
up
kind
of
maybe
a
follow-up
comment
that
one
about
getting
improved
or
reviews
by
maintainers,
and
it's
like
I
try
and
remember.
Maybe
I
know
that
we've
made
some
announcements
on
the
jenkins
channel
that
they're.
You
know
that
this
was
the
trivia
thought
was
happening,
but
maybe
we
should
because
some
of
the
repositories,
like
you
know,
mark
meg
and
angelique
me.
We
don't
really
have
commit
access
to
or
we're
not
really
the
maintainers
of
that
particular
plugin.
E
Maybe
we
should
have
done
a,
and
I
actually
think
oleg
did
a
good
job
of
this
one
for
the
jfrog
plug-in
is
like
do
a
reach
out
specifically
to
the
maintainers
and
say
hey.
You
know
this
is
what's
happening,
there's
going
to
be
some
full
requests
made
for
you
know
some
documentation,
we'd
really
appreciate.
You
know
you
being
able
to
look
at
it
and
I
think
that
might
have
helped
speed
along
some
reviews.
E
You
know
in
their
free
time-
or
maybe
you
know
they
haven't-
looked
at
it
in
a
little
while
so
so
it's
the
pace
is
a
little
bit
slower
than
if
you
were
working,
you
know
as
it
as
a
full
job
or
a
full-time
job
or
people
are
looking
to
merge
things
right
away,
so
that
is
kind
of
a
little
bit
of
the
give
and
take
broken
source.
That
is
a
little
bit
slower,
but
maybe
we
can
do
a
little
bit
more
of
a
targeted
effort
to
let
people
let
the
maintainers
know
that.
F
D
F
Went
to
write
the
new
stuff,
it's
like:
where
do
I
get
information
and
it's
like
yeah
welcome
to
open
source
that
can
be
interesting,
but-
and
I
cause
I
think
I
forget-
which
one
there
was
one
plug-in
that
we'd
identified
as
high
priority,
because
we
get
so
many
responses,
but
it
turned
out.
We
couldn't
find
anybody
who
knew
anything
about
it
and
just
I
think
it
was
oniony
who
was
stuck
there.
It's
like
well
yeah
right,
so
we
could
have
made
sure
that
they,
you
know.
H
F
If
it,
if
we
missed
a
couple
of
the
very
top
ones
to
get
some
that
where
we
had
active
support,
that's
a
great
question,
though
the
question
I
noticed
in
the
comments
about
using
the
get
chat
group
versus
slack
and
that
the
the
people
found
the
get
channels
sort
of
intimidating,
and
we
didn't
really
use
it
very
much.
But
a
lot
of
these
other
people
were
not
on
the
slack
channel.
A
A
So
so
yes,
it
was
that's
a
communication
mistake
right
and
communication,
so
clear
communication
channels
and,
and
maybe
what
we
would
say,
is
and
confirmation
they
are
working,
because
if
we
had
done
in
one
of
the
meetings,
if
we'd
done
in
the
first
meeting
or
the
second
meeting,
hey
everybody,
each
of
you
needs
to
connect
to
slack
and
send
me
a
message
that
shows
that
you've
got
access
we
would
have.
We
would
have
solved
many
problems
with
something
as
simple
as
that.
E
E
So
my
question
is:
did
you
find
anything
kind
of
out
in
your
search?
That
would
be
interesting
and
significant
to
pull
in
like
to
make
sure
it's
documented
in
the
official
jenkins
documentation
so
that
you
know
maybe
people
in
the
future
or
who
are
trying
to
do
startup
tasks
aren't
kind
of
all
over
like
searching
out
and
looking
at
stack
overflow.
E
Is
there
any
gaps
or
that
we're
missing
or
any
anything
in
particular?
If
there's
links
or
things
that
you
found
helpful
it'd
be
helpful
to
see
them,
you
can
send
them
on
slack
or
send
a
remark
directly,
so
you
can
put
them
in
the
document,
but
I
think
that's.
My
big
question
is:
what
are
we
missing
or
what
would
have
been
more
helpful
to
get?
You
started.
A
That's
a
good
one.
I
like
that,
okay,
so
what
what
did
you
learn
from
other
documentation
that
we
should
include
in
the
standard
documentation?
I
like
that
one,
a
lot
and
rough
examples
are
even
a
good
thing
online.
Do
you
want
to
do?
Are
you
willing
to
to
answer
that
question
or
share
with
us
some
of
your
insights
and
then
we'll
ask.
G
For
the
the
other
documentations
I
I
used,
or
I
looked
out
to
was-
was
just
because
everything
was
practically
new
to
me,
so
I
needed
to
to
read
from
here
which,
from
this
other
source,
to
compare
and
actually
deduce
what
I'm
looking
for
yeah.
So
the
documentation
in
jenkins
are
okay,
but
then,
personally,
I
needed
to
understand
more
about
the
plugins.
That's
why
I
needed
to
hear
from
other
people
that
have
used
the
plugin.
A
A
E
A
But
well,
but
but
now
now
I
think
let's
take
the
same
question
to
to
esther
and
then
to
cynthia,
because
they
may
they
may
have
had
a
different
experience.
So
esther
to
you
are
there
things
that
you
discovered
from
other
documentation
that
we
should
consider,
including
in
the
standard
jenkins,
documentation.
C
Let
me
see
I
I
don't
think
I
don't
think
so.
I
don't
think
so.
Everything
everything
that
was
that
I
found
outside
there
was
an
example
or
two
in
the
in
the
documentation.
I
don't
think
so.
I
think
what
I
mostly
looked
out
for
was
more
examples,
more
use
cases
on
stack,
overflow
and
other
and
other
blogs
on
issues
that
people
were
facing
and
then
looking
at
their
own
code,
looking
at
their
own
pipelines
and
all
that.
So
I
don't.
I
don't
think
so.
A
Well,
and
you,
you
already
said
one,
you
said
examples
and
that
feels
like
a
place
where
we
conceivably
could
have
said
hey
here.
I
know
we
have,
for
instance,
meg
had
pointed
us
to
the
pipeline
examples
repository
early
on,
I'm
not
sure
if
it
had
the
examples
we
were
seeking,
but
it
was
a.
It
was
a
an
excellent
resource
that
we
could
have
included
in
the
steps
in
the
in
the
task
to
say:
hey,
here's,
some
good
samples.
F
A
B
So
I
feel,
like
examples
would
would
have
been
better
also.
There
are
some
terms
that
were
being
used
and
as
a
beginner
I
was
like
okay.
What
does
this
mean,
and
that
was
making
me
go
inside
for
like
what
is
what?
What
does
that
mean?
So
I
don't
know,
maybe
trying
to
you
know,
yeah,
consider
the
beginners
also
who
are
trying
to
understand
what
that
maybe
plugin
is
doing
and
making
sure
that
the
terms
or
the
yeah,
the
terms
that
are
being
used
are
like
easy
to
understand
for
beginners
yeah.
B
A
G
A
F
A
A
A
A
Oh,
oh
yes,
okay,
one
observation
was,
did
any
of
the
three
of
you
have
difficulty
because
of
a
small
amount
of
memory
on
your
computer
or
a
unique
operating
system
you're
using.
Maybe
we
should
check
there.
Part
of
me
worries
that
it
probably
is
common
to
have
a
computer
with
four
gigabytes
of
memory
and
that
I
worried
gee
is
that
enough,
etc?
So
so
I
I
guess
my
question
that
I'm,
I
think
we
should
hear
from
each
of
them
is:
were
there
hardware
or
equipment
issues
that
we
could
have
predicted
and
assisted.
A
C
So
when
I
tried
to
log
in
the
first
time
he
gave
me
this
invalid
vlog
on
everyone-
and
I
I
followed-
I
tried
to
follow
the
online
help
theme
they
helped
out
in
the
documentation,
because
there
was
a
link
to
in
case.
I
got
anyone
get
that
error,
so
I
was
trying
to
follow
it,
and
then
there
was
this
setting
that
was
missing
in
my
laptop
it's
I
I
didn't
have
to
follow
us
online.
I
usually
listening.
C
A
Okay
and,
and
so
there
is
a
place
where
we
probably
should
advise
developers,
so
you
were
a
windows-based
developer
and
you
use
the
msi
to
do
an
installation
and
we
should
probably
guide
developers
that
you
that's,
that
it's
better
for
a
developer
on
windows
to
use
the
war
file
to
do
the
installation
rather
than
the
msi,
because
of
permission
problems
that
come.
That's
a
good
one!
Thank
you
all
right,
so
guide
developers
on
windows
and
it
oh
go
ahead.
A
B
A
A
A
A
What
happens
to
the
remaining
open,
pull,
requests,
right,
yeah
and-
and
that's
I
think,
that's
a
good
question
for
what's
what's
on?
What's
next
for
us,
so
let's
talk
through
that
and
let's
take
that.
As
the
first
question,
I
think
what
we
need
to
do
is
more
reviews
of
the
open
pull
requests
right
if
they
haven't
already
been
reviewed
and
approved,
mark
oleg
kristen
and
meg
persuade
the
maintainers
to
merge
and.
A
So,
for
example,
esther
has,
I
think,
five
or
six
pull
requests
submitted
to
the
one
she
was
working
on,
maybe
with
cynthia
one
of
the
two
or
nina.
I
know
yours
does
with
artifactory,
and
the
idea
is
what
I'll
do
is
I'll
build
all
of
those
pull
requests
together
into
a
single
copy
of
the
plugin
and
put
it
in
my
test
environment
so
that
I'm
using
it
day
in
and
day
out,
so
I'm
just
using
it.
A
A
A
So
we've
still
got
a
number
of
pull
requests
left
to
merge
and
review
so
with
the
the
mentors
will
continue
working
on
that
we'll
have
feedback
on
those
discussions
and
ultimately
the
goal
is
to
get
them
into
the
into
the
content
and
merge
into
the
plugins
and
merged
now.
In
addition,
I'd
like
to
submit
a
blog
post
proposing
to
summarize
the
results,
I'm
I'm
intensely
proud
of
what
you've
accomplished.
I
can't
tell
you
how
proud
I
am.
A
A
G
A
A
Great
any,
oh,
oh
and
I
I
had
several
other
points
in
terms
of
things
that
things
that
we
will
ask
for
next
time
will
be
more
systematic
about
it,
right
all
sorts
of
things
in
terms
of
how
to
make
this
process
work.
Well,
so
anything
else
we
should
discuss
today
before
we
conclude
or
meg
meg
were
there
other
things
that
you
needed.
F
A
F
B
B
A
F
G
A
A
So
so
as
an
example
cynthia,
if
you'd
like
to
be
involved
in
helping
with
the
development
of
the
jenkins
get
plug-in,
I
maintain
that
I
would.
I
would
love
to
have
extra
help
if-
and
there
are
other
maintainers
like
me-
who
are
similarly
interested
in
having
people
help
them.
So
you
could
choose
one,
that's
interesting
and
ask
that
maintainer.
May
I
help
you?
E
Also
like
sometimes
if
you're
just
looking
around
or
there
are
sometimes
problems
inside
of
the
jenkins
jira
that
are
tagged
as
like
newbie
problems
or
things
that
are
easier
to
tackle.
Sometimes,
if
you
go
to
the
individual
plug-ins,
you
can
see
that
they
have
github
issues
they
some
some
plug-ins
use
it
it's
again
because
it
is
open.
Source
and
jenkins
is
very
permissive.
You,
the
individual,
it's
up
to
the
individual
maintainers
to
say
how
they
track
their
issues,
so
it
could
be
in
one
or
the
other.
E
I
think
a
lot
of
people
are
using
github
issues
now,
but
you
can
go
there
and
then
sometimes
they're
tagged
with
good
for
beginners,
and
you
can
just
kind
of
work
on
it
and
submit
the
patch
or
submit
a
pull
request
and
that's
a
good
way
to
get
started
as
well.
There's
sometimes
individual
tools
that
need
help
too.
So
reviewing
free
aprs.
F
E
That's
a
really
good
point
about
the
office
hours
meg
too,
because,
like
there's
different
special
interest
groups
for
different
tasks.
So
even
if
you
go
and
you
you
can
just
sit
in
the
meeting
and
listen
if
you
don't
want
to
feel
like
you
want
to
say
anything
or
just
to
kind
of
like
learn
about
it
and
depending
on
what
they're
doing
that
meeting
they'll
be
talking
about
different
problems
just
to
kind
of
get
in
like
to
get
started
with
figuring
out.
What
else
is
happening
in
jenkins.
F
A
A
So
kristen
referenced
this
page,
which
is
the
friendly
issues
page
so
in
this
table
that
you
see
here
of
core
get
plug-in
warnings.
Ng
each
of
these
issues
has
been
tagged
as
friendly
for
someone
who
is
a
first-time
contributor.
Now
they
they
commonly
require
java
skills.
So
it's
assumed
that
you're
interested
in
learning
java
and
willing
to
work
with
java,
but
that's
the
kind
of
thing
that's
needed
or
and
in
the
case
of
warnings
ng.
A
So
here
we
would
look
for
see
good
first
issue
and
here
is
a
set
of
documentation,
things
that
are
good
first
issues
and
it's
pretty
common
for
plugins
that
are
using
github
to
track
issues
that
this
good
first
issue
is
what
they'll
use
to
flag.
This
is
a
good
choice
for
someone
who's,
a
first-time
contributor,
kristen.
A
A
A
E
All
right-
and
I'm
actually
just
thinking
about
this
too
another
place
you
might
be
able
to
find
first
issues
is:
if
you
look
at
the
google
summer
code
project
page,
they
have
those
actually,
if
you're
interested
next
year.
Unfortunately,
the
period
of
submissions
and
stuff
has
ended
already
for
this
year,
but
next
summer,
if
you're
a
student,
I'm
not
sure
if
any
all
are
students,
but
there's
a
chance
to
be
able
to
participate
in
google
summer
of
code.
A
A
G
I
just
want
to
really
really
appreciate
all
the
mentors
for
the
time
for
your
time
and
the
sections
we
had,
the
mentorship,
the
corrections
and
everything
like
the
journey
was
was
worth
it
and
this
experience
it's
it's
something
I
would
really
like
to
have
again
yeah,
because
I
was
exposed
to
so
many
things.
I
learned
practically
everything
it's
my
first
time
of
contributing
and
it
was
it
was
so
cool.
So
I
really
appreciate
all
of
you.
Thank
you
so
much.
Thank
you
so.
D
A
Actually
well
and
one
more
reminder:
I'm
preparing
a
talk
proposal
for
devops
world
and
would
love
to
have
and
it
will
be
remote
this
year.
So
I
would
love
to
have
the
three
of
you
if
you're
willing
be
part
of
that
talk
so
I'll
I'll,
send
you
comments
on
on
how
I
think
we
should
do
it
etc,
because
I
think
it's
it's
fun
to
have
talks
where
you
say
hey.
This
is
our
experience
and
this
is
what
went
well.
This
is
what
didn't
go
well,
and
so
so
I
will.