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

[Toby Negrin]

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  wrote:

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

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

[Danny Horn]

Hi everyone,

I'm happy to announce that the Community Tech team's Community Wishlist
Survey has concluded, and we're able to announce the top 10 wishes!

634 people participated in the survey, where they proposed, discussed and
voted on 107 ideas. There was a two-week period in November to submit and
endorse proposals, followed by two weeks of voting. The top 10 proposals
with the most support votes now become the Community Tech team's backlog of
projects to evaluate and address.

And here's the top 10:

#1. Migrate dead links to the Wayback Machine  (111 support votes)
#2. Improved diff compare screen  (104)
#3. Central global repository for templates, gadgets and Lua modules  (87)
#4. Cross-wiki watchlist  (84)
#4. Numerical sorting in categories  (84)
#6. Allow categories in Commons in all languages  (78)
#7. Pageview Stats tool  (70)
#8. Global cross-wiki user talk page  (66)
#9. Improve the "copy and paste detection" bot  (63)
#10. Add a user watchlist  (62)

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

So what happens now?

Over the next couple weeks, Community Tech will do a preliminary assessment
on the top 10, and start figuring out what's involved. We need to have a
clear definition of the problem and proposed solution, and begin to
understand the technical, design and community challenges for each one.

Some wishes in the top 10 seem relatively straightforward, and we'll be
able to dig in and start working on them in the new year. Some wishes are
going to need a lot of investigation and discussion with other developers,
product teams, designers and community members. There may be some that are
just too big or too hard to do at all.

Our analysis will look at the following factors:

* SUPPORT: Overall support for the proposal, including the discussions on
the survey page. This will take the neutral and oppose votes into account.
Some of these ideas also have a rich history of discussions on-wiki and in
bug tickets. For some wishes, we'll need more community discussion to help
define the problem and agree on proposed solutions.

* FEASIBILITY: How much work is involved, including existing blockers and
dependencies.

* IMPACT: Evaluating how many projects and contributors will benefit,
whether it's a long-lasting solution or a temporary fix, and the
improvement in contributors' overall productivity and happiness.

* RISK: Potential drawbacks, conflicts with other developers' work, and
negative effects on any group of contributors.

Our plan for 2016 is to complete as many of the top 10 wishes as we can.
For the wishes in the top 10 that we can't complete, we're responsible for
investigating them fully and reporting back on the analysis.

So there's going to be a series of checkpoints through the year, where
we'll present the current status of the top 10 wishes. The first will be at
the Wikimedia Developer Summit in the first week of January. We're planning
to talk about the preliminary assessment there, and then share it more
widely.

If you're eager to follow the whole process as we go along, we'll be
documenting and keeping notes in two places:

On Meta: 2015 Community Wishlist Survey/Top 10:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10

On Phabricator: Community Wishlist Survey board:
https://phabricator.wikimedia.org/tag/community-wishlist-survey/

Finally: What about the other 97 proposals?

There were a lot of good and important proposals that didn't happen to get
quite as many support votes, and I'm sure everybody has at least one that
they were rooting for. Again, the whole list is here:

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

We're going to talk with the other Wikimedia product teams, to see if they
can take on some of the ideas the the community has expressed interest in.
We're also going to work with the Developer Relations team to see if some
of these could be taken on by volunteer developers.

It's also possible that Community Tech could take on a small-scale,
well-defined proposal below the top 10, if it doesn't interfere with our
commitments to the top 10 wishes.

So there's lots of work to be done, and hooray, we have a whole year to do
it. If this process turns out to be a success, then we plan to do another
survey at the end of 2016, to give more people a chance to participate, and
bring more great ideas.

For everybody who proposed, endorsed, discussed, debated and voted in the
survey, as well as everyone who said nice things to us recently: thank you
very much for coming out and supporting live feature development. We're
excited about the work ahead of us.

We'd also like to thank Wikimedia Deutschland's Technischer Communitybedarf
team -- they came up with this whole survey process, and they've been
working successfully on lots of community wishes since their first survey
in 2013.

You can watch this 

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

[Wes Moran]

Great work and a nice process.

On Wed, Dec 16, 2015 at 3:12 PM, Danny Horn  wrote:

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

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

[Pine W]

Thank you Danny & Company!

Pine

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

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

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

[Yuri Astrakhan]

>
> #3. Central global repository for templates, gadgets and Lua modules  (87)
>

I would love to participate in this - I feel it would bring different
language communities much closer together.  And great for Graphs & Maps.


> #7. Pageview Stats tool  (70)
>

We could even do it on-wiki like here
 - it shows
how to draw a graph from pageviews API, and this graph extension
 can add
HTML controls to it.

Awesome list, thanks for getting more community involvement!
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2015-12-16 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-12-16

= 2015-12-16 =
== Reading ==

=== Web ===
* Read more feature live on all language Wikipedias as desktop beta feature
/ mobile beta. Please try it out!
* Lead image beta experiment now using WikidataPageBanner
* TechOps involvement requested: potential cache issue, unclear that it's
actually MobileFrontend - https://phabricator.wikimedia.org/T121594

=== Mobile Content Service ===
* 55% of Android Beta App users use the RB based service for link previews
(page summary) + page content

=== Android ===
* 2.1.136-2015-12-09 published.
** New Wikipedia Maps.
** Final release of 2015.

