[Wikitech-l] Fwd: [MediaWiki-l] New version of "Working with MediaWiki" released

2020-06-03 Thread Pine W
Forwarding.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Yaron Koren 
Date: Wed, Jun 3, 2020 at 8:42 PM
Subject: [MediaWiki-l] New version of "Working with MediaWiki" released
To: MediaWiki announcements and site admin list



Hi everyone,

I'm excited to announce that a new version of my MediaWiki reference book,
"Working with MediaWiki", has just been released.

To briefly recap: the first edition came out in 2012, and then an updated
version in 2014; then the 2nd edition came out in 2017, and this is an
updated version of the 2nd edition. For this new version, a lot of the text
and screenshots were updated, to reflect changes to core MediaWiki and its
extensions over the last three years.

As with the earlier version, the entire text of the book can be read for
free online:

https://workingwithmediawiki.com/book/

(That website used to be slow at times, but it's on a different server now
and should be fine.)

Of course, there's nothing like reading an actual printed book, and, though
it's never been available in stores, you can order the book online from
Amazon. Just follow the links from here:

https://workingwithmediawiki.com/

That's it, and I hope people enjoy the book!

-Yaron

--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
___
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

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

Re: [Wikitech-l] "Library" for sharing useful resources for learning technical topics

2020-05-28 Thread Pine W
Hi Amir,

This sounds like a good idea.

For what it's worth, on Meta there is the Learning Patterns Library at
https://meta.wikimedia.org/wiki/Learning_patterns. Perhaps a technical
resource library could be integrated into the LPL, or a technical
resource library could borrow ideas from the LPL.

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

Re: [Wikitech-l] Wikimedia Café online meeting for May 2020

2020-05-28 Thread Pine W
你好,*

A reminder that this month's Wikimedia Café will start 48 hours from now.

This month's meetup will focus on the recently announced 2030 strategy
recommendations. (See
https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations.)
Mehrdad Pourzaki, who is the Information and Knowledge Manager for the
Movement Strategy Core Team, will join us at this month's Café.

More information, and instructions for how to join the meetup, are at
https://meta.wikimedia.org/wiki/Wikimedia_Café.

Nosotros hablaremos pronto,**

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

* "Hello" in Chinese
** "We'll talk soon" in Spanish

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

[Wikitech-l] Fwd: [Wikimedia-l] Language Showcase, May 2020

2020-05-25 Thread Pine W
Forwarding.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Amir E. Aharoni 
Date: Mon, May 25, 2020 at 7:22 PM
Subject: [Wikimedia-l] Language Showcase, May 2020
To: wikimedia-l 


Hello,

This is an announcement about a new installment of the Language Showcase, a
series of presentations about various aspects of language diversity and its
connection to Wikimedia Projects.

This new installment will deal with the latest design research about the
upcoming section translation feature for Content Translation.

This session is going to be broadcast over Zoom, and a recording will be
published for later viewing. You can also participate in the conversation
on IRC or with us on the Zoom meeting.

Please read below for the event details, including local time, joining
links and do let us know if you have any questions.

Thank you!

Amir

== Details ==

# Event: Language Showcase #5

# When: May 27, 2020 (Wednesday) at 13:00 UTC (check local time
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200527T1300 )

# Where:

Join Zoom Meeting
https://wikimedia.zoom.us/j/9708103

Meeting ID: 970 8103 

IRC - #wikimedia-office (on Freenode)

# Agenda:

The latest design research about the upcoming section translation feature
for Content Translation.

--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


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

[Wikitech-l] Fwd: [Wikimedia-l] Etherpad upgrade and a new skin

2020-05-20 Thread Pine W
Forwarding an announcement. Feedback can go to Alexandros, who may or
may not be subscribed to a mailing list where you see this email, so
if you have something to say on list you may also want to include
Alexandros' email address in the to: field. (By the way, on one
previous occasion I saw a small number of highly hostile messages
being directed at WMF staff regarding a UI change that I thought was
reasonable. If you are a community member and something about this UI
change upsets you, please vent to me first and then after you have
finished venting you can send a calmer version of your message to
Alexandros.)

Thanks,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Alexandros Kosiaris 
Date: Tue, May 19, 2020 at 10:29 AM
Subject: [Wikimedia-l] Etherpad upgrade and a new skin
To: Wikimedia Mailing List 
Cc: Foundation Optional 


Hello everyone,

I normally don't send out emails like this when we upgrade etherpad,
but 1.8.4 (which we just upgraded to), has brought in a UI change (one
that was introduced in 1.8.3) which, in my opinion, warrants a heads
up so that people aren't caught off guard. Etherpad-lite now has had a
new skin and that's what you will experience while using it. There's
also a number of other changes, you can have a quick look at
https://github.com/ether/etherpad-lite/blob/develop/CHANGELOG.md if
you are interested.

Regards,

--
Alexandros Kosiaris
Principal Site Reliability Engineer
Wikimedia Foundation

___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


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

Re: [Wikitech-l] Wikimedia Café online meeting for May 2020

2020-05-16 Thread Pine W
I remembered to adjust US Pacific time for DST but forgot to do the
same for US Eastern time. The US Eastern time will be 12:30. Sorry
about that.

As you may have noticed, we are holding the UTC constant regardless of
DST changes.

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] Wikimedia Café online meeting for May 2020

2020-05-16 Thread Pine W
Hello colleagues,


== Announcements for this month ==

The next Wikimedia Café meetup will occur on 30 May 2020 at 9:30 AM
Pacific / 11:30 AM Eastern / 4:30 PM UTC / 10 PM IST.

This month's meetup will focus on the recently announced 2030 strategy
recommendations. See
https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations.

The organizers of the Café have not finalized the format for this
month, but this is likely to be a two hour meetup with time for
discussions regarding each of the strategy recommendations.

The Café has been well attended during the past few months. There have
been multiple requests for an alternate meetup time for the Café. This
subject is being discussed on the Café talk page, and is also on the
agenda for May's meetup. One possibility under consideration is
offering an additional Café meetup on a different day of the week and
a different time of day. Please feel free to join the discussion on
the talk page if you cannot attend the Café in its current time slot
and would like to comment regarding this issue.


== General information about the Café ==

More information regarding the agenda and links to strategy documents
are available at https://meta.wikimedia.org/wiki/Wikimedia_Café.

As usual, the meeting style for the Café will emphasize discussion
rather than presentation. People are welcome to participate as
listeners only if they prefer.

Please see the page on Meta for more information about the Café.
Please watch the page for any updates, particularly to the schedule or
the agenda. Signing up for the meeting is optional, but is helpful to
the organizers so that we can estimate how many people will attend.
Signing up for the meeting also informs us who we should notify
individually if there are significant changes.

If there are any problems with connecting to the meeting or if you
have any questions or comments, then please write on the Meta talk
page or send me an email.


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

Re: [Wikitech-l] New Feature from Community Tech: Enhanced Password Reset

2020-05-11 Thread Pine W
Thank you. I'm short on good news at the moment, and this is nice to see.

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] Fwd: [Talk-us] OSM Foundation’s Call for Microgrant Applications

2020-05-01 Thread Pine W
Forwarding.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Clifford Snow 
Date: Sat, Apr 25, 2020 at 8:06 PM
Subject: [Talk-us] OSM Foundation’s Call for Microgrant Applications
To: talk-us 


In case you missed this announcement, I'm reposting it on talk-us mailing list.


2020 will be the first year that the OSM Foundation operates the new
microgrants project. In the coming weeks, we hope to hear from you
about a bold, community-driven, and impactive OpenStreetMap project
idea that will benefit from a microgrant of up to 5000 euros. We
welcome a broad range of projects, with the minimum requirement being
a clear connection to OpenStreetMap.


What is a microgrant? In our case, it is a modest amount of funds
awarded to applicants in order to fund direct expenses of a project.
For an idea of successful projects, you can take a look at the
Humanitarian OpenStreetMap Team’s 2019 microgrant awardees. Keep in
mind that the OSMF has a wider focus than the humanitarian sector,
spanning our global community, and welcomes applications with any
focus that relates to OpenStreetMap. We particularly encourage
applicants to consider the core values from the OSMF’s mission
statement and how any microgrant work can incorporate them.

The OSMF Microgrant Program focuses on simple grant proposals, and we
will swiftly decide on what to fund. Our goal is to avoid a
complicated and long application and decision process. You should
submit a brief and concise proposal, and we plan to quickly announce
the awardees.

We encourage submissions from individuals, groups, and organizations
who have a clear idea they want to pursue. Each project should be
completed within 12 months of the microgrant being awarded this
spring. Microgrants are open to all OSMF members, and can be submitted
in any language. If you are not yet a member of OSMF then you can
apply to join up until the time you submit a microgrant application,
and be eligible for an award. Please note there is a fee waiver
program that may allow you to join the OSMF at no cost.


In light of the ongoing health crisis regarding COVID19, we will not
be awarding microgrants for projects which require offline group
gatherings and in person meetings, although these ideas are certainly
valuable for future rounds.

Funding can be used for a variety of purposes. You may need tools and
supplies for mapping activity, funds for training materials,
technology expenses for a series of virtual mapathons, prizes for an
online coding, mapping, or writing contest, and many more examples.
Please embrace your own creativity and not feel limited by the range
of examples.


We encourage you to consult with your local OpenStreetMap community
when planning a microgrant application, and make sure you adhere to
community guidelines in the scope of the project. If accepted for a
microgrant, you will be responsible for reporting progress, signing a
grant agreement, and making sure to follow the detailed microgrant
rules. It is strongly suggested that your project uses the funding to
enable volunteer work to have a wider and stronger impact than it
would without funding.

The call for microgrants will open on April 19th, 2020 and we will
continue to accept applications through May 10th, 2020. In order to
submit,  visit the OSM Wiki page and click on “Start your application”
to enter the template. When this is complete, send a message to
microgrants at osmfoundation.org. We also encourage sharing your
application on osmf-talk when it is submitted. If you need help with
the submission process, please feel free to contact the Microgrants
Committee for help. If you don’t have enough time to prepare your plan
and application, please consider submitting it in a possible future
round of microgrants.


Once the submission period closes on May 10th, we invite the community
to review the complete list of submissions and provide feedback on the
wiki page. We also will accept feedback by email to microgrants at
osmfoundation.org and via osmf-talk.


Complete timeline:

April 19: call for microgrant applications opens

May 10: final date for submission (23:59 Pacific Time Zone, USA).

May 10-TBD: community feedback period

Late May: announcement of awards

For more details, see the complete rules and guidelines on the OSM
wiki and contact us at microgrants at osmfoundation.org with any
questions. This is the first time the OSMF is sponsoring such an
activity, and we look forward to learning together about how this
benefits our community and how to build a transparent, effective, and
inclusive microgrants program for everyone involved. We are grateful
for the opportunity to make funds available to the community and hope
to hear your ideas in the coming weeks.


Clifford

Member of the OSMF Microgrants Committee



--
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list

[Wikitech-l] Fwd: [Wikimedia-l] Fwd: Wikimedia Café - Sat 25 April 2020...

2020-04-22 Thread Pine W
Forwarding to Wikitech-l. Sorry about the late notice this month.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Lane Rasberry 
Date: Wed, Apr 22, 2020 at 9:29 AM
Subject: [Wikimedia-l] Fwd: Wikimedia Café - Sat 25 April 2020...
To: Wikimedia Mailing List 


Hello,

I am writing to invite anyone to join the next online meeting of Wikimedia
Café on Saturday 25 April 2020 4:30 PM UTC. Details for joining are at
https://meta.wikimedia.org/wiki/Wikimedia_Café
> (video room open at that time) https://virginia.zoom.us/my/wikilgbt

The agenda for this month includes discussing maps on Wikipedia and
Wikimedia community fundraising outside the Wikimedia Foundation.

Wikimedia Café is a modest, one-hour, monthly online meeting which for the
past few months has had fewer than 10 attendees. At these meetings anyone
can propose to discuss any topic of broad Wikimedia community interest, as
if we all were able to meet in person over coffee. The meetings themselves
are an experiment in small group Wikimedia community conversation with
video chat, phone access options, and online shared notetaking. Please see
WikiProject Remote Event Participation for more information about this
general style of online event.
https://meta.wikimedia.org/wiki/WikiProject_remote_event_participation

   - Anyone interested in joining may do so.
   - Anyone interested in reading notes of past meetings can find them on
   the meta page.
   - If there is anyone who wants to get their ideas published in the wiki
   world, consider looking at how this Café works, because voice chat with
   notetaking could be a way to organize your own wiki community.

Thanks Pine for performing as host in this and thanks to anyone who submits
topics for discussion or who is able to join.

--
Lane Rasberry
user:bluerasberry on Wikipedia
206.801.0814
l...@bluerasberry.com
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


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

Re: [Wikitech-l] [Wikimedia Technical Talks] Understanding Wikimedia Maps and its challenges, 25 March 2020 at 5 PM UTC

2020-03-28 Thread Pine W
Hi ACN,

I am thinking about including the video in a piece for The Signpost, but if
importing the video from YouTube to Commons would be very time consuming,
then I'm OK with skipping that.

Looking at a bigger picture, a question is how much use of proprietary
services should be required for Wikimedia activities or to obtain Wikimedia
content. That's a complicated question and I'd prefer not to go into that
deeply at this time, but I'm aware of some of the issues.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Fri, Mar 27, 2020 at 1:58 AM AntiCompositeNumber <
anticompositenum...@gmail.com> wrote:

> There's not usually a compelling reason to put an hour-long talk
> recording on Commons. I'm sure it could be arranged if there's a need
> for it.
>
> On Thu, Mar 26, 2020 at 4:56 PM Pine W  wrote:
> >
> > Hi Sarah,
> >
> > Thanks for sharing this announcement. Will the video also be published
> > to Commons?
> >
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> > On Tue, Mar 24, 2020 at 3:56 PM Sarah R  wrote:
> > >
> > > Hi All,
> > >
> > > Just a reminder that we will be broadcasting this Technical Talk on *25
> > > March 2020 at 5 PM UTC*.
> > >
> > > Please note the time has shifted by an hour to reflect daylight savings
> > > time.
> > >
> > > Many kindnesses,
> > >
> > > Sarah R.
> > >
> > > On Tue, Mar 10, 2020 at 11:16 AM Sarah R 
> wrote:
> > >
> > > > Hello Everyone,
> > > >
> > > > It's time for Wikimedia Tech Talks 2020 Episode 2! This talk will
> take
> > > > place on *25 March 2020 at 6 PM UTC*.
> > > >
> > > > *Title: *Understanding Wikimedia Maps and its challenges
> > > >
> > > > *Speaker:*  Mateus Santos, Software Engineer
> > > >
> > > > *Summary: *The WMF Product Infrastructure Team has been maintaining
> the
> > > > Wikimedia Maps service for the last year and a half with help from
> SRE.
> > > > This talk will share the challenges and work of creating a better
> > > > development environment to enhance productivity, solve technical
> debt and
> > > > keep up with platform modernization.
> > > >
> > > > The link to the Youtube Livestream can be found here:
> > > > https://www.youtube.com/watch?v=2LH-pYdi9Ks
> > > >
> > > > During the live talk, you are invited to join the discussion on IRC
> at
> > > > #wikimedia-office
> > > >
> > > > You can watch past Tech Talks here:
> > > > https://www.mediawiki.org/wiki/Tech_talks
> > > >
> > > > If you are interested in giving your own tech talk, you can learn
> more
> > > > here:
> > > >
> https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Tech_talks
> > > >
> > > > Note: This is a public talk. Feel free to distribute through
> appropriate
> > > > email and social channels!
> > > >
> > > > Kindly,
> > > >
> > > > Sarah R. Rodlund
> > > > Technical Writer, Developer Advocacy
> > > > <https://meta.wikimedia.org/wiki/Developer_Advocacy>
> > > > srodl...@wikimedia.org
> > > >
> > >
> > >
> > > --
> > > Sarah R. Rodlund
> > > Technical Writer, Developer Advocacy
> > > <https://meta.wikimedia.org/wiki/Developer_Advocacy>
> > > srodl...@wikimedia.org
> > >
> > >
> > > *“I am a jug filled with water both magic and plain; I have only to
> lean
> > > over, and a stream of beautiful thoughts flows out of me.” *
> > >
> > > ― Bohumil Hrabal, Too Loud a Solitude
> > > ___
> > > 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] [Wikimedia Technical Talks] Understanding Wikimedia Maps and its challenges, 25 March 2020 at 5 PM UTC

2020-03-26 Thread Pine W
Hi Sarah,

Thanks for sharing this announcement. Will the video also be published
to Commons?

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Tue, Mar 24, 2020 at 3:56 PM Sarah R  wrote:
>
> Hi All,
>
> Just a reminder that we will be broadcasting this Technical Talk on *25
> March 2020 at 5 PM UTC*.
>
> Please note the time has shifted by an hour to reflect daylight savings
> time.
>
> Many kindnesses,
>
> Sarah R.
>
> On Tue, Mar 10, 2020 at 11:16 AM Sarah R  wrote:
>
> > Hello Everyone,
> >
> > It's time for Wikimedia Tech Talks 2020 Episode 2! This talk will take
> > place on *25 March 2020 at 6 PM UTC*.
> >
> > *Title: *Understanding Wikimedia Maps and its challenges
> >
> > *Speaker:*  Mateus Santos, Software Engineer
> >
> > *Summary: *The WMF Product Infrastructure Team has been maintaining the
> > Wikimedia Maps service for the last year and a half with help from SRE.
> > This talk will share the challenges and work of creating a better
> > development environment to enhance productivity, solve technical debt and
> > keep up with platform modernization.
> >
> > The link to the Youtube Livestream can be found here:
> > https://www.youtube.com/watch?v=2LH-pYdi9Ks
> >
> > During the live talk, you are invited to join the discussion on IRC at
> > #wikimedia-office
> >
> > You can watch past Tech Talks here:
> > https://www.mediawiki.org/wiki/Tech_talks
> >
> > If you are interested in giving your own tech talk, you can learn more
> > here:
> > https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Tech_talks
> >
> > Note: This is a public talk. Feel free to distribute through appropriate
> > email and social channels!
> >
> > Kindly,
> >
> > Sarah R. Rodlund
> > Technical Writer, Developer Advocacy
> > 
> > srodl...@wikimedia.org
> >
>
>
> --
> Sarah R. Rodlund
> Technical Writer, Developer Advocacy
> 
> srodl...@wikimedia.org
>
>
> *“I am a jug filled with water both magic and plain; I have only to lean
> over, and a stream of beautiful thoughts flows out of me.” *
>
> ― Bohumil Hrabal, Too Loud a Solitude
> ___
> 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] Fwd: [Wikimedia-l] Wikimedia Café - Sat 28 March 2020...

2020-03-20 Thread Pine W
Hello,

I'm forwarding an invitation to the Wikimedia Café meetup for this month.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Lane Rasberry 
Date: Sun, Mar 15, 2020 at 10:43 PM
Subject: [Wikimedia-l] Wikimedia Café - Sat 28 March 2020...
To: Wikimedia Mailing List 


>
> Hello,

I am writing to invite anyone to join the next online meeting of Wikimedia
Café on Saturday 28 March 2020 4:30 PM UTC. Details for joining are at
https://meta.wikimedia.org/wiki/Wikimedia_Café
> (video room open at that time) https://virginia.zoom.us/my/wikilgbt

The agenda for this month includes discussing COVID-19 and Wikipedia and
how Wikimedia community members feel about WMF/community relations.

Wikimedia Café is a modest, one-hour, monthly online meeting which for the
past few months has had fewer than 10 attendees. At these meetings anyone
can propose to discuss any topic of broad Wikimedia community interest, as
if we all were able to meet in person over coffee. The meetings themselves
are an experiment in small group Wikimedia community conversation with
video chat, phone access options, and online shared notetaking. Please see
WikiProject Remote Event Participation for more information about this
general style of online event.
https://meta.wikimedia.org/wiki/WikiProject_remote_event_participation

   - Anyone interested in joining may do so.
   - Anyone interested in reading notes of past meetings can find them on
   the meta page.
   - If there is anyone who wants to get their ideas published in the wiki
   world, consider looking at how this Café works, because voice chat with
   notetaking could be a way to organize your own wiki community.

Thanks Pine for performing as host in this and thanks to anyone who submits
topics for discussion or who is able to join.

--
Lane Rasberry
user:bluerasberry on Wikipedia
206.801.0814
l...@bluerasberry.com
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,


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

[Wikitech-l] Thank you for the reliability and performance of WMF technical infrastructure

2020-03-20 Thread Pine W
Hello,

This is a brief and very unofficial note to say thanks for what
appears to be good reliability and performance of WMF's technical
infrastructure during the current global public health environment and
the swarms of contributing and reading activity on ENWP and elsewhere.

My guess is that there are many dashboards that show how site
performance and reliability are doing. At a convenient time, perhaps
for the upcoming issue of The Signpost, I'd be interested in seeing a
report regarding how the infrastructure is handling the situation.

Ever onward,

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

Re: [Wikitech-l] MediaWiki API pageview issue

2020-02-23 Thread Pine W
Hi James,

I was aware of the first issue, but this is the first time that I can
recall hearing about the second. See
https://phabricator.wikimedia.org/T121912. You may want to ask your
second question in that thread if no one responds to it here.

Good luck,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Mon, Feb 24, 2020 at 12:17 AM James Gardner via Wikitech-l
 wrote:
