►
Description
A
The
idea
that
we
have
project
boards
for
taking
you
know
a
particular
feature
or
something
you
know
that
we
plan
and
we're
executing,
and
we
want
to
follow
the
cards.
I
guess
like
homepage,
so
so
you
could
kind
of
see,
as
you
know,
you're,
not
cluttering
yourself,
you're,
looking
at
homepage
as
a
particular
feature,
and
that
worked
well
for
for
features.
But
when
I
tried
to
reason
about
what
an
okay
our
board
would
look
like
it
wasn't
it
wasn't
really
fun.
You
know,
like
I,
didn't
know
what
kind
of
columns
or
you
know.
A
A
The
difference
between
project
and
the
labels
versus
milestones
is
that
you
can
only
have
one
milestone
for
an
issue
or
a
PR.
You
can't
have
it
under
more
than
one
label
or
under
more
than
one
project.
The
milestone
is
just
the
one
and
and
basically
I.
Think
the
trickle
down
here
is
is
how
I
would
like
to
take
our
okay,
our
so
okay,
ours
lead
to
some
milestones
which
which
then
allow
everyone
to
say
well.
A
This
issue
drives
toward
this
objective
and
those
milestones
would
then
be
potentially
key
results
that
we're
driving
at
and
all
the
issues
related
to
them
would
be
underneath
them,
and
so
that
would
be.
You
know
just
one
example
and
then
I
guess
T
one
features
so
yeah,
so
the
net
Liffe
I
thing
I
did
I,
didn't
fully
think
this
through
right,
I,
just
I'm,
proposing
it
as
a
workflow
that
that
is
parallel
to
projects,
so
people
use
projects
in
the
way
that
is
functional
right
now
and
that's
good,
and
this
is
not
contending
with
it.
A
But
just
a
parallel
system
to
say
you
know,
I'm
sure
nullify
is
a
key
result
of
some
of
our
one
of
our
objectives,
and
so
you
know
by
doing
a
better
management
effort
than
I
can
I
guess.
We
would
have
milestones
that
you
know
trace
back
to
the
king,
okay,
our
dog,
and
you
said
the
dock
itself
landed
on
master.
A
B
Thanks
for
explaining
that
my
initial
impression
of
this
is
that,
if
that
helps
people
visualize
what
they're
working
on
and
how
it
relates
to
okay,
our
is
like
that
define
our
scope,
I'm
plus
one,
for
it
is
this
something
that,
like
you
mentioned,
that
people
are
already
using
projects,
and
that
seems
to
be
working
quite
well.
Is
this
something
that
has
been
tried
like
people
already
sort
of
using
it?
Or
is
this
something
that
we'd
need
to
implement?
It
spend
a
little
bit
of
time
just
building
up.
A
A
How
would
you
add,
linkable
things
here
that
point
people
to
a
dashboard
of
some
sort
or
a
you
know
a
syndicated
thing
like
issue
or
project
or
something
so
that
they
would
know
how
what
progress
is
happening
here
for
us,
so
I
would
say
a
and
like
a
level
three,
you
know,
sub
list
like
us,
nested
list
under
this
key
result
would
say
milestones
this
milestone
in
that
milestone.
You
know,
you
would
add,
add
links
literally
to
the
milestones
that
contribute
to
this
key
result
of
this
objective.
A
So
it's
mainly
just
a
framework
that
I
personally
played
around
with
to
make
sure
it
would
work,
but
I
think
I'm,
just
proposing
it
as
here
this
could
work.
Do
we
want
to
do
this,
and
if
we
want
to
do
this,
it
might
be
actually
something
that
you
know.
Kham
Kham
and
other
places
may
want
to
borrow
as
well.
So
you
know
we're
inventing
it
together.
I
guess
sounds
fair.
B
A
So
not
Elif
I
would
be
one
of
the
bullet
points
under
this
one,
if
I'm
not
mistaken,
maybe
I
don't
know
and
then,
when
they
click
on
Natalja
phi.
As
a
bullet
point
under
this
key
result,
they
would
come
to
this
view
and
then
they
can
tell
from
this
view,
how
far
along
right.
So
it's
like
zero
percent,
complete
I'm
sure
when
we're
using
it.
It
would
actually
not
just
reflect
the
example,
but
rather
have
have
more
accurate
representation.
Some
closed
issues,
better
descriptions,
yeah
I,
guess
that's
it.
C
I
think
I
think
so
far.
This
is
a
good
good
progress
and
good
start,
but
I.
You
know
I
feel
that
you
know.
I
would
like
to
see
that
us,
you
know,
have
a
more
collaborative
effort
in
terms
of
getting
to
those
milestones.
You
know
like
cuz,
cuz
I'm,
not
I'm,
not
familiar.
My
I've
been
trying
to
figure
out
like
the
schedule
for
for
like
getting
all
this
bug,
fixes
and
stuff
like
that
like,
but
there's
a
lot
been
a
lot
of
back
and
forth.
C
So
I'm
not
like
I'm,
not
not
sure
as
to
how
we're
going
to
be
solving.
You
know
the
issues
as
well
as
doing
development
going
further
there,
just
because
if
there's
been
so
much
back
and
forth,
you
know
we
had
to
hackathon,
but
then
we
got
a
cancelled,
I'm,
not
sure
like
what's
happening.
So
I
would
like
to
see
that
part,
but
I
think
this
is
a
good
start
in
terms
of
getting
started.
Yeah.
A
So
the
the
concern
that
you
raised
right
there
I
think
that
is
why
I
was
driven
to
look
into
this.
It's
a
shirt
personally,
you
know
so
so
we
can
have
a
lot
of
side
channel
back
and
forth,
and
then
we
find
like
three
people
are
converging
in
one
way
and
you
know
others
are
in
a
different
way
and
then
everyone
will
say,
but
I
followed.
The
okay
are
right.
So
so
the
idea
that
is
chainable
means
that
there's
always
context
and
clarity
as
you
click
through
things
before
you
add
more
things.
A
Okay
and
I
thought.
That's
really.
The
intent
here
is
that
if
you're
going
to
dig
and
say
I'm
gonna
put
something
here,
then
you
will
know
that
there
is
already
something
else
or
you
know
if
you're
the
first
one
that
deep
into
the
okay
are
itself
and
then,
if
that's
the
case,
then
we
also
have
to
add
to
the
contributor
doc
that
this
is
the
process
that
we
want
to
follow
until
it
doesn't
work
for
something
and
then
we
can
improve
it.
B
A
Yeah,
so
could
I
suggest
that
we
just
indicate
what
we
decided
in
the
meeting
here
as
well,
because
I
think
some
of
like
we
want
to
have
a
label
to
say,
approve
the
meeting
or
you
know
some.
Some
of
the
issues
have
have
like
mysterious
context
missing
in
the
end,
and
then
we
have
too
many
of
those
that
we
don't
really
know
what
we
decide
in
the
meeting.
So
how
would
we
summarize
this
outcome?
I.
B
I
just
put
in
some
notes
into
the
minutes,
I
will
copy
that
over
it's
very
short.
Ideally,
these
these
minutes
are
more
complete
and
we're
actually
able
to
pair
them
into
users
reference,
but
we
haven't
been
doing
that
for
a
bit,
but
for
now
I'll
copying
the
notes
for
this
particular
section
into
a
comment
label
at
consensus,
and
if
anyone
wants
to
disagree
that
again
feel
free
to
comment
async
all.
B
D
B
Personally,
plus
one
on
this
I'm
sorry,
we've
been
a
blocker
on
this
one.
It
it
seems,
like
y'all,
have
been
ready
to
move
forward
on
this
and
we
might
have
been
the
ones
we've
been
dragging
our
feet,
but
I
have
no
personal
objections.
I'm
really
excited
the
the
work
in
ITN
has
been
progressing
and
yeah
very
exciting.
To
incorporate
some
of
this
into
our
work,
no
objections,
any
comments
from
the
team.
D
C
D
D
D
B
B
B
A
Can
I
just
raise
just
one
one?
One
related
point
here
we
were
talking
about
net
la
vie,
and
this
issue
is
one
of
those
issues
that
relates
to
that
topic.
So
I'm
not
sure
for
picking
up
this
topic
in
this
meeting.
I
don't
know
if
there's
any
input,
maybe
from
folks
on
whether
or
not
we
want
to
push
this.
You
want
to
yeah,
so
so
I
think
it's
a
topic
that
keeps
coming
up
every
time
we
try
to
you
know,
write
code
and
we're
reminded
that
the
Google
JCB
run
can
sometimes
be
a
funny
experience.
C
E
It
doesn't
reliably
the
the
post
t,
the
the
post,
a
comment
hook
doesn't
seem
to
be
working.
It
either
doesn't
work
reliably
or
else
there's
there's
something
going
on.
I,
don't
know
what
it
is,
but
there's
a
bunch
of
PRS
that
that
that
I've
been
reluctant
to
land,
because
because
I
think
one
of
them
might
be
breaking
that
that
functionality
and
I
don't
know.
If
that
is
really
anything.
We
can
talk
much
about
here
right
now,
but
there's
that.
F
A
So
so
I
think
I
think
we
tried
to
solve
the
GCD
run
problem
by
saying,
let's
document
the
you
know
funny
results
that
can
come
out
that
we
basically
have
no
logs
and
we're
trying
to
you
know,
use
our
mental
ability
to
try
to
infer
from
the
unknown
and
that
wouldn't
work.
Obviously,
so
so
definitely
this
idea
that
if
you
know
the
worst,
you
should
get
a
log
that
tells
you
don't
go
crazy.
A
Trying
all
these
all
you
know
permutations
and-
and
so
the
log
is
a
good
thing,
but
also
the
second
thing
that
I
keep
also
feeling
inclined
to
want
to
bring
up
is
if
I
fork,
and
somebody
is
convinced
pyaari
me
against
my
branch
on
my
user,
not
on
notice
that
you
know
that
they
should
also
be
able
to
use
the
free
open
source
for
it
forever
kind
of
CI
infrastructure.
So
they
are
able
to
not
wait
until
they
are
merging
the
big
collaborative
effort
against
nodejs
dev
to
be
allowed
to
run
it
through
CI.
A
A
B
While
we
don't
seem
to
have
a
clear
how
he
said
alternative
that
we
all
agree
on
words
like
we
definitely
want
to
use
this
as
an
alternative.
There
seems
to
be
consensus
that
GCB
run
is
not
ideal,
and
it's
a
consistent
feeling
over
the
past
couple
of
weeks,
two
months
at
the
very
least,
would
it
be
fair
to
say
that
our
next
step
here
would
be
to
seriously
explore
alternatives
and
swap
it
out
for
something
else,
I
think.
A
Natalja
Foy
the
experiment
that
depended
of
wasn't
wasn't
the
only
nullify
issue
related
to
this.
There
were
issues
open
about
net
lephant,
nesaf
I,
already
a
while
back,
but
basically
when,
when
I
saw
then
doing
notify
on
his
end
when
he
was
screen
sharing
once
I
basically
feel
that
this
is
a
solution.
I
don't
do
a
lot
of
CI
stuff,
so
so
I
personally
feel
inclined
that
net
liffe
I
potentially
could
be
a
solution.
A
As
long
as
we
keep
in
mind
that
we
don't
want
to
complicate
the
config
that
you
would
still
need
to
be
on
the
nodejs
repo
that
that's
my
my
only
you
know
so
so
if
we
have
like
the
yeah
mo
configs
and
in
the
staging
branch-
and
you
fork
that
branch
and
then
you
have
your
own
net
supply
account-
and
you
know
this
repo
is
obviously
free.
It's
open
source,
I'm,
hoping
we
can
make
sure
that
this
would
still
allow
you
to
to
do
it
free
of
charge
as
any
user
on
get
out.
C
A
B
A
A
I'm
sure
other
people
on
the
team
are
interested
in
many
would
know,
but
I
I
just
don't
want
us
to
model
this
out
of
the
out
of
the
repo
itself,
and
then
you
know
start
hitting
all
those
repo
related
challenges
so
can
can
we
allow
people
to
model
this
on
a
branch,
a
separate
branch
and
give
them
authority
to
do
that?
I
think
this
is
really
what
what's
been
getting
in
that
way
other
than
if
people
have
time.
Obviously,.
F
Yeah
I
think
we
probably
want
to
do
something
similar
to
the
way
the
translation
team
is
doing.
They
have
a
like
a
separate
blog
account
and
in
that
account
is
what
connects
to
the
network,
I
and
then
I
think
that
might
be
a
way
to
do
it,
but
I
think
to
answer
the
question
you
yeah.
There
is
probably
maintainer
access
permissions,
I'm
I'm,
not
really
sure.
B
A
Can
I
can
I
suggest
we
will
kind
of
want
one
person
to
have
a
little
bit
more
permission
than
the
rest
of
the
team
doing
it.
That
way
is
basically
because
you
don't
want
not
to
know
who
used
that
permission.
So
so
you
know
I'm
just
adjusting
having
a
go-to
person
at
this
point
to
have
a
little
bit
more
permission
to
see
us
through
this,
and
then
we
can
agree
on
what
what
governance
or
you
know,
what
what
what?
A
A
B
Well,
we
have
Alex
on
the
call,
and
since
we
are
thinking
about
using
the
ISU
MN
model
Alex,
if
you're,
if
you're
still
with
us,
we're
wondering
if
this
model
that
you
use
for
having
a
bot
to
connect
and
that
look
like
the.
What
was
the
rationale
behind
this?
Was
it
about
more
about
maintainability
or
like
where
open
source
contributors?
D
Okay,
so
I
think
I
understand
so
from
from
my
experience,
using
this
kind
of
model
like
ever,
both
in
open
source,
it's
not
very
comfortable
but
I'm,
not
sure
they're.
Another,
like
another
approach
that
we
can
use
in
open
source,
because
if
we
ask
some
specific
user
to
connect
their
personal
account
and
if
this
user
stopped
responding
in
some
way
it
will
hurt.
D
It
will
be
hard
to
like
give
an
access
to
your
net
if
I
can't
the
same
thing
with
no
G
as
both
but
I
I
spent,
maybe
a
few
months
to
figure
it
out.
Who
is
the
owner
of
this
boat,
how
to
connect?
How
to
integrate
and
now
I
figured
out
that
Zeke
is
owner
and
they
are
store
somewhere
in
no
GS
admin
storage.
D
They
are
password
in
encrypted
style,
so
I'm
not
sure
how
it
how
it's
working
and
I'm
still
have
like
some
blockers
with
that.
But
I
ice
I
tried
to
find
another
way,
but
I
I
didn't
find
anything
better
than
that.
We
have
so
I.
I
can't
actually
give
you
any
advice
about
that.
So
I
just
have
some
dots
and
that's
it
so
I.
Don't
know
the
best
way,
oh
and
yeah.
B
D
Password
login
password
system
for
open
source
because
I
don't
know
how
to
how
it's
possible
so
like
share
login
password
with
everyone,
but
with
some
limited
scope
of
team,
so
I
don't
know
how
how
it
work,
how
it
works.
I've
never
had
a
chance
to
find
something
like
this.
So
I
don't
know,
but
yeah
Crowden
bought
its
and
this
model
is,
is
also
contained.
Some
problems
with
access
with
time,
lockers
time,
wasters.
A
A
Think
what
we're
trying
to
say
now,
because,
like
20
minutes
to
the
end
of
the
meeting,
is
that
we
kind
of
want
to
look
what
net
LeFay
issues
related
to
this
kind
of
workflow
look
like,
because
obviously
some
other
people
had
had
a
similar
desire
and
I
think
they
say
that
when
someone
who
has
write
access
Forks
a
repo,
they
kind
of
want
to
take
that
work.
You
know
not
enough.
A
I
build
configuration
with
them,
so
it
becomes
like,
like
a
way
for
people
to
contribute
and
and
get
their
you
know
deployments
or
whatever
in
place.
So
we
want
to
maybe
create
a
an
offline
discussion,
not
offline
necessarily
but
I
mean
out
of
the
racing
hours
of
the
meeting.
Because
someone
would
champion
this
and
then
you
know
we
would
come
come
back
with
bullet
points.
A
B
A
F
B
C
B
A
Yeah
I
think
yeah,
so
I
think
then,
and
I
hacked
on
this
Randy
time's
right,
I'm,
not
sure,
maybe
I'm
mistaking
this,
but
basically
we
had
a
Gatsby
flow
that
was
created
before
the
structure
at
the
website
and
the
idea
was
they
would
build
a
website
as
contributors
added
parts
of
the
markdown
files
that
we'll
build
to
it.
But
then
we
had
areas
in
the
site
that
was
basically
the
demo
pages,
as
shown
in
the
figure
ended
India
and
the
contents
there
should
be
coming
from
markdown
files,
but
it
wasn't.
A
So
the
context
here
is
this
is
stale.
There
was
probably
a
PR
at
some
point
and
I'm
not
comfortable
with
landing.
My
own
PR
and
I
should
probably
say
that
in
the
PR
itself.
So
do
we
want
to
I,
don't
know
like
maybe
Ben.
Do
you
have
some
input
on
next
steps
on
this,
or
do
we
want
to
put
on
the
back
burner.
F
F
F
A
Yeah,
so
so
I
guess
an
issue
we
would
open
at
this
point.
How
do
we
want
to
create
the
second
content
pipeline?
Because
the
way
the
content
is
generated
right
now,
it
seems
to
be
learned
content,
and
this
is
not
learn.
Content
like
whatever
I
was
like
hacking
at
with
with
zero
knowledge
of
Gatsby,
like
I,
didn't
even
know
it
existed,
maybe
a
week
before
that
that
was
my
best
approximation
with
limited
know-how
in
documentation
right.
F
A
F
With
Gatsby
we
have
a
plug-in
for
markdown,
that's
what
the
word
country
is
using,
so
we
should
do
the
same.
Maybe
we
can
make
a
home
page
since
this
is
part
of
the
home
page
and
putting
on
I
think
for
each
maybe
for
each
tab.
This
each
tab
is
a
how
to
install
for
the
specific
OS
text
for
one
went
file
for
each
tab
and
yeah.
C
A
Html,
so
can
I
clarify
what
I
was
hitting?
Is
that
we're
doing
like
us?
You
know
wild
card
pipeline,
so
I
was
running
into
this
problem
where
it's
starting
lecture
on
got
to
learn.
Things
are
like
getting
and
learned
and
things
are
showing
up
where
I
completely.
You
know
like
understood
now
how
Gatsby
worked.
That's,
how
I
learn
you
know,
but
but
then
I
didn't
know
whether
there
is
a
convention.
If
that,
because
the
file
naming
convention,
you
know
everything
being
numbered,
the
means
in
a
one.
Oh
yeah,
you
know
kind
of
high-level.
A
F
A
I
think
the
context
was
collecting
from
many
people
who
were
at
Vancouver
and
on
the
tail
end
on
that.
So,
like
I
said,
the
structure
of
the
website
itself
did
not
exist
when
they
created
all
these
things,
and
then
they
designed
a
workflow
around
it.
So
maybe
these
restructuring
that
folder,
where
we
have
all
these
subfolders
and
making
a
folder
for
learn
a
folder
for
you
know
putting
contents
and
folders
or
represent
the
hierarchy.
The
logical
hierarchy
would
be
a
good
step
to
say
that
a
minimal
configuration
does
not
leave
people
with
their.
B
B
B
I
am
just
gonna
drop
261
into
the
chat.
That
is.
The
download
grid
item
will
keep
comments
here
to
three
minutes,
or
so
it's
okay
to
leave
the
agenda
label
on
this
one
and
the
previous
one
as
well.
Should
the
conversation
want
to
continue
at
the
next
name,
any
latest
context
from
folks
who
have
been
working
on
the
download
grid
or
want
to
work
on
the
download.
G
G
G
B
But
yeah
it
is
also
in
our
okay
ours,
because
down
the
download
grid
is
one
of
the
most
used
features
in
the
existing
website
and
added
like
essentially
we're
reproducing
that,
so
that
we
can
get
this
out
the
door.
Oh
so
I
just
updated
here
that
you're
taking
this
and
we
can
move
on
to
issue
127
five
minutes
left
by
you
127
is
how
do
we
want
to
add
new
members
miles
open
this
a
while
ago?
B
G
G
B
I'll
leave
the
label
on
so
they
can
take
a
look
next
time.
That's
okay
with
me,
and
we
are
ending
the
meeting
with
four
minutes
to
go,
which
is
really
good
for
us.
We're
typically
like
very
much
on
the
cusp
of
the
hour.
I'm
gonna
pause,
the
recording
I
mean
stop
it
for
now
and
then
uploaded
to
YouTube
later,
since
we
weren't
able
to
livestream.