Tue, Mar 21
Hi @djff, this project is waiting for mentor with experience with Flagged Revisions deployed on a large site, e.g. someone from German Wikipedia to sign up as a mentor.
@01tonythomas , maybe you know who to contact in WMDE to get some traction on this. c.f. T57081#1737726
Sun, Mar 12
Sat, Mar 11
Fri, Mar 10
Hi @srishakatux , I guess that depending on the applicant. @happy5214 is interested, has a good background knowledge for this project, and we've got a good working relationship already, so it would be easy to sole-mentor the project with him. But a different applicant might bring new challenges which would mean a second mentor would be good to have.
Thu, Mar 9
@happy5214 , I've removed myself from other mentoring projects, but I am interesting in doing this one if you want to apply. Grab me on gitter to chat?
I havent been actively developing Pywikibot, and preparing to mentor this particular project (which would fiddle deep in the belly of pywikibot) would require getting up to speed on a lot of changes since I very active.
Jan 13 2017
The pypi package doesnt support py26 as pypi is intended to be a stable/supported release, and py26 is not stable/support-able.
See T155208: pytest-httpbin support breaks Python 2.6 builds ; not a high priority
Jan 9 2017
Note we currently have good coverage, but there are still some major component of the PatchManager which do not have any coverage at all.
Jan 3 2017
Yea, good solution.
Jan 2 2017
Dec 31 2016
@Mvolz, I notice you were focusing on the citation templates, which is a great idea, and I added some bahasa ones (and increased the task count). I am sure we can easily find more of those in other languages.
Hiya @PratyyaGhosh, the task is to fix a technical bug in the translated messages (i.e. not do translation). The task gives some examples on how to find them, and I have just added some specific cases where the messages need fixing.
But ideally you get creative in trying to find syntax errors.
And if you find a syntax problem which occurs frequently, we can improve our tools to prevent it occurring again.
Should this task include or exclude research on MatterMost and Zulip, which is covered by T154001, or should it be up to the participant to choose whether to include/exclude those two?
Here is good, or on the talk page.
Dec 30 2016
Nice going so far. I can more usually be reached at https://gitter.im/jayvdb
Dec 29 2016
Unpublished task https://codein.withgoogle.com/dashboard/tasks/6553516124405760/
Dec 27 2016
Ya, see above T153559#2884218 ; IMO we should accept both body or data, and treat them the same (maybe using deprecation, if we prefer one name over the other, but I am not sure about that one). ((reviewing now))
Dec 23 2016
IMO , and I live in a country with poor English skills, and 9-5 my job is to build a tech community for Wikjmedia Indonesia, the 'build tools' are not a significant problem. In fact, the i18n of complex tools often causes problems, as the error messages are not as well maintained in non-English, and are less google-able. The focus is usually to provide error codes , and i18n-d documentation.
As these are hosted, do you intend for this research GCI task to be done using test instances provided by Zulip/Mattermost, or the participant would use toollabs to install and evaluate?
Dec 22 2016
Dec 18 2016
See also T153560
Dec 17 2016
GCI unpublished task https://codein.withgoogle.com/dashboard/tasks/5687405443022848/
Btw, it looks like body is already mapped to data, so it probably already accepts a dict.
Dec 15 2016
Thx for investigating. Fwiw, you may find my travis_log_fetch Python
package useful. I built it for times when I had to do the same.
Dec 13 2016
Dec 10 2016
Dec 8 2016
Does this task need more detail?
Dec 7 2016
Best documentation is at:
Problem with b932798d in 2013.
Dec 5 2016
Ah, my apologies. As mentioned in T113140 , LinkChecker is deprecated and is not used by LinkCheckThread or WeblinkCheckerRobot , so the decision was to leave that code as-is.
Dec 4 2016
Currently I'm thinking of HTTP status codes, but I thought if a server returns something like 403 Forbidden, we should honour it instead.
Dec 2 2016
Dec 1 2016
A badly translated TemplateData is better than no TemplateData.
Feel free to add me as a mentor to those tasks; if I cant determine the prose is >75% correct, I'll find someone who can tell me that.
You've looked through T130572?
Just do the ones you can, and supplement the tests with other types of interesting cases you can see will be helpful, even basic ones.
I suggest we also create a similar task for doing this on a non-English
project, and another for a non-Wikipedia project, otherwise the only
project that benefits is English Wikipedia, which needs the least amount of
help in this regards.
I think this is "Add a missing entry in the qqq.json file , describing the message."
https://codein.withgoogle.com/tasks/4719662784839680/ will be the GCI task for this, when it is publish - waiting for admin to press the button
I like these two combined:
The main problem is that the default is None in config2.py.
Nov 28 2016
This one hasnt been published yet.
Nov 23 2016
Nov 22 2016
@DrTrigon , the 2016 GCI task is here : https://codein.withgoogle.com/dashboard/tasks/5116835657678848/
Nov 18 2016
See also T150732: Provide a group chat system for mentoring, for a specific area where our lack of modern communication system is hurting out outreach efforts, and an area where trials of new approaches would be welcomed and localised and constrained to short projects not needing to impact our existing communication systems.
Nov 17 2016
Nov 15 2016
I am not advocating that IRC should be replaced. It is great for many purposes (I said that in the opening sentence), especially when lots of custom IRC bots are created as Wikimedia have build over many years.
One way to make this task less problematic is for it to be find only - i.e no fixing. Many fixes require knowledge of the language, while detecting a bug is able to be done without that knowledge. The intention is that this task would be followed by a task to improve the TWN checkers.