[Wikitech-l] Re: User style to reduce Gerritbot comments on Phabricator

[Greg Grossmeier]

Thanks Bartosz!

On Wed, Nov 29, 2023 at 1:02 PM Bartosz Dziewoński 
wrote:

> Do your eyes glaze over when trying to make sense of Phabricator tasks
> with a long and troubled history of patches? Do you struggle to find the
> real people in the sea of automated bot comments?
>
> I've made myself a user style to compact the Gerritbot comments on
> Phabricator. You might like it too:
>
> https://userstyles.world/style/13140/wikimedia-phabricator-reduce-gerritbot-comments
>
> (See screenshots and installation instructions there.)
>
> --
> Bartosz Dziewoński
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: commit-message-validator 1.0.0 released

[Greg Grossmeier]

On Sat, Aug 13, 2022 at 8:25 AM Kunal Mehta  wrote:

> Coincidentally we just passed the 6 year anniversary of this tool. It
> was originally written by Bryan Davis and then improved by contributions
> from Fabian Neundorf, Rafid Aslam, dalba, Arturo Borrero Gonzalez,
> Antoine Musso, Ahmon Dancy and myself. Here's to another 6 years!
>

Hear hear!
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Facing a Problem in issue #105

[Greg Grossmeier]

Hi,

Searching for "afch-rewrite" leads me to
https://github.com/WPAFC/afch-rewrite with the homepage of
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Articles_for_creation/Helper_script
.
I presume that is what this is about.

Their documentation says they use a Zulip for communication:
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Articles_for_creation/Helper_script/Contributing#Need_help?


Might want to try there if the github issue isn't proving helpful.

Best,

Greg

On Fri, Feb 4, 2022 at 9:08 PM AMEY Gupta  wrote:

> Hey I am facing a problem in issue #105  in ( afch-rewrite). I am
> following this approach for (avoiding empty comments) . At first I wrote a
> function to calculate the length of the text area and if the text area's
> length is 0 then I,ll disabled the button . but I am getting confused about
> how to get the button disabled .
>
>   Screenshot (302)_LI.jpg
> 
>
>   Screenshot (303)_LI.jpg
> 
>
>
>
>
>
>
>
>
>
> On Fri, 4 Feb, 2022, 10:07 pm Andre Klapper, 
> wrote:
>
>> On Fri, 2022-02-04 at 20:31 +0530, Ameygupta wrote:
>> > Hey I am facing a problem in issue #105 (Don.t enter empty comments)
>> > can anyone help me about it ?
>>
>> Not without further context, I'm afraid. :) What and where is "issue
>> #105"? Please provide sufficient context, as this is a mailing list
>> with hundreds of members and about any kind of Wikimedia related
>> development (which means thousands of software projects).
>>
>> Thanks,
>> andre
>> --
>> Andre Klapper (he/him) | Bugwrangler / Developer Advocate
>> https://blogs.gnome.org/aklapper/
>> ___
>> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
>> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
>>
>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: UserMerge has been undeployed from Wikimedia wikis

[Greg Grossmeier]

Thanks for that clean-up work! It's important but easily underprioritized.
We all appreciate it!

On Tue, Jan 25, 2022 at 2:18 AM Taavi Väänänen  wrote:

> Hi all,
>
> I've just undeployed the UserMerge extension from all Wikimedia
> wikis[0], after it has been unused and unmaintained for multiple years.
> This means that policy[1] no longer requires that all other WMF deployed
> extensions are compatible with it.
>
> [0]: https://phabricator.wikimedia.org/T216089
> [1]: https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment
>
> -- Taavi (User:Majavah)
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Some Phabricator and Gerrit 2021 statistics

[Greg Grossmeier]

This is great, Andre; thank you!

And thanks to everyone who contributed last year!

On Sat, Jan 1, 2022 at 12:52 PM Andre Klapper 
wrote:

> Well, hello.
>
> Sharing random numbers from that past Gregorian calendar year 2021 with
> you. Big thanks to all technical contributors! <3
>
> === Phabricator 2021 ===
>
> * 27432 tasks got created.
> * 24723 tasks got closed.
> * 3746 people were active in Phabricator.
> * 2171 people created tasks.
> * 787 people closed tasks.
> * The 20 people who created the most tasks:
> ppelberg   426
> Reedy  379
> Lucas_Werkmeister_WMDE 374
> Legoktm355
> Jdlrobson  336
> Jdforrester-WMF324
> RobH   304
> Aklapper   271
> Inductiveload  256
> Addshore   244
> dcaro  244
> Majavah232
> bd808  232
> DVrandecic 231
> cmassaro   215
> kostajh215
> kai.nissen 212
> Krinkle200
> Michael196
> DannyS712  195
> * The 20 people who closed the most tasks:
> Aklapper   981
> Addshore   672
> Jdlrobson  583
> Jdforrester-WMF580
> Jopparn558
> Etonkovidova   546
> ppelberg   490
> Urbanecm   466
> Krinkle374
> Lucas_Werkmeister_WMDE 340
> hashar 333
> Reedy  332
> Samwalton9 321
> LGoto  314
> Legoktm309
> Xqt294
> ovasileva  288
> kai.nissen 268
> Gehel  255
> matmarex   251
>
> === Gerrit 2021 ===
>
> * 54097 changesets got created. [1]
> * 98771 code reviews took place. [2]
> * 586 people created patches. [3]
> * The 20 people who submitted the most changesets: [4]
> Umherirrender 2609
> Robert Vogel  1319
> DannyS712 1265
> Zabe  1251
> Legoktm   1241
> Jforrester1237
> Jbond 1225
> Reedy 1198
> Urbanecm  1147
> Pwirth1032
> Lucas Werkmeister (WMDE)   966
> Xqt920
> Eileen 901
> Ladsgroup  901
> Thiemo Kreuz (WMDE)897
> Andrew Bogott  745
> Elukey 715
> Marostegui 703
> Muehlenhoff684
> Dzahn  682
> * The 20 people who reviewed the most patchsets: [5]
> Jforrester4176
> Jbond 4045
> DannyS712 3855
> Robert Vogel  3119
> Umherirrender 2986
> Kunal Mehta   2516
> Moritz Muehlenhoff2231
> Luca Toscano  2223
> Daniel Zahn   2144
> Patric Wirth  1823
> Andrew Bogott 1811
> Marostegui1713
> Martin Urbanec1709
> Filippo Giunchedi 1602
> Ppchelko  1526
> Andrew Otto   1482
> Jon Robson1378
> aborrero  1327
> Timo Tijhof   1289
> Giuseppe Lavagetto1252
>
> If you find a bug in these numbers, please see
> https://www.mediawiki.org/wiki/Community_metrics
>
> Cheerio,
> andre
>
> [1] See "Gerrit  Changesets" on "Gerrit  Overview":
> https://wikimedia.biterg.io/goto/c2b4d03d9afadd08b1e1a5df87071276
> [2] See "Total Number of Code Reviews  Approvals" on "Gerrit 
> Approvals":
> https://wikimedia.biterg.io/goto/e055063561a4880db0a65c4727cdf919
> [3] See "Gerrit  Changeset Submitters" on "Gerrit  Overview":
> https://wikimedia.biterg.io/goto/c2b4d03d9afadd08b1e1a5df87071276
> [4] See "Submitters" on "Gerrit  Overview":
> https://wikimedia.biterg.io/goto/c2b4d03d9afadd08b1e1a5df87071276
> [5] See "Approvals by Reviewer" on "Gerrit  Approvals":
> https://wikimedia.biterg.io/goto/e055063561a4880db0a65c4727cdf919
>
> --
> Andre Klapper (he/him) | Bugwrangler / Developer Advocate
> https://blogs.gnome.org/aklapper/
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org

[Wikitech-l] Re: Code coverage for JavaScript testing?

[Greg Grossmeier]

On Tue, Oct 26, 2021 at 2:31 AM planetenxin  wrote:

> Is there a generic approach, how to get some coverage reports for the
> JavaScript parts of MW and MW extensions?
>

Is https://doc.wikimedia.org/cover/ helpful in your case?

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: What does "ltsrel" mean?

[Greg Grossmeier]

I've updated [[Compatibility]] but I'm not sure which part of
[[Template:Extension]] needs updating. Help?

On Fri, Oct 1, 2021 at 8:47 AM Ike Hecht  wrote:

> That would be great! Can you also update Template:Extension to match,
> please?
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: What does "ltsrel" mean?

[Greg Grossmeier]

Hi Ike,

The key distinction is in the "Version lifecycle release policy" link for
the ltsrel definition. Another way of phrasing it would be:
"* long-term support release branches: For every MediaWiki release that is
a Long Term Support release (see [[mw:Version lifecycle]]) there is a
corresponding branch in the extension."

If that makes sense to you (and others) I can edit that page for clarity.

Greg

On Thu, Sep 23, 2021 at 8:55 PM Ike Hecht  wrote:

> I'm confused about what the term "ltsrel" means. The way I understand it,
> it *should* mean that the extension supports only Long Term Support
> versions of MediaWiki. It would have a branch for every LTS version of
> MediaWiki like REL1_31 and REL1_35, but not for REL1_32, REL1_33 or REL1_34.
>
> However, on the Compatibility
> <https://www.mediawiki.org/wiki/Compatibility#MediaWiki_extensions> page,
> the rel and ltsrel policies are described as:
>
> * release branches (key: rel): For every MediaWiki release, there is a
> corresponding branch in the extension. So e.g. if you use MediaWiki 1.36,
> you should use the REL1_36 branch of the extension.
>
> * long-term support release branches (key: ltsrel): For every MediaWiki
> release, there is a corresponding branch in the extension, following the
> Version lifecycle release policy.
>
> These sound exactly alike to me.
>
>
>
>
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/



-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: How we deploy code

[Greg Grossmeier]

This is great, thanks Tyler! \o/

On Mon, Sep 27, 2021 at 3:25 PM Tyler Cipriani 
wrote:

> Last week, I spoke to a few of my Wikimedia Foundation colleagues about
> how we deploy code—I completely botched it.
>
> At the end of the conversation, I was pretty sure I'd only succeeded  in
> making a complex process more opaque. I decided to write a blog to redeem
> myself: How We Deploy Code
> <https://phabricator.wikimedia.org/phame/post/view/253/how_we_deploy_code/>
>
> My goal was to write a very high-level overview of the process we use to
> deploy code to Wikimedia production.
>
> Hopefully, this is helpful.
>
> <3
> – Tyler Cipriani (he/him)
> Engineering Manager, Release Engineering
> Wikimedia Foundation
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/



-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Phabricator upstream shutdown

[Greg Grossmeier]

cc'ing engineering-all@ as well.

Yes it is true that Phacility, the Phabricator upstream, is winding down.

For the short term nothing changes for us/Wikimedia. Our Phabricator
install is fine and working.

Medium to longer term I expect some sort of decision making process that
the Engineering Productivity team will shepherd/lead (as owners of our
Phabricator installation and management) in collaboration with other teams
(notably Technical Engagement) and the community. Details to come.

Tomorrow, Monday, is a US Holiday and the rest of this week is an
Engineering Productivity Virtual Offsite. Our ability to be involved with
the conversation this week is thus very limited.

We'll communicate the next steps when we have them.

Thank you,

Greg

On Sat, May 29, 2021 at 6:01 PM AntiCompositeNumber <
anticompositenum...@gmail.com> wrote:

> https://phabricator.wikimedia.org/T283980
>
> On Sat, May 29, 2021 at 9:00 PM Brian Wolff  wrote:
> >
> > It sounds like phabricator upstream is going away:
> https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
> >
> > Just curious, are we planning to continue using it long term or move to
> something else?
> >
> > --
> > Brian
> > ___
> > Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> >
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Abstract Schema: An Update

[Greg Grossmeier]

