►
From YouTube: GMT 2018-04-09 Community WG
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
B
C
C
E
B
B
A
C
D
B
A
D
B
A
I'm
also
not
sure,
what's
happening
with
mrs.
Kahn.
We
have
this
community
meeting
recently
to
talk
with
users
about
their
potential
interest
in
facilitating
the
next
maysa
con
and
after
that
meeting
soon
L
sent
out
an
email
to
a
few
stakeholders
and
I
actually
followed
up
with
the
York
this
morning
on
that
I'm
not
sure
if
there
have
been
any
more
conversations
between
York
and
other
community
members,
but
I'm
not
sure
what
the
current
status
of
mesas
con
is
either.
B
Do
we
want
actually
I'll
ask
her
about
it
and
maybe
if
he
wants,
he
can
tell
us
about
it
at
the
next
working
meeting
or
something
if
there
any
plans
yeah.
Oh.
A
Yeah,
actually,
let's,
let's
try
to
get
York
to
attend
the
next
community
working
group
meeting
and
chat
about
that.
That's
a
good
idea
and,
let's
see
so
I
had
an
action
item.
Ask
Alex
about
release
working
group.
I
didn't
do
that.
I'm,
not
I'm,
not
sure
that
the
release
working
group
is
something
I
want
to
do
for
the
current
release.
A
A
I
I
reached
out
to
James
peach
and
Ian
X
to
see
if
they
had
any
bandwidth
for
it
and
they
do
not.
For
the
current
release,
I
had
a
meeting
with
Alex
and
Alex
is
willing
to
chip
in
and
like
help
me
out
significantly
with
the
current
release.
So
I
think
that
you
of
us
were
planning
on
still
doing
one
six.
A
A
E
I
think
I
agree
with
your
point.
Crack
so
I
think
follow
this.
We
could
maybe
for
now
adjusting
on
the
tablet
that
that
list
that
mailing
list
and
the
username
is
as
well
as
the
selection,
because,
right
now
we
have
four
working
and
I
think
the
disciplines
yeah
not
like
increasing
like
very
quickly.
So
me,
I,
don't
want
like
most
of
the
attendees
to
be
distracted
by
too
many
more
times
so,
maybe
for
now
we
should
maybe
just
have
a
focus
on
a
couple.
B
C
A
You
know
previously,
we
were
trying
to
keep
track
of
how
many
open
reviews
were
in
review
board,
trying
to
minimize
that
number,
and
so
this
code
was
kind
of
a
tool
that
we
have
used
to
just
attract
the
state
of
review
board
and
I.
Think
one
thing
that
came
up
during
a
recent
discussion
was
that
we
did
I
I'm,
not
sure
how
bad
it
is
necessarily
to
have
a
bunch
of
open
reviews
on
review
board.
I,
don't
know
that,
there's
anything
we
really
need
to
do
there
so.
A
A
E
A
Yeah
beyond
that,
I,
don't
really
know
what
we
might
use
it
for
I.
Think
my
like
TLD
art
for
me
is
that
I
don't
really
see
any
real
action
items
for
like
what
we
might
use
that
code
for
or
I,
don't
think
we
have
a
real
need
to
like
be
monitoring
the
state
of
review
board
necessarily
so
if
people
have
thoughts
or
ideas
on
that,
we
can
certainly
discuss
it.
A
B
C
B
It
was
okay,
but
it
wasn't
like
this
is
gonna
solve
all
our
problems
or
anything
so
and
it's
still
in
it's
still
in
development.
Basically,
so
they're
not
really
looking
like
it's,
not
it's
not
ready
for
primetime,
yet
and
I.
Think
they're,
like
basically
looking
for
pilot
projects
to
to
help
them
develop.
Kibble
yeah.
B
But
you
know
if
we
did,
if
there
was
a
time
when
we
were
gonna
say
like
hey
I,
think
it's
really
worth
it
to
you
know,
put
you
know,
put
people
who
owe
reviews
in
a
room
together
and
say:
like
hey,
you
review
these.
This
is
your
time
to
review
them
and
it
would
be
useful
to
know
how
many
open
reviews
I.
B
I
mean
I
do
too
but
I'm,
not
the
person
who
has
to
sit
through
the
review,
a
bunch
of
PR,
so
yeah
I
mean
I
I!
Think
that
the
hackathon
style
like
just
a
forcing
function,
to
get
people
to
do
something
during
a
certain
amount
of
time.
To
me,
it's
useful
for
my
working
style,
but
I,
don't
know
how
much
bandwidth
the
committers
have
for
that.
F
Could
I
add
a
tangential
feature,
request,
slash
action
item
as
long
as
we're
talking
about
like
review,
board,
API
sort
of
related
stuff,
because
I
know
something
that's
been
bugging
me
as
a
committer
that
I
think
we
could
automate,
especially
because
I've
seen
it
done
over
in
zookeeper.
So
if
you
guys
know
when
you
put
up
a
patch
right-
and
you
add
a
bug
item
to
your
patch,
you
then
not
only
have
your
patch
in
the
bug.
You
then
have
to
go
over
to
the
bug
change
it.
F
You
have
to
make
sure
it's
accepted,
then
you
have
to
start
progress
on
it.
You've
got
a
post
review
on
it
and
you
gotta
go
copy
the
link
over
into
it
and
that's
just
to
get
your
bug
add
them
into
a
reviewable
state,
even
though
you
already
posted
a
review
for
it.
It's
just
especially
when
you
do
like
a
chain
of
these,
where
you're
working
on
five
bugs
with
by
patches.
It
gets
it's
so
much
time
to
do
when
it's
something
that
could
be
so
easily.
Automated
zookeeper
has
managed
to
automate
this
with
JIRA.
F
F
F
F
F
F
I'd
have
said
a
hackathon
I'd
found
a
I'd
found,
an
issue
that
we
thought.
Oh,
this
is
a
good
hackathon
project
and
I
investigated
it
with
the
student
and
we
get
down
to
and
we're
like
wait.
This
isn't
a
bug
anymore.
Oh,
it
had
been
closed
and
nobody
had
closed
the
bug.
So
I
know
we
were
saying
snaps
around
review
board,
probably
not
so
useful.
But
if
we're
looking
at
review
board,
automation,
I
think
there
is
value
and
getting
review
board
and
JIRA
to
work
better
together.
So.
C
You're
saying
I
defer
for
zookeeper
is
that
so
I
know
for
like
Apache
Hadoop,
for
example,
they
put
reviews
or
patches
into
the
JIRA
itself,
and
then
the
review
board
essentially
kicks
off
from
based
off
JIRA
and
then
comments
in
JIRA
about
test
results
is
at
what
zookeeper
disorder
keeper
actually
uses
review
board,
as
can
a
source
of
truth,
and
then
it
goes
back
and
updates.
Jira.
F
Know
they
previously
did
the
Hadoop
version.
You
post
your
patch
as
an
attachment
to
the
issue,
and
that
would
go
put
it
on
I
believe
it
would
put
it
on
review
board
and
update
it.
They've,
actually
transitioned
away
from
review
board
and
now
use
github,
but
what
they
do
have.
Is
you
open
a
pool
request
and
the
first
part
of
the
subject
is
like
zookeeper,
the
number
of
the
JIRA
bug
and
they
have
a
bot
that
goes.
F
Oh
cool
goes
over
to
the
review
copies
over
all
the
conversation
that
happens
in
the
github
issue
puts
the
review
to
be
in
progress
and
links
it
to
the
github
issue.
I
was
thinking
the
same
kind
of
thing
before
when
you
put
up
a
review
board
patch
with
a
bug
number
in
it
mm-hmm
we
could
just
automate
putting
it
into
a
reviewable
state
and
linking
the
issue
over
to
it
and
follow
that
up
with
when
you
close
it
as
submitted
close
the
associated
bug
as
submitted
yeah.
C
Yeah
I
think
yeah.
We
talked
about
this
a
while
ago
when
we
were
writing
the
post
reviews
and
push
comets
and
all
that
I'm,
pretty
sure,
there's
also
a
to-do
in
there,
at
least
in
the
push
comets
Orson,
where
once
you
push
it
right
now,
it
closes
the
review
automatically
if
used
the
script,
but
it
doesn't
go
to
JIRA
and
close
the
review
and
I
think
it's
mainly
because
it
wasn't
clear
to
me
how
easy
it
is
to
interact
with
JIRA
through
Python
code
base,
because
I
don't
think
I
found
like
Arbeit
equivalent
for
JIRA.
C
That
is
open
source
that
I
could
use.
Maybe
there
is
one
that
I
just
didn't
find,
but
also
like
getting
users
credentials
to
be
able
to
log
into
JIRA
and
then
post
a
comment,
keeping
track
of
that
session
and
everything
I
I
just
thought
it's
complicated,
but
there
is
a
way
to
do
it.
Especially
Cooper
has
done
it.
Maybe
we
can
see
the
code
on
how
they
did
it,
but
yeah
that's
a
complication
when
I
was
doing
push
commits
and
stuff
where
that
thought,
organizing
to
get
also
JIRA
and
I
just
thought.
C
F
C
At
least
when
I
look
at
it
as
well,
probably
like
a
year
ago,
I
don't
know
if
there's
something
else
popped
up,
maybe
a
Python
library
or
that
isn't
allowed
to.
But
basically
you
need
to
be
able
to
get
users
credentials
maintain
that
session
somewhere
in
the
cookie
and
be
able
to
do
that
stuff.
Just
like
our
batti
batti
does
for
every
would.
I
think
we
thought
that
it
will
be
a
lot
of
us
writing
code
for
the
VIP
eyes,
which
I
don't
know
if
anyone
has
time
at
this
point
to
do
right.
I.
F
Mean
you're
right:
I
don't
want
to
duplicate
that
code
for
sure
considering.
Well,
my
hope
is:
there's
other
projects
doing
it,
since
I've
seen
them
do
with
github
and
JIRA
I
assume
there's
a
hip
code
available
somewhere
to
help
us
out.
Maybe
I
could
bug
infra
being
mostly
Apache
tools
right,
like
review
board
and
your.
C
A
How
simple
it
would
be
to
automate
because
we
don't
like
there
isn't
a
well.
There
may
be
multiple
reviews
for
a
particular
ticket
and
sometimes
you'll
and
a
few
patches
and
a
ticket
and
close
them
as
submitted,
but
the
issue
itself
isn't
closed
yet
so
I
guess
in
that
case
the
commander
would
not
to
know
to
go
reopen
the
ticket.
Well,.
C
I
would
hope
it's
more
interactive
than
that,
like
instead
of
someone
closing
review
directly,
someone
should
be
using
push
Komets
script
and
that
one
should
be
interactive
enough
to
say:
hey
I
found
this
box
can
I
close.
This.
Can
I
mark
this
close
to
end,
but
it
was
probably
yes
and
maybe
you
could
say
no,
if
you
think
it's
still
not
done
yet
kind
of
yeah.
F
C
C
C
Integrate
right
now
that
expects
you
to
so,
instead
of
basically
doing
a
once,
you
do
apply
reviews
onto
the
master
as
a
committer
bring
a
gate
push
you
would
just
use
the
script
to
do
push
commits
and
it
basically
extracts
the
review.
Links
from
the
commits
and
then
closes
marks
them
as
closed,
and
you
could
imagine
could
also
get
the
bug
ID
from
the
review
and
actually
asks
you
to
close
those
as
well.
Yeah.
F
F
Know
I
added
like
some
options
to
that
script,
to
automatically
add
people
to
all
the
reviews,
so
you
don't
have
to
go
to
each
review.
You
posted
and
paste
in
the
names
over
and
over.
We
could
do
one
for
a
bug
ID,
so
you
could
post
a
review
with
a
bug
ID
all
at
once
and
it
would
update
okay
all
right.
Yeah
we
got
I
got
ideas.
I
might
look
at
some
of
this.
D
B
B
B
B
Yeah,
that's
awesome
because
I
was
like
oh,
it's
kind
of
weird
Mesa,
Sphere
shirts,
but
then,
who
knows
so,
hopefully
you're
good
yeah.
We
might
want
to
think
about
meso,
swag
I,
don't
know
like
if
we
could
sponsor
that
with
our
marketing
team
or
if
anybody
else
could
sponsor
that
it
would
be
fun.
I
like.
B
C
A
So
that's
all
the
action
items
from
last
time,
an
agenda
for
this
week,
just
a
couple
items
that
I
put
down
the
first
one
is
checking
in
about
the
frequency
of
this
meeting.
The
last
couple
meetings
we
haven't
had
a
bunch
of
agenda
items,
so
I
was
wondering
if
you
guys
thought
that
the
bi-weekly
cadence
was
good,
or
should
we
go
to
monthly
with
you,
okay,
I,
like.
A
A
A
One
of
the
I
think
that
the
top
item
that
we
were
thinking
of
in
terms
of
blog
posts,
we
would
like
to
see,
are
some
posts
from
Asus
users
about
their
experiences
about
why
they
use
maysa,
so
I
reached
out
to
Zi
Tao
and
he
said,
he's
actually
already
gotten
approval
from
folks
at
uber
to
do
a
blog
posts.
He
just
hasn't
found
time
to
put
it
together,
yet
he's
planning
on
doing
one
I,
don't
know
precisely
the
content
there,
like
I,
don't
know
if
he
has
an
angle
planned
yet,
but
I
wanted
to
see.
F
My
only
problem
is
I
know
that
the
big
customers
that
we
have
using
it
are
under
NDA
is
with
us,
so
I'm
not
quite
sure
how
detailed
a
blog
post
would
be
about
the
use
of
maysa.
Here
that
said,
I
also
know
there
are
some
Azure
people
kind
of
using
it
in
a
more
public
fashion.
I
could
look,
I
could
look
around
the.
B
Other
thing
that
we
might
want
to
do
is
just
go
down
the
users
page
on
the
basis
website
and
check
in
with
those
people
like
see
who
you
know
see
who
proposed
putting
their
company
down
as
a
user
and
say
like
hey,
are
you
still
using
basis?
Do
you
want
to
talk
about
it
a
little
bit
more
on
the
blog,
a.