Wikimedia Foundation Annual Plan/2016-2017/draft: Difference between revisions
Content deleted Content added
m v2.05b - Fix CW error #64 - WCW (Link equal to linktext - Title linked in text - Whitespace characters after heading) |
No edit summary |
||
Line 20:
<!--T:6-->
This year’s plan focuses on improving support for--and consultation with--community, responding effectively to changing user needs, and addressing challenges facing our movement. We are investing in areas that we believe the Foundation is uniquely positioned to address, including readership and reach, volunteer retention and engagement, and support for knowledge creation. We will deepen and expand work in our newly clarified strategic directions, while strengthening the core work that supports our communities and projects. These directions distill to reach, communities, and knowledge, and were refined through a public consultation held through mid March 2016. This annual plan accompanies the presentation of the Foundation’s [[
<!--T:7-->
Line 40:
<!--T:13-->
Our department dedicated to community support, '''Community Engagement''', will focus on strengthening effective programs, improving services to community, and facilitating the health of the movement. Community Engagement will foster long-term movement sustainability by helping build supportive, engaged communities by facilitating mentorship in community leaders, supporting high-impact programs such as GLAM, and making it easier for community to access financial and learning resources. Their work primarily serves the second strategic priority,
<!--T:14-->
Line 49:
<!--T:16-->
'''Strategic Partnerships''', within our '''Advancement''' department, supports our strategic priority of reaching more people, through building and managing partnerships that support movement outreach and knowledge sharing around the world. Through the recently reintroduced Global Reach team, they will refine and carefully grow the Wikipedia Zero program, and explore and develop new forms of partnerships in areas of low readership and awareness. They will also manage relationships with key tech partners to support and strengthen our apps and preloads, and create opportunities for corporate contributions.
<!--T:17-->
Line 233:
</div> <!--end Financial 15-16-->
== <translate><!--T:115--> Programs: upcoming year's annual plan</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
=== <translate><!--T:116--> For each program, please include your targets for each of the global metrics in this table</translate> ===
''<translate><!--T:117--> All [[m:Grants:
<br /><br />
<translate><!--T:118-->
Global metrics are based on two of the primary strategic goals set out in the 2010-2015 Wikimedia strategic planning process: participation (editors) and content (articles). The Wikimedia Foundation continues to support these metrics as sensible, effective means of measuring the impact community and affiliate programs have in these two areas.<br>Historically, the Foundation has prioritized metrics of participation (contributors) and reach (readers) as primary metrics. Over the past year, the Foundation has begun to move toward department and team-specific measurements, in order to enable more granular program and product accountability. This has been accompanied by focusing many programs on the strategic priority of reaching more people through the Wikimedia projects.<br>The FY16-17 Annual Plan has highlighted the need for the Foundation to clarify its approach to global metrics, in addition to the measurable indicators set out for our programmatic goals. We are exploring how how to best measure the efficacy our work and anticipate being able to provide clearer metrics in future annual planning.</translate><br><br>
Line 249:
</div>
== <translate><!--T:830--> Community Engagement</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate>
<!--T:123-->
The Wikimedia community is the core of the movement. Community needs, priorities, and feedback are essential factors informing the Wikimedia Foundation strategy. A primary focus of the Community Engagement department is facilitating community health by ensuring the Wikimedia communities are thriving, that community needs are understood by the Foundation, and that community members have access to critical resources.
<!--T:124-->
Line 262:
<!--T:126-->
Collectively, the four teams that comprise Community Engagement positively affect people across the Wikimedia projects. Volunteer retention is essential to the sustainability of our movement, and Community Engagement addresses volunteer support at the points where users frequently decide whether to keep engaging, and for how long. They provide access to resources that strengthen community members’ work, support community members in experimenting with projects that can have short-term and long-term impact, and make the community safer and healthier.
<!--T:127-->
Line 268:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:128--> Program 1: Develop community leadership and mentorship</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:129--> Team: [[Program Capacity and Learning|Program Capacity & Learning]]</translate>''
Line 276:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:131--> Goal: Bolster community leadership development through Peer Leadership Academy</translate> ====
<translate><!--T:132--> In 2016-17 our team will continue our shift to scalable, train-the trainer style of learning in order to develop community leadership for peer mentoring.</translate>
* '''<translate><!--T:133--> Objective 1 – Peer leadership development</translate>:''' <translate><!--T:134--> By the end of FY16-17, support 300+ community leaders’ engagements in direct leadership development activities.</translate><br><br>
Line 285:
</div><!--end Program 1-->
=== <translate><!--T:139--> Program 2: Introduce training modules for functionaries and event organizers regarding issues management</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:140--> Team: [[Support and Safety]].</translate>''
Line 292:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:142--> Goal 1: Create a training platform for functionaries</translate> ====
<translate><!--T:143-->
Functionary and community governance groups – including [[stewards]], [[Administrators|admins]], global admins, and [[Arbitration Committee|Arbitration Committees]] – play a crucial administrative and editorial role on all our sites, especially in curtailing harassment of volunteers and arbitrating and resolving disputes. To help these functionary and community governance groups better coordinate their work, we will facilitate in the development of a training platform and will guide the establishment of a module based around the critical area of addressing harassment.</translate>
Line 304:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:151--> Goal 2: Create a module on the training platform that helps organizers manage our ‘event ban policy’</translate> ====
<translate><!--T:152-->
We are dedicated to creating safe online spaces for users – regardless of gender, gender identity and expression, sex, sexual orientation, disability, physical appearance, race, ethnicity, national origin, age, political affiliation, religion or community status – to meet, interact, learn and collaborate. We are also committed to ensuring our users’ offline experience at Wikipedia events. In 2016-17, we will guide the creation of at least one safety-focused content module on our new training platform, and this module will focus on helping community groups more successfully identify and de-escalate situations before they grow out of control and implement the [[Event Ban policy|new event ban policy]] as a useful tool. That policy establishes guidelines and [[Event Ban policy/process|procedures]] for identifying and handling users who are banned from Wikimedia Foundation-sponsored or funded events.</translate>
Line 315:
</div><!--end program 2-->
=== <translate><!--T:159--> Program 3: Develop capacity-building tools and resources for core Wikimedia programs</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:160--> Team: [[Program Capacity and Learning|Program Capacity & Learning]]</translate>''
Line 323:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:162--> Goal: Develop program and events dashboard and central Wikimedia resource center</translate> ====
<translate><!--T:163-->
Currently, community members must search many pages and places to stay informed about Foundation activities and resources. We will create a single point of reference - the
* <translate><!--T:164--> '''Objective 1 – Create minimum viable product for the programs and events dashboard:''' By the end of FY16-17, create a [[phab:project/view/1750/|Minimum Viable Product]] of a Programs and Events Dashboard across at least 10 projects or languages (with at least two for emerging communities). The Dashboard will be modeled on the Dashboard that the Wiki Education Foundation [https://dashboard.wikiedu.org/ uses] for its U.S. and Canada courses.</translate><br><br>
Line 334:
</div><!--end program 3-->
=== <translate><!--T:167--> Program 4: Allocate resources to effective community-led projects</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:168--> Team: [[
<translate><!--T:169-->
Line 342:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:170--> Goal: Implement our grants Streamlining Plan</translate> ====
<translate><!--T:171-->
[[Community Resources]] provides funding and other resources to mission-allied organizations and people around the world, with the goal of increasing the quantity, quality, diversity, and reach of our knowledge sites. In the summer of 2015, we held a community consultation about [[Grants:IdeaLab/
* <translate><!--T:172--> '''Objective 1 - Meet community needs during the restructuring transition:''' In FY16-17, maintain 10 core grantmaking workflows to support 50,000 individuals directly or indirectly per quarter, and with 50% of total grants going to emerging communities.</translate>
* <translate><!--T:173--> '''Objective 2 - Improve WMF’s support system for grantees:''' In FY16-17, transition 100% of grantees and committees from 2 existing grant programs (Project and Event Grants, Individual Engagement Grants) to 3 more clearly defined, specialized programs (Project Grants, Rapid Grants, Conference & Travel Support), reducing time between first proposal submission and approval when compared to the old structure (baseline will be established in FY16-17 by analyzing historical data).</translate><br><br>
* <translate><!--T:174--> '''Objective 3 - Evaluate and adapt:''' Evaluate the outcomes of grants awarded and continue to adapt and improve our systems as we learn. We expect to see a 10% increase in applicant, committee, and grantee satisfaction with support received, against a baseline of 55% indicating experience is above average or excellent, and 21% indicating below average.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 4-->
=== <translate><!--T:175--> Program 5: Give more support to GLAM partnerships</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:176--> Team: [[
<translate><!--T:177-->
Line 361:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:178-->
Goal: Improve access to GLAM knowledge and support</translate> ====
<translate><!--T:179-->
We will formalize our support in FY16-17 with tools and programmatic support, technical consultation to GLAM program leaders, and facilitating connections between potential GLAM partners and local communities. By the end of FY16-17, we will improve access to GLAM-Wiki knowledge by facilitating community curation of existing GLAM-Wiki documentation, as demonstrated through user feedback, and integrating the documentation into our new Wikimedia Resource Center.</translate>
* <translate><!--T:180--> '''Objective 1 - Complete technical consultation:''' By the end of FY16-17, complete a structured GLAM-Wiki consultation to understand technical needs and develop a plan for resourcing technical support to community leaders and organizations that engage with external pa</translate>rtners on GLAM-Wiki initiatives.<br><br>
* <translate><!--T:181--> '''Objective 2 - Develop resources on best practices:''' By the end of FY16-17, identify existing GLAM-Wiki leadership development strategies, and curriculum within existing GLAM-WIKI communities, and develop “best practices” for training new GLAM-Wiki Leaders within currently unsupported communities.</translate><br><br>
* <translate><!--T:182--> '''Objective 3 - Develop and maintain responsive staff support systems:''' In FY16-17, maintain quick response times and active consultation on community-led GLAM partnerships and grant initiatives (see [[Program Capacity and Learning/Annual Plan#Staff support for GLAM partnerships|more details]]).</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 5-->
=== <translate><!--T:183--> Program 6: Support Affiliations Committee and affiliate partnerships</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:184--> Team: [[m:Program Capacity and Learning|Program Capacity & Learning]]</translate>''
Line 381:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:186--> Goal: Maintain and improve staff support to the Affiliations Committee and affiliate partners</translate> ====
<translate><!--T:187-->
In FY16-17, we will improve support to the [[Affiliations Committee]] (AffCom), a community-run committee that advises the Wikimedia Foundation Board of Trustees on the recognition and review of movement affiliates such as chapters, thematic organizations, and user groups. We will continue support to WMF annual plan grantees and affiliates on evaluation design and survey strategies.</translate>
* <translate><!--T:188--> '''Objective 1 – Maintain quick response time:''' Throughout FY16-17, maintain initial staff review and response time of five business days or less for new affiliate applications to AffCom.</translate
* <translate><!--T:189--> '''Objective 2 – Maintain mentoring and consultation support:''' Throughout FY16-17, maintain mentoring and consultation support for learning and evaluation for annual plan grants including, grantee SMART target consultation, survey and learning supports, proposal review, and technical consultation, review, and development support to program evaluation systems (see [[Program Capacity and Learning/Annual Plan#Mentoring & Consultation|mentoring and consultation KPIs]])</translate
* <translate><!--T:190--> '''Objective 3 – Increase AffCom engagement and support to affiliate partnerships:''' In FY16-17, work to leverage AffCom as community leaders and mentors along with our existing service to bolster support for Affiliate Partnerships (see [[
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 6-->
=== <translate><!--T:191--> Program 7: Improve collaboration with communities in product development</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:192--> Team: [[Technical Collaboration]]</translate>''
Line 400:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:194--> Goal 1: Continue Community liaison support for Foundation Product goals</translate> ====
* <translate><!--T:195--> '''Objective 1 – Liaise with communities:''' Throughout FY16-17, when requested – allocate community liaison support for Foundation Product initiatives related to quarterly goals.</translate><br>
* <translate><!--T:196--> '''Objective 2 – Participate in audience planning:''' Throughout FY16-17, participate in the planning process of Foundation Product teams, offering crucial feedback for our Product releases.</translate><br>
* <translate><!--T:197--> '''Objective 3 – Facilitate all major product conversations:''' Throughout FY16-17, facilitate in and – when appropriate – moderate all major conversations involving Wikimedia communities and WMF Product teams.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:198--> Goal 2: Create a systematic approach to community engagement for product development teams</translate> ====
<translate><!--T:199-->
In 2016/17, the Technical Collaboration team will support the Foundation in its commitment to engage the community earlier and throughout the product development process, through
</translate>
* <translate><!--T:200--> '''Objective 1 – Initiate a guideline for technical collaboration between WMF teams and the communities:''' By the end of FY16-17, in collaboration with communities, initiate a “Technical Collaboration Guideline” that allows Product teams and Wikimedia communities to work together in a systematic way by establishing best practices for community involvement in the product development and deployment cycle.</translate><br><br>
* <translate><!--T:201--> '''Objective 2 – Facilitate wide adoption of the community engagement guideline:''' By the end of FY16-17, work to have all Foundation Product teams and a majority of the top 20 most-active Wikimedia projects integrate their technical decision processes with the community engagement guideline, as evidenced by community decisions and requests, as well as their processing by WMF teams.</translate><br><br>
* <translate><!--T:202--> '''Objective 3 – Integrate community engagement more closely with early Foundation product development stages:''' By the end of FY16-17, work to integrate community engagement more closely into the pre-release stages of product development, when Product researches, conceives, and plans a new release. In parallel, decrease the frequency of major discussions associated with the Release stage of a product.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
</div><!--end Program 7-->
=== <translate><!--T:203--> Program 8: Connect volunteer developer work with community technical needs</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:204--> Team: [[Technical Collaboration]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:205--> Goal: Connect free software developers with the [[2015 Community Wishlist Survey]] maintained by the Community Tech team</translate> ====
<translate><!--T:206-->
In the fall of 2015, the Foundation invited contributors to submit proposals for what the [[Community Tech|Community Tech team]] should do to improve or produce curation and moderation tools for active contributors. That wishlist provides a jumping-off point for the efforts of the Foundation Technical Collaboration team.</translate>
* <translate><!--T:207--> '''Objective 1 – Encourage volunteer focus on addressing community priorities:''' By the end of FY16-17, work with volunteer developers to complete 10 technical community requests that have strong demand.</translate><br><br>
* <translate><!--T:208--> '''Objective 2 – Encourage hackathon and outreach work into community requests:''' By the end of FY16-17, help Foundation hackathons and outreach programs, such as
* <translate><!--T:209--> '''Objective 3 – Better connect developers with tasks and mentors:''' By the end of FY16-17, improve the ability of new volunteer developers to find useful tasks and mentors easily, increasing the focus on deploying useful features. Progress will be measured with a community health survey for Wikimedia technical spaces.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 8-->
=== <translate><!--T:210--> Program 9: Identify support gaps and provide targeted resources</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:211--> Team: [[Community Resources/2016-17 Annual Plan|Community Resources]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:212--> Goal: Proactively identify gaps and provide targeted resources to communities to address those gaps</translate> ====
<translate><!--T:213--> (e.g., addressing systemic bias, harassment, reach, and support to emerging communities)</translate>
* <translate><!--T:214--> '''Objective 1 – Source new ideas:''' Run two Inspire campaigns per year through [[Grants:IdeaLab|IdeaLab]] to source ideas focused on strategic themes, resulting in 100 ideas from 200 participants and 10 grant proposals per campaign.</translate><br><br>
* <translate><!--T:215--> '''Objective 2 – Improve community capacities through pilot programs:''' Pilot, evaluate, and grow the most effective strategies for improving the capacity of 10 communities with low awareness and usage defined in the [[Community Capacity Development|Community Capacity Development Project]]. Pilots will need to demonstrate significant capacity improvement compared to a baseline, where each baseline will be defined for each pilot (e.g., Tamil technical skills pilot will see a 10% increase in number of community members engaging in technical work; Brazilian community will form a media response team).</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 9-->
=== <translate><!--T:216--> Program 10: Maintain quick public response time and expand community surveys</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:217--> Teams: [[Support and Safety]] (Goal 1)
<translate><!--T:218--> Continue responding rapidly to public questions around safety and support, while broadening WMF’s surveys to better understand the community’s needs.</translate>
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:219--> Goal 1: Respond efficiently and effectively in workflows</translate> ====
<translate><!--T:220-->
Support and Safety (SuSa) supports the Foundation, communities and public through community consultations, governance, training, public-WMF correspondence management, executive staff and functionary support, and legal team support. More specific details about the team’s core work can be read at [[:Support and Safety#What we do]]. Rapid review and appropriate response to enquiries and effective engagement with staff, community, and the public ensures that its work is carried out at a high level.</translate>
* <translate><!--T:221--> '''Objective 1 – Maintain rapid response time:''' During FY16-17, maintain a two-day initial response time (outside of weekends and staff holidays) to email requests about WMF initiatives through the answers@ and business@ systems. We expect around 1,000 requests in the year.</translate><br><br>
* <translate><!--T:222--> '''Objective 2 – Conduct follow-up surveys:''' Ensure that Support and Safety’s work is effective and useful, the team will survey affected groups to determine how satisfied they are with our help.</translate>
:: <translate><!--T:223--> More details: Throughout the year, Support and Safety will among other core duties support the Wikimedia Foundation’s non-engineering staff in meeting its community-facing questions and needs and support the Executive Director in engaging with the global community, handing complicated correspondence, and emerging issues. Support and Safety will liaise with key community groups, such as the Ombudsman Committee, Stewards, and Arbitration Committees and will work with the Wikimedia Foundation’s Legal team on public requests for such actions as copyright takedowns, requested investigations, and community support.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:224--> Goal 2: Support Foundation efforts to understand community needs</translate> ====
<translate><!--T:225-->
The Program Capacity & Learning team supports the use of listening tools to learn about the needs and ideas of audiences and stakeholders. Examples of listening tools are surveys, community consultations, conference sessions, and participatory budgeting (e.g., Community Wishlist, Inspire campaign). In this way, the team builds capacity for decision-making practices that are engaging, data-driven, and collaborative. ([[Program Capacity and Learning/Annual Plan|more details]])</translate>
Line 477:
</div><!--end Program 10-->
=== <translate><!--T:227--> Program 11: Protect our users, staff, and public</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:228--> Team: [[Support and Safety]]</translate>''
Line 484:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:230--> Goal: Maintain rapid response time and effectively resolve issues</translate> ====
<translate><!--T:231-->
In FY16-17 Support & Safety will maintain staffing support for threats to the safety of people and the projects, including immediate threats to life, limb or property; threats to child safety; inappropriate images; user investigations such as for global or event bans; and inquiries from law enforcement. We will coordinate this work as appropriate with Legal staffing, event organizers, and law enforcement and related entities, including the United States’ Federal Bureau of Investigation, the National Center for Missing and Exploited Children, and the Secret Service.</translate>
* <translate><!--T:232--> '''Objective 1 - Maintain emergency response time:''' During FY16-17, maintain a three-hour initial response time to emergency requests made through our emergency@ inbox. These emergencies include threats to life, limb or property made on our projects or at affiliated events.</translate><br><br>
* <translate><!--T:233--> '''Objective 2 – Maintain non-emergency response time:''' Create an appropriate mechanism to track non-emergency safety inquiries coming through other inboxes (ca@, individual inboxes) and ensure a two-day initial response time (outside of weekends and staff holidays).</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
Line 495:
</div><!--end CE-->
== <translate><!--T:831--> Product</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate><!--T:234-->
Line 520:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:832--> Program 1: Better understand our users</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:240--> Team: [[mw:Wikimedia Discovery|Discovery]], [[mw:Reading|Reading]], and [[mw:Editing|Editing]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:241--> Goal 1: Use research to better understand our users</translate> ====
<translate><!--T:242-->
This goal is directly linked to our first strategic priority: understand our users to better serve their needs, in order to effectively engage and retain both readers and contributors. It also provides insight into what triggers people to move from reading to contributing and highlights blockers to contribution.
Line 535:
* <translate><!--T:244--> '''Objective 1 – Continue our research into the ways readers and editors interact with content:''' Throughout the year, use a variety of generative and evaluative research methods across the product audiences to deepen our understanding of user behavior and the success of our solutions in addressing our goals. These methods include usability testing, concept evaluation, user segmentation, design ethnography (generative research), benchmarking, heuristic evaluations, surveys, and community engagement and feedback. We will apply these methods as appropriate to each project and continue to expand these capabilities across the product organization.</translate><br><br>
* <translate><!--T:245--> '''Objective 2 – Summarize, process, and apply output of [[m:New_Readers|New Readers]] research project:''' In FY15-16, we are performing ethnographic research in four countries underserved by Wikimedia projects: South Africa, Mexico, Nigeria, and India. Synthesize this research and share it with product teams and the community in FY16-17 as a core component of the project.</translate><br><br>
* <translate><!--T:246--> '''Objective 3 – Strengthen research communications:''' Employ a variety of methods to ensure that our understanding of users is communicated across the product organization and the community and is used to qualify product decisions and prioritization. Deliverables will include problem definition, personas, research findings (presentations and reports), demographic analysis and user segmentation, and quantitative usage data from event logging and hadoop.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 1-->
=== <translate><!--T:247--> Program 2: Maintain and improve content discovery</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:248--> Team: [[mw:Wikimedia Discovery|Discovery]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:249-->
Goal 1: Maintain key search functions and enhance capacity</translate> ====
<translate><!--T:250-->
This goal supports the primary mechanism that readers, editors, and third parties use to find our movement’s content. It continues our existing commitments for all public-facing interfaces and increases required for organic growth.</translate>
Line 557 ⟶ 556:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:253--> Goal 2: Improve search on Wikimedia projects</translate> ====
<translate><!--T:254-->
Our goal is to help users more quickly find relevant content within our projects so that the Foundation can better meet the needs of users. Our efforts will be based on quantitative user and feature testing.</translate>
Line 568 ⟶ 566:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:257--> Goal 3: Evolve content discovery and interactive tools on Wikimedia projects</translate> ====
<translate><!--T:258-->
Work on these tools helps WMF with two of its strategic priorities, by increasing and diversifying knowledge and forms of presentation and by increasing volunteer retention and engagement through new opportunities for curation and creation.</translate>
Line 579 ⟶ 576:
</div><!--end Program 2-->
=== <translate><!--T:261--> Program 3: Increase our global reach by increasing readership</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:262--> Teams: [[mw:Reading|Reading]]. [[mw:Reading/Strategy/2016-2017_plan|Strategic Background]]</translate>''
Line 586 ⟶ 582:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:263--> Goal 1: Maintain core readership functions and services</translate> ====
<translate><!--T:264-->
Readers access Wikipedia content millions of times a day, and we need to ensure that experiences are fast and reliable. This goal demonstrates our commitment to maintaining our core Reading experiences as a first priority.</translate>
* <translate><!--T:265--> '''Objective 1 – Maintain current pageview levels:''' Maintain the mobile and desktop websites, and APIs, as well as 29 community and Foundation [[mw:Manual:Extensions|extensions]] that are used across our sites. During the year, we expect readers to view more than 200 billion page views and 100 billion API requests through our sites and APIs.</translate>
* <translate><!--T:266--> '''Objective 2 – Maintain apps:''' Millions of readers rely on the apps to engage with Wikipedia and our sister sites. Since first being introduced in September 2012, we have seen 21 million downloads for our iOS app and 10 million downloads for our Android app. Throughout the year, maintain and update both platforms.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:267--> Goal 2: Improve the encyclopedia experience</translate> ====
<translate><!--T:268-->
For our established audiences, we want to increase retention by improving the presentation of and engagement with encyclopedic content in our current web and app experiences, while retaining the integrity of the fundamental encyclopedia model.</translate>
Line 604 ⟶ 598:
* <translate><!--T:269--> '''Objective 1 – Increase retention across our reading experiences:''' By the end of FY16-17, release new versions of our apps and web experiences with features designed to increase user retention. This will include content notifications, which we anticipate will lead to an increase in sustained return visits. Other features under consideration include an article scoring tool (possibly based on ORES) and article profiles that make it easier to discover new content. We expect to have at least 2 releases per platform in FY16-17. Our goal is to increase our retention by 5% across all of our platforms.</translate><br><br>
* <translate><!--T:270--> '''Objective 2 – Improve article rendering:''' By the end of FY16-17, improve mobile article rendering for the Web, which will give users a more engaging and polished presentation of articles. This will contribute to the goal of increasing retention by 5% on the web platform.</translate><br><br>
* <translate><!--T:271--> '''Objective 3 – Integrate Wikidata: ''' On both the mobile site and the Wikipedia native apps, experiment with using Wikidata to enhance the reading experience – using Wikidata short descriptors in search and article titles to help readers get more context at a glance, as well as building infoboxes from Wikidata to provide a better formatted quick fact lookup experience.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:272--> Goal 3: Launch the New Readers project</translate> ====
<translate><!--T:273-->
The economically less developed regions of the world have [<tvar|jsd>http://www.jsd-africa.com/Jsda/V12No3_Summer2010_A/PDF/A%20Comparative%20Analysis%20of%20Global%20North%20and%20Global%20South%20Economies%20(Odeh).pdf</> 85% of the world’s population], more than [<tvar|gsma>http://www.gsmamobileeconomy.com/GSMA_Global_Mobile_Economy_Report_2015.pdf</> 60% of mobile subscriptions], and only [[<tvar|mail>mailarchive:analytics/2016-February/004950.html</>|30% of our page views]]. There is a clear opportunity for the Foundation to further our mission by reaching new Readers in these geographies.</translate>
* <translate><!--T:274--> '''Objective 1 – Launch one new experience directed at new readers:''' The Reading team will, in co-operation with Communications, Community, Partnerships and Design Research, launch one new experience for a specific geography during FY16-17. The specifications, target markets and features will be developed through
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:275--> Goal 4: Foster a community of readers</translate> ====
<translate><!--T:276-->
This initiative is intended to increase reader engagement by creating new Wikipedia experiences based on interactions with content and other users. The community of readers hypothesis is that there is a wide swathe of readers who are more than casual browsers, but not full encyclopedia article writers, who would like to better interact with knowledge on Wikimedia. We plan to explore curation tasks within this initiative, while being very sensitive to moderation issues at all times.</translate>
Line 629 ⟶ 621:
</div><!--end Program 3-->
=== <translate><!--T:278-->
Program 4: Maintain and improve content creation and editing tools</translate> ===
<div style="border-radius:5px; margin:10px;">
''Team: [[mw:Editing|Editing]]''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:279--> Goal 1: Maintain and incrementally improve current content creation and curation interfaces</translate> ====
<translate><!--T:280-->
Besides maintaining core functionality for the movement, this goal helps WMF move forward its strategic priority: Increase and diversify contribution of quality knowledge by making the tools easier to use.</translate>
* <translate><!--T:281--> '''Objective 1 – Strengthen interfaces:''' Throughout the year, maintain and incrementally improve content creation and curation interfaces. These interfaces, like [[mw:VisualEditor|that of the visual editor]], give contributors the ability to easily and efficiently contribute writing, photos, and other content to our websites. Work on a unified, consistent editing interface between the mobile and desktop Web experiences, and between visual and wikitext editors. In support of these changes, unify around a single Wikitext parser for both reading and editing.</translate>
* <translate><!--T:282--> '''Objective 2 – Expand the core of MediaWiki to support new kinds of content:''' By the end of FY16-17, add support in MediaWiki for pages and revisions capable of storing multiple types of content simultaneously. For example, each revision of a video description page will encapsulate the state of the video, its subtitles, its metadata, the text of the description page and the associated wiki metadata such as protection levels at that particular time. This will help existing contributor workflows and allow us to provide powerful new kinds of content.</translate><br><br>
* <translate><!--T:283--> '''Objective 3 – Streamline metadata editing:''' Throughout the year, simplify the editing of page metadata, such as page titles, protection levels, incoming [[m:Help:Redirect|redirects]] and other information, in order to allow contributors to more easily and efficiently manage contributions – both their own and those of others.</translate><br><br>
Line 647 ⟶ 638:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:285--> Goal 2: Improve editing experience by reducing technical debt</translate> ====
<translate><!--T:286-->
By reducing technical debt of improving tools and features, we position communities and the Foundation to more effectively meet our strategic priority: increase and diversify contribution of knowledge.</translate>
Line 657 ⟶ 647:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:288--> Goal 3: Invest in bringing existing editing tools to new devices</translate> ====
<translate><!--T:289-->
As more people engage on mobile devices instead of desktop, making existing tools work effectively on mobile is critical to our long-term success. This helps position us to meet our strategic priorities: 1) Understand our users to better serve their needs by experimenting with mobile needs, and 2) Increase and diversify contribution of quality knowledge.</translate>
Line 667 ⟶ 656:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:291--> Goal 4: Invest in new types of content creation, curation and collaboration tools</translate> ====
<translate><!--T:292-->
This goal is critical to our vision of every single human being freely sharing in knowledge. By offering better translation tools, we can move forward two key strategic priorities: 1) Increase volunteer retention and engagement, and 2) Increase and diversify contribution of quality knowledge.</translate>
Line 677 ⟶ 665:
</div><!--end Program 4-->
=== <translate><!--T:294--> Program 5: Maintain and build contributor tools</translate> ===
<div style="border-radius:5px; margin:10px;"><!--Links in this section and its goals will all go blue when this is moved to meta, don't worry-->
''<translate><!--T:295--> Team: [[Community Tech]]</translate>''
Line 690 ⟶ 677:
* <translate><!--T:298--> '''Objective 1 - Top 10 wishes:''' In 2016, the team is responsible for investigating and addressing the top 10 wishes from the 2015 survey, including</translate>:
** [[Special:MyLanguage/Community Tech/Migrate dead external links to archives|<translate><!--T:299--> A multi-language bot that identifies dead external links, and directs those links to an archived version</translate>]]
** [[Community Tech/Pageview stats tool|<translate><!--T:300--> A new pageview stats tool to replace stats.grok.se</translate>]]
** [[Community Tech/Cross-wiki watchlist|<translate><!--T:301--> Cross-wiki watchlists</translate>]]
** [[Community Tech/Numerical sorting in categories|<translate><!--T:302--> Fixing numerical sorting in categories</translate>]]
** [[Community Tech/Improve
** [[Community Tech/Improved diff
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:305--> Goal 2: Tool labs support</translate> ====
<translate><!--T:306-->
Working with volunteer developers is an important part of Community Tech’s work. Popular contribution tools and bots become de facto production software needed to keep the wikis healthy and happy, but when a tool has a single maintainer, there’s a high risk that it will be abandoned. To mitigate against this risk, the team will improve Wikimedia Tool Labs as a center for volunteer development support, including a framework of best practices and communication, allowing projects to grow beyond what can be accomplished by a single motivated individual. This speaks directly to our strategic priority to increase volunteer retention and engagement.</translate>
Line 710 ⟶ 696:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:309--> Goal 3: Represent both large and small communities through the Community Wishlist</translate> ====
<translate><!--T:310-->
The Community Wishlist has been well received with more than 600 people participating. However, we did identify one issue with the 2015 survey, which was that the support-voting process privileged larger projects. While the Wikisource communities were a strong presence in the 2015 survey, especially considering their relative size, but they couldn’t muster enough votes for any of their proposals to break into the top 10. The process needs to allow both large and small communities to be heard.</translate>
* <translate><!--T:311--> '''Objective 1 – Conduct a modified community wishlist:''' Modify the 2016 survey process to include some carve-out space for smaller projects, to which a portion of developer time would be allocated. Conduct the new survey by December 2016 to gather a new set of proposals from the communities.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
Line 721 ⟶ 706:
</div><!--end Product-->
== <translate><!--T:312--> Technology</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate><!--T:313-->
Line 734 ⟶ 718:
</translate>
=== <translate><!--T:316--> Program 1: Improve tools that help us understand user needs</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:317--> Team: [[mw:Analytics|Analytics]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <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).
* <translate><!--T:319--> '''Objective 1 – Improve tools for data display for the Foundation and community:''' By the end of FY16-17, make tools more efficiently display overview data about editing and pageviews of the Wikimedia projects, so that the Foundation and the community can monitor the sites, understand what is happening on an overall level, and develop insights without having to use a query interface. This will involve deploying a new storage for data tailored for easier access.</translate>
:: <translate><!--T:320--> Note: Baseline data unavailable; it will be established, and then progress will be measured as part of this objective.</translate><br><br>
* <translate><!--T:321--> '''Objective 2 – Improve data computing and release processes:''' By the end of FY16-17, improve computing and dataset creation processes so that more actionable data can be released to the community, and make improvements that save storage space and therefore reduce costs. This will improve the response times of Pageview APIs (median < 1 sec), bot detection on Pageview API datasets, and release of new datasets to community.</translate>
* <translate><!--T:322--> '''Objective 3 – Real-time data processing:''' By the end of FY16-17, build a platform that will enable real-time data processing of what’s trending for pageview articles, save network storage capacity, and reduce costs of the infrastructure. This potentially will lead to new tools and services for the community and Foundation.</translate><br><br>
* <translate><!--T:323--> '''Objective 4 – Build compatibility between key databases:''' By the end of FY16-17, improve compatibility among key databases, allowing users to query them in ways that will
:: <translate><!--T:324--> More detail: No longer limited by resource constraints in MySQL. Frees DBA time as it removes one big piece of work our only DBA needs to attend to now. Teams benefit from being able to join distinct data sources (hadoop and mediawiki database). Such a pipeline does not exist today.</translate><br><br>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 1-->
=== <translate><!--T:325--> Program 2: Expand research capabilities</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:326--> Teams: [[mw:Wikimedia Research|Research and Data]], [[mw:Technical Operations|Technical Operations]], [[mw:Wikimedia_Research/Design_Research|Design Research]] (see objective)</translate>''
Line 763 ⟶ 744:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:328--> Goal 1: Build an open infrastructure to increase the volume, quality, and reproducibility of research on Wikimedia projects</translate> ====▼
▲Goal 1: Build an open infrastructure to increase the volume, quality, and reproducibility of research on Wikimedia projects</translate> ====
<translate><!--T:329-->
In FY15-16 the Research team delivered a number of projects to support volunteers performing content curation and content creation. [[Research:Revision scoring as a service|Revision scoring as a service]] brought to Wikimedians an easy way to automatically assess the quality of articles and individual revisions via a set of [[Objective Revision Evaluation Service|open APIs]], currently available in 16 languages/projects. [[Research:Increasing article coverage|Article recommendations]] showed they have the potential to triple the content creation rate while maintaining the same level of quality as organically created articles and have since been integrated into the Content Translation tool. In FY16-17 we will expand these efforts on research infrastructure that supports Wikimedia communities.
Line 770 ⟶ 750:
* <translate><!--T:330--> '''Objective 1 – Understand the editing culture:''' By the end of FY16-17, conduct research that builds on previous studies of newcomer socialization and mentorship. Focus on editors and how to increase their ability to work more effectively with projects. Analyze the effects of harassment and disrespectful behavior, to better understand how they affect the retention of new contributors and to eliminate barriers to contribution. ([[mw:Wikimedia Research|Research and Data team]])</translate><br><br>
* <translate><!--T:331--> '''Objective 2 – Evaluate AI as a service to help volunteers improve quality:''' Throughout FY16-17, continue efforts to design and evaluate services making artificial intelligence available as a service to volunteers and tool developers. Expand revision scoring as a service to make scores and quality assessments readily available to our communities via open APIs. Design and test recommender systems to support community initiatives such as edit-a-thons and outreach events and allow volunteers to easily identify tasks and areas in need of quality improvement or contributions. ([[mw:Wikimedia Research|Research and Data team]])</translate><br><br>
* <translate><!--T:332--> '''Objective 3
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:333--> Goal 2: Expand the Foundation’s research capacity by partnering with researchers in industry and academia</translate> ====▼
▲Goal 2: Expand the Foundation’s research capacity by partnering with researchers in industry and academia</translate> ====
<translate><!--T:334-->
In FY15-16 we developed an [[wmf:Open access policy|Open Access policy]] to simplify how we collaborate with researchers and to ensure that the output of these collaborations be made immediately available under open licenses, consistently with our mission. Some of our most successful projects this year are the result of [[mw:Wikimedia Research/Formal collaborations|formal collaborations]]. In FY16-17 we plan to expand the Research team’s capacity via short-term internships and formal collaborations with industry and academia, under the terms this policy, to reduce the overall cost for the organization to conduct research projects.</translate>
* <translate><!--T:335--> '''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
* <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>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:337--> Goal 3: Perform evaluative design research to iterate concepts and designs focusing on usability and solving problems and unmet needs for users</translate> ====▼
▲Goal 3: Perform evaluative design research to iterate concepts and designs focusing on usability and solving problems and unmet needs for users</translate>====
<translate><!--T:338-->
Our goal is to help the organization validate and iterate design concepts, to ensure usability and products being built around the needs of users. We employ usability testing, concept testing, surveys and co-design with users, and collaborate with product teams toward these ends.</translate>
* <translate><!--T:339--> '''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>
* <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>
* <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>
Line 798 ⟶ 776:
</div><!--end Program 2-->
=== <translate><!--T:342--> Program 3: Improve site reliability</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:343--> Teams: [[mw:Technical Operations|Technical Operations]], [[mw:Wikimedia Security Team|Security]], [[mw:Wikimedia Architecture Team|Architecture]], [[mw:Wikimedia Services|Technology Services]] (see objective)</translate>''
Line 817 ⟶ 794:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:350--> Goal 2: Overhaul legacy systems to provide an open structure that supports customization and new editor features</translate> ====▼
▲Goal 2: Overhaul legacy systems to provide an open structure that supports customization and new editor features</translate> ====
<translate><!--T:351-->
Many of our sites were built 10-15 years ago as closed systems. These legacy architectures limit our ability to build new features and tools and to make major performance improvements. By updating our systems using current technologies, we will be able to produce a better experience for both readers and editors, including the ability to experiment and adapt the look/feel, functionality, and tools available, as well as improved performance. This is essential underlying work to support our strategic priority of providing better contribution tools.</translate>
Line 830 ⟶ 806:
</div><!--end Program 3-->
=== <translate><!--T:356--> Program 4: Improve site performance</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:357--> Teams: [[mw:Wikimedia Performance Team|Performance]], [[mw:Technical Operations|Technical Operations]] (see objective)</translate>''
Line 837 ⟶ 812:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:358-->
Goal 1: Make access to Wikipedia faster and more reliable, especially for mobile and global users</translate> ====
<translate><!--T:359-->
For the Wikimedia movement to be truly global, we have to provide excellent access around the world. With more people accessing our sites and creating content via mobile phones, we have to ensure that the sites are available, even if their Internet connections are limited or devices are basic. At the moment, all logged-in user traffic is handled by a single data center in Ashburn, Virginia. By the end of the fiscal year, we plan to serve users from our Texas and Virginia locations allowing us to improve access and provide substantial user value by expanding the reach of our infrastructure in a manner that is both cost-effective and maintainable. This work will allow the Foundation to expand to other data centers as needed in the future, significantly reducing both operational costs and time delays to users.</translate>
Line 844 ⟶ 819:
* <translate><!--T:361--> '''Objective 2 – Move all URL-routing to PHP:''' By the end of Q2 in FY16-17, reduce the current complexity so that when a user enters a URL, the site quickly serves up that content, reducing processing time and increasing our ability for search engine optimization. This means that instead of multiple layers (Varnish, Apache, and HHVM), we will use a common software language, PHP, and move URL-routing logic from Apache to MediaWiki. ([[mw:Wikimedia Performance Team|Performance team]])</translate><br><br>
* <translate><!--T:362--> '''Objective 3 – Improve site availability:''' In the second half of FY16-17, reduce the time it takes to recover from a failure of our primary data center by half. ([[mw:Wikimedia Performance Team|Performance team]], [[mw:Technical Operations|Technical Operations team]])</translate>
:: <translate><!--T:363--> Note: Baseline data unavailable; it will be established, and then progress will be measured as part of this objective.</translate><br><br>
* <translate><!--T:364--> '''Objective 4 – Deploy Asian caching POP:''' Starting in Q3 FY 2017 and expected to be completed by Q2 FY 2018, optimize site access for our Asian audiences by deploying a small caching data center in Asia. ([[mw:Technical Operations|Technical Operations team]])</translate><br><br>
{{Back to top|arrow text=Back to top}}
Line 850 ⟶ 825:
</div><!--end Program 4-->
=== <translate><!--T:365--> Program 5: Expand the way software is tested</translate> ===
<div style="border-radius:5px; margin:10px; ">
''<translate><!--T:366--> Team: [[mw:Wikimedia Release Engineering Team|Release Engineering]]</translate>''
Line 859 ⟶ 833:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px;background-color:#F7F8FF">
==== <translate><!--T:368--> Goal: Add a new automated browser testing framework in a more popular programming language, namely [[w:JavaScript|Javascript]]</translate> ====▼
▲Goal: Add a new automated browser testing framework in a more popular programming language, namely [[w:JavaScript|Javascript]]</translate> ====
<translate><!--T:369-->
Currently, production testing for Wikimedia can only be created using the [[w:Ruby_%28programming_language%29|Ruby]] programming language, limiting the number of developers who create and maintain the end-to-end test suites. By adding JavaScript capability, we will greatly increase the ability of developers inside and outside the Foundation to more quickly and frequently test the software updates that our sites’ users and contributors use every day.</translate>
Line 870 ⟶ 843:
</div><!--end Technology-->
== <translate><!--T:371--> Strategic Partnerships</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
=== <translate><!--T:372--> Program 1: Increase partnerships and promotions</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:373--> Team: [[wmf:Staff and contractors#Partnerships and Global Reach|Strategic Partnerships]]</translate>''
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:374--> Goal: Increase readership and revenue to support the Foundation</translate> ====
<translate><!--T:375-->
The team will provide value for the Foundation through partnerships that increase readership, receive informative or actionable data from partners, or result in corporate donations.</translate>
Line 891 ⟶ 861:
</div><!--end Program 1-->
=== <translate><!--T:378--> Program 2: Carefully grow Wikipedia Zero</translate> ===
<div style="border-radius:5px; margin:10px; ">
''<translate><!--T:379--> Team: [[Global Reach]]</translate>''
Line 900 ⟶ 869:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px;background-color:#F7F8FF">
==== <translate><!--T:380--> Goal: Remove the barrier of cost and increase readership</translate> ====
<translate><!--T:381-->
As data charges remain high in many countries in Africa, Asia, Latin America, and Middle East, Wikipedia Zero continues to be relevant to provide access to Wikimedia projects to under-served populations in these geographies.</translate>
* <translate><!--T:382--> '''Objective 1 – Build new [[wmf:Wikipedia Zero|Wikipedia Zero]] partnerships:''' In 2016-2017, the Global Reach team will adopt a more focused approach, only pursuing proactive partnerships in our
* <translate><!--T:383--> '''Objective 2 – Refine the [[wmf:Wikipedia Zero|Wikipedia Zero program]]:''' During the course of next fiscal year, the Global Reach team will focus on understanding the impact Wikipedia Zero has had with different kinds of users – from general readers to active editors – to allow for better data-driven decision making.</translate><br><translate><!--T:835--> '''More details''': We have learned about the program’s impact through practical experience in the countries and communities where the program is active. Recently, we started [[Global_Reach#Understanding_the_Global_South_readers|conducting phone surveys]] to collect quantitative data related to our anecdotal experiences. We have completed these surveys in [[Global Reach/Ghana Survey|Ghana]] and [[Global Reach/Mexico Survey|Mexico]], with Nigeria and India planned next. We also plan to do a community consultation along with an on-wiki survey to understand the program’s impact and
* <translate><!--T:384--> '''Objective 3 – Establish at least one outreach or community support activity with a Wikipedia Zero partner:''' The Global Reach team will work with an existing mobile operator partner to further distribution, access, and awareness of Wikipedia in a Wikipedia Zero country by the end of fiscal year 2016-17.</translate><br><translate><!--T:836--> '''More details''': We want to strengthen the communication and overall connection with Wikimedia affiliates and community at large. When an unintended problem caused by zero-rating arises, our team will continue to take responsibility and work with the communities affected to find the best way to address it. When we have partnership opportunities that would affect and/or interest our communities, they will be involved early and often. Our team is committed to ensuring that the Wikipedia Zero program is always contextually aware and supportive of our mission.</translate><br><br>
{{reflist}}
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
</div><!--end Program 2-->
=== <translate><!--T:385--> Program 3: Increase reach through new types of partnerships</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:386--> Team: [[Global Reach]]</translate>''
Line 923 ⟶ 890:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:387-->
Goal: Expand Wikimedia projects’ awareness and usage through new partnerships</translate> ====
<translate><!--T:388-->
While working on Wikipedia Zero over the last four years, we have identified key barriers that go beyond affordability and require diverse types of partnerships. Lack of awareness about Wikipedia, infrastructure limitations, low digital literacy, and gender inequality are some of the issues we face when trying to expand awareness and access to Wikimedia content.</translate>
Line 933 ⟶ 900:
</div><!--end Strategic Partnerships-->
== <translate><!--T:390--> Communications</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate>
Line 943 ⟶ 910:
</translate>
=== <translate><!--T:393--> Program 1: Improve public understanding and appreciation for Wikimedia movement and projects</translate> ===▼
▲Program 1: Improve public understanding and appreciation for Wikimedia movement and projects</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:394--> Team: [[Communications]]</translate>''
Line 951 ⟶ 917:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:395--> Goal 1: Understand current public perception</translate> ====
<translate><!--T:396-->
Conduct research and analysis to understand public perception of Wikimedia projects and community using sources including international press and social media.</translate>
* <translate><!--T:397--> '''Objective 1 – Conduct coverage audit from past year:''' Review top narratives, outlets, geographies, sentiment surrounding Wikipedia, Wikimedia projects, and the Wikimedia Foundation to better understand FY15-16 coverage.</translate>
* <translate><!--T:398--> '''Objective 2
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:399--> Goal 2: Develop proactive public messaging strategy for Wikimedia projects</translate> ====
<translate><!--T:400-->
Using insights from Goal 1, build year-long messaging strategy through the end of FY16-17 to guide all proactive messaging and PR work.</translate>
* <translate><!--T:401--> '''Objective 1 – Identify top narratives:''' Use narratives to address gaps or misunderstandings in public perception (based on coverage audit and media monitoring) of Wikimedia movement and projects and support organizational objectives.</translate><br><br>
* <translate><!--T:402--> '''Objective 2 – Build strategy and tactics:''' Outline strategy for increasing awareness of
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:403--> Goal 3: Implement messaging strategy</translate> ====
<translate><!--T:404-->
Inform proactive PR, editorial, and social media with messaging strategy. Remain agile and responsive to incorporate ongoing insights and new objectives.</translate>
* <translate><!--T:405--> '''Objective 1 – Obtain positive international media coverage:''' Build and strengthen relationships with key outlets and secure coverage of top narratives, leveraging community stories and achievements, and the Foundation-led programs and technology.</translate>
* <translate><!--T:406--> '''Objective 2 – Increase engagement with top narratives:''' Reach audiences through digital channels (blog and social) with content related to top narratives. Encourage candid, meaningful discussion and incorporate feedback back into messaging strategy.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
</div><!--end Program 1-->
=== <translate><!--T:407--> Program 2: Make our brand more consistent, relatable, and more easily understood</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:408--> Team: [[Communications]]</translate>''
Line 993 ⟶ 955:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:410--> Goal 1: Expand storytelling and video production</translate> ====
<translate><!--T:411-->
We develop inclusive processes to create shareable materials for the use of the entire movement, and outside media sources. Stories and pictures explain the people, values, and efforts of Wikimedians to new audiences.</translate>
* <translate><!--T:412--> '''Objective 1 – Build testimonials of volunteer efforts:''' Help explain the movement to donors and the general public by building at least 15 new interviews of community members that can be used in outreach materials. They will be from around the globe and explain a variety of volunteer efforts.</translate>
* <translate><!--T:413--> '''Objective 2 – Develop videos of volunteer events:''' Produce guidelines (Q1) for, and publish, 10 short videos (dependent on event timing) based on video shot from throughout the movement representing volunteer events and explaining aspects of Wikimedia. This will reach millions of casual social media users.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 1-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:414--> Goal 2: Design standards and support</translate> ====
<translate><!--T:415-->
Design guidance builds a consistent look and feel over time, which has been proven to increase trust and raise public perception. Increased trust supports collaborative and partnership opportunities for the Foundation and across the movement. Careful stewardship of the movements' brand protects the tremendous cultural and financial value established by volunteers.</translate>
* <translate><!--T:416--> '''Objective 1 – Create annual report:''' Q2 to Q3 of FY16-17, work with Finance and Advancement to create an annual report of FY15-16. As an example, for FY14-15 the annual report was [<tvar|15>https://15.wikipedia.org/index.html</> integrated with Wikipedia’s 15th birthday].</translate>
* <translate><!--T:417--> '''Objective 2 – Expand design capacities:''' Assist with creative brief, plan and style guides; review of all organization materials including monthly metrics and other initiatives. Increase response time for community requests. This is an ongoing core capacity.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
</div><!--end Program 2-->
=== <translate><!--T:418--> Program 3: Identify and build understanding of new audiences</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:419--> Team: [[Communications]]</translate>''
Line 1,023 ⟶ 983:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:421--> Goal 1: Understand new readers</translate> ====
<translate><!--T:422-->
Continue research in 2+ countries (Nigeria, India, Brazil, Indonesia, or Egypt) in cooperation with Design Research, Readership, Global Reach, and Community Engagement teams.</translate>
* <translate><!--T:423--> '''Objective 1 – Establish personas:''' Establish guiding "new reader" personas that typify user habits, needs, media preferences, and technologies. Timing is tied to research.</translate><br><br>
Line 1,033 ⟶ 992:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:424--> Goal 2: Segment existing audiences</translate> ====
<translate><!--T:425-->
Identify and connect audiences with new Wikimedia products to increase Wikimedia project adoption or deepen user engagement.</translate>
Line 1,043 ⟶ 1,001:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:427--> Goal 3: Build feedback loops</translate> ====
<translate><!--T:428-->
Identify and implement feedback loops for audiences, including owned channels (social media), surveys, and more. Building a feedback loop means to establish a practice of collecting feedback, making improvements on that feedback, and reviewing that cycle. It should be iterative.</translate>
Line 1,053 ⟶ 1,010:
</div><!--end Program 3-->
=== <translate><!--T:430-->
Program 4: Increase awareness and product adoption among specific audience segments</translate> ===
<div style="border-radius:5px; margin:10px;">
Line 1,067 ⟶ 1,024:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:434--> Goal 1: Raise Wikimedia awareness among new readers</translate> ====
<translate><!--T:435-->
Develop strategies for selected audience segments to increase user engagement in low readership countries. Refine based on performance.</translate>
* <translate><!--T:436--> '''Objective 1 – Target new readers with messaging campaigns:''' Develop messaging campaigns in 1 country with low readership based on Program 3 (Identify and build understanding of new audiences) research.</translate>
* <translate><!--T:437--> '''Objective 2 – Expand press coverage:''' Execute campaigns to raise new reader awareness for Wikimedia by earning local press and social media coverage.</translate>
* <translate><!--T:438--> '''Objective 3 – Measure performance:''' Measure initial campaign impact against control baseline. Establish new, appropriate benchmarks for performance measurement, continue to iterate campaign to continuously improve performance.</translate><br><br>
{{Back to top|arrow text=Back to top}}
Line 1,078 ⟶ 1,035:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:439--> Goal 2: Showcase Wikimedia’s relevant content and share our mission through emerging digital communications platforms and services</translate> ====
<translate><!--T:440-->
We will use new social platforms to help people interact with Wikimedia content in the newest, most relevant ways.</translate>
* <translate><!--T:441--> '''Objective 1 – Grow three new social channels, with at least one in Asia:''' By using emerging communications platforms and services, show how Wikipedia/Wikimedia continues to be relevant in the world of shared online content and help people interact with Wikimedia content in new ways.</translate>
* <translate><!--T:442--> '''Objective 2 – Pilot distribution program:''' Pilot one new Wikimedia content distribution program on social media targeting new audience segment.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 2-->
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:443--> Goal 3: Introduce and advocate new products</translate> ====
<translate><!--T:444-->
Develop and launch product-specific campaigns, with campaign specific KPIs and targets for measuring impact. Refine based on performance.</translate>
* <translate><!--T:445--> '''Objective 1 – Create product campaigns:''' Design two product-specific campaigns to have statistically significant impact on user adoption and engagement. Specific metrics are TBD based on research in Program 3 (Identify and build understanding of new audiences).</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
Line 1,106 ⟶ 1,063:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:449-->
Goal 1: Spread broad messaging to new and existing communities</translate> ====
<translate><!--T:450-->
We will represent Wikimedia and Wikipedia with verified accounts on the largest social media channels as a global information source.</translate>
Line 1,123 ⟶ 1,080:
We will help explain and raise awareness of the movement by profiling community members, highlighting new initiatives, and explaining the best of the Foundation's work. We will measure this with press mentions, traffic to the blog and online engagement, such as social media mentions.</translate>
* <translate><!--T:457--> '''Objective 1 – Feature Wikipedians:''' Profile or feature Wikipedians from 10+ countries in posts and the community digest, including priority strategic growth countries (Nigeria, Egypt, India, Indonesia, Brazil, Mexico). Grow engagement, relationships and awareness in key areas: specific metrics will be developed on a country-by-country basis.</translate>
* <translate><!--T:458--> '''Objective 2 – Increase the Foundation blog readership:''' Grow Wikimedia Foundation blog readership by 5% and increase social engagement on posts about the blog in order to engage community with our created content.</translate>
* <translate><!--T:459--> '''Objective 3 – Distribute video:''' Distribute video to relevant audiences focusing on the Wikimedia movement and projects, achieving 50,000 views per video on social media as well as embeds on other websites. This will share a human view of the movement in new areas, to go beyond text on a website. (see Goal 1 under Program 2).</translate><br><br>
{{Back to top|arrow text=Back to top}}
Line 1,130 ⟶ 1,087:
<div style="border-radius:5px;border:2px dotted; margin-top:10px; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:460--> Goal 3: Cultivate new communities to support future growth of the projects</translate> ====
<translate><!--T:461-->
Just as we have a community of editors that is at the core of the Wikimedia projects, we can also use our social channels to cultivate communities of people who love and support Wikipedia.
* <translate><!--T:462--> '''Objective 1 – Engage through social media:''' Strategically and continually share relevant information on social media to encourage engagement and connect with readers who want to take part more in the movement. By strategically posting on timely subjects we can demonstrate Wikipedia’s growing relevance in current events. Target of 1M engagements (reactions, comments and shares) per month.</translate><br><br>
* <translate><!--T:463--> '''Objective 2 – Connect with growing communities:''' Gain important insights about our readers and build relationships with new or growing communities by building sustained insight relationships with 25 users across priority countries.</translate>
{{Back to top|arrow text=Back to top}}
</div><!--end goal 3-->
Line 1,142 ⟶ 1,098:
</div><!--end Communications-->
== <translate><!--T:464--> Legal</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate>
Line 1,156 ⟶ 1,111:
</translate>
=== <translate><!--T:468--> Program 1: Protect project trademarks and practices</translate> ===
<div style="border-radius:5px; margin:10px;>
''<translate><!--T:469--> Team: [[Legal]]</translate>''
Line 1,165 ⟶ 1,119:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:471--> Goal: Protect project trademarks</translate> ====
<translate><!--T:472-->
We will grant licenses to project marks that support the mission of the Wikimedia communities and enforce proper use of those marks to protect the reputation and mission of the communities and projects.</translate>
* <translate><!--T:473--> '''Objective 1 – Support mission-based community use:''' Continue to advise community members and others on the application of our open [[wmf:Trademark_policy|Trademark Policy]],
* <translate><!--T:474--> '''Objective 2 – Granting mission-oriented licenses:''' We receive requests to use project trademarks in contexts from t-shirts to popular movies and television. Consider each request and selectively grant trademark licenses to promote the project brands in contexts that will uphold their community-built reputation and attract new users consistent with our mission.</translate>
* <translate><!--T:475--> '''Objective 3 – Enforcement against misuse of marks:''' Defend the community-entrusted marks to help ensure their good reputation. Send cease and desist letters relating to deceptive or improper use of the marks on- and offline. To fight cybersquatters and fraudulent use, file [[w:World_Intellectual_Property_Organization|World Intellectual Property Organization (WIPO)]] actions, when appropriate, to protect the reputation vested in the project marks.</translate><br><br>
* <translate><!--T:476--> '''Objective 4 – Maintain and defend project marks worldwide:''' As part of our overall program, maintain project trademark registrations and domains worldwide, and defend them against wrongful legal and administrative challenges, including those from government offices and third parties globally.</translate><br><br>
Line 1,179 ⟶ 1,132:
</div><!--end Program 1-->
=== <translate><!--T:477--> Program 2: Support community members in unfair litigation while defending our mission</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:478--> Team: [[Legal]]</translate>''
Line 1,188 ⟶ 1,140:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:480--> Goal: Support community members who are facing unfair litigation</translate> ====
<translate><!--T:481-->
We will help community members when they are sued unjustly in connection with their activities on the projects to ensure that they are supported in their mission to create and disseminate Wikimedia free content. We assist community members to find legal counsel, and we often provide funding for their defense. With the support of a worldwide network of outside counsel, virtually all litigation to date has been successful under these programs.</translate>
* <translate><!--T:482--> '''Objective 1 – Administer the Defense of Contributors Program:''' Administer the [[Legal/Legal_Policies#Defense_of_Contributors|Defense of Contributors Program]] to provide support and funding when a contributor is sued in relation to their legitimate activities on the projects.</translate>
* <translate><!--T:483--> '''Objective 2 – Administer the Legal Fees Assistance Program:''' Administer the [[Legal/Legal_Fees_Assistance_Program|Legal Fees Assistance Program]] to provide support and funding when a community member who serves in an administrative or governance function is sued in relation to their legitimate activities on the projects.</translate><br><br>
{{Back to top|arrow text=Back to top}}
Line 1,199 ⟶ 1,150:
</div><!--end Program 2-->
=== <translate><!--T:484--> Program 3: Protect the communities’ discretion in determining proper content</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:485--> Team: [[Legal]]</translate>''
<translate><!--T:486-->
The Wikimedia communities exercise their editorial discretion in creating and reviewing content on the projects. To support this critical role, the Foundation only acts on content takedown notices when legally and factually required. We aggressively oppose unwarranted demands to remove content. We research and clarify the law in areas not well established.</translate>
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:487--> Goal: Ensure that the communities retain their editorial discretion with respect to project content</translate> ====▼
▲Goal: Ensure that the communities retain their editorial discretion with respect to project content</translate>====
<translate><!--T:488-->
We will aggressively oppose demands to remove content when inconsistent with facts and law.</translate>
Line 1,218 ⟶ 1,167:
</div><!--end Program 3-->
=== <translate><!--T:490--> Program 4: Join with the Wikimedia communities in advocating for policy positions relevant to the work of the communities</translate> ===▼
▲Program 4: Join with the Wikimedia communities in advocating for policy positions relevant to the work of the communities</translate>===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:491--> Team: [[Legal]]</translate>''
Line 1,227 ⟶ 1,175:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:493--> Goal: Address issues of future importance to the projects</translate> ====
* <translate><!--T:494--> '''Objective 1 – Coordination and identification:''' Coordinate with members of the communities via the [[policy:|Public Policy Portal]] and [[mail:publicpolicy/|Public Policy Mailing List]] to determine which issues should be addressed to best support the worldwide communities.</translate><br><br>
Line 1,236 ⟶ 1,183:
</div><!--end Program 4-->
=== <translate><!--T:496--> Program 5: Maintain transparency in our defense of content and user privacy</translate> ===
<div style="border-radius:5px; margin:10px;">
''<translate><!--T:497--> Team: [[Legal]]</translate>''
Line 1,245 ⟶ 1,191:
<div style="border-radius:5px;border:2px dotted; padding:10px 10px 20px; background-color:#F7F8FF">
==== <translate><!--T:499--> Goal: Fight censorship and report on efforts to modify content or obtain user data</translate> ====
<translate><!--T:500-->
Inform users and the public about requests to alter the projects or to obtain user information.</translate>
* <translate><!--T:501--> '''Objective 1 – Publication of biannual Transparency Report:''' The Transparency Report details requests we receive to alter or remove content, and to obtain nonpublic user information, from governments, businesses, and others. Publish this report twice a year, approximately in February and July.</translate>
* <translate><!--T:502--> '''Objective 2 – Resist demands to remove content or provide nonpublic user information:''' As noted above, when we receive requests to remove or alter project content, we will push back, unless otherwise compelled by facts and law. In 2015, we received 454 requests, and we denied all of them. Similarly, we will not provide nonpublic user data, unless confronted by legitimate legal process or emergency, as described in our [[wmf:Requests_for_user_information_procedures_%26_guidelines|requests for user information procedures and guidelines]]. In 2015, we received 48 requests for user data, 13 of which were informal requests from governments, and we denied all but one.</translate><br><br>
{{Back to top|arrow text=Back to top}}
Line 1,257 ⟶ 1,202:
</div><!--end Legal-->
== <translate><!--T:503--> Non-programs</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
<translate><!--T:504-->
Fundraising, Fundraising Tech, Legal, Talent and Culture, Team Practices, and Finance and Administration are considered operational. While their work represents a minority percentage of our budget, it is crucial to the strength of our organization, the health of our culture, and every success of the Foundation.</translate>
=== <translate><!--T:505--> Fundraising</translate> ===
<translate>
<!--T:506-->
Line 1,273 ⟶ 1,218:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:508--> Fundraising Tech</translate> ===
<translate><!--T:509-->
The Fundraising Tech team supports ongoing fundraising goals by maintaining and improving the existing systems used by the Online Fundraising and Major Gifts teams. We maintain and improve all existing online fundraising systems and integrated third-parties upgrades. New projects for FY16-17 include adapting to cross-border donation laws, and supporting global credit card processor mergers. Long-term scalability improvements to our customer relationship management system and work to identify and remove pain points in working with our donor data are also part of our core efforts.</translate>
Line 1,280 ⟶ 1,224:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:510--> Legal</translate> ===
<translate>
<!--T:511-->
Line 1,298 ⟶ 1,241:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:515--> Talent and Culture</translate> ===
<translate>
<!--T:516-->
Line 1,310 ⟶ 1,252:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:518--> Team Practices</translate> ===
<translate><!--T:519-->
The Team Practices Group (TPG) facilitates the use of practices and processes that support the health of teams across the Foundation, with a strong emphasis on creating conditions of clarity, trust, and continuous improvement. The team accomplishes this work through dedicated resourcing, lightweight coaching, and workshops at the Wikimedia Foundation.</translate>
Line 1,317 ⟶ 1,258:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:520--> Finance and Administration</translate> ===
<translate>
<!--T:521-->
Line 1,338 ⟶ 1,279:
</div><!--end non-programs-->
== Staffing ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
=== <translate><!--T:526--> 1. Please describe your organization's staffing plan or strategy here, or provide a link to your organization's staffing plan or organogram</translate> ===▼
▲1. Please describe your organization's staffing plan or strategy here, or provide a link to your organization's staffing plan or organogram</translate>===
<div style="border-radius:5px; padding:10px 10px 20px;>
{| class="wikitable"
Line 1,361 ⟶ 1,300:
</div><!--end P vs NP-->
=== <translate><!--T:544--> 2. # of staff by departments or functions</translate> ===
<div style="border-radius:5px; padding:10px 10px 20px;">
{| class="wikitable"
Line 1,377 ⟶ 1,316:
| <translate><!--T:558--> Communications</translate>|| {{FORMATNUM:11}}|| {{FORMATNUM:10}} || {{FORMATNUM:10}}
|-
| <translate><!--T:562--> Legal</translate>|| {{FORMATNUM:12}}
|-
| <translate><!--T:566--> Advancement (Fundraising/Partnerships)</translate>|| {{FORMATNUM:23}} || {{FORMATNUM:20}}
|-
| <translate><!--T:570--> Talent & Culture and Team Practices</translate> || {{FORMATNUM:19}} || {{FORMATNUM:19}} || {{FORMATNUM:19}}
Line 1,392 ⟶ 1,331:
</div><!--end departments-->
=== 3. Staffing expenses ===
<div style="border-radius:5px; padding:10px 10px 20px;">
{| class="wikitable"
|+ style="font-style:italic;align:left"|<translate><!--T:586--> Table 6
|-
! style="background-color:#B3CBE6;"|<translate><!--T:587--> Description</translate>
Line 1,440 ⟶ 1,379:
</div><!--end Staffing-->
== <translate><!--T:644--> Financials: FY 2016-17</translate> ==
<div style="border-radius:5px; padding:20px; margin:10px; width:75%">
=== <translate><!--T:645--> Detailed Budget: FY 2016-17 annual plan</translate> ===
{| class="wikitable"
|+ style="font-style:italic"|<translate><!--T:646--> Table 8 - Program and Non-Program Expenses Summary (all amounts in USD)</translate>
Line 1,548 ⟶ 1,487:
{{Back to top|arrow text=Back to top}}
=== <translate><!--T:688-->
Revenues: FY 2016-17 annual plan</translate> ===
<div style="border-radius:5px; padding:10px 10px 20px;">
;1. <translate><!--T:689--> Does your organization plan to draw on its operating reserves during the upcoming funding period to support its expenses? If so, please provide the amount you intend to draw from your reserves here. This should not be included as revenue in the table below.</translate>
Line 1,560 ⟶ 1,499:
</div><!--end revenues-->
=== <translate><!--T:694--> Expenses: upcoming year's annual plan</translate> ===
{| class="wikitable"
|+ style="font-style:italic"|<translate><!--T:695--> Table 9: FY16-17 Annual Plan Expenses - By Departments (all amounts in USD)</translate>
Line 1,593 ⟶ 1,532:
<!--T:719-->
''As part of our annual plan cycle, we identify some of the top potential risks that could threaten the Wikimedia Foundation’s mission to empower people to contribute to the sum of free knowledge. These potential risks cover a broad spectrum, including product and technology, fundraising, community health, legal, operations, communications, and other domains. Below we set out a number of examples.''
<!--T:720-->
| |||