►
From YouTube: GSoC 2023 Office Hours - March 30, 2023
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
Okay,
good
evening,
good
afternoon
or
good
morning,
people
around
the
world
here
welcome
to
this
ghoul
summer
of
Code
office
hours
of
today
March
the
30th
to
welcome
everybody
on
the
meeting
and
listening
to
the
recording
so
we're
slowly
reaching
no
we're
not
slowing
we're
very
rapidly
reaching
the
end
of
this
phase
of
Google
summer
of
code,
so
we're
reaching
the
end
of
The
Proposal
submission
apart.
So
just
give
a
quick
update
where
we're
standing.
A
So
we
have
a
total
of
34
3-4
drafts
that
were
submitted
for
review
on
those
34.
Eight
drafts
had
to
be
withdrawn
or
discarded
because
they
were
on
the
three
withdrawn
kojic.
So
a
lot
of
words
work
had
to
be
put
back
either
in
the
fridge
or
put
aside,
and
people
are
realigned
apart
from
Chris
Stern
I
think
we
as
a
community
as
a
mentor
Community
made
a
terrible
job
in
reviewing
and
Advising
on
all
these
drafts
I
apologize
for
for
that
we're
still
not
the
end
of
the
draft
period.
A
Now.
The
reason
for
that
is
that
we
have
about
three
times
as
many
proposals
or
drafts
than
we
had
last
year,
and
we
have
exactly
the
same
amount
of
mentors
for
that.
So
we've
been
overwhelmed
by
the
questions
on
guitar
and
the
very
active
traffic
over
there,
the
different
documents
to
to
review,
so
we
will
definitely
improve
that
and
make
it
better
I.
Thank
you
for
your
patient.
All
16
proposals
have
already
been
submitted
on
the
gsoc
portal.
A
Some
names
and
drafts
I
recognize
some
are
coming
out
of
the
blue.
The
ones
coming
from
out
from
out
the
blue.
They
need
to
be
very,
very
good,
so
proposing
the
draft
make
it
available
and
have
it
discussed
by
the
community
is
the
way
to
go
in
order
to
succeed.
A
It
is
now
time
and
I'm
talking
to
the
would-be
contributors.
It
is
now
time
to
submit
your
proposal.
Don't
procrastinate,
don't
you
can
expect
some
reviews?
I
I
a
Mark
I
think
you
want
to
give
it
a
push.
I
would
I'm
wanting
to
make
a
push
of
it
since
the
beginning
of
the
week,
but
been
busy
with
other
things
yeah
for
Sunday
evening.
I
think
there
there
will
be
no
reviews
anymore
by
mentors
so
because
the
deadline
is
for
Tuesday
yeah.
B
So
well,
the
the
Google
summer
of
code
rules
allow
them
to
submit
and
then
overwrite
their
submission
with
a
later
submission
right.
So
there's
yes,
there's
no
harm
in
then
submitting
early
and
then,
if
they
get
additional
feedback
and
decide
to
react
on
it,
they
can
replace
their
submission
with
an
improved
submission.
So
there's
no
shame
in
that
and
that
means
submit
and
then
you
can
submit
and
replace
your
PDF
with
another
PDF.
That's
a
better
one!
That's
that's
perfectly
fine.
Okay,.
B
A
Frozen
right
and
it's
the
only
one
we
use
for
grading
good
question
the
deadline.
Remember
is
Tuesday
April
4th
at
1800
UTC
that
this
is
midnight
in
Asia
or
India,
using
India
as
a
reference.
A
B
A
Yeah
during
so
once
the
the
proposals
are
submitted
and
Frozen.
This
is
where
the
mentors
will
start
grading
in
making
the
selection,
so
contributors,
would-be
contributors,
can
then
rest
a
little
bit
and
think
and
and
do
other
things.
We
will
keep
the
office
hour
open.
So
I
will
open
the
channel.
It
will
not
be
recorded
I'll
just
keep
it
as
a
social
hangout.
A
If
people
want
to
chat
or
discuss,
Indian
people
can
try
to
explain
me
the
rules
of
cricket
I'm,
more
than
eager
to
learn
them,
but
we
just
to
be
together
and
the
channel
will
be
open
and
it's
not
required
at
all
to
attend.
A
A
So
it
will
be
announced
by
mail
by
Google
to
the
people
that
will
will
have
been
selected
will
also
publish
exactly
at
that
time.
Jenkins
blog
post
and
we'll
update
the
the
project
pages
with
the
selected
projects,
and
there
will
be
also
announcements
on
social
media,
Twitter
and
Linkedin.
So
this
is
the
official
announcement
where
the
people
select
it
will
be.
A
We
will
hold
a
special
office
hours,
the
Friday
just
after
that
so
Friday
May
5th
at
1500
UTC
usual
time,
but
just
shifted
by
one
day
where
we'll
meet
we'll
we'll
congratulate
the
selected
Google
summer
of
code
contributors
will
will
answer.
Questions
maybe
give
suggestion
to
the
people
that
were
not
selected,
because
they're
they're
still
things
in
interesting
and
important
things
that
they
can
do
to
learn
from
the
experience
contribute
to
the
community.
A
There's
a
lot
of
very
exciting
things
that
can
be
done
so
we
can
discuss
them
and
we
will
also
stake
out
what
will
happen
the
weeks
after
for
the
selected
people
and
the
mentors
so
they're,
the
scope
of
the
office
hours
will
be
much
closer.
A
closed
for
the
for
the
people.
People
are
interested
to
listen
and
see
what's
happening,
they're
welcome
we're
working
in
the
open.
A
So
these
are
the
General
announcements.
Now,
I
I,
we
have
or
I
have
some
more
unpleasant
comments
to
do
when
there
were
some
some
discussions
and
and
complaints
earlier
this
week
and
I
would
like
to
come
back
on
that
and
clarify
a
couple
of
things.
A
The
first
in
in
most
annoying
thing
for
me,
was
there
were
some
precise
complaints
about
comment
bullying
what
I
call
with
that
are
people
that
anonymously
put
comments
on
documents
that
are
useless
or
rude
or
even
suggest
a
very
unpleasant
things
like
saying
or
implying
that
the
the
proposal
is
useless
and
should
be
removed.
A
I
call
that
bullying
some
people
might
see
it
as
just
a
prank
I.
Personally
don't
and
we
as
origami
end
as
organization,
don't
see
it
that
way.
It's
an
inappropriate,
behavior
and
especially
now
I
hope
I
will
not
do
hurt
somebody,
but
as
it
was
aimed
at
sonali,
who
is
a
young
lady
if
I'm
not
mistaken,
which
makes
it
even
worse.
A
So
it's
not
acceptable
is
disrespectful.
It's
not
in
the
spirit
of
Open
Source
and
it's
not
an
adult
Behavior.
A
Will
stop?
There
is
no
other
comments
on
that.
This
is
not
acceptable,
especially
as
that
we
as
a
community
follow
the
Jenkins
code
of
conduct,
which
is
really
very
important,
guiding
principle
and
in
everything
that's
doing
with
our
external
communication.
Alyssa
is
somewhere
the
the
the
the
owner
and
can
really
explain
very
well
what
this
Jenkins
code
of
conduct
is
and
so
Alyssa.
If
you
could
clarify
that
with
with
us,
yeah.
D
So,
as
John
Mark
mentioned,
the
the
code
of
conduct
is
our
guidance
into
the
Jenkins
communities.
Cultures
are
our
value
and
our
philosophy
so
I
put
a
link
in
the
chat
window
and
I'm
gonna
try
to
share
my
screen
with
you
so
that
I
can
marking
it.
Okay,
there,
it
works,
I'm,
sharing
my
screen
so
just
to
make
sure
that
there's
no
misrepresentation
or
any
misunderstanding
I'm
going
to
read
or
briefly
read
our
code
of
conduct
just
so
that,
hopefully,
when
you
hear
it
it'll,
you
know
it.
D
It
absorbs
better,
so
Jenkins
code
of
conduct
as
community
members,
contributors
and
maintainers
of
this
project
and
in
the
interest
of
fostering
an
open
and
welcoming
Community,
we
commit
to
respect
all
people
who
participate
in
the
community.
Through
reporting
issues,
posting
feature,
requests,
updating,
documentation,
submitting
pull
requests
or
patches
and
other
activities.
D
Our
pledge,
as
we
as
members,
contributors
and
leaders,
pledge
to
make
participation
in
our
community
a
harassment-free
experience
for
everyone,
regardless
of
age
body,
size,
visible
or
invisible,
disability,
ethnicity,
sex
characteristics,
gender
identity
and
expression,
level
of
experience,
education,
socioeconomic
status,
nationality,
personal
appearance,
race,
religion
or
sexual
identity
and
orientation.
We
pledge
to
act
and
interact
in
ways
that
contribute
to
an
open,
welcoming,
diverse,
inclusive
and
healthy
community.
D
So
I
know
that
this
is
a
probably
a
lot
of
things
to
digest,
but
just
a
bit
bare
basic
Foundation
is
to
take
away
from
this
is
be
kind
to
each
other,
respect
each
other
and
help
each
other
out.
That's
how
our
community
grows.
That's
what
our
values
are
as
a
community,
because
we
want
to
make
this
a
welcoming
and
diversified
Community
for
everybody.
A
A
We
have
here
in
this
meeting
two
members
of
the
Jenkins
board,
Alexander
and
Mark
Waite,
who
look
and
follow
what
we
do
and
might
take
actions
now
practically
we
cannot
defend
the
system
from
defacing
or
or
these
kind
of
comments,
comments,
bullying
which
happens
quite
not
quite
often,
but
happens
regularly
because
of
the
way
Google
form,
Google,
doc,
Google
doc
is
configured
and
because
we
want
to
be
as
open
as
possible.
A
We
give
the
opportunity
to
anyone
to
add
comments,
and
this
is
something
we
feel
is
important.
We
if
we
want
to
require
people
and
only
nominee
nominal
peoples,
to
be
able
to
do
comments.
There
will
go
against
the
flow
against
the
spirit
of
openness
of
what
we
do
so
we
want-
and
we
remind-
and
we
we've
been
very
strong
here
in
reminding
what
is
the
Open
Source
Code
of
Conduct
or
the
one
we
use
here
at
Jenkins.
A
If
these
type
of
behaviors
continue,
we
might
have
to
use,
then
what
I
call
or
Mark
called
the
nuclear
weapon
and
then
force
closed
comments
that
we'll
have
to
maintain,
who
are
the
people
who
are
able
to
do
the
comments
and
all
the
comments
assigned
and
logged
I
would
be
very,
very
disappointed
by
the
end,
because
that
would
mean
that
I
failed
in
my
work
as
mentoring
this
this
community
or
this,
this
group
of
people,
so
I
trust
you
with
that.
A
I
have
the
same
comment
to
do
about
review
comments,
closing
I've
seen
and
we
we
all
have
seen
that
either
logged
in
people
or
Anonymous
people
found
it
very
funny
to
close
comments
so
that
they're
not
seen
anymore
by
other
people
or
by
the
the
author.
It's
easy
to
do
it's
fun.
It's
it's
you're,
just
annoying
people
doing
that!
No
it
it
has
an
impact,
and
don't
do
that.
Only
the
author
of
the
the
comments
or
the
author
of
the
document
are
allowed
to
close
a
comment.
Behave.
A
Well,
it's
it's!
It's
like,
where
I
have
several
examples
in
my
mind,
but
when
you're
in
a
community
when
you're
together,
don't
don't
just
grab
the
food
in
somebody's
else's
plate
just
behave
Mark
you
wanted
to
add
something
or
so.
B
You're,
making
a
sign
any
any
one
of
the
any
one
of
the
candidates
is
welcome
to
choose
if
they,
if
they
wish
to
disallow
Anonymous
review
and
then
assign
specific
people
to
review
I.
Believe
you
each
have
access
to
our
email
addresses.
So,
if
you
need
to,
you
are
welcome
to
assign
I'll,
give
you
mine,
I'm
mark.earl.weight
gmail.com,
and
you
are
welcome
to
assign
specific
reviewers.
That
will
assure
you
that
you
don't
get
an
anonymous
comments
and
Anonymous
not
getting
Anonymous
comments
means
you
also
won't
have
Anonymous
people
closing
review
comments.
A
Now
the
the
next
topic
and
then
we're
we're
open
the
this,
the
the
the
floor
for
questions
and
discussions.
A
A
Now
I
have
a
couple
of
comments
on
that
and
I
will.
Let
then
the
other
lead
mentors
add
their
own
comments
here.
We
have
a
crowd
of
people,
so
we
have
a
lot
of
people
that
are
presenting
competing.
I
need
to
accept
that
on
a
limited
number
of
project
ideas,
you've
seen
the
number
of
drafts
that
have
been
written.
So
that
means
that
Joel's
thinks
questioning
and
so
is
expected.
But
there
is
something
stronger
behind
the
whole
discussion.
A
What
is
not
acceptable
or
not
in
and
here
we're
all
playing
with
nuances,
Gray
Zone,
so
there's
no
rules
that
can
be
followed
by
a
judge
and
no
where
it
becomes
where
this
sharing
of
idea,
com
of
Goodwill,
Community
working
together
is
definitely
discussable
is
when
we
see
text
that
has
been
copied
and
where
this
is
obvious.
Plagiarism
and
this
will
be
detected-
this
is
these
are
the
kind
of
things
that
mentors
are
looking
for,
so
copying,
cheating
or
these.
A
These
kind
of
things
is
not
relevant
at
this
phase
of
the
the
process
of
building
the
The
Proposal
and
in
the
getter
Channel,
there
was
also
reference
to
rules
from
Google
summer
of
code
and
I
didn't
want
to
get
into
that
debate
on
the
getter
Channel.
These
rule
apply
for
the
possible
exclusion
of
selected
gsoc
contributors
and
that
get
paid,
and
this
is
that,
for
instance,
using
other
people's
codes
without
attributing
it
or
these
kind
of
which
is
there,
it's
stealing
other
people's
work.
A
A
In
other
circles,
you
have
a
knife
between
your
teeth
and
you're,
going
to
kill
the
other
one,
and-
and
this
is
the
rat
race
now
my
personal
opinion
I,
don't
want
to
be
part
of
any
Rat
Race
that
way,
but
here
there's
another
choice.
I
know
the
world
is
not
as
simple
as
I
I
wished
it,
but
so
this
is.
This
is
important.
A
Now
it's
it's
gray,
it's
in
their
very
mixed
feelings
about
that
and
I
can
understand,
especially
if
it
comes
together
with
very
intimidating
behaviors
like
these.
This
commenting
and
there
we're
very
strict.
This
is
definitely
a
No-No
and
if
you
add
this
impression,
oh
somebody
else
has
been
stealing
and-
and
here
this
is
not
what
we're
talking
about
this
in
I
I
use
the
expression
before
remember
with
g-soc.
It's
not
the
goal.
A
A
Only
a
few
will
be
selected
and
and
I
I
want.
Also,
to
be
very,
very
honest.
We
made
our
calculation.
There
will
be
only
four
people
selected
in
all
all
the
crowd
that
has
been
participating
to
that,
but
not
being
selected
does
not
mean
that
first,
you
failed
anything
and
that
you
didn't
learn
anything
and
that
the
road
is
now
finished
not
at
all,
and
this
is
something
we
can-
we
can
discuss
in
a
in
another
in
another
phase.
A
The
mentors
will
evaluate
the
proposals
and
I'm
just
going
to
remind
what
are
the
criterias
that
I
refreshed
all
the
mentors
that
and
and
joined
them
to
keep
these
in
mind
when
you
grade
the
proposals,
so
is
it
a
clear
and
well-defined
proposal
must
is
the
applicant?
Does
he
have
enough
skills
and
experience
to
quickly
hit
the
ground
running?
A
Applicants
has
completed
contributions
to
the
project
prior
to
submission
and
attended
office
hours.
These
are
evidence
of
his
commitment
to
the
project
and
understanding
how
our
community
works.
The
applicant
has
demonstrated
adequate
communication
skills
with
his
submissions.
His
interactions
on
forms
or
getter
on
PR
conversations
applicant
has
the
right
stuff
to
complete
successfully
his
described
gsoc
project.
It
is
globally
the
and
it's
not
only
putting
a
mark.
There
will
be
also
an
open
discussion
on
all
the
the
The
Proposal.
A
So
the
last
thing
and
I
conclude
my
part
on
that
and
give
the
word
to
other
mentors.
There
will
be
no
exclusions
based
on
article
XYZ
and
so
on.
A
If
we
have
evidence
or
debts
for
some
reasons,
someone
obviously
cheated,
because
he
copied
parts
of
text,
we
will
see
it
and
we'll
just
not
select
The,
Proposal,
full
stop
and
so
I
we're
going
to
leave
that
discussion
that
was
raised
by
two
of
you
and
we'll
leave
it
there.
Now.
The
last
point
I'm
going
to
say
thank
you
to
have
raising
these
points
and
concerns.
A
Thank
you
to
have
reached
out
to
to
the
org
admins
to
explicitly
say
what
your
concerns
are.
We
take
it
seriously
and
we
gave
you
the
the
answer
about
that
now
who
would
like
to
add
something
to
what
I
to
what
I
said.
E
A
Thank
you,
Alex
leave
the
mic
open
for
a
couple
of
seconds
and
then
I'll.
We
can
start
taking
questions
from.
B
The
audience
there
was
a
question
raised
by
by
Mahmoud
regarding
hey
is
four
pull
requests
enough.
It's
a
fun
topic
because
almost
always
in
software
development
asking
is
number
enough
will
will
get
a
completely
ambiguous
answer
because
we
rarely
can
successfully
count
things
in
an
intellectual,
prop
intellectual
effort
and
decide
if
it's
good
or
not.
We
certainly
do
review
pull
requests
as
part
of
the
review
process.
The
most
important
thing
is
your
proposal,
not
your
pull
request.
B
It's
your
proposal
make
a
good
proposal
but
know
that
we
will
look
at
your
contributions
in
other
ways
as
well.
I,
we
don't.
We
have
full
range
of
things
we
can
evaluate.
We
can
look
at
your
public
history
on
GitHub.
We
can
look
at
pull
requests
you've
submitted.
We
can
look
at
comments
in
chat
channels.
Those
things
are
all
viable
and
can
help
us
as
we
try
to
make
our
best
decision
again.
Proposal
is
the
most
crucial
thing.
B
See
and
I
have
hit
my
time
limit.
John
Mark
I
apologize
I
need
to
give
control
of
the
session
to
I'm
gonna
hand
off
to
Alyssa
so
that
she
becomes
the
the
host
yep.
A
A
A
A
F
That
you
have
said
that
for
the
Android
project
I
make
you
want
something
that
is
on
the
left.
Part
left
part
of
the
pipeline,
so
what
I
have
proposed
is
like
basically
adding
few
stages
to
the
pipeline
and
few
things
like
you
wanted
on
your
few
things.
You
have
raised
on
your
issues
on
Gretel,
on
that
Repository
building
changes
and
few
things
like
that.
You
have
mentioned
on
the
project
piece
like
you
want
to
build.
You
want
to
have
multiple
emulators
or
something
like
that.
F
So
so
I
have
proposed.
That
is
this
enough,
for
do
you
want
to
like
add
something
more
that
I
can
look
into
before
submitting
my
proposal.
C
I
would
like
to
hear
about
your
ideas.
Mine
are
okay,
but
yours
are
way
better
I'm.
That's
for
sure.
So,
I
won't
tell
you
what
kind
of
ideas
you
should
have
just
promote
them.
If
you
have
some
and
will
evaluate
them
later
on
this.
F
A
C
A
A
C
F
I
mean
I
use
it.
Like
my
question
is:
do
you
see
that
you
want
something
on
the
left?
What
does
that
signifies
like
left
part
of
the
that
is
left
part
of
pipeline,
or
something
like
that?
You
say
two
weeks
back
on
this.
E
C
No
yeah
but
I
think
I
think
I
wanted
to
say
that
for
Android
or
mobile
applications
generally,
you
don't
want
the
end
user
to
discover
that
something
is
not
going
well
with
that
app.
You
know
we
want
to
try
to
catch
all
the
errors
before
the
application
goes
to
production.
So
what
I
think
I
meant
when
I
said
shiftless
shift,
lift
yeah
shift
left
so
try
to
catch
all
the
errors.
C
All
the
code
flows
all
the
things
that
could
make
the
application
a
better
quality
application
that
end
user
won't
have
to
face
strange
issues,
errors
and
so
on.
So
that's
what
I
meant
so,
of
course
static
analysis,
unit
testing,
of
course,
instrumented
testing.
But
if
you
have
any
other
ideas
that
could
ameliorate
the
code
like,
for
example,
dependency,
checkers
linter,
whatever
you
have
experience
with
go
ahead
and
propose
the
goal
is
to
have
the
best
quality
application
possible,
even
if
it's
an
empty
application
to
start
with
foreign.
G
I
hope
you're
having
a
great
time
I
just
wanted
to
say
thank
you
for
clearing
everything.
Our
thing
and
I
have
something
to
this.
Discuss
related
with
my
proposal.
Can
I
go.
A
G
I
was
thinking
like
I
can
maybe
add
a
default
user,
because
we
want
a
quick
start
for
the
Jenkins
and
I
think
it
will
help
them
out
if
they
have
the
tutorials
as
a
default
user
and
all
the
plugins
are
already
installed
and
they
just
want
to
like
spend
their
hands
around.
So
is
it
a
good
idea?
G
A
I
I
think
your
your
gut
feeling
is
is
good
and
the
quick
start
should
have
enough
components
pre-configured,
so
that
the
person
who
tries
it
out
has
everything
the
minimal
required
to
do
yes
or
to
so
using
Jenkins
configuration
as
code
to
configure
as
much
as
possible,
for
instance,
for
me,
is,
is
a
must
for
this.
A
Exactly
so,
to
have
a
good
handful
of
of
plugins
that
that
people
generally
used
or
are
interested
in
the
purpose
of
of
it
is
that
they
have
enough
to
get
a
good
impression
of
what
Jenkins
does
so
you're
on
exactly
on
the
right
directions.
A
Okay,
there
was
a
question
from
jakruti
that
has
already
been
answered
by
Adrian.
We,
we
don't
count
the
the
number
of
times
you've
been
on
on
the
office
hours
and
and
so
on.
So
it's
so
we're
now.
The
phrasing
is
is
not
correct.
Now,
I
apologize
for
that
is.
These
are
hints
that
shows
the
engagement
to
the
community
and
how
the
people
understand
and
interact
it
with
that,
and
we
look
at
it
in
a
holistic
way
so
globally.
So
but
the
way
Adrian
answered
I
think
so.
A
You're
you're
reassured
I
guess
so
that
a
question
for
Bruno
Patron
had
to
go.
Okay.
A
That's
good.
Thank
you.
Last
word:
I'm,
going
to
make
a
small
sales
page
I'm,
going
to
share
something.
That's
near
to
my
heart.
Some
people
had
their
proposal
canceled
because
they
were
running
on
a
project
that
was
removed
and
they
some
of
them
had
a
very
interesting
reaction.
I,
really
appreciated
that
they
continued
working
on
the
idea,
the
project
idea
and
submitted
pull
requests
and
continue
thinking
and
interacting
and
were
looking
in
ways
to
contribute
to
the
community.
A
Don't
forget
that
Google
summer
of
code
is
a
way
to
enter
in
that
world
of
Open
Source,
but
there
are
other
ways
to
to
explore
that
world
and
the
last
comment
I'd
like
to
do
especially
for
young
professionals
or
people
that
are
still
studying
open
source
is
a
wonderful
School
to
learn
more
than
just
what
your
teachers
tell
you.
They
only
teach
you
a
very
little
part
of
the
real
stuff
and
the
real
stuff.
You'll,
learn
it
by
gaining
experience
and
exploring
it
with
with
open
source.
A
A
Google
sum
of
code
is
not
the
end
of
the
road
and
we've
seen
some
very
positive
attitudes,
and
this
makes
me
happy
to
see
that
these
people
understood
the
message
that
was
behind
all
the
efforts
that
we
were
doing
here.
A
So
these
are
my
final
comments,
so
we're
now
slowly
reaching
the
top
of
the
hour.
We
have
still
quarter
of
an
hour
if
there
are
questions
comments
or
somebody
wants
to
comment
about
football
match.
No
I
don't
raise
that
subject
with
Alexander.
F
Go
ahead,
I
have
something
to
ask
how
much
help
we
can
expect
from
mentors
during
the
Json
period
during
the
contribution
period.
F
A
So
the
contributor
that
is
selected,
so
we
estimate
the
time
spent
by
mentor
to
eight
between
six
and
ten
hours
a
week,
work
together
or
reviewing
document
or
interaction.
So
it's
a
very
high
level
of
interaction.
So
it's
it's
really
Platinum
level
of
coaching
that
you
get
with
the
boy
yeah,
it's
it's,
but
you
get
a
very
high
support
for
that.
A
There
will
be
one-on-ones
I
will
I
will
insist
that
we
have
once
a
week
this
office
hour,
so
mentors
and
candidates
or
contributor
together
as
some
kind
of
a
stand-up
where
everybody's
is,
will
explain
what
is
this
progress?
What
are
his
concerns?
What
are
the
impediments
and
share
the
progress
so
that
we
do
we're
building
a
community
and
we
work
together?
So
it's
a
really
a
high
intensity
involvement
of
everybody,
and
not
only
per
project
I
want
to
have
it
globally.
A
All
the
four
projects
I
I
would
have
loved
to
have
more
projects.
Believe
me
believe
me:
I've
been
crying
to
have
help,
but
on
the
other
side,
I
don't
want
to
stretch
the
resources
we
have
because
I
want
to
be
sure
that
we
have
successful
projects,
and
you
see
you
hear
that
the
involvement
is
is
high.
A
G
G
I'm
working
on
the
Quick
Start
with
Anchorage
I
think
Bruno
is
the
lead
Mentor.
A
So
is
it
okay
now
generally
I
prefer
that
the
questions
are
raised
through
the
getter
Channel
or
publicly,
but
now
we're
slowly
running
out
of
time.
What
what
is
the
best
way
to
reach
Bruno
to
monitor
the
guitar
Channel
yeah.
C
A
C
A
C
A
Now
I
wish
you
success.
I
wish
the
mentors
so
to
us
a
little
courage,
because
this
will
be
the
last
preparation
office
hours.
So
remember:
I'll
open
the
channel
the
coming
weeks,
just
if
somebody
is
around
because
we'll
be
actively
be
working
on
the
grading
and
selection
process.