[Wikitech-l] Re: Drop dedicated support for IE 11, Edge Legacy and Opera

[RhinosF1 -]

Morning Design Team,

I've had a quick look at the usage stats from Miraheze for the last 21 days
and I'm seeing around 5.5% of traffic using Opera.

Opera isn't a well used but still fairly popular browser and I'm not sure I
believe it's got less 0.1% of traffic for Wikimedia. Where has this data
come from?

I have no objection to dropping IE but I do note that it's still about 0.5%
for us today. I haven't had time to look at Edge legacy data.

Thanks,
Sam


On Tue, 14 May 2024 at 10:44,  wrote:

> I very strongly object to dropping Opera. Opera's market share is a lot
> more than 0.1% on other stats services, there must be something wrong with
> the detection code. Opera is very popular in Africa and Eastern Europe, and
> has a lot of users with the Opera GX gaming browser as well. There are also
> multiple Opera versions as well on a large range of mobile devices. Opera
> Mini should still be supported as it is useful in areas of the world where
> data is expensive or slow. I hope you do some more studies and consider
> keeping Opera support.
> ___
> 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: Notification of edit-at-thon scheduled

[RhinosF1 -]

Hi,

I've replied on task

On Mon, 18 Mar 2024 at 17:58, Esteban Zarate  wrote:

> Please, take a look of https://phabricator.wikimedia.org/T360357 I know
> 19 days is very close to request this, but in this country (Argentina) is
> very difficult to schedule it with more time. Thanks in advance!!
> ___
> 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: Edit-a-thon

[RhinosF1 -]

Hi Esteban,

I left a few messages and one of the SRE team has said they should be able
to get it out on Monday morning's slot which will be in time for you.

Please do try and give as much notice as possible in future.

Thanks,
RhinosF1


On Sat, 2 Dec 2023 at 10:23, Zoran Dori  wrote:

> Hello Esteban,
> I'm sorry, but I don't think we will be able to help you, because
> configuration changes can't be deployed on the weekend (because people
> aren't available much like on workdays).
>
> But if the event starts after 09:00–10:00 UTC+1, maybe we could work
> something out. :)
> Can you please add a number of accounts in the task, and time when the
> event is starting and ending?
>
> Best regards,
> Zoran
>
> суб, 2. дец 2023. у 03:15 Esteban Zarate  је
> написао/ла:
>
>> Hi i need, if posible, speedy atention to
>> https://phabricator.wikimedia.org/T352569 needed for next Monday.
>> Regards!!
>> ___
>> 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] Beta Cluster Ongoing Issue

[RhinosF1 -]

Good evening all,

Please be aware that the deployment-prep beta cluster is currently offline
due to technical issues following the Cloud Services incident earlier today.

You can follow
https://phabricator.wikimedia.org/T315350 for updates on the issues.

A massive thank you to Brian King and TheresNoTime for working on the
issues so far.

Any assistance is appreciated on task or #wikimedia-releng on Libera. There
is no ETA at the moment for service restoration as the issue is unclear.

Thanks,
RhinosF1/Samuel
-- 
Thanks,
Samuel
___
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: Problems with Special:MyLanguage and German

[RhinosF1 -]

It is probably worth opening a bug on Phabricator. As far as I can tell
Special:MyLanguage (
https://github.com/wikimedia/mediawiki/blob/master/includes/specials/SpecialMyLanguage.php)
does not include any logic for using the fallback languages which for
de-formal is de.

RhinosF1

On Fri, 22 Jul 2022 at 14:23, Bernhard Krabina, KM-A <
bernhard.krab...@km-a.net> wrote:

> Dear all,
>
>
>
> in a regular MediaWiki installation switched to de-formal, all help links
> point to the English versions. This is probably because there is not
> de-formal version of the MediaWiki documentation, which of course is fine.
> But all links to SpecialMyLanguage should lead to the German documentation,
> for settings of “de”, “de-formal”, “de-at” etc.
>
>
>
> As an example: the help icon on Special:Recent changes leads to
> https://meta.wikimedia.org/wiki/Special:MyLanguage/Help:Recent_changes
>
>
>
> But if you set your wiki to de-formal, it will lead you to the English
> help pages instead the German ones.
>
>
>
> Best,
>
> Bernhard
> ___
> 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/

Re: [Wikitech-l] Wikimedia Chat

[RhinosF1 -]

For the privacy policy question, that box is standard for anything hosted
with Cloud Services.

I'd trust Amir wouldn't do that but it reduces the responsibility of WMCS.

Thanks.

On Mon, 31 Aug 2020 at 08:56, Count Count 
wrote:

> Hi!
>
>
>
> Thanks for providing another communication tool.
>
>
>
> Some questions:
>
>
>
>- Is there a reason why we are not using Wikimedia account SSO for the
>
>chat?
>
>- The Terms link leads directly to the Tech Code of Conduct. Shouldn't
>
>it link to  https://foundation.wikimedia.org/wiki/Terms_of_Use/en
> instead?
>
>After all terms are usually more than just a Code of Conduct.
>
>- The linked privacy policy
>
>
> is
>
>a bit scary. It states that there is no expectation of privacy as my
> chats
>
>could be published at any time and that the administrators might have
>
>access to my username/password combination, which should not at all be
>
>necessary. Is that really the intent here?
>
>
>
>
>
> Best regards,
>
>
>
> Count Count
>
>
>
> On Sun, Aug 30, 2020 at 2:00 AM Amir Sarabadani 
> wrote:
>
>
>
> > Hello,
>
> > Due to the current situation, there are more and more collaborations
>
> > happening online instead. and now you can see Wikimedia-related
> discussion
>
> > groups in Slack, Discord, Telegram, Facebook, and many more. Besides
> being
>
> > scattered and inaccessible to people who don't have accounts in those
>
> > platforms (for privacy reasons for example), these platforms use
>
> > proprietary and closed-source software, are outside Wikimedia
>
> > infrastructure and some harvest our personal data for profit.
>
> >
>
> > IRC on freenode is a good alternative but it lacks basic functionalities
> of
>
> > a modern chat platform. So we created Wikimedia Chat, a mattermost
> instance
>
> > in Wikimedia Cloud. Compared to IRC, you have:
>
> > * Ability to scrollback and read messages when you were offline
>
> > * Push notification and email notification
>
> > * You don't need to get a cloak to hide your IP from others
>
> > * Proper support for sharing media
>
> > * Two factor authentication
>
> > * A proper mobile app support
>
> > * Ability to add custom emojis (yes, it's extremely important)
>
> > * Profile pictures
>
> > * Ability to ping everyone with @here
>
> > * much much more.
>
> >
>
> > You can use Wikimedia Chat by going to https://chat.wmcloud.org, anyone
>
> > can
>
> > make an account. This is part of Wikimedia Social suite [1], the oher
>
> > similar project is "Wikimedia Meet". [2]
>
> >
>
> > Some notes:
>
> > * This is done in my volunteer capacity and has been maintained by a
> group
>
> > of volunteers. If you're willing to join the team (either technical or
>
> > enforcing CoC, kicking out spammers, other daily work), drop me a
> message.
>
> > * Privacy policy of Wikimedia Cloud applies: https://w.wiki/aQW
>
> > * As a result, all messages older than 90 days get automatically deleted.
>
> > * As a Wikimedia Cloud project, all of discussions, private and public
> are
>
> > covered by Code of conduct in technical spaces:  https://w.wiki/AK$
>
> >
>
> > Hope that would be useful for you, if you encounter any technical issues,
>
> > file a bug in the phabricator.
>
> >
>
> > [1] https://meta.wikimedia.org/wiki/Wikimedia_Social_Suite
>
> > [2] https://meta.wikimedia.org/wiki/Wikimedia_Meet
>
> >
>
> > Best
>
> > --
>
> > Amir (he/him)
>
> > ___
>
> > 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
>
> --
Thanks,
Samuel
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Wikimedia Chat

[RhinosF1 -]

Hi everyone,

They were issues with various things due to a CenturyLink outage that then
impacted a lot else. (IRCCloud / Cloudflare for example).

Maybe, try now?

Thanks,
RhinosF1

On Sun, 30 Aug 2020 at 17:04, ZI Jony  wrote:

> I also have same problem like QEDK, I've also tried it on two different
>
> networks after seen QEDK's email but both time out in the end.
>
>
>
> On Sun, Aug 30, 2020, 9:21 PM Strainu  wrote:
>
>
>
> > În dum., 30 aug. 2020 la 03:00, Amir Sarabadani  a
>
> > scris:
>
> > >
>
> > > Hello,
>
> > > Due to the current situation, there are more and more collaborations
>
> > > happening online instead. and now you can see Wikimedia-related
>
> > discussion
>
> > > groups in Slack, Discord, Telegram, Facebook, and many more. Besides
>
> > being
>
> > > scattered and inaccessible to people who don't have accounts in those
>
> > > platforms (for privacy reasons for example), these platforms use
>
> > > proprietary and closed-source software, are outside Wikimedia
>
> > > infrastructure and some harvest our personal data for profit.
>
> >
>
> > Hey Amir,
>
> >
>
> > Please take this email as positive feedback, even if it might not
>
> > sound like it :)
>
> >
>
> > As much as I value software freedom and my personal data, I've learned
>
> > during the years that the best conversations happen where people
>
> > converge naturally, not where one wants them to be. What you describe
>
> > below is an awesome list of features ... that already exist elsewhere.
>
> > I could give you an equally long list of things that are missing, but
>
> > individually, none of them matter. What matters is which platform most
>
> > people choose, based on which of the features are important for them.
>
> > And that platform might be different for different projects.
>
> >
>
> > What that means is that Wikimedia Chat will be just another name in
>
> > that long list of apps that people choose to use or not. It's fine if
>
> > you want to maintain it, it's great if it will gain traction, but
>
> > don't be too upset if it will have the same usage as Wikimedia Spaces.
>
> >
>
> > Strainu
>
> > >
>
> > > IRC on freenode is a good alternative but it lacks basic
> functionalities
>
> > of
>
> > > a modern chat platform. So we created Wikimedia Chat, a mattermost
>
> > instance
>
> > > in Wikimedia Cloud. Compared to IRC, you have:
>
> > > * Ability to scrollback and read messages when you were offline
>
> > > * Push notification and email notification
>
> > > * You don't need to get a cloak to hide your IP from others
>
> > > * Proper support for sharing media
>
> > > * Two factor authentication
>
> > > * A proper mobile app support
>
> > > * Ability to add custom emojis (yes, it's extremely important)
>
> > > * Profile pictures
>
> > > * Ability to ping everyone with @here
>
> > > * much much more.
>
> > >
>
> > > You can use Wikimedia Chat by going to https://chat.wmcloud.org,
> anyone
>
> > can
>
> > > make an account. This is part of Wikimedia Social suite [1], the oher
>
> > > similar project is "Wikimedia Meet". [2]
>
> > >
>
> > > Some notes:
>
> > > * This is done in my volunteer capacity and has been maintained by a
>
> > group
>
> > > of volunteers. If you're willing to join the team (either technical or
>
> > > enforcing CoC, kicking out spammers, other daily work), drop me a
>
> > message.
>
> > > * Privacy policy of Wikimedia Cloud applies: https://w.wiki/aQW
>
> > > * As a result, all messages older than 90 days get automatically
> deleted.
>
> > > * As a Wikimedia Cloud project, all of discussions, private and public
>
> > are
>
> > > covered by Code of conduct in technical spaces:  https://w.wiki/AK$
>
> > >
>
> > > Hope that would be useful for you, if you encounter any technical
> issues,
>
> > > file a bug in the phabricator.
>
> > >
>
> > > [1] https://meta.wikimedia.org/wiki/Wikimedia_Social_Suite
>
> > > [2] https://meta.wikimedia.org/wiki/Wikimedia_Meet
>
> > >
>
> > > Best
>
> > > --
>
> > > Amir (he/him)
>
> > > ___
>
> > 

