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 community-wishlist type thing), and these gadget projects should need to be created at the request of/with the knowledge of the actual gadget maintainer (otherwise it's going to be pretty pointless).
On 16 July 2015 at 00:21, Pine W <wiki.p...@gmail.com> wrote: > 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 - > > 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, as it's hard for me to first locate the code, to understand it > > (since it's not hosted in the same way as our other code and is > > typically written very differently) and then to identify who owns it > > and who I can discuss fixing with. > > > > This would be a great problem for the new community dev team to think > > about imo. > > > > On Thu, Jul 16, 2015 at 12:27 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 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 to question the "invalid" > > > closure. > > > > > > They were real bugs in real products. The fact that the software is not > > in > > > Gerrit doesn't mean that they don't affect the product de facto. Just > for > > > the sake of example, if a bug in a local Gadget affects the Flow > > extension, > > > for example, I find it perfectly valid to add tag the Flow tag to it. > > Core > > > and extension developers should be curious about how what they > developed > > > behaves in the wild. > > > > > > I do wonder what other tags are there to add to such a bug? I'm going > to > > > open one now. > > > > > > (P.S. Yes, this raises an issue of whether non-Wikimedia sites should > > > count. I say - yes, and it shouldn't be limited unless it gets > seriously > > > out of hand. But a URL with reproduction instructions must always be > > > provided.) > > > > > > -- > > > Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי > > > http://aharoni.wordpress.com > > > “We're living in pieces, > > > I want to live in peace.” – T. Moore > > > _______________________________________________ > > > Wikitech-l mailing list > > > Wikitech-l@lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > > > > > -- > > Jon Robson > > * http://jonrobson.me.uk > > * https://www.facebook.com/jonrobson > > * @rakugojon > > > > _______________________________________________ > > Wikitech-l mailing list > > Wikitech-l@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
