►
Description
Stack Overflow onboarding and training video on 2021-08-02 with Stack Overflow and internal GitLab team
A
Okay,
so
we're.
B
A
Sounds
good
just
a
quick
question
before
I
dive
in
what
should
I
expect
in
terms
of
like
overall
knowledge
about
stackoverflow
and
about
collectives
is:
has
the
majority
of
the
team
being
briefed,
or
should
I
kick
it
off
with
a
brief
brief
introduction.
B
High
level
I've
been
with
a
couple
people
on
this
team,
but
it'd
be
good
just
to
kind
of
get
into
this,
as
maybe
just
like
ground
zero,
like
we
don't
know
anything
and
just
make
sure
that
we
get
documented
reason
being
is
that
we
might
add
people
to
this
later,
and
so
I
just
wanna
make
sure
that
this
video
has
that
context
as
well.
A
Perfect
sounds
good.
If
anybody
has
any
questions
during
during
the
demo,
please
feel
free
to
either
shout
or
we'll
do
the
race
hand
feature
from
from
google
meet
then
we
can
just
keep
it
a
bit
a
bit
conversational.
So
kicking
it
off.
Introduction
to
myself,
I'm
yasha,
I'm
a
product
manager
here
at
stackoverflow.
A
Working
on
this
new
initiative
that
we've
launched
recently
collectives
on
stack,
overflow
and
collectives
on
stackoverflow
is
is
initiative
that
will
allow
allow
like
gitlab
employees
or
people
from
your
developer,
recognition
program
or
or
anybody
like
that,
to
engage
with
the
stackoverflow
community
and
specifically
the
community
around
the
gitlab
technologies.
A
A
So
I
guess,
for
the
majority,
this
page,
that
I'm
sharing
now
I'll
zoom
in
a
bit,
because
probably
it's
a
bit
small,
it's
familiar,
and
this
is
like
the
main
place
for
all
stack
overflow
users
right.
So
the
majority
of
the
users
come
in
through
like
through
a
search
or
or
anywhere
else,
and
they
get
to
a
question
page
because
they're
stuck
with
a
with
a
particular
pro
problem
and
they
want
an
answer
on
it.
A
So
for
anybody
who
is
a
developer,
probably
a
familiar
flow
for
anybody
who's?
Not
this
is
really
the
place
the
place
users
are
and
that
way
we
reach,
basically
all
the
developers
in
the
world.
So
this
is
the
way
this.
This
page
usually
looks
like
somebody
asks
a
question
and
somebody
else
answers
it.
A
So,
as
you
see
on
the
top
right,
I've
highlighted
in
in
red
to
make
sure
that
it
that
is
notified,
but
it
will
have
the
the
gitlab
callers
when,
when
we
go
live
to
the
public
on
all
questions
that
have
any
tag
that
is
related
to
gitlab
or
any
gitlab
technology,
we
will
show
this
badge
at
the
top
right.
A
All
right
and
this
showcases
that
a
question
is,
is
part
of
of
a
particular
collective
and
this
badge
links
the
user
to
the
collective
page,
which
is
the
centralized
presence
for
gitlab
on
on
stack
overflow.
A
So
if
I
scroll
down
you'll
see
that
there's
there's
somebody
that
answered
the
question-
and
this
brings
me
to
one
of
the
like
the
first
new
pieces
of
engagement
that
we've
allowed,
which
is
recommended
answers.
A
So
what
we've
learned
from
user
research
is
that
for
users
frequently,
like
a
question,
has
a
lot
of
answers
right,
it's
and
it's
difficult
to
figure
out
what
the
best
way
of
solving
a
problem
for
you
is
so
with
recommended
answers.
Somebody
from
from
the
gitlab
like
some
a
gitlab
employee
or
somebody
that
you
dedicated
designated
this
this
resource
to
is
able
to
go
in
look
at
the
different
answers
and
mark
an
answer
as
recommended.
A
A
This
is
the
best
possible
way
of
solving
this
problem,
so
I
might
as
well
and
go
in
and
try
to
to
use
this
solution,
but
it
also
cuts,
on
the
other
hand,
where
the
user
actually
written
the
answer
and
frequently
users
spend
like
at
least
half
an
hour,
but
sometimes
hours
in
writing
a
potential
answer
to
to
a
question.
A
It's
also
like
an
acknowledgement
for
their
work
right
that
an
organization
such
as
gitlab
thinks
that
the
effort
that
they
put
in
the
answer
that
they
wrote
is
a
very
good
way
of
solving
the
problem
and
again
is
kind
of
a
kudo
that
you're
giving
to
that
user
for
for
the
effort
that
they
that
they
made.
A
B
Go
ahead,
josh
can
ask
a
question
there
go
ahead.
I
I
know
the
scenario
may
be
far
and
few
between,
but
would
there
be
a
point
where
the
person
asking
the
question
picks
an
answer
that
essentially
I
help
them.
It's
like
it's
like
hey
this.
This
is
what
this
is.
The
answer
that
I
picked.
However,
that's
not
necessarily
the
like
company
recommended
answer,
and
then
the
company
pick
something
else
is
there
going
to
be,
I'm
not
sure
how
you
handle
that
conflict
or
how
that
gets
notified
within
the
question
itself.
A
I
think
that's,
that's
that's
a
great
great
question,
and
it
it
ties
in
actually
another
aspect
as
well
is
that
there
could
also
be
other
organizations
right.
So,
for
example,
you
have
a
question
which
is
around
gitlab
and
I
don't
know
google
cloud
right
there.
There
must
be
a
overlap
going
on
with
with
questions
there,
and
the
point
about
a
certain
answer
is
that
it
doesn't
have
to
be
the
only
right
way
right,
something
that
worked
for
a
user
that
they
potentially
accepted.
A
That
answer
as
being
the
answer
for
them
doesn't
necessarily
have
to
be
the
best
possible
answer
for
gitlab.
Nor
do
does
that
have
to
overlap
with
with
the
best
possible
answer
for
for
google
cloud
right
so,
and
actually
that
is
exactly
what
we
want
to
achieve
here
is
providing
some
almost
metadata
to
the
user
about
a
potential
answer,
so
they
go
into
a
question.
They
have
the
same
issue
they
scroll
down.
They
see.
Okay,
this
according
to
gitlab
is
the
best
possible
way
of
doing
it.
A
This
is
according
to
the
user
that
wrote
the
question
and
this
according
to
google
cloud
and
it
those
could
be
either
or
completely
different
answers
or
all
the
same
one
right,
that's
that's
perfectly
perfectly
fine
and
again
it's
it's.
It's
just
highlighted
to
the
user
that
gitlab
thinks
this
is
a
good
way
of
solving
this.
This
problem
and
gitlab
is
contributing
to
the
overall
stack
overflow
community
by
sharing
their
knowledge,
but
like
from
our
perspective,
this
is
the
best
way
a
possible
way
of
solving
it.
A
Sorry,
I
think
it
was
you
said
there
was
a
bit
of
noise.
I'm
not
sure
whether
everybody
heard
that
I
think
I
see
some
some
nods
I've,
I've
muted,
you
it
wasn't
badly
intentioned,
but
otherwise
I
guess
everybody
had
some
had
some
noise.
A
So
for
the
second
piece
of
new
engagement
form
I'll,
show
a
question.
I
need
an
answer
from
from
somebody
from
within
the
collective,
so
I'll
show
a
question
which
is
currently
answered
by
somebody
from
from
google
cloud
right
so
again,
similar
similar
question
scenario,
good
good,
good
question.
Cesar.
Let
me
answer
that
one
that
one
first
so
currently
it
will.
A
It
will
not
so
we've
kept
the
sorting
order
in
the
in
the
same
way
as
it
is
now,
based
on
on
the
amount
of
votes,
our
public
platform
team,
who
is
responsible
for,
like
the
the
experience
of
the
of
the
overall,
like
stack
overflow
community
they're,
currently
looking
into
the
best
way
of
sorting
right,
because
the
current
mechanism
isn't
suited
for
all
possible
use
cases.
A
So
we're
trying
to
figure
out
what
what
the
best
way
is,
and
we
feel
that
recommended
answers
could
be
like
an
input
mechanism
for
for
the
best
possible
way
of
sorting
the
sorting.
The
answer.
B
A
A
A
C
Can
you
hear
me
now
yeah,
perfect,
okay
good,
so
I
have.
I
always
have
issues
with
my
airpods.
I
don't
know
why
all
right!
So
if
I
understood
correctly
right
now,
a
an
an
answer
that
has
the
highest
number
of
votes
will
be
listed
first,
even
if
git
lab
recommended
a
different
answer:
correct
okay.
A
Well,
we're
we're
envisioning
that
that
will
change
right.
The
current
mechanism
isn't
the
best
way
we
want
to
do.
We
want
to
do
it
and
it
doesn't
work
for
all
users.
However,
we
don't
want
to
like
just
push
the
organization
approved
answer
to
the
top.
We
see
it
more
as
like
an
input
field
for
the
best
possible
way
of
of
sorting
sorting.
A
So
something
like
that
would
would
make
would
make
more
sense.
It's
also
a
bit
of
a
balance
right.
We
don't
want
people
just
feel
like
okay,
these
organizations
are
coming
in
and
like
changing
our
whole
whole
system,
we
want
to
make
sure
that
gitlab
kind
of
integrates
with
with
the
community,
which,
at
the
end
of
the
day,
is,
is
the
whole
goal
of
this.
C
It
makes
sense,
although
as
a
user
as
a
developer,
I'll
be
extremely
interested
in
knowing
what
the
actual
company
is
recommending
right
versus
other
developers.
A
D
A
This
is
recommended
by
git
lab
plus
when
I'll
go
into
the
into
the
collectors
page.
There
is
actually
a
page
where
users
can
find
all
the
answers
that
are
recommended
by
either
git
lab
employees
or
recognized
members.
A
So
then
sharing
this
screen,
which
is
again
like
I
mentioned
the
google
question,
but
is
a
good
example
of
the
the
second
new
engagement
piece,
which
is
the
recognized
member
right.
So
as
gitlab
you'll
be
able
to
make
sure
that,
like
particular
group
of
users
are
marked
specifically
within
the
within
the
gitlab
tags.
So
as.
B
A
See
this
user
from
piffla
piffle,
he
is
marked
as
google
cloud
employee,
so
gitlab
will
be
able
to
do
the
same
thing
and
there
are
two
particular
badges
that
they
can
that
they
can
assign
either
or
google
cloud
employee
or
google
cloud
recognized
memory
in
your
case,
gitlab,
employee
or
gitlab
recognizes
recognized
members.
So
this
again
highlights
the
contribution
from
gitlab
to
the
overall
stack
overflow
community
by
writing
answers
by
giving
users
information
on
the
problems
that
they're
stuck
with.
A
You
can
highlight
the
fact
that
you're
you're
contributing
that
you're
sharing
knowledge
and
also
adds
a
bit
of
let's
say
again,
metadata
about
the
affiliation
of
that
user
to
the
to
the
to
the
organization
we've
learned
from
user
research
that
we
wanted
to
avoid.
Having
too
many
like
different
name
like
champions,
mvps
captains,
the
whole
sphere,
spectrum
of
of
potential
names
that
are
that
are
out
there.
A
We
they
wanted
to
keep
it
like
fairly
simple,
but
they
did
want
to
know
whether
there's
like
a
formal
agreement
between
the
the
organization
and
and
the
user.
So
again
on
any
answer
or
question
somebody
posts
within
within
the
collective
they'll
see
this.
This
badge
and
this
badge
will
link
into
the
collectives
page
which
I'll
serve
in
a
bit
anything
else
I
wanted
to
add
there.
C
Josh,
could
you
again,
I
think
you
might
have
mentioned
this
already,
but
how
does
someone
get
a
git
lab
recognized
member
badge?
That's
it.
A
Good
good
question
so
I'll
I'll
I'll
showcase
it
in
at
the
end,
specifically
how
it
works,
but
gitlab
will
assign
a
certain
group
of
admins
right.
So
these
are
like
the
over
the
top
users.
They
can
go
into
the
admin
page,
add
the
users
and
make
them
recognized
change
the
label
from
from
recognized
member
to
to
employee
and
potentially
also
look
for
users
for
that
are
actually
answering
questions
within
stack,
overflow
and
mark
them
as
recognized
right.
A
So
it
doesn't
have
to
be
somebody
that
you
have
a
formal
agreement
with,
but
it
could
also
be
somebody
that
is
just
very
knowledgeable
about
the
github
technologies
and
you
want
to
acknowledge
them
for
for
that
by
giving
them
this
specific
batch.
So
they
can
answer
questions
on
on
your
behalf.
Basically,.
B
And
say
sorry,
I
can.
I
can
kind
of
like
speak
to
that.
A
little
bit
is
right.
Now
I've
only
used
like
internal
gitlab
employees
right
now
for
recognized
members
just
so
that
we
have
understanding
of
the
collective
and
get
like
the
usage
under
our
belt.
B
Eventually,
once
we
get
that
dialed
in
we're,
gonna
expand
that
to
the
greater
like
lab
community
itself,
not
just
gitlab
employees,
so
that
we
can
start
looking
for
get
people
in
the
gitlab
community
that
are
actually
also
active
within
stack
overflow
and
get
them
in
this
recognized
member
as
well.
One
of
the
things
that
I
will
also
work
on
is
maybe
creating
some
documentation
within
our
collectively
to
say
like
hey.
B
This
is
this
is
how
you
become
like
a
recognized
member
and
so
that
that's
available
for
people
that
come
to
our
our
page
and
are
answering
questions.
A
A
In
that
case,
I'll
go
into
the
into
the
actual
collective
page
there
we
are,
and
I'll
start
with
with
the
questions.
Tab
I'll
first
go
over
all
the
tabs
that
are
available
for
all,
basically
all
users
of
of
stack
overflow
and
then
we'll
go
into
the
different
pages
that
are
either
available
to
recognize
members
or
to
to
admits
so
starting
with
the
the
questions
tab.
This
is
an
overall
view
of
all
questions
that
are
available
within
the
gitlab
collective.
A
So
again,
there
are
different
types
of
sorts,
different
types
of
filters,
figuring
out
which
answers
are
which
questions
are
unanswered,
which
do
not
have
a
recommendation.
What
are
the
specific
topic
tags
that
are
used
within
within
the
collective?
So
how
much
overlap
is
there
between
gitlab
and
grafana?
For
example,
all
of
that
type
of
stuff
can
be
found
by
all
users
here
on
on
this
page,
moving
on
to
the
answers,
tab,
which
is
obviously
not
all
answers
within
the
gitlab
collective,
because
that
would
not
make
sense.
A
Nobody
is
just
looking
for
all
answers,
but
these
are
all
answers
that
are
either
written
by
a
recognized
member
or
an
employee
or
that
are
recommended
by
somebody
from
from
the
from
git
lab
right.
So
there
will
be
an
overview
of
all
these
answers
here.
So
users
can
see
what
the
contribution
is
from
gitlab
to
the
to
the
stackoverflow
community.
A
I'll
move
on
to
articles,
which
is
which
is
a
very
big
thing
for
for
stack
overflow
right.
So
since
the
inception
stackoverflow
has
always
been
q.
A
so
all
pieces
of
content
have
been
written
in
that
format.
So
a
question
that
has
an
answer
or
does
not
have
an
answer,
because
nobody
knows
how
to
do
it
so
articles,
but
we've
always
heard
from
from
our
users
that
there
is
an
appetite
to
go
beyond
q
a
right.
So
not
all
types
of
content
can
fit
in
in
the
q.
A
A
format
and
we've
launched
articles
already
on
our
private
stackoverflow
instance.
I
think
a
year
or
or
two
ago,
and
that
worked
out
really
well.
We've
got
pretty
good
feedback
on
that,
so
with
collectives
on
stackoverflow
we're
bringing
articles
to
to
the
public
platform.
So
we
split
articles
up
in
three
types
of
contents:
how-to
guides
knowledge
articles
and
announcements.
A
So
it
is
important
to
note
that
well,
first
of
all,
articles
can
only
be
written
in
the
initial
stages
by
recognized
members
and
and
admins
of
of
a
collective
right.
So
it's
currently
closed,
but
we
are
building
a
feature
with
which
users
can
actually
propose
certain
article
content
to
the
collective
which
will
go
through
a
review
queue
of
your
recognized
members
or
employees
before
it
gets
posted
to
the
to
the
collective,
so
also
you'll,
be
able
to
kind
of
crowdsource.
A
The
creation
of
of
knowledge,
and
another
thing
to
highlight
is
that
all
content
here
should
be
of
technical
nature
all
right,
so
I
don't
want
to
offend
anybody.
I've
I've
also
studied
marketing,
and
I
I
know
the
difficulties
here,
but
developers
want
to
hear
from
developers
or
technical
folks
right
and
announcements
are
fine
and
perfect
as
long
as
they
are
technical
of
nature,
so
a
new
release
of
something
adding
some
explaining
why
certain
features
are
working
in
a
specific
way.
That
type
of
things
are
perfect.
A
However,
it
has
to
be
like
balanced
if
you
think
about
it
in
terms
of
of
marketing
speech,
so
I
think
we
have
to
thread
carefully
there,
because
we
do
know
that
the
community
might
get
upset
if
it
gets
too
much
marketing
ish,
but
we're
in
in
it
together.
So
we're
willing
to
collaborate
on
thinking
what
what
the
best
possible
content
is,
and
I
think
already
matt
you've
sent
us
one,
one
document
with
with
a
potential
article
that
we're
that
we're
going
over
with
with
our
team.
A
So
we
can
make
sure
that
the
content
written
there
is
feasible
for
our
for
our
community
and
it
will
be
received
well
because,
at
the
end
of
the
day,
only
content
that
is
received
well
will
serve
serve
a
good
purpose.
B
And
I
just
josh,
if
I
can
just
interrupt
really
quick.
I
just
wanna
make
sure
that
there's
that
we
document
in
this
demo
that
there's
going
to
be
actually
two
different
areas
for
the
quote-unquote
articles,
like
there's
articles
right
now,
which
is
going
to
be
technical
in
nature,
right
and
then
there's
you
all
are
working
on
like
the
company
announcement
section,
which
is
kind
of
like
more
information
from
the
company.
B
A
Got
it
so
I'd
like
to
be
careful
with
committing
to
specific
things
here,
so
we
are.
We
have
noticed
that
announcements
are
are
tricky
right
and
that
they
are
aren't
always
received
well,
so
we're
currently
researching
with
our
users
and
how
we
could
make
it
work,
whether
it's
a
different
section,
whether
it's
highlighted
different,
whether
it
does
or
does
not
have
votes
right
there,
there's
things
that
we
have
to
figure
out
there,
but
we
do
see
like
the
source
of
all
of
it
should
be
that
it's
useful
to
the
user.
A
So
even
if
we
make
a
different
section,
if
we
even
if
we
remove
voting
even
all
of
that,
we
can
do
all
of
that.
But
if
it's
not
useful
to
the
user,
then
it
will
not
go
over
well
right.
So
we
we're
in
the
middle
of
the
process
of
researching
how
this
would
look
like.
I
don't
know
what
the
solution
is
for
that,
but
it
is
something
that
we're
we're
looking
into.
Does
that
make
sense,
or
does
that
answer
the
question.
B
Yeah,
I
know
that
makes
sense.
I
know
that
originally
announcements
were
part
of
articles
and
then
your
team
said,
like
you
know,
that's
based
on
the
community
feedback
yeah.
We
should
probably
like
separate
this
out,
but
that
the
announcement
section
hasn't
really
been
defined
yet
so
currently
within
articles,
we
would
just
make
the
articles
in
like
technical
in
nature.
However,
the
announcement
side
of
things
is
something
that
we
may
have
the
ability
to
do
later.
As
we're
like
I'll
use.
B
Example,
we
have
a
big
user
conference
coming
up
and
it's
actually
this
week
holy
smokes,
but
that's
something
that
we
want
to
like
communicate
to
the
community.
It's
like
hey.
This
is
coming
up
within
our
collective
itself.
A
Yeah,
no,
that
that
makes
perfect,
perfect
sense
and
again,
I
think
you
hit
the
nail
on
the
head
with
like
we
got
this
feedback
from
the
community
with
this
initial
article,
which
we
also
didn't
expect
right,
but
they
were
very
strongly
opinionated
about.
Like
don't
do
this
to
us,
we
don't
want
this
fair.
A
We
moved,
we
moved
away
for
it,
we'll
we'll
talk
with
our
users,
we'll
see
what
can
work,
how
we
could
split
this
up
to
make
sure
that
it
is
useful
for
them,
but
we
see
this
this
use
case
being
useful
for
a
particular
group
of
users
and
definitely
for
organizations,
so
we
just
have
to
figure
out
how
this
works.
A
Cool
one
thing
that
I
would
like
to
highlight
specifically
about
an
article
and
I
need
an
example
for
an
article
there,
so
I'll
go
into
the
google
cloud
one
here
as
an
example,
is
the
feedback
button
right
so.
A
We
know
that,
like
content
can
go
out
of
date
right
or
can
potentially
be
outdated
or
incorrect,
or
we
basically
want
to
make
sure
that
users
can
provide
feedback
to
the
author
or
authors
of
a
particular
article
right.
So
using
this
button,
they'll
see
a
model
where
they
will
be
able
to
provide
feedback
which
would
be
sent
directly
to
the
authors.
A
They
can
see
that
make
adjustments
to
the
article
and
then
mark
that
feedback
as
as
completed,
and
this
serves
the
purpose
mainly
to
make
sure
that
any
piece
of
document
doesn't
grow
still
and
gear
gets
out
of
date
right
and
becomes
useless
useless
to
the
user.
So
this
feedback
is
like
kind
of
our
way
to
make
sure
that,
similar
to
to
q,
a
content
remains
up
to
date
and
fresh
and
useful
useful
to
the
users
without.
B
A
To
allow
all
stack
overflow
users
to
be
able
to
to
edit
the
article.
B
Can
ask
a
question
about
that?
As
far
as
far
as
like
the
management
of
say
that
somebody
comes
in
and
says
it
gets
feedback
hey
this
article
needs
to
be
corrected
right,
but
that
the
author
has
like
doesn't
make
any
movement
on
it.
There's
no
changes.
So
how
does
that
work
with,
like
the
admins
like?
How
do
we
address
things
like
that?.
B
Right,
so
maybe
I'm
misunderstanding
your
comments,
so
when
somebody
gives
feedback
does
that
feedback
go
to
the
admin
or
does
that
go
to
the
author.
A
To
the
authors
right,
so
it's
it's
a
collaborative
effort
to
try.
B
A
To
write
an
article
so
at
that,
actually
that
that
ties
in
very
well
and
then
the
point
that
I
wanted
to
make
after
is
that
an
article
is
created
by
a
user
and
they
can
invite
other
recognized
members
to
to
to
collaborate
on
the
article
and
to
help
edit
them
admins
by
default
are
always
included
in
that
right.
A
So
we
don't
expect
admins
to
write
a
lot
of
content
because
usually
they're
more
like
on
the
management
of
the
collective
side
of
the
of
the
business,
but
they're
always
able
to
enter,
see,
see
any
type
of
feedback
and
potentially
reach
out
to
a
user
to
ask
them
to
to
update
it.
If
nothing
happens,.
B
Got
it
so
for
clarity
using
the
scenario
there's
there's
an
article,
that's
written
by
an
author
admins
are
notified
about
it
and
then
once
feedback
comes
in
that
gets
that
notification
gets
pushed
out
to
the
admins
plus
the
author.
If
there's
no,
if
there's
no
movement,
then
the
admin
can
take
action,
correct,
correct,
correct!
Okay,
thank
you.
C
How
does
stack
overflow
currently
manage
outdated
answers
to
questions
or
outdated
questions.
A
It's
it's
a
very
good
good
question,
so
the
the
most
basic
answer
there
is
that
any
user
with
a
certain
point
amount
of
reputation,
is
able
to
edit
an
answer
and
a
question
right.
So
content
doesn't
live
on
the
user,
but
lives
on
on
stackoverflow.
So
whenever
somebody
goes
in
and
finds
something
outdated,
they
can
edit
it.
They
can
make
a
comment.
They
can
do
all
of
that.
So
it's
already
a
living
and
breathing
document
because
of
the
community
effort
of
like
millions
of
users
editing
stuff.
A
This
is
definitely
not
enough.
Yet
we
do
see
some
content,
something
sometimes
becoming
outdated
and
that
actually
ties
into
the
question
that
you
asked
earlier
right
about
the
sorting.
A
We
know
that
sometimes
an
answer
that
it
might
be
outdated
is
sorted
at
the
top,
and
that
is
like
the
core
of
our
of
our
public
platform
team
is
to
figure
out
to
again
make
potential
users
vote
for
this
being
outdated
and
that
it
goes
into
queue,
so
somebody
can
update
it
so
the
majority
of
shortened
around
so
the
majority
is
done
by
the
community
itself.
A
A
Of
course,
let's
see
my
notes,
whether
I
missed
anything
about
articles,
I
think
that's,
that's
it
so
move
on
to
the
next
tab,
which
is
the
the
members
tab
so
currently,
obviously
fairly
empty,
because
the
gitlab
collective
is
only
viewable
to
a
couple
of
employees
and
the
the
people
that
matt
sent
me
will
be
will
be
added
this
week.
A
So
you
can
start
like
seeding
it
and
looking
in
and
playing
around
a
bit,
but
the
members
tab
is
the
tab
that
all
users
can
see
and
all
users
that
join
a
particular
collective,
as
I'm
I'm
joined
now
will
be,
will
be
sorted
on
on
the
leaderboard,
based
on
the
reputation
that
they
gained
in
the
last
seven
days
last
30
days
or
last
last
12
months,
and
one
is
essential
element
of
stack
overflow
is
the
gamification
right.
A
These
reputation
points
are
extremely
valuable
to
our
users
and
they're,
really
something
that
they
put
a
lot
of
value
behind
so
and-
and
that's
all
like,
I'm
guess
there
are
a
lot
of
psychologists
that
can
speak
a
lot
better
to
this
than
than
I
am,
but
this
like
game
element
and
making
sure
that
you
get
at
the
top
that
you
should
show
your
knowledge
about.
A
particular
subject
is
essential
for
them
to
contribute
hours
and
hours
of
work
and
adding
content
without
anything
else
in
return,
except
for
a
reputation.
A
So
this
leaderboard
will
be
gitlab
specific
right
for
their
contribution
to
to
the
gitlab
collective
and
if
they
get
into
a
like
into
the
top
three
of
a
particular
last
seven
days,
they'll
get
this
user
trophy
gold,
silver
bronze
on
their
user
card
on
any
gitlab
content
that
they
that
they
post
to
kind
of
showcase
their
their
knowledge.
On
the
on
the
question
page
and
showcase
that
they
have
been
on
the
on
the
top
of
the
of
the
gitlab
leaderboard.
A
I
think
a
second
aspect
that
I
would
like
to
highlight
from
this
page
is
the
fact
that,
when
you
get
beyond
the
fact
of,
like
only
having
gitlab
employees
being
part
of
the
recognized
member
pool
and
like
looking
for
a
broader
community
to
be
added,
this
would
be
a
great
place
to
to
start
looking
right.
So
stackoverflow
users
like,
if
you
sort
them
on
reputation,
you'll,
probably
get
noticed
that,
like
the
people
that
have
the
highest
amount
of
reputation,
usually
have
the
highest
amount
of
knowledge
about
the
particular
subject.
D
Hey,
I
have
a
quick
question.
I'm
sorry,
I
was
on
my
headphones
and
kind
of
like
running
an
errand
at
the
beginning
of
this
meeting
or
like
how
these
you
know,
contributions
get
ranked
and
the
questions
get
sorted
is
that
all
based
on
the
tags
that
we
were
seeing
like
the
get
lab
tag
and
the
gitlab
dash
ci
tag?
Is
that
how
all
those
questions
get
pulled
in
in
the
comments,
then,
on
those
rankings.
A
Correct,
yes,
so
a
collective
is
based
on
the
on
the
grouping
of
grouping
of
tags,
we've
selected
all
the
gitlab
tags
that
we
will
were
able
to
to
find
and
made
that
into
the
into
the
gitlab
collective
and.
A
Yes
or
no,
I
think
it's
a
collaborate
effort
with
with
us
as
well,
and
probably
we
will
get
some
notifications
from
the
stackoverflow
community
as
well
about
this.
So
whenever
there
are
new
technologies,
probably
there
will
be
new
tags,
so
it
would
be
good
to
notify
us.
So
we
can,
we
can
add
it,
and
if
that
doesn't
happen,
then
probably
we
will
find
it
because
we
obviously
have
some
queries
on
the
back
end
that
look
for
them
or
the
community
will
highlight
it
that
this
is
a
technology
that
is
actually
part
of
gitlab.
A
So
probably
you
should
have
it
in
the
gitlab
case.
It's
actually
fairly
simple,
because
everything
is
marked
with
gitlab
or
gitlab
dash.
So
it's
it's
a
fairly
simple
community
to
to
create
unless.
A
Products
with
different
names,
but
I
guess
that's
on
that's
on
you,
yeah.
D
A
Yeah,
so
that
that
makes
sense,
it's
some
organizations
do
that
more
more
frequently,
but
in
in
the
case
of
gitlab,
I
I
assume
that
keeping
this
up
to
date
will
be
will
be
fairly
simple.
A
That's
that's,
that's
an
edit
that
will
will
be
live.
I
guess
tomorrow
we're
changing
that
into
a
git
gitlab
icon,
linking
to
your
gitlab
gitlab
page
that
that
matt
provided.
A
A
Cool
and
then
last
is
the
is
the
tags
page
like
we
just
discussed.
The
collective
is
based
on
on
a
series
of
tags.
Users
can
find
all
these
tags
here,
so
they
know
what
what
a
collective
is
about.
A
So
that
was
it
for
all
views
that
are
available
for
for
users
I'll
go
into
the
actions
for
you
page
now,
which
is
available
for
recognized
members
and
admins
and
is
specifically
targeted
to
recognize
members
right
and
the
thought
process
here
is
like
imagine
as
an
employee
or
somebody
from
the
developer
recognition
program.
You
have
half
an
hour
one
hour
to
spare.
A
What
is
the
place
where
you
can
make
where
you
can
go
in
make
and
make
the
biggest
possible
impact,
and
what
is
the
effect
of
that
impact
right
so
I'll
scroll
down
to
the
bottom
here
and,
as
you
can
see
here,
there's
two
question
lists
of
like
what
are
the
best
opportunities
for
engagement
right.
So
here
are
questions
that
need
an
answer
that
have
a
lot
of
views,
but
do
not
have
an
answer
yet
and
are
more
than
more
than
30
hours.
A
So
this
is
a.
This
is
a
place
for
git
lab
to
actually
go
in
and
help
the
community
out.
So
this
particular
question
has
over
8
000
views,
but
still
didn't
get
an
get
a
particular
answer
from
from
anybody,
and
potentially
this
could
mean
that
this
problem
is
just
not
solvable
right.
However,
this
could
be
a
good
way
or
a
good
moment
for
for
gitlab
employees
or
somebody
affiliated
to
go
in
and
almost
lift
the
curtains
a
bit
right
to
showcase.
Okay.
A
This
is
not
possible
with
version
x
and
y,
however,
in
version
the
next
version.
This
is
something
you
can
solve
in
this,
and
this
way
right,
so
maybe
knowledge
that
not
the
overall
stackoverflow
community
has,
but
it
is
something
that
gitlab
potentially
internally
has
knowledge
about
and
could
help
a
lot
of
users
out
because
clearly,
like
with
eight
thousand
views.
This
is
something
that
is
searched
a
lot
by
by
the
stackoverflow
users.
A
It
could
also
potentially
be
that
just
nobody
knew
and
there
is
an
answer
and
that
gitlab
employees
could
potentially
help
out.
There
are
some
filters
here
where
you
can
filter
these
lists
on
a
particular
tag.
So
if
you're
particularly
knowledgeable
about
gitlab
ci,
for
example,
filter
it
on
that,
and
you
can
sort
make
sure
that
you
only
answer
those
questions.
A
And
here
are,
is
a
list
of
questions
that
have
a
lot
of
views,
have
a
lot
of
answers,
but
do
not
have
a
recommendation
yet
and
tying
it
back
to
the
story
that
I
was
mentioning
it
being
that
for
users,
it's
frequently
difficult
to
figure
out
among
several
answers.
What
the
best
possible
answer
is.
This
is
a
great
place
to
go
in
and
potentially
recommend
an
answer
right,
so
go
and
see
which
answers
are
given
and
see
which,
from
a
gitlab
perspective,
is
the
best
possible
way
of
solving
it.
A
I'm
marking
that,
with
with
the
recommended
answer.
A
So
scrolling
up
here
a
bit
you've
got
three
charts
here.
First
of
all,
I'll
start
at
the
top
left
the
ons,
the
average
response
rate.
So
the
average
response
rate
is
the
percentage
of
questions
that
get
a
answer
within
24
hours
right.
So
somebody
post,
something
and
within
24
hours
was,
did
somebody
get
a
response
from
from
anybody
there?
A
So
the
answer
rate
is
fairly
similar.
However,
this
also
adds
a
layer
of
validation
to
to
the
equation.
So
this
would
be
the
amount
of
questions
that
get
a
answer
within
24
hours
that
gets
validated
and
the
validation
would
be
somebody
else.
The
the
question
answer
accepted
it
as
being
an
answer
that
helped
for
them,
or
it
got
upvoted
by
a
third
party
being
another
user.
Looking
into
the
answer
and
say:
okay,
this
is
good
and
added
this,
like
a
third-party
validation
to
the
to
the
answer.
A
And
at
the
top,
we've
got
a
list
of
activities
that
we
find
and
again
this
is
ballpark.
We
fairly
really
recently
launched
it,
but
this
is
what
we
think
that
if
you
want
to
make
sure
that
the
collectives
remain
sustainable
and
adds
enough
value
to
the
to
the
overall
stack
overflow
community.
A
These
are
the
activities
that
should
be
all
done
by
the
group
of
recognized
members
within
a
week.
So
answering
10
questions
recommending
20
answers
and
writing
to
two
articles
and
these.
Basically,
these
bars
will
fill
up
as
all
the
recognized
members
within
the
collective
start
to
start
making
those
activities
we'll
probably
adjust
these
numbers
as
we
go
along.
A
A
Cool
then
I'll
move
on
to
the
admin
section.
This
is
only
available
for
admins
right.
I
want
to
clarify.
Maybe
that
wasn't
clear
enough
at
the
beginning
is
that,
from
from
a
permission
standpoint
we
have
two
labels.
One
is
admin,
and
one
is
recognized.
A
Recognized
member,
the
employee
part
is
just
a
label,
it
doesn't
add
you
any
additional
capabilities
than
you've
had
with
your
with
the
permission
level
that
you
that
you
already
have,
but
it's
just
like
the
metadata
to
the
user
that
that
qualifies
so
an
admin
admin
could
be
an
employee.
A
recognized
member
could
be
an
employee.
That's
that's
all
fine,
it's
just
a
visual
representation
of
their
relationship
to
the
to
the
organization.
A
So
talking
about
how
to
add
recognized
members,
this
is
a
place
where
you
can
do
so.
You
can
invite
new
members
here.
You
can
go
to
the
members
profile
page
and
invite
them
to
the
to
the
particular
collective
and,
like
basically
see
which
users
that
are
already
members
could
could
be
a
good
fit
and
make
them
make
them
part.
A
A
A
What
you
mean
yes,
yeah
yeah,
that's
that's
being
adjusted!
So
we've
we've
noticed
that
that
doesn't
make
sense
to
to
put
git
up
there.
A
So
the
last
piece
is
the
reporting
section
that
I
wanna
that
I
wanna
highlight.
So
we
know
that
aztec
overflow,
we
sit
on
the
wealth
of
data
about
basically
all
developers
in
the
in
the
world
and
specifically
the
gitlab
gate
lab
developers
right.
So
the
this
is
the
data
that
we
will
be
able
to
to
provide
you.
A
So
you
can
make
informed
decisions
on
like
to
actually
figure
out
how
the
overall
community
is
doing
or
how
the
collective
is
doing,
how
that
is
doing
over
time
and
what
what
the
potential
pain
points
of
the
users
are,
and
we've
created
these
reports
in
three
different
types:
a
user,
an
activity
and
a
health
report.
A
A
Creating
that
report
will
give
you
a
good
idea
of
like
the
overall
size
of
the
of
the
gitlab
collective
on
on
stack
overflow
and
also
add
the
possibility
to
add
tags
to
the
equation,
which
will
allow
you
to
create
to
figure
out
what
the
potential
like
big
pain
points
are
of
of
the
users
and
where
the
majority
of
the
users
are.
A
Then
we've
got
the
activity
report
which
looks
at
it
from
everything
from
from
a
content
lens
right.
So
what
is
the
total?
What
is
the
new
total
amount
of
new
questions
that
have
been
posted?
What
is
the
total
amount
of
new
answers?
New
new
unanswered
questions.
What
are
what
is
this
percentage-wise
done
by
the
recognized
members
and
the
employees
right?
So
what
is
your
contribution
compared
to
the
overall
stack
overflow
community
contribution
within
the
the
gitlab
collective
again?
A
This
can
be
segmented
by
by
date
and
tags,
and
specifically,
here
tags
are
really
valuable
to
figure
out.
So
what
is
this
particular
sub-subject
that
have
has
a
lot
of
new
unanswered
questions
and
potentially
desk
could
be
a
place
where
you
can
find
somebody
that
could
help
out
and
answer
some
questions
to
make
sure
that
this
knowledge
is
is
shared
with
the
overall
community.
A
And
I
think
that's
it
from
my
end,
any
questions.
B
I
don't
know
if
it's
like
a
specific
question.
Maybe
it
is
just
more
for
our
team.
There
isn't,
john
and
and
jamie.
I
know
that
we
talked
about
notifications
right,
so
how
recognized
members
admins
get
notifications
on
if
things
are
pending,
whether
or
not
we
noted
that
there's
currently
not
a
notification
functionality,
we
just
have
to
log
in
and
see
that
information.
However,
there
is
an
api
that
we
can
use
from
from
stackoverflow
that
we
can
connect
to.
B
So
we
can
create
a
dashboard
with
an
api
to
look
at
the
health
of
our
collective.
So
I'm
just
curious
if
you
think
something
like
that
would
be
helpful.
I
know
it's
like
kind
of
like
a
workaround
notification
thing,
but
I
think
that's
something
we
should
move
forward
with
or
look
into.
B
For
our
our
team
to
get
that
team,
but
maybe
specifically
to
john
and
jamie,
because
it
was
a
conversation
we
had,
I
think
a
week
or
two
ago.
D
A
So
I
think
maybe
it
would
be
worthwhile
if
we
could
set
up
a
call,
because
I
think
it
depends
a
bit
on
the
use
case
that
you
want,
but
I
think
these
type
of
things
could
be
could
be
possible
all
right
so
with
the
api
you'll
be
able
to
pull
all
apple
in
all
the
questions,
all
the
answers,
all
the
the
data
right.
So
the
pages
all
of
that
stuff.
You
can
pull
that
in
and
you
can
also
post
stuff
right
so
potential.
I'm
not
sure
how
your.
D
D
When
there's
a
new
comment
or
post
with
the
word
gitlab
in
it
that
gets
pushed
into
a
slack
channel
with
reddit
and
our
forum,
we
can
have
the
forums
with
discourse.
We
can
have
like
different
notification
settings
that
come
through
email.
Normally,
it's
like
a
digest
and
then
you
know
we
get
immediate
notifications
when
someone
requires
one
of
our
comments
so
having
something
like
that
that
gets
pushed
to
us
rather
than
us
having
to
go
pull
the
information
is
what.
A
A
Got
it,
I
think
something
like
that
would
be
would
be
possible,
but
we
need
to.
We
need
to
check
with
with
the
dev
that
created
the
api.
So
if
you're
willing
we
can,
we
can
set
up
a
call
and
discuss
specifically
that
and
see
how
that
could
work
out,
because
I
think
this
should
be
possible.
At
least
we
we
in
our
slack
channel
do
have
like
notifications
going
on
whenever
particular
things
on
stackover
happens.
So
I'm
I
would
assume
that
this
should
be
possible
for
you
as
well.
Yeah.
D
And
the
functionality
could
also
live.
You
know,
maybe
even
outside
of
collectives.
Like
I
don't
know,
I'm
not
a
super
user
of
stack
overflow,
but
if
there's
a
way
to
you
know
subscribe
to
certain
tags
and
just
get
notifications
about
those
tags,
that
would
even
be
a
step
in
the
right
direction.
A
Like
subscribing
to
tags
in
general,
that
is,
that
is
possible.
You
can
subscribe
to
any
tag
on
on
stackoverflow
and
you'll
get
a.
I
think,
a
weekly
email
digest
about
those
so
that
that
functionality
definitely
exists
cool.
A
A
Cool
in
that
case,
I'll
make
sure
that
we
send
the
recording
your
way,
so
you
can
forward
it
to
anybody
in
the
in
the
team.
I
think
matt
maybe,
would
be
good
up
good
to
sync
up
on
this
api
thing
and
see
whether
we
we
want
to
set
up
a
call
and
see
what
the
capabilities
are
and
I'll
make
sure
that
the
user
that
you
send
through
will
get
access
to
to
collect,
if
I'll
make
sure
to
communicate
that
to
you
matt.
A
So
you
can
share
that
that
internally
they
will
get
a
notification
on
on
stack
overflow,
but
I
guess
it
might
be.
It
might
be
good
to
to
sync
up
through
with
with
your
team
on
that
as
well.
So
those
are
the
three
items
I
took
away
from
it
anything
else
you
wanted
to
highlight.
B
No,
I
think,
that's
it.
I
think
we're
really
close
to
getting
this
live.
I
know
I
owe
you,
though,
you
all
like
more
content,
more
article
content
and
that's
like
the
the
blocker
right
now,
but
once
we
have
that
we'll
be
good
to
go.
As
far
as
I
know,
right.
A
Yeah
correct
we're
we're
good
to
go
context
on
that
articles
piece.
We
we
did
notice
from
the
overall
community
that
the
reception
of
having
like
a
collective
that
starts
without
articles
is
fairly
like.
Why
didn't
you
put
in
some
some
effort
here?
So
we
really
want
to
avoid
that
that
situation
by
having
an
empty,
not
having
an
empty
page
when
we
launch,
so
I'm
happy
that
we
can.
A
We
can
work
on
that
that,
together
and
again,
if
you
need
anybody
from
our
team
to
look
over
it
or
see
whether
the
tone
is
is
what
our
users
are
used
to
just.
Let
us
know.
A
Cool
thanks
all-
and
I
guess
have
a
good
rest
of
your
day.