►
From YouTube: 2022-09-08 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
B
Yeah
no
worries
no
worries.
I
think
philip
also
said
that
he
might
be
joining
but
still
eating
some
lunch.
So
yeah
give
everybody
a
few
minutes
to
to
come
in
and
then
then
we
can
get
started.
C
A
B
B
B
Let
me
see
share
my
screen.
Just
give
me
a
second.
B
B
Okay,
anyways,
I
think
if
anybody
else
can
share
the
screen
with
the
notes,
then
we
can
do
that,
but
in
the
meantime
I
can
also
just
open
it
up
or
everybody
can
open
it
up.
Philip,
should
we
just
skip
your
topic
for
for
the
first
few
minutes.
D
Okay,
I'll
try
to
speak,
and
then
you
will
see
if
it's
too
distractingly
terrible
super
high
level
thing
that's
going
on
is
so
kubecon
north
america
is
a
thing
that's
happening
in
october.
D
As
we
all
know,
one
of
the
core
problems
is,
there
is
a
cncf
event
called
open
observability
day
that
has
very
little
to
do
with
rhythmic
industry.
There
is
no
open,
celebrity
focused
event
that
has
anything
that
is
a
part
of
cncf
at
all.
So
honeycomb
has
decided
to
buy
up
an
event,
space
nearby
and
say.
C
D
Open
telemetry
community
day
version
two
here
you
go
and
we're
just
paying
for
it
and
then
a
couple
of
other
people
who
work
for
other
vendors
here
are,
like
you
know,
happy
to
pitch
in
as
well,
and
it's
gonna
be
run
on
either
the
monday
or
the
tuesday
of
the
week.
A
I
thought
it
was
going
to
be
so
sorry
the
interrupt
built
just
I
thought
it
was
going
to
be
the
tuesday,
so
people
could
go
to
both
if
they
wanted.
D
Right
right,
yeah,
okay,
yeah,
it's
it's
tuesday,
so
we're
doing
it
just
to
make
sure
we
don't
overlap
too
much
with
relevant
things
that
are
happening.
D
So
we
want
to
get
people
who
are
end
users
of
open
telemetry
and
people
in
the
community
and
all
that
stuff,
like
you
know,
attending
it
is
it's
a
vendor-neutral
thing
like,
even
though
my
employer
is
fronting
most
of
the
costs
right
now
like
it's,
not
a
honeycomb
thing.
There's
no
like
the
intent
is
that
we
have
people
from
the
community
like
go
up.
Give
one
or
two
talks:
do
breakout
sessions
like
unconference
style,
create
your
own
things
and
learn
from
one
another.
D
D
We
should
probably
have
something
on
the
website
about
this
and
promote
it
through
our
means
of
promotion.
I'm
happy
to
take
the
baton
on
getting
things
written
up,
getting
things
so
that
they're
they're
on
the
website.
We
have
like
a
banner
and
like
a
blog
post
with
like
details
and
all
that
cool
stuff
that
can,
I
think,
all
be
figured
out
asynchronously.
But
I
just
want
to
make
sure
that
everybody
here
sort
of
thinks
that
that
is
like
a
good
thing
that
we
can
do.
B
I
I
think
we
should
be
doing
it.
I
think
austin
was
also
all
in
so
I
mean
since
he's
doing
more
and
more
of
this
community
manager,
stuff,
probably
yeah.
A
Yeah
and
I'm
I
just
saw
that
ted
and
some
of
the
other
maintainers.
A
And
from
the
crowdstrike
jumio
side,
we'll
have
people
on
site
to
help
with
logistics
and
also
let
us
know,
if
there's
some
financial
help
we
can
provide
share.
The
word.
D
Okay,
okay,
cool
yeah.
B
I
think
it
would
be
good
if
you,
if
you
can
share
some
details
like
how
can
other
vendors
help
in
or
send
people
or
whatnot,
so
that
does
not
have
to
be
on
that
on
the
page,
but
maybe
in
the
in
the
hotel,
comps
channel.
So
everybody
of
us
can
poke
around
and
ask
like
hey:
do
we
have
budget,
or
can
we
send
one
or
two
people
to
yeah
lead
some
some
of
those
activities
and
then
something
like
that?
Yeah.
B
D
Okay,
I'll
take
point
on
that.
That's
the
only
topic
that
I
had.
B
Okay,
instead,
I
can
unfortunately
not
share
my
screen
because
I
have
not
ever
given
that
permission
to
sue
anyways
there's
one
ticket,
just
that
came
up
today
from
I
think
one
of
the
maintainers
from
the
c
plus
plastic
mark.
He
said
like
hey.
Could
we
have
some
labels
for
each
and
every
language
sig?
B
B
So
I
think
that's
a
good
idea,
but
I
wanted
just
to
quickly
check
with
you
if
this
is
something
we
should
implement
so
in
the
in
the
issues
of
the
website,
of
the
blog
that
if
we
raise
a
ticket
with,
I
don't
know
something
like
the
javascript
community.
We
can
just
tag
that
and
and
then
they
have
an
easier
way
into
into
our
backlog.
Saying,
like
hey,
show
me
everything
for
my
my
language.
B
B
Awesome,
let
me
skip
maybe
one
of
the
things,
because
the
other
one
was
a
little
bit
related.
B
B
So
I
was
wondering
if,
if
we,
if
we
take
up
the
the
opportunity
right
now
and
maybe
get
back
to
all
the
six
and
maybe
say
like
hey,
there's
a
few
new
people
now
running
the
blog
and
the
docs
and
here's
how
how
we
can
collaborate
or
because
maybe
it's
also
just
a
friendly
reminder
that
this
exists
and
we
might
need
some
some
level
of
collaboration
right.
B
A
I
haven't
attended,
but
it's
on
the
calendar.
So
if
anyone
wants
to
attend
it
should
be
easy
to
join.
B
Okay,
yeah,
I
should
be
able
to
make
it
yeah.
I
should
have
time
as
well,
because
actually
I
plan
to
go
on
pto
on
monday,
but
change
plans
a
little
bit,
so
I
have
a
fairly
free
calendar
now
on
monday,
don't
tell
anybody
awesome
and
the
last
thing
was
a
little
bit
more
around
the
blog.
B
So
we
had
this
one
blog
post
around
kafka,
clients
and
whatnot,
and
one
of
the
author
he's
working
on
on
one
of
the
other
cncf
projects.
I
think
it's
called
streamt
or
something
like
that.
So
the
question
is
like
hey:
should
we
follow
up
with
him
and
see
like
can?
Can
we
can
we
get
that
stuff
also
shared
on
on
their
blog
or
yeah?
B
And
the
other
thing
is,
I
don't
know
if
you
saw
that
there
was
also
a
blog
post
on
open
telemetry
on
the
cncf
blog,
and
it's
also
not
clear
to
me
how
I
assume
there's
no
relationship
between
our
blog
and
the
cncf
blog
and
how
much
it
would
make
sense
to
maybe
also
get
in
touch
a
little
bit
with
them
and
see
like
hey.
Should
those
things
go
on
both
places
or
how
are
other,
maybe
cncf,
projects
doing
that.
C
B
Yeah,
yeah
and
and
the
thing
I
was
also
thinking
about-
that's
exactly
the
one
thing:
it's
confusing
people
like
hey.
Why
is
this
published
here,
and
why
is
the
other
thing
published
here
and
at
the
same
time,
on
our
blog,
we
say
like
hey,
we
want
to
have
certain
rules
that
people
stick
to
right
and
at
the
same
time
it
looks
like
the
cncf
block
is,
let's
say,
having
having
a
different
set
of
rules.
So
I
think
it
would
be
good
to
have
some
some
yeah
collaboration
with
them.
B
Has
anybody
reached
out
to
them
in
the
past
or
worked
with
them
or
knows?
Who?
Who
even
is
the
right
point
of
contact?
I
would
not
even
know.
A
Where
to
go
so
there's
two
ways
you
can
do
it,
you
can
have
contact
with
amy.
I
can't
remember
how
to
pronounce
her
last
name:
who's
responsible
for
community
at
cncf
and
also
chris
antschig
to
get
a
blog
posted
or
to
get
a
blog
reposted.
So
if
you
have
a
blog
on
somewhere
else,
then
they
can
do
a
repost.
A
They
have
a
schedule
and
if
you're
representing
an
organization,
that's
a
member,
so
member
specifically
like
a
company
or
something
usually
as
part
of
your
membership,
you
have
a
number
of
blogs
that
you
can
get
onto
their
calendar,
but
as
a
project
under
the
cncf
banner.
I
imagine
it's
different.
We
have
more
freedom.
A
So
why
don't
I,
I
guess
in
slack,
ask
amy
in
our
comms
channel
and
see
where
we
go
from
there
or
do
you
want
an
introduction,
severan
and-
and
you
can
have
the
chat
with
her.
A
B
If
you
already
have
a
have
a
relationship,
I
mean
that
that's
that's,
maybe
a
good
starting
point,
so
I
mean
there's
probably
best
practices
from
from
other
communities.
Right
I
mean
I
mean
at
the
end,
if
they
say
the
cncf
blog,
so,
for
example,
they
are
quite
open,
I
think,
to
even
have
blog
posts
around
vendor-specific
stuff
right.
So
if
any
of
our
of
our
company
says
like
hey,
we
post
something
with
something
specific
we
are
doing.
B
Then
I
saw
this
happening
more
often
on
the
cncf
blog
and
I
just
want
to
understand
like
okay,
how
how
is
this
working
between
the
one
and
the
other
blog
and
whatnot
so
yeah?
If
you
can
ping
her,
and
maybe
we
can
see
how
the
conversation
goes
from
there.
B
A
I
know
the
last
time
we
had
an
item
on
the
agenda
was
updating
the
status
page
and
I
know
it
because
I
took
that
issue
and
that's,
I
believe,
being
closed.
I
think,
what's
his
name,
patrice
therese,
thank
you
has
been
managing
those
those
issues
in
the
repo.
I
I
don't
know
if
there
are
other
things
we
want
to
add
or
changes
that
that
this
group
should
discuss
that
will
have
wider
reaching
impact.
C
I
was,
I
was
gonna
say
because
I
have
been
like
playing
around
so
last
month.
I
was
playing
around
with
like
just
getting
go,
open,
telemetry
examples
running
and
going
off
of
like
the
open,
telemetry
docs
site,
and
then
I
spent
some
time
doing
the
same
thing
for
python,
and
I've
noticed
I
I
know
like
they're
they're,
two
different
cigs,
but
I've
noticed
there's
like
a
disparity
in
the
documents
like
as
far
as
the
getting
started.
Docs
go.
C
If
I
understand
correctly,
I
think,
like
the
documentation
for
the
getting
started
is,
is
like
on
the
like
python
and
go
site,
sorry
python
and
go
repos
respectively,
and
then
they
get
they
show
up
on
on
the
otoldoc
site.
So
I
think
it
would
be
nice
to
have
like
a
a
streamlined
experience
for
the
getting
started
doc.
So
what's
what's
the
best
way
to
go
about
that.
B
A
B
I
mean,
let
me
see
if
we
can,
if
we
can.
C
B
Know
maybe
maybe
sometimes
last
year
or
something
like
that
that
we
discussed
this
there's
the
964
getting
provide
a
uniform
experience
for
a
collector
in
all
language
six
and
there
we
kind
of
discussed
this
but
yeah.
I
probably
got
distracted
from
that.
964.
D
So
we
have
a
uniform,
getting
started
experience
now
with
dotnet
and
python,
hopefully
javascript
at
some
point
when
I
get
around
to
it.
I
also
before
request
out
on
the
the
go
repo.
The
challenge
there
is
is
actually
python
is
a
part
of
our
docs.
So
it's
really
easy
go
is
not
because
it's
part
of
the
go
repo,
okay.
D
Okay,
I
see
I
have
a
pull
request
out
with
17
commits
and
86
comments
on
it
that
I
need
to
address
some
of,
but
the
intent
is
that
it
follows
the
same
pattern
as
python.net,
and
then
we
want
to
do
the
same
thing
for
javascript
java
is
a
little
different
deal
with
that.
One
later,
I
guess
very,
very
much
very
much
work
in
progress
is
what
I'm
saying
like
there's
some
stuff.
That's.
D
I
would
say
that
if
you
want
to
contribute
to
that
right
now,
since
the
go,
one
is
like
I've
done
most
of
the
work
for
it.
I
should
probably
just
finish
it
off,
but
javascript
needs
needs
this
again
and
it
also
needs
two
there's
one
for
node
and
then
one
for
browser
and
browser
js
is
is
also
a
little
different
and
like
clearly
with
node.
You
don't
actually
require
a
collector
to
be
able
to
get
started,
but
with
browser
you
actually
will,
especially
if
you
want
to
egress
to
any
endpoint.
D
That
requires
an
api
key,
because
you
don't
want
to
expose
the
api
key
in
browsers
like
end
users
themselves.
So
like
it's
almost
it's
like
practically
a
requirement
to
use
a
collector
with
browser
dance
today,
and
that
makes
it
work
yeah.
It
makes
it
more
complicated
and
set
up
in
the
first
place.
Okay,
so
it's
kind
of,
but
like
I
think,
certainly
on
the
node
one.
We
could
basically
follow
the
same
pattern
that
we
have
with
python.net.
B
C
Oh,
I
was
gonna
say
I
I
don't
have
any
knowledge
of
javascript,
so
I
cannot
help
with
that
one.
But
I
could
possibly
look
into
the
java
one
as
I'll
be
just
educating
myself
on
the
javascript
things
soon.
B
So
the
java
one
is
is
actually
also
in
a
really
good
state.
Okay,
but
I
think
it's
it's
different
in
a
lot
of
ways
from
let's
say,
for
example,
yeah
as
philip
said,
go
and
tighten
right.
B
B
B
C
B
964
what
we
tried
there
is
coming
up
with
this.
Let's
say
structure,
so
I'm
not
sure
how
similar
or
close
this
these
are
today
or
how
much
this
is
still
making
sense.
So
I'm
a
big
fan
of
that
still
but
yeah.
Let's,
let's
see
I
mean
if,
if
this
is
something
we
could
could
drive
a
little
bit,
I
I
would
be
happy
to
see
this
going.
Yeah.
C
Okay,
cool
and
the
other
thing
on
on
a
similar
vein
like
I
was
I
I
got
started
with
the
like
when
when
I
was
doing
the
python,
I
got
started
with
the
auto
instrumentation,
which
is
like
absolutely
magical,
and
then
I've
been
like
mucking
around
with
the
manual
instrumentation
for
python,
which,
on
the
most
part,
got
it
working,
but
then
I'm
having
trace
propagation
issues,
and
then
I
was
looking
at
the
hotel
docks
on
that
and
I've
been
spinning
my
wheels
for
a
few
days.
C
I've
had
to
reach
out
to
to
a
few
people
to
ask
for
help.
They
weren't
super
straightforward,
because
I
I
felt
like
the
and
I
think
I
can
show
you
in
the
python
one
book,
which
pages.
C
On
the,
if
you
go
to
instrumentation
python,
it's
in
the
cookbook
section.
Do
you
want
me
to
share
my
screen?
I
can
do
that.
B
C
Yeah,
so
it's
this
section
here
where
they're
explaining
is
explaining
how
you
inject
the
inject,
the
carrier
for
the
trace
propagation,
and
this
is
like
an
entire
code
block,
but
it's
not
actually
really
a
sample
application.
It's
like
pieces
of
programs
and
like,
for
example,
this
line
here
where
it's
like.
Oh,
this
is
what
your
carry
is
supposed
to
look
like
and
you
can
update
the
contacts
you
can
do
this
extract
and
then
set
the
carrier.
C
But,
like
then
my
question
was
well
okay
great,
but
where
did
that
here
come
from
because
this
value
is
hard
coded
and
obviously
it's
not
going
to
be
the
same
value
every
time.
So
I
found
that
confusing.
I
don't
mind
clarifying
that,
given
that
I've
got
like
it's
pretty
fresh
in
my
mind,
I
think
I've
almost
got
it
figured
out,
but
I
wanted
to
point
it
out
and
I
can
give
myself
a
task
to
to
update
that
section
of
the
documentation
because
for
me,
like
it,
hasn't
been
super
clear.
D
C
So
I
was
playing
around
actually
I
I
grabbed
the
the
python
example
from
the
honeycomb
docs,
where
it
was
the
the
manual
instrumentation
and
then
I
had
a
little
client
program
that
called
they
called
the
server
and
basically,
what
I
was
finding
is
okay,
I
got
the
trace
for
the
client
and
the
server,
but
the
the
traces
were
disjointed
and,
and
it
didn't
utilize,
the
auto
instrumentation
in
in
this
case
I
wasn't
using
the
auto
instrumentation,
so
I
wasn't
using
open,
telemetry
dash
instrument
when,
when
writing,
when
running
the
python
code
and
in
so
in
that
case,
like
you
end
up
with
with
disjointed
traces
so
as
a
challenge,
slash
torture
to
myself,
I
was
trying
to
like
understand
well.
D
It
is,
it
is,
and
so
this
this
should
probably
be
a
subsection
in
the
manual
instrumentation
part
of
the
document,
and
then
what
I
should
probably
do
is
sort
of
clarify
that,
like
hey,
if
you're,
not
using
like
request,
instrumentation
or
the
auto
instrumentation
binary-
or
you
know
something
where
like
it,
will
actually
propagate
for
you,
then
if
you
do
want
to
connect
traces
together
yourself,
you're
gonna
have
to
do
this
work
and
I
think
I
think
javascript.
B
B
Don't
you
use
the
distro
for
automatic,
not
necessarily
and
the
point
I'm
trying
to
make
it
sometimes
I
think
I
raised
a
ticket
for
that
also.
B
If
someone
comes
especially
from
an
apm
vendor
like
in
my
case
that
dynamics
or
new
relic
or
whatever
dyna
trace,
they
always
look
for
something
like
an
agent
and,
of
course
they
find
it
with
java,
but
they
don't
find
it
for
the
other
languages.
So
it
would
be
good
somewhere
in
the
concept
section
to
at
least
give
them
something
they
should
be
looking
for.
B
So
is
the
word
distro,
or
is
it
automatic
instrumentation
or
is
it
instrumentation
because
we're
not
really
consistent
on
that
that
that's,
I
personally
find
this
a
little
bit
confusing
and
I
think
it
would
be
good
for
for
people
coming
in
to
say
like
hey,
I
I
want
to
have
all
this
auto
magic.
What
is
it,
what
I'm
looking
for,
so
I
typed
agent
in
your
search
and
then
there's
nothing
popping
up,
so
so
what?
What
is
the
thing
I'm
looking
for?
C
B
Yeah
and-
and
they
said
that's
something
we
maybe
should
I
still
discuss
here
or
maybe
bubble
this
up
a
little
bit
and
say
like
hey.
I
don't
know
if
this
has
done
something
worse
to
discuss
in
the
specification
or
in
the
community
and
say
like
hey.
How
are
we
going
to
to
call
those
things?
B
Because
it's
it's
a
little
bit
confusing
and
I
can
figure
out
my
way
right
now,
because
I
mean
I'm
doing
this
for
a
while
now,
but
I'm
always
trying
to
think
from
from
someone
who's
completely
new
to
to
open
telemetry
and
a
bunch
of
those
things
are
terminology
that
that's
not
only
unique
but
but
also
not
not
consistent.
So
that's
that's.
Definitely.
D
I
would
say,
broadly
speaking,
we're
deficient
in
two
ways:
we're
deficient
in
having
the
right
terminology
and
and
also
documentation
for
people
who
do
come
from
an
atm
background
and,
like
maybe
not
have
a
developer
background.
We're
also
deficient
in
developer
audiences
who
get
freaked
out
at
the
idea
of
running
an
agent
or
something
else
in
their
infrastructure,
but
are
perfectly
okay
with
installing
libraries
and
writing
code
and
like
for
those
people.
D
Similarly,
there
is
a
story
around
automatic
instrumentation
via
instrumentation
libraries,
but
it's
also
not
entirely
clear
that,
like
oh,
if
I'm
in
python-
and
I
use
the
request
instrumentation
and
the
flask
instrumentation,
I
get
distributed.
Traces.
D
They
can
eventually
stumble
their
way
into
realizing
that,
but
we
don't
really
make
it
clear
for
either
category
of
person.
B
Yeah
and
I
think
that
it
comes
down
to
the
thing
that
all
those
terms-
agent,
automatic
instrumentation,
instrumentation,
they're,
all
kind
of
overloaded
right
so,
as
you
said,
automatic
instrumentation
for
an
ops
person,
it
means,
like
my
application-
gets
instrumented
automatically,
makes
totally
sense,
but
for
a
developer,
it's
like
hey.
I
used
this
in
that
framework
and
this
indeed
library
and
now
this
is
automatic
instrumentation
for
me.
So
I
think
there's
the
difference
between.
I
don't
know
if
it's
thing
called
application,
automatic,
instrumentation
and
library
automatic
instrumentation.
B
B
I
think
we
also
had
the
idea
at
some
point
and
we
have
maybe
some
entry
points
on
a
kind
of
persona
level
that
we
say
like
if
you're
a
developer.
This
is
what
you're
looking
for,
if
you're
an
ops
person.
This
is
what
you're
looking
for.
I
don't
know
if
this
is
something
we
we
should
also
try
to
to
have
it,
at
least
as
a
landing
page,
or
something
like
that.
B
So
so
let
let's,
let's
make
it
that
way.
I
mean
I'm
not
sure
if
this
makes
sense,
but
right
now,
if
you
go
at
the
open,
telemetry
io
website,
I
see
like
I
see
like
hey,
learn,
more
vision,
star
and
then
get
started,
and
then
it
says
collectorjavago.net
javascript,
the
developer
will
click
there
and
expect
yeah.
I
get
something
from
my
language
right
and
the
developer
and
ops
person
that
just
wants
to
have
an
agent
is
like
okay.
Where
should
I
even
click,
so
they
maybe
click
on
learn
more.
B
So,
if
you
would
now
say
like
on
the
open
telemetry
on
the
on
the
very
very
first
page,
so
even
even
before
that,
if
you
would
here
then
instead
of
get
started,
click
on
on
those
terms,
maybe
even
click
on
ops,
devs
library,
developer
whatever
and
then
get
something
like
hey.
This
is
how
the
world
looks
like
for
you,
and
this
is
how
the
world
looks
like
for
for
another
person
that
did.
I
said
this.
This
is
just
me.
D
Yeah,
I
think
we'll
have
to
have
a
a
think
through
of
how
to
how
to
orient
that,
because,
like
we
have
a
lot
of
the
docs
already
available
for
this,
it's
just
really
it's
harder
to
understand
how
you
actually
find
what
you're.
Looking
for
here
yeah,
I
think
I
mean
to
be
fair,
like
we
could
probably
have
a
cut
at
trying
to
organize
some
of
that
stuff
at
a
top
level
by
persona.
D
We
clearly
don't
do
that
at
all,
and
you
know.
Are
you
an
operator
or
maybe
some
other
better
word?
Are
you
a
developer
decision
tree
here?
You
go.
B
Yeah
yeah
exactly
and
then
I
mean
we
could
start
with
a
single
page
that
has
all
those
people
and
then
telling
them
if
you're
in
that
role.
Here's
what
you're
looking
for,
if
you're,
that
old,
here's
what
you're
looking
for
and
later
on,
we
could
maybe
even
structure
it
around
that
so
but
yeah,
as
you
said,
like
I
mean
that's,
that's
that's
that's
not
addressed
in
in
any
way,
not
not
even
in
the
words
we
are
using
right.
B
The
question
is:
should
we
so
I
always
like
also
to
to
have
this
things
a
little
bit
async
and
we
have
a
few
of
those
issues
already,
should
we
maybe
have
some
kind
of
label
like
discussion
or
whatever,
where
we
try
to
deep
dive
a
little
bit
into
that
or
I
don't
know
what
what's
a
good
way
for
all
of
you
to
to
to
go
into
that,
because
I
mean
sure
we
can
use
those
hours
here
and
then
maybe
extend
the
time
we
have
to
meet.
B
But
I
don't
know
if
it
makes
sense
to
to
have
a
place
within
the
issues
to
organize
that
or
should
we
have
a
google
docs
for
that
separately?
I'm
not
sure.
What's
there,
what's
the
best
way
for
that.
C
I
think,
maybe
I
almost
say
like
I
don't
want
like
more
slack
channels,
but
I
don't
know
just
a
place
where
we
everything's
either
more
docs,
more
issues
or
more
channels,
but
definitely
some
place
where
we
can
collaborate.
Async.
B
B
A
A
B
So
the
thing
is
the
issue.
The
issue
I
have
with
issues
is
of
course,
especially
if
someone
comes
new
to
the
community
and
says
like
hey,
I
want
to
help
those
people
right
now
they
have
to
go
to
114
open
issues.
I
mean
I
try
to
attack
them
now
with
good,
first
issue,
how
wanted
and
what
not,
but
for
those
more
detailed
discussions,
I'm
not
sure
like
if
they
because
they
get
lost
there.
I
said:
there's
this
one
ticket
like
it's
now,
a
year
old.
B
I
think
it's
still
a
worthwhile
discussion,
but
just
get
completely
lost
there.
So
yeah,
I'm
not
I'm
not
sure.
A
A
A
B
Yeah,
maybe
we
should,
we
should
said,
maybe
stick
to
issues
for
the
time
being
and
maybe
really
work
with
the
label
like
discussion,
so
everybody
can
click
on
that
label
and
then
see
like
haters.
Those
are
these
things.
We
try
to
sort
out
more
from
how
you
would
call
this
conceptual
basis
right
where
we
said
like
hey.
We
want
to
restructure
a
lot
of
things
and
or
we
we
need
to
clarify
something
before
even
doing
any
work,
and
then
they
said
if
we
figure
out
like
it,
it's
not
a
format,
that's
really
helpful.
A
You
know,
maybe
in
the
readme
that
get
involved.
We
should
be
more
explicit,
like
I
know,
there's
this
section
down
here
that
says
contributing,
but
you
have
to
scroll
to
know
it's
there
and
maybe
up
here
we
should
say
hey.
There
are
good.
You
know
issues
that
if
you
want
to
pick
it
up
and
you're
new
they're
tagged
good
first
issues
or
maybe
even
a
link
to
them.
B
Yeah
yeah,
no,
I
mean
restructuring
or
redoing
the
readme.
I
would
not
be.
I
think,
that's
a
good
time
to
do
that,
because
it's
also
grown
a
little
bit.
I
mean
you
see
like
someone
had
it
to
get
involved,
and
I
think
I
just
added
this
recently
that
someone
added
the
adding
something
to
the
regular
street
and
we
recently
extended
a
little
bit
the
rules
around
the
blog.
B
So
the
question
is
like
hey:
should
we
yeah
redo
the
readme
a
little
bit,
and
so,
from
my
point
of
view
I
mean
the
readme
is
mainly
an
entry
point
for
newcomers
right
so
that
they
know
like
hey.
What
is
this
repo
about?
How
can
I
contribute
to
that
and
then
who?
Who
are
the
people
here
so
that
there's
this
list
of
maintainers?
A
B
B
Now
my
batteries
are
empty
on
time.
That's
awesome.
Cool
then
see
you
all
in
two
weeks
and
in
the
meantime,
on
the
slacks
yeah
yeah.
Thank
you.