https://phabricator.wikimedia.org/project/board/520/query/pXp0QaVCIVBm/
Each task must be clear and easy to understand, and needs to contain some sort of prefix / header that describe in short what Huggle is. There also might be some standard header that points to some generic wikimedia standards (is there any? @Aklapper )
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Petrb | T179983 (tracking) Manage "google code in" for huggle: import all tasks and mentor them | |||
| Resolved | Petrb | T179982 Translate Huggle to your language, or improve existing language | |||
| Resolved | Petrb | T179981 Suggest refactoring of poorly documented or hard to understand parts of Huggle code or internals | |||
| Resolved | Petrb | T150089 (recurring) Document all missing keys in translate docs | |||
| Open | None | T150056 Create a simple guide with screenshots that explains how to start windows binary with parameters | |||
| Open | None | T93380 Move stuff in huggle docs into small number of large pages | |||
| Resolved | Petrb | T179776 Localize some hard-coded strings in the interface | |||
| Resolved | Petrb | T149967 Incorporate new languages into Huggle |
There will be an org-wide footer telling students to read https://www.mediawiki.org/wiki/Google_Code-in/Participants
https://www.mediawiki.org/w/index.php?title=Google_Code-in/Mentors&oldid=2525616#Huggle is probably what you could copy and paste into tasks, if you don't run into the 1500 characters limitation.
So, here is the text I am going to copy paste as header for every task:
Huggle is a fast diff browser application intended for dealing with vandalism on Wikimedia projects, written in C++. More information: https://en.wikipedia.org/wiki/Wikipedia:Huggle. Source code is available at https://github.com/huggle/huggle3-qt-lx and can be compiled on Linux, Windows and MacOS.
For footer:
If you want to avoid troubles setting up C++ IDE, you can download preinstalled VM with everything ready for development: https://github.com/huggle/huggle3-qt-lx/wiki/Portable-development-environment
Each task that was imported was closed, if it's not done during this GCI, we can reopen it
That mean, we should keep this tracking task open until end of GCI, even if all tasks get imported
now, before we close this we need to check which tasks were finished and these that were not, can be reopened