Re: [Wikitech-l] Introducing Quibble, a test runner for MediaWiki

[Brad Jorsch (Anomie)]

On Fri, Apr 27, 2018 at 5:58 PM, Antoine Musso  wrote:

> [T193222] MariaDB on Stretch uses the utf8mb4 character set. Attempting
> to create a key on VARCHAR(192) or larger would cause:
>  Error: 1071 Specified key was too long; max key length is 767 bytes
>
> Reducing the key length is the obvious solution and some fields could
> use to be converted to ENUM.
>

Personally, I'd rather we didn't use more enums. They work inconsistently
for comparisons and ordering, and they require a schema change any time a
new value is needed. It'd probably be better to use NameTableStore instead.

-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Code of Conduct for Wikimedia technical spaces - Code of Conduct Committee - 2018.II members

[Katherine Maher]

I’d like to echo DJs thanks - when I speak with people from other technical
communities, it’s a point of pride to be able to share that Wikimedia
contributors developed, negotiated, and adopted this CoC.

And I’d like to echo Sébastien’s call for further participation - like our
various other community committees, your participation is critical to its
success. Please do consider a future candidacy!

Thank you all!

On Sat, Apr 28, 2018 at 4:38 AM Derk-Jan Hartman <
d.j.hartman+wmf...@gmail.com> wrote:

> Thank you candidates and committee !
>
> DJ
>
> On Fri, Apr 27, 2018 at 6:05 PM, Sébastien Santoro
>  wrote:
> > Hello all,
> >
> > The candidate slates has been deemed finalized.
> >
> > Thanks to the new candidates joining the committee to support
> > this important mission, sustaining our code of conduct.
> >
> > We didn't receive a lot of candidatures this session, so we'd like
> > to ask you to think for the next months if you would like to serve
> > in the 2019 half I committee, and to be ready in October to join
> > the boat.
> >
> > [ Candidates URL ]
> >
> >
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Candidates/2018-I
> >
> > This page will be moved to the members page when the new committee
> > will enter in function after a training period for new members.
> >
> > [ Procedure ]
> >
> > We haven't received any feedback to techconduct (at) twikimedia.org
> > related to one or another candidate.
> >
> > In addition to the procedure the Code of Conduct provides, we also
> > received additional comments at [[mw:Talk:Code of
> > Conduct/Committee/Candidates/2018-I]] and consider these comments
> > party addressed and partly to solve in the next weeks, and unrelated
> > to the current candidates.
> >
> > --
> > Sébastien Santoro aka Dereckson
> > http://www.dereckson.be/
> >
> > ___
> > 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

-- 
Katherine Maher

Executive Director
Wikimedia Foundation

1 Montgomery Street, Suite 1600
San Francisco, CA 94104

+1 (415) 839-6885 ext. 6635
+1 (415) 712 4873
kma...@wikimedia.org
https://annual.wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] Changes to SWAT deployment policies, effective Monday April 30th

[Gergo Tisza]

On Sat, Apr 28, 2018 at 2:19 AM, Tyler Cipriani 
wrote:

> Looking at this info maybe 6 is the magic number?
>

Other options would be to have more windows (an EU morning SWAT maybe?),
and/or make it less of an expectation to have your patches deployed in the
window you scheduled them for (e.g. not starting deploying new patches
after :45; anything that overflows just gets pushed to next day).

Another thing that could be reconsidered for more even use of SWAT windows
is the requirement that the patch owner has to be present; we could just
request a test plan in the commit summary instead for low-risk patches.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] Changes to SWAT deployment policies, effective Monday April 30th

[Martin Urbanec]

so 28. 4. 2018 v 0:05 odesílatel Greg Grossmeier 
napsal:

> 
> > ie. if the new policy was introduced at the start of the year, it would
> > have caused at least a two-week delay in all three SWAT windows at one
> > point at least, and it would have caused an ever-growing backlog of
> patches
> > for EU mid-day.
>
> 2 week delays aren't possible as all SWATs are backports of master, so
> if waiting a week it'd go out with the normal train ;)
>

No, majority of patches deployed in a SWAT window is in
operations/mediawiki-config and this repository do not have release
branches and/or train deploys. If I'd be the only one using certain SWAT
window and I'd need to deploy 5 patches per window, the first window I'll
deploy 4 patches and the remaining would be rescheduled, the second window
I'll have 1 patch rescheduled and 5 new patches (6 in total), 4 will be
deployed, 2 will be rescheduled, the third window I'll have 2 patches
rescheduled and 5 new patches (7 in total), 4 will be deployed, 3 will be
rescheduled, etc. etc. etc.

I'd have a constantly raising backlog of patches and will be enforced to a)
reserve a window to deploy all waiting patches b) use another SWAT.

This will cause even bigger pain after US holidays because then bigger SWAT
windows are expected.

I know that deploying 8 patches in a window is a problem (at least in EU
SWAT window, don't use the other windows that much), but 4 is the other
extreme.

>
> But point taken and thanks for the data.
>
> I'm comfortable with a 6 patch "limit". I put limit in scare quotes
> because I assume you all know that high priority changes can go out when
> they need to go out. The limit is to reduce SWAT deploy stress for what
> is possible in a 1 hour window and not try to squeeze things in and
> reduce the clarity when watching logs.
>
> Greg
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |
>
> ___
> 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] Code of Conduct for Wikimedia technical spaces - Code of Conduct Committee - 2018.II members

[Derk-Jan Hartman]

Thank you candidates and committee !

DJ

On Fri, Apr 27, 2018 at 6:05 PM, Sébastien Santoro
 wrote:
> Hello all,
>
> The candidate slates has been deemed finalized.
>
> Thanks to the new candidates joining the committee to support
> this important mission, sustaining our code of conduct.
>
> We didn't receive a lot of candidatures this session, so we'd like
> to ask you to think for the next months if you would like to serve
> in the 2019 half I committee, and to be ready in October to join
> the boat.
>
> [ Candidates URL ]
>
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Candidates/2018-I
>
> This page will be moved to the members page when the new committee
> will enter in function after a training period for new members.
>
> [ Procedure ]
>
> We haven't received any feedback to techconduct (at) twikimedia.org
> related to one or another candidate.
>
> In addition to the procedure the Code of Conduct provides, we also
> received additional comments at [[mw:Talk:Code of
> Conduct/Committee/Candidates/2018-I]] and consider these comments
> party addressed and partly to solve in the next weeks, and unrelated
> to the current candidates.
>
> --
> Sébastien Santoro aka Dereckson
> http://www.dereckson.be/
>
> ___
> 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