►
From YouTube: GitLab Terraform provider community hours
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
A
A
B
B
D
D
A
C
I
recommend
to
get
started
so,
first
of
all,
o
everyone
and
thanks
for
joining
the
community
of
SARS.
C
There
are
four
of
us
from
gitlab
all
from
the
configure
team
and
we
are
behind
developing
gitlab
scrubets
Integrations
and
infrastructures
code
Integrations
and
we
own
the
telephone
provider
as
well
and
so
I'm
the
product
manager
on
the
team.
I,
don't
know
where
the
others
are
within
your
Zoom
window,
but
Place
everyone
from
the
team.
Let's
quickly
introduce
ourselves
just
to
get
started.
D
Yeah
sure
yeah,
my
name
is
Timo
I'm,
the
main
maintainer
or
what's
the
main
maintainer
up
until
now
from
the
provider
I
recently
joined
gitlab
and
yeah
Charles.
You
want
to
continue.
E
F
Hey
my
name
is
Hunter
I
joined,
get
lab
seven
or
eight
weeks
ago,
so
I'm
here
to
learn
and
see
how
we
fix
our
safeties
meetings
and
yeah.
D
Yes,
I
do
so
yeah.
The
first
thing
is
that
we
moved
to
meetup.com,
which
you
probably
noticed,
because
we
before
we
just
had
like
a
standing
Google
calendar,
invite
which
is
kind
of
cumbersome,
so
I
think
that
was
a
success.
I
thought
more
will
be
joining
since
a
lot
of
people
RSVP
in
Meetup,
but
yeah
I,
I'm,
just
double
checking.
If
the
URL
there
is
actually
corrective
to
zoom
but
or
maybe
if
someone
else
can
quickly
do
this
in
the
background
and
then
I'll
continue
here.
E
I
came
from
the
zoom
okay
meeting
from
the
well,
the
URL.
That's
in
the
calendar
in
me
is
it
yes,
yeah,
okay,.
D
We
also
want
to
move
to
the
Discord
of
gitlab
there's
like
an
official
one
and
before
we
had
an
a
separate
one,
so
I
think
we'll
we'll
be
discontinue
this
in
I,
don't
know
the
next
week
or
something
I,
don't
know
Victor
what
your
plans
for
plans
were
when
you
created
it,
but
for
me
I
think
we
should
discontinue
the
old
one
as
soon
as
possible
and
just
redirect
people
to
the
new
one
yeah
to
avoid
confusion
and
also
make
it
easier
for
us.
D
Okay
and
then
the
third
thing,
which
is
probably
the
one
which
is
the
biggest
one,
at
least
from
an
announcement
point
of
view,
is
that
we
will
move
the
the
gitlab
terraform
provider
repository
from
GitHub
to
gitlab
and
will
only
accept
contributions
there
and
all
the
development
will
be
happening
there.
We'll
keep
the
GitHub
repo,
though,
because
it's
the
only
way
to
actually
deploy
a
terraform
provider
to
the
registry.
D
So
we
will
be
thinking
the
releases
from
gitlab
over
to
GitHub
when
we
create
a
release
so
that
it
will
be
yeah
released
from
there
to
the
to
the
registry.
There
is
an
epic
Link
in
the
notes
where
you
can
follow
if
you
like
to
from
our
progress
and
there's
a
few
issues
associated
to
this
Epic
yeah,
which
details
like
our
migration
plan
in
terms
of
timeline.
D
I
can't
really
tell
yet
when
this
will
be
finished
or
when
we
make
the
cut,
but
I
expect
it
not
to
be
in
the
far
future
rather
like
in
the
next
one
or
two
weeks,
because
we
have
a
lot
of
things
already
lined
up
and
prototyped,
and
it
looks
actually
all
quite
good.
D
So
far,
but
if
you
have
any
doubts
or
comments
or
wishes,
I'm
happy
to
hear
about
them
or
you're
happy
to
hear
about
them
and
make
sure
it
works
out
for
all
of
us
and
not
that
it's
just
that
we
just
solve
our
needs.
D
So
if
you
have
anything,
let
us
know
there's
also
a
GitHub
issue
pinned
to
the
Repository
which
I
I
try
to
keep
updated
with
some
progress
from
the
Epic
in
on
the
lab,
so
yeah,
if
you
I,
don't
know
if
you
have
any
comments
now
or
or
anything
or
maybe
you've
you've
seen
this
happening
for
other
providers
that
also
I
I
search
a
little
bit,
but
I
haven't
seen
any
so
if
you
know
about
anyone,
let
us
know.
B
Yeah,
my
topic
is
not
really
a
topic
more
like
a
question
about
how,
because
I'm
relatively
new
to
kubernetes
and
I,
never
use
terraform,
so
I,
today,
I
joined,
mostly
because
I
wanted
to
have
a
look
at
how
it
works,
how
what
it
does
and
things
like
that
to
get
some
insight,
if
that's
possible
during
this
office
Oracle.
Otherwise
it's
it's
nice
to
be
here
anyway.
D
No,
it's
absolutely
possible.
I
mean
like
terraform
works,
that
you
have
different
providers
for
different
kind
of
infrastructures
right
and
this
provider.
We're
working
on
is
just
to
manage
GitHub
infrastructure
and
configuration
so
meaning
that
you
can
write
some
terraform
code,
which
is
like
a
declarative
way
of
describing
some
infrastructure
and
you
could,
for
example,
you
could
describe
how
a
project
should
look
like
on
gitlab,
and
if
you
execute
this
declarative
code
with
terraform,
it
will
check
the
state
on
gitlab
and
basically
reconciles
it
to
the
same.
D
D
If
you
read
me,
then,
if
you
execute
this
with
terraform,
it
will
actually
create
that
project
as
you
described
it,
and
we
basically
have
resources
for
all
kinds
of
API
endpoints
from
gitlab,
so
you
know
creating
users
creating
projects
groups
whatever,
and
if
there's
one
missing
like
you,
could
you
could
ask
us
to
implement
this?
You
can
implement
this
yourself
like
that.
That's
basically
like
the
the
contributions
to
the
provider.
B
Yeah,
it
doesn't
make
sense
and
I
totally
misunderstood
what
terraform
managed,
because
I
on
our
kubernetes
environment
I
thought
that,
for
example,
they
get
lab
kubernetes
agent
manage
the
deployment
to
the
kubernetes
cluster,
but
the
telephone
provider
managed
the
infrastructure
where
that
cluster
got
the
got
generated
basically
start
from
the
United
cluster,
and
then
the
agent
deploys
the
application
exactly.
D
Exactly
so,
you
could
also
use
terraform
with
a
kubernetes
provider
to,
for
example,
make
sure
that
some
namespace
exists
or
even
any
kind
of
manifest,
but
in
general
like
terraforming.
Yes,
it
really
is
like
infrastructures
code.
So
you
describe
your
infrastructure
like
a
eks
cluster
and
then
you
would
use
the
agent
and
and
pull
some
you
know
with
the
github's
flow
pull
some
manifest
from
a
git
lab
Repository.
B
D
So
yeah
I
I
know
about
a
lot
of
users
who
basically,
for
example,
they
want
every
project
to
kind
of
look
the
same
in
a
certain
way
to
have
the
same,
protected
branches,
the
same
members
and
so
on,
and
they
use
terraform
to
manage
that
in
like
a
centralized
infrastructure
of
code
way,
so
so
that
you
don't
have
wild
west.
On
your
gitlab
instance.
Basically,.
D
Yeah
yeah
I
think
a
lot
of
people
are
doing
it
either
manually
by
some
kind
of
procedure.
They
document
it
or
they
actually
use
shell
scripting,
which
I've
also
seen
a
lot
they're
like
custom,
tooling
written
and
go,
or
these
kind
of
things
I
see
this
a
lot
and
yeah.
D
There's
probably
also
benefits
to
that,
but
in
general,
like
it
makes
your
life
way
easier.
If
you
have
this
as
code,
you
can
also
you
know,
the
change
management
is
much
easier
right.
You
can
just
create
a
merch
request
to
your
replay
and
basically
request
a
new
project
for
you
or
these.
These
kind
of
things.
G
So
I'm,
given
that
is
it
possible
to
make
a
demo
like
we've,
been
tightening
Discord
that
the
filing
terraform
in
GitHub
project,
which
is
terraform
scenario,
will
modify
the
projects
when
it's
merged.
Basically,.
D
So
this
I
think
this.
If
I
understood
you
correctly,
this
would
mean
that
you
would
have
a
pipeline
which
basically
runs
terraform,
and
you
would
then
request
some
changes
or
you
yeah.
You
have
a
change
in
the
terraform
code
which,
when
merged
will
run
the
pipeline,
and
then
you
have
some
new
infrastructure,
yeah.
G
C
If
you
want
I
can
I
can
quickly
share
you
one
of
my
projects,
which
is
a
pretty
cool
one
for
to
Showcase
these
things
I
think
it's
not.
It
won't
be
a
full
demo,
because
I
won't
set
it
up
and
so
on,
but
at
least
it
gives
you
an
idea
what
it
does.
C
Basically,
it
creates
a
new
project
for
every
item
in
that
project
CMO,
and
it
doesn't
a
way
that
it
creates
the
project
and
then
sets
up
the
membership
to
both
my
gitlab
user
and
my
personal
user,
so
that
I
I
don't
have
to
switch
accounts.
All
the
time
and.
C
It
sets
up
an
access
token
in
a
in
the
red.
I
have
a
renovate
book
project
that
keeps
all
my
projects
up
to
date
all
the
time
and
it
basically
runs
from
environment
variables,
the
environment
based
on
the
environment
variable
it
knows
about
the
projects
that
it
should.
It
should
look
at
and
it
sets
up
a
project
access
token
and
the
environment
variable
in
the
currently
created
project
and
in
the
renovate
project.
C
C
So
we
have
something
called
the
gitlab
managed
which
are
from
state,
which
is
an
HTTP
State
backend
for
transform.
If
you
know
a
bit
more
about
terraform
than
so
that's
one
type
of
a
backend
and
it
doesn't
need
much
initialization.
If
you
use
this
from
gitlab
CI,
because
in
gitlab
CI
we
pre-configure
all
the
environment
variables
for
that
specific
project
and
so
on,
and
that's
how
it
it
just
uses
the
state
itself,
which
encode
means
that
I
have
I
use.
The
built-in
latest
template
for
terraform
and
the
projects
are
actually
here.
C
C
The
state,
based
on
your
questions,
you
know
what
form
how
terraform
works.
I
could
download
the
Json
of
the
states,
but
there
is
no
way
to
say
it
on
the
screen,
the
post.
What
what
you
could
do
is
in
the
merge
request.
Let's
see
one.
C
Yeah
I
think
this
would
work.
We
have
a
merge
request,
integration,
that's
now
loading
telephone
reports,
as
you
can
see,
and
it
shows
that
one
Report
was
generated
that
adds
seven
things:
zero
to
change
and
one
to
delete
and
I
could
open
the
full
log
that
I
don't
want
to
do
now
because
I
don't
know
what's
in
the
log
and
the
mrb
credentials,
but
basically
that
shows
you
the
terraform
output.
C
G
G
C
D
Yeah
but
I
mean
probably
the
CI
chop,
token
won't
help
and
the
examples
you
gave
because
it
has
very
limited
access
to
things
like
releases
or
uploading
archifects
and
these
kind
of
things,
but
changing
the
project
itself.
You
would
need
to
create
a
project
access
token
manually.
Add
it
as
a
CI
CD
variable,
and
then
you
have
it
available
in
your
in
your
terraform
code.
G
Yeah
I
had
other
questions
like
related
to
the
selling.
All
the
properties
that
are
not
set
like
if
I
try
to
modify
only
descriptions
and
I
submit
terraform
scenario,
with
only
description
terraform
still
tries
to
you
know,
refer
some
some
properties
to
default.
At
least
it
was
like
two
years
before
when
I
tried
it
with
the
GitHub
project.
C
As
a
result,
if
you
don't
specify
all
the
properties
of
your
project
and
from
doesn't
have
any
default
set,
even
if
your
project
has
those
things
set
up,
it
will
just
fail.
First,
you
have
to
import
your
project
under
travel
and
afterwards,
if
you
have
set
some
customizations
that
are
non-default
and
you
don't
provide
those
values
with
the
terraform.
Therefore
we
just
want
to
overwrite
them
to
to
get
back
to
a
default
value.
C
D
And
I
think
in
the
case
where
you
want
to
change
your
own
project,
there
is
no
way
around
an
import
yeah
because
of
there's
like
a
chicken
and
egg
issue,
especially
I
mean
only
actually,
if
you
want
to
stay
to
store
the
state
in
gitlab
itself
inside
the
project,
I
think
other.
If
you
would,
if
you
would
store
the
state
somewhere
else,
you
could
actually
do
this,
but
just
locally
like
running
terraform
and
then
with
creating
the
project,
basically
committing
the
code
itself
to
that
project.
D
C
D
E
Let's
just
I
think
some
people
reported
that
they
could
only
log
in
with
the
zoom
link
inside
the
agenda.
I
posted
on
the
meeting
meet
up
page
two,
but
I
think
we
need
to
update
this.
Then,
if
you
cannot
login
with
the
calendar
event.
H
Yeah,
the
one
on
the
the
Meetup
event
required
a
passcode.
So
if
you
just
replace
that
link
with
the
one
in
the
dock
that
one
worked
for
me.
C
Cool
Ryan,
you
missed
the
very
beginning,
so
we
are
in
the
process
of
migrating
to
report
to
gitlab.
Actually,
Timo
works
on
it
mostly
I
think
but
yeah.
H
Is
that
happening
within
the
next
month
and
did
we
figure
out
the
push
to
the
registry?
I
know
that
was
one
of
the
pain
points
pushing
to
the
dashboard
registry.
D
Yes,
so
we
figured
this
out.
I
figured
this
out
at
least
one
way,
and
it
is
that
we
keep
the
GitHub
repo
and
we
sync
the
releases
made
from
gitlab
to
GitHub
and
from
there
like,
the
normal
terraform
registry
pushes
or
like
releasing
is
basically
happening,
but
the
GitHub
repo
will
be
completely
locked
down.
So
you
couldn't
you're,
not
basically
allowed
to
create
a
an
issue,
because
the
tab
is
not
even
there,
I
think
and
for
pull
requests.
H
D
D
Yes,
do
you
have
anything
else,
any
other
like
doubts
or
anything,
I
mean
you've
been
contributing,
and
is
there
anything
you
can
think
of.
H
H
D
E
A
D
Quickly
check
but
I
think
it's!
Okay!
If
it's
like
you
know,
open
sourcing,
we
just
have
a
bot
basically
closing
in
PRS.
H
D
H
A
I
Now
I'm
super
super
excited
for
it.
We
finished
earlier
actually
just
a
couple
months
ago,
our
full
migration
off
of
GitHub,
so
okay,
I'm
I'm
excited
to
be
able
to
use
one
account
for
everything,
including
open
source
contributions.
So.
D
No,
no
I
mean
there
was
nothing
on
the
agenda.
Do
you
have
anything
you
wanna.
H
Oh,
nothing
I
was
just
wondering
when
we
should
plan
to
do
it,
because
I
know
that
we
have
some
things
like
refactoring
and
other
things.
We
want
to
do
breaking
changes,
I'm,
not
sure
when
we
were
planning
on
I
think
we
were
we
going
to
create
a
parallel
Branch
to
do
some
of
these
changes
in
and
then
merge
into
time.
D
D
I
think,
let's
finish
the
migration
and
then
maybe
we
can
start
tackling
the
next
big
thing,
which
probably
is
this
4.0
4.0
release?
Maybe
for
the
others
like
we,
we
have
some
breaking
changes
coming
up
for
the
provider
just
because
a
lot
of
resources
have
issues,
especially
in
the
IDS
which
prevent
us
from
doing
a
few
things
and
yeah.
D
This
4.0
release
would
basically
or
the
idea
is
to
allow
us
making
breaking
changes
for
once,
which
we
normally
don't
do
and
I
I
did
create
a
bunch
of
issues
already
associated
with
4.0
release,
but
yeah.
Nothing
really
concrete
about
how
we're
gonna
roll
that
out
or
even
work
on
this.
If
I
think
I'll
create
an
epic
or
an
issue
on
gitlab,
once
you
migrate
it,
and
then
we
can,
we
can
start
discussing
the
discussing
there
what
what
some
good
ways
will
be
if
that's,
okay,.
D
And
actually
with
that,
like
another
thing
that
comes
to
my
mind
is
the
new
framework
for
writing.
Terraform
providers-
I'm,
not
sure
if
you
are
aware,
but
right
now
we
are
on
the
SDK
or
terraform
provider.
Sdk
I
think
it's
called
and
there
is
a
different
provider
framework
which
is
in
like
a
beta
state
or
something
which
would
solve
a
few
issues.
We
have
and
probably
probably
would
unblock
us
from
implementing
a
few
nice
things
like
we,
for
example.
D
We
have
these
issues
that
if
we
have
a
like
a
list
inside
of
a
resource,
it's
not
ordered
I
think
so
you
basically
have
to
always
provide
it
in
the
same
order.
Otherwise
it
will
have
changes,
and
these
kind
of
things
and
I
think
the
new
framework
would
actually
allow
us
to
do
this,
but
yeah
if.
H
You
know
as
much
as
I
do
is
I
just
look.
I
was
looking
at.
It
was
in
beta
and
basically
like,
like
stable,
beta
I
would
say
because
they
said
that
if
you
have
a
brain
in
the
documentation,
it
says
if
you
have
a
brand
new
provider,
it's
probably
best
to
go
with
the
new
framework.
But
if
you
have
something
existing,
it's
probably
best
to
stick
around
with
the
stable
SDK
for
now,
but
so
I'm
curious.
What
it
looks
like,
though,
if
we
were
to
migrate
that
would
solve
some
of
the
issues
we
have.
D
I
D
D
We
also
haven't
been
upgrading
or
updating
our
test
Matrix
to
the
latest
gitlab
releases,
so
I
was
on
vacation
and
onboarding
and
these
kind
of
things.
So
that's
why
I
haven't
been
really
active
the
last
few
weeks,
but
I
think
it
would
be
nice
to
to
update
those
in
the
in
the
coming
weeks
or
whatever,
basically
as
soon
as
possible.
If
anyone
has
time
I
think
will
be
very
nice
too.
H
That
one
thing
to
know
is
when
we
move
to
gitlab
as
well.
We
can
Auto
generate
those
latest
three.
Those
latest
three
values
from
like
the
releases
page
like
we
could
scrape
it
and
then
just
like
look
at
the
blog
posts
and
calculate
it
from
there.
So
we
never
have
to
make
a
code
change
then,
for
the
latest
three
releases,
don't
think
you
can
do
that
kind
of
fancy
work
with
GitHub,
but
with
gitlab
I
know
it's
possible.
Do
that
easily.
E
D
I
also
see
that
a
lot
of
like
checks
are
failing,
especially
for
ee
instances.
I
don't
know,
what's
going
on,
did
anyone
look
at
this.
I
I
I
saw
the
same
thing.
That
was
something
that
I
had
planned
to
look
at
this
weekend,
because
I
saw
a
bunch
of
ee
failing
checks
after
I
re-based
just
to
get
that
suppressed
if
taken
care
of
and
I
looked
at
that
and
went
those
aren't
caused
by
the
current
pull
requests.
I
Just
got
a
flag
to
look
at
that
this
weekend,
when
I
had
a
little
bit
more
time
to
dig
into
it.
D
Yeah
I
quickly
look
on
the
failure
yesterday,
I
think,
and
it
said
that,
like
the
featured
code
owner
approvals
is
not
available
or
something
like
that,
so
I
I
don't
know,
and
it's
for
all
the
ins,
it's
for
all
the
the
like
the
versions,
We
test
against
so
I'm,
not
sure.
What's
going
on
to
be
honest,
it's
kind
of
weird.
D
E
F
D
D
I
D
Tried
this
and
it
didn't
work-
and
we
just
pointed
them
to
gitpod
but
yeah
I,
something
I
mean
there
is
an
issue
on
gitlab
actually
and
it's
about
like
releasing
Omnibus
Docker
instances
for
arm,
which
I
think
would
be
the
proper
solution.
There
is
enough,
like
unofficial
images
on
Docker
Hub
and
those
work
with
kulima
and
podman,
so
yeah.
I
That
would
make
sense,
because
Docker
desktop
does
a
lot
of
the
arm
to
x86
emulation.
I
So
if
you
run
it
through
desktop
you're,
probably
running
it
as
an
emulated,
Docker
container,
so
but
I
would
say
at
least
for
now
for
development
just
to
make
it
as
stable
as
possible.
Like
you
said,
Teemo
until
there's
an
official
arm
image,
I
would
just
point
most
M1
users
to
get
pod,
and
once
we
get
that
becomes
even
easier
to
do
once
we
get
the
migration
to
get
lab
done,
because
our
instructions
are
literally
set
up,
get
pod
in
your
gitlab
account
and
go
so
yeah.
Yes,.
D
Yeah
I
also
think
that
for
like
more
advanced
contributors
or
even
people,
working
at
Gate
lab
or
contributing
to
gitlab,
those
can
also
use
GDK
to
test
against,
which
may
not
be
exactly
the
same
thing
as
if
you
would
test
against
the
docker
instance.
But
I
think
it's
a
good
like
mitigation.
Until
we
have
a
solution
for
M1.
I
D
I
Sorry
before
I
joined
did
we
cover
number
five
Marco
had
left
a
question
about
like
kubernetes
and
terraform.
D
Yes,
we
did
no,
we
did
and
and
Victor
showed
some
nice
demo
of
one
of
his
personal
projects.
I'm
sure
you
can.
You
can
look
at
the
recording
if
you're
interested,
but
actually
like
about
that
I
think
it
will
be
awesome
to
have
something
like
that
in
a
guide
section
in
the
terraform
provider,
Docs
there's
a
lot
of
providing
stuff
like
an
additional
section
to
data
sources
and
resources
which
is
like
guides
which
have
like
examples
of
you
could
use
this
provider
in
this
way
to
create
your
project
and
I,
know
I.
D
I
D
Yeah
I
think
it
would
be
awesome
to
kind
of
incorporate
some
pointers
to
that
in
the
docs
or
whatever
I
think
every
bit
of
information.
There
makes
it
more
approachable
and
kind
of
give
people
ideas
on
how
to
use
it,
because
if
you
just
see
resources,
maybe
it's
hard
to
kind
of
throw
for
a
beginner
to
know
what
they
can
do
with
that
like
how
powerful
it
could
be,
and
so
on
so
yeah.
I
Got
it
and
it
sounds,
there's
a
there's,
a
question
in
chat
as
well
sounds
like
Marco's,
maybe
having
trouble
talking,
which
is
perfectly
fine,
but
yeah
managing
groups
and
projects
not
manually.
I
That's
something
that
we
do.
We,
we
being
my
my
company
completely
through
terraform
as
well,
so
we
use
the
the
terraform
provider
for
that,
along
with
assigning
permissions
not
manually
as
well
so
yeah,
probably
a
good
to
teamless
point,
maybe
like
an
examples.
Folder
that
has
some
specific
call,
outs
and
and
common
use
cases
so
certainly
like
a
kubernetes
common
use
case
would
probably
be
good,
but
I
have
to
imagine
that
groups
and
permissions,
and
especially
now
that
the
saml
group
link
is
available.
I
D
Yeah
yeah
and
regarding
the
like,
bringing
already
existing
resources
into
terraforms,
State
I
know.
This
is
a
big
issue
right,
because
if
you
want
to
have
everything
in
terraform,
then
it's
a
lot
of
manual
Imports
and
these
kind
of
things.
So
at
my
last
job,
I
actually
wrote
a
little
shell
script
to
scrape
the
gitlive
API
and
try
to
transform
that
into
terraform
code
and
also
import
commands.
D
So
I
can
see
if
I
can
kind
of
polish
that
a
little
bit
and
also
add
it
somewhere
there
because
I
think
it's
it's
an
issue.
A
lot
of
people
have
and
it's
cumbersome
to
do
this
manually.
D
Right
cool
down
yeah,
let's
call
today
thanks
for
joining
and
sorry
for
the
troubles
with
the
link
in
in
the
Meetup
event,
we'll
make
sure
this
doesn't
happen
anymore
for
the
coming
one
I
think
I
like
what
is
your
opinion?
Should
we
have
one
in
a
month
I
think
we
had
it
monthly
but
then
basically
didn't
have
them,
because
people
were
not
available,
but
should
we
continue
if
that's
scheduled
by
default
and
see
how
people
RSVP
in
in
the
event
or
what
do
you
think.
I
I
I,
like
monthly
I,
worry
if
we
go
anything
longer
than
monthly
that
it'll
actually
aren't
attendance
issues
will
actually
increase
because
it
won't
be
kept
sort
of
top
of
mind
for
folks,
so
I
I,
like
monthly,
still.
E
Cool
I
think
the
fact
that
we
still
have
like
a
couple
minutes
left
a
few
minutes
left
also
say
that
we
were
able
like
to
answer
all
the
questions
and
it's
like
a
healthy
level,
also
like
as
a
major
game.
So
it
sounds
good
during
this
time.
D
Cool
I'll
make
sure
to
set
up
the
invite
I
think
we
can
do
recurrent
invites
on
meetup.com
actually
so
yeah
thanks
for
joining,
and
it
was
a
pleasure
and
I
hope
to
see
you
next
time.