=== iOS ===
* Marching to TestFlight beta testing (with org.wikimedia.wikipedia bundle
ID to ensure database upgrade coverage) soonish. Got an iOS device?
Download the Wikipedia app and let Josh Minor know if yu're interested

=== Reading Infrastructure ===
* Security: ping re SessionManager security review: Is it done, or else
what else do we need to do?
* Security: If you could squeeze in a look at
https://gerrit.wikimedia.org/r/#/c/259066 and related patches (it's another
thing needed for AuthManager that isn't "in" AuthManager itself), we'd
appreciate it.
* DBA: https://phabricator.wikimedia.org/T121335 (which I think he already
knows about)

== Community Tech ==
* Community Wishlist Survey is complete -
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
** We will be doing analysis on the top 10 proposals and pinging other
teams as needed
* Progress on PageAssessments extension - now uses parser ExtensionData and
JobQueue for better scalability
* Still working on Gadgets 2.0 - you can play with a test instance at
http://commtech.wmflabs.org/wiki/Special:GadgetManager

== Editing ==

=== Language ===
* Deployment of cxserver service-runner rewrite is delayed to Thursday

=== Collaboration ===
* Cross-wiki Echo notification work is mostly done.
* Also planning some UX changes to how Echo notifications work in general
* We finished populating the Flow artificial primary keys.
* Flow Nuke integration almost done

== Fundraising Tech ==
* Investigating potential CN bug limiting banners on mobile
* Updating donation forms and fraud prevention for backup credit card
processor
* Fixes for CiviCRM
* Internal dashboard updates


== Research ==

   - ORES:


   - 2 new models (etwiki, ukwiki) last week with some *substantial*
   improvements to the wikidata models (0.97 AUC)


   - 3 hours of downtime this morning.  See incident report:
   https://wikitech.wikimedia.org/wiki/Incident_documentation/20151216-ores


== Technology ==

=== Services ===
- Page summary end point live & pre-generated:
https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_summary_title
- EventBus incl. MediaWiki event production ready for deploy; hardware
might not be ready in time before freeze.
- mediawiki-docker-compose prototyping:
https://phabricator.wikimedia.org/T92826#1866757
- includes a combined service running RESTBase, Parsoid & in the future
mathoid & others: https://github.com/gwicke/mediawiki-node-services
- moved to service::node module
- upgraded to Cassandra 2.1.12; improved performance significantly
- Ops dependencies:
- Node 4.2 upgrade: https://phabricator.wikimedia.org/T107762

=== Analytics ===
* Event Logging has been having trouble as we switch to TokuDB because
space filled up, no data loss yet but we've been backfilling from time to
time.  We send notices to Analytics-l but if your numbers look weird,
either ask us or rerun your report
* pageview API: blogpost, clients in python, JS, R, dev summit session,
all's well that ends well
* Wikistats reports are being slowly transitioned to Hadoop, we're on track
this quarter and planning to be hopefully done in two more quarters
* We're consolidating all our Phabricator work from Analytics-Backlog and
Analytics-Engineering to just simply Analytics.

=== Security ===
Reviews: Thumber almost completed, PageAssessment starting monday for
CommTech
Security release Thursday
Not yet blocked, but will need parsing team review of T119158 soon
Password policy updates

=== Release Engineering ===
* *Blocking*: (none)
* *Blocked by*: (none)
* *Updates*:
** Scap3 refactoring and tech debt cleanup
*** https://phabricator.wikimedia.org/project/view/1449/
*** Working on common Puppet setup of scap for all services
** Started migrating Jenkins to jessie
** Brief experiment with Appium support in MW-Selenium
*** Sorta works but need a real test case (any interest from iOS or Android
teams?)
*** dr0ptp4kt just pinged bgerstle and niedzielski on #wikimedia-mobile
** Experimenting with JS-based end-to-end test framework
** Gitblit redirection work in progress
*** https://phabricator.wikimedia.org/project/board/46/

=== Technical Operations ===
* Blocking: none
* Blocked on: none
* Updates:
* udp2log decommisioning in favor of kafka complete (kudos to Andrew
Otto)
* Migration of un

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

[Dan Garry]

Hey Pine,

Responses in-line.

On 9 December 2015 at 22:14, Pine W  wrote:

> Hi, just checking to see if CAPTCHA improvements are likely anytime in the
> near future. I notice that
> https://phabricator.wikimedia.org/project/board/225/ shows nothing under
> "Awaiting code review". Is anyone working on this?


To the best of my knowledge, nobody is working on the CAPTCHA system right
now.


> If not, what kind of
> nudge would be necessary to get some resources devoted to CAPTCHA
> improvements?
>

The truthful but (presumably) unsatisfying answer is that you'd have to
convince someone responsible for planning their team's work that working on
the CAPTCHA is more important than what they had planned. That does not
seem likely to happen right now.

Dan

-- 
Dan Garry
Lead Product Manager, Discovery
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

[Pine W]

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

Pine

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

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

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

[Sam Klein]

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  wrote:

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

[Wikitech-l] [MediaWiki-announce] Announcement: Security Release Tomorrow

[Chad]

Hi all,

Tomorrow we will be issuing a security release for all branches
of MediaWiki 1.23 and beyond.

The new releases will be:
1.23.12
1.24.5
1.25.4
1.26.1

Fixes will be available in the affected release branches and master.
Tarballs will be uploaded for the indicated point releases as well.

This release encompasses 6 fixes for core only, no bundled extensions
are impacted.

Have a great day,
Chad H. & Chris S.
___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l