Re: [Wikitech-l] New Code of Conduct committee candidates

[RhinosF1 -]

Well done everyone for joins and good luck.

Let's thank those departing for their service!

RhinosF1

On Wed, 10 Jun 2020 at 20:51, Amir Sarabadani  wrote:

> Hello again,
> In the given timeframe no objection has been made, so as of today Martin
> joins the main committee and Jay joins the aux members.
>
> Join me in thanking the work of Lucie, Tpt and Rosalie and welcome Martin
> and Jay to the team.
>
> I had the pleasure of working with Lucie in the past couple of years and
> her work was invaluable in solving complex issues while it hasn't been
> public and barely anyone knows her contributions. Thank you Lucie.
>
> Best
>
> On Tue, Apr 28, 2020 at 9:27 PM Amir Sarabadani 
> wrote:
>
> > Quick correction the final date is *09 June 2020* and not *09 June 2019"
> > which I assume has past a while ago.
> >
> > Sorry
> >
> >
> > On Tue, Apr 28, 2020 at 9:12 PM Amir Sarabadani 
> > wrote:
> >
> >> Hello,
> >> The committee has finished selecting new members and the new committee
> >> candidates are (In alphabetical order):
> >>
> >>- Amir Sarabadani
> >>- Martin Urbanec
> >>- MusikAnimal
> >>- Tonina Zhelyazkova
> >>- Tony Thomas
> >>
> >> And auxiliary members will be (Also in alphabetical order):
> >>
> >>- Huji
> >>- Jayprakash12345
> >>- Matanya
> >>- Nuria Ruiz
> >>- Tpt
> >>
> >> You can read more about the members in [0]
> >>
> >> The changes compared to last term are:
> >> * Lucie has resigned in September 2019. Tpt (as one of auxiliary
> members)
> >> filled her seat in the meantime and now Tpt is moving to be an auxiliary
> >> member again.
> >> * Martin Urbanec is joining the main committee to fill Lucie/Tpt seat
> >> * Jay Prakash is joining auxiliary members
> >> * Rosalie is leaving the auxiliary members.
> >>
> >> This is not the final structure. According to the CoC [1], the current
> >> committee publishes the new members and call for public feedback for
> *six
> >> weeks* and after that, the current committee might apply changes to the
> >> structure based on public feedback.
> >>
> >> Please let the committee know if you have any concern regarding the
> >> members and its structure until *09 June 2019* and after that, the new
> >> committee will be in effect and will serve for a year.
> >>
> >> [0]:
> >>
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates
> >> [1]:
> >>
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_members
> >>
> >> Amir, On behalf of the Code of Conduct committee
> >> Best
> >>
> >
> >
> > --
> > Amir (he/him)
> >
> >
>
> --
> Amir (he/him)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

Re: [Wikitech-l] Namespace Localisations & Updates

[RhinosF1 -]

I would suggest a special window.

I normally do the late window so I can see if Catrope can come an hour
early for one and we do it then.

Samuel

On Mon, 18 May 2020 at 20:48, Tyler Cipriani 
wrote:

