Hi all,
I'm building a small pywikibot tool[1] which is designed to be installed
via pip (and in turn installs Pywikibot via pip).
The tool uses the page.touch() function which is where I get a
pywikibot.i18n.TranslationError when I run it.
page.touch() gets it's edit summary from i18n.twtranslate(self.site,
'pywikibot-touch') which in turn is defined in /scripts/i18n/pywikibot/.
Unless I'm confused the Error occurs because the pip distribution does not
include the /scripts folder or the i18n submodule.
So my first question is am I just doing something obviously wrong and the
i18n submodule should have been available over pip as well?
If it's not just me then would it not make sense to have any i18n files
necessary to the Pywikibot *library* to also be distributed via the same
pip package? (i18n for scripts is another issue since for scripts you
cannot use pip).
Cheers,
André / Lokal_Profil
[1] https://github.com/lokal-profil/pywikibot-sdc
André Costa | Chief Operating Officer, Wikimedia Sverige |
Andre.Costa(a)wikimedia.se | +46 (0)733-964574
Stöd fri kunskap, bli medlem i Wikimedia Sverige.
Läs mer på blimedlem.wikimedia.se
------
sent from my mobile, all typos are due to autocorrect ;)
Hi lovely pywikibot folks. I'd like to clean up our deprecated code
since we have some that's six years old....
% grep -RIoh "since='[^']\+'" ./* | sort | head -n 5
since='20150206'
since='20150515'
since='20150615'
since='20150617'
since='20150619'
% grep -RIoh "since='[^']\+'" ./* | wc -l
130
What is pywikibot's policy regarding code deprecation? Can we remove
it after a set duration and, if so, what is it?
Thanks! -Damian
TL;DR:
* The #pywikibot IRC channel is moving from Freenode to Libera.Chat.
* Register an account on Libera.Chat and join us there!
There has been a lot of activity over the last 2-3 days related to
staffing changes on the Freenode IRC network [0]. The Wikimedia IRC
Group Contacts (GCs) [1] evaluated the situation and decided that
moving the Wikimedia IRC channels from Freenode to the brand new
Libera.Chat IRC network [2] would be the best course of action [3].
So, we are moving!
A new #pywikibot channel has been created on irc.libera.chat for
handling Pywikibot discussion, support, Phab/Gerrit updates, etc. I am
waiting for a bit more people to join us over on Libera before closing
down the Freenode room.
There is a new subpage on Meta-Wiki [4] for information on how to create
a new account for yourself on Libera.Chat and other related information.
There is also a tracking task [5] that you can look at to see various
activities that the community hopes to take action on to complete the
migration.
One last thing: The #wmhack Freenode channel is bridged to
#wikimedia-hackathon on Libera.Chat. The new channel name will make it
easier for the GCs to help manage spam and other issues that come up
occasionally on IRC. Don't miss the fun of our 2021 virtual hackathon
from Friday, May 21st to Sunday, May 23rd! [6]
[0]: https://www.kline.sh/
[1]: https://meta.wikimedia.org/wiki/IRC/Group_Contacts
[2]: https://libera.chat/
[3]: https://meta.wikimedia.org/w/index.php?diff=21476411
[4]: https://meta.wikimedia.org/wiki/IRC/Migrating_to_Libera_Chat
[5]: https://phabricator.wikimedia.org/T283247
[6]: https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021
-- Legoktm
I was looking at Pywikibot's commit stats for something and noticed that
as of earlier today, `git shortlog -s` reports that Xqt hit 4,000
commits in the pywikibot/core repository!
For comparison, the next human is at 822 commits. In total the
repository has a little over 9,800 commits, of which ~40% are from Xqt.
Thank you Xqt for all your work maintaining Pywikibot for so many years
and for helping power so many bots across Wikimedia.
-- Legoktm
Nice opportunity for OA, Python, PostgreSQL and bibliographic dataset
enthusiasts!
https://team.inria.fr/valda/engineer-position-in-the-valda-team/
(Please forgive the crossposting.)
Best regards,
Federico
== Engineer position in the Valda team ==
Valda is hiring an engineer to work on the [https://dissem.in/ Dissemin]
platfom for a two-year position at [https://www.ens.psl.eu/ École
normale supérieure]. Dissemin is a tool to detect research articles
behind paywalls and to help their authors upload them in an open
repository. Dissemin is an [https://gitlab.com/dissemin/dissemin
open-source project] with various contributors, organized as a
[https://association.dissem.in/index.html.en non-profit].
=== Profile of the candidate ===
The applicant should be familiar with or ready to learn the following
technologies:
* the Python programming language;
* the Django Web application framework;
* the PostgreSQL database management system;
* RESTful Web APIs;
* processing of large datasets.
The applicant should be familiar with an open-source development
workflow (basics of Git, merge requests, proficiency in technical
English) and willing and interested to work in an academic environment
on a project related to academic publishing. The candidate should be
able to work autonomously, in interaction with a remote team of developers.
The applicant should hold a Master or engineering diploma in a field
related to computer science or computer engineering. Candidates holding
a PhD on a relevant topic are also welcome, with the experience of the
PhD recognized and useful for the project.
The applicant need not be French-speaking.
=== Tasks ===
The role of the engineer will be to turn Dissemin from a
proof-of-concept work into a production-ready tool, in particular to be
used by French researchers to help them deposit their works on
open-access platforms, as required by their employers or funders. Some
specific tasks include:
* day-to-day management of the Dissemin platform and bug fixing;
* integration of [https://www.crossref.org/ Crossref] and
[https://www.base-search.net/ BASE] data, in connection with
[https://hal.archives-ouvertes.fr/ HAL];
* optimization of the data ingestion from [https://www.crossref.org/
Crossref] and [https://www.base-search.net/ BASE];
* possible migration of the platform to a different hosting and
architecture;
* interaction with the Valda research team on subjects related to the
analysis of the scientific corpus (e.g., possible co-supervision of
Master's students).
=== Work conditions ===
The engineer will be hosted at École normale supérieure in the 5th
district of Paris and employed by ENS on a one-year contract renewable
once, for a total planned duration of two years.
For a full-time position, the work week is 37.5 hours (flexible hours),
with 49 vacation days yearly; part-time positions can be discussed. The
engineer will work under the supervision of the head of the Valda team,
[https://pierre.senellart.com/ Pierre Senellart]. The salary will follow
the ENS salary scale for technical employees (typically 26 to 36 k€
gross yearly salary depending on experience and degree).
The position is expected to start at the earliest in June 2021 and at
the latest in January 2022.
=== Work environment ===
The work will be conducted within a dynamic research team, also in
interaction with the [https://prairie-institute.fr/ PRAIRIE institute]
for artificial intelligence research in Paris. The engineer will be
encouraged to participate in the life of the team (research seminars,
discussions with PhD candidates and researchers, etc.). This position
can also serve as a gateway for applicants considering a PhD thesis in
related areas. All development will be open-source. Contributing to
third-party open-source projects useful to Dissemin is also encouraged.
=== Diversity ===
ENS is an equal-opportunity employer, with ENS and Dissemin committed to
diversity and professional equality in terms of gender, handicap, and
origin. For this reason, applicants need not mention any personal
information (such as age, family situation, photo) on their application.
=== How to apply? ===
Candidates can submit their application (CV, motivation letter,
references, link to past projects) as a single PDF document to
hiring(a)dissem.in . Applications will be evaluated on a rolling basis.
Early applications are recommended.
=== Acknowledgment ===
This project is funded with support from the French National Fund for
Open Science.
<tl;dr>: Your feedback as a technically-minded Wikimedian is welcome on
https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_…
Hi everyone,
last year[1] the Developer Advocacy team started to work on a single,
central entry point for developers and tech-minded people for
Wikimedia's technical documentation[2].
A central entry point ("developer portal") would cover common technical
use cases to allow existing and future technical contributors and
developers to find the information they need.
Each use case links to its most relevant documentation (i.e. to pages
on wikitech or mediawiki.org).
This is part of a larger initiative to implement an organization
strategy for key technical documents: Understand challenges about
finding and maintaining docs, identify key docs, and investigate ways
to improve our workflows around documentation.
So far we:
* Researched and reviewed existing documentation venues and pages
* Reviewed developer/documentation portals in the broader industry
* Interviewed several engineering teams around technical documentation
workflows, audiences, and key technical docs (the key themes from
these conversations are available, see the link above)
* Created an initial draft for the structure and content of the single
entry point
Now we would like to improve this initial content draft with your help.
1) Please take a look at the initial draft at
https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_…
2) Then, please help improve it by sharing your thoughts and feedback
until *May 25th* at
https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_…
Note that this is only a draft how to structure content.
It is not a design or layout proposal and it is not an implementation.
For additional future work, see also the Phabricator workboard[3].
Next steps include:
* A session at the remote Hackathon (May 22-23; [4])
* Incorporate content improvements, based on your feedback
* Check the documents linked from the single entry point proposal for
accuracy
* Investigate requirements for the technical implementation
* Investigate improvements of processes around technical documentation
(structure, locations, navigation, stewardship, etc).
If you want to learn more about the project, please see
https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal
Thanks to everybody who has provided their valuable input to get to
this stage, and thanks in advance to everyone who will!
Cheers,
andre
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2020-August/093773.html
[2] https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal
[3] https://phabricator.wikimedia.org/tag/wikimedia-developer-portal/
[4] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/