Added to 2017 GCI https://codein.withgoogle.com/dashboard/tasks/6029008296738816/

Here is the GCI 2015 task : https://codein.withgoogle.com/archive/2015/organization/4822184463695872/task/5953614677803008/

Try cleaning your cache (see maintenance script) or just delete tests/apicache*, to check whether you can reproduce locally.

The first set to do would be TestItemBasePageMethods , as there are other BasePageMethods tests in other parts of the system, making this an interesting way to get basic coverage of a lot of modules/classes quickly, and hopefully easily.

Pywikibot docstring params use epytext format.

This was already created as https://codein.withgoogle.com/dashboard/tasks/6189366353330176/ ; I am just creating a Phab task for it.
All commits should reference this Phab task

Agree, it is a waste of time to be updating this, as git log has better information if it is needed.

@Legoktm , @hashar , I guess this task can be closed. It was originally a pywikibot task, but it grew big legs and achieved many things. Re-open if I am mistaken.

This was done at my request during code review because this script wasnt being tested with tests/script_tests.py which it should be.

Specifically testme whether line=off, line=false, line=disabled or some other reasonable boolean like value is possible.
IMO line=0 is not a good option.

Hmm, I also a bit doubt of that, since I can't test it in toolforge.

@ori created https://people.wikimedia.org/~ori/bad.js as a test case, and 'Python' failed badly (likely Pygments with all of its regexes, but maybe one of its dependencies). That is an Upstream failure. See his comment on https://gerrit.wikimedia.org/r/#/c/223053/ . But that was two years ago. Perhaps this should be retested, and a bug files Upstream if there still a problem.

The entire problem space has moved, as Wikimedia now uses Pygments. @Oetterer , are you still using the syntax highlighter that uses GeSHi ?

@divadsn , you have three commits on https://github.com/python-social-auth/social-core/pull/169/commits ; that is unnecessary , and in gerrit world it would be considered messy work. Please squash them.

Repeating some of what I put into the code review of https://github.com/python-social-auth/social-core/pull/169

Looking good so far. The most recent PRs included a unit test module.

In T183698#3861026, @Paladox wrote:

Nope removing mediawiki auth will fix it, but will also prevent showing the other login form.

Can we add some CSS to hide the MediaWiki auth?

First challenge is getting a test instance of Phabricator up.
https://secure.phabricator.com/ says NOTE: You can launch a test installation of Phabricator on Phacility if you want to poke around and try things out.

This was around the time we were revising the mwparserfromhell build system . We had only finished getting Python 3.4 working, and then another problem arose when testing on Python 3.5.
I can only guess that mwparserfromhell now supports Python 3.5+, but it would be wise to rerun the mwparserfromhell tests periodically, as it doesnt see a lot of PRs so not many eyes on it.

cosmetic_changes sometimes have exceptions added for specific wikis which do not want the change.
My guess is most wikis wont have a problem with this cosmetic change. Lets try it and see who complains?

@Filip , can you add some Polish templates to the task description?

I suggest using https://www.mediawiki.org/wiki/Manual:Pywikibot/PAWS for this. Less complicated.

The task description was wrong, I've updated it.

Here is the task from last year: https://codein.withgoogle.com/archive/2016/organization/5709875686408192/task/6126939156774912/

Draft task at https://codein.withgoogle.com/dashboard/tasks/5159547750580224/

@Zppix, thanks, I'll add you to the list of mentors, but we will need mentors with more experience editing on Wikidata.

@Reedy , the task description say " The solution is to remove the & " and

@Mvolz, I just noticed this was at the top of https://twitter.com/hashtag/googlecodein?src=hash . Do you want to try this one again?
@Elitre?

I am interested in mentoring this one, but I would need help if this was to have more than a few instances available.

@Framawiki , @MtDu , any good ideas here which could be GCI tasks?
(Need to recheck which ones might have already been implemented)

@MtDu @Framawiki , status of this one? Could be a good GCI task?

@Xqt, thanks for raising this. Do we have an open task about errors such as this not being found by gerrit/jenkins?

Ya, nice idea.
(published)

@Petrb , do you think some of the information at https://meta.wikimedia.org/wiki/Huggle/Download should be included into the new revise manual ?
Otherwise the enwp and meta versions have two distinct sets of information about installation methods.

I've accepted one students task, but this will affect all pywikibot GCI tasks, and all other pywiki dev work. Should we disable these tests temporarily?

Thanks for raising this @Dalba !

Because it is a tool for Gerrit. *shrug* But removing the tag is ok.

@Paladox , this is a git client tool, which interfaces with lots of different git servers. It can happily support them all. Please read tasks before you comment on them.

Let me know if you need help with code review for pywiki

I am also willing to mentor this task for Google-Code-in-2017

@zeljkofilipin , is there any part of this which might be suitable for Google-Code-in-2017 tasks?

Yup you can mentor it, and I've updated the list.
Can just copy https://codein.withgoogle.com/dashboard/tasks/6553516124405760/
Archived at https://codein.withgoogle.com/archive/2016/organization/5709875686408192/task/4728573235560448/ (strange it is a different task ID)

Is this still a problem?

Another potential research type task is research on IRC bridges / IRC webapps / IRC foo . So that Wikimedia provides newcomers with good information on how to get 'into' IRC with the best tools for their situation.

@srishakatux , do you want to do this again for GCI 2017? Gitter is now open source, Zulip has improved a lot in the last 12 months, and RocketChat was mentioned frequently at the GSOC summit.

IIRC, the "plural" example was more problematic than helpful .
We should use examples of this type of task done in 2016 instead of the plural example.

This task was ok last year, and it is good to keep improving the same template task each year.

This is not complete, and is suitable for GCI 2017

Just a quick anecdote. I used zulip as part of GSOC 2017 mentoring for all the (weekly) meetings which we held, and we also used gitter to communicate occasionally for some of the more technical questions that needed an immediate response to avoid delays in the project. This is because gitter notifications worked better than zulip or IRC at ensuring a rapid response on specific chat rooms, because it also sends an email with any unread messages. OTOH, Zulip was better for scheduled meetings, and discussion threads which spanned large periods of time, and for keeping in contact with the other GSOC people (admins, mentors, students). Both clients were light weight, and low permissions, so it wasnt a huge drama for us to have multiple clients installed. We also both used IRC occasionally also, but not as a mechanism for having a discussion between mentor and mentee.

I dont have rollback it seems.

I just did another restore of a bad merge, and it failed with Invalid content data
https://www.wikidata.org/w/index.php?title=Q19281208&action=edit&restore=309323077

clicking restore on the last good version takes me to https://www.wikidata.org/w/index.php?title=Q9143779&action=edit&restore=198877769 , and clicking Save also results in Invalid content data for me too.