(Adding engineering-all@ for Wikimedia engineers' awareness.)

Good work on this Amir, James, Gergo, Reedy, DBAs, and all the others not
mentioned.

Cleaning up tech debt to provide a stable base for future code hygiene is
important, hard, and sometimes thankless work.

Greg

On Thu, May 27, 2021 at 4:33 PM Amir Sarabadani  wrote:

> Hello,
> If you missed the previous updates, there's the first
> <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/message/HSVI63YWZP7OOXB46WP2NRH2RWNPYA2I/>and
> the second
> <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/message/TMFVXO46J57BWQHQGZXXICXNY35EVOMI/>one.
> This is the last one I'm sending but in a good way.
>
> We now finished migrating all 57 core tables to abstract schema. Now 
> tables.sql
> is empty for MySQL
> <https://gerrit.wikimedia.org/g/mediawiki/core/+/c60ccf4e6d4932dddc2efd72a8abf6e56243f086/maintenance/tables.sql>.
> We will soon remove the tables.sql files and links to them.
>
> We have also cleaned more than hundreds of old schema change files.
> <https://phabricator.wikimedia.org/T272199> That enabled us to actually
> look for unused sql files and drop tens of unused ones that have not been
> used since 2002 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668552>,
> 2004 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668761>, or 2005
> <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/670176> (and much
> more) and they got lost in the sheer number of our sql patch files.
>
> The next update is exciting for me. With abstraction in place, we can now
> have a proper tracking of drifts between schema in paper and our production
> (This is a follow up from a major incident in 2018). Now we have
> https://drift-tracker.toolforge.org/ that keeps track of these drifts.
> Our schema has been around for more than twenty years and we have hundreds
> of database hosts, making sure everything is using the right database
> schema (and stays correct) is impossible manually and we have been finding
> and fixing these drifts since 2018, see this comment onwards
> <https://phabricator.wikimedia.org/T104459#4314828>.). Of course more
> work in improving the tracker is welcome (here's the list
> <https://phabricator.wikimedia.org/project/board/5350/>)
>
> If you want to enjoy the benefits of abstract schema [1] in extension(s)
> you or your team maintains, Please abstract the schema of your extension.
> There's a long list of WMF deployed extensions that are not using
> abstract schema <https://phabricator.wikimedia.org/T261912> and some even
> already have a patch that only needs reviewing. Once that's done, we can
> add that to drift tracking and have a more comprehensive list of potential
> issues. If you need help with the abstraction work, just ping me.
>
> This also helped us resolve several long-standing tickets like T104459
> <https://phabricator.wikimedia.org/T104459> (5.5 years old), T62962
> <https://phabricator.wikimedia.org/T62962> (7 years old), and T42626
> <https://phabricator.wikimedia.org/T42626> (soon reaching its ninth
> birthday) and will help us to address even more tech debt in future.
>
> There is more to be done, improving the abstract schema *change* system,
> finding a home of schema documentation, improving the drift tracker and
> making it more automated, so much more. But the biggest chunk of work is
> now finally done.
>
> I really would like to thank Ammarpad for great work on abstracting the
> tables and handling all sorts of edge cases, James Forrester and Tgr for
> their reviews which without them this wouldn't be possible and Sam Reed who
> wrote a script to speed up migration
> <https://github.com/Ladsgroup/db-analyzor-tools/blob/master/db_abstractor.py>.
> This was a team work to its core.
>
> [1] In more details, by abstracting you will have automated checks for
> dirfits of the schema of extension(s) you maintain and production. You will
> have Postgres support for free. Also, you can have automated documentation
> generation, ability to test the schema itself, and have better consistency
> of your data types (like one datatype for timestamps).
>
> Until the next adventure.
> --
> Amir (he/him)
>
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/



-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

Re: [Wikitech-l] Extension! Re: Wikimedia Developer Satisfaction Survey - 2021!

[Greg Grossmeier]

Hi Michael,

Thank you for that. We will address this in future editions of the survey.

In the interest of not making the survey data inconsistent, I'm going to
recommend just giving a neutral (3) response to ones that you aren't as
familiar with. Given the number of responses we already have, I think this
makes more sense than adding a "N/A" option or making the questions
optional.

Thank you,

Greg

On Thu, Mar 25, 2021 at 12:01 AM Michael Schönitzer <
michael.schoenit...@wikimedia.de> wrote:

> Hi,
>
>
>> tl;dr: It's time for the annual Developer Satisfaction Survey! *This
>>> survey is for everyone who uses any of the tools or services mentioned
>>> below*, whether you would call yourself a "developer" or not. *Closing
>>> date is March 24th.*
>>>
>>
> As a feedback to the survey:
> The survey contains *mandatory* questions to rate one's satisfaction with
> each of these services. How should one rate the satisfaction with a service
> that one does not use at all? At least for my perception this is not
> possible and therefore the survey is only suitable for everyone who uses
> *all* listed services at least to some point.
> I wonder what is the motivation for making these questions mandatory? As a
> user I am often frustrated by those, because I have the choice to
> either cancel filling out the form, or risk to dilute the results.
>
> Cheers,
>  M
>
>
>> *The survey*: https://forms.gle/xj2jNUcP7kmSgtwV8
>>>
>>> Longer:
>>> The Wikimedia Foundation is soliciting your feedback to measure
>>> developer satisfaction and determine where to invest resources in the
>>> future. This is the third iteration of this survey. We want feedback from
>>> everyone who uses any of the below tools or services, whether you call
>>> yourself a "developer" or not.
>>>
>>> Topics covered include:
>>> * Local Development Environment
>>> * Beta Cluster / Staging Environment
>>> * Testing / CI
>>> * Code Review
>>> * Deployments
>>> * Account Management and Onboarding
>>> * Observability
>>> * Phabricator
>>> * Developer documentation
>>> * General Feedback
>>>
>>> We are soliciting feedback from all Wikimedia developers, including
>>> Staff, 3rd party contributors and volunteer developers. *The survey
>>> will be open for a little over 2 weeks, closing on Wednesday March 24th.*
>>>
>>> NOTE: This survey will be conducted via a third-party service, which may
>>> be subject to additional terms. For more information on privacy and
>>> data-handling, see the survey privacy statement
>>> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
>>>
>>> *To participate in this survey, please start here:*
>>>
>>> https://docs.google.com/forms/d/e/1FAIpQLSfJCzxixT1wHCIgI5PijIMQvcIqDbsDTYbbDoxXaYcyF8RhJg/viewform?usp=sf_link
>>>
>>> Thank you for your participation,
>>>
>>> Greg
>>>
>>> --
>>> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
>>> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>>>
>>
>>
>> --
>> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
>> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>
>
> --
> *M. F. Schönitzer** (they/them)*
> Community Communication
>
> Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
>
> Tel. (030) 219 158 26-0
>
> https://wikimedia.de
>
> Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit
> teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
>
> https://spenden.wikimedia.de
>
> Imagine a world in which every single human being can freely share in the
> sum of all knowledge. Help us to achieve our vision!
>
> https://spenden.wikimedia.de
>
> Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
> der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
> Körperschaften I Berlin, Steuernummer 27/029/42207.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Forthcoming failover of irc.wikimedia.org to a new server (2021-03-25)

[Greg Grossmeier]

Adding wikitech-ambassadors@ just in case.

On Wed, Mar 24, 2021 at 2:55 AM Moritz Mühlenhoff 
wrote:

> Hi,
> the DNS name for irc.wikimedia.org [1] will be redirected to a new
> instance (irc2001.wikimedia.org) tomorrow (European) morning. This new
> instance is running a more recent OS (Debian 10/Buster).
>
> Mediawiki changes are currently broadcasted to both the old server
> (kraz.wikimedia.org) and the new irc2001.wikimedia.org. As such, the
> failover should be transparent, unless for some reason a bot has
> hardcoded kraz.wikimedia.org or it's IP address 208.80.153.44 (which
> will then need to be updated to resolve irc.wikimedia.org). The old
> instance will be around for another week.
>
> If there are any issues, please report them at
> https://phabricator.wikimedia.org/T224579
>
> Cheers,
> Moritz
>
> Footnotes:
> [1] https://wikitech.wikimedia.org/wiki/Irc.wikimedia.org
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Extension! Re: Wikimedia Developer Satisfaction Survey - 2021!

[Greg Grossmeier]

Good news!

The deadline to submit your answers to this year's Developer Satisfaction
Survey is extended!

You now have until next *Wednesday March 31st*!

Right now we're at about 60 responses. Last year we hit 75. Please fill
this out so we can continue improving!

Get your feedback in!

Thanks,

Greg

On Mon, Mar 8, 2021 at 9:54 AM Greg Grossmeier  wrote:

> Hello!
>
> tl;dr: It's time for the annual Developer Satisfaction Survey! *This
> survey is for everyone who uses any of the tools or services mentioned
> below*, whether you would call yourself a "developer" or not. *Closing
> date is March 24th.*
>
> *The survey*: https://forms.gle/xj2jNUcP7kmSgtwV8
>
> Longer:
> The Wikimedia Foundation is soliciting your feedback to measure developer
> satisfaction and determine where to invest resources in the future. This is
> the third iteration of this survey. We want feedback from everyone who uses
> any of the below tools or services, whether you call yourself a "developer"
> or not.
>
> Topics covered include:
> * Local Development Environment
> * Beta Cluster / Staging Environment
> * Testing / CI
> * Code Review
> * Deployments
> * Account Management and Onboarding
> * Observability
> * Phabricator
> * Developer documentation
> * General Feedback
>
> We are soliciting feedback from all Wikimedia developers, including Staff,
> 3rd party contributors and volunteer developers. *The survey will be open
> for a little over 2 weeks, closing on Wednesday March 24th.*
>
> NOTE: This survey will be conducted via a third-party service, which may
> be subject to additional terms. For more information on privacy and
> data-handling, see the survey privacy statement
> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
>
> *To participate in this survey, please start here:*
>
> https://docs.google.com/forms/d/e/1FAIpQLSfJCzxixT1wHCIgI5PijIMQvcIqDbsDTYbbDoxXaYcyF8RhJg/viewform?usp=sf_link
>
> Thank you for your participation,
>
> Greg
>
> --
> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikimedia Developer Satisfaction Survey - 2021!

[Greg Grossmeier]

Hello!

tl;dr: It's time for the annual Developer Satisfaction Survey! *This survey
is for everyone who uses any of the tools or services mentioned below*,
whether you would call yourself a "developer" or not. *Closing date is
March 24th.*

*The survey*: https://forms.gle/xj2jNUcP7kmSgtwV8

Longer:
The Wikimedia Foundation is soliciting your feedback to measure developer
satisfaction and determine where to invest resources in the future. This is
the third iteration of this survey. We want feedback from everyone who uses
any of the below tools or services, whether you call yourself a "developer"
or not.

Topics covered include:
* Local Development Environment
* Beta Cluster / Staging Environment
* Testing / CI
* Code Review
* Deployments
* Account Management and Onboarding
* Observability
* Phabricator
* Developer documentation
* General Feedback

We are soliciting feedback from all Wikimedia developers, including Staff,
3rd party contributors and volunteer developers. *The survey will be open
for a little over 2 weeks, closing on Wednesday March 24th.*

NOTE: This survey will be conducted via a third-party service, which may be
subject to additional terms. For more information on privacy and
data-handling, see the survey privacy statement
https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement

*To participate in this survey, please start here:*
https://docs.google.com/forms/d/e/1FAIpQLSfJCzxixT1wHCIgI5PijIMQvcIqDbsDTYbbDoxXaYcyF8RhJg/viewform?usp=sf_link

Thank you for your participation,

Greg

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] A clearer line on logspam

[Greg Grossmeier]

Hi all!

tl;dr: There's a large backlog of production errors. Release Engineering is
blocking the train for any new logspam. Your help is needed!

A quick update on the deployment train:

In the process of rolling out wmf/1.36.0-wmf.28 there were a number of
issues that prevented us from rolling forward the train in a timely manner.
After the issues were resolved and backports deployed to the current
version in production (wmf/1.36.0-wmf.27), we realized there were a few
remaining spammy log messages and blocked the following week's train on
those issues.

Release Engineering has long blocked the train on logspam issues[0]. Even
when it does not indicate user-facing errors, logspam of any kind makes it
harder for us to see real problems. We have, however, defaulted to pushing
forward the train despite minor issues.

Under this custom, many log messages have been accepted as "just
occassional, not a big deal" or "yeah, we'll fix that eventually... it's
not a big deal". Frequently, "eventually" never arrives. This results in an
unmanageable accumulation of exceptions (see the ever-growing list of
exceptions in the Wikimedia-production-error workboard[1] and logstash[2]).

To deal with these issues we are now, as a matter of policy, blocking
trains that cause any new error messages. In most cases new errors are the
result of code changes that lack defensive coding practices and/or have
unexpected interactions with other code. The best resolution in these cases
is for the code to be fixed or reverted.

Release Engineering organises a weekly "train log triage" meeting, on
Wednesdays at 19:00 UTC, where we invite people who develop MediaWiki to
help triage log messages. As of this week, there is also a second one, on
Thursdays at 10:00 UTC, to be more suitable for people in EU time zones. We
invite everyone who develops MediaWiki or its extensions to join one of the
meetings each week.

Thank you,

Greg

[0]: <
https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train#Logspam>
[1]: https://phabricator.wikimedia.org/project/view/1055/
[2]:
https://logstash.wikimedia.org/app/dashboards#/view/0a9ecdc0-b6dc-11e8-9d8f-dbc23b470465




-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] GitLab announcement: on the future of code review

[Greg Grossmeier]

Hello all,


I am pleased to announce that the GitLab consultation working group 
<https://www.mediawiki.org/wiki/GitLab_consultation#Working_Group>has 
determined that migrating our code repositories from Gerrit to Gitlab is 
the right decision.


For the last 3 weeks the working group has been summarizing the 
feedback, working on initial GitLab documentation (work-flows, ACLs, 
etc), and drafting other documentation that will be useful during this 
migration. While we might not have all the problems figured out, the 
group is confidentthat Gitlab is a better solution and that any concerns 
can be sufficiently dealt with.


The GitLab consultation wiki page has been updated with the decision 
<https://www.mediawiki.org/wiki/GitLab_consultation#Outcome>and we’ve 
created a new landing page for all things GitLab 
<https://www.mediawiki.org/wiki/GitLab>at Wikimedia.


For the immediate future nothing changes. The goal is to have a GitLab 
installation ready with a few self-contained repositories moved to it by 
this coming June, about 8 months from now. The roadmap 
<https://www.mediawiki.org/wiki/GitLab/Roadmap>, and its evolution, is 
on wiki.


Thank you to everyone who engaged with this consultation; I truly 
believe that we are in a better position because of all of the open and 
constructive dialog.


I want to personally thank the members of the working group by name. 
They all did amazing work and made working on this consultation as fun 
as it could feasibly be. Thank you all for you great work!


 * Scott Bassett
 * Brennen Bearnes
 * Daniel Cipolleti
 * Tyler Cipriani
 * Markus Glaser
 * Derk-Jan Hartman
 * Conny Kawohl
 * Andre Klapper
 * Niklas Laxström
 * Effie Mouzeli
 * Chase Pettet
 * Lucas Werkmeister

Thank you, everyone, for your participation,
Greg

--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] GitLab consultation is now closed!

[Greg Grossmeier]

On 10/2/20 15:20, Greg Grossmeier wrote:
Per the timeline the working group will begin (continue, really) its 
deliberations and then we will share out our decision by Friday Oct 23rd.
As I have been reminded, announcing things on Friday is a bad practice. 
As such, we'll delay the announcement until Monday October 26th.


Thank you for your patience,

Greg, on behalf of the GitLab Consultation Working Group

--

| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] GitLab consultation is now closed!

[Greg Grossmeier]

On 9/2/20 12:15, Greg Grossmeier wrote:

Hello all,

I am pleased to announce that the GitLab consultation is now open.

The open discussion period is set to run for 4 weeks, starting today.


4.5 weeks later and the consultation period is now closed (at the end of 
today, whenever that is for you).


Per the timeline the working group will begin (continue, really) its 
deliberations and then we will share out our decision by Friday Oct 23rd.


Thank you for your engagement,

Greg, on behalf of the GitLab Consultation Working Group

--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] Wikimedia Phabricator Tutorial Videos available on Commons

[Greg Grossmeier]

