[Wikimedia-l] ACTRIAL Post-trial Research Report posted

2018-03-13 Thread Danny Horn
The Autoconfirmed article creation trial (also known as "ACTRIAL") has been
running on English Wikipedia for the last six months, starting in mid
September 2017. During the trial, article creation was limited to users
with autoconfirmed status, meaning they had made at least ten edits and the
account was at least four days old. Non-autoconfirmed users who tried to
create a new page were redirected to a landing page, which encouraged them
to create the page in the Draft namespace.

There's been a long-standing desire in the English Wikipedia community to
run ACTRIAL since 2011, and last year, the Wikimedia Foundation Community
Tech team worked on fulfilling this request.

The Community Tech team worked in partnership with community members from
English Wikipedia to set up ACTRIAL as a research project, measuring the
impact of the trial on three key areas: new editor activity and retention,
the quality control processes (particularly New Page Patrol and Articles
for Creation), and content quality.

Researcher Morten Warncke-Wang designed the study, collected and analysed
data, and has just published the ACTRIAL Post-trial Research Report on
English Wikipedia:

https://en.wikipedia.org/wiki/Wikipedia:Autoconfirmed_
article_creation_trial/Post-trial_Research_Report

The report presents the key findings, and makes suggestions for both the
Enwiki community and the Wikimedia Foundation to consider. We hope that
this report is a productive contribution to the ongoing discussions about
new users and quality control.

We're looking forward to seeing what people think about the findings, and
having lots more conversations about these issues. Please feel free to
comment on the report's talk page, or ping us in the on-wiki conversations,
wherever they emerge. :) Thanks!
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Wishlist Survey: Top 10 wishes of 2017!

2017-12-13 Thread Danny Horn
Hi everyone,

The Community Tech team is happy to announce the top 10 wishes from the 2017
Community Wishlist Survey!

More than 1,100 people participated in the survey this year -- proposing,
discussing and voting on 214 ideas. There was a two-week period in November
to submit and discuss proposals, followed by two weeks of support voting.
The top 10 proposals with the most support votes now become Community
Tech's backlog of projects to evaluate and address.

And here's the new top 10:

#1. Maps improvements (154 support votes)
#2. Ping users from the edit summary (127)
#3. Programs and events dashboard (111)
#4. Blame tool (110)
#5. Infobox wizard (106)
#6. Article Alerts for more languages (102)
#7. Auto-save edits (96)
#7. Thanks notification for log entries (tie, 96)
#9. SVG translation (94)
#10. Commons deletion notification bot (91)

You can see the whole list here, with links to proposals, project pages and
Phabricator tickets:
https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Results

So what happens next?

In 2018, the Community Tech team is responsible for investigating and
addressing the top 10 wishes. If there's a wish in the top 10 that we can't
work on, because it's unfeasible or because another group is working on it,
then we'll explain why we can't.

To get updates on our progress:

There are project pages for each of the top 10 wishes, which you can put on
your watchlist. We'll update them as the project progresses. (At time of
writing, these are just skeletons; actual information on each project is
still to come.) Feel free to post questions and suggestions on the project
talk pages: https://meta.wikimedia.org/wiki/Category:Community_Tech_-
_Current_projects

If you're familiar with the Phabricator ticketing system, the main Phab
task for each wish is noted on the Results page. You can also subscribe to
those tickets for updates.

We also publish several status reports through the year, to keep people
updated. You can watch the main Community Tech page for updates:
https://meta.wikimedia.org/wiki/Community_Tech

There are more questions and answers on the Wishlist Survey FAQ:
https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/FAQ

Thanks to everybody who proposed, discussed, debated and voted on ideas in
this year's Wishlist Survey!
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] 2017 Community Wishlist Survey starts today!

2017-11-06 Thread Danny Horn
Darn, that link is last year's. It should be:

https://meta.wikimedia.org/wiki/2017 Community_Wishlist_Survey
<https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey>

On Mon, Nov 6, 2017 at 11:42 AM, Danny Horn <dh...@wikimedia.org> wrote:

> Hi everyone,
>
> The third annual Community Wishlist Survey starts today, and you're
> invited to post proposals for projects that you'd like WMF's Community
> Tech team to work on:
>
> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey
>
> The Community Tech team builds features and makes changes that active
> Wikimedia contributors want, and the Wishlist Survey sets the team's
> agenda for the year.
>
> The Wishlist Survey starts with a two-week proposal period, when
> contributors from all Wikimedia projects are invited to post, discuss and
> improve propsals. After that, there's a two-week voting period, when
> everyone can post support-votes on the proposals that they think are
> worthwhile. We end up with a ranked list of wishes, measured by the
> participants' enthusiasm for each idea.
>
> Community Tech is responsible for addressing the top 10 wishes on the
> list, as well as some wishes from smaller groups and projects that are
> doing important work, but don't have the numbers to get their proposal into
> the top 10. The Wishlist is also used by volunteer developers and other
> teams, who want to find projects to work on that the community really
> wants.
>
> So I hope that everybody comes and participates; it's an opportunity to
> set the agenda for a Wikimedia Foundation product team.
>
> We would also ask that you help us spread the word. Please do post on your
> wikis and tell others this is happening, and that if they don't feel
> comfortable writing in English, proposals are welcome in any language.
>
> I hope to see everyone there!
>
> Danny Horn
> WMF Community Tech
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] 2017 Community Wishlist Survey starts today!

2017-11-06 Thread Danny Horn
Hi everyone,

The third annual Community Wishlist Survey starts today, and you're invited
to post proposals for projects that you'd like WMF's Community Tech team to
work on:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

The Community Tech team builds features and makes changes that active
Wikimedia contributors want, and the Wishlist Survey sets the team's agenda
for the year.

The Wishlist Survey starts with a two-week proposal period, when
contributors from all Wikimedia projects are invited to post, discuss and
improve propsals. After that, there's a two-week voting period, when
everyone can post support-votes on the proposals that they think are
worthwhile. We end up with a ranked list of wishes, measured by the
participants' enthusiasm for each idea.

Community Tech is responsible for addressing the top 10 wishes on the list,
as well as some wishes from smaller groups and projects that are doing
important work, but don't have the numbers to get their proposal into the
top 10. The Wishlist is also used by volunteer developers and other teams,
who want to find projects to work on that the community really wants.

So I hope that everybody comes and participates; it's an opportunity to set
the agenda for a Wikimedia Foundation product team.

We would also ask that you help us spread the word. Please do post on your
wikis and tell others this is happening, and that if they don't feel
comfortable writing in English, proposals are welcome in any language.

I hope to see everyone there!

Danny Horn
WMF Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Community Tech: 2016 Community Wishlist Survey status report

2017-10-05 Thread Danny Horn
Hi everyone,

We've published a status report on Community Tech's work for the year so
far, based on the 2016 Community Wishlist Survey:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Surv
ey/Status_report_1

I'll post the quick summary version here; there's lots more information on
the wiki page.

In the top 10...

Completed 5 wishes:

Wish #5: Rewrite XTools -- Live at xtools.wmflabs.org

Wish #6: Wikitext editor syntax highlighting -- Live as Beta feature on
left-to-right
language wikis. We’re still working on right-to-left languages.

Wish #7: Warning on unsuccessful login attempts -- Live on all wikis, see
Preferences/Notifications to change defaults.

Wish #9: Fix Mr. Z-bot's popular pages bot -- Live, see WikiProject
Spiders/Popular pages for an example.

Wish #10: User rights expiration -- Completed by volunteer developer This,
that and the other.

Currently working on 3 wishes:

Wish #2: Edit summary length for non-Latin languages -- MediaWiki Platform
team is deploying the necessary database changes. There are a few more
steps; we expect the wish to be completed by the end of the year.

Wish #3: Section heading URLs for non-Latin languages -- The work has
essentially been completed, but the changes will take a couple months to
propagate across all the pages. We expect to see the first changes in late
October, with everything completed by late November.

Wish #4: Global preferences -- Currently in active development; we expect
this to be completed by the end of the year.

Still investigating 2 wishes:

Wish #1: Global gadgets

Wish #8: Automatic archive for new external links

Projects for smaller groups:

There are also some non-wishlist projects that the Community Tech team has
been working on for smaller groups:

For Wikisource: Internet Archive Upload tool
For grant recipients: Grant metrics tool
For admins and checkusers: Range contributions
For admins: Cookie blocking
For English WP New Pages Patrol: ACTRIAL research, related to Wish #14:
Article Creation Workflow

That's the quick list; check out the status report for information on all
of these projects:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_
Survey/Status_report_1

<https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Status_report_1>
The 2017 Community Wishlist Survey will start on November 6th! Stay tuned
for more info about the new survey.


