Hoi,
It is all over the news. Google will push mobile phone support by changing
its ranking algorithm. A website that does not support mobiles well will
suffer the consequences. Several sources like /. indicate that Wikipedia
has a problem.
I am anxious to learn what we are going to do.
>From my perspective this is not a time of endless deliberations; we have
done that, we have been there. Mobile is where we grow. It seems to me a no
brainer that we will move lock stock and barrel to a more mobile friendly
environment.
Thanks.
GerardM
http://ultimategerardm.blogspot.nl/2015/04/google-thank-you-for-pushing-mob…
Hi all,
the quarterly reviews for the past quarter (January-March 2015) took
place last week. Minutes and slides are now available for the
following meetings:
Community Engagement, Advancement (Fundraising and Fundraising Tech):
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
Mobile Web, Mobile Apps, Wikipedia Zero:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
Parsoid, Services, MediaWiki Core, Tech Ops, Release Engineering,
Multimedia, Labs, Engineering Community:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
Editing (covering VisualEditor), Collaboration (covering Flow),
Language Engineering:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
As mentioned in February [1], the quarterly review process has been
extended to basically all groups in the Foundation since Lila took the
helm last year, and it was further refined this quarter, reducing the
number of meetings to six overall, each combining several areas.
Minutes and slides from the remaining two meetings should come out
soon, too. (And naturally, all the engineering team names above refer
to the structure before the reorganization that has just been
announced.)
[1] https://lists.wikimedia.org/pipermail/wikimedia-l/2015-February/076835.html
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
>
> 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
>
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
Hey all,
This email to remind you to register if you want to attend the European
Hackathon.
We already have many people registered and we'll soon be full.
Registration ends on the 8th of March.
If you want to join this great week-end, you can register here:
https://dons.wikimedia.fr/civicrm/event/register?reset=1&id=8
You can't apply for a Scholarship anymore!
A page is dedicated to give you more information:
http://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015
The Phabricator listing considered tasks is :
https://phabricator.wikimedia.org/tag/wikimedia-hackathon-2015/
In any case, if you have some more questions, I'll be glad to help you! :)
Best,
*Alexandre Cella*
ASSISTANT LEVÉE DE FOND ET MÉCÉNAT
FUNDRAISING AND SPONSORSHIP ASSISTANT
*WIKIMEDIA FRANCE*
+33 6 18 16 16 19
www.wikimedia.fr
40 rue de Cléry, 75002 Paris
*Vos dons réguliers aident à faire fonctionner Wikipédia ! Soutenez
Wikimédia France aujourd'hui* : https://dons.wikimedia.fr
On behalf of the Scholarship Committeee and WMF, congratulations to the 104 people who were awarded
a scholarship to attend this year's Wikimania being held in Mexico City July 15-19, 2015. WMDE is sponsoring 13
of these. Other chapters are providing additional scholarships as well, and will announce later on.
https://meta.wikimedia.org/wiki/Grants:TPS/Wikimania_scholars#2015_WMF_Scho…
The 2015 program involved a major re-design of the application and selection process. Preliminary outcomes have already been aggregated, including a preliminary list of topics for investigation next year. Highlights include:
• ~28% identified as Female
• ~73% indicated they were from the Global South
• ~26% received a scholarship to attend Wikimania 2014
• Of these repeat applicants, most submitted good/great 2014 post-conference reports
• The average Phase 2 score for recipients was 8.9, with 70% of recipients scoring a 9 or above
See:
https://meta.wikimedia.org/wiki/Grants:TPS/Wikimania_scholars/2015_Outcomes
Updated information about registration, accommodations, and the program for Wikimania '15 will be available on or before
May 1, 2015.
Ellie Young
WMF Conference Coordinator
Cross-list posting, as it's relevant to Wiktionary and Wikimedia as a whole.
First of all, please go to Meta page "Names of Wikimedia languages"
[1] and do the best to proofread or translate items. That's
strategically important set of lists for the movement. We have to know
the names of Wikimedia languages in Wikimedia languages.
This is the first mobilization for this kind of simple translations:
few hundred terms, of which this list is the most complex, as it
requires additional column "in <this> language".
The next one will be about lexicographical and grammatical terms and
abbreviations. That one is of strategic importance for Wiktionary, as
it allows anyone to generate sane dictionary entries.
After those two lists we'll be able to start working on the
Ornithological dictionary, with something less than 400 species.
And now about the number of tanks...
Let's say that there are 250 Wikimedia languages and that we have
three matrix sets: names of languages, 100 lexicographical and
grammatical abbreviations and terms and 400 species from
ornithological dictionary. And that we have those lists translated in
all (250) Wikimedia languages. The numbers are...
* The names of 250 languages *times* in 250 languages (=62,500 entries
per project) *times* on 250 projects (=15,625,000 entries on all
projects).
* 100 lexicographical and grammatical terms and abbreviations *times*
250 languages (=25,000 entries per project) *times* on 250 projects
(=6,250,000 entries on all projects).
* 400 bird species * 250 languages (=100,000 entries per project)
*times* on 250 projects (=25,000,000 entries on all projects).
OK. That calculation is too optimistic. I would be happy if we get
translations in 50 languages. The numbers would be then 125,000
entries for languages, 250,000 entries for lexicographical and
grammatical terms and abbreviations and 1,000,000 for birds.
Besides obvious fact that traditional lexicography isn't that
optimized (note that it's about traditional lexicography, not about
Wiktionary itself, thus not that fixable) and that we need a bit
better method (OmegaWiki, Wikidata, we are developing the proof of
concept, as well), there are two other consequences:
1) If we have a set of 400 words and we translate them in 50
languages, we are getting one million of entries. We should be doing
that on monthly basis. It's not hard at all!
2) In a bit more complex form, which requires more work per matrix set
and smaller output ("just" multiplication of the first and third
number), this could be used for Wikipedia articles, as well. (You need
much more information in encyclopedic article for German language than
in a dictionary entry. But it's quite possible to do it. And it's
especially important for languages with small number of speakers.)
Please go to [1] and help this translation! Having the names of
Wikimedia languages in Wikimedia languages *is* important no matter if
it's about Wiktionary or generating the content. We should know the
names of our languages in our languages.
[1] https://meta.wikimedia.org/wiki/Names_of_Wikimedia_languages