On 9/30/20 03:12, Andre Klapper wrote:

Hi everyone,

if you've also sometimes wondered about using Wikimedia Phabricator or
struggle a bit with it: I made some tutorial videos how to best use it
(including English subtitles). They are now linked from the top of

   https://www.mediawiki.org/wiki/Phabricator/Help


Nicely done!


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

Re: [Wikitech-l] GitLab consultation is open!

[Greg Grossmeier]

Hello!

The GitLab consultation <https://www.mediawiki.org/wiki/GitLab_consultation>
open discussion period is ending this week
<https://www.mediawiki.org/wiki/GitLab_consultation#When>! Please engage
with the discussion on the talk page
<https://www.mediawiki.org/wiki/Talk:GitLab_consultation>; notable topics
include workflows (how best to use a merge request style system) and
inclusion/onboarding.

Given I failed to send out the "1 week left!" reminder last week on
Wednesday, I've extended the official close of discussion
<https://www.mediawiki.org/w/index.php?title=GitLab_consultation=revision=4132967=4132512=source>
to Friday October 2nd.

After the close of discussion the consultation working group members will
begin our deliberations and creation of summary documentation.

Best,

Greg


On Wed, Sep 2, 2020 at 12:15 PM Greg Grossmeier  wrote:

> Hello all,
>
> I am pleased to announce that the GitLab consultation is now open.
>
> The open discussion period is set to run for 4 weeks, starting today.
>
> Please see the consultation page for all of the details regarding how the
> consultation will work:
> https://www.mediawiki.org/wiki/GitLab_consultation
>
> And the associated talk page where we welcome and encourage your
> engagement:
> https://www.mediawiki.org/wiki/Talk:GitLab_consultation
>
> Thank you,
>
> Greg
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |
>
>

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GitLab consultation is open!

[Greg Grossmeier]

Hello!

This is a friendly reminder that the GitLab consultation is still open 
but officially closing on September 30th (a little less than 2 weeks 
from now).


https://www.mediawiki.org/wiki/GitLab_consultation

There is some good conversation already happening on the Talk page:
https://www.mediawiki.org/wiki/Talk:GitLab_consultation

If you would like to engage with the consultation please do so before it 
closes!


Best,

Greg and the rest of the consultation working group.


On 9/2/20 12:15, Greg Grossmeier wrote:

Hello all,

I am pleased to announce that the GitLab consultation is now open.

The open discussion period is set to run for 4 weeks, starting today.

Please see the consultation page for all of the details regarding how 
the consultation will work:

https://www.mediawiki.org/wiki/GitLab_consultation

And the associated talk page where we welcome and encourage your engagement:
https://www.mediawiki.org/wiki/Talk:GitLab_consultation

Thank you,

Greg

--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |




--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |

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

[Wikitech-l] GitLab consultation is open!

[Greg Grossmeier]

Hello all,

I am pleased to announce that the GitLab consultation is now open.

The open discussion period is set to run for 4 weeks, starting today.

Please see the consultation page for all of the details regarding how 
the consultation will work:

https://www.mediawiki.org/wiki/GitLab_consultation

And the associated talk page where we welcome and encourage your engagement:
https://www.mediawiki.org/wiki/Talk:GitLab_consultation

Thank you,

Greg

--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity   A18D 1138 8E47 FAC8 1C7D |

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

[Wikitech-l] CI and Code Review

[Greg Grossmeier]

First, apologies for not announcing this last week. A short work week
coupled with a new fiscal year delayed this until today.

tl;dr: Wikimedia will be moving to a self-hosted (in our datacenter(s))
GitLab Community Edition (CE) installation for both code review and
continuous integration (CI).

Longer:
We are making a change to our code review and continuous integration (CI)
systems in response to a complex set of inputs (Developer Satisfaction
Survey[0], passing comments/critiques, an evaluation of replacement
continuous integration infrastructure[1], feedback from leaders in the
Foundation, etc) and evaluation conversations with Wikimedia Technology
department leadership (eg CTO, VPs) and representatives from Wikimedia SRE,
Architecture, Core Platform, Product, Security, and Technical Engagement
teams. In those conversations with Technology department leadership,
coordinated by our CTO Grant Ingersoll, we determined that an RFC was not
needed for this decision[2].

We plan to replace Gerrit and Zuul+Jenkins (the software that powers our CI
system) with GitLab. We hope that making a move to GitLab now will address
most of the concerns and desires that are able to be addressed via software
alone.

We join a growing list of other free/open knowledge organizations using a
self-hosted GitLab installation and look forward to the added benefits of
working together with them.

The project portal page lives at:
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/GitLab
It is a living documentation portal and we will continue to update it as we
go. The Talk: page is also available for your feedback and questions (and
is already being used). We hope everyone will join in to make this
transition as successful as possible.

Notably, I would like to point people to the conversation[3] about
evaluating pull-request style workflows and finding a recommended workflow
for our projects. While pull-request workflows are much more common in the
wider software development world{{cn}} we would like to provide as much
guidance as reasonable so that we are using our tools to the best of their
ability.

Here is the list of stakeholders as we have them now. In a RACI[4] model
these would be Consulted. These are the people the Wikimedia Release
Engineering team will be consulting with most closely as they get this
going.
* SRE/Service Ops - Mark and delegate(s)
* Security - Chase P and Scott B
* Core Platform Team - TBD
* Technical Engagement - TBD
* Product - Daniel C

“TBD” means we have asked for a representative and we’re waiting to hear
back on confirmation. We also have a few other non-WMF groups that we have
already reached out to or will be shortly to include in that list; feel
free to ping me with other suggestions.

What does this mean for you as you do your work today? Right now, nothing.
But as we set up the new GitLab installation we will be looking for early
adopters to give us feedback as we work on improvements. As we start to
migrate more users and repositories we will strive to help everyone as much
as possible and reasonable. It should go without saying that this includes
completely volunteer projects using the shared infrastructure.

The full timeline and plan will be posted to the above project portal page.

For the avoidance of doubt, this does not impact issue/task management;
that will remain in Phabricator.

Thank you,

Greg

PS: Please let me know where else this announcement should be sent.

[0] https://www.mediawiki.org/wiki/Developer_Satisfaction_Survey/2020
[1]
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/CI_Futures_WG
[2] see also:
https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Charter#Areas_within_scope
[3] https://www.mediawiki.org/wiki/Topic:Vpbwawb4lkdy89ym
[4] https://en.wikipedia.org/wiki/Responsibility_assignment_matrix
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Backport and Config changes window (name change)

[Greg Grossmeier]

Hello everyone,

Until today if you wanted to get a backport or config change deployed to
production you used what was termed the "SWAT" window.

As of today that window of time is now called the "Backport and Config"
window. This solves a few problems. First, the overly militarized and
violence-implying name is no longer something we want in our community.
Second, this now accurately and clearly describes what the purpose of the
window is.

This should now be changed everywhere including the Deployment Calendar[0],
but if you see any errant mentions of it in documentation, please feel free
to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.

Thank you,

Greg

[0] https://wikitech.wikimedia.org/wiki/Deployments


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Satisfaction Survey

[Greg Grossmeier]

Last message, I promise :)

We won't be reviewing these results until next week, so you have until
Tuesday March 10th (Monday is a WMF US staff holiday) to put in your last
minute opinions!

Thank you,

Greg

On Wed, Mar 4, 2020 at 2:02 PM Greg Grossmeier  wrote:

> Reminder again! 2 more days!
>
> We have about the same number of responses as we did last year (almost
> 60). But given our growth of staff in the past year I hope we can get a few
> more this year.
>
> Please do share your thoughts with us: we use this data and commentary to
> plan our work to better serve you.
>
> Thank you,
>
> Greg
>
> On Wed, Feb 19, 2020 at 2:14 PM Greg Grossmeier 
> wrote:
>
>> Hello!
>>
>> The Wikimedia Foundation is soliciting your feedback to measure developer
>> satisfaction and determine where to invest resources in the future. This is
>> the second iteration of this survey.
>>
>> Topics covered include:
>> * Local Development Environment
>> * Beta Cluster / Staging Environment
>> * Testing / CI
>> * Code Review
>> * Deployments
>> * Production Systems
>> * Development and Productivity Tools
>> * Developer Documentation
>>
>> We are soliciting feedback from all Wikimedia developers, including
>> Staff, 3rd party contributors and volunteer developers. *The survey will
>> be open for a little over 2 weeks, closing on Friday March 6th.*
>>
>> This survey will be conducted via a third-party service, which may
>> subject it to additional terms. For more information on privacy and
>> data-handling, see the survey privacy statement
>> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
>>
>> To participate in this survey, please start here:
>>
>> https://docs.google.com/forms/d/e/1FAIpQLSclq5vtaonRjwQykpfi2lbLIzJl-9wcOzmzXn4xnigd_DFlpw/viewform
>>
>> Thank you for your participation,
>>
>> Greg
>>
>> --
>> | Greg Grossmeier      GPG: B2FA 27B1 F7EB D327 6B8E |
>> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>>
>
>
> --
> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Satisfaction Survey

[Greg Grossmeier]

Reminder again! 2 more days!

We have about the same number of responses as we did last year (almost 60).
But given our growth of staff in the past year I hope we can get a few more
this year.

Please do share your thoughts with us: we use this data and commentary to
plan our work to better serve you.

Thank you,

Greg

On Wed, Feb 19, 2020 at 2:14 PM Greg Grossmeier  wrote:

> Hello!
>
> The Wikimedia Foundation is soliciting your feedback to measure developer
> satisfaction and determine where to invest resources in the future. This is
> the second iteration of this survey.
>
> Topics covered include:
> * Local Development Environment
> * Beta Cluster / Staging Environment
> * Testing / CI
> * Code Review
> * Deployments
> * Production Systems
> * Development and Productivity Tools
> * Developer Documentation
>
> We are soliciting feedback from all Wikimedia developers, including Staff,
> 3rd party contributors and volunteer developers. *The survey will be open
> for a little over 2 weeks, closing on Friday March 6th.*
>
> This survey will be conducted via a third-party service, which may subject
> it to additional terms. For more information on privacy and data-handling,
> see the survey privacy statement
> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
>
> To participate in this survey, please start here:
>
> https://docs.google.com/forms/d/e/1FAIpQLSclq5vtaonRjwQykpfi2lbLIzJl-9wcOzmzXn4xnigd_DFlpw/viewform
>
> Thank you for your participation,
>
> Greg
>
> --
> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Satisfaction Survey

[Greg Grossmeier]

Reminder! You have a little over a week remaining to complete the survey.

On Wed, Feb 19, 2020 at 2:14 PM Greg Grossmeier  wrote:

> Hello!
>
> The Wikimedia Foundation is soliciting your feedback to measure developer
> satisfaction and determine where to invest resources in the future. This is
> the second iteration of this survey.
>
> Topics covered include:
> * Local Development Environment
> * Beta Cluster / Staging Environment
> * Testing / CI
> * Code Review
> * Deployments
> * Production Systems
> * Development and Productivity Tools
> * Developer Documentation
>
> We are soliciting feedback from all Wikimedia developers, including Staff,
> 3rd party contributors and volunteer developers. *The survey will be open
> for a little over 2 weeks, closing on Friday March 6th.*
>
> This survey will be conducted via a third-party service, which may subject
> it to additional terms. For more information on privacy and data-handling,
> see the survey privacy statement
> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
>
> To participate in this survey, please start here:
>
> https://docs.google.com/forms/d/e/1FAIpQLSclq5vtaonRjwQykpfi2lbLIzJl-9wcOzmzXn4xnigd_DFlpw/viewform
>
> Thank you for your participation,
>
> Greg
>
> --
> | Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
> | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
>


-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikimedia Developer Satisfaction Survey

[Greg Grossmeier]

Hello!

The Wikimedia Foundation is soliciting your feedback to measure developer
satisfaction and determine where to invest resources in the future. This is
the second iteration of this survey.

Topics covered include:
* Local Development Environment
* Beta Cluster / Staging Environment
* Testing / CI
* Code Review
* Deployments
* Production Systems
* Development and Productivity Tools
* Developer Documentation

We are soliciting feedback from all Wikimedia developers, including Staff,
3rd party contributors and volunteer developers. *The survey will be open
for a little over 2 weeks, closing on Friday March 6th.*

This survey will be conducted via a third-party service, which may subject
it to additional terms. For more information on privacy and data-handling,
see the survey privacy statement
https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement

To participate in this survey, please start here:
https://docs.google.com/forms/d/e/1FAIpQLSclq5vtaonRjwQykpfi2lbLIzJl-9wcOzmzXn4xnigd_DFlpw/viewform

Thank you for your participation,

Greg

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] 14 January 2020 security incident on Phabricator

[Greg Grossmeier]

Keeping this thread on-list to help others who might be unsure.

Hello Pine,

On Thu, Jan 16, 2020 at 4:23 PM Pine W  wrote:

> The way that I log into Phab is by using
> https://phabricator.wikimedia.org/auth/start/?next=%2F, and then logging
> into MediaWiki and authorizing Phab to access my credentials. The MediaWiki
> login including the 2FA is the same that I use for many other Wikimedia
> sites.
>

Correct, you are logging into your MediaWiki account with your 2FA token,
then you are logging into Phabricator via OAuth.

None of those logins nor 2FA tokens were affected by this.


> So, although this 2FA allows logins to Phabricator, it sounds like there is
> a separate 2FA for some people for Phabricator access, perhaps for people
> with LDAP logins, and that is the 2FA that is affected. Is this correct?
>

Correct. Phabricator has its own 2FA system for people to use.

You can see if you use it via your Account Settings, then clicking on
"Multi-Factor Auth". That is the 2FA that is affected in this incident.

Best,

Greg

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] 14 January 2020 security incident on Phabricator

[Greg Grossmeier]

On Thu, Jan 16, 2020 at 2:50 PM Pine W  wrote:

> Some of us use the same 2FA for Phabricator as for on wiki accounts. Should
> the 2FA reset apply to all Wikimedia 2FAs that could be used for
> Phabricator, or only those that actually have been used for Phabricator?
>

Hi Pine,

