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

[Yuri Astrakhan]

Denny, thanks for organizing and publishing!

You mentioned that the comm-tech team is the one "responsible for
investigating and addressing the top 10 wishes". I think the community
views WMF as more of a monolith, and I hope these votes have wider impact
on foundation priorities.  After all, commtech is only about 3% of the
staff (10 out of 291 [1]). I surely hope there is significantly more than
3% to tackle community wishes.

I think that by voting for something, the community would like WMF to
prioritize these directions above others in terms of new development work.
In other words, community speaks of **what** we think are the most
important projects, and WMF thinks of **how** it gets done - e.g. by
allocating resources, setting up a community tech team, realigning the
goals of the other teams, hiring contractors, etc etc.  It would be strange
if foundation spent significant resources on a project with marginal
interest, while ignoring community priorities.

Obviously this only applies to the new software developments, not any of
the maintenance work foundation has to do.

Thanks!!

--[[user:yurik]]

[1]:  https://wikimediafoundation.org/wiki/Staff_and_contractors

On Wed, Dec 13, 2017 at 9:29 PM, Danny Horn  wrote:

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

[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] Community Wishlist Survey: Top 10 wishes of 2016!

[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, 

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

[pi zero]

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, 

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

[James Heilman]

Thanks Danny

Some excellent projects. 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.

:-)
J

On Thu, Dec 15, 2016 at 9:20 PM, Danny Horn  wrote:

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




-- 
James Heilman
MD, CCFP-EM, Wikipedian

The Wikipedia Open Textbook of Medicine
www.opentextbookofmedicine.com
___
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!

[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, 

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

[Henning Schlottmann]

On 29.12.2015 03:40, Pete Forsyth wrote:

> This is not an "either/or" situation. At least in the past, when I have
> manually added Wayback Machine links (or seen them added by bots), they do
> not *replace* dead links, they merely complement them. The English
> Wikipedia templates include two separate parameters for "url" and
> "archiveurl".

That's true only for a) external links that use templates and b) it
assumes that people will be motivated to check for alternatives to
archive links despite their immediate need for information seems to be
satisfied by the archive link.

Maybe I'm not typical in this, but I prefer a dead link over a link to
the archive that was set by a bot without checking for a live link anytime.

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, 

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

[James Heilman]

Deadlinks are one of the most common ways of spamming Wikipedia. Paid
editors replace deadlinks with links to the spam site which now contains
the contain as it way copied from waybackmachine. Linking to waybackmachine
is thus superior.

-- 
James Heilman
MD, CCFP-EM, Wikipedian

The Wikipedia Open Textbook of Medicine
www.opentextbookofmedicine.com
___
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!

[James Heilman]

Hey Trillium

Am a little distracted. Will dug up some difs for you soon. Please email me
directly to remind me.

-- 
James Heilman
MD, CCFP-EM, Wikipedian

The Wikipedia Open Textbook of Medicine
www.opentextbookofmedicine.com
___
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] Community Wishlist Survey: Top 10 wishes!

[Trillium Corsage]

28.12.2015, 21:00, "James Heilman" :
> Deadlinks are one of the most common ways of spamming Wikipedia. Paid
> editors replace deadlinks with links to the spam site which now contains
> the contain as it way copied from waybackmachine. Linking to waybackmachine
> is thus superior.
>
> --
> James Heilman
> MD, CCFP-EM, Wikipedian

Not necessarily disbelieving you, but can you point to a single, concrete 
example of a "paid editor replacing a deadlink with a link to the spam site 
copied from waybackmachine?" I'd like to see what you are talking about.

Trillium Corsage 

___
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] Community Wishlist Survey: Top 10 wishes!

[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 
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,
> 
>
___
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] Community Wishlist Survey: Top 10 wishes!

[Pete Forsyth]

Henning, I think you have missed an important detail (and if I'm mistaken,
I'd like to know about it).

This is not an "either/or" situation. At least in the past, when I have
manually added Wayback Machine links (or seen them added by bots), they do
not *replace* dead links, they merely complement them. The English
Wikipedia templates include two separate parameters for "url" and
"archiveurl".

Adding one by an automated process does nothing to prevent the other from
being repaired, whether by automated process or by human intervention.

Also, it's essential to consider that many "dead links" are truly dead at
the source site. A newspaper may have implemented a paywall or taken its
archives offline altogether; a political campaign may have let its domain
lapse now that its candidate has retired from politics; a corrupt
government may have removed information to suppress evidence. We all agree
that repairing those dead links that can be repaired is ideal; but not all
dead links *can* be repaired.
-Pete
[[User:Peteforsyth]]

On Mon, Dec 28, 2015 at 9:51 AM, Henning Schlottmann 
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,
> 
>
___
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] Community Wishlist Survey: Top 10 wishes!

[Brad Jorsch (Anomie)]

On Mon, Dec 28, 2015 at 12:51 PM, Henning Schlottmann  wrote:

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

An automated process can't reliably do either of those, while having the
archive link available will make it easier for human editors to do both of
those since they'll have the actual content of the dead link available
rather than just what information is preserved in the citation (URL, title,
author, maybe a short quotation).
___
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] Community Wishlist Survey: Top 10 wishes!

[Henning Schlottmann]

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, 

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

[Trillium Corsage]

17.12.2015, 01:26, "Sam Klein" :
> Thanks to all for organizing the survey and for sharing!



> And a mentor-friendly feature I've wanted for a long time:
> #10. Add a user watchlist

That's not only mentor-friendly, it's hounder-friendly and harrasser-friendly. 
Really, you should have a look at the seamier side of (at least) English 
WIkipedia. There are people, particularly among the administrative set, with 
null interest in articles but consumed with interpersonal conflict and 
targeting of others. It's not a small problem.

Trillium Corsage

___
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] Community Wishlist Survey: Top 10 wishes!

[Quim Gil]

On Thu, Dec 17, 2015 at 4:01 AM, Lane Rasberry 
wrote:

> It was fun to participate in the proposal process.


I want to stress this sentence! I believe many participants will agree.

There are many ways to create a community backlog, and none of them will be
perfect. The Community Tech team chose to have a process relatively simple
to organize and to participate in, doing some sacrifices along the way to
keep that simplicity (I know well, they knocked off several ideas I
suggested). :D

The resulting backlog is just the beginning of a new phase that could be
just as fun. 10 tasks have been selected by CT, and we need everybody's
imagination to find the best ways to solve the rest.

For instance, I'm proposing to select project candidates for hackathons
from this Wishlist (https://phabricator.wikimedia.org/T119703) not only
because it seems a good thing to do, but also because I believe that the
people who voted for these proposals and the developers looking for
interesting hackathon projects can continue having fun together. Achieving
goals is important, but enjoying the ride together is just as important.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
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] Community Wishlist Survey: Top 10 wishes!

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

[Wikimedia-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: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes!

[Richard Ames]

This thread (subject) looks like it could bring lots of different thoughts,
ideas, suggestions, etc.

Please (Please, Please) --- if your message is mainly on a new topic /
thought / etc; Send a new message, with a new subject line.

Thank you, Richard.
___
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] Community Wishlist Survey: Top 10 wishes!

[Bodhisattwa Mandal]

Danny,

First of all, thanks for your comments on Wikisource community wishlist
survey. Though we are a small global community, we did our best to get our
basic problems noticed.

To my opinion, the current system of Community wishlist survey is not good
enough to solve the problems of Wikimedia sister projects like Wikisource.
As very few volunteers work on Wikisource globally, it is very difficult to
compete with Wikipedia or Commons proposals because obviously Wikisource
proposals will not get as much votes as they do.

The concept of top 10 wishes is great! But in addition, if there is a
provision to include at least top 2 wishes of each of the sister projects,
then personally I can say that it can be an effective measure to uplift
these projects. Andrea already said in the previous mail that, Wikisource
software support is totally provided by volunteers alone right from the
beginning and not WMF and that's a real issue for us.

Regards,
Bodhisattwa

On 17 Dec 2015 03:32, "Richard Ames"  wrote:
>
> This thread (subject) looks like it could bring lots of different
thoughts,
> ideas, suggestions, etc.
>
> Please (Please, Please) --- if your message is mainly on a new topic /
> thought / etc; Send a new message, with a new subject line.
>
> Thank you, Richard.
> ___
> 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: 
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] Community Wishlist Survey: Top 10 wishes!

[Lane Rasberry]

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

Re: [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 

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

[Pine W]

Question for the Wikisource folks: would Project Grants be a way to get
resources for you? If you can design a project and find people with the
right skills, that avenue might be beneficial for you. I have a software
developer in mind who would probably like to work with you if resources are
available and a project has the support of the community and WMF.

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