►
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
B
Cool
I
had
the
first
agenda
item
and
the
second
one
I'll
try
to
keep
them
briefer,
so
we
can
get
to
the
other
points
on
the
list
holly.
I
did
also
add
one
at
the
end
for
you,
since
you
asked
for
some
feedback.
Thank.
B
No
one
had
yet,
but
I
figured
this
was
a
good
chance
to
come
back
around
to
it.
So
the
first
thing
I
want
to
share
was
just
like
a
cool
moment.
I
felt
like
I
had
last
week
and
it
tied
actually
well
into
michael
lay's,
mr
he's
working
on,
but
I
see
kai
from
the
code
review
group.
The
pm
he's
really
really
skillful
about
saying,
no
specifically
by
tying
in
data
that
we
can
pull
from
git
lab
itself.
B
So
I
was
tripping
over
this
design
decision
of
whether
to
use
like
a
text
area
for
an
input
or
just
like
a
regular
form
form
input,
because
we
were
concerned
about
the
name
space
length
between,
like
the
group,
the
subgroup
and
the
project
becoming
so
long
that
it
would
extend
past
the
input
form
so
like.
Why
don't
I
just
ask
an
engineer
to
help
me
figure
out?
If
that
would
be
likely,
we
didn't
pull
back
all
the
data.
B
I
think
it
would
take
way
too
long
to
do
that,
but
he
pulled
a
good
sample
size
between
like
a
lot
of
starved
projects.
I
think
it
was
like
hundreds,
if
not
maybe
a
thousand
records,
or
so
none
of
them
had
names
had
like
a
namespace
or
a
project
full
name,
which
I
think
is
what
it's
called
in
our
back
end.
That
was
longer
than
60
characters.
B
So
this
seems
like
something
that
would
be
over
engineering
for
a
smaller
size
of
the
user
base.
So
it's
possible
that
you
know.
Maybe
some
of
our
staging
environments
might
be
annoying
to
see
the
full
length,
but
since
we
decided
to
not
disable
pasting,
and
since
we
were
saying
this
is
a
less
frequent
problem,
it
made
that
design
decision
easier.
B
B
Yeah,
the
next
one
I
will
I'll
share
my
screen
for
this.
I
brought
this
up
several
months
ago
and
it
was
just
kind
of
like
a
first
foray
into
thinking
about
how
we
might
configure
this
ability
to
stream
audit
events
outside
of
gitlab.
B
One
of
the
unique
constraints
with
audit
events
is
our
database
isn't
particularly
set
up
well
for
a
massive
influx
of
data,
which
means
that
we
don't
actually
show
all
the
events
that
we'd
like
to
an
example
of
this
would
be
like
push
events.
We
don't
capture
all
of
those
actions,
it's
just
too
many
for
our
database
to
handle,
but
we
would
love
to
be
able
to
help
send
this
data
elsewhere.
So
there
are
audits
in
which
you
have
to
know
this
event,
information
and
what
people
are
doing
today.
B
It's
like
building
custom
scripts
to
pull
this
data
out
of
git
lab
or
asking
gitlab
themselves
to
help
aggregate
this
information.
So
we
had
a
mvc
of
a
back-end
api.
Only
you
can
you
basically
just
say
this
is
where
I
want
to
send
the
data.
Here's
the
url
and
then
here's
my
group
id
pull
the
events
for
it,
and
so
kind
of
next
question
is
well.
How
do
we
start
integrating
that
back
end
feature
assuming
it
starts
pulling
well
with
our.
A
B
Good
news
is,
I
wasn't
actually
walking
through
anything
yet
so
that's
great,
but
thank
you
for
correcting
me
holly,
so
we
could
get
into
the
visuals
because
that's
coming
next.
C
B
Yeah
so
anyways
this
is
a
lot
of
events,
looks
like
today,
you
can
access
it
in
advent
area
and
the
group
level
on
the
project,
and
so
what
I
was
thinking
of
were
a
couple
different
options
to
try
and
introduce
it.
I'm
just
trying
to
figure
out
what
maybe
makes
the
most
sense
in
terms
of
an
mvc
approach
of
being
able
to
iterate
into
something
over
several
milestones.
B
That's
more
comprehensive,
but
also
isn't
super
complex,
and
we
would
still
want
to
be
able
to
validate
something
with
users
in
terms
of
the
way
you
would
set
it
up.
So
the
first
thing
I
was
thinking
is:
while
we
have
this
back
end
only
feature
is
using
a
banner
to
create
awareness
of
how
users
can
set
this
up
by
following
our
documentation.
B
So
you
can
go
over
to
the
stream,
get
a
call
to
action
to
go
set
it
up
following
a
similar
pattern
to
what
we
do
with
web
hooks.
We
might
not
be
able
to
do
all
these
things
in
nbc.
It
might
just
literally
just
be
the
destination
url,
but
ideally
maybe
we
also
are
keeping
like
the
secret
token
as
an
option,
doing
ssl
verification,
I'd
love
to
be
able
to
allow
users
eventually
to
pick
specific
events
they
want
to
send
externally.
B
But
our
small
nbc
that
we
have
now
is
you're
just
getting
everything
and
it
can
be
a
lot,
so
you
got
to
be
really
ready
for
it,
and
then
I
want
to
be
able
to
present
back
to
the
user
a
way
to
know
like
the
status
of
these
things,
which
is
this
is
very
similar
to
web
hooks,
which
I
know
is
closer
to
leeward's
world.
So
there's
some
other
ideas
that
go
with
that.
B
So
I've
got
this
like
tab
view
that
I
was
thinking
through
another
one
was
like
maybe
just
keeping
it
all
on
one
page,
so
like
tying
the
buttons
on
the
same
page,
to
try
and
create
a
similar
experience.
But
I
think
the
downside
to
this
is
the
end
of
sharing
like
the
same
real
estate.
So
it
could
put
priority
over
one
over
the
other,
depending
on
like
the
location
that
they're
living
in
and
if
you
have
a
lot
of
streaming
destinations
set
up,
it
could
conflate
the
experience
a
bit.
B
B
But
the
other
ways
I
was
thinking
about
setting
up
was
like
we
could
try
and
tie
directly
into
web
hooks
by
like
adding
an
additional
trigger
for
audit
events
and
libor.
I've
presented
this
design
to
you
before
as
like
an
idea
just
being
able
to
pick
it
as
a
specification
and
kind
of
re
build
off
of
their
existing,
like
project
hook,
design
style,
the
way
that
you
test
it
edit
it
and
manage
those
things
and
one
other
way.
I
was
thinking
about
it
just
trying
to
get
as
many
options
out
there
as
possible.
B
There's
a
configuration
section
in
security
and
compliance
and
security
and
testing
is
the
most
like
verbose
one
right
now,
but
I
was
thinking
about
adding
one
for
specifically
audited
events
that
would
give
you
a
call
to
action
for
setting
up
your
streaming
destination
and
then
eventually
being
able
to
bring
the
form
inside
of
the
app
itself
being
able
to
customize
it
from
there
long-winded
way
of
saying
these
are
the
different
variations.
I
was
thinking
of
being
able
to
help
users
set
up
their
destination
to
stream
audit
events.
C
Yeah
awesome,
I'm
curious
that
one
thing
that
comes
to
mind
is:
have
you
guys
done
any
like
problem
validation
on
this?
Yet
do
you
have
any
specific
clients
or
customers
in
mind
that
have
or
have
this
problem
that
you
could
maybe
reach
out
to
and
maybe
use
your
tests
with?
Would
you
like
a
preliminary
like
solution,
validation
with
them.
B
Yep,
so
we
did
some
preliminary
validation
with
two
or
three
customers.
I
want
to
say
earlier
last
spring
and
summer
to
talk
about
this
idea
of
sending
the
event
data
outside
of
gitlab.
We
got
like
a
lot
of
good
thumbs
up
like
yes,
we
definitely
want
to
be
able
to
take
some
of
this
data,
especially
if
you're
not
going
to
give
it
to
us
in
gitlab.
B
Some
even
said
that
that
would
be
preferable
to
gitlab
because
they
coalesce
all
their
data
together
in
like
splunk
or
something,
and
they
look
at
a
more
holistic
list
of
not
just
like
the
gitlab
data,
but
also
data
from
aws
or
other
applications,
as
well,
so
being
able
to
bring
it
all
into
their
own
data.
Warehouse
to
them
was
preferable,
I
will
say
in
terms
of
our
competitor
products.
B
One
had
already
set
up
a
similar
feature
to
this.
That
also
lets
you
stream
data
to
preferred
partners
and
then
another
one
released.
A
beta
of
this
exact
same
feature
is
not
in
their
ui,
yet
it's
just
all
api
as
well,
so
we're
getting
indicators
from
both
our
competition
and
from
our
customers.
That
being
able
to
take
the
log
data
out
of
gitlab
is
definitely
useful.
C
Got
it
yeah
that
makes
sense
yeah,
I
would
think
about
you
know,
maybe
trying
to
show
you
know,
show
customers
some
of
these
concepts.
You
know
thinking,
maybe
and
maybe
even
vetted
by
engineering.
My
gut
is
that
maybe
that
web
hook
way
is
maybe
not
the
most
elegant
way
that
exists
today.
You
know,
but.
C
B
Ours
is
like
so
much
bare
bones
right
now:
we'd
have
to
strip
away
functionality
like
we're,
gonna,
be
able
to
do
testing
or,
like
probably
be
able
to
communicate
the
status
super
well
just
yet
like
I'd
love
to
be
able
to
come
back.
But,
yes,
you
gotta
get
200
response
from
this
api,
but
that
may
not
happen
right
away
right
now.
It's
just
kind
of
like
you're
blindly
sending
events
and
currently
you're
dependent
on
your
api
to
provide
you
that
feedback
and
we're
just
starting
to
figure
out.
B
How
can
we
start
exposing
that
a
little
bit
more
in
the
ui?
So
that's,
maybe
the
one
thing
that
steers
me
away
from
web
hooks,
but
at
the
same
time
I
understand
that
they're
kind
of
a
similar
technology.
It
just
kind
of
sucks
that
they're
so
far,
apart
from
each
other.
D
D
Of
the
images
maybe
more
yeah
there.
B
I
agree
one
of
the
things
we
have
not
figured
out
yet
is
how
can
we
like,
let
users
better
pick
the
events
that
they
care
about,
which
is
why
we're
starting
with
you
just
get
everything
right
now,
so
this
would
be
more
of
a
visionary
like
we
have
to
try
and
figure
out
a
better
way,
because
there
are
so
many
events
and
they're
only
going
to
grow.
B
B
So
it's
not
very
scalable,
but
the
scalable
id,
at
least
to
start
is
being
able
to
send
everything
and
that's
up
to
users
whether
they
have
the
hardware
that
can
meet
that
volume
of
events
for
their
specific
environment
and
we're
just
kind
of
giving
that
option
to
them.
They
can
take
it
or
they
could
just
not
gitlab
can
continue
to
handle
it,
but
the
thing
that
we've
been
struggling
with
over
the
past.
B
C
Do
you
mind
after
linking
the
issue
to
this,
I
saw
you
link
just
the
figma
file.
I
guess
the
figma
file
also
has
a
link
to
the
actual
issue.
C
That,
I
might
add
like
later
this
week,.
B
Yeah
I'll
have
to
make
sure
that's
the
right
issue
number
it
might
not
be
possibly
because
I
think
the
initial
thing
was
like
a
design.
Psycho
show
customers
and
we
did
that.
So
I
closed
that
issue
and
I
might
still
be
using
that
same
figma
file.
There's
another
issue
to
like
the
first
nbc
for
the
front.
End
of
the
back
end
feature
that
we
built,
and
I
think
that's
the
next
thing
I
got
to
go
populate,
but
I
only
got
around
to
getting
all
my
ideas
down
on
paper.
B
Got
it
holly's
putting
in
a
note
about
the
add
stream
button.
A
Yeah,
just
that
and
I'm
sorry,
this
is
a
tiny
little
detail
and
and
the
larger
questions
you
were
asking,
but
I
just
happened
to
notice
it,
so
I
thought
I
would
mention
it.
The
ad
stream
button
is
using,
I
guess,
the
tertiary
styles.
I
was
curious
in
that
example.
It's.
B
Not
all
it's
just
it's
the
default,
but
maybe
the
contrast
on
your
screen
is
much
brighter.
It's
not
as
visible
yeah.
The
thing
that
I
was
struggling
with
on
this
page
is,
I
don't
know
what
the
primary
action
is
like.
I
don't
want
to
say
for
a
user
coming
to
audit
events,
that
the
primary
action
is
too
out
of
stream.
A
B
B
A
A
C
A
There,
if
anybody
has
thoughts
on
that,
I
don't
wanna.
A
B
A
C
C
B
A
B
We'll
do
this
was
helpful.
It
at
least
gave
me
some
ideas
of
ways
to
rethink
some
of
the
ui
presentation,
leave
more
things
for
the
reinforcement
of
going
back
to
customers
and
trying
to
validate
things.
I
think
where
I
probably
go
from
here
is
again
updating
an
issue
like
I
said,
and
then
maybe
just
picking
one
and,
like
you
said
just
running
it
by
some
customers
and
then
maybe
looking
at
our
usage
of
the
back
end
feature
that
we've
created
to
help
guide,
maybe
with
the
selection
of
which
one
we.
B
Test
right
nick
made
his
point
read
only
both
of
them.
I
guess.
A
All
right
well,
then,
would
that
be
me
the
next
one?
Thank
you
so
much
again,
austin
for
reposting
that
let
me
share
my
screen.
Really
quick
got
too
much
stuff
open
here,
so
we
recently
pivoted
when
it
comes
to
work,
items
and
kind
of
broke
up
the
groups.
It
was
go
ahead
and
share
project
management
and
product
planning
working
together
to
create
the
new
work
item,
view
and
long
story.
A
A
From
our
users
is,
we
want
the
ability
to
have
an
issue
and
then
a
child
element
of
an
issue
that
would
be
a
task,
so
we
will
be
working
with
product
planning
from
the
child
aspect
of
this,
but
one
of
the
ways
we're
looking
to
potentially
surface
this
opportunity
in
the
ui
of
converting
something
to
a
task
or
creating
a
work
item.
That
is
a
child
element,
is
through
the
checklist,
so
we
currently
have.
A
But
what
we're
looking
to
do
is
offer
a
way
for
someone
to
quickly
convert
one
of
these
items
to
a
task
which
is
going
to
be
using
that
new
work
item
layout
again-
and
this
is
something
that
github
offers
and
I
believe,
trello
offers
just
this
way
to
quickly
convert
one
of
these
things
to
a
child
element
of
an
issue.
So
this
is
the
default
state
of
that.
A
A
I
don't
like
the
the
bounciness
that
would
have
to
happen
there,
the
back
and
forth,
but
it
was
something
that
popped
into
my
mind
and
I
just
wanted
to
go
ahead
and
get
it
in
front
of
me
and
explore
it.
So
I
could,
if
nothing
else,
kind
of
invalidated
as
as
a
potential
opportunity.
A
My
goal
in
that
was
that
it
would
always
be
in
a
consistent
location,
as
opposed
to
putting
it
on
the
right
side
where
it
might
be
dependent
on
the
length
of
the
content,
unless
we
do
a
bit
more
of
a
tabular
approach,
where
we
kind
of
stop.
That
line
at
some
point
force
a
wrap
and
then
show
the
button
to
the
right
of
that
which
I
did
explore
as
well.
So
that
was
the
thought
in
this
you
hover
over
it.
A
You
just
get
the
option
to
make
it
a
task,
you
click
on
it
and
then
potentially
it
would
go
ahead
and
convert
it
to
a
task.
Now,
while
exploring
this,
I
did
see
some
interesting
feedback
from
users
of
github
who
have
a.
They
don't
have
the
left
align
approach,
but
they
do
have
an
approach
where,
when
you
click
the
option
to
convert
it
to
a
task,
it's
an
immediate
transition
and
people
are
accidentally
doing
that,
and
so
people
were
complaining.
A
Can
I
just
turn
this
off,
because
I
don't
I
don't
want
to
convert
it
to
a
test,
but
it's
happening
just
as
I
navigate
the
ui.
So
I
took
that
into
consideration
too.
The
second
example
is
putting
it
on
the
right,
which
is
a
bit
more
common,
and
I
had
a
really
good
conversation
with
mike
nichols
the
other
day
about
this,
and
he
was
like
you
know.
A
We
force
everything
to
happen
on
the
right,
but
why
couldn't
it
happen
on
the
left
as
well,
because
I
did
explore
that
too
and
I'll
show
that
example
in
a
moment,
but
similar
case
here,
it's
just
it's
on
the
right
and
I'm
thinking
in
this
case
too,
we
would
have
all
of
them
align
in
the
same
place,
so
it
would
be
kind
of
a
table
approach
as
opposed
to
having
it
kind
of
appear
down
here
for
the
shorter
one
and
on
the
end,
for
the
other
and
you're
kind
of
having
to
always
hunt
for
it
a
little
bit.
A
This
is
the
same
approach,
but
just
using
an
icon
as
opposed
to
a
button.
I
I
don't.
I
love
the
succinct
approach
of
icons,
but
I
also
don't
like
the
fact
that
they're
not
quite
as
check
the
time
they're,
not
quite
as
clear
to
the
users,
so
that
was
just
something
else
to
explore.
Currently,
this
is
the
winner,
and
this
is
the
one
that
I
think
I
prefer
as
well.
At
least
in
terms
of
how
it
surfaces
in
the
ui
is
showing
an
ellipsis.
A
There
is
an
option
here
to
remove.
I
don't
think
we're
going
to
offer
that
for
mbc,
but
we
do
want
to
offer
other
options
potentially
in
the
future,
such
as
adding
assignees
or
something
else
related.
So
this
gives
us
a
bit
more
room
to
grow
the
opportunities
and
options
related
to
these
these
lines,
so
that
was
part
of
what
was
being
explored
there.
A
A
So
that
was
something
that
I
think
the
pm
likes
is
having
it
on
the
left,
but
using
that
ellipsis
approach
and
and
providing
a
pop
over
with
a
menu,
but
that's
kind
of
the
first
five
options
that
I've
been
exploring.
I'm
also
looking
into
what
it
looks
like
when
it
has
been
converted
so
showing
probably
an
icon
to
help
differentiate
between
it
and
just
a
regular
link.
I
have
a
question
of
whether
or
not
that's
important
to
the
user.
Does
it
matter
I
mean
currently.
A
If
you
convert
an
issue
to
a
link-
and
you
specifically
give
it
link
text,
then
it
shows
just
this.
Otherwise,
I
think
it
resolves
to
just
the
the
id
so
kind
of
asking
questions
surrounding
that,
also
showing
if
somebody
hovers
over
one,
maybe
that
it
has
been
applied
as
a
task.
So
you
can
see
that
that
that's
the
case
to
help
further
differentiate
and
then
just
showing
like
an
edit
and
the
delete
state.
A
We're
not
going
to
worry
about
for
now
edits
because
it
is
marked
down
just
going
to
be
kind
of
standard,
markdown
approach
and
what
service
is
there
when
you
have
converted
something
I'm
trying
to
rush
it,
because
I
know
we
have
two
minutes
left.
So
I'd
love,
any
feedback
that
you
all
have
or
if
you
have
any
questions
as
well.
D
A
C
D
Perhaps
hiding
its
visibility
only
upon
hover
so
that
it
shows
on
hover
that
it
makes
tasks.
Another
thing
that
I
don't
know
if
it
makes
sense
to
add
or
not
having
two
actions
but
a
toggle
switch
for
make
tasks,
including
the
checkbox.
So
you
have
a
toggle
switch,
then
the
checkbox
then
the
copy,
but
that's
just
my
quick
ideas.
A
That's
what
I
think
too,
I
like
having
it
all
in
one
place:
it's
always
going
to
be
there:
no
movement
and
no
interruption
in
the
flow.
If
you're.
Looking
at
the
other
content,
I
was
just
concerned
that
people
have
become
so
trained
and
seeing
it
on
the
right
that
there
might
be
a
challenge.
I
know
we're
at
times,
so
thank
you
so
much
daniel
for
your
feedback.
I'd
love
to
hear
feedback
from
anybody
else,
but
I
I
actually
posted
a
link.