Re: [Wikitech-l] RFC: Add Content-Security-Policy header to MediaWiki

[Pine W]

With the disclaimer that I'm not a security engineer and that I understand
only parts of this proposal, in general this strikes me as a good idea. It
seems to me that trying to develop a comprehensive list of what tools /
scripts this proposal would likely break, how important those breaks are,
and who could fix them and when, would help with developing a roadmap
toward implementing this proposal with appropriate mitigation and
communication.

It seems to me that this is the kind of project for which product community
liasons are well suited to help with developing and implementing a rollout
plan. Is there any chance of getting a CL to help with this project?

Thanks for the initiative,

Pine

Pine
On May 22, 2016 18:18, "Brian Wolff"  wrote:

> So the RFC process page says I should email wikitech-l to propose an RFC,
> thus:
>
> Content-Security-Policy (CSP) header is a header that disables certain
> javascript features that are commonly used to exploit XSS attacks, in
> order to mitigate the risks of XSS. I think we could massively benefit
> from using this technology - XSS attacks probably being the most
> common security issue in MediaWiki. The downside is that it would
> break compatibility with older user scripts.
>
> Please see the full text of my proposal at
> https://www.mediawiki.org/wiki/Requests_for_comment/Content-Security-Policy
>
> The associated phabricator ticket is:
> https://phabricator.wikimedia.org/T135963
>
> I'd appreciate any comments anyone might have.
>
> Thanks,
> Brian
>
> ___
> 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] Reducing the environmental impact of the Wikimedia movement

[Pine W]

Some of this depends on geography.

For example, in Washington State, we have significant hydroelectric
capacity. (See http://www.eia.gov/state/print.cfm?sid=WA)

My understanding is that some data centers are being placed in the far
global north to take advantage of cold air or water  temperatures for data
center cooling.

Pine
On May 18, 2016 14:33, "Lukas Mezger"  wrote:

> You are right that our demand in bandwidth is comparably low, Ryan. But we
> do have an extremely strong brand, and the power of some really great
> people working and volunteering for Wikimedia. This is why I was hoping
> that someone could explain the technicalities of the U.S. energy system to
> me – can't we simply ask our datacenter providers to order renewable energy
> for our servers, maybe for an extra charge? This is what you can do in
> Europe, but I have a feeling things are not just as easy in the U.S.
> Thanks,
>
> Lukas
>
> 2016-05-16 19:40 GMT+02:00 Ryan Lane :
>
> > On Mon, May 16, 2016 at 12:45 AM, Lukas Mezger 
> > wrote:
> >
> > > Yes, we're also looking into reducing the environmental impact of the
> > rest
> > > of the activities in the Wikimedia movement. And I am very aware that
> > many
> > > websites consume a lot more energy than Wikipedia does. (Please see
> > > https://meta.wikimedia.org/wiki/Environmental_impact for more
> > > information.)
> > >
> > > But this doesn't mean we should not try to have the Wikimedia servers
> run
> > > on renewable energy. Even some big for-profit companies like Apple and
> > > Yahoo are already doing this. So, how can we get there as well and what
> > > would it cost us?
> > >
> > >
> > When you're as large as Apple or Yahoo, it's easy to pressure your
> > infrastructure providers to run on renewables. Wikimedia has basically no
> > bargaining power because they spend very little money (because they don't
> > run a lot of servers). I know Wikimedia feels huge and important, and
> it's
> > important in a lot of ways, but when it comes to pressuring datacenter
> > providers, it may as well not exist.
> >
> > It's possible that the only available option is to bring up new
> datacenters
> > in areas with renewable energy, and those datacenters may not be as
> > reliable, they may not be as well connected from a networking point of
> > view, they may have poor security and many other issues. I wouldn't
> expect
> > much movement towards renewables here until there's some really large
> > companies pushing for this in the relevant datacenters.
> >
> > - Ryan
> > ___
> > 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] I'd love to contribue. Can anyone help me get started?

[Pine W]

Hello Seattleite! There are some Wikimedians, many with technology
backrounds, who meet in the Seattle area. Please join our mailing list:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

I think that your existing skill set might fit well with WMF's interests in
mobile apps and mobile web. To get started there, I'd like to suggest that
you introduce yourself on the Mobile mailing list:
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Welcome aboard,

Pine
On May 18, 2016 13:42, "Ty Landercasper"  wrote:

> I'm a self employed programmer who's taking a bit of time off from
> his
> current project as a way to gain some fresh perspective and I thought I'd
> use that free time to help out a community I really appreciate. Wikipedia
> is
> one of the best things the internet has to offer and it has certainly
> helped
> me out a bunch of times, so it seemed like the place to volunteer.
>
> My problem is that is that I haven't done any sort of collaborative
> opensource project before, (the closest I've come to opensource is writing
> the compare plugin for Notepad++), and I'm not entirely sure what the best
> way to go about it is.
>
> I was wondering if someone there is willing to play the role of
> onboarding
> manager. You know, show me the ropes, assign some good relevant tasks to
> get
> a feel for things, the standard stuff. I'd really appreciate it, and I know
> I can contribute a lot to the community once I get on my feet.
>
>
> As for my skill set, while I don't have a lot of experience with
> PHP, I do
> have a lot of experience with just about everything else. I've done game
> development, mobile development, web development and even some good old
> fashioned desktop development, (not that anyone still uses desktop apps). I
> have no doubt that I can pick up the language quickly enough and I'm sure
> Google (the great teacher of all things) will help me figure out the rest.
>
> I'm attaching my resume, so that you can get a feel for my
> experience.
> (Plus it just seems like the thing to do in this situation.)
>
> I'm looking forward to getting started!
> Ty Landercasper
> t...@ibudesigns.com
>
>
> RESUME:
>
> OBJECTIVE:
> I'm one of those programmers who got into it for the love of
> programming
> and it shows. I've programmed on everything from the TI-83 to the Xbox 360,
> and if there's a skill I don't have than all I need is an excuse to learn
> it
> and I will. I turned a hobby project into a business that supported me for
> several years so I've learned a lot about how to make an amazing product
> that succeeds even in the ruthless market that is the app store, as well as
> the softer skills that you need to run a business.
>
> I'm looking for a good home. A start up or a startup like environment where
> there's more work than time and everyone has to wear multiple hats, and
> figure out how to get things done and even what can be done, because those
> are the environments that I thrive in.
>
> COMPUTER SKILLS:
> Visual Studio, C#,C++, Java, C, Visual Basic
> 4+ years iPhone, Android, Blackberry, Windows Mobile development
> Unity, Flash, Actionscript 2.0, ActionScript 3.0, Flex framework,
> Silverlight
> ASP.NET, AJAX, HTML, DHTML, CSS, Javascript, JSP
> Thirteen years experience with .NET
>
>
>
> EXPERIENCE:
> Owner Pixelality, Seattle, WA (7/14 to present)
> Created The Virtual Window a device that keeps track of your head
> and turns
> your TV into a realistic window!
> https://www.youtube.com/watch?v=DlEwnG-9O8A
> Used Kinect and Wii-mote based tracking
> Modified Unreal Engine to support Off-axis projection
> Used computer vision code to anaylize a video stream and find the
> head.
>
>
>
> Owner SupportStream, Seattle, WA (4/15 to present)
> https://supportstream.solutions/Supportee
> Funding model that allows people to donate a dollar a month to
> their
> favorite charities, artists or other things they care about.
> Created Marketing campaign that will eventually be used to drive
> donators
> to help their favorite causes : https://supportstream.solutions/
> ASP.NET backend.
> Paypal integration for payments. Went through the application
> process for
> advanced functionality.
> Cross-Site scripting with iframes
> Used JQuery for animations and popups.
> Custom designed logo and various CSS changes
>
>
>
> Contractor Big Finish Games (not Big Fish), Salt Lake City, UT (12/13 to
> 3/14)
> Programmed puzzles for the continuation of my all time favorite
> video game!
> Scripted both 2D and 3D puzzles using Unity and C#
>
>
>
> Owner Comic Reader Mobi, Seattle, WA (4/09 to present)
> http://comicreader.mobi
> Software allows fullsized comics to be read on small screens
> Several unique and intuitive UI features to make using the program
> ea

Re: [Wikitech-l] 12-May-2016 CREDIT, going back to Hangouts on Air/YouTube

[Pine W]

FYI, this week's presentations, according to the Etherpad, are:

* *Derk-Jan Hartman:* Video.js progress
* *Dmitry Brant*: Wikidata infoboxes in Android app
* *Joaquin Hernandez*: Vicky chat bot
* *Baha*: mobile printing for offline reading
* *Monte*: "smart random" content service endpoint
* *Erik*: Geo boosting search queries

Cheers,

Pine


On Thu, May 12, 2016 at 9:17 AM, Adam Baso  wrote:

> Reminder...
>
> On Thu, Apr 14, 2016 at 12:13 AM, Adam Baso  wrote:
>
> > Hi all,
> >
> > The next CREDIT showcase will be Thursday, 12-May-2016 at 1800 UTC (1100
> > SF).
> >
> > https://www.mediawiki.org/wiki/CREDIT_showcase
> >
> > For this one we'll use Hangouts on Air for presenters, and the customary
> > YouTube stream for viewers.
> >
> > See you next month!
> > -Adam
> >
> >
> >
> ___
> 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] JetBrains licenses for Volunteers and Staff

[Pine W]

Thanks for the info. I may request a license in mid to late Fall, when I
hope to be participating in Wikimedia software development.

Pine
On May 9, 2016 23:06, "Yuri Astrakhan"  wrote:

> Hi Pine,
>
> They are not upgrades, they are full one year renewable free licenses for
> the powerful ide with php, js, puppet, Ruby, Python, c++, ... , donated to
> help with Wiki development.
>
> You basically need to be a volunteer or a staff developer working on Wiki
> projects with some history of code contributions.   Resharper is a great
> product and it is part of the license, but I am not sure we have any .net
> code (I think we used to run bits of mono code somewhere, but that was a
> while ago). Have you submitted any patches? In what languages?
>
> Thanks!
> On May 10, 2016 08:48, "Pine W"  wrote:
>
> > Hi Yuri,
> >
> > ReSharper interests me. This email refers to license upgrades. What is
> > involved in initially qualifying for a license?
> >
> > Thanks,
> >
> > Pine
> > On Apr 18, 2016 09:44, "Yuri Astrakhan" 
> wrote:
> >
> > > PhpStorm, InteliJ IDEA, Resharper and other JetBrain users, we just
> > > received free upgraded licenses for all of their products.
> > >
> > > Check your account at https://account.jetbrains.com/licenses and login
> > > with
> > > that account inside your application to automatically use that license.
> > If
> > > you don't see the license, contact me or Sam Reed, and we will add you
> > > right away.  On IRC: yurik or reedy, or via email.  We could also use a
> > few
> > > more admins for these licenses. You will no longer need to copy/paste
> any
> > > licenses manually.
> > >
> > > IDEA:  use for PHP, JavaScript, Puppets, Ruby, and other web-related
> > > technologies
> > > https://www.jetbrains.com/idea/
> > >
> > > Resharper: for C# and Microsoft Visual Studio C++
> > > https://www.jetbrains.com/resharper/
> > >
> > > CLion: for C++
> > > https://www.jetbrains.com/clion/
> > > ___
> > > 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] JetBrains licenses for Volunteers and Staff

[Pine W]

Hi Yuri,

ReSharper interests me. This email refers to license upgrades. What is
involved in initially qualifying for a license?

Thanks,

Pine
On Apr 18, 2016 09:44, "Yuri Astrakhan"  wrote:

> PhpStorm, InteliJ IDEA, Resharper and other JetBrain users, we just
> received free upgraded licenses for all of their products.
>
> Check your account at https://account.jetbrains.com/licenses and login
> with
> that account inside your application to automatically use that license. If
> you don't see the license, contact me or Sam Reed, and we will add you
> right away.  On IRC: yurik or reedy, or via email.  We could also use a few
> more admins for these licenses. You will no longer need to copy/paste any
> licenses manually.
>
> IDEA:  use for PHP, JavaScript, Puppets, Ruby, and other web-related
> technologies
> https://www.jetbrains.com/idea/
>
> Resharper: for C# and Microsoft Visual Studio C++
> https://www.jetbrains.com/resharper/
>
> CLion: for C++
> https://www.jetbrains.com/clion/
> ___
> 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] [Labs-l] Fall 2015 Tool Labs user survey data published

[Pine W]

Sounds good. Thank you.

Pine

Pine
On May 5, 2016 08:19, "Bryan Davis"  wrote:

> On Wed, May 4, 2016 at 8:35 PM, Pine W  wrote:
> >
> > Hi Bryan,
> >
> > Thanks for the report. With this information in hand, what follow up is
> > planned?
>
> The primary purpose of the study was to set a baseline of qualitative
> ("how are we doing") responses. These will be used to gauge
> increase/decrease in satisfaction in comparison to future surveys.
> Tool Labs staff get regular feedback from people who are either
> extremely happy or extremely unhappy with services, but a broad survey
> like this is helpful to determine the general satisfaction of those
> who are not motivated to provide feedback by a single incident. No
> specific timetable has been set yet, but I expect to see another
> survey run between October and December of this year.
>
> Data from this survey, especially the free form comments, has already
> been shaping the quarterly planning for the Labs techops team and my
> more recent Tool Labs support initiative. I would say that a focus on
> making Tool Labs easier to use, especially by individuals who are not
> experts in the Unix command-line, is a general theme that is being
> pursued as we also seek to replace aging services like Sun Grid Engine
> and increase overall stability of the platform.
>
> One of the things that stood out the most for me personally in the
> feedback was a general need for tutorials and other task focused
> technical documentation. This is an area that I would like to
> encourage the existing Tool Labs developers to help with. There are
> some ideas of things to write in Phabricator [0][1]. Generally we are
> lacking on "big picture" documentation. We have a lot of documentation
> on solving particular problems but even those documents can be
> difficult to find and understand as they are mostly written with an
> assumption of familiarity with the services and terminology used in
> Tool Labs.
>
> [0]: https://phabricator.wikimedia.org/T101659
> [1]: https://phabricator.wikimedia.org/T123425
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> Labs-l mailing list
> lab...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Labs-l] Fall 2015 Tool Labs user survey data published

[Pine W]

Hi Bryan,

Thanks for the report. With this information in hand, what follow up is
planned?

Pine
On May 4, 2016 19:01, "Bryan Davis"  wrote:

> On Wed, May 4, 2016 at 7:57 PM, Bryan Davis  wrote:
> > [0]: https://meta.wikimedia.org/wiki/Research:Annual_Tool_Labs_Survey
>
> Apologies for that abrupt initial message, that was a great example of
> hitting the wrong key in a mail client. :)
>
> Between 2015-09-25 and 2015-10-08, the Wikimedia Foundation ran a
> direct response user survey of registered Tool Labs users. 106 users
> responded to the survey.
>
> Based on responses to demographic questions, the average[1] respondent:
> * Has used Tool Labs for 1-3 years
> * Developed & maintains 1-3 tools
> * Spends an hour or less a week using Tool Labs
> * Programs using PHP and/or Python
> * Does the majority of their work locally
> * Uses source control
> * Was not a developer or maintainer on Toolserver
>
> [1]: "Average" here means a range of responses covering 50% or more of
> responses to the question. This summarization is coarse, but useful as
> a broad generalization. Detailed demographic response data will be
> made available on wiki.
>
> Qualitative questions:
> 64% agree that services have high reliability (up time).
> 69% agree that it is easy to write code and have it running on Tool Labs.
> 67% agree that they feel they are supported by the Tool Labs team when
> they contact them via labs-l mailing list, #wikimedia-labs IRC
> channel, or phabricator.
> 53% agree that they receive useful information via labs-announce /
> labs-l mailing lists.
> 52% disagree that documentation is easy-to-find.
> 71% find the support they receive when using Tool Labs as good or
> better than the support they received when using Toolserver.
> 50% disagree that Tool Labs documentation is comprehensive.
> 50% agree that Tool Labs documentation is clear.
>
> Service usage:
> 45% use LabsDB often.
> 60% use webservices often.
> 54% use cronjobs often.
> 75% never use redis.
> 41% never use continuous jobs .
>
> The survey included several free form response sections. Survey
> participants were told that we would only publicly share their
> responses or survey results in aggregate or anonymized form. The
> freeform responses include comments broadly falling into these
> categories:
>
> Documentation (33 comments)
> Stability and performance (18 comments)
> Version control and Deployment (14 comments)
> Logs, Metrics, and Monitoring (12 comments)
> Package management (10 comments)
> SGE (8 comments)
> Database (7 comments)
> Account/Tool creation (5 comments)
> SSH (5 comments)
> Other (11 comments)
>
> Additonal details are available on meta [2].
>
> [2]: https://meta.wikimedia.org/wiki/Research:Annual_Tool_Labs_Survey
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> Labs-l mailing list
> lab...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Invitation to upcoming office hours with interim ED

[Pine W]

Forwarding.

Pine
-- Forwarded message --
From: "Katherine Maher" 
Date: May 4, 2016 17:47
Subject: [Wikimedia-l] Invitation to upcoming office hours with interim ED
To: , , <
wikimediaannounc...@lists.wikimedia.org>
Cc:

Hi everyone,

**Summary: I am delighted to invite you to join me for two upcoming office
hours, where I’ll answer community questions and share updates on the
Foundation’s work.**

It’s been a busy few weeks around the Wikimedia Foundation offices. We
shared our 2016-2017 annual plan, finished our quarterly reviews, and
attended Wikimedia Conference 2016 in Berlin with the Wikimedia affiliates.
[1]

In Berlin, I had the chance to do one of my favorite things: sit with
Wikimedians, listen, debate, and plan for the future. Of course, Berlin is
just one gathering, and there are thousands of other perspectives out
there. I want to hear more of these perspectives, and so I’m looking
forward to hosting two office hours over the coming weeks.

We plan to hold a traditional office hours on IRC, and will also experiment
with a video Q&A. We hope these different formats will make it easier for
more people to participate using their preferred communications channels.
We’ve chosen two different time zones, with the goal of reaching as many
people as possible. They are as follows:

*Video session*
*This session will be recorded, and the video will be posted on
Commons/Meta. Due to video conferencing limitations, we encourage advance
questions.*
Wednesday, 11 May 2016
00:00-1:00 UTC | 17:00-18:00 PDT [2]

*IRC session*
*This session follows the May monthly metrics meeting.[4] Like other office
hours, it will be held in #Wikimedia-office on Freenode.*
Thursday, 26 May 2016
19:00-20:00 UTC | 12:00-13:00 PDT [3]

We’re also collecting questions in advance for those who can’t make either
of those sessions. We’ve created a page on Meta where you can leave
questions or comments, check the details on the location of each session:
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Executive_Director/May_2016_office_hours

Please share this invitation with others you think may be interested!

I look forward to speaking soon,
Katherine

Translation notice - This message is available for translation on
Meta-Wiki:
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Executive_Director/May_2016_office_hours/Announcement

[1] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2016
[2] Time converter link:
http://www.timeanddate.com/worldclock/fixedtime.html?hour=0&min=00&sec=0&day=12&month=05&year=2016
[3] Time converter link:
http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=00&sec=0&day=26&month=05&year=2016
[4] https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings


--
Katherine Maher

Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105

+1 (415) 839-6885 ext. 6635
+1 (415) 712 4873
kma...@wikimedia.org
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
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] Videos from Jerusalem Hackathon & WikiArabia

[Pine W]

Forwarding

Pine
-- Forwarded message --
From: "Brill Lyle" 
Date: Apr 28, 2016 11:14
Subject: [Wikimedia-l] Videos from Jerusalem Hackathon & WikiArabia
To: "Wikimedia Mailing List" 
Cc:

In case you haven't seen these, the videos below were shared during today's
WMF Metrics and Activities Meeting - April 2016.

https://commons.wikimedia.org/wiki/File:The_2016_Wikimedia_Hackathon_in_Jerusalem.webm

https://commons.wikimedia.org/wiki/File:WikiArabia_tech_meetup_in_Ramallah_2016.webm

Best,

*Erika Herzog*
Wikipedia *User:BrillLyle* 
Secretary, Wikimedia NYC

___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
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] Technical advice on expert review?

[Pine W]

Hi Anthony,

Thanks for this initiative!

As someone who deals with budget tables, I am very supportive of improving
features for table editing. Have you tried editing tables in VE?

You might also consider using a spreadsheet like Google Sheets,  Microsoft
Excel, or (offline) LibreOffice Calc.

Because the use case here involves medical content, I am cross-posting this
thread to the Wikimedia-Medicine mailing list, and also pinging Doc James
to ask for comments.

Pine
On Apr 16, 2016 23:21, "Anthony Cole"  wrote:

> BMJ, the publishers of the *British Medical Journal* and other top-tier
> biomedical journals, have kindly recruited the best minds they can get to
> review the en.Wikipedia's article, "Parkinson's disease".
>
> We began the review by passing the article, in a Word document, from one
> reviewer to the next by email. Each made proposed changes to the article
> text and left comments in the document, using Word's "Review" and "Track
> changes" features.
>
> At that point we needed to start a discussion, and Word isn't ideal for
> that. So I pasted the relevant paragraphs from the Word document into the
> left column of a wiki table, and the reviewers' comments into the right
> column, where the discussion could happen. [1] I manually applied
> background colours to distinguish deletions from additions in the left
> column, using .
>
> That discussion has now begun but one of the many things I've learned
> during all this is, the top researchers and theorists spend a lot of time
> in the air (travelling to conferences, lectures, meetings), and it is then,
> free from the demands of job and family, when they do their reviewing.
>
> So, I have pasted that wiki table into Word and have made it available to
> the reviewers here: [2]. Now they can download a copy before they get on a
> flight, and email it back to me with their comments when they're online
> again, and I'll transcribe their comments into the wiki table for
> discussion.
>
> This may be as simple as it gets but I just thought I'd put this before
> you, in case you may have thoughts on a better technical approach for next
> time. (BMJ have offered to do more of these.) I'm finding the construction
> of the wiki table tedious (particularly highlighting the deletions and
> additions) though I'm getting faster, and transcribing offline comments
> from the Word document into the wiki table will be a small chore. The wiki
> table pastes easily into Word with highlighting and formatting intact, but
> not vice versa. (I've also asked at Village pump (technical).)
>
> Any thoughts on making this easier or smarter would be much appreciated.
>
> Anthony Cole
>
> 1. https://en.wikipedia.org/wiki/User:Anthonyhcole/sandbox
> 2.
>
> https://onedrive.live.com/view.aspx?resid=C1FF29217E209194!2141&ithint=file%2cdocx&app=Word&authkey=!AFGj7fd2K4v7N5o
> ___
> 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] How can someone get code reviews from the Wikidata dev team?

[Pine W]

A concise illustration from Lydia Pintscher that shows an innovative way to
notify the Wikidata dev team that patches are ready for review:

https://commons.wikimedia.org/wiki/File:How_to_get_Wikidata_code_review_done.jpg

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

Re: [Wikitech-l] productivity of mediawiki developers

[Pine W]

Niklas puts it well. Analogously, in sports like baseball there are lots of
statistics about players, coaches, teams, divisions, and leagues. Awards
are given based strictly on quantities, as well as more subjectively on
qualities for recognitions such as Rookie of the Year and Most Valuable
Player.

Wikimedia technical development is a team sport, and that unlike on the
content side of Wikipedia where there can be rival views, I think that on
technical matters almost everyone collaborates toward compatible goals.

I've been thinking about how to ensure that *quality* is valued alongside
*quantity*. We struggle do this balance well in the US health care system
when we evaluate hospitals and doctors, and WMF stuggles to do this well
when the Community Resources and Evaluation teams evaluate grant proposals
and the performance of Wikimedia affiliates. I'm very interested in ideas
about how to estimate the quality of contributions (including code review!)
as well as the quantity of contributions.

Pine
On Apr 4, 2016 08:22, "Niklas Laxström"  wrote:

> 2016-04-04 17:02 GMT+03:00 Quim Gil :
> > The first question to answer is what information are you looking for when
> > you want to measure developers' "productivity". What would be the
> > motivation of that estimation? What is the motivation behind this thread?
>
> One reason comes to me mind. My gut feeling is that we are not very
> good at consistently giving recognition for technical work. One
> possible reason is that we do not have clear and understandable
> metrics or promote those metrics enough. Nor am I aware of any process
> for awards and celebration (The Academy Awards would be an example in
> another context, also Wikipedian of the year).
>
> As an example, I recall vaguely that during the Bugzilla times we used
> to have regular emails on wikitech-l with list of people who closed
> most bugs.
>
> Having some metrics for different activities could stir up some
> healthy competition (also unhealthy if we are not careful) and of
> course there is a lot of important work that is not visible from the
> numbers only.
>
> I am not expert on this subject, but I think developers (especially
> volunteers, but also others) are more likely to stick around if they
> feel that their work is recognized and appreciated. For the latter we
> already know that we should improve our code review process.
>
>   -Niklas
>
> ___
> 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] Feelings

[Pine W]

I like that idea, Ori. Jonathan, what do you think about testing this
concept in the Teahouse, as well as wikitext talk pages and Flow talk pages?

Pine
On Apr 2, 2016 18:38, "Ori Livneh"  wrote:

> On Fri, Apr 1, 2016 at 10:24 PM, Legoktm 
> wrote:
>
> > Hi,
> >
> > It's well known that Wikipedia is facing threats from other social
> > networks and losing editors. While many of us spend time trying to make
> > Wikipedia different, we need to be cognizant that what other social
> > networks are doing is working. And if we can't beat them, we need to
> > join them.
> >
> > I've written a patch[1] that introduces a new feature to the Thanks
> > extension called "feelings". When hovering over a "thank" link, five
> > different emoji icons will pop up[2], representing five different
> > feelings: happy, love, surprise, anger, and fear. Editors can pick one
> > of those options instead of just a plain thanks, to indicate how they
> > really feel, which the recipient will see[3].
> >
>
> Of the many initiatives to improve editor engagement and retention that the
> Wikimedia Foundation has launched over the years, the only one that had a
> demonstrable and substantial impact (AFAIK) was the Teahouse.
>
> The goal of the Teahouse initiative was "learning whether a social approach
> to new editor support could retain more new editors there"; its stated
> design goal was to create a space for new users which would feature "warm
> colors, inviting pictorial and thematic elements, simple mechanisms for
> communicating, and a warm welcome from real people."[0]
>
> Several studies were made of the Teahouse's impact on editors. One study,
> conducted by Jonathan Morgan and Aaron Halfaker, found that new editors who
> were invited to participate in the Teahouse were 10% more likely to have
> met the thresholds for survival in the weeks and months after
> registration.[1]
>
> Another significant fact about the Teahouse is the substantial
> participation from women. Women make up 9% of the general editor
> population, but 29% percent of Teahouse participants.[2]
>
> When new editors who had been invited to the Teahouse were asked (in a 2012
> survey) to described what they liked about their experiences, many
> respondents spoke about the positive emotional environment, saying things
> like: "the fact that there is somebody 'out there', that there is a sincere
> community, gives a professional and safe feeling about Wikipedia", and "the
> editors are very friendly and patient, which is great when compared to the
> rest of Wikipedia in how new editors are treated."[2]
>
> Why am I going on about this? I guess I'm a bit bummed out that the idea of
> designing user interfaces that seek to improve the emotional environment by
> making it easier to be warm and personal to one another is a joke. I don't
> think any topic is sacrosanct, this topic included. But humor works best
> when it provides a counterpoint and a foil to "serious" discourse, and
> there just isn't very much serious discourse on this topic to go around. I
> also worry that people in and around our community who feel a need for more
> opportunities for positive emotional interactions will feel invalidated,
> ridiculous, ashamed, or at any rate less confident about ever speaking up
> about this topic in a serious way, and less hopeful about being heard.
>
>   [0]: https://meta.wikimedia.org/wiki/Research:Teahouse
>   [1]:
>
> https://meta.wikimedia.org/wiki/Research:Teahouse_long_term_new_editor_retention#Results
>   [2]:
> https://meta.wikimedia.org/wiki/Research:Teahouse/Phase_2_report/Metrics
> ___
> 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] productivity of mediawiki developers

[Pine W]

Yeah. It would be interesting to have multiple measures of "productivity"
for technical contributors, including code review.

Quim: is this something that's within Technical Collaboration's scope? If
not, perhaps it's something that I could work on developing later this year.

Pine

On Sat, Apr 2, 2016 at 12:10 PM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> Hi rupert,
>
> I'm pretty sure http://korma.wmflabs.org/browser/scm.html and other pages
> of korma will give you some information. But keep in mind, that
> productivity doesn't only mean the number of commits, or the line of codes
> :)
>
> Best,
> Florian
>
> -Ursprüngliche Nachricht-
> Von: Wikitech-l [mailto:wikitech-l-boun...@lists.wikimedia.org] Im
> Auftrag von rupert THURNER
> Gesendet: Samstag, 2. April 2016 21:06
> An: Wikimedia developers 
> Betreff: [Wikitech-l] productivity of mediawiki developers
>
> hi,
>
> is there a statistics about mediawiki developer productivity? i just fell
> over a couple of pages and i am quite impressed i must say:
> * gabriel, https://github.com/gwicke, 2'300 commits last year
> * jeroen, https://github.com/JeroenDeDauw, 3'700 commits a year
> * ori, https://github.com/atdt, 1'700
> * james, https://github.com/jdforrester, 1'200
> * yuri, https://github.com/nyurik, 900
> * matt: https://github.com/mattflaschen, 400 commits
>
> rupert
>
> ___
> 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] productivity of mediawiki developers

[Pine W]

Perhaps some Working Wikipedian and Tireless Contributor barnstars are
appropriate for that group!

Pine

On Sat, Apr 2, 2016 at 12:06 PM, rupert THURNER 
wrote:

> hi,
>
> is there a statistics about mediawiki developer productivity? i just
> fell over a couple of pages and i am quite impressed i must say:
> * gabriel, https://github.com/gwicke, 2'300 commits last year
> * jeroen, https://github.com/JeroenDeDauw, 3'700 commits a year
> * ori, https://github.com/atdt, 1'700
> * james, https://github.com/jdforrester, 1'200
> * yuri, https://github.com/nyurik, 900
> * matt: https://github.com/mattflaschen, 400 commits
>
> rupert
>
> ___
> 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] Feelings

[Pine W]

I can't tell if this is intended to be an April 1st joke or if it's
serious. In any case, I could see this being an interesting option for talk
pages, particularly where Flow is enabled.

Pine

On Fri, Apr 1, 2016 at 12:24 PM, Legoktm 
wrote:

> Hi,
>
> It's well known that Wikipedia is facing threats from other social
> networks and losing editors. While many of us spend time trying to make
> Wikipedia different, we need to be cognizant that what other social
> networks are doing is working. And if we can't beat them, we need to
> join them.
>
> I've written a patch[1] that introduces a new feature to the Thanks
> extension called "feelings". When hovering over a "thank" link, five
> different emoji icons will pop up[2], representing five different
> feelings: happy, love, surprise, anger, and fear. Editors can pick one
> of those options instead of just a plain thanks, to indicate how they
> really feel, which the recipient will see[3].
>
> Of course, some might consider this feature to be controversial (I
> suspect they would respond to my email with "anger" or "fear"), so I've
> added a feature flag for it. Setting
>  $wgDontFixEditorRetentionProblem = true;
> will disable it for your wiki.
>
> Please give the patch a try, I've only tested it in MonoBook so far, it
> might need some extra CSS in Vector.
>
> [1] https://gerrit.wikimedia.org/r/280961
> [2] https://phabricator.wikimedia.org/F3810964
> [3] https://phabricator.wikimedia.org/F3810963
>
> -- Legoktm
>
> ___
> 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] Internship opening: product management at WMDE

[Pine W]

Forwarding info about an opportunity to intern in product management with
Wikidata and the good people at Wikimedia Deutschland.

Pine
-- Forwarded message --
From: "Lydia Pintscher" 
Date: Mar 24, 2016 07:24
Subject: [Wikidata] internship opening: product management at WMDE
To: "Discussion list for the Wikidata project." <
wikid...@lists.wikimedia.org>
Cc:

Hey folks :)

I am looking for someone to support me me with my product management work
at WMDE as an intern. If you'd love to work with me and the rest of the
team, love Wikidata and want to learn, this might be the thing for you.
More details are here:
https://wikimedia.de/wiki/Internship_Product_Management


Cheers
Lydia
-- 
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata

Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.

Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.

___
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: [opensource-107] Seattle to host the 2016 OpenStreetMap State of the Map US Conference

[Pine W]

(Cross-posting)

For Wikimedia folks who are interested in possible collaborations with OSM,
now seems like a good time to start thinking about possible presentations.

Staff from the Wikimedia Foundation, and/or Wikimedia volunteers from
around the US outside of the Seattle area, may want to start thinking about
travel plans.

For Wikimedia volunteers outside of Cascadia Wikimedians territory, you
might consider applying for WMF Travel and Participation Support grants [1].

If you're inside of Cascadia Wikimedians territory and would like to attend
the conference, we may have funds in our budget that can support your
attendance. Contact me off-list for details.

Regards,

Pine

[1] https://meta.wikimedia.org/wiki/Grants:TPS


-- Forwarded message --
From: Clifford Snow 
Date: Tue, Mar 1, 2016 at 5:18 PM
Subject: [opensource-107] Seattle to host the 2016 OpenStreetMap State of
the Map US Conference
To: opensource-107-annou...@meetup.com


I am excited to announce that Seattle was chosen to host the OpenStreetMap
2016 State of the Map US Conference. The conference will take place July
23-25 on SeattleU's campus. We chose SeattleU for their low cost, proximity
to Seattle and access to public transit.  The food trucks near by didn't
hurt either.


We are looking for help! Let us know if you want to help. Request for
presentation proposals should be coming fairly soon. Start thinking about
what you want to present or teach.

The formal announcement can be found at:
https://openstreetmap.us/2016/02/sotmus-2016/

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

[Wikitech-l] Fwd: Re: [Wikimedia-l] [Wmfall] Inspire Campaign on content curation & review launches today!

[Pine W]

Forwarding the campaign announcement, and ideas from Aaron Halfaker.

Pine
-- Forwarded message --
From: "Aaron Halfaker" 
Date: Feb 29, 2016 16:00
Subject: Re: [Wikimedia-l] [Wmfall] Inspire Campaign on content curation &
review launches today!
To: "Chris Jethro Schilling" 
Cc: "Staff All" , ,
"Wikimedia Mailing List" 

I just finished submitting two ideas that I'd like to advise.

https://meta.wikimedia.org/wiki/Grants:IdeaLab/Automated_good-faith_newcomer_detection
Build and deploy a machine learning model for flagging newcomers who are
editing in good-faith. This has the potential to mitigate some of the
secondary, demotivational effects when good-faith newcomers' work passes
through curation/review processes.

https://meta.wikimedia.org/wiki/Grants:IdeaLab/Fast_and_slow_new_article_review
Concerns about the introduction of spam into Wikipedia has lead Wikipedians
towards implementing high speed new article review/curation processes. The
speed at which editors tag articles for deletion via these processes is
great for dealing with spam, but it might also be faster that good-faith
new article creators can build their articles. We could build a machine
learning classifier that is tuned to detect spammy article drafts. This
would allow the new pages queue to be split into a high-speed spammy
article review, and a low-speed article review that allows creators time to
make a better first draft.

I'll submit some more when I can.  :)

On Sun, Feb 28, 2016 at 4:56 PM, Chris "Jethro" Schilling <
cschill...@wikimedia.org> wrote:

> Hi everyone,
>
> I am pleased to announce the launch of the second Inspire Campaign for
> IdeaLab.[1]  The theme of this campaign is focused on improving tasks
> related to content curation & review in our projects:
>
> 
>
> Reviewing and organizing tasks are fundamental to all WIkimedia projects,
> and these efforts maintain and directly improve the quality of our
projects
> in addition to increasing the visibility of their content.  We invite
> everyone to participate by sharing your ideas and proposals on how to
> enhance these efforts. Constructive feedback and collaboration on ideas is
> encouraged - your skills and advice can elevate a project into action. The
> campaign runs until 29 March.
>
> All proposals are welcome - research projects, technical solutions,
> community organizing and outreach, or something completely new! Grants are
> available from the Wikimedia Foundation for projects developed during this
> campaign that need financial support.[2]  Google Hangout sessions are
> available in March if you'd like to have a conversation about your
ideas.[3]
>
> Join the Inspire Campaign and let’s work together to improve review and
> curation tasks so that we can make our content more meaningful and
> accessible.
>
> With thanks,
>
> Jethro
>
> [1] You can learn more about the results of the first Inspire Campaign
> here: <
> https://meta.wikimedia.org/wiki/Research:Spring_2015_Inspire_campaign>
> [2] 
> [3]   (Note: If
> another time would work better for you, feel free to e-mail me or ping me
> on-wiki).
>
> ---
> Chris "Jethro" Schilling
> I JethroBT (WMF) 
> Community Organizer, Wikimedia Foundation
> 
>
> ___
> Wmfall mailing list
> wmf...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
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: Fwd: February 2016 Lightning Talks

[Pine W]

(cross-posting)

Reminder that these lightning talks are happening tomorrow, Tuesday
February 16, at 1900 UTC / 11:00 AM Pacific. Because there are 3 presenters
and a 1-hour block of time, each presenter has about 15 minutes including
time for questions. We might finish early.

On the agenda:

* Pine: "LearnWIki" Instructional video series on Wikipedia mechanics
(Including VE and citoid) and community practices
<https://meta.wikimedia.org/wiki/Grants:IEG/Motivational_and_educational_video_to_introduce_Wikimedia/January_message_to_village_pumps>

* Madhu Viswanathan: "Counting unique devices accessing Wikipedia projects
using Last access method"

* Rosemary Rein: "Program Capacity and Learning-Building a Roadmap Together"
<https://commons.wikimedia.org/wiki/File:Program_Capacity_and_Learning_Roadmap_-_Office_Hours_Feb_16.pdf>

Hope to see you there!

Pine




On Tue, Feb 2, 2016 at 5:47 PM, Kevin Leduc  wrote:

> Thanks for forwarding Pine!  I welcome any 10 minute talks from GLAM and
> Education as well.  If you add your name to the list [1], email me as well
> so I can contact you and forward notes for Lightning Talk speakers.
>
> [1] https://www.mediawiki.org/wiki/Lightning_Talks#February_2016
>
> On Tue, Feb 2, 2016 at 4:59 PM, Pine W  wrote:
>
>> Boldly forwarding* in case others would like to view or present a
>> lightning talk. I plan to give a lightning talk about the video series
>> <https://meta.wikimedia.org/wiki/Grants:IEG/Motivational_and_educational_video_to_introduce_Wikimedia/January_message_to_village_pumps>
>> which I'm in the process of producing with the support of an individual
>> engagement grant.
>>
>> Although these talks can be about technical topics like video formats, I
>> think that there are education and GLAM activities that could fit under the
>> umbrella as well, especially if they have technical or research aspects.
>> For example, I'll probably focus much of my presentation on my background
>> research and project design process.
>>
>> Hope to see you there!
>> Pine
>>
>> * To boldly forward where no one has forwarded before
>>
>> -- Forwarded message --
>> From: Kevin Leduc 
>> Date: Tue, Feb 2, 2016 at 4:23 PM
>> Subject: [Wikitech-l] Fwd: February 2016 Lightning Talks
>> To: Wikimedia developers 
>>
>>
>> -- Forwarded message --
>> From: Kevin Leduc 
>> Date: Tue, Feb 2, 2016 at 4:22 PM
>> Subject: February 2016 Lightning Talks
>> To: "Staff (All)" 
>>
>>
>> Hi All,
>>
>>
>> The next Lightning Talks are scheduled for February 16th (two weeks from
>> today).  We hope at least 4 people will sign up for the talks by Friday
>> February 12th otherwise we will postpone them another month.  Lightning
>> Talks are an opportunity for teams @ WMF & in the Community to showcase
>> something they have achieved:  a quarterly goal, milestone, release, or
>> anything of significance to the rest of the foundation and the movement as
>> a whole.
>>
>>
>> Each presentation will be 10 minutes or less including time for questions.
>>
>> Sign up here:
>> https://www.mediawiki.org/wiki/Lightning_Talks#February_2016
>>
>>
>> Next round of Lightning Talks:
>>
>> When: Tuesday February 16, 1900 UTC
>> <
>> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks&iso=20160216T19&p1=1440&ah=1
>> >,
>> 11am PST (We have added this Lightning Talk to the WMF Engineering, Fun &
>> Learning, and Staff calendars)
>>
>> Where: 5th Floor
>>
>> Remotees: On-Air google hangout will be provided just before the meeting
>>
>> IRC: #wikimedia-tech
>>
>> YouTube stream: http://www.youtube.com/watch?v=D3fyCgBWvFc
>>
>>
>> Thanks!
>>
>> Kevin Leduc, Megan Neisler, Brendan Campbell
>> ___
>> 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] [Wiki-research-l] ReplayEdits tool gets a shout-out in NYT

[Pine W]

Cool. Forwarding this email.

Pine

On Tue, Feb 2, 2016 at 10:30 AM, Jonathan Morgan 
wrote:

> Yesterday, 2013 IEG grantee Jeph Paul started seeing 1000s of hits on his
> (grant-funded, volunteer-maintained) ReplayEdits tool which visually
> replays edit histories of Wikipedia articles.
>
> Here's why:
>
> http://www.nytimes.com/2016/02/02/us/politics/wikipedia-donald-trump-2016-election.html?_r=0
>   (the tool  is
> linked from one of the last few paragraphs in the article)
>
> The article itself is not exceptional. It's just cool to see one of our
> locally grown research prototypes get good press.
>
> Jonathan
>
> --
> Jonathan T. Morgan
> Senior Design Researcher
> Wikimedia Foundation
> User:Jmorgan (WMF) 
>
>
> ___
> 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

Re: [Wikitech-l] Developer Relations Weekly Summary

[Pine W]

Hi Rob,

Code review seems to be a choke point and the subject of numerous concerns,
so I'd like to see SMART goals for improvements to code review, and one or
more individuals (probably WMF individuals) taking leadership for meeting
those goals. Perhaps the conversation at the Summit will inform the
creation of these goals in WMF Q4 and in the WMF 16-17 Annual Plan.

Thanks,
Pine
On Feb 2, 2016 6:41 AM, "Rob Lanphier"  wrote:

> On Thu, Jan 28, 2016 at 2:57 PM, Pine W  wrote:
>
> > Is there, or will there be, a page somewhere that describes the outcomes
> of
> > the Developer Summit?
> >
>
> I would love for the working group chairs to make the outcomes available
> from the main WikiDev16 page:
> <https://mediawiki.org/wiki/WikiDev16>
>
> The meeting notes from most of the meetings are there, but please add
> anything you feel is missing, and/or ask the chairs of each of the meetings
> to document their next steps.  I have this on my TODO list to continue
> following up with various working group chairs (and helping with this), but
> I also have been busy with other work, so I don't fault them at all for not
> getting to it.
>
> Pine, could you describe what you hope to get out of the information?
>
> Thanks
> Rob
> ___
> 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] Please Welcome Guillaume Lederrey to the WMF

[Pine W]

Sounds like a good hire. Welcome!

Pine

On Mon, Feb 1, 2016 at 11:52 AM, Alangi Derick 
wrote:

> Welcome Guillaume Lederrey to WMF.
> Regards
> Alangi Derick Ndimnain
>
>
> On Mon, Feb 1, 2016 at 8:51 PM, Tomasz Finc  wrote:
> > I am pleased to announce that Guillaume Lederrey joins WMF this week
> > as Operation Engineer in the Discovery team. Guillaume will work
> > closely with our operations team to support Elastic Search, Maps, and
> > WDQS along with strengthening our experience with Java based services.
> >
> > Guillaume will be working remotely from Lausanne (Switzerland) where
> > he lives with his 4 month old son and his mother. Guillaume has
> > previous experience with non profits, having worked for a year in
> > Rwanda for an NGO. Working to make the world a better place is what
> > motivates him to join WMF.
> >
> > For the last 5 years, Guillaume has been working for Nespresso, taking
> > care of all things from performance and stability of the e-commerce
> > and backend stacks, challenging agile practices and introducing Puppet
> > as the main configuration tool to managing build tools, improving
> > automated code quality and bringing coffee to his coworkers.
> >
> > On his free time, Guillaume is the maintainer of JmxTrans [1], the
> > missing piece to monitor JVM based applications.
> >
> > Guillaume can be found on IRC under the nickname 'gehel'.
> >
> > Please join me in welcoming him!
> >
> > --tomasz
> >
> > [1]: https://github.com/jmxtrans/jmxtrans
> >
> > ___
> > 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] VisualEditor deployment to 1000+ users: who wants the feedback?

[Pine W]

I think the Editing team would be interested in this! Pinging James
Forrester.

I am glad to see the interest in tables. Table editing is much easier in VE
than in wikitext and I'd love to see additional table editing functionality
in VE, including the ability to import tables from spreadsheet applications
with text and cell formatting.

Pine

