https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
abraham.taheriv...@wikimedia.de changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
abraham.taheriv...@wikimedia.de changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Daniel Kinzler daniel.kinz...@wikimedia.de changed:
What|Removed |Added
See Also|
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #20 from Tyler Romeo tylerro...@gmail.com ---
So, just to be clear, the plan is to commit a temporary hack into core just so
a single WMF wiki can shorten their logs until somebody gets around to properly
fixing the bug? That
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #21 from Krinkle krinklem...@gmail.com ---
(In reply to comment #20)
So, just to be clear, the plan is to commit a temporary hack into core just
so a single WMF wiki can shorten their logs until somebody gets around to
properly
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #16 from James Forrester jforres...@wikimedia.org ---
(In reply to comment #14)
See bug 17237 for a solution based on discussion from Amsterdam Hackathon
2013 between Daniel, Tim and Timo.
So this means that, if needed, we can
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #17 from Daniel Kinzler daniel.kinz...@wikimedia.de ---
(In reply to comment #16)
So this means that, if needed, we can proceed with this as a temporary hack
in the Wikibase extension
Which temporary hack are you referring to?
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #18 from Ariel T. Glenn ar...@wikimedia.org ---
(In reply to comment #16)
So this means that, if needed, we can proceed with this as a temporary hack
in
the Wikibase extension before we re-work master as part of the
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #19 from Krinkle krinklem...@gmail.com ---
(In reply to comment #17)
(In reply to comment #16)
So this means that, if needed, we can proceed with this as a temporary hack
in the Wikibase extension
Which temporary hack are
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #15 from Ariel T. Glenn ar...@wikimedia.org ---
+1 from me for that approach. It covers all my concerns.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #14 from Krinkle krinklem...@gmail.com ---
See bug 17237 for a solution based on discussion from Amsterdam Hackathon 2013
between Daniel, Tim and Timo.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #13 from Ariel T. Glenn ar...@wikimedia.org ---
So here is (part of) why the situation is different on wikidata than anywhere
else.
1) Wikidata actually has more edits/sec than anywhere, including en wp.
2) Almost all of those
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #11 from Krinkle krinklem...@gmail.com ---
(In reply to comment #8)
[Speaking with my Product Manager for Admin Tools hat on.]
(In reply to comment #5)
I'm not sure what the point is of disabling auto patrol logging entirely.
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Daniel Kinzler daniel.kinz...@wikimedia.de changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #10 from Tyler Romeo tylerro...@gmail.com ---
(In reply to comment #9)
Can we set up a rolling log instead? Like have the log entries vanish after
30 days (recentchanges table length). After that point you can't tell whether
the
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #9 from Legoktm legoktm.wikipe...@gmail.com ---
(In reply to comment #8)
[Speaking with my Product Manager for Admin Tools hat on.]
(In reply to comment #5)
Solving the claim auto patrol log problem, by disabling the logging
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
James Forrester jforres...@wikimedia.org changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #4 from Gerrit Notification Bot gerritad...@wikimedia.org ---
Related URL: https://gerrit.wikimedia.org/r/62785 (Gerrit Change
Ic999454d001c38dea08746d1e8184f0163cb7330)
--
You are receiving this mail because:
You are on the CC
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Krinkle krinklem...@gmail.com changed:
What|Removed |Added
CC||krinklem...@gmail.com
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #6 from Ariel T. Glenn ar...@wikimedia.org ---
OK, I take your point. OTOH is there any real need for patrolling tools to
discover lots and lots of log entries for autopatrolled bot entries? Maybe
these can be excluded from the
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
--- Comment #7 from T. H. Kelly pinkampersand.wikime...@gmail.com ---
(In reply to comment #5)
I'm not sure what the point is of disabling auto patrol logging entirely.
That
means patrolling tools will be unable to discover the log entry for
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
T. H. Kelly pinkampersand.wikime...@gmail.com changed:
What|Removed |Added
CC|
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Sam Reed (reedy) s...@reedyboy.net changed:
What|Removed |Added
Priority|Unprioritized |High
--
You are
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Aude aude.w...@gmail.com changed:
What|Removed |Added
CC||aude.w...@gmail.com
---
https://bugzilla.wikimedia.org/show_bug.cgi?id=47415
Legoktm legoktm.wikipe...@gmail.com changed:
What|Removed |Added
CC|
25 matches
Mail list logo
