►
From YouTube: December 15, 2020 Ortelius General Community Meeting
Description
Discussions on goals for the coming year, component sets and website design are just a few of the topics covered during this Ortelius General Community call.
B
A
B
B
What
that
meant
briefly
and
so
right
now
we're
gonna,
put
notifications
kind
of
on
the
the
back
burner
and
focus
on
one
of
the
the
higher
prioritizations,
which
is
part
of
the
delivery
plan
that
we
have
there,
which
is
the
component
sets,
is
what
I'm
calling
them.
We
also
did
talk
about
graph
databases.
A
B
A
A
A
A
A
B
A
B
A
D
B
I
kind
of
doing
these
out
of
order
here,
and
forgive
me
I
just
didn't-
have
a
chance
to
update
this.
So
if
there's
anything
I'm
missing,
I
know
I'm
missing,
priya
shots
web
forum
in
here
tracy
you
did
look
into.
We
did
talk
about
the
reward
system
and
that
really
came
out
as
kind
of
like
a
best
way
to
describe.
B
A
A
A
And
I
did
create
a
link.
Well,
I
renamed
I
renamed
a
group,
so
ortillius
does
have
now
a
linkedin
group.
It's
called
artillious
microservice
configuration
management
and
there's
about
300
people
in
it
because
I've
been
building
it
up
over
the
course
of
the
last
year.
So
if
you
guys
make
sure
that
you
are
part
of
it
steve
could
you
bring
it
up.
A
B
E
D
D
D
A
B
B
B
B
B
B
B
B
Okay
I'll
circle
back
around
because
that's
what,
when
I
started
messing
with
it,
it
was
like
I
couldn't.
Nothing
was
like
active,
so
looks
like
it's
still
in
like
draft
mode
I'll
circle
around
with
her.
On
that
side
I
did
get
through
all
the
majority
of
the
issues
have
been
reorganized
and
I've
been
trying
to
centralize
them
all
under
the
or
ortelius
repo.
B
So,
even
if
we
have
a
like
an
issue
for
one
of
the
other
repos
I've
been
like
the
docs
or
something
like
that.
I've
been
centralizing
all
the
issues
underneath
the
artelius
repository
just
and
we
go
off
and
refer
to
the
other
repositories
and
stuff
like
that.
So
you'll
see
like
in
here
I
put
in
links
to
the
other
repo
and
examples,
and
things
like
that
as
part
of
that
process,
so
we'll
have
to
cross-reference
the
repositories
and
the
issues
right
now.
B
Also,
we
did
have
a
discussion
on
discord
with
marky
about
a
triage
type
of
website
that
we
can
pull
up
and
look
at
issues
that
we
needed
to
triage
and
kind
of
group
together
based
on
labels
and
tags.
As
part
of
that
he
said
it
was
written
in
golang,
and
that
was
about
as
far
as
I
got
as
the
details,
but
that's
something
that
we
should
look
at
putting
in
place.
Actually
here's
the
issue.
B
So
it
just
gives
you
idea
of
what
we
need
to
look
at
on
a
weekly
monthly
level,
and
we
did
talk
about
auto,
closing
issues
and
it
kind
of
came
to
a
decision
amongst
us
that
were
talking
that
we
would
hold
off
on
auto
closing
issues.
I
know
it's
a
like
stale
issues
and
things
like
that.
I
people
put
issues
out
here
for
a
reason
and
we've
got
to
make
sure
that
we
get
them
addressed
in
some
way
either.
B
I
don't
know
if
this
is
the
right
way
to
do
it
or
if
we
need
to
start
doing
tags
and
labels
and
stuff
like
that,
but
I
just
was
following
somebody's
previous
style,
so
we
can
change
that
up.
I'm
not
attached
to
any
of
this.
So
if
anybody
has
better
way
to
organize
this,
let's
do
that
and
there
was
one
other
thing
on
the
issues.
B
When
you
do
your
pull
requests,
just
a
reminder,
make
sure
go
to
squash
your
local
commits.
If
you
need
help
with
that,
let
me
know
and
we're
gonna.
We
will
probably
start
putting
on
a
validation
step
to
validate
that
the
pull
request
has
an
issue
with
it
and
that
we
may
go
ahead
and
do
when
the
polar
crust
gets
closed.
B
That
the
issue
would
get
closed
because
that's
one
of
the
things
I'm
going
through
manually
is
cleaning
up
issues
manually
once
the
pull
request
has
been
closed
for
it
not
a
big
deal.
We
don't
have
that
many
issues
out
here,
but
it
could
become
overwhelming
down
the
way
so
we'll
need
some
automation
on
that
front.
D
B
H
Okay,
see
important
is
as
we
progress
right
now.
We
are
managing
our
work
in
the
stack
of
github
or
these
word
phase,
but
the
ideal
best
way
is
to
see
the
work
in
a
flow
manner,
something
like
your
kanban
board,
where
you
can
see
what
what
you
have
in
stack,
what
you're
doing
what
you're
not
doing?
What
has
been
progress
and
what
is
not
so
you
get
a
visual
representation
of
your
work
starts
and
easy
work
management
as
well.
So
there
are
many
ways
in
which
it
could
be
done.
H
One
is
trailer
code,
another
is,
could
be
tools
from
conference
or
jada
sort
of
thing,
so
my
proposition
was,
if
you
can
use
trello
board
or
something
else
which
the
people
out
here
can
definitely
recommend
or
suggest
open
for
thoughts,
but
definitely
going
forward
as
we
are
progressing
and
we
are
progressing
a
bit
fast
now,
since
it
has
come
under
the
cds,
this
whole
project
is.
We
need
to
have
visual
representation
of.
D
A
D
A
B
That's
what
I'm
thinking,
because
I
I
don't
think
we're
going
to
be
doing
much
coding
between
now
and
then
end
of
the
year
and
we'll
do
have
we'll
have
little
stuff
going
on,
but
nothing
we
don't
have,
I
think,
at
the
beginning
of
next
year.
We
should
really
do
like
a
launch
for
component
sets,
get
everybody
on
page,
get
all
the
issues
created
and
and
then
actually
really
start
focusing
on.
You
know
some
real
deliverables
that
we're
going
to
try
to
target
for
a
release
date.
B
A
B
B
A
D
D
F
I
B
A
Okay,
yeah
and
then
one
other
last
housekeeping
issue,
so
we're
starting
to
have
trouble,
mapping
discord
names
to
people
and
what
I'm
thinking
about
doing
is
just
putting
a
an
excel
spreadsheet
out
in
the
google
docs.
If
everybody,
unless
there's
objections,
you
put
your
discord
and
your
linkedin
profile.
If
you
have
one
and
your
first
and
last
name,
so
we
can
keep
track
of
people
in
discord.
A
A
Well,
I
want
to
make
sure
everybody's
okay
with
that
for
those
of
you
on
here.
We
have,
you,
know
12
people
on
so
is
there
anybody
who
has
a
a
aversion
to
publicizing
that
information?
Then
I'd
say
just
don't
do
it,
but
it
will
be
easier
for
the
team
to
figure
out
who's
posting
stuff
on
discord
when
you're
new.
Once
we
see
you,
we
know
who
you
are
it's
like.
Oh
okay,.
D
A
A
B
B
B
B
B
A
B
A
C
B
A
B
A
B
B
B
And
then
did
we
get
a?
We
did
talk
to
owen,
he
was
out
of
on
his
farm
doing
work
and
he
doesn't
he's
doing
work
over
his
cell
phone,
so
he
said
he's
going
to
be
back
to
a
better
location.
I
think
this
next
week,
so
he
is,
he
said
he
has
it
done
about
the
the
website.
So
we'll
get
a
demo
here
soon
on
that
front,
and
I
believe
you
got
the
dates
set
up
for
our
podcast
on
webinar.
B
A
B
A
B
J
B
A
B
B
B
So
I'm
working
on
the
build
bot
to
go
ahead
and
push
the
discord
messages
when
you,
when
we
do
a
pull
request
and
we
get
the
build,
gets
completed,
we'll
go
ahead
and
post
to
the
build
bot
christopher.
I
did
see
the
there's
something
we
wanted
to
change.
We
just
want
to
we're
looking
for
a
channel
just
to
throw
a
message
or
messages
at
right.
Is
that
what
we.
D
Need
yeah,
I
I
am
on
another
discord
and
it's
got
tons
of
bots
and
and
activity,
and
so
one
of
the
things
that
they've
got
is
what
they
actually
call
their
bot
commands
room
which
we're
using
for
info,
and
so
we
created
a
builder
room.
But
it's
the
bot
builder
room
is
doing
the
same
sort
of
thing
where
people
could
put
in.
You
know
commands
to
talk
to
the
bots
and
it
wouldn't
spam
the
regular
rooms,
and
it
looks
like
we
still
need
to
enable
some
of
the
bots
in
there.
B
B
Yeah,
so
this
bot
builder
was
the
one
I
was
using
for
the
posting
messages
from
cloud
build,
but
I
see
what
you're
getting
at
and
I'll
go
ahead
and
create
a
new
channel
that
we
can.
That
will
have
access
for
people
to
throw
commands
at
that's
one
of
the
things.
That's
one
of
the
annoying
things
I
find
about
discord
compared
to
slack
slack.
B
B
B
B
B
A
A
Yes,
absolutely,
I
will
promise
everybody
that
this
week
I
will
get
a
blog
web
press
blog
add-in
to
our
website,
and
I
think
that
we
need
to
come
up
with
a
way
to
probably
check
the
blogs
into
github
and
then
and
then
somebody's
going
to
have
to
publish
someone
we'll
have
to
figure
out
a
way.
It'd
be
great
if
we
could
automate
that
in
some
way.
A
B
A
Them
under
the
I
put
your
blogs
under
the
outreach
and
I
will
be
watching
for
it
and
I'll
get
them
posted
and
then,
if
you
do,
post
them
and
I
get
them
posted,
then
I'll
social
network
them
I'll
make
sure
we're
blasting
them
out.
And
if
you
do
a
blog,
let's
say
a
blog
on
any
of
the
cdf.
Any
discussions
we're
having
with
any
of
the
cdf
projects
like,
say
we're
doing
something
with
techdon
or
doing
something
with
spinnaker
around
those
component
sets
you
want
to
write
about
it
then.