Mailing List Archive: TechCom meeting 2020-10-14

TechCom meeting 2020-10-14

Oct 14, 2020, 6:58 PM

Post #1 of 4 (376 views)

This is the weekly TechCom board review, usually in preparation for our
meeting, a few days late this week because I forgot. Apologies.

Activity since Monday 2020-10-06 on the following boards:

https://phabricator.wikimedia.org/tag/techcom/
https://phabricator.wikimedia.org/tag/techcom-rfc/

Committee inbox:

- T263904 <https://phabricator.wikimedia.org/T263904>: Are traits part
of the stable interface?
- T239742 <https://phabricator.wikimedia.org/T239742>: "Should npm
packages maintained by Wikimedia be scoped or unscoped?"
- Both have been sitting in the inbox for a month or so, Tim first
pointed this out a few weeks ago but we haven't triaged them yet.

Committee board activity (none)

New RFCs (none)

Phase progression (none)

IRC meeting request (none)

Other RFC activity:

- T262946: <https://phabricator.wikimedia.org/T262946> Bump Firefox
version in basic support to 3.6 or newer
- Some agreement between Volker and Timo to keep the scope at just the
Firefox version bump and move this RFC forward. I think Volker
is welcome
to move this back to P4 unless I missed some other ongoing discussion?
- T259771: <https://phabricator.wikimedia.org/T259771> RFC: Drop support
for database upgrade older than two LTS releases
- Discussion about upgrading from 1.16 (this humble reader says
upgrading from a version that's 10 years old should not be a priority)

Re: TechCom meeting 2020-10-14 [ In reply to ]

dandreescu at wikimedia

Oct 14, 2020, 7:02 PM

Post #2 of 4 (376 views)

Permalink

As for the minutes of our meeting today, Grant joined and we discussed
the Proposal
for a Technical Decision Making Process
<https://docs.google.com/document/d/1LOAi3RjVeWY-QRdOjnfHCchnM8bSh_D3ug9GhnQ6Nf0/edit#>.
Specifically, we went over Scope, Transition, Resourcing, and a bit about
the Forum and Timeboxing. The next steps are to establish a more concrete
transition plan, from the current Tech Com process to the new process. And
Kate will be reaching out to team managers to begin establishing the Forum.

On Wed, Oct 14, 2020 at 9:58 PM Dan Andreescu <dandreescu@wikimedia.org>
wrote:

> This is the weekly TechCom board review, usually in preparation for our
> meeting, a few days late this week because I forgot. Apologies.
>
> Activity since Monday 2020-10-06 on the following boards:
>
> https://phabricator.wikimedia.org/tag/techcom/
> https://phabricator.wikimedia.org/tag/techcom-rfc/
>
> Committee inbox:
>
> - T263904 <https://phabricator.wikimedia.org/T263904>: Are traits part
> of the stable interface?
> - T239742 <https://phabricator.wikimedia.org/T239742>: "Should npm
> packages maintained by Wikimedia be scoped or unscoped?"
> - Both have been sitting in the inbox for a month or so, Tim first
> pointed this out a few weeks ago but we haven't triaged them yet.
>
> Committee board activity (none)
>
> New RFCs (none)
>
> Phase progression (none)
>
> IRC meeting request (none)
>
> Other RFC activity:
>
>
> - T262946: <https://phabricator.wikimedia.org/T262946> Bump Firefox
> version in basic support to 3.6 or newer
> - Some agreement between Volker and Timo to keep the scope at just the
> Firefox version bump and move this RFC forward. I think Volker is welcome
> to move this back to P4 unless I missed some other ongoing discussion?
> - T259771: <https://phabricator.wikimedia.org/T259771> RFC: Drop
> support for database upgrade older than two LTS releases
> - Discussion about upgrading from 1.16 (this humble reader says
> upgrading from a version that's 10 years old should not be a priority)
>
>

Re: TechCom meeting 2020-10-14 [ In reply to ]

dkinzler at wikimedia

Oct 15, 2020, 1:17 AM

Post #3 of 4 (376 views)

Permalink

Am 15.10.20 um 03:58 schrieb Dan Andreescu:
> Committee inbox:
>
> * T263904 <https://phabricator.wikimedia.org/T263904>: Are traits part of
> the stable interface?
>
I'm working on an update for the Stable Interface Policy. Besides some minor
tweaks to the wording, the main changes are:

* added a section on "stable for use" for traits.
* overhauled the deprecation process, to follow up on the discussion on
breaking changes without deprecation we had here on wikitech-l a couple of
months ago. To give a very brief summary, the idea is that hard deprecation
should happen as soon as possible after soft deprecation, and removal should
happen right after the release that contained the hard deprecation. It also
shifts responsibility for updating calling code to the person or group that
drives the deprecation.

Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation

Re: TechCom meeting 2020-10-14 [ In reply to ]

dkinzler at wikimedia

Oct 15, 2020, 1:17 AM

Post #4 of 4 (376 views)

Permalink

Am 15.10.20 um 03:58 schrieb Dan Andreescu:
> Committee inbox:
>
> * T263904 <https://phabricator.wikimedia.org/T263904>: Are traits part of
> the stable interface?
>
I'm working on an update for the Stable Interface Policy
<https://www.mediawiki.org/wiki/User:DKinzler_(WMF)/Stable_interface_policy>.
Besides some minor tweaks to the wording, the main changes are:

* added a section on "stable for use" for traits.
* overhauled the deprecation process, to follow up on the discussion on
breaking changes without deprecation we had here on wikitech-l a couple of
months ago. To give a very brief summary, the idea is that hard deprecation
should happen as soon as possible after soft deprecation, and removal should
happen right after the release that contained the hard deprecation. It also
shifts responsibility for updating calling code to the person or group that
drives the deprecation.

Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation