Thank you for this info. I share an interest in the maintainability of code
that may be around for years, long after the people who write it are no
longer involved with Wikimedia.
It sounds like the Code Health Group is effectively an internal special
interest group for Wikimedia people (I am hoping that it isn't exclusive to
WMF staff) who share an interest in "code health", but isn't a top-down
decision-making body like TechCom. Is that correct?
One thing that I would like to request is a change of terminology. I prefer
to reserve the term "first responder" in the Wikiverse for people who are
actually on the front lines doing time-critical work, such as volunteer
administrators and functionaries who address threats, harassment, and other
issues with legal and security implications; WMF staff who respond to
emergency@ tickets; and staff and volunteers who deal with urgent technical
problems of various kinds and are on call 24/7 for that purpose.
Accordingly, I would request that you replace your use of "first responder"
with a different term; it's fine to use a term that sounds attractive, but
preferably one that doesn't already have a different (and in this case,
very important) meaning. Perhaps I'm excessively defensive and biased, so
take my opinion with a grain of salt, but as someone who occasionally deals
with certain issues on a 24/7 basis, I think that the term "first
responder" should be reserved.
On Wed, Oct 3, 2018 at 10:44 PM Jean-Rene Branaa <jbranaa(a)wikimedia.org>
Code Health Newsletter
The Code Health newsletter is a monthly publication provided by the
Code Health Group. The Code Health Group serves as the hub for all
Code Health topics and activities within the movement. If you are
aware or engaged in Code Health activities, we'd love to hear about
# First Responders
Staying with the Health theme, First Responders are those
individuals that have made strides in improving their code's health.
These efforts will hopefully act as stories of inspiration for others
to take on improving their code's health.
Do you have a story to share? Become or nominate a First Responder by
submitting a task in Phabricator in the #Code-Health-First-Responder
project. If sharing inspiration isn't enough, how about a cool free
First Responder t-shirt (more about that coming soon).
# Code Stewardship
Code Stewardship is an approach that the Wikimedia Foundation has
adopted to help ensure that components, extensions, and services that
are deployed to the production infrastructure have the necessary
support throughout their lifetime.
To date, the Code Stewardship review process has helped identify
and find Code Stewards for 10 components, extensions, or services that
were un/under-supported. The goal is to have complete Code Steward
coverage for all deployed-to-production components, extensions, and
services. Although we are not there yet, we are working towards that
goal every day.
This quarter's review window has closed. More information about how
to submit a review candidate is available on the Code Stewardship
review process wiki page.
Latest Code Stewardship Coverage
Core Components: 63%
Note: these numbers are based on the Developers/Maintainers page.
# Code Health by the Numbers
The following are some stats regarding Code Health. As we are early
in defining/implementing our Code Health metrics, data is limited.
See the Code Health Metrics project for more information.
In future issues of the newsletter, we'll expand this section to
include other metrics as well as trending information.
## Code Coverage
Extensions 71 13 4
Code Components 5 10 18
Services Not Available Yet
Note: As of 9/30/18.
# Code Health Learning Circles
Learning Circles are an effective way to share knowledge and
experience with your peers. Although Learning Circles have been done
in one form or another for quite some time, we've decided to do our
best to promote more Code Health related sessions. More information
about Code Health Learning Circles available here.
If you have a topic that you'd like to share, but want a little help
with organizing, please submit a Phabricator ticket to the
Topic: Design Principles and Code Refactoring
Presenter: Guillaume Lederrey
#Code Health Group Activities
Although the Code Health Group looks to act as a hub for all code
health topics, the group also sponsors various broader reaching
Code Health Metrics
Code Health Metrics working group has been formed. This working
group will focus on defining a core set of metrics that we can use to
assess code health. If you're interested in Code Health metrics
please engage in the discussion on the Discussion page and/or IRC
Up Coming Activities:
Code Health Office Hours
The Code Health Group is sponsoring a new bi-weekly Code Health Office
Hours starting October 16th at 3:00pm (15:00). These sessions are to
be held in Goggle Meet.
Do you have a Code Health topic that you need help with? Advice about
refactoring, tech debt, unit testing, etc... This is the place to ask
for it. Please submit a Phabricator task to the
#Code-Health-Help-Wanted project and the Code Health Group will do its
best to point you in the right direction.
That wraps up this inaugural issue of the Code Health Newsletter. If
you have any suggestions and/or want to see other topics, feedback is
welcome. Please just reply to this email.
Wikitech-l mailing list