Danny Horn & Ryan Kaldari
Senior Product Manager & Senior Engineering Manager
WMF Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] New feature: LoginNotify

2017-08-24 Thread Danny Horn
The only log is a temporary debug log, which we're using to investigate
some bug reports. They're only accessible to people with shell access to
the production servers -- Foundation staff, and people who have signed
non-disclosure agreements. We won't retain them for longer than ninety
days.

Danny

On Thu, Aug 24, 2017 at 10:58 AM, Fæ  wrote:

> Neat feature.
>
> Who has access to the logs, and for how long will the logs be retained?
>
> Thanks,
> Fae
> https://meta.wikimedia.org/wiki/LGBT+
> http://telegram.me/wmlgbt
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] New beta feature: Syntax Highlighting!

2017-08-24 Thread Danny Horn
Hi Peter,

This is the first time I've heard about that happening, thanks for bringing
it up. Can you say more about what you're experiencing? I don't think
syntax highlighting gives an error message like that, so I'm not sure what
you mean.

Danny

On Thu, Aug 24, 2017 at 2:31 AM, Peter Southwood <
peter.southw...@telkomsa.net> wrote:

> Good news indeed.
> Is there a way we can stop it from crashing in mid edit and giving
> unhelpful advice like get a faster computer or a faster connection? I would
> not mind waiting a little longer for it to finish the job. It would be
> helpful if there were a user setting which allows longer wait time for
> those of us who cannot get a faster computer or connection for economic or
> geographical reasons.
> Cheers,
> Peter
>
> -Original Message-
> From: Wikimedia-l [mailto:wikimedia-l-boun...@lists.wikimedia.org] On
> Behalf Of Danny Horn
> Sent: Wednesday, 23 August 2017 8:41 PM
> To: Wikimedia Mailing List
> Subject: Re: [Wikimedia-l] New beta feature: Syntax Highlighting!
>
> Hi everyone,
>
> I've got some good news -- wikitext syntax highlighting is live again, and
> I'm almost completely sure it's staying live. :) You can now enable it as a
> Beta feature on all LTR wikis.
>
>
>
>
> On Thu, Aug 3, 2017 at 4:23 PM, Danny Horn <dh...@wikimedia.org> wrote:
>
> > Hi Andy,
> >
> > Thanks for sending your thoughts, that's the kind of feedback that we
> > need. People can either write responses in this thread, or post it on
> > the project's talk page:
> > https://meta.wikimedia.org/wiki/Talk:Community_Tech/
> > Wikitext_editor_syntax_highlighting
> >
> > We'll respond as comments come in, making bug fixes and then making a
> > plan for changes as we see what people have to say. Thanks again.
> >
> > Danny
> >
> >
> >
> > On Thu, Aug 3, 2017 at 4:07 PM Andy Mabbett
> > <a...@pigsonthewing.org.uk>
> > wrote:
> >
> >> On 3 August 2017 at 23:21, Danny Horn <dh...@wikimedia.org> wrote:
> >>
> >> > WMF's Community Tech team team is happy to announce that Wikitext
> >> > Editor Syntax Highlighting has been released as a beta feature
> >> > today on all LTR Wikimedia projects!
> >>
> >> I'm all in favour of having syntax highlighting - I teach people to
> >> edit wikicode, and I find it helps them to learn it more quickly.
> >>
> >> I've been using the syntax highlighting gadget  en.Wikipedia:
> >>
> >>https://www.mediawiki.org/wiki/User:Remember_the_dot/
> >> Syntax_highlighter
> >>
> >> for some time now. I've just disabled, it, and instead enabled the
> >> new beta feature.
> >>
> >> My first impression is that it is lacking in contrast - it's far
> >> harder, now, to differentiate the various types of content. Indeed
> >> the colour pairs used (e.g. #8800CC vs. #B3) fail WCAG web
> >> accessibility guidelines for colour contrast.
> >>
> >> I realise that choice of styling colours is a "bikeshed" matter, but
> >> contrast ratio is a quantifiable and objective accessibility issue.
> >>
> >> Also, because the script does not load immediately, the larger
> >> headings cause the page to "dance" as the script kicks in.
> >>
> >> What plans are there to either receive and act on feedback such as
> >> this, or to provide greater user-customisation options?
> >>
> >> ___
> >> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> >> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> >> wiki/Wikimedia-l New messages to: Wikimedia-l@lists.wikimedia.org
> >> Unsubscribe:
> >> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> >> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> >
> >
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com
>
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Global preferences: request for feedback

2017-08-23 Thread Danny Horn
Hi everyone,

The Community Tech team is currently working on Global preferences, the #4
wish from the 2016 Community Wishlist Survey, and we've got a question for
folks who are interested in using the feature.

We're adapting an extension developed by Legoktm, updating the code and
making some changes to the interface. There'll be a new special page,
Special:GlobalPreferences, where you'll be able to set a preference on all
wikis at once. There's more description and screenshots on the project
page:

https://meta.wikimedia.org/wiki/Community_Tech/Global_preferences

Our question is about how people might use local overrides for the global
preferences -- setting a preference as global, but making an exception for
one or more wikis. If that sounds like the kind of thing you would have an
opinion about :), then please check out this section:

https://meta.wikimedia.org/wiki/Community_Tech/Global_preferences#For_discussion:_Local_overrides

and leave some feedback on the talk page. Of course, you can also feel free
to post any questions, suggestions or comments about the feature. Thanks!

Danny Horn
Senior Product Manager
WMF Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] New beta feature: Syntax Highlighting!

2017-08-23 Thread Danny Horn
Hi everyone,

I've got some good news -- wikitext syntax highlighting is live again, and
I'm almost completely sure it's staying live. :) You can now enable it as a
Beta feature on all LTR wikis.




On Thu, Aug 3, 2017 at 4:23 PM, Danny Horn <dh...@wikimedia.org> wrote:

> Hi Andy,
>
> Thanks for sending your thoughts, that's the kind of feedback that we
> need. People can either write responses in this thread, or post it on the
> project's talk page: https://meta.wikimedia.org/wiki/Talk:Community_Tech/
> Wikitext_editor_syntax_highlighting
>
> We'll respond as comments come in, making bug fixes and then making a plan
> for changes as we see what people have to say. Thanks again.
>
> Danny
>
>
>
> On Thu, Aug 3, 2017 at 4:07 PM Andy Mabbett <a...@pigsonthewing.org.uk>
> wrote:
>
>> On 3 August 2017 at 23:21, Danny Horn <dh...@wikimedia.org> wrote:
>>
>> > WMF's Community Tech team team is happy to announce that Wikitext Editor
>> > Syntax Highlighting has been released as a beta feature today on all LTR
>> > Wikimedia projects!
>>
>> I'm all in favour of having syntax highlighting - I teach people to
>> edit wikicode, and I find it helps them to learn it more quickly.
>>
>> I've been using the syntax highlighting gadget  en.Wikipedia:
>>
>>https://www.mediawiki.org/wiki/User:Remember_the_dot/
>> Syntax_highlighter
>>
>> for some time now. I've just disabled, it, and instead enabled the new
>> beta feature.
>>
>> My first impression is that it is lacking in contrast - it's far
>> harder, now, to differentiate the various types of content. Indeed the
>> colour pairs used (e.g. #8800CC vs. #B3) fail WCAG web
>> accessibility guidelines for colour contrast.
>>
>> I realise that choice of styling colours is a "bikeshed" matter, but
>> contrast ratio is a quantifiable and objective accessibility issue.
>>
>> Also, because the script does not load immediately, the larger
>> headings cause the page to "dance" as the script kicks in.
>>
>> What plans are there to either receive and act on feedback such as
>> this, or to provide greater user-customisation options?
>>
>> ___
>> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
>> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
>> wiki/Wikimedia-l
>> New messages to: Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] New feature: LoginNotify

2017-08-18 Thread Danny Horn
Hi everyone,

The Community Tech team has released a new security feature this week:
LoginNotify, which gives you a notification when someone tries and fails to
log in to your account. This project was wish #7 on the 2016 Community
Wishlist Survey [1].

Here’s how it works:

If someone tries and fails to log in to your account from a device or an IP
address that hasn’t logged into your account recently, then you’ll get an
on-wiki notification at the first attempt. For a familiar device or IP
address, you’ll get an on-wiki notification after 5 failed logins. This is
on by default, but you can turn it off in your preferences; you can also
turn on email notifications.

It’s also possible to turn on email notifications when there’s a successful
login from a new device or IP address. This is turned off by default, but
it might be useful for admins or other functionaries who are concerned that
their user rights could be misused. This means that you’ll get a
notification every time you log in from a new device or IP address.

We want to take this opportunity to thank Brian Wolff for all his work in
writing the underlying extension for this feature.

There’s more information on the feature on the Community Tech project page
on Meta, and please feel free to post questions on the talk page:
https://meta.wikimedia.org/wiki/Community_Tech/LoginNotify

PS: If you’re wondering what happened to the Syntax Highlighting beta
feature that we deployed a couple weeks ago and then had to roll back:
it’ll be back soon!

[1]: 2016 Community Wishlist Survey:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] New beta feature: Syntax Highlighting!

2017-08-03 Thread Danny Horn
Hi Andy,

Thanks for sending your thoughts, that's the kind of feedback that we need.
People can either write responses in this thread, or post it on the
project's talk page:
https://meta.wikimedia.org/wiki/Talk:Community_Tech/Wikitext_editor_syntax_highlighting

We'll respond as comments come in, making bug fixes and then making a plan
for changes as we see what people have to say. Thanks again.

Danny



On Thu, Aug 3, 2017 at 4:07 PM Andy Mabbett <a...@pigsonthewing.org.uk>
wrote:

> On 3 August 2017 at 23:21, Danny Horn <dh...@wikimedia.org> wrote:
>
> > WMF's Community Tech team team is happy to announce that Wikitext Editor
> > Syntax Highlighting has been released as a beta feature today on all LTR
> > Wikimedia projects!
>
> I'm all in favour of having syntax highlighting - I teach people to
> edit wikicode, and I find it helps them to learn it more quickly.
>
> I've been using the syntax highlighting gadget  en.Wikipedia:
>
>https://www.mediawiki.org/wiki/User:Remember_the_dot/Syntax_highlighter
>
> for some time now. I've just disabled, it, and instead enabled the new
> beta feature.
>
> My first impression is that it is lacking in contrast - it's far
> harder, now, to differentiate the various types of content. Indeed the
> colour pairs used (e.g. #8800CC vs. #B3) fail WCAG web
> accessibility guidelines for colour contrast.
>
> I realise that choice of styling colours is a "bikeshed" matter, but
> contrast ratio is a quantifiable and objective accessibility issue.
>
> Also, because the script does not load immediately, the larger
> headings cause the page to "dance" as the script kicks in.
>
> What plans are there to either receive and act on feedback such as
> this, or to provide greater user-customisation options?
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] New beta feature: Syntax Highlighting!

2017-08-03 Thread Danny Horn
Oh, a PS: We're going to post an announcement on some village pumps, but
please feel free to share this with your community. Thanks!

On Thu, Aug 3, 2017 at 3:21 PM, Danny Horn <dh...@wikimedia.org> wrote:

> Hi everyone,
>
> WMF's Community Tech team team is happy to announce that Wikitext Editor
> Syntax Highlighting has been released as a beta feature today on all LTR
> Wikimedia projects!
>
> Syntax Highlighting was the #6 request in this year's Community Wishlist
> Survey [1]  -- a way to help editors parse the wikitext in the edit window
> by using color, bolding, italics and size to make it easier to see which
> parts are article text, and which are links, templates, tags and headings.
>
> It's easy to separate the link target from the actual link text, section
> headings are bigger, and adding bold and italics actually changes the way
> it looks in the edit window. Plus -- thanks to the amazing performance
> optimization done by volunteer developer Pastakhov -- it loads a lot faster
> than previous versions of syntax highlighting.
>
> Unfortunately, the feature isn't available in RTL languages yet; we're
> working on some bugs, and we'll release it as soon as we can. We're also
> hoping to improve the Syntax Highlighting performance for people who also
> use the "New wikitext mode" Beta feature.
>
> You can find Syntax Highlighting under the Beta features tab in
> Preferences. I hope you all love it and find it useful! If you've got
> feedback, you can click on the Discussion link in Beta features, or leave
> comments and questions on the Community Tech project talk page. [2] Thanks!
>
>
> Danny Horn
> Senior Product Manager
> WMF Community Tech
>
> [1] Community Wishlist Survey: https://meta.wikimedia.org/
> wiki/2016_Community_Wishlist_Survey/Results
>
> [2] Project talk page: https://meta.wikimedia.org/
> wiki/Talk:Community_Tech/Wikitext_editor_syntax_highlighting
>
>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] [Wikimedia Announcements] [PRESS RELEASE] Wikimedia Foundation receives $500, 000 from the Craig Newmark Foundation and craigslist Charitable Fund to support a healthy and inclusive

2017-01-27 Thread Danny Horn
Oh, that's a really good point. For the product analyst job, we're hoping
to hire someone who's already done research on online harassment, and can
help us to learn from other people's approaches.

Your idea for using aggression/harassment scores in admin applications is
really interesting; I hadn't thought of that before. Nothing's actually
planned right now, just research and conversations, but it's neat to see
people already coming up with interesting suggestions. :)



On Fri, Jan 27, 2017 at 9:17 AM, Lodewijk <lodew...@effeietsanders.org>
wrote:

> Thanks Danny for the elaboration.
>
> I don't want to contest the value of this work at all - sorry if that
> seemed implied. I think it's an effort that may be quite necessary -
> especially in some communities.
>
> The set of tools you're describing to be developed, seem all to be related
> to a process that eventually leads to blocking people off our sites. That
> is what triggered my response. This process may be necessary in a number of
> cases (unfortunately), and helpful for the community health. But it is all
> 'after the fact' - once harassment has taken place.
>
> What I am curious about, is whether there are also efforts ongoing that are
> focused on influencing community behavior in a more preventive manner. I'm
> not sure how that would work out in practice, I don't have the solution
> (although some ideas have been bouncing around). This work seems related to
> bullying in general - which happens unfortunately in schools and
> communities around the world - and research on this topic may help identify
> methods that could have a preventive effect. I have yet to see a 100%
> effective program, but it may strengthen the efforts for a healthier
> community.
>
> I can see that where these approaches are still investigated, or
> non-technical, the community tech team may be less suitable for
> implementing them. But I do want to express my hope that somewhere in the
> Foundation (and affiliates), work is being done to also look at preventing
> bullying and harassment - besides handling it effectively. And that you
> maybe keep that work in mind, when developing these tools. Some overlap may
> exist - for example, I could imagine that if the
> harassment-identificationtool is reliable enough, it could trigger warnings
> to users before they save their edit, or the scores could be used in admin
> applications (and for others with example-functions). A more social
> approach that is unrelated, would be to train community members on how to
> respond to poisonous behavior. I'm just thinking out loud here, and others
> may have much better approaches in mind (or actually work on them).
>
> Hope that clarifies a bit,
>
> Best,
> Lodewijk
>
> 2017-01-27 17:24 GMT+01:00 Danny Horn <dh...@wikimedia.org>:
>
> > The project has four focus areas, and blocking is just one of them.
> Here's
> > the whole picture:
> >
> > * Detection and prevention: Using machine learning to help flag
> situations
> > for admin review -- both text that looks like it's harassing and
> > aggressive, as well as modeling patterns of user interaction, like
> stalking
> > and hounding, before the situation gets out of control.
> >
> > * Reporting: Building a new system to encourage editors to reach out for
> > help, in a way that's less chaotic and stressful than the current system.
> >
> > * Evaluation: Giving admins and others tools that help them evaluate
> > harassment cases, and make good decisions.
> >
> > * Blocking: Making it more difficult for banned users to come back.
> >
> > We'll be actively working on all four areas. There aren't a ton of
> details
> > right now about exactly what we'll build, for a couple reasons. The
> product
> > manager and the analyst haven't started yet, and the research that they
> do
> > will generate a lot of new ideas and insights. Also, we're going to work
> > closely with the community -- talking to people with different roles and
> > perspectives, and making plans in collaboration with contributors who are
> > interested in these issues. So there's lots of work and thinking and
> > consulting to do.
> >
> > But here's one idea that I'm personally excited about, which I think
> helps
> > to explain why we're focusing on tools:
> >
> > Right now, when two people end up at AN/I, the only way to figure out
> whose
> > version of the story to believe is by looking at individual, cherrypicked
> > diffs. You can also look through the two editors' contributions, but if
> > they're both active editors and the problem has been going on for a
> while,
> > then it's very difficult to get a sense

Re: [Wikimedia-l] [Wikimedia Announcements] [PRESS RELEASE] Wikimedia Foundation receives $500, 000 from the Craig Newmark Foundation and craigslist Charitable Fund to support a healthy and inclusive

2017-01-27 Thread Danny Horn
The project has four focus areas, and blocking is just one of them. Here's
the whole picture:

* Detection and prevention: Using machine learning to help flag situations
for admin review -- both text that looks like it's harassing and
aggressive, as well as modeling patterns of user interaction, like stalking
and hounding, before the situation gets out of control.

* Reporting: Building a new system to encourage editors to reach out for
help, in a way that's less chaotic and stressful than the current system.

* Evaluation: Giving admins and others tools that help them evaluate
harassment cases, and make good decisions.

* Blocking: Making it more difficult for banned users to come back.

We'll be actively working on all four areas. There aren't a ton of details
right now about exactly what we'll build, for a couple reasons. The product
manager and the analyst haven't started yet, and the research that they do
will generate a lot of new ideas and insights. Also, we're going to work
closely with the community -- talking to people with different roles and
perspectives, and making plans in collaboration with contributors who are
interested in these issues. So there's lots of work and thinking and
consulting to do.

But here's one idea that I'm personally excited about, which I think helps
to explain why we're focusing on tools:

Right now, when two people end up at AN/I, the only way to figure out whose
version of the story to believe is by looking at individual, cherrypicked
diffs. You can also look through the two editors' contributions, but if
they're both active editors and the problem has been going on for a while,
then it's very difficult to get a sense of what's going on. Sometimes it
really matters who did what first, and you have to correlate the two
contributions logs, and pay attention to timestamps.

The idea is: build a tool that helps admins (and others) follow the "story"
of this conflict. Look for the pages where the two editors have interacted,
and show a timeline that helps you see what happened first, how they
responded, and how the drama unfolded. That could reduce the time cost of
investigating and evaluating considerably, making it much easier for an
admin or mediator to get involved.

There are lots of UI questions about how that would work and what it would
look like, but I don't think it would be too difficult on the tech side.
The information is already there in the contributions; it's just difficult
to correlate by hand.

Assuming it works, that tool could have a lot of good outcomes. Admins
would be more likely to take on harassment cases, because there'd be
greater return for the time investment. It would take some of the burden
off the target, so they don't have to figure out which individual diffs
they should provide in order to make their case. Also, it would be harder
for harassers to get away with mistreating people, because they wouldn't be
able to hide behind a smokescreen of random diffs.

As folks on this thread have said, there are lots of other components to
tackling the harassment problems. There will probably be groups of admins
and others who are especially interested in helping with the reporting and
evaluation, and the Foundation could provide trainings and resources for
those groups. Making changes to the reporting system will involve a lot of
community discussions about policies and competing values. Some of those
conversations and plans will probably be led by the Foundation, and some of
them will arise naturally within the community.

For this specific team -- the Community Tech product team, working with the
community advocate -- our focus is on doing research and building tools
that will support those conversations and plans. We're not going to take
over the community's proper role in setting policy, or making decisions
about how to handle cases.

To Fæ's point, the community will determine the social and cultural
decisions about how to treat harassment cases, and our team's job is to
build software that will help to put those decisions into practice.





On Fri, Jan 27, 2017 at 3:06 AM, Fæ  wrote:

> On 27 January 2017 at 09:21, Lodewijk  wrote:
> ...
> > Do I understand correctly that this particular initiative will focus on
> > fighting harassment, and not necessarily on preventing it? Basically in a
> > similar pattern that vandalism is fought on most wikipedia projects?
> >
> > I really hope that prevention, education and (social) training will
> become
> > a major point in the overall agenda, but I can imagine that we can't pay
> > all that from the single grant :) So I just would like to place it in the
> > proper context.
> >
> > Best,
> > Lodewijk
>
> +1 Spot on.
>
> The plan appears to hinge on blocks as the outcome. Based on cases of
> long term harassment targeted at individuals which invariably involved
> off-wiki doxxing or contacting friends and family members of their
> target, blocking 

[Wikimedia-l] Additional information on community health initiative and next steps

2017-01-26 Thread Danny Horn
Hello,

We have an update on the community health initiative mentioned following
the Board's Statement on Healthy Community Culture, Inclusivity, and Safe
Spaces.[1]

As Patrick Earley from the Support and Safety team noted on Wikimedia-l
last month[2], we’ve been developing a community health initiative to help
address the harassment issues discussed in the Board's statement. We
believe an important aspect of our efforts to combat harassment is
providing the volunteer community with better tools to more effectively
respond to instances of harassment as they arise.

We’re excited to announce that the Craig Newmark Foundation and craigslist
Charitable Fund have agreed to provide initial funding to help the
Wikimedia Foundation begin this work. The two seed restricted grants,
collectively a gift of $500,000, will enable the Foundation to scale up our
support of these efforts and provide us with the resources to do it right.

In preparing for this work, we’ve been discussing issues with the current
tools and processes with active administrators and functionaries. These
discussions have resulted in requested improvements in several key areas
where admins and functionaries see immediate needs—better reporting systems
for volunteers, smarter ways to detect and address problems early, and
improved tools and workflows related to the blocking process.

In the coming months, the Community Tech team, working with the Support and
Safety team, will be expanding their work on development of these tools.
The long-term goal for this effort is to build up the toolbox that
volunteers can use to combat harassment and other disruptive behavior on
our wikis.

Specifically, there are four areas where we think new tools will help:

1. Detection - Improve our detection and prevention tools, like
AbuseFilter, and build new features to detect aggressive behavior.

2. Reporting - Design ways to report harassment that are less chaotic, more
respectful of privacy, and less stressful than the current workflow.

3. Evaluating - Offer admins tools that make evaluating harassment reports
easier, so that they can make good decisions.

4. Blocking - When someone is blocked from the site, we can make it more
difficult for them to return under a different name or IP address.

Of course, these improvements need to be made with the participation and
support of the volunteers who will be using the tools. We don't want to
create new systems and workflows that create more work for an already
overburdened team of wiki administrators. We want to make these tasks less
grueling and able to more consistently produce effective outcomes.

Work in other areas - such as project policies and better training for
administrators and functionaries - still needs to be done in order to
comprehensively tackle the overall issue of harassment and harmful behavior
on the projects. However, we believe that improving and building better
tools for volunteers currently most engaged in this effort is a necessary
first step.

We welcome your feedback on this approach, and invite you to join us in
thanking Craig and his charitable organizations for their support of this
initiative!

We’ll be sharing regular updates about the progress of this work in the
coming months. If you have any questions in the meantime, please reach out
to us on the talk page of the Meta-Wiki page where you can find more
information: https://meta.wikimedia.org/wiki/Community_health_initiative

You can also find more details about this announcement in this blog post:
https://blog.wikimedia.org/2017/01/26/community-health-initiative-grant

Danny Horn (Product Manager, Community Tech) and Patrick Earley (Manager,
Support & Safety)

[1]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard/November_2016_-_Statement_on_Healthy_Community_Culture,_Inclusivity,_and_Safe_Spaces

[2]
https://lists.wikimedia.org/pipermail/wikimedia-l/2016-December/085668.html
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes of 2016!

2016-12-16 Thread Danny Horn
Yes, for sure. We don't want to impose anything on wikis that don't want or
can't use it.

On Fri, Dec 16, 2016 at 7:21 AM, pi zero  wrote:

> Just a general observation:  Making things "global" can be good or bad for
> non-wikipedia projects depending on how it's done; spreading uniformity
> across projects could also damage non-wikipedia projects by imposing
> inappropriate infrastructure.  I'm not totally cynical about the idea, just
> noting one needs to be careful.  (A case that comes to mind:  I use HotCat
> all the time on Wikinews, which in some important ways is as different from
> Wikipedia as a wiki can be, yet HotCat is atm inappropriate for Wikibooks
> and could cause problems there.)
>
> On Fri, Dec 16, 2016 at 12:05 AM, James Heilman  wrote:
>
> > Great to see so many that will benefit more than
> > just the EN WP community such as global gadgets, non-Latin language
> > improvements and global settings.
> >
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Wishlist Survey: Top 10 wishes of 2016!

2016-12-15 Thread Danny Horn
Hi everyone,

The Community Tech team is happy to announce the top 10 wishes from the
2016 Community Wishlist Survey!

More than 1,100 people participated in the survey this year -- proposing,
discussing and voting on 265 ideas. There was a two-week period in November
to submit and discuss proposals, followed by two weeks of support voting.
The top 10 proposals with the most support votes now become Community
Tech's backlog of projects to evaluate and address.

And here's the top 10:

#1. Global gadgets (91 support votes)
#2. Edit summary length for non-Latin languages (90)
#3. Section heading URLs for non-Latin languages (88)
#4. Global settings (84)
#5. Rewrite Xtools (84)
#6. Wikitext editor syntax highlighting (82)
#7. Warning on unsuccessful login attempts (73)
#8. Automatic archive for new external links (72)
#9. Fix Mr. Z-bot's popular pages report (72)
#10. User rights expiration (70)

You can see the whole list here, with links to proposals and Phabricator
tickets:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results

