►
From YouTube: 2020-11-16 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).
A
I
liked
your
other
camera.
You
were
nice
and
pixelated
yeah,
the
the
eos
webcam
utility
yeah
I'll,
have
it
set
up
tomorrow,
I'm
currently
in
omaha
visiting
in-laws,
oh
okay.
I
did
bring
all
my
av
stuff
with
me
like
I'm
using
my
microphone
here,
but
I
haven't
had
a
chance
to
set
up
the
camera
yet
yeah,
but
I
wanted
to
do
it
for
the
community
today.
Tomorrow.
A
Wow
you
just
you
showed
your
hand
there,
andrew
you're
you're,
quite
a
peyton
manning
fan.
I
think
your
football
knowledge
eclipsed
his
mind
pretty
yeah
by
orders
of
magnitude
as
well.
A
A
Actually,
that's
a
good
reminder
for
everyone:
there's
the
open,
telemetry,
maintainers,
vacation
calendar
and,
if
you're
like
me,
you've
probably
forgotten,
enter
your
vacations
there.
But
please
do
I'll.
Add
that
to
the
notes
right
now,.
E
D
I
added
a
ginger
item
to
the
bottom
of
the
minutes
list
perfect.
A
A
A
Okay,
all
right,
let's
get
started
ted,
looks
like
you're
up
first
on
ot
community
yeah.
C
Hey
yeah
yeah,
just
bringing
up
open,
telemetry
community
day,
which
is
tomorrow,
so
it's
coming
right
up
on
us.
It
would
be
great
for
us
to
have
as
big
a
presence
as
possible
here.
Let
me
share
my
screen.
Real
quick!
Oh
you
got
it!
Thank
you.
Yes,.
C
So,
ideally,
hopefully,
people
can
attend
throughout
tomorrow.
If
so,
please
clear
your
schedule,
if
possible,
open
telemetry
meetings
that
are
happening
tomorrow
should
be
should
be
canceled
or
punted.
So
that
includes
the
the
specification
meeting.
We
won't
have
one
of
those
tomorrow,
the
portions,
where
it's
most
important,
I
think,
to
have
maintainers
and
core
contributors
around
are
during
the
breakout
sessions
and
then
the
maintainers
forum.
C
Obviously,
if
I
could
actually
get
a
list
of
people
who
are
planning
on
being
around
for
any
of
those
things,
it
would
be
great
just
for
me
to
kind
of
know
so.
C
C
If
there's
anyone
who
doesn't
have
a
ticket
to
open,
telemetry
community
a
commit
kubecon,
you
can
purchase
one
they're,
not
that
expensive,
but
if
that's
a
barrier
or
there's
there's
anything
weird
about
it.
Please
please
let
me
know
I
can
wrestle
up
some
kind
of
sponsor
code
for
maintainers
because
we
really
want
to
have
you
all
there.
So
if
it's
just
a
ticket
issue,
just
contact
me
and
I'll
get
you
one.
A
C
I'm
really
excited.
We
have
a
a
a
huge
and
growing
a
participation
list.
Obviously
not
everyone
who
registers
shows
up,
but
we
traditionally
get
a
spike
in
registrations
for
these
things
like
the
day
of
day
before
so,
it
looks
like
it's
going
to
be
very
well
attended,
so
hopefully
it's
also
well
attended
by
by
core
members
of
the
community
so
that
we
can
answer
their
questions
during
the
breakout
sessions.
A
I'm
excited
it's.
This
is
the
first
sort
of
big
summit
we've
had,
I
guess,
outside
of
weekly
sig
meetings,
but
where
we're
gonna
get,
I
think,
a
lot
more
community
members
who
aren't
like
active,
sig,
maintainers
or
heavy
active
contributors.
So
it's
gonna
be
interesting
to
speak
to
them,
and
I
think
it's
also
gonna
be
interesting
in
the
breakouts
to
hear
what
they
have
to
say
here.
A
What
questions
they
have
yeah
yeah
in
the
last
year
like
I
know
we're
not
at
ga
yet
or
certainly
not
even
at
rc,
yet
for
most
of
the
sdks,
but
you
look
at
the
size
of
the
community,
the
scope
of
the
project,
how
it's
grown?
It's
pretty
incredible.
This
is
the
first
time
we
really
are
able
to
take
that
in
since
san
diego.
I
guess.
C
Yeah
yeah,
it's
it's
notable
that
yeah.
The
attendee
list
is
much
larger
than
contributor
list
to
the
project
so
yeah.
It's
definitely
going
to
be
a
community
event.
Yeah
and.
C
This
event
takes
the
place
of
the
observability
summit,
which
I
ran
at
the
last
two
kubecons,
so
I
was
glad
to
see
attendance
go
up
when
we
changed
it
to
open
telemetry
yeah.
So
please,
please
show
up
and
yeah
looking
forward
to
seeing
you
all
there
tomorrow.
D
Sure
so
this
is
the
tracking
github
project
in
the
open,
telemetry
org.
That
shows
our
priority
one
issues
and
the
summary
of
where
we
are
right
now
with
that
is
of
the
p1
issues
as
tracking
for
the
spec
repo
we've
got
15
to
do
almost
all
of
them
are
spec,
metrics,
related
and
in
progress.
We've
got
four
issues
that
have
associate
prs,
some
of
them
enclosed.
I
saw
like
carlos
closed
one
like
earlier
this
morning,
so
we
had
a
p1
just
slide
on
into
the
done
column
and
yeah.
D
It
looks
like
that.
The
lion's
share
is
on
the
metrics
sick
type
related
topics.
So
I'd
like
to
talk
at
at
some
point
about
moving
the
metric
sig
into
the
spec
sig
meeting.
D
There
is
one
other
item
that
came
up
during
discussions
that
I
just
want
to
highlight
here
that
I'm
not
sure
whether
this
overlaps
with
our
what
we
want
to
get
in
for
traces,
but
there
is
a
an
outstanding
issue
in
the
proto
repo
for
maturity
of
otlp
json,
and
this
was
let
me
see
if
okay
yeah,
so
I
don't
know
if
tigran
was
on
the
call,
but
we've
frozen
for
the
trace
proto
for
the
grpc,
but
for
json
this
is
going
to
have
an
effect
on
javascript
browser
interactions.
D
So
this
is
something
that
I
think
it
is
a
related
piece
that
is
related
towards
spec
traces,
that's
not
in
the
spec
repo,
but
is
an
open
telemetry,
but
so
proto
repo.
So
just
want
to
highlight
that,
and
I
have
two
other
items
to
talk
about,
but
I
saw
this
one
get
slipped
in.
I
kind
of
put
my
status
update
ahead
of
that.
I'm
not
sure
who
who
who
added
this
do
we
need
to
talk
about
drop
spams.
G
I'll
open
it
up.
Oh
sorry,
that
was
me
yes,
I
just
this
is
just
for
maintainers
for
your
information.
We
dropped
this
one.
This
was
an
important
item.
This
was
required
for
ga,
so
just
please
check
it
out.
It
has
a
new
related
compliance.
Metrics
entry,
there
yeah
just
check
it
out
that
that's
all
from
my
side.
A
G
Actually,
I
don't
have
a
clear
idea,
I'm
actually
based
on
a
conversation
that
I
had
with
john
last
week.
This
is
something
that
we
will
be
talking
in
the
to
this
week,
so
the
this
meeting
is
on
wednesday.
So
I
hope
I
can
give
you
a
feedback.
Sorry,
an
update
on
that
after
that
yeah
sorry
for
the
delay.
A
Yeah
no
worries
yeah,
I'm
just
trying
to
just
get
a
sense
of
where
we
are
like.
Whatever
I
understand
is
for
timing.
When
are
we
going
to
be
able
to
get
the
declare
the
sort
of
release
candidate
freeze
of
of
the
metrics
and
tracing
specs
together
and
then
based
off
of
that?
A
When
do
we
think
that
the
sdks
will
issue
their
first
release
candidates
and
whether
that's
going
to
be
like
december
of
this
year
or
perhaps
even
late
november,
though
I
imagine
that's
way
too
ambitious
or
whether
that's
going
to
be
you
know
early
in
the
new
year,
yeah
perfect
yeah.
I
will
I
will
let
you
know:
okay,
perfect
thanks
all
right,
andrew,
I
think
you
had
some
other
topics,
or
did
you
go
through
all
of
them.
D
So
the
the
next
topic
that
falls
on
with
the
ga
status
of
the
spec
issues
is
talking
about
moving
the
metric
sig
into
the
spec
6.
So
I
brought
this
topic
up
before.
Is
it
like
at
some
point?
I
think
it
might
be
appropriate
to
cancel
the
metrics
sig
meeting
and
just
talk
about
the
metrics
spec
issues
at
the
spec
meeting,
making
sure
that
people's
schedule
fit
into
attending
the
the
spec
sig
meeting.
D
For
that,
and
also
I
can
then
bring
to
the
forefront
the
status
of
all
the
p1
issues
of
the
metrics,
the
metrics
issues
in
spec
repo.
I'm
waiting
for
the
inflection
point
for
that
and
I've
looked
I've
kept
an
eye
on
this
re.
This
pr,
which
is
as
it
comes
up,
declare
freeze
for
trace
where
tigrin
has
it's
got
a
lot
of
approvals
out
having
the
status
of
feature
freeze
on
these
various
documents.
D
So
that
way
we
can
kind
of
go
into
maintenance
mode
of
the
trace,
related
issues
and
address
them
as
they
come.
So
I'm
wondering
when
would
it
be
appropriate
time
for
this
to
be
merged,
or
that
I
can
then
follow
on
with
bringing
the
meetings
together
in
this
in
the
specs.
D
A
Want
to
answer
that
or
maybe
ted
sorry.
I
missed
that
all
right.
So
so
there's
a
issue
that
we
have
there's
an
issue
of
pr
that
declares
that
the
the
tracing
tracing
specification
is
now
frozen.
G
A
G
About
that,
yes,
so
basically
we're
waiting
for
the
otlp
port
part
once
that
is
merged,
we
will
waiting
on
me.
A
Okay,
are
you
waiting
on
on
the
the
issue
for
the
reserved
port
for
the
iana
to
get
back
to
us,
or
are
you.
G
No,
we
are
just
waiting,
so
basically
tigran
mentioned
that
the
request
you
know
this,
the
answer
that
you
will
be
getting
may
take
a
little
while,
so
we
are
going
to.
A
Measure
right,
I
got
it
actually
late
last
week
and
I
have
an
update
on
that
today.
A
Oh
nice,
so
I
m-
maybe
maybe
two
I
don't
have
tigers
on
the
call,
but
it
turns
out
that-
and
maybe
I
missed
some
of
the
conversations
that
we
had
there's
already
an
otlp
protocol
that
has
that
report
reserved
was
that
intentional
or
just
a
totally
random
thing
or
did
someone
else
file
this
before
I
managed
to.
A
Yeah,
it's
weird
because
yeah,
okay
I'll
talk
to
tigran,
because
maybe
I
was
wondering
why
he
chose
that
specific
port
number,
and
maybe
it's
because
someone
else
had
filed
something
with
the
same
name
and
we
thought
we
could
piggyback
on
it,
which
is
probably
fine
or
if
someone
else
saw
the
issue
and
and
filed
it
being
a
good
citizen
just
to
file
it
as
soon
as
they
could
either
way
they
got
back
to
me
saying:
oh,
is
this
the
same
aotlp
that
already
has
the
port
reserve
like
look
at
our
documentation,
I'll
tigran?
A
Request,
okay,
so
I
don't
think
it's
coincidental,
I'm
guessing
either
tigran
saw
it
and
suggested
that
number,
because
there
was
something
else
already
with
the
same
name.
That
happened
to
have
it
reserved
which
kind
of
makes
sense
or
someone
else
saw
the
issue
and
sent
something
to
ina
faster
than
I
did.
But
that
seems
unlikely
because
I
filed
it
pretty
quickly.
G
Yeah
yeah
yeah
yeah
and
for
the
record
there
was
only
one
small
light
issue
that
digram
needed
to
update
on
this
pr,
even
without
the
the
answer
to
this
record.
Okay,.
G
A
D
So
as
if
we
get
to
resolution
on
that
port,
do
we
need
to
do
a
quick
pr
to
update
anything
in
the
spec
repo.
A
No
so
that
I
think
carlos
kirkman,
if
I'm
wrong
there
already
is
a
pr-
and
this
is
the
thing
they're
technically
waiting
on
is
with
the
the
port
changes.
A
A
A
It
has
zero
documentation
whatever
it
is
so
I'll
I'll
sync
with
him,
and
then
he
and
I
will
get
back
to
the
ina.
He
wasn't
on
the
original
thread:
okay,
okay,
otherwise
we'll
just
clear
a
new
one
but
yeah,
but
consider
assuming
this
will
get
this
one
it'll
be
fine.
E
Yeah,
I
could
imagine
if
you
use
another
service,
name
and
description
that
doesn't
say
otlp
but
open,
telemetry
language
protocol
or
something
like
that,
then
it
it
should
be
fine,
because
there.
A
D
Okay,
so
the
I
can
move
on
next
topic.
Next
topic
I
have
is
for
ga
planning.
We
have
a
tracking
github
project
for
high
level
items
that
I
brought
over
from
a
spreadsheet
and
I
basically
copied
over
verbatim
what
was
in
the
spreadsheet,
but
there
was
like
a
matrix
of
languages
to
also
track
against.
D
So
I
have
like
a
few
questions
related
towards
how
we
should
use
this
going
forward.
One
of
them
is
solidifying
all
the
different
languages
that
we
want
to
track
for
ga
going
forward.
I
prefer
not
to
have
like
every
single
language.
You
should
keep
tracking
just
to
reduce
the
amount
of
scope
and
work
and
status
across
all
of
them,
so
all
the
ones
that
we
do
want
to
track
for
ga
going
forward.
I
know
we
got
a
couple
of
core
ones.
D
The
java
javascript
python
go
c,
sharp
is
erlang
really
in
the
mix,
is
php
really
in
the
mix.
Is
rust
really
in
the
mix
and
I'm
not
sure
about
you,
know
c,
plus,
plus,
and
ruby
and
and
stuff.
D
But
so
that's
my
question
is
every
single
one
of
these
issues
has
the
same
number
of
languages
to
track
against,
and
so
what
are
the
core
set
of
languages
that
we
want
to
track
for
for
ga
going
forward
wondering
if
that's
the
decision
we
can
have
right
now
is
that,
based
on
the
blog
post
that
morgan
you
had
before.
A
Yeah,
that
was
to
my
best
understanding,
so
that's
go
java,
javascript
python
and
then
we'd
also,
I
think
I'd
add
a
dotnet
to
that,
because
the
dotnet
segment
said
that
they
would
they'd
be
able
to
make
the
same
timeline
as
for
other
languages.
If
there
are
other
languages
that
can
make
the
same
timeline,
that
would
be
fantastic
because
for
beta,
for
example,
erlang
also
made
beta
at
the
same
time
as
those
other
languages.
So
I
don't
know
if
we
have
tristan
and
oh
there,
you
go
perfect,
pretty
sure
we'll
make
ga.
A
What's
the
timeline?
Look
like
right
now,
it's
as
unknown
as
the
others.
So
it's
it's
going
to
be
dependent
on
the
the
metric
spec
getting
frozen.
A
C
And
fyi,
just
following
up
from
last
week,
there
was
a
request
to
tighten
up
our
language
around
ga
long
term,
support
1.0
and
all
of
that,
I'm
working
on
a
proposal
that
I've
been
floating
around
with
the
governance
committee
and
I
plan
to
present
it
to
the
maintainers
here
next
monday
for
feedback.
A
Okay,
the
next.
A
A
It
will
not
be
yeah
and
the
c
plus
plus,
certainly
they,
I
think,
super
plus
they're
planning
on
redoing
the
entire
metrics
implementation,
so
simple
plus
will
not
be
on
the
same
timeline.
A
E
A
F
Ruby
is
probably
in
the
runnings.
I
didn't
want
to
sign
the
sig
up
without
like
floating
this
idea,
past
them
first,
so
I'll
do
that
at
the
next
sig
meeting
and
yeah
I'll
I'll
update
whatever
it
needs
to
be
updated.
Awesome,
okay,.
B
A
Do
we
know
if
well,
I
assume
both
of
them
are
probably
on
the
same
timeline.
Is
that
correct.
H
I
mean
they
share
a
code
base,
so
there's
a
very
few
components
that
are
split
out
so
that
it
would
be
difficult
to
bring
one
and
not
the
other
perfect.
I
mean
that's.
D
This
is
for
ga,
so
this
is
implementation
of
the
tracing
spec
when
it's
frozen
in
the
metric
spec
when
it's
frozen.
This
is
this
is
looking
a
little.
H
A
So
we
were
talking
about
that
earlier
on
the
call
carlos
is
going
to
get
us
an
estimate.
The
tc
is
talking
about
it
on
wednesday,
yeah.
H
A
I
had
the
same
question
for
for
when
we'll
get
the
metric
spec
freeze
got
it.
Okay,
given
that
there's
like
there's
15
open
issues,
I
I
appreciate
some
of
them
might
be
meaty,
but
given
that
we've
got
it
down
from
like
50
or
whatever
it
was
before,
I
I'm
hoping
that's
going
to
be
on
the
order
of
weeks
rather
than
months,
but
I
am
the
right
person
to
really
comment
on
this.
F
Since
we
were
just
talking
about
browser,
I
know
andrew
quickly
kind
of
mentioned
this
issue
with
otlp
json
in
the
at
the
beginning
of
the
meeting,
but
I
feel
like
that's
in
some
ways.
F
It
is
problematic
I
think,
for
calling
or
node
or
calling
browser
javascript
ga.
If
the
only
exporter,
if
the
only
collector
exporter
doesn't
have
a
stable
protocol,
I
don't
know,
maybe
that's
that's.
H
F
Yeah,
I
think
in
general,
there's
like
a
little
bit
of
reluctance
to
market
stable,
just
because,
like
you're
kind
of
stuck
with
whatever
you
mark
stable
for
json,
you
don't
have
a
lot
of
wiggle
room.
So
I
understand
that.
But
at
the
same
time
it
kind
of
leaves
at
least
browser
in
the
situation
where
you
can't
exactly
call
that
ga
or
tracing
ga.
H
D
Okay,
okay
and
then
definition
of
done
on
these.
D
This
is
what
I
had
in
mentally
in
my
mind,
in
order
to
help
with
giving
a
status
on
like
how
these
are
tracking
was
we
need
to
firm
up
specifically,
what
is
the
definition
of
that
way?
We
know
when
a
checkbox
could
be
checked
and
I
can
help
with
the
languages
after
now
that
we've
kind
of
firmed
down
to
like
what
languages
we're
trying
to
go
after
after
you
know,
ruby
gets
back
to
us
and
whatnot
is
the
and
create
a
corresponding
issue
in
the
language.
Six
that
can
do
the
overall
tracking.
D
That's
how
we
can
distribute
out
the
tracking
of
all
these
11
issues,
the
high
level
issues
for
ga,
but
for
that
I
kind
of
need
a
clear
definition
of
done
so
that
way,
we
know
that
when
we,
when
we
say
it's,
been
taken
care
of,
it's
been
taken
care
of.
C
Yeah
yeah,
it's
definitely
an
issue,
we
don't.
We
don't
really
have
concrete
definitions
for
these
terms,
and
actually
you
know
we
had
some
expectations
earlier
that
I
also
want
to
to
maybe
clear
up
one
just
so
people
aren't
surprised
next
week
we've
been
talking
about
open,
limited.
C
Ga
is
this
like
one
big
event
that
occurs
once
tracing
and
metrics
get
out
the
door,
but
we
were
kind
of
presuming
that
was
going
to
happen
by
end
of
this
year
and
given
that
tracing
is
looking
like
it's
going
to
be
much
more,
it's
going
to
be
stable
months
before
metrics
is
part
of
that
proposal
will
be
a
way
to
explain
how
we
can
launch
and
announce
and
talk
about
tracing
yeah.
E
D
Okay,
just
looking
ahead
because
of
the
vacation
time,
which
is
the
next
topic,
you
make
a
good
point,
two
weeks
from.
D
D
So
a
lot
of
americans
may
be
taking
the
entire
week
off
I'll,
be
taking
the
week
off
as
well
and
permissions
for
adding
it
to
an
hotel
vacation
calendar,
which
is
a
coordination
device
to
it,
hasn't
been
filled
yet
but,
like
so
people
know
like
who's
going
to
be
at
if
a
maintainer
is
not
out
of
sick,
whether
to
cancel
the
sick
or
not
or
letting
the
rest
of
the
community
know.
So
this
is
mostly
for
the
maintainers,
not
everybody
in
the
entire
community.
To
add
to
the
calendar.
I
Hello:
hey
there,
you
are!
Oh
all
right.
Sorry,
my
computer
got
unplugged
over
the
weekend
and
everything
turned
off
yeah.
So
I
just
wanted
to
have
a
quick
discussion
point
about
the
web
hotel
website,
because
I
understand
there
was
some
confusion
about
documentation.
I
So
the
short
version
is
we
get
a
lot
of.
We
actually
get
surprising
about
people
in
through
the
website.
It
gets
linked
out
pretty
regularly
for
sort
of
like
new
users,
people
that
are
just
hearing
about
the
project.
They'll
go
they'll,
find
open
telemetry.io,
either
linked
through
a
blog
post
or
just
through
the
googles
and
that's
kind
of
their
first
touch
with
the
project
rather
than
like
an
individual
sig
github
repo.
I
So
one
of
our
goals
for
the
website
is
to
have
kind
of
a
consistent
set
of
getting
started
documentation
for
each
language
or
for
at
least
the
the
languages
that
are
more
mature
and
to
support
that
there's,
like
some
temp
docs
templates
that
are
in
there
individual
contributors
to
the
website
can
obviously
write
these.
I
I
wrote
one
for
go,
for
example,
because
there
wasn't
a
great
one
to
pull
from.
I
I
believe
java
was
kind
of
adapted
from
stuff
that
the
javasci
had
already
done
and
just
for
everyone
else
like
you,
don't
necessarily
have
to
use
those
templates
right.
You
don't,
it
would
be
great
like
if
you
wanted
to
you
know
if
you're
someone
from
your
sig
wants
to
come
in-
and
you
know,
go
through
those
templates
and
write
the
quick
start
and
put
that
on
the
website
will
gladly
give
you
a
pr
and
if
you
want
to
have
a
maintainer,
be
an
approver
on
the
website
to
ease
kind
of
the
review
process.
I
But
I
I
want
to
be
clear,
like
the
webs
at
this
point
in
time
and
probably
for
the
foreseeable
future,
the
website
documentation
isn't
like
a
replacement
for
what
you're
already
doing
like
this
is
a
thing
to
kind
of
go
in.
In
addition,
so
you
don't
you
know
we
we
don't
expect
to
be
deleting
any
docs
off
of
your
off
of
this
sig
repos.
We
don't
expect
that
only
documentation
will
live
in
the
website,
maybe
in
like
six
eight
months
a
year.
I
You
know
when
we're
in
a
different
place,
then
we
can
talk
about
you
know.
Is
it
appropriate
to
sort
of
consolidate
even
more
documentation,
but
the
goal
for
the
website
really
is
to
when
someone
shows
up.
You
know,
someone
shows
up
for
the
first
time
comes
the
website
and
clicks
docs
that
there's
kind
of
a
clear,
consistent,
uniform
way
that
they
can
get
started
quickly.
That
will
point
them
to
where
they
need
to
go
to
get
more
information
right.
I
So
python,
I
think,
is
an
example
here,
where
python
has
some
incredible
documentation,
that's
done
on
like
a
read
the
docs
site
right,
so
the
python
docs
from
the
website
should
lean
pretty
heavily
by
linking
into
those
docs
same
thing
for
like
go
where
those
links
to
package.go.dev.
I
You
know
the
sort
of
built-in
documentation
and
for
now
those
are
going
to
be
the
canonical
docs
the
stuff
in
the
website
really
should
be
to
give
people
a
quick
start.
Show
them
hey.
This
is
you
know
the
basics?
How
you
use
this
and
here's?
Where
you
go
to
find
out
more
stuff
and
in
the
shorter
term,
or
maybe
the
medium
term,
between
now
and
some
point
next
year,
the
website's
also
going
to
have
a
lot
of
more
how
to
use.
You
know
more
like
scenario
based
so
like
hey.
I
This
is
how
you,
actually
you
know
this
is
maybe
a
reference
architecture.
This
is
how
you
would
deploy
open
telemetry
to
kubernetes
cluster.
This
is
how
you
would
use
open
telemetry
to
solve
a
problem
with
your
software
stuff.
That
is
very
cross-cutting
right.
The
concepts
that
don't
belong
in
one
particular
sig.
I
So
I
hope
that
clarifies
some
of
the
intent
and
if
anyone
has
any
questions,
you
can
ask
me
now
you
can
email
me
or
I
encourage
you.
We
do
the
the
website.
Sig
meetings,
I'm
sorry!
The
communications
sig
meetings
are
every
two
weeks
on
thursdays.
I
There
will
be
one
this
thursday,
so
yeah.
That's
what
I
wanted
to
say
about
the
website
and
docs.
A
All
right
and
ankit,
you
have
a
question:
are
we
doing
a
single
ga
announcement
or
each
language
makes
announcement?
I'm
guessing
it'll
be
a
bit
of
both
both
for
the
rc
and
ga.
To
be
honest,
I'm
expecting
probably
the
rc
is
going
to
be
even
possibly
a
bigger
adoption
point
than
than
even
the
ga.
J
Gotcha,
but
I
drafted
something
for
net,
can
I
just
send
it
to
the
getter
chat
over
here,
just
for
alignment
all
up.
I
just
want
to
make
sure
we
are
not
disaligned
per
language.
Then
that
sounds
good.
J
Yeah
yeah,
I'm
just
going
to
move
it
to
google
docs
and
I'll
post
it
everywhere,
then,
for
sure,
okay,
okay,
thanks
guys
all
right.
Any
other
topics
for.
A
Today,
all
right,
let's
wrap
it
up
early.
Thank
you
very
much
everyone
and
for
those
who've
taken
some
time
off,
happy
holidays
and
we'll
keep
plugging
away,
see
ya,
bye,.