Tgr created this task.Tgr added projects: MediaWiki-extensions-WikibaseClient, MediaWiki-Vagrant.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONAfter pulling up a new vagrant box with the wikidata role and visiting the main page of the default wiki (dev.wiki.l
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2018-02-21T00:14:05Z] Synchronized wmf-config/InitialiseSettings.php: SWAT: [[gerrit:412664|Enable x-kill feature everywhere]] T186714 T184322 (duration: 01m 13s)TASK DETAILhttps://phabricator.wikimedia.org/T184322EMAIL PREFERENCE
Stashbot added a comment.
Mentioned in SAL (#wikimedia-operations) [2018-02-21T00:14:05Z] Synchronized wmf-config/InitialiseSettings.php: SWAT: [[gerrit:412664|Enable x-kill feature everywhere]] T186714 T184322 (duration: 01m 13s)TASK DETAILhttps://phabricator.wikimedia.org/T186714EMAIL PREFERENCE
gerritbot added a comment.
Change 412664 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable x-kill feature everywhere
https://gerrit.wikimedia.org/r/412664TASK DETAILhttps://phabricator.wikimedia.org/T184322EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpref
gerritbot added a comment.
Change 412664 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable x-kill feature everywhere
https://gerrit.wikimedia.org/r/412664TASK DETAILhttps://phabricator.wikimedia.org/T186714EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpref
Tgr added a comment.
In T184000#3987414, @Addshore wrote:
So, again overriding the current wikidata description here is a breaking change.
We should not do that.
If we want to add something new, such as an article description, lets add it under a new key called "article-description" instead of r
awight added a parent task: T187836: [Epic] Audit of pending ORES GUI deployments.
TASK DETAILhttps://phabricator.wikimedia.org/T127470EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Glorian_WD, awightCc: Glorian_WD, Ladsgroup, Halfak, Glorian_Yapinus, Sumit,
Addshore added a comment.
In T184000#3984789, @Tgr wrote:
The parser function hook stores the argument of the parserfunction in the ParserOutput's page properties with a wikibase-description-override key.
So, this doesn't really have anything to do with wikibase, what we are adding here is a p
Ladsgroup added a subscriber: daniel.Ladsgroup added a comment.
So the reason I made MessageLocalizer is that we wanted to inject RequestContext somewhere just to use the msg method and @daniel pointed out that this class is a huge kitchen sink that are dragging around. That interface is an attempt
Smalyshev added subscribers: Lydia_Pintscher, daniel, Smalyshev.Smalyshev added a comment.
I'd go with wdqs-internal. Not sure what the suffix would be - it should probably only be accessible from production machines, but we need to also be able to test it somehow I think - i.e. to make sure the en
Smalyshev added a comment.
I need it only on jumbo I think, that's where I'll be connecting.TASK DETAILhttps://phabricator.wikimedia.org/T187296EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: elukey, Ottomata, Aklapper, Nuria, Ladsgroup, Pchelolo,
Ladsgroup added a comment.
Our idea would be to have it as memcached.TASK DETAILhttps://phabricator.wikimedia.org/T187775EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: thiemowmde, LadsgroupCc: daniel, Lucas_Werkmeister_WMDE, Ladsgroup, WMDE-leszek, thiemowmde
Ladsgroup added a subtask: T186714: enable x-kill feature on Commons.
TASK DETAILhttps://phabricator.wikimedia.org/T184322EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: LadsgroupCc: Agabi10, RP88, IKhitron, Joe, hoo, Doc_James, PokestarFan, eranroz, Izno, Oli
Ladsgroup added a parent task: T184322: Enable fine grained lua tracking gradually in client wikis.
TASK DETAILhttps://phabricator.wikimedia.org/T186714EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: LadsgroupCc: gerritbot, Mike_Peel, Aklapper, Lydia_Pintscher
gerritbot added a comment.
Change 412664 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[operations/mediawiki-config@master] Enable x-kill feature everywhere
https://gerrit.wikimedia.org/r/412664TASK DETAILhttps://phabricator.wikimedia.org/T184322EMAIL PREFERENCEShttps://
Tgr added a subscriber: TheDJ.Tgr added a comment.
In T184000#3987260, @Alsee wrote:
The Wikidata label is a description of the Wikidata item.
"Label" in Wikidata terminology is the article title (e.g. Q663375 has the English label "hatmaking" and English description "manufacture and design of h
Alsee added a comment.
I'm not familiar with all of the API issues, but if this helps:
The magicword Shortdesc: is actually a description of the article. The Wikidata label is a description of the Wikidata item. Someone thought Wikidata labels could conveniently be re-used as if they were an articl
Ramsey-WMF moved this task from Untriaged to Desired epics on the Multimedia board.Ramsey-WMF triaged this task as "Normal" priority.
TASK DETAILhttps://phabricator.wikimedia.org/T141622WORKBOARDhttps://phabricator.wikimedia.org/project/board/48/EMAIL PREFERENCEShttps://phabricator.wikimedia.org/se
daniel added a comment.
...as to registering the description as used: this should be governed by a separate setting. It really has nothing to do with the magic word.
I think the setting should be generic, not limited to descriptions. E.g.:
$wgWBClientSettings['impliciteUsageAspects'] = [ 'D', 'L'
daniel added a comment.
@Tgr Sounds like a decent plan. In an ideal world, the "short description" functionality would be factored out of wikidata, so it could be backed by *just* the magic word or *just* wikidata or both combined or something else. But that would of course break B/C. So I suppose
Lucas_Werkmeister_WMDE added a comment.
I think this should be working now, but I’ll try a manual test, just to make sure.TASK DETAILhttps://phabricator.wikimedia.org/T187061EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDECc: gerritbot, A
WMDE-leszek moved this task from Review to Done on the Wikidata-Sprint-2018-02-14 board.WMDE-leszek removed a project: Patch-For-Review.
TASK DETAILhttps://phabricator.wikimedia.org/T187061WORKBOARDhttps://phabricator.wikimedia.org/project/board/3247/EMAIL PREFERENCEShttps://phabricator.wikimedia.o
WMDE-leszek updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...- [x] [small helper function](https://gerrit.wikimedia.org/r/411252)
- [ - [x] [`RangeChecker`](https://gerrit.wikimedia.org/r/411041)
- [ - [x] [`CachingResultsBuilder`](https://gerrit.wikimedia.org/r/411248)TAS
gerritbot added a comment.
Change 406608 abandoned by WMDE-leszek:
[DNM] Move the lexeme "displaying" logic to the LexemePresenter
https://gerrit.wikimedia.org/r/406608TASK DETAILhttps://phabricator.wikimedia.org/T185332EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailprefere
gerritbot added a comment.
Change 406306 abandoned by WMDE-leszek:
[DNM] Display lexemes in statements
https://gerrit.wikimedia.org/r/406306TASK DETAILhttps://phabricator.wikimedia.org/T185332EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: WMDE-leszek, gerrit
gerritbot added a comment.
Change 409830 abandoned by WMDE-leszek:
[DNM] Add SQL-index-based LexemePresenter
https://gerrit.wikimedia.org/r/409830TASK DETAILhttps://phabricator.wikimedia.org/T186606EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: WMDE-leszek,
thiemowmde added a comment.
Personally, I'm totally fine with using any kind of cache, might it be an in-memory one or something else. My worst-case scenario is as follows: Let's say we have 10 million Lexemes, 2 lemmas per Lexeme, 20 bytes per lemma. The cache would need to hold about 0.4 gigabyte
Lucas_Werkmeister_WMDE added a comment.
I admit I’m tempted to go with the much simpler … fake EntityDocument …
Hm, though if we do go with a temporary solution, an alternative approach would be a new Context implementation, which only supports storeCheckResultInArray (because that’s all we need f
Lucas_Werkmeister_WMDE added a subscriber: Ladsgroup.Lucas_Werkmeister_WMDE added a comment.
what do we do?
So here are the things that you need in order to check constraints on a Context:
type (e. g. “used as qualifier” constraints)
snak (e. g. “one of” constraints)
snak rank (many constraint t
Hjfocs claimed this task.Hjfocs added a subscriber: Afnecors.Hjfocs moved this task from Upcoming to Doing on the Wikidata-primary-sources board.
TASK DETAILhttps://phabricator.wikimedia.org/T178303WORKBOARDhttps://phabricator.wikimedia.org/project/board/2788/EMAIL PREFERENCEShttps://phabricator.wi
gerritbot added a comment.
Change 411307 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Use ViolationMessageRenderer in CheckConstraintParameters
https://gerrit.wikimedia.org/r/411307TASK DETAILhttps://phabricator.wikimedia.org/T187186EMAIL PREFERENCEShttps://phabr
WMDE-leszek added a comment.
I just had a chat with @Ladsgroup and he suggested regarding wbl_lemmas table the following: what about not putting this stuff in the database table but storing all lemmas for display in the cache (or cache them when they're used). I am bit ignorant, but as wbl_lemmas i
Ottomata added a comment.
Is there a reason we want to do this on main instead of jumbo? Stas will be consuming from jumbo, since it has timestamp offset support.TASK DETAILhttps://phabricator.wikimedia.org/T187296EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/T
thiemowmde updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...Suggestion is to go with VARCHAR(20) for both columns.
Suggestion is to //not// reserve space for repository prefixes. Even on a multi-repository setting the Item references used for lexical categories and langua
Lucas_Werkmeister_WMDE created this task.Lucas_Werkmeister_WMDE added projects: Wikidata, Wikibase-Quality, Wikibase-Quality-Constraints.Herald added a subscriber: Aklapper.
TASK DESCRIPTION@Ladsgroup pointed out in a comment on I154d9cdebe that ConstraintParameterRenderer and ViolationMessageRende
thiemowmde updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...* The numbers of rows in the proposed wbl_item_references tables is going to be identical to the total number of Lexemes. There is only one lemma per Lexeme (in only one language),According https://www.mediawiki.o
WMDE-leszek added a comment.
Regarding number of lemmas per lexeme, @Lucas_Werkmeister_WMDE makes a good point. As far as I remember, @thiemowmde and I talked IRL last week about the number there, and we said something like that the security guesstimate would be to say the total number of lemmas wo
thiemowmde added a comment.
We should fix https://commons.wikimedia.org/wiki/File:Lexeme_data_model.png then, because it very prominently says there is only "one" lemma. It could be this is meant to be interpreted as "one" value that can somehow contain multiple values. I wonder what the benefit of
WMDE-leszek added a comment.
One of the longest words in an English dictionary is "Supercalifragilisticexpialidocious" (34 characters).
General note: English is probably not the best language to look for in the context of long words (even German beats it easily).
In contract to Item labels, the l
Lucas_Werkmeister_WMDE added a comment.
I’m not sure how this would look – non-static serialize and static deserialize methods on Context and its subclasses? Or should it be a separate kind of ContextSerialization service? I think my colleagues know more about this than me, there’s a lot of seriali
daniel added a comment.
Am 20.02.2018 um 15:44 schrieb Lucas_Werkmeister_WMDE:
Lucas_Werkmeister_WMDE added a comment.
There is only one lemma per Lexeme (in only one language)
Don’t we have something to support e. g. “color” and “colour” for the same
lexeme? I’m not sure if that’s two lemmas o
Lucas_Werkmeister_WMDE added a comment.
There is only one lemma per Lexeme (in only one language)
Don’t we have something to support e. g. “color” and “colour” for the same lexeme? I’m not sure if that’s two lemmas or one lemma (multilingual text) with two spellings, but there seems to be some nee
thiemowmde added a project: Technical-Debt.
TASK DETAILhttps://phabricator.wikimedia.org/T57783EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: thiemowmdeCc: samuwmde, Ricordisamoa, Aklapper, Wikidata-bugs, thiemowmde, JanZerebecki, aude, Lydia_Pintscher, hoo,
thiemowmde added a project: Community-consensus-needed.thiemowmde triaged this task as "Low" priority.thiemowmde added a comment.
As for the code, it is currently not possible and not planned to support additional languages for labels and descriptions that are not supported by MediaWiki core. Addin
ReleaseTaggerBot added a project: MW-1.31-release-notes (WMF-deploy-2018-02-20 (1.31.0-wmf.22)).
TASK DETAILhttps://phabricator.wikimedia.org/T187652EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abian, ReleaseTaggerBotCc: gerritbot, Lucas_Werkmeister_WMDE, a
thiemowmde triaged this task as "Normal" priority.thiemowmde added projects: MediaWiki-extensions-WikibaseRepository, Regression, Easy.thiemowmde moved this task from incoming to ready to go on the Wikidata board.
TASK DETAILhttps://phabricator.wikimedia.org/T187755WORKBOARDhttps://phabricator.wiki
thiemowmde updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTIONTwo new secondary database tables are proposed:
* wbl_lemmas stores the lemma (a text value) for each Lexeme.
* wbl_item_references (or similar) stores two Item references (lexical category and language) for each Lex
abian closed this task as "Resolved".
TASK DETAILhttps://phabricator.wikimedia.org/T187652EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: abianCc: gerritbot, Lucas_Werkmeister_WMDE, abian, Aklapper, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Agabi10,
gerritbot added a comment.
Change 412644 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Script exportEntityMapping: Support prefix for table names in database
https://gerrit.wikimedia.org/r/412644TASK DETAILhttps://phabricator.wikimedia.org/T187652EMAIL PREFERENCES
thiemowmde created this task.thiemowmde triaged this task as "Normal" priority.thiemowmde added projects: Wikidata, Lexicographical data, Wikidata-Sprint-2018-02-14.Herald added a subscriber: Aklapper.
TASK DESCRIPTIONTable size
WIP
Item references
WIP
Lemma column length
The numbers of r
ReleaseTaggerBot added a project: MW-1.31-release-notes (WMF-deploy-2018-02-20 (1.31.0-wmf.22)).
TASK DETAILhttps://phabricator.wikimedia.org/T185711EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDE, ReleaseTaggerBotCc: gerritbot, Aklapper
Lucas_Werkmeister_WMDE closed this task as "Resolved".Lucas_Werkmeister_WMDE moved this task from Review to Done on the Wikidata-Sprint-2018-02-14 board.
TASK DETAILhttps://phabricator.wikimedia.org/T185711WORKBOARDhttps://phabricator.wikimedia.org/project/board/3247/EMAIL PREFERENCEShttps://phabri
Lucas_Werkmeister_WMDE closed subtask T185711: Make Constraint serializable as "Resolved".
TASK DETAILhttps://phabricator.wikimedia.org/T185709EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Lucas_Werkmeister_WMDECc: Aklapper, Lucas_Werkmeister_WMDE, Lahi, Gq8
gerritbot added a comment.
Change 412741 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Make Constraint serializable
https://gerrit.wikimedia.org/r/412741TASK DETAILhttps://phabricator.wikimedia.org/T185711EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings
gerritbot added a comment.
Change 411041 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Add DependencyMetadata to RangeChecker results
https://gerrit.wikimedia.org/r/411041TASK DETAILhttps://phabricator.wikimedia.org/T187061EMAIL PREFERENCEShttps://phabricator.wiki
Hjfocs closed subtask T178306: Add SPARQL box in the primary sources filter as "Resolved".
TASK DETAILhttps://phabricator.wikimedia.org/T176638EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Afnecors, HjfocsCc: Aklapper, Afnecors, Lahi, Gq86, GoranSMilovanovic
Hjfocs closed this task as "Resolved".Hjfocs moved this task from Doing to Done on the Wikidata-primary-sources board.Hjfocs added a comment.
Working in the gadget version: https://github.com/Wikidata/primarysources/tree/betaTASK DETAILhttps://phabricator.wikimedia.org/T178306WORKBOARDhttps://phabr
gerritbot added a comment.
Change 412873 had a related patch set uploaded (by Gehel; owner: Gehel):
[operations/puppet@production] wdqs: allow configuration of kafka based updates
https://gerrit.wikimedia.org/r/412873TASK DETAILhttps://phabricator.wikimedia.org/T185951EMAIL PREFERENCEShttps://phab
Lucas_Werkmeister_WMDE updated the task description. (Show Details)
CHANGES TO TASK DESCRIPTION...- [x] [`NowValue` additions](https://gerrit.wikimedia.org/r/411237)
- [ - [x] [future time in `DependencyMetadata`](https://gerrit.wikimedia.org/r/411038)
- [ - [x] [small helper function](https://gerr
TheDJ added a comment.
@Tgr I'm assuming no markup (like in wikidata). What about text length restrictions ?
Regarding reflecting the wiki base value, i think it's best to indeed have that as an additional value within terms, but probably not by default. I'do think we would need some sort of marke
gerritbot added a comment.
Change 374328 abandoned by Urbanecm:
Restrict merging rights to autoconfirmed users on wikidatawiki
Reason:
Some concerns were raised, feel free to restore if this will be needed again.
https://gerrit.wikimedia.org/r/374328TASK DETAILhttps://phabricator.wikimedia.org/T1
Urbanecm removed projects: Patch-For-Review, User-Urbanecm.Urbanecm added a comment.
Removing from my radar.TASK DETAILhttps://phabricator.wikimedia.org/T174345EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: UrbanecmCc: Liuxinyu970226, Esc3300, Bugreporter, ma
Gehel added a project: Epic.
TASK DETAILhttps://phabricator.wikimedia.org/T178492EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GehelCc: Daniel_Mietchen, BBlack, Lydia_Pintscher, Volans, mobrovac, Jonas, Aklapper, debt, Smalyshev, Gehel, Lahi, PDrouin-WMF, Gq
Gehel created this task.Gehel triaged this task as "High" priority.Gehel added projects: Wikidata-Query-Service, Discovery-Wikidata-Query-Service-Sprint, Discovery.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONTASK DETAILhttps://phabricator.wikimedia.org/T187
Gehel created this task.Gehel triaged this task as "High" priority.Gehel added projects: Wikidata-Query-Service, Discovery-Wikidata-Query-Service-Sprint, Discovery.Herald added a subscriber: Aklapper.Herald added a project: Wikidata.
TASK DESCRIPTIONTASK DETAILhttps://phabricator.wikimedia.org/T187
Gehel added a subtask: Unknown Object (Task).
TASK DETAILhttps://phabricator.wikimedia.org/T182991EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: RobH, GehelCc: Lucas_Werkmeister_WMDE, RobH, Gehel, EBjune, Davinaclare77, Qtn1293, Lahi, Gq86, Darkminds3113, Gor
Gehel closed subtask T178548: Cost estimate for a new WDQS cluster as "Resolved".
TASK DETAILhttps://phabricator.wikimedia.org/T178492EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: GehelCc: Daniel_Mietchen, BBlack, Lydia_Pintscher, Volans, mobrovac, Jonas, Ak
WMDE-leszek removed WMDE-leszek as the assignee of this task.WMDE-leszek moved this task from In Progress to Review on the Wikidata-Sprint-2018-02-14 board.
TASK DETAILhttps://phabricator.wikimedia.org/T187316WORKBOARDhttps://phabricator.wikimedia.org/project/board/3247/EMAIL PREFERENCEShttps://pha
68 matches
Mail list logo