►
Description
This special interest group is focused on finding ways for engineers that support Drupal to collaborate on a common set of operators and helping the community solve issues that arise when running Drupal on Kubernetes — as always, full transparency and avoiding vendor lock-in will be top of mind.
Full chat log: http://bit.ly/3qbqJKz
Catch up with the group on GitHub: http://bit.ly/338dXC5
A
The
cord
on
this
computer,
so
I'm
gonna,
kick
it
off
real,
quick
just
because
I
think
that
there's
a
good
opportunity
to
collaborate
on
some
of
the
stuff
that
we
need
to
think
about
as
we
approach
hosting
Drupal
and
kubernetes.
So
the
basic
outline
for
what's
kind
of
on
the
agenda
so
far
as
has
been
recommended
from
the
slide
channel,
essentially
is
in
the
chat
box.
A
I'm
assuming
that
zooms
going
to
pick
that
up,
but
we'll
see
so
basically
there's
a
couple:
different
ideas
about
how
to
go
about
open
sourcing,
a
components
of
what
we're
going
to
use
to
host
Drupal
in
different
ways.
It's
a
common
problem
that
a
lot
of
people
are
going
to
end
up
hitting
so
kind
of
get
the
sense
that
it
might
be
good
to
start
a
conversation
around
how
we're
gonna
do
that
and
what
that
actually
means.
So
I
I,
don't
know
Jason.
Do
you
have
any
ideas
or
anything
that
you'd
like
to
say.
B
Yeah
I
think
the
the
the
absolute
minimum
to
look
at
here
is
I
think
we
can
borrow,
but
we
can
borrow
bit
off
the
model
of
the
kubernetes
project
itself,
where
we
have
enough.
We
have
upstream
kubernetes
owned
and
managed
by
the
Carnegie
Foundation,
which
has
a
fairly
well
thought-out
governance
process.
B
So
I
would
say
one
high-level
goal,
I
would
say
is
we
should
we
should
look
at
defining
and
at
the
very
least,
a
set
of
API
resources
which
any
anyone
can
run
like
a
open
source
operator,
controller
implementation
of
and
to
back
up
a
little
bit
when
I
talk
about
operators
and
controllers
tend
to
be
used.
Interchangeably
operator
really
defines
the
not
you
know
an
automation
processes
around
running
a
application,
so
a
Drupal
operator
on
my
sequel
operator
is
the
term
there
and
then
the
other.
B
B
The
you
know
that
that's
common
for
whether
or
not
you're
hosting
Drupal
yourself
on
your
own,
your
Benes
cluster,
or
if
you
are
using
a
hosting
provider
that
it
seems
based
now
on
just
talking
with
other
other
providers,
that
kubernetes
is
either
already
being
used
extensively
to
host
Drupal
or
there
is
or
is
being
rapidly
adopted
so
either
yeah.
The
providers
are
either
using
it
already
or
moving
towards
it.
B
B
You
know
it's
cloud
provider
agnostic
for
the
most
part,
someone
who
really
wants
who
would
want
us
to
go
and
manage
a
full
platform
or
an
operator
on
their
own
and
their
own
kubernetes
cluster
could,
of
course,
use
this
to
hose
through
blown
kubernetes
in
a
sustainable
pattern,
but
then
for
providers
hosting
providers
that
had
that
wants
to
be
able
to
customize
how
they
implement
that
API
object
to
a
degree
whether
or
not
they
are
using
a
different
storage
provider.
A
different
cloud
provider
is
able
to
to
either
make
modifications
to
the
open
source
controllers.
B
B
That
makes
it
one
thing
I,
think
everyone
and
all
of
the
hosting
providers,
I
think
could
potentially
really
benefit
from
is
to
make
vendor
lock,
not
a
huge
part
of
a
customer's
decision,
and
that
is
one
of
the
other
big
goals
of
cloud
native
foundation
was
to
address
that
too,
and
by
addressing
that,
you
know
like
the
enterprise
space,
especially
is
moving
far.
You
know
at
a
quicker
pace
into
the
cloud
because
they're
not
sitting
there
scared.
A
A
You
know
the
potential
benefits
of
looking
at
a
set
of
API
resources
that
anyone
can
run
an
open
source
operator
and
controller
of
that
kind
of
defines
what
Drupal
is
and
for
me,
I
think
that
has
a
lot
of
benefit
and
kind
of
maybe
both
ways,
because
another
just
random
quit
link
that
I.
Think
Jeff
was
starting
to
put
together
by
tagging
issues
in
Drupal
that
are
related
to
issues
that
different
providers
are
going
to
eventually
run
into
even
people
that
are
hosting
or
running
their
own
clusters,
and
if
we
can
nice
mccann.
A
So
so
really,
you
know
I
know
that
there's
a
lot
of
people
that
are
very
opinionated
on
how
these
problems
should
be
handled
and
I'm.
Not
quite
sure,
really
how
to
navigate
it.
So
really
the
the
point
of
this
meeting
is
just
to
say,
hi
and
and
and
start
thinking
about.
You
know
what
this
group
could
potentially
do
or
what
this
group
should
do
and
I
know
that
you
know,
as
an
organization
we're
pretty
dedicated
to
helping
a
play
as
much
as
we
can
to
making
this
work
so
yeah.
B
C
Know
one
of
the
things
that
you
hadn't
mentioned
was
the
the
move
towards
kubernetes,
I,
2
or
2
or
so
years
ago
was
when
I
first
started
looking
into
it
seriously.
Last
year
was
the
first
time
I
started,
building
actual
stuff
on
it,
but
in
that
time
it's
kind
of
ridiculous.
How
quickly
a
lot
of
like
cloud
providers
software-as-a-service,
those
kind
of
things
started,
picking
it
up
and
it's
kind
of
cool,
because
for
the
first
time
since
forever,
there's
like
a
new
technology.
C
If
you
think
Drupal
is
difficult
or
horrible
or
the
community
has
issues,
you've
never
worked
with
Magento,
definitely,
and
but
a
lot
of
the
problems
are
similar
and
the
more
we
can
solve
some
of
those
problems
and
have
some
best
practices
or
even
make
it
to
the
codebase
itself,
so
that
Drupal
itself
is
really
easy
to
run
as
a
quote/unquote
12
factor
app.
Basically,
an
app
that
is
easy
to
run
in
kubernetes
or
in
docker
or
wherever
you
want.
That's
going
to
be
it'll
continue
that
kind
of
tradition
of
Drupal.
B
Yeah
I
think
that's
a
really
really
great
point:
they're
adapting
Drupal
to
run.
You
know
in
the
new
cloud
native
paradigm,
getting
Drupal
at
least
the
the
web
container
to
to
where
it's
stateless
and
follow
those
better
practices.
It
would
be
a
massive
win
just
for
the
community,
because,
yes,
I
mean
this.
This
is
because
is
is,
is
rapidly
moving
towards
being
the
de
facto
way
to
deploy
applications
in
general.
B
So,
even
even
for
our
users,
who
aren't
thinking
too
much
about
kubernetes
right
now,
they
may
be
challenged
with
this
at
a
very
inconvenient
time.
I
think
maybe
a
comparison
there
could
be.
You
know
so
users
who
aren't
very
proactive
about
making
sure
that
they're
there
they're
keeping
their
their
pH
their
codebase
and
PHP
version
up-to-date
and
wait
until
the
end
of
life
or
the
the
the
six-month
after
end
of
life,
part
two
for
it
to
be
a
crisis
and
and
react
to
it
rather.
D
B
C
Yeah
yeah
I
actually
just
got
off
a
meeting
where
we
spent
about
an
hour
talking
about
that
particular
problem.
Now
we're
using
EFS
for
what
we're
currently
building
and
it's
working
pretty
good.
It's
a
little
slow,
sometimes
for
certain
things,
but
and
but
we're
in
habeas.
If
you're
not
in
a
be
us,
you
don't
have
the
FS
and
you
might
have
something
else.
B
B
You
know,
we've
got,
we've
been
working
on
an
implementation.
That's
now
using
the
new
Google
file
store,
so
their
equivalent
of
it,
but
yeah
NFS
is,
is
quite
limiting
and
if
you
want
to
run
more
than
one
pot,
of
course
you
then
they
get
there
have
to
you,
don't
want
NFS,
you
have
to
choose
Gloucester
or
set
up
us
at
that
point.
B
B
C
You
just
need
to
tell
your
users
to
not
do
stupid
things.
That's
the
problem
with
that.
All
these
cloud,
hosting
providers
always
have
is
the
users.
The
problem
is
always
the
users,
of
course,
but
one
thing
that
I
did
talk
about
in
our
meeting
that
I
just
had
and
something
I'd
heard
of
before,
but
never
really
looked
into.
But
report
works
no.
C
No,
if
you've
investigated
that
much
but
I
believe
they
might
be
a
paid
product,
but
I
think
that
they
have
some
way
of
using
like
EBS
packed
volumes
or
in
Google
Cloud
Google,
Cloud
volumes
or
whatever
they're
called
and
using
those
shared
some
other
protocol.
Besides
Ana
fest,
that's
supposedly
way
faster,
I,
don't
know
about
that,
but
it
was
something
that
I
was
definitely
like,
who
that
would
be
really
cool
if
that
actually
works
really
well.
C
D
On
the
hosting
platform
that
it
worked
on
previously,
they
used
port
works
and
I
could
say
towards
the
end
of
my
time
there.
The
goal
was
to
get
off
of
port
works
and
we
yeah.
It
was
a
paid
service
and
we
were
utilizing
their
support
and
their
engineers
as
much
as
possible
and
I
mean
port
work
specifically
was
the
cause
of
numerous
outages,
but
I
guess.
The
scale
of
the
platform
was
pretty
large.
I
mean
it
was
something
like
10
or
20
thousand
sites
by
time.
I
left.
C
B
C
I
mean
that
that's
the
difficulty
that,
like
an
NFS,
is
usually
the
simplest,
but
it's
also
in
in
some
situations
the
slowest.
Unless
you
can
really
lock
down
the
types
of
sites
you
run
and
they
they
only
upload
small
files
and
they
don't
do
a
ton
of
stuff
and
their
themes
don't
have
zillions
of
twig
files.
So
it's
like
that's
the
slowest
but
easiest
and
can
work
in
some
use.
Cases
Gluster
and
Saif
are
both
a
little
faster,
but
still
not
like
you're.
C
Never
gonna
approach
like
same
system
disk
speed
but
they're
a
little
faster,
but
they're
more
complex,
operationally
and
then
there's
like
the
hosted
solutions.
The
hardest
thing
is
like
I,
believe
on
Google
cloud,
but
this
can
be
right
many,
but
on
AWS
the
EBS
volumes
cannot
have
more
than
one
one
pod
right
to
it.
So
automatic.
B
B
C
C
B
A
good
question
I
think
he
FS
was
meant
to
sort
of
fill
that
gap,
but
not
be
there
completely.
Rumor
has
it
that
by
s3
I
have
not
been
able
to
confirm
that.
So
that's
not
a
fact,
but
it
explains
some
things
that
we
think
not
to
mention
there's
only
so
you
can
only
make
that
EFS
perform
so
well
so
say
they
tie
your
I/o
limits
to
to
your
towards
the
most
stuff
you're
storing
there
well.
C
They
actually
didn't
have.
They
now
have
provisioned
access,
so
you
can
say:
I
want
20
megabits
or
100
megabits,
something
like
that,
but
the
price
for
it
is
exactly
the
same
as
writing
a
like
1
terabyte
file.
So
you
can
either
have
it
auto,
expand
performance
with
file
size
or
you
can
upfront
pay
for
whatever
speed
you
want,
but
you
can't
it's
there's
no
way
to
say
like
give
me
burst
capacity
outside
of
writing.
Larger
files.
C
I
actually
just
had
a
separate
conversation
with
our
Atos
rep
and
a
couple
interesting
tidbits
for
anybody
that
does
use
EFS
or
wants
to
I
think
there's
a
hard
limit
per
byte
per
file
system
of
7,000
I,
ops,
total
for
the
file
systems.
So
even
if
you
mount
it
to
like
3,000
servers
and
I
I'm,
not
a
hundred
percent
sure
on
that
it
might
be
per
server
per
like
actual
physical
network
interface
connection,
but
it
might
be
for
the
entire
volume
and
that's
not
a
heck
of
a
lot.
C
B
With
customers
wanting
to
you
know
with
users
wanting
to
do
large,
uploads
and
downloads
that
you
know
bouncing
that
with
with
starting
web
traffic,
you
know
there's
a
lot
of
one
fit
their
needs
to
happen
there
to
make
sure
that
you
know
a
couple
of
large
imports
or
something
like
that
won't
bring
like
a
shared
EFS.
You
know
cause
of
destruction
to
those
actual
sites
just
trying
to
search
traffic.
B
B
C
C
We
still
needed
it
for
one
thing,
but
it
screwed
up
so
many
different
things,
but,
as
time
goes
on,
like
we've
submitted
some
patches
to
some
modules
that
weren't
working
with
it
correctly
and
one
of
those
modules
was
actually
honeypot,
and
then
we,
you
know
through
I,
think
through
that
process,
that
module,
even
though
it's
like
alpha
12,
which
it
really
should
be
like
beta.
At
this
point,
it
was
working
pretty
well
on
the
last
couple
sites
I
built,
but
we
were
kind
of
strict
about
only
using
it
for
certain
types
of
file.
Uploads.
C
Mostly
that
one
of
the
sites
we
used
s3
as
the
file
system
for
basically
all
public
files
and
it
worked,
but
certain
things
in
Drupal
were
a
little
slower
like
after
it
cache
clear
writing
all
the
new
like
I,
guess
it
writes
some
PHP
files
and
the
CSS
and
j/s,
and
all
that
that
it
was
similar
performance
to
the
FS,
which
again
leads
to
your
theory,
which
I
do
not
know
is
where
is
EFS
backed
and
if
it's
backed
by
a
three.
That
would
make
a
lot
of
sense.
B
Yeah,
like
precompiled
biles,
temporary
block,
storage
and
stuff
like
that
can
can
work
better.
It's
just
about
the
trouble.
I
have
and
full
disclosure.
You
know,
I
personally,
don't
have
a
multi-year
sort
background
working.
You
know,
building
something
interval
or
working
on
the
core
I'm
a
cloud
guy.
The
assistance
developer
guy
originally
was
in
Java.
So
the
thing
at
least
from
someone
who's
kind
of
coming
from
the
outside.
Getting
you
know,
learning
so
much
more
months.
Look
at
this
ecosystem!
A
C
C
Somebody
even
outside
of
that,
like
in
I,
am
starting
to
rebuild
some
like
some
of
my
projects
to
use
like
kubernetes
in
the
CI,
so
that
I
can
push
the
containers
out
to
my
production
servers
which
are
using
kubernetes,
which
is
really
easy
and
cheap
on,
like
digital
ocean
and
it'd,
be
really
cool
to
make
that
simpler
and
make
it.
So
you
can
have
a
scalable
Drupal
site
or
a
simple
Drupal
site,
really
quick
and
easy
inside
of
kubernetes.
C
But
to
that
point
to
like
some
of
those
issues
that
you
linked
under
Brad
Jones,
one
in
that
and
the
gist,
some
of
those
would
not
only
help
with
kubernetes,
but
it
would
help
with
so
many
other
things
too.
Like
you
know,
Lando
and
other
local
development
environments
could
be
made
to
be
more
efficient
and
faster
Drupal
setup
and
all
those
things
if
we
could
get
some
of
those
things
done
right.
That's.
A
A
B
A
B
You
know
there
may
be.
There
may
be
folks
that
can't
use
some
of
the
container
based
solutions
out
there,
like
LAN
Toby
dev,
for
whatever
reason,
maybe
they're
running
Windows
7
still
being
able
to
still
have
you
know
a
tool
set
or
be
able
to
have.
You
know
tooling
that
can
go
against
that
common
interface.
B
I
think
gives
that
that
flexibility
to
the
user
to
be
flexible
with
a
local
environment-
and
you
know
this-
what
users
we've
talked
to,
who
have
a
preferred
hosting
promoter,
can
always
use
that
hosting
provider
for
a
particular
client,
so
that
interoperability,
I
think
is,
is
just
everyone
I
think
it's
going
to
benefit
from
it,
and
the
hosting
providers
have
plenty
of
other
things
to
be
able
to
compete
over
that
doesn't
require.
Having
you
know,
100%
of
proprietary
api's
for
everything
on
each
platform.
A
A
Should
it
be
a
project
on
github,
or
should
it
be
the
slack
not
quite
sure
where
the
right
place
to
focus?
This
conversation
is
so
so
currently
I'm
just
going
to
put
this
particular
video
out
on
YouTube
and
just
keep
asking
the
question
until
we
have
a
more
formal
home
so
again,
I
put
that
out
to
the
group
to
see
if
anybody
has
any
ideas,
I.
B
A
B
You
know
we
focus
on
topics
around
making
Drupal
run
on
a
in
a
cloud
native
environment
and
there's
sort
of
like
two
sub
areas.
They're
things
that
should
wouldn't
may
need
to
happen
with
the
Drupal
core
and
plug-in.
You
know:
custom
module
ecosystem,
even
if
there's
things
out
there
like
creating
a
an
analysis
tool
that
can
look
at
a
Drupal
module
in
it
and
report
on
whether
it
can
meet
certain
conditions
that
make
it
run
successfully
in
a
native
environment.
And
then
this,
the
second
part,
is,
you
know
more
focused
on
the
infrastructure
stuff.
A
C
It's
an
interesting
question
like
Drupal,
has
usually
not
really
had
SIG's
in
the
sense
that
the
kubernetes
community
has
and
so
there's
not
really
any
formal
formality.
Usually
it's
it's
often
like
we
have
a
slack
channel
or
oh
there's
a
Google
Doc.
No,
it
would
be
interesting
to
have
a
github
repo,
because
then
we
have
issue
tracker.
We
could
even
throw
some
different
bits
of
code
in
there
or
use
the
wiki
or
something.
A
C
No
problem
I,
it's
I
think.
If
we
want
to
make
this
a
sustainable
initiative,
there
has
to
be
a
little
bit
of
formality
around
it.
Anyways,
like
maybe
for
these
meetings.
If
we
wanted
to
start
with
a
few
agenda,
topic
items
and
timebox
them
or
something
and
then
get
into
more
freeform
conversation
that
might
be
nice
because
I
know
today
is
a
fun
day
where
I
am
literally
in
meetings
from
8
a.m.
to
4
p.m.
so.
But
I
was
very
happy
to
jump
out
of
them
to
talk
here,
but
I
did.
C
A
A
You
know
and
I
I
know
that
8th
on
a
th,
om,
I'm,
not
sure
I
actually
pronounced
that
had
an
implementation
I,
an
operator
that
was
I
believe
backed
by
an
zaboor
that
he
put
out
there
and
I
was
hopeful
that
he'd
be
able
to
talk
a
little
bit
about
it
because
he
also
had
some
ideas
about
using
kind.
I
believe
is
a
bit
of
a
testing
infrastructure
to
be
able
to
validate
the
work.
C
So
I've
been
following,
along
with
the
ansible
operator,
to
work
a
little
bit
and
it's
interesting
because
the
the
whole
point
of
it
is
ansible
is
managed
by
Red
Hat.
It
also
manages
OpenShift
and
OpenShift
is
basically
kubernetes
with
some
layers
on
top
of
it,
so
ansible
itself
has
openshift
support,
which
is
basically
kubernetes.
Therefore,
there's
a
lot
of
initiative
to
for
Red
Hat
it's
in
their
best
interest
to
make
their
tools
work
together.
C
So
ansible
actually
has
pretty
robust
support
for
managing
kubernetes
in
a
variety
of
different
ways,
so
that,
logically,
it
followed
hey,
let's
make
an
ansible
operator,
so
you
can
write,
play
books
to
manage
CR
DS.
Instead
of
writing
like
go
applications
or
whatever
language,
you
want
that's
kind
of
how
that's
set
up,
and
it's
if
you
know,
go
you're
like
this
is
stupid.
Why
would
I
ever
use
ansible
operator,
but
it
is
kind
of
cool,
as
somebody
who
I
do
not
know
a
lot
of
go
just
enough
to
like
tweak
something
or
fix
a
bug.
C
You
know
being
able
to
write
an
operator
Foley
with
just
the
ansible
knowledge.
I,
have
this
is
kind
of
cool,
but
I
think
that's
that's
how
that
one
works
and
it
it's
not
super
flexible
right
now.
The
way
he
has
it
written
I
think
that's
more
of
a
POC
type
thing
for
him
right
now,
but
it
couldn't
mold
it
into
something.
Nice
or
I
mean
just
the
CRD
itself.
C
It
doesn't
matter
if
we
have
ant
like
his
operator
based
on
ansible
or
some
other
operator,
but
if
we
had
a
good
CRD,
you
could
swap
swap
in
a
different
operator
if
you
wanted
or
if
we
wanted,
to
standardize
on
a
one,
that's
written
and
go
or
heck.
You
could
write
one
in
PHP,
I,
don't
know
how
well
I
know
how
you'd
know.
B
B
Yeah,
it
was
has
been
pretty
passionate
about
this
one
yeah,
and
so
the
ansible
operator
makes
a
lot
of
sense
for
someone
who
is
trying
to
get
a
lot
done
and
doesn't
want
them
to
learn,
not
only
go,
but
also
everything
that
has
to
do
with
either
I
mean
the
two
of
their
three
options.
Use
the
older
controller
runtime
directly
like
the
first
generation
operators
for
prometheus
operator.
B
I
think
is
a
good
example
of
one
that
started
very
early
in
us
doing
this
or
yeah,
using
like
the
queue
builder
SD
or
the
the
Red
Hat
I,
just
called
the
IBM.
Now
SDK
that
ran
hand,
of
course
pushes
and
both
required
go
as
well
as
some
pretty
some
pretty
significant
knowledge
to
around
things
like
the
controller
at
one
time,
a
third
off
another
option
that
I
think
could
be
passable
and-
and
this
may
be
interesting
for
the
non
go
developers
to
use
the
meta
controller.
B
It's
a
web-based
one
from
it's
part
of
the
Google
cloud
platform.
Github
org
I
cannot
I'll
put
a
link
in
the
kubernetes
select
channel
to
it,
but
it
does
offer
the
ability
to
register
a
controller.
If
you
will
to
a
web
hook
that
you
can
write
in
any
language,
and
that
may
be
something
that's
compelling
to
look
at
a
lower
barrier
to
entry,
especially
for
an
open
source
implementation.
B
So
we
internally
I've,
been
you
know,
we're
a
heavy
go
shop
and
are
using
queue
builder,
but
you
know
when
I
thought
about.
You
know
the
open
source.
You
know
how
to
get
this
open
source.
That
has
been
a
question
on
my
mind,
especially
for
a
Drupal
developer,
who
wants
to
contribute
and
help
their
there
would
be
a
very
large
learning
curve
there.
B
A
C
The
the
coolest
thing
would
be
a
troop
all
that
org
got
to
stage
2
or
stage
3
elaboration.
We
could
do
it
all
there
and
we
would
have
all
the
get
lab
fanciness
with
the
hosted
drupal.org
one,
but
otherwise
I
mean
in
my
perspective,
it's
just
the
main
thing
would
be
a
central
resource
iron
issue.
I
was
thinking
like
a
readme
file
with
like
here's
links
to
this.
Here's
links
to
that.
Here's,
what
we're
looking
at
yeah
but
and
then
who's
heard
new
things
or
PRS
for
adding
to
that.
B
Question
does,
does
anyone
know
et
or
have
a
background
on
like
well
what
what
like
the
core
Drupal
team
governance?
Well
like?
What
is
the
opinion
of
github?
Is
it?
Is
it?
Is
it
the
devil?
You
know
we
don't
want
anything,
that's
part
of
like
the
community,
any
you
know
avoid
putting
community
projects
on
github
for
a
particular
reason.
A
C
Might
it's
kind
of
like
slack
in
my
opinion,
well
that
war
has
already
been
lost,
I
guess
but
beyond
slack
and
in
slack,
and
he
has
to
add
the
organization's
like
I'm
looking
at
my
sidebar
and
I
have
15
of
these
things,
and
it's
rare
that
I
click
on
any
besides
my
work,
one
because
it's
just
too
much.
If
you
click
on
it,
then
it
would
wait.
It's
12
seconds
to
load
and
then
your
ram
goes
up
by
like
three
thousand
megabytes
back
in
the
old
days
of
IRC.
C
B
Yeah,
that's
something
I
know
that
generally
in
the
open-source
communities
there
was
that
big
backlash
around
the
Microsoft
acquisition,
so
I'm
trying
to
figure
out
how
much
it
are.
You
know
because
I
came
previous.
You
know
especially
more
in
the
corporate
enterprise
space
that
wasn't
involved
directly
NIT,
but
was
using
IT
services
get
up
in
particular
had
a
everything
was
around
data
sovereignty,
data
ownership
of
data,
so
so
I
was
trying
to
see
also
to
if
there
was
some
some
concerns
around
that
with
github
or
it
was
I.
Think.
A
Our
purpose
is
for
this
group:
we
can
start
on
github
and
go
ahead
and
just
generate
kind
of
a
synopsis
of
this
meeting.
Maybe
outline
a
couple
of
items
that
might
be
considered
next
steps
and
then,
if
we
need
to,
we
can
open
up
discussion
about
moving
it.
Someplace
else
does
that
sound,
reasonable.