►
From YouTube: AMA on former JSF projects
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
Slides: https://docs.google.com/presentation/d/1SemAifhI1IloVJnR1gyuQZsB6A-nAME9_iC5qwgMHHc/edit?usp=sharing
A
C
C
A
Okay,
I'll
just
quickly
I,
don't
think
I
need
to
introduce
what
jquery's
know,
but
if
you
want
to
reach
out
to
that
project,
the
representatives
are
dating
have
been
and,
to
me
will
I
think
largely
they're
working
on
infrastructure
and
they
just
basic
kind
of
routine
release
management.
Nothing
stuff,
like
those.
A
A
A
A
F
A
C
G
A
A
A
A
There
it's
a
lynching
tool,
I
think
these
are
pretty
common
projects,
though
so
we'll
see,
y'all
probably
don't
think
too
much
info
about
them
all
right
at
large.
So
we
have
15
our
projects,
which
I
don't
like
the
bell
curve.
I
think
for
our
projects,
but
out
large
projects
are
mostly
projects
that
are
in
maintenance
mode,
they're
still
actively
used,
but
they
don't
necessarily
have
lots
of
resource
requirements
or
the
internet
foundation,
so
they
are
they're
kind
of
trucking.
A
F
H
A
A
A
A
Let's
see
I'm
in
last
but
not
least,
we
have
find
the
Nerdist
projects
which
are
so
called
because
we
value
their
contributions
to
the
ecosystem,
but
they
are
functionally
concluded,
so
we're
not
really
recommending
that
people
go
adopt
these
projects
or
against
these
projects.
But
that
being
said,
we
feel
like
the
word.
Emeritus
really
does,
can
face
respective
appreciation
for
the
time
and
efforts
that
they
wouldn't
and
so
just
to
quick,
shout
out
and
port
one
out
for
jQuery
UI
jQuery
Mobile
requirement.
He
has
it
so.
A
A
A
Okay,
so
that
sort
of
just
kind
of
recounts
that
chance
foundation
projects,
you
know
a
little
bit
later,
we'll
be
having
a
session
for
the
CPC
itself.
So
if
there
are
specific
questions
from
this
group
about
the
cross
project,
council
I
definitely
attending
that
session.
But
if
there
are
questions-
or
you
know,
ideas
about
any
of
these
projects
like
I'm
in
over
the
floor,
we
can
conclude
early.
E
B
A
G
F
B
I
E
A
A
A
Through
this
transition
process,
we
have
sort
of
had
to
figure
out
a
negotiator
at
least
time
how
the
Jazz
foundation
used
to
view
project
operating.
What
worked
with
that,
what
didn't
work
with
that?
It's
for
the
node
community
like
how
to
how
we
sort
of
kind
of
combine
our
process
even
a
way
that
makes
sense
so.
D
A
B
F
H
A
Then
we
didn't
apply
any
metrics
when
we
were
combining
them.
That
is
something
that
I
think
the
CPC
will
take
on
and
within
the
year
to
sort
of
figure
out.
Okay,
how
do
we
really
define
what
an
impact
project
is,
what
the
goals
of
the
project?
It
looks
like
that
kind
of
thing,
but
at
large,
these
15
out
large
projects
opted
into
that
stage
and
he
will
probably
reevaluate
on
in
the
annual
basis
whether
all
of
the
projects
that
are
at
large
should
really
be
there
or.
E
I
E
I
Let's
make
a
working
group
about
that's
really
not
a
team
and
the
biggest
difference
is
like
a
team
is
a
coordinating
group
of
people
working
on
a
problem,
whereas
it
working
derivative,
Germany's
been
chartered
oversee
a
particular
thing
and
they
own
it.
So
a
good
example.
The
difference
here
would
be
like
release
and
build
our
working
groups.
Release
owns
releasing
them.
I
The
TSE
cannot
go
to
the
release
team
and
even
question
what
they're
doing
without
me
chartering
the
team
build
owns,
build
the
TSE,
can't
show
up
and
tell
the
build
team
out
of
the
resources
without
me
chartering
their
team.
The
result
of
this
is
that
even
note
itself
between
the
compound
and
the
TSC
and
our
various
charter
working
groups
is
an
election
of
different
cultures,
which
is
maybe
not
even
to
literally
obvious
each
within
that
has
their
own
governance
or.
I
Drafted
their
own
complete
governance
model,
that's
different
than
any
other
team
over
here,
so
from
a
different
culture
perspective,
and
I
don't
even
think
no
recognize
that
at
first
we're
actually
already
set
up
to
have
all
these
kind
of
like
smaller
teams.
I
do
think
that
thinking
about
how
do
we
support
and
help
lots
of
different
teams
that
have
different
needs
starts
challenging
some
of
these
assumptions.
We
have
the
collaborators
and
it
was
a
really
great
example
that
note
has
a
travel
budget.
I
I
won't
ask
people
to
raise
their
hands
because
they
don't
want
to
put
you
on
the
spot,
whether
or
not
funding,
but
a
non-trivial
number
of
people
in
this
room
have
their
trouble
travel
completely
sponsored
by
the
foundation.
It
wasn't
only
of
Jas.
Well,
one
of
the
things
that
we
realize
is
perhaps
this
collaborators
them.
It
should
really
just
be
its
own
chartered
working
group
under
the
project
Council
that
has
its
own
budget.
I
Certainly
we
haven't
solved
for
one
and
now
we're
like
immediately
moving
to
solving
for
many,
but
when
we
figure
out
how
to
solve
these
problems
from
it
will
be
much
better.
You
know
right
off
the
bat.
One
thing
that
I
could
say
is
like
the
TSE,
though,
used
to
like
more
or
less
directly
report
to
the
Board
of
Directors
over
the
foundation
and
not.
I
I
It's
very
confusing,
but
we
never
really
got
the
best
measure
of
like
having
a
committee.
That's
focused
on
it
now
with
the
cross
project
Council,
we
have
a
community
elected
governing
body
that
hasn't
a
gathering
a
governing
structure
or
anyone
from
any
project
can
come
and
participate.
So
it
doesn't
have
the
same
errors
that
the
marriage
of
product
governing
money
has.
I
But
then
it's
focused
on
solving
these
problems,
so
the
TSC
could
be
far
more
focused
on
maintaining
notice
technical
infrastructure
and
when
we
need
money
for
a
thing,
we
can
just
ask
the
front
across
project
council
and
the
few
reps
with
no
no
Parab
of
that
can
go
to
the
project.
Council
advocate
for
a
very
practical
example
to
be
changes
or
turn
our
charter
used
to
be
chartered
by
the
board
and
any
changes
audit
to
make
to
our
charter
would
have
to
go
to
a
coordinating
and
it's
frustrating.
I
So
it
mean
that,
like
we
would
need
to
have
those
changes,
we
would
need
to
have
those
changes
approved
as
full
requests.
That
pull
request
would
have
to
go
to
legal
legal
and
have
to
review
it
and
rubber
stamp.
It
all
between
or
beings
that
have
applicators
now
we'll
be
able
to
just
get
charter
changes
to
one
of
our,
my
weekly
or
weekly
council
meetings,
and
as
long
as
we
are
making
what
we
call
substantial
changes,
they
can
never
even
need
to
go
to
the
board.
I
So,
yes,
I
think
that,
like
at
face
value,
these
things
seem
more
complicated,
but
this
extra
layer
of
abstraction
that
we
can
have,
because
we
have
more
people
working
together,
is
actually
going
to
create
an
ecosystem
in
process.
That's
a
far
more
fine-tuned
and
far
better
equipped
to
support
individual
projects
than
just
a
foundation.
I
A
We've
definitely
gotten
some,
not
painful,
or
maybe
pretty
boxes,
I
think
one
thing
to
just
wrap
up
so
that
the
next
session
started.
Just
you
know
the
projects.
Do
you
get
to
maintain
their
governance
system
within
the
project,
so
we're
not
mandating
a
specific
type
of
individual
project
governance?
It's
just
the
the
CPC
operational
structure,
which
we
hope.