Phabricator has its own 2fa system that is separate from that of your wiki
account 2fa.

You may be using the same authenticator application on your phone, but
there are separate accounts/codes for your wiki account and for your
Phabricator account.

tl;dr: this only affects your Phabricator 2fa token, no other tokens.

Best,

Greg

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Scrum of scrums/2020-01-08

[Greg Grossmeier]

On Wed, Jan 8, 2020 at 9:27 AM RhinosF1 -  wrote:

> Is there any possible impact to tools etc with the kube reinistalising?
>

The k8s reinitializing callout is in reference to Wikimedia Production k8s,
not the WMCS k8s cluster. So, no :)

Best,

Greg

-- 
| Greg Grossmeier  GPG: B2FA 27B1 F7EB D327 6B8E |
| Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Startup module size and ResourceLoader registry overhead

[Greg Grossmeier]

On Thu, Sep 19, 2019 at 05:09:59PM +0200, Daniel Kinzler wrote:
> My friend @wetterfrosch points out on twitter that reducing our daily 
> bandwidth
> usage by 4.3TB reduces CO2 emission by 30 tons PER DAY. That's roughly
> equivalent to flying 20 people from Berlin to San Francisco and back. Every 
> day.

More events/conferences then, got it! :)

Congrats and thanks Performance and others!

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

Re: [Wikitech-l] DockerSIG: skipping this month's meeting and a call for topic suggestions

[Greg Grossmeier]

Hello again,

I am also skipping this month's meeting (tomorrow, Aug 22nd) due to lack of
topics. There is work on-going that Release Engineering would like to share
with everyone but we can wait until the next meeting or simply share out an
email/screencast before then.

Please do also respond to me here or privately or on IRC
(#wikimedia-pipeline) with any ideas (what you want others or yourself to
do) you might have for future meetings.

Thanks,

Greg

On Tue, Jul 23, 2019 at 6:14 PM Greg Grossmeier  wrote:

> Hello,
>
> The DockerSIG[0] meeting for this month is cancelled due to the agenda
> being empty. Future DockerSIG meetings are still planned.
>
> Please do email myself or reach out in other ways if you have something
> you'd like to add to the agenda for our next session; even if it's a
> request and not something you'd lead.
>
> Best,
>
> Greg
>
> [0] https://www.mediawiki.org/wiki/Docker/SIG
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |
>


-- 
Greg Grossmeier
Release Team Manager
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] DockerSIG: skipping this month's meeting and a call for topic suggestions

[Greg Grossmeier]

Hello,

The DockerSIG[0] meeting for this month is cancelled due to the agenda
being empty. Future DockerSIG meetings are still planned.

Please do email myself or reach out in other ways if you have something
you'd like to add to the agenda for our next session; even if it's a
request and not something you'd lead.

Best,

Greg

[0] https://www.mediawiki.org/wiki/Docker/SIG

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

Re: [Wikitech-l] Train

[Greg Grossmeier]

Hi RhinosF1,

On Thu, Jul 18, 2019 at 09:21:05PM +0100, RhinosF1 Wikipedia wrote:
> Hi,
> Am I mistaken that based on
> https://phabricator.wikimedia.org/T220739 the train should be fully rolled
> back?

You are probably reading the commit message of: Revert "all wikis to
1.34.0-wmf.14", correct?

What that is saying, if you look at the actual diff, is that we reverted
the last group of wikis to go to wmf.14 ("group2"). Group2 is basically
~"the wikipedias". You can see more about it, the groupings, etc here:
https://wikitech.wikimedia.org/wiki/Deployments/One_week

For the avoidance of doubt: wmf.14 is on group0 and group1, but not
group2, due to some blockers. See Lars' email about that (subject:
"1.34.0-wmf.14 status update").

> https://noc.wikimedia.org/conf/highlight.php?file=wikiversions.json seems
> to show otherwise.

A handy tool (thanks Bryan!) to more easily see where we are with the
weekly train is: https://tools.wmflabs.org/versions/

Hope that helps,

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

Re: [Wikitech-l] Changes and improvements to PHPUnit testing in MediaWiki

[Greg Grossmeier]

This is great work Kosta and Amir (and everyone else!).

Thank you for taking this on and helping improve the health of our
testing practices.

Greg

On Tue, Jul 16, 2019 at 04:28:06PM -0400, Kosta Harlan wrote:
> Hi all,
> 
> Please have a look at 
> https://phabricator.wikimedia.org/phame/post/view/169/changes_and_improvements_to_phpunit_testing_in_mediawiki/
>  
> <https://phabricator.wikimedia.org/phame/post/view/169/changes_and_improvements_to_phpunit_testing_in_mediawiki/>
>  regarding some significant changes and improvements to the PHP testing tools 
> included with MediaWiki.
> 
> Your feedback and contributions are most welcome, either here, on phab, or on 
> IRC (Amir1 and kostajh in #wikimedia-codehealth). One of us should be around 
> during the technical advice IRC meeting tomorrow as well if you have 
> questions about how to port your tests, run Amir’s script, or have 
> suggestions / feedback.
> 
> Sincerely,
> 
> Kosta & Amir
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

Re: [Wikitech-l] Updates to the Centralized Logging Pipeline

[Greg Grossmeier]

Thanks Cole et al,

On Mon, Jul 01, 2019 at 04:17:59PM -0600, Cole White wrote:
> Please let Filippo, Keith, or myself know if you have any questions.

Is there a deprecation and removal timeline?

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

Re: [Wikitech-l] Patchsets by new Gerrit contributors waiting for code review and/or merge

[Greg Grossmeier]

Hi,

On Fri, Jun 21, 2019 at 11:51:10AM +0800, Sam Wilson wrote:
> Is that list meant to contain all extensions that are used on more than 400
> wikis? Because that looks to be 230 at the moment, going on WikiApiary
> numbers [1]. It seems like a hard list to keep up to date, and it doesn't
> add any info that's not already available elsewhere.

It is. For WMF teams the primary section to update is the
https://www.mediawiki.org/wiki/Developers/Maintainers#MediaWiki_extensions_deployed_on_the_Wikimedia_Cluster
section.

> I have a vague memory that there's some tool that reads
> [[Developers/Maintainers]] though, and (maybe?) adds reviewers on Gerrit
> based on it. Am I imagining that?

You're thinking of https://www.mediawiki.org/wiki/Git/Reviewers  :)


Best,

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] TechConf19 nominations - deadline extended until Thursday

[Greg Grossmeier]

The deadline extended until end of day Thursday June 20.

Final chance!

Greg

On Tue, Jun 11, 2019 at 10:00:26PM -0700, Greg Grossmeier wrote:
> Hello all,
> 
> Two things:
> 
> 1) On Thursday June 13th at 18:00 UTC (11am Pacific) there will be an
> open office hours for those of you who would like to share your thoughts
> on the event; topics you'd like to see discussed there, decisions you'd
> like made, etc.
> 
> It will occur using Google Meet, at this url:
> https://meet.google.com/exz-zxfy-nuj
> 
> If you can't make it to this office hours, don't fret! You can always
> (continue to) share your thoughts on the Phabricator task:
> https://phabricator.wikimedia.org/T220212
> 
> 
> 2) REMINDER: The deadline for participant/attendee nominations is Monday
> June 17th, this coming Monday. Remember, you can nominate others or
> yourself. And you can fill out the form as many times as you have
> nominations.
> 
> Form: https://forms.gle/CLeGFSMiEasJgEU27
> FAQ: https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/FAQ
> 
> This survey is conducted via a third-party service, which may make it
> subject to additional terms. For more information on privacy and
> data-handling, see this survey privacy statement:
> https://foundation.wikimedia.org/wiki/Wikimedia_Technical_Conference_Survey_Privacy_Statement
> 
> 
> On behalf of the Technical Conference Program Committee,
> 
> Greg
> 
> 
> On Wed, May 29, 2019 at 04:39:37PM -0700, Greg Grossmeier wrote:
> > Hello all,
> > 
> > As you may have seen, the next Wikimedia Technical Conference[0] is
> > coming up in November 2019.
> > 
> > It will take place November 12-15th in Atlanta, GA (USA). As announced
> > at the Hackathon and documented on-wiki[1] this year's event will
> > focus on the topic of "Developer Productivity".
> > 
> > Like last year, we are looking for diverse stakeholders, perspectives,
> > and experiences that will help us to make informed decisions. We need
> > people who can create and architect solutions, as well as those who
> > will make funding and prioritization decisions for the projects.
> > 
> > See the FAQ for (hopefully) any questions you have:
> > <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/FAQ>
> > 
> > Please fill out the survey using this link to nominate yourself or someone
> > else to attend: <https://forms.gle/CLeGFSMiEasJgEU27>
> > 
> > This survey is conducted via a third-party service, which may make it
> > subject to additional terms. For more information on privacy and
> > data-handling, see this survey privacy statement:
> > <https://foundation.wikimedia.org/wiki/Wikimedia_Technical_Conference_Survey_Privacy_Statement>
> > 
> > This nomination form will remain open between May 29 and June 17, 2018.
> > 
> > If you have any questions, please post them on the event's talk page
> > <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2019>.
> > 
> > Thanks!
> > 
> > Greg and the Technical Conference 2019 Program Committee
> > 
> > [0] <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>
> > [1] 
> > <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019#Vision_Statement>
> > 
> > -- 
> > Greg Grossmeier
> > Release Team Manager
> 
> -- 
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |

-- 
| 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] TechConf19: Nominations deadline (6/17) and office hours Thursday (6/13)

[Greg Grossmeier]

Hello all,

Two things:

1) On Thursday June 13th at 18:00 UTC (11am Pacific) there will be an
open office hours for those of you who would like to share your thoughts
on the event; topics you'd like to see discussed there, decisions you'd
like made, etc.

It will occur using Google Meet, at this url:
https://meet.google.com/exz-zxfy-nuj

If you can't make it to this office hours, don't fret! You can always
(continue to) share your thoughts on the Phabricator task:
https://phabricator.wikimedia.org/T220212


2) REMINDER: The deadline for participant/attendee nominations is Monday
June 17th, this coming Monday. Remember, you can nominate others or
yourself. And you can fill out the form as many times as you have
nominations.

Form: https://forms.gle/CLeGFSMiEasJgEU27
FAQ: https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/FAQ

This survey is conducted via a third-party service, which may make it
subject to additional terms. For more information on privacy and
data-handling, see this survey privacy statement:
https://foundation.wikimedia.org/wiki/Wikimedia_Technical_Conference_Survey_Privacy_Statement


On behalf of the Technical Conference Program Committee,

Greg


On Wed, May 29, 2019 at 04:39:37PM -0700, Greg Grossmeier wrote:
> Hello all,
> 
> As you may have seen, the next Wikimedia Technical Conference[0] is
> coming up in November 2019.
> 
> It will take place November 12-15th in Atlanta, GA (USA). As announced
> at the Hackathon and documented on-wiki[1] this year's event will
> focus on the topic of "Developer Productivity".
> 
> Like last year, we are looking for diverse stakeholders, perspectives,
> and experiences that will help us to make informed decisions. We need
> people who can create and architect solutions, as well as those who
> will make funding and prioritization decisions for the projects.
> 
> See the FAQ for (hopefully) any questions you have:
> <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/FAQ>
> 
> Please fill out the survey using this link to nominate yourself or someone
> else to attend: <https://forms.gle/CLeGFSMiEasJgEU27>
> 
> This survey is conducted via a third-party service, which may make it
> subject to additional terms. For more information on privacy and
> data-handling, see this survey privacy statement:
> <https://foundation.wikimedia.org/wiki/Wikimedia_Technical_Conference_Survey_Privacy_Statement>
> 
> This nomination form will remain open between May 29 and June 17, 2018.
> 
> If you have any questions, please post them on the event's talk page
> <https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2019>.
> 
> Thanks!
> 
> Greg and the Technical Conference 2019 Program Committee
> 
> [0] <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>
> [1] 
> <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019#Vision_Statement>
> 
> -- 
> Greg Grossmeier
> Release Team Manager

-- 
| 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] SWAT deploys - Release Engineering team members as backup deployers

[Greg Grossmeier]

Hello all,

If you watch the deployment calendar[0] closely you may have noticed a
change recently regarding the individuals listed next to each SWAT
deploy[1] window.

The short version:
* We have removed all Release Engineering team members names from the
  list of SWAT deployers.
* Release Engineering team members are still around and available on an
  as needed/backup basis.
* Release Engineering team members are still around to respond to any
  issues that arise, of course.
* Also, Release Engineering would love to train more individuals on any
  engineering team to self-serve their own SWAT deploys. Please contact
  me if you'd like to explore next steps.

This is a relatively minor change to reflect the growing reality of how
SWAT deploy windows happen now.

I would also like to take this opportunity to thank all of our current
and past SWAT deployers; thank you for helping get fixes out to our
users quickly and safely.

Best,

Greg


[0] https://wikitech.wikimedia.org/wiki/Deployments
[1] https://wikitech.wikimedia.org/wiki/SWAT_deploys

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Technical Conference 2019 - Call for participant nominations

[Greg Grossmeier]

Hello all,

As you may have seen, the next Wikimedia Technical Conference[0] is
coming up in November 2019.

It will take place November 12-15th in Atlanta, GA (USA). As announced
at the Hackathon and documented on-wiki[1] this year's event will
focus on the topic of "Developer Productivity".

Like last year, we are looking for diverse stakeholders, perspectives,
and experiences that will help us to make informed decisions. We need
people who can create and architect solutions, as well as those who
will make funding and prioritization decisions for the projects.

See the FAQ for (hopefully) any questions you have:
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/FAQ>

Please fill out the survey using this link to nominate yourself or someone
else to attend: <https://forms.gle/CLeGFSMiEasJgEU27>

This survey is conducted via a third-party service, which may make it
subject to additional terms. For more information on privacy and
data-handling, see this survey privacy statement:
<https://foundation.wikimedia.org/wiki/Wikimedia_Technical_Conference_Survey_Privacy_Statement>

This nomination form will remain open between May 29 and June 17, 2018.

If you have any questions, please post them on the event's talk page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2019>.

