►
From YouTube: Core Team Meeting 2019-12-04
Description
Core Team Meeting 2019-12-04
B
The
current
status
of
the
request
is
to
add
them
as
a
sub
team
of
dev
tools,
so
with
the
current
status
of
the
pull
request,
I,
don't
think
they
need
anything
special
because
we
add
saw
teams
of
teams
all
the
time.
That's
supposed
to
be
like
low
effort.
I
believe
a
hope
is
to
have
a
top
level,
dockstar
RS
team
and
and
like
made
me
figure
out
how
that
fits
in
with
Krista
IO
and
yet
the
website
it
may
be
like
there
there.
A
D
B
It's
unclear,
if
that's
the
state
that
we
want
to
merge
it
with.
So
what
I'm
trying
to
say
is
that
the
current
state
of
the
pull
request
is
something
we
can
merge
without
an
RFC.
That
said
where
there
was
debate
in
the
threat,
whether
or
not
that
is
what
we
want
in
what
people
seem
to
be
of
gravitating
towards
with
separate
team,
and
it's
unclear
if
that
separate
team
needs
an
RFC
I
kind
of
am
leaning
towards
it
needing
an
RFC
other
people
also
are
but
I'm,
not
sure
so,
like
yeah
I.
C
E
We
have,
but
if
not,
we
need,
we
should
be
saying
what
the
scope
of
the
team
is
like
I,
don't
think
an
RFC
is
such
a
huge
hurdle.
I
mean
I,
think
we
could
create
a
team
and
our
exceedances
we're
making
a
doctor's
team.
But
even
here
there
are
some
questions
right
like
do
they
come
into
the
court
team
or
not,
and
so
on
and
I
can
understand
why
it
seems
like
it's
a
non-trivial
decision.
A
B
Charters
but
really
I
feel
like
everyone
should
have
charters.
Working
groups
have
been
using
charters
because
there
are
the
only
teams
that
have
been
formed
in
the
last,
like
top-level
team
team
organization
and
thingies
that
have
been
formed
in
the
last
few
years,
and
before
that
we
were
never
doing
charters.
C
E
I,
don't
know
how
much
it
matters
really.
It
seems
like
something
where
if
we
did
a
good
job
of
it,
it
could
be
great
of
structuring
our
things
and
thinking
about
this.
But
I
feel
like
we're.
I
have
this
feeling
that
we're
blocking
progress
and
I
don't
like
that,
but
maybe
it's
just
because
there's
an
open
fire
and
that
it
feels
like
something
to.
C
Me
yeah
I,
agree
with
that.
I
think
like
we
do
need
to
think
about
our
team
structure
like
this
just
feels
like
another
thing,
where
things
don't
fit
nicely
into
what
we
have
at
the
moment.
So
for
my
money,
I'd
rather
do
the
lightweight
thing,
which
is
make
them
as
a
sub
team
of
talks
on
our
ass,
with
a
note
that
this
is
one
the
things
that
we
want
to
revisit.
C
E
D
Okay,
I
can
reply
on
the
thread
that
we
feel
that
we
can
merge
this
PR,
as
is
without
a
draft
RFC,
and
then
we
will
consider
whether
an
RFC
or
similar
document
is
necessary
in
the
future
and
sort
of
get
back
to
the
team
at
some
point,
I
think
you
should
then
just
go
ahead
and
merge
it.
Yes,
I
can
get
that
as
well.
E
I
forgot,
where
I
last
had
the
document
read,
but
the
two
things
first
I'm
working
on
a
proposal
that
is
to
encapsulate
the
front
end
of
the
process.
I
think
I
talked
about
that
I
have
a
blog
post
that
I
wanted
to
have
posted
before
this
meeting,
but
things
came
up
and
we're
having
a
meeting
at
the
governance
working
group
in
two
weeks
time
to
talk
about
it,
which
will
be
announced
shortly.
I
have
to
write
the
announcement
so
for
folks
who
might
be
interested
there's
some
discussion
happening
around.
E
F
E
F
When
we
were
discussing
access
control
in
the
government's
working
group,
we
might
we
are
thinking
about
moving
the
community
team
repositories
that
are
still
in
use
under
Ross
Lang,
because
the
reason
we
had
the-
and
this
might
be
something
to
talk-
also
talked
about
with
other
with
other
groups.
The
main
reason
for
having
the
community
team
organization
separate
was
because
we
didn't
automate
access
control.
F
Rust
lag
so
was
hard
to
make
sure
that
everyone
had
consistent
access
to
what
they
needed
access
to
and
to
make
sure
that
people
didn't
have
access
to
what
they
are
haven't
got
access
to.
This
is
now
fixed,
so
we
can
move
them
back
in
to
make
sure
we
have
a
better
overview
who
even
has
access
to
things
that
might
be
considered
or
official.
E
E
B
E
We
kind
of
we
had
a
discussion
last
meeting
about
access
rights
and
came
up
with
the
policy
that
were
no
I
think
right,
eventually
an
RFC
around
it
for
how
to
manage
the
access
rights
to
repos.
But
one
of
the
parts
of
it
was
that
everything
is
a
lot
easier
if
we
have
fewer
github
orgs,
so
we're
trying
to
rein
that
in
we
decided
not
to
for
the
time
being
to
leave
the
domain
working
groups
alone.