> On 20-05-18 16:32:59, RhinosF1 - wrote:
> >My only concern with that is that between the 2 tasks it would be 5/6
> >patches in the SWAT window.
>
> Yes, this work looks like it will consume a whole window easily :(
>
> >It would also be my first mediawiki core + extensions SWAT so are the
> >patches safe to +2 during / just before SWAT or Should I get that done
> >before?
>
> On process I think might work:
>
> * Merge core changes to master early in the week you plan to SWAT (but
> after branch cut for the week)
> * Prepare cherry-picks to backport to current stable + branch to go out
> that week
> * Add cherry-picks to deploy window
>
> It's likely this is more than 6 patches :\
>
> Syncing with a SWATter prior to SWAT and ensuring that you pick a window
> with some time after it (should you need more time to deploy) OR making
> a special window on the deployment calendar[0] for this set of changes
> would be best.
>
> -- Tyler
>
> [0]: <https://wikitech.wikimedia.org/wiki/Deployments>
>
> >On Mon, 18 May 2020 at 16:25, Tyler Cipriani 
> >wrote:
> >
> >> Hi Samuel
> >>
> >> On 20-05-18 09:57:54, RhinosF1 - wrote:
> >> >On https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/, it was
> >> >raised correctly that namespaceDupes.php would need to be ran.
> >> >
> >> >https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/ and
> >> >https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 can mostly run with
> the
> >> >train (expect the mediawiki config patch) but all require
> namespaceDupes
> >> to
> >> >be ran and on https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 could
> do
> >> >with being deployed as close together as possible to avoid
> >> >inconsistently translated namespaces.
> >> >
> >> >Would as mentioned SWAT be better for all 5 patches or should we let
> what
> >> >can ride with the train and deploy the one config patch shortly after
> and
> >> >run for both wikis in that window? or could we ask the train runners
> to do
> >> >that?
> >>
> >> What you're describing sounds like it would be a good candidate for SWAT
> >> deployment. My reasoning is that (1) it is atypical to run maintenance
> >> scripts as part of the train and (2) there are no guarantees that a
> >> train won't rollback.
> >>
> >> That is, backporting to a version that is stable ensures that we don't
> >> end up having rolled forward to all wikis, run the maintenance script,
> >> and then having to rollback due to an unrelated problem. Additionally,
> >> the log triage that follows a train window may mean that we can't
> >> guarantee a timely deploy of the configuration change following train.
> >>
> >> To me, this feels safer/faster/easier as a SWAT deployment; even though
> >> this might make for a particularly long SWAT window.
> >>
> >> Thanks!
> >> -- Tyler
> >> ___
> >> Wikitech-l mailing list
> >> Wikitech-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> >--
> >Thanks,
> >Samuel
> >___
> >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

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

Re: [Wikitech-l] Namespace Localisations & Updates

[RhinosF1 -]

I’m quite happy go with a SWAT deployment and I agree that it’s probably a
lot safer.

My only concern with that is that between the 2 tasks it would be 5/6
patches in the SWAT window.

It would also be my first mediawiki core + extensions SWAT so are the
patches safe to +2 during / just before SWAT or Should I get that done
before?

Thanks,
Samuel

On Mon, 18 May 2020 at 16:25, Tyler Cipriani 
wrote:

> Hi Samuel
>
> On 20-05-18 09:57:54, RhinosF1 - wrote:
> >On https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/, it was
> >raised correctly that namespaceDupes.php would need to be ran.
> >
> >https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/ and
> >https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 can mostly run with the
> >train (expect the mediawiki config patch) but all require namespaceDupes
> to
> >be ran and on https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 could do
> >with being deployed as close together as possible to avoid
> >inconsistently translated namespaces.
> >
> >Would as mentioned SWAT be better for all 5 patches or should we let what
> >can ride with the train and deploy the one config patch shortly after and
> >run for both wikis in that window? or could we ask the train runners to do
> >that?
>
> What you're describing sounds like it would be a good candidate for SWAT
> deployment. My reasoning is that (1) it is atypical to run maintenance
> scripts as part of the train and (2) there are no guarantees that a
> train won't rollback.
>
> That is, backporting to a version that is stable ensures that we don't
> end up having rolled forward to all wikis, run the maintenance script,
> and then having to rollback due to an unrelated problem. Additionally,
> the log triage that follows a train window may mean that we can't
> guarantee a timely deploy of the configuration change following train.
>
> To me, this feels safer/faster/easier as a SWAT deployment; even though
> this might make for a particularly long SWAT window.
>
> Thanks!
> -- Tyler
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

[Wikitech-l] Namespace Localisations & Updates

[RhinosF1 -]

Hello all,

I hope everyone is doing well.

On https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/, it was
raised correctly that namespaceDupes.php would need to be ran.

https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/596424/ and
https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 can mostly run with the
train (expect the mediawiki config patch) but all require namespaceDupes to
be ran and on https://gerrit.wikimedia.org/r/#/q/bug:%20T251287 could do
with being deployed as close together as possible to avoid
inconsistently translated namespaces.

Would as mentioned SWAT be better for all 5 patches or should we let what
can ride with the train and deploy the one config patch shortly after and
run for both wikis in that window? or could we ask the train runners to do
that?

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

Re: [Wikitech-l] composer test failure for operations/mediawiki-config

[RhinosF1 -]

Try running just the build db lists command as documented. Can you also
share the error?

Thanks,
Samuel

On Thu, 30 Apr 2020 at 05:40, Zoran Dori  wrote:

> Hello,
> can someone help me with this:
> https://phabricator.wikimedia.org/T251371#6095785 ?
>
> Why composer test fails for me locally?
>
> Best regards,
> Zoran Dori
> volunteer, Wikimedia Serbia
> s: zoranzoki21.github.io e: zorandori4...@gmail.com
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

Re: [Wikitech-l] Remote hackathon (May 9 - 11, 2020)

[RhinosF1 -]

Added, let the fun begin!

On Tue, 21 Apr 2020 at 14:44, Andre Klapper  wrote:

> Heja,
>
> On Mon, 2020-04-20 at 21:03 +0200, Maarten Dammers wrote:
> > The first weekend of May the Wikimedia Hackathon 2020 in Tirana was
> > supposed to happen. As an alternative, we're organizing a remote
> > hackathon. Please have a look at
> > https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020/Remote_Hackathon
> > and sign up if you're interested in participating.
> >
> > All of the sessions, projects, and initiatives are run by the
> > participants themselves and not overseen by a core organizing team.  All
> > ideas including technical projects and sessions, non-technical projects
> > and sessions, and social events/socal time are very welcome.
>
> It should probably also be added that as a movement, we don't have yet
> the experience to run remote events and we're all learning. :)
> This initiative is not a fully planned hackathon, but hopefully a nice
> opportunity to spend some social and hack time together.
>
> I'd also like to explicitly point out that if you plan to work on
> technical projects which will require deploying changes at some point,
> please be mindful and make sure to read and follow
> https://wikitech.wikimedia.org/wiki/Deployments/Covid-19 - let's not
> create more work for fellow developers and keep (some) things stable.
>
> Hope to see you there, even if you only join for a few hours!
>
> Happy hacking!
>
> andre
>
> --
> Andre Klapper (he/him) | Bugwrangler / Developer Advocate
> https://blogs.gnome.org/aklapper/
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

Re: [Wikitech-l] Code of conduct committee call for new members

[RhinosF1 -]

Good luck to all applicants!

Samuel

On Sat, 18 Apr 2020 at 21:24, Amir Sarabadani  wrote:

> Hello,
> Here's reminder that you have one day to send us your candidacy.
>
> Serving at the committee would help the technical community foster a
> hospital and welcoming environment for everyone. Join and help us!
>
> Best
>
> On Sat, Apr 4, 2020 at 5:09 PM Amir Sarabadani 
> wrote:
>
> > Hello all,
> >
> > It's coming close to time for annual appointments of community members to
> > serve on the Code of Conduct (CoC) committee. The Code of Conduct
> > Committee is a team of five trusted individuals plus five auxiliary
> > members with diverse affiliations responsible for general enforcement of
> > the Code of conduct for Wikimedia technical spaces. Committee members are
> > in charge of processing complaints, discussing with the parties affected,
> > agreeing on resolutions, and following up on their enforcement. For more
> on
> > their duties and roles, see
> > https://www.mediawiki.org/wiki/Code_of_Conduct/Committee
> >
> > This is a call for community members interested in volunteering for
> > appointment to this committee. Volunteers serving in this role should be
> > experienced Wikimedians or have had experience serving in a similar
> > position before.
> >
> >
> >
> > The current committee is doing the selection and will research and
> discuss
> > candidates. Six weeks before the beginning of the next Committee term,
> > meaning 27th of April 2019, they will publish their candidate slate (a
> > list of candidates) on-wiki. The community can provide feedback on these
> > candidates, via private email to the group choosing the next Committee.
> The
> > feedback period will be two weeks. The current Committee will then either
> > finalize the slate, or update the candidate slate in response to concerns
> > raised. If the candidate slate changes, there will be another two week
> > feedback period covering the newly proposed members. After the selections
> > are finalized, there will be a training period, after which the new
> > Committee is appointed. The current Committee continues to serve until
> the
> > feedback, selection, and training process is complete.
> >
> > If you are interested in serving on this committee or like to nominate a
> > candidate, please write an email to *techconductcandidates** AT
> > wikimedia.org * with details of your experience on
> > the projects, your thoughts on the code of conduct and the committee and
> > what you hope to bring to the role and whether you have a preference in
> > being auxiliary or constant member of the committee. The committee
> > consists of five members plus five auxiliary members and they will serve
> > for a year; all applications are appreciated and will be carefully
> > considered. The deadline for applications is end of day on 19th of April,
> > 2020.
> >
> > Please feel free to pass this invitation along to any users who you think
> > may be qualified and interested.
> >
> >
> > Best,
> >
> > Amir on behalf of the CoC committee
> >
>
>
> --
> Amir (he/him)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

[Wikitech-l] Fwd: Wikimedia Hackathon 2020: Registration Open!

[RhinosF1 -]

Cross Post

-- Forwarded message -
From: Rachel Farrand 
Date: Fri, 31 Jan 2020 at 16:09
Subject: Re: [Wikitech-l] Wikimedia Hackathon 2020: Registration Open!
To: Wikimedia developers 
Cc: 


Hello!
This is a reminder that 10 days from now (9 February) is the deadline for
volunteers requesting a scholarship or visa and WMF staff to register for
the Wikimedia Hackathon 2020 in Tirana. After that point the decision
committees will begin work and we will not be able to accept any more
applications so please make sure to register before then if you have an
interest in attending.
For those self-funding to attend this event, registration will remain open.

Again, please help make sure this is passed around to the relevant mailing
lists. :)
Thanks! We are here to help or answer questions that you may have.


On Thu, Jan 9, 2020 at 10:35 AM Rachel Farrand 
wrote:

> On behalf of Open Labs Albania  and the Wikimedia
> Foundation Community Events Team we are pleased to announce that
registration
> for the Wikimedia Hackathon 2020
>  is now
> open for both scholarships and regular attendees!
>
>
>
> The hackathon will be held at OFIÇINA  in Tirana,
> Albania between 9-11 May 2020 (please note that this is a Saturday through
> Monday instead of the usual Friday - Sunday). Additionally, we encourage
> attendees to stay in Tirana and attend the 7th annual Open Source
> Conference Albania (OSCAL)  which will be in
> the same venue on May 16th and 17th, and will have a Wikimedia Track and
> mission aligned organizations participating.
>
>
>
> We have identified two focus areas
> <
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020#Hackathon_Focus_Areas
>
> for the event which we will continue to refine and clarify over the next
> months. As usual, we welcome participants who plan to work on or learn
> about any project that they like related to any area of Wikimedia
> Technology.
>
>
>
> If you have any questions or comments please contact:
> wiki-hackat...@openlabs.cc Otherwise, please continue to follow our
> program and organizational developments on Wikimedia Hackathon 2020 on
> Mediawiki .
>
>
>
> Please help us by forwarding this email to relevant lists and looking
> forward to see you in Tirana!
>
>
> --
> Rachel Farrand
> Senior Program Manager
> Events Team
> Wikimedia Foundation
>


