A single gadgets project that just tracks an issue with any MediaWiki
gadget out there is just going to create a completely useless mess. I think
that to track an issue with a gadget in Phabricator, there should be at
least one associated project for the specific gadget (i.e., not just a tag
or
On Thu, 2015-07-16 at 01:00 -0500, Alex Monk wrote:
A single gadgets project that just tracks an issue with any MediaWiki
gadget out there is just going to create a completely useless mess.
+1.
On Jul 15, 2015 10:16 PM, Jon Robson jdlrob...@gmail.com wrote:
On phabricator should there be
On Thu, 2015-07-16 at 07:27 +0300, Amir E. Aharoni wrote:
In the past it happened to me a few times that I opened bugs about
something wrong that happened on a Wikimedia site, and it was closed as
invalid because the issue was not in MediaWiki code, but in a local gadget,
style or template on
It's very simple: this is what #Wikimedia-General-or-Unknown has always
been used for. Just makes sure there is a way for relevant/interested
people to eventually find (and understand) the report.
Relevant quip: domas: who are you, and on what did you base your
opinion? in the end, everything
Yes, yes, a thousand times yes. We're tracking all sorts of nontechnical
stuff in Phab too these days, there is no reason at all we should close out
legit technical issues with site JS, CSS, Gadgets, templates, etc without
actually doing something to help.
-- brion
On Jul 15, 2015 11:28 PM, Amir
Perhaps Engineering Community as well? Unlike Community Tech, CE has a
manager and therefore perhaps more ability to address this sooner. Any
comments, Quim?
Thanks!
Pine
On Jul 15, 2015 10:16 PM, Jon Robson jdlrob...@gmail.com wrote:
I'm encountering a similar problem now -
Hi,
In the past it happened to me a few times that I opened bugs about
something wrong that happened on a Wikimedia site, and it was closed as
invalid because the issue was not in MediaWiki code, but in a local gadget,
style or template on that project.
The bugs were actually fixed, but I'd like
I'm encountering a similar problem now -
https://phabricator.wikimedia.org/T99361
On phabricator should there be a gadgets project? Community project?
I hit this issue all the time and to me is the biggest flaw with the
fact editors can introduce code. Templates/gadgets for me are hard to
debug,
Perhaps a solution is to tag as something other than invalid; perhaps
downstream dependency?
Pine
On Jul 15, 2015 9:28 PM, Amir E. Aharoni amir.ahar...@mail.huji.ac.il
wrote:
Hi,
In the past it happened to me a few times that I opened bugs about
something wrong that happened on a Wikimedia
