This paper (first reference) is the result of a class project I was part of
almost two years ago for CSCI 5417 Information Retrieval Systems. It builds
on a class project I did in CSCI 5832 Natural Language Processing and which
I presented at Wikimania '07. The project was very late as we didn't send
the final paper in until the day before new years. This technical report was
never really announced that I recall so I thought it would be interesting to
look briefly at the results. The goal of this paper was to break articles
down into surface features and latent features and then use those to study
the rating system being used, predict article quality and rank results in a
search engine. We used the [[random forests]] classifier which allowed us to
analyze the contribution of each feature to performance by looking directly
at the weights that were assigned. While the surface analysis was performed
on the whole english wikipedia, the latent analysis was performed on the
simple english wikipedia (it is more expensive to compute). = Surface
features = * Readability measures are the single best predictor of quality
that I have found, as defined by the Wikipedia Editorial Team (WET). The
[[Automated Readability Index]], [[Gunning Fog Index]] and [[Flesch-Kincaid
Grade Level]] were the strongest predictors, followed by length of article
html, number of paragraphs, [[Flesh Reading Ease]], [[Smog Grading]], number
of internal links, [[Laesbarhedsindex Readability Formula]], number of words
and number of references. Weakly predictive were number of to be's, number
of sentences, [[Coleman-Liau Index]], number of templates, PageRank, number
of external links, number of relative links. Not predictive (overall - see
the end of section 2 for the per-rating score breakdown): Number of h2 or
h3's, number of conjunctions, number of images*, average word length, number
of h4's, number of prepositions, number of pronouns, number of interlanguage
links, average syllables per word, number of nominalizations, article age
(based on page id), proportion of questions, average sentence length. :*
Number of images was actually by far the single strongest predictor of any
class, but only for Featured articles. Because it was so good at picking out
featured articles and somewhat good at picking out A and G articles the
classifier was confused in so many cases that the overall contribution of
this feature to classification performance is zero. :* Number of external
links is strongly predictive of Featured articles. :* The B class is highly
distinctive. It has a strong "signature," with high predictive value
assigned to many features. The Featured class is also very distinctive. F, B
and S (Stop/Stub) contain the most information.
:* A is the least distinct class, not being very different from F or G. =
Latent features = The algorithm used for latent analysis, which is an
analysis of the occurence of words in every document with respect to the
link structure of the encyclopedia ("concepts"), is [[Latent Dirichlet
Allocation]]. This part of the analysis was done by CS PhD student Praful
Mangalath. An example of what can be done with the result of this analysis
is that you provide a word (a search query) such as "hippie". You can then
look at the weight of every article for the word hippie. You can pick the
article with the largest weight, and then look at its link network. You can
pick out the articles that this article links to and/or which link to this
article that are also weighted strongly for the word hippie, while also
contributing maximally to this articles "hippieness". We tried this query in
our system (LDA), Google (site:en.wikipedia.org hippie), and the Simple
English Wikipedia's Lucene search engine. The breakdown of articles occuring
in the top ten search results for this word for those engines is: * LDA
only: [[Acid rock]], [[Aldeburgh Festival]], [[Anne Murray]], [[Carl
Radle]], [[Harry Nilsson]], [[Jack Kerouac]], [[Phil Spector]], [[Plastic
Ono Band]], [[Rock and Roll]], [[Salvador Allende]], [[Smothers brothers]],
[[Stanley Kubrick]]. * Google only: [[Glam Rock]], [[South Park]]. * Simple
only: [[African Americans]], [[Charles Manson]], [[Counterculture]], [[Drug
use]], [[Flower Power]], [[Nuclear weapons]], [[Phish]], [[Sexual
liberation]], [[Summer of Love]] * LDA & Google & Simple: [[Hippie]],
[[Human Be-in]], [[Students for a democratic society]], [[Woodstock
festival]] * LDA & Google: [[Psychedelic Pop]] * Google & Simple: [[Lysergic
acid diethylamide]], [[Summer of Love]] ( See the paper for the articles
produced for the keywords philosophy and economics ) = Discussion /
Conclusion = * The results of the latent analysis are totally up to your
perception. But what is interesting is that the LDA features predict the WET
ratings of quality just as well as the surface level features. Both feature
sets (surface and latent) both pull out all almost of the information that
the rating system bears. * The rating system devised by the WET is not
distinctive. You can best tell the difference between, grouped together,
Featured, A and Good articles vs B articles. Featured, A and Good articles
are also quite distinctive (Figure 1). Note that in this study we didn't
look at Start's and Stubs, but in earlier paper we did. :* This is
interesting when compared to this recent entry on the YouTube blog. "Five
Stars Dominate Ratings"
http://youtube-global.blogspot.com/2009/09/five-stars-dominate-ratings.html…
I think a sane, well researched (with actual subjects) rating system
is
well within the purview of the Usability Initiative. Helping people find and
create good content is what Wikipedia is all about. Having a solid rating
system allows you to reorganized the user interface, the Wikipedia
namespace, and the main namespace around good content and bad content as
needed. If you don't have a solid, information bearing rating system you
don't know what good content really is (really bad content is easy to spot).
:* My Wikimania talk was all about gathering data from people about articles
and using that to train machines to automatically pick out good content. You
ask people questions along dimensions that make sense to people, and give
the machine access to other surface features (such as a statistical measure
of readability, or length) and latent features (such as can be derived from
document word occurence and encyclopedia link structure). I referenced page
262 of Zen and the Art of Motorcycle Maintenance to give an example of the
kind of qualitative features I would ask people. It really depends on what
features end up bearing information, to be tested in "the lab". Each word is
an example dimension of quality: We have "*unity, vividness, authority,
economy, sensitivity, clarity, emphasis, flow, suspense, brilliance,
precision, proportion, depth and so on.*" You then use surface and latent
features to predict these values for all articles. You can also say, when a
person rates this article as high on the x scale, they also mean that it has
has this much of these surface and these latent features.
= References =
- DeHoust, C., Mangalath, P., Mingus., B. (2008). *Improving search in
Wikipedia through quality and concept discovery*. Technical Report.
PDF<http://grey.colorado.edu/mediawiki/sites/mingus/images/6/68/DeHoustMangalat…>
- Rassbach, L., Mingus., B, Blackford, T. (2007). *Exploring the
feasibility of automatically rating online article quality*. Technical
Report. PDF<http://grey.colorado.edu/mediawiki/sites/mingus/images/d/d3/RassbachPincock…>
Hoi,
I have asked and received permission to forward to you all this most
excellent bit of news.
The linguist list, is a most excellent resource for people interested in the
field of linguistics. As I mentioned some time ago they have had a funding
drive and in that funding drive they asked for a certain amount of money in
a given amount of days and they would then have a project on Wikipedia to
learn what needs doing to get better coverage for the field of linguistics.
What you will read in this mail that the total community of linguists are
asked to cooperate. I am really thrilled as it will also get us more
linguists interested in what we do. My hope is that a fraction will be
interested in the languages that they care for and help it become more
relevant. As a member of the "language prevention committee", I love to get
more knowledgeable people involved in our smaller projects. If it means that
we get more requests for more projects we will really feel embarrassed with
all the new projects we will have to approve because of the quality of the
Incubator content and the quality of the linguistic arguments why we should
approve yet another language :)
NB Is this not a really clever way of raising money; give us this much in
this time frame and we will then do this as a bonus...
Thanks,
GerardM
---------- Forwarded message ----------
From: LINGUIST Network <linguist(a)linguistlist.org>
Date: Jun 18, 2007 6:53 PM
Subject: 18.1831, All: Call for Participation: Wikipedia Volunteers
To: LINGUIST(a)listserv.linguistlist.org
LINGUIST List: Vol-18-1831. Mon Jun 18 2007. ISSN: 1068 - 4875.
Subject: 18.1831, All: Call for Participation: Wikipedia Volunteers
Moderators: Anthony Aristar, Eastern Michigan U <aristar(a)linguistlist.org>
Helen Aristar-Dry, Eastern Michigan U <hdry(a)linguistlist.org>
Reviews: Laura Welcher, Rosetta Project
<reviews(a)linguistlist.org>
Homepage: http://linguistlist.org/
The LINGUIST List is funded by Eastern Michigan University,
and donations from subscribers and publishers.
Editor for this issue: Ann Sawyer <sawyer(a)linguistlist.org>
================================================================
To post to LINGUIST, use our convenient web form at
http://linguistlist.org/LL/posttolinguist.html
===========================Directory==============================
1)
Date: 18-Jun-2007
From: Hannah Morales < hannah(a)linguistlist.org >
Subject: Wikipedia Volunteers
-------------------------Message 1 ----------------------------------
Date: Mon, 18 Jun 2007 12:49:35
From: Hannah Morales < hannah(a)linguistlist.org >
Subject: Wikipedia Volunteers
Dear subscribers,
As you may recall, one of our Fund Drive 2007 campaigns was called the
"Wikipedia Update Vote." We asked our viewers to consider earmarking their
donations to organize an update project on linguistics entries in the
English-language Wikipedia. You can find more background information on this
at:
http://linguistlist.org/donation/fund-drive2007/wikipedia/index.cfm.
The speed with which we met our goal, thanks to the interest and generosity
of
our readers, was a sure sign that the linguistics community was enthusiastic
about the idea. Now that summer is upon us, and some of you may have a bit
more
leisure time, we are hoping that you will be able to help us get started on
the
Wikipedia project. The LINGUIST List's role in this project is a purely
organizational one. We will:
*Help, with your input, to identify major gaps in the Wikipedia materials or
pages that need improvement;
*Compile a list of linguistics pages that Wikipedia editors have identified
as
"in need of attention from an expert on the subject" or " does not cite any
references or sources," etc;
*Send out periodical calls for volunteer contributors on specific topics or
articles;
*Provide simple instructions on how to upload your entries into Wikipedia;
*Keep track of our project Wikipedians;
*Keep track of revisions and new entries;
*Work with Wikimedia Foundation to publicize the linguistics community's
efforts.
We hope you are as enthusiastic about this effort as we are. Just to help us
all
get started looking at Wikipedia more critically, and to easily identify an
area
needing improvement, we suggest that you take a look at the List of
Linguists
page at:
http://en.wikipedia.org/wiki/List_of_linguists. M
Many people are not listed there; others need to have more facts and
information
added. If you would like to participate in this exciting update effort,
please
respond by sending an email to LINGUIST Editor Hannah Morales at
hannah(a)linguistlist.org, suggesting what your role might be or which
linguistics
entries you feel should be updated or added. Some linguists who saw our
campaign
on the Internet have already written us with specific suggestions, which we
will
share with you soon.
This update project will take major time and effort on all our parts. The
end
result will be a much richer internet resource of information on the breadth
and
depth of the field of linguistics. Our efforts should also stimulate
prospective
students to consider studying linguistics and to educate a wider public on
what
we do. Please consider participating.
Sincerely,
Hannah Morales
Editor, Wikipedia Update Project
Linguistic Field(s): Not Applicable
-----------------------------------------------------------
LINGUIST List: Vol-18-1831
We know NSA wants Wikipedia data, as Wikipedia is listed in one of the
NSA slides:
https://commons.wikimedia.org/wiki/File:KS8-001.jpg
That slide is about HTTP, and the tech staff are moving the
user/reader base to HTTPS.
As we learn more about the NSA programs, we need to consider vectors
other than HTTP for the NSA to obtain the data they want. And the
userbase needs to be aware of the current risks.
One question from the "Dells are backdored"[sic] thread that is worth
separate consideration is:
Are the Wikimedia transit links encrypted, especially for database replication?
MySQL has replication over SSL, so I assume the answer is Yes.
If not, is this necessary or useful, and feasible ?
However we also need to consider that SSL and other encryption may be
useless against NSA/etc, which means replicating non-public data
should be avoided wherever possible, as it becomes a single point of
failure.
Given how public our system is, we don't have a lot of non-public
data, so we might be able to design the architecture so that
information isnt replicated, and also ensure it isnt accessed over
insecure links. I think the only parts of the dataset that are
private & valuable are
* passwords/login cookies,
* checkuser info - IPs and useragents,
* WMF analytics, which includes readers iirc, and
* hidden/deleted edits
* private wikis and mailing lists
Have I missed any?
Are passwords and/or checkuser info replicated?
Is there a data policy on WMF analytics data which prevents it flowing
over insecure links, and limits what is collected and ensures
destruction of the data within reasonable timeframes? i.e. how about
not using cookies to track analytics of readers who are on HTTP
instead of HTTPS?
The private wikis can be restricted to https, depending on the value
of the data on those wikis in the wrong hands. The private mailing
lists will be harder to secure, and at least the English Wikipedia
arbcom list contain a lot of valuable data about contributors.
Regarding hidden/deleted edits, the replication isnt the only source
of this data. All edits are also exposed via Recent Changes
(https/api/etc) as they occur, and the value of these edits is
determined by the fact they are hidden afterwards (e.g. don't appear
in dumps). Is there any way to control who is effectively capturing
all edits via Recent Changes?
--
John Vandenberg
Hi folks,
to increase accountability and create more opportunities for course
corrections and resourcing adjustments as necessary, Sue's asked me
and Howie Fung to set up a quarterly project evaluation process,
starting with our highest priority initiatives. These are, according
to Sue's narrowing focus recommendations which were approved by the
Board [1]:
- Visual Editor
- Mobile (mobile contributions + Wikipedia Zero)
- Editor Engagement (also known as the E2 and E3 teams)
- Funds Dissemination Committe and expanded grant-making capacity
I'm proposing the following initial schedule:
January:
- Editor Engagement Experiments
February:
- Visual Editor
- Mobile (Contribs + Zero)
March:
- Editor Engagement Features (Echo, Flow projects)
- Funds Dissemination Committee
We’ll try doing this on the same day or adjacent to the monthly
metrics meetings [2], since the team(s) will give a presentation on
their recent progress, which will help set some context that would
otherwise need to be covered in the quarterly review itself. This will
also create open opportunities for feedback and questions.
My goal is to do this in a manner where even though the quarterly
review meetings themselves are internal, the outcomes are captured as
meeting minutes and shared publicly, which is why I'm starting this
discussion on a public list as well. I've created a wiki page here
which we can use to discuss the concept further:
https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…
The internal review will, at minimum, include:
Sue Gardner
myself
Howie Fung
Team members and relevant director(s)
Designated minute-taker
So for example, for Visual Editor, the review team would be the Visual
Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
I imagine the structure of the review roughly as follows, with a
duration of about 2 1/2 hours divided into 25-30 minute blocks:
- Brief team intro and recap of team's activities through the quarter,
compared with goals
- Drill into goals and targets: Did we achieve what we said we would?
- Review of challenges, blockers and successes
- Discussion of proposed changes (e.g. resourcing, targets) and other
action items
- Buffer time, debriefing
Once again, the primary purpose of these reviews is to create improved
structures for internal accountability, escalation points in cases
where serious changes are necessary, and transparency to the world.
In addition to these priority initiatives, my recommendation would be
to conduct quarterly reviews for any activity that requires more than
a set amount of resources (people/dollars). These additional reviews
may however be conducted in a more lightweight manner and internally
to the departments. We’re slowly getting into that habit in
engineering.
As we pilot this process, the format of the high priority reviews can
help inform and support reviews across the organization.
Feedback and questions are appreciated.
All best,
Erik
[1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
[2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
I can think of a few reasons why we should accept bitcoin:
* It's consistent with our leadership in internet technology
* Our peers like EFF, and Internet archive accept it
* It's secured using the same kinds of encryption we rely on to maintain
user privacy
* It permits donations from countries that do not have Visa/Mastercard
services
* It has a fanatically loyal and growing following that is dying to give us
money in that currency
Most imporantly, current technology would permit us to accept bitcoin
without ever *holding* bitcoin.
Companies like BitPay ( https://bitpay.com/) and CoinBase (
https://coinbase.com/) are little different than accepting Visa,
Mastercard, or Paypal. It's now possible for funds received as bitcoins to
be *immediately* converted to USD.
I don't think we should 'make a statement' by accepting bitcoin, I think
the currency is simply at the stage where it would be to our benefit to do
so.
Jake (Ocaasi)
Hi folks,
While watching the current changes to Wikimedia France microgrants program
implemented, I was curious to know which Wikimedia entities had similar
funding programs for individuals - how they worked, how we could learn form
each other.
Since apparently there was no Meta page for that(tm) (yet!) I went ahead and
drafted <https://meta.wikimedia.org/wiki/User:Jean-Frédéric/Funding_programs
>
I dug my information out of my email archives and FDC proposal forms, so I
could totally have missed some programs - please add the ones you know
about!
Of course, it would be more useful to have more detailed information on
every program.
Together with Caroline & Pierre-Selim we threw some ideas on what we
thought was interesting to know about the programs, but that's still very
alpha - please add more ideas!
Looking forward to your thoughts about this!
Cheers,
--
Jean-Frédéric
Wikimédia France
Have come across a collection of basic college textbooks that appear to be
more or less based on text from Wikipedia. There are 21 of them. The
company claims that they are being used by more than 2 million students.
They are under a CC BY SA license and if you follow the links seen here
http://books.google.ca/books?id=7avpAAAAQBAJ&pg=PA2058 they do eventually
attribute Wikipedia.
They are being offered for free on amazon.comhttp://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Daps&field-keywo…
and
are being sold for $19.99 on their website. https://www.boundless.com/
So the question is should we have a response? I think this could generate
position press for our movement. Attribution could be better (I would
consider theirs to be borderline). Additionally should we be adding this
textbooks to Wikiversity or Wikibooks to make sure they stay free available?
--
James Heilman
MD, CCFP-EM, Wikipedian
The Wikipedia Open Textbook of Medicine
www.opentextbookofmedicine.com
Dear Chapters,
this is a mail focused on chapters within the European Union but of course
support and participation of any chapter is welcome!
== Preamble ==
Some might have heard about the State Parliament Projects done in Germany
and Austria since 2009:
A bunch of Wikipedians and photographers meet politicians in the
parliament, shoot professional photos, discuss their Wikipedia articles
etc. This way hundreds of free licensed, high quality images have been
made, Wikipedia articles have been improved. In the latest project at
Schwerin (Mecklenburg-Vorpommern) we added videos, politicians give a short
introduction about themselves, their position and political focus in German
and in their mother tongue if different from German.
About 20 photographers were able to participate and processes how to work
with the parliament's administration, how to interact with the politicians,
how to efficiently take a lot of photos in a short time and with good
quality have been established.
== Next Level: European Parliament ==
Now we would like to take this to next level: After contacting the European
Parliament I was able to get their approval, the support by the parties and
a date!
Unfortunately the date is already in February, 3rd to 7th, as we have to
use the short time gap between budget deliberations and elections. MEPs
only travel to the EP when deliberations are ongoing but then they are also
busy with meetings, as soon as the election preperation starts there won't
be any time for our project within the next 6 months.
Anyway I am sure we can do that - the elections are also a great
opportunity to raise awareness on our material we have in Wikipedia and on
Commons. It is also an excellent opportunity to bring together volunteers
in doing our core work together, maybe we can transfer the idea of
Parliament Projects to other countries. Volunteers get the opportunity to
learn from each other - the EP is a very challenging project, having more
than 700 MEPs to be handled within a few days. And Wikipedia may improve
its articles, also by bringing together volunteers from different EU
countries. Many MEPs have their articles only in a few of the European
languages, some not even in their native language!
== Your Chapter Involved ==
We are looking forward to get volunteers from as many countries as possible
involved in this project. In order to be handle it we need approx. 35
people to help. Obviously the german and austrian photographers are already
waiting for it, from past projects they already know what will go on. But
there is much more to it: We want your volunteers!
Imagine a project where we could bring together volunteers from all 24
language communities in the EU - that is what we are trying!
Therefore we ask you for a favour:
* please forward this invitation to your local community - you can point
them to our project page on Wikimedia Commons:
**
https://commons.wikimedia.org/wiki/Commons:Wikipedians_in_European_Parliame…
* does your chapter provide travel support for those volunteers in your
country who want to participate? Please do so. Your chapter pays for the
transportation to / from Strasbourg and the accommodation (around 300 EUR
per person for all 6 nights), we take care of the rest (transportation
hotel - EP, catering etc.)
**
https://commons.wikimedia.org/wiki/Commons:Wikipedians_in_European_Parliame…
* does your chapter have photographic equipment we might need? We could use
DSLRs, flash units, background systems, lenses...
**
https://commons.wikimedia.org/wiki/Commons:Wikipedians_in_European_Parliame…
* we would like to supply the volunteers with t-shirts or hoodies with
Wikipedia logo or similar - for a unified appearance and to make them
visible as volunteers and Wikimedians. Is your chapter (or the WMF?)
interested in providing 90 shirts / hoodies? (We planned 2 pc. per person
as they will be worn almost one week.)
**
https://commons.wikimedia.org/wiki/Commons:Wikipedians_in_European_Parliame…
* everyone who likes this project: state your support on the talk page of
our grant request to the WMF which should cover the general costs of the
project. By this grant request we make sure that each chapter only has to
handle local support and can stay within it's budgeted limits and area of
operation.
**
https://meta.wikimedia.org/wiki/Grants:PEG/Olaf_Kosinsky/Wikipedians_in_Eur…
Thanks for your attention and your support! We are confident that even with
the short time given we will be able to run an awesome project which will
have an impact in so many areas - Wikipedia, Commons, our volunteers,
chapter collaboration, outreach, reader experience...
Regards,
Olaf Kosinsky
FYI :)
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Thu, Dec 12, 2013 at 11:40 PM
Subject: Update on community advocacy & liaison work
To: All Wikimedia Foundation staff & contractors
Hi all,
As many of you know, we recently brought on board a team of community
members to support the development and rollout of mission-critical WMF
projects like VisualEditor and Flow. To-date, this work has been
coordinated by Philippe Beaudette (reporting to James Forrester for
this purpose), with the community liaisons maintaining a dotted-line
reporting relationship to him while being hired by
engineering/product. In addition, the Community Advocacy team has made
available several of its staff members to work and partner on a
day-to-day basis with the liaisons.
What we’ve learned so far includes:
- Community engagement continues to be critical for successful
development and deployment of products with a strong impact on
community interactions. Not all products have such an impact -- e.g.
improvements to the mobile reading experience or mobile apps don’t
affect the experience of content authors directly nearly as much. In
other cases (e.g. VisualEditor) the impact is huge and the
coordination and communication requirements can be very significant.
- We need to start the process as early as possible - community
engagement isn't something that can just be done at the tail end to
support a rollout. Liaison work includes on-wiki participation in
discussions; organizing roundtables, IRC sessions, feedback and
brainstorming pages, etc. The earlier, the better -- this helps
surface likely points of contention, empowering Product Managers to
better understand the high priority needs and wants from the
community, as well as the cost of a change (how difficult will it be
to make the change, and what negative side effects may it have?).
- Product Managers and Community Liaisons need to work closely
together and see each other as being on the same team. While a typical
liaison likely will support multiple projects, just like designers,
liaisons work best when they develop a deep understanding for the
needs of one or two teams and are in active partnership with the
relevant PM. The PM and Community Liaison should be collaborating on a
day-to-day basis.
- There are other classes of community-related work that need to be
appropriately resourced, but are less directly relevant to product
development. This includes: emergency and crisis management and
response, support for policy-related RFCs, training for OTRS agents,
organizing of visits of key functionaries and committees, etc.
- Learning the lessons from the existence of a Community Department,
we don't view "Community" as a function that can be owned, controlled
or managed in a single department -- each department needs to be
supported by community expertise in its day-to-day work, partnering
closely with other team members.
Consistent with that, after careful discussion, we have decided to
create a new leadership function, Director of Community Engagement
(Product), reporting to me (as VP Product) and partnering closely with
Howie and individual Product Managers. The Director of Community
Engagement (Product) will be responsible for managing community
liaisons (staff or contractors) who directly support product
development.
Once this Director is hired and on-boarded, the Community Advocacy
team currently reporting to Philippe will re-focus its energy on some
of the aforementioned non-product matters. The community liaison team
will at that point move to the new Director, and we will staff up as
needed. We will still intersect on projects such as election support
or policy implementation.
I’m not currently considering merging this group with the "Engineering
Community Team" under Sumana Harihareswara’s leadership. That team is
focused on engaging volunteer developers who contribute to MediaWiki,
and while there is some overlap, I consider the goals and workflows to
be pretty distinct. That said, I expect the two teams to work closely
together in practice, with folks like Andre Klapper (Bug Wrangler)
acting at the intersection between the two teams.
I want to thank Geoff, Philippe and the Community Advocacy team for
all their support bootstrapping the liaison team and partnering with
us on key product roll-outs, on very short notice. It’s been
absolutely invaluable. I’m also grateful for the continuation of this
partnership until we fill the new Director-level role, and for help in
the interview and on-boarding process. Finally, thanks for all the
hard work of the community liaisons on a day-to-day basis; no matter
how hot things sometimes can get, we know that we can count on you.
:-)
I expect to post the job by early January, and it will likely take us
until at least March/April to fill the position.
Please let me know if you have any questions. :-)
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Dear all,
The next WMF metrics and activities meeting will take place on Thursday,
January 9, 2014 at 7:00 PM UTC (11 AM PST). Please note that on this
occasion we are holding this meeting on the second Thursday of January, but
we will resume holding the meetings on the first Thursday of each month
thereafter.
The IRC channel is #wikimedia-office on irc.freenode.net and
the meeting will be broadcast as a live YouTube stream.
The current structure of the meeting is:
* Review of key metrics including the monthly report card, but also
specialized reports and analytic
* Review of financials
* Welcoming recent hires
* Brief presentations on recent projects, with a focus on highest priority
initiatives
* Update and Q&A with the Executive Director, if available
Please review
https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings for further
information about how to participate.
We’ll post the video recording publicly after the meeting.
Thank you,
Praveena
--
Praveena Maharaj
Executive Assistant to the VP of Engineering and Product Development
+1 (415) 839 6885 ext. 6689
www.wikimedia.org