Hi,
There are a few aspects of packaging which will benefit from more
brains and a collective decision we can all live with, both in the
short term for '2.0' and what we want long term (e.g. '2.1', etc).
I would appreciate assistance with...
https://www.mediawiki.org/wiki/Requests_for_comment/pywikibot_2.0_packaging
--
John Vandenberg
In one week bugzilla will move to phabricator.
I am still not friend with phabricator, and I am not able to find how
to report bugs about pywikipedia. Is somewhere something about it,
some project etc?
JAnD
Hello pywikibot community,
cc wider Wikimedia community,
Given the discussion on pywikipedia-l on the bugzilla migration, I
thought it might be a good idea to have a more formal discussion
beforehand on what we, as pywikibot community, want to do once the
rest of the community moves from Gerrit to Phabricator.
As such, I've prepared an RFC draft [1], and I would welcome your input there.
Best,
Merlijn
[1] https://www.mediawiki.org/wiki/Requests_for_comment/pywikibot_git_hosting
As a workaround, chdir to the pwb.py path before running, or explicitly
define the user-config path with -dir:/path/where/pwb.py/is
On 9 Nov 2014 15:10, <bugzilla-daemon(a)wikimedia.org> wrote:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=72680
>
> Steinsplitter <steinsplitter(a)wikipedia.de> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Priority|Unprioritized |High
> CC| |
> steinsplitter(a)wikipedia.de
> Severity|normal |major
>
> --- Comment #8 from Steinsplitter <steinsplitter(a)wikipedia.de> ---
> It breaks all bots with the newest version on toolslabs
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
>
> _______________________________________________
> Pywikipedia-bugs mailing list
> Pywikipedia-bugs(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/pywikipedia-bugs
>
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