►
From YouTube: She Code Africa contributhon sync-up. April 26, 2021
Description
At this session we discussed the closedown week of the contributhon: prioritizing completion of pending pull requests, the upcoming retrospective and the summary blogpost. We also had a Q&A with students about reverting changes in Git and contributing to Jenkins after the event. Meeting notes: https://docs.google.com/document/d/1xhmEtwYIlGuuKtwn6Ek8DWyBEkPFA5q8CfWRRL7xZ9U/edit#heading=h.z4madwwp083a
A
Hello
yeah
today
is
april
26th.
We
are
recording
the
meeting
of
chicago
contributor,
so
we
have
several
contributors
on
the
call
and
we
will
just
go
through
the
updates
talk
about
the
close
down
of
the
event
and
then
just
agree
on
the
whatever
you
want
to
discuss.
A
A
A
A
A
And
actually
the
best
thing
to
focus
on
is
finishing
your
work,
because
all
of
you
have
multiple
open
pull
requests,
so
it
would
be
better
if
you
focus
on
generalizing
them,
so,
instead
of
creating
new
pull
requests,
etc,
let's
focus
on
delivering
what
has
already
started,
because
it's
better
to
complete
less
but
to
deliver
that
to
jenkins
users
and
yeah.
My
recommendation
would
be
to
do
that.
A
D
A
A
I
recommend
to
focus
on
that
if
there
are
open,
pull
requests
which
are
missing,
pull
which
are
missing,
reviews
again,
consider
focusing
on
getting
reviews,
ask
help
from
the
community
from
mentors
if
needed,
so
that
we
could
get
this
pull
request
over
the
line.
If
you
want,
you
can
totally
submit
new
pull
requests.
D
A
A
A
A
For
example,
anyone
all
mentors
and
students
invited
just
put
their
notes
there.
For
example,
I
can
suggest
my
change.
A
A
You
can
provide
some
examples.
We
have
a
similar
feedback
for
gsoc,
so
there
is
a
google
doc
called
jsoc,
username
mentor
testimonials.
We
started
just
several
weeks
ago
and
you
can
find
some
examples
of
feedback
we
collected
from
our
participants.
So
you
can
see
that
this
feedback
was
collected
in
video
form
or
in
text.
You
basically
can
do
the
same
or
whatever
you
prefer.
A
A
So
if
you
work
in
agile
environments,
you
may
have
seen
that
teams
joined
together,
sometimes
to
discuss
what
went
well,
what
could
be
done
better
and
it's
a
very
good
practice,
because
it
allows
the
team
to
iterate
and
improve
how
they
collaborate
with
each
with
each
other
and
to
improve
their
processes
and
for
each
program
we
run
engineers.
We
recommend
to
do
a
public
retrospective
and
we
basically
invite
everyone
to
submit
their
experiences
for
three
items.
A
So
what
went
well
what
we
do
better.
A
A
A
So
something
like
that
and
yeah.
This
is
rather
good
experiences,
so
usually
they
don't
require
too
much
discussion,
but,
for
example,
there
are
things
we
could
do
better,
and
this
is
also
something
we
can
add.
So,
for
example,
I
can
say
that
it
needs
a
better
engagement
with
wider
jenkins
community.
A
E
A
Okay,
so,
for
example,
yeah
I
put
just
one
of
my
idea,
yes
and
what
clarification
so,
for
example,
if
you
disagree
and
it's
perfectly
fine
to
disagree,
you
can
just
put
a
comment
there,
or
maybe
you
make
your
suggestion.
If
you
see
other
things,
we
could
do
better.
You
can
just
again
make
a
suggestion
added
to
the
list
and
then
we
will
be
discussing
what
went
well
and
what
could
we
do
better
and
we
will
be
defining
action
items
for
the
future.
So,
for
example,
I
can
propose
let's
say.
A
B
A
Yeah,
it's
better
to
do
it
synchronously,
because
meetings
happen
quite
rarely
and
the
time
is
not
a
convenient
for
participants.
So
if
you
do
it
synchronously,
you
can
just
chat
with
the
entire
community.
So
please
feel
free
to
put
any
ideas
here
and
on
friday
we
will
discuss
them.
I'm
not
sure
I
will
be
able
to
join
it's
super
late
in
my
time
zone.
D
So
the
retrospective
will
be
done
on
friday
right.
I
was
supposed
to
to
write
them
down.
A
A
Usually,
when
big
teams
do
retrospectives,
they
vote
on
the
ideas
on
the
discussion
so
that
we
can
get
more
feedback,
I
don't
think
we
will
be
doing
that
for
chicot
africa,
because
we
have
only
a
few
participants,
so
we
can
just
discuss
them
the
things
on
the
call
but
yeah,
it's
still
essential
to
put
your
notes
and
your
experiences
there
so
that
we
can
improve
and
I'm
pretty
sure
that
africa
organizers
will
be
also
asking
for
your
feedback
in
some
form
after
the
event
so
yeah,
you
can
basically
start
preparing
that.
B
A
A
So
if
you
see
something
like
that,
yeah
please
put
them
there,
because
it
would
be
a
really
valuable
feedback
to
us
as
a
community.
We
don't
always
see
issues
because
we
work
on
this
project
for
years
or
for
decades
like
me
and
mark
so
yeah.
A
A
A
C
B
And
be
honest:
if
there's
anything
that
you're
concerned
about
that
you're
uncomfortable
writing
for
everybody,
I
would
feel
free
to
send
a
slack
message
just
to
mark
or
to
any
one
of
us
actually.
B
But
I
want
you
to
feel
that
you
can
be
honest
and
we
don't
want
to
make
you
uncomfortable,
but
we
just
want
to
yeah.
As
our
leg
says,
we
want
to
make
it
so
that
next
year's
people
have
a
better
experience,
so
we're
always
trying
to
improve
things.
A
Yeah,
so
again,
if
you
see
that
something
went
bad,
no
repercussions
at
all,
we
are
looking
for
feedback,
so
it's
not
something
like
it
will
influence
anything,
and
actually
any
negative
feedback
is
also
appreciated.
As
long
as
it's
justified
and
actionable.
D
A
So,
for
example,
there
are
ways
there
are
multiple
ways
to
share
that,
for
example,
if
you
want
to
shape
it
back
with
organizers,
so
it's
shikota
africa
or,
for
example,
you
can
check
it
back
with
mark
weight
for
internal
stuff,
and
you
can
also
share
feedback
with
the
jenkins
governance
board.
If
something
went
wrong.
A
Yeah,
I'm
not
sure
whether
mark
referenced
to
that
in
the
beginning,
all
contributors
are
expected
to
follow
this
code
of
conduct
and
if
something
goes
wrong.
For
example,
if
you
get
let's
say
a
toxic
response
in
your
pull
request
or
whatever
yeah,
you
can
report
that,
so
that
jenkins
governance
board
can
follow
up.
A
No
need
to
postpone
that,
because
again
we
are
trying
to
improve
the
community
and
again
there
will
be
no
repercussions
or
whatever,
because
yeah
that's
how
the
jenkins
community
works.
A
B
A
This
is
on
the
message
that
she's
f
key,
so
I'm
not
sure
whether
she's
back
okay,
there
is
a
question
from
leicester.
Could
we
still
contribute
after
this
program?
Of
course?
Yes,
so
you're
welcome
to
contribute
to
the
jenkins
project
at
any
time,
as
well
as
pretty
much
everybody
else
so
yeah.
If
you
want
to
keep
contributing,
please
do
so,
whether
it's
related
to
chica
africa
or
not.
A
We
also
consider
participating
in
more
rich
programs,
so,
for
example,
yeah
you
might
be
eligible
for
some
of
them.
So,
as
we
discussed
before
chicago
africa,
contributing
participants
might
be
technically
eligible
for
google
summer
of
code,
but
the
application
deadline
is
closed.
At
the
same
time,
there
are
other
events,
so,
for
example,
yeah
there
will
be
oktoberfest
in
october.
They
will
be
outrageous
in
winter,
so
the
application
phase
for
summer
is
also
closed.
Then,
hopefully,
next
year
we
will
be
accepted
to
google
seasonal
talks.
A
A
Yeah,
of
course,
so
yeah
the
main
objective
for
us
for
african
contribution
for
other
events.
Firstly,
to
provide
a
great
experience
to
participants
to
let
them
learn
it's
the
first
power.
Second
priority
is
to
introduce
them
to
open
source
communities
and
to
get
them
onboarded
to
the
jenkins
community,
if
possible,
or
maybe
to
other
open
source
community,
because
it's
also
equally
available
and
the
third
priority
is
actually
to
deliver
something.
D
A
E
A
Yeah,
sorry
because
yeah
it
really
didn't
follow.
So
I
guess
helping
with
the
pull
request
but
yeah
you
didn't
understand,
which
one
sorry
about
that.
D
I
think
audrey
is
better.
D
A
A
A
Request
for
code
examples
to
workflow
basic
steps.
Plugin,
when
I
push
commits,
I
found
out
that
it
includes
other
commits
from
another
branch.
How
can
I
remove
them?
So
in
this
case
you
would
need
to
rebase
the
branch
and
yeah
for
that
there
are
tools
in
jenkins.
Sorry
inkit.
I
cannot
show
you
a
few
examples.
Second,.
A
Okay,
so
for
that,
actually
there
are
two
common
tools:
one
is
a
git
rebase,
another
one
is
cherry
peak
and
actually
for
the
most
common
cases.
I
recommend
the
latter
one
so
how
it
works.
You
have
a
three
and
from
this
3
you
can
take
a
particular
commit.
So,
for
example,
I
can
show
you
an
example
in
the
web
in
the
ui,
because
it's
easy,
but
you
can
do
the
same
in
the
common
line.
A
So,
for
example,
I
have
jenkins
remoting,
so
I
won't
commit
it
anyway
and
you
can
see
that
there
is
just
a
master
branch
which
includes
a
fuel
request.
Let's
imagine
I
want
to
put
something
to
the
previous
release,
so
here,
for
example,
I
will
create
a
branch,
for
example,
641.
A
Yeah
and
here
for
example,
I
want
to
take
a
commit,
so
you
can
see
that
if
I
just
merge
the
three
I
will
get
all
the
history
of
commits.
So
it's
probably
the
case.
You've
got
because
yeah
most
likely,
you
just
started
building
a
new
branch
on
the
top
of
the
wrong
page
and
here
what
I
can
do,
for
example,
if
I
want
to
take
a
specific
commit
like
this
one,
I
can
call
it
cherry
pick
command.
So
what
it
does
is.
A
Basically
it
takes
the
same,
commit
contents
and
applies
you
them
to
your
current
range.
So
I
got
it
here
and
now
you
can
see
that
I
have
a
new
branch,
removing
four
or
six
one
and
then
includes
just
one
community
that
I
cherry
picked.
Then
I
can
push
this
branch
to
my
fork
and
submit
a
pull
request.
Just
with
this
content,
it's
one
of
the
ways.
A
A
Okay,
then,
if
no
other
questions
thanks
everyone
and
talk
to
you
on
friday,
I
will
try
to
join
the
final
meeting,
if
not
anjali,
mark
and
mark
will
be
able
to
handle
that,
and
thanks
again
for
all
your
contributions,
so.
A
Yep,
I
am
happy
to
confirm
that
so,
let's
focus
on
finishing
the
program
and
yeah
celebrate
that
once
we
are
done.