>
> Hi all,
>
> We are a group of undergraduates working on a project using the MediaWiki
> API. While working on this project, we ran into a unique issue involving
> pageviews. When trying to pull pageview data for a particular page, the
> redirects of a page would not be counted along with the original pageviews.
> For example, the Hong Kong protests page only has direct views, and not
> views from previous titles.
>
> We attempted to use the wmflabs.org tool, but it only shows data from a
> certain date. (Example link:
> https://tools.wmflabs.org/pageviews/?project=en.wikipedia.org=all-access=user=2019-07-01=2020-01-25=2019%E2%80%9320_Hong_Kong_protests|China
> 
> )
>
> Then we attempted to use the redirects of a page and using the old page ids
> to grab the pageview data, but there was no data returned. When we
> attempted to grab data for a page that we knew would have a long past, but
> the parameter of "pvipcontinue" did not appear (
> https://www.mediawiki.org/w/api.php?action=help=query%2Bpageviews).
> (Example:
> https://www.mediawiki.org/wiki/Special:ApiSandbox#action=query=json=pageviews=MediaWiki=pageviews=60=
> )
>
> In the end, we are trying to get an accurate count of view for a certain
> page no matter the source.
>
> Any guidance or assistance is greatly appreciated.
>
> Thanks,
> Jackie, James, Junyi, Kirby
> ___
> 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] [WikimediaMobile] Commons app Android... and iOS!

2020-02-23 Thread Pine W
تريما کاسيه‎.*

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

* I think that this is Malay for "thank you". See
https://en.wiktionary.org/wiki/terima_kasih.

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

[Wikitech-l] Reminder: Wikimedia Café online meeting for February 2020 with focus on the 2030 strategy

2020-02-13 Thread Pine W
Hello colleagues,

This is a reminder that this month's Wikimedia Café will start
approximately 48 hours from now.

--

Hello colleagues,

The February 2020 Wikimedia Café meetup will occur on 15 February 2020
at 8:30 AM PST / 11:30 AM EST / 4:30 PM UTC / 10 PM IST. The date is
earlier than usual in the month due to scheduling constraints.

This month's meetup will focus on the 2030 strategy recommendations,
and will be divided into two discussions of one hour each.

More information regarding the agenda and links to strategy documents
are available at https://meta.wikimedia.org/wiki/Wikimedia_Café.

As usual, the meeting style for the Café will emphasize discussion
rather than presentation. People are welcome to participate as
listeners only if they prefer.

Please see the page on Meta for more information about the Café.
Please watch the page for any updates, particularly to the schedule or
the agenda. Signing up for the meeting is optional, but is helpful to
the organizers so that we can estimate how many people will attend.
Signing up for the meeting also informs us who we should notify
individually if there are significant changes.

If there are any problems with connecting to the meeting or if you
have any questions or comments then please write on the Meta talk
page.

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] Fwd: [Wiki-research-l] TIB Hannover searches for Semantic MediaWiki Engineer

2020-02-05 Thread Pine W
Forwarding a job posting.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Hagemann-Wilholt, Stephanie 
Date: Wed, Feb 5, 2020 at 1:53 PM
Subject: [Wiki-research-l] TIB Hannover searches for Semantic MediaWiki Engineer
To: 


Dear colleagues,

Leibniz Information Centre for Science and Technology - Technische
Informationsbibliothek (TIB)   searches a
Semantic MediaWiki Engineer (m/f/d) to work in the Data Science &
Digital Libraries Research Group

 (Prof. Dr. Sören Auer) at the next possible date. The job position
includes working in the development of innovative services for the
research community.

TIB offers a creative, academic as well as family friendly work
environment in Hannover, Germany. Here, You can find more information
on the job position:
https://www.tib.eu/en/tib/careers-and-apprenticeships/vacancies/details/job-advertisement-no-92020/.

Best regards

Dr. Stephanie Hagemann-Wilholt

Referat PID- und Metadatenservices

Technische Informationsbibliothek (TIB) // German National Library of
Science and Technology

Welfengarten 1 B, 30167 Hannover

Tel.: +49 (0)511 762-14226 // Fax: +49 (0)511 762-14237// E-Mail:
stephanie.hagem...@tib.eu 

https://www.tib.eu/de/publizieren-archivieren/doi-service


ORCID ID: https://orcid.org/-0002-0474-2410




___
Wiki-research-l mailing list
wiki-researc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wiki-research-l

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

[Wikitech-l] Wikimedia Café online meeting for January 2020 with focus on the 2030 strategy

2020-02-04 Thread Pine W
Hello colleagues,

The February 2020 Wikimedia Café meetup will occur on 15 February 2020
at 8:30 AM PST / 11:30 AM EST / 4:30 PM UTC / 10 PM IST. The date is
earlier than usual in the month due to scheduling constraints.

This month's meetup will focus on the 2030 strategy recommendations,
and will be divided into two discussions of one hour each.

More information regarding the agenda and links to strategy documents
are available at https://meta.wikimedia.org/wiki/Wikimedia_Café.

As usual, the meeting style for the Café will emphasize discussion
rather than presentation. People are welcome to participate as
listeners only if they prefer.

Please see the page on Meta for more information about the Café.
Please watch the page for any updates, particularly to the schedule or
the agenda. Signing up for the meeting is optional, but is helpful to
the organizers so that we can estimate how many people will attend.
Signing up for the meeting also informs us who we should notify
individually if there are significant changes.

If there are any problems with connecting to the meeting or if you
have any questions or comments then please write on the Meta talk
page.

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] Comment regarding technical newsletters

2020-02-04 Thread Pine W
Hello colleagues,

I have a brief comment regarding technical newsletters. I have in mind
Tech News and the Growth Team's update newsletters. I find these to be
helpful and I appreciate the work that goes into writing them. Thank
you to the people who work on these, including translators.

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] Fwd: [OSM-talk] W3C Maps on the Web workshop

2020-02-03 Thread Pine W
Forwarding.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Rushforth, Peter (NRCan/RNCan) 
Date: Tue, Jan 28, 2020 at 9:46 PM
Subject: [OSM-talk] W3C Maps on the Web workshop
To: t...@openstreetmap.org 


Dear Open Street Map community,



I apologize if you are seeing this email for a second time. I sent it
originally to the talk-ca list, and I was advised that this list might
be more appropriate.



My name is Peter Rushforth, and I’m with the Canada Centre for Mapping
and Earth Observation, at Natural Resources Canada (a Canadian
government department).  We are planning a World Wide Web Consortium
(W3C) workshop on maps in the Web platform (specifically HTML),
together with the W3C and the Open Geospatial Consortium (OGC).  The
workshop will be collocated with the OGC Technical Committee meeting,
June 15-17 2020 in Montreal, Quebec.



I am sending this email to see if Open Street Map (especially the Web
client development teams) might be interested in being invited to
participate (by presenting a short position paper, in person) in this
workshop on the concept of better integrating mapping into the Web
platform standards, and if so, how does Open Street Map see this.
Even if you believe that the Web platform standards are already good
enough for mapping, it might be worthwhile staking that out as a
position. If you are interested, though, we would certainly welcome
OSM to also be part of the program committee.



The objective of the workshop will be to start the conversation
between the geospatial (and geospatial standards) and Web platform
communities, about how Web standards could better serve the needs of
Web mapping and most especially users of Web maps and the Web in
general.



Some topics of potential interest include:



a native map viewer, similar to that provided for video content
standards for how such a map widget might integrate with map services and APIs
accessibility of browser maps
privacy of user location information
security of browser-based maps
Integration / relationship of maps and location with other browser
APIs, e.g. geo-video, geolocation API, forms, SVG
crawling, indexing and searching map information
standardized browser elements and APIs
CSS styling of maps and map features
Map feature creation / input forms
federated map services with linking - aka the Web



Mostly the agenda will be driven by position papers, and what
organizations like yours want to discuss.  If OSM is interested in
sending one or two people to present a position, please reply directly
to me, and I will ensure that you / they are invited.





Sincerely,

Peter





Peter Rushforth



Technology Advisor

Canada Centre for Mapping and Earth Observation

Natural Resources Canada / Government of Canada

peter.rushfo...@canada.ca / Tel: 613-759-7915



Conseiller technique

Centre canadien de cartographie et d’observation de la Terre

Ressources naturelles Canada / Gouvernement du Canada

peter.rushfo...@canada.ca / Tél: 613-759-7915



___
talk mailing list
t...@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

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

Re: [Wikitech-l] [WikimediaMobile] Commons Android app v2.12

2020-02-01 Thread Pine W
Sounds good. Thanks for these updates, Josephine.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Sat, Feb 1, 2020 at 12:55 PM Josephine Lim  wrote:
>
> Hi all,
>
> We've just released v2.12 of the Commons app to production on the Play 
> Store[1]! :) This contains the legacy code overhaul that we've been working 
> on for the better part of the last year, in order to reduce 
> difficult-to-debug issues and create a better foundation for stability and 
> further improvements.
>
> One of the goals in this overhaul is to prevent the issue of failed uploads 
> which has plagued our users sporadically for years. According to our beta 
> testers' feedback, this issue has been solved - however, if you are using 
> v2.12 (can be seen in About page) on a *fresh install* and you are still 
> experiencing failed uploads, please do let us know so we can take a look at 
> it. Also, as this version contains the most lines of code changed compared to 
> any of our other versions, it is possible that there may be a few teething 
> issues that we are as of yet unaware about, but we will try to fix any 
> reported issues ASAP.
>
> Also, we have a new feature: Filters for place types and states in Nearby 
> Places! With this feature, you should be able to filter for (or filter out) 
> specific types of places that need photos, and also filter out places that 
> are on Wikidata but don't "exist" anymore.
>
> Thank you all for your support and patience. :)
>
> Best regards,
> Josephine / @misaochan (Commons app project maintainer)
>
> [1] https://play.google.com/store/apps/details?id=fr.free.nrw.commons
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l

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

Re: [Wikitech-l] Google Code-in 2019: Read what students worked on

2020-01-30 Thread Pine W
Thanks for sharing, Andre. That's a nice list.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Tue, Jan 28, 2020 at 2:35 PM Andre Klapper  wrote:
>
> A few days ago, Google Code-in 2019 ended.
>
> 194 students completed 715 Wikimedia tasks.[1]
> Big thanks and congratulations to everybody!
>
> Read about their GCI experience with Wikimedia in their blog posts:
> https://www.mediawiki.org/wiki/Google_Code-in/2019#Wrap-up_blog_posts
>
> Thanks to our 43 mentors for being available, also on weekends &
> holidays. Thanks to everyone on IRC, Gerrit, Phabricator, mailing
> lists, Github, etc. for your friendliness, patience, support and help.
> Thanks to Wikimedia org admins for making this run really smoothly.
> And thanks to Google for organizing this opportunity for young people
> to learn about and contribute to free software and free knowledge.
> Google will announce Grand Prize winners and finalists on February 10.
>
> We also welcome everybody's feedback what Wikimedia could improve:
> https://www.mediawiki.org/wiki/Google_Code-in/Lessons_learned#2019
>
> Sharing some of the students' achievements, to give you an impression:
>
>  * WMCZ's Tracker software received 40 fixes and improvements
>  * 37 fixes and improvements to the WatchTranslations tool
>  * 24 fixes and improvements to the VideoCutTool tool
>  * 12 fixes and improvements to the WikiContrib tool
>  * Tasks to learn programming in Lua were completed 218 times (such as:
>Introduction to Lua in Wikipedia, Working with modules, Calculations
>and tests, Loops and tables, Lua libraries, MediaWiki libraries,
>Wikibase client, Name formats, Date formats, Using Wikidata)
>  * 13 extensions got extension.json converted to manifest_version 2
>  * 8 extensions got jshint and jscs replaced with eslint
>  * 5 extensions got jsonlint replaced with eslint
>  * Blockly, Huggle, Phabricator, video2commons, and Wiki Ed Dashboard
>got migrated to the new Translate validator framework
>  * Flask-JSONLocale received three bug fixes
>  * Watchlist notifications can be delivered as web notifications
>through Echo (but not enabled yet on Wikimedia sites)
>  * Kiwix Android App has a button to search for a new article
>  * Quarry has a button to toggle syntax highlighting
>  * Wikilink tool has a namespace filter and can filter bot edits
>  * Commons Android App has screenshots in 14 more languages, the
>username can be clicked in the navigation drawer, an improved share
>message, and videos for best media upload practices were created
>  * Commons Mass Description tool: /users does not throw a fatal error
>  * EasyTimeline has a system message to track category description
>  * MediaWiki Core's UploadFromUrl::isAllowedHost has tests
>  * Google Drive to Commons tool allows removing files after selection
>before uploading, and has a redesigned 'upload complete' screen
>  * Hashtags tool allows charts to be downloaded as images
>  * MobileFrontend extension allows turning on the lead paragraph in
>other namespaces and the nav menu drawer received a CSS shadow
>  * DynamicPageList extension uses page images as the image in gallery
>mode for pages which are not in the File namespace
>  * MassMailer tool has improved internationalization, its alerts are
>dismissable, and is integrated with Translatewiki.net
>  * Map of Monuments tool can filter by country and language
>  * Wiki Education Dashboard Android App has better screenshots and a
>placeholder for empty screens
>  * WikiEduDashboard has a git pull hook to update gems and packages,
>and its ArticleViewer adds appropriate styling for Wikidata
>  * Music on Wikimedia pages was transcribed to LilyPond 9 times
>  * 4 templates on English Wikipedia received Documentation
>  * A web app to showcase a variety of tools hosted on Wikimedia
>Toolforge was created
>  * meta:Research_on_open_source_team_communication_tools was expanded
>  * Hackathons of other FOSS orgs were researched, to improve ours
>  * 14 text files in MediaWiki core's /doc got converted to Markdown
>  * Logos designed for VideoCutTool tool, the MediaWiki FormWizard
>Extension, the Friends of the Docs working group, and the Google
>Drive to Wikimedia Commons Uploader tool
>  * Designs for "Personal Space Needed" and "Wikimedia Friends of the
>Docs" stickers created
>  * HD logos were added for several Wikimedia project websites
>
> Thanks for helping making free knowledge available to everybody. <3
>
> On behalf of the org admins,
> andre
>
> [1] https://www.mediawiki.org/wiki/Google_Code-in/Statistics
>
> --
> 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

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org

Re: [Wikitech-l] New Tool from Community Tech: Who Wrote That?

2020-01-25 Thread Pine W
Cool. Thanks for sharing.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Fri, Jan 24, 2020 at 8:50 PM Ilana Fried  wrote:

> Hello everyone,
>
>
> I’m very excited to share a new tool created by the Community Tech team:
> Who Wrote That[1],
> available as a
> <
> https://chrome.google.com/webstore/detail/who-wrote-that-beta/ekkbnedhfelfaidbpaedaecjiokkionn
> >Chrome[2]
> and Firefox[3] browser extension. We developed this tool in response to the
> <
> https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2017/Search/Blame_tool
> >#4
> wish[4] from the 2017 Community Wishlist Survey[5]. With Who Wrote That?
> (WWT), you can find authorship information directly on Wikipedia articles.
> When you hover over content, the tool highlights all content by the same
> author. When you click on content, the tool identifies the author of the
> revision, along with revision details.
>
>
> We would love your feedback[6]! You can download the
> <
> https://chrome.google.com/webstore/detail/who-wrote-that-beta/ekkbnedhfelfaidbpaedaecjiokkionn
> >Chrome[2]
> and Firefox[3] extension, and documentation on the tool is available on the
> MediaWiki WWT page[1]. The data and analysis in WWT come from the WhoColor
> API[7], developed by WikiWho[8], and the MediaWiki API.
>
>
> We hope that you all enjoy using the tool!
>
>
> Thank you,
>
>
> Ilana Fried
>
> Product Manager, Community Tech
>
>
> [1]. https://www.mediawiki.org/wiki/WWT
>
> [2].
>
> https://chrome.google.com/webstore/detail/who-wrote-that/ekkbnedhfelfaidbpaedaecjiokkionn
>
> [3]. https://addons.mozilla.org/en-US/firefox/addon/whowrotethat/
>
> [4].
>
> https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2017/Search/Blame_tool
>
> [5]. https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2017
>
> [6].
> https://meta.wikimedia.org/wiki/Talk:Community_Tech/Who_Wrote_That_tool
>
> [7]. https://api.wikiwho.net/en/whocolor/v1.0.0-beta/
>
> [8]. https://www.wikiwho.net/
> ___
> 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

2020-01-20 Thread Pine W
Thanks for the updates, transparency, and timely notifications.

I hope that I didn't sound like I was trying to be a pest earlier in this
thread. What may have been clear to people who are familiar with
Phabricator 2FA was not clear to me at the time.

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

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

2020-01-16 Thread Pine W
Hi Greg,

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.

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?

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Thu, Jan 16, 2020, 15:18 Greg Grossmeier  wrote:

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

2020-01-16 Thread Pine W
Hi David,

Thanks for the information.

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?

Is there a public ticket that people can watch for updates and where public
questions may be asked?

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Jan 16, 2020, 13:25 David Sharpe  wrote:

>
>
> Hello,
>
> On 14 January 2020, staff at the Wikimedia Foundation discovered that a
> data file exported from the Wikimedia Phabricator installation, our
> engineering task and ticket tracking system, had been made publicly
> available. The file was leaked accidentally; there was no intrusion. We
> have no evidence that it was ever viewed or accessed. The Foundation's
> Security team immediately began investigating the incident and removing the
> related files. The data dump included limited non-public information such
> as private tickets, login access tokens, and the second factor of the
> two-factor authentication keys for Phabricator accounts.  Passwords and
> full login information for Phabricator were not affected -- that
> information is stored in another, unaffected system.
>
> The Security team has investigated and assesses that there is no known
> impact from this incident. However, out of an abundance of caution, we are
> resetting all Two-Factor Authentication keys for Phabricator and
> invalidating the exposed login access tokens. Additionally, we continue to
> encourage people to engage in online security best practices, such as
> keeping your software updated and resetting your passwords regularly.
>
> The Foundation will continue to investigate this incident and take steps
> to prevent it from occurring again in the future. In the meantime,
> Phabricator is online and functioning normally. We regret any inconvenience
> this may have caused and will provide updates if we learn of any further
> impact.
>
>
> Respectfully,
>
> David Sharpe
> Senior Information Security Analyst
> 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] Scrum of scrums/2020-01-08

2020-01-08 Thread Pine W
Thanks for the updates, especially regarding the Desktop Improvements
Project.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, Jan 8, 2020 at 5:21 PM Ž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:
> ** Search Platform: MW Job consumers sometimes pause for several minutes
> [[phab:T224425]]
> ** RelEng: [[phab:T241448]]
> * Updates:
> ** New session storage to roll out to production -> Redis cluster going
> away
>
> === Engineering Productivity ===
>
>  Release Engineering 
> * Blocked by:
> ** SRE 

[Wikitech-l] Fwd: [Analytics] Introducing statistics for media files

2020-01-02 Thread Pine W
Also forwarding to Research-l and Wikitech-l.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Francisco Dans 
Date: Mon, Dec 23, 2019 at 5:52 PM
Subject: [Analytics] Introducing statistics for media files
To: A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics. 


Hi everybody,

Just in time for the holidays, we're announcing the addition of Media
Requests to our metrics catalog. Over the last few months we've been
working on a dataset offering request numbers for every single image,
audio, video and document in the Wiki universe, since 2015.

This means we have 3 new metrics available in the Analytics Query Service:

   - Media requests per referrer: e.g. how many images, audio, videos...
   have been accessed from English Wikipedia in the last month? *73 billion
   for November
   
.*
   - Media requests per file: e.g. how many hits did this cool painting
   
   get in November? The answer is 483,791 hits
   

   .
   - Top files by media requests: e.g. what was the most popular video
   yesterday, December 22nd? Fred Rogers testifying before the Senate
   Subcommittee on Communications
   
.
   Fun! You can check out the top 1000 media files for any month or day, for
   any media type.

Media requests is, in terms of absolute numbers, a huge dataset, so the per
file and top metrics are still being loaded with data all the way to 2015.
We expect this loading to finish in mid January.

You can read more about this in Wikitech
. As usual
if you have any questions about the dataset or the new metrics please send
them our way here on the list or via Phabricator.

Happy holidays!
Francisco + the A team
-- 
*Francisco Dans (él, he, 彼)*
Software Engineer, Analytics Team
Wikimedia Foundation
___
Analytics mailing list
analyt...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Café online meeting for January 2020. Note the schedule change.

2019-12-31 Thread Pine W
After re-reading what I wrote, I think that I came across as being
irritated, and I'm sorry about that. I was rushing to get that email out,
and I should have slowed down. Let me try this again.

With the hope that some folks on Wikitech-l may be interested in this
invitation to the Wikimedia Café, I am sharing it here. There may be some
feeling on Wikitech-l that these invitations are not sufficiently
technical, and if I get the sense that there is a consensus on Wiitech-l
that these invitations are distractions unless there are technical subjects
on the agenda then I will respect that decision and refrain from sharing
Wikimedia Café invitations to Wikitech-l except when there are technical
subjects on the agenda. However, I hope that there will be general interest
in the Cafe..Anyone is welcome to add a topic to the agenda.

Apologizes again for being hasty and for sounding irritated in my previous
email.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Tue, Dec 31, 2019 at 11:56 PM Pine W  wrote:

> Hello Wikitech-l colleagues,
>
> I don't know how much interest there is on Wikitech-l regarding meeting
> invitations for the Wikimedia Café, but I'm cross-posting this invitation
> for the to the list. If I hear a bunch of complaints then I will stop the
> cross-posting of Café invitations when there are not clearly tech-oriented
> items on the agenda for the Café. However, I would hope that some
> subscribers to Wikitech-l are interested in the Café.
>
> A reminder: you are welcome to add items to the Café's agenda.
>
> Best wishes for the new year,
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> -- Forwarded message -
> From: Pine W 
> Date: Tue, Dec 31, 2019 at 11:39 PM
> Subject: Wikimedia Café online meeting for January 2020. Note the schedule
> change.
> To: Wikimedia Mailing List 
>
>
> Hello colleagues,
>
> The Wikimedia Café meetings have generally been well received. We had
> approximately seven people in the December meeting. In an attempt to make
> the meetings be accessible to more people, in January 2020 the Café is
> tentatively scheduled for a Saturday, and the Café will be earlier in the
> day. The meeting will be on 25 January 2020 at the following time: 11:30 AM
> EST, 4:30 PM UTC, and 10 PM ITC.
>
> During the most recent Café we had an extensive discussion about
> documentation for Wikitext and templates. We ran out of time to discuss
> NavWiki <https://outreach.wikimedia.org/wiki/NavWiki>. For the January
> meeting the only non-introductory agenda item so far is NavWiki. You are
> welcome to add more items to the agenda
> <https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#25_January_2020_at_11:30_AM_EST_/_4:30_PM_UTC_PM_UTC_/_10_PM_IST>
> .
>
> As usual, the meeting style for the Café will emphasize discussion rather
> than presentation. People are welcome to participate as listeners only if
> they prefer.
>
> Please see the page on Meta
> <https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9> for more
> information about the Café. Please watch the page for any updates,
> particularly to the schedule or the agenda. Signing up for the meeting is
> optional, but is helpful to the organizers so that we can estimate how many
> people will attend. Signing up for the meeting also informs us who we
> should notify individually if there are significant changes, such as
> changes to the schedule.
>
> If there are any problems with connecting to the meeting or if you have
> any questions or comments then please write on the Meta talk page.
>
> Best wishes for the new year,
> 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] Fwd: Wikimedia Café online meeting for January 2020. Note the schedule change.

