Last modified: 2012-12-12 13:37:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43588, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41588 - Item "kidnapped" after creation
Item "kidnapped" after creation
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
master
All All
: Lowest normal (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on: 41495
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-31 15:03 UTC by Raimond Spekking
Modified: 2012-12-12 13:37 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Raimond Spekking 2012-10-31 15:03:02 UTC
No idea what really happened: 

http://www.wikidata.org/w/index.php?title=Q2106&action=history

I created this item for https://de.wikipedia.org/wiki/Bahnhof_K%C3%B6ln_Messe/Deutz

After a distration of a few minutes the new item was "kidnapped"/"hijacked" (no offence, really!) by another user for another Wikipedia article.
Comment 1 jeblad 2012-10-31 16:52:29 UTC
This kind of thing happens because an item will be without a readable label or description in some language. It is at least possible to stop it if there is one sitelink, we are missing code for this but it is possible, but without any hint these kind of things will happen.

We have a system for fallback languages that could be used to give a readable name if there is none in some language, but it is not working in the item view. It is although working in several other pages.
Comment 2 Lydia Pintscher 2012-10-31 17:09:43 UTC
I'll close this since there are other bugs that we'll need to fix to close this and the "kidnapping" itself can't entirely be fixed.
Comment 3 Andre Klapper 2012-11-06 15:08:49 UTC
What does RESOLVED LATER mean exactly in this case? That fixing this depends on other issues to be fixed first? That it's a WONTFIX (will not be fixed)? Or that it's lowest priority but a valid issue?
Comment 4 Daniel Kinzler 2012-11-06 16:27:44 UTC
@andre: it can't really be fixed directly, but we will work to make it easier to see what content an item has in other languages, so *accidental* kidnapping will become less likely.

"LATER" usually means "bug us again if this is still a problem in a few months".
Comment 5 jeremyb 2012-11-08 16:39:09 UTC
(In reply to comment #4)
> "LATER" usually means "bug us again if this is still a problem in a few
> months".

FWIW, I've never heard that interpretation before.

As far as I knew LATER means "this is not a current high priority and is also a distraction for the next X weeks/months/years and we want to hide it from some searches / reports so that people have a clearer view of what needs to be tackled at the moment" and does *not* mean that there's any expectation that the issue has been fixed or resolved or disappeared or been found to be unreproducible.

So, e.g. support for using alternative backends for storing MW data (not a database and not SQL) might be a legit request but is not something that people should work on in the foreseeable future unless they have some reason to care about it personally. (or funding from someone who does) But it shouldn't necessarily be WONTFIX either. It's not *totally* crazy, a lot can change in a year (or 4 months!) and we could revisit it. (of course that time period can be somewhat context sensitive. but generally would not be "we'll look at it again in 3 weeks". for that you can use milestones. speaking of which... milestones can be added for you if needed. I think.)
Comment 6 Andre Klapper 2012-11-08 16:53:46 UTC
JeremyB: YTou might want to chime in http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html - let's try to keep the "LATER" debate off this specific report. Thanks :)
Comment 7 Daniel Kinzler 2012-11-08 17:12:26 UTC
(In reply to comment #5)
> As far as I knew LATER means "this is not a current high priority and is also a
> distraction for the next X weeks/months/years and we want to hide it from some
> searches / reports so that people have a clearer view of what needs to be
> tackled at the moment" and does *not* mean that there's any expectation that
> the issue has been fixed or resolved or disappeared or been found to be
> unreproducible.

Right, I didn't mean to imply any of that. Practically, for the person who reported the issue, what you said still means "bug us again if this is still a problem in a few months". By them, someone will tell them that someone is looking into it - or more likely, find that nobody looked at it again, so it needs to be re-considered. All I'm saying is that the user should not rely on people re-examining LATER bugs. They need to be poked.
Comment 8 Andre Klapper 2012-12-12 13:16:34 UTC
[Removing RESOLVED LATER as discussed in http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html . Reopening and setting priority to "Lowest" as discussed on IRC.
For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]
Comment 9 Lydia Pintscher 2012-12-12 13:37:23 UTC
Closing as wontfix then. The actual kidnapping can't be fixed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links