Main Page: Difference between revisions

From atwg
No edit summary
m (Minor tweaks)
Line 1: Line 1:
<div style="max-width:100%;margin:0;font-weight:bold;padding:20px;background-color:#ddd;">
<div style="max-width:100%;margin:0;font-weight:bold;padding:20px;background-color:#ddd;">
In recent months, teams across the organization have authored documents outlining both needs of, and issues with the current WMF technical infrastructure. During conversations around these topics it has become increasingly clear that stakeholders around the organization are not aligned on goals for our infrastructure which this was making it difficult to move discussions forward in a productive way. This purpose of Audiences and Technology Working Group (ATWG) is to gather and organize information on these issues in a systematic way in order to facilitate collaboration, decision making, and solution development within the WMF.
In recent months, teams across the organization have authored documents outlining both the needs of, and issues with the current WMF technical infrastructure. During conversations around these topics, it has become increasingly clear that stakeholders around the organization are not aligned on goals for our infrastructure which was making it difficult to move discussions forward in a productive way. The purpose of the Audiences and Technology Working Group (ATWG) is to gather and organize information on these issues in a systematic way in order to facilitate collaboration, decision making, and solution development within the WMF.
</div>
</div>




{{#invoke:CDP Hierarchy|showGoal|empower the Wikimedia Foundation to accomplish its goals of Knowledge Equity and Knowledge as a Service by evolving and investing in our technology stack to improve its flexibility, maintainability, and sustainability}}
{{#invoke:CDP Hierarchy|showGoal|Empower the Wikimedia Foundation to accomplish its goals of Knowledge Equity and Knowledge as a Service by evolving and investing in our technology stack to improve its flexibility, maintainability, and sustainability}}


{{#ask:[[Category:Outcomes]]
{{#ask:[[Category:Outcomes]]

Revision as of 19:22, 11 February 2018

In recent months, teams across the organization have authored documents outlining both the needs of, and issues with the current WMF technical infrastructure. During conversations around these topics, it has become increasingly clear that stakeholders around the organization are not aligned on goals for our infrastructure which was making it difficult to move discussions forward in a productive way. The purpose of the Audiences and Technology Working Group (ATWG) is to gather and organize information on these issues in a systematic way in order to facilitate collaboration, decision making, and solution development within the WMF.


<graphviz format="png">digraph goal { graph [splines=ortho, nodesep=0.2]; node [shape=box, fontsize=10, fontname="Arial bold"]; edge [color=gray75];

goal [URL="Audiences Technology Working Group", label=<

Empower the Wikimedia Foundation to accomplish its
goals of Knowledge Equity and Knowledge as a Service
by evolving and investing in our technology stack
to improve its flexibility, maintainability, and sustainability

>, style=filled, color=black, fillcolor=dodgerblue4, fontcolor=white];

} </graphviz>


Outcomes Outputs
Outcome 1: Infrastructure for Wikimedia projects can be more easily scaled due to increased modularization, re-use, maintainability, and testability of the technology stack
  • [[Output:1.1|]]
  • [[Output:1.2|]]
  • [[Output:1.3|]]
  • [[Output:1.4|]]
Outcome 2: More of the full functionality of MediaWiki can be delivered across all interfaces, devices, and form factors while maintaining usability, accessibility, and internationalization standards
  • [[Output:2.1|]]
  • [[Output:2.2|]]
Outcome 3: WMF and volunteer engineers and developers are more effectively onboarded using new and improved documentation that is clear, complete, and cohesive
  • [[Output:3.1|]]
  • [[Output:3.2|]]
  • [[Output:3.3|]]
  • [[Output:3.4|]]
Outcome 4: Session management system is isolated from the rest of the platform
  • [[Output:4.1|]]
  • [[Output:4.2|]]
  • [[Output:4.3|]]
  • [[Output:4.4|]]
Outcome 5: It is easier to install, update, deploy, and configure our development, testing, and production environments as well as simple third-party instances of our technology stack