So -- who's going to work on all these wishes?

The Community Tech team is responsible for investigating and addressing the
top 10 wishes. If there's a wish in the top 10 that we can't work on,
because it's unfeasible or because another group is working on it, then
we'll explain what's happened.

Community Tech will also pick up some wishes below the top 10 that support
smaller user groups who are doing important work, but don't have the
numbers to vote a proposal all the way up to the top 10. This will apply to
some combination of: campaign and program organizers, GLAM participants,
stewards and CheckUsers, and people working on smaller projects or smaller
languages. We haven't determined which wishes we'll pick up yet; we'll be
talking about these as we get into 2017.

Also, some of these wishes will be granted by volunteer developers; the
Technical Collaboration team will help to connect volunteers with important
wishes that they can work on.

Some of these wishes are or will be on the roadmap for our colleagues on
the WMDE Technical Wishes team, and other Wikimedia Foundation product
teams.

To get updates on our progress:

There are project pages for each of the top 10 wishes, which you can put on
your watchlist. We'll update them as the project progresses. (At time of
writing, these are just skeletons; actual information on each project is
still to come.) Feel free to post questions and suggestions on the project
talk pages:
https://meta.wikimedia.org/wiki/Category:Community_Tech_-_Current_projects

If you're familiar with the Phabricator ticketing system, the main Phab
task for each wish is noted on the Results page. You can subscribe to those
tickets for updates.

We also publish several status reports through the year, to keep people
updated. You can watch the main Community Tech page for updates:
https://meta.wikimedia.org/wiki/Community_Tech

There are more questions and answers on the Wishlist Survey FAQ:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/FAQ

Thanks to everybody who proposed, discussed, debated and voted on ideas in
this year's Wishlist Survey, to everyone who's said nice things to us
recently, and to all people everywhere in time and space, on general
principles.
Danny Horn
Sr Product Manager, Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Voting on 2016 Community Wishlist Survey ends Monday

2016-12-08 Thread Danny Horn
Hi everyone,

There's just a few more days to vote on the 2016 Community Wishlist Survey,
to help determine what WMF's Community Tech team will be working on next
year:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

Everyone is invited to show your support for the features and changes that
you want to see. The top 10 proposals with the most support votes will be
Community Tech's to-do list for the year, and the wishes below the top 10
will be offered to other staff and volunteer developers as highly-valued
projects.

Voting ends on Monday at 23:59 UTC, so please come by and check it out
while there's still time to vote!

Danny Horn
Senior Product Manager, Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Voting's open on 2016 Community Wishlist Survey

2016-11-28 Thread Danny Horn
Hi everyone,

The voting has started on the 2016 Community Wishlist Survey, and all
Wikimedia contributors are invited to come and vote on the projects that
WMF's Community Tech team will work on next year:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

There are 267 proposals this year, on a wide range of subjects that I'm
pretty sure you have an opinion about.

You've got two weeks to vote, from now through December 12th. You can vote
for as many proposals as you like, by adding a {{support}} tag under the
proposals that you think are worthwhile.

Once the voting's over, we'll have a ranked list of projects for the
Community Tech team to work on, as well as other developers and volunteers
who want to build features and make changes that the core contributors
really want.

This is an opportunity for you to help set the agenda for a WMF product
team, so I hope everybody comes and participates!


Danny Horn
WMF Product Manager
Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] 2016 Community Wishlist Survey

2016-11-07 Thread Danny Horn
Hi everyone,

The second annual Community Wishlist Survey starts today, and you're
invited to post proposals for projects that you'd like WMF's Community Tech
team to work on:

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

The Community Tech team builds features and makes changes that active
Wikimedia contributors want, and the Wishlist Survey sets the team's agenda
for the year.

The Wishlist Survey starts with a two-week proposal period, when
contributors from all Wikimedia projects are invited to post, discuss and
improve propsals. After that, there's a two-week voting period, when
everyone can post support-votes on the proposals that they think are
worthwhile. We end up with a ranked list of wishes, measured by the
participants' enthusiasm for each idea.

Community Tech is responsible for addressing the top 10 wishes on the list,
as well as some top wishes from smaller groups and projects that are doing
important work, but don't have the numbers to get their proposal into the
top 10. The Wishlist is also used by volunteer developers and other teams,
who want to find projects to work on that the community really wants.

So I hope that everybody comes and participates; it's an opportunity to set
the agenda for a Wikimedia Foundation product team.

We would also ask that you help us spread the word. Please do post on your
wikis and tell others this is happening, and that if they don't feel
comfortable writing in English, proposals are welcome in any language.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Tech: Status report on Wishlist progress

2016-10-17 Thread Danny Horn
Hi everyone,

The WMF Community Tech team is starting to wrap up our work on this year's
Community Wishlist projects, as we prepare for the new Community Wishlist
Survey starting in November.

We've got a new Status report to share, with an update on the work that's
been done this year on the Community Wishlist:

https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_report_3

Here's a quick overview for the top 10 --

COMPLETED WORK on 5 wishes:

* Wish #1: Migrate dead external links to archives, with volunteer dev
Cyberpower678 -- currently on English Wikipedia, other languages coming

* Wish #2: Improved diff comparisons, by WMF developer MaxSem, live on all
wikis

* Wish #5: Numerical sorting in categories, currently on English, Swedish
and Macedonian Wikipedias, more languages coming soon

* Wish #7: Pageview stats tool, live on all wikis

* Wish #9: Improve the plagiarism detection bot, with volunteer dev Eran --
currently on  English Wikipedia, other languages coming

CURRENTLY WORKING on 1 wish:

* Wish #4: Cross-wiki watchlist, currently in progress

OTHER TEAMS ARE WORKING on 2 wishes:

* Wish #3: Central repository for gadgets, templates and Lua modules,
foundational work is underway by Legoktm

* Wish #6: Allow categories in Commons in all languages, related work is
underway by the Wikidata team

DECLINED 2 wishes:

* Wish #8: Global cross-wiki talk page

* Wish #10: Add a user watchlist

There's lots of information on the top 10, plus the work being done by
WMDE's Technical Wishes team and the Technical Collaboration team, on the
Status report page:

https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Status_report_3

And we hope that everyone will come and participate in the 2nd annual
Community Wishlist Survey, starting November 7th!

https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey

See you soon,

-- Danny

DannyH (WMF)
Senior Product Manager
WMF Community Tech Team
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Tech survey on watchlist use

2016-03-25 Thread Danny Horn
Hi everyone,

WMF's Community Tech team is starting to work on a Cross-wiki watchlist,
one of the top 10 wishes in the Community Wishlist Survey that we conducted
at the end of last year. [1]

We're running a survey on how people use their watchlists, to help inform
our work. If you've got a minute and want to share your thoughts, here's
the survey link:

https://wikimedia.qualtrics.com/SE/?SID=SV_1BRVhdayaTyuGJ7

The survey's hosted on a third-party service. We'll be running the survey
for about a week, and once it's closed, we'll publish aggregated results on
Meta.[2] Feel free to pass the link on, if you'd like to.

Let me know if you have any questions. Thanks!

Danny Horn

Product Manager, WMF Community Tech

[1] Info on the Community Wishlist Survey:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

Info on the Cross-wiki watchlist project:
https://meta.wikimedia.org/wiki/Community_Tech/Cross-wiki_watchlist

[2] Survey Privacy Statement:
https://wikimediafoundation.org/wiki/Survey_Privacy_Statement_for_March_2016_Watchlist_Survey
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Are we too rigid?

2016-02-23 Thread Danny Horn
If I remember correctly, I think that's how the Content Translation project
started -- it was someone's personal project, which got more people and
attention because it's a great idea and showed real success.

It's hard to know what the mechanism would be for how to gauge community
support at meaningful intervals. Most people aren't paying a lot of
attention to what the WMF is working on from one day to the next, and
there's only so many big surveys you can do before people get tired of
them. It's a tough problem.


On Tue, Feb 23, 2016 at 4:53 PM, Yuri Astrakhan 
wrote:

> Something in Oliver's departure email caught my eye:
>
>
> *  "Because we are scared and in pain and hindered by structural biases and
> hierarchy, we are worse at our jobs." (quoted with Oliver's permission)*
>
> And that got me thinking. WMF, an organization that was built with the open
> and community-driven principles - why have we became the classic example of
> a corporate multi-level hierarchy? Should we mimic a living organism rather
> than a human-built pyramid?
>
> This may sound naive and wishful, but could we have a more flat and
> flexible team structure, where instead of having large teams with
> sub-teams, we would have small self-forming teams "by interest".  For
> example, someone decides to dedicate their 20% to building support for
> storing 3D models in wiki. Their efforts are noticed, the community shows
> its support, and WMF reacts by increasing project resourcing. Or the
> opposite - the community questions the need of a project, and neither the
> team nor WMF can convincingly justify it - the project resources are
> gradually reduced.
>
> An organism reacts to the change of its environment by redistributing
> resources to the more problematic areas. Would small, flexible, and more
> focused teams achieve that better?
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Why we changed

