Re: [Wikitech-l] Question to WMF: Backlog on bugs

Hi and thanks for joining the discussion! On Sat, 2019-03-16 at 20:37 -0400, Thomas Eugene Bishop wrote: > Here’s a specific example, created in 2015: > > https://phabricator.wikimedia.org/T116145 < > https://phabricator.wikimedia.org/T116145> > > > A bug fix was provided years ago but

Re: [Wikitech-l] New Gerrit privilege policy

On 17/3/19 12:48 am, Merlijn van Deen (valhallasw) wrote: > On Sat, 16 Mar 2019 at 03:01, Tim Starling wrote: > >> No, managing +2 permissions is not up to the maintainer of the tool, >> that's the whole point of the change. >> > > I feel that this policy, although well-meaning, and a step

Re: [Wikitech-l] Gerrit outage

The watchlist should be in All-Users. If someone removed your watchlist you can clone that repo. Then in .git/config change refs/heads to just refs/*. Then it should show some refs (I forget which one you check out so you should try them all) you can use git log to see if someone git committed

Re: [Wikitech-l] Question to WMF: Backlog on bugs

> On Mar 13, 2019, at 6:48 PM, Andre Klapper > wrote: > > On Wed, 2019-03-13 at 21:01 +0100, John Erling Blad wrote: >> ... But nobody does anything about the >> sinkhole itself. > > And repeating the same thing over and over again while repeatedly > ignoring

[Wikitech-l] Where should extension default preferences be specified?

There are two places the default value for an extension-specific preference can be specified: (1) DefaultUserOptions in extension.json (2) onGetPreferences (or whatever function hooks GetPreferences) in MyExtension.hooks.php Which is better? If you do it in both places, and

Re: [Wikitech-l] Gerrit outage

Hello, after the Gerrit outage, my list of watched changes is seemingly empty, while it has not been a day before. Is it possible to fix this issue? MGChecker -Ursprüngliche Nachricht- Von: Wikitech-l [mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Pine W Gesendet:

Re: [Wikitech-l] Unbreak now! problem in this week train Watchlist

It happens again now. Igal בתאריך יום ו׳, 15 במרץ 2019, 15:45, מאת Željko Filipin ‏< zfili...@wikimedia.org>: > Hi everybody, > > I'm in charge of train this week. Should this be added as a blocker? > > https://phabricator.wikimedia.org/T206675 > > Thank you, > > Željko > > On Thu, Mar 14, 2019

Re: [Wikitech-l] New Gerrit privilege policy

I just want to point out that this wasn't "handed down by a CTO", it was a RFC [1] that and was open for discussion to everyone and was discussed extensively (and the RFC changed because of these discussions, look at the history of the page), then had an IRC meeting that was also open to everyone,

Re: [Wikitech-l] New Gerrit privilege policy

I agree that while possibly made with good intentions, policy changes like these should go through dev community discussion + vote, not be handed down from a CTO. Wikipedia as a movement started that way, and many people participated in it because of its transparency and community-driven process.

Re: [Wikitech-l] Gerrit outage

Thanks for the updates and for everyone who was or is working on a weekend day. Sometime in the next few weeks if you can publish an incident report that has any sensitive information redacted, I would like to read it. Pine ( https://meta.wikimedia.org/wiki/User:Pine ) On Sat, Mar 16, 2019,

Re: [Wikitech-l] New Gerrit privilege policy

Andre, from what im gathering from this thread thats not what I understand, so i redact the part of my last email about toolforge, however my point on this policy change should of been put to a community vote/consensus is valid. -- Devin “Zppix” CCENT Volunteer Wikimedia Developer Africa

Re: [Wikitech-l] Gerrit outage

Hello, Gerrit is available again but we are continuing to investigate the suspicious activity. Our preliminary findings point to no users or production systems being compromised and no loss of any confidential information. As we continue to investigate over the next few days we will add any

Re: [Wikitech-l] New Gerrit privilege policy

On Sat, 2019-03-16 at 12:40 -0500, Zppix wrote: > So your basically telling me, I can’t decide who gets the power to +2 > on for example a toolforge tool I actively am the primary maintainer > of? Instead it has to be requested. I do not disagree with a lot of > the changes to technical policies,

Re: [Wikitech-l] New Gerrit privilege policy

So your basically telling me, I can’t decide who gets the power to +2 on for example a toolforge tool I actively am the primary maintainer of? Instead it has to be requested. I do not disagree with a lot of the changes to technical policies, but with this change it seems to restrict ability to

[Wikitech-l] Gerrit outage

Hello, On 16 March 2019, Wikimedia Foundation staff observed suspicious activity associated with Gerrit and as a precautionary step has taken Gerrit offline pending investigation. The Wikimedia Foundation's Security, Site Reliability Engineering and Release Engineering teams are investigating

Re: [Wikitech-l] Question to WMF: Backlog on bugs

În sâm., 16 mar. 2019 la 15:55, David Barratt a scris: > > Perhaps a better example would be the Drupal community who has a total of > ~1,071,600 issues and ~282,350 of those are open > https://www.drupal.org/project/issues and they have several organizations >

Re: [Wikitech-l] New Gerrit privilege policy

On 16/03/2019 14:35, Bartosz Dziewoński wrote: On 2019-03-16 14:48, Merlijn van Deen (valhallasw) wrote: 1. According to the policy, self-+2'ing is grounds for revocation of Gerrit privileges. For a Toolforge tool, self +2-ing is common and expected: the repository is hosted on Gerrit to

Re: [Wikitech-l] New Gerrit privilege policy

On 2019-03-16 14:48, Merlijn van Deen (valhallasw) wrote: 1. According to the policy, self-+2'ing is grounds for revocation of Gerrit privileges. For a Toolforge tool, self +2-ing is common and expected: the repository is hosted on Gerrit to allow for CI and to make contributions from others

Re: [Wikitech-l] New Gerrit privilege policy

On 16/03/2019 13:48, Merlijn van Deen (valhallasw) wrote: On Sat, 16 Mar 2019 at 03:01, Tim Starling wrote: No, managing +2 permissions is not up to the maintainer of the tool, that's the whole point of the change. I feel that this policy, although well-meaning, and a step forwards for

Re: [Wikitech-l] Question to WMF: Backlog on bugs

Perhaps a better example would be the Drupal community who has a total of ~1,071,600 issues and ~282,350 of those are open https://www.drupal.org/project/issues and they have several organizations https://www.drupal.org/organizations working on the software. I do not understand how a large

Re: [Wikitech-l] New Gerrit privilege policy

On Sat, 16 Mar 2019 at 03:01, Tim Starling wrote: > No, managing +2 permissions is not up to the maintainer of the tool, > that's the whole point of the change. > I feel that this policy, although well-meaning, and a step forwards for MediaWiki and other WMF-production software, is unreasonably

Re: [Wikitech-l] New Gerrit privilege policy

On Sat, 2019-03-16 at 12:59 +1100, Tim Starling wrote: > On 16/3/19 7:53 am, Andre Klapper wrote: > > What is supposed to happen with > > https://phabricator.wikimedia.org/tag/repository-ownership-requests/ ? > > I archived it. Thanks! I've updated its Phab project description to explain where

Re: [Wikitech-l] Question to WMF: Backlog on bugs

On Sat, 2019-03-16 at 04:52 +, Pine W wrote: > From the end user perspective, reporting a bug and then having nothing > happen, or getting an initial reply but later seeing that a bug appears to > stall for months or years, may be frustrating depending on the nature of > the bug and the