►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220805
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220805
A
Hello
and
welcome
to
the
august
5th
2022
edition
of
the
contributor
comms
team
meeting.
We
are
a
sub-project
of
sig
contribex
within
the
kubernetes
project
and
we
have
a
code
of
conduct
that
we
adhere
to
which
basically
says
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other.
B
I
think
the
pigments
would
be
a
lot
of
tweets
caught
out
this
week
regarding
the
annual
contributor
survey,
and
then
we
had
this
removal
and
deprecation
blog
that
is
out
this
week.
So
we
had
a
lot
of.
We
had
a
tweet
on
that.
So
that's
also
out
thanks.
A
B
C
C
A
And
two
two
release
related
tweets
this
week:
yeah
the
blog
and
code
freeze,
and
I
also
speaking
of
which
I
have
a
list
somewhere
here
of
all
of
the
dates
coming
up
for
the
release
that
we
need
to
make
tweets
about,
and
I've
been
meaning
to
put
it
into
our
slack
channel.
I
like
tried
to
ask
the
person
first
to
like
make
sure
they
wanted
like
they
were
okay
with
us
doing
that
yeah
just
to
make
sure,
and
then
they
never
responded.
So
then
it
was
a
bad
thing.
B
Whoops
yeah,
I
think
we
have
ray
to
approve
us
as
well
as
from
com
side.
You
have
thumbs
up
so
yeah.
You
could
go
ahead.
A
Yeah
also,
I
mean
it's
a
related
update,
it's
also
in
the
table,
but
I'll
mention
it
now.
I
also
put
out
the
pr
for
the
social
media
lead
role,
so
I
would
like
someone
else
to
lgtm
that,
especially
if
anyone
is
particularly
interested
in
taking
on
that
role,
definitely
take
a
look
at
that.
I
need
to
grab
the
link
for
it.
D
I
missed
it
now.
I
I
miss
the
the
announcement
in
slack,
but
it's
not
completely
outside
of
the
things
that
I'm
interested
in
so
yeah.
D
A
Understand
but
you
have
help.
D
No
but
yeah,
I'm
still
honestly,
I'm
sometimes
on
these
conversations,
I'm
still
on
that
position
of
thinking.
Well,
I
actually
don't
know
half
as
much
as
I
should
to
even
consider
this
stuff.
D
On
the
other
hand,
I'm
doing
things
that
are
obviously
related
to
it,
so
I
don't
want
to
be
too
shy
in
taking
up
things
that
I
could
be
helpful,
so
I
I
obviously
welcome
your
own
input,
so
feel
free
to
push
me
and
steer
me
towards
things
that
you
consider
to
be
adequate
cool.
C
A
Cool
so
great
big
win.
Thank
you,
debba
good
suggestion.
Also,
there's
only
one
more,
I
think,
of
frederico's
tweet
prs
still
in
there
about
the
the
report
from
the
help
wanted
section
there's
only
one
of
those
left,
because
I
let
one
go
this
morning,
I
figured
I'd.
Maybe
let
the
next
one
go
after
this
meeting
I
tried
to
do
them
like
9
a.m
before
earlier,
and
then
like
after
six
for
time
zone
reasons,
which
is
one
reason.
D
D
Add
the
I'll
let
two
more
by
the
end
of
today,
so
we'll
have
something
for
next
week.
Yeah.
C
A
Yeah,
that
is
so
good,
any
other
big
wins
before
we
move
into
the
table
or
any
new
items
that
need
to
be
added
to
the
table.
B
A
The
last
update
on
this
was
that
hina
had
created
our
team
in
github
and
we're
trying
out
this
approach
of
adding
an
at
our
team
into
the
issue
template
the
issue
with
that.
Is
that
it's
possible
when
someone
creates
their
issue,
they
could
remove
that.
So
then
we
would
not
get
notified,
which
is
our
goal.
We
had
one
other
solution
that
we
were
looking
into
and
I'm
not
sure
if
he
ended
up
implementing
that
one
as
well.
A
I
think
our
recommendation
was
to
do
both
and
see
how
it
goes,
but
so
there
is
a
status
to
be
checked
on
there,
but
there
is
at
least
something
in
place
also
to
fulfill
this.
A
I
think
that's!
What's
going
on
there
cool
next
item
chris's
article
on
squash,
we
discussed
that
a
bit
last
week,
yep.
D
And
it's
it's
up
to
me.
So
I've
changed
the
the
article
on
my
computer
to
include
some
of
the
comments
there.
I
do
have,
however,
a
strange
technical
dependency
issue,
because
in
order
for
me
to
preserve
the
the
history
of
the
commits
that
were
and
the
nits
that
were
already
applied,
I
need
to
to
fork
the
existing
chris
fork
of
the
contributor
side.
But
I
can't
do
that
because
I
I
only
I
already
have
a
fork
of
the
contributor
site
that
is
tied
with
my
own
six
spotlights
storage
article
right.
D
So
if
I
delete
it
and
then
I
need
to
add
something
there,
I
would
then
have
to
delete
the
one
from
chris
and
go
like
this,
and
this
doesn't
sound
like
a
great
way
to
spend
my
time
so.
D
Yeah,
the
only
problem
is
that
I
I
I
wanted
to
maintain
them
co-authored
by,
because
you
already
have
that.
Because
of
the
comments
of
tim
of
yeah.
D
So
it
would
be
more
elegant
to
actually
keep
that
right.
I
would
create
a
fork
of
your
repository
and
then
my
editions
will
would
would
emerge
as
a
continuation
of
that.
D
Maybe
I
can't
simply
delete
the
fork
that
I
have,
because
I'm
not
saying
like
movement,
delete
it,
create
and
then
delete
it
and
create
again
and
just
and
just
do
this,
because
I
I'm
not
seeing
a
lot
of
action
on
the
six
spotlight
one
and
I
don't
think
that
actually
I
I
have
to
change
more
more
things
because
everything
was
already
applied,
so
yeah
I'll.
Go
that
way,
I'll
delete
it
and
I
will
submit
it
using
your
fork
as
a
reference.
D
No,
it's
because
I'm
I'm
sensitive
to
the
auto-ship
thing
because
of
the
other
discussion
right.
So
I
I
imagine
it
makes
sense
to
keep
the
the
history
there,
even
if
it
ends
up
being
squashed
later
yeah,
it's
it's
relevant,
so
yeah.
I
will
go
that
route.
So
in
the
next
couple
of
days
I
will
say
I
already
have
the
the
copy
on
my
on
my
laptop
so
I'll.
I
will
just
push
that
using
chris
fork
as
a
reference
in
in
the
new
pr
that
I
will
reference
the
original
one.
D
D
The
directory
is
called
like
this
is
the
real
pr
version
too.
It's
it's
the
equivalent
of
echo
the
codes
wishes
here
in
the
wagon
yeah.
It.
C
C
C
A
D
Yeah,
no,
absolutely
I
will
I
will.
I
will
tell
the
process
in
the
in
the
slack
channel
at
least.
A
That's
what
open
source
is
all
about
facing
fears.
Next
item
is
buffer
status
and
so
bob
killen,
my
last
update
here
was:
I
know
that
we
need
to
create
an
account
for
the
cncf
to
be
able
to
put
their
billing
information
into.
I
created
an
account
just
to
kind
of
look
around
it
a
little
bit
we
I
was
discussing
with
chris
that
there's
probably
some
other
account
that
we
need
to
put
into
it.
Chris
suggested
an
account,
and
I
wanted
to
check
with
bob
on.
A
A
Which
you're
thinking
is
probably
the
one
that'll
need
to
be
under,
which
makes
total
sense
to
me,
and
I'm
thinking
so
too,
but
just
to
check
with
bob
to
make
sure
plus
then
I'll
have
the
ping
with
bob
already
to
be
like
this
is
what
I'm
gonna
do.
Does
that
sound
right
and
then
I'll
be
like
okay?
Here
it
is.
C
A
At
least
that's
the
plan
all
right.
Next,
two
items
are
both
the
the
buffer
sub
items
so
we'll
go
ahead
and
skip
those
for
now
next
item.
Oh
that's!
Right!
Last
time
I
said
that
I
would
start
sharing
my
screen
for
this
because
that
seems
like
it
would
be
much
easier
to
follow
and
for
some
reason
I
never
do
it,
which
is
super
weird.
A
So
I'm
going
to
share
my
screen
actually
now
part
of
the
way
through
the
list.
Already
all
right,
we'll
share
that
we'll
zoom
in
cool
folks
can
see
that.
B
A
Okay,
so
our
next
item
is
the
roll
descriptions
I've
already
updated
on
the
one
that
I've
been
shepherding,
which
is
the
social
media
role,
there's
a
pr
out
for
it.
The
link
was
in
the
chat
it's
676
in
the
community
repo,
so
I
just
need
an
lgtm
on
that.
I
guess
I
need
an
approval
too.
I'm
not
an
approval
and
approver
in
the
community
repo,
so
I'll
need
to
figure
that
out
as
well,
but
other
role
updates,
avanesh.
B
C
B
A
Yeah
I
saw
that
so
I'm
probably
good
to
go
cool
project
manager.
Concept
for
hina
is
still
in
very
early
stages
of
brainstorming,
and
we
have
lots
of
stuff
to
work
out
with
that.
So
that's
kind
of
where
that
one
is
atarva,
approver,
leader
role,
potarva,
isn't
on
today
right.
I
had
a
discussion
with
him
on
slack
about
this
role,
though
no.
A
Okay,
but
I
suggested
that
atarva
take
point
on
starting
to
figure
out
this
role
and
set
it
up.
I
think
it
I
suggested
it
would
be
a
good
good
exercise
for
him
to
understand
more
about
the
role
since
he
suggested
it
and
give
him
an
opportunity
to
have
a
fun
project
with
some
ownership.
So
so
I've
suggested
that
he
talk
with
a
couple
of
other
folks
about
the
concept
to
to
kind
of
figure
it
out.
A
Contributor
sites
role
concept
looks
like
we
had
said
imran.
You
were
gonna
look
into
that
along
with
the
help
of
chris,
probably
any
updates
from
either
of
you.
B
Yeah
something
I'm
working
on
something
on
the
contributor
side,
understanding
the
work
I'm
just
exploring
it
still.
There
is
a
bug
which
I
sell.
It's
also
one
of
the
items
yeah,
I'm
just
figuring
out,
yeah.
C
The
theme
itself,
which
is
doxy
and
actually
I
I
built
a
doc
site
this
week,
using
doxy
or
last
week,
using
doxy
and
built
a
container
to
build
it
on
arm
linux
and,
like
that
apparently
isn't
available
by
default
because
of
some
other
dependencies.
So
interesting
be
careful
there
if
you're
using
a
container,
for
example,
to
like
spin
up
the
site
locally
kind
of
deal
but
yeah.
Let
me
know
if
you
need
any
help
like.
B
Yeah,
I
just
checked
the
netlify
jobs.
To
see
I
mean
I
was
basically
exploring
the
issue
with
the
publishing
date
and
the
the
job
build
feature
so
just
exploring
how
the
workflow
looks
like
and
add
some
understanding,
yeah.
But
definitely
I
think
when
I
fix
this
issue,
which
we
have.
I
think
I
probably
would
have
explored
how
this
thing
worked.
So
so,
there's.
C
C
A
B
A
B
A
We
originally
had
this
concept
of
like
a
development,
lead
role
where
we
could
recruit
someone
with
better
knowledge
of
the
project,
which
would
be
really
difficult,
but
the
goal
was
to
have
someone
with
like
the
the
technical
know-how
for
the
pieces
that
we
might
need
to
know
about,
but
we
decided
that
the
contributor
site
role,
plus
the
approver
role,
would
kind
of
be
two
roles
that
would
share
responsibilities
related
to
technical
tasks
that
we
need
to
perform.
A
A
So
we'll
establish
that
once
we
have
the
other
two
and
blogging
lead,
I'm
supposed
to
write
out
a
draft
for
this
nice.
That's
one
thing
that
I
forgot
that
I
needed
to
update.
I
thought
I
did
so
well
this
week
I
was
like
I
have
like
three
things
I
need
to
update.
A
C
A
Some
folks
have
just
been
non-stop,
sounds
horrible,
yeah
anyway,
all
right,
so
that's
it
for
the
rolls
we
can
always
discuss
those
anytime
very
important
work
going
on
there.
Oh
chat
windows
here.
I
should
move
that
over
here.
A
Okay,
so
next
item
updating
the
contributor
com's
name,
it's
been
going
on
for
entirely
too
long.
It's
true,
but
I
checked
in
with
hashida
and
josh
on
this
last
week.
From
their
perspective,
it
was
good
to
go,
but
that
changed
this
week,
so
sometimes
delaying
things
has
its
uses.
I
guess
one
of
the
prs
needed
some
changes
for
the
contributor
site.
I
think
I
think
it's
a
contributor
site
related
pr
for
this,
so
harshita
was
working
on
that
as
of
like
yesterday
or
the
day
before.
A
A
So
I'm
gonna
move
on
from
that.
Next
item:
sig,
spotlight
posts,
furnace
wire,
isn't
on
right,
so
and
tarpa
isn't
either
so
just
frederico
updates
on
yours.
It's.
D
Same
as
last
week,
so
essentially
sig
architecture
have
just
pinged
the
kosher
again
to
ask
for
the
status,
but
it's
ongoing
in
terms
of
the
the
content
in
the
docs
file
and
for
security,
and
I
haven't
even
started
because
I
I
haven't,
got
additional
feedback.
But
I'm
insisting
to
to
to
see
what
we
yeah.
But
it's
it's
paused,
I
would
say,
and
the
the
other
one
is
ongoing.
D
But
I
will
continue
to
to
press
on
both
because
sometimes
these
things
like
stay
flat
during
a
couple
of
weeks
and
they
pick
up
so.
A
D
D
No
well,
I
I
would
assume
that
all
spotlight
interviews
have
a
component
of
of
what
are
you
doing
right
now
for
this
release
cycle.
I
know
that
I
have
them
in
in
my
own
and
and
and-
and
there
are
a
couple
of
questions
there
around-
what's
important
in
125,
what
are
the
major
features
etc?
Actually,
part
of
it
are
also
present
in
the
feature
in
the
mid
mid
cycle,
feature
block
that
comes
dead
and
but
well
that's.
This
is
just
a
note
it
it.
D
It
isn't
critical,
but
it
would
be
interesting
to
have
it
released,
at
least
within
the
existing
release
cycle.
A
A
A
A
D
A
Yep,
so
I
wouldn't
worry
about
it
too
terribly
much,
but
up
to
you,
however,
you
want
to
handle
that
I
feel
like
there
was
something
else
I
was
gonna.
Add
on
that
oh
link
to
the
sig
doc's
post
would
be
nice
to
have.
I
guess
I
should
find
it
now.
A
A
It's
not
gonna
happen
yep,
and
I
still
need
to
find
that
list
of
dates
for
all
of
the
release,
things
that
I
saw
going
on
so
I'll
make
sure
to
add
that
in
our
slack
channel
after
this,
if
I
don't
find
it
before,
we
finish
up
here,
we're
moving
along
a
good
click,
though
today
so
we'll
see
so
I'll
move
on
from
the
sig.
A
Oh,
the
other
thing
I
was
gonna
say
is
that
it's
pretty
common
for
for
these
interviews
to
take
a
while,
especially
since
code
freeze,
happened
this
week,
I'm
sure
that
they
were
kinda
underwater
for
that,
so
it
takes
a
while.
Sometimes
that's,
okay,
all
right
updates
to
the
blogging
instructions.
Frederico.
You
had
a
pr
out
for
that.
This
is
the
wrong.
D
Yes-
and
this
is
the
right
one
yeah
and
in
the
meantime,
I
actually
created
the
a
a
a
candy
file
as
well,
because
it's
it's
a
bit
circular,
because
these
instructions
are
supposed
to
talk
about
using
akmd
as
a
preliminary
step.
But
my
so
my
initial
approach
was
to
be
very
minimal
in
the
changes.
Just
just
adds
that
those
specific
steps
that
I
found
were
missing
in
terms
of
the
instructions,
because
they
for
someone
knew
they
pointed
towards
adding
directly
to
the
to
the
main
side
in
order
to
contribute
side.
D
So
I
added
there,
but
in
the
meantime,
I've
I've
had.
I
had
comments
that
are
more
that
have
a
wider
scope,
so
in
terms
of
really
changing
the
the
way
that
the
the
the
instructions
work.
What
I
did
in
the
meantime
was
to,
and-
and
I
didn't
update
this
in
the
in
the
in
the
file,
but
in
the
pr,
but
I've
shared
it
in
the
in
slack
with
all
those
that
were
involved,
was
to
create
a
net
md
file.
D
To
avoid
exactly
part
of
the
problem
that
we're
trying
to
explain
that
we
want
to
avoid
in
those
blogging
guidelines.
So,
to
avoid
having
this
being
reviewed
in
the
in
the
using
github
and
because
now
it's
it's
wider
in
terms
of
the
scope
of
changes.
So
let
me
paste
it
to
you
here.
D
A
D
Yeah
it's,
but
I
I
think
that
so
I've
I've
started
to
add
the
comments
that
I
I
got
to
that.
So
maybe
we
should
review
the
the
ekmd
file
until
it's
on
a
in
a
level
that
everyone
agrees
with,
and
then
I
will
update
the
pr
with
the
with
the
new
commits
that
reflects
the
state
of
our
discussion
in
fmd.
D
A
So
you
have
a
pr
out,
but
some
changes
were
requested.
You're,
looking
at
kind
of
broadening
the
information
a
little
bit
and
you're
doing
that
via
hackmd,
because.
D
B
A
And
one
important
thing
to
note
is
that
this
is
for
our
own
groups
blogging
guidelines,
it's
not
like
broader
or
anything
like
that.
C
A
Docs,
it's
not
the
doc's
team.
This
is
just
our
own
recommendations,
because
our
group,
it
makes
a
lot
of
sense
for
anything
that
we
do
to
go
up
on
the
contributor
side
as
well,
whereas
that
might
not
always
be
the
case
first
off
going
to
the
okay
and
that.
D
D
A
A
Work
out,
that's
how
we
do
it
need
driven
learning
sounds
good,
so
I'll
try
to
remember
to
take
a
look
at
that
later
today,
hopefully
at
least
before
our
next
meeting,
all
right,
so
I'll
move
on
from
that
migration
from
katakota
to
killer
coda,
just
keeping
an
eye
on
this,
because
it's
fascinating
anyone
got
any
updates
on
that.
B
Yeah,
so
I'm
working
along
with
github
to
see
how
the
code
spaces
thing
work
in
the
bi-weekly
meeting,
we
had
a
discussion
on
how
we
could
make
this
thing
work
for
our.
I
think,
contributor
playground
where
you
know
people
need
to
come
and
be
part
of
an
org.
Actually
there
are
some
permissions
that
need
to
be
given
to
merge
the
pr
and
play
with
it.
So
I
think
let
me
first
try
to
run
kubernetes.
B
Let's
keep
when
it
is
on
codespaces,
because
the
free
version
it
was
tight,
it
was
getting
timed
out
every
time
I
tried,
so
I
have
asked
them
to
increase
my
a
memory
as
well
as
cpu
nodes.
So
let's
see
how
that
works.
B
Yeah
yeah
yeah
this
code
space
is
capability
because
I
think
you
might
have
noticed
this
this
week.
Someone
from
github
came
up
and
you
know
they
wanted
us
to
try
their
gita
port
spaces,
which
is
scheduled
to
release
this
november,
okay,
so
yeah.
I
saw
it
to
be
a
potential
thing
because
it's
very
easy.
Someone,
like
you,
create
on
the
code
green
code
button
to
fork
or
to
clone
you
get
the
good
spaces
option
just
beside
it.
So
yeah,
it's
very
beginner
friendly.
B
A
All
righty,
I'm
gonna,
move
on
to
the
next
item.
Annual
report.
Stuff
federico
has
been
killing
it
with
that.
As
we
said,
there's
one
tweet
left
as
a
pr,
and
you
said,
there's
two
more
coming
this
week:
yep
exactly
yeah.
I
think
you're,
the
only
one
actively
working
on
that.
So
I
swapped
that
there,
but.
B
A
All
right
and
I'll
plan
this
in
that
last
pr
right
after
this
meeting
I
mentioned
earlier.
C
C
A
C
C
A
A
Rajulo's
been,
and
we've
talked
about
this
a
couple
times
he's
been
swamped
with
work,
so
he
hasn't
been
able
to
work
with
our
group
for
a
bit,
but
there's
some
knowledge
that
he
has
that
we
want
to
make
sure
is
passed
on
to
other
folks
in
the
group.
So
that's
something
we
discussed
the
last
time.
I
chatted
with
him
and
it's
something
I
need
to
check
up
with
him
on.
C
A
All
right
so
I'll,
just
kind
of
move
on
from
that
apac
meet
our
contributors
blog
this
one's
like
a
rolling
thing,
any
updates
on
that
debba.
Yes,.
B
Yes,
a
recent
update,
seven
is
code
cape,
but
on
the
pr
side,
why
it's
not
getting
merged
from
the
computer
site
is
because
they
are
trying
to
overhaul
the
system.
How
apr.
A
B
A
Oh
one
thing
rodrigo:
I
haven't
reviewed
your
pr
for
updates
to
our
blog
process,
but
one
thing
I
just
thought
of
that
we
might
want
to
add
into
our
blogging
recommendations
is
we
were
already
recommending
doing
a
hackmd
or
google
docs
as
a
first
round
of
review.
We
just
need
to
add
in
that
we
need
to
share
that
with
the
blogging
team
now
at
least
for
now,
until
they
get
their
new
stuff
out.
I
think
that's
a.
D
Should
they
contact
someone,
so
that
would
be
very
important
now
up
until
now,
I've
just
said
that
people
would
coordinate
whatever
action
inside
our
new
slack
channel
and
take
it
from
there,
but
maybe
something
else
needs
to
be
done
right,
so
do
review
it,
and-
and
I
think
that
we-
I
I
we
must
add
something
around
that
so.
A
Yeah,
what
I
was
thinking
is,
I
think,
a
few
of
the
blog
reviewers
at
least
have
joined
our
channel
exactly
so
we
could
ping
them
directly
in
there
if
we
have
specific
people
that
we
want
to
ping,
but
also
posting
it
in
the
sig
docs
blog
subproject
channel,
that
might
be
actually
a
better
process.
D
Okay,
even
because
the
from
what
I
got,
the
idea
is
to
have
the
editors
to
actually
open
the
pr.
So
it
means
that
someone
will
be
identified
at
an
early
stage,
so
someone
will
have
to
take
ownership
of
that
of
that
pr.
So
it's
very
important
to
to
try
to
explain
to
people
where
should
they
get
the
that
editor
if
it's
in
our
channel
or
if
it's
in
sick
dogs
or
whatever,
right.
C
A
As
we
work
it
out
and
also
since
they're
still
in
progress
of
updating
their
blogging
guidelines,
it's
we
might
want
to
update
it
when
they
finish
that
too.
So
we
could
always
go
with
this
and
then
add
that
update
later,
but
just
a
thought,
all
right.
A
B
Yeah,
so
that's
that's
what
we
are
chatting
in
the
slack,
so
I'm
just
we
and
this
week
as
well
like
check
out
some
flags
to
see.
I
actually,
I
think
the
suggestion
what
we
wrote
last
time.
The
box
within
suggestion
may
not
seem
to
work
because
there
is
no
flag
which
actually
says
that
it,
the
hugo,
respects
the
flag
and
it
tries
to
publish.
But
there
is
something
else
which
I
need
to
check
so
yeah,
I'm
just
still
looking
at
it
and,
let
me
see,
seems
like
chris
had
some
suggestions
so
I'll
I'll.
B
A
B
A
A
A
B
Yeah
yeah
yeah
cool
cool.
I
think
it
also
has
to
wait
because,
once
until
the
process
has
been
established,
we
have
to
wait.
A
B
A
Sig
doc's
blog
subproject
process
changes.
We've
discussed
that
quite
a
bit
already.
B
D
There's
actually
some
movement
there.
If
I
not
mistaken.
D
Okay,
I
know
this
is
the
other
one.
Sorry
I
was
I'm
I'm
lost
between
so
many
squash
prs.
This
is
the
one
around.
D
D
But
but
there's
a
there
was,
if
you
remember
there
was
an
additional
pr
that
was
to
mention
that
on
the
actual
instructions,
let
me
get
that
clip
for
you.
A
A
B
D
So
this
was
relate.
It
is
related
with
the
other
one
with
chris
around
the
blog
article
right,
but
one
of
the
comments
was
that
this
was
missing
from
the
actual
instructions
that
we
had.
So
I
I
I
had
to
open
this
one
and
three
days
ago
it
was
update
it's
okay
to
test
so.
B
D
I
think
this
should
be
to
keep
it
simpler.
This
one
should
be
tied
with
the
other
one
around
the
okay.
It's.
D
A
B
A
B
A
B
If
you
try
to
squash
comments,
just
using
get
three
base
and
let's
say
you
have
a
merge
conflict
in
between
the
digit,
so
let's
say
you
take
the
you
try
to
squash
the
three
latest
comments
and
one
of
them
is
a
merge
comment.
You
suddenly
end
up
with
a
lot
of
comments
in
the
editor,
so
something
along
that
lines,
that
how
would
you
squash
comments?
If
you
have
a.
D
Yeah
yeah.
I
think
this
would
be
an
interesting
con
additional
contribution,
because
we
are
saying
that
the
the
other
process
simplifies
not
not
needing
to
know
how
to
do
it,
but
but
for
example,
I
I
do
it
manually
with
replays
and
amanda
and
stuff
like
that.
So
it
would
be
interesting
to
as
a
follow-up
exactly
to
explain
outside
of
this
automated
pro
and
tiled
process.
How
would
the
contributor
do
it
by
hand
so
using
git
commands?
So
I
think
this
is
as
a
is.
A
is
a
very
interesting
follow-up.
That's
a
good.
A
D
Honestly,
I
can
see
it
either
way,
but
well,
but
actually
I
think
that
we
should
keep
the
focus
on
the
on
the
automation
separate.
So
one
should
be
about
using
the
github
actions
and
well
the
the
bot
and
the
the
tile,
the
and
pro
process-
and
I
I
see
this
but
I'm
open
to
to
a
discussion,
of
course,
as
a
additional
article
on
its
own.
That
could
say.
D
Well,
you
we've
seen
how
to
do
this
through
tiled,
pro
etc,
but
now
we'll
take
a
look
into
how
to
do
it
using
git
commands,
and
I
think
this
by
itself
would
be
a
an
article
that
has
enough
myth
in
it
to
warrant
a
dedicated
blog.
A
So
you
all
can
chat
on
that.
We
are
at
901,
so
I
want
to
check
on
the.
A
And
we
can
always
come
back
to
that
for
a
second,
if
you
all
want
to
chat
more
but
avinish.
There
was
one
last
thing
that
I
want
to
check
on
with
you,
the
hina
thing
we
already
discussed,
so
we
can
skip
that,
but
security
comes
guidelines,
any
updates
there
a
lot
of
your
zavinish.
By
the
way
I
said
you
I
saw
that
you
mentioned
that
you're
on
a
lot
of
things.
A
lot
of
them
are
just
like
you
know.
What's
going
on,
so
we
check
in
with
it
yeah
exactly.
B
That
kid,
whenever
I
see
I
I'm
like,
did
I
miss
something,
but
no
that's
not
the
case
about
this.
I've
actually
reached
out
to
one
of
the
folks
from
security
asking.
If
there
is
an
update,
I
have
not
received
any
updates
yet
so
it's
okay.