Hi @Uziel302, thanks for creating this. What exactly is someone working on this task supposed to do? Which knowledge is needed, and what exactly is the goal of this task?

(task moved in Information needed because of question by @Aklapper)

The task requires two things: scan for typos in dumps and user interface to correct in one click.
Steps:
1 downloading the c program, word list and dump of enwikibooks
2 running the c program to scan the dump file for the typos on the list
3 copying user script from enwiki to enwikibooks
4 creating project page for the output and adjusting the script to run on that page
5 testing by correcting typos using the new buttons the script adds

@Uziel302: Thanks for the quick reply! Where would you get a "dump of enwikibooks"? Does "running the c program" require to first compile that program myself? Where should I "create the project page"? I assume I should create an account on a Wikimedia wiki for that first? And "enwiki" probably means "en.wikipedia.org" here.
(I'm not asking these questions to annoy you, but to help you imagine being a person who would like to work on this task and might have zero knowledge about Wikimedia, to avoid misunderstandings on both sides in GCI.)

1 Download "Articles, templates, media/file descriptions, and primary meta-pages." from https://dumps.wikimedia.org/enwikibooks/20191120/
2 Running the program requires compiling, which can be done by gcc command. I'm not sure about the students prior knowledge in coding.
3 Creating the project page can be done by searching "Wikibooks:Correct typos in one click" inside en.wikibooks.org and clicking on the red link of "Wikibooks:Correct typos in one click" on the top of the results. It is preferred to edit on Wikibooks with an account, which can be created by clicking "Create account" on the top menu.
4 enwiki is en.wikipedia.org and the same project there is at https://en.wikipedia.org/wiki/Wikipedia:Correct_typos_in_one_click

@Aklapper anything missing?

@Uziel302: Hi, if this should go into GCI, then a full description which includes all that students should do or must know beforehand, without a need for interpretation (e.g. "What's the gcc command which I cannot find on my Windows 10 machine?"). See https://www.mediawiki.org/wiki/Google_Code-in/Mentors#Task_requirements . You can edit the task description by clicking Edit Task. Thanks!

@Aklapper thanks for the instructions, I edited the task. Let me know if something is still missing.

Thanks! Is gcc enwiki\ autocorrct.c meant to be a command? The backslash confuses me.
Which content is "basic" enough to copy it? How many typos is a contributor supposed to fix until the GCI task is approved by the mentor?
Looking at the two sections above, is a GCI student an "editor" or an "admin" or both (and why does that differentiation matter)?

@Aklapper the backlash was needed when I ran it since it had space in the file name, I changed the description to instruct to use file name without spaces so backlash is no longer needed.

I think treating 5 typos is enough on the editor side to understand how it works.

I added explanation about the need of both sides.

I feel a bit like a broken record however there seem to be still a lot of things that feel unclear to me. Please try hard to imagine being a complete newcomer, or define clearly required knowledge and skills beforehand.

• Is gcc installed by default on all unix based system? (I doubt, so what would I have to do?)
• "Search for the list of misspelled words in the downloaded wiki," - so it is not me searching, but that application does that for me? "Download this file. Compile this file. Then run that application which will search...." would be more correct, I assume? Clear steps explaining what does what in which order are welcome.
• The task summary says "Wikibooks". The text however only talks about "en.wikibooks.org". Is this task only about fixing English typos, or not?
• I have no idea what "Treat 5 typos from the list as done on the editor side" means. Or what is an "editor side".
• Which content on the English Wikipedia project page is considered "basic content" and which not?
• Should I create a user account on en.wikibooks.org for this? If so, how?
• https://github.com/Uziel302/websites-spell-checker/blob/master/enwiki%20autocorrect.c hardcodes an xml filename, so it will fail given the dumps link.

@Aklapper I changed the task to be more adapted to newbies. As of Wikibooks, I created the project there myself: https://en.wikibooks.org/wiki/Wikibooks:Correct_typos_in_one_click

I followed the steps and failed at "Find a typo where the offer correction is right and click replace". Because I have no clue how to do that.
Furthermore, in step 6, there is no "start the ... page" option - en.wp says "Start the ... article". Have you tried to follow your steps?

Hello,

I've looked at this task as well, and I concur with what @Aklapper says. I assume step 12 can mean "Fix a correction you consider correct", but I'm not sure and it should be probably reformulated.

I also think that instead of mandatory steps like "click contribs and examine your edits" you can suggest students what they can do there, and how diffs work (preferably with links to applicable help pages), to facilitate students self-learning process. Either way, we have no way to see if they did that, and i believe that would make the task little bit more friendly .

Step 11 should explain what the buttons do. It's not immediately clear to me, as an experienced editor, and I don't expect it'll be any more cleaner to a total newbie. Ideally, the tool itself should be altered to add more details (on-hover popup maybe?). You can make it a new GCI task, I guess!

I strongly recommend that step 5 says what personal JS is. It is one of the most dangerous things Wikimedia sites allows anyone to do, and it should be made clear what would that do.

Thanks for volunteering to mentor!

Yes, I agree with @Urbanecm and @Aklapper comments, I followed the same steps and fixed a typo, Me as I already used several user scripts and gadgets before, so I know how this works, But for newbies, it's better to include task description at the top of the task so this will give a good/brief idea what the students are going to try themselves in this task.