Can you give me some example I have no idea what you talk about.

In T173969#3552821, @Petrb wrote:

Can you give me some example I have no idea what you talk about.

If you see in a patrolling session a user that want to insert a picture in a infobox, but uses [[File:xxx.jpg]] instead of |picture=xxx.jpg, I would post a message like {{subst:help-pictures}}.
So having a list of these templates would be great.
Something like what exists with Twinkle (more simple list of course, about 20 entry would suffice)

I purpose to add this task to Google-Code-in-2017. It needs skills in C++, and if possible in the Qt framework.

A new form was created recently in Huggle (custommessage.ccp/h/ui) : it allows patrollers to send a custom message to editors. The purpose of this task is to add a way to avoid enter the same message again and again.
So we can suppose that these messages can be stored in user configuration. The first step is to add a new variable in this config, a list that will store a few messages. You'll need to read and write this variable, then you can create a space in the form (custommessage.ui) that shows all the available messages, and where the user can select one of them, that update the text area with this message.
Don't hesitate to ask if we can help you somewhere. When it's good for you, please create a PR on the Github repo.

@Framawiki and/or @Petrb: Would any/both of you [feel like having enough knowledge to] mentor this task in Google-Code-in-2017?

Given my experience with previous years of GCI, I doubt that we could find a student skilled enough to do this. This task is IMHO too easy for GSoC and too hard for GCI, but we can try if @Framawiki creates a simple explanation of what he wants and how to implement it. By simple I mean simple enough that 15 years old student with 0 wikipedia / huggle experience would understand it, not just me ;)

Keep in mind that these students possibly never edited Wikipedia and therefore have absolutely no idea what these things are and possibly mean, each of these terms should be somehow explained in task description:

• OTRS
• Messaging on MediaWiki sites, how it works
• Reference - what it means in context of wikipedia
• Template
• Patroller
• Twinkle

Looking back, I also think that this task is too complicated for GCI, and we're not even ourselves about what we want. Let's remove this tag.