2016-02-22 Thread Danny Horn
> Does anyone know when the board is meeting (has it met) to resolve this? I
> don't want them to rush a poorly thought-through decision but, after a
> while, inaction in a human crisis like this becomes negligent abuse.
>


Yeah, that happened four months ago. It's going great so far.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] An Open Letter to Wikimedia Foundation BoT

2016-02-20 Thread Danny Horn
You know, it's possible that the people who work for the Foundation might
understand the situation in a more nuanced way than you do. I know it
doesn't seem likely, but dare to dream.

On Sat, Feb 20, 2016 at 5:01 PM, Anthony Cole  wrote:

> Thanks James.
>
> I'm not on staff, nor am I part of the inner circle of volunteers in
> constant touch with staff or the board. From the perspective of the wider
> community, though, this all looks very dodgy. Lila's arrival marked for us
> a revolution in the relationship. There is probably nothing either of us
> can do to change our conflicting views.
>
> Most disturbing to me is the reappearance of some former C-level staff, who
> I (among many others) was delighted to see the back of, on this list and
> Wikipedia Weekly, positioning themselves for the new dawn. It's very
> unseemly seeing the people responsible for the shambles Lila inherited now
> lighting up the torches.
>
> On Sunday, 21 February 2016, James Alexander  wrote:
>
> > It is probably best for me not to get into a long count/counterpoint here
> > but I couldn't avoid not responding at all.
> >
> > As Ori hinted at I hope that everyone can reflect on the idea of
> causation
> > vs correlation
> > .
> The
> > fact that good things have happened is not necessarily because of, but
> > despite of, current leadership. There is no doubt that there have been a
> > lot of good things to occur in the past while but those are, very
> > frequently, because people have been freed up some to do what they want.
> A
> > lack of direction or clear strategy can, in fact, have good side effects
> if
> > you have amazing people on board because they're able to make decisions
> > they've wanted to make for a while. However at the same time it can drive
> > them insane as they strive to keep it on that track and to avoid the
> taking
> > crazy routes or stop leadership from making decisions they feel would
> > disrupt the projects and the movement too much or go against our morals.
> >
> > We have a lot of great new hires but much of that was driven by the good
> > people who already existed since it's the older ones who got into more
> > management type roles either officially or unofficially). Even at the
> > executive level it's telling that the 3 most long standing and solid
> > C-levels we have are all pre-lila appointees: Katherine (just before Lila
> > but still before), Lisa and Geoff. Our cycle of c-level replacements
> since
> > then have been both hires and departures (with, unfortunately, less hires
> > then departures still) including multiple short term hires (in roles that
> > are traditionally very long term).
> >
> > I am not going to pretend I agreed with Sue at all times, or that every
> > decision she made was right however I at least felt like I knew what they
> > were (In fact I strongly disliked her strategy believing it bad for the
> org
> > and the movement, but again, I felt I knew what it was/understood it).
> > However I am also not going to accept the idea that Lila has made this
> > place so much better. As someone who saw them happen internally I don't
> > think her finger prints are really on any of the things you mention, they
> > were all 'despite' not 'because' of her and so much more could have been
> > done and wanted to be done. Slight exception possibly for the FDC bit but
> > that happened after all of this started exploding internally in the past
> > couple months and so she knew that she had  no trust left internally and
> > all of the staff close to it basically said "we can not defend you on
> this
> > if you don't go the FDC" so I still don't really see it as a proactive
> > choice on her front.
> >
> > James
> > [[User:Jamesofur]]/[[User:Jalexander-WMF]]
> >
> > Personal capacity, as signaled by my email address, but since some
> complain
> > I don't make it clear my role in WMF when I send this type of email: I am
> > also the Manager of Trust & Safety
> >
> > On Sat, Feb 20, 2016 at 3:18 PM, Anthony Cole  > > wrote:
> >
> > > I know.
> > >
> > > Anthony Cole
> > >
> > >
> > > On Sun, Feb 21, 2016 at 7:17 AM, Brion Vibber  > >
> > > wrote:
> > >
> > > > On Sat, Feb 20, 2016 at 2:56 PM, Anthony Cole  > >
> > > wrote:
> > > >
> > > > > * The Community Resources Team is in place - it surveyed the
> > community
> > > > and
> > > > > discussed with them their technical priorities, and tailored their
> > Idea
> > > > Lab
> > > > > Campaign accordingly.
> > > > >
> > > >
> > > > FYI, the head of that team is one of those who resigned last week:
> > > >
> > >
> >
> https://lists.wikimedia.org/pipermail/wikimedia-l/2016-February/081809.html
> > > >
> > > > -- brion
> > > > ___
> > > > Wikimedia-l mailing list, guidelines 

[Wikimedia-l] Community Wishlist Survey: Status report #1

2016-01-20 Thread Danny Horn
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: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes!

2015-12-28 Thread Danny Horn
Henning,

If we're going to solve the problem of dead links, it needs to involve
automation, at least for the heavy lifting. Obviously, if a human
contributor can add a better source, that's great. But there are more dead
links than people willing to replace them.

On English Wikipedia, there's Category:All articles with dead external
links, and it contains more than 134,000 articles[1] -- and those are just
the pages where somebody's added the Dead link template. There are a lot of
missing references -- not just on English WP, but on all the projects --
and connecting those links to a live archive makes them useful again.

For links that were moved, we may be able to collect and use that
information -- I know that we're looking into what kind of metadata we can
collect when a new link is added to the page. But I think finding
alternative sources has to come from human contributors, and that's hard to
scale.

Danny
PM, Community Tech

[1]:
https://en.wikipedia.org/wiki/Category:All_articles_with_dead_external_links



On Mon, Dec 28, 2015 at 9:51 AM, Henning Schlottmann <h.schlottm...@gmx.net>
wrote:

> On 16.12.2015 21:12, Danny Horn wrote:
>
> > #1. Migrate dead links to the Wayback Machine  (111 support votes)
>
> I really hope, you don't follow that wish, as it is detrimental to the
> quality of Wikipedia.
>
> Switching dead links to the archive is a move to a dead end, instead of
> looking for
>
> a) the new correct URL, as many links were just moved.
> b) alternative sources for the same fact.
>
> Ciao Henning
>
>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes!

2015-12-17 Thread Danny Horn
Yes, if there are wishes that we can't work on -- or we can only do one
part of a larger wish -- then it's our team's responsibility to really
think it through, and report back to the community about it.

We're planning to have some checkpoints through the year, where we'll give
a report on how things are going. The first one is going to be at the
Wikimedia Developers Summit in the first week of January, and after the
Summit we'll publish the information, including notes from the
conversations that we have at the event.

Then there are other Wikimedia events that we can use as checkpoints -- the
Hackathon in April, Wikimania in June -- so that we can keep people updated
about how things are going.

We're also keeping our notes on a Meta page, so interested people can
follow along if they like --
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10

Right now, that's just notes from some preliminary assessment meetings, so
it's not particularly thrilling, but ideas will get more concrete as we go.

I'm glad people are excited about this year; we are too.


On Wed, Dec 16, 2015 at 7:01 PM, Lane Rasberry <l...@bluerasberry.com>
wrote:

> Wow!
>
> I have strong opinions about everything on this list and apparently so do
> many other people.
>
> It was fun to participate in the proposal process.
>
> If any of these proposals are not feasible to develop then I would enjoy
> reading a short explanation explaining why from the perspective of a
> developer to a layman audience.
>
> The entire list seems like magic to me - it is so many things that I want.
>
> yours,
>
>
> On Wed, Dec 16, 2015 at 8:24 PM, Sam Klein <sjkl...@hcs.harvard.edu>
> wrote:
>
> > Thanks to all for organizing the survey and for sharing!
> >
> > A lot of these should help people stay in touch on smaller wikis and
> > sibling projects where they are less active (and currently less likely to
> > see pings and messages), so while I also want to see wikisource take over
> > the world, these seem like great choices.
> >
> > It's wonderful to see a cross-organization collaboration topping the
> list.
> >
> > Slow migration back to a single unified namespace:
> > #3. Central global repository for templates, gadgets and Lua
> > #4. Cross-wiki watchlist
> > #8. Cross-wiki user talkpage
> >
> > And a mentor-friendly feature I've wanted for a long time:
> > #10. Add a user watchlist
> >
> > SJ
> >
> >
> > On Wed, Dec 16, 2015 at 3:12 PM, Danny Horn <dh...@wikimedia.org> 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 othe

