►
Description
[SIG ContribEx] GitHub Administration Subproject Bi-Weekly Meeting for 20220825
A
B
B
What
we
called
upstream
so
working
entirely
with
community
and
contributions
back,
and
I
work
now
on
a
product
called
code
spaces
and
anybody
familiar
with
codespace
is
awesome.
If
not
quick,
real
quick
introduction
is
it's
cloud-based
development
environments,
and
so,
if
you
may
have
heard
of
it
originally
as
vs
code
online,
it
was
came
out
of
that
effort.
B
The
story
is
that
in
a
code,
space
there's
a
default
experience
that
actually
works
for
lots
of
different
projects
or
there's
a
highly
customized
experience
that
is
tailored
perfectly
to
a
project
that
encapsulates
encoding
all
of
the
dependencies
and
startup
requirements
in
a
spec
called
the
dev
container
and
then
codespaces
reads
that
launches
a
codes.
You
know
this
dev
environment
with
a
pre-built
container
that
can
be
a
pre-built
container
or
it
builds
on
the
flyout
container.
B
That's
already
done
for
you,
and
so
as
a
new
contributor.
Instead
of
being
all
fiddly,
you
can
run
a
test
and
make
a
change
and
see
the
output
of
that
change
immediately
and
then
work
out
from
there.
So
it's
sort
of
encourages
new
contributors
by
giving
them
a
very
fast
time
to
joy
and
then
on
the
maintainer
side.
B
You
can
it's
great
for
branches,
it's
great
for
pr,
so
you
can
start
a
codespace
on
a
pr
and
it
automatically
clones
all
the
code
and
make
sure
the
pr
is
in
place.
So
it's
perfect
for
testing
prs
and
it
has
a
great
kind
of
side
benefit
of
just
making
collaboration
across
maintainers
and
with
other
new
contributors,
which
straight
more
easy
and
so
I'll
pause
for
a
second.
Before
I
go
into
what
I've
been
talking
to
contributes
about
see
if
there
any
questions
about
code
spaces
as
a
product.
B
B
We're
going
to
be
doing
a
big
marketing
announcement
about
that
later
this
year.
That
will
make
it
easy
for
everyone
to
use
that.
I
can't
say
more
than
that
at
this
point,
especially
since
I'm
being
recorded,
and
this
will
be
on
youtube-
and
I
don't
want
to
get
myself
in
trouble,
but
it'll
be
good,
and
then
the
next
piece
is
that
I've
been
talking
to
contribex
about
this.
B
Obviously
the
catacota
thing
died,
and
so
one
direction
is
to
kind
of
revamp
and
revive
the
at
least
the
goals
of
what
pedocodo
was
about
using
code
spaces
to
create
kind
of
playgrounds
where
people
can
try
things
out
and
learn,
learn
the
ropes
of
kubernetes
and
then
the
other
thing
is
that
contribex
is
working
on
a
new
contributor
experience,
education
program,
training
program
and
in
partnership
with
the
consulting
firm
that
built
that
we've
got
at
least
preliminary
agreement.
That
codespace
is
code.
B
You
know
and
then
essentially
code
spaces
and
the
way
it
is
in
github
would
naturally
become
a
part
of
the
way.
One
at
least
has
an
option
to
work
with
the
codebase,
that's
kind
of
where
we
are
right.
Now
we're
just
kicking
off
that
curriculum
development
process
and
actually
have
a
meeting
next
week,
wednesday,
with
dee
vibrata
to
kind
of
kick
off
the
kadakota
work.
C
I'd
have
I
have
one
question
craig:
if
that's,
okay,
and-
and
so
so
one
of
the
one
of
the
use
cases
that
will
be
awesome
to
to
tease
out
would
be
people
collaborating
on
fix
working
on
end-to-end
tests.
So
do
you
think
it
would
be
possible
to
run
end-to-end
tests
for
for
two
people
to
to
collab
on
that
and
work
on
that?
Absolutely
cool?
Okay?
Yes,.
B
B
One
is
you
can
obviously,
as
an
individual,
I
can
run
the
ed
tests
in
my
code
space
and
then
there's
a
technology
called
live
share,
which
you
can
kind
of
co
code
using
the
same
same
web,
browser
interface
into
it
and
see,
and
do
that
together,
which
certainly
helps
the
the
code
space
is
actually
owned
by
an
individual
user.
So
it's
not
like
co-owned
per
se.
The
resources
are
actually
assigned
to
someone
with
their
permissions,
and
so
you
have
to
use
the
web
browser
capability
to
do
the
sharing.
A
C
A
And
craig
to
be,
to
be
quite
honest,
we've
been
talking
about
godzilla's
for
communities.
For
three
years
now
we
basically
had
the
idea
when,
when
it
came,
when
code
failed
went
out,
we
tried
to
do
that,
for
I
remember
there
was
a
possibility
to
use
that
for
contributor
work.
Subject
contributing
summit,
but.
A
Yeah
and
we,
I
think
we
add
performance
issues
and
boundaries
and
stuff
like
that,
so
we
never
were
able
to
to
use
that.
I
I
think
your
the
big
concern
is
how
we
basically
gonna
land,
the
dev
container
fire
in
the
kk
repo.
That's
gonna
be
the
biggest
concern,
because
if
we
basically
provide
the
possibility
to
people
to
bootstrap
code
space
with
the
kk
ripple,
the
rest
is
just
spilling.
B
That's
very
sensible.
I
think
the
the
product
has
changed
and
improved
quite
a
bit
in
the
last
couple
of
years.
I
I
heard
the
stories
of
the
failed
efforts
a
couple
of
years
ago,
and
I
was
very
pleased
when
you
know
before
I
started
this
effort
of
reaching
out
to
the
kubernetes
community.
When
I
joined
github,
I
I
tried
to
replicate
what
you
guys
were
trying
to
do
using
you
know
our
current
configurations
and
product
and
had
a
very
different
and
good
experience
using
a
four
core
machine
now
with
the
product.
B
You
can
provision
anything
from
a
two
core
machine
to
a
32
core
machine
with
plenty
of
ram
and
this
space,
and
so
the
experience
can
be
dramatically
different
than
what
you
could
do
on
your
local
dev
box.
You
know,
since
you
have
a
machine
in
the
data
center
with
great
network
bandwidth
available
to
it.
B
A
A
D
It's
so
good
to
see
you
again
greg
I
I
we
should
catch
up
more
often
one
of
the
things
that
iii
does
a
lot
of
is
pairing
and
that's
the
whole.
Even
the
representation
of
an
eye.
Next
to
an
eye
is
people
working
together
and
so
we've
ever
since
we
logged
on
to
some
unix
boxes,
solaris
boxes
back
in
university
and
shared
a
t-mux
or
a
gnu
screen
back
then
a
session
together
like
how
do
we
get
people
to
do
it
together?
D
It's
storytelling
in
a
in
a
very
many
language
form,
including
they
actually
have
a
library
called
the
org
babel
and
it's
from
from
babel.
It's
how
they
get
all
these
different
people
speaking
languages
together
to
work
together.
Well
and
it's
primarily
been
used
internal
to
our
team
and
when
we
pair
with
someone
else
for
a
period
of
time,
one
of
the
things
we've
been
looking
at
is
trying
to
make
that
available
to
others.
D
And
so
we've
been
looking
at
ways
to
use
the
cncf
ability
to
spin
up
infrastructure
underneath
projects
to
support
something
like
your
the
piece
of
software
working
on
dot,
github
user
dot,
the
name
of
the
project,
dot
cncf.
That
is
very
similar
to
code
spaces,
but
it
hasn't
involved
any
work
with
vs
code.
Yet,
but
I
just
submitted
to
bs
co
or
through
the
lfx
mentorship
stuff
to
get
people
to
I've.
D
Had
a
few
people
apply
to
go
through
that
to
be
kind
of
this
initial
phase
of
instead
of
of
of
bringing
up
just
our
terminal
environment
to
go
ahead
and
using
something
like
coder.com
to
bring
up.
They
currently
don't
target
cluster
api,
but
he
thought
about
this.
This
initiatives
to
add
cluster
api
support
to
the
provisioner
for
coder,
so
that
anyone
anywhere
can
target
a
cluster,
and
if
we
go
for
v,
cluster
and
and
and
kuba
admin,
I'm
sorry
cooper.
D
D
How
old
oregon
emacs
are
yeah,
but
there's
really
well
defined
engineering
things
that
could
be
brought
forward
if
we
can,
and
so
that's
why,
with
the
code
spaces,
that's
what
it's
called
right
in
the
github
trying
to
find
some
of
these
ways
to
overlap
some
of
the
things
we're
doing
and
pull
them
out
so
they're
available
to
a
wider
community
and
also
things
from
what
we're
doing
to
maybe
be
brought
into
workspaces.
So
they're
stuff
we're
doing
this
cross-pollination
of
ideas.
I
think
it's
particularly
well
for
this
onboarding
conversation.
B
B
Yeah,
like
I
guess,
I'm
wondering
like
why,
wouldn't
you
invest
then
in
doing
using
that
approach,
as
opposed
to
you
know,
invest
like
why?
Why
do
the
effort
of
trying
to
find
where
the
synergies
are
between
code
spaces
and
that,
as
opposed
to
investing
mostly
in
the
pair
sharing,
I
guess
what's
what
what's
complementary,
that's
conflicting?
What's
absolutely.
D
D
D
We
do
have
a
little
bit
of
that
in
vs
code,
where
there's
a
terminal
down
there,
but
we
don't
have
that
code
coda
code
thing
where
here
is
the
document
that
drives
the
the
the
terminal,
and
we
also
don't
provide
people
the
ability
to
edit
the
code
inside
while
they're
working
on
it,
which
is
what
we
do
like
our
template
for
getting
started
for,
identifying
a
new
endpoint
in
kubernetes
that
doesn't
have
a
test,
yet
is
all
org
mode.
You
bring
it
up
and
there's
the
sql
block.
D
You
execute
the
sql
block,
says
here's
the
things
defined
by
all
of
our
ci
engines.
This
ain't
done
yet
choose
one,
and
then
they
choose
ones
where's
the
documentation.
That's
a
little
more
manual,
take
the
docs
and
then
write
a
little
small
snippet
of
golem
code
and
it's
not
in
a
file.
It's
just
there
and
it
goes
through
and
hits
it
and
then
another
thing
to
check
the
db.
This.
B
B
D
Love
to
see
what
you
found
currently
I've
only
found
things
that
that,
in
the
document
itself,
support
the
the
highlighting
and
all
of
the
tree
collapsing
and
all
that
of
org
mode,
but
don't
support
because
it's
kind
of
essential
as
all
those
code
blocks
have
parameters
and
things
that
need
to
be
passed
on.
And
I'm
assuming
at
this
point
to
a
lisp
engine.
A
C
C
Yeah
you
could
you
can
reach
out
either
to
hippie
or
myself.
I
I
shared
some
links
for
a
hippie
there
just
to
give
some
refs
on
what
he
was
talking
about
and
if
you
want
to,
I
think
the
synergies
will
be
to
see
what
can
be
done
right
now
in
pair
and
then
look
at
look
at.
What's
good
look
at
what's
might
be
limiting
and
then
just
just
learn,
learn
from
that
experience
and
see
what
we
can,
how
we
can
marry
the
two.
D
Yeah,
so
real
real
quick
if
you'll
drop
a
link
to
the
issue,
we're
trying
to
get
prow
hook,
actions
plugins
to
run
as
github,
and
we
have
an
issue
open,
and
my
this
seems
like
the
primary
scary
thing-
is
the
hard
limit
across
an
entire
org
for
github
actions.
Api
calls
being
a
thousand
per
hour,
and
I
want
to
check
and
see
if
there's
a
way
that
that
can
be
limited
higher.
D
I
think
for
most
projects
that
would
allow
most
proud
plug-ins
to
work
as
they
won't
hit
that
limit.
But
I
want
to
find
some
way
that,
when
we
do,
projects
are
more
successful
without
having
to
provide
prow,
but
just
continue
to
provide
this
github
action
that
we
don't.
We
have
a
way
forward
when
they
get
successful.
C
This
this
custom
action
called
pga,
which
is
proud,
github
action,
and
so
the
hippie
is
is
concerned
about
hitting
that
rate
limiting
at
that
rate
limit,
I'm
concerned
about
instantiating
the
proud
plugin
right
now,
because
I'm
I'm
to
my
eyes
and
trying
to
implement
that
so
I'll
worry
about
rate
limits
when
I
get
the
brow
plug
and
running
so
yeah.
But
that's
that's
that's
where
I'm
at
at
the
minute.
A
E
C
E
A
A
A
Oh
okay,
I
think
it's
better
to
do
that
anything
because
we,
after
the
time
I
would
say
for
you,
priyanka,
opened
an
issue
about
getting
a
token
for
this.
We
agree
to
you
an
existing
one
yep.
We
can
follow
up
on
that
on
on
the
slack
channel
and
see
what's
happening
basically,
because
I
think
once
we
get
your
pro
request
merge
we
can
work
on
set
up
the
project.
E
E
This
would
save
a
lot
of
time
for
at
least
one
of
the
sub
group
and
segregates,
and
also
it
will
be
like
a
good
demo
for
or
a
poc
for
enhancement
and
the
other
groups
as
well,
so
yeah,
I'm
working
with
priyanka,
so
she
was
taking
over
this
because
I
was
in
vacation.
So
would
love
to
you
know
like
continue
helping
moving
forward
with
that.