-- 
Rachel Farrand
Senior Program Manager
Events Team
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

[RhinosF1 -]

The spelling of ‘August’ is wrong in the second image on
https://phabricator.wikimedia.org/T243247. Looks fine in the code though so
not sure if fixed.

RhinosF1

On Thu, 23 Jan 2020 at 16:55, Mukunda Modell  wrote:

> The update was deployed last night just a bit after midnight UTC. Upon
> logging in, anyone with an affected auth factor should see a notification
> with instructions for how to proceed.
>
> For the curious, you can see screenshots of the notification which I
> attached to the task for this change, T243247 [1].
>
> [1]. https://phabricator.wikimedia.org/T243247
>
> On Mon, Jan 20, 2020 at 8:17 PM Mukunda Modell 
> wrote:
>
> > The plan is as follows:
> >
> > Sometime in the near future, we will be invalidating the sessions of
> > anyone who has an auth factor which was potentially affected. If you were
> > one of the potentially affected users then the next time you log in to
> > Phabricator, you should see a notification directing you to reset your
> TOTP
> > auth factor. If you don't see any notice like that then you are not among
> > those who were potentially affected.
> >
> > I will post an update here once that is done, in the meantime you don't
> > need to take any action in particular.
> >
> > On Fri, Jan 17, 2020 at 11:22 AM RhinosF1 -  wrote:
> >
> >> What about those that do?
> >>
> >> RhinosF1
> >>
> >> On Fri, 17 Jan 2020 at 15:51, David Sharpe 
> wrote:
> >>
> >> > There is a team working on the Phabricator 2FA action item right now.
> >> >  More to come soon…
> >> >
> >> > No action is required for people without 2FA configured within
> >> Phabricator.
> >> >
> >> >
> >> >
> >> > > On Jan 17, 2020, at 10:25 AM, RhinosF1 - 
> wrote:
> >> > >
> >> > > Can you also confirm we need to take NO action?
> >> > >
> >> > > RhinosF1
> >> > >
> >> > > On Fri, 17 Jan 2020 at 11:02, revi  wrote:
> >> > >
> >> > >> Hi,
> >> > >>
> >> > >> If it is possible to do so, can you notify to the people whose 2FA
> >> were
> >> > >> reset? I know at least few people who uses 2FA on Phab, and does
> not
> >> > read
> >> > >> emails from wikitech-l and/or wikimedia-l.
> >> > >>
> >> > >> Thanks!
> >> > >>
> >> > >> 나의 iPhone에서 보냄
> >> > >>
> >> > >>> 2020. 1. 17. 06:26, David Sharpe  작성:
> >> > >>>
> >> > >>> However, out of an abundance of caution, we are resetting all
> >> > Two-Factor
> >> > >> Authentication keys for Phabricator and invalidating the exposed
> >> login
> >> > >> access tokens.
> >> > >>
> >> > >>
> >> > >> ___
> >> > >> 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 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 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] 14 January 2020 security incident on Phabricator

[RhinosF1 -]

What about those that do?

RhinosF1

On Fri, 17 Jan 2020 at 15:51, David Sharpe  wrote:

> There is a team working on the Phabricator 2FA action item right now.
>  More to come soon…
>
> No action is required for people without 2FA configured within Phabricator.
>
>
>
> > On Jan 17, 2020, at 10:25 AM, RhinosF1 -  wrote:
> >
> > Can you also confirm we need to take NO action?
> >
> > RhinosF1
> >
> > On Fri, 17 Jan 2020 at 11:02, revi  wrote:
> >
> >> Hi,
> >>
> >> If it is possible to do so, can you notify to the people whose 2FA were
> >> reset? I know at least few people who uses 2FA on Phab, and does not
> read
> >> emails from wikitech-l and/or wikimedia-l.
> >>
> >> Thanks!
> >>
> >> 나의 iPhone에서 보냄
> >>
> >>> 2020. 1. 17. 06:26, David Sharpe  작성:
> >>>
> >>> However, out of an abundance of caution, we are resetting all
> Two-Factor
> >> Authentication keys for Phabricator and invalidating the exposed login
> >> access tokens.
> >>
> >>
> >> ___
> >> 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 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] 14 January 2020 security incident on Phabricator

[RhinosF1 -]

Can you also confirm we need to take NO action?

RhinosF1

On Fri, 17 Jan 2020 at 11:02, revi  wrote:

> Hi,
>
> If it is possible to do so, can you notify to the people whose 2FA were
> reset? I know at least few people who uses 2FA on Phab, and does not read
> emails from wikitech-l and/or wikimedia-l.
>
> Thanks!
>
> 나의 iPhone에서 보냄
>
> > 2020. 1. 17. 06:26, David Sharpe  작성:
> >
> > However, out of an abundance of caution, we are resetting all Two-Factor
> Authentication keys for Phabricator and invalidating the exposed login
> access tokens.
>
>
> ___
> 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] Scrum of scrums/2020-01-15

[RhinosF1 -]

Thx :)

On Wed, 15 Jan 2020 at 18:03, Željko Filipin  wrote:

