►
From YouTube: Ortelius General Community Meeting - September 7, 2020
Description
The Ortelius open source project continues to grow. This meeting held on September 7, 2020 covers the progress to date.
A
Check,
but
there
was
only-
maybe
I
think,
500
or
acres,
but
it's
in
pretty
steep
terrain.
They
worked
on
it
for
a
couple
weeks.
B
A
Okay
yeah,
so
I
we
moved
the
the
meeting
over
to
my
account
because
we're
just
running
into
conflicts
so
also
in
the
calendar.
Invite
is
the
link
to
the
document.
So
if
you
go
in
and
edit
the
the
meeting,
invite
you'll
see
the
link
there
so
go
ahead
and
sign
in,
if
you
can
so
some
of
the
things
that
we
talked
about
last
week
were
to
get
some
working
groups
going.
A
A
So
we
need
to
get
a
time
slot
for
that
and
then
also
a
marketing
and
outreach
working
group
as
well,
so
those
were
kind
of
the
two
ones.
What's
the
easiest
way
for
us
to
get
the
a
time
slot
figured
out,
do
we
just
want
to
decide
that
now
or
do
we
want
to
send
out
an
email
and
go
from
there.
B
I
mean
we
can
do
a.
We
can
send
out
a
what
is
that
tool
that
you
can
send
out
for
voting
on
time
slots.
A
C
A
A
Yeah,
let's
send
out
the
survey
because
I
know
there's
we're
short
people
today
with.
A
Yeah,
so
let's
send
out
a
couple
servers:
let's
send
out
the
two
surveys
for
that
and
I
think
we'll
be
better
off
just
to
be
picking
up
anybody
that
could
make
it
today.
So.
A
So
we'll
get
those
out
this
week,
we
won't,
we
won't
leave
them
open
long.
You
know
we
don't
need
to
leave
them
open
for
like
a
week
or
anything
like
that.
We'll
just
do
a
couple
day.
You
know
maybe
the
end
of
the
week
for
to
figure
out
the
time
slots.
Then
we
can
get
going
on
some
of
the
meetings
next
week,
which
would
be
great,
and
then
I
talked
to
marky
over
the
weekend
and
last
week
and
he
couldn't
make
it
today.
A
So
one
of
the
things
that
he
was
put
on
his
to-do
list
was
some
github
restructuring.
One
of
the
things
I
did
work
out
with
him
was
in
github.
You
have
issues,
and
then
we
were
having
problems.
I
I
was
having
problems
with
getting
people
to
be
assigned
to
the
issue.
What
he
is
working
on
is
at
the
ortelius
level.
A
A
You
know
when
somebody
says
they
want
to
work
on
something
they'll
be
able
to
go
ahead
and
either
assign
themselves,
or
you
know,
whoever
is
managing
that
repo
can
assign
the
person
at
that
level.
So
that's
going
to
help
a
lot
we're
going
to
get
that
going
here,
he's
out
sick
actually,
so,
hopefully,
when
he
gets
back
on
his
feet,
he'll
be
able
to
get
that
wrapped
up.
If
not
we'll
we'll
take
a
stab
at
it,
creating
those
teams
and
and
getting
people
into
the
groups.
A
What
we'll
do
is
we'll
base
it
off
of
the
the
readme.
You
know
where
people
have
decided
which
projects
they
want
to
work
on.
We'll
use
that
as
the
group
membership
for
now
to
figure
out
like
give
us
a
jump
start
also.
I
talked
to
him
about
the
the
contributor
guide
that
we,
the
issue
that
was
open
around,
that
he
had
some
ideas
on
that
was
going
to
take
a
stab.
A
He
wanted
to
put
together
a
google
doc
for
each
high
level
working
group
and
the
contributor
guide
was
was
part
of
that,
so
that
is
is
moving
moving
slowly
as
part
of
that,
and
one
thing
I
need
to
do
is
I
forgot-
is
to
record
this.
I.
B
A
Okay,
good
so
we'll
get
the
recording
pushed
up
to
youtube
as
part
of
that
and
getting
the
links
in
the
contributor
guide.
So
basically
people
know
you
know
what
what
each
repository
is
working
with
just
some
basic
stuff
that
he
had
some
ideas
on
also
we'll
be
looking
for
getting
some
twitter
stuff
out
there
on
the
social
media
side
and
looking
for
right
now,
blogging
on
medium
about
ortelius,
we're
not
going
to
start
off
with
our
own
blog
site,
we'll
just
go
ahead
and
use
medium
for
now.
A
Also
markie
was
going
to
put
together
a
quick
session
on.
He
had
it
in
his
discord
channel
where
he
was.
A
He
was
working
on
a
a
way
to
I
didn't
see
it
there,
basically
like
a
getting
getting
started
guide
with
git
and
github,
and
he
was
going
to
record
that
basically
do
a
video
type
of
of
working
session
on
how
to
get
get
working.
A
I
think
he
was
gonna,
make
it
interactive
as
part
of
that.
So
the
set
up
a
scenario
of
I
have
a
pull
request.
You
know
what
are
the
steps
you
need
to
go
through
to
squash
emerge
and
what?
What
does
a
good
comment?
Look
like
those
type
of
things
was
the
session
that
he
was
going
to
be
putting
together
so
keep
a
heads
up
on
that
about.
A
If
you
want
to
get
to
go
through
that,
it's
a
good
thing,
because
everybody
does
things
a
little
bit
differently.
Around
github
markey
was
one
of
those
one
of
the
release
coordinators
for
kubernetes.
So
he
has
a
lot
of
background
with
dealing
with
you
know,
merging
and
prs
and
along
those
lines.
A
On
that
same
note,
on
the
ortus
discord
channel
just
make
sure
that
you're
out
there
and
you
can
pick
up
the
announcements
that
we'll
see
out
on
one
of
the
get
the
the
announcement
channel.
As
part
of
that,
I
forgot
to
finish
my
thought
there,
I'm
going
to
come
back
to
growing
the
team
here
in
in
a
second,
oh,
so
there's
the
link
to
the
cdf
checklist,
and
one
of
the
things
that
we
need
to
see
is.
A
If
somebody
could
take
a
look
at,
I
don't
know
if
we
need
to
create
an
issue
for
this
or
a
pr
to
figure
out
where
we're
at
and
what
needs
to
be
done.
Kind
of
dan
gave
us
the
the
checklist
and
we
just
need
to
go
through
and
see.
You
know,
we've
completed
half
of
it
and
we
have
this
other
stuff
to
do
or
we're
80
of
the
way
through
as
as
part
of
that
list.
A
So
if
anybody
wants
to
volunteer
for
taking
a
look
at
that,
that
would
be
great
and
a
lot
of
it
is
just
the
organizational
pieces
the
contributor
guide
coming
into
play.
You
know
the
the
license.
You
know
that
we
have
licensing
in
place
those
types
of
things,
so
it's
not
anything
like
really
around
how
the
code
is
structured
but
more
around
the
organization
of
how
the
open
source
projects
being
handled
on
the
pr
side,
I'm
going
to
have
some
downstream
maintenance
fixes
going
in
this
week
from
deploy
hub.
A
We
found
a
couple
bugs
that
were
pushing
up
into
from
the
downstream
back
into
the
upstream.
Also
we
have
the
enhanced
reporting
that
we
talked
about
last
week.
I
did
not
get
a
chance
to
do
a
sample
yet,
but
I
did
work
with
a
couple
people
on
getting
their
development
environment
up
and
going
as
part
of
that
process.
A
Javascript,
the
one
thing
that
we're
that
I'm
considering
and
this
is
going
to
come
back
to
the
architecture
meeting
is
if
we
want
to
start
doing
these
as
microservices
themselves.
A
These
reports,
because
they're
pretty
isolated
and
they
may
be
a
good
place
for
us
to
start
with
a
a
instead
of
tacking
on
to
the
monolith
that
we
have
actually
breaking
out
these
reports
into
microservices
at
that
level.
A
So
I
think
we'll
take
a
look
at
how
that
schedule
comes
about,
and
hopefully,
by
by
next
week,
we'll
have
a
architecture
meeting
that
we
can
talk
about
that
look
at
still
and.
A
A
A
We
still
need
some
creative
genius
for
our
our
logo
to
come
up
with
a
new
new
logo
and
then
please
go
to
the
main
readme
and
fork.
It
fork,
the
main
repo
and
add
yourself
as
a
contributor
to
the
section
that
you
like
you're
interested
in.
So
this
is
the
read
me
off
of
the
main
project,
just
pick
which
section
or
subcommittee
you're
interested
in
and
go
ahead
and
fork
and
add
yourself
to
that
as
part
of
that
process,
that'll.
A
Yeah
it's
the
basic
yeah
it'll,
get
through
the
basics
of
checking
in
and
those
types
of
things
and
understanding
of
a
basic
pr
nobody's
going
to
scream
at
you.
If
you
do
a
pr
wrong
or
anything
like
that,
this
is
this
is
a
friendly
environment.
You
know
everybody's
learning
here
as
part
of
this
process
and,
like
I
said
even
it's
gonna,
be
interesting.
I'm
looking
very
forward
to
markies
how
to
get
get
working
correctly,
because
you
know
how
I've
been
using
it
and
how
it's
being
used
in
a
larger
team.
A
Larger,
open
source
teams
can
be
interesting
to
to
understand
so
just
jumping
back
to
ideas
for
growing
the
team
just
want
to
open
it
up
for
that
and
anything
else
that
we
need
to
cover.
B
I
think
it'd
be
helpful
to
see
what
what
work
has
been
done.
I
know
that
there's
some
on
the
team
that
are
starting
to
do
coding
updates.
Would
you
mind
just
covering
those
those
folks
who
have
started
doing
some
work
in
that
area?.
A
Yep,
so
some
of
the
people
have
started
with
the
main
repository.
I
worked
with
a
couple
people
to
go
ahead
and
check
out
the
main
repository
and
from
there
we
set
up
eclipse
to
deal
with
the
java
code,
which
is
in
this,
the
dm
admin
web.
A
So
this
is
where
the
eclipse
project
lives,
so
we're
able
to
actually
get
that
all
up
and
running
one
of
the
things
that
did
come
about
that
was
because
ortelius
uses
a
postgres
database,
the
you
can
install
postgres
locally,
but
it
was
decided
on
those
calls
that
we're
going
to
just
do
a
hosted
postgres.
So
we
could
have
shared
test
data
over
on
azure
and
there's
an
issue
open
on
that
to
go
ahead
and
and
work
with
azure.
A
So,
if
anybody's
interested
in
setting
up
postgres
on
azure
just
grab
the
ticket,
you
can
take
it
away
from
me.
I'm
I'm
happy
to
have
less
work,
but
the
idea
was
to
get
some
shared
data
that
people
can
for
their
development
and
local
testing
that
they
can
point
to
a
shared
database
at
that
level.
A
So
that
was
the
main
part
or
main
thing
we
focused
on
was
getting
the
those
pieces
up
and
going
other
people
have
been
going
in
and,
like
I
said,
learning
the
basics
getting
some
of
the
documentation
updated.
A
So
if
you're
looking
for
easy
issues
to
work
with,
go,
look
at
the
docs
repository
and
we'll
have
a
couple
issues
out
here
that
we
need
to
look
at,
and
this
is
where
right
now,
it's
kind
of
hard,
because
we
don't
have
anybody,
we
have
no
assignees,
but
that
will
get
fixed
as
per
that
level.
So
there's
a
couple
things
over
in
documentation
and
there's
there's
always
updates
that
we
need
to,
like,
I
said,
the
the
main
readmes
about
the
contributor
guide.
A
A
B
And
in
terms
of
those
working
groups,
steve
are
we
going
to?
Are
you
going
to?
Are
we
going
to
start
trying
to
get
meetings
for
each
of
those
working
groups?
Is
that
what
the
goal
is
to
send
out
the.
A
Just
the
first
two,
so
the
architecture
and
marketplace:
that's
one
group.
B
B
A
Is
the
other
group
so
we'll
just
have
those
two
as
the
starting
point
and
then,
if,
if
we
need
to
get
into
like
a
developer
specific.
A
B
A
I
just
had
a
one.
Sorry,
I'm
drawing
a
blank
here,
something
with
github.
A
I
can't
remember
any
any
comments,
questions,
any
ideas
that
we
can
put
together
for
growing
the
team.
B
Yeah
we're
starting
down
that
road
and
in
fact
markey
and
I
are
on
a
keynote
at
devops
world
talking
about
open
source
and
we
talk
about
the
artillious
project.
So
I
I
can
take
take
that
on
as
a
as
an
effort.
E
Yeah
hi,
this
is
canal,
I
think
value
proposition
is
important
and
beyond
that,
just
understanding,
like
you
know,
at
the
different
levels,
like
an
understanding
at
the
30
000
feet
level,
and
then
I
think,
understanding
from
a
nuts
and
bolts
level
is
necessary,
especially
for
like
technical
people
like
myself,
who
you
know,
I
won't
even
touch
a
project
unless
I
understand
from
the
top
all
the
way
to
the
bottom,
because
then
I
can
kind
of
get
motivation
as
to
okay,
here's
the
reason
why
this
system
is
being
built
or
this
integration
is
happening.
E
I
think
it's
very
important,
I'm
just
being
for
myself
that
other
developers
can
kind
of
chime
in
and
let
me
know
does
that
even
make
sense
to
them
that
they
know
from
the
the
big
picture
all
the
way
down
to
the
nuts
and
bolts.
A
Yeah,
I
think
that's
a
great
idea-
and
I
think
part
of
the
the
value
proposition
will
take
care
of
the
30
000
foot
view
we'll
just
have
to
work
on
getting
the
the
the
transition
down
all
the
way
to
the
nuts
and
bolts
yeah.
E
I
mean
this
is
kind
of
standard.
Like
I've
been
a
consultant
many
places.
What
they
have
is
a
standardized
document,
so
they
start
off
with
a
high-level
design
document,
and
then
they
go
down
to
technical,
specs
database
design
documents,
api
design
documents
which
are
then
you
know
nuts
and
bolts
so,
but
they
always
start
with
a
high
level
and
then
kind
of
deep
dive
and
during
the
high
level
they
do
business
requirement
documents
and
other
things
too.
A
Yeah
and
that's
where
markie
was
working
on
that
part
of
the
contributor
guide
and
the
team
assignments,
so
at
least
at
the
30
000
foot
view
putting
some
meat
around
the
in
the
the
different
pieces
at
that
level.
You
know
about
what
what
does
it
mean
to
be
part
of
the
outreach
group?
You
know
what
does
it
mean
to
be
part
of
the
developer
group?
A
You
know
those
type
of
things
and
then
we'll
get
into
each
working
group
will
be
producing
its
own
documents
as
well.
So
when
we
get
into
design,
docs
will
start
creating.
You
know
google
docs
or
mark
markdowns
that
we
can
reference
as
part
of
the
pr
and
people
can
contribute
to
as
part
of
the
design
doc,
because
that
seems
to
work
really
well
as
part
of
that
the
shared
docs
and
being
able
to
to
edit
and
comment
on
them.
A
What
like,
like
you,
said,
one
of
the
things
that
we'll
need
to
do
is
really
focus
in
on.
We
need
to
get
into
those
technical
documents
is
to
focus
in
on
a
specific
problem
that
we're
going
to
try
to.
D
Yeah
hi,
I
wanted
to
ask,
since
we
have
a
couple
of
virtual
conferences
coming
up.
So
is
there
any
plan
to
like
set
up
a
virtual
booth?
We
can
like
arrange
for
demos
and
even
like
get
access
to
some
mailing
lists.
A
B
Yeah
we
have,
I
have
we
deploy
hub,
will
be
at
both
cdcon,
we'll
be
at
devops
world
and
we'll
be
at
cubecon.
So
that's
september,
october
and
november,
and
deploy
hub
will
have
access
to
the
folks
who
show
up
to
our
booth
and
we're
gonna
have
ortillius
material
at
the
booth,
so
we
can
submit
once
we
after
the
shows.
We
can
create
a
like
a
mailing
list
around
ortillius
for
recruiting
potential.
A
So
a
lot
of
the
well.
B
A
Yeah
and
I
think
what
we'll
need
to
keep
an
eye
out
for
is
call
for
submissions
for
the
spring
virtual
conferences,
because
they'll
start
doing
call
for
papers
and
call
for
speakers
about
two
to
three
months
ahead
of
time
from
the
shows.
So
I
think
for
the
next.
You
know
all
the
way
through
november
those
have
been
basically
already
pretty
much
locked
down,
but
when
we're
looking
at
the
next
trade
show
for
lack
of
a
better
word
season
will
start
usually
march
time
frame.
So
what
to
keep
an
eye
out.
A
So
if
you
guys
see
any
virtual
conferences
and
calls
for
papers,
please
let
us
know,
and
we
can
get
to
pull
something
together
and
get
it
submitted.
A
Working
group
schedules,
so
please
get
that
once
you
get
to
the
survey
goes
out
we'll
try
to
get
that
wrapped
up
by
next
week,
so
we
can
start
having
working
group
meetings
next
week
and
then
also
one
last
question.
I
did
remember
what
I
was
thinking
about
on,
like
the
github
side.
Does
anybody
have
problems
with
google
groups.
A
Okay,
so
the
reason
why
I
was
asking
you
know
how
the
when
you
see
people
trying
to
edit
the
document
here
and
it
shows
like
an
anonymous
mouse
or
you
know
all
these
weird
characters
are
showing
up.
I
found
out
that
that's
because
we
sent
out
the
initial
link
to
the
document,
as
with
anybody
that
can
anybody
that
has
this
link
can
edit
the
document
and
when
that
happens,
google
decides
to
make
everybody
anonymous.
A
So
if
we
restructure
the
this
document-
and
you
can
give
a
google
group
access
to
the
document
and
then,
if
you're
part
of
the
that
group,
when
you
log
in
you're,
going
to
be
able
to
see
your
name
and
we'll
be
able
to
track,
who
made
comments
and
stuff
like
that
on
these
documents,
because
that's
really
important
for
us
to
know
who
you're
who's,
making
a
comment
and
who's
making
updates
just
makes
it
easier
to
have
offline
chats.
A
It's
it's
the
bizarre
thing
unless
you
like
specifically
log
in
to
that's
where
we
got
an
anonymous
walrus.
A
I
have
no
idea,
but
that's
what
I
was
reading
about
that
so
we'll
use
the
yeah
and
also
allow
us
to
have
people
join
the
they'll
just
go
and
join
the
google
group
and
then
from
there
all,
the
the
permissions
will
get
associated
to
all
the
documents
and
everything
else
and
all
the
anything
that
has
to
do
with
with
google
would
be
based
on
that
group,
and
it
just
makes
the
security
a
lot
easier.
A
So
if
you're,
a
member
of
the
the
the
group,
then
you're
gonna
have
the
right
permissions
to
go
edit
things
and
when
that
happens,
we're
gonna
we'll
get
rid
of
this
anonymous
unicorn.
So
all
right,
that's
all!
I
wanted
to
wrap
up
with.
Thank
you,
everybody
and
we
will
keep
an
eye
out
for
the
survey
and
we'll
touch
base
in
a
couple
weeks.
Then.