Thanks!

Greg and the Technical Conference 2019 Program Committee

[0] <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>
[1] 
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019#Vision_Statement>

-- 
Greg Grossmeier
Release Team Manager

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

Re: [Wikitech-l] Introducing the codehealth pipeline beta

[Greg Grossmeier]

Thanks for pushing this forward, Kosta. I'm really excited for this work
and how it will help us all improve the quality of the code we write.

I definitely encourage others to check this out and leave feedback!

Greg

On Wed, May 15, 2019 at 8:38 PM Kosta Harlan  wrote:

> Hi,
>
> I’ve written a post about the codehealth pipeline in Wikimedia CI, which
> the code health metrics group has been working on over the last few weeks
> and months:
>
>
> https://phabricator.wikimedia.org/phame/post/view/160/introducing_the_codehealth_pipeline_beta/
>
> Your feedback and contributions are very welcome!
>
> Kosta
> --
> --
> Kosta Harlan (he/him/his)
> Sr Software Engineer
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Greg Grossmeier
Release Team Manager
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MediaWiki 1.33 branch announcement

[Greg Grossmeier]

Hello!

We are beginning the process of working on the 1.33.0 release of
MediaWiki. The release is currently scheduled for May 2019.

We created the REL1_33 branch this week (aligned with the final
Wikimedia alpha, 1.33.0-wmf.25), and will be generating the first
release candidate soon, so this means it's now "pencils down".

If you have any open Phabricator tasks tagged with mw-1.33-release
[0], please check to see if they are indeed blockers for the release.
If not, please remove the tag from them. Conversely, if there are any
blockers that are not tagged with mw-1.33.release, please tag them.
Please feel free to reach out to me if you have any questions about
this.

We will be in the normal patch master + backport process from now
until the release in May.

Thanks,

Greg

[0] https://phabricator.wikimedia.org/tag/mw-1.33-release/

-- 
Greg Grossmeier
Release Team Manager

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

Re: [Wikitech-l] Uploading new versions of other people's patches to gerrit

[Greg Grossmeier]

On Tue, Apr 9, 2019 at 10:38 AM Isarra Yos  wrote:
> Hi. I'm trying to think of a way to put this politely, but I can't, so:
> this is insane.

Please try to remain civil and polite, even when things aren't as you want.

We (Release Engineering, the Security team, and SRE) are all trying to
make the situation better for everyone. Right now we can't undo this.
We hope to have a better solution (opening the right up more than it
is now) soon pending other in-progress work (as Tyler said).

I request your patience as we work through this.

PS: I just saw your follow-up reply. Sadly Gerrit is not mediawiki ;)
so it doesn't have all of the other built in anti-abuse features that
comes with the nice user features.

-- 
Greg Grossmeier
Release Team Manager

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

Re: [Wikitech-l] [Train] 1.33.0-wmf.18 status update

[Greg Grossmeier]

> In addition to those, I'm not sure whether we should be pushing out a
> new train while beta cluster is unusable (locked in read-only mode):
> <https://phabricator.wikimedia.org/T216404>.

It is incredibly unfortunate that the Beta Cluster is down due to the
corruption fallout.

However, given that the new train is now already on group0 and the only
new issue we've seen thus far is
https://phabricator.wikimedia.org/T216561 (with patch merged and ready
for backport) I'm inclined to continue the train while being (as always)
vigilant.

The cost/benefit of skipping a train is also not great; the added
complexity of another week's wroth of changes going out increases our
risk.

Thanks for bringing it up,

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] Announcing the Docker Special Interest Group

[Greg Grossmeier]

Hello,

At this year's WMF All Hands there was an unconference session about
MediaWiki and Docker; what people currently are doing/using and what
plans are for the future.

One of the identified needs during the session was a single forum for
those working with this tooling to collaborate more efficiently. To that
end it was proposed to create a Special Interest Group[0] (a "SIG").

I'd like to announce that we now have the basics of such a group:
* Wiki: https://www.mediawiki.org/wiki/Docker/SIG
* Mailing list: https://lists.wikimedia.org/mailman/listinfo/docker-sig
* IRC: #wikimedia-pipeline (reusing an already in use topical channel
  for efficiency)

Please join!

I will be setting up a first meeting Soon (TM) and will announce on the
SIG's mailing list (and probably cross-post it here the first time).

Best,

Greg

[0] https://www.mediawiki.org/wiki/Special_Interest_Groups

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Beta Cluster and CI issues (was Fwd: [Cloud] [Cloud-announce] VPS hardware failure -- downtime ongoing)

[Greg Grossmeier]

This WMCS outage is affecting Beta Cluster (aka: deployment-pre VPS
project) and our CI build/test servers (aka: the integration project).

Apologies for any downtime and/or slow CI responses while this is being
sorted.

Greg

- Forwarded message from Andrew Bogott  -

> Date: Wed, 13 Feb 2019 07:25:39 -0600
> From: Andrew Bogott 
> To: cloud-annou...@lists.wikimedia.org
> Subject: [Cloud] [Cloud-announce] VPS hardware failure -- downtime ongoing
> Reply-To: cl...@lists.wikimedia.org
> 
> We're currently experiencing a mysterious hareware failure in our datacenter
> -- three different SSDs failed overnight, two of them in cloudvirt1018 and
> one of them in cloudvirt1024.  The VMs on 1018 are down entirely.  We may
> move those on 1024 to another host shortly in order to guard against
> additional drive failure.
> 
> There's some possibility that we will experience permanent data loss on
> cloudvirt1018, but everyone is working hard to avoid this.
> 
> The following VMs are on cloudvirt1018:
> 
> 
> a11y | reading-web-staging
> abogott-scapserver   | testlabs
> af-puppetdb01    | automation-framework
> api  | openocr
> asdf | quotatest
> bastion-eqiad1-02    | bastion
> clm-test-01  | community-labs-monitoring
> compiler1002 | puppet-diffs
> cyberbot-exec-iabot-01   | cyberbot
> deployment-db03  | deployment-prep
> deployment-db04  | deployment-prep
> deployment-memc05    | deployment-prep
> deployment-pdfrender02   | deployment-prep
> deployment-sca01 | deployment-prep
> design-lsg3  | design
> eventmetrics-dev01   | eventmetrics
> fridolin | catgraph
> gtirloni-puppetmaster-01 | testlabs
> hadoop-master-3  | analytics
> ign  | ign2commons
> integration-castor03 | integration
> integration-slave-docker-1017    | integration
> integration-slave-docker-1033    | integration
> integration-slave-docker-1038    | integration
> integration-slave-jessie-1003    | integration
> integration-slave-jessie-android | integration
> k8s-master-01    | general-k8s
> k8s-node-03  | general-k8s
> k8s-node-05  | general-k8s
> k8s-node-06  | general-k8s
> kdc  | analytics
> labstash-jessie1 | logging
> language-mleb-legacy | language
> login-test   | catgraph
> lsg-01   | design
> mathosphere  | math
> mc-clusterA-1    | test-twemproxy
> mwoffliner5  | mwoffliner
> novaadminmadethis-4  | quotatest
> ntp-01   | cloudinfra
> ntp-02   | cloudinfra
> ogvjs-testing    | ogvjs-integration
> phragile-pro | phragile
> planet-hotdog    | planet
> pub2 | wikiapiary
> puppenmeister    | planet
> puppet-compiler-v4-other | testlabs
> puppet-compiler-v4-tools | testlabs
> quarry-beta-01   | quarry
> signwriting-swis | signwriting
> signwriting-swserver | signwriting
> social-tools3    | social-tools
> striker-deploy04 | striker
> striker-puppet01 | striker
> t166878  | otrs
> togetherjs   | visualeditor
> tools-sgebastion-06  | tools
> tools-sgeexec-0902   | tools
> tools-sgeexec-0903   | tools
> tools-sgewebgrid-generic-0901    | tools
> tools-sgewebgrid-lighttpd-0901   | tools
> ve-font  | design
> wikibase1    | sciencesource
> wikicitevis-prod | wikicitevis
> wikifarm | pluggableauth
> women-in-red | globaleducation
> 
> 
> 
> ___
> Wikimedia Cloud Services announce mailing list
> cloud-annou...@lists.wikimedia.org (formerly 
> labs-annou...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud-announce
> ___
> Wikimedia Cloud Services mailing list
> cl...@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud

- End forwarded message -

-- 
| 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] Gerrit now automatically adds reviewers

[Greg Grossmeier]

Hello,

Yesterday we (the Release Engineering team) enabled a Gerrit plugin that
will automatically add reviewers to your changes based on who previously
has committed changes to the file.

For more, please read the blog post at:
https://phabricator.wikimedia.org/phame/post/view/139/gerrit_now_automatically_adds_reviewers/

NOTE: There are a couple requests from us open upstream to improve the
plugin[0], we'll incorporate those improvements when they are released.

On behalf of the rest of the Release Engineering Team[1],

Greg

[0] https://phabricator.wikimedia.org/T101131#4890023
[1] As well as Paladox, a Wikimedia volunteer with strong ties to
upstream Gerrit.

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

Re: [Wikitech-l] [Engineering] Announcing Wikimedia Release Engineering's 1st Annual Developer Satisfaction Survey

[Greg Grossmeier]

You have one more week!

The survey was going to be closed last week, but with the short US work
week this week we have extended the deadline to Monday Nov 26th.

Greg


> This survey will help the Release Engineering team measure developer
> satisfaction and determine where to invest resources. The topics covered
> will include the following:
> 
> * Local Development Environment
> * Beta Cluster / Staging Environment
> * Testing / CI
> * Code Review
> * Deployments
> * Production Systems
> * Development and Productivity Tools
> * Developer Documentation
> * General Feedback
> 
> We are soliciting feedback from all Wikimedia developers, including Staff,
> 3rd party contributors and volunteer developers. The survey will be open
> for 2 weeks, closing on November 14th.
> 
> This survey will be conducted via a third-party service, which may subject
> it to additional terms. For more information on privacy and data-handling,
> see the survey privacy statement
> https://foundation.wikimedia.org/wiki/Developer_Satisfaction_Survey_Privacy_Statement
> 
> To participate in this survey, please start here:
> https://docs.google.com/forms/d/e/1FAIpQLSfXGpjUIO3ARqxPHOYPwI2Dw-jEg1xMeLi_HpZ_HcU-_i_Arw/viewform

> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering


-- 
| 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] Status of translation updates (was Re: Translations on hold until further notice)

[Greg Grossmeier]

Hello,

Thank you for bearing with us while translation updates were stopped.

We are now updating translations for Wikimedia sites with the weekly
MediaWiki train based on the updates that are being provided by
translatewiki.net. Feel free to add new translatable strings now.

However, during the investigation of the instigating security incident
we identified architectural issues with the systems and processes that
make up the nightly localization updates. This update process is
currently disabled and will remain disabled until there is a clear plan
and resourcing for improving the architecture. The task tracking this
discussion is at https://phabricator.wikimedia.org/T206694 .

In the mean time new translations will go out with the weekly MediaWiki
train.

Thank you for your continued understanding,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] MediaWiki 1.32 branch announcement

[Greg Grossmeier]

Greetings!

We are beginning the process of working on the 1.32 release of
MediaWiki. The release is currently scheduled for Nov. We plan to create
the REL1_32 branch on October 16 and to generate the first release
candidate, so we will be requesting "pencils down" on October 15.

In the meantime, if you have any open Phabricator tasks tagged with
mw-1.32-release [0], please check to see if they are indeed blockers for
the release. If not, please remove the mw-1.32-release tag from them.
Conversely, if there are any blockers that are not tagged with
mw-1.32.release, please tag them. Please feel free to reach out to me if
you have any questions about this.

We will be in the normal patch master + backport process from October 16
until the release in Nov.

Thanks,

Greg

[0] https://phabricator.wikimedia.org/tag/mw-1.32-release/

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Translations on hold until further notice

[Greg Grossmeier]

tl;dr: Please refrain from adding new strings that require translations
to MediaWiki and deployed extensions until further notice.

Due to changes we are making in the way our translation systems process
data we will be temporarily disabling the auto deployment of newly
translated content until further notice.  The goal of these changes will
be to improve the evaluation of content submitted to our translation
services.

This means developers should not merge new translatable strings into
MediaWiki Core nor Wikimedia deployed extensions until we re-enable the
system. This is to prevent longer term issues where local wiki admins
overwrite a string and thus prevent updates from new and improved
translations. 

We apologize for any inconvenience this delay in service may cause and
will alert you as soon as this maintenance is completed. 

Greg Grossmeier

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] [Wmfall] Datacenter Switchover recap

[Greg Grossmeier]

> Hello all,
> 
> Today we've successfully migrated our wikis (MediaWiki and associated
> services)
> from our primary data center (eqiad) to our secondary (codfw)

Well done, all.

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

Re: [Wikitech-l] [Ops] [Engineering] MW Train status: Incomplete rollout, blocked on two issues

[Greg Grossmeier]

> Deployments during the week of wikimania are always tough.  I'm surprised
> we even tried to do that this year.

There is/was sufficient coverage from both RelEng and SRE so there
wasn't an issue of site outage without available people to respond. IOW,
no one from RelEng nor SRE was attending Wikimania (sadly).

There is the issue of not getting quick feedback and resolution on UBN!
bugs from attendees at the conference, though. (This was obviously
dependent on who was at the conference and only manifested itself in a
couple cases.)

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] MW Train status: Incomplete rollout, blocked on two issues

[Greg Grossmeier]

Hello,

The 1.32.0-wmf.13 version of MediaWiki is rollout to almost all group0
and group1 wikis, but not group2. In plain wording: It is deployed to
all non-wikipedias (Commons, wiktionaries, etc) except Wikidata.

It was blocked from going to all wikis yesterday due to two issues found
during the week:
* Fatal MWException in Babel: "Language::isValidBuiltInCode must be
  passed a string" - https://phabricator.wikimedia.org/T199941

* Wikidata showing wrong language for page elements -
  https://phabricator.wikimedia.org/T199983

Assuming these issues are resolved before Monday we hope to resume the
deployment of this version Monday during European working hours.