> Hi RhinosF1,
>
> This was the only public reference about it that I could find.
>
> https://commons.wikimedia.org/wiki/Category:Wikimedia_Foundation_All_Hands
>
> Wikimedia Foundation All Hands is a yearly gathering of Wikimedia
> Foundation employees and contractors.
>
> Željko
>
> On Wed, Jan 15, 2020 at 6:53 PM RhinosF1 -  wrote:
>
> > What is ‘All Hands’?
> >
> > On Wed, 15 Jan 2020 at 17:17, Željko Filipin 
> > wrote:
> >
> > > Hi,
> > >
> > > for HTML version see
> > > https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-01-15
> > >
> > > Željko
> > >
> > > --
> > >
> > > = 2020-01-15 =
> > >
> > > == Callouts ==
> > > * Release Engineering
> > > ** January 27-31 - No deploys at all (including train), All-Hands
> > > ** The weekly MediaWiki branch cut is moving to full automation soon.
> If
> > > the timing of the branch cut affects you, please join the discussion at
> > > [[phab:T242446]]
> > > * SRE:
> > > ** Debian Jessie deprecation is ongoing. Deadline both OS wise and
> > hardware
> > > wise is 31March 2020. SCB cluster deployers, if you haven't already
> reach
> > > out to ServiceOps for help with migrating your service to Kubernetes,
> > > please do so.
> > >
> > > == Product ==
> > >
> > > === Editing ===
> > > * Updates: Summary: Refining reply features for DiscussionTools for
> first
> > > release with partner wikis projected for early February
> > > ** Add handling for mw:DisplaySpace (task [[phab:T241906]])
> > > ** Use mw.Api#getErrorMessage instead of custom handling (task
> > > [[phab:T240519]])
> > > *** Fix 'escape' to teardown by Ed Sanders
> > > *** Fix re-initialization after page is updated (task [[phab:T241861]])
> > > *** ReplyWidget: Load modules required by the content when previewing
> > (task
> > > [[phab:T241193]])
> > > *** Fix crash when opening VisualEditor NWE while DiscussionTools
> enabled
> > > (task [[phab:T241396]])
> > > *** ReplyWidget: Pass 'title' when previewing (task [[phab:T241221]])
> > >
> > > === Growth ===
> > > * Updates: Summary: continuing to implement and refine topic matching
> for
> > > newcomer suggested edits
> > > ** Add hidden preference for topics feature flag (task
> [[phab:T242698]])
> > > ** Newcomer tasks: Don't randomize for morelike search
> > > ** Newcomer tasks: Make a separate search query for every topic (task
> > > [[phab:T242560]]) (task [[phab:T242476]])
> > > ** Newcomer tasks: Topic matching instrumentation (task
> [[phab:T242052]])
> > > ** Suggested Edits: Fix button label from done state (task
> > > [[phab:T238612]]) (task [[phab:T238611]])
> > > ** Suggested Edits: Expand filters if below the fold item is checked
> > (task
> > > [[phab:T238612]])
> > > ** Suggested Edits: Use classic_noboostlinks for morelike query (task
> > > [[phab:T240512]])
> > > ** SuggestedEdits: Only export Topics.json once
> > > ** Suggested Edits: Add topic filters dialog (task [[phab:T238612]])
> > > ** Suggested Edits: Add topic filter button (task [[phab:T238611]])
> > > ** Newcomer tasks: Log search errors in task backend (task
> > > [[phab:T240512]])
> > > ** Newcomer tasks: Add test for API parameter info (task
> > [[phab:T240512]])
> > > ** Newcomer tasks: Expose task type / topic set in API parameter info
> > (task
> > > [[phab:T240512]])
> > > ** Newcomer tasks: Randomize suggested tasks locally (task
> > > [[phab:T242057]])
> > > ** StartEditingDialog: Add topics (task [[phab:T238610]])
> > > ** ApiQueryGrowthTasks: remove logged-in requirement (task
> > > [[phab:T242400]])
> > >
> > > === Android native app ===
> > > * Updates:
> > > ** Finished integration with mobile-html, finishing up migration logic
> of
> > > existing saved data on users' devices.
> > > ** Proceeding with Suggested Edits v4 (adding image tags)
> > >
> > > === Web ===
> > > * Updates:
> > > ** Summary: continuing desktop improvements (DIP).
> > > ** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project
> > (Vector
> > > / DIP)]]:
> > > *** [[phab:T242835|[RFC] Port MobileFrontend Feature Management
> > > into core]]
> > > *** [[phab:T23

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

[RhinosF1 -]

What is ‘All Hands’?

On Wed, 15 Jan 2020 at 17:17, Željko Filipin  wrote:

> Hi,
>
> for HTML version see
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-01-15
>
> Željko
>
> --
>
> = 2020-01-15 =
>
> == Callouts ==
> * Release Engineering
> ** January 27-31 - No deploys at all (including train), All-Hands
> ** The weekly MediaWiki branch cut is moving to full automation soon. If
> the timing of the branch cut affects you, please join the discussion at
> [[phab:T242446]]
> * SRE:
> ** Debian Jessie deprecation is ongoing. Deadline both OS wise and hardware
> wise is 31March 2020. SCB cluster deployers, if you haven't already reach
> out to ServiceOps for help with migrating your service to Kubernetes,
> please do so.
>
> == Product ==
>
> === Editing ===
> * Updates: Summary: Refining reply features for DiscussionTools for first
> release with partner wikis projected for early February
> ** Add handling for mw:DisplaySpace (task [[phab:T241906]])
> ** Use mw.Api#getErrorMessage instead of custom handling (task
> [[phab:T240519]])
> *** Fix 'escape' to teardown by Ed Sanders
> *** Fix re-initialization after page is updated (task [[phab:T241861]])
> *** ReplyWidget: Load modules required by the content when previewing (task
> [[phab:T241193]])
> *** Fix crash when opening VisualEditor NWE while DiscussionTools enabled
> (task [[phab:T241396]])
> *** ReplyWidget: Pass 'title' when previewing (task [[phab:T241221]])
>
> === Growth ===
> * Updates: Summary: continuing to implement and refine topic matching for
> newcomer suggested edits
> ** Add hidden preference for topics feature flag (task [[phab:T242698]])
> ** Newcomer tasks: Don't randomize for morelike search
> ** Newcomer tasks: Make a separate search query for every topic (task
> [[phab:T242560]]) (task [[phab:T242476]])
> ** Newcomer tasks: Topic matching instrumentation (task [[phab:T242052]])
> ** Suggested Edits: Fix button label from done state (task
> [[phab:T238612]]) (task [[phab:T238611]])
> ** Suggested Edits: Expand filters if below the fold item is checked (task
> [[phab:T238612]])
> ** Suggested Edits: Use classic_noboostlinks for morelike query (task
> [[phab:T240512]])
> ** SuggestedEdits: Only export Topics.json once
> ** Suggested Edits: Add topic filters dialog (task [[phab:T238612]])
> ** Suggested Edits: Add topic filter button (task [[phab:T238611]])
> ** Newcomer tasks: Log search errors in task backend (task
> [[phab:T240512]])
> ** Newcomer tasks: Add test for API parameter info (task [[phab:T240512]])
> ** Newcomer tasks: Expose task type / topic set in API parameter info (task
> [[phab:T240512]])
> ** Newcomer tasks: Randomize suggested tasks locally (task
> [[phab:T242057]])
> ** StartEditingDialog: Add topics (task [[phab:T238610]])
> ** ApiQueryGrowthTasks: remove logged-in requirement (task
> [[phab:T242400]])
>
> === Android native app ===
> * Updates:
> ** Finished integration with mobile-html, finishing up migration logic of
> existing saved data on users' devices.
> ** Proceeding with Suggested Edits v4 (adding image tags)
>
> === Web ===
> * Updates:
> ** Summary: continuing desktop improvements (DIP).
> ** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
> / DIP)]]:
> *** [[phab:T242835|[RFC] Port MobileFrontend Feature Management
> into core]]
> *** [[phab:T237635|[SPIKE] What should feature management look like
> in desktop improvements?]]
> *** [[phab:T237561|[SPIKE 10hrs] Investigate how skin suboptions
> can be presented in Special:Preferences]]
> *** [[phab:T240622|[Technical debt payoff] Remove
> InlineDiffFormatter and InlineDifferenceEngine from
> MobileFrontend]]
> *** [[phab:T240062|Extract components from VectorTemplate to
> Mustache files]]
> *** [[phab:T242674|Add storybook to Vector]]
> *** [[phab:T239248|[EPIC] Divide VectorTemplate into
> components]]
> *** [[phab:T117279|[EPIC] Core should provide inline diffs as well
> as side by side (Move InlineDifferenceEngine into core / remove
> MobileDiff)]]
> ** Mobile website (MinervaNeue / MobileFrontend):
> *** [[Reading/Web/Advanced_mobile_contributions|Advanced mode]]:
>  [[phab:T242491|Regression: AMC Outreach Drawer doesn't open
> when user is eligible]]
> *** Miscellaneous:
>  [[phab:T242281|Site navigation refers to undefined ARIA label
> (Minerva)]]
>  [[phab:T242310|Regression: issues with MobileDiff]]
>  [[phab:T214647|[EPIC] Re-define the contract for displaying
> drawers and overlays in MobileFrontend]]
>  [[phab:T242784|Regression: Watchstar CTA fails to display
> properly 2nd and 3rd time]]
>  [[phab:T241179|Remove Special:MobileMenu]]
>  [[phab:T237290|Disable mobile beta mode (for now)]]
>  [[phab:T237050|The `site` and `site.styles` module should be
> explictly disabled on mobile rather than abuse the targets
> system]]
>  [[phab:T234570|Tech debt: Drop Browser.supportsAnimations
> method]]
>  [[phab:T217616|Ordered lists per default receive `decimal`
> list style 

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

[RhinosF1 -]

Great!

Thanks greg for your help.

On Wed, 8 Jan 2020 at 18:35, Greg Grossmeier  wrote:

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

[RhinosF1 -]

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

RhinosF1

On Wed, 8 Jan 2020 at 17:21, Željko Filipin  wrote:

> Hi,
>
> for HTML version see
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-01-08
>
> Željko
>
> --
>
> = 2020-01-08 =
>
> == Callouts ==
> * Release Engineering
> ** January 27th-31st - No deploys at all (including train), All-Hands
> ** Need some help (from CPT? Maybe?) looking at jobqueue on beta cluster
> which is evidently running slowly: [[phab:T241448]]
> * SRE:
> ** The eqiad kubernetes cluster will be reinitialized on Tuesday Jan 14th
> 2020. The duration is expected to be up to 4 hours during EU morning. All
> requests will have been routed beforehand to codfw to avoid causing issues
> to users. Please refrain from trying to deploy to that cluster during that
> time period.
> ** OKRs in final drafts, reach out if your team requires SRE involvement
>
> == Product ==
>
> === Editing ===
> * Updates:
> ** Preparing to release v1.0 of DiscussionTools to target wikis to discuss
>
> === Growth ===
> * Updates:
> ** Main focus is on releasing the first version of topic matching for
> suggested edits module. Initial release utilizing morelike targeted for
> before All Hands.
>
> === Android native app ===
> * Updates:
> **Preparing for a minor release with some bug fixes and improved language
> variant support. The release candidate is currently in Beta :
> https://play.google.com/store/apps/details?id=org.wikipedia.beta
> **Mobile-html integration is 70% complete. The Android O board with the
> rest of the work will be the next major release: [[phab:project/view/4318]]
>
> === Web ===
> * Updates:
> ** Summary: digging into desktop improvements (DIP).
> ** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector
> / DIP)]]:
> *** [[phab:T232140|Separate out logo handling into square image
> logos and long text/wordmark banner logos]]
> *** [[phab:T240062|Extract components from VectorTemplate to
> Mustache files]]
> *** [[phab:T239248|[EPIC] Divide VectorTemplate into
> components]]
> *** [[phab:T117279|[EPIC] Core should provide inline diffs as well
> as side by side (Move InlineDifferenceEngine into core / remove
> MobileDiff)]]
> *** [[phab:T237561|[SPIKE 10hrs] Investigate how skin suboptions
> can be presented in Special:Preferences]]
> ** Mobile website (MinervaNeue / MobileFrontend):
> *** [[Reading/Web/Advanced_mobile_contributions|Advanced mode]]:
>  [[phab:T240644|Regression: Label is visible on Logout button
> for logged in users on  all wikis (non-AMC) and contribution icon on user
> page]]
>  [[phab:T238364|[Bug] Simplified Talk Page Does Not Support
> Sections With Non-ascii Characters/Several ascii characters aren't
> supported either]]
>  [[phab:T236328|Username should be on its own line (Recent
> changes & Watchlist)]]
> *** Miscellaneous:
>  [[phab:T237050|The `site` and `site.styles` module should be
> explicitly disabled on mobile rather than abuse the targets
> system]]
>  [[phab:T214647|[EPIC] Re-define the contract for displaying
> drawers and overlays in MobileFrontend]]
>  [[phab:T241179|Remove Special:MobileMenu]]
>  [[phab:T240502|Raw HTML in MobileFrontend]]
>  [[phab:T234570|Tech debt: Drop Browser.supportsAnimations
> method]]
>  [[phab:T214049|Technical: Every Drawer has a shield for
> catching clicks]]
>  [[phab:T198265|Special:MobileOptions is empty for third
> parties and when beta is disabled and this is confusing]]
>  [[phab:T171000|[EPIC] Minerva works independently of
> MobileFrontend]]
>  [[phab:T206069|Transition MobileFrontend Gruntfile.js tasks to
> NPM scripts]]
>  [[phab:T140045|Respect
> $wgAllowSiteCSSOnRestrictedPages]]
>
> === Product Infrastructure ===
> * Blocked by:
> ** SRE on buster nodejs10 images for proton. Will resume work this week
>
> === Structured Data ===
> * Blocking:
> ** Search Platform: Data dumps for SDC: [[phab:T221917]]
>
> === Inuka ===
> * Updates:
> ** KaiOS app: read article in another language [[phab:T234628]]
> ** KaiOS app: loading experience [[phab:T240888]]
> ** KaiOS app: navigate to previous article [[phab:T241423]]
> ** KaiOS app: offline mode indicator
>
> == Technology ==
>
> === Fundraising Tech ===
> * Updates:
> ** CiviCRM
> *** Updating Civi version to latest
> *** More improvements to contact de-duplication
> ** Payments-wiki
> *** Implementing iDEAL and recurring card payments via our backup processor
>
> === Core Platform ===
> * Blocked by:
> ** RelEng on Quibble [[phab:T236680]]
> ** Security OAuth 2.0 review [[phab:T239940]]
> * Blocking

