►
From YouTube: Project Quay Community Ask Me Anything AMA 2020 07 06
Description
Project Quay Community AMA Ask Me Anything
2020 07 06
OpenShift Commons Briefing
https://projectquay.io
A
All
right,
everybody
welcome
again
to
another
OpenShift
Commons
briefing
as
we
do
on
Mondays.
We
have
asked
me
anything
sessions
with
different
upstream
projects
or
community
leaders,
and
so
this
week
we
have
brought
together
the
team
from
project
Quay.
We're
gonna
get
a
little
bit
of
an
introduction
from
Daniel
Nestor
and
then
we'll
have
it
open
for
Q&A
and
Tom.
Mckay
is
going
to
lead
the
QA,
but
we
have
a
number
of
folks
here
on
the
call
from
the
engineering
teams
from
clay
and
Claire
which
are
now
part
of
project
clay.
A
So
please
queue
up
your
questions
in
the
chat
and
we
will
gather
them
if
you're
on
Facebook
live,
YouTube
live
or
in
the
twitch
stream
will
aggregate
them
and
bring
them
here
as
well,
so
ask
where
you
live
and
know
deep.
We
can
get
them
all
answered
so
with
that
Daniel
take
it
away,
give
us
a
little
intro
to
what
project
Quay
is
and
where
we're
at
today.
B
B
If
you
haven't
heard
that
way,
gizzard
organ
a
we
cap
off
the
history
of
Quay,
which
is
pretty
interesting.
It
was
actually
the
first
private
registry
on
the
internet.
So
it
had
the
ability
to
store
private
or
offer
private
container
repositories
even
before
the
docker
registry
and
container
index
at
the
time
had
and
I
was
basically
launched
as
a
service
as
a
SAS
service
with
cradle
io
and
a
non-prime
version
of
Krannert
price
by
company
called
def
table,
which
was
eventually
acquired
by
Korres,
which,
as
you
all
know,
but
incorporated
into
Red
Hat.
B
B
Impressive
tracker
brag
record
already.
Since
then,
the
mission
of
the
project
is
quite
straightforward:
quais
allow
begin
allowing
you
to
build,
store
to
cure
and
distribute
your
applications
in
form
of
containers,
the
lively
pet
scale-
and
there
are
two
important
things
here,
which
is
secure
in
security,
as
well
as
a
liability
at
scale,
and
these
aspects
come
from.
The
fact
that
Quay
is
an
open
source
technology
runs
the
Quay
door
I
all
offering.
In
fact,
all
the
code
base
is
shared
between
the
on
cran
product
and
the
Quetta.
By
offering.
D
B
All
the
new
features
go
into
Cueto
die
out
first
right,
so
we
basically
test
at
the
scale
of
crater
die
over
tens
of
thousands
of
users
and
hundreds
of
thousands
of
API
requests
each
day
before
we
actually
release
this
into
into
a
product,
but
it's
all
coming
from
the
github
open
source
project
and
that's
where
the
community
now
lives.
So
it's.
B
B
We
have
basically
video
and
mostly
I
reference
implementation
with
clay.
We
are
on
giving
people
using
way
early
access
to
futures
type,
ocmi
types
as
well
as
also
fire
artifacts
back
and
maintain
us
to
declare
project
are
actually
part
of
that
community
body.
Right.
If
you
were
to
sum
up
the
strength
of
clay
as
a
project,
is
it's
really
about
providing
secure
access
to
container
images
which
drive
containerized
application
architectures
or
contain
orchestration
platforms?
B
It
does
that
with
performance
and
scalability
in
mind,
quais
again
one
of
the
largest
public
registries
available
next
to
talk,
Arad
and
it
focuses
a
lot
of
automations-
was
perfectly
available
and
to
integrate
NCI
CD
system.
I
said
that
Quay
itself
was
just
open
source
more
or
less
little
bit
over
half
a
year
ago,
but
already
since
then,
we
have
seen
quite
upstream
of
adoption.
B
So
Quay
is
very
active
from
github,
and
so
it's
clear,
which
is
actually
the
project
that
implements
security,
vulnerability
scanning,
so
Claire
is
open
source
and
a
little
bit
longer
than
Quay
and
is
also
used
outside
of
Quay.
But
all
the
clamoring
cameras
are
actually
under
the
project
and
also
on
this
call.
Today's
I
have
any
questions
for
Claire.
Please
do.
D
B
B
Its
way
into
the
official
repository
this
gives
you
tight
integration
for
work
flows
between
openshift
and
quaint,
so
that
things
like
namespaces
and
apposite
or
ease
or
service
console
once
the
remote
tokens
or
captain
soon
that
you
automatically
have
permissions
to
push
and
pull
to
your
little
car
of
the
world
and
wave
from
openshift,
and
you
can
also
use
image,
strings
and
open
shoot,
builds
and
conductor
earthquake
and
get
the
familiar
user
experience
that
you
had
with
the
internal
registries.
We
also
had
a
couple
of
smaller
improvements
across
the
board.
B
Things
like
I
look
for
during
help
users
with
that
kind
of
authentication,
back-end
to
be
more
precise,
but
which
users
they
want
to
see
and
where
we
have
some
features
that
actually
triggered
down
from
Cueto.
Do
like
a
forwarding,
larger
volumes
of
logging
data
to
elastic
search,
and
we
always
introducing
some
experimental
features.
One
of
them
is
helm.
We
free
chart
support
which
is
based
on
the
OCIO
artifacts
back.
B
All
read
head
up
projects
have
there
will
be
a
really
looking
for
feedback
like
these
kind
of
a
maze
sessions
from
you
in
order
to
and
get
ideas
on
what
we
can
improve
where
we
can
head
in
terms
of
integrations
and
features
throughout
the
product
and
then
start
making
those
available
on
crater
they
all
in
a
canary
fashion
and
then
make
them
available
to
the
paying
customers
with
privatised
a
version
of
quay
going
forward.
We
pursue
Queen
main
focus
areas.
B
One
is
that
we
want
to
get
closer
to
the
platform
we
are
running
on
and
the
platform
we
are
most
likely
to
be
used
with
a
lot
which
is
Oakley,
the
upstream
or
OCP
downstream.
So
there's
a
lot
of
potential
for
very
close
integration
in
the
developer
workflow,
as
well
as
administrative
workflow,
to
know
about
events
regarding
contain
images
that
happen
in
quays
for
those
to
be
able
to
trickle
down
into
open
chat.
B
This
is
the
more
detailed
road
map
I'm
not
going
to
talk
to
every
point
here,
but
one
thing
that
we
are
currently
working
on
quite
intensely.
It
is
actually
updating
the
quake
code
base
to
be
vital,
be
free
compatible.
So
that's
gonna
take
up
most
of
the
bandwidth
on
the
quaking
for
the
upcoming
pathologies
towards
the
end
of
the
year
and
at
the
same
time,
we
are
also
redesigning
the
qwave
operator
with
the
mangoes
that
it
can
actually
manage
clay
and,
despite
updates-
and
it
can
also
provide
required
databases
in
a
useful
fashion
to
acquire.
B
We
are
also
looking
to
add
builder
support
for
OCP.
This
is
just
you
know
closely
missed
on
the
last
work
window.
Button
that's
going
to
be
in
free
for
clearly
for
has
two,
because
one
is
notifications
and
we're
just
going
to
be
we've
written
from
scratch,
as
well
as
part
of
clear
before
being
a
completely
new
code
base
and
also
having
the
ability
to
get
window
ability,
data
from
different
sources,
which
is
primarily
driving
the
agate
deployment
case.
They
should
want
to
run
clear
and
disconnect
environment
with
no
network
access.
B
A
B
Sure
so
the
crane
operator
and
operating
a
half
that
I
own
a
speedy,
the
operator
that
maintains
quite
itself
right.
So
that's
the
operator
that
basically
gives
you
the
way
deployment
has
a
service
and
we've
just
called
it
quite
operator
these
days.
Even
though
we
used
to
call
it
a
setup
operator,
but
it's
really
the
component
that
is
responsible
for
the
lifecycle
of
Quay
on
the
kubernetes
cluster
right,
the
quake
bridge
operator
was
specifically
created
to
integrate
and
running
quayne
instance
with
openshift
clusters.
B
Home
shift
also
comes
with
a
ninja
granted
registry
and
has
done,
and
has
some
extensions
that
are
only
available
with
the
integrated
registry
by
default,
and
the
bridge
operator
opens
this
up
to
be
used
with
Quay
as
well.
So
the
most
predominant
features
here
are
support
for
image
streams,
as
well
as
automated
deployments
when
bills
and
Quay
have
produced
in
your
image
or
effect.
The
one
operator
you
used
to
install
claimed
the
anima
is
to
integrate
it
before.
A
B
C
So
yeah
there
is
a
time.
Okay,
there
is
a
JIRA
issue
where
we
track
our
issues
upstream
and
downstream.
For
that
feature,
it
is
not
on
our
list
of
things
to
do
in
the
coming
months,
but
it
has
been
asked
by
number
of
people,
so
it
has
not
gone
unnoticed,
but
I
wouldn't
expect
it
in
thoroughly,
not
the
3.3,
which
is
an
z
stream
right
now
and
probably
not
the
next
release
3.4,
which
we
are
actively
working
on
early.
A
And
will
lead
is
asking:
would
it
be
possible
to
abstract
the
mirror
pass-through
for
developers
on
Prem
that
is
developer,
asked
for
an
image
in
pod,
manifest
openshift
Kubik
pennies,
we'll
pass
it
to
Quay
on
Prem,
if
not
there,
it
pulls
out
of
the
internet
from
Quay,
dot,
IO
or
any
other
container
registries
and
I'm
going
to
unmute.
Will
that
well
lead?
So
he
can
follow
up
on
this
too.
But
it's
there,
a
quick
answer
to
that.
B
A
E
C
A
A
So
a
lead
had
an
earlier
question
at
the
very
beginning
of
the
whole
conversation,
he
queued
up,
one
on
restricted,
Network,
air-gapped
environments
and
support
updates
to
vulnerability
scanners
databases
via
periodic
updates,
allowing
other
standards
other
than
declare.
That's
like
a
bunch
of
questions
mashed
into
one,
but
you
want
to
tease
that
out
there,
tom
and
figure
out,
I.
E
Can
answer
that
the
vulnerability
updates
for
air-gap
are
planned
for
Claire
before
Claire
v4
is
targeted
for
October
to
come
into
GA.
As
part
of
that,
it
is
being
designed
explicitly
for
the
idea
that
you
would
be
able
to
load
in
the
updates,
as
opposed
to
today,
where
it
expected
that
Claire
and
download
those
update
as
four
different
security
scanners.
E
Nothing
in
quei
is
clear,
specific
any
security
scanner
that
speaks
the
current
or
upcoming
they're
different
version
of
the
Quai
security
scanner,
api
of
which
today
it's
claire
v2
for
the
current
one
and
Claire
before
the
upcoming.
Can
you
use
with
quai
without
any
additional
configuration
on
the
quayside?
You
just
pointed
to
the
security
scanner.
There
just
has
not
been
any
community
agreement
yet
on
what
a
registry
security
standard
api
should
look
like.
E
So
every
registry
today
has
a
different
API,
but
there
has
been
some
work
done
by
various
external
security
scanner
providers
to
integrate
with
Claire's
API
we've.
In
fact,
one
provider
has
a
working
prototype
of
a
small
proxy
server
that
actually
will
let
way
talk
to
their
security
scanner.
I,
don't
recall
what
it's
called
at
the
moment,
though
so
I
don't
want
to
answer
incorrectly,
but
nothing
precludes
anyone
from
using
a
difference.
If
you
scanner
with
quai
today,.
B
B
E
Far
as
I
know,
there
was
one
security
scanner
that
had
a
shim
prototype,
but
I
don't
know
off
the
top
of
my
head.
What
it's
called
none
of
the
other
ones
do
today
nothing
for
clues
them
from
doing
so.
It's
just
no
one
has
gotten
around
to
doing
it.
It's
also
not
complicated
at
all.
The
party
scanner
API
is
very,
very
simple
and.
A
C
C
We
do
have
an
email
list,
it's
a
Google
Group
Quay
sig
and
we
are
on
freenode,
IRC
I,
know,
there's
a
lot
of
chat
tools
out
there
slack
and
discord,
and
but
with
all
them
IRC
seems
the
one
that
lives
the
longest
and
then
again,
as
mentioned,
we
do
have
the
github
organization,
so
the
majority
of
our
repos
are
under
that
equate.
Org.
C
There
is
one
the
Quai
operator,
which
is
the
quays
setup
operator,
that's
still
in
a
redhead
community
of
practice
repo,
but
that
will
be
moving
over
to
quite
as
well
so
feel
free
to
explore
there
and
the
repos
have
varying
policies
in
terms
of
issues.
So,
for
example,
declare
repo
declare
community
indicates
most
frequently
through
github
issues.
C
We
do
not
have
github
issues
enabled
on
most
of
our
Quay
specific
repos.
Instead,
we
use
issue
tracking
through
JIRA
I
link
there
as
well.
We
use
the
same
tracking
for
both
upstream
so
project
way
and
downstream
redhead
way,
and
so,
if
you
want
to
really
see
the
roadmap
and
what's
being
worked
on
actively,
it's
all
there
for
you
to
to
look
at
and
again
all
of
our
code,
that
is
for
Red
Hat
Quay,
as
well
as
quite
at
I/o,
Wells
project
way
all
is
being
and
is
successful
on
the
various
branches.
C
C
If
anyone
is
familiar
to
I
thought,
but
where
the
the
benefit
that
we
do
have
an
extensive,
both
internal
read:
heck
QE
team
as
extensive
unit
tests
and
Gration
tests,
so
the
largest
portion
of
the
conversion
is
really
checking
the
updated
package
versions
where
in
Python
2
would
not
be
using
an
older
version
of
an
integration
package.
We've
updated.
C
That,
though,
and
as
you
can
see,
there's
a
lot
of
integration
points
so
LDAP
all
the
storage
engines,
all
sorts
of
flavors
of
things,
there's
a
lot
to
be
tested
and
reviewed,
and
we'll
put
this
in
the
top
of
the
readme
information
about
our
bug
here
and
the
rewards
for
our
community's
hard
work
and
helping
us
with
this.
But
we
hope
to
see
you
on
IRC
and
on
the
email
list
and
fixing
and
raising
issues.
A
The
significant
effort
to
do
this
so
any
and
all
help
much
appreciate
and
we'll
socialize
this
a
little
bit
too
as
well
and
I,
think
bill.
Dida
Buck
has
got
a
t-shirt
design
up
his
sleeve
as
a
reward.
So
hopefully
we
can
showcase
that
too
sometime
soon
and
attempt
you
all
to
use
your
Python
skills
and
help
us
out
here,
because
that's
really
where
the
community
is
at
the
other
piece
of
information.
A
If
you
don't
know
as
well,
we've
got
an
effort
on
to
bring
project
Kwai
to
the
CN
CF
and
have
made
a
pull
request
and
are
working
our
way
through
the
CN
cloud
native
computing
foundations
review
process
for
bringing
a
project
into
incubation.
So
that's
that's
been
in
the
works
for
a
while,
and
it's
wandering
its
way
through
some
sig
reviews,
but
I'll
put
in
the
chat
the
link
to
the
pull
request.
A
If
you're
interested
in
following
through
commenting
on
that,
please
let
us
know-
or
just
do
so
and
we'd
be
happy
to
have
your
support
and
also
your
feedback
on
that
process
as
well.
So
that's
that
that's
where
we're
at
with
the
CN
CF.
At
the
moment,
and
hopefully,
you'll
see
us
on
that
beautifully
complex
CN,
CF,
landscape,
dot,
io
diagram
sometime
in
the
not-too-distant
future
battle.
That'll
also
help
raise
visibility
for
for
this
project
and
also
give
us
another
lots
more
options
and.
C
D
So
I
mean
Claire
before
is
a
reimagining
of
Claire
be
to
use
original
architecture.
There
are
some
issues
with
the
original
architecture
which
we
addressed,
most
of
them
evolving
around
performance,
and
there
was
also
some
data
model
issues
which
didn't
allow
us
to
really
connect
the
dots
between
certain
package
types
like
binary
and
source.
All
this
is
now
built
into
the
data
model
and
in
the
performance
side,
we
really
looked
at
basically
how
claire
v2
was
pulling
down
images.
How
I
was
analyzing
them
did
most
of
the
work
in
memory.
D
We
moved
that
to
actually
be
buffered
on
disk,
which
will
actually
want
to
be
more
performant,
because
some
of
these
layers
can
get
rather
large.
You
don't
want
to
do
all
that
work
in
memory
and
then
we
basically
RER
connected
the
actual
library
which
does
most
work
into
a
repository
called
Claire
core.
D
That
was
for
an
effort
to
remodel
and
also
to
kind
of
promote,
easier
integration,
easier
contribution
from
the
community.
You
can
actually
take
a
look
at
that
in
Clare
core.
We
have
had
some
outside
contributions.
Everything
is
well
documented
now,
and
it
should
be
a
little
bit
easier
to
just
jump
in
and
add
things
to
the
codebase.
It's
a
little
bit
more
difficult
in
Clearview
to,
and
you
know,
there's
a
couple
other
things:
Claire
b2
didn't
really
consider
content-addressable
layers
and
artifacts
content.
D
D
That's
the
first
class
citizen
that
got
brought
into
the
you
know:
docker
specifications
after
image
IDs.
So
it's
not
like
claire
v2
ignored
that
it
just
wasn't
a
thing
at
that
point.
So
we
kind
of
worked
that
into
the
solution.
Yeah,
there's,
there's
quite
a
bit
that
has
changed
mostly
from
taking
a
look
at
clear
v2.
You
know
when
claire
v2
was
developed,
it
was
developed
at
the
onset
of
a
lot
of
those
technologies,
so
they
benefit
us.
A
lot
can.
C
D
D
Air-Gap
and
notification
and
I
hope
that
once
we
get
through
those,
then
we
will
be
able
to
attack
more
of
the
language
package.
Scanning
is
actually
one
of
the
things
I'm
more
excited
about.
I
think
it
can
add
a
lot
to
the
solution,
so
I
want
to
you
know
as
soon
as
possible,
whether
it
comes
from
contribution
or
not.
I
think
that
it
should
be
like,
like
a
major
point
on
our
radar.
C
A
C
Don't
think
he's
long?
Okay,
so
Alec
is
our
lead
engineer.
On
the
quite
operator,
the
current
version
of
the
Quay
setup
operator
was
written
in
conjunction
with
Red
Hat,
consulting
and
customer,
and
they
graciously
allowed
it
to
be
open
source
work
and
that's
what's
ship
now,
with
with
3.3
with
Red
Hat
Quay
3.3,
there
is
work
in
re
architecting
that
to
be
more
operator
like
and
that
repo
again
exists
up
on
our
github.
There's
some
back-end
tooling
we're
using
called
customize.
It's
very
kubernetes
friendly.
C
There's
a
lot
of
work
going
on
there,
one
to
make
sure
the
transition
from
the
existing
operator
to
the
new
next
generation
operator
goes
smoothly,
but
also
to
ensure
that
we
capture
all
the
user
personas
that
we
envision,
and
this
really
is
focused
on
the
day
to
operations
as
well.
So
the
current
operator
really
installs
but
doesn't
further
manage,
but
we're
looking
to
raise
the
maturity
level
of
the
operator
to
include
things
like
upgrades
and
day
to
operations.
B
Yeah
so
like
Tom
mentioned
today,
the
operator
actually
deploys
Kuwait
and
it
can
actually
also
deploy
all
the
immediate
dependencies
of
Quay,
which
is
an
ax
memory,
cache
based
on
reddit's,
as
well
as
a
signal
database
that
is
either
basic
or
Postgres.
So
we
do
Plotkin
stress
today
with
with
your
operator,
so
we
want
to
make
that
a
little
bit
more.
B
Let's
say
opinionated,
though
it
becomes,
on
the
one
hand,
less
customizable,
but
also
more
maintainable
for
us,
so
the
more
options
we
give
people
in
order
to
obviously
change
the
way
way
is
to
directly
the
operator.
The
more
competitive
operator
code
obviously
gets
right
and
complexity
is
the
enemy
of
all
of
all
updates
right.
B
The
way
you
can
actually
deploy
the
database
will
create
to
something
that
is
easier
to
incorporate
by
the
body
operator
so
and
that's
all
in
order
to
help
the
operator
to
be
able
to
manage
update
lifecycle
so
that
when
you
have
quavery
for
installed
and
say,
if
we
file
this
release,
you
can
actually
use
the
operator
to
just
change
a
little
version,
spec
and
the
custom
resource.
And
then
the
crane
operator
will
notice
that
and
will
actually
take
/
reconciling
yoga,
B's
and
updating
it
in
the
way
we
are
doing.
B
E
A
Thanks,
another
question
came
in
and
asking
if
you
could
elaborate
more
on
the
repo
organization
team
level
structure,
can
it
be
more
flexible,
more
levels
he's
a
new
user
and
he
finds
it
limiting.
For
example,
how
should
I
provide
to
my
end-users?
The
images
from
upstream
Quay
tile
chorus,
such
as
Claire
and
clay
yeah.
C
C
C
E
Little
further,
the
reason
we
don't
support
it
at
this
time
is
because
it's
not
supported
in
the
darker
v1
protocol
and
as
part
of
our
commitment
to
full
backwards
and
forwards
compatibility.
We
can't
support
it.
If
and
when
we
formally
deprecated
version
1
of
the
protocol,
which
will
likely
happen
at
some
point
in
the
future,
because
its
usage
has
been
dropping,
then
we
can
investigate
adding
hierarchical
support,
but
we
will
likely
not
unless
something
changes.
We
will
likely
not
be
allowing
you
to
set
permissions
at
different
levels
of
the
hierarchy.
E
It
will
be
a
naming
convention,
as
for
which
is
what,
in
fact,
most
custom
implementations
that
do
have
quote-unquote
hierarchy
actually
do
in
terms
of
how
to
allow
customers
to
access
things
that
are
currently
current
promoted
solution,
as
you
create
a
robot
account
per
customer,
or
if
you
don't
have
a
problem
sharing
the
robot
excuse-me
credentials,
you
get
one
robot
account
to
all
your
customers,
and
you
just
give
permissions
to
that.
Robot
account
in
the
particular
set
of
repositories
that
the
customer
will
have
access
to.
E
A
A
B
F
Yeah
yeah,
so
I'm
buildable,
back
I'm,
the
engineering
manager
for
Quay
and
yeah,
just
I
think
that's
one
of
things.
We
didn't
talk
about
too
much,
but
I
think
it's
a
it's
a
feature
that
we've
got
slated
for
the
next
me
minor
release
for
three
for
a
lot
of
folks
who
use
Quay
on
premise:
don't
realize
that
there's
actually
a
facility
for
builds
if
you
use
Quay
dot,
IO
you're,
probably
very
familiar
with
it.
We
don't
have
too
much
uptake
folks
running
Quay
and
house
with
the
builders.
F
F
Actually,
the
the
builders
are
the
first
thing
we
moved
over
to
kubernetes
when
we
started
to
retarget
quit
I
over
to
openshift.
We've
been
running
the
builders
now
on
on
open
shift
for
about
eight
months
or
so,
and
so
we
decided
that
it
was
time
to
to
productize
that
bring
that
back
into
the
product.
So,
with
with
the
next
major
release,
you'll
be
able
to
run
the
builders
now
pretty
easily
on
top
of
a
kubernetes
Orchestrator,
we've
done
some
internal
changes
in
conjunction
with
the
Python
3
migration
as
well.
F
We've
taken
the
opportunity
to
obviously
update
the
build
manager
code,
the
quake
container
to
Python
3,
and
while
we've
got
the
hood
up
on
the
car,
where
we're
swapping
out
some
stuff
like
an
old
RPC
framework
that
we
used
before
4G
RPC
and
we're
trying
to
simplify
the
code
as
much
as
possible,
we're
also
bumping
up
the
version
of
the
VM
that
we
use
or
the
actual
builds
inside
the
pods
to
a
more
supported
version.
It
was
on
container
Linux
we're
moving
that
over
to
Fedora
core
OS
I
believe
so
anyway.
F
I
thought
it
would
be
worth
to
just
call
that
out
as
a
new
feature,
I
think
with
the
introduction
of
builders
on
OCP
and
kubernetes.
It
should
be
very
simple
to
stand
those
up
as
a
new
build
facility
for
on-prem
customers
so
and
if
there's
detailed
questions
on
I
see
Kenny's
on
Kenny's
actually
doing
the
work,
so
I
will
defer
the
hard
questions
to
him.
A
A
D
You
want
some
just
something
to
hold
you
over.
There
is
a
repository
I'll
put
the
link
in
the
chat
too,
but
we
have
worked
on
basically
formal
documentation
in
the
Claire
core
repository,
it's
a
little
bit
more
of
like
a
upstream
resource,
but
it
does
carry
a
lot
of
weight
as
far
as
explaining
how
everything
works
so
I'll
put
that
into
the
chat
all.
D
I
mean
one
of
the
big
things
that
come
to
mind
like
we
had
some
great
contributions
from
with
VMware
who
added
their
own
OS
support.
Language
support
would
be
great,
I
think
that
any
contributions,
even
knowledge,
share
contributions
around
security
protocols
around
how
organizations
kind
of
package
their
applications
internally
is
all
really
great
stuff
that
we
can
benefit
from
but
yeah
as
far
as
like
code
contributions.
D
A
I
think
that
when,
when
the
transition
hopefully
takes
place
over
to
the
CN,
CF
will
probably
get
that
done
and
then
there's
the
Clare
core
link.
Thank
you,
but
I
think
that
we
we
do
have
that
Stig
page
for
project
quay
and
if
you
want
to
share
that
again,
come
and
that
that
would
be
great
and
we'll
come
ad
declare
a
little
bit
here
to
that
as
well.
A
A
D
B
Interesting
discussion
because
we're
actually
involved
in
some
of
the
community
work
that
is
revolving
around
making
that
available
in
the
Quai
project
as
well.
I
know
that
Joey
is
working
actively
on
this
upstream,
with
the
community
around
Halloween
and
maybe
Joey.
You
can
give
a
quick
update
on
where
this
is
party,
yet.
E
However,
over
the
last
few
years,
there's
been
a
lot
of
community
discussion
about
the
pitfalls
and
problems
associated
with
doctor
notary
and
to
that
end
the
community
is
currently
working
on
a
new
version
of
notary
called,
never
easy.
It's
a
working
group
there's
actually
a
community
meeting
in
I
think
eight
minutes
that
meets
weekly,
so
anyone
who's
interested
feel
free
to
go
search
out
the
notary,
v-2
working
group
and
take
a
look,
but
the
high-level
description
is
basically
because
of
this
recognition
that
there's
needs
to
be
something
better.
E
The
community
is
working
on
something
new,
and
so,
as
a
result,
we
are
part
of
that
working
group
and
as
soon
as
the
working
group
comes
up
with
a
you
know,
proposal
and
an
implementation
for
that
proposal.
Then
we
will
be
working
to
adopt
that,
but
as
of
this
moment
in
time,
it's
still
very
much
in
the
development
phase,
and
so
given
that
and
the
lack
of
the
universal
adoption
of
the
original
doctor
notary,
we're
taking
the
approach
of
let's
contribute
to
the
new
version
as
opposed
to
adopting
a
flawed
old
version.
E
So
that's
the
high-level
description.
It
means,
unfortunately,
that
we're
gonna
have
to
wait
a
little
bit
longer
to
get
a
really
good
solution
in
place.
But
since
the
whole
community
has
finally
recognized
that
this
is
something
we
should
do,
I'm
pretty
confident
and
excited
about
the
direction
that
everyone's
going.
C
Yeah,
so
let
me
just
touch
on
the
ways
to
contact
us
again
as
you've
seen
we're
new
to
being
open
source
and
part
of
that
growth.
Pattern
is
figuring
out
the
best
way
to
collaborate
with
our
community
and
right
now,
claire
has
a
community.
As
I
said,
it
does
a
lot
of
its
discussions
through
the
github
issues.
C
We
are
hoping
that
over
time
we
can
sort
of
consolidate
the
communities
with
Quay
and
Claire.
So
you
know,
Claire
questions
are
completely
fine
and
the
operator
questions
or
completely
fine
on
the
quay
sig.
The
issue
tracking
the
giro
that
we
use
is
for
both
projects,
both
Quay
Claire,
as
well
as
all
the
operators.
C
The
work
gets
done,
even
if
there's
an
issue
upstream
that'll
often
be
created
recreated
as
a
JIRA
and
yeah.
So
there
is
a
Claire
channel
on
freenode
as
well.
Both
declare
and
Kwai
channels
on
IRC
are
very
lightly
populated.
I
would
encourage
you
to
use
the
quite
one,
which
is
why
I
listed
it
as
the
only
one
just
to
sort
of
get
everyone
in
the
same
room
so
to
speak.
B
Think
I
get
the
direction
there
so
and
the
answer
is
no.
We
are
pursuing
a
different
standard
for
getting
enhanced
contacts
coverage,
and
so
we
are
basically
looking
at
our
oval
with
two
feet
since
we're
a
CD
RF
data
to
get
a
more
comprehensive
coverage
on
specifically
now
what
is
distractin
will
abilities
for
red
head
rpms
and
that's
beyond
the
Red
Hat
server
rpm
repository.