►
From YouTube: January 7, 2021 Ortelius Architecture Working Group
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).
C
D
The
january
7th
or
today's
architecture
and
marketplace
working
group
and
let
me
throw
the
link
in
the
chat
window.
D
Looks
like
I
have
to
I
gotta
double
check
that
the
last
meeting
was
published
out
to
youtube.
D
I
think
I
missed
doing
that,
but
I'll
do
that
when
I
publish
this
one
out
to
youtube,
if
you
could
go
ahead
and
sign
yourself
in
and
just
a
couple
things
that
we
have
and
I
think
they're
going
to
flow
into
one
another.
D
So
the
the
google
google
summer
of
code
for
those
of
you
don't
know.
Basically
it's
focused
around
students
that
want
to
get
some
coding
experience
and
you
we
basically
get
a
a
student
to
work
with,
and
it's
supposed
to
be
a
full-time
type
of
position
for
the
student,
where
they're
going
to
be
working
full-time
on
our
project.
D
So
one
of
the
things
that
we
need
to
do
is
come
up
with
some
project
ideas
for
what
we
can
like
publicize
out
there
to
try
to
get
some
people
to
join
us
as
students
for
for
coding,
we're
going
to
be
rolled
up
underneath
the
the
cncf.
So
cncf
is
going
to
do.
C
D
D
I
know
that
this
is
what
happened
on
the
toc
meeting
yesterday
or
the
day.
C
D
All
right
so
looks
like
from
what
they've
said
in
the
past
is
like
jenkins
would
get
like
seven
people,
the
other
groups
like
spinnaker,
and
I
can't
remember
the
other
one
that
they're
talking
about.
Maybe
tecton
got
like
one
or
two
people
to
to
join.
D
So
I'm
thinking
that
we
would
be
targeting
at
least
one
maybe
two
people
and
it's
a
mentor
mentor
type
based
program
where
dan
lark
was
saying
that
they
they
it
works
out
best
or
tara,
that
you
have
two
mentors
to
every
student
just
to
off
those
you're
not
pulled
away
from
your
regular
day
job
all
the
time.
D
D
Well,
I
the
that's
the
thing
the
intern
doesn't
have
to
do
the
whole
thing
on
their
own.
They
just
start
they
just
work
with
us
on
that
right.
So
we.
C
D
Bring
him
in
as
part
of
and
part
of
that
I
was
thinking,
is
there's
gonna,
be
a
coding
piece
to
it,
mainly
you're,
looking
like
python
javascript
and
then
we'll
have
back
end,
which
will
be
some
database
work.
D
And
then
obviously,
we're
gonna
have
the
devops
piece
of
hooking
all
together.
The
plumbing.
D
And
that's
some
of
the
things
I
was
thinking
about.
I
don't
know
if
we
want
to
look
at
the
other
parts
of
it
which
would
be
getting
into
design
and
architecture.
I
think,
by
the
time
this
starts
we'll
be
past
the
design
phase
and
pass
the
architecture
phase
for
what,
for
the
summer
code.
D
Pieces
that
we
want
to
focus
on,
I
mean
it
could
get
into
even
things
like
training
videos,
those
types
of
things
as
well,
because
I'm
I'm
not
sure
if
it's
going
to
be
100
like
developer
coding,
personas
or
if
it's
going
to
be
more
of
a
wide
range
of
people
that
we're
going
to
try
to
attract.
E
So
I'm
I
guess
I
sort
of
share
tracy's
concern
about
the
complexity
of
the
component
set
thing
and
maybe
that's
a
better
project
than
I'm
imagining
it
to
be.
But
you
know
something
that
seems
more
isolated
and
potentially
you
know
easier
for
somebody
to
do.
E
Semi-Independently
would
be
integrating
with
one
of
these
new
ci
platforms
that
we
don't
have
much
support
for,
and
you
know
that's
something
that
shouldn't
require
as
many
in-depth
changes
in
the
core
of
things
and
yeah.
But.
D
E
By
being
more
ancillary,
I
feel
like
it's
a
win,
because
if,
if
the
person
just
totally
fails
in
the
project-
and
it
doesn't
produce
anything,
then
we
can
just
start
over
later
or
next
year
or
whatever,
but
the
component
that
stuff
we're
going
to
have
to
build
on
that,
and
I'm
not
saying
that
a
google
summer
of
coding
person
wouldn't
produce
lovely
code
that
we'd
be
happy
to
build
on,
but
it's
not
guaranteed.
You
know
who
knows.
C
I
think
we
could
do
something
in
the
area
of
some
of
the
reports.
We
could
have
a
intern
look
at.
You
know
different
ways
to
present
our
existing
data,
so
I
I
I
suspect
we
can
come
up
with
some
things
that
they
can
do.
C
C
And
it
just
even
doing
you
know
putting
together
some
sample,
graphs
and
whatnot
that
we
can
all
choose
from
would
be
a
a
good
project
for
a
college.
Kid.
D
Yeah-
and
you
know
something
like
the
the
data
visualization
will
tie
into
the
component-
sets
as
well,
because
we'll
need
to
visualize
the
component
sets
as
well,
so
the
they
will
have
interaction
with
everybody.
That's
working
on
component
sets
at
that
level.
I
do
like
the
the
cicd.
C
D
The
one
thing
I'm
worried
about
on
that
is,
if
you
get
when
you
get
into
like
argo
cd,
that's
a
whole,
get
ops
world
same
thing
like
with
code
fresh
and
a
college
person's,
probably
not
going
to
understand
the
com.
Why
you're
why
things
aren't
scaling
just
because
of
their
lack
of
experience
and.
D
Now,
the
other
way
we
could
we
could
slant.
This
is
by
breaking
it
out.
My
thought
process
was
to
take
the
person
from
start
to
finish,
so
they
learn
a
little
bit
of
everything.
A
little
learn
coding
then
learn
about.
You
know
what
what
devops
is
putting
in
places
putting
in
things
like
you
know
the
build
the
deployment,
the
issue
management,
all
those
pieces
of
that
you
deal
with
on
a
devops
basis.
D
C
Yep
we'll
get
it,
you
know
we're
gonna.
I
think
we
just
have
to
put
a
web
page
up
with
what
our
project
is.
D
Yep
and
karam
and
sasha
already
stepped
up
to
be
mentors.
D
C
Well
I'll
put
up
I'll,
put
a
google
doc
out
there
and
send
it
out
to
everybody
that
says:
here's
what
we're
thinking
about
and
we
can
collaborate
from
there.
D
Yeah
in
the
I
did
post
some
stuff
on
the
discord
channel
around
links
to
and
also
in
there
there's
a
github
issue.
Let
me
find
it
real,
quick.
D
So
if
you
want
to
see
what's
going
on,
where
we're
tracking
it
and
the
discussion
that's
been
happening.
D
Markdown
but
so
there
are
a
couple
steps
logistically
that
we
need
to
work
on
and
it's
newton's
tracking
that
in
that
issue.
D
There's
a
small
pull
request
that
we
need
to
do
with
the
cdf
as
part
of
that
to
update
that
our
project
will
be
part
of
the
the
s,
the
sock,
the
g
stock,
anything
else
on
summer
of
code,
all
right
cool.
We
do
have
our
meeting
with
argo,
intuit
and.
C
D
Yep,
so
it
was
interesting.
I
was
on
a
doing
some
training
with
one
of
our
customers.
Was
it
monday,
tuesday,
the
week's
blending
together
already,
and
I
did
looking
at
how
they
laid
things
out
and
they've,
took
two
micro
services
and
rolled
them
together
into
an
application
version
and
they
were
deploying
at
that
level.
D
One
of
the
things
I
think,
that's
that
we're
missing
is
the
our
capability
of
deploying
incrementally.
So,
if
you
have,
you
know
20
microservices
and
you
try
to
change
only
two
of
them
that
only
the
two
are
going
to
deploy.
D
What
I
think
is
coming
about
from
the
application
sets
is
people
are
looking
at
that
as
the
deployable
unit,
so
they
would
go
through
and
deploy
that
unit,
and
then
they
go
off
to
the
next
next
set
and
deploy
that
unit,
and
then
they
go
to
the
next
set
and
deploy
that
unit,
because
the
tools
that
they're,
using
like
argo
or
spinnaker
are
not,
or
even
just
like
a
tech
on
a
jenkins
job,
is
not
set
up
to
handle
the
relationships
so
they're
thinking
very
linear
and
very.
D
Not
in
a
a
way
that
allows
it
allows
the
relationships
to
be
pulled
up
to
another
level,
it's
basically
very
thinking
very
monolithic
still
about
the
deployment
process,
so
that
I
thought
that
was
interesting
when
we
got
into
component
sets
it'll
be
interesting
to
see
what
what
we
find
out
from
the
the
argo
cd
space.
D
D
D
They
have
another
repository
that
has
all
the
deployment
yaml
files
kind
of
thrown
into
that
other
repository
to
enable
the
get
ops
world
to
drive
off
of
that
now.
One
of
the
things
is
that's
happening,
and
the
reason
why
application
sets
are
coming
about
is
because
it's
a
single
repo
and
because
they
are
not
able
to
do
incremental
deployments
anytime.
D
D
D
Manage
the
relationships,
but
I
can
see
from
my
git
ops
way:
that's
the
only
way
to
do
it
because
gets
so
flat,
they're
taking
a
single
repository
but
creating
a
bunch
of
directories
underneath
it
for
each
microservice
and
then
trying
to
filter
through
and
and
say
that
these
are
going
to
go
now
as
per
an
update,
so
that's
kind
of
what
I've
uncovered
on
that
front
and
the
reason
why
it
came
about
so
what
they're?
D
The
other
thing
I
found
on
on
the
argo
cd
is:
they
do
have
another
level,
but
but
they
don't
really
talk
about
it,
which
is
called
a
project.
So
project
is
a
collection
of
applications.
D
Yep,
so
once
we
have
that
that
meeting
we'll
go.
E
D
And
start
hammering
out
our
solution
around
what
we're
calling
component
sets
and
in
our
world
a
component
is
one
of
the
smallest
levels
of
something
that
can
be
deployed,
and
then
those
components
are
associated
up
to
an
application,
and
you
deploy
an
application
that
contains
components
and
like
I
said,
because
we
can
do
incremental,
we'll
recognize,
what's
on
a
what's
been
deployed
to
a
cluster
and
then
the
next
time
we
come
across.
If
we're,
only
three
things
have
changed.
D
We'll
only
deploy
those
three
things
as
part
of
that
process,
so
we
have
a
different
slightly
take
on
it,
and
the
one
thing
that
we'll
have
to
look
at
is
what
we
end
up,
calling
it.
We
may
I'd
like
to
stick
with
component
sets.
We'll
have
to
see
how
it
plays
out
with
with
the
way,
argo
and
and
the
get
ops
world
is
trying
to
talk
about
what
they're
calling
get
ops
2.0.
D
That
was
the
main
things
that
I
wanted
to
bring
up
today
want
to
talk
about
goals
at
all,
steve
yeah.
We
could
get
into
that.
D
So
one
of
the
things
that
we
put
out
there,
our
general
working
group,
was
goals
of
what
we
want
to
achieve
and
from
like
architecture
coding
perspective,
I
think
we
can.
You
know
we
have
some
good
metrics
around
the
you
know
like
pull
requests
commits
those
type
of
things,
but
the
the
higher
level
goals
were
around
adoption.
D
You
know
how
many
people
are
are
signing
up,
how
many
people
are
downloading
the
containers,
those
type
of
things
as
part
of.
C
So
that
so
the
outreach
community
is
going
to
focus
on
adoption,
we're
gonna,
potentially
we're
gonna
we're
gonna,
organize
a
blogathon
to
include
more
blogs
around
tips
and
tricks
to
start
making
it
easier
for
people
to
learn
and
understand
the
product.
C
So
I
think
the
question
for
this
group
is
what
we
think
we
might
be
able
to
do
to
enhance
that
as
well.
I
know
that
you
know
onboarding
will
be
pretty.
I
think
onboarding
in
general
for
everything
that
we
do
and
making
it
easy
as
possible
is
going
to
be
a
challenge
for
us,
and
I
think
that
this
group,
we
need
to
start
having
discussions
about
how
we
can
make
the
product
just
for
anybody
who
is
going
through
and
installing
a
a
an
on-premise
version.
Does
that
all
work?
Fine
do
we.
C
C
A
What
I've
seen
tracy
is
when
these
new
concepts
comes
up.
One
of
the
easiest
way
to
bring
confidence
among
the
users
of
this
is
the
first
question
come
up.
Is
I
mean
again
my
perception
people
may
differ
to
what
I
say
is.
Can
I
do
this?
Can
I
work
on
this
new
framework
or
new
structure
or
new
architect
or
new
solutionize
solutions
which
are
coming
across
and
if
I
have
an
answer
to
it,
then
probably
I
have
more
confidence
and
I'll
probably
try
to
work
or
experiment.
A
A
What
probably
we
can
do,
and
people
can
jump
on
to
add
to
it
is,
if
we
can,
you
know,
write
small
articles
of
how
they
have
implemented
this
ordinance
framework
in
their
piece
of
project
or
a
short
way
of
configuring
and
working
on,
or
at
least
maybe
you
know,
a
30
minutes
exercise
to
onboard
yourself
or
not
would
be
a
good
option.
D
And
do
you
think
the
that
we
would
get
better
traction
with,
like
blog
articles
or
like
training,
videos
on
youtube
or
do
we
need
both.
A
Happens
what
happened
is
you
know
answering
the
sleeve
question
is
at
times
a
people
like
me
would
hesitate
in
writing
the
blocks,
but
people
like
me
probably
could
take
5-10
minutes
of
recording
the
video
step
by
step
of
how
to
install
it,
how
to
configure
and
how
to
work
on
it.
So
it
is
like
you
know
what
people
easing
if
they
like
to
probably
create
a
video,
not
writing
enough
of
stuff.
That
also
works
either
of
them.
C
D
And
do
you
think
the
the
well?
I
think
it
probably
I'll
probably
answer
my
own
question,
but
I'll
throw
it
out
there.
Do
you
think
the
blog
article
should
be
like
a
step-by-step
guide,
or
should
they
be
more
more
general
about
like
why
you're
doing
this,
or
do
we
need
to
have
a
combination
of
both.
A
From
the
organization
point
of
view,
I
think,
step
by
step
is,
should
be
there,
but
if
step
is
there
are
enough
step
by
step,
then
it
could
be
generated.
So
this
answer
is
from
the
organization
standpoint:
individuals
under
you,
whatever
they
you
know,
feel
like.
D
F
I
wanted
to
say
that
I
haven't
be,
I
I
haven't
deployed
or
telus,
I'm
so
new
here,
first
time
came
up.
When
I
see
we
have
a
container
image
was
to
put
it
on
into
kubernetes
so
right
now
my
personal
goal
is
taking
this
and
deploying
into
kubernetes
and
trying
to
do
what
I
don't
know
the
the
more
for.
For
me,
it's
like,
if,
if
you
have
this
concept
about
one
push
bottom
to
deploy,
everything
is
going
to
flow
from
there.
F
There
is
a
lot
of
solution
today,
but
usually,
if
you
have
a
really
easy
way
like
almost
like
a
push
button
to
do
this,
make
this
work.
It
has
a
huge
impact
because
you
can
focus
about
the
futures
about
the
functionality
about
what
is
solving
after.
If
you
are
really
interested,
you
are
going
to
get
into
it,
even
if
it's
hard,
but
if
you
cannot
jump
and
you're
stuck
in
this
this
trying
to
follow
a
step
by
step-
maybe
maybe
you're
never
going
to
get
there.
F
So
my
personal
goal-
and
I
think
can
be
useful-
is
to
to
get
into
this
one
push
button.
I
was
thinking
like
using
operator
framework
because
that
is
going
to
be
handy
for
kubernetes,
but
still
you
can
grab
up
into
just
a
common
shell
right,
so
most
of
the
people
is
just
going
to
have
a
linux.
A
local
linux
is
going
to
deploy
this.
So
for
me
this
those
though
these
two
implementation
of
this
button
is
going
to
get
easy
to
people
just
download,
execute
and
try
out
even
with
a
playground,
sounds
good.
F
Maybe
I
have
environment
like
like
a
clustered
qr
nets.
Maybe
I
don't
know
a
playground
where
you
can
just
go
jump
into
it
and
and
check
what
you
can
do
is
is
a
good
idea
too.
I
just
all
around
like
playing
with
this
trying
this
before
having
this.
This
decision
about
going
deep
to
ortelis
yeah.
C
Because
we
we
tried
to
sergio
thank
you
for
that
those
comments,
because
we
we
we've
made
an
attempt
to
do
that,
to
make
it
as
push
button
and
as
simple
as
possible.
So
something's
already
set
up
almost
like
you
know,
think
about
our
hipster
story
as
our
hello
world.
So,
let's,
let's,
let's
try
to
get
an
understanding,
or
at
least
a
consensus
that
that
that
hipster
store
is
the
good,
a
good
place
to
start
well.
I
think.
D
Part
of
it
is
I,
what
we
may
need
to
do
is
bubble
the
getting
started.
You
know
your
first
steps,
or
it's
actually
even
before
that.
It's
welcome
and
move
this.
You
know
like
sergio
saying
as
a
because
right
now
this
is
in
our
documentation
and
I
it
may
be
just
too
low
for
people
to
go
and
find
you
know
how
to
get.
C
Started
so
we
may
need
to
bubble
this
up,
let's,
let's,
let's
make
sure
that
it
works
first
right
so
and
then
we'll
figure
out
where
how
we
need
to
you
know
how
we
need
to
put
it
in
some,
because
everything
that
we,
I
believe
right
now
are
if
somebody
does
sign
up
or-
and
we
need
to
start
thinking
about
downloads
as
well.
D
C
So
if,
in
the
next
two
weeks
between
now
and
our
next
meeting,
if
we
can
get
some
feedback
on
it-
and
we
can
do
that
through
a
google
doc
too
so
that
it's
easy
just
say,
here's
some
notes
and
I'll
create
that
doc.
Right
now.
E
I
want
to
get
back
to
steve's
original
question
for
a
second,
I
like
the
direction
this
is
gone,
but
I
feel
like
the
tutorial
sort
of
stuff
is,
is
better
in
the
short
term
sense
and
then
the
sort
of
why
we're
doing
things
sort
of
thing
is
something
that
should
come
later
and
that
would
generally
be
something
I
would
associate
with
like
landing.
This
component
set
application
set
idea.
C
Yeah,
I
I
think
it's
bloggable
I've
gone
through
it.
I
I
believe
that
it
is
bloggable,
but
I
feel
like
we
need
somebody
else.
Who's
never
touched
it
before
or
you
know
fresh
eyes
to
make
sure
that
it
the
process
was
easy.
I
think
that's
my
biggest
concern.
D
And
there's
what
I'll
do
is
I'll
put
out
a
couple
github
issues,
so
we
can
track
this
and
just
like,
like
the
basic
thing
getting
signed
up,
you
know
the
sign
in
process
getting
logged
in
because
I
know
rosalind
from
the
cdf
ran
into
an
issue
where
it
wasn't
prompting
for
the
admin
password
and
because
the
documentation
is
slightly
off
on
that.
So
there's
things
that
just
the
little
things
like
that
that
will
get
us.
C
So
I
created
a
under
the
architecture
meeting
I
created
a
doc
called
adoption
notes,
that's
what.
D
I
mean
put
in
the
link
or
just
add
it
as
into
the
dock
yourself:
okay,.
C
D
D
You
know
now
that
we're
over
the
holidays
and
stuff
like
that-
and
you
know
this
is
where
we're
we're
gonna
start
really
hitting
the
ground
running
with
this.
So
things
will
start
we'll
you'll,
see
more
issues
being
created
around
coding
and
like
again
like
the
the
blog
articles
and
things
like
that,
so
we
are
going
to
get
ramped
up
a
little
more
on
that
front.
So
just
give
everybody
a
heads
up
and.
C
Yeah
and
that's
why
I'm
worried
about,
I
want
to
make
sure,
as
we
push
this
product
out
to
the
cdf
community,
I
just
want
to
make
sure
that
it
was
great
that
rosalind
had
gone
through
it
and
found
those
little
things.
But
if
there's
anything
else
like
that
that
she
just
kind
of
hacked
through
that
somebody,
it
might
stop
somebody
else.
We
just
need
to
catch
them.
C
D
Alrighty
well,
thank
you.
Everybody
and,
like
tracy,
said.
C
Yeah,
there
is
one
more
thing
we
do
have
a
new
new
person
harsha.
You
want
to
introduce
yourself.
B
Yeah
yeah,
hey
guys,
see
yeah.
This
is
harsha
hershey.com
30
from
california
san
jose,
which
I
work
at
the
walmart
as
a
devops
team
member.
So
I
basically
work
on
like
deploying
stuff
on
kubernetes
for
the
walmart
teams.
B
So
so
we
don't
own
the
platform
or-
and
we
don't
own
the
application
so
we're
in
the
middle
like
exact,
like
a
proper
or
devops
structure.
B
So
so
I
help
teams
to
implement
their
their
deployment
scripts
in
yaml
files
like
like
a
pfe,
so
like
a
poc
thing,
and
then
new
teams
will
implement
on
themselves.
So
we
have
a
wrapper
around
the
kubernetes
which
is
inbuilt
by
walmart,
but
we
don't
have
like
micro
services
as
of
now.
So
that's
why
I'm
interested
in
this
project.
So
let's
see
how
this
goes
and
I'm
with
brand
new
to
this,
which
art
list
so
I'll,
be
installing
on
my
personal
laptop
and
see
how
it
goes.
B
D
C
D
C
Harsha
on
the
topic
of
adoption,
since
you're
going
through
that
you
know,
please,
you
know
open
tickets
on
any,
even
small
thing
that
you
run
into
that
says.
This
doesn't
make
sense.
D
So
and
the
and
that's
one
of
the
things
that
for
people
getting
started,
the
sas
version
is
actually
the
easiest
way
to
get
up
and
going
because
it
doesn't
involve
installing
anything.
D
And
that
may
be
where
we
need
to
redirect
people
to
looking
at
the
sas
version
instead
of
the
on-prem,
because
that's
what
like
rosalind,
did
the
on-prem
docker
container
locally.
So.
D
Yeah,
I
think
sergio's
idea
of
of
maybe
doing
an
operator
and
having
that
set
up
to
do
something
really
simple,
to
bring
it
up
into
a
cluster
locally,
maybe
a
a
better
way
to
for
people
to
to
kind
of
kick
the
tires
or
to
learn
it.
E
Mean
I
think
the
sas
version
is
great.
It's
like
an
initial
taste,
but
as
an
ops
person,
if
I
can't
run
it
on
my
own
infrastructure,
I
don't
believe
it's
real,
and
so
you
know
having
the
ability
to
do
that
without
it
being
any
more
painful
than
necessary,
I
think
is,
is
a
critical
second
step
to
getting
it
truly
adopted.
D
Yeah
yeah,
I
totally
agree
it's
interesting
how
the
the
sass
is
viewed
in
by
different
groups.
D
Yeah
yeah
all
right.
Well,
keep
that
in
mind,
because
I
think
that
I
think
there's
a
I
think,
we're
really
close,
and
it's
just.
We
need
to
uncover
some
of
the
the
smaller
little
stumbling
blocks
that
can
turn
people
off.
D
C
C
If
you
haven't
read
any
of
the
there's
some
in
harsha,
there
are
some
notes
in
that.
When
you
go
to
discord,
we
probably
should
include.
Maybe
we
did
include
the
notes
are:
are
the
notes
from
where
you
can
get
information
on
how
argo
cd
is
addressing
that
component
sets
is
that
in
the
dock
from
last
week,
did
we
put
that
in
there.
D
D
It
may
be
in
the
general
working
group.
C
C
So
if
you
want
to
attend
that
meeting-
and
you
want
to
do
a
little
bit
of
homework
ahead
of
time,
those
two
links
will
be
helpful
for
seeing
the
problem
set.
From
the
argo
perspective,
I
think
that
we'll
hear
a
different
perspective
from
the
spinnaker
folks
and
I
believe,
they're
trying
to
solve
the
same
thing
and
I've
noticed
that,
as
in
all
developers,
when
we
start
chatting
with
these
developers,
they
don't
they
jump
to
the
solution
faster
than
they
can
just
describe
the
problem.
C
So
I
think
that
that
could
be
happening
because
I
think
they're
both
trying
to
solve
the
same
problem
they're
just
talking
about
it
differently.
So
that's
one
of
the
reasons
I'm
we're
trying
to
get
them
together
to
have
a
discussion
to
really
clearly
understand
the
use
cases
so
that
we
can
solve
the
problem
from
from
a
central
place.
So
that
any
deployment
tool
that's
trying
to
manage
what
they're
calling
application
sets
can
do.
C
E
B
B
D
Yeah,
let
me
throw
the
link
in
real
quick.
Give
me
one.
D
D
D
E
B
C
And
then
only
the
last
thing
before
we
have
to
jump
off
and
I
know
we're
over,
we
there
is
now
in
this
cli
in
the
cncf
there
is
a
working
group
called
get
ops.
C
I
am
going
to
start
attending
those
meetings,
so
if
anybody
is
interested
in
getting
involved
in
that
I'll
make
sure
and
cross
post
when
they
start
having
the
meetings
again,
they've
only
had
one.
I
haven't
seen
a
new
announcement,
but
I'll
go
ahead
and
post
in
the
in
these
architecture
notes
all
of
the
links
to
the
get
ops
notes
that
they're
working
on,
because
what
they're
trying
to
do
is
standardize
and
what
git
ops
means.
D
Yeah,
it
looks
like
you're
just
like
popping,
so
I
think
you're
gonna
be
all
set.
D
Okay
and
then
like
in
a
few
minutes,
is
going
to
be
the
cdf's
interoperability
meeting
and
that's
going
to
be
very
similar
as
well.
How
it
seems
the
general
problem
in
the
cicd
world
is
is
how
to
talk
to
each
other
and.
C
Yeah
and
that
interoperability
just
to
be
a
bit
critical
of
it,
they
haven't
really
gone
anywhere.
The
team
that's
really
doing
some
interesting
stuff
is
the
team,
that's
working
on
events
and
event,
driven
integration,
I'm
trying
to
get
them
to
spin
that
off
to
a
separate
working
group,
so
we
can
just
focus
on
declarative
pipelines
and
events,
and
so
that
that
may
happen
soon
as
well.
A
D
All
right,
everybody
all.