[Wikitech-l] Live Incident: Tools.wmflabs.org

[RhinosF1 -]

Hello all,

Please note that all tools.wmflabs.org tools are currently down.

See https://phabricator.wikimedia.org/T234834 for live updates.

Thanks,
RhinosF1
FOSS Developer
-- 
Thanks,
RhinosF1
Mediawiki System Administrator
Miraheze
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia service interruptions; phab task https://phabricator.wikimedia.org/T232224

[RhinosF1]

Good luck to everyone working on this and a virtual drink is waiting for
you when you're done.

RhinosF1

On Fri, 6 Sep 2019 at 21:21, Vi to  wrote:

> We've been under a DDoS attack for more than two hours.
>
> Vito
>
> Il giorno ven 6 set 2019 alle ore 22:20 Pine W  ha
> scritto:
>
> > Discussion in https://phabricator.wikimedia.org/T232224. I had trouble
> > connecting to Phabricator also, so I'm guessing that IRC is a good
> > alternate channel for communications. However, as usual, let's not all
> pile
> > into IRC, email, and/or Phabricator and say "I'm having problems
> connecting
> > to Wikimedia sites" when the technical ops folks are working on this.
> >
> > Regards,
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> > ___
> > 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

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

Re: [Wikitech-l] البحث في الويب باستخدام Chrome

[RhinosF1]

Can we help you?

On Mon, 19 Aug 2019 at 20:41, YAZED sd  wrote:

> https://support.google.com/chrome/answer/95440?hl=ar-AE_topic=6069779
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

Re: [Wikitech-l] Wikiwisdom: A Project Proposal

[RhinosF1]

I'll make sure to have a look, should be quite an interesting idea.

RhinosF1
Miraheze Volunteer

On Thu, 15 Aug 2019 at 21:15, Adam Sobieski 
wrote:

> Wikimedia-l,
> Wikitech-l,
>
> I would like to share a new project proposal:
> https://meta.wikimedia.org/wiki/Wikiwisdom . The project intends to
> provide a large-scale, crowdsourced collection of wisdom materials
> (anecdotes, proverbs, quotations, lyrics, poetry, narratives and humor).
> The project intends to increase the ease with which people can search for,
> discover and share wisdom materials. The project intends to advance
> scholarly and scientific research into wisdom, folklore, heritage,
> tradition, history and culture.
>
> Thank you for taking a look at the project proposal. You may edit the
> project proposal page and add yourself as an interested person. The
> discussion page of the project proposal is also available for discussions.
>
>
> Best regards,
> Adam Sobieski
> http://www.phoster.com/contents/
>
> ___
> 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] Phabricator monthly statistics - 2019-07

[RhinosF1]

Nice to see you guys are fixing UBN tasks in 0 days now even better during
a time where the train keeps getting stalled.

On Thu, 1 Aug 2019 at 01:00,  wrote:

>
> Hi Community Metrics team,
>
> This is your automatic monthly Phabricator statistics mail.
>
> Accounts created in (2019-07): 291
> Active Maniphest users (any activity) in (2019-07): 967
> Task authors in (2019-07): 521
> Users who have closed tasks in (2019-07): 293
>
> Projects which had at least one task moved from one column to another on
> their workboard in (2019-07): 313
>
> Tasks created in (2019-07): 2573
> Tasks closed in (2019-07): 2401
> Open and stalled tasks in total: 42311
>
> Median age in days of open tasks by priority:
>
> Unbreak now: 0
> Needs Triage: 513
> High: 919
> Normal: 1118
> Low: 1531
> Lowest: 1502
>
> (How long tasks have been open, not how long they have had that priority)
>
> Active Differential users (any activity) in (2019-07): 12
>
> TODO: Numbers which refer to closed tasks might not be correct, as
> described in https://phabricator.wikimedia.org/T1003 .
>
> Yours sincerely,
> Fab Rick Aytor
>
> (via community_metrics.sh on phab1003 at Thu Aug  1 00:00:23 UTC 2019)
>
> ___
> 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] Train

[RhinosF1 Wikipedia]

Hi greg,

I did know about the versions tool and checked both to work it out.

I actually was chatting with someone on discord and worked out that it
saying 'all wikis' is from the commit that pushed it which sent 'all wikis'
to .14 even though it only affected group2 as 0 and 1 were already on .14
so just confused me a bit.

Thanks,
RhinosF1

On Thu, 18 Jul 2019 at 22:38, Greg Grossmeier  wrote:

> 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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Train

[RhinosF1 Wikipedia]

Hi,
Am I mistaken that based on
https://phabricator.wikimedia.org/T220739 the train should be fully rolled
back?

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

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

Re: [Wikitech-l] 今週あなたを幸せにするものは何ですか？ / What's making you happy this week? (Week of 16 June 2019)

[RhinosF1 Wikipedia]

I should probably sign up for WikiMedia-l Then.

I quite like these emails.

Thanks,
Pine

On Thu, 20 Jun 2019 at 09:01, Pine W  wrote:

> Brian,
>
> Thanks for the civil comments.
>
> I think that language diversity valuable, and there is no requirement to
> post in English to this list.
>
> Although I appreciate the idea, I am unwilling to create a more narrowly
> focused version of these threads for Wikitech-l. Someone else might be
> willing to do that.
>
> The 2 !votes against and 0 !votes in favor of continuing to cross post
> these threads to Wikitech-l in their current form likely mean that I will
> post these threads only to Wikimedia-l in the future. Although I am mildly
> disappointed, I am OK with that.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
> ___
> 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] 1.34.0-wmf.6 status and cawikinews outage

[RhinosF1 Wikipedia]

Got back on IRC and apergos showed me
https://wikitech.wikimedia.org/wiki/Deployments/One_week which is probably
the most simple.

Thanks all!
And good luck with fixing everything and the remainder of the train.

RhinosF1

On Wed, 22 May 2019 at 18:36, Bryan Davis  wrote:

> On Wed, May 22, 2019 at 10:35 AM Andre Klapper 
> wrote:
> >
> > On Wed, 2019-05-22 at 17:29 +0100, RhinosF1 Wikipedia wrote:
> > > what's on Group 1
> >
> > See the dropdown on https://tools.wmflabs.org/versions/
>
> The TL;DR answer for what is in each group is basically:
> * Group 0 == mediawiki.org, "testing" wikis, and "closed" wikis
> * Group 1 == wikis that are not wikipedias or in group 0
> * Group 2 == wikipedias
>
> There are some more subtle distinctions, but that's the general setup
> of the groups.
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]] Manager, Technical EngagementBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> 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] 1.34.0-wmf.6 status and cawikinews outage

[RhinosF1 Wikipedia]

Looks like IRCCloud is having issues for me, would have asked in -tech but
what's on Group 1

On Wed, 22 May 2019 at 17:14, Antoine Musso  wrote:

