►
From YouTube: Cartographer Community Meeting- June 2nd, 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
welcome
everyone
to
cartographer
office
hours
in
community
meeting.
So
today
we
are
yeah
briefly
discussing
a
question
from
cora
about
the
intention
to
or
the
proposal
to
rename
some
of
the
cryptographer
resources
and
see
that
in
progress.
B
A
C
Sort
of
like
how
far
away
that
whole
change
is
to
move
from
using,
like
the
whole
renaming
resources-
and
I
guess
I
guess-
maybe
it's
a
two-part
question
like-
is
there
a
model
already
worked
out?
Do
we
know
that
it's
a
blueprint
and
blah
blah,
blah
or,
and
also
how
far
away?
That
is
how
fast.
B
So
the
team
has
been
developing
in
the
direction
that
there's
probably
going
to
be
some
move
in
that
direction.
There's
been
a
sprint
for
our
040
release,
which
is
about
ready,
so
we
haven't
thought
much
about
it.
Lately
I
mean,
I
think
we
all.
We
all
would
like
something
like
that,
and
so
I
think
it's
a
reasonable
question
that
you
asked
and
having
some
sort
of
timeline
on
that
would
be,
would
be
helpful.
There's
a
few
proposals
flying
around
too,
that
might
that
might
inform
the
decision
to
standardize
on
the
blueprint.
B
So
the
idea
in
general
is
that
the
blueprint
that
the
supply
chain
and
the
delivery
that
we
have
today
are
very
similar
objects
and
for
whatever
differences
they
have,
those
differences
can
easily
be
encapsulated
in
a
singular
concept
called
a
blueprint.
That's
why
we
use
the
word
blueprint
in
our
docs
and
there's
another
proposal.
That's
out
there
that
we
care
about
for
snippets.
B
I
think
it's
been
described
as
the
snippets
rfc,
which
is
the
idea
that
a
few
people
have
been
asking
and
saying
you
know,
there's
pieces
of
a
supply
chain
that
we
kind
of
always
want
to
use,
and
we
want
to
use
repeatedly
in
multiple
supply
chains.
How
can
we
get
that
kind
of
reuse
without
having
to
just
copy
past
the
yaml
all
the
time,
and
so
the
concept
also
includes
the
idea
that
a
blueprint
itself
also
represents
it's
meta.
It
can
also
be
a
template.
It
has
an
output
type.
B
So
that's
where
the
idea
is
going,
even
if
we
do
land
on
something
concrete,
which
I
hope
we
do
in
the
next
sprint
is
part
of
our
design
process.
There
will
have
to
be
migrations
and
we'll
have
to
be
discussions
about.
B
You
know
the
broader
term,
the
the
broader
changes
that
will
and
impacts
that
we'll
have
on
our
users
for
sure
and
will
certainly
be
brought
up
as
a
proper
rfc
before
it
gets.
There
is
a
blueprint
rfc
there,
but
I
think
people
have
gone
away
to
think
about
it
a
little
bit
and
so
that
hasn't
been
pushed
along.
Yet
so
maybe
it's
something
we
can
make
sure
that
at
the
next
more
attended
meeting
we
actually
have
a
discussion
about.
B
I
think
that
would
be,
I
think
now
is
just
the
poor
attendance
is
in
reflection
of
the
fact
that
we're
all
pushing
to
get
a
release
out
at
the.
C
No,
I
mean
even
even
that
helps
like
it's
not
like
it's
not
imminent,
yeah,
okay,
because
it
just
makes
for,
like
my
my
my
personal
concern
is
just
like,
as
I
talk
about
it
as
I
put
out
material,
is
it
going
to
change
in
like
two
weeks
and
then
am
I
better
off
waiting,
but
it.
B
Thank
you
and
we
appreciate
the
material
that
you
put
out
so
you
know
I
appreciate.
B
So
we
want
to
be
just
I
I
I
was
the
one
who
pushed
for
that
rfc
to
start
so
that
we
would
start
having
the
discussions
right
and
because
folks
were
like
well,
we
can't
do
that
right
now.
We've
got
so
much
else
going
on,
I'm
like
absolutely,
but
I
think
everyone
should
be
aware
of
what
we're
thinking,
because
just
want
it
to
be
a
great
product
and,
of
course,
there's
going
to
be
a
huge
migration
issue.
B
There,
a
real
pain
in
that
respect,
so
certainly
something
we
want
to
make
sure
that
we
care
about
and
and
that
the
rsc
includes
how
we're
going
to
do
crd
migrations
right.
A
Thank
you
rush
all
right.
Let
me
share
my
screen.
Real
quick
here,
yeah
so
feel
free
to
have
your
name
there.
If
your
affiliation
is
with
vmware,
you
just
need
to
add
your
name
just
to
save
you
time
if
your
affiliation
is
with
terasky.
Also,
please
add
it
there
cool.
So
what's
new
in
the
project
yeah,
I
think
rash
already
summarized
that
work
on
the
and
the
new
release
the
full
release.
B
Well,
I
could
probably
yeah.
I
could
probably
go
into
a
little
bit
more
depth
of
those
who
are
here,
because
a
couple
of
things
have
landed.
I
think
it's
worth
knowing
there's
a
bug
fix
and
it
will
change
behavior,
but
only
only
in
the
sense
of
the
behavior
probably
was
not
working
properly,
that
is
around
runnable
runnable
was
not
reporting
status
correctly,
and
it
would
happily
copy
forward
an
output
if
it
was
present,
even
if
the
techdon
task
had
only
just
started.
B
So
if
you
were
taking
an
input
say
from
the
spec
that
would
have
just
been
copied
forward,
and
so
you
would
have
found
that
you're,
especially
if
you're
running
like
a
tekton
source
test,
you
would
find
that
was
running
in
parallel
with
your
following
step,
which
probably
be
a
build,
so
it
wasn't
really
gating
anything
that
should
be
it.
It's
dependent
on
tech
time
finishing
with
succeeded,
equals
true
now
and
that's
important,
so
you
have
to
detect
on
task
now
has
to
succeed
at
equal.
B
True
for
that
value
to
copy
forward,
the
status
of
the
object
is
still
inaccurate.
That's
an
ongoing
bug,
I'm
hoping
to
fix
that
before
o4,
it's
finalized,
but
it
may
not
make
it,
but
at
least
the
important
part
of
that,
which
is
that
the
gating
would
work
with
techdon
runnable's
not
supposed
to
be
techno
specific.
But
it
is
at
the
moment
because
that's
as
far
as
we've
gotten,
so
that's
just
something
to
be
aware
of
it's
it's
based
on
the
concept
that
there's
a
condition
succeeded.
B
There's
been
a
lot
of
efforts
to
develop
internally.
There's
been
a
lot
of
efforts
to
develop
a
a
pr
workflow,
I'm
not
sure
where
that
will
land,
but
I'm
hoping
we'll
have
some
examples
of
pr's
soon
in
the
open
source
as
well,
I
mean.
Obviously
people
can
roll
it
themselves,
but
I'd
love
to
get
those
examples
in.
B
So
that's
some
work
that
we've
been
learning
about,
so
I'm
hoping
that
will
land
soon
to
make
p
pull
requests
instead
of
just
doing
git
pushes
so
I'm
hoping
that
we'll
land
an
open
source
at
some
point
soon,
but
at
least
there's
knowledge
that
we've
built
up
around
that.
Let's
see
what
else
might
have
landed,
oh
and
and
the
the
health
health
status
work
is
mostly
done.
There's
still
the
multi-match
for
that,
I'm
not
sure
that
that's
landed
yet,
but
most
of
the
health
status
work
is
done.
B
I'm
I'm
meant
to
be
on
that
by
now,
but
you
know
how
life
is
exactly
it's
it's
next
on
the
list,
though
for
sure,
but
it
probably
won't,
will
not
be
making
it
to
o4.
Actually
it
won't
be
so.
B
It's
not
even
hard
work.
It's
yeah,
I
think,
there's
a
little.
B
B
Internally,
too,
to
think
about
how
we've
been
doing
testing
but
without
the
rest
of
the
team.
Here,
I'm
I
don't.
B
As
much
into
that,
except
that,
I
would
like
to
pick
up
some
of
the
testing
practices
that
we
see
in
in
the
convention
control
the.
B
And
cartographer
conventions
and
yeah
some
simpler
testing
based
around
stubbing
api
requests,
instead
of
using
the
amp
test
approach
from
controller
runtime,
but
I
have
to
ratify
that,
but
that's
I
would
like
to
see
some
of
that
happen
so
that
I
can
write
these
tests
in
an
easier
way,
one
that's
less
async
and
a
little
easier
to
test.
So
so
that's
the
the
main
thing
I'm
I'm
trying
to
make
happen
before
I
actually
implement
the
events,
but
after
that
it
should
should
land
pretty
quickly,
definitely
be
in
the
next
version.
D
B
Yeah,
I
really
hope
that
we
find
some
time
to
prioritize
generating
an
actual
controller
for
that
approach.
Obviously
it's
not
cartographer's
problem
so
to
speak,
but
I
just
think
that
it
would
really
strengthen
cartographer's
stance
if
we
have
a.
B
D
Isn't
no
yeah,
there's
very
like
job
specific
ones
right
so,
like
you
have
flux,
has
the
image
reflector
which,
when
it
recognizes
a
new
tag
in
an
image
registry,
creates
a
pr
to
update
the
image
tag
in
a
manifest,
but
that's
like
very
specific
to
only
that,
it's
not
for
full
anything.
You
want
prs.
B
Yeah
yeah
a
controller
that
accepted
a
some
source
in
the
specification.
D
D
Yeah,
instead
of
writing
a
bunch
of
bash
code
with
some
git
commands
in
there
and
making
it
very
specific
to
a
git
provider,
because
there
is
no
pr
api
for
git,
there
is
a
special
one
for
gitlab
and
for
github
and
for
bitbucket
and
for
github.
Enterprise
has
a
different
api
than
github
itself
and
yeah
yeah.
D
B
D
B
My
my
thought
on
that
was
to
try
and
work
out.
If,
if
all
of
those
things
have
some,
you
know
false
false
starts,
you
you
hit
an
end
point.
No,
it's
not
there!
Okay,
so
it's
not
github
enterprise
right
hit!
Another
endpoint!
Oh
it's!
Clearly
it's
a
you
know:
it's
bitbucket!
You
know
right,
you
know,
so
I.
D
Exactly
but
yeah
because
the
pr
api
there's
examples
on
like
tech
on
hub
of
doing
things
with
you
know:
github
prs,
but
nothing
around
any
other
git
provider
right.
B
D
Exactly
I
mean
one
of
the
things
I
was
talking
with
stephen
about
before
was
the
idea
that
I
think
that
you
know
what
would
be
so
amazing
down
the
road
for
cartographer.
Talking
about
these
examples
is
actually
taking
that
idea
of
techdon
hub
that
exists
right
and
creating
something
like
that
of
cartographer.
Absolutely
I'm.
B
D
B
The
first
thing
I
would
do
I
mean
I
already-
I
already
feel
that
there
needs
to
be
a
like
a
community
hub
on
the
site,
but
the
first
thing
I
would
do
is
I'd
raise
an
issue
for
that
on
the
cartographer's
site,
and
also
I
would
not.
I
don't
think
any
of
us
would
resist
a
first
draft
pr
to
see.
You
know
to
add
something
like
that,
because
there's
no
reason
we
can't.
C
B
It
using
using
hugo
at
the
moment
so
right,
I
don't
disagree.
I
think
that's
the
thing
that
we
need
to
do
and
I
think
it
needs
to
help
us
drive.
B
So
perhaps,
if
you
all
don't
mind,
I'd
jump
onto
that
yeah
yeah,
I
just
I've,
got
a
link
there
for
hacking
on
front
matter,
and
this
is
this
is
the
markdown
hackmd
that
I
did
now?
This
is
not
editable,
because
this
is
my
space
for
thinking
about
this
stuff,
but
by
all
means,
add
comments
or
have
a
shot
at
this
yourself,
but
I
feel,
like
the
I
feel
like
when
you
walk
into
the
cartographer
website.
You
don't
really
understand
what
we
do.
B
I've
I've
got
friends
and
family,
who
are
software
engineers
perfectly
capable
and
they
go.
I
still
don't
know
what
it
is
you're
working
on
and
I
go
that's
fair
enough.
I
think
it's.
The
current
front
matter
is
not
great,
and
so
what
I
tried
to
do
was
something
a
little
like
carvel's
front
page,
and
you
know
a
few
of
these
places
have
got
like
three
big
tiles
that
just
try
to
generalize
what
it
is.
The
product
is
and
use
a
big
icon
for
it.
B
So
so
the
three
principles
that
I
came
up
with
here,
I
think
one
of
them.
I
think
they
all
lead
to
it,
but
I
think
mostly,
that
composability
controllers
do
the
heavy
lifting
means
that
we
need
a
place
to
talk
about
what
controllers
already
exist,
that
we
recommend
people
use
that
we've
got
examples
of
being
used,
because
I
think
we,
you
know
we
we
are
dependent
on
the
idea
that
the
ecosystem
will
grow
with
controllers
that
are
suitable
for
supply
chains.
B
It
can't
just
be
the
the
core
team,
because
we
haven't
got
a
hope
of
generating
that
many
controllers
in
the
world
all
right.
We
definitely
want
to
see
it
happening
in
the
the
broader
community
and
so
one
example.
Being
a
controller
for
prs
is,
I
think,
incredibly
valuable
and
the
time
is
is
ripe
for
that,
but
yeah.
So
so
I
guess
my
my
point
is:
is
that
if
people
agree
with
a
lot
of
what
I'm
saying
here
and
you
may
not,
I
feel
like
that
is
exactly
the
right
direction
to
go.
B
Is
that
there's
a
hub
for
finding
controllers
more
important
than
examples
of
how
to
use
them
is
to
know
that
those
those
controllers
exist,
and
you
know
you
can
pick
them
up
and
and
quickly
purpose
them
using
a
simple
template
right.
That's
the
that's!
The
dream!
A
simple
template
will
quickly.
Let
you
absorb
a
controller,
that's
great
for
great
for
supply
chains.
B
That's
that's
the
intention,
but
I'd
really
like
it.
If
y'all
could
comment
on
this
and
see
if
this
would
have
got
you
square
on
the
ideas
behind
cartographer
a
little
quicker,
then.
C
Ci
cd
separation
of
concerns,
and
so
the
you're
saying
that
the
the
launch
point
like
you're
you're,
are
you
suggesting
basically
changing
this
page
and
trying
to
make
it
something
where
people
land
and
they
more
quickly,
can
absorb?
What
cartographer
does.
B
B
Don't
know
I
might,
I
might
need
to
be
I'm.
I
might
need
to
take
a
step
back
and
think
about
this
again.
I
still
feel
like
when
I
look
at
this
page.
I
don't
know
what
it
is
that
it
it
does,
and
most
people
who
most
people
who
come
along
are
thinking
in
terms
of
live,
I'm
using
tech,
donald
jenkins
or
concourse,
or
I'm
using
some
kind
of
like.
I
guess,
there's
two
entry
points
to
this
this
world
there
is
the
I've
heard
great
marketing
about
this.
B
A
Not
a
problem
yeah,
one
of
the
mods
yeah
frequent
questions
we
receive
is
how
is
this
different
to
tech
tone
chains
or
whatever
yeah,
and
we
are
also
running
an
exercise
with
users
to
try
to.
We
will
be
running
this
exercise
to
try
to
gather
feedback.
A
B
Looking
at
it,
I
feel,
like
I
feel,
like
jumping
off
to
examples,
is
also
be
very
useful
right,
very
quickly
showing
how
how
our
structure
gives
you,
as
per
my
document,
how
it
gives
you
a
convention
over
configuration.
I
don't
even
think
that's
very
well
sold
at
the
first
like
it's
a
big
offering.
The
developer
only
has
to
write
the
shortest
bit
of
yaml
on
the
planet
to
to
go
through
path
production.
B
It's
the
heroku,
push
experience
right
where,
but
instead
of
heroku
you've
got
your
ops
teams
managing
whatever
the
supply
chain.
Is
that
actually
gets
you
to
prod?
So
I
think
you
know
just
there
right.
First
first
thing
we
should
say
is
versus
all
of
this
yaml
to
describe
what
your
application
looks
like
here's
a
workload
and
that's
why
this
is
better
all
right
and
then
you
know,
composability
controllers.
Do
the
heavy
lifting.
Why?
B
Because
this
stuff
is
now
one
place
to
do
our
back
one
place
to
do
to
define
your
your
supply
chains
that
matches
the
same
the
same
principles
you
use
for
your
productionized
environments.
B
So
if
you
know
our
back
for
running
your
kate's
resources,
then
you
know
our
back
for
managing
cartographer
right
those
sorts
of
skills
that
then
translatable.
I
don't
know
how
you
do
an
example
for
that
that
one's
a
little
less
like
immediate-
and
I
don't
know-
that's
that's
where
I'm
going
and
I'd
love
some
feedback
on
getting
this
stuff,
a
little
squarer
and
straighter
with
with
users.
C
I
think
I
think
one
of
the
points
that
could
be
driven
more
is
also
just
like
I
feel
like.
Sometimes
when
we
talk
about
what
cartographer
does
the
things
that
it
does
are
not
necessarily
things
that
enterprises
aren't
doing.
C
C
But
what
but
what
this
does
is
it
says
you
know
that
whole
thing
that
you
had
to
diy
until
now,
it's
kind
of
like
when
we
transitioned
you
know
even
into
cloud
foundry.
It
was
like
yeah
you're.
C
You
know
you
have
a
platform
you're
running
your
web
servers,
but
you
don't
have
to
do
this
manually
anymore
and
now
it's
not
just
that
we're
automating
it,
but
we're
actually
offering
a
better
way
to
do
it
so
that
it
is
intrinsically
more
simpler,
more
elegant
and
more
maintainable,
and
it's
built
on
this
next
generation
of
technologies
right.
So
this
isn't
not.
C
This
is
not
just
automating
your
supply
chain
or
or
finding
a
way
to
sort
of
like
save
companies
from
diying
something,
but
it's
actually
I
mean
it
is
doing
that,
but
it's
doing
it
based
on
this
leap
forward
that
kubernetes
offers.
Where
now,
suddenly
everything
is
running
on
kubernetes
everything
is,
you
know,
top
to
bottom
leveraging
those
things
kubernetes
becomes
as
common
operating
system,
so
the
lifecycle
management
is
delegated
to
this
common
layer
and
really
you're
you're
picking
and
choosing.
C
You
know
best
of
breed
ecosystem
point
solutions
for
any
particular
part
of
your
process
and
we're
giving
you
this
ability
to
integrate
all
of
those
and
that
elegance
and
power
is
what
can
replace
this
diy
thing.
You
know
kind
of
like
thing
that
you've
been
wielding
all
this
time,
so
in
a
way
like
while
it
is
valuable,
of
course,
to
talk
about
the
things
that
it
can
do
those
I
I
feel
like
a
lot
of
companies
have
achieved
some
of
those
outcomes
to
a
what
they
consider
you
know.
C
C
B
B
And
so
what
we
need
there?
What
comes
up
for
me
is.
We
need
to
draw
a
bead
on
replace
your
snowflakes,
all
right,
replace
your
snowflakes
with
with
with
evolving
industry
standards,
and
then
that
was
where
cartographer
as
a
project
runs
aground
a
little,
because
cartographer
is
a
project
at
the
moment.
Pretty
much
represents
the
platform.
B
The
platform
authoring
platform,
not
the
platform
itself,
whereas
maybe
like
tce,
is
an
example
of
a
platform
that
that
is
authored,
right
and
is
flexible
would
be
where,
where
you
can
say
like
directly
to
an
organization
here,
you
already
got
some
stuff
rolled
out
that
we've
got
some
best
practices
for
the
industry,
that
you
can
immediately
roll
out
all
right,
whereas
cartographer's
not
suggesting
that
today,
I'm
not
saying
it
shouldn't,
I'm
just
saying
at
the
moment.
It's
really
we
run
aground
with
people
who
think
that
cartographer
is
the
sea
of
push
experience.
B
They
think
when
they
grab
cartographer.
What
they're
getting
is
a
is
pre-roll
platform
right
and
they're
like
wait,
cartographers
are
not
that
and
no
supply
chains
are
there,
and
people
can
write
their
own
cartographer
enables
that
right.
I'm
not
saying
it's
right
or
wrong.
I'm
saying
that
I
want
to
make
sure
that
we
actually
help
people
with
that,
because
I
hit
that
too
often
with
users
who
are
expecting
cartographer
itself
to
solve
the
platform
problem.
B
D
B
Yeah
it
took
a
while,
but
we
should
actually
mention
that
in
the
in
the
notes,
the
cartographer
catalog
is
now
open
and
available.
So
you've
got
a
working
example,
except
I
can't
seem
to
find
it.
B
I
have,
I
have
so
much
trouble
with
typing
on
a
laptop
keyboard.
B
Yes,
I
mean
that
should
be
on
that
page
right.
I
know
we
have
a
resources
page,
but
I
think
this
is
a
different
thing.
David
right,
I
think
there
is
this
idea
of,
like
specifically
components
that
you
can
immediately
use
examples
of
examples
or
tested
supply
chains,
great
controllers,
that
you
might
want
to
pick
up
ticked
on
tasks
that
immediately
reusable
with
with
you
know.
We
could
even
categorize
them
that
thusly.
D
Yeah-
and
I
definitely
think
so-
it's
things
like
I
I
had
built
originally
like
an
integration
with
argo
workflows,
just
to
show
like
the
plugability
over
that
it
doesn't
need
to
be
techton
right.
Just
even
having
that
like
a
simple
example
of
running
a
hello
world
test,
you
know,
like
the
simple
tech
time
tasks
that
are
used
is
a
way
of
validating
to
the
community.
Of
that
this
is
pluggable
right
like
we
all.
We
know
it's
pluggable.
It
was
built
in
a
plugable
way,
but
where
do
we
have
more
options
right?
D
There's,
no,
real,
nothing
really,
except
for
flux,
that
does
what
flux
source
controller
does,
but
for
other
parts
there
are
other
controllers
that
could
be
implemented.
D
That
are
definitely
beneficial
to
show
that
type
of
an
integration,
and
it
could
even
be
just
cluster
source
templates
or
someone
could
upload
a
supply
chain
with
all
of
the
templates
themselves
right,
but
it
could
be
all
types
of
resources
that
could
just
be
out
there
for
people
to
be
able
to
really
take
a
look
at.
B
I'm
silenced
I
didn't
realize,
is
it
I
mean?
Is
it
enough
today
that
that
if
we
created
a
page
like
that,
we
just
mentioned
at
the
top
of
it
we
put
an
edit
link
and
say
and,
and
that
just
creates
a
pr
for
I.
B
D
Exactly
and
I
think
that
it
can
be
at
the
beginning
like
for
just
to
like
start
getting
it,
it
could
be
just
links
that
people
put
in
a
link
into
the
docs
to
some
other
github
repo
and
down
the
work
down
the
road
when
this
starts
to
grow.
Hopefully-
and
there's
more
examples,
then
something
like
a
tecton
hub,
which
has
you
know
the
whole.
D
It
also
removes
any
burden
of
testing
or
anything
like
that
from
the
cartographer
team
or
any
responsibility
of
this
stopped
working,
because
there
was
a
change
and
it
wasn't
updated
with
the
new
version
of
cartographer,
whatever
it's
not
hosted
under
the
cartographer
org,
it's
just
linked
to
under
like
community
resources,
and
then
that
takes
away
some
level
of
you
know.
D
B
A
Right,
I
think
we
need
a
story
for
this
who
would
like
to
write
a
brief
issue
about
this.
B
B
Our
project
board
spans
all
of
them,
the
github,
the
new
github
projects
are
quite
neat
and
their
ability
to
view
across
multiple
repos.
B
B
I'm
not
aware
either,
but
it
definitely
should
be
yeah
I'll.
Try
and
remember
to
do
that.
I
don't
have
a
note
card.
A
All
right,
yeah
next
will
be
to
reveal
standing
rfcs.
I
don't
know
if
we
should
do
this
right
away.
I
don't
think
so
right.
I
think
it's
worth
skipping.
B
Unless
cora
or
scott
feel
particularly
inclined,
I'd
like
to
see
a
much
bigger
turnout
for
the
next
time,
we
discuss
rfcs.
A
B
I
don't
know
how
to
allay
any
anxiety
it
might
be
causing
other
people
cora.
Hopefully
they
pick
up
on
the
notes
from
this
meeting.
If
they're
anyone's
concerned.
A
Yeah
feel
free
to
check
out
the
rfp
board.
You
know
add
comments.
If
you
need
cool
okay,
yeah
next
up
will
be
the
computer
of
the
month.
Remember.
This
is
something
we
do
at
the
beginning
of
every
month
to
try
to
recognize
every
type
of
contributions
from
users
out
there.
A
This
time
we
have
may
large
she's
being
she
not
only
sent
a
pr
backing
temporary
to
improve
one
of
the
examples.
The
git
rider
examples
to
be
specific,
but
besides
that
she's
been
creating
demos
and
yeah
helping,
you
know,
spread
the
word
about
the
project
explaining
the
and
demoing
the
project
out
there
to
users
and
customers
in
the
field.
A
Cool
all
right
seems
like
that's
it
in
terms
of
the
agenda.
Is
there
anything
else
you'd
like
to
discuss
or
share
here.