►
From YouTube: 2022-04-25 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
Okay,
let's
get
started
thanks
everyone
for
filling
these
in
we
are
starting
with
the
spec.
I
wasn't
able
to
join
the
spec
meeting
last
week.
So
do
we
know
from
anyone
if
we
have
updates
from
the
spec
bug?
Do
I
see
her
on
the
call?
Do
you
wanna
or
or
carlos,
actually
carlos
you're,
on
the
wall?
Do
you
wanna
give
us
any
spec
updates.
D
C
Yeah,
sorry,
I
think
my
connection
is
not
very
good.
Today,
yeah,
no
no
update,
we
will
have
a
release
in
theory
in
may
early
may
as
part
of
the
monthly
cadence.
A
Okay,
I'll
assume
that
covers
metrics
and
logs
as
well
so
php.
We
have
the
0.0.10
release
coming
out
excellent
for
java,
both
john
and
anarag
are
going
to
be
changing
jobs
in
the
near
future
and
neither
will
be
being
paid
to
work
on
hotel
anymore
uh-oh.
A
Both
are
committed
to
spending
at
least
a
bit
of
personal
time
on
maintenance,
but
will
unable
to
spend
nearly
as
much
time
previously.
This
leaves
jack
berg
is
the
only
full-time
sponsored
maintainer
on
java
core
call
for
vendors
and
other
java
users.
We
will
definitely
need
some
more
help
with
maintenance
for
the
core
java
libraries
very
soon.
Okay,
this
is
actually
concerning
something
we
need
to
take
action
on.
A
Okay,
yeah.
I
don't
know
if
this
is
immediately
actionable
by
this
group,
but
I
think
it's
a
call
out
to
all
of
us.
If
we
know
anyone
who
wants
to
work
on
java
or
if
any
of
us
do
want
to
work
on
java,
there
is
an
opportunity
here
to
step
up.
E
Yeah,
just
I'm
leaving
I'm
leaving
splunk
at
the
end
of
the
week
and
honorable
is
leaving
aws
in
early
june.
I
believe
so.
That's
kind
of
the
that's
the
time
frame.
Okay,.
A
And
I
take
it,
neither
of
you
are
going
to
places
where
you
will
be
working
on
hotel
java,
well,
not
be
being
paid
for
it
for
sure,
okay,
okay,
cool!
Is
that
true
for
you
do
you
know
if
that's
true
for
anarch
as
well?
John,
yes,.
E
We
talked
about
it
extensively
at
our
our
office
hours
on
last
thursday,
so,
okay.
A
A
All
right,
javascript
released
the
metrics
alpha
and
these
documentation
examples
working
on
cleanup
still
targeting
rc
for
kubecon
excellent
python,
aiming
for
the
metrics
rc
by
the
end
of
this
week,
released
1.11.1
net,
no
updates.
Let
me
see
if
we
have
riley
or
anyone
from.net
on
here
looks
like
no
okay
go
metrics
sdk
alpha
release
is
ten
percent.
We're
blocked
on
28
issues.
Four
is
to
do
five
in
progress.
Five
are
finished
release.
A
One
point:
seven
point:
zero
is
feature
complete
plan
for
this
week
c,
plus
plus
the
metric
sdk
alpha
release,
milestone
is
85,
complete
still
targeting
may
13th
fantastic
help
is
required
for
logging
sdk
to
make
a
compliant
specs
ruby,
nothing
new,
still
working
on
metrics
and
the
contrib
repo
has
been
split,
so
they're
doing
some
refactoring.
For
that
collector
planning
to
release
point
five:
zero
point
zero
this
week,
that
was
that
represent
the
p
data
rc1,
that's
a
big
milestone
and
rust
preparing
the
0.18
release.
A
Okay
first
topic
is
carter,
requested
communica
creation
of
a
community
demo.
Sig
first
meeting
is
going
to
be
may
2nd
or
9th
working
through
some
setup
steps.
Looking
for
more
contributors
carter,
you
want
to
speak
more
to
this.
F
A
All
right
next
up
is
the
hotel
community
day
who
wants
to
speak
to
this
like
daniel.
G
Yeah
quickly,
I
don't
have
much
to
say
about
it.
I
already
talked
about
it
last
week
at
the
maintainer
meeting,
but
I
just
wanted
to.
G
Events
like
this
are
important
for
the
the
health
of
the
project
and
the
more
maintainers
we
can
get
there.
The
the
more
successful
the
event
will
be.
You
know
from
from
a
community
standpoint.
This
is
one
of
very
few
times
that
we
really
get
to
to
meet
end
users,
and
things
like
that.
So,
if
you
can
make
it,
you
know
please
at
least.
A
Consider
it-
and
this
is
daniel-
this
is
attached
to
another
linux
foundation,
summit
or
event
or
something
correct.
G
It
is
yeah
yeah,
it's
the
same
week
and
venue
as
open
source
summit
north
america
in
austin
the
week
of
june
20th
to
the
25th.
G
You
do
not
need
to
attend
the
open
source
summit
in
order
to
attend
this
event,
though,
so
you
can
attend
separately
and
even
if
travel
is
not
possible
at
least
attending
virtually
would
be
yeah.
I
don't
know
from
maintainers
standpoints
and
meeting
meeting
end
users,
whether
the
virtual
has
quite
as
much
value
for
that
or
not.
But
you
know
I'm
just
trying
to
encourage
as
much
attendance
by
maintainers
as
possible.
I
understand
that
everybody
can
travel
but
yeah.
That's.
H
All
I
really
had
to
say
about
it:
yeah
be
be
great
to
see
y'all
in
person
I'm
planning
on
going,
but
especially
with
the
pandemic
raging
like
we
just,
I
feel
like
it's
been
forever
since
I've
seen
a
bunch
of,
I
feel.
H
H
Actually,
having
one
so
it'd
be
great
to
see
people
there.
Dan,
I
don't
know,
do
you,
I
don't
see
the
link
to
like
the
lightning
talk
proposal,
stuff.
G
Oh
it's
on
the
website,
so
I
I
added
the
registration
link
if
you
got
yeah.
So
if
you
go
to
like
the
the
landing
page
for
just
click
on
like
the
logo
on
the
top
left
there
uh-huh.
Oh,
I
see
this
page
yeah
there's
a.
H
There's
a
submission
there:
okay,
yeah
so
I'll,
post,
a
link
to
the
forum,
but
yeah,
that's
the
other
thing:
there'll
be
lightning
talks
and
stuff.
If
people
want
to
give
one
feel
free
to
sign
up
for
one
of
those.
G
Anthony
asks:
will
there
be
a
mask
mandate?
Will
they
change
that
two
weeks
out,
I
assume
changing
two
weeks
out
is
a
reference
to
something
else.
A
H
That'll
come
down
to
you,
know
the
city
of
austin,
texas,
probably
and
the
cncf
as
an
organization.
My
my
guess
will
be.
There
will
not
be
a
mask
mandate
unless
there
is
a
new
covet
outbreak
of
some
kind.
Yeah.
I
But
but
I
mean
they
hold,
the
mass
mandate
for
kubecon
eu
and
have
just
know
announced
that
they've
reconsidered,
because
it
was
a
terrible
idea.
G
I
G
If
they're
reconsidering
for
that,
then
this
is
a
cncf
official
event,
so
I
assume
the
same
people
are
making
this
making
the
decisions
for
both
events
and
they're
fairly
close
to
each
other
in
time
there
is
a
vaccination
mandate
for
the
event,
or
at
least
there
was
when
it
was
originally
for
for
open
source
summit
in
general.
I
believe
you
need
to
be
vaccinated
to
get
into
any
of
the
co-located
events
as
well,
though,.
A
G
I'm
not
the
one
that
makes
that
decision.
Unfortunately,
we
will
do
whatever
the
cncf
tells
us
to
do.
B
G
Yeah
I
mean
I
I've
been
to
texas,
also
and
I've
been
to
I've
been
to
austin
and
dallas,
and
I
can
say,
austin
was
significantly
better
than
dallas
from
from
that
perspective,
still
not
amazing,
but
it
was
noticeably
different,
but
that
was
a
year
ago,
yeah.
H
In
general,
in
the
us,
like,
mass
mandates
have
been
dropped
and
even
in
like
portland
oregon,
which
is
a
very
like
mass
hearing.
City
people
are
generally
just
not
wearing
them
anymore,
when
they're
out
in
restaurants
or
at
events,
and
things
like
that.
So
cncf
might
mandate
it
for
the
conference,
but
you
probably
will
not
be
seeing
a
lot
of
mask
requirements
anywhere
else.
Yeah.
H
A
All
right
as
daniel
mentioned,
definitely
recommend
that
people
attend
either
in
person
or
virtually,
and
as
we
mentioned
in
case,
you
missed
it.
You
can
also
submit
the
lightning
talk
using
one
of
these
two
links.
A
H
Sig
health
checks
ted.
Do
you
want
to
kick
this
one
up,
yeah,
funny
timing,
because
I
meant
to
to
bring
this
up
this
week
even
before,
knowing
that
john
and
underage
were
announcing
imminent
retirement,
but
as
part
of
just
in
general,
trying
to
like
systemize
the
health
of
hotel.
H
You
know
maintainers
come
and
maintainers
go
the
the
various
like
health
levels
of
different
cigs
changes
over
time.
We
don't
currently
have
any
like
you
know,
process
for
checking
in
on
the
different
cigs
and
then
as
a
community,
trying
to
to
rally
some
help
if
needed
or
a
process,
for
you
know
reminding
maintainers
to
to
promote
people
within
their
community
to
approvers
and
maintainers.
H
If
they
haven't
thought
about
it
in
a
while
in
general,
you
know
we
want
the
things
to
be
kind
of
self-sufficient,
so
I
just
wanted
to
to
check
in
with
the
maintainer
community
and
see
what
you
all
thought
might
be
useful
on
that
front.
The
idea
I
was
thinking
was
something
simple
like
just
once
a
quarter,
you
know
kind
of
like
do
a
survey
of
the
different
cigs
about
sig
health
for
the
maintainers
to
fill
out
and
then,
as
a
community
try
to
pile
on
where
it's
helpful.
H
But
what
do
people
feel
about
that?
Do?
Maintainers
have
have
thoughts
about
what
what
they'd
like
to
see
from
the
broader
community
here.
J
I
think
that's
a
good
idea
ted.
I
question
how
useful
the
survey
is.
Gonna,
be
sorry
if
I
did
that
delicately
enough.
I
just
like
because
I
you
know,
I
don't.
J
Filling
it
out,
you
know
if
it's
just
the
maintainers,
it
may
just
be
a
subjective
view
of
like
what
they
think
is
the
problem,
which
I
can
tell
you
when
things
get
really
bogged
down.
You
just
think
the
world's
crashing
around
you,
but
I
also
wonder,
like
we
have
cncf
dev
stats.
Can
we
maybe
use
those?
I
know
like
we
start
seeing.
J
Yeah,
I
also
I
mean
for
the
record,
if
you
hand
out
a
survey
I'll
fill
it
out,
I'm
saying
otherwise.
B
D
B
I
think
that
it's
sort
of
like
with
grpc
like
this
is
a
weird
a
weird
example,
but
hear
me
out.
It's
like
there
are
languages
that
grpc
uses
to
that
are
like
known,
good.
First
class
languages
like
go
and
java
pretty
much
similar
to
the
ones
with
open,
telemetry
and
then
there's
second
and
third
class
languages
that
people
don't
pay
as
much
attention
to,
because
they
don't
care
about
as
much,
and
I
think
that
we
need
to
find
a
way
to
like.
H
Yeah
yeah.
No,
I
definitely
agree
with,
like
I
think,
there's
like
two
parts
of
my
proposal
that
are
vague.
One
is
like
what
is
the
the
point
of
a
survey
and
what
should
be
in
it
and
the
other.
Is
you
know
what
what
as
a
community
broader
community?
What
kind
of
things
can
we
actually
do
when
when
a
sig
is
having
trouble?
H
I
think
there's
there's
two
ways:
six
can
have
trouble
from
the
perspective
of
maintainers
and
that's
when
I
say
survey,
it's
just
more
like
making
sure
we're
checking
in
on
one
that
cigs
are
not
understaffed.
Right,
like
there
are
some
cigs
like
like
php,
where
you
know
we
know
it's
just
been.
H
It's
just
been
difficult
to
get
get
php
developers
to
to
work
on
it,
and
but
other
sigs
might
have
been
fine
with
lots
of
maintainers
and
approvers,
but
people
have
have
moved
on
to
other
projects
or
whatever
and
now
actually
javascript
or
some
other
sig
is
in
a
place
where
there's
there's
only
one
or
two
maintainers
and
they're.
You
know
concerned
that
they
might
be
be
dropping
to
to
0.5
maintainers
soon
and
just
making
sure
that
we
are.
H
We
aren't
just
like
just
hanging
around
waiting
for
maintainers
to
raise
their
hand
and
say
they're
in
that
situation.
You
know
how
can
we
like
proactively
as
a
community
notice
that
that
that's
going
on
so
I
was
thinking
survey,
there's
a
better
way
to
to
do
that.
I'm
definitely
all
ears
and
then
the
the
other
thing
is
just
if
there's
like
conflict
and
strife
and
human
emotion
going
on.
H
You
know
like
open
source
like
like,
we
all
generally
like
working
on
open
source,
because
we
like
the
camaraderie
that
comes
with
it,
but
open
source
often
also
comes
with
drama,
and
if
there
is
like
drama
going
on
or
there's
something,
that's
just
making
it
emotionally
or
mentally
difficult
to
to
to
work
in
a
group.
H
The
degree
to
which,
like
the
broader
community,
can
help
with
that
either
the
tc,
the
gc,
the
cncf.
You
know
other
other
sig
members
just
making
sure
there's
we're
at
least
reminding
people
that
there's
channels
they
can.
You
know
places
they
can
go
to
to
raise
those
concerns
if
they're
happening
so
survey
might
not
be
the
the
correct
solution
there
and
quarterly
might
not
be
the
right
tempo,
but
those
are
the
the
two
things
that
was
like
two
warning
indicators.
I
was
thinking
about
trying
to
to
to
get
some
advanced
warning
on.
G
Yeah,
I
think
we
have
two
separate
problems.
One
is
identifying
which
segs
need
help
and
one
is
figuring
out
how
to
actually
bring
that
help
to
bear
yeah.
They
require
two
very
different
solutions.
Both
of
them
are
are
difficult
in
different
ways.
Yep,
I
def.
I
think
that
this
solves
one
of
those
things
or
attempts
to
solve
one
of
those
things.
It's
not
even
not
even
attempting
to
solve
the
second
one,
but
you
can't
solve
the
second
one
until
you
have
a
firm
grasp
on
the
first.
H
Yeah
yeah
exactly
I
feel
like
we,
we
have
like
this
meeting
and
we
might
check
in
with
people
in
this
meeting
or
people
might
raise
their
hands
and
say:
hey.
You
know
we're
losing
numbers,
but
it
would
be
great
to
have
have
have
like
a
backstop
to
that
where
we're
not
just
just
waiting
for
maintainers
to
proactively.
H
Like
start
start
organizing
that
stuff
themselves,
you
know
what
some
cadence,
where
like
as
a
community,
we
kind
of
take
stock
of
how
things
are
going
and
what
would
be
the
the
best
way
to
do
that,
but
you're
right
figuring
out
what
to
do
in
some
cases
in
some
languages.
There's
the
enough
organizational
interest
in
open
telemetry
from
organizations
that
have
enough
programmers
who
program
in
those
language
that
it's
like
feasible
to
just
kind
of
do
a
call
to
action
and
then
maybe
get
get
some
more
people
cycled
onto
the
project.
H
But
then
we
have
other
languages
like
php,
where,
like
that's
not
the
case,
and
actually
we
have
to
to
go
more
to
like
the
language
community
and
the
end
user
community
to
find
find
maintainers,
which
is
where
it's.
It's
honestly.
H
Just
a
lot
harder,
because
it's
not
as
easy
to
to
try
to
basically
language
communities
where
me
and
other
people
don't
have
access
to
to
pms
and
ems
that
we
can
bug
and
try
to
like
ask
nicely
if
you
could
literally
like
pay
someone
to
like
come
work
on
this
thing
that
then
it's
a
lot
harder
and
the
tools
we
have
are
more
limited.
A
So
I
have
a
question,
and
probably
starting
with
john
because
he's
departing
and
has
the
opportunity
to
be
most
honest,
like
like
john,
what
as
a
maintainer,
what
what
are
the
biggest
challenges
that
you
face,
like
my
my
assumption,
and
perhaps
it's
wrong,
and
please
tell
me
if
it
is-
is
that
across
most
of
the
sigs,
the
biggest
challenge
I
think
maintainers
have
is,
is
we
want
more
contributors
and
more
maintainers
right,
and
we
just
it's
a
we
want
more
people
to
produce
more
throughput.
A
E
Thanks
for
putting
me
on
the
spot,
sorry,
it's
a
no
it's
a
difficult
question.
I
would
say
that
the
thing
that
we've
needed
the
most
in
java
and
we've
actually
had
a
significant
amount
of
it.
It's
just
people
willing
to
put
in,
like
so
the
core
libraries
in
java.
When
you
talk
when
you
take
into
account
metrics,
especially,
I
have
a
lot
of
inherent
complexity
and
a
lot
of
it's
a
it's
a
complex
piece
of
code,
and
we
really
need
people
who-
and
I-
and
these
are
not
just
kind
of
random
people.
E
What
we've
tended
to
get
when
we've
tried
to
recruit
new
approvers
is
people
who
are
a
little
bit
just
more
cursory
and
kind
of
given
a
once-over
and
get
a
rubber
stamp,
and
when
we're
talking
about
something
like
the
core
java
libraries,
which
are
I
mean
java-
is
for
better
for
ill,
probably
almost
certainly
the
most
common
language
in
the
stroke,
information
and
the
most
high
profile
has
the
most
users
has
the
most
have
the
most
usage.
E
I
think
and
getting
it
right
and
getting
it
right
in
a
very
careful
and
deliberate
manner
is
extremely
important
and
I
think
really
it's
the
hard
part
and
we've
been
extremely
lucky
so
far
with
the
maintainers
we've
had
with
honorary
me
and
jack
and
bonnie
before
that,
to
have
people
who
care
very
deeply
about
the
quality
of
the
code
at
a
very,
very
micro
level,
as
well
as
the
macro
level,
and
it's
really
hard
to
find
people.
E
E
So
I
would
say
for
java
at
least
that's
where
the
toughest
thing
was,
and
actually
what
I'm
most
worried
about
is
that
it's
really
really
hard
to
find
those
people,
and
it
does
require
a
tremendous
amount
of
time
and
energy
to
do
that.
Work.
E
It's
not
just
something.
I
mean.
I
think
that
now
that
anurag
and
I
have
been
doing
it
for
so
long-
we
can
be
a
little
bit
more
like
we
can
do
it
without
a
huge
amount
of
energy,
because
we
know
the
code
base
really
well,
but
for
people
who
are
coming
in
who
don't
know
it,
it's
going
to
take
a
long
time
to
get
to
know
this
code
base
as
intimately
as
really
isn't
it
to
be
a
maintainer
and
maintain
the
quality.
The
current
quality.
G
I
think,
at
least
in
javascript.
Our
struggles
are
very
similar
to
to
what
john
mentioned
it's
difficult
to
find
people
that
really
want
to
like
extremely
deeply
review
code,
especially
when
it's
in
an
area
that
they
don't
view
as
their
area
of
expertise
like
we're
working
on
metrics,
we
got
a
bunch
of
people
that
are
just
like.
I
haven't
been
working
on
metrics.
I
don't
really
know
that
much
about
it
and
they're
less
likely
to
review
those
pr's,
and
then
they
just
sit
for
a
long
time.
B
G
G
There
are
various
ways
that
we
can
do
that
in
terms
of
putting
logos
on
things
is
an
obvious
way
to
do
it,
but
there's
there's
probably
other
ways
to
to
just
to
incentivize
a
lot
a
company
that
says
you
know
we
don't
care
that
much
about
php
as
a
company,
but
you
know
maybe
we
care
about
this
incentive
provided
by
the
project
that
we
can,
that
we
can
get
if
if
we
dedicate
php
engineers
anyways,
but
that's
probably
more
of
a
gc
topic.
J
Note,
though,
I
think
I
think
that's
a
great
idea,
but
also
remember
that
we
can
do
a
good
job,
facilitating
that.
I
know
of
a
few
examples
where
we've
already
done
this,
where
we
had
people
come
to
the
project
that
were
not
getting
paid
and
just
really
wanted
like
enjoyed
the
project
and
through
the
power
of
hotel,
they
found
a
job
that
could
pay
them
to
do
that.
J
J
And
then
I
think,
cultivating
those
you
know,
non-paid
hotel
contributors
and
connecting
them,
I
think,
is
something
that
we
should
really
try
to
focus
on
as
well,
especially
for
that's
a
really.
A
J
No,
in
fact
somebody
just
asked
in
slack
recently,
if
there's
even
a
slack
channel
for
it
and
there
isn't,
but
a
jobs
board's
a
great
idea.
Yeah.
J
Channels,
usually
just
they
become
really
stale
yeah.
A
If
we
have
a
list
of
job
postings
and
things,
it
shows
people
who
are
maybe
partially
involved
in
the
community,
but
are
not
in
a
position
right
now
where
they
can
be
fully
devoted
to
it
that
there's
there
are
actually
like
opportunities
out
there,
where
they
can
dedicate
themselves
to
hotel
and
have
a
career,
doing
it.
D
Yeah,
I
feel
at
least
in
the
in
the
python
side.
The
instrumentations
are
something
that
grows
very
quickly
and
each
instrumentation
kind
of
requires
someone
to
maintain
them
separately.
Who
knows
about
the
details
of
the
library?
That's
been
instrumented
and
that's
a
particularly
hard
to
find
you
know
people
who
take
code
ownership
of
those
instrumentations,
since
there
are
so
many
of
them.
J
Yeah,
that's
a
good
point,
diego.
I
know
that
you're
not
alone
go
has
a
very
similar
issue.
In
fact,
we've
had
to
just
start
turning
away
contribut,
you
know
request
because
we
don't
know
the
time
or
the
effort
from
the
community.
J
Yet
you
know
our
goal
is
eventually
to
have
that,
but
I
think
that's
also
something
to
keep
in
mind
that,
like
yeah,
the
amount
of
work
is
really
important
to
scope,
but
I
also
think
that
it's
really
a
good
thing
to
think
ask
about
perspective
from
the
maintainer
community.
You
know
we
in
the
go
media.
I
don't
know
if
it's
possible
for
everyone,
we'd
really
try
to
ask
anyone.
J
That's
asking
to
submit
interpretation
effectively
natively
in
the
library
that
they're
trying
to
submit
it
for,
and
I
think
that
helps
in
multiple
ways.
One
is
that
it
gets
the
project
out
there
in
a
more
broader
scope
and
it's
free
pr.
You
know
I
know
in
the
go
say
we
have
contributions
to
kubernetes
and
std
already
like
in
the
wilds
and
a
lot
of
other
orms,
and
it's
like
every
time.
Somebody
sees
that
in
the
wild
they
go
what's
open.
J
Telemetry
and
how
can
this
benefit
me
and
all
of
a
sudden,
you
have
a
new
convert,
so
you
know
I
think,
if
there's
some
real
power
and
I
think,
pushing
back
and
asking
the
community
to
spread
it.
You
know
further
than
just
the
community's
boundaries
here
in
the
github
board,
but
I
agree
like
at
some
level,
then
you
have,
you
know,
10
different
options
for
how
to
solve
the
same
problem
and
you
want
to
unified.
So
then
you
need
somebody
internal
to
the
project
to
unify
like
the
canonical
source.
H
Just
just
as
a
aside
with
the
instrumentation
sigs
there's
been
more
interest
developing
release
more
people
showing
up
who
are
interested
in
instrumentation,
like
I
don't
think
we
have
enough
people
yet
to
maintain
all
the
contribs
that
we
have
everywhere,
but
I
do
think
we'll
have
enough
to
help
build
some
more
tooling
in
different
languages.
That'll
at
least
make
maintaining
those
libraries
a
little
bit
easier
but
yeah.
I
agree.
H
The
the
contribute
is
like
kind
of
an
unsolved
mystery
at
this
moment,
because
I
think
finding
consistent
finding
people
to
contribute
to
those
things
is
a
lot
easier
than
finding
people
who
want
to
maintain
those
things
over
time.
That
they're
not
nearly
as
interesting
as
maintaining
something
like
the
sdk.
H
Sorry
not
that
java
agent,
that
that
that
stuff
is
cool
a
little
bit
a
little.
E
E
Even
if
it's
like,
hey,
you're,
you're,
asking
a
question
in
the
wrong
channel:
here's
where
you
should
go
like
we
just
need
people
everyone
to
kind
of
more
people.
I
would
say
to
monitor
the
public
channels
and
and
at
least
make
sure
that
people
know
that
people
are
listening,
because
I
definitely
feel
like
people
tend
to
ask
questions.
A
I
guess
the
next
step
is
then
now
that
we've
identified
these
challenges
is
is
determining
how
to
fix
them.
Some
of
these
are
a
bit
challenging
because
there's
a
pure
open
source
project
right.
We
can't
just
snap
our
fingers
and
make
people
appear.
However,
many
of
us
are
also
positioned
at
the
companies
that
contribute
to
this
project.
So
we
can.
We
have
some
influence
at
least
over
over
this,
but
it's
it's
really
what
I,
what
I'm
seeing
is
kind
of
what
I
had
suspected
well,
not
even
suspected
known,
was
it's
just.
We.
H
Yeah,
I
also
wonder
I
mean
maybe
this
is
a
fool's
hope,
but
I
have
had
a
a
feeling
that
we
have.
H
The
core
community
has
really
had
to
put
a
lot
of
cycles
into
building
these
core
implementations
of
tracing
metrics
and
logs,
and
I
kind
of
I've
had
some
hope
that,
once
metrics
and
logs
are
in
a
stable
place,
there
will
that
will
free,
maintainers
up,
and
it
won't
feel
as
burdensome
to
to
kind
of
look
at
some
of
these.
These
other
issues
we
have
lying
around.
H
I
don't
I
don't
know
if
that's
true,
it
could
very
well
be
that
we're
just
going
to
keep
on
thinking
of
new
things.
We
want
to
add
to
open,
telemetry
and
being
an
sdk
maintainer
means.
You
know
you
always
have
your
hands
full
with
that
stuff,
but
I.
H
A
A
You
know,
we've
discussed
like
profiling
and
other
things
and
I'm
sure
we
will
add
other
types
of
signals
over
time,
but
I
doubt
it's
going
to
be
a
break
next
speed,
or
at
least
at
the
same,
like
amount
of
things
we're
trying
to
jam
in
while
building
and
defining
the
project
at
the
same
time,
so
I
think
I
think
you're
right
ted
like
there
will
be-
I
guess
more
time
in
a
sense
for
maintainers
to
maybe
focus
on,
integrations
and
and
and
other
aspects
beyond,
just
like
develop
these
core
features
across
the
whole
sort
of
suite
of
open
telemetry.
H
Yeah,
at
least
that's
my
hope,
is
we'll
be
able
to
maybe
take
a
more
we'll,
have
the
bandwidth
to
kind
of
take
a
more
systematic
approach
to
to
tackling
some
of
these
other
issues.
Once
a
good
chunk
of
the
maintainers
feel
like
they
aren't
yeah
just
trying
to
to
jam
out
these
super
complicated
implementations
like
tracing
and
metrics,
probably
the
most
complicated
things
we're
gonna
have
to
build
here
for
open
telemetry.
So
this
that's
that's
kind
of
my
hope,
so
it'll
feel
a
little
different
once
those
are
those
are
at
the
door.
A
Okay,
all
right
so
takeaways
from
this,
I
think,
are
a
we
need
to
continue
to
try
and
recruit
more
people
into
the
community,
and
that's
that's
for
all
of
us
and
b.
I
know
it's
not
like
the
biggest
action
here,
but
I'm
just
looking
for
concrete,
like
tasks
is
some
kind
of
jobs
board
or
something
for
the
community
would
be
really
powerful
and
tyler
you
mentioned
like
you
know
we
could
have
a
slack
channel,
but
it
probably
I
it's
slack
is
pretty
ephemeral
right
like
it's
the
I
don't
know.
A
J
I've
seen
it
in
like
the
the
main,
go
slack
space
and
it's
just
it's
a
stream.
A
Yeah,
I
wonder,
could
we
just
create
like
a
github
page
under
the
community
page?
Maybe
the
people
can
just
put
prs
on.
Would
that
would
that
be
sufficient?
Do
we
think,
like
I,
I
don't
know
if
there's
really
a
route
to
go
down
like
a
formal
jobs
board
for
hotel,
like
that,
might
be
kind
of
complicated,
but
like
would
a
github
page,
be
a
good
first
step
in
this.
H
Yeah,
exactly
okay
I'll
try
to
remember
to
bring
this
up
with
the
com
sig
for
the
website.
Also.
H
A
H
The
website
there's
a
community
page
but
there's
also
github,
has
added
a
feature
where
now
you
can
make
kind
of
like
a
home
page
for
your
organization.
H
Place
where
I
think
we
could
add
just
some
more
like
a
directory,
that's
a
little
more
like
you
know.
Are
you
looking
to
help
out
go
here?
Are
you
looking
for
this?
You
know:
go
there
so
yeah
those
those
things
might
might
help
funnel
people
into
the
right
place.
At
least.
G
L
I
was
just
going
to
add
to
the
jobs
board,
make
sure
that
there's
some
process
for
making
sure
that
the
posts
are
updated
jobs
boards
tend
to
age
out
after
some
time.
C
H
H
Are
still
active
yeah,
that's
a
really
good
point
right,
maybe
that
that
can
just
be
part
of
this.
This
process
that
I'm
trying
to
put
together,
which
is
just
what
what
are
the
things
we
need
to
have
like
like
an
alarm
that
goes
off
at
some
quarterly
or
monthly
schedule
with
like
a
checklist
stuff,
is
like
a
community.
We
need
to
to
do
that's
helpful
and
not
really
annoying
to
the
maintainers.
A
C
Yeah,
that's
correct.
I
think
that
it's
good
to
have
this
and
I
will
probably
keep
it
for
a
few
weeks
going
forward.
I
remember
that,
as
mentioned
two
meetings
ago,
that
a
lot
of
people
take
long
holidays
so
yeah
to
prevent
blocking
others.
Probably
we
can
do
proper
planning
and
I'm
also
adding
this
because
I'm
myself
considering
taking
at
least
one
month
off
during
summer,
so
I
will
be
posting
as
soon
as
I.
As
I
know,
nice
gonna
go
anywhere,
exciting
or
stay
home.