Thu, Sep 13
@Aklapper you are amazing! I even commented on that task and don't remember it :-) It is a dup.
Thu, Sep 6
@Aklapper, I've been spending a bit of time on this and one of the directions I'm leaning is to have the ROO be an output of the deployment review process (Review Queue today). My thought being that the ROO could be used by deployers as an authoritative source to determine whether or not a new extensions, services, etc... should be deployed. I spoke a to Tyler a bit about this and it seems like it would be of value.
After some initial thought and discussions regarding this goal, it seems that a closely coupled area of concerned is that of the Review Queue (the process by which extensions are reviewed prior to initial deployment).
Thu, Aug 30
Aug 8 2018
Jul 22 2018
Jul 10 2018
Take a look at: https://docs.google.com/spreadsheets/d/1plkHOPQ0HAMKKxNhBRH9PXo4340tQsyscstShwJjgvs/edit#gid=0. Some of the metadata that was collected was whether it was testable or not. Outside of the incidents that have happened since then, this spreadsheet should provide a good starting point.
Moving to resolved. I've been engaging with Platform team as well as Search Platform team regarding refactoring as part of the broader Technical Debt/Code Health discussions.
Jul 9 2018
Closing this as resolved as Audiences->Contributors has been identified as Code Stewards moving forward and plan is in place and being worked on actively.
Hey @Mvolz, just wanted to check in on this task. It seems like we are waiting on Zotero team in order to move forward. With the August deadline looming, I wanted to know what you thought it would take to complete our part (development, testing, deployment) once the Zotero part is complete.
Jul 5 2018
Moved to Resolved. Additional discussions to be had as we start revisiting/refactoring the Review Process.
Jun 28 2018
Jun 25 2018
Although this work looks to address things that might be outside of the scope of the Code Stewardship Reviews (which is focused primarily on un/under maintained orphaned code deployed to WMF production). There's a rubric that we created to help use evaluate and propose what to do with these areas of code. Might be worth taking a look to see if there's some stuff we could leverage either way. Note, archiving/sunsetting of code is only one of the possible outcomes for the Code Stewardship Review process.
Jun 19 2018
Jun 14 2018
Jun 12 2018
Added entry to developers/maintainers page. Please augment with more accurate description and list of maintainers.
At this juncture the Language-Team will move forward as the Code Stewards for this extension. Runa and I have briefly discussed and will be working to get this extension the support/funding for more active maintenance. In the meantime non-UBN issues that need support will be reviewed on a case-by-case basis. @MarcoAurelio of the open changesets, are there any in particular that are of higher priority?
Jun 11 2018
We're looking to have Audiences->Contributors->Editing be the Code Stewards for this moving forward.
Jun 8 2018
@faidon it looks like there's a plan in place to address the pending EOL, in short Marielle and Marko are working on a NodeJS based solution. Now it's more a question of timing. What happens in August in terms of our infrastructure? Are we able to keep it going for a little while longer or does it get turned off no matter what?
Jun 7 2018
Updated to developers/maintainers page to reflect Code Stewardship being assigned to MediaWiki Platform team.
May 31 2018
Survey has been sent out. The survey will closed on June 15th.
Although this is to be an ongoing effort, I've promoted/surfaced Technical Debt topic at the Barca Hackathon. As this is the last event for the 17/18 fiscal year, we'll call this task resolved/closed.
May 30 2018
@danstillman thanks for the additional info regarding your developments. As timing is of the essence with this, please keep us apprised of any new developments.
May 29 2018
May 28 2018
May 25 2018
May 24 2018
May 23 2018
Slide set used during the session is available at: