Re: [Wikitech-l] TechCom meeting 2020-10-06

2020-10-07 Thread Timo Tijhof
The minutes from TechCom's triage meeting on 7 October 2020.

Present: Daniel K, Giuseppe L, Dan A, Timo T.
RFC T260714: Parsoid Extension API

   -

   https://phabricator.wikimedia.org/T260714
   -

   Last Call ended. No objections on ticket nor otherwise brought to us.
   -

   Approved.

RFC T487: Associated namespaces

   -

   https://phabricator.wikimedia.org/T487
   -

   Last Call ended. Discussion about the process. Task to remain open, but
   decline as proposed.

FYI: Heavy Wing - Machine Learning at WMF

   -


   
https://docs.google.com/document/d/1U8PKfotPUFmEXH1EXrQwqlccFE8i7smlQtxMrTAM6GE/edit#heading=h.5ha1j1agkk55

Controlling HTTP cache around cookies and privileged content is hard

   -

   https://phabricator.wikimedia.org/T264631
   -

   Yes, it’s hard.
   -

   TT: We have three or four layers in MW to defend against this going
   wrong. I’ll comment about past work around cookie blocks and error pages
   which relates to this.

Next week IRC office hours

No IRC discussion scheduled for next week.

On Tue, Oct 6, 2020 at 11:19 AM Giuseppe Lavagetto 
wrote:

> This is the weekly TechCom board review in preparation of our meeting on
> Wednesday. 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.
>
> Activity since Monday 2020-09-28 on the following boards:
>
> https://phabricator.wikimedia.org/tag/techcom/
>
> https://phabricator.wikimedia.org/tag/techcom-rfc/
>
> Committee inbox:
>
>-
>
>T264334 : Could the
>registered module manifest be removed from the client?
>-
>
>   New task about the possibility of removing the huge module registry
>   from the js sent to the client. The idea is being discussed.
>
> Committee board activity: Nothing to report, besides inbox
>
> New RFCs: none.
>
> Phase progression:
>
>-
>
>T262946 : Bump Firefox
>version in basic support to 3.6 or newer
>-
>
>   Moves to P3 (explore)
>   -
>
>   It is pointed out that we’ve dropped support in production for TLS
>   1.0/1.1 in january, so de facto only Firefox 27+ is able to connect to 
> the
>   wikimedia sites
>   -
>
>   In light of that, it’s suggested that we might bump the minimum
>   supported versions of browsers further.
>
> IRC meeting request: none
>
> Other RFC activity:
>
>-
>
>T260714 : Parsoid Extension
>API.
>-
>
>   Last call to be approved, that will end on October 7 (tomorrow)
>   -
>
>T487 : RfC: Associated
>namespaces.
>-
>
>   On last call to be declined, there is some opposition to the
>   opportunity of marking it as declined on phabricator. Last call should 
> end
>   on October 7 (tomorrow)
>   -
>
>T263841 : RFC: Expand API
>title generator to support other generated data.
>-
>
>   Erik asks if this is going to be generally applied to all
>   generators or not.
>
> Cheers,
> Giuseppe
> --
> Giuseppe Lavagetto
> Principal Site Reliability Engineer, Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] TechCom meeting 2020-10-06

2020-10-07 Thread Daniel Kinzler
Another thing for attention by TechCom:

We need a robust and consistent way to determine whether a response should be
(publicly) cacheable. We Seem to fail in both directions currently, in some edge
cases. On a related note, we need more control over which responses are allowed
to contain which cookies.

See discussion on https://phabricator.wikimedia.org/T264631


Am 07.10.20 um 10:30 schrieb Daniel Kinzler:
>
> There is something I came across that I'd like to briefly discuss briefly
> during the meeting:
>
> It would be nice if the updater could change default settings. This way, we
> could make some behavior the default for new wikis, while keeping old behavior
> for existing wikis. I envision an DefaultOverrides.php file that the installer
> would append to. It would be in .gitignore, but I'm not sure where it should
> be located.
>
> Point in case: Wikis that share the user table should also share the actor
> table. But we haven't been doing that so far, and wikis that now already have
> a shared user table but per-wiki actor tables are rather ticket to migrate. So
> we could add the actor table to wgSharedTables per default, but tell the
> installer to override that for wikis that already have out-of-sync actor
> tables. See T243276#6519078. 
> 
>
> Am 06.10.20 um 12:18 schrieb Giuseppe Lavagetto:
>>
>> This is the weekly TechCom board review in preparation of our meeting on
>> Wednesday. 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.
>>
>> Activity since Monday 2020-09-28 on the following boards:
>>
>> https://phabricator.wikimedia.org/tag/techcom/
>>
>> https://phabricator.wikimedia.org/tag/techcom-rfc/
>>
>> Committee inbox:
>>
>>  *
>>
>> T264334 : Could the registered
>> module manifest be removed from the client?
>>
>>  o
>>
>> New task about the possibility of removing the huge module registry
>> from the js sent to the client. The idea is being discussed.
>>
>> Committee board activity: Nothing to report, besides inbox
>>
>> New RFCs: none.
>>
>> Phase progression:
>>
>>  *
>>
>> T262946 : Bump Firefox version
>> in basic support to 3.6 or newer
>>
>>  o
>>
>> Moves to P3 (explore)
>>
>>  o
>>
>> It is pointed out that we’ve dropped support in production for TLS
>> 1.0/1.1 in january, so de facto only Firefox 27+ is able to connect
>> to the wikimedia sites
>>
>>  o
>>
>> In light of that, it’s suggested that we might bump the minimum
>> supported versions of browsers further.
>>
>> IRC meeting request: none
>>
>> Other RFC activity:
>>
>>  *
>>
>> T260714 : Parsoid Extension 
>> API. 
>>
>>  o
>>
>> Last call to be approved, that will end on October 7 (tomorrow)
>>
>>  *
>>
>> T487 : RfC: Associated 
>> namespaces.
>>
>>  o
>>
>> On last call to be declined, there is some opposition to the
>> opportunity of marking it as declined on phabricator. Last call
>> should end on October 7 (tomorrow)
>>
>>  *
>>
>> T263841 : RFC: Expand API
>> title generator to support other generated data.
>>
>>  o
>>
>> Erik asks if this is going to be generally applied to all generators
>> or not.
>>
>> Cheers,
>> Giuseppe
>> -- 
>> Giuseppe Lavagetto
>> Principal Site Reliability Engineer, Wikimedia Foundation
>>
>> ___
>> 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

-- 
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-10-06

2020-10-07 Thread Daniel Kinzler
There is something I came across that I'd like to briefly discuss briefly during
the meeting:

It would be nice if the updater could change default settings. This way, we
could make some behavior the default for new wikis, while keeping old behavior
for existing wikis. I envision an DefaultOverrides.php file that the installer
would append to. It would be in .gitignore, but I'm not sure where it should be
located.

Point in case: Wikis that share the user table should also share the actor
table. But we haven't been doing that so far, and wikis that now already have a
shared user table but per-wiki actor tables are rather ticket to migrate. So we
could add the actor table to wgSharedTables per default, but tell the installer
to override that for wikis that already have out-of-sync actor tables. See
T243276#6519078. 

Am 06.10.20 um 12:18 schrieb Giuseppe Lavagetto:
>
> This is the weekly TechCom board review in preparation of our meeting on
> Wednesday. 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.
>
> Activity since Monday 2020-09-28 on the following boards:
>
> https://phabricator.wikimedia.org/tag/techcom/
>
> https://phabricator.wikimedia.org/tag/techcom-rfc/
>
> Committee inbox:
>
>  *
>
> T264334 : Could the registered
> module manifest be removed from the client?
>
>  o
>
> New task about the possibility of removing the huge module registry
> from the js sent to the client. The idea is being discussed.
>
> Committee board activity: Nothing to report, besides inbox
>
> New RFCs: none.
>
> Phase progression:
>
>  *
>
> T262946 : Bump Firefox version
> in basic support to 3.6 or newer
>
>  o
>
> Moves to P3 (explore)
>
>  o
>
> It is pointed out that we’ve dropped support in production for TLS
> 1.0/1.1 in january, so de facto only Firefox 27+ is able to connect to
> the wikimedia sites
>
>  o
>
> In light of that, it’s suggested that we might bump the minimum
> supported versions of browsers further.
>
> IRC meeting request: none
>
> Other RFC activity:
>
>  *
>
> T260714 : Parsoid Extension 
> API. 
>
>  o
>
> Last call to be approved, that will end on October 7 (tomorrow)
>
>  *
>
> T487 : RfC: Associated namespaces.
>
>  o
>
> On last call to be declined, there is some opposition to the
> opportunity of marking it as declined on phabricator. Last call should
> end on October 7 (tomorrow)
>
>  *
>
> T263841 : RFC: Expand API title
> generator to support other generated data.
>
>  o
>
> Erik asks if this is going to be generally applied to all generators
> or not.
>
> Cheers,
> Giuseppe
> -- 
> Giuseppe Lavagetto
> Principal Site Reliability Engineer, Wikimedia Foundation
>
> ___
> 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-10-06

2020-10-06 Thread Giuseppe Lavagetto
This is the weekly TechCom board review in preparation of our meeting on
Wednesday. 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.

Activity since Monday 2020-09-28 on the following boards:

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

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

Committee inbox:

   -

   T264334 : Could the
   registered module manifest be removed from the client?
   -

  New task about the possibility of removing the huge module registry
  from the js sent to the client. The idea is being discussed.

Committee board activity: Nothing to report, besides inbox

New RFCs: none.

Phase progression:

   -

   T262946 : Bump Firefox
   version in basic support to 3.6 or newer
   -

  Moves to P3 (explore)
  -

  It is pointed out that we’ve dropped support in production for TLS
  1.0/1.1 in january, so de facto only Firefox 27+ is able to
connect to the
  wikimedia sites
  -

  In light of that, it’s suggested that we might bump the minimum
  supported versions of browsers further.

IRC meeting request: none

Other RFC activity:

   -

   T260714 : Parsoid Extension
   API.
   -

  Last call to be approved, that will end on October 7 (tomorrow)
  -

   T487 : RfC: Associated
   namespaces.
   -

  On last call to be declined, there is some opposition to the
  opportunity of marking it as declined on phabricator. Last call
should end
  on October 7 (tomorrow)
  -

   T263841 : RFC: Expand API
   title generator to support other generated data.
   -

  Erik asks if this is going to be generally applied to all generators
  or not.

Cheers,
Giuseppe
-- 
Giuseppe Lavagetto
Principal Site Reliability Engineer, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l