►
From YouTube: OKD Community Development Meeting 01-10-2023
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
https://okd.io
A
B
Folks,
welcome
to
the
okd
Community
Development
meeting
for
January
10th
of
2023..
It's
our
first
meeting
of
the
new
year,
Happy
New
Year
to
everybody,
and
let's
take
a
look
at
the
agenda,
real
quick.
Let
me
know
if
there's
anything
that's
been
missed.
B
If
you
wanted
to
add
it
or
remove
it
or
move
things
around,
let's
take
about
30
seconds
to
look
at
that
see.
If
there's
anything
that
needs
to
be
changed.
B
Okay,
all
right,
we
good
anything
needed
to
be
added
or
removed
around
or
anything.
B
All
right:
well,
then,
let's
jump
right
to
it.
Sno
documentation,
how's
that
going
did
anything
change
since
mid-December
our
last
meeting
or.
E
C
Okay,
so
I'm
back
now,
so
we
we
are
still
working
on
it.
Putting
it
together.
Trying
to
you
know,
make
it
clear
and
step
by
step
and
just
going
through
it
and
and
and
earning
and
earning
and
learning
you
know
the
way
through.
D
So
Joanne
and
I
are
working.
Sorry,
sorry,
Jamie,
we're
working
together.
We
we've
created
a
couple
of
sessions,
so
we've
broken,
we've
got
a
slide
deck
that
we've
we've
split
up
and
then
you
know
we'll
do
a
session
separately,
but
I
think
Dwayne
had
a
problem
with
his
with
these
recording
computer.
So
what
we'll
try
and
do
what
I
suggested
is?
D
We
can
do
together
on
a
g,
meet
call
or
maybe
a
zoom
session
and
just
work
through
the
document
and
give
examples
of
how
we
set
up
the
you
know
the
h8
proxy
or
the
the
actual
Apache
server
and
so
on
and
so
forth.
So
yeah
it's
a
work
in
progress,
but
we're
making
progress.
Excellent.
B
All
right
in
terms
of
the
tecton
I
did
work
on
it
a
little
bit
over
the
break.
There's
a
couple
of
tweaks
that
I
need
to
make
because
of
the
namespace
expectations
in
terms
of
the
installation
but
I'm
making
my
way
to
finishing
the
tecton
documentation
and
actually
I
started
I
signed
up
as
a
tecton
user
and
I've
looked
at
some
of
their
meetings
and
so
I'm
tempted
to
start
like
attending
a
couple
of
the
meetings
in
the
tecton
community,
just
to
sort
of
be
aware
of.
B
What's
going
on
and
and
maybe
leverage
some
some
knowledge
there
to
help
us
along
email
hosting.
So
we
do
have
an
update
as
of
just
like
two
hours
ago,
they
finally
found
someone
who
can
modify
the
DNS
records
to
point
to
the
appropriate
servers
for
email
aliases.
The
question
now
is:
where
do
we
want
these
aliases
to
go?
B
Those
are
the
aliases
and
so
do
we
do
we
set
up
multiple
accounts
somewhere
or
do
we
have
these
all
go
to
One
account
and
just
look,
and
just
you
know,
filter
by
Alias
to
different
folders?
How
would
folks
like
to
proceed
with
this?
B
B
Be
easy
to
change
in
the
future.
It
was
the
hard
part
was
getting
the
DNS
to
point
to
the
to
the
to
the
postfix
servers
that
that
osbo
are
using.
F
If
there's
anything
there
I
think
everything
going
into
one
is
going
to
be
much
easier
and
then,
if
we
find
that
a
different
group
of
people
need
to
do
a
different
one
say
something
that's
a
bit
more
sensitive,
then
we
may
want
to
put
that
into
a
separate
one
and
have
a
smaller
group
might
be
able
to
do
that.
That's
my
thought
anyway.
B
Yeah,
what
do
other
people
think
I
see
some
heads
nodding,
yeah?
Okay,
that
seems
to
be
the
consensus
there.
Okay,
do
we
want
to
use
that
same
Gmail
account,
that's
used
for
like
the
Twitter
and
everything
like
that,
since
the
credentials
are
shared
out
amongst
like
three
or
four
of
us.
Does
that
make
sense,
I
think
the
chairs
have
it
at
this
point
Brian.
What
do
you
think
I
think
you've
got
the
credentials
to
that
one
as
well
right.
F
D
D
Wanted
me
to
send
out
the
tweet
that
we
created
a
new
okd
release
and
so
which
was
it's
about
literally
a
month
late,
but
nonetheless
we've
we've
done
it.
So,
oh.
B
B
D
B
It's
and
then,
after
that,
I
posted
the
video
to
the
Community
Development
meeting
from
November
29th
right,
yeah.
Okay,
all
right
well
having
multiple
tweets
on
it
is
fine,
not
an
issue.
Okay,
so
we
will
we're
in
agreement
that
we'll
have
the
addresses
aliased
to
that
Gmail
account
for
now
and
then
eventually
break
things
off
as
we
get
more
volunteers
and
we
see
the
need
for
redirecting
is
that
is
that
the
feeling
in
the
room?
B
Okay,
see
lots
of
heads
nodding,
sounds
good.
Okay
up
next
is
social
media.
So,
since
we
last
spoke
everyone's
going
to
Mastodon,
it
seems
so.
What
do
you
have
for
a
certain?
You
were
going
to
gather
some
resources,
so
Omega.
A
C
A
Let's
see
if
I
can
pick
the
right
one
okay,
I
was
gonna,
do
a
slide
deck,
but
then,
when
I
was
putting
it
together,
I
was
like
you
know
what
a
document
might
be
easier
for
us
to
kind
of
share
and
process
and
whatnot,
so
I
guess
maybe
start
with
a
showa
hands
or
like
how
many
people
here
are
familiar
with
Mastodon
already
like
how
deep
should
I
go
on
there
so
I
know
so.
Jamie
is
like
I.
A
Good
point
good
point:
so:
okay
yeah,
so
the
top
of
this
I,
just
you
know,
put
a
little
put
a
little
boilerplate
on
the
front
here,
just
letting
everyone
know
that
you
know
really
the
point
of
this
documentation
that
I've
created
is
to
to
share
with
the
okd
community
a
high
level
perspective
of
what
Mastodon
is
in
comparison
to
Twitter
and
kind
of
some
of
the
reasons
for
for
what
we
might
want
to
think
about
for
why
we
might
want
to
use
it
or
not
use
it.
A
It's
not
meant
to
be
exhaustive
about
you
know
what
is
Mastodon
shirt,
there's
tons
more
information
you
can
get
into,
but
this
is
just
a
high
level
kind
of
approach.
So
the
first
thing
I
did
what
is
Mastodon
and
I
just
copied
this
from
Wikipedia,
because
I
thought
it
was
pretty
good.
A
So
Mastodon
is
free
and
open
source
software
for
running
self-hosted,
social
networking,
Services
right
it
has
micro
blogging
features
similar
to
Twitter
and
the
way
it
works
is
it's
run
by
independent
nodes
that
they
call
instances
and
I
will
use
that
language
throughout
this
documentation
each
instance
is
separate
from
the
other
ones
that
might
have
their
own
codes
of
conduct
terms
of
service
Etc.
A
So
you
know
how
is
Mastodon
different
than
Twitter
the
biggest
thing,
and
this
is
alluded
to
in
the
description
there
is
it's
decentralized
as
opposed
to
centralized,
and,
and
what
does
this
mean
well
in
you
know,
Twitter
is
a
centralized
service,
which
means
that
all
the
messages
go
to
one
point,
and
then
you
know
the
Hub
distributes
out
to
the
to
the
spokes.
Essentially
in
Mastodon,
all
instances
are
separate
from
each
other
and
they
use
a
world
wide
web.
You
know
W3
standard,
called
activity
Pub
to
share
information
between
them,
an
activity.
A
Pub
is
you
know
it's
it's
essentially
a
structured
schema
for
sharing
data,
and
it
you
know
it.
One
use
of
activity.
Pub
is
to
make
something
sort
of
like
Twitter.
You
know
where
you
could
share
little
Snippets
of
text
and
you
can
have
addresses
you
can
send
it
to
and
hashtags
and
those
kind
of
things,
but
there
are
other
uses
of
activity
Pub
as
well.
You
might
have
in
addition
to
Mastodon
there
are
other
services
like
pixel
fed,
is
something
that's
very
similar
to
Instagram.
A
It's
a
way
to
use
activity
Pub,
to
share
kind
of
like
image,
updates
and
and
do
those
kind
of
things
there's
also
a
service
called
peer2
tube,
which
is
very
similar
to
YouTube
but
built
in
a
decentralized
fashion.
So
activity
Pub
is
not
only
for
doing
Mastodon,
but
Mastodon
is
one
use
of
activity
Pub
and
in
in
the
community
in
the
kind
of
The
Wider
activity,
Pub
Community,
this
whole
kind
of
sharing
of
all
these
things
is
referred
to
as
the
fetiverse.
A
So
if
you
use
Mastodon
or
if
you
use
pure
tube
or
any
of
these
other
services,
you
might
see
people
referring
to
the
fetiverse
and
that's
usually
what
they're,
referring
to
as
the
kind
of
the
loose
network
of
of
instances
that
pass
along
activity.
Pub
information
to
each
other
I
think
it's
important
to
note
for
us
that
each
instance
may
have
different
rules
about
content
creation
and
moderation
as
well
as
each
instance
will
have
their
own
unique,
allow
and
block
lists.
A
This
is
kind
of
a
big
deal
on
Mastodon
and
I'll
get
into
that
in
the
next
topic.
A
little
bit.
Another
thing
to
keep
in
mind
here
as
well
is
that
in
Twitter,
because
everything
is
centralized,
Twitter
uses
algorithmic,
you
know
I,
guess,
processing
to
create
curated
lists
of
things
that
users
will
see,
and
so
you
know
the
action
of
of
liking
things
or
or
doing
retweets
those
actually
feed
into
some
sort
of
machine
learning
algorithm
that
helps
Twitter
to
understand
how
to
display
these
things
in
the
Mastodon
Network.
A
This
this
concept
doesn't
quite
exist.
There
is
not
a
you
know.
There
is
not
some
sort
of
central
processing
algorithm
running
that
catalogs
and
indexes
everything
and
create
search
routines.
So
content
is
boosted
to
gain
visibility,
there's
no
inherent
algorithm
for
curating
that
stuff.
A
Another
big
point
is
the
focus
on
privacy,
so
the
Mastodon
community
and
really
the
larger
activity.
Pub
Community.
You
know
some
of
their
founding
principles
and
some
of
their
cores
have
to
do
with
user
privacy
and
user
safety.
You
know
Community
privacy,
Community
safety,
those
kind
of
things
and
as
such
Mastodon
provides
many
more
tools
for
users
to
ensure
that
their
content
is
protected
and
their
identity
is
protected
and
the
way
that
you
would
most
frequently
run
into
this
is
through
things
like
allow
lists
and
block
lists.
A
A
In
other
instances,
you
may
see
just
individual
blocking
of
users
who
are
known
to
you
know
to
be
bad
actors
or
whatever,
but
this
also
extends
to
the
notion
of
some
users
also
set
up
content.
A
You
know
privileges
where
you
would
have
to
ask
them
before
you
could
get
their
content.
You
might
have
to
ask
them
before
you
could
follow
them.
So
there's
a
whole
range
of
of
kind
of
content,
protection
measures
that
I
think
exist
on
Mastodon.
That
may
have
some
equivalency
on
Twitter,
but
it's
much
stronger
on
Mastodon.
So
this
is
something
to
keep
in
mind.
A
Is
that
the
the
focus
on
privacy
is
a
is
a
one
of
the
big
points
of
this
network
and,
as
I
mentioned
earlier,
searching
and
sorting
so
Mastodon
does
have
some
search
capabilities,
but
those
are
mainly
around
the
use
of
hashtags
and
mentioned
usernames.
So
if
you
mention
a
username
in
a
in
your
content
in
a
two
as
they
call
it,
you
know
this
is
the
equivalent
of
a
tweet.
A
If
you
mention
another
username
that
will
get
indexed
by
search
engines
and
any
hashtags
you
put
will
get
indexed
by
search
engines
and
really
the
you
know,
the
hashtags
then
become
like
a
very
big
way
for
communities
to
organize
in
the
Mastodon.
You
know
fediverse,
basically,
so
like
use
of
hashtags
is
very
big,
especially
if
you're
trying
to
find
other
people
who
are
interested
in
your
topics.
A
So
I
think
you
know,
probably
the
biggest.
The
biggest
difference
is
culture.
You
know
there
are
many
technological
differences
that
you
know
could
be
enumerated,
but
I
think
it's
really
worth
highlighting
that
the
culture
of
the
community
on
Mastodon
is
very
different
than
that
of
Twitter.
A
You
know,
and
and
Twitter
in
general,
especially
at
this
point
has
become
you
know,
it's
very
common
place
to
use
Twitter
as
an
advertising
method
or
use
it
as
a
as
a
marketing
place.
You
know
the
community
on
Twitter
is
very
I.
Guess
is
very
they.
They
accede
to
commercial
content
quite
well.
You
know
it's
known
that
this
is
part
of
the
content
on
Mastodon.
A
By
contrast,
it's
got
a
much
more
Grassroots
feel
to
it
and
although
there
is
usually
pretty
good
community
support
for
people
who
are
like
kind
of
showing
off
the
work,
they're
doing
or
open
source
communities
that
are
trying
to
share
their
latest
changes
and
everything,
there's
a
different
Community
perception
about,
like
purely
commercial
marketing
Ventures.
A
You
know
these
are
much
less
popular
and
because
you
know
because
the
network
itself
has
to
be
boosted
by
users
who
use
it,
you
know
there's
really
not
a
place
for
advertisers
to
work
in
the
same
way
that
they
work
on
Twitter.
So
this
is,
you
know,
kind
of
like
another.
You
know
big
part
of
this
and
it
it
feeds
into
the
culture
of
what
happens
there.
A
So,
like
you
know,
if
you're
used
to
using
Twitter-
and
you
might
think
well,
if
I
like
somebody's
tweet,
you
know
the
algorithm
will
pick
up
those
likes
and
then
they'll
like
internally,
make
it
more
important
and
make
it
more
visible
and
the
Mastodon
side
of
things
you
know
just
liking.
Someone's
you
know,
content
is
more
akin
to
just
kind
of
letting
them
know
that
you've
seen
it
and
you
like
it.
A
It
doesn't
necessarily
do
anything
for
the
wider
network
of
people
viewing,
whereas
boosting,
on
the
other
hand,
is
very
big,
and
this
is
like
you
know,
considered
part
of
the
community.
So
you
know,
if
you
really
like
content
and
you
want
to
see
it
promoted,
you
should
really
boost
it
in
addition
to
liking
it,
because
that
helps
to
spread
the
content
through
the
network,
and
so
this
is
just
something
to
kind
of
internalize,
as
you
think
about
mastodon.
A
So
you
know
this
has
been
pretty
brief
so
far,
but
you
know,
hopefully
you
can
kind
of
see
the
shape
of
Mastodon
and
understand
you
know
kind
of
some
of
these
things
and
so
the
recommendations
that
I
have
after
looking
at
this
and
kind
of
looking
at
what's
been
going
on
there
you
know
I
think
we
should
keep
the
Twitter
account.
We
should
keep
using
the
Twitter
account
from
everything.
I
can
tell.
A
But
with
that
said,
I
think
for
the
future.
We
should
consider
creating
a
mastodon
account
and
having
it
replicate
our
Twitter
content,
because,
as
we're
seeing
there
is
a
migration
of
people
from
Twitter
to
Mastodon,
and
if
you
know,
if
there
were
disruptions
in
the
future
and
Twitter,
that
would
cause
even
more
people
to
leave
or
maybe
cause
the
technology
not
to
work
as
well.
I
think
we
would
be
best
served
to
have
a
backup
or
a
redundancy
that
we
could
use.
A
You
know
to
share
our
messaging
and
and
more
people
are
getting
used
to
Mastodon
as
a
way
to
see
these
things,
so
that
kind
of
brings
up
the
the
question
of
instance,
choice
and
I
just
put
a
couple
of
suggestions
here,
I
think.
If
we,
if
we
do
or
if
and
when
we
choose
to
make
a
mastodon
count,
we
should
probably
work
with
the
community
to
figure
out
the
best
place.
But
I
put
some
of
the
top
places
that
I
see
projects
going
and
people
going.
A
Fasterdon.Org
is
one
of
the
big
ones.
It's
obviously
focused
on
free
and
open
source
projects.
The
main
accounts
for
like
the
Fedora
project
and
Arch
Linux
broadcast
on
fostudon,
and
so
it's
a
community
kind
of
built
around
that
that
ethos,
so
I
think
that's
kind
of
a
natural
fit.
It's
also
a
relatively
larger
server.
Mastodon.Social
is
one
of
the
really
old
large
servers.
It's
very
large.
A
It's
kind
of
dedicated
to
General
socializing,
but
I
did
notice
that
there
are
some
news
channels
and
other
organizations
that
are
broadcasting
there,
just
because
I
think
it's
a
place
where
you're
hitting
a
lot
of
people.
So
that's
probably
another
good
choice
to
consider
and
then
lastly,
the
last
one
I
put
here
is
called
hackaderm,
it's
hackaderm.io
and
they
promote
that
they're
dedicated
to
curating
a
community
of
Technology
professionals
and
there's
a
lot
of
people
from
The,
Wider
kind
of
Open,
Source
and
kubernetes
communities
who
have
gone
there.
A
I
didn't
see
so
many
organizations
broadcasting
out
of
hackaderm,
but
it's
probably
something
that
we
should
consider.
And
then
you
know
this
join
Mastodon
server.
Instances
link
that
I
have
here
I
put
this
here
because
you
know
there
really.
There
are
a
lot
of.
There
are
a
lot
of
servers
and
many
different.
You
know
kind
of
I
guess
different
qualities.
Each
one
has
that
we
could
think
about.
A
So
that's
maybe
something
you
know
something
to
consider
as
we
get
closer
to
to
kind
of
making
a
decision
and
then
I
just
put
a
summary
at
the
bottom.
You
know
we
should
continue
posting
our
Twitter
account
I
think
within
the
next
12
months.
We
should
create
a
mirror
of
the
Twitter
account
on
one
of
the
Mastodon
instances
and
probably
set
up
some
automation
that
could
just
make
it
so
whoever
is
putting
stuff
on
Twitter.
It's
easy.
A
You
know
it
just
gets
replicated
directly
to
the
Mastodon
account
yeah
and
we
should
make
no
plan
to
deprecate
that
Twitter
account.
You
know
at
this
time
so
yeah
like
does
anybody?
Have
questions
or
comments
or
follow-ups.
B
A
That's
a
great
question:
Jamie
yeah,
so
there
are
some
kind
of
like
you
know.
Obviously
it
would.
It
would
be
a
little
disruptive
in
the
community
side
to
see
like
the
the
name
switch
from
one
place
to
another.
The
Mastodon
Community
has
really
good
tools
for
automating
that
migration.
So
if
we
had
an
account
on,
let's
say
we
had
an
account
on
fosted
on
and
we
wanted
to
move
to
hackaderm.
A
There
are
tools
that
will
automatically
migrate.
All
of
your
followers.
It
will
migrate.
You
know,
I,
don't
know
if
it
will
migrate.
Your
old
content,
I
think
that
would
still
be
on
the
old
server,
but
everyone
who
is
following
you
would
get
migrated
and
the
old
server
would
would
have
like
a
pointer
to
the
new
place.
A
So
anyone
who
went
to
the
old
location
would
get
forwarded
to
the
new
location
that
there
would
probably
be
some
people
who
would
be
left
out
in
that
you
know
people
who
just
maybe
had
a
link
or
whatever
or
or
had
followed
you
and
never
updated,
but
in
general
for
anyone
who's
actively
using
the
Mastodon
Network
they
would
get
automatically
bumped
and,
interestingly
enough,
I
just
went
through
this
because
right
about
the
time
a
little
bit
before
the
big
Twitter
disruption
that
happened
recently,
where
we
saw
people
going
to
Mastodon
the
Mastodon
server
that
I
had
been
using
before,
which
was
called
mastodon.technology.
A
The
owner
of
that
server
ran
into
some
family
problems
and
wasn't
able
to
continue
the
server
and
so
I
actually
went
through
the
migration
process
and
it
took
about
72
hours,
I.
Think
for
all
of
my
followers
and
everything
to
make
it
over,
but
it
was
mostly
seamless
I,
just
I
followed
the
automation.
I
did
what
it
told
me
to
do,
and
you
know-
and
it
kind
of
automated
it
all
for
me.
So
it's
it's
not
too
bad.
A
I
see
I,
see
Bruce,
asking
a
question
in
chat
here.
How
is
safe,
defined
I'm
using
that
term
very
broadly,
but
it
in
general
I
mean
like
like
in
a
code
of
conduct
kind
of
way,
usually
the
if
I.
If
I
understand
your
question
correctly
and
please
you
know
Bruce
if
I'm
not
getting
this
correct,
you
know
definitely
correct
me.
A
You
know
the
Mastodon
Community,
like
I,
said
they've
been
very
focused
on
privacy
and
focused
on
protecting
individual
users
and
whatnot.
So
when
I
say
safe,
usually
what
I
mean
is
you
know
a
community
may
not
may
not
particularly
tolerate
a
certain
type
of
content
that
comes
across
their
door
and
so
some
servers,
you
know
deem
other
ones
as
I,
don't
want
to
say
unsafe,
but
they
put
them
on
the
block
list
because
they
don't
consider
that
content
to
be
something
that
their
users
want
to
see
and
I.
A
Think
when
we
talk
about
safety,
you
know
this
gets
into
a
much
deeper
discussion
about.
You
know
kind
of
what
how
we're
policing
ourselves
online
and
I
don't
want
to
you
know:
I,
don't
necessarily
want
to
get
into
the
opinion.
A
Based
discussions
about
what's
happening
with
Twitter
and
the
content
that
happens
there,
but
I
think
you
know
one
of
the
reactions
to
the
Twitter,
verse
and
kind
of
why
we
see
the
fediverse
is
that
there
are
many
marginalized
communities
and
and
minority
communities
that
exist
in
these
places
and
they
have
really
desired
stronger
content
control
mechanisms
so
that
you
know
just
so
that
I'm
not
having
to
see
content
on
a
daily
basis
like
blasted.
In
my
face
that
I
that
I
don't
accede
to
and
maybe
is
really
like.
E
Yeah
I
guess.
My
question
is
because
that
many
words
have
been
redefined
over
the
last
couple
of
decades
and
safe
used
to
mean
physical
safety,
and
it's
often
come
to
mean
freedom
from
opinions
that
you
don't
like
to
hear,
and
my
concern
is
because,
like
this
is
a
technical
group
and
I
think
we
should
avoid
at
all
costs
getting
enmeshed
in
various
political
opinions,
ideological
opinions,
the
whole
range
of
non-technical
things.
E
And
Red
Hat
has
sort
of
gone
down
that
rabbit
hole
a
little
bit
with
Banning
certain
words
that
might
be
offensive
to
some
people,
or
at
least
some
other
people
might
think
that
they're
offensive
to
some
third
parties,
Etc
et
cetera
and
I,
think
that
that
is,
that
can
easily
become
non-productive
and
we're
a
small
enough
group
that
we
can't
really
afford
to
balkanize
based
on
some
of
these
non-technical
concerns,
so
that
that's
just
my
overall
concern
and
I
I
did
see
some
information
that,
in
terms
of
the
self-selection
of
people
on
Mastodon,
by
virtue
of
being
increased
by
people,
that
didn't
want
to
be
on
Twitter
for
various
political
reasons
that
I
I
actually
am
not
active
on
Twitter
because
of
age,
I
suppose
as
much
as
anything
but
the.
E
If
people
are
fleeing
Twitter
because
they
don't
like
the
politics
and
going
to
Mastodon,
then
then
they
bring
their
politics
to
Macedon
and
I.
I
want
to
avoid
all
politics.
A
Yeah
I
think
those
are
great
points
Bruce
and
I.
Think
in
general,
I
tend
to
agree
with
you
about
like
for
an
open
source
project.
We
probably
don't
want
to
involve
ourselves
with
the
greater
politics
that
are
going
on,
and
so
that's
why
I
think
instances
like
fostudon
and
hackaderm
are
probably
more
in
line
with
what
we
would
want
to
do
as
a
project
than
something
like
mastodon.social.
That
puts
us
into
a
much
larger
pool.
A
I
would
think
that
and,
and
honestly
like
I
would
want
the
community
to
decide
if
we,
if
we
decide
to
have
a
mastodon,
account
the
community
to
decide
where
should
decide
like
where
it
should
go,
but
I
think
ultimately
aligning
ourselves
with
an
instance
that
says:
hey
we're
dedicated
to
promoting
technology
and
that's
kind
of
our
main
thing,
and
we
find
that
their
code
of
conduct
kind
of
like
aligns
with
our
code
of
conduct.
Those
are
probably
good
signifiers
for
us
that
we're
we
would
be
in
the
right
place,
but
I
agree
with
you.
A
I,
wouldn't
want
to
see
us
end
up
on
some
server
that
had,
like
you
know,
a
very
strong
ideological
bent
to
it,
because
you're
right
that
would
kind
of
lump
Us
in
politically
with
the
body
of
people
who
are
there.
So
very
poignant,
I
think
that's,
definitely
something
we.
We
need
to
keep
in
mind
as
we
go
forward
with
this
process.
B
One
thing
I
would
say
is
that
you
mentioned
the
code
of
conduct
and
I
was
actually
thinking
about
the
code
of
conduct.
We
should
link
to
it
at
the
top
of
our
meeting,
notes
and
I
think
we
can
use
that
as
a
basis
for
interactions
through
Mastodon
and
our
Twitter
as
well.
Right
is
just
adhering
to
those
things
and
expecting
people
that
interact
with
us
to
adhere
to
those,
and
if
they
choose
not
to
adhere
to
the
code
of
conduct,
then
we
can
block
them
or
something
like
that.
B
That
we
have
to
you
know
without
getting
too
deep
into
the
weeds,
make
sure
that
the
okd
community
remains
open
to
everyone
and
that
no
one
feels
like
unsafe
or
or
unwelcome
right,
so
I
mean
there's,
there's
extremes
to
that
and
whatever,
but
I
do
want
to
make
sure
that
that
people
do
feel
welcome
and
that
some
of
the
bad
behavior
on
any
social
media
in
terms
of
of
being
abusive
to
people
and
stuff
like
that
doesn't
leak
over
into
wherever
we
go
from
here.
B
I
mean
we're
lucky
enough
that
our
Twitter
is
so
not
really
used
a
lot
right
now.
But
my
understanding
looking
at
comments
from
people
who
have
made
the
move,
is
that
Mastodon
actually
has
more
engagement
like
actual
engagement
with
people
who
are
interested
in
those
particular
topics.
So
that's
the
only
thing
that
I
would
say
is
with
increased
engagement.
You
know
we
want
to
make
sure
that
the
code
of
conduct
is.
Is
there
for
people
to
know
that
it's
it's
something
we
you
know
adhere
to.
B
E
My
idea
anyway
yeah
one
of
the
things
I
if
I
could
comment
is
that
when
you
say
we
don't
want
people
to
feel
offended
or
whatever
you
absolutely
cannot
control
how
people
feel
no.
B
C
E
You
know
Colonial
White,
patriarchy
and.
E
Associated
with
cultures
that
put
people
down
and.
B
Minoritize
and
I
understand
where
you're
going
Bruce
what.
B
Sure
what
I'm
thinking
is
that
we
have
a
leadership.
We
have
a
code
of
conduct
and
the
leadership
is
tasked
with
enforcing
that
code
of
conduct
and
making
decisions
based
on
that
code
of
conduct,
their
interpretation
of
the
code
of
conduct
and
so
yeah
as
those
things
arise.
That's
what
the
leadership
can
look
at
and
say.
Okay
is
this,
you
know
what
is
a
reasonable
interpretation
of
the
code
of
conduct?
Yes,
that's
that's.
D
D
Jamie
100,
but
for
me,
if
we
keep
things
Technical
and
we
stay
and
remain
technical,
the
rest
of
the
junk
that's
all
over
the
show
just
just
doesn't
take
hold,
and
so
yeah
I
I
totally
agree
with
what
you
guys
are
saying.
We
we
don't
want
to
get
involved
in
politics.
We
don't
want
to
get
involved
in
ideologies
for
your
technical
bunch
of
guys
that
want
to
make
open
source
awesome
for
everybody
and
that's
how
we
should
stay.
Okay,.
A
A
You
know
this
is
kind
of
like
guilt
by
association
right.
Whatever
server
we
choose
to
be
on,
we
probably
should
just
make
sure
that
we
don't
choose
one
that
has
a
code
of
conduct
that
has
language
that
you
know
either
goes
above
and
beyond
what
we
expect
as
a
community
or
somehow
clashes
with
what
we've
already
signed
up
to
so
I
think
just
to
bring
it
back
that
that
I
think
that's
kind
of
the
real
reference
point
here.
With
regards
to
Mastodon.
B
So,
in
terms
of
process,
are
we
thinking
that
this
group
can
make
the
decision
or
do
we
want
to
move
the
discussion
to
the
larger
technical
group
in
terms
of
deciding
to
to
go
on
Mastodon
or
not
I'm
comfortable
with
us,
making
the
decision
here
now?
Yes
or
no,
does
anyone
feel
that
we
should
bring
it
to
the
larger
group.
F
B
D
A
Here
yeah
I
mean
in
general,
I
support
this
group,
but
I
I
also
want
to
make
sure
that
like,
and
maybe
this
is
something
we
need
to
think
about
as
we
go
forward
about
how
to
make
decisions
like
do.
We
have
a
mailing
list
for
like
just
the
Community
Development
part
of
this
or
something
where
we
could
say
all
right.
We
could
pose
this
question
to
the
extended
Community
Development
Group,
because
I
just
want
to
make
sure
that
people
who
maybe
couldn't
make
it
today
aren't
necessarily
excluded
from
the
conversation
and.
B
Well,
we
can
send
something
out
over
the
the
working
group
Google
group
email
list.
If
you
want
and
just
say
this,
is
this
document?
Do
we?
So
what
is?
Let's
do
a
straw
poll
vote
so
that
in
in
the
message
that
gets
sent
to
the
larger
group
that
we
have
a
sense
of
what
we've
decided
straw
poll
vote,
Yes
on
mastodon
raise
your
hand
virtually
or
icon
wise?
Okay.
So
that's
all
of
us,
so
I
can't
see
what
you're
what
you're
doing
there
Dwayne.
Are
you
voting?
Yes,
no,
maybe
don't
know.
C
Thinking,
maybe
about
six
months
I
would
I
would
vote
Yes
just
want
to
give
the
year
time
to
flow
in
because
there's
there's
so
much
going
on
with
social
media.
You
know
it's
it's
hard
to
see.
You
know
politics
online
are
out
of
control.
You.
F
Yeah
I'm
just
going
to
say
one
thing:
I
mean
as
as
we
do.
This
I
mean
I've
stopped
following
that
Google
group
in
in
terms
of
I,
don't
go
and
actively
check
it
and
I.
Think
one
of
the
things
we
need
to
do
is,
as
we
decide
to
support
a
channel.
We
almost
need
somebody
responsible
for
checking
it,
because
there's
only
so
many
hours
in
the
day
and
I
I
don't
think
we
are
going
to
sit
on
the
slap
channel.
F
The
Google
group,
The
Mastodon,
the
Twitter
I,
know
that
there
are
Facebook
as
well
that
I
don't
actually
follow
either
so
I
just
think.
Whatever
Channel
we
do.
We
either
nominate
a
person
or
people
and
say
that
you're
responsible
for
checking
this
at
least
I,
don't
know
it's
going
to
be
once
a
week
once
a
day,
but
we
we
have
a
yeah.
We
have
somebody
responsible.
So
there's
no
point
in
having
a
Channel
people
are
following
it
and
they're
not
getting
any
feedback.
I.
B
Think
we
should
have
communications
officers
that
are
basically
like
volunteers
and
we
can
rotate
maybe
every
year
every
six
months.
I
think
two
people
is
good
because
then,
if
one
person
goes
on
vacation
or
something
we
don't
have
to
worry
about
figuring
out
who
the
next
person
up
is
or
they
can
take,
turns-
or
you
know
you
know
do
shifts
or,
however
you
want
to
do
it.
Does
two
people
sound
good?
B
B
B
B
It's
it's
ad
hoc,
it's
it's
me
doing,
Twitter
and
and
Luigi
now
doing
Twitter
and.
B
Right
and
then
I
don't
think
we
I
do
the
Facebook
occasionally
what's
and
the
Facebook
is
the
openshift
Commons
Facebook
group
there's
an
open
shift.
Openshift
Facebook
group,
that's
run
by
Diane.
A
I
mean
I'm
wondering:
would
it
maybe
make
sense
for
us
to
put
together
like
a
document
for
the
community
like
so
that
we
can
kind
of
organize
around
the
like
here's,
where
our
here's,
where
our
socials
are
now
here's,
how
we're
going
to
manage
them
so
that
we
can
kind
of
propose
like
what
you're
talking
about,
because
I
would
love
to
see
this
like
as
part
of
the
community
repo
or
something
we
could
just
say
like
here's,
our
policy
for
how
we
manage
management-
and
here
are
the
people
who
you
can
get
in
touch
with
who
are.
B
Managing
right
now
or
whatever
you
know,
yeah
I
think
that's
a
great
idea.
So,
let's
create
a
document.
We'll
add
that
to
the
to
Do's,
we'll
create
a
document
that
lists
what
our
social
media
presence
is
like,
where
we
are
the
fact
that
we
adhere
to
the
community
standards
document
that
we
have
and
then
list
the
people
that
can
be
contacted
and
if
we
look
at
the
aliases
I
think
we
actually
do
have
Communications.
So
that
would
be
we
would
just
have
people
email,
the
communications,
Alias
right.
B
A
Yeah
I
mean
part
of
my
concern
here
is,
like
you
know,
there's
no,
there's
no
pressure
for
us
to
rush
off
and
create
a
mastodon
account.
We
can
certainly
take
our
time
doing
it
and
I
think
it
would
be
really
cool
if
we
had
like
if
we
kind
of
get
our
policies
in
order
before
we
Adventure
into
like
a
new
social
media
Zone
and
then
also
like
I,
think
it
would
be
worthwhile
to
spend
some
time.
You
know
getting
some
automation
together
so
that
maybe
we
could
make
whoever's
job.
D
Yeah,
sorry
sorry
I
was
going
to
ask
dude.
Does
it
have
a
set
of
apis
that
are
available?
Obviously
I
would
imagine
you
need
some
tokens
in
it
and
then,
if
you
can,
we
can
if
it
has
got
it,
then
it's
easy
to
build
it
in
a
pipeline.
Once
we
do
our
releases
just
to
update
Mastodon
and
whatever
you
know
right.
A
No
you're,
absolutely
right
there
are.
There
is
an
API
there's,
a
rest
API
for
interacting
with
all
these
things
and
there's
even
there
are-
and
this
is
kind
of
side
to
what
we're
talking
about.
But
there
are
even
instances
that
are
completely
dedicated
to
bots.
There's
one
called
bots
in
space,
where
all
the
accounts
on
that
instance
are
just
Bots
and
they
do
bot
type
activities
like
copying,
messages
and
stuff,
like
that.
A
So
I
think
in
in
the
end,
like
what
would
probably
be
like
I
think,
there's
a
long
tail
to
all
this,
which
would
be
really
cool,
which
is
like
eventually,
if
we
get
to
the
point
where
our
community
is
operating
its
own
openshift.
You
know
cluster
at
some
point
or
operating
like
some
sort
of
okd
cluster.
You
know
we
could
even
be
running
these
automation
out
of
an
okd
cluster.
You
know
really
show
people
how
we're
using
kubernetes
with
you
know,
kind
of
the
most
current
technology
to
create
these
type
of
things.
A
So
I
think
there's
probably
like
some
room
for
us.
If
we
can
in
the
next
you
know
year
or
two,
we
can
start
to
carve
out
like
a
community
space
where
we
could
run
things
in
in
openshift.
We
could
use,
you
know,
use
it
to
do
these
type
of
things
like
we.
We
could
probably
make
some
really
cool
stuff
here.
That
would
show
the
community.
You
know
how
we're
using
okay,
yeah
yeah.
It's
part
of
our
mission
right.
B
Right
so
who
wants
to
take
up
the
task
of
sort
of
starting
an
outline
document?
You
did
so
well
on
the.
Let
me
go.
You
did
so
well
on
getting
this
information
together.
You
interested
in
creating
sort
of
a
document
that
outlines
what
you
just
mentioned.
A
Start
on
something
I'll
need
some
help,
though,
and
I
I
don't
I
I,
honestly
can't
I
can't
agree
to
like
take
a
ton
of
time.
But
if
you
know,
if
you
give
me
like
kind
of
a
two
three
four
week
time
frame,
yeah
I
could
certainly
work
with
some
people.
You
know
probably
work
with
you
Jamie
and
reach
out
to
Brian
and
others
too
yeah.
E
A
B
A
B
All
right,
so
the
last
thing
I
wanted
to
end
with
is
prioritization
and
just
to
sort
of
list
out.
We've
got
a
handful
of
tickets,
but
what
are
our
top?
What
are
our
top
five?
What
are
our
top
five
things
in
q1
Brian.
B
Was
thinking
in
terms
of
this
group,
but
you
know
in
terms
of
the
community
development.
F
B
F
And-
and
it's
like,
how
do
we
do
that
because
I
know
a
lot
of
a
lot
of
these
discussions
will
happen
internally
within
red
hat
and
then
the
community
sort
of
get
to
see
the
results
and
I.
For
that
one
I'm
certainly
happy
to
be
part
of
the
discussion,
and
then
my
number
two
would
be
covered.
What
what
Nico
already
said
is
getting
some
standardization
and
some
automation
to
some
of
our
community
management
activities.
B
E
E
Yeah
I
would
add
in
something
along
the
lines
of
you
know:
blog
slash,
videos,
slash
help
for
people
installing
new
okds.
E
B
E
Yeah
but
anyway
we
had
a
a
a
good,
albeit
unofficial,
discussion
on
you
know
like
over
versus
you
know,
charo's.
You
know
you
know
KVM.
E
I'm
losing
the
the
acronym.
You
know
acronym
City,
but
you
know
basically,
the
the
standard,
Linux,
virtualization
and
Charo
has
been
updating
his
massive
blogs
and
you
know
things
but
and-
and
so
at
the
moment,
I
don't
think
we
have
a
finalized
decision
of
what
we
want
to
prioritize
on
that
whole
stream
of
things
right
so
I
think
that
deserves
being
on
our
list
to
well.
E
E
B
D
What
else
yeah
I
would
also
I
would
also
venture
to
say,
but
I
think
it's
part
of
the
whole
okay
D
single
node
stuff
is
okd
on
edge.
D
I
mean
everything
in
the
last
couple
of
meetings
we've
had
internally
in
Red
Hats,
it's
the
whole
Drive
is
is
is
going
towards
Edge
and
the
microchip
things
you
know.
So
it
would
be
great
to
have
a
almost
a
simple
okay,
the
install
of
of
okb.
You
know
what
I
mean
and
on
a
on
even
getting
it
somewhere
on
a
small,
Raspberry,
Pi
or
something
I
mean
but
I
mean
I,
know
that's
pushing
the
the
limits,
but
if
we
could
do
it,
it'd
be
great
yeah.
C
Yeah
and
I
think
there's
some
user
cases
for
that,
and
that
may
be
a
way
to
pull
into
pulling
some
Community
users,
because
Edge
is
a
very
powerful
buzzword
nowadays.
B
Was
that
that
was
the
big
somebody
in
our
group
was
always
asking
about
where
it
was
where
things
were
and
could
they
get
it
on
like
a
Raspberry
Pi,
it's
something
that
hasn't
been
coming
to
meetings
lately,
but
I
can't
remember
who
it
was,
but
we
had
someone
that
was
a
big
proponent
of
it.
I
was
always
asking
Christian
about
well.
Can
we
do
it?
Can
we
do
it?
I
can't
think
of
who
it
was
now.
I'll
have
to
look
back
on
the
meeting
notes,
but
yeah
I
mean
we
can
actually
bring
this
up.
B
So
I
think
at
the
next
meeting,
we'll
bring
this
up
and
then
at
the
next
main
tech
meeting,
bring
this
up
and
bring
the
operators
Thing
Up,
The,
Operators
thing
I
think
we
need
some
clarity.
We.
B
Who
to
bug
or
do
we
need
to
just
do
this
ourselves?
Like
you
know
my,
we
landed
on
there
being
a
separate
catalog,
but
I
don't
know
if
it's
being
populated
or
where
it's
at
right
well,.
F
I
think
one
of
the
problems
I
mean
I
I
sort
of
started.
Looking
at
this
I
don't
want
to
go
down
too
too
deep
in
the
rabbit
hole,
but
it
it's
it's
all
the
things
that
we
do
with
the
main
okd
like.
Are
we
going
to
try
and
stay
in
step
with
ocp?
Each
operator
has
its
own
life
cycle.
It
has
its
own
update
graph
and
are
we
going
to
go
separate?
Are
we
going
to
stay
in
touch
and
I
noticed
that
the
operator
repositories
are
out
there
onto
all
standards
from
them?
F
Actually
don't
have
any
tags
that
link
back
to
I?
Think
it's
within
prow
or
some
other
repo
of
how
they
manage
that.
So
there's
a
lot
of
stuff
that
we
have
to
actually
decide
as
a
community
in
terms
of
the
whole,
how
we're
going
to
handle
each
operator
plus,
then
the
catalog
as
a
whole.
So
that's
where
I
I
say
I
think
there
has
to
be
some
Community
discussion.
F
D
And
it
was
a
not
sort
of
overstep
the
boundaries
with
subscriptions
on
some
operators
that
red
hat
don't
want.
You
know
we
we
have
to
you
know
they
are.
D
They
are
going
to
be
restrictions
and
yeah,
and
that
sort
of
brings
me
to
another
point
that
at
the
moment
our
team
is
working
on
and
I'm,
also
personally
working
with
the
the
OC
mirror,
interface
and
and
that's
building
file
based
Firebase
catalogs,
there's
a
specific
ask
for
IBM,
and
so
if,
if
we
do
succeed
in
getting
this
thing
done,
it
means
that
anyone
can
build
their
own
catalog
and
push
it
to
a
remote
registry
and
build
their
own
catalog
and
consume
that
catalog
how
they
want.
D
Obviously,
you
know
within
reason
that
everything's
signed
and
it's
and
you
know
you
know
it's
a
trusted-
a
trusted
Source,
and
these
are
the
the
the
other
issues
that
you
know.
We
could
also
look
at,
but
yeah
you're
right.
It
is.
It
is
quite
a
big,
a
big
issue
there
Brian,
so
I
think
we
should
set
up
a
meeting
and
and
discuss
these
things
and
go
through
them,
as
as
a
group.
A
Yeah
I
mean
just
to
kind
of
follow
up
on
that
I
think
you
know,
Brian's
question
is
really
poignant
and
I
would
I
would
love
to
kind
of
like
ask
the
larger
Community,
because,
like
I
have
this,
you
know,
I,
have
this
notion
of
when
I
come
to
okd
community
I.
Think,
like
there's
a
lot
of
inspiration
we
could
draw
from
the
Fedora
Community
right,
especially
in
the
trajectory
we're
going
and
everything
where
it's
like.
You
know
we're
evolving
okd
almost
as
this.
A
You
know
this
is
the
community
version
of
open
shift,
but
it's
also
kind
of
growing
as
its
own.
You
know
Community
whatever
right
kubernetes,
and
so
you
know
like
Fedora,
has
their
own
package
management
system
and
everything
right.
They
have
their
own
places
for
this
and
and
yeah
I
think
this
is
a
question
we
need
to
ask
ourselves.
Is
that
if
this
community
is
going
to
continue
growing
in
this
in
this
Direction,
Where
We
would
like
to
support
ourselves,
and
we
would
like
to
kind
of
really
build
a
community.
Then
it's
like.
A
Doesn't
it
behoove
us
to
start
thinking
about
how
we
will
host
our
own
operator?
Catalog
who
we
need
to
work
with
in
Red,
Hat
to
understand
the
technology
better
and
then
like
who
in
our
community,
is
really
interested
in
this,
because
I
think
we
we've
seen
interest
for
maintaining
certain.
You
know
very
specific
bits
of
the
catalog
right,
but
if
we
can
start
to
build
this
contributor
list
of
you
know
people
who
are
willing
to
own
an
individual
operator
or
something
in
the
same
way
that
you
might
own
a
package
in
Fedora,
then
you
know.
A
Maybe
we
really
can
start
to
build
this
community
out
in
terms
of
really
we're
self-supporting
and
we
take
the
code.
You
know
we
we
share
code
with
ocp,
but
we
have
our
own
ideas
about
like
how
we're
going
to
use
it
and
everything
so
I
would
love
to
kind
of
get
into
some
of
those
bigger
questions
with
the
community.
So
maybe
that's,
maybe
that's
one
of
my
desires
for
q1
is
I.
Would
love
to
see
us
have
these
conversations
and
maybe
figure
out
some
things
as
a
community
yeah.
B
And
I
think
we
can
start
that
next
week,
I
I'm
almost
inclined
person
recently
I
would
be
inclined
to
take
the
approach
like
we
did
with
the
mail
I
mean
the
mail
thing
eventually
resolved
itself,
the
email
thing,
but
it's
like
Fisher
cut
bait
right.
One
of
the
things
is
that
we've
been
told
that
you
know
the
the
catalog
thing
got
sidetracked
the
end.
You
know
the
internal
work
in
Red
Hat
got
sidetracked
and
they
haven't
worked
on
it.
The
internal
workouts.
B
F
Yeah
sorry
I
mean
I,
think
it
is
damaging
an
okd
because
we
can't
use
olm
Community,
because
you
already
have
that
pre-installed
and
that
pulls
in
the
red
hat.
Ocp
version
of
olm
and
many
of
those
operators
are
broken
because
they
point
back
to
Red
Hat
built
versions.
So
we
don't
have
the
community,
and
yet
we
don't
have
the
red
hat.
So
once
you
get
okay
installed,
you
actually
try
and
do
anything
on.
F
F
So
I
think
we
need
to
sort
The
Operators
one
way
or
another.
My
way
is
to
take
the
public
source
code
and
build
it
ourselves,
so
we
created
an
okd
build
then
we're
not
we'd
have
no
licensing
issues.
If
Red
Hat
doesn't
want
something
to
be
built,
they
shouldn't
put
it
in
public
domain
yeah.
D
E
F
Don't
have
any
licensing
issues
there
because
we're
not
using
Red
Hat
binaries
we're
using
Community
built
binaries
but,
as
you
say,
we
then
have
to
go
and
think
about.
How
do
we
sign
them?
How
do
we
control
them?
So
it's
a
trusted
Source
rather
than
a
free-for-all,
so
I
think
there's
a
lot
of
subtlety
to
these
discussions
that
we
need
to
get
into
and
it's
not
trivial,
yeah.
B
D
F
Yeah
we
can
solve
the
discussions
and
work
out
who
wants
to
be
involved,
and
how
are
we
going
to
do
this?
Are
we
going
to
actually
set
up
another
regular
meeting?
Are
we
going
to
have
ad
hoc
meetings
I
think
you
can
sort
of
move
forward
with
it?
There's
a
there's,
a
slim
chance,
and
maybe
here
in
two
weeks
time,
but
I'm-
definitely
not
here.
Next
week,
okay,.
B
Well
and
I
will
draw
it.
I
will
make
sure
that,
folks,
that
people's
attention
is
drawn
to
you
added
to
that
thread,
actually
I
noticed
a
couple
weeks
ago,
and
you
mentioned
that
here,
yeah
I'll
draw
people's
attention
to
that
discussion,
which
is
ongoing,
yeah
doing.
C
Yes,
and
and
just
to
continue
to
add
to
everyone
wanting
to
build
out
the
community
and
the
interaction,
especially
of
some
of
the
things
we
want
to
do,
need
funding.
Do
we
have
a
cost
objective?
I
mean
I'm,
always
working
on
grants.
If
there's
a
certain
cost
parameter
that
needs
to
be
met
to
make
things
actual
I
know
one
time
we
talked
about
hey
giving
people
access,
but
then
we
need
to
screen
them
to
make
sure
they're
not
doing
bit
mining
or
something.
C
But
you
know
a
way
we
can
systematically
bring
in
resources
where
our
community
can
get
into
the
prototyping
the
testing
and
and
if
there's
a
cost
there
you
know
what
is
that
cost
and
how
can
we,
you
know
and
that
that's
a
long-term
six
months
process
and
you
have
to
have
to
have
delegate
management
with
you
know,
Outsiders
who
are
who
are
actually
contributing
to
okd?
So
it's
just
something
to
think
about.
If,
if
people
are
interested
in
that
type
of
potential
funding,
if
that
is
need
eat
it
yeah.
B
All
right:
well,
we
are
at
oh
Diane.
G
I'm
I'm
doing
fine.
Thank
you
very
much
yes
and
I.
I
didn't
get
the
UTC
change,
but
anyways
good
to
see
all
your
faces.
G
G
So
anyways
I
was
typing
very
fast.
I
apologize
for
that
I
was
just
wondering
if
what
kind
of
feedback,
if
any
and
if
we
had
done
any
sort
of
blog,
write
up
on
the
new
release,
Shireen
or
anybody
had
done
anything
around
that
that
I
could
promote
or
if
maybe
I,
could
get
a
glean.
A
few
words
from
you
guys
and
do
that
writing
myself.
For
you,
foreign.
B
D
What
what
we
could
do
is
just
just
make
notes
of
the
fact
that
it
you
know
that
was
built
without
Pipeline,
and
even
the
release
was
created
with
the
pipeline.
D
A
couple
of
words
and
I
could
just
quickly
knock
that
up
and
send
you
an
email
Diane.
If
that's
okay,
yep.
G
Yep,
that
would
be
wonderful
and
then
I
will
use
the
normal
okd
blog
posting
site
a
process
and
do
that
and
next
next
time
I
will
come
an
hour
earlier.
Okay,.