►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20221118
Description
[SIG ContribEx] Weekly Marketing Meeting 20221118
A
B
A
My
major
update
and
big
win
for
this
week
is
that
I
actually
made
PRS
hey
the
fact
that
GitHub
has
a
GUI
and
actually
has
a
workflow
for
editing.
Existing
documents
is
extremely
helpful.
That
is
a
good
point.
I
love
it
even
though
it's
pretty
wonky
sometimes,
and
it
sometimes
it
makes
me
do
things
wrong.
It
I
do
things
even
more
wrong
if
I
was
doing
it
through
the
regular
CLI
anyway,
so
I
made
three
PR's
this
morning.
A
A
Yeah
so
LG
TMS
and
approvals
welcome
on
that
one.
You
got
it
yay!
Thank
you
and
the
next
one
is
deprecating
the
marketing
Council
concept.
So
we
had
a
file
that
described
the
marketing
Council
in
our
role
handbook,
so
I
put
in
a
PR
to
delete
that
file.
It
used
to
be
I
think
the
editor
role
that
Matt
was
filling
before
so.
C
A
Was
like
there's
probably
some
useful
stuff
in
the
history
of
that
file,
but
we
don't
really
need
it
right
now.
We
might
want
to
keep
that
in
mind,
though,
because
one
thing
Chris
and
I
were
discussing
earlier
is
that
we
need
to
create
a
sub-project
lead
role.
So
that's
gonna.
Once
we
get
into
the
table.
If
we
get
into
the
table,
we
might
just
kind
of
freeform
this
I
don't
know
the
table
is
helpful
for
managing.
B
B
B
C
A
B
A
B
A
Yeah
Avinash
made
some
changes,
I
think
there's
probably
some
more
like
detail.
We
could
add
to
the
shadowing
thing,
but
I
think
it
has
the
basics
in
there.
So
I
thought
we
should
go
ahead
and
do
that,
but
I
don't
have
approver
access
on
community
yet
seems
like
I'll,
probably
get
that
at
some
point
soon,
but.
C
A
A
C
A
B
A
B
B
E
E
A
C
B
B
B
A
B
A
A
B
D
B
The
owner's
file
system
is
very
confusing
to
me
just
to
let
everybody
know
right
like
when
it
works.
It
works
when
it
doesn't.
It's
like
untangling,
a
spider
web
of
spider,
webs
right,
so
yeah
chasmine,
if
you
want
to
like
add
me
to
the
group
of
people
too,
that'd,
be
great,
because
I
need
to
figure
this
out
yeah.
It's
super
confusing
right
now
right
and
like
figure
it
out
document
it
watch
it.
You.
E
E
A
A
There
was
a
proposal
in
the
contribex
like
Sig
meeting
a
while
ago,
where
people
were
saying
we
need
to
have
automation,
to
manage
the
owners
files
and
here's
some
Concepts
about
how
we
would
do
that,
and
it
was
basically
shot
down
like
it's.
These
things
are
uncontrollable.
That's
basically
basically
got
out
of
it
like
you
have
to
manage
them
manually.
Doing
it
in
an
automated
fashion,
misses
too
many
edge
cases
pretty
much,
no
matter
how
you
do
it
so
yeah.
D
E
A
Also,
I
remembered
something
during
that
discussion:
Avinash
I
pick
up
yours,
no
I,
guess
I
didn't
actually
never
mind
the
because
you
helped
out
with
the
contributor
Summit
did
you
you
signed
up
for
a
Jersey
right,
I.
Think
Bob
is
on
that.
So
I
should
at
least
make
a
note
to
myself
to
check
on
that.
For
you,
foreign.
D
D
A
B
A
B
B
E
E
A
B
A
B
B
A
B
A
D
B
E
B
D
C
A
B
B
A
B
B
B
D
C
B
Right
stability,
okay,
the
sub
project
will
be
a
responsible
for
establishing
policy
standards
and
procedures
for
routine
GitHub
management
tasks,
including,
but
not
limited
to
order
membership,
org
permissions,
repo
creation,
Administration
so
establishing
a
policy
around
org
owner
permissions
and
Grant
limit
these
privileges.
Accordingly,
we're
going
to
have
that
policies
around
Bots
I
think
we
got
that
covered
because
we're
just
picking
it
up
from
Upstream,
maintaining
documentation
to
the
above
yeah.
This
is
all
on
us,
so.
B
D
A
B
E
B
A
D
C
A
A
C
B
C
D
D
D
D
A
B
B
D
B
D
A
E
Anyway,
we
we
don't
so
particularly
about
this
role,
the
event
role
right.
How
are
we
going
to
look?
I
mean
the
functioning
of
this
role,
because
for
now
I
don't
think
we
do
have
an
event,
particularly
the
mean
like,
or
do
we
have
any
events
that
needs
to
be
handled
apart
from
the
community
meetings.
A
Just
the
community
meetings
and
I
mean,
as
we
plan
for
the
contributor
Summit,
so
we
might
want
to
ask
for
stuff
from
you.
There
I
think
it's
mainly
like,
as
we
as
a
group
become
aware
of
events
that
are
happening.
If
those
events
need
a
liaison
to
make
sure
that
they're
getting
tweets
and
blog
posts
or
generally
if
they
need
help
with
comms
it'll,
be
up
to
you
to
make
sure
that
those
things
get
done.
A
D
B
B
B
D
B
A
Start
on
the
table
now
that
we
have
seven
17
minutes
left
there
are
only
a
few
of
us.
We
might
be
able
to
do
that.
So
there's
the
Hina
issue
involving
making
sure
that
we
get
notifications
also
require
an
update
to
the
team,
which
I
think
is
a
little
bit
later
in
this
move,
kubecon
sheet
into
our
new
Drive
uh-huh.
You
gave
me
the
link
to
this
last
time,
but
I
didn't
do
it
because
I
didn't
highlight
it.
I
found
the
Highlight
very
helpful
last
time,
so
I'm
going
to
do
that
again.
Okay,.
A
A
B
A
A
B
A
A
D
D
A
B
C
D
A
E
D
A
A
A
D
D
D
B
A
A
E
A
D
D
A
A
B
C
D
A
D
A
A
A
D
B
A
B
D
A
D
A
E
A
D
C
A
C
C
B
D
A
So
at
kubecon
I
helped
to
give
the
contribex
session,
and
when
we
were
debating
how
I
present
my
work
on
this
sub-project
I
said,
like
I
lead
the
meetings
and
kind
of
generally
keep
the
thing
going.
I
have
approver
access
and
Bob
was
like
you're.
The
sub
Project
Lead,
oh
and
I
was
like
yes,
obviously
I'm
the
sub
Project
Lead.
So
that's
what
sub
Project
Lead
means.
It's
that
Bob
told
me
that's
what
I
was.
A
B
D
B
Like
AWS
doesn't
well
I
shouldn't
say
this
on
a
recorded
call,
but
like
Engineers
contribution
is
normal,
but
does
not
necessarily
factor
into
promotion
unless
you're
in
a
lead
kind
of
role.
So
hence
why
job
move
makes
sense
to
become
sub-project
co-lead
or
whatever
you
can
be.
The
lead
I
can
be
the
co-lead.