►
From YouTube: 2020-12-10 meeting
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).
C
A
D
Greg,
oh
and
background
it
looks
like
a
real
one:
yeah
the
clouds
even
moving
yeah.
C
I
I'm
right
now
in
the
east
side
right
so
and
eric.
Where
are
you
I'm
out
on
kind
of
the
west
side
of
portland
so
yeah?
I
see
yeah.
A
I'm
getting
the
normal
project
sound
rainy
grade
day,
yeah
of
going
there.
A
A
Yeah,
usually
we
wait
a
little
bit
for
some
people
to
join,
but
basically
I'm
almost
saying:
let's
resume
where
we
stop.
It.
D
D
D
Yep,
so
basically,
this
is
our
repo.
If
we
go
to
here,
then
I
set
up
a
project
and
then
I
set
up
a
board.
D
D
It
will
be
very
familiar
to
zach,
so
essentially
this
year
is
for
all
the
stuff
that
we,
you
know
want
to
do,
but
we're
not
about
to
actually
start
doing
this,
so
it's
kind
of
a
backlog
thing
great
and
really
what
what
the
thing?
What
I
learned
today,
what
the
thing
lets
me
do
I
we,
you
can
either
drag
apr
an
issue
here
or
you
can
create
a
card.
So
there
is
like
three
types
of
things
that
you
can
have
on
this
board
and
I
went
through.
D
I
went
through
like
what
we
have
and
some
of
the
issues
that
we
had
made
sense
as
a
task
and
some
of
them
didn't,
but
I
just
did
it
at
hawk
if
you
disagree
just
feel
free
to
change
it
so
anyway,
here
I
started
putting
everything
that
kind
of
we
are
keeping
track
of,
but
we
are
not
about
to
like
you
know,
it's
kind
of.
We
should
do
it
sometime
here.
It's
also
a
to
do
column,
but
being
here
it
means
like
we
really
want
to
do
it.
D
So
basically
there
is
we're
going
to
actively
start
working
on
it
in
some
foreseeable
future.
It's
not
theory,
and
here
I'm
putting
everything
that
we
discussed
earlier
today
in
progress
means
someone
is
actively
working
on
it.
Right
doesn't
like
you
know,
for
example,
I
am
actively
working
on
setting
this
board
up.
D
D
Sometimes
people
find
it
easier
to
kind
of
you
know
this
so
that
people
can
go
here
and
like
look.
This
is
like
being
reviewed.
There
is
no
other
active
work
going
on.
If
you
feel
like
it,
we
can
merge
it
whatever
I.
I
did
it
this
way
for
now,
but,
like
you
know
at
the
ad
hoc,
I
kind
of
copied
what
we
have
in
on
our
team,
but
we
have
it
for
because
it
sort
of
makes
sense
right.
D
So
this
one
I
actually
if
there
were
tags
in
the
system,
I
prefer
to
have
this
as
tags,
but
I
don't
see
a
good
thing
for
tags.
It's
like,
if
you
have
a
item
that
really
should
be
in
progress,
but
it's
blocked,
so
you
cannot
make
progress
so
that
if
it's
in
progress
forever
people
you
know
the
task
would
would
arise
like.
Are
you
actually
making
progress?
D
So
you
know
some
teams
prefer
to
put
a
label
or
a
tag
on
on
a
corresponding
item,
but
I
don't
think
there
is
a
facility
for
it
here.
So
that's
a
column
for
things
that
are
like
in
progress
but
blocked
and
then
the
last
one
it's
done
or
cut.
I
don't
think
we
need
a
difference.
We
can
have
two.
Actually
it
allows.
You
have
two
terminal
states
or
more,
but
I
don't
know
whether
we
need
it.
D
I
think
it's
just
like
yeah
and
then
there's
also
a
way
to
archive
things
somehow
somewhere
here.
There
is
a
way
to
look
at
archived
items,
but
so
far
I
I
don't
know
so
anyway.
I
set
this
up
and
I
was
just
in
the
progress
or
process
of
copying
everything
that
we
have
here
that
we
discussed
earlier
today
onto
this
board
and
I
didn't
yet
finish
it,
but
I
will,
after
this
meeting
so
here
we
go.
A
Yeah,
I
I
think
it's
great.
I
I
like
the
in
review.
I
I
actually
like
that,
because
I
I'm
overwhelmed
with
github
notifications
and
if
I
have
a
place
that
I
can
see
the
reviews
just
for
that.
That
repo
is
great,
you
know
and.
D
Yeah
there
is
more
pull
requests
here,
but
I
didn't
don't
think
they
needed
like
review,
so
I
didn't
pull
them
here.
D
B
B
And
and
then
greg
for
the
the
labels.
I
know
you
can
put
labels
on
issues
and
pr's,
but
I
don't
know
that
you
can
put
labels
on
the
the
cards.
D
I
I
don't
think
you
can,
you
may
be
able.
D
On
the
la
I
wanted
to
put
it
as
lightweight
as
possible
and
honestly
I
did
this
like
this,
just
because
you
know
we
have
this
thing,
but
I
think
if
we
end
up
using
this,
then
you
don't
want
prs
on
this
board.
You
want
issues
and
for
for
things
that
do
exist
like
really
most
teams
that
I
know
who
are
big
and
are
github-centric
they
go
like.
Why
do
you
have
a
pi
if
there
is
no
issue
for
it
right.
D
Like
we
don't
do
this,
for
example,
because
we
have
an
internal
tracking,
we
don't
have
issues
for
everything,
but
like
people
who
pretty
much
everybody
who
I
know
who
is
like
all
on
github,
including
item
tracking,
they
they
don't
have
prs
without
issues,
and
here
they
just
check
issues
and
notes,
because
pi
is
like
it
only
it's
either
in
review,
or
it's
done
right.
I
mean
sort
of
anyway
for
now
I
just
put
it
here
so
that
we
really
the
only
reason
why
we
started
looking
at.
D
A
Yeah
yeah
and
we
kind
of
discussed
a
lot
of
paths
that
we
could
take
in
about
how
to
prioritize
the
work
and
the
things
that
you
are
seeing
committed
on
the
column
on
the
board.
A
Are
they
stuff
that
we
are
kind
of
to
prioritize
on
the
short
term,
with
the
goal
for
us
kind
of
having
something
that
we
perhaps
can
start
to
have
with
minimal
support,
but
we
can
start
to
have
minimum
functionality
actually,
but
we
can
start
to
deploy
at
least
to
some
people
that
are
eager
to
try,
let's
say
alpha
of
of
open
telemetry
and
also
it
gets
us
moving
and
testing
the
new
stuff
that
is
being
implemented.
A
One
thing
that
we
talked
about
was
about
having
the
open
telemetry
just
using
call
target
and
not
using
the
old
instrumentation
that
the
the
current
one
so
open
telemetry
becomes
kind
of
a
beach
head
to
test.
That
kind
of
that
new
feature.
B
No
nope,
and
so
eric
as
part
of
that
work,
the
ability
to
to
test
this.
We
need
to
be
able
to
export
so
there's
a
pr
out
there
to
export
the
data
in
zipkin
format,
but
we
we
would
still
need
the
data
exported
to
to
be
in
compliance
with
the
open,
telemetry
semantic
conventions,
and
so
that's
part
of
this
work
as
well.
That's
being
split.
B
A
Yeah
so,
as
chris
already
mentioned,
I
I
put
yesterday
the
pr
for
zip
increase
already
has
some
feedback.
I
didn't
have
time
yet
to
go
over,
but
hopefully
I
go
today
over
that
and
soon
we
have
the
export.
I
I
put
it's
very
simple.
I
I
didn't
want
to
make
anything
complicated,
but
this
should
be
able
to
get
people
testing
exporting
for
zipping.
If,
if
we
need
other
formats,
I
I
I
think
anyone
can
implement,
but
I
think
zipking
is
good
enough
for
us
to
test.
D
And
then
for
for
once,
that's
done
we'll
organize
a
meeting
with
tony
who
can
give
us
a
tutorial
on
on
the
best
way
to
port
integrations
to
to
code
target
and
then
in
the
process
of
we
will
pick
a
few
most
important
ones
and
in
the
process
of
doing
it,
we
will
also
modify
them
to
to
use
open,
telemetry
semantic
conventions,
while
also
understanding
how
we
can
avoid
breaking
the
existing
data
flow
so
that
we
don't
get
code
diversions.
D
D
A
One
I
think
I
mentioned
last
week
that
I
have
kind
of
until
the
the
next
week
this
year,
so
I
I
and
I
have
mentioned
I
was
going
to
move
some
work
up
front
that
is
not
related
to
open
11,
so
I
could
educate
more
time
to
open
the
length
that
is
kind
of
looking
good.
I
should
be
able
to
do,
but
most
of
next
week,
basically
just
open
the
limit.
D
We
have
tasks
so
as
soon
as
this
merge
is
done,
I'll
get
I'll,
spend
some
time
on
the
on
the
library,
so
that
will
make
progress.
Then.
So
I
think
if
you
can
start
with
this
one,
paulo,
that
that
would
be
awesome
and
chris,
I
think
the
two
tasks
that
you're
picking
up
also
made
made
sense
right
from
your
perspective,
so
and
then,
like.
D
I
guess,
in
whatever
way
you
feel
fit
like
either
that
you
can
create
a
small
document
that
describes
how
we
should
like
have
the
subtraction
or
we
can
just
discuss
it
or
some
sort
of
way
to
communicate
it
to
to
people
who
cannot
attend.
The
meeting
would
probably
be
good,
but
whatever
you
feel
is
appropriate.
B
Yeah,
no,
definitely,
I
think,
having
a
document
makes
sense
and
then
this
way
people
can
comment
on
that
and.
D
Cool
cool,
then
maybe
this
can
become
an
issue
so
that
we
can
comment
and
discuss
it
there,
I'll
I'll
change
it,
and
then
the
small
branch,
like
finish
rendering
and
blood.
This
probably
doesn't
need
to
be
an
issue.
This
can
be
a
card.
D
D
I
have
nothing
else
since
we
already
it's
it's
like,
basically
for
the
context
we
we
met
with
with
chris
and
paulo
earlier
today,
because
we
wanted
to
look
at
code
and
detailed
stuff
and
didn't
want
to
use
everybody's
time
for
it
and
that's
what
came
out
of
it
so
on.
On
my
end,
there
is
no
news.
I
spent
a
lot
of
time
studying
what
david
showed
me
last
time
and
things
around
it.
D
D
I
spent
I
had
a
lot
of
fun
the
last
few
days
trying
to
have
the
have
managed
code
use
and
nate.
So
basically,
I
wanted
to
have
a
string
object
that
is
shared
so
that
I
can
create
a
string
object
in
native
code
and
then
I
wanted
to
use
it
in
managed
code
without
copying.
The
string-
and
I
like
you,
know,
assuming
that
nobody
is
actually
modifying
it,
but
I
couldn't
figure
it
out
so.
E
D
Yeah
I
was,
I
was
thinking
that,
but
I
I
was.
I
was
a
bit
scared
that
some
kind
of
unicode
like
I
was
scared
that
the
managed
string
wouldn't
be
simply
like
two
bytes
per
character
and
then
be
stupid
about
it.
I
I
just
was
worried
that
there
is
some
kind
of
edge
case
that
are
very
rarely
but
sometimes
occurs,
and
when
you
become
ignorant
about
it
something
gets
broken
eventually.
So
that's
why.
E
It
should
always
be
16
bytes,
I
don't
think,
there's
cases
do
we
ever
use
udf8.
No
I'd
have
to
look,
but,
generally
speaking,
it
should
be.
You
know,
16-bit
characters.
This
is.
E
Yeah
there's
even
because
on
linux
we
we
use,
you
know
car
16s
and
it
makes
it
really
difficult
to
interrupt
with
anything.
So
where
is
the?
E
No,
so
when
you
pin
something
it
pins
it
in
place
and
pinning
for
a
really
long
time
can
cause
issues,
because
what
happens
is
so
if
you
have,
if
you
have
a
gen
zero
object
and
you
pin
it
for
a
really
long
time,
the
gc
can
never
move
that
gen
zero
object,
and
so
it
basically
has
to
work
around
it
and
it
can
cause
some
pretty
big
perf
issues
so
yeah.
So
what
our
general
advice
is
is
to
make
sure
it's
in
gen
2
before
you
pin
it.
E
If
you
want
to
pin
it
for
a
really
long
time,
and
there
are
various
ways
that
you
can
do
that,
if
you
just
have
one
object
and
you
want
to
pin
it
for
a
really
long
time
is
you
can
just
call
gc
twice
and
but
another
way
is
to
you
know
a
lot
of
people.
Do
it
with
buffers,
and
so
our
advice
is
to
maintain
a
buffer
pool
where
you
you
know,
instead
of
deleting
the
objects.
E
Well,
I
guess
you
don't
delete
them,
but
instead
of
letting
them
be
reclaimed,
you
just
reuse
the
same
buffer
over
and
over
again
and
and
then
they
will
eventually
end
up
in
gen
two,
and
so
it
doesn't
matter
how
long
you
pin
them
and
then
in
dot
net
five
there's
actually
a
way
to
just
allocate
an
object
on
a
special
heap.
That's
called
the
pinned
object
heap,
so
you
don't
have
to
worry
about
any
of
this,
but
it's
only
done
at
five
and.
D
I
I
was,
I
was
worried
about
like
I
this
this
gen
zero
pinning
thing,
and
I
think
it's
it's
it's
all
about
resolving
symbols,
and
I
actually
initially
had
a
prototype.
That
was,
you
know
I
would
do
the
whole
stack
walking
and
then
I
would
resolve
all
the
symbols
and
then
put
them
in
a
cache
from
where
they
would
like
never
leave.
And
then
I
wanted
to
put
it
all
in
managed
code.
D
D
A
Yeah,
I
think
I
think
we
we
had
a
pretty
good
meeting
this
morning
and
we
have
things
to
act
on
the
short
term
so
and
what
we
are
trying
and
I
will
try
to
post
this
on
the
guitar
greg
chris
and
I
we
we
said
that
this
morning
are
going
to
try
to
integrate
fast
kind
of
perhaps
instead
of
waiting
the
meeting
to
discuss
something.
Perhaps
we
post
something
there
on
the
git
and
the
three
of
us
got
together
and
move
ahead.
A
You
know,
so
we
we
get
the
blocks
out
one
thing,
especially
for
greg
and
zach.
If
you
could
look
at
the
zip
king,
don't
worry
so
much
about
the
code
of
the
export
itself.
You
can
always
optimize,
but
the
integration
points
where
we
pick
up
configuration
this
kind
of
thing,
not
nothing.
There
is
this.
Definitely
it's
just
a
small
thing,
but
perhaps
gives
ideas
about
the
directions
that
we
want
to
go
down
the
road.
You
know.
D
You
cool
all
right,
well,
cheers
guys
have
a
great
week.
We
have
work
items
to
do
so
see
also.