[Engineering] Code Stewardship Reviews - Q3 Update and Q4 Request for Feedback...

Jean-Rene Branaa jbranaa at wikimedia.org
Wed May 2 05:14:49 UTC 2018


Hello All,

We're kicking off another round of Code Stewardship reviews for the
quarter.  Please take a look and share your thoughts through the
Feedback Solicitation talk pages[1].

Below you'll also find a brief update for the Q3 Code Stewardship
Review activities.


Q4 Code Stewardship Reviews

The dicussion window for this quarter's stewardship review candidates
is opening today (May 1st) and will remain open until the 21st of May.

As a brief reminder, the Code Stewardship Review process[0] has been
put in place to help us discuss and plan a course of action for code,
extensions, and services that are deployed in Wikimedia Foundation's
production environment and are currently un/under funded.

We are soliciting your feedback for the following items during this
review cycle:

* Geodata Extension[2]

* LiquidThreads Extension[3]

* Zotero Translation Server[4]

* TranslationNotifications Extension[5]

* FlaggedRecs Extension[6]

Once the feedback window is closed, we will review the feedback and if
needed, prioritize those items to be reviewed further during this
quarter's review cycle.



Q3 Code Stewardship Reviews

We wanted to provide a quick update on the Code Stewardship Reviews
from last quarter.

Below is a list of those items we reviewed last quarter and a brief
status for each of them.

* TimedMediaHandler[7]: Code Steward identified - Readers Engineering.
Preliminary plan in place.

* IRC RecentChanges Feed[8]: Code Steward identified - Analytics.

* RelatedSites[9]: Code Steward identified - CommTech.  Plan is to
sunset extention.  Details to follow.

* AbuseFilter[10]: Code Steward identified - Platform Team.  Team will
be as responsive as possible with current resourcing levels.  Code
Stewardship for this extension will be included in future resource
plans.

Although not included in the complete review process, UrlShortener
[11] did end up finding a steward once being submitted as a review
candidate.

This past quarter was our first attempt at using this review process.
We were successfully able to address four areas of concern. Assigning
Code Stewards as well as laying out some initial plans for moving
forward.  Although good progress was made this quarter, there are some
challenges ahead.

Simply assigning a Code Steward doesn't necessarily translate into the
gaps getting fully addressed. To that end, we'll be working with the
Code Stewards to help identify ongoing gaps.  Over time we will look
to fill those gaps through the Foundation's annual planning and
community engagement.

The process wasn't without it's challenges, one of which was the
concern that all items being reviewed were being considered for
sunsetting.  After clarifying some of this in our process
definition[0], it seems most of these concerns have been addressed.
As always, if there's any additional feedback on the process, please
don't hesitate to contact Greg Grossmeier or I.

Cheers,

Jean-Rene Branaa
Release Engineering
Wikimedia Foundation

[0] https://www.mediawiki.org/wiki/Code_stewardship_reviews
[1] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation
[2] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/Geodata
[3] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/LiquidThreads
[4] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/Zotero_Translation_Server
[5] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/TranslationNotifications
[6] https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation/FlaggedRevs
[7] https://phabricator.wikimedia.org/T185551
[8] https://phabricator.wikimedia.org/T185319
[9] https://phabricator.wikimedia.org/T185206
[10] https://phabricator.wikimedia.org/T185154
[11] https://phabricator.wikimedia.org/T187052



More information about the Engineering mailing list