2019-12-31 Thread Pine W
Hello Wikitech-l colleagues,

I don't know how much interest there is on Wikitech-l regarding meeting
invitations for the Wikimedia Café, but I'm cross-posting this invitation
for the to the list. If I hear a bunch of complaints then I will stop the
cross-posting of Café invitations when there are not clearly tech-oriented
items on the agenda for the Café. However, I would hope that some
subscribers to Wikitech-l are interested in the Café.

A reminder: you are welcome to add items to the Café's agenda.

Best wishes for the new year,
Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Pine W 
Date: Tue, Dec 31, 2019 at 11:39 PM
Subject: Wikimedia Café online meeting for January 2020. Note the schedule
change.
To: Wikimedia Mailing List 


Hello colleagues,

The Wikimedia Café meetings have generally been well received. We had
approximately seven people in the December meeting. In an attempt to make
the meetings be accessible to more people, in January 2020 the Café is
tentatively scheduled for a Saturday, and the Café will be earlier in the
day. The meeting will be on 25 January 2020 at the following time: 11:30 AM
EST, 4:30 PM UTC, and 10 PM ITC.

During the most recent Café we had an extensive discussion about
documentation for Wikitext and templates. We ran out of time to discuss
NavWiki <https://outreach.wikimedia.org/wiki/NavWiki>. For the January
meeting the only non-introductory agenda item so far is NavWiki. You are
welcome to add more items to the agenda
<https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#25_January_2020_at_11:30_AM_EST_/_4:30_PM_UTC_PM_UTC_/_10_PM_IST>
.

As usual, the meeting style for the Café will emphasize discussion rather
than presentation. People are welcome to participate as listeners only if
they prefer.

Please see the page on Meta
<https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9> for more information
about the Café. Please watch the page for any updates, particularly to the
schedule or the agenda. Signing up for the meeting is optional, but is
helpful to the organizers so that we can estimate how many people will
attend. Signing up for the meeting also informs us who we should notify
individually if there are significant changes, such as changes to the
schedule.

If there are any problems with connecting to the meeting or if you have any
questions or comments then please write on the Meta talk page.

Best wishes for the new year,
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] WMDE job openings for a UX designer and a technical writer

2019-12-30 Thread Pine W
FYI:

1.
https://wikimedia-deutschland.softgarden.io/job/5681755/UX-Designer-Wikidata-Wikibase-m-f-d-?jobDbPVId=15549395=en
2.
https://wikimedia-deutschland.softgarden.io/job/5681080/Technical-Writer-m-f-d-?jobDbPVId=15546960=en

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] Fwd: [AI] The WebConf (WWW 2020) Call for Papers (Demo Track)

2019-12-28 Thread Pine W
Forwarding an announcement. For what it's worth, WMF is listed as a sponsor
of the 2019 conference, and multiple conference tracks appear to be
relevant to Wikiverse activities. However, announcements which include
lofty adjectives such as "visionary" often give me pause due to the risk of
over-promising and under-delivering. Your views may vary.

Regards,
Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Jui-Yi Tsai 
Date: Tue, Dec 24, 2019 at 2:42 AM
Subject: [AI] The WebConf (WWW 2020) Call for Papers (Demo Track)
To: 


*The WebConf (WWW) Call for Papers: Demo Track*
 April 20-24, 2020
Taipei, Taiwan
  https://www2020.thewebconf.org/

*Important Dates*
• Submission deadline: January 06, 2020
• Notification: February 10, 2020

For almost three decades, the Web Conference series has been the premier
venue for researchers, academics, businesses and standards bodies to come
together and discuss latest updates and the future of the Web. The
Demonstration Track of the Web Conference has become an important venue for
sharing cutting-edge and exciting web-based prototype systems with
significant research and development efforts. The Demonstrations Track
allows researchers and practitioners to demonstrate first-hand visionary
systems with innovative features and functionalities in a dedicated
session. Submissions must be based on an implemented and tested system that
pursues one or more innovative ideas in the interest areas of the
conference.

*Topics include (but are not limited to)*
● Health on the Web
● Behavioral analysis and personalization
● Crowdsourcing systems and social media
● Bio-feedback and emotional computation
● New human-computer interfaces
● Internet economics, monetization, and online markets
● Pervasive Web and mobility
● Security, privacy, and trust
● Semantics and knowledge
● Semantic Web, content analysis, and Web mining
● Social networks, social analysis, and computational social science
● Web infrastructure: datacenters, cloud computing, and systems
● User modeling, personalization, and experience
● Mobile, ubiquitous, ambient, and pervasive computation, Web of Things
● Web science, Web search, and Web systems

Demonstrations are encouraged from academic researchers, from industrial
practitioners with prototypes or in-production deployments, as well as from
any W3C-related activities to interact while exploring the latest
techniques for managing web information and knowledge. Software (including
games or learning platforms) and hardware demos will be considered equally,
provided they show innovative use of Web-based techniques. Each submission
must make clear which aspects of the system will be demonstrated, and how.
What exactly will the audience experience? What are the interesting
scenarios to motivate the demonstration? They should strive to state the
significance of the contribution to Web technology or applications. In
other words, submissions should describe the intended audience, point out
the innovative aspects of the system being demonstrated, and explain how
those aspects contribute to the state of the art in the Web and information
technology. Submissions will be peer-reviewed by members of the track
program committee, who will judge the originality, significance, quality,
and clarity of each submission.

*Submission Guidelines*
Demonstration Track submissions must be formatted according to the ACM SIG
Proceedings Template and are limited to four pages (including references
and appendices). It is the authors’ responsibility to ensure that
submissions adhere strictly to the required format. The format cannot be
modified with the objective of squeezing in more material. Submissions that
do not comply with the formatting guidelines will be rejected without
review.

Each demonstration track submission should contain an introduction, brief
description, screenshots, value and contribution. Submissions should also
indicate how the demonstration will be demonstrated and the hardware
requirements (for the organizers).

Submissions must be double-blinded. Submissions must be in PDF and must be
made through the EasyChair system (Demonstrations Track):

https://easychair.org/conferences/?conf=www2020

At least one author of each accepted demonstration paper must register for
the conference and attend in person to demonstrate the system during the
demonstration sessions.

To better identify the value of demonstrations, as well as to reach out to
external audiences, we also encourage authors to submit a pointer to a
screencast, using web-accessible platforms such as Vimeo or YouTube. The
maximum duration of screencasts is 10 minutes. We also highly encourage any
external material related to the demo (e.g., shared code on GitHub).

*Track Co-chairs*
Hsu-Chun Hsiao (National Taiwan University)
De-Nian Yang (Academia Sinica)
Email: demos2...@thewebconf.org
___
AI mailing list

Re: [Wikitech-l] Math at the Wikimedia Technical Conference 2019

2019-12-28 Thread Pine W
Thanks for sharing updates, physikerwelt.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Sat, Dec 28, 2019 at 10:41 AM Physikerwelt  wrote:

