►
From YouTube: Community Standup: 8/6/19
Description
Lisa discusses Governance and Code of Conduct documents
A
A
A
A
A
A
A
A
C
C
C
A
A
C
Well,
I
don't
want
to
take
up
any
time,
but
talking
with
Matt
as
well
on
the
in
re
community
I
noticed.
So
you
all
want
to
move
to
using
a
vagrant
file
and
the
option
of
running
Energy
labs
without
a
VM
image
inside
a
self
medicate,
so
using
mini
Cube
with
a
driver
of
none.
So
I
was
playing
around
with
it
the
last
two
days
and
it's
a
lot
more
complicated
and
I
initially
thought.
C
A
B
B
B
B
The
other
addition
is
weava,
so
we
have
selected
English
as
the
default
language
of
project
operations
and
mainly
because
it's
the
the
common
common
code
of
interoperability
for
international
proper
operations
and
as
such,
we
expect
that
there
will
be
regional
variations
in
how
people
speak
in
absolute
right,
accents
and
so
forth
and
so
on,
and
we
expect
people
to
be
respectful
of
that
and
we
also
encourage
internationalization
of
of
the
projects
most
protected.
The
lessons.
C
B
B
To
the
steering
committee
and
we'll
talk
about
that,
a
little
bit
in
the
governance
talk
so,
for
example,
if
you're
having
trouble
with
another
member
of
the
community
or
someone
who
is
you
know
a
project
leader,
whoever
you
can
reach
out
to
the
steering
committee.
This
my
email
address
does
need
to
be
updated
and
if,
if
you
are
uncomfortable
going
to
the
steering
committee
as
a
group,
you
can
reach
the
steering
committee
director
and
once
that
person
is
elected,
will
have
their
email
address
and
all
of
the
other
certain
community
people's
email
addresses.
D
B
B
When
we
talk
about
the
scope
and
we'll
get
that
to
this
a
little
bit
later,
we
want
to
make
sure
that
obviously
says
it's
open
source
and
the
code
is
open
source.
Anybody
can
grab
the
code
and
go
do
whatever
they
want
with
it.
But
in
terms
of
what
the
community
is,
a
group
needs
to
be
focused
on.
We
kind
of
all
need
to
agree
on.
B
Lessons,
obviously,
anybody
can
write
a
lesson
they
can
host
it
privately.
They
can
do
whatever
they
want
with
it.
In
order
for
it
to
be
hosted
on
the
inner
you
lads
site
again,
it
would
need
to
meet
sort
of
the
the
criteria
that
we'll
need
to
develop
and
spell
out
to
make
sure
that
it's
aligned
with
the
mission
of
the
project.
B
Anything
relating
to
achieving
the
mission
is
good
of
the
project,
anything
relating
to
the
platform
itself,
as
well
as
the
lessons.
This
is
a
reiteration
also
that
there
is
a
documented
contribution
process.
We
will
need
to
develop
an
inbound
code
review
policy
that
has
all
of
the
I
always
blank
on
the
term.
There
is.
There
is
basically
a
a
very
sort
of
lightweight
process
that
code,
committers
or
contributors
will
include
with
their
with
their
contributions.
B
That
basically
says
yay
verily
I'm
allowed
legally
allowed
to
give
you
to
contribute
this
code
right,
I'm,
not
I'm,
not
taking
proprietary
code
and
contributing
it
to
anybody
else.
It
doesn't
belong
to
anybody
else.
It
is
free
and
clear
and
I
can
contribute
it
to
the
project.
So
we
need
to
develop
an
inbound
code
review
policy
that
includes
that
language,
but
that
sort
of
eight
you
do-
and
we
are
acknowledging
here
that
that's
something
that
we
need
to
do
as
a
community.
B
There
are
some
projects
within
NRE
labs,
they're,
all
listed
separately
in
github,
antidote
and
various
other
projects.
Each
project,
ideally
and
obviously
will
need
to
grow
our
community
a
little
bit
to
achieve
this,
but
ideally
each
project
would
have
two
committers
so
that
no
one
has
sole
power
of
acceptance
or
a
rejection
of
of
code,
not
that
again
I.
You
know
we're
not
particularly
expecting
this
to
be
a
highly
political
or
politicized
project.
B
Some
are
definitely
more
than
others,
but
you
know
people
are
people,
and
sometimes
people
get
on
ego
trips
or
you
know,
have
falling
outs
or
whatever,
and
so
having
to
to
committers
is
just
good
standard
practice.
A
contributor
may
become
a
committer
with
the
majority
approval
approval
of
existing
committers
and
may
need
to
MA,
and
it
need
may
be
removed
by
a
majority
approval
of
other
existing
committers
project
contributors
may
request
the
removal
of
a
committer
by
notifying
the.
B
So
if
we
have
a
committer
who
either
you
know,
is
abusing
people
or
much
more
likely
is
simply
just
not
present
on
a
regular
basis
and
therefore
not
reviewing
and
committing
code
in
a
timely
fashion
and
is
becoming
a
roadblock
to
progress.
That
might
be
a
reason
to
request
the
removal
of
a
committee.
B
Something
I've
seen
in
some
projects
is
sometimes
there's
a
developer
advocate,
who
is
on
a
steering
committee
in
addition
to
the
technical
community
lead
that
typically
happens
in
very
large
projects,
especially
projects
where
most
of
the
steering
committee
or
Governing
Board,
or
what
have
you
is-
is
kind
of
made
up
of
non
non-technical
people.
In
this
case
you
know,
that's
sort
of
not
the
composition
of
our
community,
nor
of
our
steering
committee,
but
we
did
want
to
make
sure
that
there
was
plenty
of
visibility
of
the
technical
community
of
the
doings
of
the
steering
committee.
B
B
Okay,
we've
also
talked
about
the
idea
of
creating
a
community,
a
curriculum,
lead
role,
and
this
might
in
some
sense
be
sort
of
the
developer,
evangelist
kind
of
role,
in
the
sense
that
the
curriculum
lead
is
not
just
the
person
who's.
Writing
the
lessons,
but
is
is
responsible
as
much
as
anything
else
for
finding
other
people
who
are
interested
in
contributing
lessons
and
helping
them
get
get
on-boarded,
learn
the
contribution
process,
know
and
and
adhere
to
the
code
review
policy
track.
B
B
Really
ought
to
put
this
good.
This
break.
I
do
have
some
of
those
and
I.
Also
I,
don't
know
if
you
know
her.
The
key
presser
is
in
our
open
source
office
and
she's
worked
in
open
source
for
30
years,
and
so
we
she's
also
provided
input
on
us
as
well,
based
on
her
extensive
experience
in
multiple
open
source
projects,
all
up
and
down
the
stack
all
right
so
steering
committee-
and
this
is
sometimes
the
most
contentious
steering
committee-
basically
does
administration
and
administrative
oversight
so
budget,
paying
the
bills
legal,
stuff
marketing
anything
non-technical.
B
The
expectations'
really
is
that
the
steering
committee
will
help
set
strategic
direction
from
the
project
for
the
project
with
the
input
of
the
technical
community.
But
you
know
for
all
technical
matters.
The
steering
committee
is
is
really
in
a
support
role
in
terms
of
you
know:
finding
funding
for
things
you
know,
marketing
the
the
doings
of
achievements
of
the
technical
community
and
so
on.
B
B
We're
saying
the
originally:
we
had
the
director
the
treasurer
and
the
community
leader,
and
then
we
added
the
curriculum
lead
and
then
we
said
well,
that's
four,
and
there
really
should
be
an
odd
number,
and
so
then
we
also
added
a
marketing
lead.
It
may
take
us
a
while
to
actually
find
five
people
to
fill
this
all
out,
but
an
absolute
minimum.
We
should
have
these
three
yeah.
B
B
B
B
And
if
there
are
multiple
candidates
for
director,
then
you
know
it's.
Whoever
gets
the
the
largest
share
of
the
vote.
Directors
do
not
need
to
have
made
technical
contribution,
but
are
expected
to
have
demonstrated
consistent
support
for
the
project
and
either
technical
or
non
technical
capacity.
So
that's
inherently
a
bit
fuzzy
and
some
sometimes
people
kind
of
get
uncomfortable
with
things
being
not
spelled
out
with
great
exactitude.
B
The
treasurer
is
basically
there
it
to
be
a
second
set
of
eyes
on
the
money
and
make
sure
that
it's
all
being
spent
appropriately
and
that
the
director
isn't
funding
their
retirement
or
vacations
in
Tahiti.
The
marketing
lead
does
marketing
things
and
I'm
noticing
that
there
should
be
a
see
here
in
metrics.
B
Reporting
on
marketing
tech,
things
working
on
launches
for
major
releases
and
any
other
major
events
that
we
might
choose
to
do
in
the
future,
working
with
the
community
community
manager
who
have
whose
role
hasn't
been
specifically
defined
in
the
governance
stock,
because
it's
just
kind
of
you
know
it's
day-to-day
operations
and
not
relating
to
power
and
control,
particularly
the
technical
community
leader
and
the
curriculum
leader
roles
that
we've
already
talked
about.
And
we've
also
said.
The
committee
can
formalize
additional
roles
if
desired.
B
B
B
Contributors
will
will
comply
with
all
the
policies
which
may
include
a
contributor,
License
Agreement
code
of
contact
privacy
policy,
which
we
will
need
to
write
Terms
of
Use
and
Trademark,
and
branding
policy
and
I'll
comment
on
that.
Just
for
a
moment
here.
In
parallel
with
all
of
this,
we've
been
exploring.
B
Moving
the
project
to
a
conservatorship
or
foundation
of
some
sort,
mainly
so
that
we
some
first
order
so
that
again
juniper
gets
out
of
the
business
of
running
the
project
and,
more
specifically,
as
we
break
on
other
sponsoring
organizations
that
we
have
a
a
neutral
place
to
put
money
which
is
really
when
it
comes
down
to.
So
whenever
that
happens,
the
in
in
pretty
much
all
cases,
conservator,
conservancies
and
tre
foundations
have
generally
have
their
own
trademark
and
branding
policies.
F
Lisa
one
thing:
not
a
question
on
that:
you've
been
highlighting
over
those
lines;
I
don't
know
if
you
notice
those
blue
blue
button
that
pops
up
whenever
you
hover
over
one.
Yet
if
you
click
that,
that's
how
you
can
add
a
comment,
I
know
you
had
a
to
do
that
you
thought
of
in
one
of
the
previous
lines.
F
So
you
could
do
that
to
take
a
quick
note,
saying
like
this
yeah
yeah
and
at
the
phraseology
that
you
you
wanted,
but
also
general
comments,
everybody.
This
is
how
you
this
is
how
you
can
leave
comments
on
the
dock.
So
this
is
a
pull
request
and
github
and
you
can
just
click
any
one
of
those
lines
in
that
in
that
blue
box
to
leave
a
comment
and
as
we
make
changes
if
we
change
the
line
that
you
commented
on,
then
your
comment
will
automatically
get
dismissed.
B
B
So
tada,
that
is,
that
is
the
governance
dock
that
we
have
put
forward
for
the
the
the
community
as
a
whole
to
to
look
at.
We
should
probably
at
some
point-
you
know,
allow
some
further
further
time
for
review
and
comment
by
the
community
at
large
and
then
in
a
future
in
a
future
community
meeting
either
vote
to
to
ratify
it
or
not.
B
So
Ethan
Andrew
in
particular,
since
I
know
we
haven't,
we've
been
talking
with
you
guys
about.
You
know
coming
into
the
project
kind
of
more
as
a
partner
or
sponsoring
org.
Do
you
have?
Are
you
comfortable
with
this?
Does
it
kind
of
meet
with
what
you
would
hope
to
see
in
terms
of
how
how
the
project
would
be
run
any
any
anything
that
we
may
have
missed.
D
Again,
going
back
to
my
earlier
comment:
Lisa
I
don't
have
background
in
open
source
governance
with
I
have
no
history
here.
So
there's
nothing
sticking
out
to
me.
The
I
think
something
like
this
goes.
If
there
are
any
lingering
questions,
people
might
have
in
their
minds
about
you
know
a
Juniper
thing
versus
you
know
on
a
true
open
source
project
that
should
be
dispelled
by
this
I
think
that's
pretty
significant
great.
B
D
B
D
E
F
If
you're
gonna
publish
something
Thursday,
that
probably
means
I
owe
you
a
link
because
we
don't
have
it
published
on
our
fraud
site
so
hopefully
we'll
be
all
deployed
by
then
I'm
hoping
to
be
I,
don't
see
why
we
wouldn't,
because
we're
pretty
close
right
now,
I'm
actually
about
to
start
doing
the
release
processes
myself
if
I,
if
I
run
into
any
issues
with
that
I'll,
let
you
know
but
I.
Imagine
you'll
want
to
link
to
the
batch
lesson
in
our
production
site
by
then.
F
B
F
F
E
F
My
last
stand
up.
I
thought
we
mentioned
the
12th,
so
that's
what
sort
of
all
the
planning
was
going
around
I
as
usual,
I
expected
try
to
have
things
done
well
before
that.
So
that's
why
I'm
saying
like
it's
not
impossible
to
me
Thursday,
but
what
I
was
planning
on
was
the
was
the
brain,
fart
yeah.
Thank
you.
E
F
We'll
see
what
we
got
where
we're
at
like
I
said
we
always
try
to
operate
as
a
head
as
possible.
So
I
will
let
you
know
if
we
run
into
any
issues
and
yeah.
If
we
need
to
we
can
we
can
push
it
out
a
little
bit,
but
no
matter
what
the
batch
lesson
we've
still
planned
to
be
available
on
the
12th
that
okay,
the
current
plan,
we'll
just
flex
when
we
write
the
blog
about
it.
Okay,.