On Fri, Jan 29, 2016 at 12:22 PM, Daniel Barrett  wrote:

> Within the next few weeks, I'll be deploying VisualEditor for 1000+
> authors here at Cimpress/Vistaprint, in a wiki with 225,000 articles.
>
> I plan to collect feedback from our users on what works and what doesn't.
> What would be the best way to communicate this feedback to Wikimedia?
>
> Here are some early, informal comments from our pilot group of 20 users:
>
> "I am in love!"
>
> "TemplateData integration is awesome."
>
> "How do I insert  tags?"  (He didn't notice the "More" link in the
> font menu.)
>
> "How do I set the width of a table column?"
>
> "How do I copy and paste table rows?"
>
> "Editing links is fiddly" (https://phabricator.wikimedia.org/T124305)
>
> "I didn't see the editing tools at first because they're white on a white
> background."
>
> "Can we save the page without having a pop-up?"
>
> Thanks,
> DanB
>
>
> ___
> 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] Developer Relations Weekly Summary

[Pine W]

Hi Quim,

Is there, or will there be, a page somewhere that describes the outcomes of
the Developer Summit?

Thanks!
Pine

On Thu, Jan 28, 2016 at 6:19 AM, Quim Gil  wrote:

> The Winter break took longer than expected. Busy times!
>
> You can help develop the next summary.
>
> *Developer Relations focus*
>
> * Wrapping up Google Code-in 2015
> * Wikimedia Hackathon 2016 travel sponsorship requests
> * Wikimedia Developer Summit 2016/Lessons Learned
> * Developer Relations strategy and annual plan
>
> There is a lot more at
>
> https://www.mediawiki.org/wiki/Developer_Relations/Weekly_summary#2016-01-26
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
> ___
> 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-l] Community Wishlist Survey: Status report #1

[Pine W]

Thanks Danny, it's nice to see these initiatives being analyzed and options
for them being considered actively.

Pine
On Jan 20, 2016 5:37 PM, "Danny Horn"  wrote:

> Hi everyone,
>
> We've posted the Community Tech team's first status report on our progress
> with the Community Wishlist Survey, and you're invited to come and check it
> out:
>
>
> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_report_1
>
> In November and December, we invited active contributors to Wikimedia
> projects to propose, discuss and vote on the features and fixes that they
> most want to see. 634 people participated in the survey, voting on 107
> proposals.
>
> Our team has committed to investigating and responding to the top 10
> wishes. In many cases, our team will be designing and building tools
> ourselves, or collaborating with other teams and volunteers who are working
> in that area. For the wishes that we can't build this year -- because it's
> too big for our team, or there's a problem that we can't solve -- then we
> can at least offer open discussion on the problem, and detailed
> documentation explaining what we've learned, so the information can be used
> by other developers in the future.
>
> We've done a preliminary assessment of the top 10, which is described in
> the status report. As of right now (mid-January), the two items that we're
> actively working on  are #1) Migrate dead links to the Wayback Machine, and
> #7) Pageview Stats tool. Why are we working on those two and not the
> others? Check out the status report for all the answers.
>
> I'm going to post the quick overview of the top 10 wishes here. Each of
> these wishes is discussed in detail on the status report page.
>
> 1. Migrate dead links to the Wayback Machine: Currently in progress,
> working with a community developer and the Internet Archive. This is one of
> the two projects we're actively working on now (mid-January).
>
> 2. Improved diff compare screen: Needs investigation and community
> discussion to define the problems that we want to solve.
>
> 3. Central repository for templates, gadgets and Lua modules: Needs
> underlying technical work that's currently under discussion by another
> team.
>
> 4. Cross-wiki watchlist: Needs technical investigation on the existing
> Crosswatch tool, and the Collaboration team's cross-wiki notifications.
>
> 5. Numerical sorting in categories: Investigation is underway. There are a
> couple potential solutions that we need to figure out.
>
> 6. Allow categories in Commons in all languages: Currently talking with
> Wikidata about using structured metadata to solve the underlying problem.
>
> 7. Pageview Stats tool: Currently talking with the Analytics team about
> their new pageview API. Needs some community discussion to define the
> front-end spec. This is one of the two projects we're actively working on
> now (mid-January), because the Analytics team is eager to use the new API
> that they've developed.
>
> 8. Global cross-wiki talk page: Needs community discussion to define the
> product.
>
> 9. Improve copy and paste detection bot: Need to work with volunteer
> developers to define scope on improving the existing Plagiabot.
>
> 10. Add a user watchlist: We've heard significant pushback about the
> vandal-fighting use case, because of the risk of enabling harassment.
> Currently investigating an opt-in version that would be useful for mentors,
> classes, editathons and WikiProjects.
>
> Here's the status report link again, for lots more information:
>
>
> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_report_1
>
> Our team is really excited about the work that we'll get to do this year,
> and we're looking forward to talking and working with you as we go along.
>
> Thanks,
>
> Danny Horn
> Product Manager
> WMF - Community Tech
> User:DannyH (WMF)
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> 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] Meeting scribes for WMF meetings

[Pine W]

Just want to note that I believe that Community Resources and L&E use
interns for this purpose. You can probably contact Siko or Rosemary to
learn more.

Pine

On Tue, Jan 19, 2016 at 10:08 PM, Rob Lanphier  wrote:

> Hi folks,
>
> One thing we'd love to get better at is taking and publishing useful
> notes from our meetings.  An example of that is ArchCom meetings, for
> which we have been taking notes for a while, but I haven't gotten
> around to publishing.  Another example is our weekly tech Engineering
> Tech managers meetings, which are increasing in importance as we head
> into budget setting season.
>
> Is there anyone available to be a volunteer scribe for ArchCom and/or
> Tech/Eng management meetings?  For logistical reasons, I would prefer
> existing WMF employee offers over non-WMF offers, but beggars can't be
> choosers ;-)
>
> The next meeting opportunity is in 15 hours: the ArchCom is having
> it's weekly 1pm PST (21:00 UTC) meeting just prior to the 2pm PST
> public IRC meeting.  If you're interested, please let me know!  The
> best way to express your volunteer interest is by adding your sig on
> the bottom of this page:
> 
>
> ...and discussion is welcomed on the associated talk page.
>
> Rob
>
> ___
> 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: Thank yous and video recordings for the Wikipedia 15 joint celebrations (SF, NYC, and Seattle)

[Pine W]

Forwarding video links (:

-- Forwarded message --
From: Pine W 
Date: Sat, Jan 16, 2016 at 6:43 PM
Subject: Thank yous and video recordings for the Wikipedia 15 joint
celebrations (SF, NYC, and Seattle)
To:



Video links to Youtube (Commons uploads will happen in the near future, I
believe):

* Welcome and lightning talks: https://www.youtube.com/watch?v=dGhxEpowM6A
* "Wikipedia's content gender gap":
https://www.youtube.com/watch?v=uW1WSVmpvwk
* "Stories from the weird old days":
https://www.youtube.com/watch?v=ZLmGc-hpp3U
* Panel discussion "The impact of 15 years of Wikipedia":
https://www.youtube.com/watch?v=CiEjkxCGmgU

Here's to the next 15 years!

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

Re: [Wikitech-l] New tutorial for interactive graphics on Wiki

[Pine W]

I've played with this more, and I like how it works. I can imagine people
using this map with other data sets like HDI, GDP per capita, inflation,
Wikipedia readership, and WMF fundraising (:

Pine

On Thu, Dec 31, 2015 at 2:13 AM, Szymon Grabarczuk  wrote:

> Great! now, I think it should be marked for translation.
>
> On 31 December 2015 at 08:38, Pine W  wrote:
>
> > The tutorial looks nice! I will take a look when I am less distracted by
> > finance reports. Thank you for working on this.
> >
> > Pine
> > On Dec 30, 2015 22:37, "Yuri Astrakhan" 
> wrote:
> >
> > > I just finished writing a tutorial on how to build interactive Vega
> > graphs
> > > for Wikipedia. And yes, we could build video games this way too :)
> > >
> > >
> >
> https://www.mediawiki.org/wiki/Extension:Graph/Interactive_Graph_Tutorial
> > > ___
> > > 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
> >
>
>
>
> --
> *Szymon Grabarczuk*
>
> Free Knowledge Advocacy Group EU
> Head of Research & Development Group, Wikimedia Polska
> pl.wikimedia.org/wiki/User:Tar_Lócesilion
> <http://pl.wikimedia.org/wiki/User:Tar_L%C3%B3cesilion>
> <http://pl.wikimedia.org/wiki/User:Tar_L%C3%B3cesilion>
> ___
> 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] New tutorial for interactive graphics on Wiki

[Pine W]

The tutorial looks nice! I will take a look when I am less distracted by
finance reports. Thank you for working on this.

Pine
On Dec 30, 2015 22:37, "Yuri Astrakhan"  wrote:

> I just finished writing a tutorial on how to build interactive Vega graphs
> for Wikipedia. And yes, we could build video games this way too :)
>
> https://www.mediawiki.org/wiki/Extension:Graph/Interactive_Graph_Tutorial
> ___
> 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] New tutorial for interactive graphics on Wiki

[Pine W]

Excellent. Can I create a full-detail 3D model of the Millennium Falcon? (:

Pine
On Dec 30, 2015 22:37, "Yuri Astrakhan"  wrote:

> I just finished writing a tutorial on how to build interactive Vega graphs
> for Wikipedia. And yes, we could build video games this way too :)
>
> https://www.mediawiki.org/wiki/Extension:Graph/Interactive_Graph_Tutorial
> ___
> 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] VisualEditor support for table copy-and-paste from Word

[Pine W]

Following up on this thread:

1. I'm continuing to find that VE's table editor is a significant
improvement over the Wikitext editor for typical tasks. I'm looking forward
to the day when I can copy and paste formatted spreadsheet data from places
like Google Sheets, ODS, and Excel into VE and have them convert fully into
Wikimarkup.

2. I have a recently-approved IEG [1] to create a series of modular video
tutorials about Wikipedia editing, including the use of VisualEditor. The
preparation for this project has been happening for quite awhile. The goal
is to have a series of video modules be published in 2016, and to have the
videos produced in such a way that multilingual translation is possible. A
number of Wikipedians have volunteered to assist with translation efforts;
the languages with translation volunteers are currently Spanish, German,
Greek, Czech, Arabic, and Armenian. Anyone who wants to volunteer for
translation assistance is welcome!

Pine

[1]
https://meta.wikimedia.org/wiki/Grants:IEG/Motivational_and_educational_video_to_introduce_Wikimedia
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Pine W]

Thanks. Perhaps some work on CAPTCHA could happen via a Project grant once
there is a concrete proposal that's agreeable to the participants and WMF?
Pinging Marti to ask about the possibility.

Pine

On Wed, Dec 16, 2015 at 10:46 PM, Dan Garry  wrote:

> Hey Pine,
>
> Responses in-line.
>
> On 9 December 2015 at 22:14, Pine W  wrote:
>
> > Hi, just checking to see if CAPTCHA improvements are likely anytime in
> the
> > near future. I notice that
> > https://phabricator.wikimedia.org/project/board/225/ shows nothing under
> > "Awaiting code review". Is anyone working on this?
>
>
> To the best of my knowledge, nobody is working on the CAPTCHA system right
> now.
>
>
> > If not, what kind of
> > nudge would be necessary to get some resources devoted to CAPTCHA
> > improvements?
> >
>
> The truthful but (presumably) unsatisfying answer is that you'd have to
> convince someone responsible for planning their team's work that working on
> the CAPTCHA is more important than what they had planned. That does not
> seem likely to happen right now.
>
> Dan
>
> --
> Dan Garry
> Lead Product Manager, Discovery
> 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] [Wikimedia-l] [Wmfall] Community Wishlist Survey: Top 10 wishes!

[Pine W]

Thank you Danny & Company!

Pine

On Wed, Dec 16, 2015 at 12:22 PM, Toby Negrin  wrote:

> No one asked for 10 more wishes? :)
>
> Thanks Danny and the Community Tech team. This is a great model for working
> with our Communities.
>
> -Toby
>
> On Wed, Dec 16, 2015 at 12:18 PM, Nirzar Pangarkar <
> npangar...@wikimedia.org
> > wrote:
>
> > It's really cool to see community wish list coming together!
> >
> > > We're going to talk with the other Wikimedia product teams, to see if
> > they can take on some of the ideas the the community has expressed
> interest
> > in.
> >
> > +1
> >
> > On Thu, Dec 17, 2015 at 1:42 AM, Danny Horn  wrote:
> >
> >> Hi everyone,
> >>
> >> I'm happy to announce that the Community Tech team's Community Wishlist
> >> Survey has concluded, and we're able to announce the top 10 wishes!
> >>
> >> 634 people participated in the survey, where they proposed, discussed
> and
> >> voted on 107 ideas. There was a two-week period in November to submit
> and
> >> endorse proposals, followed by two weeks of voting. The top 10 proposals
> >> with the most support votes now become the Community Tech team's
> backlog of
> >> projects to evaluate and address.
> >>
> >> And here's the top 10:
> >>
> >> #1. Migrate dead links to the Wayback Machine  (111 support votes)
> >> #2. Improved diff compare screen  (104)
> >> #3. Central global repository for templates, gadgets and Lua modules
> (87)
> >> #4. Cross-wiki watchlist  (84)
> >> #4. Numerical sorting in categories  (84)
> >> #6. Allow categories in Commons in all languages  (78)
> >> #7. Pageview Stats tool  (70)
> >> #8. Global cross-wiki user talk page  (66)
> >> #9. Improve the "copy and paste detection" bot  (63)
> >> #10. Add a user watchlist  (62)
> >>
> >> You can see the whole list here, with links to all the proposals and
> >> Phabricator tickets:
> >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
> >>
> >> So what happens now?
> >>
> >> Over the next couple weeks, Community Tech will do a preliminary
> >> assessment on the top 10, and start figuring out what's involved. We
> need
> >> to have a clear definition of the problem and proposed solution, and
> begin
> >> to understand the technical, design and community challenges for each
> one.
> >>
> >> Some wishes in the top 10 seem relatively straightforward, and we'll be
> >> able to dig in and start working on them in the new year. Some wishes
> are
> >> going to need a lot of investigation and discussion with other
> developers,
> >> product teams, designers and community members. There may be some that
> are
> >> just too big or too hard to do at all.
> >>
> >> Our analysis will look at the following factors:
> >>
> >> * SUPPORT: Overall support for the proposal, including the discussions
> on
> >> the survey page. This will take the neutral and oppose votes into
> account.
> >> Some of these ideas also have a rich history of discussions on-wiki and
> in
> >> bug tickets. For some wishes, we'll need more community discussion to
> help
> >> define the problem and agree on proposed solutions.
> >>
> >> * FEASIBILITY: How much work is involved, including existing blockers
> and
> >> dependencies.
> >>
> >> * IMPACT: Evaluating how many projects and contributors will benefit,
> >> whether it's a long-lasting solution or a temporary fix, and the
> >> improvement in contributors' overall productivity and happiness.
> >>
> >> * RISK: Potential drawbacks, conflicts with other developers' work, and
> >> negative effects on any group of contributors.
> >>
> >> Our plan for 2016 is to complete as many of the top 10 wishes as we can.
> >> For the wishes in the top 10 that we can't complete, we're responsible
> for
> >> investigating them fully and reporting back on the analysis.
> >>
> >> So there's going to be a series of checkpoints through the year, where
> >> we'll present the current status of the top 10 wishes. The first will
> be at
> >> the Wikimedia Developer Summit in the first week of January. We're
> planning
> >> to talk about the preliminary assessment there, and then share it more
> >> widely.
> >>
> >> If you're eager to follow the whole process as we go along, we'll be
> >> documenting and keeping notes in two places:
> >>
> >> On Meta: 2015 Community Wishlist Survey/Top 10:
> >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10
> >>
> >> On Phabricator: Community Wishlist Survey board:
> >> https://phabricator.wikimedia.org/tag/community-wishlist-survey/
> >>
> >> Finally: What about the other 97 proposals?
> >>
> >> There were a lot of good and important proposals that didn't happen to
> >> get quite as many support votes, and I'm sure everybody has at least one
> >> that they were rooting for. Again, the whole list is here:
> >>
> >> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
> >>
> >> We're going to talk with the other Wikimedia product teams, to see if
> >> they can take on some of the ideas the the 

Re: [Wikitech-l] Interactive graphs & charts are now live

[Pine W]

Nice graphs (:

On Mon, Dec 14, 2015 at 7:28 PM, Yuri Astrakhan 
wrote:

> The  tag has just been upgraded to Vega 2.0, adding interactivity
> support.  See live examples here
> .
>
> Vega 1.0 is still available, but it is obsolete.  Please migrate all your
> graphs to the new system so we can turn 1.0 off. See how to migrate:
> https://github.com/vega/vega/wiki/Upgrading-to-2.0
>
> Unless the graph definition contains a "version" value, the default is
> still 1. After I tag all existing graphs, I will switch the default to
> version 2.
>
> See Vega main page for more: http://vega.github.io/vega/
> ___
> 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] Appreciation thread, 2015

[Pine W]

I could name a lot of individuals. I'll name these in particular: Peaceray,
Bluerasberry, Siko, Rory, and the now-departed Gayle and Philippe. I'm
grateful for them.

Pine

On Sat, Dec 5, 2015 at 12:25 AM, Legoktm 
wrote:

> Hi,
>
> It's been a while since we had one of these, and 2015 has been a very
> busy year! :-)
>
> I'll quote Sumana from last time:
>
> > How about a little email thread for us to say nice things about each
> > other?  Rules: be kind, thank someone, and say why you're thanking
> > them.
> > [If you don't get thanked and you feel mopey, email me and I'll
> > comfort you. :-)]
>
>
> I'll start off with thank yous to:
> * Addshore, for his awesome work on CatWatch and help with recent
> ExtensionDistributor improvements
> * YuviPanda, for coming up with unique and useful tools for Wikimedians,
> and then following through and building them
> * S Page, for consistently nagging me and other developers to improve
> documentation
>
> -- Legoktm
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Pine W]

Hi, just checking to see if CAPTCHA improvements are likely anytime in the
near future. I notice that
https://phabricator.wikimedia.org/project/board/225/ shows nothing under
"Awaiting code review". Is anyone working on this? If not, what kind of
nudge would be necessary to get some resources devoted to CAPTCHA
improvements?

Thanks,
Pine

On Tue, Aug 25, 2015 at 6:48 PM, Brian Wolff  wrote:

> On 8/25/15, Dan Garry  wrote:
> > On 19 August 2015 at 23:06, Matthew Flaschen 
> > wrote:
> >>
> >> I agree this is an important issue.  It just isn't resourced right now
> by
> >> the WMF, as far as I know.
> >>
> >
> > Indeed. There have been numerous discussions about the captcha on this
> > mailing list over the past few years, but no progress because this issue
> > just isn't being worked on by anyone.
> >
> > Dan
> >
>
> Well there's that, but its also because its very unclear what "we"
> actually want and how we would get there.
>
> Make captchas not suck, well a great goal, is not an action plan in itself.
>
> --
> -bawolff
>
> ___
> 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 Announcements] Wikimedia Foundation IEG program will fund 14 community-led projects

[Pine W]

Forwarding good news for a wide variety of domains including GLAM,
research, education, maps, language tools, outreach, and more.

Pine

On Fri, Dec 4, 2015 at 4:58 PM, Marti Johnson 
wrote:

> Hi all,
>
> In the latest round of Individual Engagement Grants
> , 29 eligible proposals were
> submitted for review. The committee recommended 14 for funding, with 19
> grantees selected to receive $83,113 overall.  WMF has now approved all
> 14 grants.  Here’s what we’re funding.[1]
>
> Tools - 7 projects funded
>
> * Batch Uploader for small GLAM projects
> 
> :
> This project will create a simple batch content upload tool in order to
> address the needs of smaller GLAM institutions who may not have the
> necessary resources, including budget, time, or staff expertise, to operate
> the existing tools used by larger galleries, libraries, archives, and
> museums.[2]
>
> * Pan Scandinavian Machine Assisted Content Translation
> 
> :
> Using Apertium, an open-source machine translation platform, this project
> will create translation data for closely-related languages Swedish, Danish
> and Norwegian (Bokmål and Nynorsk) for use in Content Translation, an
> on-wiki translation tool.[3]
>
> * StrepHit: Wikidata Statements Validation via Reference
> 
> :
> Using natural language processing, this project will take online content
> from a selection of (non-Wikimedia) websites and documents and then
> automatically convert the raw text into references to external sources
> thereby verifying the data provided in existing Wikidata statements.[4]
>
> * Wikimaps Warper 2.0
> :
> This project will focus on improvements to Map Warper, an open-source tool
> used for digitally aligning and overlaying historical maps, in order to
> make the software more accessible to Wikimedians and better integrated with
> Wikimedia projects.[5]
>
> * Wiki Needs Pictures
> :
> By centralizing multiple sources of data including local templates,
> category labels, and Wikidata item properties in one application, this
> project will create a coordinated image request system with a
> mobile-friendly map-based interface that allows contributors to easily
> discover where there is demand from Wikimedia projects for specific
> images.[6]
>
> * Semi-automatically generate Categories for Vietnamese Wikipedia
> 
> :
> By implementing natural language processing patterns, this project aims to
> create and apply English Wikipedia category structures to Vietnamese
> Wikipedia with the help of the community to evaluate and standardize the
> naming convention process.[7]
>
> * Proofreading semi-automatically the Catalan Wikipedia with LanguageTool
> 
> :
> Using the open source program LanguageTool, this project will supervise
> the analysis of content, document common grammar errors, and develop bots
> and scripts to replicate their corresponding edits in Catalan Wikipedia.
> [8]
>
> Offline Outreach & Partnership - 5 projects funded
>
> * Editing Maithili Wikipedia
> :
> This project will deliver a series of in-person training sessions to
> students in Nepal’s Satpari District in order to create and nurture an
> active group of editors on Maithili-language Wikipedia.[9]
>
> * Increase Awareness of and Participation in Indic Language Wikipedias in
> Colorado
> 
> :
> Small group instruction and training in native language typing in multiple
> Indic scripts are the focus of this project which seeks to eliminate some
> of the barriers preventing the Indian diaspora community of Colorado
> Springs, CO from editing on Marathi, Gujarati, Hindi,Telugu, and Tamil
> Wikipedias.[10]
>
> * Motivational and educational video to introduce Wikimedia Video
> 
> :
> This project will create a modular series of instructional videos that can
> be updated and translated as needed, and that can be used to successfully
> onboard new editors en masse, for example, at edit-a-thons and other events
> where it is not possible to have the involvement of experienced
> Wikimedians.[11]
>
> * Wikitherapy 