> Hello,
>
> When promoting group1 to MediaWiki 1.34.0-wmf.6, cawikinews has been
> unreachable for roughly half an hour.
>
> The reason is that very early in the process of loading the wiki, a PHP
> fatal error occurred.  I thus roll backed cawikinews to 1.34.0-wmf.5
> which fixed it:
>   https://phabricator.wikimedia.org/T224116
>
> Then eventually other wikis have been found to be missing localisation
> strings indicating FlaggedRevs has other issues:
> https://phabricator.wikimedia.org/T224124
>
>
> I am thus rolling back group1 to 1.34.0-wmf.5 until FlaggedRevs is fixed.
>
>
> The root cause is the conversion of MediaWiki extension FlaggedRevs to
> the extension registry system. Apparently some settings are loaded later
> than they used to and cause a Fatal when trying to interact with an
> unset variable.
>
> The task is https://phabricator.wikimedia.org/T224116  If you are
> familiar with operations/mediawiki-config load order and extension
> registry loading, your help will be more than appreciated.
>
>
> --
> Antoine "hashar" Musso
>
>
>
> ___
> 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] Improving the mediawiki.org frontpage: It's available!

[RhinosF1 Wikipedia]

Looks so much cleaner and modern, well done!

On Sat, 13 Apr 2019 at 14:21, Andre Klapper  wrote:

> Hi everybody,
>
> https://www.mediawiki.org has a new frontpage!
>
> Thank you to everyone who provided great feedback and comments on
> https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_improvements_2018
> and
>
> https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_improvements_2018/Proposal
> in the last weeks! Several improvements have been implemented before going
> live.
>
> For a list of potential future work on problems with related pages, see
>
> https://www.mediawiki.org/wiki/MediaWiki/Homepage_improvements_2018#Potential_follow-up_work
>
> Enjoy!
> andre
>
> (This email is a follow-up to the previous three announcements:
> https://lists.wikimedia.org/pipermail/wikitech-l/2018-September/090886.html
> https://lists.wikimedia.org/pipermail/wikitech-l/2018-December/091213.html
> https://lists.wikimedia.org/pipermail/wikitech-l/2019-March/091814.html )
> --
> Andre Klapper | Bugwrangler / Developer Advocate
> https://blogs.gnome.org/aklapper/
>
>
>
> ___
> 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] s3 primary db master failover on Thursday 10th April 05:00AM UTC

[RhinosF1 Wikipedia]

Thanks for the information,
I've seen you've added user notice to the Phab task but as far as I'm aware
that needs to be added asap so it can be translated so I've added it with
https://meta.wikimedia.org/w/index.php?title=Tech/News/2019/15=18991805=18990102

On Fri, 5 Apr 2019 at 07:23, Manuel Arostegui 
wrote:

> Hello,
>
> Due to hardware malfunction on the current s3 database primary master
> (T219115) we need to failover it to a different host.
>
> We are going to do this on Thursday 10th at 05:00 AM UTC, and we have
> requested a 30 minutes window (T220080) as we have to go read only for all
> the wikis living on s3 (P7994).
>
> Impact: Writes will be blocked, reads will remain unaffected.
> Time: 05:00AM UTC - 05:30 AM UTC (we do not expect to use the full 30
> minutes window).
>
> Communication will happen at #wikimedia-operations
> If you are around at that time and want to help with the monitoring, please
> join us!
>
> Thanks
> ___
> 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] Easy list whitelist

[RhinosF1 Wikipedia]

Based on -tech IRC discussion, I'm summing this up @
https://meta.wikimedia.org/wiki/Tech/20190404-Adblock-issue given WikiTech
is currently Account creation locked.

On Thu, 4 Apr 2019 at 21:17, RhinosF1 Wikipedia  wrote:

> Hi Nick,
>
> Thanks for the Clarification, From what I know, the issue was present for
> about 10 hours. I'm not sure how widespread the impact was page wise. Is it
> worth summarising what happened anywhere else?
>
> Thanks,
> RhinosF1
>
> On Thu, 4 Apr 2019 at 21:15, Nick Wilson (Quiddity) 
> wrote:
>
>> Hi RhinosF1,
>> It was only a single webpage that was reported as being blocked by the
>> browser extension (although there were presumably other pages and wikis
>> affected that went unreported in the past), thus it is probably not of
>> great concern to our thousands of contributors who read the short Tech News
>> newsletter. We try to keep the newsletter short and focused on important
>> items of widespread interest, both for ease of translation and so that
>> people read it in full each week. You can read details about what normally
>> gets included at
>> https://meta.wikimedia.org/wiki/Tech/News/For_contributors
>> Cheers,
>>
>>
>> On Thu, Apr 4, 2019 at 12:38 PM RhinosF1 Wikipedia 
>> wrote:
>>
>>> Hi,
>>> Thanks to Nick for the PR.
>>>
>>> As far as I understand, Easy list is some sort of ad blocking system
>>> that multiple ad blockers use.
>>>
>>> From what I can see, Wiktionary got caught up in a block on URLs ending
>>> in /ads and /advert making some pages blank. It's best to read the Tech IRC
>>> log from 4pm onwards to get the idea.
>>>
>>> I'll have a look at Tech News. I'm happy to write a proper report on
>>> what happened if necessary. Where you would suggest posting it? I can't use
>>> Wikitech due to Account Creation block.
>>>
>>> Thanks,
>>> RhinosF1
>>>
>>> On Thu, 4 Apr 2019 at 19:02, Nick Wilson (Quiddity) <
>>> nwil...@wikimedia.org> wrote:
>>>
>>>> Easy List seems to be one of the component in various adblocker tools
>>>> (possibly enabled by default in some or all of them?).
>>>> https://easylist.to/
>>>> E.g. the "uBlock Origin" extension's settings panel which lists it,
>>>> apparently enabled by default:
>>>> https://i.postimg.cc/yN217Tg5/Selection-001.jpg
>>>> I've submitted a pull-request at
>>>> https://github.com/easylist/easylist/pull/3190
>>>> (and +1 to the "please include sufficient context" note :)
>>>>
>>>> On Thu, Apr 4, 2019 at 9:58 AM Andre Klapper 
>>>> wrote:
>>>>
>>>> > On Thu, 2019-04-04 at 16:08 +0100, RhinosF1 Wikipedia wrote:
>>>> > > Could someone please see if WMF wikis could be whitelisted as a
>>>> follow up
>>>> > > to
>>>> > > https://github.com/easylist/easylist/issues/3188?
>>>> >
>>>> > What does that mean? Whitelisting what exactly? Where? Please include
>>>> > sufficient context to allow folks on this list to understand
>>>> relevance.
>>>> >
>>>> > > Despite the short term distruption, Could it be placed on Tech News
>>>> as
>>>> > > users were noticing that some pages were blocked?
>>>> >
>>>> > See https://meta.wikimedia.org/wiki/Tech/News for "Inclusion
>>>> criteria"
>>>> > under "Get started". Obviously I have no idea what "Easy List" is.
>>>> >
>>>> > Cheers,
>>>> > andre
>>>> > --
>>>> > Andre Klapper | Bugwrangler / Developer Advocate
>>>> > https://blogs.gnome.org/aklapper/
>>>> >
>>>> >
>>>> >
>>>> > ___
>>>> > Wikitech-l mailing list
>>>> > Wikitech-l@lists.wikimedia.org
>>>> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>>
>>>>
>>>>
>>>> --
>>>> Nick "Quiddity" Wilson (he/him)
>>>> Community Engagement - Documentation
>>>> Wikimedia Foundation
>>>> ___
>>>> Wikitech-l mailing list
>>>> Wikitech-l@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>
>>>
>>
>> --
>> Nick "Quiddity" Wilson (he/him)
>> Community Engagement - Documentation
>> Wikimedia Foundation
>>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Easy list whitelist

[RhinosF1 Wikipedia]

Hi Nick,

Thanks for the Clarification, From what I know, the issue was present for
about 10 hours. I'm not sure how widespread the impact was page wise. Is it
worth summarising what happened anywhere else?

Thanks,
RhinosF1

On Thu, 4 Apr 2019 at 21:15, Nick Wilson (Quiddity) 
wrote:

