►
From YouTube: CHIPS Alliance TSC Meeting - 2021-01-27
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).
A
All
right,
good
morning,
everybody
we
are
recording,
welcome
to
the
first
tsc
meeting
of
the
chips
alliance
on
the
call.
Today,
we've
got
myself
brian
warner
from
the
linux
foundation.
We
have
henry
cook
from
sci-5.
We
have
michael
guilda
from
ant
micro,
and
the
purpose
of
today's
call
is
to
adopt
the
initial
documents
of
the
tsc
and
really
get
things
bootstrapped
and
moving
so
henry.
Would
you
like
to
call
us
to
order
yeah?
I
would
like
to
call
the
meeting
to
order.
Okay,
great
so
we're
getting
started.
It
is
11
26
a.m.
A
The
work
that
we're
doing
here-
okay
for
anybody
who's
looking
at
this
and
and
wondering
you
know
what
we're
doing
here-
the
chips
alliance
technical
steering
committee
is
the
the
group
that
handles
the
ongoing
coordination
between
the
various
different
technical
projects
that
are
part
of
the
chips
alliance,
the
projects
and
specifications
we
are
aiming
to
meet
monthly
and
typically,
the
way
this
will
work
is
that
we
have
a
repository
chips
alliance
tsc,
which
is
where
we
keep
all
of
our
tsc
documents.
A
But
the
intention
is
in
the
future
that
these
meetings
will
be
held
regularly
and
they'll
be
used
for
project
onboarding
or
for
project
status
reports,
or
any
other
of
the
ongoing
initiatives
that
the
tsc
may
decide
to
take
upon
itself.
A
So
that
gets
us
through
our
first
part
here
or
welcome
the
first
thing
we
are
going
to
do
today,
so
that
it's
you
know
available
and
easy
for
everybody
to
find
is
to
review
a
couple
of
key
tsc
meeting
procedures.
A
One
of
the
main
things
that
we
do
need
to
go
through
here
is
what
what
are
the
quorum
requirements
and
how
does
the
tsc
make
decisions?
Quorum
requirements
are
pretty
straightforward.
They
are
laid
out
in
the
technical
charter
which
we're
going
to
be
adopting
here
shortly
and
basically,
it's
just
a
majority
of
voting
tsc
members
which
that
leads
us
into
our
second
point
here
of
what
exactly
is
a
voting
tsc
member
and
how
our
decision
is
made
as
as
defined
in
the
charter
which
we're
about
to
adopt
the
voting.
A
Member
now,
the
term
voting
member
is
somewhat
misleading
in
the
way
that
we
expect
the
chips
alliance
tsc
to
operate
on
an
ongoing
basis
in
general,
the
goal
is
to
operate
using
the
lazy
consensus
model,
which
is
essentially
when
a
decision
needs
to
be
made.
If
it's
not
something
which
specifically
needs
a
formal
vote
decision
is
basically
made
by
consensus.
So
whoever
shows
up
and
and
where
the
prevailing
winds
appear
to
be
blowing
is
the
way
that
we
make
decisions.
A
The
goal
is
to
be
as
lightweight
as
possible
and
to
eliminate
formalities
where
we
don't
need
formalities
now,
on
the
other
hand,
there
will
be
some
things
which
do
require
a
vote.
These
things
would
be
fairly
rare,
but
an
example
would
be
if,
if
there's
a
particularly
contentious
decision
or
something
where
it's
not
easy,
to
determine
a
consensus,
in
which
case
then
we
would
go
through
a
voting
process,
a
private
voting
process
for
for
making
that
decision
very
much,
though
that
is
expected
to
be
the
exception,
rather
than
the
rule.
A
A
And
that
basically
brings
us
to
the
to
the
next
point
in
the
agenda,
which
is
to
adopt
the
tsc
charter.
Now
this
one
in
general,
the
tsc
charter,
you
can
find
a
link
to
it
if
you
go
to
technical
dash
charter,
dot,
ships,
alliance,
dot,
org.
That
will
take
you
to
this
page,
which
has
the
technical
charter.
A
The
history
of
this,
the
the
governing
board
and
the
legal
committee
for
the
chips
alliance
have
been
working
on
the
draft
of
this,
and
I
have
agreed
to
recommend
terry
that
the
tsc
adopt
this
as
the
charter.
A
The
technical
steering
committee,
the
the
responsibility,
is
really
providing
technical
oversight
and
what
this
means
it
doesn't
mean.
The
tsc
is
telling
the
projects
what
to
do,
but
rather
the
tsc
is
playing
a
coordinating
role
and
ultimately,
you
know
really
when
you
look
at
what
the
tsc
does
it?
It's
it's
supposed
to
be
the
neutral
body
in
the
middle
of
all
the
different
projects
in
the
ecosystem,
where
you
know
we
can
get
together
and
get
work
done
that
spans
more
than
one
project.
A
There's
a
provision
in
the
technical
steering
committee
for
projects
with
similar
characteristics
be
organized
into
work
groups.
The
idea
here
is
that
there
may
be
certain
projects
which
have
some
things
in
common
and
they'd
like
to
meet
on
an
ongoing
basis,
and
you
know
have
a
ongoing
zoom,
zoom
call
or
whatever
the
case
may
be.
A
There
are.
In
addition,
there
are
provisions
in
here
on
who
the
voting
members
are
so
I'd
mention.
As
I
mentioned
earlier,
each
one
of
the
projects
that
becomes
part
of
the
chips
alliance
can
say
you
know
we're
designating
a
certain
person
as
our
voting
member
it
is.
We
do
need
for
each
one
of
the
projects
to
do
this,
so
that
when
a
decision
does
require
a
vote,
we
know
who
to
go
to
in
order
to
collect
those
votes.
One
of
the
key
things
that
that
changed
early
on
in
the
process.
A
The
charter
also
defines
who
participates
in
the
project.
Generally
speaking,
if
a
project
doesn't
already
have
roles
set
up,
we
recommend
they
adopt
this
terminology
of
contributors
and
committers
we're
contributors
or
anybody
who's.
Making
a
contribution
to
the
project.
Committers
are
the
people
who
decide
whether
or
not
to
apply
that
contribution
against
the
project
itself.
A
One
of
the
key
aspects
of
of
open
source
projects
here,
and
particularly
projects
under
the
chips
alliance,
is
that
we
do
need
to
have
defined
workflows
so
that
contributors
who
are
actively
involved
in
the
projects
who
are
working
their
way
towards
project
leadership,
know
what
it
takes
in
order
to
become
a
committer
and
a
project.
A
This
is
really
a
key
part
of
open
governance
is
making
sure
that
each
one
of
these
things
is
is
defined,
and
certainly
one
of
the
the
areas
where
the
tsc
can
provide
leadership
is
by
providing
policies
and
procedures
and
draft
documents,
and
things
like
that,
so
that
projects
that
come
in,
which
don't
already
have
this
open
governance,
defined
understand
what
exactly
they
need
to
do
in
order
to
put
these
things
in
place.
A
In
addition,
the
charter
says
that
the
tsc
has
the
responsibility
and
the
right
to
be
able
to
say
here's
what
the
workflow
looks
like
when
a
project
wants
to
come
into
the
chips
alliance.
A
Here's
here
are
the
different
stages
that
it
would
progress
through
as
it
becomes
mature
and
here's
the
process
for
archiving
all
projects
have
a
life
cycle
and,
at
a
certain
point,
certain
projects
may
decide
that
it's
time
to
time
to
wind
up,
so
the
tsc's
responsibility
really
is
to
here
to
to
define
these
processes
and
to
to
be
able
to
follow
them.
A
A
The
key
theme
that
you'll
see
throughout
all
of
these,
though,
is
that
decision
making
is
pushed
to
the
lowest
level
possible
in
really
in
in
technical
matters.
The
goal
again
is
not
for
the
tsc
to
make
technical
decisions
for
the
project
or
to
set
technical
direction
for
them.
The
goal
is
for
the
projects
to
do
that
and
the
tsc
is
involved,
particularly
for
things
that
cut
across
projects.
A
Tsc
voting
procedures
are
outlined
here,
quorum
again,
as
I
mentioned
earlier,
for
tsc
meetings
is
50
percent
of
all
voting
members
tsc
can
still
meet
if
quorum
is
not
met,
but
you
know
can't
make
decisions,
and
in
this
case
it's
voting
decisions
at
the
meeting
and
the
there's
one
part
in
here
that
I
should
probably
clarify
if,
if
a
vote
can't
be
resolved
by
the
tsc
like,
for
example,
if
there's
something
which
comes
up
for
vote
and
it's
deadlocked,
then
there
are
various
different
things
you
can
do.
A
One
of
them,
though,
the
kind
of
key
thing
it's
outlined
here
in
the
technical
charter
is
that
it
can
also
be
referred
to
the
linux
foundation
for
for
help
on
the
on
making
that
final
decision
again.
This
is
a
last
resort,
though
the
goal
is
not
to
to
tell
the
project
what
to
do
and
then.
Finally,
there
are
a
number
of
items
in
here
on
trademarks
and
things
like
that
they're.
The
final
piece
that
I
think
we
probably
ought
to
take
a
look
at
is
intellectual
property
policy.
A
This
is
I'm
not
going
to
read
through
this
on
the
call,
but
it
is
worth
noting
that
this
is
where
the
intellectual
property
policy
is
defined,
and
this
is
where
the
you
know,
projects
are
looking
to
refer
to
the
chips
alliance,
ip
policy.
This
is
where
you
go
to
find
it.
A
A
The
tsc
is
a
self-governing
body,
and
again
this
takes
a
two-thirds
vote
of
the
entire
tsc,
and
that's
that's
all
the
voting
members.
So
basically,
one
representative
from
each
project,
plus
henry
henry
and
michael-
does
that
make
sense
any
questions
on
any
of
that.
A
Okay
sounds
good,
so
now
we're
at
the
the
key
part
of
the
meeting
henry
is
the
sole
tsc
member.
Would
you
like
to
adopt
the
tsc
charter
yep?
I
would
like
to
adopt
the
tsc
charter,
as
recommended
by
the
governing
board.
Okay
sounds
good.
That's
adopted
next
up.
We
have
the
couple
of
other
documents
to
go
through
as
well.
This
is
a
one-time
thing
that
we
do
in
the
first
meeting.
Basically.
A
Go
back
to
the
tsc
repo,
if
you're
looking
at
the
tsc
repo,
what
you'll
see
here
is
a
fairly
long
document
that
lists
out
a
number
of
key
things
that
helps
the
chip's
alliance.
Tsc
run
itself,
everything
from
where
you
find
the
various
collaboration
tools
like
where
to
find
the
mailing
list
and
where
to
go
on
slack
and
where
to
find
a
calendar
to
the
tsc
members.
A
Currently,
as
I
had
mentioned
earlier,
henry
is
the
the
only
tsc
member,
and
this
is
meant
to
be
a
a
bootstrap
period
where,
basically,
we
are
going
to
work
on
getting
the
initial
projects
to
go
through
the
project.
Lifecycle
go
through
the
project
application
process
so
that
we
can
get
some
additional
tsc
members
on
board.
A
A
The
a
few
other
things
to
call
attention
to
here
in
the
readme
again,
it's
documented
how
to
become
a
tsc
member.
So
the
technical
charter
describes
the
composition
of
the
tsc.
Of
course
this
is
one
member
from
each
project.
A
The
key
thing
here
and
the
thing
that
I
want
to
make
sure
that
if
you
take
nothing
else
from
this,
take
this
tsc
itself
is
open
for
up
for
everybody
to
attend.
You
don't
have
to
be
a
voting
member
to
participate
and
attend
tsc
meetings.
Nor
do
you
have
to
be
a
voting
member
to
participate
in
the
consensus
seeking
process
so
again
becoming
a
member.
This
is
strictly
related
to
things
which
require
a
formal
vote.
A
The
next
thing
in
the
readme
goes
down
through
the
definition
of
what
the
projects
and
the
work
groups
are
michael
and
henry,
and
I
have
gone
through
over
the
past
few
months
here
and
put
together
a
draft
process
here
for
the
project
life
cycle.
A
Essentially,
we'd
have
three
stages
here:
there's
sandbox
there's
graduated
projects
in
their
archives
projects
when
a
project
is
looking
at
joining
the
chips
alliance
tsc.
This
is
the
process
they
would
go
through.
So
initially
for
projects
which
are
are
you
know
wanting
to
prepare
themselves
to
become
a
part
of
the
tsc
and
and
to
join
the
chips
alliance?
We
have
a
stage
called
sandbox,
which
is
optional,
but
the
idea
here
is
that
it's
it's
a
place
where
a
project
can
say:
hey,
I'm
I'm
interested
in
joining
the
chips
alliance.
A
What
do
I
need
to
do?
Well
this?
Basically,
it
allows
us
to
know
who
they
are
to
help
them
through
this
process
and
guide
them.
Other
projects
may
say:
okay,
you
know
I'm
fine.
I
don't
necessarily
need
to
go
through
the
sandbox
I'll,
fill
out
the
application
and
we'll
just
start
there,
in
which
case
you
can
skip
the
sandbox
phase.
A
Finally,
if
a
project
has
decided
that
it's,
you
know
that
it's
time
to
wind
down
operations
or
if
you
know
it
becomes
clear
from
a
lack
of
activity
that
a
project
has
has
wound
down
on
its
own,
then
there's
a
process
as
well
to
archive
projects,
basically
to
provide
long-term
storage
and
kind
of
a
safe
home
for
for
the
foreseeable
future.
Even
though
they're
not
active.
A
We
include
in
this
document
here
a
number
of
things
on
how
to
actually
go
through
and
instantiate
a
project
and
to
put
together
a
work
group.
I
won't
go
through
these
on
here
and
then
there's
another
section
in
here
which
has
been
under
discussion
in
various
different
places
about
setting
up
the
chips
alliance.
Commons
and
this
came-
there
were
a
number
of
a
number
of
comments
from
folks
saying.
A
Well,
there
are
projects
which
they
may
be
members
of
other
organizations,
or
they
may
be
wanting
to
have
some
affiliation
with
chips
lines,
but
are
maybe
not
ready
to
adopt
all
the
policies
and
procedures,
but
we
still
want
to
make
sure
that
we're
keeping
you
know
keeping
close
touch
with
these
projects.
This
is
the
the
goal
of
the
chips
alliance.
Commons
is
basically
to
have
a
way
to
to
keep
track
of.
A
The
last
bits
of
this
document
that
I'm
just
going
to
call
attention
to
here
are
the
various
policies
and
procedures.
This
is
everything
from
you
know.
I
I've
identified
a
security,
vulnerability
and
ships
alliance
project.
I
don't
know
who
to
go
to
this,
provides
a
default
escalation
path.
A
We
basically
want
to
make
sure
that
you
know,
since
this
is
a
global
organization,
with
people
working
in
different
time
zones.
If
somebody
wants
to
change
one
of
these
things
in
this,
this
policy
document
that
there's
enough
time
for
it
to
be
reviewed,
so
that
decisions
don't
get
made
unilaterally
or
or
too
quickly.
A
There
are
a
few
other
things
in
here
as
well.
Again,
a
call
out
to
the
ip
policy
call
out
to
some
of
the
common
questions
that
we
get
like.
What's
the
policy?
What's
the
recommended
policy
for
copyright
notices
in
code
for
projects
like,
for
example,
do
I
need
to
if
I
make
a
change
to
a
project?
A
Do
I
need
to
add
a
copyright
line
to
the
top
of
the
file
linux
foundations
published
some
guidance
on
this
to
hopefully
simplify
things
for
projects
and
then,
finally,
we
put
together
a
couple
of
standard
website
footers
when
a
project
becomes
a
member
of
the
chips
alliance
or
becomes
a
member
of
the
the
chips
alliance.
Tsc
it'd
be
helpful.
A
If
you
include
this
information,
you
know
both
in
your
github
readme
or
on
your
project
websites,
which
basically
says
you
know
this
project
is
associated
with
the
chips
alliance
and
here's
where
to
find
our
our
policies
and
procedures.
A
A
So
henry
and
michael
do
either
of
you
have
any
questions
on
this.
Are
you
comfortable
with
the
contents
of
what's
in
here,
yeah,
I'm
comfortable
with
it?
Thank
you
for
that
thorough
review.
Sure
yep
same
here,
okay
sounds
good.
So
all
right,
I'm
going
to
take
that
as
an
approval
that
we're
basically
adopting
these
policies
and
procedures
and
again
these
are.
These
can
be
changed.
The
it's
the
chips
alliance,
tsc
is
a
self-governing
body,
and
these
the
contents
of
this
document
you
know,
can
be
changed
by
the
tsc
itself.
A
Okay
sounds
good.
Thank
you,
michael
okay,
and
then
I
wanted
to
also
really
quickly
go
through
the
contributing
document
as
well.
We
have,
let's
see
here
there
we
are
so
this
is
currently
the
drafts
folder.
A
A
If
there's
a
situation
where
a
project
has
some
sort
of
an
exception
like,
for
example,
if
you
call
the
people
who
make
merged
decisions
maintainers
instead
of
committers,
you
know
things
like
that
are
fine.
This
is
basically
meant
to
be
for
projects
which
need
help,
establishing
their
open
governance
or
to
be
able
to
tell
how
far
apart
a
project's
governance
is
from
the
accepted
governance
of
the
chips
alliance
that
that's
really
the
goal
of
this
document.
A
There
shouldn't
really
be
any
surprises
in
here.
One
thing
I
do
want
to
call
your
attention
to,
though,
is
again
things
to
do
prior
to
contributing
contributions
to
chips.
Alliance
projects
do
have
to
adhere
to
the
ip
policy.
A
The
document
itself
is
fairly
straightforward.
It's
based
upon
the
apache,
fairly
common
apache
style,
clas
and
there's
more
information
here.
Basically,
when
you,
when
you
open
up
a
pull
request
against
a
repo
repository,
that's
being
managed
by
the
easy
cla
tool,
it
will
present
the
cla
for
you
and
then
you,
you
basically
assign
that
in
docusign.
A
The
last
thing
to
bring
up
here
is
code
of
conduct,
so
the
chips
alliance,
it
it's
as
part
of
lf
projects.
It
adopts
the
lf
project's
code
of
conduct
by
default.
There's
a
link
here
as
well
to
find
that
so
michael
and
henry
the
contributing
document.
Does
this
look
look
reasonable
to
you
and
are
you
comfortable
adopting
this.
A
Okay
again,
yes,
all
right
great.
Thank
you.
So
then
the
last
thing
that
I
have
for
today
or
sorry
second
to
the
last
thing,
is
discussing
additional
tsc
members.
A
A
Michael
has
been
very
heavily
involved
in
this
whole
process
and
provided
a
substantial
amount
of
of
guidance
and
feedback
on
this.
So
henry,
would
you
like
to
appoint
michael
as
a
temporary
tsc
member
until
we
get
get
some
projects
on
board
to
help
through
the
process?
Yes,
I
would
definitely
like
to
appoint
him.
Okay
sounds
good,
michael.
Does
that
work
for
you
absolutely
okay,
great,
so
just
again,
just
kind
of
putting
a
putting
a
scope
on
this.
A
This
is
meant
to
to
be
a
temporary
thing,
but
the
idea
is
basically
to
get
the
the
tsc
bootstrapped
so
that
we
have
a
a
sufficient
number
of
projects
on
board
who
can
provide
the
actual
voting
members
and
with
that
that
brings
us
basically
to
the
end
of
the
agenda,
except
for
reviewing
meeting
times
we
were
talking
prior
to
the
meeting.
We
will
probably
try
and
keep
this
particular
time
attempt
to
meet
monthly
fourth,
wednesday
of
the
month
at
11
a.m.
A
Eastern
time,
so
I
will
put
this
call
on
the
calendar
on
the
chips
alliance,
calendar
which
is
calendar.chipsallians.org,
and
anybody
who
would
like
a
standing
invite
to
the
meeting.
Just
let
me
know-
and
I
can
add
you
to
the
invitation-
and
I
think
that's
everything
that
we
needed
to
cover
for
today,
just
doing
a
quick
review
here.
We've
gone
through
the
various
tsc
meeting
procedures,
quorum
requirements
and
how
decision
making
is
expected
to
work.
A
A
You're
very
welcome
all
right,
great,
so
henry
I
think
we
could
probably
close
the
meeting
down
if
you'd
like
to
call
the
mainstream
class
yeah.
The
first
meeting
of
the
technical
steering
committee
is
adjourned.
Great.
Thank
you.