Re: [Wikitech-l] Introducing WikiToLearn to developers

[Pine W]

Could we meet on Thursday, 3 December at 10 AM PST / 7PM CEST, or Monday, 7
December at 10 AM PST / 7PM CEST?

I'm fine with this being an open "office hour"-like environment where
anyone can join the conversation on Hangouts. I'm wondering if staff from
the Wiki Ed Foundation like LiAnna would be interested, and/or staff from
WMF Education like Tighe or Anna.

Pine

On Fri, Nov 27, 2015 at 10:59 PM, Riccardo Iaconelli 
wrote:

> On Friday, November 27, 2015 04:15:09 PM Pine W wrote:
> > This sounds like a wonderful project for the Wikimedia universe. It also
> > aligns with the interests of the education interests of multiple US
> > affiliates. Would you be able to set up a Hangout meeting with some of us
> > (me and whoever else is interested) during the next few weeks? I wouls
> like
> > to learn more about this project!
>
> Hi Pine,
>
> of course, I'd be glad to!
> I live in the CEST timezone, and I am free most of next week. The first
> days
> are better though, since later on I will be commuting Milan-Geneva. Pick a
> day
> and we'll try to make it work. :-)
>
> If next week is better, fine with me.
>
> Bye,
> -Riccardo
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Peer-to-peer sharing of the content of Wikipedia through WebRTC

[Pine W]

Thanks for this initiative.

I think that concerns at the moment would be in the domains of privacy,
security, lack of WMF analytics intstrumentation, and WMF fundraising
limitations.

That said, looking in the longer term, a number of us in the community are
interested in decreasing our dependencies on the Wikimedia Foundation as
insurance against possible catastrophes and as a backup plan in case of
another significant WMF dispute with the community. It might be worth
exploring the options for setting up Wikipedia on infrastructure outside of
WMF. I would be interested in talking with you to discuss this further;
please let me know if you have time for a Hangout session in early to mid
December.

Thank you for your interest!
Pine
On Nov 27, 2015 10:50 PM, "Yeongjin Jang" 
wrote:

>
> Hi,
>
> I am Yeongjin Jang, a Ph.D. Student at Georgia Tech.
>
> In our lab (SSLab, https://sslab.gtisc.gatech.edu/),
> we are working on a project called B2BWiki,
> which enables users to share the contents of Wikipedia through WebRTC
> (peer-to-peer sharing).
>
> Website is at here: http://b2bwiki.cc.gatech.edu/
>
> The project aims to help Wikipedia by donating computing resources
> from the community; users can donate their traffic (by P2P communication)
> and storage (indexedDB) to reduce the load of Wikipedia servers.
> For larger organizations, e.g. schools or companies that
> have many local users, they can donate a mirror server
> similar to GNU FTP servers, which can bootstrap peer sharing.
>
>
> Potential benefits that we think of are following.
> 1) Users can easily donate their resources to the community.
> Just visit the website.
>
> 2) Users can get performance benefit if a page is loaded from
> multiple local peers / local mirror (page load time got faster!).
>
> 3) Wikipedia can reduce its server workload, network traffic, etc.
>
> 4) Local network operators can reduce network traffic transit
> (e.g. cost that is caused by delivering the traffic to the outside).
>
>
> While we are working on enhancing the implementation,
> we would like to ask the opinions from actual developers of Wikipedia.
> For example, we want to know whether our direction is correct or not
> (will it actually reduce the load?), or if there are some other concerns
> that we missed, that can potentially prevent this system from
> working as intended. We really want to do somewhat meaningful work
> that actually helps run Wikipedia!
>
> Please feel free to give as any suggestions, comments, etc.
> If you want to express your opinion privately,
> please contact ss...@cc.gatech.edu.
>
> Thanks,
>
> --- Appendix ---
>
> I added some detailed information about B2BWiki in the following.
>
> # Accessing data
> When accessing a page on B2BWiki, the browser will query peers first.
> 1) If there exist peers that hold the contents, peer to peer download
> happens.
> 2) otherwise, if there is no peer, client will download the content
> from the mirror server.
> 3) If mirror server does not have the content, it downloads from
> Wikipedia server (1 access per first download, and update).
>
>
> # Peer lookup
> To enable content lookup for peers,
> we manage a lookup server that holds a page_name-to-peer map.
> A client (a user's browser) can query the list of peers that
> currently hold the content, and select the peer by its freshness
> (has hash/timestamp of the content,
> has top 2 octet of IP address
> (figuring out whether it is local peer or not), etc.
>
>
> # Update, and integrity check
> Mirror server updates its content per each day
> (can be configured to update per each hour, etc).
> Update check is done by using If-Modified-Since header from Wikipedia
> server.
> On retrieving the content from Wikipedia, the mirror server stamps a
> timestamp
> and sha1 checksum, to ensure the freshness of data and its integrity.
> When clients lookup and download the content from the peers,
> client will compare the sha1 checksum of data
> with the checksum from lookup server.
>
> In this settings, users can get older data
> (they can configure how to tolerate the freshness of data,
> e.g. 1day older, 3day, 1 week older, etc.), and
> the integrity is guaranteed by mirror/lookup server.
>
>
> More detailed information can be obtained from the following website.
>
> http://goo.gl/pSNrjR
> (URL redirects to SSLab@gatech website)
>
> Please feel free to give as any suggestions, comments, etc.
>
> Thanks,
> --
> Yeongjin Jang
>
>
> ___
> 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] Introducing WikiToLearn to developers

[Pine W]

This sounds like a wonderful project for the Wikimedia universe. It also
aligns with the interests of the education interests of multiple US
affiliates. Would you be able to set up a Hangout meeting with some of us
(me and whoever else is interested) during the next few weeks? I wouls like
to learn more about this project!

Pine
On Nov 27, 2015 5:22 AM, "Riccardo Iaconelli"  wrote:

> Hi all,
>
> I would like to introduce to the Wikimedia community WikiToLearn, a FOSS
> project of which I am a participant and which is lately getting a lot of
> contributions and momentum.
>
> It is a KDE project sponsored (among the others) by Wikimedia Italy and
> recently joined by institutions such as HEP Software Foundation (CERN,
> Fermilab, Princeton...) or Universities such as University of Pisa and
> Milano-
> Bicocca. These institutions are already populating the website with
> content.
>
> We aim to provide a platform where learners and teachers can complete,
> refine
> and re-assemble lecture notes in order to create free, collaborative and
> accessible textbooks, tailored precisely to their needs.
>
> Although the project is quite young (only a few months old), it is already
> growing in allure at an unexpected rate. Thanks to this we are now
> counting on
> nearly 40 developers, and growing (including content developers).
>
> We are different from Wikipedia and other WMF projects in several ways,
> and in
> a sense, complementary. Our focus is on creating complete textbooks (and
> not
> encyclopedic articles), drawing from a professor’s or a student’s own
> notes,
> either existing or that have to be written down.
>
> We also have a strong focus on offline use: all the content of WikiToLearn
> should be easily printable by any student for offline use and serious
> studying.
>
> Besides a good team for content development, we can count on a small but
> motivated team of developers, and we would like to improve communication
> with
> upstream (a.k.a. you ;-) ), because we found ourselves developing a few
> features which could probably be made available to the general public, with
> some generalization and polishing. ;-)
>
> Is this a right place to start such a discussion?
>
> We would like to help as much as we can, but we might need some mentoring
> in
> how to best approach MediaWiki development, as many of us are relatively
> new
> to OSS/Web development.
>
> Bye,
> -Riccardo
>
>
> ___
> 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] Design thinking at IBM

[Pine W]

Interesting read:
http://www.seattletimes.com/business/ibms-design-centered-strategy-to-set-free-the-squares/

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

Re: [Wikitech-l] Please welcome Joe Matazzoni as Product Manager, Collaboration

[Pine W]

My impression is that Lila has taken an interest in Flow, partially
influenced by the discussions on her talk page on Meta. I do hope that Joe
will have the time for a careful review of the situation with Flow so that
we can get some kind of resolution and then move on to other matters for
collaboration improvements such as enhancements to Echo and cross-wiki
collaboration tools.

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

[Wikitech-l] Because visualizations are cool

[Pine W]

These resources may give ideas to people who create project proposals or
any of several kinds of reports.

http://www.datavizcatalogue.com/index.html

http://survey.timeviz.net/

Have fun exploring,

Pine

P.S. In the multimedia domain, I'd like to have the ability to add
interactive visualizations to Wikipedia and its sister projects. For
example, imagine how engaging it would be to have interactive phylogenetic
trees that allow the user to zoom in and out and see images of species.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Please welcome Joe Matazzoni as Product Manager, Collaboration

[Pine W]

Good, more people with video experience and from WSJ. (:

I personally think we should look into poaching more talent from WSJ. I
like their infographics, and we seem to have a very capable new hire in
Comms who also worked for WSJ.

Welcome, Joe.

Pine

On Mon, Nov 23, 2015 at 12:00 PM, James Forrester 
wrote:

> Everyone,
>
> It's my pleasure to welcome Joe Matazzoni to the Editing department as the
> new product manager for the Collaboration team from today. Joe will help
> the team develop aligned with the needs of our editors, prioritizing and
> shaping the improvements we're making to notifications, watchlists, change
> tracking, discussions and more. He replaces Danny Horn, who is now helping
> the Community Tech team.
>
> Joe has had a long career in digital publishing and media, particularly in
> public broadcasting, first at NPR, where he helped rebuild the Web site and
> then founded the Arts & Life section, and more recently at KQED, where he
> created an Emmy-winning arts video team. Joe has a master’s degree in
> interactive telecommunications from NYU and a background in UX design. He
> was the director of UX at the Wall Street Journal, where he helped lead a
> complete site and CMS redesign and relaunch.
>
> After many years in New York and DC, Joe is delighted to be back in his
> native Bay Area. He's a big reader, enjoys biking and swimming and likes to
> dabble in the kitchen. He will be based in the office, which he plans to
> commute to via the ferry from Marin, where he lives with his wife and
> 11-year-old son. Joe will be on IRC and of course on-wiki as
> [[User:JMatazzoni
> (WMF) ]].
>
> Welcome, Joe!
>
> Yours,
> --
> James D. Forrester
> Lead Product Manager, Editing
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.org | @jdforrester
> ___
> 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] WIkigenes tools

[Pine W]

Just noticed that Wikigenes has a couple of interesting tools. There's a
way for editors to highlight the contributions in an article that were made
by specific users, and also a way to rate edits on a scale of 0 to 4. I'm
unsure how valuable the scale would be in light of Aaron's ongoing work
about edit value and also in light of our "thanks" feature, but I'd like
the ability to highlight contributions on a page by individual authors. Is
there any possibility of bringing that tool over to Wikimedia sites?

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

Re: [Wikitech-l] [Wikitech-ambassadors] Update about on-going work on Notifications, especially cross-wiki notifications

[Pine W]

Yes, we lack efficient and effective ways of cross-listing conversations,
which might be another use case for which the Collaboration team might
engineer some solutions, possibly involving Echo and/or Flow. (:

On Sun, Nov 15, 2015 at 4:13 PM, Rachel diCerbo 
wrote:

> I wonder if the most effective place to have and follow conversations about
> a product are on that product's page, rather than Lila's Talk page or
> WM-L.
>
> The main page to talk about Echo notifications overall is here:
> https://www.mediawiki.org/wiki/Talk:Echo_(Notifications)
>
> A particular problem is that that page is Flowized and I know that many
> users prefer original Talk pages - but the RfC page  allows for Talk page
> format. It's here:
>
> https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Cross-wiki_notifications
>
>
> On Sun, Nov 15, 2015 at 2:41 PM, Brian Wolff  wrote:
>
> > On Sunday, November 15, 2015, Pine W  wrote:
> > > The discussion about Flothat I referened is currently happening on
> Lila's
> > > talk page on Meta. Would you like to join the conversation there? The
> > > discussion there might get more staff attention than Wikimedia-l. (I
> hear
> > a
> > > number of staff avoid Wikimedia-l because they find the tone to be
> > hostile
> > > and/or because the volume is more than they can handle.)
> >
> > You really think the staff that dont follow wikimedia-l are going to
> follow
> > lila's talk page?
> >
> > --bawolff
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
>
> Rachel diCerbo
> Director of Community Engagement (Product)
> Wikimedia Foundation
> Rdicerb (WMF) <https://meta.wikimedia.org/wiki/User_talk:Rdicerb_%28WMF%29
> >
> @a_rachel <https://twitter.com/a_rachel>
> ___
> 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] [Wikitech-ambassadors] Update about on-going work on Notifications, especially cross-wiki notifications

[Pine W]

It's worth a try. In any case the person who seems to be making the
decisions is Lila, and since a conversation started on her talk page it
seems reasonable to me to keep it there. She can move it if she wishes.

Pine

On Sun, Nov 15, 2015 at 2:41 PM, Brian Wolff  wrote:

> On Sunday, November 15, 2015, Pine W  wrote:
> > The discussion about Flothat I referened is currently happening on Lila's
> > talk page on Meta. Would you like to join the conversation there? The
> > discussion there might get more staff attention than Wikimedia-l. (I hear
> a
> > number of staff avoid Wikimedia-l because they find the tone to be
> hostile
> > and/or because the volume is more than they can handle.)
>
> You really think the staff that dont follow wikimedia-l are going to follow
> lila's talk page?
>
> --bawolff
> ___
> 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] Update about on-going work on Notifications, especially cross-wiki notifications

[Pine W]

The discussion about Flow that I referened is currently happening on Lila's
talk page on Meta. Would you like to join the conversation there? The
discussion there might get more staff attention than Wikimedia-l. (I hear a
number of staff avoid Wikimedia-l because they find the tone to be hostile
and/or because the volume is more than they can handle.)

By the way, staff reasoning may be quite different than mine. You may want
to ask Lila about her current thinking. It would also be nice if Wes would
engage in public.

Thanks,

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

Re: [Wikitech-l] Update about on-going work on Notifications, especially cross-wiki notifications

[Pine W]

Hi MZMcBride,

The hypothetical here is that I have a binary choice between Echo and Flow.
In practice it's possible to develop them in parallel. With the
hypothetical in mind, I'll outline why I would prioritize Echo.

My thinking is that Echo is used widely on many, many wikis and is helpful
to users of all skill levels. It must be years since I've heard someone say
that they find the nature of Echo to be problematic. By contrast, the
reception to Flow is more mixed. Also, as some of us are discussing with
Lila, it may be feasible to extend VE  to talk pages and/or give some love
to the wikimarkup editor at less expense and with less disruption than the
expense and disruption involved with converting talk pages to Flow pages.

From a communications persoective, I asked recently for clarification on
the status of Flow and no one from WMF answered my question. If there is so
much uncertainty or disorganization with respect to Flow that users don't
get answers to questions that are asked in prominent venues, that makes me
wonder all the more what is happening, and therefore inclined to oppose
investing more resources in a black box until community questions are
answred.

Flow has its supporters and I think that keeping it maintained and healthy
on wikis where the communities like it is probably wise. Given the choice
of investing more resources into further development of a product that has
mixed reviews, is used on only some wikis, and about which community
questions aren't answered, seems questionable to me when investing in a
well-accepted and widely-used tool (Echo) is an alternative.

Pine
On Nov 14, 2015 9:11 PM, "MZMcBride"  wrote:

> Pine W wrote:
> >Agreed. If I had a binary choice between investing in Echo and investing
> >in Flow, I would be inclined to choose Echo.
>
> Can you please elaborate on why you would prioritize Echo over Flow? The
> Wikimedia Foundation has made the same decision and it's mind-boggling to
> me. I'd really like some greater insight into the thought process here.
>
> MZMcBride
>
>
>
> ___
> 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] Update about on-going work on Notifications, especially cross-wiki notifications

[Pine W]

Agreed. If I had a binary choice between investing in Echo and investing in
Flow, I would be inclined to choose Echo.

Pine
On Nov 14, 2015 7:08 AM, "Derk-Jan Hartman" 
wrote:

> Thank goodness. Finally we might be able to start fully building out the
> promise of powerful, targeted and appropriate messaging that Echo always
> was the the kick off for.
> I especially like the acknowledgment of the 'volume knob'. Balancing the
> 'noise' of messaging is going to be really important.
>
> I've always been a big proponent (Nick knows this all to well :D ) of
> investing in this area, seeing it as one of the few places of investment
> that can bring our communication between community members, but also the
> communication between foundation and editors to a level that is required to
> sustain and improve what we have right now, but most definitely to take our
> communities into the future. I predict big returns on improving this area.
> Awesomeness.
>
> DJ
>
> > On 13 nov. 2015, at 23:41, Nick Wilson (Quiddity) 
> wrote:
> >
> > Hi, this is an update on the work we in the Collaboration team are
> > doing. Our focus is on cross-wiki notifications and other back-end
> > improvements to that system.
> >
> > Our long-term goals are to make various improvements to the Notification
> system.
> >
> > Notifications are at the core of many different on-wiki activities.
> > Making notifications easy to find and use can help those processes. We
> > are focusing our immediate plans on supporting cross-wiki
> > notifications. These will help editors stay informed about the changes
> > they care about on every Wikimedia project on which they work. This is
> > especially important for the editors who work on more than one wiki.
> > Examples include if you upload to Commons, curate on Wikidata, or edit
> > in two or more languages.
> >
> > The team has spent the last few weeks researching the existing and
> > proposed features. This has included examining existing tools such as
> > Crosswatch. We've been considering the problems of:
> >
> > * technical performance (scaling the requests across 800+ wikis),
> > * user preferences (both existing and desired),
> > * user interface design possibilities (how it should work),
> > * how to release an initial, user-testable version for feedback and
> > improvement, and
> > * how to measure the impact of the project (reducing the time it takes
> > to process a notification).
> >
> > We are also doing user research via 1-on-1 interviews. In these we ask
> > active editors about their current notification usage and pain-points.
> > Using a prototype we are evolving, we get feedback on directions to
> > take the design.
> >
> > == Details and further reading ==
> > You can read more about the technical details at:
> >
> https://www.mediawiki.org/wiki/Requests_for_comment/Cross-wiki_notifications
> > .
> >
> > Some of the new backend improvements to Echo:
> > https://phabricator.wikimedia.org/T107823 ("Rewrite
> > EchoNotificationFormatter") and linked tasks.
> >
> > User preference options are:
> > * https://phabricator.wikimedia.org/T117670 ("Define Cross-wiki
> > Notifications settings")
> >
> > User interface design possibilities cover several questions. For
> > example, how should cross-wiki notifications look within the pop-up?
> > How and when should we add enhancements to the Special:Notifications
> > page to filter things? We are drafting and discussing these in:
> >
> > * https://phabricator.wikimedia.org/T114357 (Clarifications to the
> > currently confusing "primary/secondary" link, and proposed future
> > enhancements)
> > * https://phabricator.wikimedia.org/T114356 (Bundled notifications)
> > * https://phabricator.wikimedia.org/T115264 (Controlling notification
> > 'volume' based on the type or location)
> > * https://phabricator.wikimedia.org/T115845 (Clearer use of the
> > notification badges (coloured number in personal toolbar))
> > * https://phabricator.wikimedia.org/T115316 (Better organization of
> > the Special:Notifications page)
> >
> > Note: Most of these are not part of the cross-wiki notifications
> > feature. We won't for sure roll all these out together with the main
> > change.
> >
> > We started user research at https://phabricator.wikimedia.org/T114086
> > and it continues at https://phabricator.wikimedia.org/T116741 . (Note:
> > You can sign-up as a volunteer at https://wikimedia.org/research .)
> >
> > A user-testable release is still just in planning. We decided on a
> > Beta Feature on each wiki as the most scalable and least confusing of
> > all the do-able options. Read our plans in
> > https://phabricator.wikimedia.org/T114237 ("Present cross-wiki
> > notifications as a beta feature to users"). This will help users to
> > try the feature anytime, disabling it if it interferes with their work
> > in some context, and easily suggest how the tool could be improved.
> >
> > There is no system for users having or setting cross-wiki preferences.
> > Waiting t

Re: [Wikitech-l] Summit proposal: Turning the Table of Contents into a discrete object

[Pine W]

I lean in favor of this concept. Can someone from Performance comment in
Phabricator?

Thanks!
Pine
On Nov 9, 2015 7:26 PM, "Isarra Yos"  wrote:

> Hi! I would like to turn the mw ToC into a discrete object within the
> codebase. Write a ToC class and pull all the random building parts out of
> the parser and five levels of pageoutput, and make it stop messing up the
> page caching and stuff. Make this class a thing, separate from the content
> itself, that can appear on the page or be toggled or messed with or added
> to or moved or whatever by extensions.
>
> I have a proposal about this for the developers summit which is about as
> specific: https://phabricator.wikimedia.org/T114057
>
> Please come discuss. Would this affect what you're doing in a good or bad
> way? What do we know of that this should support at present? What would we,
> as developers or whatever the buckets, want out of it?
>
> Also is this the sort of thing you normally use an RfC for? I'm a designer
> so I'm just asking questions and soliciting stories and all that before I
> go trying to do designy stuff on the mw backend, but maybe that's not
> really the way to do this here.
>
> -I
>
> ___
> 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] Deepcat Gadget: intersection and subcategory search on Wikipedia and Commons

[Pine W]

Kasis, this sounds very interesting! Cross-posting to the Discovery mailing
list.

Pine
On Nov 3, 2015 8:39 AM, "Kasia Odrozek"  wrote:

> Hello all,
>
> I am happy to announce that the Software-Development Team at WMDE (TCB)
> developed the so called “Deepcat” gadget [1] that is now ready to use not
> only in German wikis but also internationally.
>
> The possibility for intersection and subcategory search was one of the
> top-wishes from the TOP20 of the Germany Community Technical Wishlist [2].
> DeepCat acts as an interface between a graph database and MediaWiki's
> search engine. The Wiki's category structure is stored via their page-ids
> in the graph database while the Gadget does the translation of the search
> string, retrieves the information from the database and sends it to the
> search engine. Tool developers interested in exploring possibilities for
> using the CatGraph database can find more information on the respective
> infopage [3] or can approach us directly.
>
> The Deepcat gadget allows to go deeper in the category search and generates
> results not only for a certain category but also for its subcategories.
> Furthermore, it supports intersection search (among others: searching for
> articles or pictures that are in two different categories e.g. “Art” and
> “Technology”). The gadget works on Wikipedia, on Wikimedia Commons, as well
> as in many other wikis [4]. For performance and technical reasons there is
> a search limitation of 15 categories in depth and 70 categories in total
> that the gadget can search through (you will see a hint about that while
> using the gadget). The gadget doesn’t load on mobile devices however once
> you switch to desktop-view, it should work as usual.
>
> The gadget can be used via typing the keyword “deepcat:” into the regular
> search field. An instruction how to install Deepcat and a detailed
> description of its functionality can be found on its infopage [5]. Bugs can
> be reported on Phabricator [6].
>
> We hope it will serve you well!
>
> Cheers,
> Kasia
>
> [1] https://github.com/wmde/DeepCat-Gadget
> [2]
>
> https://de.wikipedia.org/wiki/Wikipedia:Umfragen/Technische_W%C3%BCnsche/Top_20#.E2.80.9ECatScan-Funktionalit.C3.A4t.E2.80.9C_in_die_Software_integrieren
> [3] https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph
> [4] https://tools.wmflabs.org/cgstat
> [5] https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph/Deepcat
> [6]
>
> https://phabricator.wikimedia.org/maniphest/task/create/?projects=DeepCat-Gadget
>
>
> --
> Kasia Odrozek
> Product Manager
> Software Development and Engineering
>
> Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
> Tel. +49 (030) 219 158 260
> Mobil: +49 151 46752534
>
> http://wikimedia.de 
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
> der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
> Körperschaften I Berlin, Steuernummer 27/681/51985.
> ___
> 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] Fiscal Year Q2 Engineering goals

