►
From YouTube: W2 Onboarding WG: ZenHub!
Description
This week, there is a great demo of ZenHub for project management! Also learn how to use GitHub to create and modify issues. Priorities include onboarding proposals and hatchers! Everyone should write a blog post about themselves and send it to Jess!
Question of the week
What are your intentions and distractions for the week?
00:00 - Griff is slowing down bit next week to rest for the hatch phase coming up towards the end of the year.
03:20 - Daiti got his powerful machine up and running! He's getting the gardens template installed. Daiti is learning golang. He is architecting the chat bot.
05:30 - Getting hatchers and projects as the main priority for onboarding
06:30 - Ideal scenario for a journey has been mapped out in Miro, the need to seek out projects rather than passively wait for them to come to us
07:20 - Github Epic is underway, proposal to review these issues during onboarding calls
12:40 - User's journey
17:56 - TEC Onboarding Roadmap
* Hatch requirements
* Database for potential hatchers
* 15 Proposals based on points
21:29 Issue 81 - requirements to being a cstokens holder - Issue 55 public list of hatchers
22:30 - Recruit and promote TE projects
24:00 - Process aggregation - Recruitment database table
* Feature comms blog
* Everybody write your own blog
26:54 - Github issues creation
27:30 - Zenbook overview
31:00 - Github Demo
34:00 - Engagement Process
41:20 - Trusted seed integration - access management
48:00 - Scheduling 5 minute comms presentations using google calendar
* who is responsible? (THE FINAL LINE OF DEFENSE)
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/DDr5kYU
or say hello on Telegram http://t.me/CommonsStack
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: http://twitter.com/CommonsStack
Learn more http://tecommons.org/
Solve issues! https://github.com/TECommons/coordination/issues
A
Ecuador-
and
so
I'm
pretty
excited
to
actually
take
next
week,
really
slow.
So
I
might
not
show
up
for
some
calls
and
stuff
like
that
and
take
a
little
break
before
the
the
craziness
really
starts
to
begin
so
yeah
and
as
far
as
distractions,
I'm
hoping
to
score
some
food.
But
that
might
have
to
wait
till
next
call
I'll
pass
it
to
edu.
B
C
D
E
Novelstore,
you
managed
to
say
my
last
name:
that's
amazing,
daniel
here
I
guess
dan
or
daniel.
Is
it's
more
human
and
humane
to
anybody
say
so
that
distracted
me
a
bit,
but
it's
okay.
My
main
distraction
this
week
has
been
connectivity
down
here.
I
need
characters,
but
I
think
I
found
a
a
solution.
So
I'm
happy
and
grief
it's
good
yeah.
It's
going
to
be
okay
but-
and
my
intention
is
just
to
listening
in
terms
of
onboarding.
F
It
only
took
a
week
and
a
half,
so
that's
a
I've
been
in
caveman
mode
for
the
past
while
and
I
now
have
a
really
powerful
machine.
I
am
so
with
this.
I
think
I'm
going
to
go
and
get
the
gardens
template
installed
and
I've
gotten
yeah.
I've
come
come
across
an
issue
so
I'll
post
that
and
then
I'm
gonna
put
a
proposal
up
on
the
what
you
call
it
to
the
zell,
but
I
never
I
never
clicked
that.
I
accepted
it
when
it
got
funded.
To
do
to
do
something.
F
I
bought
a
chatbot,
you
know,
so
I
might
work
with
that.
I
I
want
to
learn
goal
line,
so
I'm
going
to
be
like
most
programmers
and
the
dh
and
doing
the
goal
line,
even
though
the
industry
is
known.
So
stop
me
if
I
should
that's
what
I'm
going
to
do
I'll,
do
up
the
scaffold
and
then
put
a
document
up,
and
we
can
have
a
look
and
normally
with
something
like
this.
F
You
come
out
from
a
model,
building
an
api
and
get
your
dto
right,
so
we'll
try
and
get
that
in
the
document,
maybe
a
table
with
what
people
would
like
to
see
so
you're
in
a
chatbot
or
something
and
then
you
just
type
in
you
know
your
forward
slash
command.
You
know
how
much
funds
is
in
the
dial
proposal,
number
etcetera,
give
me
information
and
stuff
and
yeah.
That's
my
plans.
F
B
So
we
sort
of
put
in
common
our
common
goal
and
a
common
priority,
which
is
to
actually
get
proposals,
slash
projects
and
then
to
also
get
hatches
as
my
main
priority
for
this
for
this
group
and
also
to
create
a
process
to
get
these
people
on
board.
So
that's
our
priority
for
this
time
being
we,
it
took
us
an
hour
to
to
like
find
the
sense
and
the
common
goal
in
this
working
station
monday,
and
the
idea
would
be
that
the
next
session
we
actually
work
on
this.
B
We
also
have
a
mirror
in
the
middle
in
the
middle
board.
The
people
who
were
present
today
you're
welcome
to
add
any
any
of
you,
but
the
people
who
are
present
that
day
on
the
middle
board,
we
were
called
to
input
what
what
would
be
the
ideal
scenario
for
a
journey
like,
for
example,
once
you
arrive
or
you're
contacting
a
possible
project.
What
would
you
do
and
how
that
journey
will
be,
in
your
ideal,
mind
how
the
journey
will
be
executed,
so
we
did
that
in
the
mirror
up
so
different
outputs.
B
So
that's
something
to
take
consideration,
and
then
yesterday
we
had
a
call
with
tamara
regarding
the
process
and
the
priorities
of
this
group
and
also
to
create
the
github
issues
and
an
epics
to
be
assigned,
and
I
don't
know
if
anyone
has
read
the
issues
list
or
of
the
hit
on
the
github
epic
that
was
working
yesterday
regarding
assignments
and
the
things
to
do.
If
not,
I
invite
you
to
take
a
look
into
it.
B
I
think
that's
something
we
should
do
in
this
poll
in
order
for
and
if
anyone
wants
to
take
some
assignments
and
anyone
want
to
like
sort
of
redirect
the
work
and
understand
it.
So
let
me
know
if
you
have
this,
this
is
linked.
If
not,
if
can
you
pass
it
on
it?
The
link
to
this
issues
and
an
epic,
so
we
can
start
like
sort
of
redirecting
the
work.
I
don't
know
if
anyone
has
any
doubt
about
what
what
just
what
I
just
explained
regarding
this
week,
work.
A
B
B
B
B
B
B
A
B
B
B
B
B
B
So
so
originally
we
were
working
with
this,
which
was
this
is
where
the
the
trigger
was.
The
first
conflict
came
because
on
this
section
we
were
talking
more
of
a
general
onboarding
journey,
not
focused
on
a
hatchery
and
not
focused
necessarily
on
a
proposal,
so
we
started
working,
that's
where
we
found
the
first,
like
complication.
B
So
when
we
add
it
here,
we
can
actually
reach
some
conclusions
and
then
start
working
in
the
next
session,
creating
a
more
organized
process
to
reach
out
the
hatcheries
and
the
proposals.
This
is
in
order
to
achieve
as
a
kind
of
automatic,
automated
process
that
can
be
replicated
no
matter.
If
sandy,
do
it
or
not,
my
exception
must
have
said
it
doesn't
matter
who
does
it?
The
process
will
be
kind
of
standardized,
so
everyone
will
receive
the
same
information
and
we
will
say
more
or
less
the
same
information.
G
Yeah,
I'm
good
a
little
low
the
last
days
because
it's
been
raining
for
like
five
or
six
days,
so
that's
challenging
me
a
little
bit
but
yeah,
I'm
feeling
a
lot
better
today
than
yesterday.
I
just
took
some
time
for
also
thanks
for
asking
and
yeah
look
forward
to
working
on
some
of
these
things
in
eduardo.
I
wanted
to
ask
you
yeah
we
about
something
when
we
have
a
break
in
the
agenda.
B
Sure
no
problem-
I
was
just
explaining
jessica
about
the
the
things
that
were
we
were
worked
or
that
we
worked
on
this
past
week
regarding
the
mural
up
and
the
journey
and
the
results
of
that
meeting
and
also
the
conversation
we
had
yesterday
with
tamara
regarding
the
github
issues
and
epics,
I'm
not
following
necessarily
an
agenda
right
now,
because
craig
is
not
present.
So
I'm
just
like
summarizing
what
has
been
done.
So
if
there
is,
if
I'm
missing
out,
anyone
is
more
than
welcome
to
join
and
fill
the
gaps.
B
B
A
B
B
So
typical,
beginning
of
the
meeting
we
were,
we
went
through
the
instructions
intentions,
tamara's
objective
for
this
meeting
was
to
confirm
deliverables
and
search
and
executables
to
adapt
to
github
issues
and
epics.
Eventually,
so,
first,
we
went
through
the
first
part,
which
was
trying
to
understand
what
was
the
mission
of
the
group,
and
this
was
the
conclusion
to
target
and
bring
hatcheries
on
board
and
to
solid
and
to
solid,
solid,
fit
high
quality
proposals.
B
B
We
are
not
repeating
the
same
things
on
the
proposal.
We
are
just
putting
the
things
that
are
specific
to
the
hatcher's,
so,
for
example,
the
hatch
requirements
coming
from
the
legal
and
so
on
the
outreach-
and
here
this
is
something
that
craig
was
working
on,
which
is
the
database
for
potential
hunchers,
which
is
document
he
was.
We
call
it
the
database,
it's
not
necessarily
a
database,
but
that's
how
we
call
it
and
then
in
the
proposal
around
15
proposal.
B
Ideally,
we
had
this
points
that
were
needed
in
order
for
which
kind
of
success
on
that
point
of
the
proposals
and
then
the
other
deliverable
we
were
talking
it.
The
data
set
conclusions
of
the
jonas
research
so
moving
forward.
I
don't
know
if
anyone,
if
everyone
has
any
doubt
regarding
these
four
deliverables
for
this
group.
G
Now
this
is
exactly
what
I
feel
like
was
needed,
but
I
didn't
have
the
like
energy
to
make
chaos
into
order
again.
This
is
so
great.
This
is
exactly
what
we
need
that
I
like
was
struggling
to
do
the
last
days.
This
is
great
just
like
make
everything
super
simple
like,
and
then
you
made
some
githubs
for
these,
or
we
need
to
make
issues
for
these.
B
A
We
just
kind
of
threw
that
in
onboarding
catch-all,
but
but
so
we
just
made
three
epics
everything
for
proposals
and
everything
for
hatchers
and
and
organize
the
board
a
little
bit,
but
there's
probably
a
little
bit
more
granularity
that
could
be
used
for
sure.
But
I
think
for
now
we
have
we
I've
identified.
What
some
of
the
blockers
are.
I
think
dan
dan's
still
on
the
call
right
daniel.
A
That's
the
what
will
allow
us
to
kind
of
advertise.
The
the
c
stack
token
holder
like
and
make
sure
that
we
know
who
want
is
available
to
be
a
c
stack,
token
holder
and
all
those
things.
So
that's
a
big
one
and
just
in
general,
establishing
the
requirements
for
being
a
tec
token
holder.
This
is
issue
81
and
that's
kind
of
just
collecting
information
from
legal
and
making
sure
that
we
know
like
if
we
have
to
do
kyc
or
something
like
that
and
so
issue.
A
88
is
what
dan
is
working
on
and
that
will
lead
to
issue
55,
which
would
allow
us
to
kind
of
say
these
are
all
the
cool
people
that
are
c-stack
token
holders
that
are
available
to
be
hatchers
and
make
that
list
even
publicly
available.
That
might
also
help
recruit,
hatchers
and
then,
but
so
that's
kind
of
that
on
the
hatching
front
and
then
on
the
proposal
front.
So
in
general,
the
hatching
front
is
a
little
bit
more
blocked
by
that
work.
A
So
the
but
the
project
front
is
totally
open,
so
we
have
recruit
and
promote
te
projects,
which
is
just
general
onboarding,
finding
te
public
good
projects
that
we
want
and
we
can
start.
You
know
this
could
be
broken
up
into.
Maybe
a
few
smaller
issues
like
making
a
list
just
doing
research.
Who
are
the
t?
You
know
public,
good
projects
that
we
have.
I
don't
think
we
even
have
a
list
yeah.
I
do
so.
B
A
G
G
We
we
have
like
steps
like
invited
them
to
the
group,
sent
them
onboard
information,
followed
up,
that
they
understand
and
like
a
little
note
about
how
they
want
to
engage
with
us
and
then
maybe
you
could
suggest
like
feature
comms
blog
and
maybe
even
like
what
we
used
to
do.
When
I
worked
at
a
software
company,
we
would
have
people
write
their
own
blog
like
a
guest
blog
about
themselves.
G
G
And
it's
just
like
a
really
tight
blog,
like
a
guest
feature
that
we
could
put
in
our
medium,
so
yeah
just
developing
a
little
bit
of
the
process
and
then
the
github
issues,
and
then,
when
it'll
be
easier
to
like
delegate
and
hand
things
off,
because
it'll
be
really
clear.
I
think
that's
been
this
like
sentence
making
process
in
the
last
week
is
just
like:
okay,
what.
G
B
Right
now
we
were,
I
think,
the
next
30
minutes
of
the
call
we
should
go
to
the
game
through
the
github
and
sort
of
I'm
new
to
github.
I
have
no.
I
have.
This
is
not
a
tool
that
I
control
completely.
So
if
you
can
lead
the
process
or
directly
the
process
through
the
work
that
we
did
just
today,
it
will
be
amazing.
A
G
A
And
we
can
also,
we
can
also
assign
people
in
github
and
then
they
get
an
email
anytime,
there's
action
on
that
issue,
but
that
involves
also
making
sure.
I
think
everyone
in
here
is
actually
on
the
github,
we're
pretty
liberal
with
giving
people
power
over
the
gap.
So,
okay,
so
here's
the
zenhub
board.
I
gave
it
a
link
in
the
onboarding
working
group
channel.
If
you
haven't
seen
it
so
anytime,
you
make
a
new
issue.
It
will
just
pop
up
here
right
now,
it's
filtered
by
onboarding
working
group.
A
A
The
first
column
here
is
new
issues.
Anytime,
you
make
a
new
issue.
It'll
show
up
here.
Second,
column
is
epics.
Epics
are
kind
of
large
grouping
of
issues
based
on
a
topic
right,
so
we
need
onboard
proposals,
we
need
onboard
hatchers
and
then
they
will
have,
and
then
we
have
onboard
and
catch
all.
Ideally,
every
issue
for
the
onboarding
working
group
ends
up
in
an
epic
that
there
aren't
any
like
orphan
issues.
A
A
A
A
It
can
just
hang
out
there
oh
come
on
and
then,
if
you
are
tackling
an
issue
at
that
moment,
it's
kind
of
like
like
dan,
is
working
on
this
right
now
we
can
move
that
one
to
in
progress,
and
then
everyone
can
see
that
oh,
this
issue
is
being
worked
on
by
someone
and
things
in
the
sprint
backlog.
Maybe
someone
has
it
claimed,
but
they're
not
actively
working
on
it.
So
it's
a
an
opportunity
for
you
know
this
is
a
high
priority
task
that
needs
to
be
that
can
be
taken
on.
B
A
A
B
G
G
A
G
I
will
be
happy
to
like
set
up
the
pro.
I
think
also
this
is
this
is
kind
of
more
than
one
task
I'll
set
up
the
process
and
then
I'll
just
need
help
with
people,
volunteering
to
kind
of
relationship
manage
the
different
people,
and
then
we
just
need.
I
think
the
process
is
what's
missing
like
are
we
gonna?
G
C
G
A
google
form,
and
then
we
have
a
we
make
sure
that
we
calendar
when
we
invite
somebody
to
do
the
elevator
pitch
in
the
thursday
meetings
that
we
put,
that
on
the
calendar
or
at
least
on
the
agenda
and
tell
the
students
and
then
we
need
to
have
like.
I,
I
I'll
just
I'll,
set
up
the
process
and
start
and
if
I
need
help
I'll
ask
for
help,
I
guess
maybe,
if
eduardo
you're.
A
A
H
B
Can
we
not
lose
track
and
go
back
to
the
things
that
were
open,
the
epics
and
stuff,
so
we
can
like
actually
recognize
what's
priority
to
target
and
then
to
what
is
needed.
If
someone
here
wants
to
do
or
and
then
we
focus-
and
we
can,
we
can
team
up
jessica
to
this.
Stop
this
issue.
But
I
don't
want
to
stay
too
long
in
a
single
issue.
G
A
Yeah,
I
would
say
that
we
don't
have
like,
for
instance,
this
is
the
epic
for
onboarding
proposals
and
there's
only
two
issues.
There's
this
make
a
list
issue
and
then
there
sounds
like
jess
just
listed
out
like
four
other
issues
that
we
could
add
right
now,
and
so
let's,
let's
do
it,
you
know,
let's
add
those
issues.
Yes,.
B
E
B
I
want
to
make
sure
that
the
rest
of
the
rest
of
everyone
in
the
call
it's
like
completely
on
board
what
we're
doing
like,
because
I
haven't
heard
anyone
else
in
the
past.
15
minutes
it's
anyone
else
has
any
doubt.
Everyone
has
to
understand
what
we
are
doing
or
is
there
anything
that
you
need
help.
D
G
If
you
want
to
get
more
involved
and
start
taking
these
github
issues
with
me-
and
I
can
just
say
like
hey,
if
you
have
time
do
this,
this
like
point
you
in
the
direction
and
if
you
have
time
to
do
it,
if
you
wanted
one
or
two
issues,
I
support
you
and
like
on
boarding
you
into
like
how
to
do
that.
So
you
can
come
a
little
deeper
to
take
on,
because
I
hear
you
wanting
to
take
on.
G
A
B
B
Yeah
for
me,
it's
the
we
started
talking
here
about
the
onboarding,
like
assigning
onboarding
assignments
assignments
on
board.
I
don't
know
how
you
call
that
phrase,
but
it's
basically
we
start.
We
we
pick
one,
we
target
that
person
and
we
go
for
it
like
or
that
project
and
we
go
for
it.
So
for
me,
it's
more
of
a
yeah.
It's
yeah!
It's
reaching
out.
A
A
G
F
I
was
just
going
to
show
something
there.
I
put
a
can't
find
the
issue
and
it
was
on
like
getting
the
project.
If
it
was
me,
I
kind
of
go
with
it
to
have
it
have
an
end
goal
of,
and
usually
these
things
like
amaze
would
would
be
would
be
good.
So
you
would
take
your
media
and
everything
you're
doing
on
me
on
medium
and
all
the
articles
and
stuff
and
then
do
whatever
we
decide
to
do
for
them
to
get
the
projects
in
without
the
suggestion.
F
F
G
Thank
you
for
that
yeah.
That's
a
really
cool
idea
to
do
the
ama,
like
with
the
different
groups
and
such
so
that's
a
good
thought
as
well,
because
I
think
it's
easier
than
reading
vlogs.
Sometimes
if
it's
in
a
super
tight
like
two
to
five
minute
format
or
something
but
yeah,
we'll
definitely
pull
you
in
here,
for
it.
B
G
G
If
you
want
to
put
like
dates
on
this
kind
of
strategy
document
or
something
I
like,
the
roadmap
idea,
that's
probably
really
helpful
but
yeah.
First,
we
can
clean
it
up
and
everything
and
yeah
griff-
I
don't
know
where
it
would
go.
Did
you
already
create
an
issue
for
summarizing
the
stakeholder
research
from
jonas.
A
Yeah
yeah,
that's
that's
that's
already
there.
It's
not
part
of,
I
wouldn't
say
it's
directly
like
as
cleanly
related
to
onboarding
projects,
but
it's
like
a
catch-all.
It's
in
the
catch-all
just
keep
on
boarding
and
it
might
be
in
and
we
could
even
say
hey.
It's
blocking.
You
know
a
certain
thing.
Oh.
G
A
B
A
A
A
A
G
Oh
and
also
eduardo,
I
need
to
pull
out
of
that
document.
What
kind
of
people
said
they
would
fund
and
what
they
wouldn't
fund
or
a
content
piece
that
I'm
working
on?
For
that?
I
think
for
me
right
now
too
having
the
github
issues
is
so
helpful,
because
so
many
links
flying
and
I'm
like
having
to
go
through
my
telegram
chat
from
like
a
week
ago
and
be
like.
Where
was
that
thing
again.
A
Cool
well,
another
issue,
that's
kind
of
related
to
that
is
organizing
our
slots
for
thursday
calls
right
now,
it's
kind
of
scary,
because
I
I
don't
feel
like
anyone
feels
comfortable
like
I'm
like
talking
to
jonathan
I'm
like
yeah,
you
should
talk
on
thursday
man.
I
have
no
idea
if
there's
like
someone
already
scheduled
for
this
thursday
or
not
or
or
what,
but
now
we
know,
chevnam
is
talking
to
tomorrow,
right.
G
G
It's
kind
of
part
of
for
me.
It's
part
of
that
process,
of
engaging
with
the
project.
What
my
imagination
is
like,
we
make
a
checklist.
I
said
like
invite
them
to
present
in
meeting
put
the
date,
send
them
onboarding
materials,
follow
up
and
answer
questions
like
a
little
checklist
that
anybody
could
come
in
and
jump
in
and
like
follow
this
little.
A
Small,
I
guess
I
I
really
don't.
I
I
have
a
strong.
I
have
a
strong
desire
to
make
sure
there
is
one
person
managing
it,
because
when
somebody
cancels
you
know,
if
that's,
if
that
there's
not
like
who
do
they
cancel
with
you
know
and
then,
like
oh
wait
but
isn't
jonathan
supposed
to
show
up.
Oh
he's
not
coming
and
we
find
out
during
the
meeting.
You
know
it's
like
there's
gotta
be
someone
who's
like.
Oh,
I
know
when
everyone
is
talking.
A
A
Every
thursday
there's
a
there's
a
five
minute
slot,
where
in
in
the
thursday
sinkhole,
where
we
have
some
token
engineering
public
good
project
present,
and
we
need
to
coordinate
that
because,
right
now,
the
community
stewards
are
all
kind
of
reaching
out
to
people
and
then
like
we're,
not
really
sure
who's
speaking
and
on
which
dates,
and
we
don't
have
it's
scheduled
or
anything
and
it'd
be
really
nice
just
to
have
like
oh
yeah.
This
person
is
talking
on
this
day
and
this
person
is
talking
on
this
thursday
and
this
person's
time.
This
thursday
yeah.
B
For
me,
this
is
a
matter
of
a
simple
calendar.
Google
calendar
notes
where
other
stewards
by
wednesday
should
add
the
link,
the
information
to
whoever
is
going
to
talk
and
present
the
day.
So
we
are,
we
all
come
at
least
with
an
idea
who
we
are
going
to
see
or
what
it's
going
about.
So
for
me,
it's
just
a
simple
action
to
just
have
it
on
the
google
calendar.
Probably
we
need
a
next
step
to
have
that
centralized
in
a
document
where
we
keep
track
of
these
people.
A
This
is
my
suggestion
to
that
money.
I
think
that's
a
great
way
to
go.
The
main
thing
I'm
having
trouble
with
is
the
fact
that
I
don't
feel
comfortable
inviting
jonathan
to
speak,
because
I
don't
know
if
someone's
already
got
the
slot
like,
I
can't
coordinate
with
him
to
find
the
time,
so
I
need
to
find
so.
Yes,
that's.
B
Right,
that's
why
if
we
put
it
and
if
we
put
it
on
the
google
calendar-
and
we
just
ask
the
swords
or
whoever
does
this
to
put
in
the
calendar
we
realize
if
jonas,
if
there's
someone
else,
if
there's
a
space,
it's
not
your
space,
we
have
to
say
how
many,
how
many
people
presenting
that
day
and
so
on.
So
it's
just
a
matter
of
having
the
information
accessible
in
a
scene.
B
This
way,
what
happens
to
me
is
that
usually,
when
I
look
for
something
there
are
so
many
documents,
documentaries
that
it's
quite
chaotic,
but
we
all
know
where
to
look
when
we
want
to
know
the
link
for
the
stuff.
So
for
me
they
will
calendar
appointment,
it's
easier
not
only
for
us
but
for
the
people
who
is
coming
to
the
meeting
too
to
to
see
how
much
time
there's
other
people
or
you
know.
I
think
it's
a
helpful
way.
G
Okay,
maybe
this
I
don't
think
we
need
like
a
whole
thing
like
you're,
saying
grip,
just
bring
it
up
in
the
stewards
agenda
like
we
don't
need
a
person
to
manage
it.
I
don't
think
I
think
we
just
need
to
put
it
on
the
calendar
like
edusing.
Are
you
cool
with
that,
like
we'll
just
put
on
the
stewards
agenda,
or
you
want
somebody
besides
a
steward
to
handle
it.
A
B
It
I
mean
for
me
it's
just
it's
just
to
be,
for
everyone
to
just
add
a
little
action
to
their
brains
in
sense
of
okay.
You
you,
you
book
someone
for
that
day,
just
remember
to
add
it
to
the
google
calendar,
because
otherwise
we
will
create
three
or
more
steps
for
another
person
who
is
not
a
steward
to
keep
tracking
behind
people,
and
that
would
be
a
little
bit
messy
because
of
people's
times.
B
B
B
C
Do
that
just
one
one
comment
here,
which
I
completely
agree
with
eduardo:
the
problem
arises
when
someone
who
committed
to
come
for
whatever
reason
is
falling
from
from
coming,
because
you
know
things
happen,
it
happens
and
at
the
very
last
minute
they
say
they
can't.
Then
we
have
to
real
quick,
try
to
reschedule
someone
who's
scheduled
for
another
day
or
try
to
find
someone
who's
gonna
take
his
place.
B
We
may
have
an
issue
what
about
we
do
up
on
always
plus
one
like
we
always
invite
someone,
plus
just
I'm
just
trying
to
understand
how
this
works
but
like
to
invite
someone
else.
Always
I
go,
I
get
what
I'll
get
what
you
mean?
It
makes
completely
sense.
I
think
what
could
be
interesting
is
that,
for
example,
it
will
be
easier
if,
if
by
wednesday
jessica
me,
whoever
it
is
just
see
the
list
on
google
calendar
and
and
and
check
that
check
that
everyone
can
come.
B
A
Just
have
a
voice,
probably
someone
someone
will
improv
I'll.
You
know
and
just
jump
it
there
and
be
like
oh
yeah,
here's
the
spotlight
yeah.
I
have
a
proposal.
I
want
to
make
sure
that
you
know
closed-source
cad-cad
models
get
open
sourced
and
then
you
know,
then
they
just
make
something
up
on
the
spot,
but
I
mean
it's
not
the
worst
case.
B
It's
not
a
horrible
thing,
I
don't
I
I
don't
really
like
I'm
just
trying
to
be
clear
in
this
process.
Are
we
just
kind
of
thinking
and
overcompensating
about
something
that
prob
that
probably
won't
be
harmful
in
the
sense
of
we
don't
need
to
fill
the
gap?
If
if
there
is
no
one,
we
just
don't
fill
that
gap,
and
it's
fine
like
I
don't
know
why
we
need
to
cover
overcompensate
this
just
trying
to
understand.
A
Okay,
for
me,
I
have
a
guideline
of
like
if
everyone's
responsibility,
it's
not
ability
and
fail.
So
like
I,
I
have
zero
faith
in
issues
that
have
not
a
single
person
who
feels
responsible
for
them
being
completed.
That's
just
like
a
value
I
uphold
or
a
foundational
belief
in
my
project
management
like
world.
So
like
you
know
it,
it's
something.
It's
a
it's
an
I
project
that
we
want
to
run
on
a
repetitive
scale,
every
thursday.
It's
a
small
thing.
A
G
Just
that
it's
top
of
the
hour
and
yeah,
if
we
had
any
more
like
high
level
stuff,
was
really
important.
Otherwise
we
can
circle
for
a
work
session
at
some
point
and
clean
up
these
issues
and
then
like
when
we're
ready,
then
we
can
do
the
handoff
to
daity
and
zeptimus
for
a
few
and
since
they're
willing
to
take
them
on,
but
I'm
sure,
there's
stuff,
I'm
forgetting
I
kind
of
to
like
organize
myself.
G
But
this
is
a
good
start
and
I
think
yeah
summarizing
the
research
is
talks
and
getting
some
of
this
onboarding
project
stuff
rolling.
And
then
I
have
a
few
communications
elements
I
need
to
throw
in
like
number
one
for
me.
Is
this
content
piece
on
what
what
kind
of
projects
will
fund
and
what
not
so,
that's
kind
of
my
priority
list?
I
guess.
B
D
G
B
H
D
G
A
A
B
B
So
we
can
keep
working
on
this
and
the
ones
who
have
missed
what
they.
What
the
github
part
you
can
enter
to
github
and
see
some
of
the
issues
and
and
a
pixel
has
been
created,
and
if
anyone
has
any
doubts
or
wants
any
issues
for
themselves
or
want
to
create
another
one
just
think
some
machines.
Just
please
note
it
on
the
discord
channel
and
that's
it.