[Wikidata-l] Link to gerrit not working (Re: weekly summary #52)

Hi all, On Sat, Apr 6, 2013 at 12:43 AM, Lydia Pintscher wrote: > You can follow our commits at > https://gerrit.wikimedia.org/r/#/q/(status:open+project:mediawiki/extensions/Wikibase)+OR+(status:merged+project:mediawiki/extensions/Wikibase),n,z I never succeed in making this link work. Am I the

Re: [Wikidata-l] Page history and properties

On 5 April 2013 23:53, Michael Hale wrote: > But you do agree that it is easier to curate articles by updating one value > in a database than updating the value separately everywhere it appears? Absolutely. But in my experience Wikipedia editors care about the product of a readable, intelligable

[Wikidata-l] weekly summary #52

Heya folks :) Here's your summary of what happened around Wikidata over the last week. = Development = * The first year is over. Thank you everyone for being amazing and helping to build Wikidata and making it more than we could possibly have hoped for already. <3 * Put a lot of work into impro

Re: [Wikidata-l] Page history and properties

But you do agree that it is easier to curate articles by updating one value in a database than updating the value separately everywhere it appears? > From: g.m.haged...@gmail.com > Date: Fri, 5 Apr 2013 23:45:10 +0200 > To: wikidata-l@lists.wikimedia.org > Subject: Re: [Wikidata-l] Page history a

Re: [Wikidata-l] Page history and properties

On 5 April 2013 23:19, Michael Hale wrote: > So you agree that it is more important to reduce clutter than to add > functionality that very few people use? No, I strongly disagree with this. I think the functionality of being able to curate the page Wikipedia editors care for should have highest

Re: [Wikidata-l] Page history and properties

So you agree that it is more important to reduce clutter than to add functionality that very few people use? They used to save backups of the HTML versions of pages, but they stopped 5 years ago because it's not worth the extra overhead for something so few people use. http://dumps.wikimedia.or

Re: [Wikidata-l] Page history and properties

On 5 April 2013 21:41, Michael Hale wrote: > Well, I could make a view that shows the diff of a Wikipedia article stacked > on top of the diff for the corresponding Wikidata item on my computer in a > few minutes. But diffs can be very long sometimes, so there would be a lot > of discussion about

Re: [Wikidata-l] Page history and properties

Well, I could make a view that shows the diff of a Wikipedia article stacked on top of the diff for the corresponding Wikidata item on my computer in a few minutes. But diffs can be very long sometimes, so there would be a lot of discussion about whether that view is more appropriate than just m

Re: [Wikidata-l] Page history and properties

On 5 April 2013 20:05, Michael Hale wrote: > The thing to remember is that the history of a page is the history of the > wiki markup for the page, not the history of the rendered HTML. It would be > misleading if edits were shown in the markup history for an article each > time a template or Wikid

Re: [Wikidata-l] Page history and properties

Oh, nice. > From: lydia.pintsc...@wikimedia.de > Date: Fri, 5 Apr 2013 20:07:44 +0200 > To: wikidata-l@lists.wikimedia.org > Subject: Re: [Wikidata-l] Page history and properties > > On Fri, Apr 5, 2013 at 8:05 PM, Michael Hale wrote: > > The thing to remember is that the history of a page is th

Re: [Wikidata-l] Page history and properties

On Fri, Apr 5, 2013 at 8:05 PM, Michael Hale wrote: > The thing to remember is that the history of a page is the history of the > wiki markup for the page, not the history of the rendered HTML. It would be > misleading if edits were shown in the markup history for an article each > time a template

Re: [Wikidata-l] Page history and properties

The thing to remember is that the history of a page is the history of the wiki markup for the page, not the history of the rendered HTML. It would be misleading if edits were shown in the markup history for an article each time a template or Wikidata item changed because reverting the markup to

Re: [Wikidata-l] Usability flaws

On 05/04/13 16:00, Lukas Benedix wrote: * when no text is available in the users language the statement section looks like this: http://lbenedix.monoceres.uberspace.de/screenshots/mejpee0fxi_(2013-04-05_15.34.41).png

[Wikidata-l] Usability flaws

Hi, I had a short look at the current UI and the test-repo and found some usability and design flaws: * when no text is available in the users language the statement section looks like this: http://lbenedix.monoceres.uberspace.de/screenshots/mejpee0fxi_(2013-04-05_15.34.41).png

Re: [Wikidata-l] Page history and properties

My concern is, that the Wikidata editors, those not with random editing behavior, but those who are curators/caretakers of specific pages, experience a disempowerment, because they loose control. I view the decision to inform about wikidata changes only in the short-lived recentchanges, but not in

Re: [Wikidata-l] Page history and properties

Le 2013-04-05 09:32, Gregor Hagedorn a écrit : On 4 April 2013 22:23, Michael Hale wrote: trench, then I just want to update it on Wikidata, and then every article that references it will be updated. I don't want to have to update it on Wikidata and then go do a null edit on every article tha

[Wikidata-l] Page history and properties

Storage aside, one major problem with the save-in-the-article is that it shovels a lot of increased complexity onto the Wikipedia editors - one of the hopes for Wikidata is that we can convert the existing morass of WP template data into invoking {{infobox city}} and have population, etc, magically

Re: [Wikidata-l] Page history and properties

On 4 April 2013 22:23, Michael Hale wrote: > trench, then I just want to update it on Wikidata, and then every article > that references it will be updated. I don't want to have to update it on > Wikidata and then go do a null edit on every article that uses that > information. You are correct, t