[Pine W]

Hi Tilman,

After rereading that email from September, I'm still a little hazy on what
the plan is.

I see that "Starting in October, Flow will not be in active development".
But rollout of Flow will continue on an opt-in basis, I see.

I'm hazy on what is happening with regard to the ex-Flow team's focus on
helping with improvements  to structured workflows; are those workflows
with or without the involvement of Flow, and what are some examples of of
assistance to structured workflows (example: ENWP BASC?) where this team is
likely to try to improve workflows (hopefully done with local consensus)?

Is integration of other tools like Echo still planned for Flow, or has that
already happened?

I have experimented more with VE than Flow and would appreciate some
clarifications WRT what to expect from Flow as well as the other structured
collaboration goals.

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

Re: [Wikitech-l] Fiscal Year Q2 Engineering goals

[Pine W]

Thanks Toby.

Some of the goals for Research and Design Research particularly interest me.

Can you (or someone in Product and Engineering) clarify what is happening
with Flow? I thought that development status had changed to maintenance
only, but then I heard otherwise off-list, and now I see that there is a
Flow-related goal to "Increase access to Flow by deploying and supporting
an opt-in system for it". Deploying it sounds different than putting it
into maintenace-only status. Having Flow be opt-in will probably please
Flow's supporters, and  hopefully will be a nice incremental way to
identify problems with it on a manageable scale, and to allow wikimarkup
users to continue to use that more flexible option. Is the plan to continue
an opt-in rollout and continue to allocate development resources for Flow
beyond minimal maintenance support? Clarification would be appreciated.

(Side note: there are ongoing discussions about Flow on Lila's talk page on
Meta.)

Thanks,
Pine
On Nov 1, 2015 7:01 PM, "Toby Negrin"  wrote:

> Hi Everyone --
>
> A bit late but I wanted to let you know that the Engineering goals for the
> 2d quarter (October to December) of this current Fiscal year are posted on
> Mediawiki.org.
>
> https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals
>
> We'll be more timely in the future. Please reach out to the respective goal
> owner identified in the wiki page for more information.
>
> -Toby
> ___
> 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] Wikidata descriptions to show on mobile web Wikipedias

[Pine W]

Request: for non-urgent, potentially high-impact changes, can notices to
village pumps and mailing lists go out at least 3 weeks in advance to give
the community opportunity to prepare and/or comment? I am not anticipating
that we'll get meaningfully more mobile Web vandalism, but announcing
non-urgent changes like this would be appreciated weeks in advance.

Thanks,
Pine
On Oct 28, 2015 7:51 PM, "Jon Katz"  wrote:

> Hi All,
>
> TLDR: on the mobile web, Wikidata descriptions will appear under article
> titles in search results, nearby and watchlist starting tomorrow afternoon
> (Thu, Oct 29) across projects.  A 'kill switch' has been implemented so
> that this feature can be turned off if necessary.
>
> Background:
> In Q2 of last year, Wikidata descriptions were added to both our official
> apps: iOS and Android and resulted in wonderful qualitative feedback (as
> the discovery team knows, it is hard to define 'success' with search (fewer
> searches, more searches?).  Though moving Wikidata descriptions to search
> on mobile web was planned for Q3 of last year, it has been sitting in beta
> for many months as there was some concern that at scale on the web, it
> might prove to be an incentive to vandalize Wikidata (and article editors
> would not have an obvious, wikipedia way to undo such edits).
>
> Ultimately, we think that anything showing up on Wikipedia should be
> editable ON Wikipedia. Wikidata description editing is something we are
> going to aim for. Given the success of descriptions in search results on
> apps, we would rather move forward with the presentation and work towards a
> goal of editing in-line than to hold up the entire thing based on a fear
> that might not be warranted. In consultation with the Wikidata team, we
> decided to move forward with pushing the feature to stable as long as we
> had the ability to pull the feature back if there were any issues.
>
> We are relying on community feedback to let us know if you have any issues
> or hear from anyone that this is causing problems. Our community liaison
> team will be posting notices on village pumps shortly. Thanks!
>
> Best,
>
> Jon
> WMF Reading Product Lead
> ___
> 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] XSS warning for an image download

[Pine W]

*Here is the 404:*

"404 Not Found

The resource could not be found.

File not found: /v1/AUTH_mw/
wikipedia-commons-local-public.ad/a/ad/Commodore_Grace_M._Hopper,_USN_%20covered%20.jpg
"

*Below is the log from the browser console. It looks like Noscript thinks
that going from commons.wikimedia.org <http://commons.wikimedia.org> to
upload.wikimedia.org <http://upload.wikimedia.org> involves an untrusted
XSS. I can tell Noscript to do what it considers to be an unsafe reload and
it will then load the image properly.*

NS_ERROR_FAILURE: Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsIWebProgress.addProgressListener] browser.xml:546:0
[NoScript InjectionChecker] JavaScript Injection in
///wikipedia/commons/a/ad/Commodore_Grace_M._Hopper,_USN_(covered).jpg
(function anonymous() {
wikipedia/commons/a/ad/Commodore_Grace_M._Hopper,_USN_(covered).jpg /*
COMMENT_TERMINATOR */
DUMMY_EXPR
})
[NoScript InjectionChecker] JavaScript Injection in
///wiki/File:Commodore_Grace_M._Hopper,_USN_(covered).jpg
(function anonymous() {
File:Commodore_Grace_M._Hopper,_USN_(covered).jpg /* COMMENT_TERMINATOR */
DUMMY_EXPR
})
[NoScript XSS] Sanitized suspicious request referer. URL [
https://upload.wikimedia.org/wikipedia/commons/a/ad/Commodore_Grace_M._Hopper%2C_USN_%28covered%29.jpg
(REF:
https://commons.wikimedia.org/wiki/File:Commodore_Grace_M._Hopper,_USN_(covered).jpg)]
requested from [
https://commons.wikimedia.org/wiki/File:Commodore_Grace_M._Hopper,_USN_(covered).jpg].
Sanitized Referrer: [
https://commons.wikimedia.org/wiki/File:Commodore_Grace_M._Hopper,_USN_%20covered%20.jpg
].
[NoScript XSS] Sanitized suspicious request. Original URL [
https://upload.wikimedia.org/wikipedia/commons/a/ad/Commodore_Grace_M._Hopper%2C_USN_%28covered%29.jpg]
requested from [
https://commons.wikimedia.org/wiki/File:Commodore_Grace_M._Hopper,_USN_(covered).jpg].
Sanitized URL: [
https://upload.wikimedia.org/wikipedia/commons/a/ad/Commodore_Grace_M._Hopper,_USN_%20covered%20.jpg#36059408556548644467
].
[NoScript HTTPS] AUTOMATIC SECURE on https://upload.wikimedia.org:
WMF-Last-Access=25-Oct-2015; domain=upload.wikimedia.org; path=/; HttpOnly;
Secure
TypeError: self.urlTooltipLabel is undefined


*Pine*

On Sun, Oct 25, 2015 at 12:01 PM, Brian Wolff  wrote:

> On 10/24/15, Pine W  wrote:
> > When I right-click on the image download link for
> > File:Commodore_Grace_M._Hopper,_USN_(covered).jpg the download I get is
> > only 269 bytes and it contains a 404 error in plaintext even though it's
> a
> > jpg file.
> >
> > When I click on the image preview that's 480x600 pixels, I get an XSS
> > warning from Noscript.
> >
> > All other images download ok for me.
> >
> > Any knowledge of what the issue is with this one file?
> >
> > Thanks,
> > Pine
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> I have a vauge memory of hearing a similar report once before but I
> can't find any report about it. Something about noscript not liking
> brackets in image urls, especially when using media viewer, and
> redirecting the url to something invalid. (Which if true, is
> ultimately noscript's fault for being stupid)
>
> Can you include the exact text of the 404 message (Most importantly,
> is it one of ours), and verify the precise url you're downloading to
> make sure noscript hasn't messed with it?
>
> --
> -bawolff
>
> ___
> 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] XSS warning for an image download

[Pine W]

When I right-click on the image download link for
File:Commodore_Grace_M._Hopper,_USN_(covered).jpg the download I get is
only 269 bytes and it contains a 404 error in plaintext even though it's a
jpg file.

When I click on the image preview that's 480x600 pixels, I get an XSS
warning from Noscript.

All other images download ok for me.

Any knowledge of what the issue is with this one file?

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

Re: [Wikitech-l] Developer Relations Weekly Summary

[Pine W]

Hi Quim,

I'm glad to see the tasks about 3D files in there. Open license 3D files
were a need mentioned at WCONUSA for GLAMs.

There has been a lot of discussion recently about the Education Exension's
problems. Any chance of getting Developer Relations resources in making
that code at least secure and maintainable enough to keep it deployed on
its current wikis in the short term and in order to buy some time for
development of long term solutions?

I want to express moral support for anything related to improving the code
review experience, which seems to be a pinch point in multiple workflows
and I hear is a subject of frequent concern. I would support finding
additional budget resources (preferably through internal transfer rather
than new expenditure) to address this problem if analysis shows that
transferring or adding some resources (maybe 0.5 FTE?) would make a
meaningful difference.

Can you provide a brief update on how the deployment is going of the
Newsletter extension?

Thanks!
Pine
On Oct 22, 2015 3:24 AM, "Quim Gil"  wrote:

> Third edition of the still experimental Developer Relations Weekly Summary.
> This time introducing sections.
>
>
> https://www.mediawiki.org/wiki/Developer_Relations/Weekly_summary#2015-10-22
> Events
>
>- Tech Talk: Introduction to Free and Open Source Licensing at Wikimedia
> on
> 2015-10-23
>17:00 UTC
><
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Introduction+to+Free+and+Open+Source+Licensing+at+Wikimedia&iso=20151023T17&p1=%3A&ah=1
> >,
>by Slaporte (WMF)
> aka Slaporte
>.
>- The Wikimedia Developer Summit 2016
> has 10
>session proposals on track
> >,
>7 missing active discussion, 36 missing expected information.
>- Wikimania 2015 survey results
><
> https://meta.wikimedia.org/wiki/Grants:Evaluation/Case_studies/Wikimania_Mexico_Survey_Results#Direct_products
> >:
>"The majority (*53%*) of Hackathon participants *discussed future work*,
>and the second-highest mentioned accomplishment was *fixing bugs* (*34%*
>)"
>
> Outreach
>
>- Outreachy round 11  >
> has 9 featured project ideas
> and 5
>proposals submitted by candidates
> welcoming
>community feedback. The deadline for submissions is 2015-11-02.
>- Google Code-in 2015
> is coming, and our
>planning has started .
>
> Documentation
>
>- API:Presenting Wikidata knowledge
> is a
>new article for the Web APIs hub
>.
>
> Community health
>
>- The discussion about the Code of Conduct draft
><
> https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft>
> welcomes
>feedback on these points:
>   - "Publication of non-harassing private communication"
>   <
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> >
>(new proposal
>   )
>   - "Project administrators and maintainers have the right and
>   responsibility..."
>   <
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> >
>(rewording proposal
>   )
>   - Finishing the "Report a problem" section
>    (new)
>
> Project management
>
>- Now anybody can join and watch the Operations project
> in
>Phabricator. (Phab:T90491 )
>- Are the Commons ,
>Wikisource , and
>Wiktionary  projects
>in Phabricator useful? (Phab:T111046
>)
>
> Code review
>
>- Gerrit Cleanup Day: lessons learned
> and proposal for a new
>edition  in January 2016.
>- Decide/document whether "controversial" changes should be marked as
>CR-2 in Code Review. (Phab:T115850
>)
>
> Metrics
>
>- Ope

Re: [Wikitech-l] Tools repository

[Pine W]

I like the idea of a tools index. Bob Cummings was looking for some GLAM
tools that IIRC sounded perfectly reasonable but no one seems to know if we
have them.

Pine
On Oct 13, 2015 6:52 PM, "Quim Gil"  wrote:

> On Mon, Oct 12, 2015 at 7:04 PM, Ricordisamoa <
> ricordisa...@openmailbox.org>
> wrote:
>
> > Il 12/10/2015 18:56, Quim Gil ha scritto:
> >
> >>
> >> Interesting. Has there been any discussion about having an authoritative
> >> and well promoted catalog of Wikimedia tools?
> >>
> >
> > Yes.
> > https://lists.wikimedia.org/pipermail/labs-l/2015-March/thread.html#3462
>
>
> After reading the (short) discussion, I think it is worth creating a task
> to assure that at least this idea is not forgotten again in another mailing
> list archive. Ricordisamoa, do you want to create it and associate it at
> lest with the #Developer-Relations project?
>
> I also believe that we need a catalog of tools. Even when some experts in
> our community know or can find what is available and functional, most
> potential users of those tools will have a hard time connecting with them.
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
> ___
> 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] [discovery] WikiConference USA

[Pine W]

Yes, Andrew's talk was quite good. He and I recorded video at some of the
other sessions, including a SWOT analysis and visioning exercise regarding
Wikipedia culture, and a session about video on Wikipedia. Some of the
videos (Andrew's) came out better than others (mine) due to hardware issues
(my camera's video quality is mediocre although some of its stills are
pretty good). Andrew will hopefully post links to the videos after they're
uploaded.

Pine
On Oct 13, 2015 2:55 PM, "Trey Jones"  wrote:

> For those who didn't make it to WikiConference USA, you can watch
> everything that happened in the biggest auditorium on YouTube. (Don't
> forget the settings to play at higher speed—most people don't talk as fast
> as you can listen.)
>
> While it isn't focused on Discovery, I found Andrew Lih's talk to be very
> interesting:
> https://www.youtube.com/watch?v=Gj6U22uJzGM&t=24m30s
>
> Links to the other National Archives recordings are on the schedule:
> http://wikiconferenceusa.org/wiki/2015/Schedule
>
> Other talks were also recorded, but not by the National Archives. I'm sure
> they'll pop up somewhere online eventually.
>
> Aaron Halfaker gave a very cool talk on AI bots that support Wikipedia,
> and discusses a machine learning platform that could support other
> tasks—and though he didn't mention it, I thought of detecting languages,
> detecting gibberish queries (very similar to what they do to find gibberish
> edits), and other things that may be useful to Discovery:
> http://wikiconferenceusa.org/wiki/Submissions:2015/Revscoring:_AI_support_for_Wikipedians
>
> See more on machine learning as a service here:
> https://meta.wikimedia.org/wiki/Objective_Revision_Evaluation_Service
>
> —Trey
>
> Trey Jones
> Software Engineer, Discovery
> Wikimedia Foundation
>
>
> ___
> discovery mailing list
> discov...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/discovery
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Updates on WMF product leadership

[Pine W]

Thank you for the announcement. Congrats to Wes.

Pine
On Oct 8, 2015 8:34 PM, "Lila Tretikov"  wrote:

> All,
>
> I want to share an update about the WMF’s product leadership. As of today,
> Wes Moran has stepped into the role of Vice President of Product. In this
> role, he’ll oversee the Foundation’s product across all audience verticals,
> reporting to me. Please join me in welcoming Wes into this new role.
>
> Wes has more than 17 years of experience in product design and development,
> with expertise in open source communities, user-centered design,
> interaction design, user experience, user research and testing, product
> management, and more. Since joining the Foundation, he led the
> newly-created Discovery team to focus on user needs, transparency, and
> accountability, and worked closely with our colleagues at Wikimedia
> Deutschland on key projects such as Wikidata. He has been an invaluable
> resource as we have continued to recruit for a Chief Technology Officer,
> working with Terry and myself to cover critical leadership
> responsibilities.
>
> With this change, Tomasz Finc, Katie Horn, Toby Negrin, and Trevor Parscal
> will report to Wes. Tomasz will now lead the Discovery team. Tomasz has
> been Director of Discovery and helped build and lead development of this
> new team. He has served in many leadership capacities over his 7 years here
> at the foundation and joined us from Amazon where he worked with the A9
> search team. Please join me in congratulating Wes and Tomasz.
>
> Lila
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> 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] Developer Relations Weekly Summary

[Pine W]

Thanks Quim, I like the summary. Code review is a particular interest of
mine and I'm glad to see some stats mentioned here.

Pine
On Oct 8, 2015 3:03 AM, "Quim Gil"  wrote:

> We are discussing the possibility of maintaining a weekly summary of news
> related to the areas covered by Developer Relations
> : technical
> documentation, events, and community. See Phab:T114224.
> 
>
> We have a number 0 at
> https://www.mediawiki.org/wiki/Developer_Relations/Weekly_summary, pasted
> below for convenience. How can we improve the content and the distribution?
> We welcome your feedback.
>
> 2015-10-08[edit
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&veaction=edit&vesection=1
> >
>  | edit source
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&action=edit§ion=1
> >
> ]
>
>- By the call for participation deadline on October 2, the Wikimedia
>Developer Summit 2016
> had
>   - 52 session proposals
>   <
> https://phabricator.wikimedia.org/tag/wikimedia-developer-summit-2016/>
>presented
>   - 129 people registered, from which 17 request travel sponsorship.
>- Outreachy round 11 
> is
>here. Tony Thomas  is
>the new org admin, and Niharika Kohli
> is secondary org admin
> in
>this round. (T112267) 
>   - 5 project ideas featured, 18 missing mentors, 34 need discussion.
>   You can help at Possible-Tech-Projects workboard
>   . (
>   T112620 )
>- Code of Conduct draft
><
> https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft
> >:
>the second round
><
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> >
> of
>feedback for the first sections ended with mixed results. The open
>discussions will continue in a new round
><
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> >
>.
>- There is a new process to mark inactive software projects
>, aimed to
>highlight stalled repositories without code reviewers or maintainers. (
>T102920 )
>- Creating tasks to clean the code review queue of slow repositories?
>The first task goes for analytics/wikistats. (T113695
>)
>- Google has released a set of Freebase to Wikidata mapping tools
> thanks to an
>internship with Tpt . (
>announcement
><
> https://lists.wikimedia.org/pipermail/wikidata/2015-October/007319.html>
>)
>
> Metrics[edit
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&veaction=edit&vesection=2
> >
>  | edit source
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&action=edit§ion=2
> >
> ]
>
>- Code repositories with slowest code review
>:
>   1. Wikistats
>   <
> https://gerrit.wikimedia.org/r/#/q/project:analytics/wikistats+status:open,n,z
> >:
>   475 days, 5 changesets. (T113695
>   )
>   2. Collection/OfflineContentGenerator/latex renderer
>   <
> https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/Collection/OfflineContentGenerator/latex_renderer,n,z
> >:
>   463 days, 4 changesets.
>   3. EducationProgram
>   <
> https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/EducationProgram,n,z
> >:
>   459 days, 2 changesets.
>   4. BookManagerv2
>   <
> https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BookManagerv2,n,z
> >:
>   443 days, 21 changesets.
>   5. BayesianFilter
>   <
> https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/BayesianFilter,n,z
> >:
>   386 days, 1 changeset.
>
> Jul-Sep 2015[edit
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&veaction=edit&vesection=3
> >
>  | edit source
> <
> https://www.mediawiki.org/w/index.php?title=Developer_Relations/Weekly_summary&action=edit§ion=3
> >
> ]
>
> Tech community metrics
>  presented
> at the Community Engagement quarterly review
> :
>
> Code review
>
>   

Re: [Wikitech-l] Technical expertise needed for Individual Engagement Grant proposals!

[Pine W]

Thanks Siko.

Also, @Brian: the last I heard is that the Committee would like more
members with software development experience. If that sounds like something
you would want to do, I think that the committee coordinators or Marti
would like to hear from you about joining IEGCom for the next round
(although it may or may not be called IEG any more as it joins up with the
new grants categories; the last I heard is that the new category will be
"Project Grants" and they will have some nice new features).

Pine
On Oct 7, 2015 10:06 AM, "Siko Bouterse"  wrote:

> Useful points as always, thanks! Marti and Quim have partnered on improving
> processes for technical IEG proposals and there's no doubt still room for
> improvement, but always good to have feedback as they're building changes
> into each round. Having separate application templates for different kinds
> of proposals may be an option, but it will need significant thought to
> implement well so we haven't yet gone that route (more choices before a
> user can get started isn't always a good thing).
>
> Templates aside, writing a great grant proposal or project plan isn't a
> skill everyone has (no matter how good the form/guidelines are), and there
> is a delicate balance to find between expecting an applicant to have
> everything prepared up front and creating so many barriers to entry so that
> good ideas are killed before the community has a chance to see them. We've
> found the IEG community comments period to be a useful time to help some
> folks improve their proposals significantly, get confirmation on those that
> are already in good shape, and also to flag issues to the committee which
> may seem obvious to you, but not to everyone.
>
>
>
> On Wed, Oct 7, 2015 at 5:40 AM, Andre Klapper 
> wrote:
>
> > On Tue, 2015-10-06 at 21:05 -0600, Brian Wolff wrote:
> > > It would be nice if before asking for general review, the proposals
> > > were vetted to have sufficient detail. Some of these seem to be "I
> > > want X$ to do Y, and I'm not going to tell you how I plan to do Y, or
> > > how I determined X$ is needed, or even give a detailed definition of
> > > what Y is".
> > >
> > > For a grant proposal, I'd expect to see budget justifications, time
> > > estimations broken down by rough sub tasks, a general plan of attack,
> > > potential risks and how the grantee plans to mitigate them, user
> > > acceptance criteria, etc
> >
> > Thanks Brian. These sound like very valid points.
> >
> > I'm curious if application templates of other (technical) programs have
> > already been looked at for IEG and which conclusions were drawn. Seeing
> > https://www.mediawiki.org/wiki/Outreach_programs/Application_template a
> > nd
> >
> >
> https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project
> > I can imagine there's knowledge to share (*if* that hasn't happened
> > yet).
> >
> > andre
> > --
> > Andre Klapper | Wikimedia Bugwrangler
> > http://blogs.gnome.org/aklapper/
> >
> >
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> Siko Bouterse
> Director of Community Resources
> Wikimedia Foundation, Inc.
>
> sboute...@wikimedia.org
>
> *Imagine a world in which every single human being can freely share in the
> sum of all knowledge. *
> *Donate  or click the "edit" button today,
> and help us make it a reality!*
> ___
> 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] Technical expertise needed for Individual Engagement Grant proposals!

[Pine W]

I would mention that in your comments.

Pinging Siko to see if she wants to share a grantmaker's perspective. (Siko
is dealing with some of the fallout from Wikimaniagate, so I'm not sure if
she will respond.)

Pine
On Oct 6, 2015 9:10 PM, "Brian Wolff"  wrote:

> I feel that way about all of them, except maybe StrepHit and
> Vietnamese categories (Pan-Scandinavian lang is on the border imo)
>
> I feel like the only things really being assessed here is the
> reputation of the author, if the funding is orders of magnitude
> off-base, if the goal is remotely in scope of strategic goals, and if
> the author said anything outright ridiculous in the proposal.
>
> Most of them don't even have a definition of a minimum viable product
> that you could use to determine if the grantee actually even completed
> the proposal as promised.
>
> --
> -bawolff
>
> On 10/6/15, Pine W  wrote:
> > Disclaimer: I was a founding member of IEGCom, for a time I was one of
> its
> > coordinators, and I currently have a grant proposal for this round of
> IEGs.
> >
> > Comment: if you think that a proposal needs further development before
> > funding it, please say so on that proposal's talk page. When I was on the
> > Committee, I found it helpful to have  public comments to read; the
> > responsiveness and articulateness of grant proposers when replying to
> > public questions and comments was also a factor that I considered when
> > evaluating proposals. And as a grantee, I find that good-faith comments
> > help me to improve my proposal.
> >
> > Thanks for your interest in IEG!
> >
> > Pine
> > On Oct 6, 2015 8:05 PM, "Brian Wolff"  wrote:
> >
> >> On 10/6/15, Chris Schilling  wrote:
> >> > Hey folks,
> >> >
> >> > Applicants for the current round of Individual Engagement Grants (IEG)
> >> have
> >> > submitted many proposals that involve new tools, bot tasks, and other
> >> > technical elements.  I’ve provided the list of these proposals and
> brief
> >> > descriptions below.
> >> >
> >> > Your feedback in these technical proposals is requested!  If one of
> >> > these
> >> > ideas interests you, consider reading it over, and feel free to
> endorse,
> >> > express concerns, make suggestions, and ask questions.  Your input and
> >> > expertise will help the applicants develop better proposals, and
> support
> >> > the IEG Committee during their evaluation. Comments are requested
> until
> >> > October 19th.
> >> >
> >> > With thanks,
> >> >
> >> > Jethro
> >> >
> >> > 
> >> >
> >> > Wiki Needs Pictures
> >> > <https://meta.wikimedia.org/wiki/Grants:IEG/Wiki_needs_pictures>
> >> >> Developing a map to show entities around the world that need
> >> >> photographs
> >> > on Wikipedia
> >> >
> >> >
> >> > Wikimedia Maps Rendering Improvements
> >> > <
> >>
> https://meta.wikimedia.org/wiki/Grants:IEG/Wikimedia_Maps_Rendering_Improvements
> >> >
> >> >> Improving road labels and borders on Wikimedia Maps
> >> >
> >> >
> >> > Wikimaps Warper 2.0
> >> > <https://meta.wikimedia.org/wiki/Grants:IEG/Wikimaps_Warper_2.0>
> >> >>Refactoring Wikimaps Warper code to make the project more accessible
> for
> >> > volunteer contributions
> >> >
> >> >
> >> > Alt Text Tools <
> >> https://meta.wikimedia.org/wiki/Grants:IEG/Alt_text_tools>
> >> >>Tool to make it easier to improve text alternatives for images
> >> >
> >> >
> >> > Batch Uploader for Small GLAM Projects
> >> > <
> >>
> https://meta.wikimedia.org/wiki/Grants:IEG/Batch_uploader_for_small_GLAM_projects
> >> >
> >> >>Creating a simple batch uploader for small-to-medium entry level
> partner
> >> > institutions.
> >> >
> >> >
> >> > Bot Development for Azerbaijani Wikipedia
> >> > <
> >>
> https://meta.wikimedia.org/wiki/Grants:IEG/Bot_Development_for_Azerbaijani_Wikipedia
> >> >
> >> >>Developing a translation bot for Azerbaijani Wikipedia
> >> >
> >> >
> >> > Proofreading semiautomatically the Catalan Wikipedia with LanguageTool
> >> > <
> >>
> https://meta.wik

Re: [Wikitech-l] Technical expertise needed for Individual Engagement Grant proposals!

[Pine W]

Disclaimer: I was a founding member of IEGCom, for a time I was one of its
coordinators, and I currently have a grant proposal for this round of IEGs.

Comment: if you think that a proposal needs further development before
funding it, please say so on that proposal's talk page. When I was on the
Committee, I found it helpful to have  public comments to read; the
responsiveness and articulateness of grant proposers when replying to
public questions and comments was also a factor that I considered when
evaluating proposals. And as a grantee, I find that good-faith comments
help me to improve my proposal.

Thanks for your interest in IEG!

Pine
On Oct 6, 2015 8:05 PM, "Brian Wolff"  wrote:

> On 10/6/15, Chris Schilling  wrote:
> > Hey folks,
> >
> > Applicants for the current round of Individual Engagement Grants (IEG)
> have
> > submitted many proposals that involve new tools, bot tasks, and other
> > technical elements.  I’ve provided the list of these proposals and brief
> > descriptions below.
> >
> > Your feedback in these technical proposals is requested!  If one of these
> > ideas interests you, consider reading it over, and feel free to endorse,
> > express concerns, make suggestions, and ask questions.  Your input and
> > expertise will help the applicants develop better proposals, and support
> > the IEG Committee during their evaluation. Comments are requested until
> > October 19th.
> >
> > With thanks,
> >
> > Jethro
> >
> > 
> >
> > Wiki Needs Pictures
> > 
> >> Developing a map to show entities around the world that need photographs
> > on Wikipedia
> >
> >
> > Wikimedia Maps Rendering Improvements
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Wikimedia_Maps_Rendering_Improvements
> >
> >> Improving road labels and borders on Wikimedia Maps
> >
> >
> > Wikimaps Warper 2.0
> > 
> >>Refactoring Wikimaps Warper code to make the project more accessible for
> > volunteer contributions
> >
> >
> > Alt Text Tools <
> https://meta.wikimedia.org/wiki/Grants:IEG/Alt_text_tools>
> >>Tool to make it easier to improve text alternatives for images
> >
> >
> > Batch Uploader for Small GLAM Projects
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Batch_uploader_for_small_GLAM_projects
> >
> >>Creating a simple batch uploader for small-to-medium entry level partner
> > institutions.
> >
> >
> > Bot Development for Azerbaijani Wikipedia
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Bot_Development_for_Azerbaijani_Wikipedia
> >
> >>Developing a translation bot for Azerbaijani Wikipedia
> >
> >
> > Proofreading semiautomatically the Catalan Wikipedia with LanguageTool
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Proofreading_semiautomatically_the_Catalan_Wikipedia_with_LanguageTool
> >
> >>Proofreading the whole Catalan Wikipedia using the LanguageTool with the
> > help of scripts and appropriate supervision.
> >
> >
> > Color Blindness Content Checker
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Color_blindness_content_checker
> >
> >>Make Wikipedia chart and diagrams color blind accessible
> >
> >
> > Pan-Scandinavian Machine-assisted Content Translation
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Pan-Scandinavian_Machine-assisted_Content_Translation
> >
> >>Creating more machine translation language data for use in Content
> > Translation, for Swedish, Danish and Norwegian Bokmål+Nynorsk projects.
> >
> >
> > StrepHit: Wikidata Statements Validation via References
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/StrepHit:_Wikidata_Statements_Validation_via_References
> >
> >>Creating a process that extracts facts from text and produces Wikidata
> > statements with reference URLs.
> >
> >
> > Semi-automatically generate Categories for Vietnamese Wikipedia
> > <
> https://meta.wikimedia.org/wiki/Grants:IEG/Semi-automatically_generate_Categories_for_Vietnamese_Wikipedia
> >
> >>Generating new categories for small-scale & medium-scale Wikipedias where
> > editors are lacking.
> >
> > --
> > Chris "Jethro" Schilling
> > I JethroBT (WMF) 
> > Community Organizer, Wikimedia Foundation
> > 
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> It would be nice if before asking for general review, the proposals
> were vetted to have sufficient detail. Some of these seem to be "I
> want X$ to do Y, and I'm not going to tell you how I plan to do Y, or
> how I determined X$ is needed, or even give a detailed definition of
> what Y is".
>
> For a grant proposal, I'd expect to see budget justifications, time
> estimations broken down by rough sub tasks, a general plan of attack,
> potential risks and how the grantee plans to mitigate them, 

Re: [Wikitech-l] What is the status of Cirrus Search development?

[Pine W]

Hi, I have a hunch that discussions about search moved to the Discovery
mailing list: https://lists.wikimedia.org/mailman/listinfo/discovery

Pine
On Oct 3, 2015 9:28 PM, "billinghurst"  wrote:

> For a while Cirrus Search was the "bee's knees"[1] around here, and we were
> got to the stage that all wikis were moved onto this search functionality.
>
> Then silence.  Complete and utter silence.
>
> Presumably there has been stuff happening out of the public eye, and I am
> not wanting to dig into personal areas, however, the silence on what was a
> key development is very disappointing.  Can we please have an update.
> Thanks.
>
> Regards, Billinghurst
> [1] https://en.wiktionary.org/wiki/bee's_knees
> ___
> 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] Would anyone be interested in a tech talk about how to make a mw skin?