The tracking task for this deployment:
https://phabricator.wikimedia.org/T191059

A handy tool to see which wikis have which version:
https://tools.wmflabs.org/versions/

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] [Ops] [Engineering] Additional European-appropriate MediaWiki train window starting week of July 9th (also SWAT change)

[Greg Grossmeier]

> I believe that pinning them to UTC would actually eliminate the confusion.

Two thoughts...

1) If we do this let's do this for all European-focused windows.

That would be the European mid-day SWAT window and the Train window, to
start (there are some other one-off type windows, eg the Portals window,
that would probably also make sense to be pinned to non-SF time, but
it's up to those individuals/teams).

2) I believe it makes more sense to pin the windows to the human
experience time of those who are responsible for doing the window (eg:
follows DST/Summer time in Europe). That way the deployment windows
continue to stay at the same time relative to people's other meetings
(which, some are coordinated with the various deploy (SWAT and Train)
windows). That's what we do for all of the rest of the windows (pinned
to Pacific/SF time, which changes based on DST) and would then be less
of a surprise for everyone.

Based on this map[0] it appears the vast majority of our contributors
and deployers live in DST-affected (inflicted? infected? ;-) )
countries.


Greg

[0] 
https://en.wikipedia.org/wiki/Daylight_saving_time_by_country#/media/File:DST_Countries_Map.png

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

Re: [Wikitech-l] [Engineering] Additional European-appropriate MediaWiki train window starting week of July 9th (also SWAT change)

[Greg Grossmeier]

> One question/clarification, though: deployment windows have traditionally
> been pinned to SF time (wrt DST changes, concretely), but in your email you
> list them in CEST/UTC. Does that imply that these slots are pinned to
> Europe's DST, UTC or will they stay pinned to pacific DST?

Great question! (Unfortunately) for simplicity we will keep the windows
pinned to SF/Pacific timezone. Some windows moving and others not would
create too much confusion; even more than the normal daylight savings
changes already do.

Thanks,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Additional European-appropriate MediaWiki train window starting week of July 9th (also SWAT change)

[Greg Grossmeier]

Reminder that this is starting this week (tomorrow).


> Hello,
> 
> The Release Engineering team will be expanding the set of people
> responsible for the weekly MediaWiki train deployments[0] to include
> people working normal European hours. Unfortunately, the current MW
> train deployment window is too late in the day for them.
> 
> To address this we are adding a European-focused timeslot for the MW
> train (and moving the current "EU SWAT window" 2 hours earlier to
> accommodate).
> 
> The first planned use of the new window will be next week, the week of
> July 9th.
> 
> For the avoidance of doubt: the normal MW train windows will not go
> away, these EU-timezone ones are in addition to them and only used
> during weeks that the train is conducted by someone in Europe. But, the
> EU SWAT window will indeed be permanently moved for simplicity (IOW: not
> dependent upon who's doing the train).
> 
> == European train window and changes ==
> This would affect Tuesday, Wednesday, and Thursday
> 
> * 1300-1400 CEST (1100-1200 UTC) - EU SWAT window (2 hours earlier)
> * 1400-1500 CEST (1200-1300 UTC) - Break
> * 1500-1700 CEST (1300-1500 UTC) - EU Train window
> * 1700-1800 CEST (1500-1600 UTC) - Break
> * 1800-1900 CEST (1600-1700 UTC) - PuppetSWAT (Tue/Thu only, no change)
> 
> 
> Also, at the same time we'll be moving the Wednesday morning (SF time)
> SWAT window on hour earlier to 9am Pacific. This is to alleviate a
> contention with the weekly Scrum of Scrums meeting.
> 
> Best,
> 
> Greg
> 
> [0] https://www.mediawiki.org/wiki/MediaWiki_1.32/Roadmap
> 
> -- 
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |



-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Additional European-appropriate MediaWiki train window starting week of July 9th (also SWAT change)

[Greg Grossmeier]

Hello,

The Release Engineering team will be expanding the set of people
responsible for the weekly MediaWiki train deployments[0] to include
people working normal European hours. Unfortunately, the current MW
train deployment window is too late in the day for them.

To address this we are adding a European-focused timeslot for the MW
train (and moving the current "EU SWAT window" 2 hours earlier to
accommodate).

The first planned use of the new window will be next week, the week of
July 9th.

For the avoidance of doubt: the normal MW train windows will not go
away, these EU-timezone ones are in addition to them and only used
during weeks that the train is conducted by someone in Europe. But, the
EU SWAT window will indeed be permanently moved for simplicity (IOW: not
dependent upon who's doing the train).

== European train window and changes ==
This would affect Tuesday, Wednesday, and Thursday

* 1300-1400 CEST (1100-1200 UTC) - EU SWAT window (2 hours earlier)
* 1400-1500 CEST (1200-1300 UTC) - Break
* 1500-1700 CEST (1300-1500 UTC) - EU Train window
* 1700-1800 CEST (1500-1600 UTC) - Break
* 1800-1900 CEST (1600-1700 UTC) - PuppetSWAT (Tue/Thu only, no change)


Also, at the same time we'll be moving the Wednesday morning (SF time)
SWAT window on hour earlier to 9am Pacific. This is to alleviate a
contention with the weekly Scrum of Scrums meeting.

Best,

Greg

[0] https://www.mediawiki.org/wiki/MediaWiki_1.32/Roadmap

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Phabricator spam - account approval requirement enabled

[Greg Grossmeier]

Hello,

Unfortunately we are experiencing spam in our Phabricator instance
again and have decided to turn on the requirement for new account
approval by Phabricator admins as a mitigation step.

I'm sorry for the inconvenience. We are actively working to address this
issue.

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Clarification Re: [nominations needed] Wikimedia Technical Conference

[Greg Grossmeier]

Hello,

The Wikimedia Technical Conference Program Committee wanted to send a
clarifying note regarding the nomination process.

Initially we said that relevant budget owners will be invited directly
by us and thus *do not need to be explicitly nominated*. This is still
half true.

We will be directly inviting many budget owners BUT please do nominate
those budget owners that you believe should be in attendance (including
yourself, if applicable). Do this even if you believe we will already
select them. There's no harm in nominating someone.

I have updated the FAQ accordingly[0].

Please post any questions on the talk page[1].

Thanks,

Greg

[0] 
https://www.mediawiki.org/w/index.php?title=Wikimedia_Technical_Conference%2F2018%2FFAQ=revision=2801232=2801090
[1] https://www.mediawiki.org/wiki/Talk:Wikimedia_Technical_Conference/2018

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

Re: [Wikitech-l] 2018-05-09 Scrum of Scrums meeting note

[Greg Grossmeier]

> == Callouts ==

Sorry we missed the meeting today, but, FYI that next week there will be
no change to MediaWiki "train" deployments nor SWAT deployments *even
though* we'll be at an offsite and the Hackathon (we have sufficient
coverage in RelEng and SRE for the week).


> *RelEng: Please review my patch!  https://gerrit.wikimedia.org/r/#/c/415886/
>  <3 -mdh (RI)

ack'd :)

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

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

[Greg Grossmeier]

> 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 ;)

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] Changes to SWAT deployment policies, effective Monday April 30th

[Greg Grossmeier]

Hello,

I have made two changes to SWAT policies today.

First, we now disallow multi-sync patch deployments. See T187761[0].
This means that the sync order of files is determined by git commit
parent relationships (or Gerrit's "depends-on"). This is to prevent SWAT
deployers from accidentally syncing two patches in the wrong order.

Second, we are reducing the number of allowed patches from 8 to 4. This
is to reduce stress on the SWAT deployer as well as set expectations for
requesters on the pace of the windows. See the approximate best case
time spent breakdown[1] for how we came to this number.

I've updated the on-wiki documentation on wikitech[2][3].


Thank you for flying scap,

Greg


[0] https://phabricator.wikimedia.org/T187761
[1] 
* +2/Wait for Jenkins to merge - 2 min
* prepare git on tin - 1 min
* Deploy to mwdebug - 1 min
* Verify on mwdebug - 3 min
* Deploy to production - 1 min
* Verify & wait/watch logs - 2 min
[2] 
https://wikitech.wikimedia.org/w/index.php?title=SWAT_deploys=prev=1789212
[3] 
https://wikitech.wikimedia.org/w/index.php?title=SWAT_deploys=next=1789212

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

Re: [Wikitech-l] MediaWiki train rolled back to wmf.26

[Greg Grossmeier]

This is still the case. Updates available on the relevant tasks.

We plan to resume the train (catch up) early next week.

Sorry for the inconvenience.

Greg


> The new MediaWiki weekly branch has some issues that are preventing us
> from deploying as planned.
> 
> The specific issue: https://phabricator.wikimedia.org/T190960
> 
> The tracking task for the train: https://phabricator.wikimedia.org/T183966
> 
> 
> Reminder that you can use the "Wikimedia MediaWiki versions"[0] tool on
> ToolForge to to know which wikis have which version at any time.
> 
> 
> Greg
> 
> [0] https://tools.wmflabs.org/versions/
> 
> -- 
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |



-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] MediaWiki train rolled back to wmf.26

[Greg Grossmeier]

The new MediaWiki weekly branch has some issues that are preventing us
from deploying as planned.

The specific issue: https://phabricator.wikimedia.org/T190960

The tracking task for the train: https://phabricator.wikimedia.org/T183966


Reminder that you can use the "Wikimedia MediaWiki versions"[0] tool on
ToolForge to to know which wikis have which version at any time.


Greg

[0] https://tools.wmflabs.org/versions/

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] CI interruption tomorrow (was Fwd: Brief service interruption tomorrow 2018-03-28 at 15:00 UTC)

[Greg Grossmeier]

FYI: tomorrow much of our CI tests will not run due to a planned
Wikimedia Cloud reboot.

Sorry for the inconvenience.

Greg

- Forwarded message from Andrew Bogott <abog...@wikimedia.org> -

> Date: Tue, 27 Mar 2018 09:34:55 -0500
> From: Andrew Bogott <abog...@wikimedia.org>
> To: cloud-annou...@lists.wikimedia.org
> Subject: [Cloud] [Cloud-announce] Brief service interruption tomorrow 
> 2018-03-28 at   15:00 UTC
> Reply-To: cl...@lists.wikimedia.org
> 
> About 24 hours from now we're going to reboot a couple of servers[1] in the
> cloud infrastructure to apply security updates.
> 
> Few WMCS users (and, in particular, no tools users) should notice any
> interruption.  Nonetheless, a few services will be down:
> 
> 
> - New instance creation will fail
> 
> - CI tests will stop running
> 
> - Horizon and Wikitech may display incorrect or missing information
> 
> 
> Apologies in advance for any inconvenience!
> 
> 
> -Andrew
> 
> 
> [1] labservices1001 and labcontrol1001
> 
> 
> ___
> Wikimedia Cloud Services announce mailing list
> cloud-annou...@lists.wikimedia.org (formerly 
> labs-annou...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud-announce
> ___
> Wikimedia Cloud Services mailing list
> cl...@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud

- End forwarded message -

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

Re: [Wikitech-l] [Proposal] Change terminology used for wikitech/LDAP/Toolforge/Labs accounts

[Greg Grossmeier]

> Quiddity closed the proposal as accepted today! I have been making
> edits on Wikitech to reflect the new "Wikimedia developer account"
> term.

\o/

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

Re: [Wikitech-l] You can now translate Phabricator to your language

[Greg Grossmeier]

> It's now possible to translate Phabricator in translatewiki.net thanks
> to the Phabricator developers, Mukunda Modell, and many others who
> participated in https://phabricator.wikimedia.org/T225

Thanks everyone who was involved with this long running task; really
happy to see it come to fruition.

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] No more SWAT deploys this week

[Greg Grossmeier]

Hello,

Due to both the SRE (nee Technical Operations) team traveling this week
combined with the Release Engineering team at an offsite we are
cancelling the remaining SWAT deploys this week.

For the most up to date and canonical version of the deployment calendar
please see, as always:
https://wikitech.wikimedia.org/wiki/Deployments

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] Code stewardship reviews, seeking feedback

[Greg Grossmeier]

Hello,

Some background:

The Sunsetting Working Group[0], which came out of a WMF Technology
manager's face-to-face after Wikimania and is made up of
cross-departmental members, was given the goal of determining how we
can reduce the set of un-, under-, or not clearly maintained code
running in Wikimedia production. To be clear, the goal was not to
"sunset" (aka: remove) all un-, under-, or not clearly maintained
code, but instead make an effort to resolve
'stewardship'/'ownership'/'maintainership' issues as best we can.

The process the working group devised is outlined on mediawiki.org[1].
In short it is: propose something to review, fill out the rubric, give
time for wider feedback, submit a prioritized list to the WMF Chief
Product and Chief Technology officers so they can make the hard
decisions of what to fund and how.

This is the first time we are doing this process and we are on an
abbreviated schedule with respect to the Foundation Annual Planning
timeline. We will be doing these quarterly on a known schedule (to be
published at a later date) to remove any future similar time schedule
stress.


The point of this email:

We have 4 reviews currently proposed[2]. They are:
* AbuseFilter (and dependencies)
* IRC RecentChanges feed
* RelatedSites extension
* TimedMediaHandler

We are soliciting wider feedback on wiki[3]. Please leave feedback on
the relevant talk page.[4][5][6][7]

Again, unfortunately our timeline is abbreviated this time around and we
will be closing the feedback on February 7th.

Thank you for your feedback!

Greg

[0] https://www.mediawiki.org/wiki/Sunsetting_Working_Group
[1] https://www.mediawiki.org/wiki/Code_stewardship_reviews#Process
[2] https://phabricator.wikimedia.org/project/board/3144/
[3] Subpages of 
https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitation
[4] 
https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solicitation/AbuseFilter
[5] 
https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solicitation/IRCRecentChanges
[6] 
https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solicitation/RelatedSites
[7] 
https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solicitation/TimedMediaHandler

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Wednesday morning SWAT moved 1 hour earlier

[Greg Grossmeier]

Hello,

