►
From YouTube: OpenCrowbar Meeting 2014 01 15
Description
Kickoff for OpenCrowbar Community Meetings
A
C
D
C
A
A
E
B
F
Mom
I
I
can
jump
in
I,
know,
I,
know
Rob
re-imported
the
crowbar
core
repository
into
the
open,
crowbar
org
little
history.
Here
we
hit,
we
hit
a
fairly
obscure
issue
with
github
I,
don't
know
if
everybody
was
familiar
with
it,
but
the
import
into
the
new
organization
on
github
under
open
crowbar
was
a
fork
of
bar
clamp
crowbar.
So
it
showed
all
the
history
and
it
showed
the
link
back
to
the
original
bar
clamp.
F
The
problem
we
ran
into
is,
if
somebody
tried
to
fork
that
new
repository
github
viewed
it
as
a
fork
of
bar
clamp
crowbar.
So
if
you
had
the
existing
bar
clamp
crowbar
from
the
original
crowbar
repository
or
crowbar
organization,
then
github
would
not
fork
it.
It
would
actually
just
kind
of
take
you
to
the
page.
F
F
It's
not
get
right,
it's
not
a
get
issue
per
se.
It's
the
way,
github
track
the
fork
on
their
side.
You
know
so
the
the
issue
was.
If
you
went
to
github,
if
you
wanted
to
fork
the
repository
into
your
local
account
on
github,
when
you
tried
to
fork
it
github
knew
that
that
repository
is
a
fork
of
the
original
bar
clamp
crowbar
and
it
refused
to
fork
it
again.
If
you
already
had
a
bar
clamp
crowbar,
which
made
it
impossible
to
work
on
the
two
repositories
simultaneously,.
F
There
there
was
a
way
around
that
using
basic
get
magic,
you
could
clone
it
locally
and
then
push
it
to
github.
But
when
you
did
that
github
didn't
recognize
it
as
a
fork,
which
meant
you
couldn't
submit
pull
requests
so
that
process
broke
so
that
no
one's
resolved,
but
I
figured
I'd,
throw
some
insight
into
what
was
going
on
behind
the
scenes
because
it
it
seemed
like
a
lot
of
juggling.
But
it
was
just
funny.
F
I
sent
Rob
and
I
think
the
rest
of
the
architects,
an
email
on
what
I
had
done
and
I'm
not
sure
what
Rob
actually
did
eventually
but
I
think
he
did
the
same
process.
I
did
the
juicer
the
gist
of
the
process.
It's
actually
very
simple.
At
the
get
level
you
the
repository
that
was
on
github
the
open,
crowbar
repository
you
clone
it
make
a
local
copy.
So
you
literally
clone
the
repository
locally.
But
you
you
don't
do
a
check
out.
You
do
a
ver
repository
clone.
F
You
then
create
a
repository
on
github
and
empty
repository,
and
you
then
push
it
up
in
mirror
mode
and
once
you've
done
that
you
have
the
repository
on
github,
but
the
this
effectively.
You
do
the
fork
by
cloning
it
locally
and
then
pushing
it
to
github.
Instead
of
doing
the
fork
on
github
itself,
that's
effectively
what
you
do.
A
F
So
that
happened,
and
so
far
I
believe
that
repository
is
in
good
shape.
The
the
Rob's
been
working
on
the
BDD
tests
in
there
to
get
them
all
passing,
but
generally
the
codes
in
good
shape
it
does
substantially
work,
I
mean,
obviously
there
may
be
bugs
I
haven't
found
anything
showstopper
and
I've
kind
of
been
working
out
of
that
repository.
Most
of
the
changes
I've
done
are
on
the
area
of
the
documentation
system.
I
haven't
done
any
kind
of
core
crowbar
changes,
except
in
the
dock
area.
F
A
C
F
F
D
B
B
E
D
D
Are
you
have
the
development
tool
you
know
today
for
developers
to
share
and
collaborate?
It's
not
a
release
mechanism.
So
yeah
there's
going
to
be
broken
stuff
all
the
time
and
we're
going
to
do
our
best
to
make
sure
that
it's
working
and
if
it
works,
we
can
tag
it.
That
is
that
is
the
religion
network
tag.
D
E
There
are
two
categories
of
users
of
the
repository:
there
is
a
core
crowbar
work,
and
that
includes
the
developed
development
tools
and
everything
else
and
under
is
the
workload
work
on
the
OpenStack
on
Hadoop.
It
is
perfectly
fine
for
the
first
category
of
people
to
you
know
to
work
around
the
deficiencies
on
the
on
the
toolset.
There
is
no
need
for
the
workload
people
to
work
on
that
until
the
tools
are
ready
for
them
to
do
the
work,
because
it
will
be
spending
a
lot
more
time.
D
D
E
Visible
week,
we
can
do
that
we
can
work
on
the
workloads
on
the
bar
clamps
for
the
OpenStack
and
for
Hadoop,
currently
out
of
the
crowbar
org,
the
current
build
tools
at
least
work.
We
can
do
the
ISO
and
we
can
do
you
know
all
of
the
current
ways
we
do
the
testing
of
of
our
current
code,
including
the
simulator
of
the
crowbar
too
now
this
out
having
the
ability
to
deliver
something
which
you
can
pass
to
the
QA
organizations
for
them
to
test
the
thing
we
are.
D
D
If
I
want
to
see
what
uncle's
done
so
far
in
building
scripts
to
build,
RPM
and
all
he's
done
is
emailed
it
to
someone
else.
That's
not
you
know
and
I
do
not
want
to
make
the
negative
example
out
of
ABS
on
purpose,
because
you
generally
amazingly
wonderful,
I'd,
really
love
to
be
able
to
set
eyes
on
it
and
the
general
idea
that
we
share
as
much
as
possible
all
the
time
and.
A
E
D
In
terms
of
our
released
products
and
will
work
with
other
words,
what
we're
concerned
about
it
for
developing
bar
clamps
and
stuff-
that's
still
down
the
road
not
think
of
this.
The
subject
is
the
open,
probar
migration,
so
Rob
drop
a
lot
of
really
good
bullet
points
into
the
open
club,
our
backlog.
Thank
you.
D
A
C
D
A
D
But
you
know
your
mileage
may
vary
and
contact
me
for
help
the
I'd
like
to
get
to
a
point
over
the
next
three
to
six
months,
where
we
actually
have
real
community
governance,
where
we
have
a
elected
and
voting
body
that
has
control
over
checking
releases
to
make
this
a
real
project,
but
not
something
that
seems
opaque
and
willy
nilly,
as
it
seems
for
the
past
few
years
it's
been
we've
been
pushing
taking
that
can
down
the
road
of
creating
a
real
community
for
a
long
time
and
that
it
really
got
to
change.
Otherwise.
C
A
D
Going
to
take
that
up
rather
move
forward
with
it
in
my
coming
through
the
six
month,
because
that's
that's
critical,
for
it
is
a
huge
opportunity
with
creating
a
new
organization
and
having
that
clean,
repoed
and
let's
be
clear
and
eliminating
as
much
as
possible.
The
package
that
we
carry
or
press
be
able
to
establish
community
and
proper
governance.
C
G
G
It's
trying
to
figure
out
what
things
need
to
be
done
in
order
to
have
you
make
the
open,
crowbar,
ricos
usable
for
different
communities
that
we
need
surf
right.
Firstly,
getting
developers
in
there
next
to
see
will
have
a
theme
pulling
the
code
and
testing
the
curves
right,
then
actually
bringing
up
being
able
to
enough
demos
and
pilots
and
things
like
that
out
of
it.
A
G
That
it's
very
easy
to
not
know
what
we're
doing
if
they
have
it
written
down
the
ejecta
straight
hard,
why
we
did
the
rationalization,
email,
high
level
objectives,
anything
to
cause
that
that's
why
I
was
typing
in
the
back
in
the
background,
trying
to
figure
out
all
right,
what
record
things
need
to
get
done
so
that
we
can
aren't
you
dizzy?
Things
start
struggling
people
over,
but
I
don't
want
to
create
a
moving
a
moving
target.
G
So
I'm
going
to
want
economy
at
at
things
that
we
don't
think
would
be
nice
ass,
but
we
don't
actually
need
rice
developers
could
come
in
without
I
gated
full
system.
We
don't
want
that,
but
it's
not
block.
It
is
a
problem
when
you
get
to
ask
you
a
cleaner
nice
to
not
have
to
Nicole.
So,
let's,
let's
break
these
things
in
the
milestones,
get
people
prioritize
on
those
and
then
working
through
that
required.
That's
why
we
needed
to
have
a
kickoff
call
to
restart
this
effort
right.
G
G
E
A
A
D
D
Government
body
would
look
like
the
nine
of
the
community
I'm
familiar
with
hatchery
run
things,
and
we
have
quite
a
bit
of
experience
with
house.
Openstack
kids
is
running
things
and
the
scope
of
the
openstack
organization
is
much
much
broader
than
a
robar
product.
So
I
look
to
organizations
such
as
mozilla
org,
the
apache
found
pics
project
from
the
apache
foundation,
or
something
as
as
simple
as
the
folks
who
developed
the
I.
Don't
know
the
mud.
D
If
folks
are
interested
in
that
I'm
going
to
be
following
up
with
this
I've
written
a
bunch
of
stuff
about
it
last
year,
believe
you
get
much
traction
on
it.
But
I'd
like
to
try
to
really
make
that
happen
system,
because
I
think
crowbar
can
be
so
incredibly
useful.
A
wide
variety
of
folks,
especially
with
the
design
of
open
so
far,
that
we
need
to
be
prepared
to
get
people
active
in
the
community.
I.
D
Suppose,
there's
going
to
be
a
lot
of
interest,
you
know,
I
can
get
on
the
I
can
get
on
the
fruit
slide,
show
and
go
over
the
design
and
what
we've
got
with
with
open,
crowbar
and
get
a
whole
lot
of
interest
in
our
project
all
of
a
sudden.
But
unless
we
have
a
governance
body
and
and
really
active
community
participation,
it's
just
going
to
fall
flat
and
will
continue
to
look
like
just
a
veneer
of
open
source
and
not
real
and
like
making
they'll
look
good,
not
really
an
open-source
project.
D
A
E
D
D
For
example,
at
the
ops
coats
on
it,
the
the
chef's
summit
I
had
three
major
infrastructure
as
a
service
organization,
some
open
source,
others
closed
source,
say
we
needed
appointment
or
we
need
an
orchestration
tool
that
works
on
bare
metal.
You
need
a
bare
metal
story
and
we
need
an
orchestration
story
and
you
guys
have
one
and
we
don't
and
we'd
love
to
be
able
to
fit
your
our
product
into
your
product
and
we'd
love
to
be
able
to
help
with
crowbar.
D
How
do
we
get
started
and
all
I
could
say
was
like
find
me
on
IRC,
you
know
and
and
join
the
community
called.
But
you
know
people
are
very
busy
with
their
own
project.
So
when
there's
a
governing
body
and
people
dedicated
to
really
to
continue
these
relationships
than
the
project
came
forward,
then
the
project
will
will
get
a
lot
of
so.
E
D
Were
three
major
infrastructures
of
the
service?
And
then
there
were
some
big
player
dealt
customers
who
wanted
these
features
and
had
the
inner
very
involved
in
the
chef
community
and
have
the
DevOps
kind
of
people
who
can
collaborate
on
this
project,
but
again
they're
just
like
yeah.
It
looks
like
they'll
just
developing
it
and
throwing
it
over
the
wall
and
forgetting
about
the
community.
We
don't
want
to
be
involved
with
that.
We
need
an
organization
that
it's
committed
to
who's,
not
just
reaching
out,
but
maintaining
a
relationship
and
encouraging
participation.
D
D
It
needs
to
be
nurtured.
You
know,
if
you
look
at
how
the
OpenStack
is
this
huge
organization
with
so
many
projects
that
there's
there's
consistent
follow-up,
there's
always
reviewing
now,
there's
always
every
week
with
SATA
gmail
same
thing
with
chefs
same
thing,
with
puppets
same
thing
with
any
of
these
successful
projects,
even.
A
D
D
With
other
large
organizations
like
to
maintain
that
relationship,
but
that
not
actually
community
building,
that's
just
who's
going
to
do
what
and
tit
for
tat
and
your
release
cycle
in
our
release
cycle.
It's
not
it's
not
actually
building
a
community,
so
I'm
super
excited
to
be
able
to
help
out
with
this
and
would
like
to
over
the
course
like
by
the
end
of
March,
to
have
comes
a
mission
statement
and
the
proper
bylaws
and
everything
in
place
to
be
able
to
say.
E
Okay,
now
I
fully
agree
that
the
current
structure,
where
there
is
no
person
really
responsible
and
in
charge
and
not
having
the
full
process
and
the
governing
body
established
as
well
as
not
well
defined
processes
and
infrastructure
to
support
the
open-source.
You
know
the
open-source
development
activity
are,
you
know
severe
em
Frank
steps.
F
Yeah,
I
mean
honestly
judge,
I
think,
just
getting
these
meetings
back
on
a
regular
schedule,
help
if
there's
an
agenda-
and
there
are
minutes
from
the
meetings.
I
think
we'll
see
a
you
know
from
a
practical
point
of
view,
it's
kind
of
hard
for
an
outsider
to
join
the
community
right
now,
because
there's
been
so
much
change
and
dell
has
been
driving
a
lot
of
that
change.
You
know:
we've
had
input
from
other
people,
but
we've
kind
of
been
taking
the
lead.
F
I
think
now's
a
good
time
to
begin
just
having
regular
meetings,
making
sure
people
know
what
we're
doing
letting
people
contribute
and
the
new
doc
system.
The
new
repos
really
make
a
difference
in
making
the
project
more
approachable.
You
know
the
old
organization,
with
the
the
old
code
structure,
with
dev
tool
and
the
way
we're
handling
multiple
repos
was
it's
it's
a
steep
learning
curve.
It's
just
weird,
so
I
think
you're
going
in
the
right
direction
and
I
think
will
will
do
fine
going
forward
here.
F
G
Would
I
would
add
there
proposal
that
was
floated
I,
think
back
in
December
to
begin
a
more
consistent,
maybe
dr.,
very
consistent
predictive.
These
are
stories
that
are
going
in.
The
pull
request
for
stories
that
should
be
discussed
in
community
are
going
to
be
prioritized
as
an
ultra-flattering.
His
word
we
need
to
codify
that
opium
and
then
start
implementing
that
sort
of
got
shot
down
because
crowbar
the
old
crobar
stuff
didn't
have
the
infrastructure
we
needed
table
meant
that
a
plan
I
think
we
have.
We
have
a
chance
to
actually
fix
that.
D
G
And
I
know
there
was
a
straw
men
together,
you're
the
included
things
like
gaiden
told
you.
No
automated
smoked
have
something
about
having
storage
in
here
he's
got
here
defect.
All
these
things
is
that
are
going
to
make.
You
know,
help
turn
this
into
a
product
and
the
other
ones
that
I
thought
was
really
significant
police
coordination.
One
thing
that
seems
like
been
attained
to
cover
one
has
been
different.
A
C
D
You
know
we're
really
hampered
by
running
our
infrastructure,
our
open
source
infrastructure
behind
the
whole
firewall.
It's
just
not
scalable
in
terms
of
access
for
people.
I
I
really
feel
strongly
that
unless
the
the
organization
that
is
hosting
the
infrastructure
is
already
holy
has
open
so
late
its
DNA,
it's
just
going
to
be
roadblock
after
roadblock
after
roadblock
to
be
able
to
expose
what
we're
doing
with
this
project,
we
did
and.
A
D
D
Of
an
open
source
project
is
its
most
tracking
database
and
code.
The
parks
recommendation
image
is
where
the
developers
communicate
and
the
code
is
what
they're
communicating
about
and
without
that
exposed,
you
just
have
no
zombies
walking
around
so
for
all
the
new
infrastructure
pieces
that
we
put
in
place
like
strongly
and
I
want
to
make
this
a
really
important
part
of
the
cross
meeting
perfect
cause
the
processes
that
we
developed
and
the
governance
model.
That
is
we
as
governors
we
will
discourage
or
not
allow.
E
God,
let's
talk
internally
about
it
because
we
are,
we
are
representing
del
vr
del
sol,
the
only
resource
we
can
bring
to
the
table
which
we
got
from
the
company
of
the
end,
one
way
or
another
it's
played
by
Del.
So
let's
figure
out
how
to
do
it
right
before
proposing
something.
So
we
will
be
able
to
deliver.
E
F
As
we
were
talking
here,
Rob
popped
up
a
note
here.
Let's
start
talking
about
deliverables
for
next
sprint,
which
would
be
probably
a
good
idea,
item
number
to
disguise
items
for
a
backlog
which
is
recursive
yeah,
we're
also
being
recursive,
because
we're
linking
to
ourselves
here
for
the
updates,
but.
F
Actually,
we
arguably
should
put
these
the
comments
we
just
made
into
a
separate
minutes
document,
but
armed
looking
at
the
next
sprint,
I,
don't
know
what
the
priorities
are.
I
would
mention
that
I
added
one
item
down
here
on
the
backlog,
which
is
to
look
into
rendering
docks
using
github
flavored
markdown
we've
really
been,
we've
been
going
in
loops
trying
to
deal
with
you
know
with
the
real
markdown
standard.
E
D
F
F
Hey,
I
have
actually
been
I've,
been
starting
to
follow
the
guidelines
for
Ruby
doc.
You
know
when
I
make
changes,
you
know
I'm
putting
in
common,
so
I
haven't
put
a
lot
of
documentation
in,
but
I
am
putting
I'm
putting
Ruby
doc
compatible
comments
on
new
functions
and
things
like
death.
Just
so
we
know
what
they
do,
but
I'm
a
hundred
percent
behind
code
level
doc.
We
currently
have
no
standards
or
guidelines
I'll
pretty
much
any
Kenny.
So.
E
Alright,
so
yeah,
okay
cuz
got
it.
So
we
need
to
have
the
agreement
on
how
we're
going
to
generate
the
docs
and
reach
tools
that
we're
going
to
use
for
that,
and
we
will
have
to
enforce
that
all
the
pull
request
will
have
them
appropriate
documentation
in
the
pull
request
to
to
be
accepted,
and
then
I
will
will
set
up
the
guidance
for
all
of
the
reviewers
to
follow
that.
Okay,.
F
H
H
We
don't
have
that
kind
of
knowledge
base
yet,
and
I
think
that
you
know
like
Chris
and
I
are
kind
of
stuck
we've
gone
as
far
as
we
can,
with
the
ceph
bar
clamp
as
a
skeleton,
but
our
stuffs
installing
not
working
and
now
we're
like
where
we
do
next
so
I
think
to
bring
more
people
on
board.
That
would
be
the
next
priority.
In
my
opinion.
Oh.
B
E
Let
the
community
decide,
but
all
of
the
work
is
going
on
right
now
in
the
current
organization,
on
not
an
open,
crowbar
and
again,
if
open,
crowbar
is
ready
for
the
development
to
be
done
on
that
in
terms
of
the
tools
and
everything
else,
then
I'm
for
it.
Until
that
time,
I
would
say:
let's
have
the
guidance
to
be
done
where
a
crowbar
to
code
but
base
is
in
the
crowbar
at
work.
Yeah.
F
D
And
that's
good
because
this
works
can
inform
what
we
decide
to
do
with
the
open,
crowbar
reflow
in
terms
of
success,
documentation
plan,
you
know,
I've
gotten
so
much
benefit
out
of
when
Ruby
code
is
well
documented
and
it's
easy.
The
like
you
know,
I've
lived
in
the
chef's
coat
and
it's
not
going
dating
for
a
while
and
system.
Isn't
great.
D
D
F
D
C
G
G
There's
obviously,
a
voice
to
hold
on
there's,
obviously,
a
looping
problem
with
no
internal
process,
because
we
can't
commit
items
are
not
in
the
spring
yet.
So
this
is
this,
this
part
of
the
process
of
Jesus
right.
We
think
we
need
to
figure
out
how
to
do
that.
Bc
actually
can
probably
put
things
in
our
special
commit
or
priorities,
and
then,
after
after
we
get
done
planning
eternally,
we
can
then
do
the
priority
to
commit
well
they're
not
committed.
Yet
we
need
to
work
out
a
process.
Okay,.
E
H
D
Will
well
well
turning
to
commitment
after
our
own
print
planning
and
any
other
groups
who
would
join
us,
you
know
we
would.
We
would
meet
on
these
paul's
and
say
leave
the
things
we
want
to
take
back
to
our
group
to
commit
to,
and
hopefully
you
know,
some
of
them
to
be
firm
commitments
during
the
community
calls,
but
others
like
for
our
process
have
to
go
back
to
the
balance
off
of
customer
needs
and
internal
needs.
A
very
natural
process.
D
B
B
B
A
D
We
get
together,
we
planned
like
we
are
doing
now.
We
go
back
to
our
separate
organizations
and
then
the
separate
organizations
report
back
to
you
know.
Dell
is
committed
to
these
items
for
the
Sprint
internally,
what
they
enlisted
as
priorities,
and
they
came
back
as
well.
You
know
some
of
them
dropped
for
us,
we'll
get
them
you
know,
so
they
can
pick
it
up
for
next
sprint
and
we
can
reshuffle
there.
E
E
What
is
the
communication
we
go
on
a
process
for
documentation,
we're
going
to
switch
to
set?
Is
it
yard?
Is
it
our
dock
from
the
Ruby
and
set
up
the
process?
How
to
do
that?
I?
Think
that's
a
very
concrete
thing!
You
have
some
discussion
on
the
reflector
and
then
we
can
finalize
that
tangible.
The
second
one
is
the
one
which
David
mentioned
there
is
the
full
documentation
of
how
to
create
the
bar
clamp.
How
to
deploy.
E
D
E
One
word
well
think
Judd
with
respect
to
or
the
Dockers
the
goal
for
the
Dockers
work
with
you
were
doing
is
to
integrate
these
testing
framework.
So
we
can
test
the
scale
out.
So
you
can
test
a
larger
number
of
the
notes
which
includes
you
know
note.
We
can
do
obviously
bias
and
right,
but
we
should
be
able
to
do
the
no
discovery
and
putting,
whereas
on
a
note,
so
let's
set
up
the
meeting
between
yourself
and
Derek.
E
H
D
To
Derek
academically
talk
to
dark
and
we
can.
We
can
sort
of
blue
sky
all
the
things
we'd
like
to
do
with
dr.,
and
so
we
can
get
a
set
of
feeling
for
its
capability,
but
I
can
give
them
a
demo
of
what
I've
got
working
and
then
we
need
to
plan
exactly
how
every
integration
would
work.
Such
an
implementation
of
that,
which
is
a
big
fight
too
big
a
bite
for
the
Sprint.
G
G
Included,
put
in
that
because
I'll
be
able
to
debate
the
face
with
Erick
and
that'll
help,
but
some
of
some
of
the
things
that
you're
describing
Arkady
are
some
quite
make
sense
with
docker
because
of
the
way
it
does
it
work.
So
we
need
to.
We
need
to
clarify
what
soccer
useful
for
from
that
perspective
in.
A
A
A
D
I
think
we're
kind
of
wrapping
up
I
had
the
my
last
thing
was
we
have
to
collect
agenda
for
design
calls
and
then
the
review,
the
state
of
the
dev
tool.
I
guess
we're
not
going
to
get
to
it-
would
be
foolish
to
try
to
review
the
spate
of
acceptable
now
and
if
there's
any
other
agenda
items.
Folks,
we've
longed
for
a
follow-on
design
calls
let's
hear
them
in
the
in
the
CD
2014
etherpad.