[Pine W]

I would like to see a beautiful skin that looks like it was made in 2015!

On Mon, Sep 28, 2015 at 2:00 PM, Isarra Yos  wrote:

> Jack Phoenix and I were considering doing a tech talk about how to make a
> MediaWiki skin. Would there be any interest in this? What would you folks
> want to see from such a talk?
>
> -I
>
> ___
> 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] Mentors and projects needed for Outreachy round 11

[Pine W]

Hi Brian,
I was told by a WMF non-management employee that they have little
discretion about which projects they're working on, and that the decisions
about priorities come top-down. Hence my interest in engaging with the
quarterly planning processes and the people managing those processes to see
if there's a way to get community input into the teams' quarterly goals.

On Mon, Sep 28, 2015 at 12:02 PM, Brian Wolff  wrote:

> WMF is made up of individuals. If there's something that you think
> should be done, why not figure out which team it would normally fall
> under, and politely suggest it to the people on the team that they
> should make it a priority (If it doesn't fall under any team - lets be
> realistic, it probably won't be done)
>
> They're either going to say yes or they're going to say no. The better
> reasoned your argument for why its important, the more likely they are
> going to say yes.
>
> That said, gsoc/opw usually doesn't reflect Wikimedia community
> priorities all that much (imo).
>
> --
> -bawolff
>
> On 9/28/15, Pine W  wrote:
> > Hi Quim,
> >
> > For projects that don't move forward in Outreachy for any reason, is
> there
> > a way of suggesting that the particularly useful open projects get WMF
> dev
> > time next quarter? It would be nice if there is a way to incorporate
> > community priorities into quarterly department goal setting.
> >
> > Pine
> > On Sep 28, 2015 4:18 AM, "Quim Gil"  wrote:
> >
> >> A new round of Outreachy is about to start and we need mentors for
> >> projects.
> >>
> >> https://www.mediawiki.org/wiki/Outreachy/Round_11
> >>
> >> Mentors go first, because we haven't many confirmed for this round, and
> we
> >> have already many possible project ideas:
> >>
> >> https://phabricator.wikimedia.org/tag/possible-tech-projects/
> >>
> >> Still, if you want to volunteer as mentor for a new project, the gates
> are
> >> also wide open for you.
> >>
> >> There are already several candidates looking for a project and asking
> for
> >> microtasks to show their skills.
> >>
> >> Questions? Just ask, here or at
> https://phabricator.wikimedia.org/T112620
> >>
> >> --
> >> Quim Gil
> >> Engineering Community Manager @ Wikimedia Foundation
> >> http://www.mediawiki.org/wiki/User:Qgil
> >> ___
> >> 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] Mentors and projects needed for Outreachy round 11

[Pine W]

Hi Quim,

For projects that don't move forward in Outreachy for any reason, is there
a way of suggesting that the particularly useful open projects get WMF dev
time next quarter? It would be nice if there is a way to incorporate
community priorities into quarterly department goal setting.

Pine
On Sep 28, 2015 4:18 AM, "Quim Gil"  wrote:

> A new round of Outreachy is about to start and we need mentors for
> projects.
>
> https://www.mediawiki.org/wiki/Outreachy/Round_11
>
> Mentors go first, because we haven't many confirmed for this round, and we
> have already many possible project ideas:
>
> https://phabricator.wikimedia.org/tag/possible-tech-projects/
>
> Still, if you want to volunteer as mentor for a new project, the gates are
> also wide open for you.
>
> There are already several candidates looking for a project and asking for
> microtasks to show their skills.
>
> Questions? Just ask, here or at https://phabricator.wikimedia.org/T112620
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
> ___
> 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] Report on last year's Freenode security breach

[Pine W]

I just now see that there was a report published about last year's security
breach on Freenode. The report, written by NCC Group’s Cyber Defence
Operations team, may be of interest to infrastructure security and tech ops
people:

https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2014/october/analysis-of-the-linux-backdoor-used-in-freenode-irc-network-compromise/

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

[Wikitech-l] Upcoming database purge on Freenode

[Pine W]

Freenode occasionally purges its databases of "expired nicks, channels and
accounts". If you have a nick, channel or account that you want to keep and
haven't used recently, now is a good time to do so. See
https://blog.freenode.net/2015/09/services-database-purge/ for more info.
Please send any questions to Freenode staff.

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

Re: [Wikitech-l] Link: useful article on in-person events

[Pine W]

That is a nice article.

In the Wikiverse, conferences are good venues for Q&A, structured dialogue,
building and maintenance personal connections, and brainstorming. Excluded
from this picture is the ordination of community policy, but brainstorming,
drafting, and creating policy proposals are all ok and probably benefit
from high-frequency interactions, both spontaneous and planned.



Pine


On Wed, Sep 16, 2015 at 11:33 AM, Frances Hocutt 
wrote:

> An excellent article on best practices and pitfalls for in-person technical
> events: https://modelviewculture.com/pieces/software-in-person
>
> This has some ideas and framings that can be useful for planning for the
> upcoming developer summit.
>
> -Frances
> ___
> 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] Tools for dealing with citations of withdrawn academic journal articles

[Pine W]

Ryan, can we get an update about when
https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey
will be launched? Thanks!

Pine


On Tue, Aug 18, 2015 at 2:24 PM, Ryan Kaldari 
wrote:

> On Tue, Aug 18, 2015 at 2:06 PM, Pine W  wrote:
>
>> 1. I was thinking of a tool that would let users input a variety of ways
>> of referring to the retracted articles, such as DOI numbers (Peaceray is an
>> expert in these). The tool would accept multiple inputs simultaneously,
>> such as all 64 articles that were retracted in a batch. The tool would
>> return to the user a list of all articles in which those references are
>> used as citations, and highlight the paragraphs of the article where the
>> citations are used. This would, I hope, greatly improve the efficiency of
>> the workflow for dealing with retracted journal articles.
>>
>
> Sounds like a reasonable proposal, although I have to wonder if the time
> spent building and maintaining this tool would be more or less than the
> time it would save editors to search for retracted journal articles.
>
>
>> 2. I'm not clear on where I should list a new idea. The list of ideas in 
>> Community
>> Tech team/All Our Ideas/Process
>> <https://www.mediawiki.org/wiki/Community_Tech_team/All_Our_Ideas/Process>
>> is based on a survey that has already been completed. Is there a
>> Phabricator workboard that would be appropriate for listing a new idea such
>> as this?
>>
>
> Community Tech is currently only accepting new tasks related to the All
> Our Ideas survey results (
> https://www.mediawiki.org/wiki/Community_Tech_team/All_Our_Ideas). We
> will be opening up a new survey next month though (
> https://www.mediawiki.org/wiki/Community_Tech_team/Community_Wishlist_Survey/Process).
> In the meantime, you can post the idea at
> https://meta.wikimedia.org/wiki/Community_Tech_project_ideas to get more
> input on it. More details about all of this will be announced hopefully
> next week.
>
>
>> 3. I would prefer to have everyone using the same system, which is
>> lists.wikimedia.org. It makes sense to me that everyone might migrate
>> eventually to a newer system. I suggest avoiding fragmentation. Researching
>> the possibility of migrating all mailing lists to a newer system sounds
>> like a good project for Community Tech and I could propose that in
>> Phabricator as well if there's a good place to do so.
>>
>
> That's a pretty good point. I'll request to have the mailing list moved to
> lists.wikimedia.org.
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fwd: [Engineering] September Lightning Talks

[Pine W]

Ok, how about having a detailed Flow and Collaboration presentation at the
October metrics meeting?

Pine
On Sep 9, 2015 2:47 PM, "Kevin Leduc"  wrote:

> Hi Pine,
>
> I don't think Lightning Talks are the right venue for discussing the
> decision to put Flow into maintenance.  I'd like to give priority to
> engineering teams who can showcase their work.  Also, I think any
> discussion on Flow deserves more than 10 minutes.
>
> On Wed, Sep 9, 2015 at 12:01 PM, Pine W  wrote:
>
> > Would it be possible to request a lightning talk about the reasoning
> behind
> > the decision to put Flow into maintenance mode, and about the plans for
> the
> > Collaboration team's work post-Flow?
> >
> > Pine
> > On Sep 9, 2015 11:36 AM, "Rachel Farrand" 
> wrote:
> >
> > > lightning talks <https://en.wikipedia.org/wiki/Lightning_talk> on Sep
> > 22!
> > > ~ More logistic details/signups found in the email below ~
> > >
> > > Please sign up if you would like to do a quick 10 min talk this month.
> > >
> > > These talks will continue every month until there is no longer
> interest.
> > >
> > > A youtube stream will be sent out to this list just before the talks
> > start
> > > so you can follow along, you can ask questions on IRC, and the talks
> will
> > > also be recorded so that you can watch them whenever you like.
> > >
> > > -- Forwarded message --
> > > From: Kevin Leduc 
> > > Date: Tue, Sep 8, 2015 at 4:33 PM
> > > Subject: [Engineering] September Lightning Talks
> > > To: "Staff (All)" , Engineering list <
> > > engineer...@lists.wikimedia.org>
> > >
> > >
> > > Hello!
> > >
> > >
> > > September's Lightning Talks are in two weeks and we are looking for
> more
> > > volunteers to present. Lightning Talks are an opportunity for teams @
> > WMF &
> > > in the Community to showcase a Quarterly Goal achieved, significant
> > > milestone, release, or anything of significance to the rest of the
> > > foundation and the movement as a whole. These talks will be open to our
> > > communities.
> > >
> > >
> > > Each presentation will be 10 minutes or less, the formal part should be
> > not
> > > be longer than 5 minutes and the remainder can be used for questions.
> We
> > > need at least three people to sign-up to be speakers on the wiki page
> > > <https://www.mediawiki.org/wiki/Lightning_Talks> by September 15 or
> else
> > > the talks will be postponed to the next month.
> > >
> > > Too many questions to answer in the allotted time?  No worries, your
> > > lightning talk will be a great candidate for a future Tech Talk.
> > >
> > > Third Round of Lightning Talks:
> > >
> > > When: Tuesday September 22, 1800 UTC
> > > <
> > >
> >
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks+-+August&iso=20150922T18&p1=1440&ah=1
> > > >,
> > > 11am PDT
> > >
> > > Where: 5th Floor
> > >
> > > Remotees: On-Air google hangout will be provided just before the
> meeting
> > >
> > > IRC: #wikimedia-tech
> > >
> > > Sign up for a 10 minute slot here:
> > > https://www.mediawiki.org/wiki/Lightning_Talks
> > >
> > >
> > > Thanks!
> > > Kevin Leduc, Rachel Farrand, Megan Neisler
> > >
> > > ___
> > > Engineering mailing list
> > > engineer...@lists.wikimedia.org
> > > https://lists.wikimedia.org/mailman/listinfo/engineering
> > > ___
> > > 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] Fwd: [Engineering] September Lightning Talks

[Pine W]

Would it be possible to request a lightning talk about the reasoning behind
the decision to put Flow into maintenance mode, and about the plans for the
Collaboration team's work post-Flow?

Pine
On Sep 9, 2015 11:36 AM, "Rachel Farrand"  wrote:

> lightning talks  on Sep 22!
> ~ More logistic details/signups found in the email below ~
>
> Please sign up if you would like to do a quick 10 min talk this month.
>
> These talks will continue every month until there is no longer interest.
>
> A youtube stream will be sent out to this list just before the talks start
> so you can follow along, you can ask questions on IRC, and the talks will
> also be recorded so that you can watch them whenever you like.
>
> -- Forwarded message --
> From: Kevin Leduc 
> Date: Tue, Sep 8, 2015 at 4:33 PM
> Subject: [Engineering] September Lightning Talks
> To: "Staff (All)" , Engineering list <
> engineer...@lists.wikimedia.org>
>
>
> Hello!
>
>
> September's Lightning Talks are in two weeks and we are looking for more
> volunteers to present. Lightning Talks are an opportunity for teams @ WMF &
> in the Community to showcase a Quarterly Goal achieved, significant
> milestone, release, or anything of significance to the rest of the
> foundation and the movement as a whole. These talks will be open to our
> communities.
>
>
> Each presentation will be 10 minutes or less, the formal part should be not
> be longer than 5 minutes and the remainder can be used for questions. We
> need at least three people to sign-up to be speakers on the wiki page
>  by September 15 or else
> the talks will be postponed to the next month.
>
> Too many questions to answer in the allotted time?  No worries, your
> lightning talk will be a great candidate for a future Tech Talk.
>
> Third Round of Lightning Talks:
>
> When: Tuesday September 22, 1800 UTC
> <
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks+-+August&iso=20150922T18&p1=1440&ah=1
> >,
> 11am PDT
>
> Where: 5th Floor
>
> Remotees: On-Air google hangout will be provided just before the meeting
>
> IRC: #wikimedia-tech
>
> Sign up for a 10 minute slot here:
> https://www.mediawiki.org/wiki/Lightning_Talks
>
>
> Thanks!
> Kevin Leduc, Rachel Farrand, Megan Neisler
>
> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
> ___
> 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] Collaboration team reprioritization