[Wikimedia-l] Community Wishlist Survey: Top 10 wishes!

2015-12-16 Thread Danny Horn
 can watch this page for further Community Tech announcements:
https://meta.wikimedia.org/wiki/Community_Tech/News

Thanks!

Danny Horn
Product Manager, WMF Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] [Wmfall] Community Wishlist Survey: Top 10 wishes!

2015-12-16 Thread Danny Horn
Yeah, we've been thinking about the best way to support the smaller
projects. For this first survey, we wanted to see what happened when we
just open the voting as wide as we can, and encourage people from smaller
projects to participate and spread the word.

The Wikisource community did a tremendous job in showing up and giving
support to the Wikisource proposals. The top wishes in that category got 41
and 39 votes, which is really impressive considering the relative size of
the projects.

The discussion on using Google's OCR in Indic language Wikisource is
especially interesting -- a lively debate about finding the right solution
to what is clearly a deeply-felt need from a community that's working
really hard to add their languages' knowledge to the movement. I hope that
having that debate here is a step towards a larger discussion about how we
can support Wikisource projects.



On Wed, Dec 16, 2015 at 12:39 PM, Risker <risker...@gmail.com> wrote:

> Thanks, Danny - this looks like a pretty good list.
>
> Every one of the top-10 proposals is worthwhile all by itself, and a couple
> of them have the potential to have multi-project effects; I'm not
> suggesting that they be set aside.  However, I'd like to suggest that at
> the next selection process, a slot be specifically reserved for a project
> on one of the less populous projects.  The system of selecting the most
> popular options almost guarantees that something to improve (for example)
> Wikisource or Wiktionary will be an also-ran, simply because there aren't
> enough members of those specialized communities to out-vote the really
> popular things from Wikipedia. This can lead to the circular effect of
> small projects having a hard time expanding their community because of
> technical weaknesses which don't get fixed because there isn't a big enough
> community to vote to get them to the top of the community tech wishlist...
>
> Nonetheless, this is a great first attempt at actively involving
> communities in determining priorities for this specific WMF team. I hope
> that the WMF staff involved have also felt the process was worthwhile, and
> I'll really be looking forward to the viability assessments.
>
> Risker/Anne
>
> On 16 December 2015 at 15:22, Toby Negrin <tneg...@wikimedia.org> 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 <dh...@wikimedia.org>
> 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?
> >

[Wikimedia-l] Community Tech: November report

2015-12-09 Thread Danny Horn
Hi everyone, here's what the Community Tech team's been up to lately.

* Community Wishlist Survey: we've been running this survey to identify the
most important features and fixes to work on in 2016; you might have heard
about it because we've been spamming mailing lists and village pumps. If
you haven't checked it out yet -- the voting phase ends on Monday, please
come and vote for the proposals you want to support! There are a lot of
proposals, and many of them are awesome.
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

* Gadgets 2.0: A new Gadget Manager has been in the works for a long time,
to replace Mediawiki:Gadgets-definition as the interface for managing
gadgets on a wiki. Community Tech is helping to complete the feature -- in
November, we created new Gadget and Gadget_definition namespaces and
content models, and we're currently working on the Gadget Manager itself.
For more info: https://www.mediawiki.org/wiki/Gadgets_2.0 and
https://phabricator.wikimedia.org/T31272.

* GadgetUsage: We made some improvements to the Special:GadgetUsage report,
filtering out removed gadgets and adding a recently active users count. You
can see the improved report at
https://www.mediawiki.org/wiki/Special:GadgetUsage, and it'll roll out to
more projects next week.

* Citation bot: We've been working on getting Citation bot into shape;
check out https://phabricator.wikimedia.org/T108412 for more.

In December, we've got more work coming up on Gadget Manager, Citation bot
and storing WikiProject article assessment metadata. Plus come and vote in
the Wishlist Survey so that we have interesting things to work on in
January. Thank you and good night.

DannyH (WMF)
Community Tech



(cross-posted to Wikimedia-l, Wikitech-l and WMF staff lists, sorry for the
duplication)
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Wishlist Survey - voting open

2015-11-30 Thread Danny Horn
Hi everyone,

The Community Tech team's Wishlist Survey is now open for voting; come on
over and upvote your favorites. We're looking for the most important
features and fixes that our team can work on to help the core contributors
on Wikimedia projects.

https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

We've got more than 100 proposals to choose from, organized on
easy-to-browse category pages. As a taster, some of the contenders include:

* Improve diff compare screen
* Migrate dead links to the Wayback Machine
* Enhanced per-user, per-article blocking
* Cite : Share : Export tools
* Improve SVG rendering
* Cross-wiki watchlists
* Pageview Stats tool

And if anything on that list makes you excited, outraged or -- well,
honestly, any reaction besides a blank stare -- then you need to come and
vote for the ideas you like best. Once the voting is over, the prioritized
list becomes the Community Tech's backlog of projects to investigate and
address.

We'll be posting invites to as many village pumps as we can find tomorrow,
to make sure that everyone has the chance to vote. All of the voting pages
are marked for translation, and we would welcome any volunteers to help
translate a proposal into a language of their choice.

Thanks for checking it out; I'm looking forward to seeing your votes.

Danny

Product Manager, WMF Community Tech


(I'm cross-posting this to Wikimedia-l, Wikitech-l, and the WMF staff list
-- apologies to people who subscribe to all three for the duplicate spam.)
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Wishlist Survey - proposals phase ending soon

2015-11-19 Thread Danny Horn
Hi everyone,

There's just a few more days to add proposals on the Community Tech team's
Wishlist Survey. We're looking for the most important features and fixes
that our team can work on to help the core contributors on Wikimedia
projects.

https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

We've got about 140 proposals so far, which is clearly not enough, because
there's a very good chance that we don't have yours yet. You can submit
your proposal on the survey page, and you can discuss and endorse other
people's proposals too.

The proposal phase ends on Monday, and then we'll open voting on the
proposals a week later, on November 30th.

Thanks for checking it out; I'm looking forward to seeing your ideas.

Danny

Product Manager
WMF Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Community Tech: October report

2015-11-03 Thread Danny Horn
In the Community Tech team, we're constantly striving to make the world
better by creating helpful things and fixing unhelpful things. We're
basically superheroes, and we wear capes at all times. Here's what we've
been up to this month.
* We built a new Special:GadgetUsage report that's live on all wikis; it
lists gadgets used on the wiki, ordered by the number of users. Not to be
clickbait or anything, but THE RESULTS WILL SHOCK YOU. Check it out at
https://commons.wikimedia.org/wiki/Special:GadgetUsage or your own favorite
wiki.

* HotCat is one of the most popular gadgets -- see: GadgetUsage report
above -- which helps people remove, change and add categories. We fixed
HotCat on over 100 wikis where it was broken, including Wikipedias in
Egyptian Arabic, Ripuarian, Buginese and Navajo, and five projects in Farsi
-- Wikinews, Wikiquote, Wikisource, Wikivoyage and Wiktionary. You're
welcome, Farsi! (More info on https://en.wikipedia.org/wiki/Wikipedia:HotCat
)

* CitationBot is a combination tool/on-wiki gadget that helps to expand
incomplete citations. We got it running again after the https change,
updated it, and fixed some outstanding bugs, including handling multiple
author names. (See http://tools.wmflabs.org/citations/doibot.html for more
info.)

* We also built a prototype of a new tool called RevisionSlider, which
helps editors navigate through diff pages without having to go back and
forth to the history page. The prototype is live now on test.wp, and we'd
love to get your feedback -- visit
https://meta.wikimedia.org/wiki/Community_Tech/RevisionSlider

Coming up in November:
* We're starting a big cross-project Community Wishlist Survey on November
9th, inviting contributors from any wiki to propose and vote on the
features and fixes they'd like our team to work on. The survey page is on
Meta, at https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey --
please join us there on Monday to add your proposals.

* While that's going on, we're currently considering work in a few
different areas, including completing Gadgets 2.0 and building some modules
to help WikiProjects.

You can keep track of what we're working on by watching Community Tech/News
on Meta: https://meta.wikimedia.org/wiki/Community_Tech/News -- and feel
free to leave questions or comments on the talk page. Thanks!


DannyH (WMF)

Community Tech
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Collaboration team reprioritization

2015-09-05 Thread Danny Horn
We are planning to put Flow into public dumps this month, and work with all
the remaining communities still using LQT about converting to Flow. I
wanted to let this announcement settle for a minute before we talk to them.

On Fri, Sep 4, 2015 at 10:23 PM, John Mark Vandenberg 
wrote:

