►
From YouTube: [SIG ContribEx] Weekly Meeting for 20220302
Description
[SIG ContribEx] Weekly Meeting for 20220302
A
Hello,
everybody
and
welcome
to
the
sick
contributor
experience
weekly
meeting.
It
is
march,
the
second
I'm
your
host,
alison
daltoni
and
a
bit
of
housekeeping
before
we
begin.
We
abide
by
a
code
of
conduct
in
here.
So
in
short,
that
means
be
excellent
to
each
other.
We've
got
quite
a
lot
to
go
through
here
today,
so
make
sure
you
also
add
your
name
to
the
attendees
under
meeting
notes,
so
awesome.
A
So
with
that
out
of
the
way,
let's
begin
so,
we've
got
first
off.
We
have
our
annual
report,
so
I
will
pull
this
up
now
and
I
will
share
my
screen
because
I
wanted
to
go
through
this
with
the
rest
of
the
group
just
to
check
if
we,
if
we
need
to
add
if
we've
missed
out
any
ever
anything,
so
I'm
going
to
share
screen.
A
Here
here
we
go
I'll:
just
there
we
go.
Can
everybody
see
the
text
there?
A
We
can
rich
stuff.
We
want
rich
diff,
so
current
initiatives.
So
this
is
what
we've
got
so
far.
We
managed
to
migrate
cadev
to
a
managed
kubernetes
dot.
Io
account
we
sort
of
running
the
steering
election
with
alecto.
A
It
was
a
major
change
in
how
we
do
elections
and
we
well
laura
here
and
I'll.
Actually,
you
know
community
meaning
overhaul.
Thank
you
very
much
laura
for
the
help
on
that
effort.
Last
year
and
this
year
easy
cla
migration.
We
migrated
to
easy
cla
contributor
summit,
north
america
contributor
celebration
and
we
managed
to
restart
up
the
teams
for
moderation
in
youtube
admin,
and
I
know
there's
some
things
missing
here.
A
Just
by
sitting
in
the
room,
for
instance,
you
know,
office
hours
is
something
that's
kind
of
you
know
been
a
big
part
kind
of,
and
I
know
david's
here
and
has
been
helping
out
with
office
hours.
I
was
just
probably
good
to
check
in
on
that
or
yeah.
Anyone
in
the
in
the
cool
here
is
there
anything
here
that
we
should
highlight
that
I've
that
me
and
bob
have
missed
out
on
this
draft.
A
All
righty
we'll
move
on
to
the
next
part
of
this
document,
so
we've
got.
We
don't
really
do
caps
because
we're
a
service
and
program
orientated
sig.
So
most
of
our
initiatives
cover
long-term
services
for
the
project.
So
this
is
the
current
list
of
all
our
initiatives
here.
Community
management
contributor,
documentation,
contributor
comms.
A
So
yes,
I
think
I
think
we've
got
everything
in
here,
but
please
give
a
yell.
If
you
are
looking
over
this
and
you
see
that
I've
missed
an
area
that
would
miss
an
area.
Oh
hi,
bob
you're
on
mute,
hi,
bob.
C
Me
now:
yes,
okay,
can
he
the
developer
guide
audit
is
complete.
However,
we
are
in
the
process
of
updating
the
contributor
guide
and.
A
Is
this?
Is
this
up
forever
up
in
the
dock
here
under
highlighter.
A
Last
year's
yes,
last
to
the
past,
so
yeah.
This
is
the
yeah
initiatives
ongoing
initiatives.
I
think
we
covered
that
bob
project
health.
This
is
going
to
be
a
really
good
point
for
a
discussion
in
this
call.
What
areas
and
or
sub
projects
does
do
we
need
to
help
the
most
with
right
now
and
so
we've
covered
these
areas,
but
I
was
hoping
to
get
more
input
from
the
wider
contrabax
team,
we're
hoping
to
get
input
from
the
wider
contravex
team
here.
A
A
Here
we
go
project
help
we're
gonna,
add
over
here.
A
A
A
A
Okay,
does
your
contributing
dot
md
help
new
contributors
engage
with
your
group,
so
we
don't
really
have
a
contributing.md
for
for
a
contributor
experience,
as
the
our
current
process
doesn't
differ
from
the
process,
that's
in
the
contributor
guide.
Currently,
if
your
group
has
special
training
requirements,
we
don't
have
any
special
training
requirements
for
people
and
contributor
experience.
As
far
as
I
know,
is
anyone
got
any
feedback
or
comments
on
that?
No
does
your
group
have
contributors
from
multiple
affiliations?
Yes,
other
ways
in
companies
contribute
the
way.
A
Are
there
ways
end
users
and
companies
can
contribute
that
they
the
work
that
they
currently
are?
Not
sorry,
I'm
trying
to
more
full-time
support
for
item
various
items
under
bullet
point
one.
So
that
being
our
you
know,
we
need
more
help
on
the
github
admin
side.
Community
management,
automation
and
yep
it'll
reduce
toil
for
not
only
contribute
experience,
but
all
groups
in
the
project
membership
statistics
were
retrieved
on
the
2021.
A
Okay,
so
I'll,
primarily
so
that
this
was
all
the
stats
on
on
2022.0130.
A
I
still
need
to
use
dimms
tool
to
look
over.
The
links
for
owner's
files
here
would
be
good,
if
actually,
if
anyone
else
here
in
the
call
has
experience
with
using
the
tool
that
dims
made
to
go
through
all
the
owners,
files
and
stuff
like
that,
that
would
be
helpful.
Please
would
love
would
be
good
to
get
your
help.
A
And
this
is
all
our
continuing
sub
projects
copy
paste.
We
copy
paste
that
from
the
readme
in
a
contribute,
experience
folder
under
community
and
working
groups,
don't
believe
we
have
working
groups.
A
A
So
outside
here,
so
I
can
look
over
this
and
the
meeting
notes
and
then
erase
it.
Okay,
operational,
operational
tasks,
so
we
need
to
review
the
readme
for
accuracy.
We
need
to
review
contributing.md,
but
we
can
cut
that
one
out,
because
we
don't
have
one
subprojects
list
and
linked
owners
review.
We
need
to
review
our
owner's
files.
We
need
to
review
the
roles
that
we
have
and
the
folks
who
are
in
those
roles
and
specifically
like
is
there
anyone
we
need
to?
Is
there
any
areas?
A
We've
gotten
to
update
meeting
notes
and
recording
for
2021
are
linked
from
readme
and
upload
updated
uploaded
if
needed
and
community-wide
updates
in
2021.
So
we
need
a
link
down
in
here
all
the
kubecon
stuff
and
yeah.
That's
that's
the
report,
the
annual
report,
any
comments
or
feedback
on
any
part
of
that
from
the
team.
Anybody.
A
All
righty,
oh
the
pr,
is
linked
inside
the
the
agenda.
A
So
if
you
want
to
take
a
look
over
that
later
on
and
some
things
come
to
mind,
please
leave
a
comment
be
good
to
get
more
input
on
this,
and
that
brings
us
to
our
next
item
in
the
agenda
events
office
hours.
So
we've
got
david
on
the
line
who
I
believe
has
been
hosting
office
hours
or
is
it
meet-up.
E
Yeah,
I've
been
here
for
a
little
over
a
year
now
and
ashamedly.
This
is
my
first
contribution
so.
A
Oh
welcome
along
yeah.
It's.
A
E
Yeah,
so
we've
been
making
some
changes
to
the
format
over
the
last
three
months
where
we
we
found
that
we're
getting
low
engagement
of
questions
and
we're
doing
a
lot
of
work
to
discover
the
discourse
forms
for
unanswered
ones
and
try
and
handle
them
on
the
stream
and
but
we
decided,
maybe
just
to
split
the
time
with
the
officers
and
try
and
get
updates
from
some
of
the
sex
across
the
project.
E
Just
so,
people
can
get
a
flavor
and
a
taste
of
what's
actually
happening
on
the
kubernetes
project
as
well
as
hopefully
getting
some
help
and
questions
answered
along
the
way
and
we
also
brought
on
a
new
co-host,
and
so
carlos
santana
has
joined
us
for
the
last
two
months
and
my
plan
is
to
have
him
bring
someone
else
on
in
a
few
more
months
time
and
just
keep
that
rotation
going
so
I'll
drop
out,
hopefully
in
april
or
may.
A
Awesome
thanks
for
the
update
david
and
thank
you
for
hosting
office
hours
for
the
last
year,
really
appreciate
you
and
the
team
just
helping
put
their
effort
into
kind
of
keeping
that
running
and
welcome
along
to
the
contributes,
biweekly
cool.
A
A
So
contributor
summits,
contributor
summit,
eu
we've
got
a
pull
request
here.
I've
added
a
pull
request
for
the
brief
description
of
you
know
what
is
contributor
summit.
You
know
I
haven't
had
time
to
say
to
make
that
doodle
that
I
was
supposed
to
make
last
week
two
weeks
ago,
so
we're
gonna
just
start
asynchronous
meetings
in
the
slack
every
tuesday
from
around
11
a.m.
A
British
time-
and
that
means
it's
usually
like
an
hour
later
in
eu
time,
so
all
the
eu
folks
involved
and
then
we'll
close
those
out,
probably
in
the
evening
that
was
just
kind
of
a
thought
in
my
head:
I'd
like
some
feedback
on
that
from
other
folks
on
the
call,
if
that's
a
good
idea
or
it's
a
bad
idea
just
because
I
know
like
there's,
we
all
have
like
a
lot
of
meetings.
So
if
we
do
those
slack
meetings,
it
might
be
easier
for
us
to
coordinate
thoughts.
C
I
would
still
probably
try
and
have
at
least
one
in
person
like
either
bi-weekly
or
something
like
that
to
get
some
of
the
more
bigger
things
worked
out.
The
one
problem
for
like
until
the
crew
is
recruited,
if
most
of
the
people
wind
up
being
in
the
u.s,
that
is
6
a.m.
Eastern
time,
3
a.m,
pacific
time.
A
B
A
Okay,
so
that
brings
me
to
kind
of
the
next
item
on
the
list
on
under
contributor
summit
eu.
We
need
to
send
out
just
another
thing
to
the
mailing
list.
Just
so
we
have
a
email
record
of
you
know.
This
is
everyone
who's
kind
of
put
their
interest
forward
in
contributor
summit
eu,
particularly,
you
know
just
double
checking
like
what
who
do
we
have
like
how
many
volunteers,
who
do
we
have
as
volunteers
and
who
will
be
attending
so
yep.
C
Because
if
it
is
going
to
be
more,
you
know
if
we
are
trying
to
recruit
more
eu
people
to
help
run
the
eu
summit
having
that
information
would
be
helpful.
C
Github
issue
to
point
it
towards,
and
then
the
the
people
that
would
get
tracked
in
the
events
duras
named
individuals
would
be
the
the
various
leads.
A
Yeah
any
other
comments.
Oh
I
see
chris
you've
got
your
hand
up.
A
I
think
that
would
be
really
good
actually,
especially.
C
A
Alrighty,
I
think
I
just
wanted
to.
I
just
realized-
I
might
have
accidentally
scrolled
the
page
too
far
and
skipped
over
a
community
meeting.
Sorry
laura!
It's!
Okay,
no
big
deal.
F
Just
real
quick
nigel
did
a
great
job
and
I
know
I
didn't
get
a
chance
to
call
that
out
in
this
meeting.
Yet
there
are
some
updates
to
do
on
the
docs
on
the
website.
I'm
aware
of
them.
They
will
be
coming
and
there
will
be
a
call
going
out
for
hosts
soon,
unless
anyone
on
the
call
would
like
to
hand
raise
to
host
the
next
one
which.
F
The
date
should
be
the
third
thursday,
so
whatever
that
is,
I
don't
have
it
in
front
of
me
at
the
moment,
the
17th
so
17th
march.
F
F
Okay,
thank
you.
Also,
there
is
a
forum
for
topics
I
do
want
to
socialize
that
a
little
more
and
thank
you
chris,
so
we're
trying,
since
we're
not
doing
the
sig
updates
or
anything
like
that,
we're
trying
again
to
do
more
updates
about
the
topics
that
people
need
to
talk
about
across
the
project.
So
for
now
that
form
is
out
there.
I'm
still
trying
to
figure
out
how
to
get
it
transferred
over
to
the
sick
contributor
google
drive
until
then,
but
this
is
just
the
starting
point.
F
A
Cool
beans,
which
brings
us
to
steering
election
we
skip
over,
that
I
haven't
any
other
discussion
about
events.
Is
there
any
events
we
haven't
covered.
C
One
one
quick
thing
at
least
on
the
steering
election
is
that
elections
are
now
going
to
be
a
contraband
sub
project.
H
B
Yeah,
as
well
as
maybe
trying
to
advance
stuff
and
make
election
tools
available
to
sigs,
for
example,
it's
waiting
on
a
bunch
of
technical
stuff.
I
need
to
do
which
is
actually
partly
waiting
on
the
current
security
overhaul
of
electo.
Since
that's
one
of
our
primary
tools,
which
which
is
going
on
right
now,.
B
Link
to
issue
to
the
issue
of
making
it
a
subproject
yep
hold
on.
A
Awesome
mentoring
so
meet
our
contributors
upset
any
updates
from
anyone
on
the
line
about
meet
our
contributors.
A
New
contributor
workshop,
I
still
need
to
update
the
meeting
template
as
the
new
contributor
workshop
and
how
that's
going
forward
is
it's
being
worked
on
by
folks.
So
I
s
yeah
any
updates
bob
or.
C
The
with
it
being
turned
into
a
course
yeah,
I
will
toss
it
over
to
eric,
but
that
that
has
not
been
started
yet.
A
All
right
and
I've
now
just
updated
the
the
meeting
notes
here
so
that
new
contributor
workshop
will
contribute.
New
contributor
guide
will
be
under
eric
yep
and
last
but
not
least,
there's
a
new
mentoring
meeting
doodle
and
do
we
have
a
link
to
that
doodle
in
the
chat.
B
That
doodle
is
actually
down
right
now.
Oh,
I
was
trying
to
put
in
the
link
and
discover
that
I
could
not
access
doodles,
so
I
you
know
be
aware
that
it's
out
there,
I
put
it
on
slack
I'll,
add
it
in
the
notes.
Once
doodle
is
back
up
the
given
the
people,
I
already
know
really
need
to
be
involved
in
a
cyclical
mentoring.
Meeting
it'll,
probably
be
a
dual
meeting.
B
I
with
you
know
sort
of
two
different
cycles
12
hours
apart,
just
because
there's
no
way
to
have
a
meeting
with
people
in
india,
europe
and
the
united,
india,
europe,
the
united
states
and
new
zealand
all
at
the
same
time.
There
is
no
time
slot
that
works.
For
that.
B
A
Awesome
well,
I
hope
I
hope
doodle
comes
back
up
soon.
B
Yeah
initially
I
was
so
unfortunately
initially
when
I
was
seeing
the
results.
A
lot
of
people
were
picking
the
current
time
slot,
which
is
mondays
at
8
pacific.
B
You
know
and
saying
they
were
available
for
that
which
is
kind
of
manifestly
not
true,
because
I've
run
the
last
three
of
those
and
it's
generally
been
me
and
either
deba
or
nate,
and
nobody
else
so
so
in
terms
of
people
voting
on
the
doodle.
Please
vote
for
vote
for
things
that
you
will
actually
be
able
to
attend.
A
All
righty,
thank
you
very
much.
Josh.
Now
we're
on
to
the
next
items
in
our
agenda.
Any
updates
around
community
management.
J
Yeah,
quick
non-update
that
the
crunch
is
over
at
work,
so
I
have
time
to
dedicate
to
automation
again.
A
Awesome,
thank
you
very
much
for
taking
that
on
nigel
appreciate
it
yep.
Next
up
we
have
marketing
chris.
D
Hey
all
from
the
marketing
side,
I
was
actually
out
last
week,
so
I'm
just
gonna
kind
of
skim
over
the
notes.
D
There's
a
draft
moc
apec
blog
that
we're
going
over
we've
updated
the
marketing
council
to
actually
point
to
the
right
people
and
shadows
as
well,
as
you
know,
just
who's
doing
what
in
the
org
as
far
as
campaigns
and
progress,
we're
trying
you
know
to
help
josh
as
much
as
possible,
with
some
kind
of
mentorship
coordinator
trying
to
keep
track
of
when
to
reach
out
to
the
sigs
and
stuff.
Like
that,
the
release
team
there's
the.
D
Issue
with
one
of
the
tweeted
issues,
so
we'll
figure
that
out
but
yeah,
but
everything
seems
to
be
going
good,
we're
looking
into
new
tools
for
tweeter,
tweet,
tweet,
automation,
twitter
automation.
However,
I
wanted
to
say
that
the
first
time
and
yeah
everything's
going
well,
please
join
us
on
fridays
at
11am
eastern
time,
if
you're
interested
in
participating,
there's
plenty
of
work
to
do
what
new
tools
are
you
looking
at
from
here?
There's
microsoft,
workflow
there's
another.
G
Yeah,
so
this
is
the
documentation,
it's
just
it's
still
in
progress,
but
we
are
looking
at
few
automations
like
microsoft,
workflow
and
a10.io,
but
the
problem
here
is
that
we
we
we
are
unable
to
find
us
a
solution
where
it's
free.
For
now
the
n-10
dot
io
is
free
for
self-hosting
on
the
desktop
app
but
to
host
it
on
the
cloud
solution.
G
And
the
microsoft
workflow
is
pretty
much
very
flexible
and
is
very
powerful.
I've
tried
it.
I've
tried
it.
I've
gone
through
some
of
the
workflows
there
are.
We
can
create
conditions,
we
can
integrate
multiple
workflows.
G
C
G
Exactly
so,
I
was
going
there's
an
ongoing
issue
on
the
main
twitter,
together
repository
for
scheduling
to
its
twitter
implementation
of
twitter
thread
better
link
it
here,
but
till
then
we
are
only
relying
on
this
twitter
together,
github
action
so
that
we
can
either
work
on
the
existing
workflow
or
search
for
new
tools.
That's
just
a
proposition.
A
I
think
it
would
be
very
valuable
to
be
able
to
have
something,
that's
more
flexible,
and
you
know
in
terms
of
like
tools
that
could
potentially
cost
money.
I
know
I
would
like
your
comment
on
this
as
well
bob
like,
if
you
find
something,
that's
going
to
be
a
really
good
solution
that
works
for
it,
works
really
well,
and
it's
going
to
cost
something.
It
might
be
good
to
raise
it
higher
up.
A
So
we
can
get
kind
of
some
funding
for
that,
because
it's
very
important
that,
like
we,
that
we
get
y'all
super
getting
the
tweets
out
and
not
being
bogged
back
by
the
stuff,
not
working,
I
know
bob.
What
are
your
thoughts?
My.
C
Gut
is
to
actually
try-
and
you
know,
either
find
someone
to
make
the
change
to
upstream
to
twitter
together,
because
the
there
are
other
projects
that
want
to
do
this,
and
if
we
can
push
that
change
up
there
or
if
we
have
to
fork
it
and
maintain
our
own
copy,
then
that
not
just
benefits
kubernetes
that
benefits
all
the
other
projects
that
want
to
use
it.
C
Just
because
that's
what
a
lot
of
people
understand-
and
I
know
that
like
right
now-
people
aren't
like
opening
up
their
own
tweets.
They
aren't
creating
their
own
tweets,
like
we
kind
of
hope
that
they
would,
but
I
think,
that's
more
of
a
discoverability
issue
and
that
they
don't
know
that
that
capability
is
there.
C
Whenever
I
have
personally
talked
like
other
sick
leads,
they
had
no
idea.
It
existed
like
it
that
they
have
pygmy
like
asking
like
hey.
Can
we
tweet
this
out,
I'm
like
sure
open
up
like
create
an
issue
here,
so
I
think
that
is
the
the
main
reason
why
we
aren't
seeing
you
know
more
engagement
and
usage
of
that
tool
from
the
rest
of
the
community
but
yeah.
My
my
gut
is
to
try
and
and
work
on
the
upstream
version
to
support
that
feature.
G
But
currently
we
we
don't
have
the
means.
We
are
relying
on
the
update,
update
on
the
official
twitter
together
thing
to
get
because
in
the
current
automation
we
cannot
create
twitter,
threads
or
schedule
tweets.
So
I
tried
it
on
my
repository
for
scheduling
tweets,
but
it's
not
working
and
that's
been
an
issue
mentioned
in
the
twitter
together
repository
so
till
then,
should
we
then
rely
on
the
existing
workflow.
C
C
And
you
will
never
get
anyone
else
outside
this
group
ever
touching
it.
You
will
never
get
sick
leads
you'll,
never
get
anyone
else,
actually
trying
to
use
it.
One
of
the
reasons
we
really
pushed
for
twitter
together
was
because
it
would
integrate
with
like
our
sort
of
standard
way
of
doing
things.
D
It's
kind
of
a
chicken
and
egg
thing
right
now,
because
if
we
can't
schedule
tweets,
that
means
someone
has
to
go
in
and
manually
approve
the
tweet
at
the
right
time
kind
of
deal
so
yeah
I
mean
we
don't
necessarily
want
to
open
the
floodgates,
but
you're
right.
We
definitely
should
communicate
that
out
somehow
more
effectively.
K
A
Over
at
that
issue,
that
was
on
twitter
together,
and
I
see
that
26
days
ago,
someone's
commented
that
they're
interested
in
helping
build
it.
It
might
be
good
to
reach
out
to
them
and
kind
of
see.
G
Yeah,
I
proposed
the
thing
about
lfx
mentorship
in
the
marketing
subgroup,
so
yeah.
It
would
be
great
for
some
something
like
mentorship
thing,
to
have
a
proper
guidance
on
what
needs
to
be
done
in
the
workflow,
because
currently
working
on
new
features
is
not
possible
like
this
one
I'll
link
it
here.
So
the
major
problem
that
came
up
with
this
project
is,
we
don't
have
enough
people
like
either
to
you
know.
At
the
point
of
time
we
need
to
approve
also
the
previous
folks
who
helped
us
to
develop.
G
L
Yeah
yeah,
so
the
thing
was
like
I
I
had
been
working
on
this
issue
like
I've,
been
trying
to
develop
it
on
my
own
side,
and
I
did
this
the
last
week
and
face
some
errors.
I
think
the
original
maintainer
of
this
project
on
twitter
and
presently
isn't
like
so
active
in
this
project
itself,
so
he
told
me
to
create
an
issue.
L
Basically
what
was
happening
that
when
you
create
a
developer
twitter
account,
it
has
a
lot
of
like
twitter
gives
you
a
lot
of
options
like
it
has
some
limited
access,
some
elevated
access
and
the
one
which
needs
the
one
account
which
needs
automation,
requests
and
elevated
access.
But
earlier
I
used
to
do
my
own
automation.
L
Things
like
I
used
to
test
out
with
a
limited
access
account,
and
now
I
have
to
like
upgrade
it
to
the
elevated
thing,
and
for
that
it
requires
some
business
proposition
like
it
needs
your
company
name
and
all
that
things.
So
currently
it's
not
like
possible
at
night
to
do
it
so.
M
C
Yeah,
I
would
also
suggest
peeing
jason,
the
other
major
contributor
on
there.
He
is
much
more
active
and
would
be
willing
to
take
this
on.
L
Yeah,
so
basically
this
the
twitter
automation
for
kubernetes
was
developed
by
rajula.
I
guess-
and
I
had
bringed
him
like
two
to
three
times
about
this
and
he
responded
and
the
last
time
the
problem
I
faced
recently.
I
had
pinged
him
about
it
and
he
hasn't
responded
but
yeah.
Maybe
you
can
expect
a
reply,
then
some
days
and
yeah
I'll
do
that
the
one
you
just
said
about
google,
it
is
putting
that
is
the
company.
C
So
I
just
linked
so
the
two
other
primary
contributors
to
the
project
outside
of
gr2m
jason
on
there
like
he
does
this
sort
of
like
he
updates
the
stuff
for
fun
so
like
I'm,
I'm
pretty
sure
he'd
be
willing
to
help
guide
or
potentially
just
take
it
on,
and
do
it.
L
Okay,
I
I
don't
think
the
issue
which
was
linked
earlier
by
tawa,
isn't
isn't
active
like
if
we
need
to
develop
some
new
stuff
like
threading
or
replying
or
putting
some
chips
or
media.
We
need
to
do
it
by
ourselves
by
creating
a
team
within
the
contravix
team,
maybe
or
the
marketing
team
like.
I
don't
think
there
are
enough
contributors
to
this
issue
now.
So
if
you
need
a
quick
solution,
we
might
have
to
work
on
it
intensively
on
our
own.
E
A
Oh
any
other
thoughts.
A
Oh,
thank
you
very
much,
a
father
for
preparing
that
document
and
sharing
with
the
team
and
helping,
and
we
had
we'll
got
to
have
a
really
good
discussion
about
that.
It's
good
and
which
brings
us
to
our
next
item
contributor,
documentation.
I
Contributor
documentation
is
going
along
pretty
well,
we've
done
a
bunch
of
pull
requests
that
are,
you
know,
crawling
along
at
the
speed
of
pull
requests,
but
I
think
we've
got
maybe
like
two
more
big
changes
to
do.
I
you
know
we're
trying
to
get
through
it
so
that
we
can
work
on
the
the
thing
that
I
talked
about
earlier
that
I,
the
the
new
contributor
workshop,
so
I'm
trying
to
get
through
this
latest
batch
of
contributor
guide
updates
as
quickly
as
possible.
I
I
also
contributed
a
script.
That's
in
the
hack
directory
or
it's
in
a
pull
request.
That's
affecting
the
hack
directory
to
auto
format,
markdown,
it's
it
does
almost
everything
pretty
well
and
require
you
know.
It
still
requires
some
manual
fixes
afterwards,
but
it's
it's
it's
pretty
good.
It
needs,
I
think,
some
more
reviews,
maybe
like
one
more
review
from
somebody
who
can
look
at
shell
scripts
and
tell
me
if
I'm
bad
at
them-
and
I
think
that's
about
where
I
am
right
now.
A
Awesome
if
you
grab
those
links
to
the
pull
requests-
and
I
can
get
them
into
the
into
the
meeting
notes
and
you
can
have
a
look
over
it.
A
A
Yeah,
so
I've
got
a
contributor
guide,
developer,
guide
and
contributor
site.
I
Okay,
the
developer
guide-
I
still
I
I'm
not
really
sure
what
changes
we're
gonna
be
making
there
in
the
last
meeting
somebody
who
might
be
here,
oh
ray,
pointed
out
that
a
bunch
of
the
other
sigs
have
their
own
contributor
files
or
contribution
files.
I
didn't
take
a.
I
took
a
look
at
those
a
little
bit,
but
they're
kind
of
I
kind
of
feel
like
it's
going
to
be
tough
for
people
who
aren't
part
of
those
other
cigs
to
really
do
a
lot
of
work
on
those.
I
H
I
should
also
make
a
note
that
cigs
that
do
have
them
they
haven't,
because
they
the
way
they
can
they
they
contribute
in
that
sig
is
different
from
the
main.
The
main
developer,
skype.
I
Right,
yeah,
yeah,
and
I
mean
I
guess
it's
important
for
you
know
to.
I
guess-
make
it
easier
to
contribute
to
a
bunch
of
those
cigs,
but
that
that's
a,
I
think,
that's
that's
a
different
can
of
worms
to
open.
I
C
The
other
sort
of
general
thing
I
want
to
bring
up-
and
this
will
require
a
discussion
on
the
mailing
list-
what
are
people's
thoughts
about
actually
just
moving
the
contributor
guide
to
the
contributor
site?
D
D
C
C
We
have
had
this
conversation
before
and
there
that
was
mostly
pre,
like
the
contributor
site
being
a
thing.
Okay,
and
one
of
the
reasons
why
the
contributor
site
came
about
with
my
shameful
batch
script
is
because
people
did
not
want
to
move
the
content
out
of
k
community.
C
They
wanted
that
to
be
the
source
of
truth.
The
thing
is:
is
that
like
we,
we
like
now
that
more
people
are
actually
starting
to
use
the
contributor
site
they're
going
there
first,
like
we
had
an
issue
open
the
other
day
asking
where
to
update
content
in
the
contributor
guide,
so
it
wind
up
being
this
circular
thing.
If
they
open
up
an
issue
and
then
transfer
it
like
responding,
there,
then
transferring
it
over
to
k
community
for
them
to
update
it.
C
D
J
I
I
think
that
it
should
happen
too,
because
you
know,
like
bob,
found
errors
in
my
markdown,
that
I
could
have
found
myself
if
it
was
easy
enough
to
run
the
website
in
a
testing
environment.
But
it's
such
a
it's
it's
it's
such
a
confusing
setup
that
I
I
think
I
tried
for
like
three
minutes
I
was
like
I
want
to
just
gonna
go
back
to
writing,
so
I
think
it'd
be
a
really
good
idea.
C
It's
because
so
for,
for
others,
markdown
is
up
to
interpretation,
and
there
are
some
things
like
some
things
will
work.
If
you
have
a
link
that
spans
multiple
lines,
others
do
not.
Hugo
is
one
that
does
not.
C
It's
technically
like
it
is
technically
marked
out,
like
hugo,
is
more
strict
than
his
markdown
than
github
that
that
is.
That
is
why
so
I
I
am
personally
in
favor
of
it,
but
I
I
I
want
to
hear
others
thoughts
before
potentially
kicking
a
beehive
and
sending
something
to
the
mailing
list.
A
I
think
the
points
you
made
before
about
how
a
lot
of
people
are
going
to
k
dev
rather
than
k
community
first,
is
a
sign
that
we
need
to
be
putting
more
attention
on
to
onto
cadev
the
site
and
making
sure
that
becomes
our
source
of
truth
and
how
we
approach
that
problem
is
going
to
be
a
whole.
Another
different
question
because
there's
a
whole
lot
of
like
we've
got
two
different
kind
of
things
on
the
table.
B
I
I've
always
been
in
favor
of
of
everything
that
we
expect
to
be
reference
information
being
on
the
community
site
rather
than
buried
in
in
the
repo
of
kdev.
Among
other
things,
that
makes
it
much
more
searchable.
Yeah
google
assigns
very
low
rank
to
anything.
That's
a
text
page
in
the
github
repo.
K
K
K
K
Agreed
agreed,
but
then
you're
making
you're
making
pull
requests
into
it
called
contributor
site,
but
then
also
again
having
dangling
documentation
in
kate
community.
I
would
be
in
favor
of
this
if
there
was
a
plan
in
place,
they're
pretty
much
either
sunsets
k,
community
or
there's
a
strategy
of
what
goes
in
k
community
and
what
goes
in
in
on
the
website
and
who's,
taking
care
of
what
and
also
a
very
nice
placeholder
where
the
community,
where
the
contributor
guide
goes
right
now
that
links
to
the
contributor
site.
A
A
You
know
you
know
how
power
the
people
working
on
this
this
community
documentation
going
to
interface
with
it.
You
know,
what's
go.
What
does
the?
How
will
this
affect
the
kind
of
contributing
process?
You
know
this
is
a
very
kind
of
big
thing,
just
thinking
about
it
out
loud
and
hearing
everyone's
thoughts
on
the
line
and
yeah
I'm
100
on
board
with
we
need
a
plan,
you
know
we
we
should
is
there?
Do
we
have
a
github
issue
for
this
hold
up.
C
There
are
like
there
are
other
things
that
are
blocking
ingesting
content
from
other
repos
too,
and
honestly,
like
that
has
like
replacing
my
basket,
has
been
picked
up
and
dropped
by
like
four
different
people.
Now
the
me
included.
B
One
of
the
prior
requirements
was
that
we
somehow
slurp
stuff
that's
in
k,
community
as
it
is
without
modification
and
include
that
in
the
website
and
and
that
was
technically
prohibitive,
the
we
need
to
be
able
to
reformat
it
as
hugo
docs
or
we're
asking
the
people
who
are
working
on
the
contributor
documentation
to
do
too
much
in
order
to
avoid
changing
anything.
B
So
the
you
know
the.
B
I
think
let's
go
ahead
and
start
with
an
issue
here
and
list
the
items,
because
I
also
think
discussing
in
the
abstract
we're
actually
making
into
a
bigger
deal
than
it
is
because
I
mean
what
else
is
in
k:
community,
the
contributor
summit,
the
sig
pages,
which
are
also
something
that
should
be
present
on
a
website.
K
Of
the
site,
because
because
right
now,
like
even
under
resources
and
community,
I
feel
like
there's
just
kind
of
information
scattered
there.
All
I'm
saying
is
that
we
should
take
a
little
bit
more
of
a
finesse
approach.
I'm
not
blocking
it!
I'm
just
saying:
let's
write
down
what's
in
kate,
what's
in
k,
community
where
it
should
live,
and
why
and
just
have
some
kind
of
like
higher
thought
process
around
this,
so
that,
like
we,
don't
have
to
clean
up
the
clean
up
the
cruft
later
on
from
what
we
build
from
this
exercise.
F
A
So
mailing
list
somewhere
we
can
track
this
and
github
because
I
feel
like
this
is
a
yeah,
a
lot
of
ideas
here
and
we've
got
one
minute
left
for
github
management.
A
I
should
have
kept
an
eye
on
the
time
of
it
better,
but
github
management.
A
Okay,
which
leads
us
down
to
open
mic
and
discussion,
probably
not
gonna,
have
any
time
for
open
mic
today,
but
we
had
a
lot
of
really
good
discussions
here
around
many
many
topics
yeah
it's
good
to
see
y'all
and
thank
you
for
coming
along
to
today's
meeting
and
I'll
catch
you
all
later,
thanks,
bye.