[Pine W]

Thanks for the expanded update.

I'm a big fan of Echo and am happy to hear that global notifications are
coming.

If you'll be at WikiConference USA, I'd appreciate a chance to talk with
you there in person, and others might as well!

Pine


On Fri, Sep 4, 2015 at 2:48 PM, Danny Horn  wrote:

> Flow is going to be one of the extensions that the Collaboration team
> maintains, along with Echo and Thanks. "Not in active development" means
> that we're not going to build or change features, but we're going to fix
> bugs and make sure that people who are using Flow have a good experience
> with it.
>
> It's a similar situation to Echo, which wasn't in active development for at
> least eighteen months, but we fixed bugs and made some changes to connect
> it up with Flow. We've recently started doing the prep work for global
> cross-wiki Echo notifications, which is another project that we're going to
> be working on in October.
>
> We talked about the Workflows project at Wikimania, introducing it as
> something that we were going to work on in early 2016. This priority change
> basically means that Workflows moves from "3 to 6 months from now" to next
> month.
>
> As people have noted, the Foundation spent money developing Flow discussion
> features, and we did the work in iterative stages, to make sure that there
> was a useable (if incomplete) product at every stage. That gave us the
> opportunity to get great feedback and see how people were using Flow, but
> it also just provides value on its own. Shifting priorities happens with
> product teams all the time, so you always want to be able to get to a
> stable place, and still have something worthwhile.
>
> Right now, there are several wikis that are enthusiastic about using Flow,
> on user talk pages, help forums and village pump-style discussion pages.
> Later this month, we're going to release the opt-in beta feature for wikis
> that request it, so that people can turn Flow on for their own user talk
> pages, and continue to get value out of the existing product. At that
> point, it's our responsibility to fix bugs and maintain it, so that we're
> not jerking the rug out from under the people who have been so helpful and
> important to the team.
>
> Danny
>
>
>
> On Fri, Sep 4, 2015 at 9:07 AM, Jonathan Morgan 
> wrote:
>
> > On Fri, Sep 4, 2015 at 1:25 AM, Brian Wolff  wrote:
> > >
> > > I seriously doubt any form of technology will solve the problem of
> > > independent groups with overlapping interests discussing things in
> > > multiple venues.
> > >
> > > My reading of the original email is that they want to work on things
> > > that have rather fixed bureaucratic procedures (e.g. Discussions about
> > > what content to delete). Relatively free-form discussion across many
> > > locations, seems like the opposite of that imo. I would love to hear
> > > in more detail what the team concretely plans to work on, although I
> > > imagine that's still in the process of being planned.
> > >
> > >
> > You're correct, as far as I know. I can't/won't speak for Danny about the
> > product roadmap (I'm sure he will jump in here again), but one component
> of
> > what's planned is indeed support for these so-called "bureaucratic
> > procedures". I did some initial research before Wikimania (still-drafty
> > wikipage report[1], internal presentation[2]), and Danny incorporated
> some
> > of this into his Wikimania presentation.[3]
> >
> > I've heard of several other components from the team, but "workflows" is
> > definitely part of it.
> >
> > Thanks to you, Pine, Risker and others for the good-faith assessments,
> btw.
> >
> > J
> >
> > 1.
> >
> >
> https://www.mediawiki.org/wiki/Flow/Community_process_workflow_interviews_(June_2015)
> > 2.
> >
> >
> https://www.mediawiki.org/wiki/File:Flow_workflow_interviews_-_initial_findings_June_2015.pdf
> > 3.
> >
> https://www.mediawiki.org/wiki/File:User(s)_Talk(ing)_-_Wikimania_2015.pdf
> >
> >
> > > --
> > > -bawolff
> > >
> > > ___
> > > Wikitech-l mailing list
> > > Wikitech-l@lists.wikimedia.org
> > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > >
> >
> >
> >
> > --
> > Jonathan T. Morgan
> > Senior Design Researcher
> > Wikimedia Foundation
> > User:Jmorgan (WMF) 
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Collaboration team reprioritization

[Pine W]

I'm speculating that an analogue for Flow's situation will be Echo's
situation: somewhat maintained, but on the back burner for feature
development. (Although I occasionally hear rumors of feature additions to
Echo, and I think Echo might play well with improved discussion tools. I'd
also like to see global watchlists and global notifications.) Hopefully
we'll get a reply from Danny in the near future with more definitive
answers about Flow's situation. (:

Pine


On Fri, Sep 4, 2015 at 1:34 AM, Brian Wolff  wrote:

> I don't think putting a $$ value on it is necessary to answer David's
> question (Or even sufficient from a user perspective). The core of it
> is:
>
> *Will anyone (from WMF) be coding any new features, that don't exist yet.
> *Will features that half work or are currently in the process of being
> developed, be completed (Assuming there are any, I'm not following
> flow development that closely).
> *Will someone be working on existing bugs during this time (Or at
> least existing bugs at some level of seriousness. And if so, what
> level of seriousness would be required for someone to do it)
> *Will someone be triaging and fixing new bugs as they come in (And
> again, how does the answer vary depending on the seriousness of the
> bug).
> *Is the team planning to come back to Flow at a later date in a
> serious way, or is this the end of active development for the
> foreseeable future.
>
> --
> bawolff
>
> On 9/4/15, Pine W  wrote:
> > Regarding specific resource-level commitments: I've always had a hard
> time
> > with getting project-level financial data from WMF. I'm still waiting for
> > replies to questions that I asked about the Annual Plan a couple of
> months
> > ago. I do think that information like that should be public, and it would
> > be nice if WMF would move toward more financial transparency that's at
> > least on par with what's provided by US government agencies. I'd like to
> > keep the financial transparency discussion a bit separate from the
> > discussion about Flow's status. If WMF starts to provide public details
> > about project-level accounting in general, I would welcome that.
> >
> > Pine
> >>
> >>
> >> It read to me and many others like a fairly standard set of euphemisms
> >> for when a project is killed but nobody wants to say "killed". Perhaps
> >> we're all reading it wrong.
> >>
> >> So, non-euphemistically: could someone please detail what, precisely,
> >> is and is not the level of resource commitment to Flow? (And how it
> >> compares to e.g. the level of resource commitment to LQT.)
> >>
> >>
> >> - d.
> >>
> >> ___
> >> 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] Collaboration team reprioritization

[Pine W]

Yes and no on the first point. Aggregation tools would be helpful.
Admittedly it's rare to have discussions spill into so many venues, so ROI
is questionable on an investment like that.

On more structured discussions, yes, those could be made easier to handle.
Maybe it would be better to handle the easier cases first. I'm with you in
looking forward to hearing plans for more details. (Maybe there can be a
live discussion about this at WikiConference USA, with remote participation
as an option?)

Pine


On Fri, Sep 4, 2015 at 1:25 AM, Brian Wolff  wrote:

> On 9/4/15, Pine W  wrote:
> > Re-reading the original email, it sounds to me like Flow is being put
> into
> > maintenance mode, not killed. It also sounds to me like the resources
> that
> > were being invested in Flow are going to be redirected to "the curation,
> > collaboration, and admin processes that take place on a variety of pages.
> > Many of these processes use complex workarounds -- templates, categories,
> > transclusions, and lots of instructions -- that turn blank wikitext talk
> > pages into structured workflows..."
> >
> > As those of us who have spent a lot of time with these workflows know,
> they
> > can be a time-consuming pain. (Does anyone else remember trying to track
> > the discussion about the MediaViewer deployments to Commons, DEWP and
> ENWP
> > over however many dozens of separate pages, at least three wikis, and
> > multiple email threads?)
>
> I seriously doubt any form of technology will solve the problem of
> independent groups with overlapping interests discussing things in
> multiple venues.
>
> My reading of the original email is that they want to work on things
> that have rather fixed bureaucratic procedures (e.g. Discussions about
> what content to delete). Relatively free-form discussion across many
> locations, seems like the opposite of that imo. I would love to hear
> in more detail what the team concretely plans to work on, although I
> imagine that's still in the process of being planned.
>
> --
> -bawolff
>
> ___
> 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] Collaboration team reprioritization

[Pine W]

Regarding specific resource-level commitments: I've always had a hard time
with getting project-level financial data from WMF. I'm still waiting for
replies to questions that I asked about the Annual Plan a couple of months
ago. I do think that information like that should be public, and it would
be nice if WMF would move toward more financial transparency that's at
least on par with what's provided by US government agencies. I'd like to
keep the financial transparency discussion a bit separate from the
discussion about Flow's status. If WMF starts to provide public details
about project-level accounting in general, I would welcome that.

Pine


On Fri, Sep 4, 2015 at 12:24 AM, David Gerard  wrote:

> On 4 September 2015 at 01:38, Ricordisamoa 
> wrote:
> > Il 04/09/2015 01:24, Brandon Harris ha scritto:
> >>> On Sep 3, 2015, at 4:06 PM, Ricordisamoa
> >>> wrote:
>
> >>> I appreciate the acknowledgement of failure.
>
> >> I don't think that's what was said at all.  You may wish to
> >> re-read all of this.
>
> > Putting "active development" on hold when the software is little used in
> > production and even some features a MVP should have had are missing,
> really
> > sounds like a failure to me, although Danny has been very good at not
> making
> > it sound like it.
> > "To better address the needs of our core contributors", "we shift the
> team's
> > focus to these other priorities", "communities that are excited about
> Flow
> > discussions will be able to use it"
>
>
>
> It read to me and many others like a fairly standard set of euphemisms
> for when a project is killed but nobody wants to say "killed". Perhaps
> we're all reading it wrong.
>
> So, non-euphemistically: could someone please detail what, precisely,
> is and is not the level of resource commitment to Flow? (And how it
> compares to e.g. the level of resource commitment to LQT.)
>
>
> - d.
>
> ___
> 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] Collaboration team reprioritization

[Pine W]

Re-reading the original email, it sounds to me like Flow is being put into
maintenance mode, not killed. It also sounds to me like the resources that
were being invested in Flow are going to be redirected to "the curation,
collaboration, and admin processes that take place on a variety of pages.
Many of these processes use complex workarounds -- templates, categories,
transclusions, and lots of instructions -- that turn blank wikitext talk
pages into structured workflows..."

As those of us who have spent a lot of time with these workflows know, they
can be a time-consuming pain. (Does anyone else remember trying to track
the discussion about the MediaViewer deployments to Commons, DEWP and ENWP
over however many dozens of separate pages, at least three wikis, and
multiple email threads?)

I think that Flow was intended to help with these situations. I guess that
where it might be fair to say that Flow has been "killed" is in the sense
that WMF seems to have decided that there are better options than Flow for
addressing some of these workflow problems. It seems to me that the end
goals are similar; the tools to achieve those goals may be different, and
that's ok.

Pine


On Fri, Sep 4, 2015 at 12:24 AM, David Gerard  wrote:

> On 4 September 2015 at 01:38, Ricordisamoa 
> wrote:
> > Il 04/09/2015 01:24, Brandon Harris ha scritto:
> >>> On Sep 3, 2015, at 4:06 PM, Ricordisamoa
> >>> wrote:
>
> >>> I appreciate the acknowledgement of failure.
>
> >> I don't think that's what was said at all.  You may wish to
> >> re-read all of this.
>
> > Putting "active development" on hold when the software is little used in
> > production and even some features a MVP should have had are missing,
> really
> > sounds like a failure to me, although Danny has been very good at not
> making
> > it sound like it.
> > "To better address the needs of our core contributors", "we shift the
> team's
> > focus to these other priorities", "communities that are excited about
> Flow
> > discussions will be able to use it"
>
>
>
> It read to me and many others like a fairly standard set of euphemisms
> for when a project is killed but nobody wants to say "killed". Perhaps
> we're all reading it wrong.
>
> So, non-euphemistically: could someone please detail what, precisely,
> is and is not the level of resource commitment to Flow? (And how it
> compares to e.g. the level of resource commitment to LQT.)
>
>
> - d.
>
> ___
> 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] Collaboration team reprioritization

[Pine W]

The decision to stop Flow development could have been a matter of
prioritizing resources, and a decision may have been made that many of the
resources that would be invested in improving Flow can now be better used
elsewhere.

I am reluctant to throw stones about Flow.

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

Re: [Wikitech-l] QA: Holding our code to better standards.

[Pine W]

I just want to say that I appreciate this overview.

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

Re: [Wikitech-l] Collaboration team reprioritization

[Pine W]

Thanks for the update. Discussion is taking place on Wikimedia-l.

Pine
On Sep 1, 2015 2:27 PM, "Danny Horn"  wrote:

> For a while now, the Collaboration team has been working on Flow, the
> structured discussion system. I want to let you know about some changes in
> that long-term plan.
>
> While initial announcements about Flow said that it would be a universal
> replacement for talk pages, the features that were ultimately built into
> Flow were specifically forum-style group discussion tools. But article and
> project talk pages are used for a number of important and complex processes
> that those tools aren't able to handle, making Flow unsuitable for
> deployment on those kinds of pages.
>
> To better address the needs of our core contributors, we're now focusing
> our strategy on the curation, collaboration, and admin processes that take
> place on a variety of pages. Many of these processes use complex
> workarounds -- templates, categories, transclusions, and lots of
> instructions -- that turn blank wikitext talk pages into structured
> workflows. There are gadgets and user scripts on the larger wikis to help
> with some of these workflows, but these tools aren't standardized or
> universally available.
>
> As these workflows grow in complexity, they become more difficult for the
> next generation of editors to learn and use. This has increased the
> workload on the people who maintain those systems today. Complex workflows
> are also difficult to adapt to other languages, because a wiki with
> thousands of articles may not need the kind of complexity that comes with
> managing a wiki with millions of articles. We've talked about this kind of
> structured workflow support at Wikimania, in user research sessions, and on
> wikis. It's an important area that needs a lot of discussion, exploration,
> and work.
>
> Starting in October, Flow will not be in active development, as we shift
> the team's focus to these other priorities. We'll be helping core
> contributors reduce the stress of an ever-growing workload, and helping the
> next generation of contributors participate in those processes. Further
> development on these projects will be driven by the needs expressed by wiki
> communities.
>
> Flow will be maintained and supported, and communities that are excited
> about Flow discussions will be able to use it. There are places where the
> discussion features are working well, with communities that are
> enthusiastic about them: on user talk pages, help pages, and forum/village
> pump-style discussion spaces. By the end of September, we'll have an opt-in
> Beta feature available to communities that want it, allowing users to
> enable Flow on their own user talk pages.
>
> I'm sure people will want to know more about these projects, and we're
> looking forward to those conversations. We'll be reaching out for lots of
> input and feedback over the coming months.
>
> Danny Horn
> Collaboration team, PM
> ___
> 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 does "Director of Architecture" mean anyway?

[Pine W]

Welcome back. It's good to hear of your recovery.

Pine
On Sep 1, 2015 8:29 PM, "Rob Lanphier"  wrote:

> Hi everyone,
>
> It's been a while since I've been involved here, and I've got a pretty good
> excuse.  I'm going to avoid going into too much detail, but in short, I was
> involved in a pretty nasty traffic collision, and have only recently
> returned to work.  It turned out the way that a lot of bike versus car
> collisions go, which is to say, I lost  :-(
>
> The good news (for me at least), I've largely recovered.  The surgeons here
> did a remarkable job putting me back together again.  I returned to
> part-time work a couple of weeks ago, and I'm getting back up to speed on
> things.  I still have a number of personal obligations that keep me from
> working full-time, but I'll keep my user page on mediawiki.org
>  updated with the latest
> (or
> point you to where I plan to keep that info).
>
> Though we hadn't announced it in April, we had *just* talked about making
> my title "Director of Architecture" in the big reorg we had here at WMF.
> We hadn't worked out exactly what that meant when I was in the wreck, but I
> had a vague idea which I intend to flesh out.  In the short term, I want to
> facilitate the activity of the Architecture Committee
> .  I've started
> chairing the private meetings of that group, and I'm taking on a bunch of
> the administrivia.  I'll make things clearer as they become clearer in my
> head  :-)  Well, maybe after that, and after I get a chance to write down
> what I'm thinking.
> I'm really happy to be back involved!  \o/  If you have any questions, or
> you simply want to wave back, feel free to drop a comment on my MediaWiki
> talk page:
> https://www.mediawiki.org/wiki/User_talk:RobLa-WMF
>
> Rob
> ___
> 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] Delays in loading pages on Wikimedia sites

[Pine W]

OK, thanks.

Pine


On Tue, Sep 1, 2015 at 12:35 PM, Keegan Peterzell 
wrote:

> On Tue, Sep 1, 2015 at 2:13 PM, Pine W  wrote:
>
> > Yesterday and today, I've experienced a number of delays in getting pages
> > to load on Wikimedia sites. My connectivity to other websites is normal,
> so
> > I think something may be going on internally with Wikimedia
> connectivity. I
> > recall seeing discussions during Mexico Wikimania about testing
> connections
> > to Wikimedia sites systematically from geographically dispersed
> locations.
> > Is that kind of testing being done? Are there any other tools which might
> > explain the delays in getting connections and loading pages?
> >
> > Thanks,
> >
> > Pine
>
>
> Hm, I don't see anything alarming here:
> http://status.wikimedia.org/8777/169667/https-services---wikipedia
>
>
> --
> Keegan Peterzell
> Community Liaison, Product
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Delays in loading pages on Wikimedia sites

[Pine W]

Yesterday and today, I've experienced a number of delays in getting pages
to load on Wikimedia sites. My connectivity to other websites is normal, so
I think something may be going on internally with Wikimedia connectivity. I
recall seeing discussions during Mexico Wikimania about testing connections
to Wikimedia sites systematically from geographically dispersed locations.
Is that kind of testing being done? Are there any other tools which might
explain the delays in getting connections and loading pages?

Thanks,

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

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Pine W]

Brian,

Quite likely. (: But the Wikimedia CAPTCHA workboard suggests a lack of
emphasis on improving the general CAPTCHA situation for Wikimedia. The two
high priority tasks on that Phabricator workboard last received comments in
May and June. Those dates, plus the relative quiet on this mailing list,
suggest that there could be higher priority placed on CAPTCHA improvements.
I will discuss this with Luis on his talk page.

Thanks,
Pine
On Aug 18, 2015 11:43 PM, "Brian Wolff"  wrote:

> On Tuesday, August 18, 2015, Pine W  wrote:
> > what's happening with regard to improving usability for humans and
> > increasing the difficulty for bots?
>
> Generally speaking, isnt that an open problem in computer science?
>
> --
> Bawolff
> ___
> 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] Tools for dealing with citations of withdrawn academic journal articles

[Pine W]

1. I was thinking of a tool that would let users input a variety of ways of
referring to the retracted articles, such as DOI numbers (Peaceray is an
expert in these). The tool would accept multiple inputs simultaneously,
such as all 64 articles that were retracted in a batch. The tool would
return to the user a list of all articles in which those references are
used as citations, and highlight the paragraphs of the article where the
citations are used. This would, I hope, greatly improve the efficiency of
the workflow for dealing with retracted journal articles.

2. I'm not clear on where I should list a new idea. The list of ideas
in Community
Tech team/All Our Ideas/Process
<https://www.mediawiki.org/wiki/Community_Tech_team/All_Our_Ideas/Process>
is based on a survey that has already been completed. Is there a
Phabricator workboard that would be appropriate for listing a new idea such
as this?

3. I would prefer to have everyone using the same system, which is
lists.wikimedia.org. It makes sense to me that everyone might migrate
eventually to a newer system. I suggest avoiding fragmentation. Researching
the possibility of migrating all mailing lists to a newer system sounds
like a good project for Community Tech and I could propose that in
Phabricator as well if there's a good place to do so.

Thanks,

Pine


On Tue, Aug 18, 2015 at 1:52 PM, Ryan Kaldari 
wrote:

> On Tue, Aug 18, 2015 at 1:22 PM, Pine W  wrote:
>
>> Thanks for the info, Tilman.
>>
>> I ended up looking at the Community Tech page on MediaWiki, which says
>> that their scope of work includes "Building article curation and monitoring
>> tools for WikiProjects", so the kind of tools that we're discussing here
>> seem to be within their scope.
>>
>
> This project sounds like a good idea, but I don't really understand how it
> would work as a tool. There's no API for retracted journal articles. It
> seems like the best way to handle it would be when you find out about a
> retracted journal article to just search Wikipedia for the title of the
> article. What would a tool for this look like and how would it be more
> efficient that just searching?
>
>
>> Ryan, you seem to be the lead communicator for the group. Can you add
>> these tools to the list of projects that are in the Community Tech backlog?
>>
>
> See
> https://www.mediawiki.org/wiki/Community_Tech_team#Work_input_and_prioritization_process
>
>
>> Also, can you clarify why Community Tech is using Google Groups for its
>> mailing list instead of lists.wikimedia.org?
>>
>
> That's what WMF Office IT recommended (probably because it's interface
> wasn't developed in 1999). Do you think it should be on
> lists.wikimedia.org instead? Personally, it doesn't matter to me.
>
>
>> Thanks,
>>
>> Pine
>>
>>
>> On Tue, Aug 18, 2015 at 12:56 PM, Tilman Bayer 
>> wrote:
>>
>>> Related discussion from 2012:
>>>
>>> https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Medicine/Archive_26#Creating_a_bot_to_search_Wikipedia_for_retracted_papers
>>> (afaics it resulted in the creation of the {{retracted}} template, but
>>> no bot)
>>>
>>> The Community Tech team has its own mailing list now btw
>>> (https://groups.google.com/a/wikimedia.org/forum/#!forum/community-tech
>>> ).
>>>
>>> On Tue, Aug 18, 2015 at 2:42 AM, Pine W  wrote:
>>> > Is there any easy way to find all of citations of specified academic
>>> > articles on Wikipedias in all languages, and the text that is
>>> supported by
>>> > those references, so that the citations of questionable articles can be
>>> > removed and the article texts can be quickly reviewed for possible
>>> changes
>>> > or removal?
>>> >
>>> > See
>>> >
>>> https://www.washingtonpost.com/news/morning-mix/wp/2015/08/18/outbreak-of-fake-peer-reviews-widens-as-major-publisher-retracts-64-scientific-papers/?tid=hp_mm
>>> >
>>> > If we don't have easy ways to deal with this (and I believe that we
>>> don't),
>>> > I'd like to suggest that the Community Tech team work on tools to help
>>> when
>>> > these situations happen.
>>> >
>>> > Thanks,
>>> >
>>> > Pine
>>> > ___
>>> > Wikitech-l mailing list
>>> > Wikitech-l@lists.wikimedia.org
>>> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>
>>>
>>>
>>> --
>>> Tilman Bayer
>>> Senior Analyst
>>> Wikimedia Foundation
>>> IRC (Freenode): HaeB
>>>
>>> ___
>>> 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] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Pine W]

