►
From YouTube: CHAOSS.Asia.Pacific.Community.Sept.23.2020
Description
CHAOSS.Asia.Pacific.Community.Sept.23.2020
A
C
C
B
About,
if
you
have
specific
questions
and
because
most
of
the
slides
we
covered
all
of
most
of
them,
that
was
a
reminder
introduction
to
inner
source,
key
concepts
and
so
on
then
a
bit
about
of
the
industrial
command.
And
then
we
went
through
the
well
how
to
have
certain
metrics
strategy
in
place
and
specifically,
this
role
that
chaos
may
play
together,
the
tooling
and
all
of
these
with
some
use
cases.
So
my
idea
for
today
was
mainly
two
things.
B
D
Hi
hi
hi
daniel,
I
I'm
william,
I
I
have
quite
interesting
discussions
in
our
company's
website
and
as
I'm
not
sure,
if
you
already
knows
we,
we
we
start
the
inner
source,
maybe
four
or
five
years
ago,
and
some
people
are
just
getting
through
it.
And
now
we
are
starting
inner
source
2.0
to
build
the
community
around
the
inner
source
projects.
But
I
got
some
feedback
from
my
colleague:
they
are
not.
D
They
are
not
optimist.
They.
They
think
that
the
inner
source
could
be
failed
because
the
it's
hard
for
them
to
find
the
motivation
for
the
innocence
project.
They
they
think
if
they
have
chance,
they
may
work
on
the
open
source
projects
because
they
can
solve
more
valuable
things
when
they
do
the
open
source
project,
but
do
the
inner
source
project.
B
B
So
one
of
the
experiences
I
can
bring
here
is
what
we
did
some
years
ago,
a
couple
of
surveys
and
interviews
to
developers
from
middle
managers
and
for
for
the
developers
that
there
was
a
real
gap
in
terms
of
expectations
between
both
groups.
First,
we
surveyed
developers
and
we
asked
directly
developers
about
okay.
What
would
you
like
to
to
have
when
contributing,
for
instance,
as
a
reward
right?
So
we
are
talking
about
rewarding
developers
in
somehow,
and
developers
were
stating
that
in
most.
C
B
Cases
they
were,
they
would
be
very
happy
about
having
a
specific,
for
instance,
training
sessions
in
other
technologies,
perhaps
a
ticket
for
attending
specific
conferences
that
they
would
like
to
relate
it
to
any
technical
issue
that
they
are
they
are
in
and
so
on.
Then
we
went
and
asked
middle
managers
and
in
the
case
of
the
military
managers,
the
the
interesting
fact
here
is
that
middle
managers
believe
that
their
developers
were
mostly
interested
in
money
and
having
more
money.
B
So
then
there
is
definitely
a
gap
in
terms
of
what
middle
managers
think
developers
would
like
to
see
or
to
have
or
as
a
reward
and
then
what
what
developers
would
like
to
have
as
a
reward.
So
the
first,
the
first
advice,
perhaps
I
can
give
here-
is
try
to
talk
to
the
developers
and
what
what
they
would
like
to
see
or
have
in
return
as
this.
B
So
in
order
to
motivate
developers,
let's
say
a
policy
we've
seen
that
has
been
applied
in
some
organizations
at
the
inner
search
commons
is
to
try
to
help
them
first
through
training
and
hackathon
sessions
and
then
reward
them.
Somehow,
with
respect
to
this
and
by
reward
that
means
that
you
you,
you
may
need
to
build
certain
sense
of
community
and
for
this
we
can
we
can.
We
can
bring
the
example
of
open
source
communities,
definitely
where
open
source
communities
are
creating
this
sense
or
this
feeling
of
community
and
not
teams.
B
So
what
we
need
to
create
within
organizations
are
those
communities
and,
depending
on
the
approach,
different
companies
are
using
different
different
strategies.
So
we
we
can
go
to,
let's
say
simple
things
as
building
communities
through
the
existence
of
simple
things
as
stickers
or
t-shirts.
Where,
then,
suddenly
people
will
recognize
someone
else,
because
that
person
is
is
have
a
sticker
in
her
laptop
on
her
laptop
for
certain
communities
that
you
have
internally
or
perhaps
they
are
wearing
a
t-shirt
and
they
will
say
to
each
other:
hey
I'm
working
there
as
well.
B
Oh,
so
you
are
this
person,
okay,
great
great,
so
these
are
let's
say,
first
steps
people
are
doing
and
then,
in
the
same
way,
that
in
open
source,
there
are
specific
roles
that
exist
with
the
goal
of
facilitating
and
unblocking
situations
and
so
on,
as
as
community
managers
or
developer
advocates,
or
kind
of
all
of
these
type
of
roles
internally
in
large
corporations.
What
they've
seen
is
that
they
are
they.
B
And,
finally,
perhaps
the
most
motivational
action
is
to
have
in
your
quarterly
goals
something
related
to
participation
in
other
business
unit
projects,
so
in
the
inner
source
projects
and
somehow-
because
if
you
have
this
in
your
quarterly
goals,
then
you
have
a
reason
why
you
should
be
there
at
some
point.
So
this
is
not
about,
let's
say
forcing
people,
but
at
least
at
the
very
beginning,
about
looking
for
the
right
people
to
proceed
to
participate
in
initiative.
So
this
is
about
looking
for
ambassadors,
but
then
they
can
help
spreading.
B
C
D
Okay,
I
I
have
a
another
question
about:
how
do
we
choose
a
peak,
what
kind
of
project
which
is
suitable
for
the
inner
source?
And
currently
we
have
a
bunch
of
the
tools
that
may
use
across
the
department
and
they
may
not
have
the
investment,
because
it's
a
building
tool.
It's
like
the
engineer,
just
creates
this
kind
of
tool
to
impose
their.
B
First
of
all,
probably
you
should
ask
yourself
if
the
project
you
are
releasing
internally
as
inner
source,
if
it
makes
sense
from
a
technological
point
of
view
to
be
in
resource-
and
this
means
is
this
gonna
be
used
by
others
in
the
organization?
Is
this
some
certain
interest
by
other
members
other
business
units?
Is
this
ready
for
a
technological
point
of
view
to
be
shared
with
others?
So
then
others
can
participate
in
the
project
in
somehow.
C
B
With
this
I
mean
not
just
the
technology
but
guidelines
requirements,
process,
design
meetings.
So
all
of
this
so
as
let's
say
that
once
you
open
the
project,
you
should
be
as
transparent
as
possible
with
clear
rules
and
create
clear,
clear
roles
in
the
community.
One
of
those
roles
is
this
concept
of
drastic
committer
that
we
are
playing.
B
We
are
playing
with
in
the
in
at
the
inner
source
commons,
and
the
role
of
the
trusted
committee
is
similar
to
the
role
of
a
committee
in
open
source,
where
this
is
a
person
which
is
typically
a
technical
leader
and
this
person.
If
I
assume
you
are
working
nowadays
kind
of
in
an
agile
way,
probably
with
a
certain
probability.
So
this
means
that
you
are
working
in
teams
of
five
six
people,
probably
all
of
them,
working
in
the
same
office
or
space.
B
Well,
you
know
this
with
a
cubic
rolling
in
all
of
them
at
home,
but
they
are
supposed
to
work
together
because
then,
in
that
way
they
will
be
much
more
productive
with
certain.
Then
we
have
scrum
master
or
whatever
method
you
are
using
in
the
case
of
inner
source,
so
the
documentation
you
are,
you
are
creating
there
in
the
way
of
doing
things
is
mostly
focused
on
the
final
customer
right
final
client
in
our
source.
B
The
documentation
we
need
to
create
is
mostly
for
developers
for
other
developers
that
are
willing
to
participate
in
the
project
and
for
others
to
give
them
clear
rules
that
to
to
show
them
how
to
participate.
So
quick
example
here
is:
will
I'm
if
I'm
going
to
your
house,
probably
you
you
will
have
some
rules
like?
Oh,
please,
take
off
your
your
shoes
or
bring
a
bottle
of
wine,
or
you
know
come
at
this
time
between
this
time
slot,
because
I'm
I
may.
B
Or
with
my
family,
so,
given
that,
if
I'm
going
to
your
house,
you
have
certain
house
rules,
this
is
the
same
way
with
internal
development
in
certain
projects.
So
if
I'm
gonna
participate
in
others
projects,
I
need
to
fully
understand
what
they
are
doing
right
and
for
this
I
need
to
understand
the
guidelines.
I
need
to
know
the
team
behind
all
of
these.
B
I
need
to
understand
how
to
produce
the
code,
how
you
would
like
to
to
deal
with
the
requirements
and
well
certain
good
practices
that
that
you
need
to
have
written
down
somewhere
so
to
foster
this
collaboration.
Is
that
that's
one
of
the
very
first
steps,
the
trusted
committee
good
guidelines
and
have
certain
roles
with
that
they
only
have
written
right
access
so
then
anything
that
anyone
else
produce
needs
to
go
through
a
code
review
process.
B
The
advice
I
can
give
is
all
about
thinking
twice.
If
opening
that
project
makes
sense
internally,
that's
all
because
you
can
go
it's
it's
probably
the
same
in
open
source,
so
you
can
search
something
with
the
rest
of
the
world
in
github
and
say
now.
This
is
open
source,
but
you
may
not
have
any
any
contribution
at
all
right.
So
then,
is
this
really
open
source
thing,
so
the
same
happens
with
inner
source
where
well
we
are
using
github
enterprise
or
gitlab
enterprise
or
any
other
tool
that
lassen
has
stacked
internally.
B
So
we
are
doing
inner
source
okay,
but
how
many
contributions,
for
instance,
from
other
business
units?
Are
you
having
why
others
so
and
going
to
your
specific
questions?
Why
why
there
are
other
people
or
developers
that
are
not
coming
to
my
to
my
project?
Why
is
this
happening?
Why
don't?
I
have
any
kind
of
traction.
B
B
So
then,
reusability
and
discoverability
of
existing
projects
in
the
organization
is
key.
So
how
to
do
this?
That's
that's
another
problem,
and
probably
this
is.
This
is
quite
interesting
for
chaos
as
well
in
the
sense
of
how
can
people
discover
in
the
right
way
project
open
source
projects
or
how
can
people
reuse?
B
D
Yeah
yeah
yeah,
I
I
think
you
you
make
or
good
questions
you
mentioned.
We
need
to
ask
ourselves
if
this
inner
social
project
will
be
well
well,
have
any
other
participation
from
other
departments
or
if
they
have
any
users.
I
I
just
have
a
questions
about
the
trust
trusted
committee,
because
in
in
my
company
few
people
have
open
source
experience,
so
that
could
be
a
trendy
things
for
we.
Normally,
we
we
think
the
trusted
committer
is
the
project
owner.
Maybe
the
project
founder
or
something,
but.
D
B
B
B
B
And-
and
this
means
that
we
need
to
to
change
the
the
way
of
working
of
management
and
managers
in
general,
probably
to
a
more
community
oriented
type
of
work
somehow
and
that
person
so
would
be,
could
be
the
one
kind
of
helping
others
and
so
on.
So
what
other
companies
have
have
have
done
so
far?
Is
they
they
have
their
own,
how
to
say
kind
of
inner
source
department
or
inner
source
office,
where
the
same
way
that
you
have
open
source
office
and
so
on?
They
are
dealing
with
this
detail.
B
Out
there
there
are
other
organizations
that
are
using
the
open
source
office
as
a
way
to
start
training
developers
to
work
internally
in
the
same
way
that
they
should
work
outdoors.
So
then
that
means
that
they
are
kind
of
doing
inner
source
with
the
goal
of
scaling
up
all
of
the
developers
they
have
so
at
some
point,
all
of
them.
It
doesn't
matter
if
they
are
working
internally
or
externally
in
the
open
or
in
a
regulatory
environment
that
they
are
working
in
a
pretty
similar
way.
B
So
inner
source
is
a
really
good
way
to
to
help
people
to
to
have
to
acquire
this.
This
kind
of
skills
right
related,
open
source
skills
yeah.
So
with
respect
to
the
trusted
committer
that
that
department
set
of
people
mana
years
kind
of
first
should
have
a
full
understanding
of
how
open
source
works
in
in
the
different
flavors.
Let's
say
because,
as
there
are
different
flavors
of
open
source,
then
there
are
different
flavors
of
inner
source
and
that
department
would
be
the
one
helping
others
to
understand
this.
B
So
the
first
step
is
about
looking
ambassadors
like
okay,
who
else
in
the
company
is
interested
in
participating
in
working
in
this
way.
In
exploring
these
these
ways
of
working
and
those,
then
we
need
those
might
be
at
some
point,
be
those
technical
leaders
or
at
least
helping
others
to
become
those
technical
leaders.
So
then
that
would
be
the
role
of
the
trusted
committee
yeah.
So
this
is
this
is
more
or
less
there
is.
There
is
a
book
by
by
paypal
where
they
were
specifically
dealing
with
this
problem.
B
D
Okay,
currently
I
I
played
the
the
the
the
trainer
or
the
mentor
to
for
our
intel
in
in
the
source
project
we
have
about
around
10
projects,
but
but
here's
the
my
challenge,
I
I
I
can
only
pay
attention
to
one
or
two
projects
at
a
time,
but
now
we
we,
we
have
a
bunch
of.
Maybe
it's
near
turn
projects.
So
so
I
I
need
to
convince
my
my
my
my
manager,
my
leader,
to
to
give
me
some
time.
D
B
Yeah,
the
way
I
see
that
might
be
worth
exploring
is
through
trying
to
automate
things
on
the
one
hand,
so
so
I
I
just
served
in
the
chat
as
well.
We
we've
been
working
on
a
maturity
model
in
the
at
inner
church
commons,
with
some
output
from
from
previous
projects
and
so
on,
and
the
idea
is,
is
well
not
about
using
maturity
model
as
cmmi
that
perhaps
one
company
is
asking
our
company
to
be
certified
in
certain
level,
blah
blah
blah.
B
But
it's
more
about
about
self-assessment
and
create
awareness
about
where
you
are
at
the
at
the
resource
journey,
because
if
you
have
the
trusted
committers,
you
have
ambassadors
and
people
that
are
starting
to
participate.
So
you
are
creating
some
kind
of
community,
probably
the
the
more
you
are
like
the
apache
server
foundation
or
or
the
openstack
foundation
cncf
any
other
foundations
the
better,
because
that
means
that
you
will
be
internally
transparent,
collaborative
communicative.
C
B
Cetera
right,
so
this
maturity
model
is
kind
of
trying
to
assess
that
so
checking
this
might
be
might
be
worth
having
having
a
look
at
this
yeah
so,
and
this
brings
the
discussion
about
the
inner
source
patterns,
which
is
what
I
I
can
show
you
in
the
following
minutes.
If
you
want
so,
I
don't
know,
if
you
have
more
questions.
D
B
C
B
Perhaps
I
don't
know
if
we
can
focus
the
discussions
here
in
chaos
around
how
to
measure
things
in
an
inner
source
initiative.
That's
one
thing
and
then
yeah
there
are.
There
are
of
course,
companies
that
are
providing
commercial
services
around
dinner
source
and
so
on
so
yeah
in
terms
of
first
steps
or
specific
consultancy
that
you
can
check
at
the
inner
source
commands
as
well.
So
those
those
are
the
way.
So
I
don't
know
much
on
drone
and
others.
What
you
think
about
the
topic
of
these
meetings
should
be
at
some
point.
F
B
Meetings
like
this
yeah,
so
there
are
there
are,
there
are
three
four
working
groups.
One
of
them
is
the
learning
path
which
is
about.
There
is
a
bunch
of
videos
edited
by
already
in
this
case,
with
the
goal
of
teaching
how
inner
sources
versus
et
cetera.
So
william.
Definitely
you
should
have
a
look
at
this
yeah,
it's
really
good
materials.
B
Then
there
is
another
one
related
to
patterns
which
is
looking
for
solutions
for
existing
problems,
and
there
is
another
one
for
marketing.
There
is
another
working
group
for
for
the
for
the
summits,
and
there
is
another
group
for
the
governance,
and
so
on
so
I
mean
there
are
a
bunch
of
them
and
then,
in
the
slack
channel.
B
There
there
are
some
so
far,
people
are
kind
of
building
their
own
stuff
internally,
so
they
are
decide.
They
are
sharing
from
time
to
time
their
experiences
when
having
metrics
the
tooling
if
they
have
reused
any
open
source
tool
of
the
they
started
from
scratch
and
so
on.
But
there
are
definitely
discussions
about
metrics
so
and
this
maturity
model
might
be
something
related
to
metrics,
as
you
need
to
move
from
one
level
to
the
other
so
more
or
less.
This
is
the.
F
You
know
what
I
mean,
because
it
seems
like
the
larger
discussion
around
inner
sources
very
well
set
in
inner
source
commons
and
the
chaos
project
could
help
articulate
what
some
of
those
metrics
are
that
are
used
internally
and
try
to
pull
out
the
stories
about.
Why
they're
important
I
mean
this
is
when
we
do
the
metrics
articulation.
F
B
F
D
Yeah
yeah
couldn't
say
we.
This
is
my
first
priority
task,
so
I'm
quite
interested
about
that.
But
at
the
meantime
I
also
quite
interested
you
know
about
the
magics
and
to
try
to
use
this
metrics
to
evaluate
the
inner
source
project
health.
So
so
I
I
think
it's
a
quite
common
use
case
scenarios
so
so.
E
D
D
F
So
I
would
propose,
then,
that
we,
it's
your
point
to
williman
and
daniel
that,
because
we
don't
have
a
specific
location,
whether
it's
intersource
commons
or
chaos,
where
thinking
through
inner
source
metrics
work
exists,
it
doesn't
sound
like
it
exists
right
now,
formally
in
inner
source
commons
to
me,
it
seems
completely
reasonable
to
use
this
time
to
start
thinking
through
what
some
of
those
metrics
can
be
and
why
we
would
basically
thinking
through
what
those
metrics
can
be.
You
know,
what's
the
description,
what's
the
objective,
how
would
we
measure
them?
F
What
are
we
hoping
just
following
the
goal?
Question
metric
approach
and
because
we
have
folks
like
daniel
who
are
so
well
connected
with
inner
source
commons
that
we
could
start
the
line
of
communication
is
certainly
open
between
chaos
and
inner
source
common,
so
the
work
that
would
occur
on
this
call
to
try
to
define
what
some
of
those
metrics
would
be.
F
F
There's
no
reason
to
reinvent
it,
and
I
think
it's
also
very
reasonable
to
use
the
the
asia
pacific
call
to
focus
on
this
again.
This
seems
to
be
the
important
topic
of
interest,
and
I
think,
when
we
set
up
the
asia
pacific
call,
it
was
to
explore
where
those
points
of
connection
could
be-
and
this
is
the
one
that
has
has
kind
of
drawn
forward.
G
I
do
want
to
ask
the
question,
though,
of
whether
or
not
that's
reflective
of
everyone
that
joins
this
call,
because
I
know
that
a
couple
of
people
are
very
interested
in
inner
source,
but
a
lot
of
people
have
been
quite
quiet.
What
I
don't
want
to
do
is
take
quiet
for
agreement
and
and
just
and
go
down
the
path
of
making
this
specific
to
inner
source.
If
that's
not
reflective
of
kind
of
the
majority
of
the
people
on
the
call,
I
just
want
to
make
sure
that
we
we
don't
move
too
quickly
down.
D
D
D
G
H
H
F
Yeah,
I
was
going
to
say
to
to
don's
point:
that's
a
well
well
taken.
I
don't
think
my
intention
wasn't
to
turn
this
into
an
inner
source
working
group
call.
It
was
maybe
just
to
spend
a
little
bit
of
time
on
this
issue
and
we
can
always
reflect
on
maybe
what
the
next
topic
is.
So
the
point
super
well
taken.
G
B
D
H
B
D
Yeah
I
yeah
I
I
just
want
to
start
this
conversation
so
so
get
some
feedback
from
from
who
wants
to
join,
and
I
can
ask
around
because
I
know
a
bunch
of
people
who
quite
interesting
about
inner
sauce.
So
maybe
I
can
bring
them
to
this
kind
of
meeting,
but
but
it's
look
like
we
just
hijacked
the
the
kills
asia
pacific
meetings
to
the
inner
speed
meeting.
I
I
think
the
violence
is
we
talk
about
the
magics.
D
So
if
we
can
measure
this
kind
of
dependency
or
of
it,
it's
very
good
for
us
to
find
a
good
common
project,
which
is
shell
across
across
the
department
of
some
sense,
because
the
the
the
more
common
project,
the
more
user
they
may
have
more
development
they
may
have.
So
this
kind
of
project
is
a
good,
a
very
good
candidate
project,
well
for
the
inner
source.
D
So
so
maybe
we
can
get
some
self
assessment
by
this
listing
these
kinds
of
metrics.
So
I
I
think
this
is
a
good
waste.
So
so
so
this
metrics
could
be
part
of
the
chaos
projects
to
and
share
with
the
inner
source
comment
so
so
to
to
project
thinking.
Working
together
can
work
together
in
this
way.
So
this
is
my
my
myself
in
this.
H
F
D
I
F
I
D
I
I
know
there
was
some
some
websites
which
is
used
for
the
program
interview,
so
so
each
one
can
tap
to
see,
and
I
I
I
will
look
around
to
see
if
we
can
access
it
directly
from
china.
So
so
maybe
we
can
use
it
it's
to
do
the
real-time
editing
and
then
we
we
can
copy
past
it
to
the
google
doc
and
then
send
out
with
the
email
or
something
so
just
get
around.
With
this.