►
From YouTube: Ortelius General Community Feb. 8 2022
Description
March/April Hackathon, updates from the architecture group and Podcasts are the topic of this General Community Meeting.
A
I
dropped
the
link
in
the
chat.
I
didn't
really
get
a
chance
to
update
it
to
sign
yourself
in
so
today
is
february,
8th,
ortiz,
general
community
meeting
go
ahead
and
sign
in
and
just
some
things
that
we
kind
of
are
looking
at
from
the
last
outreach
and
architecture
meanings
is
we're
trying
to
to
come
up
with
a
way
to
do.
Co-Coding
events-
and
I
want
to
kind
of
I-
I
wouldn't
necessarily
call
them
like
a
mini
hackathon
but
they're
going
to
be.
A
You
know,
extended
meetings,
maybe
an
hour
and
a
half
to
two
hours,
we'll
focus
on
a
set
of
issues
that
we
need
to
to
get
addressed.
A
Yeah,
so
I'm
gonna
be
working
with
sergio
to
figure
out
how
to
get
everything
organized
and
get
get
a
plan
in
place
for
like
getting
on
the
calendar.
B
A
And
and
kind
of
the
thought
is
that
we'll
probably
use
the
extend
out
the
time
slots
that
we
have
for
the
architecture
meeting
on
thursdays,
instead
of
it
being
we'll
just
extend
it
out
for
a
couple
hours.
So
folks
can
join
in
on
that,
but
more
to
come
on
that.
So
just
keep
an
eye
out.
A
B
A
Yep
so
same
time
as
this
meeting,
basically
the
summer
google
summer
code,
we're
gonna
sit
this
one
out
for
this
time
we
did
get
a
request
from
chico's
africa
and
I
did
not
look
at
that.
What
did
anybody?
Simon
and
tracy?
Did
you
look
at
the
chico's
africa?
I.
A
B
Wanted
to
do
it
and
he
thought
it
was
a
great
program.
He
just
didn't
think
we,
if
we
were
going
to
have
time
this
year,
to
have
a
mentor,
because
I
know
he
thinks
that
sasha's
got
his
head
into
some
other
things.
So
it
was.
Maybe
we
go
ahead
and
sponsor
it,
but
we
can't
participate
as
mentors
this
year.
A
Yeah,
that
sounds
like
a
good
plan.
We
got
to
get
the
this
release
wrapped
up
and
out
the
door
and
some
other
things
that
are
happening,
that
we
need
to
get
some
new
ideas
in
the
pipeline
from
the
architecture
side
and
we're
going
to
pull
that
together.
So
that
sounds.
D
Yeah,
that
sounds
sounds
good
to
me.
I
mean
I
really
enjoyed
doing
it,
but
at
the
moment,
this
time
I'm
having
a
bit
of
a
tough
time
with
this
client.
That's.
B
D
It's
not
tough
for
now,
we've
gone
over
that
we've
gotten
over
the
part
where
we
people
are
now
involved
in
getting
thinking
this
update,
they're,
taking
responsibility
from
then,
but
I'm
just
busy
training
a
developer
to
take
over
the
micro
services
which
we've
migrated.
So
I
could.
B
D
B
In
that
time
zone
that
we
can,
that
potentially
might
be
able
to
help.
D
A
Yeah
because
I.
A
A
couple
new
folks
coming
out
of
sweden
and
germany
that
may
be
able
to
help
or
may
be
able
to
do
it,
but
I
don't
know
their
what
we
can
do.
You
know
their
their
time,
commitment
and
stuff
like
that.
So
I
think
I
think
right
now,
like
tracy
said,
I
think
we
should
sponsor
but
not
mentor
and
then,
as
we
get
things
kind
of
worked
around
on
our
side,
that
we
can
go
ahead
and
do
it
again
because
I
think
they
I
don't
know
their
their
cadence.
If
they
do.
A
E
B
What
I,
what
I'll
do,
is
I'll,
send
an
email
out
to
the
general
group
and
see
if
there's
anybody
who
would
be
interested
in
picking
up
that
mentorship
this
time
and
then,
if
not
I'll.
Let
her
know
that
we're
going
to
send
her
the
500
bucks,
but
we
can't
support.
We
don't
have
the
bandwidth
to
support
a
mentee.
F
F
B
We
have
our
next
week
is
our
our
first
podcast
for
the
year
ryan's
gonna
be
interviewed
on
trends
and
devops.
Sasha
and
syme
are
the
hosts.
B
We
have
I've
scheduled
it
to
be
broadcast,
we're
going
to
record
it,
of
course,
on
zoom
and
then
I'll
post
it
up
to
plug
the
audio
file
up
to
a
buzz
sprout,
but
we
are
going
to.
We
are
going
to
hold
it
on
twitch
as
well.
B
C
B
If
you
want
to
his,
his
email
is
just
matt
at
deploy.
C
B
Because
then,
you
can
touch
base
with
him
about.
He
should
be
the
person
managing
the
twitch
for
the
podcast,
so
be
sure
you
touch
base
with
them
before
you
might
want
to
do
a
test
or
something
with
them.
C
B
Yeah
and
he
can
have
fun
he
can
put
like
you
know
you
can
put
little
names
of
everybody.
You
can
put
a
chat
on
there
if
you
wanted
and
then
we'll
just,
but
we
will
be
hosting
it
on
zoom,
so
I'll
be
able
to
take
the
audio
file
and
then
I'll
upload
it
to
bus
sprout
and
then
we'll
and
then
we'll
do
the
social
networking
around
it.
A
Did
we
ever
figure
out
twitter
live.
C
Yes,
a
lot
of
the
folks
are
doing,
I
think,
in
the
periscope.
They
are
doing
live
stream,
not
many
people,
but
I
think
the
twitter,
when
you
you
see
there
is
twitter
spaces
happening
all
the
time
rather
than
people
going
live
there.
I
don't
know
why
people
are
going
there
there.
I
think
we
can
leverage
the
twitter
space
in
the
future
as
well.
I'm
doing
I
have
schedule,
I
have
hosted
two
of
them
and
it's
been
a
wonderful
experience,
so
I
will,
I
think
we
can
utilize
twitter
space
as
well.
C
Yes,
absolutely
we
have
set
it
up.
I
think
search
you.
As
some
said,
you
have
all
the
credits
or
the
doing
things
live
as
well.
So
if
the
the
person
we
I
I
we
can
utilize
the
linkedin
live
as
well,
because
I
think
we
can
grab
more
audience
over
there
because
a
lot
of
the
people
doing
the
linkedin
live,
they
grab
more
audience
like
the
technical
audience
they
all
are
already
available.
There.
B
B
C
Share
the
knowledge
on
the
linkedin
live.
You
have
to
actually
check
the
geographical
equation
as
well
like
previously,
I
have.
I
will
try
to
set
up
for
myself
doing.
Some
live.
Linkedin
live
stream
there,
but
there
are
geographical
restrictions
there.
It
won't
be
available
on
the
asia
side.
I
have
to
check
it
again,
like
is
it
available
right
now
on
the
site
might
be
me
or
sasha
we
can
host
this
linkedin
live
as
well.
Well,
I
will
try
to
touch
with
brian
as
well
like
how
we
can
able
to
utilize
this
platform
as
well.
A
C
I
C
G
So
sasha
you're
gonna
host
the
the
podcast
next
week.
Well,
science.
D
G
Eject
from
the
jet
is
there:
is
there
anything
you
guys
recommend
I
do
to
prepare?
Is
it
or
coffee,
coffee?
Okay,
I
can
do
that.
B
No
we're
trying
to
run
the
we're
trying
to
run
the
podcast
as
kind
of
relaxed
as
possible.
Okay,
but
yeah
brian.
If
there's
any,
I
think
we,
I
think
matt
put
together
a
shared
doc
between
the
three
of
you.
So
if
you
have
any
questions
that
you
might
want
to
ask,
have
them
ask
you,
and
that
would
be
a
good
place
to
put
it
and
then
sasha
and
simon
can
figure
out
who's
going
to
ask
the
questions,
but.
G
My
shared
docks-
and
I
don't
think
I
have
it-
let's
short
the
other
direction
yeah
I
do
not
so
do
if
you
know,
if
you,
if
there
is
so
I
have
to
oh
here,
we
go
feb.
16
podcast
got
it.
Thank
you.
Yep.
B
G
A
B
Try
to
keep
it
slanted
with
a
kind
of
a
cloud
native
microservices
focus
as
well,
even
though
we're
talking
about
devops.
B
And
I
have
us
on
buzzfra
connected
to
spotify,
but
I'm
thinking
about
and
connecting
us
they're
kind
of
pissing
me
off
right
now.
A
Well,
we'll
we'll
follow
who's
it.
Neil
young.
A
B
B
A
E
A
So
this
is
the
some
of
the
stuff
that
utkarsh
is
working
on
our
3d
layout
of
history
for
an
application
version,
so
he's
been
able
to
isolate
this
out
of
the
demo
library
from
who
curses?
Is
this
a
viz.js
or
d3s.
A
Okay,
cool
nice,
so
this
is
one
style
and
the
other
one
I
liked
was.
I
think
this
one,
a
little
less
cluttered
kind
of
gives
the
idea.
But
what
we'll
have
is
these
will
be
deployments
over
time
and
the
height
will
be
the
number
of
versions
in
that
from
the
base
version
in
that,
and
then
each
row
will
be
a
component
so
kind
of
building
that
out.
A
No,
it's
just
the
color
and
this
one
they're,
just
it's
just
some
sample
data.
So
each
each
row
here,
like
this
green
row
and
then
this
multi-color
row
here
will
be
so.
This
will
be
one
component
because
in
a
in
the
logical
view
of
an
application,
you
have
multiple
components
that
are
part
of
it,
and
then
you
have
multiple
versions
of
of
that
component.
A
So
each
row
here
will
be
a
a
component,
so
whether
we
have
the
shopping,
cart
payment
service
ad,
you
know
product
management
whatever,
so
those
each
row
will
be
a
component
and
then
this
axis
here
will
be
the
number
of
deployments
of
the
application.
So
this
is
this.
This
is
kind
of
like
a
backwards
representation,
but
so
your
first
deployment
will
be
low
because
you
only
have
one
version
of
the
component
and
then
the
next
time
you
deploy
maybe
only
two
out
of
the
ten
services
change.
A
So
you'll
see
two
rows
here:
stack
up
to
be
too
high
and
the
rest
will
be
still
at
the
one
level
and
then,
as
we
go
through
time
and
keep
on
doing
our
deployments,
the
stacks
will
get
higher
and
what
this
will
represent
is
like
these
here,
where
we
have
components
that
have
never
changed
since
the
very
first
deployment.
A
But
then
we
have
something
like
the
this
other
row
that
is
constantly
changing.
So
it
kind
of
gives
you
that
that
visualization
to
see
in
a
logical
view
of
an
application
which
components
are
changing
a
lot
and
kind
of
gives
you
that
visualization
of
of
understanding,
where
your
change
is
actually
happening
with
your
application.
A
G
A
Yeah
I
mean
yeah,
that's
how
well
and
like
I
said
this.
This
graph
here
is
kind
of
backwards
because,
as
we
go
through
time,
we're
we're
we'll
have
the
columns
slowly
increase
right
right,
it
will
go
down
and
up
you.
It
won't.
A
You
may
get
an
occasional
one
where
you
go
back
down
where
they
like
roll
back
back
yeah,
but
that's
the
concept
that
we're
working
on
so
ukarsha
is
working
on
this,
and
thank
you
for
for
getting
this
pulled
out
of
the
the
sample
world
and
working
standalone,
because
I
know
that
can
be
the
that's
like.
The
first
major
challenge
is
to
get
things
pulled
out
of
the
example,
libraries
and,
and
now
we'll
be
able
to
plop
in
our
own
data.
A
And
what
will
happen
is,
on
the
back
end,
we'll
create
a
new
python,
fast
api
microservice
to
load
up
the
data
at
that
level.
So
we'll
have
the
front
end
piece
and
then
the
back
end
piece
so
more
more
microservices
on
the
horizon.
Folks.
That
will
be
writing
for
artelias,
so
keep
stay
tuned
for
that
for
some
little
projects
and
just
to
give
everybody
the
background
of
our
microservices
they're
written
in
python
under
fast
api.
A
We
finally
chose
that
after
a
couple
stumbles,
but
it
gives
us
built-in
swagger
gives
us
a
bunch
of
stuff
recovery
at
the
pod
level.
So
if
the
container
crashes,
we
have
this
whole
simple,
retry
logic
and
the
whole
program
is
like
under
300
lines
long.
A
So
that's
what
we're
striving
for
these
is
these
small
mini
microservices
to
keep
bolting
on
to
our
monolith
that
we
have
that's
all
in
java.
B
B
A
So
simon
will
make
sure
that
matt
loops
back
around
with
you
and
we
get
a
test
run
going
in
place.
A
And
simon,
do
you
have
a
like
a
calendar
link
to
your
calendar.
C
It
now
doesn't,
but
I
will
try
to
find
it
like
I
will
able
to
when
I
do
a
thursday
I
have
so.
I
will
share
with
you.
A
That
need
to
like,
let
people
kind
of
self-choose.
Let
me
get
you
the
product.
A
So
in
the
chat
is
what
I
trace
and
I
use
it's
it's
one
once
hubs
schedule
once
and
you
can
sign
up
for
a
free
account
connected
to
your
google
and
you
can
pick
and
choose
the
the
time
slots
and
how
long
it
just
makes
it
an
easy
way,
and
you
can
send
somebody
a
link
if
you
want
them
to
give
them
a
30
minute
slot.
You
can
send
them,
there's
a
link
for
a
30
minute
slot
versus
a
15
minute
slot
those
type
of
things.
A
So
that's
the
one
I
like
to
use.
I
we
did
use
calendary
before,
but
I
ran
into
problems
with
it.
Syncing
up
with
google.
A
But
that's
that
is
another
one
to
try.
Sometimes
it
may
work
depending
on
what
you
got
going
on
with
your
calendar.
My
calendar
can
get
pretty
crazy.
B
Only
other
thing
was
for
the
hack,
the
our
our
hack
hour.
We
were
gonna,
do
it,
we
were
gonna
figure
out
what
was
the
best
time
for
everybody.
Do
we
want
to
just
pick
out
a
time,
and
I
can
just
post
it
or
how
do
you
want
to
announce
that
I.
A
B
B
G
I
haven't
used
dev
post,
but
I
don't
know
I
just
stumbled
across
dev
post.
Are
you
familiar
with
that?
No
all
right
I'll
shoot
a
link
over
you
might
see
if
there's
a
fit
there,
it's
just
devpost.com
and
it
is
a
sort
of
public
hackathon
listing
they
do
some
of
the
back
end.
Coordination.
A
And
there
is
another
one
that
I
ran
into
if
you
folks
don't
mind
running
over
for
a
few
minutes,
there's
another
one
where
we
may
just
kick
this
down
to
the
outrage
committee,
but
where
you
would
tag
certain
issues
with
the
bitcoin
value
and
then,
if
you
close
that
issue,
then
you
get
the
bitcoin.
A
It's
just
another
way
to
kind
of
get
folks
interested
and
and
get
a
little
bit
of
money
in
their
pocket.
It
wasn't
huge,
I
think
it
was
called
git
coin
was
one
of
the
companies
that
that
I
I
remember
running
into
a
trade
show
at
one
point,
but
that
may
be
something
we
want
to
look
at
is
is
assigning
some
value
to
some
of
the
issues
to
to
get
it
taken
care
of.
B
B
And
extend
the
two
architecture
meetings
to
an
hour
and
a
half
that
work.
A
I
I
just
remember
talking
to
guy.
This
is
like
three
four
years
ago,
but
I
it
may
be
interesting
to
to
look
at.
A
All
right,
everybody
thank
you
and
we
will
stay
tuned.
I'm
going
to
be
working
with
sergio
to
get
those
issues
cleaned
up.
Hopefully
this
week
and
syme
and
brian
and
sasha
good
luck
on
the
podcast
excellent
thanks,
I'm
going
to
wear
a.