Re: [Wikimedia-l] All the lakes in Sweden

2013-05-19 Thread Emilio J . Rodríguez-Posada
Thanks. I have discovered some estimations of lakes for more countries, but
no datasets.

Belarus: 11,000+
Canada: 31,752+ larger than 3 km² (2-3 million in total)
Estonia: 1,000+
Finland: 187,888 lakes 500 m² or larger (56,000 over 10,000 m²)
Latvia: 3,000+
Lithuania: 3,000+
Norway: 450,000+

2013/5/17 Anders Wennersten

 Sorry not, and what we have learned is how hard is to to define what a
 lake is

 In Swden some mention there are 200 000 lakes, and that the Hydrology
 authority has data of over 150 000  but where less then 75 000 has a name
 and many with just rudimentary data. The lakes with environment impact data
 are 7 233 and in this project data with 100 dataitems per lake are
 collected from three authorities,  and articles are generated into sv:wp
 for 57 648 (not 30 000) lakes. Only around a few percent of these are
 without name and the most common name is used by 645 unique lakes... (just
 to take care of the forkpages is a science in its own)


 Emilio J. Rodríguez-Posada skrev 2013-05-17 18:06:

 Very cool project. Do you know how many lakes are there in other European
 countries (or website/datasets)?

 It is for this**User:Emijrp/All_human_**knowledge#Lakes

 2013/5/16 Anders Wennersten

  A new major botgenerating effort is now under way on sv:wp. All lakes
 (3, all down to ones of pondsizes with no name) is now produced based
 on lake data from Swedish metereology institute and all lake environment
 data from a newly set up authority demanded by EU, in order to register
 track all data of lakes in all Europe.

 The articles are generated by AWB and with some manual effort to take
 of text in existing articles and a major effort taking care of all with
 same name (Little lake, Black lake etc)


 Also on maps from Google or Bing you can localize all lakes if you do not
 know the name (and for the ones missing name)**para/****q=**

 As you can see the text is substantial around 5000 characters and even
 thing like fisharts in the lakes are generated from databases.

 We are now starting to contemplate to put these type of basedata in
 Wikidata (we are experimenting with this for some adm units), and to
 generate the articles from that as a base instead of from database
 extracted from the authorities and put on personal PCs

 We have excellent relations with involved authorities that are really
 happy with the result, and we are now being approached by other
 who wants to follow and get their data from theirs databases used to
 generate qualified Wp articles (like all runestones, all archaeological
 excavations sites, all artworks placed on official grounds etc)

 Are there any other effort like this going on, especially if any one come
 further in establish links from authorities databased to wikidata?


 Wikimedia-l mailing list 

[Wikimedia-l] [Wikimedia Announcements] Advocacy Advisory Group open for membership

2013-05-19 Thread Stephen LaPorte
Hello all,

Are you interested in policy and legislative issues that could affect the
Wikimedia movement? If so, please join the the Advocacy Advisory Group at

The Advocacy Advisory Group is an open, public email list that focuses on
legislative advocacy, affiliations, and other related issues. The group
discusses these topics, advises the Wikimedia Foundation on advocacy and
affiliation actions, and shares updates on similar activities by chapters
and other organizations. Additional background is available in the
Foundation's Policy and Political Association Guideline:

Many thanks,

Stephen LaPorte
Legal Counsel
Wikimedia Foundation

*For legal reasons, I may only serve as an attorney for the Wikimedia
Foundation. This means I may not give legal advice to or serve as a lawyer
for community members, volunteers, or staff members in their personal
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
WikimediaAnnounce-l mailing list
Wikimedia-l mailing list

[Wikimedia-l] [Wikimedia Announcements] Hiring Community Liaisons (Contract)

2013-05-19 Thread Howie Fung

Hey all,

For the last 18 months, the Engineering  Product Development department
has been experimenting with the role of “Community Liaison, Product
Development” - a staff member embedded in the Product team and tasked with
factoring community concerns into our software development process, keeping
editors informed about what we’re doing, and maintaining a dialogue between
those who write code and those who write articles.

While there is always room for improvement, I think this role has shown a
lot of promise.  We have a number of large projects coming down the
pipeline (e.g., visual editor, discussion systems) and we need more help
reaching out to our contributor communities, especially our non-English
speaking projects, as our outreach there has traditionally been challenged.
 We’d like to recruit a small number of English-speaking or multilingual
editors to do the Community Liaison job with different development teams
and focuses.

In particular we’re looking for people with a strong history of
contributions to our projects who can provide sound and reasoned judgment
and are trusted to do so by their community. Speaking other languages in
addition to English is a major plus, as one of the objectives here is to
ensure we can properly interact with and support non-English projects.
 I’ve included the full job description below.

Our immediate need is for help with the Visual Editor.  We’d like to hire a
few community liaisons to help inform different Wikipedia language
communities of the upcoming launch, create spaces for feedback and
discussion, synthesize feedback for the Visual Editor team, and other
activities required to support the Visual Editor launch later this year.

If this is a role that would interest you, please e-mail Philippe Beaudette
 And if you know someone else who might fit the role, let them know about
it :-). We’re provisionally interested in hiring 2-3 liaisons, at an hourly
rate commensurate with experience.  This can be a part-time role, but we’ll
need at least 15 hours/week for the length of the engagement (minimum 3
months).  Please do apply if you think it’s a role that suits you, and if
you find places we haven’t notified, spread the word!


Howie Fung
Director of Product Development
Wikimedia Foundation


Community Liaison Job Description

Background Information and Statement of Purpose

The Wikimedia Foundation’s Engineering  Product Development Department is
looking at ways to more effectively incorporate broad community
perspectives in decisions and hold dialogues with our editors about the
scope, pace and features of upcoming changes to Wikimedia projects. As part
of this, it is hiring additional Community Liaisons from our volunteer

Scope of Work

Support and improve our ongoing software development projects, in


   Building up a network of volunteers from both English language and
   non-English language wikis, increasing the number of projects we can
   interact with;

   Engaging the community in the software development process, by acting as
   a conduit for community questions, bugs and and feature requests, talking
   to editors about our work and how they can participate in it effectively,
   and recruiting them for workgroups and studies;

   Being available from time to time to provide expertise and knowledge
   about our projects, including but not limited to training
   externally-sourced staff in the way our projects work, answering their
   questions, and providing expert advice on an ad-hoc basis;

   Ensuring that our community is represented in the decision-making
   process and that our planned software adequately reflects user needs;

   Monitoring Wikimedia projects, with the assistance of a network of
   volunteers, for emerging issues that have an impact on Engineering
   programmes; and

   Other duties as needed.


Effective Community Liaisons will be:


   Experienced users of Wikimedia projects, capable of representing our
   community within the Foundation and vice-versa.

   Strong communicators (both verbally and with the written word), able to
   explain our products to different groups of users with different levels of
   technical understanding.

   Able to focus on the larger picture, understanding which concerns and
   views are widespread and which are marginal or individual.

   Approachable, as both users and product developers must be able to trust
   these people for the relationship to function.

   Self-motivated - they will be given important projects and expected to
   execute with little to no supervision.

   Strongly empathetic - they excel at understanding the perspectives of
   others and bridging the gap between different approaches to the world.

   Willing and able to