I see that there's an active workboard in Phabricator at
https://phabricator.wikimedia.org/project/board/225/ for CAPTCHA issues.

Returning to a subject that has been discussed several times before: the
last I heard is that our current CAPTCHAs do block some spambots, but they
also present problems for humans and aren't especially difficult for more
sophisticated spambots to solve. Can someone share a general update on
what's happening with regard to improving usability for humans and
increasing the difficulty for bots? I'm particularly concerned about the
former issue, since CAPTCHAs might be filtering out some good-faith human
editors.

Thanks,

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

Re: [Wikitech-l] Tools for dealing with citations of withdrawn academic journal articles

[Pine W]

Thanks for the info, Tilman.

I ended up looking at the Community Tech page on MediaWiki, which says that
their scope of work includes "Building article curation and monitoring
tools for WikiProjects", so the kind of tools that we're discussing here
seem to be within their scope.

Ryan, you seem to be the lead communicator for the group. Can you add these
tools to the list of projects that are in the Community Tech backlog? Also,
can you clarify why Community Tech is using Google Groups for its mailing
list instead of lists.wikimedia.org?

Thanks,

Pine


On Tue, Aug 18, 2015 at 12:56 PM, Tilman Bayer  wrote:

> Related discussion from 2012:
>
> https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Medicine/Archive_26#Creating_a_bot_to_search_Wikipedia_for_retracted_papers
> (afaics it resulted in the creation of the {{retracted}} template, but
> no bot)
>
> The Community Tech team has its own mailing list now btw
> (https://groups.google.com/a/wikimedia.org/forum/#!forum/community-tech
> ).
>
> On Tue, Aug 18, 2015 at 2:42 AM, Pine W  wrote:
> > Is there any easy way to find all of citations of specified academic
> > articles on Wikipedias in all languages, and the text that is supported
> by
> > those references, so that the citations of questionable articles can be
> > removed and the article texts can be quickly reviewed for possible
> changes
> > or removal?
> >
> > See
> >
> https://www.washingtonpost.com/news/morning-mix/wp/2015/08/18/outbreak-of-fake-peer-reviews-widens-as-major-publisher-retracts-64-scientific-papers/?tid=hp_mm
> >
> > If we don't have easy ways to deal with this (and I believe that we
> don't),
> > I'd like to suggest that the Community Tech team work on tools to help
> when
> > these situations happen.
> >
> > Thanks,
> >
> > Pine
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> Tilman Bayer
> Senior Analyst
> Wikimedia Foundation
> IRC (Freenode): HaeB
>
> ___
> 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] Geohack tools

[Pine W]

Interesting about the database situation. I was contemplating something
like a gadget that would be embedded on the page but be hosted on Labs.
Alternatively, the frequently updated info could be posted to Wikidata for
text and Commons for imagery so that information can be efficiently updated
across projects and languages.

Pine
On Aug 18, 2015 5:26 AM, "Erik Zachte"  wrote:

> As for realtime, I recommend caution with burdening Wikipedia with even
> more highly transient information, at least within our current database
> scheme.
>
> For years Serbian Wikinews has been inundated with weather info, hourly
> (!), per city (!), and thus managed 3 million revisions with a handful of
> editors.
>
> All those edits have made the dump explode in size: 6 GB uncompressed for
> 77k articles with about 2k content on average. Even if disk size doesn't
> matter, it slows batch processing, and clutters page history.
>
> Erik
>
>  -Original Message-
> From: wikitech-l-boun...@lists.wikimedia.org [mailto:
> wikitech-l-boun...@lists.wikimedia.org] On Behalf Of Oliver Keyes
> Sent: Tuesday, August 18, 2015 13:52
> To: Wikimedia developers
> Subject: Re: [Wikitech-l] Geohack tools
>
> Discovery is currently working on a maps service, which is a first step
> towards "geo-relevant" information, but the plan is to put that on hold for
> Q2 (read: the next 3 months) while we identify a clearer use case for it.
> If you or anyone else are interested in this kind of project (or in the
> functioning of our search service) I recommend subscribing to
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-search
>
> On 18 August 2015 at 06:09, Pine W  wrote:
> > Toby, is there any chance that the Reading team (or maybe Multimedia
> > or
> > Discovery?) will incorporate more intractive features or realtime
> > geo-relevant into Wikipedia with information like weather, air and
> > marine traffic, bus and train service (particularly for landmarks with
> > lots of tourists), star and sattelite positions in the sky,
> > socioeconomic data maps, financial statistics, etc?
> >
> > Thanks,
> >
> > Pine
> > On Aug 13, 2015 2:22 PM, "Pine W"  wrote:
> >
> >> It's great to hear that work is progressing on this.
> >>
> >> I'd like to see more interactive features on pages, for example live
> >> air traffic, ground traffic, and marine traffic data; and weather
> conditions.
> >>
> >> Pine
> >>
> >>
> >> On Fri, Aug 7, 2015 at 8:34 PM, Yuri Astrakhan
> >> 
> >> wrote:
> >>
> >>> Pine, you are right. That list is not very useful, and instead
> >>> should look something like this:
> >>>
> >>> https://en.wikivoyage.org/wiki/Salzburg#Get_around
> >>>
> >>> The bad news is that the tile service it uses is hosted on labs,
> >>> which means it cannot scale to the regular wikipedia-usage levels.
> >>> Plus there might be a potential policy problem there - default
> >>> lab-content loading on every page visit without user's consent.
> >>>
> >>> The good news is that we are very close to launching a full-blown
> >>> WMF production-hosted tile service, based on the wonderful data from
> OSM.
> >>>
> >>> See general info and some ideas people have proposed -
> >>> https://www.mediawiki.org/wiki/Maps  (feel free to add more)
> >>>
> >>>
> >>> On Fri, Aug 7, 2015 at 11:23 PM, Gergo Tisza 
> >>> wrote:
> >>>
> >>> > On Thu, Aug 6, 2015 at 11:01 PM, Pine W  wrote:
> >>> >
> >>> > > I just now realized how powerful these tools are when I started
> >>> clicking
> >>> > > around.
> >>> > >
> >>> > >
> >>> > >
> >>> >
> >>> https://tools.wmflabs.org/geohack/geohack.php?pagename=File%3AWhite-
> >>> cheeked_Starling_perching_on_a_rock.jpg¶ms=34.610576_N_135.54054
> >>> 2_E_globe:Earth_class:object_&language=en
> >>> > >
> >>> > > Is there any chance of integrating some of these tools more
> >>> > > directly
> >>> onto
> >>> > > Wikipedia pages, and into mobile web/mobile apps?
> >>> > >
> >>> >
> >>> > There is an ongoing project
> >>> > <https://phabricator.wikimedia.org/project/profile/1127/> to
> >>> > integrate maps into MediaWiki; that

Re: [Wikitech-l] Geohack tools

[Pine W]

Toby, is there any chance that the Reading team (or maybe Multimedia or
Discovery?) will incorporate more intractive features or realtime
geo-relevant into Wikipedia with information like weather, air and marine
traffic, bus and train service (particularly for landmarks with lots of
tourists), star and sattelite positions in the sky, socioeconomic data
maps, financial statistics, etc?

Thanks,

Pine
On Aug 13, 2015 2:22 PM, "Pine W"  wrote:

> It's great to hear that work is progressing on this.
>
> I'd like to see more interactive features on pages, for example live air
> traffic, ground traffic, and marine traffic data; and weather conditions.
>
> Pine
>
>
> On Fri, Aug 7, 2015 at 8:34 PM, Yuri Astrakhan 
> wrote:
>
>> Pine, you are right. That list is not very useful, and instead should look
>> something like this:
>>
>> https://en.wikivoyage.org/wiki/Salzburg#Get_around
>>
>> The bad news is that the tile service it uses is hosted on labs, which
>> means it cannot scale to the regular wikipedia-usage levels. Plus there
>> might be a potential policy problem there - default lab-content loading on
>> every page visit without user's consent.
>>
>> The good news is that we are very close to launching a full-blown WMF
>> production-hosted tile service, based on the wonderful data from OSM.
>>
>> See general info and some ideas people have proposed -
>> https://www.mediawiki.org/wiki/Maps  (feel free to add more)
>>
>>
>> On Fri, Aug 7, 2015 at 11:23 PM, Gergo Tisza 
>> wrote:
>>
>> > On Thu, Aug 6, 2015 at 11:01 PM, Pine W  wrote:
>> >
>> > > I just now realized how powerful these tools are when I started
>> clicking
>> > > around.
>> > >
>> > >
>> > >
>> >
>> https://tools.wmflabs.org/geohack/geohack.php?pagename=File%3AWhite-cheeked_Starling_perching_on_a_rock.jpg¶ms=34.610576_N_135.540542_E_globe:Earth_class:object_&language=en
>> > >
>> > > Is there any chance of integrating some of these tools more directly
>> onto
>> > > Wikipedia pages, and into mobile web/mobile apps?
>> > >
>> >
>> > There is an ongoing project
>> > <https://phabricator.wikimedia.org/project/profile/1127/> to integrate
>> > maps
>> > into MediaWiki; that's probably the best place to catalog the use cases
>> of
>> > Geohack and decide which can and need to be supported by the new tools.
>> > ___
>> > 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] Tools for dealing with citations of withdrawn academic journal articles

[Pine W]

Is there any easy way to find all of citations of specified academic
articles on Wikipedias in all languages, and the text that is supported by
those references, so that the citations of questionable articles can be
removed and the article texts can be quickly reviewed for possible changes
or removal?

See
https://www.washingtonpost.com/news/morning-mix/wp/2015/08/18/outbreak-of-fake-peer-reviews-widens-as-major-publisher-retracts-64-scientific-papers/?tid=hp_mm

If we don't have easy ways to deal with this (and I believe that we don't),
I'd like to suggest that the Community Tech team work on tools to help when
these situations happen.

Thanks,

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

Re: [Wikitech-l] Fwd: Lightning Talks August 25

[Pine W]

Ok, let's plan for Leigh and/or I to share the Tec de Monterrey video at
the lighning talks on August 25th if there are about 10 minutes available
after the tech-focused talks. Leigh might be available for an introduction
and/or questions.

Thanks,

Pine
On Aug 12, 2015 11:41 AM, "Rachel Farrand"  wrote:

> Hi Pine! I love the idea, so thanks for bringing it up. :)
>
> As I said in the email - it is not mandatory that the talks are tech
> related, however the point of these specific lightning talks are to be
> mostly tech related. Kevin, Megan and I are all very involved in Wikimedia
> Tech and are doing this specifically with the goal of spreading information
> about ongoing tech projects. We will probably give priority to tech focused
> talks for this series, but any extra space can go to whatever else wants to
> participate.
> If there is someone else (you!?) or another group who wants to run lighting
> with the purpose of a broader range of topics I will be happy and willing
> to share our lessons learned from these lightning talks. Keep in mind that
> this is only our second round of talks so we still have lots of room to
> learn, improve, document and change.
>
> A goal of mine is to start documenting the organization process and lessons
> from running these talks. Anything that gets written up will go here:
>
> https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Lightning_Talks
> There is already a small amount of info, but not much. Check back for
> updates! :)
>
> Hope this helps!
>
> On Wed, Aug 12, 2015 at 11:23 AM, Pine W  wrote:
>
> > Hi, nice idea. I'm just wondering if this concept could be expanded to be
> > more explicitly inclusive of other kinds of activities like L&E,
> education,
> > GLAM, Legal, Comms, Research, affiliates, etc. I think that this could
> > increase participation.
> >
> > Pine
> > On Aug 12, 2015 10:53 AM, "Rachel Farrand" 
> wrote:
> >
> > > We (Kevin Leduc, Megan Nestler and I) will be doing a second run of
> > > lightning talks <https://en.wikipedia.org/wiki/Lightning_talk> on
> August
> > > 25. The first round had about 40 people viewing living bother remotely
> > and
> > > in SF as well as another 45 views after the talks.
> > > ~ More logistic details/signups found in the email below ~
> > >
> > > These lightning talks are meant for anyone working on wikimedia tech
> and
> > > are not limited to WMF engineers. If you would like to do a lightning
> > talk
> > > on any project you are working on please feel free to sign up. Make
> sure
> > to
> > > include contact information (or email it to me) so that we (the
> lightning
> > > talk organizers) can coordinate with you. These lightning talks should
> be
> > > relevant to something related to our movement and will mostly be
> focused
> > on
> > > tech related projects however it is not mandatory that they are related
> > to
> > > tech.
> > >
> > > These talks will continue every month until there is no longer
> interest.
> > >
> > > A youtube stream will be sent out to this list just before the talks
> > start
> > > so you can follow along, you can ask questions on IRC, and the talks
> will
> > > also be recorded so that you can watch them whenever you like.
> > >
> > > We will adapt this process as we go to make it as interesting and
> useful
> > to
> > > everyone as we can.
> > >
> > > -- Forwarded message --
> > > From: Kevin Leduc 
> > > Date: Tue, Aug 11, 2015 at 6:26 PM
> > > Subject:
> > > To: wmf...@lists.wikimedia.org, Engineering list <
> > > engineer...@lists.wikimedia.org>
> > > Cc: Rachel Farrand , Megan Neisler <
> > > mneis...@wikimedia.org>
> > >
> > >
> > > Hello!
> > >
> > >
> > > The next round of Lightning Talks are in two weeks. This effort will
> not
> > > work without your participation...
> > >
> > > Lightning Talks are an opportunity for teams @ WMF & in the Community
> to
> > > showcase a Quarterly Goal acheived, significant milestone, release, or
> > > anything of significance to the rest of the foundation and the movement
> > as
> > > a whole. These talks will be open to our communities.
> > >
> > > Each presentation will be 10 minutes or less, the formal part should be
> > not
> > > be longer than 5 minutes and the remainder can be used for questions.
> > 

Re: [Wikitech-l] Code of conduct

[Pine W]

Yes, and it may be possible to have enough social support for netiquette
without resorting to written policies and enforcement procedures. I'd like
to think that this is true, but given examples about problematic activities
like personal attacks, I'm not sure. Is informal social pressure combined
with occasional admin or IRC op action enough to deal with those
situations, or do we need something more formal?

Pine


On Thu, Aug 13, 2015 at 2:34 PM, Vi to  wrote:

> But as a collaborative project a decent amount of netiquette is definitely
> needed.
>
>
> Vito
>
> 2015-08-13 23:30 GMT+02:00 rupert THURNER :
>
> > On Aug 13, 2015 10:16 PM, "Oliver Keyes"  wrote:
> > >
> > > On 13 August 2015 at 16:10, Antoine Musso  wrote:
> > > > Le 07/08/2015 02:17, Matthew Flaschen a écrit :
> > > >> We're in the process of developing a code of conduct for technical
> > > >> spaces.  This will be binding, and apply to all Wikimedia-related
> > > >> technical spaces (including but not limited to MediaWiki.org,
> > > >> Phabricator, Gerrit, technical IRC channels, and Etherpad).
> > > >>
> > > >> Please participate at
> > > >>
> >
> https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft
> > .
> > > >>  Suggestions are welcome here or at
> > > >>
> >
> >
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> > > >> .
> > > >
> > > > Hello Matt,
> > > >
> > > > It seems the code of conduct is fairly similar to the friendly space
> > > > policy. Though the later was meant for conferences, it can probably
> be
> > > > amended to be applied to cyberspace interactions.
> > > >
> > > > https://wikimediafoundation.org/wiki/Friendly_space_policy
> > > >
> > > > Do we have any examples of unfriendly behaviour that occurred
> recently?
> > > >
> > >
> > > The thread you are replying to contains both examples of unfriendly
> > > behaviour in a technical context and discussion over the direct
> > > applicability of the friendly spaces policy; reviewing it may be a
> > > good idea.
> >
> > Oliver,  I must be a little blind but I do not see examples of unfriendly
> > behaviour in this thread.
> >
> > In general,  Matt, I do experience that the wikimedia movement is
> > criticized having too many rules and policies. Add another one does not
> > help. At the end of the day your target group is code contributors,  not
> > policy readers. If somebody does not behave and not contribute,  the
> person
> > is easily shut up. If somebody contributes a lot, some diplomacy is
> > required. What you do here is, imho, an example of an organization busy
> > with itself. I won't be angry if you stop this thread and delete the wiki
> > page. Let me add,  I really appreciate and find very valuable all the
> other
> > technical contributions and discussions. And Matt, of course I appreciate
> > that you know what you are talking about beeing software and Wikipedia
> > content contributor.
> >
> > Best,
> > Rupert
> > ___
> > 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] Code of conduct

[Pine W]

Yeah, it seems to me that there's a choice here. Either have a policy with
an enforcement strategy and the social support for actually following
through with that enforcement strategy in a way that makes situations
better rather than more acrimonious, or don't have a written policy and let
nature take its course. Developing the former is a lot of work, and it's
going to be imperfect. The latter can be more chaotic and will also be
imperfect. So there's a choice of costs and benefits.

Pine


On Thu, Aug 13, 2015 at 2:30 PM, rupert THURNER 
wrote:

> On Aug 13, 2015 10:16 PM, "Oliver Keyes"  wrote:
> >
> > On 13 August 2015 at 16:10, Antoine Musso  wrote:
> > > Le 07/08/2015 02:17, Matthew Flaschen a écrit :
> > >> We're in the process of developing a code of conduct for technical
> > >> spaces.  This will be binding, and apply to all Wikimedia-related
> > >> technical spaces (including but not limited to MediaWiki.org,
> > >> Phabricator, Gerrit, technical IRC channels, and Etherpad).
> > >>
> > >> Please participate at
> > >>
> https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft
> .
> > >>  Suggestions are welcome here or at
> > >>
>
> https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft
> > >> .
> > >
> > > Hello Matt,
> > >
> > > It seems the code of conduct is fairly similar to the friendly space
> > > policy. Though the later was meant for conferences, it can probably be
> > > amended to be applied to cyberspace interactions.
> > >
> > > https://wikimediafoundation.org/wiki/Friendly_space_policy
> > >
> > > Do we have any examples of unfriendly behaviour that occurred recently?
> > >
> >
> > The thread you are replying to contains both examples of unfriendly
> > behaviour in a technical context and discussion over the direct
> > applicability of the friendly spaces policy; reviewing it may be a
> > good idea.
>
> Oliver,  I must be a little blind but I do not see examples of unfriendly
> behaviour in this thread.
>
> In general,  Matt, I do experience that the wikimedia movement is
> criticized having too many rules and policies. Add another one does not
> help. At the end of the day your target group is code contributors,  not
> policy readers. If somebody does not behave and not contribute,  the person
> is easily shut up. If somebody contributes a lot, some diplomacy is
> required. What you do here is, imho, an example of an organization busy
> with itself. I won't be angry if you stop this thread and delete the wiki
> page. Let me add,  I really appreciate and find very valuable all the other
> technical contributions and discussions. And Matt, of course I appreciate
> that you know what you are talking about beeing software and Wikipedia
> content contributor.
>
> Best,
> Rupert
> ___
> 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] Geohack tools

[Pine W]

It's great to hear that work is progressing on this.

I'd like to see more interactive features on pages, for example live air
traffic, ground traffic, and marine traffic data; and weather conditions.

Pine


On Fri, Aug 7, 2015 at 8:34 PM, Yuri Astrakhan 
wrote:

> Pine, you are right. That list is not very useful, and instead should look
> something like this:
>
> https://en.wikivoyage.org/wiki/Salzburg#Get_around
>
> The bad news is that the tile service it uses is hosted on labs, which
> means it cannot scale to the regular wikipedia-usage levels. Plus there
> might be a potential policy problem there - default lab-content loading on
> every page visit without user's consent.
>
> The good news is that we are very close to launching a full-blown WMF
> production-hosted tile service, based on the wonderful data from OSM.
>
> See general info and some ideas people have proposed -
> https://www.mediawiki.org/wiki/Maps  (feel free to add more)
>
>
> On Fri, Aug 7, 2015 at 11:23 PM, Gergo Tisza  wrote:
>
> > On Thu, Aug 6, 2015 at 11:01 PM, Pine W  wrote:
> >
> > > I just now realized how powerful these tools are when I started
> clicking
> > > around.
> > >
> > >
> > >
> >
> https://tools.wmflabs.org/geohack/geohack.php?pagename=File%3AWhite-cheeked_Starling_perching_on_a_rock.jpg¶ms=34.610576_N_135.540542_E_globe:Earth_class:object_&language=en
> > >
> > > Is there any chance of integrating some of these tools more directly
> onto
> > > Wikipedia pages, and into mobile web/mobile apps?
> > >
> >
> > There is an ongoing project
> > <https://phabricator.wikimedia.org/project/profile/1127/> to integrate
> > maps
> > into MediaWiki; that's probably the best place to catalog the use cases
> of
> > Geohack and decide which can and need to be supported by the new tools.
> > ___
> > 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] [Engineering] Code of conduct

[Pine W]

David's example is, unfortunately, probably a good one to keep in mind.

Regarding enforcement, WMF's traditional approach is that staff discipline
is handled on a track that's  independent of community enforcement actions,
and the WMF in-house actions are almost entirely opaque which is in
contrast to the more transparent process of community enforcement. Because
staff and community are comingling in these technical spaces, it may be
best to have more harmonious and more transparent linkage between community
and staff investigations and enforcement procedures. This might require the
involvement of WMF Legal and/or HR to sort out how this system will work.

For the purpose of developing enforcement procedures that will apply to
staff and to community members in similar if not identical ways, I would
like to suggest setting up a working group that includes WMF HR, WMF Legal,
WMF technical staff (broadly construed), community technical contributors
(broadly construed), and community admins and IRC ops who may be involved
in investigations and enforcement of this proposed code of conduct.
Enforcement in these circumstances is complicated, and I think that a
working group would be best positioned to propose a legally sound solution
for consideration by staff and community alike.

Pine
On Aug 12, 2015 3:42 PM, "David Gerard"  wrote:

> On 12 August 2015 at 23:00, Matthew Flaschen 
> wrote:
>
> > Enforcement is still to-be-determined.
>
>
> This does need to be sorted out ahead of time. Here's today's horrible
> example:
>
> http://kovalc.in/2015/08/12/harassers.html
>
>
> - d.
>
> ___
> 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