> Hi RhinosF1,
> It was only a single webpage that was reported as being blocked by the
> browser extension (although there were presumably other pages and wikis
> affected that went unreported in the past), thus it is probably not of
> great concern to our thousands of contributors who read the short Tech News
> newsletter. We try to keep the newsletter short and focused on important
> items of widespread interest, both for ease of translation and so that
> people read it in full each week. You can read details about what normally
> gets included at
> https://meta.wikimedia.org/wiki/Tech/News/For_contributors
> Cheers,
>
>
> On Thu, Apr 4, 2019 at 12:38 PM RhinosF1 Wikipedia 
> wrote:
>
>> Hi,
>> Thanks to Nick for the PR.
>>
>> As far as I understand, Easy list is some sort of ad blocking system that
>> multiple ad blockers use.
>>
>> From what I can see, Wiktionary got caught up in a block on URLs ending
>> in /ads and /advert making some pages blank. It's best to read the Tech IRC
>> log from 4pm onwards to get the idea.
>>
>> I'll have a look at Tech News. I'm happy to write a proper report on what
>> happened if necessary. Where you would suggest posting it? I can't use
>> Wikitech due to Account Creation block.
>>
>> Thanks,
>> RhinosF1
>>
>> On Thu, 4 Apr 2019 at 19:02, Nick Wilson (Quiddity) <
>> nwil...@wikimedia.org> wrote:
>>
>>> Easy List seems to be one of the component in various adblocker tools
>>> (possibly enabled by default in some or all of them?).
>>> https://easylist.to/
>>> E.g. the "uBlock Origin" extension's settings panel which lists it,
>>> apparently enabled by default:
>>> https://i.postimg.cc/yN217Tg5/Selection-001.jpg
>>> I've submitted a pull-request at
>>> https://github.com/easylist/easylist/pull/3190
>>> (and +1 to the "please include sufficient context" note :)
>>>
>>> On Thu, Apr 4, 2019 at 9:58 AM Andre Klapper 
>>> wrote:
>>>
>>> > On Thu, 2019-04-04 at 16:08 +0100, RhinosF1 Wikipedia wrote:
>>> > > Could someone please see if WMF wikis could be whitelisted as a
>>> follow up
>>> > > to
>>> > > https://github.com/easylist/easylist/issues/3188?
>>> >
>>> > What does that mean? Whitelisting what exactly? Where? Please include
>>> > sufficient context to allow folks on this list to understand relevance.
>>> >
>>> > > Despite the short term distruption, Could it be placed on Tech News
>>> as
>>> > > users were noticing that some pages were blocked?
>>> >
>>> > See https://meta.wikimedia.org/wiki/Tech/News for "Inclusion criteria"
>>> > under "Get started". Obviously I have no idea what "Easy List" is.
>>> >
>>> > Cheers,
>>> > andre
>>> > --
>>> > Andre Klapper | Bugwrangler / Developer Advocate
>>> > https://blogs.gnome.org/aklapper/
>>> >
>>> >
>>> >
>>> > ___
>>> > Wikitech-l mailing list
>>> > Wikitech-l@lists.wikimedia.org
>>> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>
>>>
>>>
>>> --
>>> Nick "Quiddity" Wilson (he/him)
>>> Community Engagement - Documentation
>>> Wikimedia Foundation
>>> ___
>>> Wikitech-l mailing list
>>> Wikitech-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>>
>
> --
> Nick "Quiddity" Wilson (he/him)
> Community Engagement - Documentation
> Wikimedia Foundation
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Easy list whitelist

[RhinosF1 Wikipedia]

Hi,
Thanks to Nick for the PR.

As far as I understand, Easy list is some sort of ad blocking system that
multiple ad blockers use.

From what I can see, Wiktionary got caught up in a block on URLs ending in
/ads and /advert making some pages blank. It's best to read the Tech IRC
log from 4pm onwards to get the idea.

I'll have a look at Tech News. I'm happy to write a proper report on what
happened if necessary. Where you would suggest posting it? I can't use
Wikitech due to Account Creation block.

Thanks,
RhinosF1

On Thu, 4 Apr 2019 at 19:02, Nick Wilson (Quiddity) 
wrote:

> Easy List seems to be one of the component in various adblocker tools
> (possibly enabled by default in some or all of them?).
> https://easylist.to/
> E.g. the "uBlock Origin" extension's settings panel which lists it,
> apparently enabled by default:
> https://i.postimg.cc/yN217Tg5/Selection-001.jpg
> I've submitted a pull-request at
> https://github.com/easylist/easylist/pull/3190
> (and +1 to the "please include sufficient context" note :)
>
> On Thu, Apr 4, 2019 at 9:58 AM Andre Klapper 
> wrote:
>
> > On Thu, 2019-04-04 at 16:08 +0100, RhinosF1 Wikipedia wrote:
> > > Could someone please see if WMF wikis could be whitelisted as a follow
> up
> > > to
> > > https://github.com/easylist/easylist/issues/3188?
> >
> > What does that mean? Whitelisting what exactly? Where? Please include
> > sufficient context to allow folks on this list to understand relevance.
> >
> > > Despite the short term distruption, Could it be placed on Tech News as
> > > users were noticing that some pages were blocked?
> >
> > See https://meta.wikimedia.org/wiki/Tech/News for "Inclusion criteria"
> > under "Get started". Obviously I have no idea what "Easy List" is.
> >
> > Cheers,
> > andre
> > --
> > Andre Klapper | Bugwrangler / Developer Advocate
> > https://blogs.gnome.org/aklapper/
> >
> >
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> Nick "Quiddity" Wilson (he/him)
> Community Engagement - Documentation
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Easy list whitelist

[RhinosF1 Wikipedia]

Hi,
Could someone please see if WMF wikis could be whitelisted as a follow up
to
https://github.com/easylist/easylist/issues/3188?

Despite the short term distruption, Could it be placed on Tech News as
users were noticing that some pages were blocked?

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

Re: [Wikitech-l] Phabricator Login Error

[RhinosF1 Wikipedia]

Thanks!

On Thu, 4 Apr 2019 at 10:03, RhinosF1 Wikipedia  wrote:

> Ok, thanks for the clarification.
>
> User is still in -tech channel. I've looked through the Phab Admin list
> and it looks like most are US/Canda based so they might be best waiting
> until later.
>
> Thanks for the help
>
> On Thu, 4 Apr 2019 at 09:59, K. Peachey  wrote:
>
>> It's been used on and off as required for the past few years.
>>
>> On Thu, 4 Apr 2019 at 18:55, RhinosF1 Wikipedia 
>> wrote:
>> >
>> > Do we know when it was implemented and why? Is it part of the response
>> to earlier security issues?
>> >
>> > On Thu, 4 Apr 2019 at 09:51, K. Peachey  wrote:
>> >>
>> >> It's a anti-spam measure, One of the Phab administrators will approve
>> >> when available.
>> >>
>> >> On Thu, 4 Apr 2019 at 18:28, RhinosF1 Wikipedia 
>> wrote:
>> >> >
>> >> > Hi all,
>> >> > Is there any reason Phabricator accounts would be marked not
>> approved?
>> >> > I've not noticed this happening before but there's been a report on
>> IRC
>> >> > (see
>> >> > https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
>> >> > https://phabricator.wikimedia.org/p/Dusti/ saying they are getting
>> the
>> >> > error:  'Your account has been created, but needs to be approved by
>> an
>> >> > administrator. You'll receive an email once your account is
>> approved.' (see
>> >> > https://snag.gy/InXbLz.jpg)
>> >> >
>> >> >
>> >> > Can someone approve and clarify what's happened?
>> >> > ___
>> >> > 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phabricator Login Error

[RhinosF1 Wikipedia]

Ok, thanks for the clarification.

User is still in -tech channel. I've looked through the Phab Admin list and
it looks like most are US/Canda based so they might be best waiting until
later.

Thanks for the help

On Thu, 4 Apr 2019 at 09:59, K. Peachey  wrote:

> It's been used on and off as required for the past few years.
>
> On Thu, 4 Apr 2019 at 18:55, RhinosF1 Wikipedia 
> wrote:
> >
> > Do we know when it was implemented and why? Is it part of the response
> to earlier security issues?
> >
> > On Thu, 4 Apr 2019 at 09:51, K. Peachey  wrote:
> >>
> >> It's a anti-spam measure, One of the Phab administrators will approve
> >> when available.
> >>
> >> On Thu, 4 Apr 2019 at 18:28, RhinosF1 Wikipedia 
> wrote:
> >> >
> >> > Hi all,
> >> > Is there any reason Phabricator accounts would be marked not approved?
> >> > I've not noticed this happening before but there's been a report on
> IRC
> >> > (see
> >> > https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
> >> > https://phabricator.wikimedia.org/p/Dusti/ saying they are getting
> the
> >> > error:  'Your account has been created, but needs to be approved by an
> >> > administrator. You'll receive an email once your account is
> approved.' (see
> >> > https://snag.gy/InXbLz.jpg)
> >> >
> >> >
> >> > Can someone approve and clarify what's happened?
> >> > ___
> >> > 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phabricator Login Error

[RhinosF1 Wikipedia]

Do we know when it was implemented and why? Is it part of the response to
earlier security issues?

On Thu, 4 Apr 2019 at 09:51, K. Peachey  wrote:

> It's a anti-spam measure, One of the Phab administrators will approve
> when available.
>
> On Thu, 4 Apr 2019 at 18:28, RhinosF1 Wikipedia 
> wrote:
> >
> > Hi all,
> > Is there any reason Phabricator accounts would be marked not approved?
> > I've not noticed this happening before but there's been a report on IRC
> > (see
> > https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
> > https://phabricator.wikimedia.org/p/Dusti/ saying they are getting the
> > error:  'Your account has been created, but needs to be approved by an
> > administrator. You'll receive an email once your account is approved.'
> (see
> > https://snag.gy/InXbLz.jpg)
> >
> >
> > Can someone approve and clarify what's happened?
> > ___
> > 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Phabricator Login Error

[RhinosF1 Wikipedia]

Hi all,
Is there any reason Phabricator accounts would be marked not approved?
I've not noticed this happening before but there's been a report on IRC
(see
https://wm-bot.wmflabs.org/logs/%23wikimedia-tech/20190404.txt) by
https://phabricator.wikimedia.org/p/Dusti/ saying they are getting the
error:  'Your account has been created, but needs to be approved by an
administrator. You'll receive an email once your account is approved.' (see
https://snag.gy/InXbLz.jpg)


Can someone approve and clarify what's happened?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l