►
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).
B
Hi
Ron,
okay,
so
the
first
issue
or
question
is,
should
be,
and
we
touched
on
that
like
last
meeting
I
think
now
there
was
a
question
from
a
customer
of
cross,
linking
like
one
other
use
case
for
tracking
the
external
issues
being
able
to
keep
the
links
from
Princeton's
commands
or
some
some
other
external
stuff
into
the
github
issues.
So
now
that
I
think
that
we
wanted
to
destroy
the
externally
she
to
be
able
to
know
like
which
issues
were
kind
of
not
imported
or
something
happened
there.
B
So
I
wanted
to
track
those
external
issues
for
that
situation,
and
now
it
seems,
there's
one
additional
issue:
there's
no
case
to
store
those.
My
question
there
is:
do
we
want
to
add
that
feel
to
the
issues
table
or
should
we
add
a
different
table
where
we
want
to
track
this
connection?
So
that's
the
technical
part
that
needs
to
be
answered,
yeah
and
I'm,
not
sure.
That's
for
NDC,
probably
not
for
embassy,
we're
still
working
on
getting
this
embassy
out.
B
So
is
that
probably
going
to
come
as
a
as
a
next
iteration,
although
to
keep
in
mind,
is
that
we?
If
we
add
it
for
the
next
deterioration
than
anything,
that's
imported
within
MBC
will
not
have
the
capability
of
of
linking
back
to
the
github
issues
from
within,
for
instance,
commit
references,
and
so
on.
C
B
I'll
leave
it
to
the
end.
Maybe
we
can
it's
like
sneak
it
into
in
the
Seekers.
It's
not
the
big
task.
So
to
say
it's
just
adding
a
field
which,
on
its
own,
can
be
a
big
task,
because
it's
setting
to
the
issues
table
which
is
a
big
table,
and
then
there
are.
There
is
a
process
to
do
that,
but
other
than
they
are
just
storing
the
key.
There
is
not
it's,
not
it's
a
one-liner,
but
yeah
we'll
see.
If
we
can
stick
that
in.
B
B
D
A
B
Well,
labeling
is
hard
work
to
sort
somewhat
different
from
what
I'm
saying
he
is
like
how
many
times
the
import
was
actually
run
and
by
whom
and
which
projects
so
like.
If
you
import
once
and
you
don't
keep
any
kind
of
reference
back
to
what
was
important.
When
you
go
next
time
to
the
import
page,
you
you
can
pre
import
the
same
project,
although
it
was
already
imported.
So
maybe
once
you
have
some
sort
of
like.
B
B
The
other
question
is
that
should
be
displayed.
Should
we
have
a
separate
screen
for
that
just
to
go
and
see
it
so
where
would
that
fit
into
the
cold?
Because,
like
right
now
we
don't
have
a
dedicated
page
for
the
imports.
It's
all
done
on
the
issues
page.
Then.
How
does
that
fit
into
into
the
whole
story?
I,
like
with
collar
I,
think
we
discussed
something
like
having
maybe
a
tab
on
the
same
page
where
we
do
they
like
the
import,
but
yeah
I,
don't
know.
What's
the
progress
on
that
here,
I
just
keep
them.
E
Yes,
so
basically
the
first
iteration
is
assigned
to
the
viewer,
so
there
are
only
couple
things
that
I
have
not
done
that
few
things
we
don't
basically
support
like
we
don't
support
cows
texts,
we
don't
support
panels,
and
these
are
the
most
important
thing,
I
think
about
colors.
We
could
extend
our
mouths
down,
but
I
think
it's
not
I,
don't
know
what
it
is.
You
want
to
have
NBC
down
to
be
honest,
I.
C
E
B
One
other
thing
is
that
if
we
do
store
this
journal
keys
and
the
references
within
the
texts
like
commands
or
descriptions,
we
can
probably
reuse
those
keys
to
link
the
issues
now
with
the
ingot
lab,
because
we
will
have
those
references,
so
we
can
parse
them.
Just
update
the
parser
to
parse
these
types
of
references.
So
maybe
we
don't
have
to
like
completely
change
those
links.
I,
don't
know
yeah.
E
B
B
B
B
C
There's
also
benefit,
and
potentially
maybe
parsing
twice,
as
in
do
things
that
have
no
references
at
the
time
of
import
and
then
come
back
and
add
references
and
because,
if
anything
breaks
or
if
we
interrupt
or
if
there's
any
kind
of
issue
there,
at
least
we
will
have.
You
know
the
markdown
parsed
for
the
items
that
were
already
imported
and
we
wouldn't
leave
it
in
a
bad
state.
Does
that
make
sense?
Yeah.
B
B
Okay,
so
there
is
the
label
creation,
I,
think
last
time
for
the
NBC
we'll
discuss,
we
will
who
can
do
the
label
link
of
the
issue
behind
the
scenes
in
the
workflow?
If
you
don't
wireframe
from
Holly,
we
have
this
page,
the
Y
of
creating
the
the
label
I'm,
not
saying
it
adds
a
lot
of
complexity,
but
then
there
are
questions
like
what,
if
I
want
to
label
with
two
labels,
this
important,
three
or
four
or
more,
and
so
on
so
yeah
again,
I'm,
not
sure,
that's
going
to
see
I
think
we
decided
from
BC.
B
F
B
B
B
So
to
me
that
sounds
like
we.
We
encourage
people
to
rerun
the
import
if
an
error
happens,
I'm
like
not
sure,
if
that's
what
we
want
or
we
instead
want
to
have
this
reporting
screen
all
the
like
right
now,
it's
in
green,
we
do
probably
have
some
this
imported
file
and
this
of
the
issue
that
not
import.
So
what
action
do
you
want
to
take
yeah?
Just
as
a
idea,
I
don't
know,
I
have.
F
Concerns
about
that
too,
because
I'm
afraid
that
if
we
encourage
them
to
run
it
again,
that
they're
gonna
end
up
with
the
duplicates
situation
that
we've
been
talking
about.
What
I've
been
told
is
that
that
is
not
an
NBC,
but
that's
something
that
we'll
be
worrying
about
in
the
future
and
not
to
worry
about
it.
B
B
C
When
we
are
on
the
project
like
the
way,
the
button
is
right
now
to
import
from
CSV.
That
is
already
a
known
project
and
if
I
click
on
the
button
there,
it
imports
it
into
that
project
for
the
flow
where
we
do
the
new
project.
You
also
don't
have
to
pick
it
because
you
are
only
create
a
new
project
screen,
so
whatever
thread
is
being
created,
we're
gonna
pour
the
issues
into
it.
So.
A
F
So
one
thing
that
is
missing
from
this
particular
flow
is
the
actual
process
of
creating
the
project.
That's
something
that
again
needs
to
be
added
in,
but
I
was
told,
don't
worry
about
it
right
now.
It's
not
MBC.
Let's
do
research
and
find
out
what
all
we
need
to
include
as
part
of
this
process,
but
that
is
missing
from
here.
Is
that
what
point
do
we
go
through
the
other
steps
that
are
involved
with
creating
that
project
create.
C
Project
flow
is
also
kind
of
shifting
stance
right
now,
because
we
are
looking
to
change
how
that
works.
So
the
the
new
project
creation
I
mean
there's
a
flow
right
now
that
we're
not
happy
with
and
we're
changing
it.
So
it
may
be
good
just
to
stay
away
from
that
for
now
until
that
settles
a
little
bit
and
then
we'll
leave
this
in.
F
F
B
Like
for
the
embassy,
we
don't
need
it
and
then
I
think
we
can
talk
later
on
that
I
was
just
I
just
saw
it
I
wanted
to
raise
like
the
question,
rather
sooner
sooner
than
later.
So,
like
aware
of
that,
it's
not
something
important,
then
I,
don't
think.
Most
of
the
questions
on
this
agenda
today
are
not
for
the
endlessly
I
think
it's
more
of
on
preparation
for
the
next
iterations
of
them,
sort
of
and
being
aware
of
the
things
that
are
currently
there.
F
I'm
up
Oh,
look
at
the
agenda,
I
didn't
even
realize.
I
put
something
in
here:
I
must
have
been
a
couple
of
days
ago.
F
Oh
yes,
I
did
I'm.
So
sorry,
okay,
so
can
we
accurately
show
the
number
of
success
failed?
Attempts
at
the
end
of
the
import
process,
so
Alex
I
know
you
and
I
had
talked
about
this
a
little
bit
and
it's
possible
that
when
I
put
this
in,
it
was
before
I
had
as
much
information
as
I
do
now
about
it,
but
I
feel
that
that's
something
that's
pretty
important
to
Gabe
and
I
also
agree
that
it
would
be
valuable
to
show
so
just
to
confirm.
F
B
A
bigger
question
of
what
a
successful
importing
is
I,
guess:
okay,
because
then
the
important
issue-
and
you
skipped
a
comment
or
an
attachment-
is
that
as
successfully
important
issue
or
not
I,
guess
not,
then
how
do
we
track
that?
How
do
we
count
that?
How
do
we
mark
an
issue
that,
because
almost
everything
imported
is
just
one
command
missing?
Where
I
don't
know
so?
B
But
if
we
talk
strictly
strictly
for
the
NBC,
the
issue
is
created,
then
the
issue
is
imported,
then
yeah
we
can
count
those
and
then
we
can,
in
a
lot
of
instances,
count
the
ones
that
fail
just
rescue
the
exceptions
and
so
on
so
and
also
I
think
we
are
able,
at
least
to
some
extent,
to
get
the
number
of
issues
that
are
supposed
to
be
imported
in
advance.
Now,
I'm,
not
sure
how
that's
going
to
work
with,
if
you
have
to
import
a
million
issues
were
more
from
JIRA.
B
Would
Europe
provide
that
number
back
to
us
in
a
single
request
and
so
on,
but,
like
so
far
it
seems
to
be
providing
them
the
count
of
the
issues
or
commands
that
you
want
to
import.
So
I
think
we
should
be
able
to
get
that
number
in
advance
and
then
compare
against
that
and
provide
a
feedback
like
this.
B
How
many
we
wanted
to
import
and
this,
how
many
we
actually
ended
up
with
so
yeah
and
yeah,
that
that
can
be
done
in
an
MVC
and
again
I
think
we're
going
to
store
that
in
that
same
JSON,
import
data
that
we're
starting
right
now,
because
we
don't
have
a
data
structure
per
se
yet
because
we
didn't
use
that
for
any
other
imports
and
then
yeah
again
for
the
embassy.
Cutting
this
code
will
do
that
there
and
we
should
not
be
querying
that
data
too
much
so
to
say
so.
C
If
we
do
have
the
ability
to
count
success,
partial
success
and
failure-
maybe
not
for
NBC-
that
would
still
be
useful.
So
you
know
it's
it'd
be
good.
If
we
could
know
that
it,
the
issue
was
created,
but
there
were
some
some
problems
with
some
of
the
attachments
or
things,
and
then
we
could
just
count
those
as
partially
the
C
note.
This
money
successfully
imported
this
many
partial
and
this
when
he
failed
and
eventually
then
also
provide
a
list
like
a
CSV
list
of
all
the
issues
that
failed,
so
that
somebody
can
follow
up.
C
B
B
So
if
you
imported
once
you're
done
and
you
move
on
now
because
of
the
ringing
words
and
because
we
use
the
same
data
structure
for
the
mirroring
with
the
JIRA
imported
projects,
we
have
kind
of
a
interesting
situation
where,
if
you,
if
you
have
mirroring
on
a
repository,
enabled
for
the
JIRA
imported
project,
you
may
may
end
up
with
situations
where
I
don't
know,
maybe
well
I
kind
of
prevented
it.
But
there
are
some
sub
niche
cases,
probably
that
I
didn't
think
of
where
you
can
end
up,
because
mirroring
is
scheduled.
B
B
It's
on,
we
don't
track
the
like.
We
don't
track
the
state
for
different
imports.
We
just
have
one
state
object
and
we
use
that
for
mirroring
and
for
important.
So
when
the
import
is
done,
it
sets
to
finished,
but
then
we
do
mirroring
I,
think
every
30
minutes
or
so,
if
mirroring
is
enabled
for
that
project.
B
C
B
B
Again,
just
how
I
solve
it
is
add
a
flag
into
this
same
jisan
data
thing.
So
we're
checking
that
if
that
that
flag
is
set-
and
this
is
actually
an
import
of
the
issues-
if
that
flag
is
not
said
that
it's
just
a
mirroring,
so
we
can
use
that,
but
that's
that
they
take
you
way
to
do
it
so
we'd
rather
have
a
separate
entity
to
track
the
actual
jury,
import,
I
think
so.
Yeah.
D
C
D
B
Good
because,
like
especially
for
the
imports,
every
import
is
so
so
very
different
from
one
another
like
they
will
share
their
little
information
to
only
maybe
only
the
states
but
again
depending
from
very
important,
and
what
is
important.
You
can
have
various
states.
You
can
have
various
flows
and
behaviors.
So
it's
probably
okay
to
just
to
just
have
a
jeweler
import.
D
You
know
I
think
the
best
thing
to
do
is
have
one
one
one
for
each
separate
and
we
can
extend
them
as
we
see
fit
and
we
can
modify
them.
You
know
they
don't
have
to.
They
don't
have
to
be
all
the
same
depending
on
the
needs
yeah
and
from
scalability
point
of
view.
Each
separate
table
is
going
to
be
way
more
lightweight
than
don't
have
members
in
one
table.
A
A
D
B
Think
I'm
going
to
keep
using
at
least
for
now,
I'm,
not
sure
if
I
will
be
able
to
do
it
in
the
MVC.
It's
not
a
big
change
but
like
nothing,
is
a
big
change,
although
again
I'm
just
trying
to
shy
away
to
from
from
reading
things
just
to
make
sure
that
we
do
release
it
on
time
and
you
don't
get
like
missing
the
12:10
just
because
we
added
too
many
small
things
so.
D
A
A
The
first
thing
should
be
like:
what's
the
minimum
amount,
we
can
do
that
we
can
run
even
if
it's
not
particularly
valuable
to
customers,
and
then
this
kind
of
thing
should
be
in
the
second
iteration
or
further
down
the
line
which
is
still
part
of
the
MVC.
But
it's
it
gives
us
a
working
piece
of
software.
First.