In T145439#2775091, @Aklapper wrote:

If someone picks up this task, note that a patch (that needs improvement) already exists. See https://www.mediawiki.org/wiki/Gerrit/Tutorial#Amending_a_change_.28your_own_or_someone_else.27s.29

@Ragesoss Valid points, the task is mismatched for the Code-In. But I'm still interested in trying to help. Is there anyway I could get in touch with the community?

@Ragesoss Yup, I can definitely see the lack of... content. :|
Is there any forum for where a link to survey could be posted. So that current and potential users could express their views?
While, this task strongly falls in to outreach, UX. A time frame of 36 hours is way to short to be effective. I think a task involving creation of a survey, acquiring whatever data can got in 3 days and submitting it as a spreadsheet should suffice.
Along with a report about what the student thinks perhaps?

In T145439#2702270, @matej_suchanek wrote:

Looking at i18n/en.json:

"echo-email-footer-default-html": "To control which emails we send you, <a href=\"$2\" style=\"text-decoration:none; color: #3868B0;\">check your preferences</a>.<br />\n$1",
"echo-email-footer-default": "$2\n\nTo control which emails we send you, check your preferences:\n{{canonicalurl:{{#special:Preferences}}#mw-prefsection-echo}}\n\n$1",
"echo-email-plain-footer": "To control which emails we send you, check your preferences:",
"echo-email-html-footer-preference-link-text": "check your preferences",
"echo-email-html-footer-with-link": "To control which emails we send {{GENDER:$3|you}}, $1.",

there are even more messages which could benefit from the same changes. But I'm not sure whether all of them are used...

What exactly is the task here? I'm planning on metoring for Google-Code-In-2016

I will mentor this in Google-Code-In-2016
Seems simple enough for me to introduce the student to image viewer, while allowing me to go understand it better as well.
Looking forward to it.

In T29650#2762087, @srishakatux wrote:

I would like to mentor this in GCI with support from others (if available).

Make sure you remove the screenshots you added separately later on. And thanks for doing this task. :)

@Saylikarnik
To add screenshots to the infobox update the 'image' parameter with the file name, not the file path.
eg: For the 'example skin' once you click on 'edit source' the infobox.image parameter should be just ExampleSkin.jpg and not https://commons.wikimedia.org/wiki/File:ExampleSkin.jpg

Done

The author replied. Apparently I can do anything I want with the image, it doesn't have a license.
So I'll do what the I said in my last post.

kk, thanks.
The original one doesn't have a 'machine readable license'. And the author hasn't replied to my email, yet.
I'll wait for a week. If he doesn't reply, then I'll upload this image with the CC-BY-SA (https://creativecommons.org/licenses/).
If he does reply, then I'll upload it with his license. (Probably the same one)

I fused the two screenshots to make one big one!!!
Should I use that instead?

Licensing still needs to fixed. I sent an email to the author (air_bob). Included a link to this Phab. ticket as well. He may use the licensing asked for by this task.

Thanks.
Yup, the screenshot is valid, check: https://wiki.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki?useskin=purecss (hilariously long loading time).

But I didn't takethat screenshot. It was already there. I just updated the 'image' parameter. (Does that count?)

Okay. I've updated the PureCss skin.
I'll take the screenshots of 'Monaco' and 'Timeglass'. Once I've finished (re)installing MW-vagrant

What would count as 'the extension's functionality'?
Would it be something like this? ( even though it's a skin ) https://www.mediawiki.org/wiki/Skin:PureCss#How_it_looks
(btw, that one needs to be removed from ' MW skins without a screenshot'.

In T120976#1889870, @NiharikaKohli wrote:

In T120976#1889869, @JadeMaveric wrote:

Submitted GCI task.

In T120976#1869128, @Krenair wrote:

Defaults for these messages are stored in i18n/en.json in the extension repository. They can be overridden by on-wiki customisations.

Didn't understand this

The messages are initially written in code but the on-wiki admins can modify them as they see fit. We don't have to bother about it for the purposes of this task.

Submitted GCI task.

So far so good, I'm also saving a log. If it finishes without errors I can update https://www.mediawiki.org/wiki/MediaWiki-Vagrant/Initial_run

Things went fine. A few misshaps but Niharika helped! Unfortunately I had to shutdown the PC when vagrant was running (or rather, building the system). Here's the terminal session once I restarted it: http://ur1.ca/oclcb

Thanks, it's downloading now.
I've run vagrant up --provider=virtualbox --debug. So it's easier to fix in case something goes wrong.

vagrant --version : Vagrant 1.7.4
vboxmanage --version : 5.0.10_RPMFusionr104061
vagrant up --debug : Lots of stuff