Dear Sir,
I thank you for your answer. There were many discussions about this important issue. We have already organized a meeting about the matter and created https://m.wikidata.org/wiki/Wikidata:Database_evaluation. Other works can be https://iswc2017.semanticweb.org/wp-content/uploads/papers/PostersDemos/pap… and http://snap.stanford.edu/wikiworkshop2016/papers/Wiki_Workshop__WWW_2016_pa…. This research project is absolutely simple. We define critical matters in the structure of the information provided by Wikidata and we try to develop easy tools to solve them. For example, if a Wikidata property X is asymmetric and X(A,B) exists, then X(B,A) is not possible. However, this particular situation exists in Wikidata. Here, we need a simple tool that let a triple X(A,B) highlighted in yellow if the triple X(B,A) exists. As you see here, the creation of such a tool is simple and does not require a lot of time.
Yours Sincerely,
Houcemeddine Turki (he/him)
Medical Student, Faculty of Medicine of Sfax, University of Sfax, Tunisia
Undergraduate Researcher, UR12SP36
GLAM and Education Coordinator, Wikimedia TN User Group
Member, WikiResearch Tunisia
Member, Wiki Project Med
Member, WikiIndaba Steering Committee
Member, Wikimedia and Library User Group Steering Committee
Co-Founder, WikiLingua Maghreb
Founder, TunSci
____________________
+21629499418
-------- Message d'origine --------
De : Andre Klapper <aklapper(a)wikimedia.org>
Date : 2019/07/24 21:25 (GMT+01:00)
À : wikitech-l(a)lists.wikimedia.org
Objet : Re: [Wikitech-l] Looking for a Wikimedia tool developer for our research project
Hi,
On Wed, 2019-07-24 at 20:13 +0000, Houcemeddine A. Turki wrote:
> I thank you for your efforts. I am working on a research project to
> ameliorate linked data quality of Wikidata. I am looking for a
> develop who can create Gadget tools like Merge that can be
> implemented on Wikidata to adjust common deficiencies. I have several
> ideas on how to develop the Gadget tools.
Could you be more specific, please? Have there been public discussions
on wikidata.org related to your ideas, that you could link to?
Also, if you asked me to do work I'd probably want to know if it's more
like two hours or more like two weeks, plus what *exactly* you are
thinking of. Otherwise I could not judge if I had sufficient skills.
> But, I lack the skills needed to do that.
See https://www.mediawiki.org/wiki/Gadget_kitchen for some basics.
> I ask if someone can join our research project and create the tools
> for our work. I will attend Wikimania from 16 to 18 August 2019 and I
> will be honoured to meet him during the conference.
I guess you wanted to write "them", to also include non-male people. :)
Cheers,
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Dear all,
I thank you for your efforts. I am working on a research project to ameliorate linked data quality of Wikidata. I am looking for a develop who can create Gadget tools like Merge that can be implemented on Wikidata to adjust common deficiencies. I have several ideas on how to develop the Gadget tools. But, I lack the skills needed to do that. I ask if someone can join our research project and create the tools for our work. I will attend Wikimania from 16 to 18 August 2019 and I will be honoured to meet him during the conference.
Yours Sincerely,
Houcemeddine Turki (he/him)
Medical Student, Faculty of Medicine of Sfax, University of Sfax, Tunisia
Undergraduate Researcher, UR12SP36
GLAM and Education Coordinator, Wikimedia TN User Group
Member, WikiResearch Tunisia
Member, Wiki Project Med
Member, WikiIndaba Steering Committee
Member, Wikimedia and Library User Group Steering Committee
Co-Founder, WikiLingua Maghreb
Founder, TunSci
____________________
+21629499418
Dear all,
I thank you for your efforts. I am working on a research project to ameliorate linked data quality of Wikidata. I am looking for a develop who can create Gadget tools like Merge that can be implemented on Wikidata to adjust common deficiencies. I have several ideas on how to develop the Gadget tools. But, I lack the skills needed to do that. I ask if someone can join our research project and create the tools for our work. I will attend Wikimania from 16 to 18 August 2019 and I will be honoured to meet him during the conference.
Yours Sincerely,
Houcemeddine Turki (he/him)
Medical Student, Faculty of Medicine of Sfax, University of Sfax, Tunisia
Undergraduate Researcher, UR12SP36
GLAM and Education Coordinator, Wikimedia TN User Group
Member, WikiResearch Tunisia
Member, Wiki Project Med
Member, WikiIndaba Steering Committee
Member, Wikimedia and Library User Group Steering Committee
Co-Founder, WikiLingua Maghreb
Founder, TunSci
____________________
+21629499418
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2019.07. This bundle is The bundle is compatible with MediaWiki
1.32 or above and requires PHP 7.0.0 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar…
* sha256sum: 84cb6de241f62c7e5e9853d74390c4ffbf55cf35aab930c36f9ec5733a351130
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel, CleanChanges and LocalisationUpdate ==
* Maintenance and localization updates only.
== cldr ==
* Update to cldr 35.1 ([https://phabricator.wikimedia.org/T220906 T220906]).
* Maintenance and localization updates.
== Translate ==
* Translate now requires MediaWiki >= 1.32.0. Please upgrade!
=== Noteworthy changes ===
* Reduced the size of the cache used by the Translate extension
([https://phabricator.wikimedia.org/T213802 T213802]).
* Fixed incorrect link to the message on the translate editor
([https://phabricator.wikimedia.org/T222588 T222588]).
* Fixed the tabs on the message table on Special:Translate with the
new Timeless theme.
* Added a new MessageValidator framework to improve translation
validation. ([https://phabricator.wikimedia.org/T204568 T204568])
([[Help:Extension:Translate/Validators|See documentation]]).
* Fixed invalid more warnings label shown during message translation
([https://phabricator.wikimedia.org/T220789 T220789])
* Moved Translate special pages to a specific Translation section in
Special:SpecialPages ([https://phabricator.wikimedia.org/T227393
T227393])
* Fixed issue with base page not getting removed when removing translatable page
* Removed unused global variable <code>$wgTranslateCC</code>
([https://phabricator.wikimedia.org/T214356 T214356])
== UniversalLanguageSelector ==
* UniversalLanguageSelector now requires MediaWiki >= 1.32.0. Please upgrade!
==== Input Methods ====
* Added Afrikaans, N'Ko and Vai syllabary keyboards.
* Added new input methods for languages of Africa without the need for
replacement or key combinations: Akan (ak, tw), Bambara (bm), Dagbani
(dag), Dinka (din), Fula (ff), Ga (gaa) and Wolof (wo).
* Fixed the combining character in Yoruba Alt method.
* Minor fixes in existing layouts with replacements and key
combinations for Akan, Dagbani, Dinka, Fula, and Ga.
Hi All,
Reminder there is a TechCom RFC on the RFC "Merge Extension: Theme
into core": <https://phabricator.wikimedia.org/T122924> in
#wikimedia-office on July 24th at 21:00 UTC/23:00 CEST/14:00 PDT
The RFC is a proposal to merge the Extension:Theme into core because
of the limitations it has being an extension.
Thanks,
-Kate
--
Kate Chapman
Senior Program Manager, Core Platform
Wikimedia Foundation
kchapman(a)wikimedia.org
Hello,
I use parsoid to publish email messages into wiki and have a little
issue.
Sometimes generated article has "preformatted" fragments that do not
have any special formatting in source text.
After investigation I discovered that it is caused by spaces that start
new line in HTML text.
When source HTML of email is viewed in browser these spaces do not have
any effect, but after converting to wikitext they became part of markup.
Next, trying to discover they way parsoid works I have seen that
normally these spaces became surronded with <nowiki> tag, but in some
circumtances it does not happen.
So I made test HTML file to see different results of converting:
<html>
<head>
</head>
<body>
<p>test2<span>
test3
</span></p>
<p><span>test2
test3
</span></p>
<p>textx<span>test2
test3
</span></p>
</body>
</html>
The result of conversion is:
test2<span>
test3
</span>
<span>test2
<nowiki> </nowiki>test3
</span>
textx<span>test2
<nowiki> </nowiki>test3
</span>
It seems that if new line is just at end of <span> tag, <nowiki> is not
inserted.
How do you get patches merged when you don't actually know anyone to
review it?
Sometimes you just get lucky, but sometimes you add a bunch of people, a
few others even wander in and +1 it, you ask a few people with core +2
to take a look, and then you're still waiting on a product owner to
maybe even comment at all and you can't get anyone to actually merge it
months later.
The patch I'm referring to right now is this:
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Interwiki/+/501820
It adds another global inheritance feature, this time for interlanguage
links, where they can just be set once on a single wiki and other wikis
in the farm can likewise just use those instead of local ones. Separate
setting from the global interwikis because ones that would share this
will be a smaller subset than would share general interwikis.
Normally we'd just merge each other's patches in-team or go get an
actual product owner to review it, but there are a couple of problems
with this:
* The patch was co-authored by Jack Phoenix and me (and I defined the
design in the first place), so neither of us can meaningfully review
it any further than we already have. No one else has +2 here.
* We don't know any product owners (in fact we're not even sure if
there are any product owners), so we can't get them to review it.
Given the total lack of comment, normally we might just declare this
as 'nobody cares' after awhile and charge ahead regardless, but:
* Nobody else we know with general +2 is willing to merge it without
weigh-in from the product owners/actually has any time to review it
in the first place, either.
Basically, uh, can anyone else help us with this? Any of this? Given the
nature of the patch we really do kind of need it merged so it can get
translations.
-I