A recent incident post-mortem improvement was to create a one hour
buffer between the last Service/SWAT deploys and the MediaWiki Train[0].

We addressed that on Tuesday already by removing the Morning SWAT window
(was at 11am Pacific).

Now we are addressing that on Wednesday by moving the Morning SWAT
window one hour earlier (to 10am Pacific). This is effective as of next
week (Jan 15th).

As always, please see the Deployments calendar[1] for the canonical
source of what is scheduled when.

Best,

Greg


[0] https://phabricator.wikimedia.org/T182733
[1] https://wikitech.wikimedia.org/wiki/Deployments

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] 1.31.0-wmf.16 MediaWiki train blocker - Rollback

[Greg Grossmeier]

> We just had to rollback 1.31.0-wmf.16 from group1 (eg: all
> non-wikipedias), so -wmf.16 is only on group0 at this time.
> 
> The issue is a data corruption bug[0]. The relevant people are aware.

Status update: The fix is merged into master (with a backport to wmf.16)
and thus on the Beta Cluster for testing. Given it is a Friday we will
attempt a continuation of the train on Monday (per policy[0]), to be
coordinated with Mukunda and/or Tyler (it's on the border of a train
conductor switch over) and Addshore.

Greg

[0] 
<https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train#What_happens_next?>

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] 1.31.0-wmf.16 MediaWiki train blocker - Rollback

[Greg Grossmeier]

We just had to rollback 1.31.0-wmf.16 from group1 (eg: all
non-wikipedias), so -wmf.16 is only on group0 at this time.

The issue is a data corruption bug[0]. The relevant people are aware.

Reminder that we have a task for each train rollout to track (potential)
blockers; the one for this week is [1]. You can follow that task to
track future progress.

Additional reminder that you can use the "Wikimedia MediaWiki
versions"[2] tool on Toolforge to know which wikis have which version at
any time.

Greg

[0] https://phabricator.wikimedia.org/T184749
[1] https://phabricator.wikimedia.org/T180749
[2] https://tools.wmflabs.org/versions/

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Announcing MediaWiki code search

[Greg Grossmeier]

> MediaWiki code search is a fully free software tool that lets you
> easily search through all of MediaWiki core, extensions, and skins
> that are hosted on Gerrit. You can limit your search to specific
> repositories, or types of repositories too. Regular expressions are
> supported in both the search string, and when filtering by path.
> 
> Try it out: https://codesearch.wmflabs.org/search/

This is really awesome, Kunal! Great work! Thanks for filling a gap for
us :)

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

Re: [Wikitech-l] 2017-12-20 Scrum of Scrums meeting notes

[Greg Grossmeier]

Sorry! We failed to put in our updates in time:


> https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-12-20
> 
> === Release Engineering ===
* Blocking
** 
* Blocked
** Teams that did not port Selenium tests from Ruby to Node.js
(T139740): No team (1), Editing (1), Fundraising Tech (1), Global
Collaboration (4), Multimedia (1), Reading Web (3), WMDE Engineering (5)
* Updates
** REMINDER: No deploys this week and next (18th and 25th). Take a
break! [wiki][email]
*** We’re (Chad) going to spend some time this week cleaning up
log-spam.
** Our Q3 goals posted
** Completed the security upgrade of RuboCop and Rubyzip
** Our Q2 “SSD” (Program 6) goals are now all complete [wiki][email]
** Antoine is migrating the CI docker image build process to using
docker-pkg (from Giuseppe)
** Follow-up continues on the ORES post-mortem follow-ups

-- 
| 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] Fwd: [Engineering] Wikimedia-log-errors summary - 2017-12-01

[Greg Grossmeier]

Forwarding as engineering@ is rarely used anymore.

Thanks Timo.

- Forwarded message from Timo Tijhof <ttij...@wikimedia.org> -

> Date: Fri, 1 Dec 2017 18:42:26 -0800
> From: Timo Tijhof <ttij...@wikimedia.org>
> To: Engineering <engineer...@lists.wikimedia.org>
> Subject: [Engineering] Wikimedia-log-errors summary - 2017-12-01
> 
> Been a while since the last summary, so here is one.
> 
> * 168 reported unresolved issues
> * 160 issues without an assignee
> * 10 issues tagged with "Patch-For-Review"
> 
> Please check out the breakdown of open issues by project to see which
> errors in your field welcome fixing:
> <https://phabricator.wikimedia.org/maniphest/query/OunXBb3QsLmc/#R>
> 
> Or get the latest straight from Logstash:
> <https://logstash.wikimedia.org/app/kibana#/dashboard/mediawiki-errors>
> 
> Top 5 by hit count in last 24 hours:
> 
> 1. ERROR channel=PageViewInfo "Failed fetching {url}: {error}"
> 
>#PageViewInfo
>https://phabricator.wikimedia.org/T181011
> 
> 2. ERROR channel=error "Fatal error: Call to exists() on a non-object"
> 
>#ProofreadPage
>https://phabricator.wikimedia.org/T181868
> 
> 3. WARNING channel=XMP "XMPReader::parse .. "
> 
>#Multimedia #MediaWiki-File-management
>https://phabricator.wikimedia.org/T118799
> 
> 4. WARNING channel=session "Metadata merge failed: {exception}"
> 
>#MediaWiki-Authentication #CentralAuth
>https://phabricator.wikimedia.org/T158365
> 
> 5. WARNING channel=session "Metadata has an anonymous user, but a non-anon"
> 
>#MediaWiki-Authentication #CentralAuth
>https://phabricator.wikimedia.org/T181869
> 
> -- Timo

> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering


- End forwarded message -

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

Re: [Wikitech-l] MediaWiki train for 1.31.0-wmf.8 is on hold due to a database failure

[Greg Grossmeier]

> There was a badly timed database failure today that has caused all
> deployments to be on hold until the situation is resolved.

The database incident[0] is resolved and we will resume the MW train on
this coming Monday to catch up.

Best,

Greg

[0] 
https://wikitech.wikimedia.org/wiki/Incident_documentation/20171116-s5-dewiki-wikidata

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] MediaWiki train for 1.31.0-wmf.8 is on hold due to a database failure

[Greg Grossmeier]

Hello,

There was a badly timed database failure today that has caused all
deployments to be on hold until the situation is resolved.

See: https://phabricator.wikimedia.org/T180714 "db1063 crashed"

The MW Train blocker task, https://phabricator.wikimedia.org/T178635,
will be updated when we move forward.

Sorry for the inconvenience,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Upcoming holidays/events and their impact on the deployment schedule

[Greg Grossmeier]

Reminder as we approach Thanksgiving in the US in a couple weeks:


> Hello all,
> 
> It's that time of year again where the density of holidays increases and
> at the same time our plans for fundraising also increase.
> 
> Per our usual practice we will be not doing deployments at various
> points in the next few months. Here's the full outline:
> 
> Reminder for all on we did last year:
> * No MW train the week of Thanksgiving (but SWAT deploys were open for
>   high-priority things).
> * No deploys (at all) the last two weeks of December. People were happy
>   with this.
> * The first week of January was normal (minus Monday being Jan 2nd, our
>   observed New Year's Day holiday) deployment wise.
> * The second week was weird due to Dev Summit/All Hands: No MediaWiki
>   train, only SWATs as needed on Mon/Tues/Wed. No SWATs/deploys during
>   All Hands.
> 
> I imagine we'll do similarly. In that case (looking at the calendar)
> 
> * No MW train the week of Thanksgiving (Nov 20th), SWATs open for high
>   priority things
> * No deploys weeks of Dec 18th and 25th (last two weeks)
> * Normal week week of Jan 1st (minus no deploys that Monday)
> * The Dev Summit and WMF All Hands is the week of January 22nd, so that
>   will be a "No Train but SWATs OK on Mon/Tues/Wed" week.
> * The following week (week of January 29th) the Release Engineering team
>   will be on an offsite, so a week of "No Train, but SWATs and service
>   deploys OK".
> 
> This is now on-wiki at:
> https://wikitech.wikimedia.org/wiki/Deployments#Upcoming
> 
> Best,
> 
> Greg
> 
> -- 
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |



-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Migrating away from nose (was 2017-11-01 Scrum of Scrums meeting notes)

[Greg Grossmeier]

(adding in qa@ list)


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> On 11/01/2017 10:53 AM, Grace Gellerman wrote:
> > === Scoring Platform === ** Converted our tests from nosetests to
> > pytest (Anyone else making the transition?) *** nosetests is
> > under-maintained *** python community is moving towards pytest ***
> > converting our repos was pretty straightforward
> 
> I didn't realize nose was in such a state :( They put a notice[1] on
> their website, but I always skipped it.
> 
> pytest[2] claims that it's compatible with nose out of the box - was
> that the experience you had as well?
> 
> Off the top of my head, Pywikibot, CI, and other miscellaneous
> projects all use nose and should probably be migrated over to pytest.
> 
> [1] https://nose.readthedocs.io/en/latest/#note-to-users
> [2] https://docs.pytest.org/en/latest/
> 
> - -- Legoktm
> -BEGIN PGP SIGNATURE-
> 
> iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAln6D0gXHGxlZ29rdG1A
> bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KKbMw/+Nh/tGRagrvZgJqHBZakvvAYE
> IHCUFPTUhfQ4cQ++oUqDpblAxR/FNO6BN2UQIrIh9gUylHCf/hwZ3BToC5GGPFY5
> D9Sgi/ce9v5dp3IIvNZq/NZgb0DkityVkxWg8tiZJPwhJ6hTKw9LjaPl++ee9Po/
> 940WYy7UQ7L/xwgy7rNJrViW0j4VD4mM7+PVvxPuv6rovOpa/H0VMbSlEuoXQYFG
> P2DPJE1f8B9tn/xun6O6tveWdD7cdna2DVCXhFF+Tldnpa+XtOerE3P+YBA8Gp/+
> sRJZuDjbCljM0GCzYYVR00klp8xDFQJXn+ELWaE1E3pAitZQdjb1A+xPmxagk1Up
> ysqSc9nndVm6c59lkzdMcqz1myWyzLVho/RBmRVAAm37Wv7F7tvxHufuwWe8QO/I
> sUJsRXkH7/TdsSzs8TU9YTZECE5QntTOM7gGgP4jPQgiwZrHob9si1jDUaQMuFoC
> i8U9dylhrh280VAJj9LRaoRaSb48Ln6sZrCMdpCW8gt4UiRsUcSYCXbD45AgUS9Z
> 3oPLMEpt+ESqDxJrBl9rgxyFZF19KhpeE3FPCvlAMZQShLZCAlRdDozczV4nFSHC
> zhRmuRITmnDomf8prk7NwFSM0q601kTOgVqVZiBn9AY3Axvsa1TS1HM582y4rJ8U
> O+eQbaSCyiI6HTE0lcc=
> =4lTI
> -END PGP SIGNATURE-
> 
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

-- 
| 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] Upcoming holidays/events and their impact on the deployment schedule

[Greg Grossmeier]

Hello all,

It's that time of year again where the density of holidays increases and
at the same time our plans for fundraising also increase.

Per our usual practice we will be not doing deployments at various
points in the next few months. Here's the full outline:

Reminder for all on we did last year:
* No MW train the week of Thanksgiving (but SWAT deploys were open for
  high-priority things).
* No deploys (at all) the last two weeks of December. People were happy
  with this.
* The first week of January was normal (minus Monday being Jan 2nd, our
  observed New Year's Day holiday) deployment wise.
* The second week was weird due to Dev Summit/All Hands: No MediaWiki
  train, only SWATs as needed on Mon/Tues/Wed. No SWATs/deploys during
  All Hands.

I imagine we'll do similarly. In that case (looking at the calendar)

* No MW train the week of Thanksgiving (Nov 20th), SWATs open for high
  priority things
* No deploys weeks of Dec 18th and 25th (last two weeks)
* Normal week week of Jan 1st (minus no deploys that Monday)
* The Dev Summit and WMF All Hands is the week of January 22nd, so that
  will be a "No Train but SWATs OK on Mon/Tues/Wed" week.
* The following week (week of January 29th) the Release Engineering team
  will be on an offsite, so a week of "No Train, but SWATs and service
  deploys OK".

This is now on-wiki at:
https://wikitech.wikimedia.org/wiki/Deployments#Upcoming

Best,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Technical Debt SIG...

[Greg Grossmeier]

Wikimedia as a whole as well.

--
Sent from my phone, please excuse brevity.

On Aug 17, 2017 6:48 PM, "Daniel Zahn"  wrote:

> > discussion regarding MediaWiki Technical Debt.
>
> Is it limited to MediaWiki or is it all Wikimedia Tech Debt?
>
> On Thu, Aug 17, 2017 at 2:11 PM, Jean-Rene Branaa 
> wrote:
>
> > Hello All,
> >
> > I'm reaching out to invite you to an ongoing discussion regarding
> MediaWiki
> > Technical Debt.  The topic of technical debt has been discussed in a
> number
> > of forums, and there's even been some work towards reducing it.
> >
> > This SIG's purpose is to get better alignment on what technical debt is,
> > how to approach reducing it, and what are things we can do to avoid it
> > moving forward.
> >
> > If you'd like to attend, please register here by August 22nd:
> >
> > https://goo.gl/forms/6sFWuBxfgGfwNUZ93
> >
> > I'm trying to get a sense of those that are interested in attending and
> > their timezone.  I look to schedule sessions that are timezone friendly.
> >
> > Thanks and look forward to some good discussion.
> >
> > Cheers,
> >
> > JR
> >
> > Jean-Rene Branaa (irc: jrbranaa)
> > RelEng Team
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> Daniel Zahn 
> Operations Engineer
> ___
> 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

[Wikitech-l] (Mostly) Normal deployment schedule next week during Wikimania

[Greg Grossmeier]

Hello all,

Next week is Wikimania (yay!), for those of you who weren't aware.

Due to having good non-Wikimania coverage in both Release Engineering
and Operations we will, however, be doing the normal MediaWiki train
that week along with SWAT and (if needed) service deploys.

Please don't merge risky things thinking that you have an extra week
to make them less risky.

Best,

Greg

-- 
Greg Grossmeier
Release Team Manager

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

Re: [Wikitech-l] [Engineering] MediaWiki 1.30.0-wmf.12 deployment is blocked

[Greg Grossmeier]

On Wed, Aug 2, 2017 at 1:33 PM, Mukunda Modell <mmod...@wikimedia.org> wrote:
> Due to today's train deployment more than doubling the error rate seen in
> fatalmonitor[1], I have rolled-back group 1 wikis to wmf.11. I've submitted
> an UBN task T172320 [2] detailing the error, which appears to be fallout
> from issues in Wikibase first noticed two weeks ago.

To answer questions regarding what issues will hold back the train and
what Release Engineering will do after we've made the decision to hold
the train see: https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train

Greg

-- 
Greg Grossmeier
Release Team Manager

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

[Wikitech-l] Change to version number incrementing for weekly Wikimedia MediaWiki deploys

[Greg Grossmeier]

Hello all,

I failed to send this notice out before when the change was made; mea
culpa.

Background:
* We start a new 1.XX-wmf.XX series after each MW 'tarball' release. For
  example right now we're in the 1.30-wmf.XX series now that 1.29 is
  nearing release.

The change:
* Instead of only incrementing the wmf.XX portion when a new branch is
  actually deployed to Wikimedia production servers, we will increment
  that number each week regardless.
** For example, last week we did not push a new branch out to production
   due to the short work week. That week would have been 1.30-wmf.8. We
   thus skipped wmf.8 and are now on wmf.9 this week.

Why?
We hope to make the creation of the weekly deployment branch
(1.XX-wmf.XX) automatic in the near future. This will allow us to put
that on a cron and not worry about special cases (another special case
being when we hold back the train due to a bad regression). This (every
week gets a wmf.XX number) should simplify logic in many places.

Thanks!

Greg on behalf of the Release Engineering team


PS: Yeah, we could have just gone with ISO week numbers, but we didn't
want to change too much in the version string to reduce the chance of
breaking too many other tools.
PPS: And yes, my failure to pre-announce this instead of post-announce
caused at least the ReleaseTaggerBot to break this week. Mea cupla.

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] MW 1.30-wmf.2 deployed to and reverted from group2 (all wikipedias) today

