►
From YouTube: 2021-04-07 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
A
B
B
C
Hello,
everybody,
I
think,
we're
probably
ready
to
get.
B
C
Sounds
good
what
about
removing
the
the
the
bass
plug-in
and
the
plug-in
loader?
This
thing:
okay
and
you're,
working
on
core
contrib
or
both
just
for
now,
just
core?
Okay,
I
can
do
the
contrib
one!
Then
yeah.
C
Okay,
that
includes
meta
packages
too
right,
you're,
removing
the
old.
C
C
C
Okay,
in
the
meantime,
it's
not
that
big
of
a
deal
because
I
just
ran
it
manually
and
it
was.
It
was
no
real
problem.
E
I
know
that
there
was
the
issue
with
like
that.
That
was
the
second
workflow.
That
actually
does
the
publishing.
Have
you
run
the
first
workflow
that
creates
the
pr
successfully
or
was
there
have
we
not
yet
cause
there?
Was
that
one
problem
that
wasn't
related
to
the
workflow,
but
that
prevented
it.
C
No,
I
was
able
to
use
it.
I
just
fixed
the
issue
and
this
in
a
separate
pr
merged
it
and
then
ran
the
workflow,
so
it
that
one
ran
fine.
E
Okay,
great,
it's
just
a
second
one
cool.
There
were.
C
Two
issues
that
I
found
with
it.
The
first
is
that
the
change
log-
and
this
is
this-
is
not
your
fault.
This
is
a
problem
with
learn
a
change
log.
The
change
log
put
most
of
the
pr's
into
just
some
other
category,
rather
than
properly
tying
them
to
a
specific
package.
C
C
And
everything
else
it
doesn't
see,
so
I
actually
am
working
on
a
pr
against
learn
a
changelog
to
update
that.
But
for
now
I
just
manually
updated
the
change
log
and
then
that
made
me
realize
the
second
issue,
the
second
workflow
when
it
runs
it,
creates
a
release
and
everything.
C
E
Yeah,
I
I
I
that
was
intentional,
because
I
figured
if,
like
an
additional
change
or
feature,
had
been
added,
while
the
release
pr
was
still
open,
then
we'd
want
to
include
that
in
the
change
log
as
well.
So
I
just
decided
it
would
make
sense
to
regenerate
the
change
log
and
yeah.
But
that
being
said,
if
for
now
we
do
not
want
that,
then
I
can
change
that.
C
I
mean
we
probably
want,
whichever
one
was
included
in
the
in
the
actual
changelog
md
file,
to
be
the
one
from
the
release,
because
if
we
merge
additional
pr's
that
are
then
included
in
the
release,
we
already
have
to
go
back
and
update
that
pr
manually
to
fix
the
change
log
like
that
it
doesn't
automatically
update
itself
right.
C
Changeable
writing
happens,
I
updated
manually
and
then
the
one
on
github
was
just
regenerated
right.
So
if
we
had
merged
another
pr,
while
the
release
pr
was
open,
the
changelog.md
would
not
have
been
automatically
updated.
I
would
have
needed
to
manually
update
that
one
anyways
got
it
right:
okay,
yep,
so
that
one
should
probably
just
be
used
as
the
release
change
log.
E
Instead
of
recalling
learn
or
change
instead
of
calling
it
again,
okay
yeah,
I
can
see
it.
I
can
definitely
try
to
do
that.
So
just
copying
over
the
content,
it
makes
sense.
F
C
All
right-
and
I
would
appreciate
if
everybody
could
add
their
name
to
the
attendee
list.
C
Okay,
so
I
think
that's
a
reasonable
summary
of
of
what's
going
on
for
now.
I
just
ran
it
manually.
It
wasn't
that
big
of
a
pain
but
yeah.
It
would
be
nice
if
it
worked.
C
So
for
the
sdk
release
candidate,
I
think
we
are
almost
there.
All
we
need
to
do
now
is
remove
the
old
plug-in
system
and
there
are
a
few
small
things
like
the
the
jaeger
or
not
jaeger.
Specifically,
the
propagator
environment
variable
configuration
that
I
believe
jacob
was
working
on.
C
But
there's
a
couple
of
small
things
like
that
and
then
we'll
be
good
to
release
the
release
candidate
for
the
sdk.
C
At
this
point,
I
need
to
know
if
anybody
has
anything
that
they're
aware
of
that
would
block
the
release
candidate
of
the
sdk,
any
shortcomings
that
we
have.
So
we
currently
have.
C
Beyond
that,
I
am
also
talking
to
the
technical
committee.
I
think
armin
is
going
to
do
a
quick
look
through
our
repository,
both
the
api
and
the
sdk,
to
ensure
that
we're
spec
compliant
before
we
actually
go
to
1.0.
C
C
G
G
C
Yeah,
just
out
of
curiosity,
what
made
you
decide
to
host
them
yourself
rather
than
putting
them
in
the
the
contrib
repo.
A
Hey
so
yeah,
I'm
I'm
michael
also
working
with
with
amir
well.
To
be
honest,
it's
a
bit
relates
to
kind
of
losing
a
bit
of
control
over
the
code,
and
initially
we
just
started.
We
were
kind
of
new
but
like
as
we
progressed
with
that,
we
felt
like
that's
once
we
put
in
the
country
with
losing
control
over
over
the
code.
A
C
Yeah
I
mean
thanks
for
it
looks
like
a
fair
amount
of
work
must
have
gone
into
these.
If
you
know
it
looks
like
what
seven
or
eight
plugins
so
thank
you.
We
appreciate
that.
F
C
I
know
we've
had
a
short
agenda
today.
Is
there
anything
that
anybody
anything
else
anyone
wants
to
bring
up
before
we
call
it,
or
should
we
just
call
it
a
short
meeting
today.
H
Get
one
question:
that's:
why
do
you
know
where
the
the
source
code
or
the
project
of
for
the
semantic
convention
generators?
Because
I
want
to
look
into
something
if
it's
possible,
because
I
I
have
made
a
template
to
generate
the
touchkit
file,
but
the
typical
generator
is
only
generating
like
one
file.
We,
instead
of
one
like
how
we
have
in
our
javascript
project,
where
we
generate
per
cut
per
category.
C
H
Yeah,
so
basically,
I
based
it
on
their
how
they
are
doing
it,
but
they
generate
like
one
big
file
of
all
resource
attributes
and
one
big
file
for
all
the
other
attributes.
But
we
have
like
one
file
for
fast
one
for
messaging
one
for
jobs,
and
things
like
that.
So
just
try
to
find
out
if
that's
built
in
in
the
generator
that
you
just
need
to
corner
it
once
for
each
file.
C
C
C
Generated,
there's
no
reason
to
worry
about
stuff
like
that.
Okay,
so
it's
fine.
If
the
change
needs
to
even
be
backwards
incompatible,
that's
no
real
problem,
we'll
just
update
all
of
our
references.
It'll
be
maybe
a
little
bit
painful
to
do
it
the
first
time,
but
beyond
that
it
should
be
much
easier
to
maintain
when
it's
automatically
generated.
So
I
think
it's
probably
worth
it.
C
Okay,
well,
thank
you,
everybody
for
your
time
and
I'll
talk
to
you
next
week.