Hi all,
finding, inserting and removing templates becomes now easier on a group of
wikis with the new bundle of changes from WMDE’s Technical Wishes team. All
other wikis will follow over the course of this year.
In the VisualEditor, 2017 wikitext editor and 2010 WikiEditor, an improved
search will help you find relevant templates even if you’re not sure of
their exact name. The search will look for matches for your keyword within
the entire template name, not just its beginning [1]. In VisualEditor, a back
button will be added to the “Insert a template” dialog, making it easier to
explore different templates [1]. For the same dialog, a warning will appear
if you have entered data and close the form without saving. In the past,
all changes were just lost [1]. Last but not least, it will be clearer how
to remove a template from a page with the new “delete” button next to the
“edit” button in a template’s context menu of the VisualEditor [2].
We plan to deploy these improvements on German, Greek, Malay, Twi, French,
Hungarian, Turkish, Hebrew, Finnish Wikipedia and English Wikivoyage &
Nauruan Wiktionary on 7th of July. If you have any feedback, please let us
know on the projects’ talk pages [3] [4].
[1]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Finding_and_inserting…
[2]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_f…
[3]
https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Finding_and_inse…
[4]
https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Removing_a_templ…
Timur
for the Technical Wishes team
--
Timur Vorkul
Technische Wünsche
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23–24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Bleiben Sie auf dem neuesten Stand! Aktuelle Nachrichten und spannende
Geschichten rund um Wikimedia, Wikipedia und Freies Wissen im Newsletter: Zur
Anmeldung <https://www.wikimedia.de/newsletter/>.
Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
Wikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hello,
I have been thinking of a way to organise data in Wiktionary that would allow
for words to automatically show translations to other languages with much less
work than is currently required.
Currently, translations to other languages have to be added manually, meaning
they are not automatically propagated across language pairs. What I mean by
this is showcased in the following example:
1. I create a page for word X in language A.
2. I create a page for word Y in language B.
3. I add a translation to the page for word X, and state that it translates to
word Y in language B.
4. If I want the page for word Y to show that it translates to word X in
language A, I have to do this manually.
Automating this seems a bit tricky. I think that the key is acknowledging that
meanings can be separated from language and used as the links of translation.
In this view, words and their definitions are language-specific, but meanings
are language-agnostic.
Because I may have done a bad job at explaining this context, I have created a
short example in the form of an sqlite3 SQL script that creates a small
dictionary database with two meanings for the word "desert"; one of the
meanings has been linked to the corresponding words in Spanish and in German.
The script mainly showcases how words can be linked across languages with
minimal rework.
You can find the script attached. To experiment with this, simply run
.read feature_showcase.sql
within an interactive sqlite3 session. (There may be other ways of doing it
but this is how I tested it.)
I believe this system can also be used to automate other word relations such as
hyponyms and hypernyms, meronyms and holonyms, and others. It can also allow
looking up words in other languages and getting definitions in the language of
choice. In short, it would allow Wiktionary to more effortlessly function as
a universal dictionary.
Has something like this been suggested before? I would be pleased to receive
feedback on this idea.
With kind regards,
Wolter HV
Hi,
wikibugs needs to be autovoiced in all the IRC channels it speaks in to
avoid being killed by antispam bots.
If wikibugs speaks in your channel and isn't voiced, please have a
channel founder autovoice it:
/msg chanserv flags <#channel> wikibugs +Vv
<https://phabricator.wikimedia.org/T283983> has a list of channels and
the people with appropriate permissions should've been pinged on it.
If your IRC channel isn't in use anymore please file a bug (or submit a
patch!) to have wikibugs removed from it.
Thanks,
-- Legoktm
Hi all.
Is anyone able to help me troubleshoot getting Fresh set up and working on
Windows? I recently set up mediawiki with docker and want to be able to use
fresh. I use Windows 10.
Based on the instructions in the latest version of the README file[1], I
ran within git bash
```
bash -c 'curl -fsS
https://gerrit.wikimedia.org/g/fresh/+/21.04.1/bin/fresh-node10?format=TEXT
\
| base64 --decode > /usr/local/bin/fresh-node \
&& echo "d38c34d542dc685669485bbe04a9d1a926a224a4ba27a01d59ae563558d8e987
/usr/local/bin/fresh-node" | shasum -a 256 -c \
&& chmod +x /usr/local/bin/fresh-node \
&& echo -e "\n\xf0\x9f\x8c\xb1\x20Fresh\x20is\x20ready\x21\n"||(echo -e
"\xe2\x9d\x8c";false)'
```
and got the error
```
bash: line 1: /usr/local/bin/fresh-node: No such file or directory
curl: (23) Failure writing output to destination
❌
```
Some investigation in the file system shows that `/usr/local` does not
exist. Where should I be trying to install it instead so that it works as a
normal command (eg `fresh-node -env -net`)?
Thanks,
--DannyS712
[1]
https://gerrit.wikimedia.org/r/plugins/gitiles/fresh/+/2eabb06e32a9971b1e95…
Hello,
I would like to push my tests in Jenkins/Gerrit. For the moment, I test manually and with Selenium IDE my extensions :
https://www.mediawiki.org/wiki/Extension:PushAllhttps://www.mediawiki.org/wiki/Extension:NamespaceDatahttps://www.mediawiki.org/wiki/Extension:LinkedWiki
I need to have two instances of Mediawiki with these extensions because I need to test transferring pages from a private wiki to a public wiki.
For the moment in local, I use two docker containers with Mediawiki (and with Centos7 because I install/compile also specific databases)
I have the time to do this task properly.
How would you do it if you had to?
Thanks in advance.
Karima
Dear All,
I have been trying to develop a tool which uses OAuth with Flask using
mwoauth as specified here[1].
Unfortunately, the OAuth request seems to not work as it ends with no error
messages.
After investigating, it looks like /oauth-callback does not execute (which
seems unusual).
This is not the first time I am doing this but it looks like I can't get
hold of the issue here.
I will appreciate any help!
Thanks
Eugene233
[1]
https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool
On 7/1/21 9:54 AM, Martin Urbanec wrote:
> Hello Brennen and team,
>
> no longer on Freenode -- we're on Libera chat those days. Didn't manage
> to find the template on wiki, so I inform via mail instead.
Yeah, thanks for the heads up - I typically just re-edit the last of
these messages I sent, and missed this.
For future reference, our rough template is here:
https://wikitech.wikimedia.org/wiki/Heterogeneous_deployment/Train_deploys#…
(Sending this to all lists since several folks have already responded
with the same correction. Glad to know people are reading these. :) )
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
<tl;dr>: Your feedback is wanted 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/