> On Sat, Sep 5, 2015 at 12:37 PM, MZMcBride  wrote:
> > Amir E. Aharoni wrote:
> >>Much more importantly, Flow very much does cover basic talk pages. You
> can
> >>write a title and an OP and get people to reply. This has been working
> for
> >>many months already. This is my definition of "covering basic talk
> pages".
> >>
> >>Even more importantly is that you can write a title and an OP and get
> >>people to reply ON THEIR PHONES. This is nearly impossible on the classic
> >>talk pages; on them you are lucky to even manage to read the existing
> >>discussions, and typing a reply requires extra finger-acrobatics. With
> >>Flow it's as easy as on Twitter. I do almost no coding for Mobile
> >>Frontend and apps, but I'm a kind of a volunteer mobile technologies
> >>ambassador in my home wiki, and good mobile support for talk pages is the
> >>#1 request that I hear from veteran editors with regards to using
> >>Wikipedia on their phones. This is another thing that Flow has been doing
> >>for many months already.
> >
> > I think most of the points you raise here are true of LiquidThreads or
> > _any_ prototype of a discussion system. Yes, you get a reply button
> > instead of needing ":: " wikitext. That's great, I agree, but after
> > having watched LiquidThreads rot and then seeing a lot of time, money,
> and
> > effort put into Flow, I'm pretty dissatisfied with the deliverable being
> > essentially a very intricate proof-of-concept. I think not getting Flow
> > fully deployed to Wikimedia wikis is objectively a large failure to
> > deliver. Consequently, it seems most prudent to be asking what went wrong
> > and how it will be better next time. The underlying reality is that we
> > still need a better on-wiki discussion system and it now looks like
> > neither LiquidThreads nor Flow are going to be it.
>
> In addition to this, we still have LiquidThreads (LQT) in production.
>
> I can understand Flow being put into maintenance mode, especially if
> temporarily while energy is focused elsewhere, but I believe the main
> Flow project should at least include:
>
> 1. dumping Flow content into the public dumps (
> https://phabricator.wikimedia.org/T89398 ), and
>
> 2. decommissioning LiquidThreads on all Wikimedia sites by converting
> them to Flow
>
> According to Wikiapiary [1] , there are still seven 'active' WMF sites
> using LiquidThreads.
>
> I see LQT is still actively being used on five of them:
>
>
> https://en.wikinews.org/w/index.php?title=Special:RecentChanges=30==90
>
>
> https://en.wiktionary.org/w/index.php?title=Special:RecentChanges=30==90
>
>
> https://pt.wikibooks.org/w/index.php?title=Especial:Mudan%C3%A7as_recentes=30==90
>
>
> https://fi.wikimedia.org/w/index.php?title=Toiminnot:Tuoreet_muutokset=30==90
> (conversion to Flow requested: T104089)
>
>
> https://se.wikimedia.org/w/index.php?title=Special:Senaste_%C3%A4ndringar=30==90
> (conversion to Flow requested: T106302)
>
> But no Thread: activity on two others:
> http://hu.wikipedia.org/
> (They are trialling Flow? T107301)
> http://sv.wikisource.org/
>
> It is also installed on two locked projects: Wikimania 2010, and
> Wikimedia Strategic Planning.  Can't they be converted to Flow ?
>
> And it is still installed on https://www.mediawiki.org/ .  Is that
> still necessary?
>
> Is the current plan simply "let users request LiquidThreads pages be
> converted to Flow"?
>
> Which of the above sites are only using it in user talk?
>
> Have any of the above sites affirmatively decided they do not want to
> switch to Flow (yet)?
> If so, what are their reasons?
>
> 1.
> https://wikiapiary.com/w/index.php?title=Special:Ask=0=20=[[Has+extension%3A%3AExtension%3ALiquid+Threads]]=format%3Dtable%2Flink%3Dall%2Fheaders%3Dshow%2Fmainlabel%3D-2D%2Fintro%3D-3Cb-3EThis-20extension-20is-20in-20use-20on-20the-20following-20websites%3A-3C-2Fb-3E-3Cbr-20-2F-3E%2Fsearchlabel%3D%E2%80%A6-20further-20results%2Fdefault%3DThis-20extension-20is-20no-20longer-20in-20use-20on-20any-20website.%2Fclass%3Dsortable-20wikitable-20smwtable=%3FHas+website%3DWiki+name%0A%3FHas+MediaWiki+version%3DMediaWiki+version%0A%3FHas+extension+version%3DExtension+version%0A=Has+MediaWiki+version=descending%2Crand=no
>
> --
> John Vandenberg
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 

Re: [Wikimedia-l] To Flow: on featured article discussions

2014-09-16 Thread Danny Horn
Diego, that is definitely what we're thinking about for the subscriptions
options -- giving users the ability to choose whether they want to
subscribe to every new thread, or just get a notification that a new thread
has been created. The balance that we have to figure out is how to provide
options on that page-by-page level without forcing people to go through two
clicks every time.

Right now, the list of items on the roadmap is on the Mediawiki Flow page.
[1] We're not enforcing a strict centralized place for discussions right
now; they're happening in a few different places. I'm going to be talking
with the Community team later this week to see what we can do about that. I
think the EE mailing list [2] is probably the best place to see what's
current and talk with the team.

We'll probably be tackling the subscription/notifications question in more
detail in a few weeks. Right now, we're working on Hide, the Table of
Contents, Search and the LiquidThreads transition. There's a lot to do! But
we'll definitely be getting back to notification options before too long.

Danny

[1]: Mediawiki Flow page: https://www.mediawiki.org/wiki/Flow#Roadmap
[2]: EE mailing list: https://lists.wikimedia.org/mailman/listinfo/ee

On Tue, Sep 16, 2014 at 3:51 AM, Diego Moya dialm...@gmail.com wrote:

 On 15 September 2014 19:24, Danny Horn dh...@wikimedia.org wrote:
  Some people are seeing Flow messages as really important, something that
  they want to get updates on right away -- and right away can mean
 either
  in their watchlist where they go all the time, or in Echo where they'll
 see
  the notification. Other people see Flow messages as something they'll get
  to later, and they want to see more of a message inbox.

 And then you have people like me who see them as *both*, just not for
 the same pages. I've suggested that some topics and boards should
 raise notifications and not others, depending on how important each
 topic is for the user.

 At least one other editor suggested that this could be done with a
 check (notify me of updates for this board) to be selected on the
 pop-up that appears when you add a topic to your watchlist. Is there
 someone taking note of all these scattered suggestions in a central
 place where they can be discussed?

 ___
 Wikimedia-l mailing list, guidelines at:
 https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
 Wikimedia-l@lists.wikimedia.org
 Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
 mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] To Flow: on featured article discussions

2014-09-15 Thread Danny Horn
Figuring out how Flow integrates with the watchlist and Echo is one of the
toughest and most important parts of the project. The feedback that the
team got from the last couple releases was actually pretty diverse, and
showed us that there's going to be a lot of work ahead of us to figure out
how to represent Flow activity.

Some people are seeing Flow messages as really important, something that
they want to get updates on right away -- and right away can mean either
in their watchlist where they go all the time, or in Echo where they'll see
the notification. Other people see Flow messages as something they'll get
to later, and they want to see more of a message inbox.

The interesting thing for me is that this doesn't seem to break down along
new user vs power user lines. People with the same level of experience
and activity can still use and think about those tools differently.

The work that we've done on the Flow/Echo/watchlist integration so far is
just a couple steps into what is going to be a longer process. We need to
build more options into the feature to help people choose what kind of
notifications they want to see, and where.

Danny



On Mon, Sep 15, 2014 at 7:55 AM, Diego Moya dialm...@gmail.com wrote:

 On 15 September 2014 15:24, Amir E. Aharoni
 amir.ahar...@mail.huji.ac.il wrote:
  That is quite true. A deep modernization of the Watchlist should be
 coupled
  with the Flow poject somehow. Either Special:Watchlist itself should be
  profoundly redesigned and upgraded, or the Flow+Echo notifications should
  become so good that they can replace it.
 

 Whatever you do, please don't try to replace the Watchlist with Echo
 notifications; they serve quite different roles and are complementary,
 not a surrogate.

 The recent backlash that Echo received when it was updated last week
 was in part because of that, as it included as notifications all the
 updates that would normally be seek out at the watchlist and therefore
 shouldn't generate an alert.

 I agree that the Watchlist could be enhanced with more granular
 filters, groupings and search functions. A lot of user workflows are
 based on personal usages of the watchlist, which work as the de-facto
 coordination tool between editors participating in the same projects.

 ___
 Wikimedia-l mailing list, guidelines at:
 https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
 Wikimedia-l@lists.wikimedia.org
 Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
 mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe