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 <npangarkar@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 dhorn@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 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 page for further Community Tech announcements: https://meta.wikimedia.org/wiki/Community_Tech/News
Thanks!
Danny Horn Product Manager, WMF Community Tech
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
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 tnegrin@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 < npangarkar@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 dhorn@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 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 page for further Community Tech announcements: https://meta.wikimedia.org/wiki/Community_Tech/News
Thanks!
Danny Horn Product Manager, WMF Community Tech
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org https://meta.wikimedia.org/wiki/Mailing_lists/GuidelinesWikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
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.wp@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 tnegrin@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 < npangarkar@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 dhorn@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 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 page for further Community Tech announcements: https://meta.wikimedia.org/wiki/Community_Tech/News
Thanks!
Danny Horn Product Manager, WMF Community Tech
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org <
https://meta.wikimedia.org/wiki/Mailing_lists/GuidelinesWikimedia-l@lists.wi...
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@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-request@lists.wikimedia.org?subject=unsubscribe
On Wed, Dec 16, 2015 at 9:55 PM, Danny Horn dhorn@wikimedia.org wrote:
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.
Thanks, Danny. In the Wikisource Conference, held in Vienna from 20 to 22 November, we discussed a lot about what Wikisource needs to reach it's full potential as a project. We decided to agree on a priority list (here: https://etherpad.wikimedia.org/p/wscon2015needs) and also to participate in the Survey.
But, if you feel brave enough, there is the whole 665 lines Etherpad here: https://etherpad.wikimedia.org/p/wscon2015weekend [1]
Wikisource, as a project, is completely dependent on the Proofread Page Extension [2]. Unfortunately, the extension is maintained by volunteers only (I think, just one: Tpt). Also, the extension doesn't support RTL languages: so Wikisources in arabic, hebrew, farsi, indic languages don't really work as the others.
This is to be added to the fact that there is no good embedded OCR for Indic languages, right now.
And, finally, to the simple fact that we'd love to have the Visual Editor, *within* the ProofreadPage Extension, as Wikisource uses a *lot* of formatting, and that could enable many, many more users in proofreading and validating pages.
Of course, we are a small community, but we're trying really hard to make our case. At the moment, to the best of my knowledge, there is no, and there's never been, any software development dedicated to Wikisource from the WMF.
Aubrey (also a member of the Wikisource Community User Group)
[1] I hereby claim this as the longest Etherpad written by a group of wikimedians (~40). I hope there is a prize for it. You can even read the Wikisource mission forged and translated in real time in 21 languages (line 564). [2] https://www.mediawiki.org/wiki/Extension:Proofread_Page
+1 - this is a good idea, Risker. Projects from smaller communities get easily outvoted by the more heavyweight projects, and in some cases they may be both easier to implement and have more impact for the projects as a whole than a more popular (but more complex) project on a large wiki.
I also want to echo everyone's comments about determining priorities: this is a really good step to see!
Richard Symonds Wikimedia UK 0207 065 0992
Wikimedia UK is a Company Limited by Guarantee registered in England and Wales, Registered No. 6741827. Registered Charity No.1144513. Registered Office 4th Floor, Development House, 56-64 Leonard Street, London EC2A 4LT. United Kingdom. Wikimedia UK is the UK chapter of a global Wikimedia movement. The Wikimedia projects are run by the Wikimedia Foundation (who operate Wikipedia, amongst other projects).
*Wikimedia UK is an independent non-profit charity with no legal control over Wikipedia nor responsibility for its contents.*
On 16 December 2015 at 20:39, Risker risker.wp@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 tnegrin@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 < npangarkar@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 dhorn@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 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 page for further Community Tech announcements: https://meta.wikimedia.org/wiki/Community_Tech/News
Thanks!
Danny Horn Product Manager, WMF Community Tech
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org <
https://meta.wikimedia.org/wiki/Mailing_lists/GuidelinesWikimedia-l@lists.wi...
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@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-request@lists.wikimedia.org?subject=unsubscribe
Thank you Danny & Company!
Pine
On Wed, Dec 16, 2015 at 12:22 PM, Toby Negrin tnegrin@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 < npangarkar@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 dhorn@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 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 page for further Community Tech announcements: https://meta.wikimedia.org/wiki/Community_Tech/News
Thanks!
Danny Horn Product Manager, WMF Community Tech
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
Wmfall mailing list Wmfall@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall
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-request@lists.wikimedia.org?subject=unsubscribe
wikimedia-l@lists.wikimedia.org