(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
, ask if you have any questions, and add your name to
Thanks (as we will not be able to run this without your help),
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
Dear pywikibot users,
Please be advised that "sysopnames" is now deprecated. For all actions that
rely on a sysop account (such as deletion or protection), the code now
checks the rights of the bot user (as defined by the "usernames" array) and
if that user has the necessary right to perform the action, it will be
used. If not, an attempt will still be made to use the sysop account as
defined in the "sysopnames" array. However, we will soon clean up the code
to remove this feature altogether.
If a user wants to use different accounts for different actions, then the
bot script must explicitly use multiple instance of the Site class. Once we
completely remove support for "sysopnames", users who relied on the dualism
it caused will be left with a few choices: either get their main account
promoted to sysop (or any other group that has the desired rights), or
update the bot script such that it explicitly enforces the use of a second
account. While we are working on proving a cleaner example of how to deal
with two accounts in the bot script, you can refer to this comment on
Phabricator <https://phabricator.wikimedia.org/T71283#5446801> as a starter.
This has been a long-desired change in pywikibot code base (see T71283
<https://phabricator.wikimedia.org/T71283>). You can contribute to this
movement by removing "sysopnames" from your bot's user-config.py and
reporting any issues that arise afterwards. You can also help us by
updating the documentation on the MediaWiki wiki (for instance here