So, hi, I'm Gavor and I will talk about how it looks like in the QA Viki.
So, if someone wants to join as a newcomer, the QA team, fortunately there is a lot of very
useful Viki pages on how to do this, thanks to Foundation employees, mostly Air Marie
Cisco, Stefan and Parapsalot others.
So, this is supposed to be good so far, but actually let us ask ourselves how useful is this
actually in onboarding our newbie.
And I ask this from myself because when there is a monthly QA blog about what the QA team
did, there is this top-hand treasures section and I always see the same names, sometimes
even I am in the script, but this last time I was on it.
But these are old contributors and looks like there are no newcomers, that sounds like
a problem.
So let's get to testing how to do that, let's take a newbie.
So my wife was interested in this, yes, it would have been better if I would have a
university class, but I am not a teacher, so that's what I can do, but still she had
some technical background even in this area, so let's just retrain her.
So give her a few common tasks in QA and I would suppose that someone based on just reading
the Wiki can do that, those simple tasks, okay?
And that's observe and do what are the results.
So first task, find a QA Wiki from hibrofiz.org, find a QA Wiki, it's hidden here in the testing
QA menu item, improve it is like not simple English, so that was a little bit of a turnoff,
but eventually it was successful, so so far we are good, yeah, second and third tasks installed
in the nightly build, why not, that's on the latest and greatest development version,
and from the previous menu, it was successful, good, find the bugs in there and register
in that, okay, this was also straightforward and easy, soon we will get to the problematic
parts, okay, let's look up some unconformed works to confirm that recent reports are indeed
valid or not, and that's also something QA team does, so from the Wiki, I was supposed
supposing this should be easy task, but turns out not and it was on the bugs in the
home page, these links, such as bugs reported in the last 24 hours, around days, and that
was straightforward, but this info was not on the Wiki, so if someone goes to the Wiki and asked,
okay, how do I have, they don't find this information, but it's a, three we are simple task
for a new camera, okay, so maybe this is an improvement opportunity for the Wiki, okay, five,
find bugs that need a buy buy set, which is something a little bit up advanced, but yeah,
I wanted to give some more difficult task as well, so find in the buy buy set pages, of course,
easy, but then it was, it was introducing a video about the topic, which is half an hour,
and yeah, that's not what beginners want to watch, so that's not very useful anymore,
and also finding the Windows specific buy buy set, the Git repository is very easy,
there's a huge table in the Wiki about those, okay, what else, the Windows specific part of the
Wiki is somewhat confusing, there is a big table with order, repositories we have like 20 or
something like that already in the last 10 years, and we make one for every, every main
release, so that's two repositories per year, each of them are being like 8 or 10 gigabytes of
disk space, so it is filling up your disk very quickly, and there was a really easy repository
at the end of the table, and she asked me it's important, but actually it was not, so finding the
last few repositories, which contained the most recent regressions, that was less easy to
find, so that's also improvement opportunity, but as setting up the environment is a very short
section in this page, and it said that you are supposed to download Git for Windows,
but there was no link to that software, so that's a small banana peel, but now I have fixed it,
okay, another thing Cygwin is mentioned, that we used to recommend this, and yeah,
this was somewhat of a red herring or something, but she started to use Cygwin, and
somehow on her very new laptop, it failed to download the release repository, which is like 17 gigabytes,
so rather large, but some very weird Git error came in the middle, so.
Two minutes. Yeah, that's maybe that's something to remove from the page, and overall my impression is
that this Windows specific page is very large, it contains instructions for insha setup and
how to do troubleshooting while doing, by bisecting, and how to do the overall process, so maybe
it could be split up into smaller chunks, so whoever is already done with insha setup is no longer
seeing that part, because why should they see it? Okay, next, yeah, it's a, it's the same for the
general QA search, by bisect page, mixes setups, setups instructions, troubleshooting, how to
process descriptions, and also tasks for beginners, so in this part was the wasom query for the
bugs in bugs yellow, which are needing this sort of examination, but this part was well hidden
from the casual eye, so she did not find this, but otherwise it would be a very good
how do I have type of content for perhaps a separate page, and also it's sort of from all
this ones, which are the 10 year old bugs, which was somehow reported to be hidden, by bisect,
but no one came to do it, so it's the ugliest part of the task, so not something for beginners,
how about sorting it by new-est, it would be so much better, because most fresh bugs are easier to
tackle, and that's good for beginners, so that's another improvement of opportunity,
and that's all for today, thank you for listening.