alaa_wmde added a comment.
If I understand the suggestion correctly, we will then do the following: - setup tool for detecting/watching cyclic dependencies (maybe other metrics) for our extensions - tackle those issues the tool will surface in campsite, where more problematic cyclic dependencies will also show up anyway that sounds good to me as well. Although I might have preferred a little more focused efforts on it. Another motivation for these is that they can be good examples of much shorter trailblazings. I mean, one trailblazing can start with as little as 2 weeks time, taking one cyclic dependency between only 2 classes, focus on it and figure out whether it's worth it to fix and how to fix. To my mind, trailblazings are not bound to their length/complexity necessarily. A trailblazing can as well be 1 week long. The main thing that makes it a trailblazing is that it is: 1. tackling a deeply technical issue without clear/direct impact on product, and 2. the actual solution isn't clear yet but only the problem. I have a split mind now :D if it makes sense to do small iterations of trailblazings on such topic, then I'd be happy to try it out.. but I'm also fine saving that for a better topic. TASK DETAIL https://phabricator.wikimedia.org/T220958 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: alaa_wmde Cc: Addshore, Ladsgroup, Aklapper, alaa_wmde, darthmon_wmde, Nandana, Lahi, Gq86, GoranSMilovanovic, Jayprakash12345, QZanden, LawExplorer, _jensen, rosalieper, Izno, Wikidata-bugs, aude, Dinoguy1000, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