> Dear all,
>
> a minor update on hyperlinks in formulae~[1]:
> The demo on the beta cluster works quite well.
> There is just one minor problem~[2], which seems to a problem within
> wikibase, which will hopefully be resolved as wikibase improves
> without any changes to the Math extension codebase.
>
> As a next step, we will enable the feature by default~[3]. This will
> have no impact as the qid-attribute is not set on any formulae in
> production wikis currently.
>
> While we were hoping that the change to the popup extension that André
> contributed would be merged, we will need to plan more time to discuss
> this change with the maintainer of the popups extension. However, a
> first step was successful, and we could identify who is responsible
> for the popups extension~[4].
>
> Any feedback or suggestions are highly appreciated.
>
> All the best
> Moritz (physikerwelt)
>
> [1]: https://phabricator.wikimedia.org/T208758
> [2]: https://phabricator.wikimedia.org/T229939
> [3]: https://phabricator.wikimedia.org/T239356
> [4]: https://phabricator.wikimedia.org/T239357#5738927
>
> http://moritzschubotz.de | +49 1578 047 1397
>
> On Sat, Nov 16, 2019 at 8:00 PM Physikerwelt  wrote:
> >
> > Hi all,
> >
> > I was happy to be invited by the Wikimedia Foundation to the Wikimedia
> > Technical Conference 2019 in Atlanta~[1]. At this conference, I
> represented
> > the technical needs of the mathematical community~[2]. Apart from a lot
> of
> > great achievements for the whole Wikimedia movement with regard to the
> five
> > focus areas of the conference~[3], there were also several math-specific
> > achievements. In this message, I will focus on those aspects:
> >
> > 1) Bold italic capital greek symbols are now possible. Please join me in
> > thanking Petr Kadlec (aka. Mormegil) for his perennial effort to make
> this
> > possible~[4].
> >
> > 2) We will - very soon - have a demo on the Wikimedia beta cluster
> enabling
> > links from formulae to a dedicated special page that displays
> definitions and
> > explanations regarding mathematical objects of interest, i.e.,
> identifiers,
> > symbols, terms. Thank you André Greiner-Petter for the implementation of
> this
> > feature~[5].
> >
> > 3) In a session on 'Integrating contributions from other teams or
> volunteers`
> > organized by Christoph Jauera (aka. Fisch). We derived definitive action
> items
> > on improving the participation opportunities to the Math on wikis~[6].
> >
> > 4) We discussed the future of Math rendering with Petr Pchelko (WMF)
> which
> > will simplify the setup of mathoid and eventually get rid of fallback
> images
> > while maintaining support for MathML disabled browsers~[7].
> >
> > I am grateful to the Wikimedia Foundation and the organizers of the
> event, in
> > particular, Rachel and Greg to get the chance to enjoy this
> well-organized
> > conference with amazing people and a wonderful program.
> >
> > All the best
> > Moritz (physikerwelt)
> >
> > http://moritzschubotz.de | +49 1578 047 1397
> >
> >
> > [1]:https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019
> > [2]:https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Math
> > [3]:https://phabricator.wikimedia.org/T238406
> > [4]:https://phabricator.wikimedia.org/T218295
> > [5]:https://phabricator.wikimedia.org/T208758
> > [6]:https://phabricator.wikimedia.org/T234662#5660102
> > [7]:https://phabricator.wikimedia.org/T237516
> >
> > Some more details on item 4, from my personal, biased perspective:
> >
> > I started working on the Math extension in 2012 and implemented the
> > main functionality
> > of the new rendering method which is based on MathJax rather
> > than on LaTeX in 2013 at the Wikimedia Foundations Headquarter in San
> > Francisco. At that time the vision was to replace the monolithic PHP
> based
> > framework MediaWiki, with a large number of small dynamic JavaScript
> modules.
> > The idea was that those modules are developed as isomorphic
> platform-independent
> > components using interfaces of a management framework that takes
> > care of caching and efficient execution. The long-term goal was that the
> > functionality could be executed either on the client or on the server
> and that
> > the management layer would figure out the best execution strategy based
> on the
> > current prerequisites. In the first step, a framework based on HTTP
> requests was
> > set up to handle services such as math rendering. Mathoid the math
> rendering
> > service was one of the first instances of this service template. From the
> > retro perspective that might have been too early. Neither a convenient
> type and
> > schema description language existed, nor a way to specify rich metadata
> on the
> > execution characteristics existed. However, a fine-grained I/O schema
> seems
> > desirable for 

Re: [Wikitech-l] Wikimedia Café online meeting for December 2019

2019-12-19 Thread Pine W
Hello colleagues,

This is a reminder that the December 2019 Wikimedia Café meeting will start
approximately one hour from now.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Fri, Nov 29, 2019 at 10:50 PM Pine W  wrote:

> Hello colleagues,
>
> For the next Wikimedia Café online video meeting, agenda items include:
> * Documentation for Wikitext <https://en.wikipedia.org/wiki/Help:Wikitext>
> * The NavWiki <https://outreach.wikimedia.org/wiki/NavWiki> project
>
> Last month's Wikimedia Café had a problem with an inaccurate time
> conversion from USA Eastern time to UTC. People attempted to join the
> meeting at different times based on whether they referred to UTC or to US
> Eastern time. I apologize for the error, and I think that it has been
> corrected for December.
>
> The meeting style for the Café will emphasize discussion rather than
> presentation. People are welcome to participate as listeners only if they
> prefer.
>
> Please see the page on Meta
> <https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9> for more
> information about the Café. Please watch the page for any updates,
> particularly to the schedule or the agenda. Signing up for the meeting is
> optional, but is helpful to the organizers so that we can estimate how many
> people will attend. Signing up for the meeting also informs us who we
> should notify individually if there are significant changes, such as to the
> schedule.
>
> If there are any problems with connecting to the meeting or if you have
> any questions or comments then please write on the Meta talk page.
>
> 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] Fwd: [Wiki-research-l] Survey on data visualization for Wikipedia

2019-12-03 Thread Pine W
Forwarding in case this is of interest to people on other mailing lists.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Jaqen 
Date: Tue, Dec 3, 2019 at 11:52 AM
Subject: [Wiki-research-l] Survey on data visualization for Wikipedia
To: Research into Wikimedia content and communities <
wiki-researc...@lists.wikimedia.org>, 


Hi!

As a part of my job at OBC Transeuropa 
among the other things I contribute to Wikipedia and Commons with graphs
and text coming from EDJNet , a
data journalism network we promote that is publishing its content with a
free license.

In the attempt of inserting graphs using MediaWiki instead of svg images I
realised the tool now available are cumbersome and there is the
possibilities for improvement.

Thus we are making a survey to understand if Wikipedia users are interested
in having better tools, allowing to publish better graphs more easily.  So
I ask you to please spend a few minutes of your time to let us now what you
think :)

https://surveys.europeandatajournalism.eu/quiz/data-visualization-for-wikipedia-eng/


The survey is anonymous. You will be given the opportunity to leave your
e-mail address to receive updates on developments, but this is optional.
The results of the survey will be published on EDJNet and on Meta, and I
will also link them here.

Let me know if you have any questions! Thank you!

Niccolò "Jaqen" Caranti
___
Wiki-research-l mailing list
wiki-researc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Wikimedia Café online meeting for December 2019

2019-11-29 Thread Pine W
Hello Wikitech-l,

Usually I send emails that announce Wikimedia Café meetings only to
WIkimedia-l, but because December's meeting agenda includes discussing the
documentation for Wikitext, I am forwarding this announcement to WIkitech-l.

Regards,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Pine W 
Date: Fri, Nov 29, 2019 at 10:50 PM
Subject: Wikimedia Café online meeting for December 2019
To: Wikimedia Mailing List 


Hello colleagues,

For the next Wikimedia Café online video meeting, agenda items include:
* Documentation for Wikitext <https://en.wikipedia.org/wiki/Help:Wikitext>
* The NavWiki <https://outreach.wikimedia.org/wiki/NavWiki> project

Last month's Wikimedia Café had a problem with an inaccurate time
conversion from USA Eastern time to UTC. People attempted to join the
meeting at different times based on whether they referred to UTC or to US
Eastern time. I apologize for the error, and I think that it has been
corrected for December.

The meeting style for the Café will emphasize discussion rather than
presentation. People are welcome to participate as listeners only if they
prefer.

Please see the page on Meta
<https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9> for more information
about the Café. Please watch the page for any updates, particularly to the
schedule or the agenda. Signing up for the meeting is optional, but is
helpful to the organizers so that we can estimate how many people will
attend. Signing up for the meeting also informs us who we should notify
individually if there are significant changes, such as to the schedule.

If there are any problems with connecting to the meeting or if you have any
questions or comments then please write on the Meta talk page.

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

Re: [Wikitech-l] [Wikidata] Several primary database masters switchovers scheduled (read-only required)

2019-09-25 Thread Pine W
Thanks for the updates and for the short maintenance windows.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Sep 26, 2019 at 5:13 AM Manuel Arostegui 
wrote:

> Hello,
>
> s4 (commonswiki) was done:
>
> Read-only start: 05:00:51
> Read-only stop: 05:01:42
> Total read-only time: 51 seconds
>
> Thanks,
> Manuel.
>
> On Thu, Sep 26, 2019 at 6:00 AM Manuel Arostegui 
> wrote:
>
>> Hello,
>>
>> The last switchover, from this batch, s4 (commonswiki), will start in 1h
>> https://phabricator.wikimedia.org/T230784
>>
>> Thanks
>> Manuel.
>>
>>
>> On Tue, Aug 20, 2019 at 12:49 PM Manuel Arostegui <
>> maroste...@wikimedia.org> wrote:
>>
>>> Hello,
>>>
>>> The following primary database masters will be switched over during the
>>> next few weeks (more details at
>>> https://phabricator.wikimedia.org/T230788):
>>>
>>> Impact:
>>> *Writes will be blocked*
>>> *Reads will remain unaffected*
>>>
>>> These are the concrete days, hours and affected wikis:
>>>
>>> * s8: 10th Sept from 05:00-05:30 UTC. The affected wiki is: wikidatawiki
>>> - tracking task: T230762
>>>
>>> * s2: 17th Sept from 05:00-05:30 UTC. The list of affected wikis is at:
>>> https://raw.githubusercontent.com/wikimedia/operations-mediawiki-config/master/dblists/s2.dblist
>>>  - tracking task: T230785
>>>
>>> * s3: 24th Sept from 05:00-05:30 UTC. The list of affected wikis is at:
>>> https://raw.githubusercontent.com/wikimedia/operations-mediawiki-config/master/dblists/s3.dblist
>>> - tracking task: T230783
>>>
>>> * s4: 26th Sept from 05:00-05:30 UTC. The affected wiki is: commonswiki
>>> - tracking task: T230784
>>>
>>> If everything goes well, we do not expect to use those 30 minutes of
>>> read-only and rather just a few minutes.
>>>
>>> We will email send an email the day of each failover before and after it
>>> is done.
>>>
>>> Sorry for any inconvenience this might cause.
>>>
>>> ___
> Wikidata mailing list
> wikid...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia Announcements] Welcoming Wikimedia Foundation’s new CTO, Grant Ingersoll

2019-09-18 Thread Pine W
Forwarding to Wikitech-l and MediaWiki-l.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

-- Forwarded message -
From: Katherine Maher 
Date: Wed, Sep 18, 2019, 10:44
Subject: [Wikimedia Announcements] Welcoming Wikimedia Foundation’s new
CTO, Grant Ingersoll
To: wikimediaannounce-l 


Hi all,

I’m excited to officially welcome Grant Ingersoll as our Chief Technology
Officer! Grant will be starting September 23. He’ll be based in Charlotte,
North Carolina.

Grant comes from a long history of working on open source projects. Most
recently, he served as the Chief Technical Officer of Lucidworks, an
AI-powered open-source search services company which he co-founded. He is a
Lucene and Solr committer, co-founder of the Apache Mahout machine learning
project, and a long-standing member of the Apache Software Foundation. He’s
an author, having written a book for Java developers on how to wrangle
unstructured text for search, text-mining, and the like. He’s also a
long-time, committed remotee, having worked with the distributed Lucidworks
team from his home in North Carolina for nearly a decade.

In Grant’s own words, “The power of learning and knowledge have always
stood as key pillars in my career. I'm a big believer that access to free,
trusted knowledge is of vital importance as society looks to tackle large
scale challenges. My wife, Robin, and I recently moved from Chapel Hill,
North Carolina, our home for 10 years, to Charlotte, North Carolina, where
our daughter lives. We also just dropped our son off at college for his
freshman year. We're adjusting to the empty nest life with our dog Allie (a
black lab mix). When not traveling or exploring Charlotte, I can usually be
found on a bike, out kayaking, or writing code.”

Grant will be working with myself, Erika Bjune (who is transitioning to VP,
Technology), and others in the leadership of the technology department to
determine a set of priorities for his first year. I expect these will
likely focus around evaluating our current capacities and co-creating a
vision for the continued evolution of our technical platforms, supporting
the staff of the department, working with the finance and operations folks
on planning and budgeting for the future, and of course, getting to know
our technical community and the broader movement. Under Grant’s leadership,
we will continue the work of improving and modernizing our technical
ecosystem to respond to our future needs, as laid out in the movement
strategy.

I’m thrilled to have the CTO role filled, and to bring Grant in at a time
when the movement is digging into the question of what it means to “become
the essential infrastructure of free knowledge.” From our first meeting, I
was struck by his curiosity. He was genuinely interested in how Wikimedia
works, and was willing to get into what I often think of “Wiki PhD” level
conversations about the nuances of our community and values. I have
generally found that the folks who bring that sort of openness and humility
to their work are the folks who thrive in the challenges of our mission and
movement.  As our movement expands, I’m glad to have Grant’s experience,
curiosity, and passion for building things on board here at the Foundation.

I want to also thank Erika Bjune for her work as interim CTO. She
passionately advocated for the importance of our platforms, embodied
partnership and cooperation, and her expertise on the interview panel was
invaluable. I’m thrilled she’ll be working so closely with Grant as we move
forward.

Please join me in welcoming Grant to the Wikimedia Foundation!

Katherine
-- 

Katherine Maher (she/her)

Executive Director

Wikimedia Foundation 

___
Please note: all replies sent to this mailing list will be immediately
directed to Wikimedia-l, the public mailing list of the Wikimedia
community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list
wikimediaannounc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
___
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

2019-09-11 Thread Pine W
Thanks very much to those who worked on this problem.

I'm hoping to see a public report with more technical and legal info than
has been published so far. I think that such a report is not urgent, but it
would be nice to have the report available by the end of next week, which
would allow plenty of time for reference and commentary in the September
issue of *The Signpost*.

Pine
( https://meta.wikimedia.org/wiki/User:Pine  )

On Fri, Sep 6, 2019, 13:26 RhinosF1  wrote:

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

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

2019-09-06 Thread Pine W
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

Re: [Wikitech-l] Code of Conduct committee meeting at Wikimania

2019-08-30 Thread Pine W
+1 on the thanks for the update.

I have some ideas regarding modifications that I would like to propose to
the CoC but I am already stretched among too many tasks, so I am holding
these proposals. I do not want anarchy in technical spaces, and in general
I think that having some version of a code of conduct is good.

I am not sure whether Fae is referring to the chronological age of the
Committee as an organization or to the ages of its human members, though I
think that Fae is referring to the former. Regarding the latter, I'll make
a few comments. I am not very concerned regarding the chronological age of
committee members provided that they have reached the age of majority in
their relevant countries. I am more interested in language skills, publicly
reviewable experience and training in dispute resolution, understanding of
Wikimedia technical processes, emotional temperaments, listening skills,
reading comprehension, writing skills, research skills, demonstrated
willingness to make unpopular decisions (unpopular with WMF and/or
unpopular with a significant minority of community members), and degrees of
affiliation with WMF and the community.

Onward,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Aug 29, 2019, 14:04 Fæ  wrote:

> Thanks for the update. It's great to see the CoC processes improving
> transparency and potentially accountability to the community.
>
> It's worth noting how old the discussions are, with comments dating
> back more than a year ago, especially in the context of how relatively
> young the committee and the CoC is. Perhaps the members can discuss
> with each other how improvements can be implemented and iterated more
> manageably?
>
> Thanks,
> Fae
>
> On Thu, 29 Aug 2019 at 21:25, Amir Sarabadani  wrote:
> >
> > Hello,
> > The CoC committee had a meeting with four members out of five (Lucie,
> Tony,
> > Tonina, and Amir were at Wikimania and MusikAnimal wasn't present). These
> > notes are the public outcomes of the meeting.
> >
> > * The committee chose Amir as the chair (Amir requested to be the table
> but
> > it got rejected)
> > * The committee is currently composing the anonymized report of its cases
> > and will be published soon.
> > * The committee soon will decide on the two amendments currently under
> > discussion. Feel free to comment on these two:
> > ** Public logging of bans:
> > https://www.mediawiki.org/wiki/Topic:Uikcu1emvmw6e4z8
> > ** Modifications on the appeal process:
> > https://www.mediawiki.org/wiki/Topic:Uay0vz6no8ayac3m
> > * The committee is willing to introduce a new internal role which for
> lack
> > of better term, we call it secretary for now. The role's main
> > responsibility is to help the committee on organizational bookkeeping.
> Like
> > reports, documentation of cases, etc.
> > * At the end, the committee wants to remind people that its role is
> > reactionary and we won't interfere when there's no report. If you see a
> > behaviour you find unacceptable, stand up and send us a report and don't
> > wait for the committee to jump in.
> >
> > Regards,
> > Amir on behalf of the committee
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> fae...@gmail.com https://commons.wikimedia.org/wiki/User:Fae
> Personal and confidential, please do not circulate or re-quote.
>
> ___
> 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] m1 (etherpad, bacula, librenms, rt, racktables) db primary master switchover: 10th Sept 16:00 UTC

2019-08-30 Thread Pine W
Hi Manuel,

I'm not familiar with User-Notice tags, but I'll trust your judgment.
Perhaps you could also mention the planned outage of Etherpad in Tech News.

It sounds like this will be a low impact outage, but there is a small
chance that someone will be taking notes on Etherpad during a meeting that
is important to them and they will experience a few seconds of information
loss during the time that Etherpad is read only due to the inability to
write new information while the meeting is ongoing.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Aug 29, 2019, 06:55 Manuel Arostegui 
wrote:

> On Thu, Aug 29, 2019 at 3:50 PM Pine W  wrote:
>
> > Yes, I tink that a banner would be preferable, but i think that a notice
> on
> > the homepage would be a reasonable backup option.
> >
> >
> Thanks - Unfortunately I don't know if that is possible on Etherpad, I
> don't have the knowledge to do so.
> Maybe I can put an User-Notice tag on the phabricator task, so more people
> would be aware of that brief interruption?
> Again, we are expecting 5-10 seconds of read-only time.
>
> Thanks,
> Manuel.
>
>
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> > On Thu, Aug 29, 2019, 06:28 Manuel Arostegui 
> > wrote:
> >
> > > On Thu, Aug 29, 2019 at 3:05 PM Pine W  wrote:
> > >
> > > > Hello,
> > > >
> > > > Does this mean that https://etherpad.wikimedia.org/ will be
> > temporarily
> > > > read only? That site seems to be somewhat popular for taking notes
> > during
> > > > meetings. If that site will be affected then I recommend that you put
> > up
> > > a
> > > > site notice there, possibly a multilingual one depending on how much
> > use
> > > > the site gets for non-English content.
> > > > Pine
> > > > ( https://meta.wikimedia.org/wiki/User:Pine )
> > > >
> > > >
> > > >
> > > Hello Pine,
> > >
> > > Yes, etherpad will be read-only for a few seconds (5-10 seconds)
> > > I don't know if it is possible to put a banner on Etherpad itself, is
> > that
> > > what you mean?
> > >
> > > Thanks
> > > Manuel.
> > >
> > >
> > >
> > > >
> > > > On Thu, Aug 29, 2019, 04:01 Manuel Arostegui <
> maroste...@wikimedia.org
> > >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > The current primary master for m1 (db1063), which is mostly for
> > > internal
> > > > > services + etherpad isn't in a great healthy status: it is an old
> > host,
> > > > > which needs to be decommissioned and which is having disks failing
> > > pretty
> > > > > much every week (plus disks on predictive failure).
> > > > >
> > > > > We have decided to fail it over one of the newer hosts, db1135:
> > > > > https://phabricator.wikimedia.org/T231403
> > > > >
> > > > > We have scheduled this switchover for: Tuesday 10th September at
> > 16:00
> > > > UTC
> > > > >
> > > > > This failover should be rather quick and would only take a few
> > seconds
> > > > > (while we re-load the haproxy) - during those few seconds, the
> > > following
> > > > > services will be on read-only:
> > > > >
> > > > > bacula
> > > > > etherpadlite
> > > > > librenms
> > > > > puppet
> > > > > racktables
> > > > > rt
> > > > >
> > > > > 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
> > > ___
> > > 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] m1 (etherpad, bacula, librenms, rt, racktables) db primary master switchover: 10th Sept 16:00 UTC

2019-08-29 Thread Pine W
Yes, I tink that a banner would be preferable, but i think that a notice on
the homepage would be a reasonable backup option.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Thu, Aug 29, 2019, 06:28 Manuel Arostegui 
wrote:

> On Thu, Aug 29, 2019 at 3:05 PM Pine W  wrote:
>
> > Hello,
> >
> > Does this mean that https://etherpad.wikimedia.org/ will be temporarily
> > read only? That site seems to be somewhat popular for taking notes during
> > meetings. If that site will be affected then I recommend that you put up
> a
> > site notice there, possibly a multilingual one depending on how much use
> > the site gets for non-English content.
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> >
> >
> Hello Pine,
>
> Yes, etherpad will be read-only for a few seconds (5-10 seconds)
> I don't know if it is possible to put a banner on Etherpad itself, is that
> what you mean?
>
> Thanks
> Manuel.
>
>
>
> >
> > On Thu, Aug 29, 2019, 04:01 Manuel Arostegui 
> > wrote:
> >
> > > Hello,
> > >
> > > The current primary master for m1 (db1063), which is mostly for
> internal
> > > services + etherpad isn't in a great healthy status: it is an old host,
> > > which needs to be decommissioned and which is having disks failing
> pretty
> > > much every week (plus disks on predictive failure).
> > >
> > > We have decided to fail it over one of the newer hosts, db1135:
> > > https://phabricator.wikimedia.org/T231403
> > >
> > > We have scheduled this switchover for: Tuesday 10th September at 16:00
> > UTC
> > >
> > > This failover should be rather quick and would only take a few seconds
> > > (while we re-load the haproxy) - during those few seconds, the
> following
> > > services will be on read-only:
> > >
> > > bacula
> > > etherpadlite
> > > librenms
> > > puppet
> > > racktables
> > > rt
> > >
> > > 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
> ___
> 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] m1 (etherpad, bacula, librenms, rt, racktables) db primary master switchover: 10th Sept 16:00 UTC

2019-08-29 Thread Pine W
Hello,

Does this mean that https://etherpad.wikimedia.org/ will be temporarily
read only? That site seems to be somewhat popular for taking notes during
meetings. If that site will be affected then I recommend that you put up a
site notice there, possibly a multilingual one depending on how much use
the site gets for non-English content.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )



On Thu, Aug 29, 2019, 04:01 Manuel Arostegui 
wrote:

> Hello,
>
> The current primary master for m1 (db1063), which is mostly for internal
> services + etherpad isn't in a great healthy status: it is an old host,
> which needs to be decommissioned and which is having disks failing pretty
> much every week (plus disks on predictive failure).
>
> We have decided to fail it over one of the newer hosts, db1135:
> https://phabricator.wikimedia.org/T231403
>
> We have scheduled this switchover for: Tuesday 10th September at 16:00 UTC
>
> This failover should be rather quick and would only take a few seconds
> (while we re-load the haproxy) - during those few seconds, the following
> services will be on read-only:
>
> bacula
> etherpadlite
> librenms
> puppet
> racktables
> rt
>
> 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] Skipcaptcha assigned to users coming from throttle-exempted IP addresses

2019-07-14 Thread Pine W
Hi Martin,

I think that putting the info in Tech News is a good idea. I would suggest
reaching out to wikis that get large volumes of new users to ask for input
from patrollers and other users who could be affected. Here are a few
places that I would recommend on ENWP for short notices regarding the
proposed change.

* https://en.wikipedia.org/wiki/Wikipedia_talk:Recent_changes_patrol
* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)

I also suggest testing the change in phases before scaling it up to all
wikis, in order to check for unintended consequences.

Thank you in advance for being careful about the implementation of this
change. The change might work perfectly well, but sometimes "the road to
hell is paved with good intentions", so I think that some advance
consultation and a phased rollout with a moderate amount of testing would
be a good idea.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Sun, Jul 14, 2019 at 9:43 PM Martin Urbanec 
wrote:

> Hi Pine,
>
> well, I'm a patroller, admin and a checkuser myself, and as you know, I
> don't see a problem with this change :-). Anyway, I'm just one of them. At
> least in cswiki, admns don't have issues with manually confirming users on
> request by course coordinator, autoconfirmed shouldn't be a big deal.
>
> Don't know how to consult (all) patrollers etc., IIRC there is no central
> list for them or anything like that. Feel free to forward my message to
> anywhere you think it is helpful (please, ping me/CC me in such messages,
> so I can watch the conversation on that place as well).
>
> I've added
> <
> https://meta.wikimedia.org/w/index.php?title=Tech%2FNews%2F2019%2F30=revision=19203494=19203433
> >this
> to next tech news, to notify about this change more widely than "just" on
> wikitech-l.
>
> Martin
>
> pá 12. 7. 2019 v 0:05 odesílatel Pine W  napsal:
>
> > Hi Martin,
> >
> > I'm not familiar with all of the information about how WMF currently uses
> > CAPTCHAs, but I suggest being careful about doing anything that could add
> > to the workloads of volunteer patrollers, admins, and checkusers. My
> > feeling is that you should consult with people who are most likely to get
> > more work as a result of this change, even if you think that any negative
> > impact will be negligible. There may be some requests for carefully
> > designed tests to ensure that any changes do not result in surprise
> > increases to workloads for existing volunteers who already have more than
> > enough work to do.
> >
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> >
> > On Mon, Jul 8, 2019 at 2:37 PM Martin Urbanec <
> martin.urba...@wikimedia.cz
> > >
> > wrote:
> >
> > > Hi,
> > >
> > > I created https://phabricator.wikimedia.org/T227487, which proposes to
> > add
> > > skipcaptcha to all users coming from throttle-exempted IP addresses
> (see
> > > /wmf-config/throttle.php in operations/mediawiki-config for that). This
> > can
> > > make some events go more smoothly. Given users coming from such
> addresses
> > > are generally trusted, this shouldn't be an issue IMHO.
> > >
> > > What do the others think?
> > >
> > > Martin
> > > ___
> > > 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] Skipcaptcha assigned to users coming from throttle-exempted IP addresses

2019-07-11 Thread Pine W
Hi Martin,

I'm not familiar with all of the information about how WMF currently uses
CAPTCHAs, but I suggest being careful about doing anything that could add
to the workloads of volunteer patrollers, admins, and checkusers. My
feeling is that you should consult with people who are most likely to get
more work as a result of this change, even if you think that any negative
impact will be negligible. There may be some requests for carefully
designed tests to ensure that any changes do not result in surprise
increases to workloads for existing volunteers who already have more than
enough work to do.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Mon, Jul 8, 2019 at 2:37 PM Martin Urbanec 
wrote:

> Hi,
>
> I created https://phabricator.wikimedia.org/T227487, which proposes to add
> skipcaptcha to all users coming from throttle-exempted IP addresses (see
> /wmf-config/throttle.php in operations/mediawiki-config for that). This can
> make some events go more smoothly. Given users coming from such addresses
> are generally trusted, this shouldn't be an issue IMHO.
>
> What do the others think?
>
> Martin
> ___
> 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] 今週あなたを幸せにするものは何ですか? / What's making you happy this week? (Week of 16 June 2019)

2019-06-30 Thread Pine W
Hi Isarra and Gergo,

Thanks very much for the feedback.

I appreciate the suggestion about a poll. I have been reluctant to start a
poll about this because I have several other issues that are occupying my
mind at the moment, including WMF's relationship with the
community/communities in general and ENWP in particular. Also, I have other
tasks that I need to complete.

I am continuing to send these threads to Wikimedia-l, and as of this month
an adapted version of these threads is included in *The Signpost*
.

In the future, I think that a poll would be worth considering. In the
meantime I think that Wikitech-l may be well served by the "Thank you
Tuesday" threads.

Regards,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Jun 27, 2019 at 8:53 AM Gergo Tisza  wrote:

> Regular practice of gratitude is well-understood to be a key element of
> personal well-being (and while community health is a less researched area,
> it seems likely that the benefits extend there too). As such these threads
> are IMO very useful.
>
> On Mon, Jun 24, 2019 at 6:40 PM Isarra Yos  wrote:
>
> > Mailing lists aren't really a good place to establish consensus, as
> > every time someone weighs in, everyone is notified, so 'me too's are
> > frowned upon in principle.
> >
> > Perhaps you might want to create an actual poll about preferred venues
> > etc onwiki and then send out a message to wikimedia-l linking to that if
> > you want a more meaningful assessment.
> >
> > -I
> >
___
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)

2019-06-23 Thread Pine W
Hi,

Thank you for the positive comments, Stephan and RhinosF1.

I think that there is not a clear public majority opposed or in favor of
continuing to have these threads on Wikitech-l in their current form. The
relatively small number of people who commented suggests to me that most
readers of this list are neutral. I will err on the side of caution and
stop sharing the threads to Wikitech-l. I will continue to post these
threads to Wikimedia-l. Also, I will share modified versions of the content
for these threads in *The Signpost*
, starting with
the next issue of that publication. If someone would like to create a
Wikitech-specific version of these threads, I think that they are welcome
to do 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

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

2019-06-20 Thread Pine W
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

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

2019-06-19 Thread Pine W
Hi Andre,

I think that whether these threads are welcome by Wikitech-l subscribers in
general is a reasonable question, although I disagree with a number of
elements of your description of these threads. I took a somewhat bold step
in February 2018 of expanding the posting of these threads from Wikimedia-l
to both Wikimedia-l and Wikitech-l, and I expressed a willingness to listen
to objections; see
https://lists.wikimedia.org/pipermail/wikitech-l/2018-February/089495.html.
At that time, no one objected.

Of the occasional feedback that I have received in public (more on
Wikimedia-l than Wikitech-l) and private, 100% has been positive until now.
However, I recognize that people's opinions may change over time. If a
consensus emerges from Wikitech-l subscribers that these threads are not
currently welcome on Wikitech-l then I will respect that and I will stop
cross-posting the threads to Wikitech-l. However, if no such consensus
emerges, then I suggest that you ignore these threads in the future.

The purpose of these emails is certainly not to annoy people, and I regret
if people find them to be more annoying than interesting, useful, or
encouraging.

I hope that people will contribute their own posts to these threads in
response to the prompt, "What’s making you happy this week? You are welcome
to comment in any language." Also, I would be happy to see a new person
start these threads each week, and to see multiple people contribute their
thoughts each week. However, if a new consensus emerges in against having
these threads on Wikitech-l, then I will abide by that consensus.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, Jun 19, 2019 at 11:45 AM Andre Klapper 
wrote:

> On Wed, 2019-06-19 at 07:17 +, Pine W wrote:
> > While browsing Japanese Wikipedia, I found this
>
> As "What's making you happy this week" messages seem to contain no
> questions, no expected interaction or followup on specific technical
> topics, no announcements about specific technical topics, and often no
> connection to the technical scope of wikitech-l@ (in the previous
> message, 1 out of 4 items covered a technical aspect), but seem to be a
> random link list of collected personal interest items:
> Has it been considered to post such messages to a personal blog (or
> such) instead, which might be a more suitable venue?
>
> 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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

2019-06-19 Thread Pine W
While browsing Japanese Wikipedia, I found this

article with beautiful photos. Although I cannot read Japanese, my
understanding from an automated translation is that the article describes
the Tajima Highland Botanical Garden in Kami, Hyogo prefecture, Japan, and
that there are over 2,000 types of plants in these gardens.

The botanical garden article reminded me of an English Wikipedia featured
article that I enjoyed reading, "*Bonshō*
".

There is a series of photos of a high speed Japanese train that is under
consideration for the Featured picture designation on English Wikipedia
.
By looking at the code for this nomination, I learned about the
“frameless” parameter
for images ,
which I think is new to me.

I am a low ranking novice in the subject of continuous integration in
software development ,
and I understand merely some of this email
,
but there appears to be good news regarding MediaWiki CI jobs.

What’s making you happy this week? You are welcome to comment in any
language.

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

Re: [Wikitech-l] Switching to elections for the Code of Conduct Committee?

2019-06-19 Thread Pine W
Hi,

I would like to address the proposal for Technical Code of Conduct
Committee elections in general terms, without discussing specific
incidents.

When selecting candidates for powerful public bodies such as the Technical
Code of Conduct Committee, I think that considerable public scrutiny is
appropriate. There are a variety of ways that this level of scrutiny could
be applied, and I think that public elections are one option that is worth
considering. However, I also encourage us to be mindful that a public
political process of elections can have the unfortunate side effect that
candidates who become members of the Committee and want to retain their
roles for additional terms feel obligated to submit to political pressure
to make decisions regarding the conduct of specific users based on popular
opinion instead of what they believe is correct based on their (one would
hope carefully and skillfully considered) evaluation of facts.

Thank you for raising this topic for discussion.

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] ¿Qué te hace feliz esta semana? / What's making you happy this week?

2019-06-11 Thread Pine W
 Hello colleagues,

I hope that you feel welcome to add your own comments to this email thread.
Your participation would be appreciated, including starting these threads
in future weeks.

I like this

Commons Picture of the Day. The photo is of a sun parakeet. The photo was
taken on the Canary Islands.

The May issue 
of *This Month in GLAM* was published.

What's making you happy this week? You are welcome to comment in any
language.

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] Fwd: [Wikidata] Scaling Wikidata Query Service

2019-06-06 Thread Pine W
Forwarding in case this is of interest.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Guillaume Lederrey 
Date: Thu, Jun 6, 2019 at 7:33 PM
Subject: [Wikidata] Scaling Wikidata Query Service
To: Discussion list for the Wikidata project. 


Hello all!

There has been a number of concerns raised about the performance and
scaling of Wikdata Query Service. We share those concerns and we are
doing our best to address them. Here is some info about what is going
on:

In an ideal world, WDQS should:

* scale in terms of data size
* scale in terms of number of edits
* have low update latency
* expose a SPARQL endpoint for queries
* allow anyone to run any queries on the public WDQS endpoint
* provide great query performance
* provide a high level of availability

Scaling graph databases is a "known hard problem", and we are reaching
a scale where there are no obvious easy solutions to address all the
above constraints. At this point, just "throwing hardware at the
problem" is not an option anymore. We need to go deeper into the
details and potentially make major changes to the current architecture.
Some scaling considerations are discussed in [1]. This is going to take
time.

Reasonably, addressing all of the above constraints is unlikely to
ever happen. Some of the constraints are non negotiable: if we can't
keep up with Wikidata in term of data size or number of edits, it does
not make sense to address query performance. On some constraints, we
will probably need to compromise.

For example, the update process is asynchronous. It is by nature
expected to lag. In the best case, this lag is measured in minutes,
but can climb to hours occasionally. This is a case of prioritizing
stability and correctness (ingesting all edits) over update latency.
And while we can work to reduce the maximum latency, this will still
be an asynchronous process and needs to be considered as such.

We currently have one Blazegraph expert working with us to address a
number of performance and stability issues. We
are planning to hire an additional engineer to help us support the
service in the long term. You can follow our current work in phabricator
[2].

If anyone has experience with scaling large graph databases, please
reach out to us, we're always happy to share ideas!

Thanks all for your patience!

   Guillaume

[1]
https://wikitech.wikimedia.org/wiki/Wikidata_query_service/ScalingStrategy
[2] https://phabricator.wikimedia.org/project/view/1239/

-- 
Guillaume Lederrey
Engineering Manager, Search Platform
Wikimedia Foundation
UTC+2 / CEST

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

[Wikitech-l] Quod facit beatus hic sabbati? / What's making you happy this week? (Week of 2 June 2019)

2019-06-04 Thread Pine W
As usual, I am grateful for the volunteer contributors to the most recent
issue

of The Signpost.

I was happy to see that Wikimedia Canada
 and Library and Archives Canada
 announced a
collaboration
.

Thanks to Brooke Storm (WMF Cloud Services) and Bryan Davis (WMF Technical
Engagement), I found an amusing xkcd depiction  of
successful task automation and unsuccessful task automation.


Here are some recent stories that were published by WMF:

* Four open design methods we used to improve Wikipedia’s iOS app


* With Wikipedia in the classroom, a former student has become the teacher


* Wikimedia Foundation announces tenth transparency report


* Wikimedia Foundation urges Chinese authorities to lift block of Wikipedia
in China


* MediaWiki is the software that underpins Wikipedia. This conference shows
all the other ways it can be used.


* Wikimedia Argentina and the National University of La Plata partner to
promote free knowledge


The Word of the Day for English Wiktionary on June 2nd was "rubicon". I was
familiar with a fictional ship named
Rubicon
 and I guessed that the
name referred to a river, which it does
, but I did not know that more than
one river  is
named Rubicon, and I did not know about many other uses for the name
. Thanks to
Wiktionary, I learned that the word "rubicon" (with a lowercase "r") has its
own meanings
 and
an interesting
etymology  that refers to the the
Italian river as a location of a notable event in history
, and possibly also
refers the red color of the river

.

What's making you happy this week? You are welcome to comment in any
language.

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] Kedu ihe na-eme gị obi ụtọ n'izu a? / What's making you happy this week? (Week of 26 May 2019)

2019-05-29 Thread Pine W
 I was happy to read this announcement
 by
Amir regarding improvements for typing in African languages on Wikimedia
projects. (I hope that the translation of the subject of this week's email
is correct.)

I thought that this
 was
an interesting WMF Tech Talk regarding WMF and W3C. I felt that it was
encouraging that WMF staff on the call wanted to support the needs and
wishes of Wikimedia readers and contributors. Thank you to WMF for
publicizing this meeting and for collaborating with W3C.

Thank you to engineering and technical staff who take initiative to respond
to problems in a timely and constructive way. Someone who comes to mind is
James Forrester, who has endured years of complaints regarding
VisualEditor. Over time WMF has polished the tool's rough edges, greatly
improved its performance, and added significant functionality. I know that
hearing a barrage of complaints can be difficult, such as happens in this video
clip  from *Star Trek: Deep
Space Nine* that is hosted on Youtube. (Yes, another *Star Trek* video. The
title of the episode is shown at the start of the video, which is why it
displays "Honor Among Thieves".) I appreciate James' calm demeanor,
willingness to listen, responsiveness, patience, and perseverance.

What's making you happy this week? You are welcome to comment in any
language.

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] Seni bu hafta ne mutlu ediyor? / What's making you happy this week? (Week of 19 May 2019)

2019-05-23 Thread Pine W
This week I would like to thank people who volunteer significant time and
effort to hunt advertising, undisclosed conflict of interest editing, and
sockpuppet accounts in the Wikiverse. I was reminded of these subjects by this
email
.
For the enjoyment of people who are familiar with *Star Trek: Deep Space
Nine*, there is a relevant video clip
 on Youtube.

I would like to thank WMF for its efforts
 to
persuade the government of Turkey to lift its block of Wikipedia. I hope
that these efforts will succeed.

Congratulations to Wiki Community User Group Tchad

regarding their recognition by the Affiliations Committee.

What makes you happy this week? You are welcome to comment in any language.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

P.S. I am sorry for the late email this week. I am behind on email but I
think that I will catch up by Saturday.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Scrum of scrums/2019-05-22

2019-05-22 Thread Pine W
Regarding the request for feedback on SoS meetings, for me these notes are
frequently interesting and occasionally useful in their current form. I
like having the placeholders for teams so that I can get a sense of what
teams currently exist and how they are named. However, my guess is that
these are expensive meetings in terms of dollars spent on staff time for
meeting preparation, the meetings themselves, and post-meeting
documentation and reading, so I understand the desire to weigh the value of
these meetings and to consider revisions.

Regards,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, May 22, 2019, 09:52 Željko Filipin  wrote:

> I have forgot link to HTML version 臘‍♂️
>
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-05-22
>
> Željko
>
> On Wed, May 22, 2019 at 6:50 PM Željko Filipin 
> wrote:
>
> > Hi,
> >
> > I would like to highlight a few notes from SoS Meeting Bookkeeping:
> >
> > * We're still looking for a backup facilitator. 
> > * We're still looking for feedback if this meeting is useful. If it is,
> is
> > there anything we could do to make it more useful?
> > ** SoS is really useful to Release Engineering because we are frequently
> > blocked by various teams because of train. We also frequently block other
> > teams because we're in charge of continuous integration (CI).
> > ** Should we make the meeting notes as short as possible, so interested
> > people could read all of it? One step in that direction could be removing
> > teams that did not leave any updates.
> >
> > Željko
> >
> > --
> >
> > = 2019-05-22 =
> >
> > == Callouts ==
> >
> > * Train blocked
> > ** Growth - operand type was used:  expects array(s) or collection(s) in
> > /srv/mediawiki/wmf-config/flaggedrevs.php on line 182
> > https://phabricator.wikimedia.org/T224116
> > ** Growth - Special:ProblemChanges on several Wiktionary sites show raw
> > message IDs instead of translated strings
> > https://phabricator.wikimedia.org/T224124
> > * Introducing the codehealth pipeline beta (by Kosta Harlan)
> >
> https://phabricator.wikimedia.org/phame/post/view/160/introducing_the_codehealth_pipeline_beta/
> > * Language -> SRE:
> > https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/506043/
> >
> > == Audiences ==
> >
> > === Contributors ===
> >
> >  Community Tech 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> >
> >  Anti-Harassment Tools 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> >
> >  Editing 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> > ** git #b6704010 - Automatically add a template when chosen from the
> > autocomplete list (Hackathon project)
> > ** git #3285b7db - Initialize $restbaseHeaders to null (T223281)
> > ** Working on a model corruption issue related to selections in VE:
> > (T202719)
> >
> >  Growth 
> > * Blocked by:
> > * Blocking:
> > ** Release Engineering - Train blocked
> > *** operand type was used:  expects array(s) or collection(s) in
> > /srv/mediawiki/wmf-config/flaggedrevs.php on line 182
> > https://phabricator.wikimedia.org/T224116
> > *** Special:ProblemChanges on several Wiktionary sites show raw message
> > IDs instead of translated strings
> > https://phabricator.wikimedia.org/T224124
> > * Updates:
> > ** Introducing the codehealth pipeline beta (by Kosta Harlan)
> >
> https://phabricator.wikimedia.org/phame/post/view/160/introducing_the_codehealth_pipeline_beta/
> >
> >  Language 
> > * Blocked by:
> > ** SRE (BBlack):
> > https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/506043/
> > * Blocking:
> > * Updates:
> >
> > === Readers ===
> >
> >  iOS native app 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> > ** Continuing development on v6.3 - beginning user testing soon
> > *** Talk page MCS endpoint - https://phabricator.wikimedia.org/T221148
> > *** Talk page native work - https://phabricator.wikimedia.org/T215928
> > *** Link wizard in Editor - https://phabricator.wikimedia.org/T213979
> > *** Media wizard in Editor - https://phabricator.wikimedia.org/T209398
> >
> >  Android native app 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> > ** New Beta release with minor bug fixes and enhancements (and with
> > updated logout behavior).
> > ** Continuing to build on the Suggested Edits feature (beginning work on
> > editing structured captions on Commons).
> >
> >  Readers Web 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> >
> >  Readers Infrastructure 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> > ** Maps: node10js migration is finished for a couple of weeks and remains
> > stable
> >
> >  Multimedia 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> > ** qualifiers for depicts statements now on test-commons, should reach
> > commons itself later in the week
> > ** next release - other statements, within the next few weeks
> >
> >  Parsing 
> > * Blocked by:
> > * Blocking:
> > * Updates:
> >
> >  UI Standardization 
> 

Re: [Wikitech-l] planned Phabricator upgrade tomorrow

2019-05-22 Thread Pine W
OK, thanks for the info.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Wed, May 22, 2019, 03:01 Mukunda Modell  wrote:

> Indeed, routine Phabricator maintenance is scheduled to take place every
> Wednesday at 0:00 UTC.
> This maintenance window is not always utilized as we only make changes once
> or twice each month.
> When there is a maintenance task, typical downtime is less than 5 minutes.
> When nothing needs to be done for a given week,
> I try to at least !log the absence of any maintenance. Realistically though
> I often forget to do that.
>
> This week the planned work involves a lot of changes so expect a few
> minutes of downtime while we switch everything over.
> Then we will take a few more minutes to validate that the new system is
> working as expected, if not we will roll back to the old one.
>
> Optimistically I'd guess that the whole process takes 10 to 15 minutes with
> downtime closer to 5 minutes.
>
> On Wed, May 22, 2019 at 2:02 AM Lewis Cawte via Wikitech-l <
> wikitech-l@lists.wikimedia.org> wrote:
>
> > To answer the first part of your question, Pine, Daniel's email was sent
> at
> > 01:52 UTC on the 22nd. So tomorrow would refer to 00:00 on the 23rd.
> >
> > -- Lewis Cawte (Lcawte)
> >
> > On Wed, 22 May 2019 at 07:26, Pine W  wrote:
> >
> > > Hi, thanks for the notice. Can you specify whether "tomorrow" refers to
> > 22
> > > May UTC or 23 May UTC, and how long the maintenance window is likely to
> > be?
> > > Some of us may want to read or write a Phabricator
> > > complaint task during the maintenance window, and if
> we
> > > know when to expect Phabricator may be temporarily unavailable then we
> > can
> > > plan accordingly.
> > >
> > > Pine
> > >
> > > ( https://meta.wikimedia.org/wiki/User:Pine )
> > >
> > >
> > >
> > >
> > >
> > > On Tue, May 21, 2019, 17:52 Daniel Zahn  wrote:
> > >
> > > > Tomorrow we have planned a major upgrade of the Phabricator prod
> > server.
> > > >
> > > > Starting from around 00:00 UTC (after Evening SWAT) we want to switch
> > > from
> > > > phab1001 to phab1003 as the production server.
> > > >
> > > > This will involve:
> > > >
> > > > - switching from jessie to stretch
> > > > - switching from mod_php to php-fpm
> > > > - switching from PHP 5 to PHP 7.2
> > > > - upgrading apache from 2.4.10 to 2.4.25
> > > >
> > > > We are also hoping it will finally fix the httpd memory leaks we have
> > > been
> > > > seeing on the current server for a long time and which require
> periodic
> > > > service restarts.
> > > >
> > > > In case we run into any unexpected issue we will simply fall back to
> > > > phab1001
> > > > and keep running as before.
> > > >
> > > > https://phabricator.wikimedia.org/T221389
> > > > https://phabricator.wikimedia.org/T182832
> > > > https://phabricator.wikimedia.org/T190568
> > > > https://phabricator.wikimedia.org/T151070
> > > >
> > > > Cheers,
> > > >
> > > > Daniel and Mukunda
> > > >
> > > > --
> > > > 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 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] planned Phabricator upgrade tomorrow

2019-05-22 Thread Pine W
Hi, thanks for the notice. Can you specify whether "tomorrow" refers to 22
May UTC or 23 May UTC, and how long the maintenance window is likely to be?
Some of us may want to read or write a Phabricator
complaint task during the maintenance window, and if we
know when to expect Phabricator may be temporarily unavailable then we can
plan accordingly.

Pine

( https://meta.wikimedia.org/wiki/User:Pine )





On Tue, May 21, 2019, 17:52 Daniel Zahn  wrote:

> Tomorrow we have planned a major upgrade of the Phabricator prod server.
>
> Starting from around 00:00 UTC (after Evening SWAT) we want to switch from
> phab1001 to phab1003 as the production server.
>
> This will involve:
>
> - switching from jessie to stretch
> - switching from mod_php to php-fpm
> - switching from PHP 5 to PHP 7.2
> - upgrading apache from 2.4.10 to 2.4.25
>
> We are also hoping it will finally fix the httpd memory leaks we have been
> seeing on the current server for a long time and which require periodic
> service restarts.
>
> In case we run into any unexpected issue we will simply fall back to
> phab1001
> and keep running as before.
>
> https://phabricator.wikimedia.org/T221389
> https://phabricator.wikimedia.org/T182832
> https://phabricator.wikimedia.org/T190568
> https://phabricator.wikimedia.org/T151070
>
> Cheers,
>
> Daniel and Mukunda
>
> --
> 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] Qu'est-ce qui te rend heureuse cette semaine? / What's making you happy this week? (Week of 12 May 2019)

2019-05-14 Thread Pine W
I think that the mobile Suggested Edits feature and the related analysis
are interesting. I am forwarding text from that discussion.

Also, I was happy to see the recognition of two new user groups. They are
the WikiClassics User Group and the Wikimédiens du Bénin User Group.

What's making you happy this week? You are welcome to comment in any
language.


Pine

( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Charlotte Gauthier
Date: Tue, May 14, 2019, 08:07
Subject: Re: [WikimediaMobile] Stats & data from launch of Suggested Edits
on Wikipedia Android app


Thanks for this great info, Mikhail, and for the work that went into
producing this useful - and beautiful! - report.

We do indeed have plans to experiment with the thresholds to find the
optimum balance point between wide adoption and maintaining contribution
quality, to extend the feature with new microcontribution types, and to
begin intensive testing to find ways to encourage users to explore more of
the feature, and to inspire long-term use. Advertising new contribution
types and re-activation of editors who have previously tried the feature
will be one of the mainstays of our push messaging strategy.

If anyone is interested in our particular plans over the next year, don't
hesitate to get in touch. We've already been having wider discussions with
several teams on how we could possibly work together towards mutual goals.

Cheers,
Charlotte

On Fri, May 10, 2019 at 9:37 PM Mikhail Popov  wrote:

> Hi folks,
>
> I wanted to highlight a few really interesting pieces of data/stats
> regarding the release of the Suggested Edits feature on Wikipedia app for
> Android. These come from the daily report
> ,
> which is also where you'll find a brief description of the feature.
>
> First, at this time 25.3% of editors (whose contributions are being
> tracked since launch of the backend) have unlocked the feature by making
> the 5+ title description edits
> 
> currently required to unlock it. (See: unlock stats
> )
> That's 632 editors out of the 2495 editors who have made at least one title
> description edit since April 5th. We have plans to experiment with this
> threshold and see what happens if we lower the barrier to entry.
>
>
> By the way, we don’t expect all logged-in users to edit or unlock the
> feature (by making the required number of title description edits), as
> there are incentives on the mobile apps to use an account just for reading
> (e.g. reading list syncing
> ).
> However, perhaps we should advertise this ability better (especially to
> logged-in users) and that those title descriptions don’t require any
> knowledge of wikitext.
>
>
> And since the production release, the feature has had a steady stream of
> 20+ users unlocking it per day. What are our users doing with it once they
> unlock it? They’ve been using it! (Sorry if the text in the included graph
> is too small to be legible, it's larger in the report.)
>
> Nearly half of all title description edits made with the Android app each
> day are coming in from editors using the Suggested Edits feature to add &
> translate descriptions. More than half, even, on some days! Furthermore,
> some of those edits are made by users who have previously used the feature.
> Every day we have some editors who are using Suggested Edits for the first
> time, but there are also quite a few who are returning to the Editor Tasks
> screen & contributing more. (See: edit stats
> 
> )
>
> “Okay, so what’s the quality of those 200-400 descriptions being added
> every day?” you might ask. Well, one way we can check that is to check how
> many of those edits are reverted within 48 hours. Turns out, almost none
> of them:
>
> This is especially impressive when compared to the proportion of other
> title description edits that are reverted. (See: revert rate
> 
> )
>
> When the user goes to the Suggested Edits screen and opens a task, they
> begin receiving suggestions of articles to add descriptions to (or
> translate descriptions, if they have unlocked that next tier of Suggested
> Edits). On average, users express interest in editing 30-40% of those
> suggestions. Among the suggestions they tapped to edit, they end up
> actually making an edit around 60% of the time (although the average varies
> from 40% to 70%). (See: interactions
> 

[Wikitech-l] What's making you happy this week? (Week of 5 May 2019)

2019-05-06 Thread Pine W
I am trying to restart the "What's making you happy this week?" threads.


I am grateful for the volunteers who are facilitating significant portions
of the selection process

for two WMF Board seats.

Also, I was happy to see a new issue of *The Signpost*. In addition to the
many interesting pieces of information in this issue, I appreciated the
Wikipedia humor of renaming this visual depiction to *Simplified Guide to
Categories*
.


Preparations for Wikimania 2019 sound like they are going well. I am very
interested in the conference’s highlighting
 of the United Nations
Sustainable Development Goals.

Finally, I join with others in congratulating Wikimedia Korea for its promotion
to chapter

.

What's making you happy this week? You are welcome to comment in any
language.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )

P.S. Sometimes I try to translate "What's making you happy this week?" into
an additional language that is related to the content of the email, but
this week I had significant doubts regarding the the automated translations
that I received for Korean and Swedish, and I was unable to create a manual
translation that was likely to be accurate. I enjoy seeing diverse
languages on Wikimedia mailing lists. If I continue to start these threads
then I will continue to try to translate the titles. Anyone else who would
like to start one of these threads in a future week is welcome to take the
initiative!
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Temporary personal break from mailing lists

2019-03-23 Thread Pine W
Hi mailing list colleagues,

I'm not sure whether I should make this be public, but I tend to be a
frequent participant on mailing lists so maybe sharing this would be good.

I am taking a temporary break from participating on Wikimedia mailing
lists. Recently I am finding myself frequently experiencing frustration in
conversations on lists, and I am concerned that in my frustration I may
write something that I later regret. Also, I would like to be a generally
positive presence on the lists, and I think that a "reset" would be good.

I will remain in the Wikiverse for the foreseeable future. I like
Wikimedia's educational mission, and I like my current principal project. I
will continue to be a list subscriber, and may occasionally read list
discussions. Also, I will continue to read off list emails. Perhaps in a
month or two I will resume participating on lists.

Thanks for all that you do in support of the mission. The Wikiverse is
amazing and I am grateful to be a small part of it.

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

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

2019-03-21 Thread Pine W
On Wed, Mar 20, 2019, 3:32 PM Nick Wilson (Quiddity) 
wrote:

> Pine,
> please see the exact (quite precise) definition of
> https://en.wiktionary.org/wiki/technical_debt
> https://en.wikipedia.org/wiki/Technical_debt
> https://martinfowler.com/bliki/TechnicalDebt.html
> I.e. Technical debt is Not at all equivalent to "bugs". The topic is a
> tangential one. Software can work perfectly fine for end-users even if it
> has a lot of "technical debt", it is just a pain for developers to change
> anything in it or connected to it because the code has complex issues (it's
> a mess, or imperfectly architected at a higher-level, or "icky", or other
> factors). It is not possible to measure, and is somewhat subjective in
> nature.
>

Thanks for correcting me regarding the definition. That helps. (One of
these days I will probably write something that will reveal a deep
ignorance of a Wikimedia topic, and I'm sure that I will hear about it.
Making errors is one way to learn, although it is a way that I often make
an effort to avoid.)


> Overall this thread is going in circles, and I recommend dropping it here.
> There are several good suggestions above if anyone wants to put effort into
> actual solutions.
>

It sounds like we have different perspectives. However, get the impression
that people are getting tired of the this topic, so I'll move on.


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] Comments and questions regarding VisualEditor, Citoid, and Parsoid

2019-03-20 Thread Pine W
I'd like to say thanks to the folks who have been working on VisualEditor,
Citoid, and Parsoid in the past few years.

When I first started to work in 2015 on what I eventually called the LearnWiki
project
,
I was a bit hesitant to recommend VisualEditor due to it having some rough
spots in performance and reliability, but I knew that VE was probably the
way of the future for new Wikipedia contributors. As I've been writing
scripts recently for a 2019 small pilot project that will teach users how
to create citations with VE
,
I've been impressed by how much has improved. The VE's performance seems to
be faster, the automatic citation tool can be easy and enjoyable to use,
and the system (VE + Parsoid + Citoid) seems to be generally stable on ENWP.

I think that you made the desktop user experience significantly better for
new contributors on ENWP who use VE.

While I'm writing, I'll ask a couple of related questions. If someone knows
of recent research that analyzes the productivity and longevity of new
users who try the VE and/or New Wikitext Editor ("NEWT") interfaces, I
would be appreciative if that information could be added to this project
talk page

so that I can take a look. Especially interesting would be research that
shows points in workflows on English Wikipedia where new editors who use VE
seem to become stuck. (The sticking points may have more to do with
policies than with interfaces.) Also, Guy Macon has asked some questions here
(a secton of the same talk page)

regarding the percentage of editors that use different editing interfaces.
Please participate on the talk page if you have the time and interest.

Thanks again for the good work on VisualEditor and related systems.

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

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

2019-03-20 Thread Pine W
:) Structured data exists regarding many other subjects such as books and
magazines. I would think that a similar approach could be taken to
technical debt. I realize that development tasks have properties and
interactions that change over time, but I think that having a better
quantitative understanding of the backlog would be good and would likely
improve the quality of planning and resourcing decisions.

To use an analogy, as far as I know there is no project management system
that reliably produces accurate estimates of the time and resources
required to complete large projects, but I think that attempting to use a
project management system is, in many cases, better than trying to execute
a large project without a project management system.

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

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

2019-03-20 Thread Pine W
On Tue, Mar 19, 2019 at 4:16 PM Gergő Tisza  wrote:

> On Mon, Mar 18, 2019 at 3:01 PM Derk-Jan Hartman <
> d.j.hartman+wmf...@gmail.com> wrote:
>
> > Last year has seen a lot of focus on Technical Debt. WMF also has a core
> > platform team now, which finally allows a more sustainable chipping away
> at
> > some of the technical debt.
>
>
> Yeah. Having tech debt is never great but what gets people concerned is
> when it just grows and grows, and management dismisses concerns because it
> is always more important to have the next feature out quickly. We used to
> have a bit of that problem, but IMO there have been lots of positive
> changes in the last two years or so, and there is now a credible
> organization-wide effort now to get debt under control (mainly looking at
> the Platform Evolution program here). Having the core platform team also
> helped a lot, and in my impression some other teams that had in the past
> focused on fast feature iteration have also been given more space to do
> things right.



Thanks very much for the explanations regarding that point.

One of my continuing concerns is that, as far as I know, no one has a way
of reliably quantifying the scale of the technical debt or measuring how it
is changing over time. It sounds like the internal view in WMF is that the
situation is improving, which is good to hear. However, I would prefer to
have a way to measure technical debt and how it is changing. If that
information is available then I think that making decisions about
resources, priorities, etc. will involve less guesswork. I think that this
proposal could align with WMF's work on code health.(See
https://www.mediawiki.org/wiki/Code_Health).

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

Re: [Wikitech-l] Gerrit outage

2019-03-20 Thread Pine W
I'd like to give a quick thanks to folks who have been dealing with
turbulence.

I think that short term mitigation measures sound reasonable, while longer
term improvements are planned and developed.

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

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

2019-03-18 Thread Pine W
Hi,

First, I'll respond to Scott's comment that " A secondary issue is that too
much wiki dev is done by WMF/WMFDE employees (IMO); I don't think the
current percentages lead to an overall healthy open source community. But
(again in my view) the first step to nurturing and growing our non-employee
contributors is to make sure their patches are timely reviewed."

I'll make a distinction between two types of proposals:

a, Offload development work from WMF onto volunteers, and
b, Grow and support the population of developers..

The first type of proposal is likely to get a cold reception from me, but
I'm more supportive of the second. I don't know how many non-Wikimedia
organizations which use MediaWiki software have staff that contribute in
significant ways to WMF in the forms of software, time, or money, but
growing the significance of those contributions sounds like a good idea. I
also like programs such as GSoC and Outreachy, and for WMF providing
support for volunteer devs who create tools, bots, etc. on their own
initiative.

Second, returning to the subject of technical debt, my understanding was
that WMF staff were concerned for years about the accumulation of technical
debt, but in this thread I get the impression that WMF staff has changed
their minds. Am I misunderstanding something? If the consensus opinion
among the staff changed, how and why did that change happen?

Thanks,

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

Re: [Wikitech-l] Gerrit outage

2019-03-16 Thread Pine W
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, 12:25 PM John Bennett  wrote:

> 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 appropriate updates to the phabricator task (
> https://phabricator.wikimedia.org/T218472 ) .
>
> Thanks
>
>
> On Sat, Mar 16, 2019 at 10:26 AM John Bennett 
> wrote:
>
> > 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 this incident as well as
> > potential improvements to prevent future incidents. More information will
> > be posted on Phabricator (https://phabricator.wikimedia.org/T218472 ) as
> > it becomes available and is confirmed. If you have any questions, please
> > contact the Security (secur...@wikimedia.org
> > ).
> >
> >
> > 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] Question to WMF: Backlog on bugs

2019-03-15 Thread Pine W
Stas made a point that I was considering too, although from a different
perspective.

One of the issues may be a difference between end user expectations and
what the resources are available to fulfill those expectations.

Communications requires time and mental bandwidth, both of which are
limited resources for everyone, including WMF staff and end users. Also,
there are financial considerations regarding how people use their time.

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 patience of the user. I think that communicating with users
regarding when bugs will likely be fixed would be helpful. I think that
some of that happens already, but there's more that can be done. There are
probably ways to automate some of these communications to a degree.

On the larger scale, I don't know whether it's possible to get a good large
scale understanding of all of the open tasks in Phabricator. I speculate
that teams might be able to create semi-automated reports regarding their
own teams' tasks. To get a larger view of the situation in Phabricator
might require combining the unique outputs of the reports from individual
teams. By having a big picture view of the situation I hope that we could
improve our collective situational awareness regarding tasks, including
open feature requests and technical debt. Also, by creating snapshots of
the results of the same type of combined report over a period of months or
years, maybe we could get a sense of how technical debt is changing over
time.

To summarize: I am thinking that a two pronged approach would be good, one
regarding communications regarding the status of individual bugs, and one
regarding a big picture analysis of technical debt.

I realize that there would be costs of time and money for both of those
approaches. Automation can help with both.

My guess is that managing thousands of bugs in an continuous development
environment is challenging in the best of circumstances. I am somewhat
familiar with the end user experience and financial considerations (both of
which motivated me to participate in this thread), but I'm not an expert in
software engineering for a product that is on the scale of a top 10 website.

What do others think regarding these proposals?

Thanks for the good discussion.

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

Re: [Wikitech-l] Community-Engineering gaps as defined in configuration

2019-03-13 Thread Pine W
I believe that I've seen discussions of RC patrolling on ENWP too, although
I can't recall specifics. I am not familiar with the original discussion,
although my first guess is that the experienced patrollers were surprised
and that the surprise factored into their opposition to the change.

Starting an RfC regarding this would require some effort, but if other
communities are finding that the tool is useful, then I'll +1 the hope that
ENWP reconsiders this. Similar to Amir's comment, I'm thinking that having
participation in the discussion from someone like a WMF Community Relations
person or someone who could offer training might be useful so that people
can familiarize themselves with the option before making a decision. I
haven't used the tool myself, but in general I prefer that people have
"informed consent".

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Tue, Mar 12, 2019 at 5:00 PM James Forrester 
wrote:

> On Sat, 9 Mar 2019 at 11:50, bawolff  wrote:
>
> > In regards to wgUseRCPatrol - I suspect (but don't know) that originally
> > that was disabled on enwiki as a performance thing. If it was a
> performance
> > concern, that's probably irrelevant at this point.
> >
>
> Sadly, no. It was enabled as a new feature to help communities do their
> patrolling work. A small handful on enwiki power users complained in the
> hours after it was deployed about the "disruption" (the appearance of a !
> on edits in Recent Changes), and rather than help the community adjust to
> the new software and find it useful, the feature was disabled, effectively
> permanently. In the subsequent years, many English Wikipedians have
> complained about the lack of support for their work on Recent Changes
> patrolling, but there's been no effort to struggle through the community
> arguments to (re-)enable this tool, I believe.
>
> It would be lovely if we could enable this feature on the English Wikipedia
> given how useful many other communities have found this, but I don't expect
> it to happen.
>
> J.
> --
> *James D. Forrester* (he/him  or they/themself
> )
> 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] Question to WMF: Backlog on bugs

2019-03-13 Thread Pine W
Hopefully I can say this in a way that is mutually acceptable.

For me this discussion is difficult but enlightening. I think that this is
the most difficult Wikimedia discussion in which I have been a participant
so far this year. I don't know what agreements will emerge from this
thread, if any. But the enlightenment is useful, and I hope that other
people also feel that they are learning something new or are being heard on
issues that are important to them.

I am thinking that ideally we would all be in a room together to have this
discussion. Perhaps a second best choice would be an online meeting
regarding the subject of technical debt. We could schedule a meeting via
Doodle. It's okay if people don't want to participate, but I'd like to
suggest an online meeting as an option.

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

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

2019-03-12 Thread Pine W
Andre, good points, thanks. I think that this ties in with my comments
regarding having a common situational awareness. I don't think that I have
good situational awareness regarding the state of the backlog, the
composition of the backlog, etc. I'm confident that there is a backlog and
that there are tasks in that backlog which I would like to see solved, but
it's difficult to get a sense of the big picture.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Tue, Mar 12, 2019 at 9:13 PM Andre Klapper 
wrote:

> On Tue, 2019-03-12 at 20:34 +0000, Pine W wrote:
> >
> > 1. My impression is that there's agreement that there is a huge backlog.
>
> Phabricator is public. Anyone can propose and report anything. Hence
> the number of ideas, bugs, feature requests is usually higher than the
> number of available developers (paid or not) needed to work on them.
> Hence the number of tasks which will remain unresolved grows.
> Because in theory someone could always show up and provide a patch.
>
> If you know a larger free and open source software project where the
> number of resolved (not: declined) tickets per month/year/etc is higher
> than the number of open(ed) tickets, I'd be curious to know.
>
> > 2. I think that there's consensus that the backlog is a problem.
>
> No, why?
>
> There are likely quite some ideas that don't make much sense to
> prioritize and fix (out of project scope, time consuming because of
> required huge architecture changes, increased test complexity and
> maintenance costs after adding yet another preference, etc etc).
>
> And many ideas and bugs that will not get fixed (limited number of
> available developers, different individual and group priorities) until
> you (or someone else) writes code if you're really interested in seeing
> that fixed. (If that idea is considered 'in scope' - see above.)
>
> And disappointment *if* someone makes a decision to decline a request.
> And followup discussion to challenge someone's decision which takes
> time that could have been spent to work on tasks that someone considers
> more important.
> In practice, people and time are limited resources.
>
> 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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

2019-03-12 Thread Pine W
I'm going to make a few points that I think will respond to some comments
that I've read, and I will try to organize some of my previous points so
that they're easier to follow.

1. My impression is that there's agreement that there is a huge backlog.

2. I think that there's consensus that the backlog is a problem.

3. I think that we're collectively unsure how to address the backlog, or
how to analyze the backlog so that everyone has shared situational
awareness, but we collectively seem to agree that the backlog should be
addressed.

If any of the above is wrong, please feel free to say so.

Regarding my own opinions only, I personally am frustrated regarding
multiple issues:

a. that there's been discussion for years about technical debt,

b. that WMF's payroll continues to grow, and while I think that more
features are getting developed, the backlog seems to be continuing to grow,

c. that WMF, which has the largest budget of any Wikimedia entity, is not
more transparent regarding how it spends money and what is obtained from
that spending;

d. that although I think that the Community Liaisons help a lot with
communications, there remains much room for improvement of communications.
One of my larger frustrations is that the improvements regarding
communications have not been more extensive throughout all of WMF.

e. that WMF retains the ability to veto community decisions regarding
decisions such as deployments of features, but the community has little
ability to veto WMF decisions. I think that staff as individuals and
collectively have become more willing to negotiate and yield ground in the
past few years, which is good, but I remain concerned that these are
informal rather than formal changes.

f. that I think that some of what WMF does is good and I want to support
those activities, but there are other actions and inactions of WMF that I
don't understand or with which I disagree. Conflicts can be time consuming
and frustrating for me personally, and my guess is that others might feel
the same, including some people in WMF. I don't know how to solve this. I
realize that some people might say "Then you should leave", and I regularly
consider that option, but Wikipedia and the sister projects do a lot of
good, so I'm torn. This is very much my personal issue and I don't expect
to discuss it more on Wikitech-l, but it's a factor in how I think about
this email thread, which is why I mention it.

I hope that this email provides some clarity and is useful for this
discussion.

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

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

2019-03-09 Thread Pine W
This discussion touches on a number of my frustrations. If someone is in a
bad mood then they might want to postpone reading my comments below.

As far as I know, WMF wants to advertise itself as being a provider of
infrastructure for fundraising purposes, and wants to exercise absolute
power over technical matters (see, for example, Superprotect). I think that
it would be difficult to reconcile these factors with an attempt by WMF to
disclaim responsibility for deficiencies in the technical infrastructure
that WMF created and remains in use on Wikimedia sites. (I think that this
does not generally extend to bots, tools, etc. that were not primarily
created by WMF.)

Regarding "There's an anti-pattern here: we all have a big mailing list
discussion,
agree there's a problem, agree that the Foundation should solve the
problem, then ask again in a year what they did even though they didn't
actually say they'd do anything about it. That's not a healthy dynamic.":
if WMF doesn't say that it will fix a widely known problem, that is not
necessarily an excuse for not fixing it by a year later, and may also
indicate a failure by WMF to clearly communicate what it *won't* fix.

It's true that for profit companies can sometimes ignore important bugs and
have poor customer service, but when a provider is not a monopoly then
customers who are unhappy can (with varying amounts of expense and pain)
change providers.

Other organizations being sloppy does not imply that WMF should follow
their bad example or make excuses that WMF is probably no worse than others.

I don't agree that the technical space is owned by all of us. WMF never
apologized for Superprotect, and there is nothing to stop WMF from making
arbitrary decisions against community consensus other than the threats of
(1) community members quitting in substantial numbers and (2) bad press
coverage. Also, WMF's technical services are one of the primary
justifications for WMF's budget.

I believe that WMF does a lot of good for the world, but it also has a lot
of room for improvement, and hearing excuses (or getting no substantive
responses) regarding the same problems year after year gets old,
particularly as WMF's payroll continues to grow.

These subjects are frustrating and depressing for me, so let me close on a
more positive note. I am glad that we have these discussions in public, and
the strategy process may be a way to make progress. Also, I think that WMF
has improved the infrastructure over the years. For example, I like the New
Wikitext Editor, and I think that VisualEditor is now a good option for
many use cases. Citoid is wonderful. Wikimedia sites generally seem to be
more performant than in years past. The Search Platform team seems to do a
lot of good work. I like the new edit filters in the watchlist.

So, much good has been done, and there remains much to improve.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Sat, Mar 9, 2019, 4:13 AM Dan Garry (Deskana)  wrote:

> On Sat, 9 Mar 2019 at 11:26, Strainu  wrote:
>
> > How many successful commercial projects leave customer issues unresolved
> > for years because they're working on something else now?
> >
>
> Almost all of them, they just keep it secret. Companies pay millions of
> dollars each year for support packages, even after having paid for software
> in the first place, specifically because otherwise their support issues may
> not be answered in a timely fashion, or even answered at all. I don't think
> comparing us to commercial products makes much sense in this context.
>
>
> > There were a
> > number of proposals on how to track such issues so that reporters have a
> > clear image of the status of the bugs. Have any of them been tried by at
> > least one of the teams at wmf? If so, is there a way to share the results
> > with other teams? If not, how can we convince the wmf to give them a
> > chance?
> >
>
> I don't agree with shifting responsibility onto the Wikimedia Foundation.
> There's an anti-pattern here: we all have a big mailing list discussion,
> agree there's a problem, agree that the Foundation should solve the
> problem, then ask again in a year what they did even though they didn't
> actually say they'd do anything about it. That's not a healthy dynamic.
>
> The technical space is owned by all of us, so if we, as a technical
> community, decide this is important to us, then we can look at the problem
> and try to tackle it, and then figure out how the Wikimedia Foundation
> could catalyse that.
>
> Dan
> ___
> 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] Fwd: [Wikimedia-l] Project Grants program will fund 20 community-led projects

2019-03-01 Thread Pine W
Forwarding in case people are interested in seeing what was funded.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


-- Forwarded message -
From: Chris "Jethro" Schilling 
Date: Fri, Mar 1, 2019 at 9:06 PM
Subject: [Wikimedia-l] Project Grants program will fund 20 community-led
projects
To: Wikimedia Mailing List 


Hi folks,

In the latest round of Project Grants, the committee has recommended 20
projects for a total of approximately $678,666 USD in funding.  We received
42 proposals for review, the largest round of proposals we’ve received in a
single round. Please join me in congratulating the applicants! I’d also
like to express my thanks to all applicants this round for their hard work
and engagement with their proposals, and to the Project Grants Committee
for their careful diligence in reviewing and providing crucial feedback
during this round. Without further ado, here’s what we’re funding:[1]

==Software: five projects funded==* Commons Android app v3: This third
version of the Commons mobile uploader app aims to increase app stability,
improve a recommendations feature for nearby places, maintain a limited
connectivity mode, and provide better outreach to underrepresented
communities. [2]

* Scribe: Scribe is an editing tool to support underserved Wikipedia
editors, helping them to plan the structure of their new articles and to
find references in their language.[3]

* Culture Gap Monthly Monitoring: The Wikipedia Cultural Diversity
Observatory (WCDO) proposes a set of solutions to regularly assist
communities and individual editors to increase the cultural diversity in
their language editions’ content.[4].

* GlobalFactSyncRE: GlobalFactSyncRE will extract all infobox facts and
their references to produce a tool for Wikipedia editors that detects and
displays differences across infobox facts in an intelligent way to help
sync infoboxes between languages and/or Wikidata. The extracted references
will also be used to enhance Wikidata.[5]

* Wikidata & ETL: This project aims at improving management and increasing
automation of processes loading data into Wikidata, and proposes a tool as
a platform for creation of repeatable processes for bulk loading data into
Wikidata and other Wikibase instances from various data sources.[6]

==Online organizing: four projects funded==* Wiki Loves Monuments
international team/2019 coordination: The international coordination team
for Wiki Loves Monuments (WLM) [7] proposes to strengthen the foundation
for healthy and sustainable WLM competitions across the world. In this
grant, the team will focus considerable effort on increasing the
sustainability of these events by addressing known issues around developing
best practices, resourcing local teams to run successful events, and
adapting to mobile engagement.[8]

* CEE Spring 2019: This annual international article writing contest
generates
content from every country and region in Central and Eastern Europe on 30+
Wikipedias.  CEE Spring’s remarkable community spirit plays a central role
in fostering a thriving, collaborative volunteer base in the region. The
grant will continue incentivizing content creation focused on similar
themes from last year, including closing the gender gap, and expanding
minority language Wikipedias, and showcasing the cultural heritage of
Central and Eastern Europe. [9]

* WM HU/Editor retention program: This grant will fund the editor retention
program in the Hungarian Wikipedia. The project helps the Hungarian
Wikipedia community in decreasing the negative experiences and
strengthening the positive experiences of the contributors; improving the
community atmosphere and strengthening the community cohesion, the
Wikipedia identity, the sense of mission and pride in Wikipedia.[10]

* VisibleWikiWomen2019: Whose Knowledge?, in partnership with Wikimedians
and women’s and feminist organizations around the world, is organizing a
campaign to add more diverse and quality images of women to Commons and
Wikipedia throughout March 2019 to celebrate International Women’s Month.
This year, the organization plans to take what they have learned from 2018
#VisibleWikiWomen and grow the campaign, creating more materials and
connections that will be useful for this year’s campaign and many more
years to come.[11]

==Offline outreach: ten projects funded==* Smithsonian
Wikimedian-in-Residence for Gender Representation: This project will
establish a Wikimedian-in-Residence for the Smithsonian Women's History
Initiative, and increase the representation of women on Wikimedia projects,
and seek ongoing support for a permanent Wikimedian-in-Residence at the
institution.[12]

* Action Plan for Wikipedia + Libraries Training in Mexico: OCLC will
investigate the viability of and approach to a Wikipedia+Libraries training
program for library staff in Mexico, to leverage the libraries in support
of the Wikimedia Foundation’s New Readers initiative. This project will
identify a Mexico-based 

Re: [Wikitech-l] Invitation to a "Wikimedia Café" casual online meetup

2019-02-20 Thread Pine W
Hi,

Taking into consideration the input from the Doodle poll, I'm scheduling
this meetup for March 29th at 8:15 AM Pacific / 3:!5 PM UTC.

Reminder: the focus of this meetup will be communications in the Wikiverse.

See you there,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Sat, Feb 9, 2019 at 3:38 AM Pine W  wrote:

> Hi,
>
> For the next Wikimedia Café online meetup we will focus on the subject of
> communications in the Wikiverse. What about communications is working well,
> what is not working well, and what should be done to improve
> communications? This will be a casual discussion but formal proposals may
> emerge from it, and at the meetup people are welcome to discuss their ideas
> for formal proposals. Participants are also welcome to suggest topics for
> discussion other than communications, but the plan is to spend the majority
> of the time on the subject of communications.
>
> The Café meetup will be in late March, on a time to be chosen via Doodle
> poll: https://doodle.com/poll/t3w8nkt9vy5mm3r5. I am skipping February
> due to some existing commitments. When you visit the Doodle poll you should
> be able to change the timezone that you see for the calendar. Please be
> sure to select the correct timezone for you before you vote.
>
> I will host the meeting using the free version of Zoom. Zoom limits the
> length of meetings using the free version to 40 minutes.
>
> The Zoom online meeting link will be the same link that we have used for
> previous Wikimedia Café meetups; see below.
>
> If you would like to attend then please vote in the Doodle poll.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> On Thu, Aug 9, 2018 at 11:15 PM Pine W  wrote:
>
>> Hi folks,
>>
>> Based on comments that I received on Wikimedia-l, I would like to invite
>> people to a casual online meetup one hour before the monthly WMF Metrics
>> and Activities Meeting.
>>
>> There will be no set agenda. You can come with questions or ideas that
>> you would like to discuss. Please be willing to listen to questions and
>> ideas from other Wikimedians.
>>
>> I will host the meeting with the Zoom software. You can join with
>> software or by using your phone. If you join by phone then your phone
>> number will be visible to other participants.
>>
>> The primary language of the meeting will be English, but if people would
>> like to communicate in diverse languages then that is okay too. We can
>> facilitate translation by text chat. Many Wikimedians, myself included, are
>> multilingual in varying degrees, so we might try to have live
>> interpretation also.
>>
>> Here is information about how to connect:
>>
>> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
>>
>> Or iPhone one-tap :
>> Argentina: +543415122188,,136978210#
>> Or Telephone:
>> Dial (for higher quality, dial a number based on your current
>> location):
>> Argentina: +54 341 512 2188
>> Australia: +61 (0) 2 8015 2088  or +61 (0) 8 7150 1149
>> Canada: +1 647 558 0588
>> Hong Kong, China: +852 5808 6088
>> France: +33 (0) 1 8288 0188  or +33 (0) 7 5678 4048
>> Germany: +49 (0) 30 3080 6188  or +49 (0) 30 5679 5800
>> Israel: +972 (0) 3 978 6688
>> Italy: +39 069 480 6488
>> Japan: +81 (0) 3 4578 1488  or +81 524 564 439
>> Mexico: +52 229 910 0061  or +52 554 161 4288
>> Spain: +34 84 368 5025  or +34 91 198 0188
>> Sweden: +46 (0) 7 6692 0434  or +46 (0) 8 4468 2488
>> Russia: +7 495 283 9788
>> United Kingdom: +44 (0) 20 3051 2874  or +44 (0) 20 3695 0088
>> US: +1 408 638 0986  or +1 646 558 8665
>> Meeting ID: 136 978 210
>> International numbers available: https://zoom.us/u/ekaPibJIy
>>
>> The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00 UTC
>> / 10:00 Pacific.
>>
>> Let me emphasize that the environment won't be like this
>> <https://en.wikipedia.org/wiki/File:West_Hartford,_Connecticut_health_care_reform_town_hall_meeting,_2009-09-02.jpg>,
>> so please don't feel intimated if you are nervous about public speaking.
>> (If a conversation feels to me like it is becoming uncivil or intimidating,
>> then I will ask the debaters to quiet themselves or to move to somewhere
>> else.) The meeting will generally have an environment that is more like
>> this
>> <https://en.wikipedia.org/wiki/File:Caf%C3%A9_M%C3%A9lange,_Wien.jpg> or
>> this
>> <https://en.wikipedia.org/wiki/File:Takamatsu-Castle-Building-Interior-M3488.jpg>.
>> I anticipate that few people will come, which is okay. I hope that if you
>> come then you will enjoy the environment and conversation.
>>
>> Until next time,
>> 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

Re: [Wikitech-l] New Security Reviews Process

2019-02-20 Thread Pine W
Hi Charlotte,

Thanks for the announcement.

I have a suggestion. Instead of inviting people to email questions about
the process, you could encourage people to place questions on the talk page
unless there is a reason for making a certain question be nonpublic. This
would facilitate interaction among people who use this process, and
hopefully reduce duplication of effort for people who respond to emails
that are sent to security-team@.

Best wishes,

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

Re: [Wikitech-l] A potential new way to deal with spambots

2019-02-13 Thread Pine W
On Wed, Feb 13, 2019 at 12:13 PM bawolff  wrote:

> I actually meant a different type of maintenance.
>
> Maintaining the encyclopedia (and other wiki projects) is of course an
> activity that needs software support.
>
> But software is also something that needs maintenance. Technology,
> standards, circumstances change over time. Software left alone will
> "bitrot" over time. A long term technical strategy to do anything needs to
> account for that, plan for that. One off feature development does not.
> Democratically directed one-off feature development accounts for that even
> less.
>

I understand. I was intending to comment on maintenance activities in
general, whether that be maintenance of a city's water system, maintenance
of the text of encyclopedia articles, or maintenance of software. My train
of thought proceeded into a somewhat detailed commentary detail regarding
maintenance of non-software Wikimedia elements. I think that the tendency
to under-resource maintenance in favor of novelties is similar in many
domains of human activity, but I also think that humans collectively are
not so unwise that we will prefer novelties over maintenance every time
that there is a referendum on whether to maintain an existing service or to
create something new. {{Citation needed}}

I think that multiple good points have been raised in this thread regarding
the subjects of technical and human systems for detecting and intervening
against possible unflagged bots. I am wondering what a good way would be to
get a WMF product manager or someone similar to dedicate time to this
topic. My preference remains that one or more WMF people, or teams, add
this to their list of topics to address in a future quarter such as Q1 of
the WMF 2019-2020 fiscal year. I don't know how the WMF Community Tech team
plans for maintenance of features after the features are initially built,
debugged, and deployed, and based on the current state of this discussion I
don't currently have a strong opinion regarding whether Community Tech or a
different team would be best suited to work on the topic of unflagged bots.
I also don't know how WMF makes decisions about what goals are for teams
other than Community Tech for future quarters, but that information could
be helpful to have for this conversation.

Thanks,

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

Re: [Wikitech-l] A potential new way to deal with spambots

2019-02-12 Thread Pine W
Since we're discussing how the Tech Wishlist works then I will comment on a
few points specifically regarding that wishlist.

1. A gentle correction: the recommendations are ranked by vote, not by
consensus. This has pros and cons.

2a. If memory serves me correctly, the wishlist process was designed by WMF
rather than designed by community consensus. I may be wrong about this, but
in my search of historical records I have not found evidence to the
contrary. I think that redesigning the process would be worth considering,
and I hope that a redesign would help to account for the types of needs
that bawolff described in his second paragraph.

2b.. I think that it's an overstatement to say that "nobody ever votes for
maintenance until its way too late and everything is about to explode". I
think that many non-WMF people are aware of our backlogs, the endless
requests for help and conflict resolution, and the many challenges of
maintaining what we have with the current population of skilled and good
faith non-WMF people. However, I have the impression that there is a common
*tendency* among humans in general to chase shiny new features instead of
doing mostly thankless work, and I agree that the tech wishlist is unlikely
even in a redesigned form to be well suited for long term planning. I think
that WMF's strategy process may be a better way to plan for the long term,
including for maintenance activities that are mostly thankless and do not
necessarily correlate with increasing someone's personal power, making
their resume look better, or having fun. Fortunately the volunteer
mentality of many non-WMF people means that we do have people who are
willing to do mostly thankless, mundane, and/or stressful work, and I think
that some of us feel that our work is important for maintaining the
encyclopedia even when we do not enjoy it, but we have a finite supply of
time from such people.

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

Re: [Wikitech-l] A potential new way to deal with spambots

2019-02-12 Thread Pine W
Hi David, do you have a question? I saw the GIF but I don't know how to
interpret it in the context of this conversation.

Thanks,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Tue, Feb 12, 2019 at 5:49 AM David Barratt 
wrote:

> http://gph.is/2lnp32Z
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] A potential new way to deal with spambots

2019-02-11 Thread Pine W
Thanks for the replies.

I think that detailed discussion of the pros and cons of the Tech Wishlist
should be separate from this thread, but I agree that one way to get a
subject like unflagged bot detection addressed could be through the Tech
Wishlist assuming that WMF is willing to devote resources to that topic if
it ranked in the top X places.

It sounds like there are a few different ways that work in this area could
be resourced:

1. As mentioned above, making it be a tech wishlist item and having
Community Tech work on it;
2. Having the Anti-Harrassment Tools team work on it;
3. Having the Security team work on it;
4. Having the ORES team work on it;
5. Funding work through a WMF grants program;
6. Funding through a mentorship program like GSOC. I believe that GSOC
previously supported work on CAPTCHA improvements.

Of the above options I suggest first considering 2 and 4. Having AHAT staff
work on unflagged bot detection might be scope creep under the existing
AHAT charter but perhaps AHAT's charter could be modified into something
that would resemble the charter for an "Administrators' Tools Team". And if
the ORES team has already done some work on unflagged bot detection then
perhaps ORES and AHAT staff could collaborate on this topic.

In the first half of the next WMF fiscal year, I think that planning for an
existing WMF team or combination of staff from existing teams to work on
unflagged bot detection would be good. If WMF does not resource this topic,
then if community people want unflagged bot detection be resourced, we can
consider other options such as 1 and 5.

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

Re: [Wikitech-l] A potential new way to deal with spambots

2019-02-09 Thread Pine W
To clarify the types of unwelcome bots that we have, here are the ones that
I think are most common:

1) Spambots

2) Vandalbots

3) Unauthorized bots which may be intended to act in good faith but which
may cause problems that could probably have been identified during standard
testing in Wikimedia communities which have a relatively well developed bot
approval process. (See
https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval.)

Maybe unwelcome bots are not a priority for WMF at the moment, in which
case I could add this subject into a backlog. I am sorry if I sound grumpy
at WMF regarding this subject; this is a problem but I know that there are
millions of problems and I don't expect a different project to be dropped
in order to address this one.

While it is a rough analogy, I think that this movie clip helps to
illustrate a problem of bad bots. Although the clip is amusing, I am not
amused by unwelcome bots causing problems on ENWP or anywhere else in the
Wikiverse. https://www.youtube.com/watch?v=lokKpSrNqDA

Thanks,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )



On Sat, Feb 9, 2019, 1:40 PM Pine W  OK. Yesterday I was looking with a few other ENWP people at what I think
> was a series of edits by either a vandal bot or an inadequately designed
> and unapproved good faith bot. I read that it made approximately 500 edits
> before someone who knew enough about ENWP saw what was happening and did
> something about it. I don't know how many problematic bots we have, in
> addition to vandal bots, but I am confident that they drain a nontrivial
> amount of time from stewards, admins, and patrollers.
>
> I don't know how much of a priority WMF places on detecting and stopping
> unwelcome bots, but I think that the question of how to decrease the
> numbers and effectiveness of unwelcome bots would be a good topic for WMF
> to research.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> On Sat, Feb 9, 2019 at 9:24 PM Gergo Tisza  wrote:
>
>> On Fri, Feb 8, 2019 at 6:20 PM Pine W  wrote:
>>
>> > I don't know how practical it would be to implement an approach like
>> this
>> > in the Wikiverse, and whether licensing proprietary technology would be
>> > required.
>> >
>>
>> They are talking about Polyform [1], a reverse proxy that filters traffic
>> with a combination of browser fingerprinting, behavior analysis and proof
>> of work.
>> Proof of work is not really useful unless you have huge levels of bot
>> traffic from a single bot operator (also it means locking out users with
>> no
>> Javascript); browser and behavior analysis very likely cannot be
>> outsourced
>> to a third party for privacy reasons. Maybe we could do it ourselves
>> (although it would still bring up interesting questions privacy-wise) but
>> it would be a huge undertaking.
>>
>>
>> [1] https://www.kasada.io/product/
>> ___
>> 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] A potential new way to deal with spambots

2019-02-09 Thread Pine W
OK. Yesterday I was looking with a few other ENWP people at what I think
was a series of edits by either a vandal bot or an inadequately designed
and unapproved good faith bot. I read that it made approximately 500 edits
before someone who knew enough about ENWP saw what was happening and did
something about it. I don't know how many problematic bots we have, in
addition to vandal bots, but I am confident that they drain a nontrivial
amount of time from stewards, admins, and patrollers.

I don't know how much of a priority WMF places on detecting and stopping
unwelcome bots, but I think that the question of how to decrease the
numbers and effectiveness of unwelcome bots would be a good topic for WMF
to research.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Sat, Feb 9, 2019 at 9:24 PM Gergo Tisza  wrote:

> On Fri, Feb 8, 2019 at 6:20 PM Pine W  wrote:
>
> > I don't know how practical it would be to implement an approach like this
> > in the Wikiverse, and whether licensing proprietary technology would be
> > required.
> >
>
> They are talking about Polyform [1], a reverse proxy that filters traffic
> with a combination of browser fingerprinting, behavior analysis and proof
> of work.
> Proof of work is not really useful unless you have huge levels of bot
> traffic from a single bot operator (also it means locking out users with no
> Javascript); browser and behavior analysis very likely cannot be outsourced
> to a third party for privacy reasons. Maybe we could do it ourselves
> (although it would still bring up interesting questions privacy-wise) but
> it would be a huge undertaking.
>
>
> [1] https://www.kasada.io/product/
> ___
> 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] Invitation to a "Wikimedia Café" casual online meetup

2019-02-08 Thread Pine W
 Hi,

For the next Wikimedia Café online meetup we will focus on the subject of
communications in the Wikiverse. What about communications is working well,
what is not working well, and what should be done to improve
communications? This will be a casual discussion but formal proposals may
emerge from it, and at the meetup people are welcome to discuss their ideas
for formal proposals. Participants are also welcome to suggest topics for
discussion other than communications, but the plan is to spend the majority
of the time on the subject of communications.

The Café meetup will be in late March, on a time to be chosen via Doodle
poll: https://doodle.com/poll/t3w8nkt9vy5mm3r5. I am skipping February due
to some existing commitments. When you visit the Doodle poll you should be
able to change the timezone that you see for the calendar. Please be sure
to select the correct timezone for you before you vote.

I will host the meeting using the free version of Zoom. Zoom limits the
length of meetings using the free version to 40 minutes.

The Zoom online meeting link will be the same link that we have used for
previous Wikimedia Café meetups; see below.

If you would like to attend then please vote in the Doodle poll.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Thu, Aug 9, 2018 at 11:15 PM Pine W  wrote:

> Hi folks,
>
> Based on comments that I received on Wikimedia-l, I would like to invite
> people to a casual online meetup one hour before the monthly WMF Metrics
> and Activities Meeting.
>
> There will be no set agenda. You can come with questions or ideas that you
> would like to discuss. Please be willing to listen to questions and ideas
> from other Wikimedians.
>
> I will host the meeting with the Zoom software. You can join with software
> or by using your phone. If you join by phone then your phone number will be
> visible to other participants.
>
> The primary language of the meeting will be English, but if people would
> like to communicate in diverse languages then that is okay too. We can
> facilitate translation by text chat. Many Wikimedians, myself included, are
> multilingual in varying degrees, so we might try to have live
> interpretation also.
>
> Here is information about how to connect:
>
> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
>
> Or iPhone one-tap :
> Argentina: +543415122188,,136978210#
> Or Telephone:
> Dial (for higher quality, dial a number based on your current
> location):
> Argentina: +54 341 512 2188
> Australia: +61 (0) 2 8015 2088  or +61 (0) 8 7150 1149
> Canada: +1 647 558 0588
> Hong Kong, China: +852 5808 6088
> France: +33 (0) 1 8288 0188  or +33 (0) 7 5678 4048
> Germany: +49 (0) 30 3080 6188  or +49 (0) 30 5679 5800
> Israel: +972 (0) 3 978 6688
> Italy: +39 069 480 6488
> Japan: +81 (0) 3 4578 1488  or +81 524 564 439
> Mexico: +52 229 910 0061  or +52 554 161 4288
> Spain: +34 84 368 5025  or +34 91 198 0188
> Sweden: +46 (0) 7 6692 0434  or +46 (0) 8 4468 2488
> Russia: +7 495 283 9788
> United Kingdom: +44 (0) 20 3051 2874  or +44 (0) 20 3695 0088
> US: +1 408 638 0986  or +1 646 558 8665
> Meeting ID: 136 978 210
> International numbers available: https://zoom.us/u/ekaPibJIy
>
> The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00 UTC
> / 10:00 Pacific.
>
> Let me emphasize that the environment won't be like this
> <https://en.wikipedia.org/wiki/File:West_Hartford,_Connecticut_health_care_reform_town_hall_meeting,_2009-09-02.jpg>,
> so please don't feel intimated if you are nervous about public speaking.
> (If a conversation feels to me like it is becoming uncivil or intimidating,
> then I will ask the debaters to quiet themselves or to move to somewhere
> else.) The meeting will generally have an environment that is more like
> this <https://en.wikipedia.org/wiki/File:Caf%C3%A9_M%C3%A9lange,_Wien.jpg>
> or this
> <https://en.wikipedia.org/wiki/File:Takamatsu-Castle-Building-Interior-M3488.jpg>.
> I anticipate that few people will come, which is okay. I hope that if you
> come then you will enjoy the environment and conversation.
>
> Until next time,
> 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] A potential new way to deal with spambots

2019-02-08 Thread Pine W
This sounds like an interesting potential approach to deal with spambots,
and hopefully to deter the people who make them.

https://techcrunch.com/2019/02/05/kasada-bots/

I don't know how practical it would be to implement an approach like this
in the Wikiverse, and whether licensing proprietary technology would be
required.

I would be interested in decreasing the quantity and effectiveness of
spambots that misuse WMF infrastructure, damage the quality of Wikimedia
content, and drain significant cumulative time from the limited supply of
good faith contributors.

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

Re: [Wikitech-l] Changes to the Block paradigm

2019-02-04 Thread Pine W
Hello 80hnhtv4agou,

I believe that any allegations of misconduct by admins or stewards should
be addressed in a separate thread, and most likely not on Wikitech-l unless
you a referring to an incident that happened in a location that focuses on
technical matters such as Phabricator. In most cases I would caution
against trying to address an allegation in multiple venues simultaneously
because many Wikimedians have heavy workloads and have limited willingness
to read about the same conflict multiple times. Some projects have clearly
defined routes for appealing certain administrative actions, but others do
not. If you would like information about how to make an appeal or report an
allegation of misconduct then those questions are probably better suited to
Wikimedia-l, an OTRS ticket, or to the Wikimedia Forum on Meta (
https://meta.wikimedia.org/wiki/Wikimedia_Forum).

Keeping threads on topic is courteous to others, so I request that if you
have further questions regarding allegations of misconduct then please
raise them at one of the places that I mentioned instead of in this thread.

Thanks,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Mon, Feb 4, 2019 at 11:02 PM 80hnhtv4agou--- via Wikitech-l <
wikitech-l@lists.wikimedia.org> wrote:

>
> what about abuse by administrators and stewards ?
>
> From: Moriel Schottlender
> Sent: Monday, January 7, 2019 7:53 PM
> To: Wikimedia developers ;  wikitech-ambassad...@lists.wikimedia.org
> Subject: [Wikitech-l] Changes to the Block
> paradigm
>
> Greetings,
>
> Have
> you written code that deals with or depends on user blocks? Read on.
>
> =
> TL;DR: =
>
> The new “Partial Blocks” feature has fundamentally changed the
> way MediaWiki
> considers what “block” means; any code that handles blocks
> should consider
> whether the questions it is asking are still valid or should
> adjust its
> expectations. Please read for more details.
>
> = Preamble
> =
>
> A couple of months ago, as part of the Anti Harassment Tools
> team’s
> continued work on improving the general experience of our users
> and
> providing more robust tools to administrators, an RFC to enable
> “Partial
> Blocks[1]” has passed and has been implemented in MediaWiki,
> affecting the
> way blocking users operates.
>
> While the actual feature,
> enabling the blocking of users for specific pages
> and namespaces, will be
> slowly rolled out as part of our rollout and
> testing plans, the change has
> resulted in a complete change of paradigm for
> what “block” means throughout
> our code.
>
> = Change of paradigm =
>
> Until recently, Block was fairly
> straight forward; whether a block was done
> on an IP range or a specific user,
> the question the code would ask is “is
> the user blocked from this action” and
> the answer will be a boolean yes or
> no, depending on whether the user was
> blocked from the wiki and whether the
> action was a blockable
> action.
>
> With the new Partial Blocks feature, that question is now more
> elaborate.
> We are giving admins and wikis in general much more robust options
> when
> deciding to block IPs or users. “Sitewide” block is no longer the
> only
> option. Now, a user can be blocked from editing a specific page, and
> soon
> from a specific namespace. There are also blocks that prevent a
> specific
> action, such as uploading files or creating new pages.
>
> This
> means that the question “is the user blocked” is no longer accurate.
> In most
> cases, the question should be “is the user blocked from the action
> on this
> page”, because users may receive a block that is not sitewide, but
> from a
> specific page or set of pages.
>
> = What we worked on =
>
> The Anti
> Harassment Tools team has been working diligently on making sure
> that the new
> blocking behavior does not produce obvious regressions in
> production, and
> does not add to any still existing inconsistencies. In
> cases where we
> identified a clear mismatch, we’ve tried to either fix it
> outright or alert
> the code owners to adjust.
>
> If we have missed any iteration or use-case,
> please open a Phabricator
> ticket and add the ‘anti-harassment’[2] tag to it.
> If the use-case is
> sensitive or identifies a current loop-hole in the way
> blocks work, please
> make it a security ticket and alert us and the relevant
> team immediately.
>
> = General steps forward =
>
> While the team is
> following up on making the code clear and robust and
> fixing what we’ve
> identified as paradigm-changes to deal with, there are
> still many instances
> where the changes required to the code are not
> straight-forward or clear.
> Some extensions ask whether a user is blocked
> and may need to change the way
> that the product’s “business logic” behaves.
>
> These are cases where we
> cannot make the decision for the codebase. We
> encourage you to look at your
> product and consider adjusting if necessary.
>
> = General guidance
> =
>
> We’ve identified some areas that may help code owners 

Re: [Wikitech-l] Invitation to a "Wikimedia Café" casual online meetup

2019-01-23 Thread Pine W
Sorry, I started the meeting but the meeting ID number was wrong. I don't
know how that happened. I think that this problem has been corrected, so if
you were trying to connect, please try again.


Pine
( https://meta.wikimedia.org/wiki/User:Pine )

On Tue, Jan 8, 2019, 12:49 PM Pine W  wrote:

> Hi, the Wikimedia Café for January will be on Wednesday the 23rd at 11 AM
> Pacific / 7 PM UTC. The Zoom link is below. Because of the monthly limit
> for emails from any one person to Wikimedia-l and my wish to conserve my
> remaining emails to that list for other topics, I likely will not send a
> reminder about this event, so please mark your calendars now if you want to
> attend. Thanks!
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> On Wed, Jan 2, 2019, 3:07 PM Pine W  wrote:
>
>> Hi,
>>
>> The next "Wikimedia Café" meetup will be on Wednesday the 23rd of
>> January, on a time to be chosen via Doodle poll:
>> https://doodle.com/poll/5mf5cfkuxpprk727. The plan is that for January's
>> meetup we will focus on Wikidata. Bluerasberry
>> <https://en.wikipedia.org/wiki/User:Bluerasberry>, who works extensively
>> with Wikidata at the University of Virginia's Data Science Institute, plans
>> to participate.
>>
>> The Zoom online meeting link will be the same link that we have used for
>> previous Wikimedia Café meetups; see below.
>>
>> The Café meetups are usually small, so they are a good place to ask
>> questions or to discuss ideas, regarding Wikidata or other Wikimedia topics.
>>
>> Pine
>> ( https://meta.wikimedia.org/wiki/User:Pine )
>>
>>
>> On Thu, Aug 9, 2018 at 11:15 PM Pine W  wrote:
>>
>>> Hi folks,
>>>
>>> Based on comments that I received on Wikimedia-l, I would like to invite
>>> people to a casual online meetup one hour before the monthly WMF Metrics
>>> and Activities Meeting.
>>>
>>> There will be no set agenda. You can come with questions or ideas that
>>> you would like to discuss. Please be willing to listen to questions and
>>> ideas from other Wikimedians.
>>>
>>> I will host the meeting with the Zoom software. You can join with
>>> software or by using your phone. If you join by phone then your phone
>>> number will be visible to other participants.
>>>
>>> The primary language of the meeting will be English, but if people would
>>> like to communicate in diverse languages then that is okay too. We can
>>> facilitate translation by text chat. Many Wikimedians, myself included, are
>>> multilingual in varying degrees, so we might try to have live
>>> interpretation also.
>>>
>>> Here is information about how to connect:
>>>
>>> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
>>>
>>> Or iPhone one-tap :
>>> Argentina: +543415122188,,136978210#
>>> Or Telephone:
>>> Dial (for higher quality, dial a number based on your current
>>> location):
>>> Argentina: +54 341 512 2188
>>> Australia: +61 (0) 2 8015 2088  or +61 (0) 8 7150 1149
>>> Canada: +1 647 558 0588
>>> Hong Kong, China: +852 5808 6088
>>> France: +33 (0) 1 8288 0188  or +33 (0) 7 5678 4048
>>> Germany: +49 (0) 30 3080 6188  or +49 (0) 30 5679 5800
>>> Israel: +972 (0) 3 978 6688
>>> Italy: +39 069 480 6488
>>> Japan: +81 (0) 3 4578 1488  or +81 524 564 439
>>> Mexico: +52 229 910 0061  or +52 554 161 4288
>>> Spain: +34 84 368 5025  or +34 91 198 0188
>>> Sweden: +46 (0) 7 6692 0434  or +46 (0) 8 4468 2488
>>> Russia: +7 495 283 9788
>>> United Kingdom: +44 (0) 20 3051 2874  or +44 (0) 20 3695 0088
>>> US: +1 408 638 0986  or +1 646 558 8665
>>> Meeting ID: 136 978 210
>>> International numbers available: https://zoom.us/u/ekaPibJIy
>>>
>>> The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00
>>> UTC / 10:00 Pacific.
>>>
>>> Let me emphasize that the environment won't be like this
>>> <https://en.wikipedia.org/wiki/File:West_Hartford,_Connecticut_health_care_reform_town_hall_meeting,_2009-09-02.jpg>,
>>> so please don't feel intimated if you are nervous about public speaking.
>>> (If a conversation feels to me like it is becoming uncivil or intimidating,
>>> then I will ask the debaters to quiet themselves or to move to somewhere
>>> else.) The meeting will generally have an environment that is more like
>>> this
>>> <https://en.wikipedia.org/wiki/File:Caf%C3%A9_M%C3%A9lange,_Wien.jpg>
>>> or this
>>> <https://en.wikipedia.org/wiki/File:Takamatsu-Castle-Building-Interior-M3488.jpg>.
>>> I anticipate that few people will come, which is okay. I hope that if you
>>> come then you will enjoy the environment and conversation.
>>>
>>> Until next time,
>>> 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

Re: [Wikitech-l] [Engineering] Gerrit now automatically adds reviewers

2019-01-18 Thread Pine W
I'm glad that this problematic change to communications was reverted.

I would like to suggest that this is the type of change that, when being
planned, should get a design review from a third party before coding
starts, should go through at least one RFC before coding starts, and be
widely communicated before coding starts and again a week or two before
deployment. Involving TechCom might also be appropriate. It appears that
none of those happened here. In terms of process this situation looks to me
like it's inexcusable.

In the English Wikipedia community, doing something like this would have a
reasonable likelihood of costing an administrator their tools, and I hope
that a similar degree of accountability is enforced in the engineering
community. In particular, I expect engineering supervisors to follow
established technical processes for changes that impact others' workflows,
and if they decide to skip those processes without a compelling reason
(such as a site stability problem) then I hope that they will be held
accountable. Again, from my perspective, the failure to follow process here
is inexcusable.

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

Re: [Wikitech-l] [Engineering] Gerrit now automatically adds reviewers

2019-01-17 Thread Pine W
Although this change doesn't personally affect me because I'm not active on
Gerrit, my reading of the situation is similar to Giuseppe's. Sending
people potentially large numbers of automatic and unsolicited notifications
is not something that I would generally support, and I would likely believe
to be a misuse of communications tools and an inconsiderate use of others'
time, no matter how well-intentioned.

My impression of this change to communications is that it should have been
broadly discussed, and consensus requested through an RfC, before
implementation. Was there an RfC? Were there previous wide notifications
regarding this proposed change to communications?

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

Re: [Wikitech-l] s3 primary db master failover on Thursday 17th January 07:00 AM UTC

2019-01-16 Thread Pine W
That was quick. Thanks for the speedy work, which I am guessing was helped
by good planning.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, Jan 16, 2019, 11:15 PM Manuel Arostegui 
wrote:

> This was done.
> Read only ON at: 07:01:00
> Read only OFF at: 07:04:20
>
> Total time read only time: 03:20 minutes
>
> If you see something strange, please let us know.
> Thanks
>
> On Thu, Jan 17, 2019 at 7:40 AM Manuel Arostegui  >
> wrote:
>
> > This will start in 20 minutes.
> >
> > Thanks.
> >
> > On Wed, Jan 16, 2019 at 2:02 PM Manuel Arostegui <
> maroste...@wikimedia.org>
> > wrote:
> >
> >> Hello,
> >>
> >> Due to the recent issues with the PDUs on both A2 (T213748) and A3
> >> (T213859) we need to swap s3 db primary master (T213858), as it lives
> on A2.
> >>
> >> We are going to do this on Thursday 17th at 07:00 AM UTC, and we have
> >> requested a 30 minutes window (T213864) 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: 07:00AM UTC - 07: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] 2019-01-09 Scrum of Scrums meeting notes

2019-01-12 Thread Pine W
Thanks Gergő. I think that what I am seeking occupies a middle ground
between Tech News and and the quarterly check-ins. Quarterly check-ins can
have lengthy slide decks which are wonderfully detailed but require
considerable time to read. Tech news is less comprehensive than the type of
resource that I am seeking. The Discovery / Search Platform newsletters are
great but they are also more detailed than I need on a per-team basis.

I'll use some vocabulary from baseball in trying to describe the info that
I would like to see from each Audiences and Technology team each week:

LAST PLAY: activities that were completed last week, such as "We completed
planning of deployment for desktop beta of Wikistats 2.1. Hiring of new dev
and DBA was finalized; their first day of work is two weeks out. Fixed a
regression that caused an unplanned failover (Phabricator task link here);
service is back to normal."

AT BAT: highlights of current activities that are happening prior to the
release of the next weekly update, such as "This week we are deploying the
desktop beta of Wikistats 2.1 (Phabricator task link here) and we are
working with Research to improve API documentation. Work on the incident
report for last week's unplanned failover (link to document here) is
continuing."

ON DECK: activities that are planned for the next 1 to 2 weeks after the
completion of the "at bat" activities, such as "Survey of needs for API
users is in final design and awaiting sign-offs (Phabricator task link
here); staff onboarding for new dev and DBA; IRC office hour to discuss the
beta desktop Wikistats 2.1".

IN THE HOLE: highlights of activities that are 2 to 6 weeks away. Such as
"Budget planning associated with Annual Planning; early design of the
mobile interface for Wikistats 2.1 (Phabricator task link here); planning
of documentation (Phabricator task link here) and test methodology (Phabricator
task link here) for mobile Wikistats 2.1; staff cross-training".

My guess is that there are routine internal meetings where this information
is discussed. I would like for information at approximately this level of
detail to be published, with allowance for redactions of security and
privacy sensitive information.

Is there interest from others in publishing or reading information like
this? My guess is that other people might also benefit from reports like
these, including people at WMF who might want to know what other teams are
doing, but if no one else is interested then I'll try to go along with the
status quo.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Fri, Jan 11, 2019 at 8:04 PM Gergő Tisza  wrote:

> On Fri, Jan 11, 2019 at 11:29 AM Pine W  wrote:
>
> > [...] Are there any upcoming plans for systematic
> > study or development of WMF-to-public communications processes from
> > Audiences and Technology?
> >
>
> Not quite the same thing, but touches on communication:
>
> https://meta.wikimedia.org/wiki/Research:Growth_and_diversity_of_Technology_team_audiences
>
> There are a couple existing ways to learn about new developments, though.
> There is Tech News (focused on immediate user-facing changes), quarterly
> department checkins (focused on the big picture and progress of annual plan
> goals and other large projects), most teams have a monthly or sometimes
> weekly newsletter and/or on-wiki updates page, there are some regular
> showcases (research and more recently language), and people write blog
> posts about larger or more interesting developments on Phabricator and the
> WMF blog. (The discoverability of all of these things could certainly be
> improved.) And if you are sufficiently interested in a specific team, team
> Phabricator boards are public.
>
> On Fri, Jan 11, 2019 at 11:29 AM Pine W  wrote:
>
> > On Fri, Jan 11, 2019, 9:31 AM Dan Garry (Deskana) 
> > wrote:
> >
> > > On Wed, 9 Jan 2019 at 20:25, Pine W  wrote:
> > >
> > > > I would like to request that every Audiences and Technology team
> submit
> > > > highlights of recent and upcoming activities for inclusion in every
> set
> > > of
> > > > SoS notes, even if no one personally attends the SoS meeting from a
> > > > particular team, so that readers of these notes can keep better track
> > of
> > > > what is happening in the Audiences and Technology departments and so
> > that
> > > > readers can make adjustments to our own plans as needed.
> > >
> > >
> > > Scrum of scrums meetings are intended to be a venue for development
> teams
> > > to surface upcoming blockers and dependencies on other teams, so that
> > teams
> > > can better work together and not block each other. Scrum of scrums
> > meetings
> > > are

Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes

2019-01-11 Thread Pine W
On Fri, Jan 11, 2019, 9:31 AM Dan Garry (Deskana)  wrote:

> On Wed, 9 Jan 2019 at 20:25, Pine W  wrote:
>
> > I would like to request that every Audiences and Technology team submit
> > highlights of recent and upcoming activities for inclusion in every set
> of
> > SoS notes, even if no one personally attends the SoS meeting from a
> > particular team, so that readers of these notes can keep better track of
> > what is happening in the Audiences and Technology departments and so that
> > readers can make adjustments to our own plans as needed.
>
>
> Scrum of scrums meetings are intended to be a venue for development teams
> to surface upcoming blockers and dependencies on other teams, so that teams
> can better work together and not block each other. Scrum of scrums meetings
> are not intended to be a forum for general announcements about activities
> by end-users. These are very different use cases with different target
> audiences.
>
> I understand your concerns about visibility of the actions inside the
> Wikimedia Foundation. It's certainly difficult to see things from the
> outside. That said, taking a meeting with a well-defined purpose and
> objective, and expanding that objective to add an additional, quite
> different use case, is not good practice; doing so may cause people to
> disengage or lose focus, thereby meaning the original objective of the
> meeting is no longer met.
>
> Some reading you might find useful:
>
>- https://www.agilealliance.org/glossary/scrum-of-scrums/
>- https://www.scruminc.com/scrum-of-scrums/
>
> Dan



Hi Dan,

That is helpful. Perhaps the info I am seeking would be better communicated
in a different way. I am reluctant to request a new communications process
that would require nontrivial effort to start and to maintain if I am the
only one who is interested. Are there any upcoming plans for systematic
study or development of WMF-to-public communications processes from
Audiences and Technology? If so, perhaps I could have a conversation with
whomever will work on that communications effort.

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

Re: [Wikitech-l] A difficult goodbye

2019-01-10 Thread Pine W
Thank you for your service, Victoria. I'm glad that your next steps sound
like they will be good for you professionally and will be at another
organization that does public service.

I've appreciated that you have been consistently responsive and polite in
our interactions. I wish you the best on your journey. Perhaps we'll meet
again.

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

Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes

2019-01-10 Thread Pine W
Hi Andre,

When I read the SoS notes and I see nothing from some teams, this leaves me
to guess what their current states are. I do not know whether teams are
working on backlogs of bugs, developing a new feature, at a team retreat,
conducting a post-deployment evaluation, designing an interface change,
evaluating survey results, writing grant requests, hiring new staff,
upgrading hardware, installing new cables, etc. I don't need to know, and I
don't want to know, every detail of what teams are doing, but there is a
happy medium between reporting nothing and reporting too much.

Does that help to explain what I would like to see in SoS notes?

If there is an alternative way to learn the same information, I would be
glad to hear suggestions.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )



On Thu, Jan 10, 2019, 4:25 AM Andre Klapper  wrote:

> On Wed, 2019-01-09 at 12:25 -0800, Pine W wrote:
> > I would like to request that every Audiences and Technology team
> > submit
> > highlights of recent and upcoming activities for inclusion in every
> > set of
> > SoS notes, even if no one personally attends the SoS meeting from a
> > particular team
>
> What is your assumption based that this is not already the case
> (if/when a team or project has something to share)?
>
> 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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] 2019-01-09 Scrum of Scrums meeting notes

2019-01-09 Thread Pine W
Hi, I think that I previously made this request and it went unanswered, so
I am escalating this request to Toby who I believe reads at least some of
these SoS notes. If someone else is better suited to answer authoritatively
than Toby, or if someone else would like to share their thoughts regarding
this request, please feel free to comment. Also, please feel free to fork
this request to a new thread if you think that a new thread would be a
better place for this discussion.

I would like to request that every Audiences and Technology team submit
highlights of recent and upcoming activities for inclusion in every set of
SoS notes, even if no one personally attends the SoS meeting from a
particular team, so that readers of these notes can keep better track of
what is happening in the Audiences and Technology departments and so that
readers can make adjustments to our own plans as needed. I would guess
that, in addition to myself, other people who are not WMF staff might also
benefit from this, along with WMF staff who miss SoS meetings.

Thanks,

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, Jan 9, 2019, 11:43 AM Grace Gellerman 
wrote:

> https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-01-09
>
> =2019-01-09=
> == Callouts ==
> * Fundraising campaigns
> https://meta.wikimedia.org/wiki/CentralNotice/Calendar
> * Language blocked by RelEng:
> https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/
> * Security: if there are notes from the Proton security review, they would
> be useful for the handover from Reading Web to Reading Infrastructure. See
> also https://phabricator.wikimedia.org/T177765#4822198
> * Growth: Who do I (mdholloway) talk to about/add for review on changes to
> Extension:GettingStarted?
> * Readers Web and Performance, in case you notice performance hits on the
> mobile site: #Research ran reader trust survey from 01/07 till 01/09:
> https://phabricator.wikimedia.org/T209882
> * Core Platform (from Analytics)
> https://phabricator.wikimedia.org/T202781#4865947 (same for MediaWiki
> history reconstruction).
> * Release Engineering: January 28 - wmf.15 - No Train (due to All Hands
> week)
>
> == Audiences ==
>
>
> === Contributors ===
>  Community Tech 
> * Blocked by:
> * Blocking:
> * Updates:
> **
>
>  Anti-Harassment Tools 
> * Blocked by:
> * Blocking:
> * Updates:
> **
>
>  Editing 
> * Blocked by:
> * Blocking:
> ** Updates:
> **
>
>  Growth 
> * Blocked by:
> * Blocking:
> * Updates:
> **Deploying Help Panel this week
> https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk
>
>  Language 
> * Blocked by: CI/RelEng:
> https://gerrit.wikimedia.org/r/#/c/integration/config/+/482766/
> * Blocking:
> * Updates:
> ** Google Translate available for ContentTranslation now!
>
> https://wikimediafoundation.org/2019/01/09/you-can-now-use-google-translate-to-translate-articles-on-wikipedia/
>
> === Readers ===
>  iOS native app 
> * Blocked by:
> * Blocking:
> * Updates:
> **completed user testing of the Editing prototype -
> https://phabricator.wikimedia.org/T211152
> ** will be conducting user testing of the Editing prototype among internal
> users this week
> **still working on/refining editing tools and syntax highlighting -
> https://phabricator.wikimedia.org/tag/ios-app-v6.2-beluga-on-a-pogo-stick/
>
>  Android native app 
> * Blocked by:
> * Blocking:
> * Updates:
> **
>
>  Readers Web 
> * Blocked by:
> * Blocking:
> * Updates:
>
> ** Summary: starting Advanced Mobile Contributions work and Webpackifying
> the remaining MobileFrontend modules. Say hello to our new test engineer,
> Edward Tadros!
>
> ** Responsive website (MinervaNeue / MobileFrontend):
>
> *** Invest in the MobileFrontend & MinervaNeue frontend architecture
>
> https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
>  Webpackify mobile.languages.structured and mobile.mediaViewer
> asynchronous ResourceLoader modules T210210 T210209
>  Drawers and Overlays should not auto-append themselves T209129 T211691
>  Replace inheritance with composition T205592
>
> *** Advanced mobile contributions
> https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions
>  Build AMC opt-in toggle T211197 T212516
>  Team planning
>
> *** Page issues
> https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues
>  Deploy to enwiki and all remaining projects on January 14th T210554
>
> *** Miscellaneous bug fixes and maintenance T212518 T211724 T212970
>
> ** Desktop website (Vector, Popups)
>
> *** Popups https://www.mediawiki.org/wiki/Page_Previews
>  Generate all possible combinations of page previews with Storybook
> T205989 https://zen-pasteur-e92b1e.netlify.com/
>  WMDE reference previews are in progress
> https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews
>
> ** PDF rendering (Proton)
> 

[Wikitech-l] Industry news: GitHub policy change for free private repos with up to 3 collaborators

2019-01-08 Thread Pine W
Industry news that I think may interest some Wikimedians, particularly
students and developers of small projects where privacy of code is a
concern, but keep in mind that GitHub is now owned by Microsoft:
https://blog.github.com/2019-01-07-new-year-new-github/


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

Re: [Wikitech-l] Invitation to a "Wikimedia Café" casual online meetup

2019-01-08 Thread Pine W
Hi, the Wikimedia Café for January will be on Wednesday the 23rd at 11 AM
Pacific / 7 PM UTC. The Zoom link is below. Because of the monthly limit
for emails from any one person to Wikimedia-l and my wish to conserve my
remaining emails to that list for other topics, I likely will not send a
reminder about this event, so please mark your calendars now if you want to
attend. Thanks!

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Wed, Jan 2, 2019, 3:07 PM Pine W  wrote:

> Hi,
>
> The next "Wikimedia Café" meetup will be on Wednesday the 23rd of January,
> on a time to be chosen via Doodle poll:
> https://doodle.com/poll/5mf5cfkuxpprk727. The plan is that for January's
> meetup we will focus on Wikidata. Bluerasberry
> <https://en.wikipedia.org/wiki/User:Bluerasberry>, who works extensively
> with Wikidata at the University of Virginia's Data Science Institute, plans
> to participate.
>
> The Zoom online meeting link will be the same link that we have used for
> previous Wikimedia Café meetups; see below.
>
> The Café meetups are usually small, so they are a good place to ask
> questions or to discuss ideas, regarding Wikidata or other Wikimedia topics.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
> On Thu, Aug 9, 2018 at 11:15 PM Pine W  wrote:
>
>> Hi folks,
>>
>> Based on comments that I received on Wikimedia-l, I would like to invite
>> people to a casual online meetup one hour before the monthly WMF Metrics
>> and Activities Meeting.
>>
>> There will be no set agenda. You can come with questions or ideas that
>> you would like to discuss. Please be willing to listen to questions and
>> ideas from other Wikimedians.
>>
>> I will host the meeting with the Zoom software. You can join with
>> software or by using your phone. If you join by phone then your phone
>> number will be visible to other participants.
>>
>> The primary language of the meeting will be English, but if people would
>> like to communicate in diverse languages then that is okay too. We can
>> facilitate translation by text chat. Many Wikimedians, myself included, are
>> multilingual in varying degrees, so we might try to have live
>> interpretation also.
>>
>> Here is information about how to connect:
>>
>> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
>>
>> Or iPhone one-tap :
>> Argentina: +543415122188,,136978210#
>> Or Telephone:
>> Dial (for higher quality, dial a number based on your current
>> location):
>> Argentina: +54 341 512 2188
>> Australia: +61 (0) 2 8015 2088  or +61 (0) 8 7150 1149
>> Canada: +1 647 558 0588
>> Hong Kong, China: +852 5808 6088
>> France: +33 (0) 1 8288 0188  or +33 (0) 7 5678 4048
>> Germany: +49 (0) 30 3080 6188  or +49 (0) 30 5679 5800
>> Israel: +972 (0) 3 978 6688
>> Italy: +39 069 480 6488
>> Japan: +81 (0) 3 4578 1488  or +81 524 564 439
>> Mexico: +52 229 910 0061  or +52 554 161 4288
>> Spain: +34 84 368 5025  or +34 91 198 0188
>> Sweden: +46 (0) 7 6692 0434  or +46 (0) 8 4468 2488
>> Russia: +7 495 283 9788
>> United Kingdom: +44 (0) 20 3051 2874  or +44 (0) 20 3695 0088
>> US: +1 408 638 0986  or +1 646 558 8665
>> Meeting ID: 136 978 210
>> International numbers available: https://zoom.us/u/ekaPibJIy
>>
>> The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00 UTC
>> / 10:00 Pacific.
>>
>> Let me emphasize that the environment won't be like this
>> <https://en.wikipedia.org/wiki/File:West_Hartford,_Connecticut_health_care_reform_town_hall_meeting,_2009-09-02.jpg>,
>> so please don't feel intimated if you are nervous about public speaking.
>> (If a conversation feels to me like it is becoming uncivil or intimidating,
>> then I will ask the debaters to quiet themselves or to move to somewhere
>> else.) The meeting will generally have an environment that is more like
>> this
>> <https://en.wikipedia.org/wiki/File:Caf%C3%A9_M%C3%A9lange,_Wien.jpg> or
>> this
>> <https://en.wikipedia.org/wiki/File:Takamatsu-Castle-Building-Interior-M3488.jpg>.
>> I anticipate that few people will come, which is okay. I hope that if you
>> come then you will enjoy the environment and conversation.
>>
>> Until next time,
>> 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

  1   2   3   4   5   6   >