►
Description
We discussed how to manage access and permissions to repositories in the rust-lang Github organizations.
B
All
right
cool
all
right.
Well,
hello!
Everyone
welcome
to
the
December,
its
December,
already
December
third
meeting
of
the
rust
governance
working
group.
A
topic
for
this
meeting
is
the
access
policy
for
github
permissions,
but
before
we
dive
into
that,
is
there
anything
else
anyone
wants
to
make
sure
we
discuss
or
that's
on
people's
minds.
A
B
Cool
yeah,
let's
dive
right
in
so
we
began
discussing
the
github
access
policy
and
I,
put
a
link
in
the
discord
channel
I,
which
I
you.
We
need
some
sort
of
policy
for
giving
it
right
access
or
admin
access
to
our
github
works
right
now.
My
understanding
is
it's
very
ad
hoc
and
it'd.
Be
good
to
you
know,
have
some
sort
of
system
in
place
on
this
or
just
just
make
it
a
lot
more
manageable
than
it
currently
is
so
I
thought?
B
Maybe
we
could
I
this
was
months
ago,
but
I
drafted
a
couple
of
ideas
for
a
policy
based
on
the
conversation
and
I'm
gonna
link
directly
to
one
of
them,
putting
it
in
the
discord
forum.
I
think
it's
already
on
that
yep
that
thing.
So,
if
we
scroll
down
now
to
September,
we
have
our
latest
draft
of
this,
and
then
we
there
were
some
questions
that
happened
afterward.
So
what
we
can
do
is
we
can
start
with
the
draft
and
discuss
it.
We
can
discuss
the
questions
that
came
up
in
the
github
issue.
C
Okay,
so
once
is
that
about
everyone
having
a
tree
taxes
that
might
not
be
what
we
actually
would
like
I
think
we
have
a
few
laboratories
on
the
rest'll
condition
and
other
actually
private
and
I.
Like
I
mean
those
rappers
are
mostly
for
security
or
core
I
guess,
select,
I,
don't
know
it's
useful
to
talk
in
the
policy,
but
like
we
want
somewhere
it
was
that
not
everyone
else
need
access
to.
C
C
Also
about
the
tears
roller,
it's,
it
doesn't
really
work
for
us
because,
like
I,
like
I,
think
it
doesn't
allow
to
edit
each
user
or
the
ID
comments,
and
at
least
on
the
mic,
mine,
compiler
Apple
does
something
that
everyone
does
all
the
time
like
on
the
compiler.
We
have
I
think
under
and
50
people
with
flat
access,
because
we
need
to
either
the
comments
from
their
masters
butter
and
also
to
change,
stack
boxes
or
issue
descriptions
and
a
facility
does
not
something
we
can
do
it
to
a
role.
C
B
D
D
E
A
So
one
thing
I
would
say
is
like
we
might
want
to
get
more
specific,
like
I'm
thinking
about
the
compiler
team,
specifically
that
I
think
they're
we
probably
want.
We
have
a
variety
of
repositories.
You
probably
want
a
policy,
that's
like
the
compiler
team
has
a
policy
here
and
how
no
weather
should
be
included
or
not,
but
it's
kind
of
like
the
compiler
team,
gets
write
access.
The
compiler
team
contributors
get
write
access
to
all
of
those,
and
then
there
is
often
a
working
group
team.
A
That's
also
associated
that
also
has
access
and
I
was
kind
of
bad
and
I
would
imagine.
We
have
some
structure
that
we
might
might
be
worth
spelling
out
kind
of
like
that.
A
typical
structure
would
be
that
the
team
has
some
number
of
like
the
the
russ
team,
has
some
github
teams
associated
with
it
and
they
get
write
access
and
then
specific
to
the
repository.
There
might
be
also
a
team
that,
like
a
rust
working
group
or
some
other
rust
structure
that
wants
access
well,
I,
don't
know
is
sometimes
we
just
add.
A
B
A
B
E
D
A
E
A
A
D
E
A
A
A
A
C
Like
I
think,
the
end
goal
would
be
to
add
automation
that
sex
every
episode
up,
they
don't
have
individual
collaborators
so
and
then
having
a
desynchronisation
code
to
remove
teams
that
are
not
defined
in
the
team
or
episode.
All
the
structure
is
the
fine
sister
yes,
but
do
we
need
to
do
a
lot
of
work
to
get
to
that
point
right.
A
B
E
B
D
C
I
think
on
the
team
wrapper
on
the
roster
after
the
team
with
Christ
tires
access
to
it.
I
can
speak
tonight
and
that
mostly
because
they
started
using
it,
so
they
don't
own
it
and
that
it
issues
like
no
stridor
switch.
They
push
a
team
to
me
too
and,
like
we
got
complaints
like
a
few
minutes
after.
A
A
D
A
C
C
A
A
B
A
B
E
A
D
C
Dot
dot
like
that's
way
more
complex
and
I'm,
pretty
sure
we
don't
want
to
give
access
to
other
episodes
because,
like
giving
bright,
access
to
people
works
on
the
main
compiler
opposite
Ori,
because
we
have.
We
have
branch
protection.
So
even
though
they
have
read
access,
they
can
portion
master.
For
example,
okay,.
A
A
E
A
E
C
C
A
E
A
It
these
are
some
what
the
last
time
I
yeah
since
I,
have
the
screen
I
get
to
control
a
little
bit.
The
last
time
I
tried
to
do
a
review
of
the
open
questions.
This
is
what
I
came
up
with
I,
don't
know
if
we
we
didn't
address
all
of
these,
but
most
one
was
github.
Orgs
I
think
we
said
the
policy
we
strongly
prefer
rustling
I
personally
think
we
should
just
move
everything
to
rustling,
but
that's
so.
A
C
A
C
Them
for
the
main
organization
we're
doing
the
but
and
I
think,
and
we
did
some
work
to
switch
to
enforce
it
on
the
University
as
well,
but
like
for
their
team,
specific
organizations,
I,
don't
know
I,
don't
actually
know.
What's
the
status
because
I
don't
have
access
to
them.
I
can't
say
that
it's
like,
like
another
reason,
to
centralize
everything
as
much
as
possible
that
we
can
just
and
for
security,
much
easier
right.
A
D
B
C
Those
are
kind
of
strange
because
Dora's
are
deprecated
but
are
actually
sort
of
maintained
in,
like
we
sometimes
mesh
patches,
because
I
think
I
can
do.
Deprecated
creates
like
time
or
all
those
old
stuff
that
we
still
want
to
match
patches
from
time
to
time.
But
then
you
shouldn't
use
them
see
what,
if.
A
C
E
C
C
A
D
F
Do
you
know
yes,
better?
Okay,
so
the
media
team
is
mainly
easier
management
of
access
for
a
non
for
non
crucial
repositories.
That's
mainly
historic!
So
back
when
everything
was
handled
manually,
we
just
found
it
easier
to
have
a
team
that
has
members
joining
very
often
and
dropping
that
don't
need
any
kind
of
privileged
access
to
last
night.
We
just
found
it
better
to
basically
use
it
as
a
blast
view,
but.
F
F
F
F
F
C
D
E
D
F
F
A
C
A
B
F
C
F
My
favorite
word
official
and
I
think
a
lot
of
the
I
think
the
embedded
working
group
is
actually
good
example
to
investigate.
If
you
want
to
investigate
these
questions,
because
it's
a
highly
productive
group,
but
it
also
implements
things
like
the
specific
board
support
for
certain
kinds
of
vendor
boards
that
they're
currently
investigating
and
I'm,
not
sure
if
coming
up
with
a
policy
on
how
such
a
such
a
repository
should
be
run
under
Ross
Lang
is
but,
for
example,
the
embedded
book
or
things
like
that.
That
might
be
interesting,
I,
don't
know
yeah.
D
A
A
E
We
have
with
the
governance
working
group
where
it's
just
a
single
repository
under
I
was
linked
to
had
all
the
organization
and
then,
if
they
want
to
have
their
own
repositories,
they
can
make
in
their
own
organization,
and
this
will
also
be
good
for
his
working
groups.
The
membership
fluctuates
more
than
the
team's
one.
F
One
question
I
still
have
is:
if
we
have
to
make
working
groups
that
are
official,
how
do
we
still
have
expectations
like,
for
example,
police
enforce?
If
a
because
these
are
attack
vectors
and
the
second
one
being?
Do
we
expect
that,
for
example,
at
least
a
a
rust
Lang
account
will
be
owner
of
the
organization
so
that
no
one
can
grab
the
organization
and
run
away
with
it
likes,
and
some
kind
of
minimal
expectation.
D
E
D
A
E
A
E
A
Like
the
actual
steps
we
have
our
first,
we
got
to
figure
out
which
to
you,
which
probably
send
out
an
email
just
being
like.
We
know
about
these
team
specific
words.
Are
there
others
that
wouldn't
be
surprised
if
there
was
another
one
and
yeah
I
bought
to
try
out
numerate
I'm,
guessing
virtually
every
repository
and
the
best
thing
or
it
does
not
follow
these
policies,
but.
B
C
D
D
D
E
B
A
A
A
C
C
C
F
A
C
E
C
Feel
like
in
my
us,
be
able
to
like,
like
the
I've
in
some
way,
dot
also
basically
solve
all
the
problem.
Just
the
amount
of
changes
you
can
make
in
a
web
application
sex
a
oh
you're,
a
team.
You
can
automatic
in
push
a
coming
directly
to
master
a
person
without
going
from
request,
but
that's
development
and.
B
A
B
A
B
A
E
C
C
D
E
A
See
it's
more
of
a
future
would
I
the
other
thing
would
be
for
the
for
the
rustling
nursery
org,
there's
a
long
list
of
crates
that
still
have
to
be
migrated
or
repose,
and
somebody
probably
needs
to
go
through
them
and
decide
what
happens
to
them.
As
an
example,
I
see
things
like
failure
and
error
chain
or
in
there,
which
is
quite
surprising
to
me.
I,
don't
know
I,
guess
they
probably
all
go
to
rustling.
Maybe
some
of
them
just
get
our
characters.
C
C
D
E
D
C
E
E
C
C
C
E
Teams
are
mostly
pretty
recently
synched.
The
main
thing,
though,
is
all
the
working
groups,
so
the
domain
working
groups,
as
well
as
the
compiler
and
line
team
working
groups
specifically,
there
are
also
a
lot
of
working
groups
where
their
status
is
unclear,
whether
they
should
continue
to
exist
or
be
archived
and
had.
B
So
we've
got
about
10
minutes,
lit,
left
and
I've
got
a
hard
stop
at
two
minutes
to
the
hour.
So
we've
got
a
whole
bunch
of
action.
Items
I
often
find
the
only
way
in
action
item.
Progress
gets
done
as
if
it
is
assigned
to
someone
so
I
can
take
on
rewriting
the
proposal
who
wants
to
take
on
investigating
the
compliance
bot.
B
C
B
F
A
E
D
D
A
D
Just
in
terms
of
to
see
who's
responded
to
your
pings
and
then,
and
also
which
repos
have
been
audited
and
then
also
yeah.
Basically,
who
responds
to
the
pings
to
the
audit
requests
and
the
synchronizing
I
see
several
things
there,
where
you'd
need
a
list
to
keep
track
of
who's,
who
you're
trying
to
reach
in
whose
responded.
A
Any
making
that
happen
D
would
be
the
easiest
to
this
or
an
issue
I'd
like
to
track
these
things.
That
sounds
great
I
mean
luckily
the
rain
from
it
absolutely
in
a
github
issue
were
the
only
problem
with
the
issue.
Is
you
have
to
be
able
to
edit
good
thing
sweet?
Ironically,
we
have
to
get
the
access
permissions
for
our
own.
B
B
D
E
A
Do
we
did
we
cover
there?
So
there's
the
clarify
working
group
terminology
I'm,
just
looking
for
issues
they
have
like
some
progress.
I
have
this
thing
around
I
have
a
proposal
around
the
line
team
structure
that
I've
been
trying
to
move
forward.
That
I
could
see
it
being
useful
to
talk
about
here,
but
I,
don't
know,
I,
don't.