►
From YouTube: January 12, 2021 Ortelius General Community Meeting
Description
Our first 2021 general community meeting for Ortelius covered our 2021 goals and how to track project initiatives. The use of GitHub boards vs. Trello boards was covered as well as how to coordinate some of the activities between the Outreach and architecture meetings.
B
B
B
Everybody
knows
that
I'm
into
having
measurable
goals,
and
we
talked
at
the
end
of
last
year.
We
talked
a
little
bit
about
some
of
the
goals
that
we
have
and
we
actually
put
together
a
excel
spreadsheet
that
had
goals
for
technical
updates
on
the
product
and
where
the
open
source
roadmap
needs
to
go,
which
thank
you
very
much
for
everybody.
For
noting
that
I
will
review
it
with
the
technical
oversight
committee.
B
I
have
a
meeting
scheduled
with
them
sometime
in
february,
but
in
terms
of
of
common
goals
between
the
architecture
and
between
the
outreach.
The
goal
that
I
really
would
like
us
all
to
focus
on
is
the
goal
of
adoption
in
two
two
places:
number
one
adoption
for
an
easy
on-ramp
for
new
open
source
contributors.
B
There
was
some
work
done
on
that
siddharth
started
a
developer
guide.
Now
we're
calling
a
contributor
guide
that
was
steve
and
siddharth
and
myself
we
worked
on
that
and
that
has
been
published.
If
you
go
out
now
to
the
artillius
documentation,
you
will
see
that
there's
two
docs
there's
a
user
guide
and
a
contributor
guide.
B
So
all
of
us
need
to
look
at
that
contributor
guide
and
see
if
we,
if
there's
other
things,
that
we
need
to
add
to
that
contributor
guide,
to
make
it
easy
for
new
people
in
the
open
source
community
to
get
started.
You
know
where
they
you
know
where
github
is
whether
how
to
do
a
pull
request
where
the
the
community
docs
are,
if
there's
anything
that
we've
missed.
If
we
could
all
take
a
look
at
that,
I
would
very
much
appreciate
it.
B
We
have
the
unique-
and
maybe
we're
not
unique,
but
we
have
a
lot
of
people
on
this
in
this
group
that
have
never
been
in
an
open
source
community
before
so.
Those
of
us
who
have
your
input
to
make
it
easy
for
for
new
people
to
create
their
full
pull
request.
Their
first
pull
request.
I
would
love
to
have
everybody
have
had
the
experience
of
creating
their
full,
their
first
pull
request
and
understand
what
that
feels
like
the
second.
B
So
we
need
to
have
videos
and
blogs
and
and
on
tips
and
tricks
in
in
using
the
product,
or
we
need
feedback
that
says
this
sucks
and
if
it
sucks,
we
need
to
know-
and
we
need
to
understand
it
and
get
some
poor
issues
opened
out
there.
So
we
can
start
addressing
it
so
for
the
next
month,
we
really
are
going
to
work
on
those
those
two
areas
making
it
easy
for
new
people
to
contribute
and
making
it
easy
for
new
people
to
become
users.
B
We
are
going
to
be
having
a
blogathon
starting
february.
Siddharth
is
working
on
sorting
out
a
reward
system
through
electronic
badges.
Garima
is
working
on
a
a
reward
schedule
and
she's
gonna
present
that
to
the
group
and
she
gets
it
finished,
I'm
hoping
that
that
soon
so
we're
working
on
a
ways
to
create
a
reward
system
for
work.
Well
done.
I
would
love
to
send
out
t-shirts
and
we
might
do
that,
but
unfortunately
like
getting
karam
and
sasha
t-shirts,
look
like
another
100
bucks.
B
B
A
B
A
D
C
B
I
don't
want
to
be
you
know
to.
I
don't
want
to
damper
anybody's
creative
juices,
but
I
think
I
think
the
goal
is
useful
content
around
those
two
topics,
so
useful
content
for
some
somebody
who's
never
contributed
to
an
open
source
project.
Before
I
know
I
have
posted
links
to
areas
that,
like
the
jenkins
community
has
created,
but
if
there's
things
that
are
specific
to
contributing
to
ortillius
that
they
should
know
about,
then
it
would
be
great
to
have
a
you
know:
tips
tips
for
contributing
to
artillius.
B
A
B
B
This
is
how
you
define
your
domain
structure
and
decompose
your
application
and
pull
together
a
domain
structure
to
track
your
decomposed
objects
and
then
there's
the
lower
level
technical
things
that
I
know
people
are
going
to
want
to
know.
I
posted
a
a
blog
on
how
to
use
a
helm
with
deploy
hub,
and
that
tends
to
get
a
lot
of
traffic.
So
people
are
looking
for
those
kinds
of
answers,
so
anything
that
you
find
that
you
realize
this
was
an
easy
way
to
do
something.
B
C
B
Bite
size,
videos,
yeah.
I
think
that
a
whole
podcast
series
that's
entitled
conversations
with
the
big
giant
head
and
just
have
steve
talking
about
answering
all
the
questions
that
I
know
that
people
have
asked.
It
would
be
a
really
great
a
good
like
blah
podcast
or
our
video
series.
Somebody
has
to
think
through
what
that
you
know
what
conversations
with
the
big
giant
head
would
include,
but
I
think
that
something
like
that
would
be
a
lot
of
fun
and
be
very
it'd,
be
very
useful.
A
A
B
Of
people
want
to
read
about
not
just
as
it
relates
to
ortillius,
so
that
could
be
a
really
great
way
to
drive
traffic
back
to
our
website
and
siddharth.
On
that
question,
you
know
if
we
really
talk
about
what
the
original
goal
was,
is
that
the
original
goal
is
to
get
more
people
who
are
core
contributors
of
the
product
and
more
users,
and
one
of
the
leading
indicators
was
how
many
hits
on
the
website
that
we
would
find
and
that's
what
led
us
to
the
blogathon.
B
So
let
me
restate
the
goal.
The
goal
is
to
drive
traffic
to
the
website.
So
if
you
have,
if
you
have
a
discussion
that
you
want
to
have
on
what
you've
learned
around
kubernetes,
I
have
a
whole
area
that
is
just
contributor
content
that
you
can
post
on
anything
you
want,
but
in
terms
of
driving
more
usage
around
ortillius
and
getting
new
contributors,
I
think
the
tips
and
tricks
is
is
useful,
but
anything
you
want
to
blog
on
is
totally
is
going
to
be
totally
fine.
B
Yes,
absolutely
so,
I'm
going
to
say
any
any
any
any
kind
of
contribution
you
want
to
make
is
totally
up
to
you.
The
categories
we
have
are
basically
get
ops
and
configuration
management,
contributor
content.
So
that's
anything
you
want
to
talk
about
and
tips
and
tricks
for
ortillius
in
the
open
source
community,
and
then
we
have
news.
C
A
B
G
A
B
Okay
on
another
topic,
I'm
just
moving
on-
we
have
been
talking
about
using
some
kind
of
project
management
like
kanban
boards,
so
that
we
can
keep
track
of
where
we're
at.
On
some
of
these
efforts,
we've
looked
at
trello
siddharth.
It's
all
up
to
you,
he's
going
to
give
us
a
little
overview
of
what
he's
learned
about
github,
github,
trello
boards
and
and
how
he
thinks
that
we
could
use
it.
C
The
current
way,
which
you're
working
is
the
github
issues.
Everything
has
been
tracked
raised
worked
across
github,
but
if
we
segregate
majorly
between
two
things,
one
is
the
community
piece
of
thing,
and
one
is
the
technical
piece
of
that
community
technical
piece.
Of
course,
the
github
is
the
best
source
that
we
should
use
because
the
code
is
out
over
there.
However,
when
we're
talking
about
these
community
pieces
and
probably
what
you're
seeing
on
the
screen
the
working
groups
are,
it
gets
a
bit
fade
away
of.
What
is
happening.
Who
is
doing?
C
C
C
H
C
Things,
the
good
thing
is
you,
you
know
one
can
see
how
much
work
is
there
in
the
community
space.
So
that
is
one
good
thing.
Second
thing
is
for
each
of
the
work
we
can
have
the
conversations
of
prospering,
for
example,
I'm
just
picked
up
something
from
this.
Randomly
the
publish
to
community
is
one
of
the
words
it
is
in
this
state.
Who
is
doing
that?
You
can
add
members
to
it?
Definitely
you
can
add
the
due
date.
C
E
C
C
C
C
The
other
thing
is
that
we
can
help
and
managers
work
better.
Definitely
you
know
if
you
have
something
in
this
form
in
shape
and
not
exactly
trello.
So
just
do
don't
go
with
the
words
of
trello.
If
we
have
some
work
managed
in
this
manner,
it
helps
in
you
know,
people
raising
their
hands
and
trying
their
things
out.
Also,
there's
a
lot
of
ideas
that
comes
across
from
people
and
what
you
see,
for
example,
what
steve
was
showing
in
the
wordpad
it
gets
lost.
It
gets
lost
on
those
conversations.
What
happened?
C
C
The
besides
this
thriller
board.
We
can
have
other
option,
which
is
the
github
project.
I
tried
doing
it,
but
I
guess
it
was
not
shown
to
me
as
one
of
the
projects
I
tried
doing
that
we
can
choose
the
github
projects,
also
as
maintaining
the
kanban,
but
the
point
is:
let's
have
some:
let's
have
more
better
way
of
doing
things
rather
than
getting
into
the
traps
of
exergy
toward
documents,
so
I'll.
G
C
I
First
of
all,
that's
a
great
idea.
I
I
totally
agree
that
we
should
have
like
a
visual
flow
of
you
know
things
in
backlog.
To
do
doing.
I
have
used
trello.
I
am
part
of
a
couple
of
boards,
and
this
is
a
pattern
that
I'm
noticing
you
know.
There
are
too
many
things
to
check
like,
for
example,
distro
and
github,
and
then
trello
to
add
it,
and
then
this
slack
and
all
that,
so
I
feel
it.
I
I
was
wondering
if
we
can
explore
the
github
project
board
to
do
the
same
from
what
I'm
reading.
We
can
do
the
same
backlog
to
do
doing,
and
I
was
just
wondering
if
there
are
any
pros
and
cons
to
using
trello
versus
within
github
itself,
because
a
lot
of
people
will
be
accessing
github
already
right.
So
can
is
there
a
way
to
just
have
this
project
management
piece
there
as
well.
I
H
I
I
can
create
artillerius
doesn't
have
a
public
project,
then,
probably
because
I
am
community
manager.
I
can
create
one
and
I'll
set
up
a
meeting
with
you
and
we
can
go
through
it
to
just
see
if
we
can
do
all
these
things,
because
it's
ultimately
moving
cards
from
one
state
to
another
and
defining
our
flow
from
what
I'm
reading
we
can
do
it
in
github.
I
So
if
we
can,
then
I
and
that's
just
my
view.
You
know
I
would
want
to
hear
communities
view
as
well.
This
is
my
view
that
the
more
we
put
things
within
the
github
repo,
I
think,
the
more
the
less
the
burden
is
on
contributors
to
go
on
various
channels
to
check
on
status
updates
so
yeah.
That
was
just
my
view.
For
example,
we
are
already
using
google
docs
for
the
blog
content
right
and
so
there's
google
in
the
mix,
and
there
is
distro
in
the
mix
and
then
there's
github
and
then
adding
trello.
C
C
Get
our
one,
so
that
is
point
one
here.
I
think
that
was
one
of
the
other
concerns.
Second,
was
we?
We
have
too
many
tools.
Yes,
I
am
also
not
in
pro
of
having
too
many
few
tools,
but
we
use
them
effectively
and
efficiently
should
be
the
target
any
other
concerns,
or
I
think
these
are
two
by
sort
of
interests.
A
J
J
It
gives
you
a
lot
of
nice
things
that
you
can
do
visually,
like
you
see,
he's
put
in
he's
attached
the
backlog
to
do
doing
and
done,
which
you
know
the
sort
of
column
headings,
but
you
know
being
able
to
visualize
your
tickets,
and
you
know,
put
images
in
there
that
make
sense,
for
them
can
be
a
really
fun
thing
and
definitely
something
I
like,
but
to
you
know,
go
more
toward
the
direction
that
nitu
was
talking
about.
You
know
adding
another
tool.
J
If
we
can
do
this
in
github,
I
do
think
is
basically
a
bad
idea,
because
there
isn't
anything
that
I
know
of
that
would
easily
duplicate
all
of
the
issues
between
the
two
and
my
biggest
concern
is
you
know?
Where
would
people
subscribe
for
updates?
If
I've
submitted
an
issue
on
github
and
then
it
disappears
for
three
months
and
then
it
eventually
ends
up
getting
mark
done,
then
I'm
gonna
be
happy,
but
not
knowing
what
happened
in
the
interim,
I'm
going
to
be
like
well.
J
That
was
mysterious
and
disturbing
and
oh,
it
was
all
in
trello
and
I
just
wasn't
following
the
right
trello
card,
but
I
was
following
the
right
github
issue.
You
know
that
that's
going
to
be
confusing
to
folks
that
we
don't
have
those
things
you
know
automatically
in
sync.
So
if
we
can
make
github
workforce,
I
haven't
tried
the
kanban
functionality
in
github,
but
even
if
it's
less
awesome
than
trello,
I
think
that
makes
sense
is
a
good
thing
to
try.
First,
so
you
don't
have
to
duplicate
the
issue.
A
Is
in
the
in
the
github
issues
in
the
github
project,
and
it
looks
like
there's
a
section
on
cards
so
we'll
be
able
to
add
the
the
cards
as
well.
Now,
one
of
the
the
things
that
we're
doing
on
I'm
working
with
chrome
on
is
hooking
in
some
automation
to,
for
example,
if
you,
when
you
do
a
pull
request,
and
you
do
your
merge
that
we
go
ahead
and
close
the
issues
that
are
associated
to
that
pull
request,
so
I
think
we'll
be
able
to
with
the
github
projects.
A
I
think
we'll
have
access
to
do
some
automation
as
well,
and
that's
that
will
be
something
that
looks
like
we'll
through
the
github
actions
we'll
be
able
to
expose
that.
So
I
would
be
in
favor
of
like
need
to
say
keeping
everything
in
on
the
github
side.
I
think
it'll
be
easier
just
to
manage
through
automation,
what's
happening.
H
H
One
thing
our
team
used
trello
in
the
past
and
and
it
was
it-
was
used
primarily
for
managing
the
cards
from
for
a
group
of
people
who
needed
to
see
it,
but
they
were
non-technical,
so
it
was
just
an
easy
way
for
them
to
see
progress
of
main
ideas,
not
necessarily
details
of
bugs,
and
things
like
that.
So
I
agree.
I
like
the
idea,
if
we're
gonna,
if
the
team
is
in
github,
you
know
we
need
to
manage
these
very
particular
things
it.
B
A
C
I
I
saw
cdf
and
tracy.
Tracy
miranda
was
using
this
github
kanban
board,
but
you
know
continuing
to
where
sean
left
is.
If
you
want
to
have
two
technical
aspects
of
it,
then
yes,
github
would
be
the
right
place.
But
if
you
want
to
have
broader
audience,
techy,
non-techie
and
contributing
to
community,
you
know
they
may
not
be
contributing
the
technical
aspect
of
the
art
list.
C
For
example,
the
website
designing
the
publishing
blogs
and
all
those
things
then
trello
is
the
thing
to
go
for
again:
I'm
not
making
any
decisions
just
cheering
across
views.
We
may
start
using
github,
for
example
the
github
kanban
board
and
see
if
how
did
it
work
and
anything
can
be
moved
to
trello
or
not
to
travel.
B
I
think
that
sounds
like
a
good
path
forward
start
using
the
the
the
github
and
they're
we
may
get
to
a
point
where
it
doesn't
make
sense
to
use
github
for
some
of
the
work
that
we're
doing,
and
I
know
that
we
use
trello
with
at
the
devops
institute
and
if
I've
got
a
blog
or
something
that
I'm
due.
It
actually
is
pretty
helpful.
B
I
B
B
G
F
A
G
G
B
A
A
A
So
that's
one
thing
we
can,
I
think,
be
good
starting
point.
It
looks
like
it's
pretty
much
the
same
functionality
being
able
to
do
lists
and
check
boxes
and
things
like
that
and
links
to
the
documentation,
because
you
can
do
a
a
link
to
a
google
doc
and
it'll
show
up
that
way
as
well.
So
that's
just
some
things.
I've
seen
really
quick
here
in
what
we
have
going
on.
B
B
And
then
I
have
one
more
thing
and
I
know
we're
over,
but
I
have
a
in
the
last
discussion.
We
talked
about
making
it
easy
for
easier
for
people
to
sign
up
for
adoption
of
for
new
users,
and
there
was
some
discussion
about
how
we
needed
to
have
a
probably
a
download.
So
I
think
what
I'm
going
to
do
for
now
until
I
get
clarification
from
the
linux
foundation,
is
that
we
we
need
to
create
a
new
container
image
that
has
the
proper
branding
for
ortillius.
B
It
doesn't
have
our
deploy
hub
logo
on
there.
It
needs
to
be
taken
off
and
that
artillious
brand
needs
to
be
on
there.
And
if
you
go
to
the
ortelius
site,
you
will
download
a
it'll,
be
a
download
instead
of
a
sas
signup
and
we'll
keep
the
that'll
clearly
separate
between
deploy
hub
and
artillius,
which
is
our
ultimate
goal.
B
I
B
I
B
Okay,
yeah,
it
will
be
still
needed,
but
we
need
to
have
a
follow-up
to
that.
That
says,
we
need
a
whole
image,
a
container
image
that
people
can
download
from
different
sites.
We
need
to
have
that.
We
probably
need
to
register
it
with
red
hat.
We
need
to
you
know,
I'm
sure,
there's
there's
places
that
we
need
to
register
the
ortillius
container
to
so
people
can
get
to
it
other
than
just
our.
A
Website,
so
to
answer
your
question
need
to
the
logo
that
we're
that
we
chose
like
back
in
the
summer.
One
with
the
alien
and
the
dog
in
the
spaceship
is
the
one
we're
going
to
keep
moving
forward
with
and
we're
just
going
to
reach
out
to
get
that
cleaned
up
to
be
a
svg.
So
we
can
is
one
of
the
formats
we
needed
in
so
we'll
go
ahead
and
get
that
process
started
to
clean
up
that
that
that
image.
A
Yeah
and
then
on
the
as
far
as
like
the
download
the
logos
around
the
for
the
when
we
you
download
the
docker
image,
and
then
it
has,
when
you
run
that
one
it
has
the
right
or
julius
logo
in
there,
I
have
to
double
check.
I
think
we
just
need
to
do
a
pull
request
to
pull
in
the
right
image
on
that
front.
J
I
A
A
A
A
A
I
I
I
I
A
Sasha
and
crum
so,
based
on
that
we'll
go
ahead
and
from
what
the
cdf
was
saying,
the
jenkins
project
had
seven
last
time.
I
think
spinnaker
had
two
and
I'm
trying
to
think
what
the
other
project
they
had
out
there.
Maybe
techton
had
two
people,
so
two
students
so
we'll
have
to
look
at
that
front.
Like
you
said
how
how
we
can
scale
it.
I
G
A
D
D
D
G
I
I
B
I
A
I
A
D
A
A
D
A
A
Oh
yeah
we'll
have
to
see
how
we
want
to
break
it
down
if
we
want
to
have
one
student
work
on
the
argo
cd
and
another
student
work
on
the
spinnaker
or
if
we
want
to
throw
both
of
them
at
argo
cd
to
start
with
and
then
both
of
them
at
against
spinnaker.
That's
gonna
be
more
of
a
project
management.
Once
we
get
going.
B
I
D
A
G
A
A
I
D
So,
like
I
went
to
the
documentary
shock
like
on
the
issues
that
we
had,
so
it
was
mentioning
that
we
should
have
a
regular
mentor
should
have
a
regular
connect
with
our
academy,
but
things
like
steve
like
we
are
you
like.
I
don't
know
how,
like
you,
your
plates
are
going
to
be
completely
filled
out
like
with
us,
as
well
as
students
like
right.
As
you
mentioned,
like
we
can
add
one
more
mentor
then
like
you
can
like
you,
can
like
work
on
the
main
managing
the
mentors.
D
I
In
my
experience
they
need
usually
a
little
bit.
It
depends
on
how
mature
the
mentee
is.
Sometimes
they
need
like
basic,
helpful
github
and
all
that
sometimes
they
get
into
project
it's.
It
might
require
six
to
eight
depending
on
you
know
the
project
and
the
experience
of
the
mentee.
But
in
my
experience
it
did
not.
It
requires
a
lot
more
in
any.
I
It
requires
less
initially,
but
a
lot
more
wow
in
the
middle
and
at
the
end,
when
they're
making
a
presentation
because
they
have
to
it's
sort
of
like
an
exam
that
they
have
to
pass.
You
know
that
did
they
do
the
work
that
they
did
and
during
the
presentations
and
all
they
are
a
little
bit
more
nervous.
You
know,
how
do
you
show
our
work?
How
do
we
present
it?
I
It
is
sponsored
by
google,
so
the
way
we
happens
is
like
we
submit
our
ideas
that
we
would
like
to
get
work
done
on
this,
and
this
is
the
way
we
have
broken
down
into
project
like
for
a
three
month
period
for
the
first
month.
This
is
what
the
student
can
work
second
month.
You
know
and
third,
this
is
what
we
like
to
get
done
and
then
google
invites
mentees
who
can
choose
the
projects.
So
if
the
mentees
like
that
project,
they
apply
for
it
and
then
we
can
choose
if
we
like.
I
A
A
Okay,
just
fyi,
I
know
the
the
docs
are
down.
I'm
messing
around
with
the
ssl
keys
on
the
cluster.
That's
part
of
why
it's
it's
having
problems.
I
have
to
put
ssh,
I'm
sorry
ssl
keys
in
today,
so
I'm
just
going
to
be
messing
around
with
the
the
cluster,
that's
hosting
the
docs,
so
it
hopefully
I'll
get
it
done
today.
So
we
can
get
those
links
going
back
up
and
running.
So
that's
what's
happening
on
that.