►
From YouTube: Ortelius Outreach 10/25/21
Description
Finishing up Hackathon and starting the community voting process, as well as the December 8th Visionaries event are the topics for this meeting.
B
B
A
C
B
B
So
we
we
actually
have,
we
have
five
responses
and
then
I'll
add
my
name
that
gives
us
six,
so
I
don't
think
we
should
vote.
I
think
we
should
just
announce
the
announce.
Those
of
us
who
are
on
who
got
elected,
so
the
new
the
new
board
would
be
siddharth
and
anne-marie,
sergio
aisha,
bryan
dawson
and
myself.
C
B
C
B
B
A
B
B
A
C
E
I
think
something
I
think
it
was
something
funny
with
the
video
yeah,
because
serge
was,
he
was
he's
quite
far
away
he's
not
at
home.
He
was,
I
think
he
was
using
mobile,
something
when
finally,
the
something
went
funny
with
the
video,
but
I
mean
we
got
it
off
the
ground
now
yeah,
which
was
cool
yeah.
A
E
D
E
E
E
C
C
B
B
B
B
We
have
the
get
up
special
working
group
or
they're
out
of
the
folks
down
in
australia
and
new
zealand,
and
then
we
really
need
to
start
looking
at
that
building
the
relationship
maps
between
what
I'm
calling
transitive
services
and
then
the
data
science,
and
I
think
the
data
science
is
going
to
be
the
one
that's
going
to
be
a
longer
ongoing
project,
because
I
think
I
don't
think
we
ever
answer
the
question
for
data
science.
I
think
we'll
always
be
growing.
That.
B
And
sometimes
I
hate
to
start
new
projects
coming
into
the
holidays,
we're
here
at
the
we
have
two
two
months
left
of
the
year
and
we
really
do
start
losing
people
right
around
now
so
and
everybody
gets
kind
of
back
into
it
in
january.
So
just
we're
trying
to
finish
off
these
projects.
We've
started
and
be
ready
for
the
work
in
january.
B
B
C
B
B
B
B
I
think
he
works
for
natwest
who's
done
a
lot
of
work
around
service
mesh
and
microservices,
so
I've
invited
him
to
be
our
guest
speaker,
so
he'll
just
he'll
be
presenting
this
data
from
an
end
user
perspective
of
the
kind
of
challenges
that
they're
going
through.
So
I
think
that'll
be
a
great
guest
speaker,
so
that
gives
us
a
guest
speaker.
B
B
C
E
D
B
B
B
C
B
A
B
B
And
right
there,
if
you
scroll
down
on
the
first
page,
is
the
sign
up
for
testing
so
sign
up
and
you
will
get
a
an
environment
will
be
created
for
you,
for
a
a
project
will
be
created
for
you
and
if
you,
if
you
can't
remember
how
to
get
there,
there's
a
login
link
as
well.
Once
you
sign
up
you're
going
to
get
your
own,
your
own
kind
of
project
and
the
area
that
we're
working
on
is
specifically
related
to
components.
B
And
if
you
choose
any
of
these
components,
you
can
start
just
doing
basic
testing
and
documentation
so
the
documentation
we
have
not
gone
through
any
of
like
this,
the
readme,
the
general
data,
the
readme,
how
you
know
the
swagger,
how
to
upload
the
swagger.
I
thought
we
were
gonna
put
a
button
on
there
steve.
It
says.
B
Although
these
four
little
blocks
need
to
be
documented,
steve
was
going
to
add
a
button
that
said
upload
file,
but
we
do
need
to
document
how
we
up
add
this
information
without
the
button,
so
the
button's
just
going
to
make
it
a
little
easier
to
understand
where
it
came
from,
but
for
each
of
these
boxes
we
need
to
have
that
documented.
So,
for
example,
you
could
take
on
the
entire
this,
the
swagger
integration
and
how
the
swagger
integration
was
written,
was
is
done
or
you
could
take
up
the
cve
or
the
license
consumption.
B
Okay,
so
then
you
can
just
start
adding
the
documentation
and
I'll
work
on
I'll
help
work
on
the
editing
of
the
documentation.
So
once
you
get
it
up
there,
then
I'll
start
going
through
and
doing
the
editing.
So
you
can
go
ahead
and
grab
one
of
these.
I
think
there
is
one
like
here's
documentation
describes
swagger
box
on
the
component
version
just
go
ahead
and
grab
it,
so
we
know
somebody's
working
on
it.
C
A
And
then
just
do
full
four
pull
requests
or
three
or
however
many
you
need
to
do
just
set
them
out.
So
it's
you
do,
you
know,
do
like
the
license
box.
Do
the
the
pull
request
for
that
and
then
go
on
to
the
cve
box
and
then
do
another
pull
request
for
that,
and
then
do
the
readme
and
then
I'll
be
your
third
pull
request.
For
example,.
B
B
B
Free
yep,
steve's
gonna,
we're
gonna
focus
on
this,
so
just
make
sure
just
get
your
get
time
on
this
calendar
and
he
will
he'll
make
it
the
effort,
because
it's
gotta
get
done
so
then
you'll
have
for
each
of
those.
You
have
the
potentially
having
to
to
pull
requests
right
because
you
should
go
through
the
testing
of
it.
G
B
C
A
C
A
Will
happen
yeah?
So
when
you
do
your
pull
request,
I
will
be
able
to
see
what
your,
what
you've
written
for
the
documentation
and
the
the
testing
summary
and
then
we
can
make
changes
and
and
suggestions
through
the
comments
and
the
pull
requests
and
then
once
we're
once
everything
looks
good,
then
we
just
merge
it
and
you
we
tag
it.
So
you
get
your
hecktoberfest
credit.
A
C
C
E
E
B
E
E
Yeah,
I'm
going
to
show
you
what
I'm
attempting
to
do
here
so
steve,
kindly
put
all
the
all
the
process
into
steps
right,
here's
the
process
and
a
table;
okay
and
here's
the
link.
If
you
want
to
see
it
live
it's
all
in
it's
all
in
the
attilius
google
drive
and
I'm
working
of
that.
So
nice
you'll
see
changes.
E
Yeah,
I
have
crazy
ideas,
I've
been
learning,
I've
been
checking
out,
uml
language
and
how
we
could
actually
automate
this
diagram,
and
the
guy
taught
me
how
you
can
use
uml
to
have
this
diagram
automate
automatically
update
itself
so
but
that's
a
whole
other
story
and
we
need
to
write
some
python
that
can
basically
pass
pass
the
information
into
uml
and
then
the
url
will
capture
that
and
draw
the
diagram
for
us.
Yeah.
C
E
So
yeah
so
steve
gave
me
the
table,
like
I
say,
and
some
other
people
have
helped
me
understand
the
process
better.
So
what
I've
done,
I'm
taking
this
table
and
I'm
attempting
to
take
the
logic
in
the
table
and
adapt
it
to
the
diagram.
So
then,
so
each
color
represents
a
component.
So
captain
is
this.
I
don't
even
know
what
color
that
is,
but
it's
some
type
of
blue
or
something
and
then
I
will
then
take
that
color
and
put
it
in
the
table
so
that
people
can
correlate
the
color
with
colors.
E
Because
it
works
better
with
humans,
you
know,
I
don't
know
for
me,
it
works
really.
Well,
I
don't
know
we
put
colors
together
and
stuff.
What
till
this
is
the
is.
This
is
the
alien
green.
So
wherever
you
see
the
alien
green,
you
know
that
tortilla
is
doing
its
thing.
The
pink
is
obviously
argo.
Argo
is,
then
it's
just
showing
how
argo
and
otillos
are
working
together
and
those
little
blue
blobs
are
supposed
to
be
pods
right.
Yeah.
D
E
Showing
each
cluster
dev
qa
and
production-
and
that
shows
you
that
what
argo
is
doing
there
and
obviously
there
might
be
some
stuff-
that's
wrong
here,
but
I'm
going
according
to
the
table
and
obviously
steve
can
just
say:
oh
no,
that
doesn't
make
sense
or
you
know,
fix
this
or
fix
that
I'm
still
busy
ortilla's
the
cat.
I
know
you've
got
dogs,
but
there's
a
cat
now,
so
you've
got
an
extra
a
member
of
the
deploy
hub
family.
It's
telling
us
the
cat.
B
B
E
E
So
that's
that's
our
developer
who's
pushing
code.
The
initial
commit
this.
This
page
will
be
the
initial
commit
page,
and
then
we
can
have
another
page
for
when
we
start
having
branches-
and
you
know
when
there's
a
full
flow
of
development
right
and
we
can
just
take
this
whole
diagram
and
replicate
it
and
then
turn
it
into
that
right.
E
A
E
E
B
E
B
E
Yeah
yeah.
I
think
there
was
a
lot
of
pull
requests
in
here,
but
I'm
building
it
as
a
picture
and
as
a
table
like
what
steve
suggested
was
really
great,
because
you
can
put
the
numbers
next
to
it,
then
I
can
take
the
numbers
with
the
color
coding
and
some
of
the
description
in
there,
and
it
really
helps
it
just
kind
of
gives
people
a
visual
and
a
an
idea
on
how
all
the
pieces
fit
together.
Right.
Yes,.
E
It's
crazy,
complicated
eh,
because
I'm
going
through
your
table
right
and
I'm
like
oh
geez.
How
do
I
describe
this
now
and
and
the
more
I'm
going
through
it,
I'm
also
starting
to
simplify
it,
because
I'm
I'm
trying
to
treat
myself
like
a
complete
idiot
right.
I
have
no
idea
about
this.
You
know
I'm
talking
to
somebody
who's,
maybe
on
the
business
side
you
know,
and
they
want
to
know.
Why
do
we
need
githubs
right?
E
E
E
E
E
G
B
A
E
B
E
B
B
E
Well,
that's
cool,
but
you
see
the
thing
is
we
can
just
reiterate
the
whole
time
right
and
go.
Oh,
let's
just
tweak
this
a
bit
better.
Make
this
look
a
bit
better.
You
know,
and
I've
just
got
I've.
Just
the
square
doesn't
say
you're
only
using
these
clouds.
This
just
represents
that
we
don't
care
where
you
are,
whether
you're
on
prem
or
in
the
cloud.
We
don't
care.
This
process
works
anyway.
It's
it's
agnostic.
C
E
A
A
D
B
E
B
E
E
It's
now
grown
from
six
steps
to
now
22
steps.
You
know
and
that's
going
through
one
application
for
one
team
right
just
to
get
them
on
board
and
they
don't
need
every
single
component,
because
not
all
services
are
relevant
to
them
like
lambda,
they
might
not
use
lambda,
for
example,
but
they
they
need
monitoring.
They
need
all
their
database
stuff.
I
need
all
that
kind
of
thing
right,
so
it's
quite
I've
documented
that
whole
that
whole
process-
and
it's
like
22
now
you
know
22
processors
to
go
through
now.
It's
pretty
interesting.
A
E
It's
not
it's
super
complicated
and
you
can't
do
it
without
other
people.
It's
it's
almost
like
a
magnifying
glass
on
the
whole
microservices
process
right
now,
especially
like
no.
I
have
to
break
up
multi
what
mono
multi-component
mono
repos
into
micro
services,
pretty
interesting,
the
horrible
world
of
maven
node,
js,
ng,
mpm
and
angular
all
mixed
into
this
lovely
mess
of
spaghetti
to
try
and
get
it
working
is
just
like
insane.
Yeah
yeah.