[Greg Grossmeier]

Investigation is still underway, but as of the end of Thursday wmf.2 is
only on group0 (testwikis) and group1 (non-'pedias). See the
tracking/blocker task at:
https://phabricator.wikimedia.org/T163512

The issue that caused the revert is being tracked at:
https://phabricator.wikimedia.org/T166345

You can track the status of the wmf.2 rollout via that tracking task
above or by watching https://tools.wmflabs.org/versions/

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Post-hackathon MediaWiki train deployment - Help us stay safe

[Greg Grossmeier]

We just completed another great Wikimedia Hackathon with a ton of great
work happening across many different areas and projects.

From a release engineering perspective this can also be a bit scary :).

The normal 'train' deployment is scheduled for this week starting
Tuesday May 23rd (per usual).

However, we request that due to the large variance of changes going out
this week please be on the alert and let us know if you see anything out
of the ordinary.

How? We (Release Engineering) have a tracking task per weekly deploy.
This week's is: https://phabricator.wikimedia.org/T163512

Comment on that task or add a subtask to it to indicate a blocker. We'll
respond accordingly. As you can see there's also a number of blockers
being tracked.

Thank you,

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] Fwd: [QA] Ruby tests updated to Selenium 3

[Greg Grossmeier]

FYI

- Forwarded message from Željko Filipin <zfili...@wikimedia.org> -

> Date: Fri, 10 Mar 2017 15:22:33 +0100
> From: Željko Filipin <zfili...@wikimedia.org>
> To: "Software quality assurance for Wikimedia projects." 
> <q...@lists.wikimedia.org>
> Subject: [QA] Ruby tests updated to Selenium 3
> Reply-To: "QA for Wikimedia projects." <q...@lists.wikimedia.org>
> 
> The majority of migration was without problems. Three repositories still
> need to be updated because some tests are failing: MobileFrontend,
> RelatedArticles, Wikibase.
> 
> This task has all details:
> 
> https://phabricator.wikimedia.org/T158074
> 
> mediawiki_selenium 1.8.0 release notes document changes.
> 
> https://phabricator.wikimedia.org/diffusion/MSEL/browse/master/RELEASES.md
> 
> If you have any questions, or you need help upgrading, let me know.
> 
> Željko

> ___
> QA mailing list
> q...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa


- End forwarded message -

-- 
| 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] Minor change to SWAT windows

[Greg Grossmeier]

tl;dr: I have removed the Tuesday 19:00 UTC SWAT window from the
deployment calendar due to conflicts. Pick one of the other 11 SWAT
windows.

The (current) Tuesday 19:00 UTC SWAT window is directly before the 20:00
UTC MediaWiki train window.

The nature of SWAT windows meant that the state of the deployed
MW+Extension+Config code was changing while the creation of the new MW
train version (eg: 1.29-wmf.8) was happening. This causes delays and
confusion.

The simple solution is to not have a normal SWAT window at that time.
Other deploys (eg Services) are fine to happen at that time which is why
I didn't just extend the MW train window to include that earlier hour.

Luckily, you still have 11 SWAT windows to choose from. :)

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] Deployments: upcoming holidays and their impact

[Greg Grossmeier]

As it always has since I've been here. But you're right. We should disable
it.

--
Sent from my phone, please excuse brevity.

On Dec 21, 2016 6:30 PM, "Alex Monk"  wrote:

> Although this is theoretically a deployment freeze week, in reality
> l10nupdate is still running:
>  !log l10nupdate@tin scap sync-l10n completed (1.29.0-wmf.6)
> (duration: 07m 54s)
>
> On 7 December 2016 at 17:39, Chad  wrote:
>
> > On Wed, Dec 7, 2016 at 9:22 AM Alex Monk  wrote:
> >
> > > Are we also going to be disabling l10nupdate then? That's surely more
> > risky
> > > than syncing beta's files (which aren't even loaded by production
> > apaches)
> > >
> > >
> > Sounds like a plan!
> >
> > -Chad
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> Alex Monk
> VisualEditor/Editing team
> https://wikimediafoundation.org/wiki/User:Krenair_(WMF)
> ___
> 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] 2016-12-14 Scrum of Scrums meeting notes

[Greg Grossmeier]

> On Wed, Dec 14, 2016 at 11:06 AM, Grace Gellerman <ggeller...@wikimedia.org>
> wrote:
> 
> > * Eileen published our first real CiviCRM extension to
> > https://civicrm.org/extensions/unsubscribe-email-data-entry-screen
> > ** existing extensions are all actually Drupal modules, not publicized
> > except in gerrit
> > ** hope more of our code becomes widely usable
> > https://www.mediawiki.org/wiki/Fundraising_tech/Free_Software_Citizenship
> > ** Katie is helping push for time in 2017 to further those goals
> >
> 
> That's great to hear, thank you Fundraising Tech! Non-profit fundraising is
> a very underserved sector, and CiviCRM is widely used; I'm sure sharing
> code back will indirectly advance our mission, and other worthwhile goals.

+1. I was really happy to see this as well. It should be standard
practice for our organizational community (iow: non-profits who hire
engineers).

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

Re: [Wikitech-l] [Engineering] Gerrit upgrade (w/ short downtime) tomorrow

[Greg Grossmeier]

> On Tue, Dec 6, 2016 at 10:10 AM, Chad Horohoe <choro...@wikimedia.org>
> wrote:
> 
> > Tomorrow evening (18:30–19:30 UTC) I'll be taking Gerrit offline shortly
> > for a planned upgrade from 2.12.5 to 2.13.3. It shouldn't take the full
> > hour, but you never know :)
> >
> 
> It seems the links to Differential (next to the commit and parent sha1,
> below the commit message) went away with the update. Those were quite
> useful. (Instead, there are links on top of the diff screens, but they
> don't work.)

I didn't see a task or follow-up on this, so I filed:
https://phabricator.wikimedia.org/T153130

For the record, what I see now:
* The "(Diffusion)" link is next to the commit sha1, but not the parent
  one
** and it works as expected
* The "(Diffusion)" links at the top of the diff view do not work

Thanks for the report, Gergo,

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

Re: [Wikitech-l] Deployments: upcoming holidays and their impact

[Greg Grossmeier]

Reminder: This next week (Dec 12th) is the last normal week before the
end of year holiday season deploy freeze goes into effect. Plan
accordingly.

Greg


> It's that time of year again; the holiday season.
> 
> Different from last year: 
> In the interest of both 1) giving engineers full time off at the end of the
> year (not needing to be aware of what code they wrote is being deployed)
> and 2) to keep the site reliable during our end-of-year fundraising
> pushes there will be 2 weeks (instead of just 1) at the end of December
> that are NO DEPLOYS weeks.
> 
> Here's the basic outline from now until mid-January (by week):
> * Nov 7th: normal
> * Nov 14th: normal
> * Nov 21st: (Thanksgiving)
> ** All week: no train
> ** Mon/Tues: SWATs only 
> ** Wed/Thur/Fri: NO DEPLOYS
> * Nov 28th: normal
> * Dec 5th: normal
> * Dec 12th: normal
> * Dec 19th: NO DEPLOYS (XMAS)
> * Dec 26th: NO DEPLOYS (XMAS)
> * Jan 2nd: normal (with train)
> * Jan 9th: no train, SWATs only (but no one from RelEng is garaunteed to
> * be around) (DevSummit+All Hands)
> * Jan 16th: resume normalcy (Monday is MLK Day)
> 
> As always, the canonical location for deployment information is at:
> https://wikitech.wikimedia.org/wiki/Deployments
> 
> Best,
> 
> Greg
> 
> -- 
> | Greg Grossmeier    GPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |



-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

Re: [Wikitech-l] 2016 Wikimedia Developer Summit videos now available on YouTube

[Greg Grossmeier]

> Hello,
> The Wikimedia Developer Summit 2016 videos have been published to YouTube
> (and Commons!). [1] [2]
> 
> These videos cover the event earlier this year that saw MediaWiki and
> Wikimedia contributors come to gather to discuss the future of our shared
> technologies. Please enjoy and share.
> 
> [1] https://www.youtube.com/playlist?list=PLeoTcBlDanyNOFQmVMVwpKUXeuw_-896K
> [2] 
> https://commons.wikimedia.org/wiki/Category:Wikimedia_Developer_Summit_2016
> 
> A big thanks to the people who helped get these videos online to share.
> Particularly Husn Shujaat and Andre Klapper.

Thanks for the heads up Chris!

Particularly timely given the ~1 month until DevSummit '17.

I was just reviewing a couple of the videos myself for things we wanted
to do but haven't yet :)

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

Re: [Wikitech-l] Deployments: upcoming holidays and their impact

[Greg Grossmeier]

Reminder. We are now in the 3 weeks of normalcy before the end-of-year
holiday freeze begins.

Greg


> It's that time of year again; the holiday season.
> 
> Different from last year: 
> In the interest of both 1) giving engineers full time off at the end of the
> year (not needing to be aware of what code they wrote is being deployed)
> and 2) to keep the site reliable during our end-of-year fundraising
> pushes there will be 2 weeks (instead of just 1) at the end of December
> that are NO DEPLOYS weeks.
> 
> Here's the basic outline from now until mid-January (by week):
> * Nov 7th: normal
> * Nov 14th: normal
> * Nov 21st: (Thanksgiving)
> ** All week: no train
> ** Mon/Tues: SWATs only 
> ** Wed/Thur/Fri: NO DEPLOYS
> * Nov 28th: normal
> * Dec 5th: normal
> * Dec 12th: normal
> * Dec 19th: NO DEPLOYS (XMAS)
> * Dec 26th: NO DEPLOYS (XMAS)
> * Jan 2nd: normal (with train)
> * Jan 9th: no train, SWATs only (but no one from RelEng is garaunteed to
> * be around) (DevSummit+All Hands)
> * Jan 16th: resume normalcy (Monday is MLK Day)
> 
> As always, the canonical location for deployment information is at:
> https://wikitech.wikimedia.org/wiki/Deployments
> 
> Best,
> 
> Greg
> 
> -- 
> | Greg Grossmeier    GPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |



-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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

[Wikitech-l] Fwd: [Ops] mw1017, mw1099 are gone

[Greg Grossmeier]

FYI to those who use these hosts during SWAT deploys.

- Forwarded message from Giuseppe Lavagetto <glavage...@wikimedia.org> -

> Date: Tue, 22 Nov 2016 14:53:50 +0100
> From: Giuseppe Lavagetto <glavage...@wikimedia.org>
> To: Operations Engineers <o...@lists.wikimedia.org>
> Subject: [Ops] mw1017, mw1099 are gone
> 
> Hi all,
> 
> due to an unfortunate chain of events, mw1017 and mw1099, the MediaWiki
> test appservers in eqiad, had to be decommissioned this morning. Their
> substitutes are mwdebug1001 and mwdebug1002
> 
> So, not to break the deployers workflow, what is happening is what follows:
> 
> - when you select mw1017 from the browser extension, the request will go do
> mwdebug1001
> - when you select mw1099, the request will go to mwdebug1002
> 
> the extensions will be updated as soon as possible (in a way that will
> allow us an easy change of the server list without any extension release),
> and I am in the process of upgrading the documentation on wikitech.
> 
> I apologize for the inconvenience,
> 
> Giuseppe
> -- 
> Giuseppe Lavagetto, Ph.d.
> Senior Technical Operations Engineer, Wikimedia Foundation

> ___
> Ops mailing list
> o...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ops


- End forwarded message -

-- 
| 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] No MediaWiki train deployment next week (US Holiday/short week)

[Greg Grossmeier]

Hello all,

A quick note that next week is Thanksgiving in the US. As such the week
is shorter (only 3 days) and we will NOT be rolling out a new version of
MediaWiki.

We will have the normal SWAT windows on Monday and Tuesday (but not
Wednesday, as that is effectively a "Friday"). Those SWATs are only for
important fixes; don't even think about using them as a way of getting
around the lack of a train.

Details:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_November_21st

Best,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


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