Hi Pywikibot crew,
Google Code-In (GCI) will soon take place again - a contest for 13-17
year old students to contribute to free software projects.
Wikimedia wants to take part again.
Last year's GCI results were surprisingly good - see
https://www.mediawiki.org/wiki/Google_Code-in_2013
We need your help:
1) Go to
https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and
read the information there. If something is unclear, ask!
2) Add yourself to the table of mentors on
https://www.mediawiki.org/wiki/Google_Code-in_2014#Contacting_Wikimedia_men…
- the more mentors are listed the better our chances are that Google
accepts us.
3) Please take ten minutes and go through open recent tickets in
https://bugzilla.wikimedia.org in your area of interest. If you see
self-contained, non-controversial issues with a clear approach which you
can recommend to new developers and would mentor: Add the task to
https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks
Until Sunday November 12th, we need at least five tasks from each of
these categories (plus some less technical beginner tasks as well):
* Code: Tasks related to writing or refactoring code
* Documentation/Training: Tasks related to creating/editing documents
and helping others learn more - no translation tasks
* Outreach/research: Tasks related to community management,
outreach/marketing, or studying problems and recommending solutions
* Quality Assurance: Tasks related to testing and ensuring code is of
high quality
* User Interface: Tasks related to user experience research or user
interface design and interaction
Google wants every organization to have 100+ tasks available on December
1st. Last year, we had 273 tasks in the end.
Note that you could also create rather generic tasks, for example fixing
two interface messages from the list of dependencies of
https://bugzilla.wikimedia.org/show_bug.cgi?id=38638
Potentially helpful Bugzilla links:
* Reports that were proposed for GCI last year and are still open:
https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=ALL%20whiteboard%3Ag…
* Open Pywikibot tickets created in the last six months (if I got your
products and components right):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu…
* 19 already existing Pywikibot "easy" tickets (are they still valid?):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu…
Could you imagine mentoring some of these tasks?
Thank you for your help in reaching out to new contributors and making
GCI a success again! Please ask if you have questions.
Cheers,
andre
PS: And in a future Phabricator world, Bugzilla tickets with the 'easy'
keyword will become Phabricator tasks with the 'easy' project.
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Hello!
I set up my bot on Labs and use shared repo of pywikibot.
That's why I am interested in 2 options:
1) how can I define which file should be used as user-config.py in the
script's running parameters? For example, I want to run "redirect.py br
-delete -always" with config of sysop bot and "redirect.py do -always" with
usual bot account, that's why I want to create 2 different configs and
define them in parameters.
I haven't such functions in global parameters but I am quite sure that this
was possible before.
2) I want to run my custom script but use shared repo of framework: for
example, to run delinker.py from my home location but use wikipedia.py,
etc. from shared repo not to clone frameworks on Labs.
Is it possible, too?
Thanks,
rubin16
I just want to notify, that the nose tests are going to fail now as
test wikipedia now emits a warning when a action=query is executed
without a continue parameter.[1]
I've uploaded a temporary fix which avoid breaking the tests[2] but
this should replaced with a better solution soon.
Unfortunately I don't know how we solve this the best. The main
problem is that we don't know what we need to do because for that we
need to know which version the server is using. My idea would be to
add an empty 'continue' if there is no 'continue' or 'rawcontinue'
present (could be done in Request._add_defaults). Of course we also
need to update QueryGenerator to set 'rawcontinue' at first until we
update it to use the new system.
I'll try to upload a intermediary fix for which I invite others to add
comments (if applicable of course) and improve it.
1: https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2014-September…
2: https://gerrit.wikimedia.org/r/168523
Hi guys,
I'm wondering how to add references that have multiple parts. Take for
example https://www.wikidata.org/wiki/Q76 (Barack Obama). The third
reference of date of birth has two parts:
* "stated in" -> "Integrated Authority File"
* "date retrieved" -> "9 April 2014"
Currently a reference in our implementation is a special claim [1]. I'm
pretty sure the left hand side of a claim is always one property (for
example "date of birth"), with references this can be multiple (for
example "stated in" and "date retrieved"). Am I missing something or
should we change our implementation?
Maarten
[1]
https://git.wikimedia.org/blob/pywikibot%2Fcore.git/5b04107f5f4151a82293389…
Hello ,
I am Juhi Tandon, in third year of undergraduate study, pursuing Btech. in
Computer Science and MS by Research in Computational Linguistics at
International Institute of Information Technology (IIIT) Hyderabad. I want
to apply for OPW Winter round 2014.
I want to contribute to pywikibot. As such I tried to do the setup of
compat and core repositories. The script pwb.py wouldnot compile. After
having spent considerable time on IRC and help from a developers, I managed
to solve the proxy issue and create an account.
Please guide me on how to start contributing , especially to compat to core
migration .
Thanks and Regards,
Juhi Tandon.
Hi! I am new to pywikibot and have been going through
installation/contribution articles. I have two questions:
1. What is the difference b/w pywikibot-core/compat and core/compat? Do i
need to install both?
2. I wish to fix the bug 57995 - Add function for list=watchlistraw. On the
gerrit page(https://gerrit.wikimedia.org/r/#/c/100363/). A couple of
patches have been uploaded but I cant view the given links. Also, I am
assuming that I need to continue where others left but how do I know what
parts of the bugs have been fixed?