►
From YouTube: Hands-on: Migrating user documentation to jenkins.io
Description
Mark Waite reviews the goals of the Jenkins Wiki migration project. He demonstrates the steps to collect, transform, and publish content from the Jenkins Wiki site to the Jenkins documentation site (jenkins.io). He shares the categories of information on the Wiki and how we’ve prioritized the effort to include that information in the Jenkins documentation. A page is migrated from the wiki. It identifies likely problems and discusses how contributors can resolve those problems.
The session also shows how to report your Hackfest contributions at https://github.com/jenkinsci/ui-ux-hackfest-2020/issues/new/choose .
References:
* Contributing: https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc
* Slides: https://docs.google.com/presentation/d/1fiVoDFrSNTOHsHT4cIqyOIBKYXG0q5zVn_XPue_Khkw/edit?usp=sharing
* Reporting progress: https://github.com/jenkinsci/ui-ux-hackfest-2020/issues/new/choose
A
Hello
welcome
to
the
Jenkins
urx
hug
fest.
This
is
a
day
and
we
have
a
presentation
by
Mark
about
migrating
documentation
from
Jenkins
weekly
to
Gingka,
Scion,
so
mark
will
show
how
to
negate
the
documentation,
what
tools
you
can
use
and
also
we
will
talk
about
the
development
process
forging
io
specifically
so
that
you
can
create
new
documentation
if
you
want,
if
you
have
any
questions
during
the
session,
please
just
use
zoom
Connie
and
we
will
be
giving
you
permission
so
that
you
can
ask
your
questions
during
the
session.
A
If
you
want
to
ask
questions
of
line,
we
have
two
charts
one
Archer,
this
Jenkins
hot
fest,
it's
our
chat
for
the
UI
UX
harvest
and
everyone
is
welcome
to
participate
until
May
29th.
We
welcome
all
contributors
to
join
us
and
to
start
improving.
Jenkins
are
specifically
either
pigmentation
for
Jenkins.
If
you're
interested
there
is
a
page
and
Jenkins
and
after
the
session
we
have
a
documentation
cheek
channel
anyway,
again,
you
can
ask
any
questions.
B
Let's,
let's
go
ahead
and
show
so
what
I'd
like
to
do
is
use
some
slides
to
initially
frame
an
outline,
and
then
we
can.
We
can
actually
go
through.
So
this
is
the
hackfest
and
I'm
specifically
talking
today
about
how
to
migrate
docs
to
Jenkins
dot
IO
the
goal
here.
The
agenda
here
is
to
talk
about
the
goals
of
the
migration.
Why
we're
doing
it
then
talk
briefly
about
how
to
collect,
transform
and
publish,
and
then
a
demo
and
the
mass?
The
mass
of
this
session
today
is
about
that
demo.
B
At
the
end
of
it,
I've
got
some
brief
notes
on
information
categories
and
prioritizing
migration
efforts.
We'd,
like
your
questions
to
come
throughout
the
entire
time.
All
right
don't
be
shy
about
asking
a
question:
don't
hold
it
don't
wait.
This
is
a
great
excuse
to
ask
questions.
We
intend
for
this
session
to
be
interactive,
so
questions
and
feedback
you
can
ask
them
to
resume
Q&A.
You
can
ask
them
to
the
hackfest
getter
channel.
We
also
have
hackfest
office
hours.
We
just
concluded
one
today,
we'll
have
another
session
tomorrow
and
the
following
day.
B
We
had
Doc's
office
hours
on
Monday
and
we'll
have
those
every
Monday
for
an
extended
period.
You
can
also
ask
questions
together
or
on
the
mailing
lists,
so
user
documentation
what's
the
kind
of
fundamental
concept
here.
It
is
that,
over
the
course
of
the
life
of
the
Jenkins
project,
we
have
accumulated
a
lot
of
very
good
and
very
useful
content
inside
the
Jenkins
wiki.
There
are
things
in
there
that
are
are
very
helpful
for
users,
but
that
because
the
wiki
has
been
made,
read-only
can't
be
refined
and
can't
be
improved.
B
So
we
have
a
tool-
the
wiki
exporter,
which
will
help
us
as
contributors,
take
content
from
the
wiki
export
it
and
put
it
into
a
place
where
we
can
modify
them
where
we
can
improve
them.
The
Jenkins
style
website
we're
tracking
those
with
github
issues
and
where
we've
actually
gone
through
a
prioritization
and
an
outlining
process
to
get
those
ready.
So
our
goal
here
is
get
content
to
users
so
that
they
can
benefit
from
what
we
already
know
and
what
is
already
captured
in
the
wiki.
B
So
how
do
you
choose
a
page
to
migrate?
There
are
lots
of
pages
in
the
wiki
and
I
mean
by
lots.
There
are
hundreds
that
were
accessed
in
the
last
90
days.
Well,
we've
created
github
issues
for
the
top
50
most
accessed
pages.
Those
top
50
pages
have
also
had
the
wiki
migration
label
associated
with
them
in
github,
so
that
you
can,
you
can
see
very
readily,
which
pages
to
migrate.
There
are
many
more
pages
than
just
those
top
50,
but
we
thought
we'd
start
with
the
top
50.
B
Now,
if
you're
interested
in
some
other
page,
we
also
have
a
worksheet
that
we've
used
to
prioritize
all
the
pages
and
it
shows
pages
which
have
not
been
visited
yet
for
triage.
It
shows
a
number
of
pages
which
are
plugin
pages,
where
we
may
need
to
convert
the
plug-in
documentation
to
code
all
of
those
a
great
opportunity
for
you
to
help
with
Jenkins
documentation.
B
So
it's
time
for
the
demo,
let's,
let's
look
at
what
we
do.
So
what
how
we
approach
this
and
and
why
so
I'm
gonna,
put
up
first
question
is
how
do
we
choose
a
page
okay,
so
what
I
did
is
I
didn't
want
to
collide
with
anybody
else.
So
I
went
to
the
wiki
conversion
spreadsheet
and
found
a
page
that
haven't
had
a
github
issue
assigned
to
it.
Yet
this
is
just
me
being
lazy.
I
could
have
gone
to
any
one
of
the
github
issues
and
looked
at
them
as
well.
So
I
could
look
here.
B
B
Here's
the
page
and
here's
how
it
looks
in
the
wiki.
Okay.
If
we
look
at
this
page,
we
see
that
let's
make
it
bigger
so
that
we
can
see
alright.
So
how
do
view
Jenkins
in
your
language?
First,
we
look
at
the
picture.
Oh
dear,
it's
got
the
name
Hudson
in
it,
so
it's
not
a
perfect
page
for
sure,
but
it's
got
information
here.
That
probably
will
help
people,
for
instance,
that
Jenkins
will
display
text
depending
on
language
of
the
browser.
Now
Oleg
has
the
benefit
of
not
being
a
native
English
speaker
Oleg.
B
A
B
I,
do
not
I,
do
not
read
French
either
I
speak,
I
speak
comfortably
Italian,
but
but
I
was
just
more
thinking
of
the
we're
still
able
to
do
locale.
Switching
and
therefore
this
is
yes
and
thank
you.
Damien
of
all
people,
my
friend
Damien,
deport
I'll
just
commented
that
no
one
can
read
French
thanks
Damien.
We
appreciate
that.
That's
really
great,
certainly
I
cannot
speak
French,
but
this
page
makes
an
interesting
choice
of
a
page
that
we
might
translate
and
might
might
convert
from
the
wiki
page
into
a
page
on
Jenkins
Tadeo.
B
So
we
pick
the
page
the
from
page.
Now
we
need
to
find
the
okay.
Where
should
it
go?
Okay?
So,
let's
see
it's
probably
not
installing?
Maybe
it
should
go
under
using
and
we
say
hey
what,
if
it's
using
Jenkins
with
a
separate
language,
yeah
that
might
be
right
might
be
a
reasonable
place.
To
put
it
so,
we've
got
using
Jenkins
using
credentials
of
boarding
a
build
and
fingerprints.
We
might
put
a
new
section
here
which
says
this
is
how
to
use
another
language.
B
So,
let's,
let's
take
that
as
our
begin
point,
so
we're
going
to
go
from
this
page,
how
to
view
Jenkins
in
your
language
to
the
using
Jenkins
page
here
and
to
do
that
we
need
to
get
something
that
will
let
us
convert
this
old
page
into
the
new
page.
So
let's
go
to
the
Jenkins
wiki
exporter
and
it's
right
here.
B
Okay,
this
tool
created
by
Gavin
Magan
using
pan
doc,
will
convert
a
wiki
page,
add
a
specific
URL
into
either
markdown
or
asciidoc.
Now,
because
this
one
includes
includes
an
image,
I
could
do
asciidoc
or
asciidoc,
zip
I.
Think
for
my
sake,
I've
looked
at
this
image
and
that
image
is
not
one
that
I
actually
want
to
convert
because
I
don't
want
Hudson
in
the
in
the
page,
I
want
to
say
Jenkins,
so
I'm
just
going
to
convert
to
ASCII
dog,
so
I
click
convert
here
and
it's
going
to
go
read
the
page.
B
Now
that
was
that
was
a
pretty
easy
start
now.
I
need
a
place
to
put
it
okay
so,
and
we
said
we
were
going
to
put
it
here
in
using
Jenkins.
So
now
I'm
going
to
bring
up
my
handy
terminal,
emulator
sink
my
my
repository,
so
I
need
to
check
out
a
branch,
and
this
is
add
Jenkins
in
local
language,
so
I
like
to
name
my
branches
for
Bhosle,
so
that
I
remember
what
I'm
working
on
and
now
I'm
going
to
take
and
I
need
to
find
that
location
where
I
put
it
now.
B
You'll
notice
that
on
this
page
on
the
using
Jenkins
page,
there
is
in
the
bottom
left-hand
corner
a
link
which
says
improve
this
page.
If
I
click
improve
this
page,
it's
going
to
take
me
right
to
the
page
and
github.
So
here
is
the
page
and
github
and
for
convenience.
It's
just
given
me
the
path
to
that
page.
B
So,
hey
that's
a
help
so
improve
this
page
took
me
right
to
where
I
need
to
go.
So,
if
I
look
at
that
in
my
repository
there,
it
is
and
now
to
add
a
new
page
in
that
section.
I
bring
up
this
file
content
dot
using
I'm,
going
to
put
in
the
chapter
llamo
file
and
then
I'm
going
to
create
a
new
page
content
doc
book
using
and
what
did
we
decide?
We
would
call
it
it's
using
local
language.
B
A
B
One
main
I,
if
I
work
really
deeply
into
it.
It
probably
would
eyes
in
my
case,
I
found
it.
The
color
highlighting
is
already
enough
to
help
me
I
suspected
it,
given
that
it
has
almost
everything
in
the
kitchen
sink
in
it.
It
probably
does
alright
so
and
usually
as
here's
a
good
example
of
one
of
the
things.
For
instance,
we
don't
really
want
to
refer
to
the
wiki
when
we're
talking
about
the
locale
plug-in,
so
we
say
plugin,
:,
locale,.
B
So
here
I've
captured
it
now.
What
I
don't
have
is
the
asciidoc
headings
and
headings
and
footer
information
so
for
that
I
usually
just
go
borrow
from
a
neighbor
file.
So
if
I
borrow
from
using
credentials,
I
can
grab.
Let's
see
here's
this
section,
it
looks
like
that's
the
usual
thing
and
it
starts
with
a
level
1
head.
B
B
And
now
I
was
reminded
here
one
of
the
things
that's
that
I've
had
to
make
a
change
in
the
past
was
whenever
I
find
the
word
slave
I
need
to
be
sure
and
change
to
agent
and
if
I
find
an
HTTP
URL
I
should
consider
very
carefully
if
that
shouldn't
be
an
HTTP
URL.
Many
of
these
pages
are
old
enough
that
that
they
just
don't
ok
or
in
this
case
I'm
checking
in
the
link
that
it's
referencing
is
not
not
good.
B
It
doesn't
exist
any
longer,
so
that
should
be
taken
out
and
I've
got
to
find
a
way
to
all
have
to
look
for
that
separately
after
our
session
here
to
see
hey.
Where
is
the
thing
that
I
should
refer
to?
Instead
of
that,
so
these
kinds
of
activities
are
what
we're
doing
is
we're
taking
acknowledging
that
we're
taking
a
page
that
maybe
multiple
years
old,
and
thus
we
need
to
refresh
it
and
be
sure
that
it
is
still
a
working
page
nope
so
that
that
browser
add-on
also
isn't
working.
So
another.
B
B
A
Be
able
to
run
so
in
lengths
you
can
install
new
plugins
in
the
most
of
cases.
It
will
work.
You
can
update
plugins
in
the
default
instance,
because
the
Sun
logging
is
disabled
by
default.
If
you
really
wanted
to
do
dynamic,
update
and
don't
rate
of
plugins,
it
would
be
possible,
but
it's
quite
challenging
in
Java.
A
A
B
B
B
I'm
confident,
although
that's
a
very
valid
question,
because
I
have
several,
my
raspberry
pi
is
just
an
agent
right
now,
not
a
not
a,
not
a
master
there.
We
go
ok,
so
here
we
have
it
and
if
we
scroll
down
locale
was
I
have
to
search,
don't
I
there,
we
go
default
language,
and
now
this
is
one
where
I
can
just
type
in
the
I
love
having
help
okay,
so
locale
dot.
So
it's
probably
IT
underscore
I
T
dot,
utf-8.
B
A
B
There
we
have
a
new
or
lamento
20
chronology
couple
Etzioni.
Yes,
this
this
feels
like
Italian,
wonderful,
okay,
so
we've
seen
that
okay,
that's
that's
how
it
now
I.
Probably
we
want
to
take
a
screenshot
of
this
so
that
let's
shrink
it
a
little
because
I
need
a
picture
and
this
picture,
let's
take
it
at
a
reasonable
size,
save
1152
and
let's
take
a
screenshot
that
I
can
then
embed.
All
my
poor
windows
is
very
busy,
so
take
a
screenshot.
B
A
Is
one
thing
to
keep
in
mind
that
your
current
IP
rate,
increased
user
documentation
and
user
documentation
has
a
bit
different
approach:
400
images?
Okay,
it
usually
puts
everything
in
the
resources,
but
it
was
a
hit.
It's
basically
historical
thing.
After
introducing
the
Jenkins
user
handbook,
because
the
most
of
his
a
documentation
originally
came
from
there.
So
if
you
open
other
pages
in
the
same
folder,
you
may
see
that
the
define
resources
and
images
differently
from
as.
B
Well,
as
I
should
I
should
follow
their
pattern.
So,
let's,
let's
use
that
as
my
as
a
way
to
follow
their
pattern
just
to
be
healthy,
okay,
so
this
one
doesn't.
This
may
be
the
first
image
I'm
inserting
but
I
think
you
had
said
that
there
are
other
examples
where
we've
got
it
in
the
resources,
so
it
would
be
in
this
directory.
B
B
A
B
A
Reasonable
I'm
not
sure
how
we
handle
Tata,
políticas
and
yeah
I've
gotta
mention
it
for
the
contributors.
Because
for
me,
whatever
works
you
can.
We
don't
really
build
the
user
handbook
for
it.
Now
we
could.
But
right
now
we
can
use
communal
approach
by
putting
clear
images
to
stash
images.
I
think
it
would
be
perfectly
fine.
So
it's
okay
either
your
your
that's!
A
good
point.
I
have.
B
I'm
I
am
a
very
simple
soul.
I'll
take
take
things.
I
have
tend
to
follow
existing
patterns
where
I
can
alright,
so
we
really
using
directory
and
now
I've
got
to
put
that
now.
I
admit
I'm
running
in
a
little
bit
different
environment,
because
I
do
my
development
work
on
a
Linux
box,
but
I'm
actually
seated
at
a
Windows
computer.
B
B
B
B
A
B
A
B
B
B
A
B
B
A
B
B
B
I
could
also
do
it
from
terminal
window,
and
so
what
it's
going
to
do
is
it's
going
to
start
up
a
docker
image,
read
the
files
from
my
file
system
and
start
a
running
web
browser
or
a
running
web
server
on
my
computer
on
port
4
4.
So
you'll
see
it
right
here
now.
I
could
access
that
if
I
were
sitting
on
that
Linux
computer
or
in
my
case
I
start
a
tunnel
so
that
I
can
access
it
from
my
Windows
computer
and
now
let's
bring
it
up
and
see
what
it
looks
like
so
now.
B
B
So
I
was
in
using
Jenkins
and
I
added
using
local
language
there.
It
is
and
here's
the
page
now
that
image
is
awfully
big
but
probably
workable.
I
may
need
to
resize
it
it's
got.
It
doesn't
really
have
anything
particularly
personal
in
it,
but
from
a
strategy
it
prot.
It
may
need
to
be
that
I
have
to
change
it
to
be
simpler,
cleaner,
less
about
less
mention
of
mark
weight,
less
mention
of
individual
specifics,
but
it
is
really
a
Jenkins
page,
converted
from
the
wiki
to
Jenkins
audio.
B
B
B
And
I
made
that
change
the
running
web
browser
detected
that
chain
or
the
running
running
web
server
detected
that
change.
Now,
if
I
go
back
to
that
page
and
I
reload,
that
page,
my
change
is,
is
they're
active,
so
I
didn't
have
to
stop
the
compilation
process.
I
didn't
have
to
do
anything
other
than
modify
the
file.
Is
it
always
perfect
that
way?
No,
but
many
times
it
will
work
just
great
for
you
that
way.
B
A
B
And
so
for
me,
I
like
I,
like
the
hub
command
I
could
use.
The
I
could
use
the
web
user
interface
to
create
the
pull
request.
Oleg
are
you
okay,
if
I
use
hub,
instead
of
just
as
a
show
a
different
way
to
do
it?
I
could
create
the
pull
request
just
by
committing
I
have
to
commit
the
changes
here?
No
matter
what
right.
So,
let's
commit
the
changes
and
that's
my
grade
using
local
language
from
wiki.
B
Now
I
push
that
and
I'm
lazy
I
like
to
make
it
tell
me
what
the
command
is
I
should
put
in
so
I've
pushed
that
to
my
remote
branch.
Now,
if
I
go
look
at
that-
and
it
gives
me
a
nice
hyperlink
there
if
I
go,
look
at
that,
I
can
see
right
here
that
it's
ready
to
go
and
I
could
pull
requests
right
here.
Just
by
clicking
the
create
pull
request.
B
A
B
Very
good,
okay,
so
then
I'm
just
gonna
go
ahead
and
do
it
here.
This
is
what
Moe
yes,
and
this
is
the
checkbox
that
I
saw
you
so
yesterday
in
our
Doc's
office
hours,
we
talked
about
this
particular
checkbox,
allow
edits
by
maintainer
x'.
This
will
allow
other
maintainer
x'
of
the
project
to
actually
make
changes
to
my
pull
request.
It's
an
option
that
allows
me
a
little
bit
of
extra
flexibility
if
I
said
no
I
want
complete
control
of
my
I
could
uncheck
that
good
I
finally
see
that
okay,
pull
request
created.
B
A
B
B
A
B
Thank
you,
and
now
after
this
poor
request
is,
is
approved
and
merged.
I
can
do
one
additional
thing
which
would
really
help,
which
is
create
a
submit,
a
redirect
requests
to
cause
the
original
wiki
page
to
automatically
redirect
to
the
new
page
on
Jenkins
dot
IO
that
can
help
search
engine
optimization.
It
helps
people
get
to
accurate
information
more
quickly,
yep.
A
B
We've
definitely
seen
benefits
to
using
these
redirects
in
that
it
helps
people
find
the
information
sooner
and
we
really
want
to
help
the
users
so
I'm
gonna
go
ahead
and
submit
this.
Oh,
let's
see
submit
this
issue
now.
I
probably
have
permission,
but
most
users
will
not
have
permission
to
link
to
the
pull
request,
or
will
they
see
I,
don't
I
know
what
my
provisions
are
yeah.
A
B
I
could
so
I
could
I
could
have
referenced
it
here
by
saying,
implement
or
Paul
request
is
number
and
then
I
would
put
in
that
number,
which
is
3
3
5
up
there.
It
is
3
3,
5
6
like
that
good.
Thank
you,
I've
sort
of
droned
on
on
this
demo
are
there
other
things
that
we
think
that
should
be
are
crucial
that
we
should.
B
And
for
me,
I
am
not
nearly
well
enough
practice
in
it,
so
what
Oleg
was
just
alluding
to
is
that
we've
got
this
really
cool
github
repository
that
tracks
contributions
to
this
week's
hackfest
and
we're
going
to
use
that
information
to
send
out
swag,
etc.
So
now
that
hackfest
repository
is
here
right:
Jenkins,
CI,
/,
UI,
UHU,
X,
hackfest
I
think
this
is
the
one
right
elect
yes,
okay
and
now
what
I
do
here
is
I
just
create
a
new
poll
request.
No.
B
B
Okay,
so
lengthily
related
pull
requests,
so
it
would
be
there's
the
pull
request.
I,
do
you
care
if
it
has
a
link
to
the
issue?
Pull
request
is
enough.
What
that
one
looks
okay,
great
and
this
one
doesn't.
Actually
it's
got
to
have
a
screen
shot.
We
have
to
drag
in
a
screen
shot,
so
I'm
gonna
pull
in
a
screen
shot
from
here,
Jenkins
in
Italian,
very
lovely.
A
So
it
will
be
plus
by
one
of
the
organizers
will
use
spots.
So
if
you
so
basically
you
just
process
these
reports
at
the
bomber
and,
for
example,
for
that
we
used
to
all
contributors.
So
if
you
go
to
the
booth
page
of
this
repository
mark
mm-hmm,
then
you
can
see
all
contributors
who
have
already
reported
these
contributions.
A
B
A
A
B
B
B
So
one
of
the
questions
might
be
hey.
How
do
I
know
where
to
put
things
and
for
me
the
first,
where
do
I
put
things
you're
welcome
to
just
ask
in
the
in
the
docs
getter
channel
you're,
welcome
to
do
your
own
investigation
and
propose
a
place
you're
welcome
to
suggest
it
in
your
pull
request
and
if
has
poor
review
as
pull
request
reviewers,
we
don't
feel
like
you
got
the
right
place,
we're
comfortable
telling
you
hey.
Could
you
put
it
here?
B
Instead,
it's
not
a
huge
bunch
of
work
to
put
it
in
a
different
place
after
starting
in
one
location.
Now
we
found
that
there
are
at
least
for
me,
there
are
some
general
categories:
there's
they
using
Jenkins
administering
Jenkins
and
we've
got
to
get
hub
projects
tracking
those.
Where
we're
we
had
a
longer
term
vision
to
create
two
separate
volumes
of
information,
one
for
using
and
one
for
administering
right
now,
they're
sort
of
commingled
and
we're
tracking
those
in
these
github
project
projects
that
are
linked
here.
B
B
B
I
think
that
categorization
will
help
you.
If
you
find
a
question,
go
ahead
and
just
ask
now
in
terms
of
prioritizing
the
migration,
what
should
you
work
on
I
think,
first,
choices
work
on
things
that
you
find
personally
interesting
if
you've
been
involved
with
something
you're,
much
more
likely
if
you've
used
it
before
you're
much
more
likely
to
understand
what
should
be
said
and
shouldn't,
we
said,
make
corrections,
add
value.
If
you
say:
oh
I,
don't
haven't
worked
on
any
of
those
things.
B
We
have
the
top
50
most
actively
read
pages
as
github
issues
pick
one
of
those.
If
none
of
those
look
like
they're
interesting,
you
can
actually
go
all
the
way
to
the
wiki
conversion
sheet.
That
has
two
hundred
and
fifty
see
if
I
can
find
it
two
hundred
and
fifty
or
more
pages.
Yes,
here
it
is
things
these
need
to
be
triaged.
Someone
needs
to
look
at
each
page
and
say
this
page
I
think
should
go
here.
B
C
Thank
you
very
much
alike
for
allowing
me
to
ask
thank
you,
Mark,
for
providing
this
wonderful.
Webinar
I
have
a
question
about
a
kind
of
process
about
creating
these
issues
and
pull
requests.
For
instance,
I
am
working
on
documentation
after
we
created
an
issue
of
pull
request
to
modify
a
recommendation.
Do
we
need
to
do
to
this
heck
fast,
UI
side
to
create
another
issue
track
in
our
issue
in
the
commutation?
In
case
we
already
created
initial
issue.
C
A
Is
no
need
to
attract
Anisha,
though
it
would
be
nice
if
you
could
report
chunks
of
work.
For
example,
if
you
spend
some
time
on
reviewing
particular
pages
on
trading
in
relational
pages
example
once
they
submit
it
can
issue
a
summary
of
your
work.
Why
it's
useful,
because
we
use
this
information
to
clip
it
with
assemble
work
reports
for
the
harvest,
so
we
will
be
posting
the
first
report
tomorrow
and
if
we
have
this
data,
it
will
take
much
less
time
for
us.
A
B
I
like
that
heuristic,
if
I've
worked
on,
worked
on
something
for
the
hackfest
in
a
particular
day.
That's
a
good
excuse
to
submit
an
issue
to
this
repository
for
that
day,
once
a
day
is
probably
good
enough.
Oleg
yeah
well
whatever
card
in
sports,
yeah,
okay,
great
good
questions
loud.
Thank
you.
Thank
you.