Hi!
The Wikipedia Library has new, free research donations available:
* MIT Press Journals — scholarly journals in the humanities, sciences, and
social sciences (200 accounts)
<http://enwp.org/WP:MIT>
*Loeb Classical Library — Harvard University Press versions of Classical
Greek and Latin literature with commentary and annotation (25 accounts)
<http://enwp.org/WP:Loeb>
*RIPM — music periodicals published between 1760 and 1966 (20 accounts)
<http://enwp.org/WP:RIPM>
*Sage Stats — social science data for geographies within the United States
(10 accounts)
<http://enwp.org/WP:SAGE _Stats>
*HeinOnline — an extensive legal research database, including 2000
law-related journals as well as international legal history materials (25
accounts)
<http://enwp.org/WP:HeinOnline>
Many other partnerships with accounts available are listed on: <
http://enwp.org/WP:TWL/Journals>
Do better research and help expand the use of high quality references
across Wikipedia projects: sign up today!
--The Wikipedia Library Team
<http://meta.wikimedia.org/wiki/The_Wikipedia_Library>
Today the Wikidata Visualization Challenge starts, a competition aimed to
make it easier to understand the value of Wikidata, what is in there,
and/or how it is being created.
The challenge ends June 1 and there are some nice prizes available.
Checkout http://wvc.se for more details.
*Best regards,Jan Ainali*
CEO, Wikimedia Sverige <http://wikimedia.se>
0729 - 67 29 48
*Tänk dig en värld där varje människa har fri tillgång till mänsklighetens
samlade kunskap. Det är det vi gör.*
Bli medlem. <http://blimedlem.wikimedia.se>
Dear Wikimedians,
Today we had a meeting at the Foundation to announce changes in our Product
and Engineering team structure. They represent the outcome of many
conversations with people from across the Wikimedia community and within
the Foundation. These changes will organize our teams around the needs of
people they serve, and empower them to focus deeply on their audiences to
deliver great outcomes.
We’re bringing together our Product and Engineering departments to form new
audience teams, reporting to Damon Sicore, our VP of Engineering. We’re
grouping core research, architecture, performance, and security functions
together, and will begin the search for a Chief Technology Officer (CTO) to
lead our engineering future. And we’re integrating support for Community
Engineering into the broader Community Engagement team. These changes are
effective today.
Earlier this year we set out some goals for our work at the Foundation,
described in our Call to Action
<https://meta.wikimedia.org/wiki/Communications/State_of_the_Wikimedia_Found…>
for 2015. These goals came out of conversations with you, and with
Foundation staff. You’ll see that the first thing we identified was the
need to improve our technology and execution. These goals focused on
defining commitments, data-driven decision making, support for community
engineering requests, and a commitment to engineering leadership.
The new changes reflect these commitments. We have organized our product
engineering around six teams each with unique audiences. This includes a
Community Tech team dedicated to supporting tools for core contributors, as
well as teams for Editing, Reading, Search & Discovery, Infrastructure, and
Fundraising Tech.
In particular, I wanted to share more about the plans for the Community
Tech team. The creation of this team is a direct response to community
requests for more technical support. Their mission is to understand and
support the technical needs of core contributors, including improved
support for expert-focused curation and moderation tools, bots, and other
features. Their mandate is to work closely with you, and the Community
Engagement department, to define their roadmap and deliverables. We are
hiring for a leader for this team, as well as additional engineers. We will
be looking within our communities to help. Until then, it will be incubated
under Toby Negrin, with support from Community Engagement.
We’re also committed to our long-term technology future. A new CTO will
support teams and functions dedicated to performance, architecture,
security, privacy, structured data, user experience, and research. Their
mandate is to keep Wikimedia fast, reliable, stable, and secure -- and to
support the Engineering team in their development of excellent products and
features.
You may notice there is no standalone Product department. We are moving
away from a matrix management structure. Instead, product managers,
designers, analysts, engineers, and others working together will report to
the same manager, who will report through to the VP of Engineering. This is
because we believe that everyone is responsible for user experience and
each team is ultimately responsible for delivering on the product vision
and a roadmap. It also gives teams ability to make decisions that are best
for their audiences, based on their user’s feedback. This represents a
maturation of our organization and processes, and will give each new teams
more focus, dedicated focus, and more support.
I want to thank everyone who has worked so hard to bring this new structure
together. Thank you to everyone in the community, for being thoughtful and
honest with your needs, criticisms and encouragements. Thank you to our
engineers, designers, researchers, and product managers, who have given us
extensive feedback about what works best for you. Thank you to our new team
managers and leads for stepping up into new roles. And thank you to Erik
and Damon, who have worked closely for many months to make this happen.
You can find more information about this new structure, the new teams,
their missions, and leadership, as well as other questions in a FAQ on
Metawiki
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Engineering_reorganiza…>.
We will update the Wikimedia Foundation site Staff page soon to reflect
these new teams.
~~~~Lila