I happen to have a personal interest in both automated testing, and refactoring. Refactoring is obviously more directly relevant to tech debt, but I view automated testing as a prerequisite for aggressive refactoring.
I'm not familiar with the details of our platform(s), but I would be willing to facilitate an open discussion on either of these topics.
That could be interesting; a "basic prerequisites to paying down technical debt" type talk.
How would you see an open discussion about these topics going? Sort of a "let's talk about these things in the abstract and how they can help developers"? Or "what are the current tools available to Wikimedia Devs to help them in these areas"?
If it were a general discussion, I could be an active participant. If it were about specific tools, I would purely be a facilitator. Either could work.
Title alternatives to "basic prerequisites to paying down technical debt"
@KSmith (WMF), I'm going to riff on this statement: you said you are "not familiar with the details of our platform(s)". Genuine question: if you had to pick one wiki page (presumably on mediawiki.org), which page would you suggest for someone wanting to learn the details important for learning automated testing for our platform(s)?
@RobLa-WMF: Not having attempted to do any research yet, I see Selenium/Cindy The Browser Test Bot and Manual:Unit testing. That's where I would start to try to figure out what's going on.
It would probably be good to have an Automated Test[ing|s] page, which doesn't seem to exist yet.
@KSmith (WMF) as far as I know, there is no landing page on test automation.
Manual:Unit testing looks to me like a good place to start learning more about unit testing.
Selenium/Cindy The Browser Test Bot is not a good place to start learning about Selenium tests. It's parent page, Selenium, would be a better starting point.
Today is the deadline, and I don't have the energy to move this forward. If someone proposes something in this area, I would be happy to help with it.
Is this really about "managing" or also about "dealing with and decreasing"? If the scope is not MediaWiki Core only, might case studies provide some insights? (Open question; maybe the answer is a clear "No".) Like killing AFTv5 in the past (still used by 3rd party sites; took a while to properly remove any traces on WMF sites), or unresolved tasks like "Deprecate EducationProgram extension" in Phab:T125618 ?
I'm not sure I understand your first question. "Managing" is a synonym for "dealing with", and "decreasing" is only one of many strategies. Sometimes increasing technical debt is smart. Great software designers frequently decide that "kludgy but fast and functional" is better than "perfect when it's 'ready'". I also fully agree with @Greg (WMF)'s statement about scope: "Scope is not just MediaWiki Core or even just MW Core+Extensions, but everything (where 'everything' == 'things of concern in the Wikimedia development community')."
1) Scope is not just MediaWiki Core or even just MW Core+Extensions, but everything (where "everything" == "things of concern in the Wikimedia development community"). So, explicitly this includes eg services like OCG.
2) I think case studies/lessons learned would be a great session (either of one or a couple, depending). I'd love someone who is closely familiar with the thing at hand to do it (probably not me, though I'd be more than willing to help prepare or even present if needed).
