►
Description
We hosted a special meeting to discuss the External Fingerprint Storage project idea: https://jenkins.io/projects/gsoc/2020/project-ideas/external-fingerprint-storage-for-jenkins/
Meeting notes: https://docs.google.com/document/d/1T6MuuDekqToLeAOZpEJ1erh8ph9iZrkuALwXS899h-o/edit?usp=sharing
A
B
A
We
moved
it
to
the
scene
and
the
main
objective
of
this
project
is
contribute
to
the
pluggable,
so
logical
system
in
Jenkins.
Originally
it
was
a
part
of
cognitive,
special
interest
group,
so
we
reached
a
bit
so
I'm
making
Jenkins
about
negative,
or
at
least
cloud
friendly
and
one
of
the
projects
was
pluggable
storage
and
there
is
a
wider
scope
which
includes
a
number
of
errors,
and
fingerprints
is
just
one
of
these
areas.
But
fingerprints
has
a
lot
of
try.
Use
cases
talk
about
solutions,
not
just
externalizing
storage
is
probably
initial
analytics.
A
We
possibly
put
it
to
a
bigger
place
like
elastic
search.
Whatever
you
can
query
the
deity
and
visualize
it
outside
Jenkins
same
may,
apply
to
post
players
or
to
whatever
solution
and
be
interested
to
have
this
project
in
G.
So
because
it's
the
code
base
is
relatively
isolated
being
compared
to
other
pluggable
storage
stories
and
it
can
be
delivered
separately
within
days
of
entering.
So
that's
why
we
have
this
project
ID,
the
last
I
didn't
start
the
project
for
it
and
we
had
several
applications,
but
we
said
to
them.
Only
during
the
final
project.
A
A
So
yeah
the
project
is
quite
straightforward.
That
is
a
fingerprint
file.
Storage,
implementation
in
Jenkins
right
now,
historically,
Jenkins
does
everything
through
XML
storage
on
the
discs
within
jenkins,
home
and
fingerprint
storage
is
not
an
exception.
So,
right
now
everything
is
being
stored
and
xml's
before
2018
or
1988
79.
Yes,
you
had
the
performance
issues
related
to
that,
because
his
fingerprint
was
stored
as
a
separate
file.
Now
the
storage,
good
optimized,
but
still
it's
a
problem
for
my
teams.
A
A
Even
if
you
use
a
storage
command
from
volume,
you
would
rather
predict
a
database
for
it
and
that's
the
main
idea.
Also.
We
keep
one
icon
accessing
this
data,
so
if
somebody
is
interested
to
create
new
rest,
a
paragraph
Curro
support
for
existing
fingerprint
data,
for
example,
if
you
needed
tricks
articles,
it's
something
where
you
could
do
and
if
you're
interested
in
the
web
UI,
if
you're
interested
in
a
particular
security
related
area
features
like
encryption,
etc.
It's
also
could
be
on
the
table
because
there's
a
lot
of
potential
improvements,
we
could
do
so.
A
This
project
is
wide
open
and
you
can
submit
your
own
ideas
based
on
the
top
level
description
or
your
own
interest.
My
duty
is
to
discuss
the
project,
answer
the
questions
and
provide
as
much
information
as
possible,
and
if
you
want,
you
can
do
code
dives
and
whatever,
and
we
can
schedule
more
sessions.
A
So,
let's
my
goal
for
today
and
I
hope
it
provides
some
top-level
overview.
If
you
want
I
can
show
you
some
examples
of
how
our
fingerprint
the
engine
Keys
look
like.
So
one
of
the
good
examples
is
actually
doc:
traceability
Lincoln.
It's
not
a
good
example
in
terms
of
birth
status
because
of
the
plug-in
is
rather
Bunton.
Now
I
created
it
in
2015,
but
due
to
reasons
me
and
my
controller
I
had
to
move
other
more
important
projects,
but
still
it
allows
tracking
usage
of
containers
within
Jenkins.
A
So
you
can
see
that
was
terrible
so
that
the
red
container
info
and
basically
the
plug-in
allowed
men
to
Tracey
image
usages
and
continual
usages
within
Jenkins
interface,
the
more
the
more
popular
his
keys
for
that
is
actually
artifact
storage.
Because
when
you
publish
artifacts
you
can
enable
fingerprints
and
it's
a
jenkees
core
functionality.
So
many
plugins
in
Jenkins,
like
copper,
artifacts.
B
I'm
sorry,
so
the
first
question
I
have
is
so
I
just
wanted
to
confirm.
First,
two
things
in
the
proposal
there
is
this
enjoyed,
not
in
the
proposal
in
the
idea
on
the
project
idea.
It
is
mentioned
that
to
implement
new
local
storage.
Is
this
correct?
That
is
the
interpretation
of
this
correct
in
the
sense
that
we
need
to
have
the
file
storage,
as
I
said
abstracted
away,
and
you
know
is
the
same
thing:
yeah.
A
So
when
you
create
your
storage
implementation,
you
can
hard
coded
or
you
could
create
extension
points
so
for
Jenkins
in
the
default
way
is
to
pay
the
extension
points,
and
you
can
see
that
there
is
quite
a
number
of
them,
so
this
list
is
just
for
the
Jenkins
code
and
plugins
can
also
define
their
own
extension
points.
So
you
can
have
something
like,
let's
say,
a
fingerprint
storage
for
example.
A
A
What
for
EPA
provides
local
store
implementation?
We
can
get
to
it
so
one
examples.
For
example,
it's
a
credentials
provider
so
for
credentials
provider
here,
and
you
can
see
that
this
extension
point
has
several
implementations,
the
coordinators,
credential,
stolen,
etc.
And
if
you
take
a
look
at
Javadoc,
you
can
see
that
this
is
extension
point
which
basically
provides
a
number
of
methods.
Both
emotional
side
defaults,
some
of
methods,
she'll
be
actually
extended
by
implementations
and
the
Jenkins
call
up
like
in
Sector.
A
It
will
be
this
extension
points
using
API,
so
you
will
provide
an
abstraction
layer
where
you
hide
the
functionality,
the
case
of
a
fingerprint
storage.
This
abstraction
layer
is
yet
to
be
created
because
originally
it
was
just
storage
implementation.
Then
there
is
a
additional
functionality,
for
example
a
fingerprint
cleanup
and
other
bits.
So
if
you
look
at
the
current
fingerprint
quarter
in
Jenkins,
it's
a
bit
scattered
and
the
factoring
of
Wheaton
freaky
abstraction
layer
would
be
one
step,
and
then
you
can
reuse
a
filing
system,
fingerprint
storage
as
a
first
reference
implementation.
A
If
you're
interested,
we
had
several
project
which
Smith
already
referenced
is
about
log
storage.
If
we
go
to
the
previous
page,
you
can
see
that
there
was
a
number
of
jobs
submitted,
so
we
implemented
it
for
pipeline.
It
was
just
the
face,
so
Jessie
was
working
on
and
that
big
stash
for
pipeline.
So
this
one
is
delivered
under
plugins
easily,
but
we
also
wanted
to
expand
it
into
the
Jenkins
code.
A
A
In
such
case
you
can
have
common
functionality
for
converting
a
big
to
JSON
and
we
could
put
it
to
the
API
level,
and
that
was
also
core
functionality
which
basically
provided
this
extension
points.
So
here,
if
you
take
a
look,
you
can
find
yeah.
This
pull
request
is
weak
and
actually
this
boot
across
was
feature
complete.
So
it
wasn't
in
delivered
just
because
there
were
some
design
concerns
and
then
we
had
to
move
on
to
another
task.
A
A
So
one
of
the
things,
the
other
day
is
look
storage,
yeah
log
storages
in
if
it's
in
workflow
appearing
so
I
yeah.
But
this
lock
storage
is
different
because
so
having
pipeline
was
so
the
first
step.
But
python
is
just
a
symbol,
type
and
pipeline
western
dress,
with
kisses,
for
example,
for
freestyle
jobs
like
matrix
configuration,
etc.
It
doesn't
address
kisses
for
system
login
or
agent,
provisioning
and
other
bits
so
for
the
second
phase
was
to
actually
provide
a
more
complex
solution
right
inside
the
genius.
A
Until
today
it
was
pipeline
so
yeah
you
can
take
a
look
at
block,
storage,
implementation
and
5-time,
but
I
was
just
showing
you
this
hold,
because
it
shows
what
changes
in
Jenga
score.
If
you
want
to
do
that,
for
example,
there
was
API
for
built
this
all
this
okay,
so
that
is
run.
So
it's
a
common
entity
which
can
represent
any
Jenkins
build,
and
here
you
can
see
that
there
are
some
EP
is
just.
A
Common
keys
is
like
just
the
covering
storages,
etc
and
also
we
needed
to
customize
log
storage,
because
our
design
decision
there
was
to
support
multiple
locks
for
use
on
build
pages.
So,
for
example,
you
could
keep
historical
builds
in
a
file
system
or
you
could
to
keep
in
built
in
the
new
system
or
in
arbitrary
system.
If
you
wish
so
it
would,
it
was
our
approach
to
editing
innovation
concern,
because
if
you
just
decide
in
your
project
proposal
to
have
single
storage,
then
you
don't
have
to
resolve
when
a
communication.
Here
we
approached
differently.
A
We
decided
that
okay,
we
will
just
about
our
little
establish
and
it
won't
be
our
problem
to
emigrate.
After
that,
and
maybe
also
some
changes
in
AP
is
so
you
can
see
that
better
changes
here
and
there,
because
the
implementation
was
relied
on
file,
a
system
approach
eternally.
So
there
was
method
like
get
log
file
right
in
the
run,
and
it
presumes
that
there
is
a
file
and
file
system.
A
So
very
we
added
some
compatibility
layers,
but
for
the
most
of
implementations
we
introduce
new
efficient
layers
we
shouldn't
plate
which
don't
require
creation
of
temporary
files
when
it's
not
needed.
So
that
was
what
was
done
for
implementation
and
all
the
abstraction
layer
was
happening
through
two
compliments:
one
was
a
locked
storage,
so
here,
lock,
storage
is
just
the
extra
class
which
which
provides
common
methods
so,
for
example,
the
task
listeners
which
provides
streaming
Cody,
Dean,
Jenkins
and
some
decoration
project,
which
would
allow
to
externalize
slogan.
A
Because
for
beautiful
thing
we
wanted
to
do
submissions
right
from
the
agents
Jenkins,
but
yeah.
This
is
deal.
So
this
is
a
main
abstraction
there
and
we
said
that
already
tails
just
go
to
implementations,
so
Jenkins
God
doesn't
have
any
implementation
for
them
except
file
storage,
and
you
can
also
see
that
there
is
another
class
which
is
locked
storage
factor.
So
in
this
case
we
made
a
design
decision
to
make
a
log
storage
factory
an
extension
point.
A
So
there
is
a
producer
class
which
can
be
configured
and
I
built
which
produces
your
log
storage,
but
we
created
the
producer,
an
extension
point
just
because
it
was
more
easier
from
EPA
perspective
for
fingerprint
storage.
The
design
is
up
to
use
and
it
can
be
treated
using
the
trust
phrases.
So
you
don't
have
to
create
a
final
design
right
now,
but
keep
in
mind
that
factory
abstractions
and
other
common
abstractions
from
object
oriented
problem
program.
It
could
be
also
applied
here.
A
So
yeah
this
is
lock,
storage
and
basically,
fingerprint
storage
could
be
quite
similar
in
terms
of
implementation
and,
if
you
do
it
in
Jake
this
code,
so
you
can
just
take
a
look
at
the
job.
I
was
referencing
and
it
provides
some
information
about
how
it
was
done
and
they
evening
outs
take
a
look
at
the
API
plugins.
A
These
plugins
are
other
prototypes,
just
reference
implementations,
which
show
how
it
could
be
used
so
do
not
kind
a
final
solution,
but
if
you
want
to
you
can
actually
them
so
I
hope
it
summarizes
how
to
work
it's
actually
and
by
phases.
If
we
return
to
the
proposal
yeah
my
expectation
that
there
is
a
new
extension
point
for
sure
so
that
everything
else
can
be
infinite
externally,
we
don't
look
forward
to
adding
more
dependences
into
the
Jenkins
core.
A
We
try
to
avoid
it
as
much
as
possible,
so
we
hope
that
all
the
new
implementations
could
be
done
as
against
the
equated
with
plugins
is
the
most.
They
will
be
basically
happening
in
parallel,
so
you
can
design.
Ep
is
an
extension
points
on
parallel.
We
introduce
some
tooling
for
it
example
in
case
Jenkins.
Couldn't
the
motor
test
better,
so
you
don't
commit
to
Oh
binary
compatibility,
even
if
you
went
code
earlier
so
you
will
be
able
to
devote
this
plug-in
side
of
this
curve.
Changes.
A
They
can
run
in
parallel,
just
not
how
we
approach
our
g-shock
projects.
We
want
components
to
be
changed
and
integrated
into
master
branch,
so
we
don't
want
to
have
a
JSOC
project
which
basically
has
a
long-standing
request
for
three
months
four
months
and
then
something
happens
if
it's
possible
to
break
down
the
project
and
to
deliver
things
incrementally
to
the
main
code
base.
We
recommend
this
approach.
It
shows
to
be
much
more
efficient
and
that's
how
we
develop
Jenkins,
so
it
also
changes
some
up
for
overture.
A
A
B
A
But
so
it's
difficult
to
design
a
boutique
here
from
the
first
approach.
That's
why,
when
we
started
doing
major,
it's
actually
changes
around
2014-15.
We
added
some
tool
and
then
this
student
was
extended.
So
now
it's
possible
to
just
click.
Beta
ap
is
the
great
man
without
committing
to
binary
compatibility,
which
is
a
big
bada
around
becomes
product
test,
but
and
you
can
also
incremental
a
little
changes.
A
A
A
I'm
not
sure
what
happened
to
in
this
session,
so
you
can
see
that
there
are
URLs,
but
so
basically
it
should
be
published
with
the
ID.
But
then
you
didn't
control.
So
maybe
something
went
wrong
to
this
deployment,
but
in
principle
for
every
food
request
and
follow
rebuilt
in
range,
it
should
be
getting
a
version
which
you
consume
them
can
consume
in
your
plugin,
so
you
can
really
do
development
in
parallel.
This
using
the
Jenkins
share,
infrastructure
and
other
needs,
and
you
can
do
development
picture.
A
B
A
A
Okay,
so
here
we
keep
and
see
the
structure
of
fetching
the
paint,
but
one
way
and
I
think
hey
that
fingerprint
ID
consists
of
faces,
so
it
contains
a
list
of
faces
and
each
face.
It
is
basically
an
object
structure
which
is
provided
by
plugins
or
by
a
jinkies
code,
and
it
doesn't
have
fixed
strategy,
doesn't
have
schema
so,
for
example,
if
you
just
wanted
to
create
a
table
in
SQL
database,
it
might
be
a
challenge
for
you,
because
we
have.
This
strategy
is
not
normalized
in
any
way.
A
It's
just
an
object
and
we
use
a
library
extreme
to
satirize.
This
object
to
the
disk.
So
one
of
the
potential
challenges
in
this
project
is
how
to
service
it
to
databases.
If
you
use
database,
especially
if
you
still
want
to
access
this
data
for
whatever
analytics
yeah,
it's
a
nice
challenge
and
you
can
come
up
with
a
solution
but
yeah
what
I
mean
here
that
you
cannot
really
rely
on
regular
data
structure,
which
sometimes
common
for
databases.
B
Yes,
actually
that's
what
I've
been
thinking
because
I
mean
either,
if
I'm,
storing
an
XML
file
in
a
storage
that
kids
I
mean
if
I
store
it
directly
as
examine.
Not
only
do
I
have
a
memory
overhead,
but
also
then
I
have
the
problem
of
maintaining
consistency,
because
if
some
other
Jenkins
instanced
reads
it
after
I
have
read
it
and
tries
to
access
it
either.
B
A
Multiple
Jenkins
instance
succession
on
the
same
database.
It's
a
use
case
for
yoo
jae-seok
application.
I
have
a
choice
whether
you
want
to
support
it
or
not,
because
that
is
definitely
benefits
for
that,
especially
when
we
talk
about
large-scale
jenkins
instances,
which
includes
hundreds,
hundreds
of
masters
put
in
called
the
leading
to
the
same
database,
would
really
make
sense
and
ya,
know
betaf
and
then
build
the
challenge
for
you,
though,
in
current
idk
disease
allow
result
in
beta.
That
is
over
to
be
a
lot
of
functionality.
A
As
long
as
you
do
not
try
to
trace
the
same
artifact,
then
yes,
you
will
have
to
have
proper
EPS
and
you
put
at
some
logic
on
the
database
side,
but
still
you
would
need
to
figure
out
a
way
how
to
handle
it
in
Genki
ck,
because
you
need
to
amend
fingerprint
story
sheet
to
make
sure
that
it's
not
a
problem
of
the
Jenkins
core.
It's
a
problem
of
liking
which
talks
to
a
database
or
whatever
and
uses
specific
functionality.
I.
B
A
So
good,
no,
so
that
you
don't
have
to
provide
the
production
ready
implementation.
This
all
features
a
bit
your
step
again,
you
could
start
from
prototype
from
alpha
version
for
the
plugin,
which
provides
some
features
and
be
our
advice
is
to
have
alpha
leaders
early
to
get
some
community
feedback,
and
then
you
can
do
from
the
top
of
it
and
for
me,
even
if
the
result
of
your
project
is
a
API
in
jenkins
core
and
reference
implementation
which
works
but
which
has
some
documented
mutations.
A
A
Okay,
so
speaking
of
face
it's
another
beat.
So
if
you're
concerned
about
storing
text
and
notes
to
disk,
there
is
actually
an
another
approach.
For
example,
you
could
just
use
Globes,
because
Jenkins
includes
its
own
data
serialization
of
an
engine.
We
have
a
remote
in
protocol
which
their
master
in
communication
and
it
uses
object
serialization,
and
for
that
there
is
an
engine
and
Jenkins.
A
B
So
the
other
option
was
obviously
then
I
go
for
a
relational
approach
and
break
it
down
and
have
it
into
tables.
But
even
that
is
not
a
straightforward
solution,
because
even
that
involves
that
I
have
to
know
when
changes.
What
changes
have
happened
without
that,
so
I
mean
what
I
was
trying
was
I
didn't
want
to
touch
the
fingerprint
class
as
much,
but
I
think
this
is
going
to
ultimately
I
mean
I,
can't
think
of
a
way
that
I
achieved
this
without
touching
it
so
yeah.
A
Yeah,
it's
technically
possible,
so
finger
length
is
just
an
abstraction
layer
right
now,
Jenkins.
Well,
to
be
honest,
this
abstraction
is
sneaky
because
it
references
file
system
and
vice
versa,
but
still
that
is
abstraction
where
we
could
use
I
mean
if
you
want
to
do
the
generational
structure
for
some
components
as
possible,
because
for
artifacts
for
other
deployment
phases,
other
classes
right
inside
Jenkins
code.
A
So
you
could
try
to
do
relational
sludge
that
if
it
helps
and
if
you
build
the
it
mayor,
might
be
difficult
ly
helpful
for
getting
information
about
these
artifacts
for
tracing
cookware,
including
from
the
storage
shop
from
the
drink
inside.
So
if
you
do
that,
it
would
be
definitely
a
nice
addition.
At
the
same
time,
it
might
be
challenging
when
you
go
into
details.
For
example,
if
we
talked
about
local
traceability,
I
presented
so
here,
for
example,
dr.
A
fingerprint
trace
it,
which
basically
is
just
an
abstraction
layer,
but
the
storage
implementations
actually
include
a
lot
of
the
traceability
plug-in
because
we
just
invoke
commands
like
doctor,
inspect
and
translate
these
commands
to
the
data
structure.
So
finally,
there
is
a
lot
of
data
being
stored
and
just
handling
this
data
indexing.
This
data
in
hospice
it
might
be
challenging.
A
A
B
A
In
your
proposal,
you're
welcome
to
put
it
how
you
prefer,
for
example,
with
a
separate
section,
is
documentation,
etc.
So
just
explain
what
you
want
to
do.
It
will
be
enough.
If
you
want
to
get
feedback,
you
can
go
beyond.
For
example,
platform
special
interest
group
or
cognitive
I
see,
but
others
shouldn't
just
books
and
Jake
is
like
music
experience
and
what
you
could
do.
If
you
have
a
particular
section,
you
can
just
join
the
guitar
chat
or
sent
a
message
to
the
amenities
and
say:
hey:
I
have
a
proposal.
A
What
do
you
think
also
you
can
just
go
to
the
junkies
developer
to
manually
is
because
we
are
perfectly
fine
to
discuss
such
topics
there.
So
if
you
have
a
proposal,
which
is,
let's
say
a
part
of
your
project,
but
it's
a
part
which
can
be
done
separately,
just
feel
free
to
start
a
thread
about
that
and
I
mean,
if
you
know
we'll
get
feedback.
A
Personally,
I'm,
not
an
expert
in
UI
expression
in
terms
of
user
experience,
I
can
write
some
code
but
yeah
also
and
yesterday
we
just
had
a
blog
post,
but
it
will
have
talked
about
some
components,
so
I'm
not
sure.
Well
whether
you
have
already
seen
that
but
yeah
we
defy
the
user
interface
of
reporter
plugins,
but
basically
same
approaches
could
be
applied
to
fingerprints,
etc,
because
this
error
could
be
improved.
A
lot
on
Jenkins.
A
A
So
my
proposal
would
be
to
postpone
and
Jeff.
So
if
you
talk
about
the
formal
jab
towards
the
community,
bonding
and
recording
phase
so
right
now,
Jeff
is
a
pretty
heavy
process
and
right
now
going
through
that
might
be
time-consuming.
So,
for
me,
recommendation
is
to
do
it
during
their
project.
At
the
same
time,
if
you
have
a
proposal,
you
can
just
submit
it
as
google
dog
finish
routine.
They
can
just
cut
you
an
example
I,
so
I'm
working
on
the
road
map
for
the
Jenkins
fluid.
So
before
submitting
a
job,
I
just
started
there.
A
Many
developers
might
exist
through
and
you
can
see
link
to
the
Google
dog
so
instead
of
doing
formal,
job,
I
basically
use
the
Google
dog
to
put
the
information
I
made
it
public
variable
for
commands
have
got
some
comments
there
and
unplugs.
So
even
before
submitting
the
job,
I
get
some
feedback
from
the
community
and
use
that.
If
you
have
something
in
mind,
you
could
do
it
in
this
way.
A
A
A
A
We
have
many
projects,
central
which
are
interesting,
and
you
can
find
something
create
a
new
project
and
listen.
It's
fun.
So
project
ideas
are
just
project
ideas
yep,
for
example,
in
your
keys
sliding
if
you're
interested
since
you
work
from
Dhaka
Poland
proposal.
Maybe
you
would
be
interested
to
take
a
look
at
doctor,
fingerprints
and
doctors,
traceability
because
it's
in
the
same
area
so
yeah,
for
example,
for
you
it
might
be
an
interesting
addition
to
your
project.
Did
you
just
look
a
bit.
C
A
So
this
is
basically
sherry
traceability,
so
just
to
explain
the
history
of
this
plugin,
it
was
started
in
2015
I
just
spent
two
weeks
or
maybe
a
bit
more
naked,
so
it
was
working,
but
it
has
some
downsides
right
now.
For
example,
it
has
no
fixed
client,
so
you
have
to
use
a
REST
API
to
submit
the
data
from
external
locations.
A
Probably
it
allows
to
do
entrant
image
and
continue
to
be
searched
reckoning
within
Jenkins.
So,
for
example,
we
build
a
docker
image
using
docker
fight,
went
again
and
then
use
it
in
test
environment.
So
you
can
use
disliking
to
trace
this
usage
of
just
dismiss
cases,
for
example,
and
maybe
some
summaries
with
deployment
of
events
and
everything
is
powered
by
fingerprint
engine.
So,
for
example,
will
be
some
really
created
external
fingerprint
storage,
who
put
still
big
benefits
from
betting,
dr.
pol
and
project.
Okay.
A
B
A
Yeah
so
I
work
remotely
and
my
internal
quality
is
not
very
good,
especially
on
mornings.
You
to
reason.
I
cannot
explain,
ok,
so
what
I
wanted
to
say
that
right
now
the
project
uses
cloud
native
special
interest
group
channels,
depending
on
the
state
we
might
keep
with
disease
or
we
might
move
it
to
the
platform
special
interest
group,
which
is
much
much
so
I,
will
make
sure
that
that
is
coming
in
here
on
this
project.
A
B
A
Also,
my
recommendation
is
to
do
buffer,
so
for
jenkees
community
this
we
operate
through
Google
Doc
and
through
my
name.
Please,
because
we
want
the
discussions
to
be
as
public
as
possible
on
the
mentals
would
have
access
to
your
application
on
the
g'tok
website.
So
basically
we
don't
use
jsoc
website
for
discussions.
A
We
use
other
channels,
but
still
as
a
media
project
out
there
and
make
sense
and
because,
firstly,
we
can
see
who
is
going
to
apply
to
this
project
or
who
considers
a
bit,
and
we
can
do
some
initial
planning
plus
we
can
get
metrics
because
we
have
two
or
three
dozens
active
students
across
the
projects.
Right
now
likely
will
better
modifications.