edits based on FDC comments
← Older revision
Revision as of 04:23, 26 May 2016
Line 851:
Line 851:
'''Objective 2 – Modify and improve curation tools:''' Throughout the year, iterate modifications and improvements to core curation tools, like edit, [[m:Help:Diff|diff]] and [[m:Help:Page history|history]] pages, in order to allow contributors to more easily and efficiently manage contributions – both their own and those of others.</translate><br><br>
'''Objective 2 – Modify and improve curation tools:''' Throughout the year, iterate modifications and improvements to core curation tools, like edit, [[m:Help:Diff|diff]] and [[m:Help:Page history|history]] pages, in order to allow contributors to more easily and efficiently manage contributions – both their own and those of others.</translate><br><br>
+
*
'''Objective 3 – Guiding edits:''' We will experiment in the visual and wikitext editors with different ways to suggest to users things they can do to make better, more constructive edits as they make them. This work is aimed at reducing the burden on experienced users when they review new editors' changes. We also intend for these experiments to improve the "on-boarding" experience for new users, helping them learn what is wanted and valued by their wiki's community.
'''Objective 3 – Guiding edits:''' We will experiment in the visual and wikitext editors with different ways to suggest to users things they can do to make better, more constructive edits as they make them. This work is aimed at reducing the burden on experienced users when they review new editors' changes. We also intend for these experiments to improve the "on-boarding" experience for new users, helping them learn what is wanted and valued by their wiki's community.
Line 917:
Line 918:
** [[Community Tech/Improved diff compare screen|<translate><!--T:304-->
** [[Community Tech/Improved diff compare screen|<translate><!--T:304-->
Assisting Wikidata with building structured data on Commons, in response to a wish for translated category names </translate>]]<br><br>
Assisting Wikidata with building structured data on Commons, in response to a wish for translated category names </translate>]]<br><br>
+
More details on timelines and targets: Community Tech
{{Back to top|arrow text=Back to top}}
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end goal 1-->
Line 949:
Line 951:
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate><!--T:313-->
<translate><!--T:313-->
−
The technology department supports global access to the Wikimedia projects that is reliable, fast, and secure.
We
want
projects
to
be
available to as many people as possible, on as many devices as possible, in a manner that safeguards users’ privacy and trust.</translate>
+
The technology department supports global access to the Wikimedia projects that is reliable, fast, and secure.
This
team
supports performance, availability, development infrastructure, technical operations, security, architecture, release management, analytics engineering and Research. One of the larger teams, they support most of the core operations
to
make sure our projects, services and development pathways are
available to as many people as possible, on as many devices as possible, in a manner that safeguards users’ privacy and trust.</translate>
<translate><!--T:314-->
<translate><!--T:314-->
−
We support progress by providing tooling and infrastructure that make it possible for developers to enhance and augment the capabilities of our software. We create pathways for creative and motivated individuals to translate their ideas into working software that is reliable, easy-to-use, secure, and scalable.
We provide counsel by assisting other units within the organization and the movement to make good choices on technology by assessing costs, analyzing usability, anticipating failures, projecting impact, and suggesting alternatives.</translate>
+
We support progress by providing tooling and infrastructure that make it possible for
product
developers to enhance and augment the capabilities of our software. We create pathways for creative and motivated individuals to translate their ideas into working software that is reliable, easy-to-use, secure, and scalable.
+
+
We work closely with the Product team to support ongoing initiatives and cover development dependencies. We provide counsel by assisting product teams and other units within the organization and the movement to make good choices on technology by assessing costs, analyzing usability, anticipating failures, evaluating privacy, reviewing security, projecting impact, and suggesting alternatives.</translate>
<translate><!--T:315-->
<translate><!--T:315-->
−
We conduct, enable, and review research to validate and iterate on concepts, to ensure usability and that products are built around users’ needs. We conduct research and explore services so that we can surface the best ways to end barriers to contribution. We use formal collaborations with industry and academia to scale efforts of the organization.</translate>
+
We also work with the Product audiences providing research before new products or features are built.
We conduct, enable, and review research to validate and iterate on concepts, to ensure usability and that products are built around users’ needs. We conduct research and explore services so that we can surface the best ways to end barriers to contribution. We use formal collaborations with industry and academia to scale efforts of the organization.</translate>
+
+
Tracking performance targets is a new discipline for our team. In FY16-17, we will be establishing baselines so that we can more accurately make predictions and measure performance increases in future annual planning. We will also develop a roadmap to show which projects will be completed each quarter.
===<translate><!--T:316-->
===<translate><!--T:316-->
Line 962:
Line 964:
''<translate><!--T:317-->
''<translate><!--T:317-->
Team: [[mw:Analytics|Analytics]]</translate>''
Team: [[mw:Analytics|Analytics]]</translate>''
+
+
The Analytics Team is focused on making Wikimedia related data available for querying and analysis to both WMF and the different Wiki communities and stakeholders. We develop infrastructure so all our users, both within the Foundation as within the different communities, can access data in a self-service fashion that is consistent with the values of the movement. This ties directly into the first strategic priority, to understand our users to better serve their needs. In the past, this has been difficult to accomplish, due to lack of proper infrastructure for computation (cluster) and serving data (APIs).
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:318-->
==== <translate><!--T:318-->
Goal: Build the infrastructure and capacity to better understand our users’ online interactions with our projects and more quickly respond their needs=</translate>===
Goal: Build the infrastructure and capacity to better understand our users’ online interactions with our projects and more quickly respond their needs=</translate>===
−
Currently, the Foundation has limited capacity to understand what users as a whole are doing with the projects, where they are experiencing problems, and what would best facilitate easier reading and editing. By focusing efforts on improving our querying and analysis tools, services and systems so all our users, both within the Foundation and the different communities, can access data. This will help us better serve readers’ and editors’ needs
(this maps to our first strategic priority of understanding our users to better serve their needs)
.
+
Currently, the Foundation has limited capacity to understand what users as a whole are doing with the projects, where they are experiencing problems, and what would best facilitate easier reading and editing. By focusing efforts on improving our querying and analysis tools, services and systems so all our users, both within the Foundation and the different communities, can access data. This will help us better serve readers’ and editors’ needs.
+
+
More details on all projects: Analytics projects
* <translate><!--T:319-->
* <translate><!--T:319-->
Line 985:
Line 989:
===<translate><!--T:325-->
===<translate><!--T:325-->
−
Program 2: Expand research capabilities</translate>===
+
Program 2: Expand research capabilities
to equip product development to better meet users’ needs
</translate>===
<div style="border-radius:5px; margin:10px;">
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:326-->
''<translate><!--T:326-->
Line 1,017:
Line 1,021:
'''Objective 1 – Expand academic research outreach:''' Aim to achieve a stronger academic presence by submitting the output of our work to key conferences in the field and by organizing an annual research workshop. These efforts will help us align the interests of the academic community to issues of strategic importance for the movement. Targets: 4 Papers submitted and accepted in peer reviewed conference proceedings in the fiscal year; 40 Works submitted and accepted by researchers attending annual workshops. ([[mw:Wikimedia Research|Research and Data team]])</translate> <br><br>
'''Objective 1 – Expand academic research outreach:''' Aim to achieve a stronger academic presence by submitting the output of our work to key conferences in the field and by organizing an annual research workshop. These efforts will help us align the interests of the academic community to issues of strategic importance for the movement. Targets: 4 Papers submitted and accepted in peer reviewed conference proceedings in the fiscal year; 40 Works submitted and accepted by researchers attending annual workshops. ([[mw:Wikimedia Research|Research and Data team]])</translate> <br><br>
* <translate><!--T:336-->
* <translate><!--T:336-->
−
'''Objective 2 – Initiate formal research collaborations:''' Set up three new collaborations with external research teams to address critical, under-resourced areas. ([[mw:Wikimedia Research|Research and Data team]])</translate>
<br><br>
+
'''Objective 2 – Initiate formal research collaborations:''' Set up three new collaborations with external research teams to address critical, under-resourced areas
. Targets: FY 2016-17 Q2-Q4
. ([[mw:Wikimedia Research|Research and Data team]])</translate>
+
For more details: Formal collaborations
+
<br><br>
{{Back to top|arrow text=Back to top}}
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
</div><!--end goal 2-->
Line 1,030:
Line 1,034:
'''Objective 1 – Conduct evaluative design research:''' Continue to collaborate with the Foundation teams and Communities toward building user-facing functionality around the needs of users and contributors. Iterate features and functionality toward usability and utility. Target: 15 evaluative research projects in FY16-17. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate> <br><br>
'''Objective 1 – Conduct evaluative design research:''' Continue to collaborate with the Foundation teams and Communities toward building user-facing functionality around the needs of users and contributors. Iterate features and functionality toward usability and utility. Target: 15 evaluative research projects in FY16-17. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate> <br><br>
* <translate><!--T:340-->
* <translate><!--T:340-->
−
'''Objective 2 – Analyze and apply generative research for new readers:''' Analyze and synthesize data collected in three generative, qualitative research studies for new readers. This work will inform how we can best support online learning in these regions, and invite more readers to Wikis. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate><br><br>
+
'''Objective 2 – Analyze and apply generative research for new readers:''' Analyze and synthesize data collected in three generative, qualitative research studies for new readers
in India, Nigeria, and Mexico
. This work will inform how we can best support online learning in these regions, and invite more readers to Wikis. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate><br><br>
* <translate><!--T:341-->
* <translate><!--T:341-->
−
'''Objective 3 – Build a product benchmarking system:''' Build a benchmarking system to evaluate, over time, the usefulness, user experience, and usability of product functionality. This work will contribute information to product teams for deciding which areas are most important to put effort toward. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate><br><br>
+
'''Objective 3 – Build a product benchmarking system:''' Build a benchmarking system to evaluate, over time, the usefulness, user experience, and usability of product functionality. This work will contribute information to product teams for deciding which areas are most important to put effort toward
. Targets: First two quarters of FY 16-17
. ([[mw:Wikimedia_Research/Design_Research|Design Research team]])</translate><br><br>
+
+
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
+
====Goal 4: Improve communications and access of all research projects, so that institutional knowledge is easily shared and applied====
+
Currently, research, data analytics, and community surveys are conducted by different departments of the whole Foundation. This structure was intentionally built to ensure better integration and responsiveness of key personnel to serve specific projects. However, this structure makes it challenging to share information across teams and effectively with the community. By improving how we communicate and organize this information, institutional knowledge can be more effectively applied.
+
+
*
+
'''Objective 1 – Create a Research minisite that would act as a landing page for all resources related to research at the organization:''' Potentially by end of Q1, build a centralized location for storage of research projects, with a primary focus on the two teams in the Research department: Research & Data and Design Research.
+
+
More details: Research’s quarterly goals; a complete list of ongoing projects, cross-linked with Phabricator and organized by quarter; and a list of our current formal collaborations and documentation on how they are set up.
+
+
+
{{Back to top|arrow text=Back to top}}
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
</div><!--end goal 3-->