►
From YouTube: Working Group: 2021-01-12
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).
B
All
right
so
for
today,
let's
see
we've
got
outstanding
language.
Family
rfcs,
starting
from
the
bottom
we've
got
this
proposal
to
create
a
keto
project,
programming
style
guide.
I
want
to
say
frankie
said
this
was
ready
to
go
and
it
looks
like
both
emily
and
myself
have
approved
this,
so
I
think
it
probably
could
get
merged.
At
this
point.
B
B
The
call,
but
I
do
see
mark,
I
think,
the
question
I
ended
up
asking
on
this.
One
was
whether
or
not
this
actually
needs
to
be
a
separate
repo.
I
think
I
agreed
with
what
emily
was
asking.
A
B
D
So
it's
interfacing
with
the
actual
sources
of
dependencies
so
like.
If
you
ask
it
for
go
versions,
it
actually
reaches
out
to
the
go
like
download
page
and
get
the
versions
from
there.
So
it's
for
fetching
source
code
and
versions
of
available
dependencies,
but
not
the
ones
that
we
built
we'd
have
a
client
for
that.
We
just
put
them
in
or
we
have
the
just
adapt
servers
api
is
that
applying
links?
D
D
A
I
think
I'd
love
in
this
rfc
just
have
like
a
little
bit
more
information
about
this
workflow,
just
because
I
found
it
confusing
to
understand
what
exactly
is
going
on,
because
I
think
last
time
we
talked
about
the
rfc,
I
got
the
impression
that
the
depth
server
was
just
serving
metadata
rather
than
serving
like
the
actual
dependencies
themselves.
Is
that
did
I
understand
that
correctly
or
incorrectly.
D
This
is
basically
just
letting
us
know:
are
there
what
versions
of
go
and
ruby
and
whatever
are
available,
and
where
can
we
download
the
source
code,
so
we
can
compile
it
basically,
every
like
funk.
Every
struct
in
this
library
just
has
a
like
what
method
to
get
all
the
versions
and
the
method
to
get
better
data
for
a
single
version.
C
D
It's,
I
think,
mostly
our
motivation
is
transparency,
like
this
is
source
code
that
we
wrote
in
private
that
we
use
to
you
know,
put
together
the
bike
buttons
that
build
these
things.
So
end.
Users
wouldn't
necessarily
use
this,
but
if
someone
wanted
to
say
create
a
ph
build
pack
for
like
r
or
some
depends,
we
don't
file,
they
could
add
r
to
this
library
and
then
make
it
very
simple
for
us
to
be
able
to
build
our
future.
B
B
This
one
is
a
draft
frankie.
This
is
not
ready,
not
at
all
yeah,
okay
cool.
I
will
skip
over
it
then
moving
on
to
language
specific
rfcs,
there
still
is
just
this
php
one.
I
think
we
talked
about
it
last
week
and
I
don't
believe
anything
has
changed
in
the
week
since
we
did
so
I'll
just
skip
over
that
one.
Unless
someone
objects
not
hearing
any
objections.
B
B
What's
being
outlined
here
is
basically
the
hopes
and
dreams
wishes
for
anything
that
could
possibly
be
worked
on
in
the
paquetto
org
in
in
the
next
year,
and
so
what
we're
looking
for
is
really
you
know
nothing
too
big
or
too
small.
You
know
anything
you
can
possibly
think
of
to
to
have
the
keto
work
on
and
we're
gonna
take
from
that
list
of
things
and
kind
of
organize
a
set
of
themes
for
stuff
that
we're
going
to
be
focused
on
in
2021.
B
Okay,
there's
nothing
left
on
the
agenda.
Does
anyone
have
anything
that
wasn't
on
the
agenda
that
they
want
to
speak
of
now
and
discuss.