Re: [Wikitech-l] TechCom meeting 2020-12-02

[Dan Andreescu]

>
>
>- Create WikiTeq group on Gerrit
> is now more clear (see note
>from Daniel  to
>discuss, which we should do here)
>
> Committee board activity:
>
> The process for adding a "trusted organization" isn't clear, but since the
> group is not maintaining any extensions deployed by wmf, we can probably
> just go ahead and add them.
>
+1

>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] TechCom meeting 2020-12-02

[Daniel Kinzler]

Am 30.11.20 um 22:00 schrieb Dan Andreescu:
> Automatically index extensions in Codesearch
>  is still in the inbox, no activity
> since last week's discussion

I have abandoned this in favor of relying on the list of 3rd party extensions
maintained by the MediaWIki Stakeholder group, see
https://github.com/MWStake/nonwmf-extensions/


>   * Create WikiTeq group on Gerrit 
> is now more clear (see note from Daniel
>  to discuss, which we
> should do here)
>
> Committee board activity:
>
The process for adding a "trusted organization" isn't clear, but since the group
is not maintaining any extensions deployed by wmf, we can probably just go ahead
and add them.


>   * General ParserCache service class for large "current" page-derived data
>  was declined by Daniel, see
> his reasoning there
>
I'd like to note that "declined" here means that I have withdrawn my own 
proposal.


-- 
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] TechCom meeting 2020-12-02

[Daniel Kinzler]

Hi all!

I'd like to mention one additional topic: I have been touching up my proposal
for the introduction of PageIdentity
, as a lightweight  alternative to
Title and WikiPage. I would like to propose for it to go on last call. It has
been sitting in the "tune" phase for a while, and it seems pretty mature to my
by now.

You can find the proposed code on gerrit, see
Iaed4871e0d32c67d4fb13e487625527f6a21e9c5
.
There is a chain of follow-up patches (some incomplete) that demonstrate how the
new interface is intended to be used, and how it can improve existing code.

Am 30.11.20 um 22:00 schrieb Dan Andreescu:
>
> This is the weekly TechCom board review. If there are additional topics for
> TechCom to review, please let us know by replying to this email. However,
> please keep discussion about individual RFCs to the Phabricator tickets.  This
> week, the meeting is async, so we'll be replying to the email as well, *feel
> free to join in*!
>
> Activity since Wednesday 2020-11-25 on the following boards:
>
> https://phabricator.wikimedia.org/tag/techcom/
> https://phabricator.wikimedia.org/tag/techcom-rfc/
>
> Committee inbox:
>
>   * Automatically index extensions in Codesearch
>  is still in the inbox, no
> activity since last week's discussion
>   * Create WikiTeq group on Gerrit 
> is now more clear (see note from Daniel
>  to discuss, which we
> should do here)
>
> Committee board activity:
>
>   * General ParserCache service class for large "current" page-derived data
>  was declined by Daniel, see
> his reasoning there
>
> New RFCs: (none)
>
> Phase progression: (none)
>
> IRC meeting request: (none)
>
> Other RFC activity:
>
>   * RFC: Re-evaluate librsvg as SVG renderer for WMF wikis
>  saw more conversation
>   * RFC: Discourage use of MySQL's ENUM type
>  Amir points out the need to
> overhaul all db documentation (I agree, could we have a doc sprint about
> this?) including policies
>   * RFC: Amendment to the Stable interface policy, November 2020
>  has a suggestion/question
> about clarifying default status and deprecation procedure
>   * RFC: Store WikibaseQualityConstraint check data in persistent storage
>  WMDE calls for help from
> TechCom and the Platform team to collaborate here.  See Adam Shorland's
> comment about putting it through the new Technical Decision Making Process
>   * RFC: Expand API title generator to support other generated data
>  Carly Bogen is asking for
> clarity on the need for a steward.  Timo's comment
>  on the task indeed
> seem to contradict his note from last week's grooming email.  Timo, would
> you please clarify.
>
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

-- 
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] TechCom meeting 2020-12-02

[Dan Andreescu]

This is the weekly TechCom board review. If there are additional topics for
TechCom to review, please let us know by replying to this email. However,
please keep discussion about individual RFCs to the Phabricator tickets.
This week, the meeting is async, so we'll be replying to the email as
well, *feel
free to join in*!

Activity since Wednesday 2020-11-25 on the following boards:

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

Committee inbox:

   - Automatically index extensions in Codesearch
    is still in the inbox, no
   activity since last week's discussion
   - Create WikiTeq group on Gerrit
    is now more clear (see note
   from Daniel  to
   discuss, which we should do here)

Committee board activity:

   - General ParserCache service class for large "current" page-derived data
    was declined by Daniel, see
   his reasoning there

New RFCs: (none)

Phase progression: (none)

IRC meeting request: (none)

Other RFC activity:

   - RFC: Re-evaluate librsvg as SVG renderer for WMF wikis
    saw more conversation
   - RFC: Discourage use of MySQL's ENUM type
    Amir points out the need to
   overhaul all db documentation (I agree, could we have a doc sprint about
   this?) including policies
   - RFC: Amendment to the Stable interface policy, November 2020
    has a suggestion/question
   about clarifying default status and deprecation procedure
   - RFC: Store WikibaseQualityConstraint check data in persistent storage
    WMDE calls for help from
   TechCom and the Platform team to collaborate here.  See Adam Shorland's
   comment about putting it through the new Technical Decision Making Process
   - RFC: Expand API title generator to support other generated data
    Carly Bogen is asking for
   clarity on the need for a steward.  Timo's comment
    on the task indeed
   seem to contradict his note from last week's grooming email.  Timo, would
   you please clarify.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l