Re: [Wikimedia-l] The ProWikimedia award and thanking the volunteers
Great iniciative. I love it and I'll try to do something similar in Spain. Thanks for sharing this. Santi El 2015-06-11 22:43, Natalia Szafran-Kozakowska escribió: Dear all As you all know in the Wikmedia movement nothing really inspiring and creative can be done without the volunteers. Their ideas, time and energy are priceless. That is why Wikimedia Poland has created an award to say thank you to great people that inspire and coordinate our projects (expeditions, workshops, editathons, photo contests etc.) and for the volunteer of the year. We invited four people from the outside of the Wikimedia movement - people representing cultural institutions NGO's and the media - to form a jury with a task to choose the projects and the volunteer that should be rewarded. The jury also gave us precious information about how people who are not Wikimedians see our projects and which they perceive as the most interesting and inspiring. The ProWikimedia 2015 award will be given in 4 categories: 1. Free content ambassador - in recognition of a project which had major impact on promoting openness, knowledge of free licenses, and free culture outside Wikimedia communities or which resulted in resources that were of great use to projects, institutions and publications outside of the WIkimedia movement 2. Efficient content acquisition - in recognition of a project which exhibited a high ratio of acquired content quality and quantity in the context of financial outlays 3. Innovation / pioneering character in acquiring free content - in recognition of a project which showed creativity, innovative approach and original viewpoint in acquiring free contents for the WIkimedia projects 4. The volunteer of the year The award ceremony will take place this Saturday in the library of the European Solidarity Center - an institution with a mission of maintaining the heritage and message of the Solidarity movement and sharing the achievements of the peaceful struggle for freedom, justice, democracy and human rights. And it is a great place to recognize the great effort of Wikimedia volunteers who change the world by sharing knowledge. The ProWikimedia project has already (thanks to the outside jury) thought us a lot about our actions and initiatives and given us precious (and sometimes surprising) insight. But it's main purpose is to keep our volunteers inspired, encourage them to start new initiatives and show them how great job they are doing. I am really excited about this award as I truly believe that showing gratitude to our volunteers is something really important. And we need to find new ways to do it. Natalia Szafran-Kozakowska [[user:Magalia]] ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/, Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be complicated. For us, this process began years ago and involved teams from across the Wikimedia Foundation. Our engineering team has been driving this transition, working hard to improve our sites’ HTTPS performance, prepare our infrastructure to handle the transition, and ultimately manage the implementation. Our first steps involved improving our infrastructure and code base so we could support HTTPS. We also significantly expanded and updated our server hardware. Since we don’t employ third party content delivery systems, we had to manage this process for our entire infrastructure stack in-house. HTTPS may also have performance implications for users, particularly our many users accessing Wikimedia sites from countries or networks with poor technical infrastructure. We’ve been carefully calibrating our HTTPS configuration to minimize negative impacts related to latency, page load times, and user experience. This was an iterative process that relied on industry standards, a large amount of testing, and our own experience running the Wikimedia sites. Throughout this process, we have carefully considered how HTTPS affects all of our users. People around the world access Wikimedia sites from a diversity of devices, with varying levels of connectivity and freedom of information. Although we have
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
This is really fantastic. Thanks, Habib Le 12 juin 2015 21:22:26 CET, Juliet Barbara jbarb...@wikimedia.org a écrit : The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/, Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be complicated. For us, this process began years ago and involved teams from across the Wikimedia Foundation. Our engineering team has been driving this transition, working hard to improve our sites’ HTTPS performance, prepare our infrastructure to handle the transition, and ultimately manage the implementation. Our first steps involved improving our infrastructure and code base so we could support HTTPS. We also significantly expanded and updated our server hardware. Since we don’t employ third party content delivery systems, we had to manage this process for our entire infrastructure stack in-house. HTTPS may also have performance implications for users, particularly our many users accessing Wikimedia sites from countries or networks with poor technical infrastructure. We’ve been carefully calibrating our HTTPS configuration to minimize negative impacts related to latency, page load times, and user experience. This was an iterative process that relied on industry standards, a large amount of testing, and our own experience running the Wikimedia sites. Throughout this process, we have carefully considered how HTTPS affects all of our users. People around the world access
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
Comets, I can answer that. From the dev who switched HTTPS on during prime usage times, complained about working 60+ hours this week, then left for the day. I get the impression that the WMF doesn't give a shit about those users who choose to opt-out of HTTPS for one reason or another. It's basically your now screwed, it works for us so figure it out without us. On Friday, June 12, 2015, Comet styles cometsty...@gmail.com wrote: Congrats, you just made internet shitty for all 3rd world countries and did you people even bother to find out how it will affect users in China or Iran where HTTPS is BANNED?. On 6/13/15, Tito Dutta trulyt...@gmail.com javascript:; wrote: Great job. :) Thanks for informing [PS. to members, you may read the WP:VPT https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default discussion too] On 13 June 2015 at 03:05, Habib M'henni habib.mhe...@gmail.com javascript:; wrote: This is really fantastic. Thanks, Habib Le 12 juin 2015 21:22:26 CET, Juliet Barbara jbarb...@wikimedia.org javascript:; a écrit : The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/ , Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
This reminds me of the VE rollout debacle On Friday, June 12, 2015, John phoenixoverr...@gmail.com wrote: Comets, I can answer that. From the dev who switched HTTPS on during prime usage times, complained about working 60+ hours this week, then left for the day. I get the impression that the WMF doesn't give a shit about those users who choose to opt-out of HTTPS for one reason or another. It's basically your now screwed, it works for us so figure it out without us. On Friday, June 12, 2015, Comet styles cometsty...@gmail.com javascript:_e(%7B%7D,'cvml','cometsty...@gmail.com'); wrote: Congrats, you just made internet shitty for all 3rd world countries and did you people even bother to find out how it will affect users in China or Iran where HTTPS is BANNED?. On 6/13/15, Tito Dutta trulyt...@gmail.com wrote: Great job. :) Thanks for informing [PS. to members, you may read the WP:VPT https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default discussion too] On 13 June 2015 at 03:05, Habib M'henni habib.mhe...@gmail.com wrote: This is really fantastic. Thanks, Habib Le 12 juin 2015 21:22:26 CET, Juliet Barbara jbarb...@wikimedia.org a écrit : The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/ , Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment.
Re: [Wikimedia-l] [Languages] Wikipedia article per speaker
Illario, Latin doesn't have L1 speakers. And data about languages are such a mess, that I would stick with Ethnologue's data for L1 speakers, although they are not reliable. Ethnologue counts there are 100,000 speakers of language X in country A and 34 in country B, thus there are 100,034 speakers in total (although likely error margin for the first number is 150 times larger than the second number), as well as it has numerous other flaws, like fringe macrolanguage category is. However, besides counting the same way, English Wikipedia has much worse failures when we leave ~50 major languages safety, if not based on Ethnologue's data. (It's mostly about wishful thinking of ethnic nationalists and chronic lack of manpower to fix that bullshit promptly.) Nemo, yes I was thinking about various data instead of article count and GDP/PPP per capita, so here are the thoughts, including those two parameters: * Article count per speaker gives one one nice pseudo-hyperbolic curve. Basically, you can see a hyperbolic curve by drawing the line over the highest points: Hawaiian-Upper Sorbian-Basque-Swedish-Dutch-English. By normalizing the numbers, we could get targets per language. * However, edit count seems like better idea. I think, but it has to be proved, that such numbers won't have to be adjusted for the number of speakers themselves. * We could count various numbers related to users. For example, it seems that as smaller ratio between the number of active and very active users is, as healthier community is. Also, number of editors per million of speaker per GDP or HDI could be useful parameter. * I was thinking yesterday about HDI. But then I've realized that it would be good to create all of possibly relevant charts and see what they bring as information. I am interested in comparison of Wikipedia stats with Gini coefficient, for example. And I will do that. After I finish with the most frustrating part of the job: draw the line between Wikipedia editions, Ethnologue data and actual languages. Good news is that I am on ~150th of ~280 Wikipedia editions and it's likely I will finish it during the next week. (After almost eight years of dealing with this matter, whenever someone says that there are two hundred eighty something Wikipedia languages or that there are 7000 languages in the world, I reach for my revolver.) On Jun 12, 2015 20:51, Federico Leva (Nemo) nemow...@gmail.com wrote: Milos Rancic, 08/06/2015 00:23: And I suppose somebody with statistical knowledge would be able to give us the number which would have meaning ability to create Wikipedia article. Why not use the human development index (HDI) as factor? Also, instead of the number of articles I'd rather use database size or number of words. Nemo ___ Languages mailing list langua...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/languages ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] What's cool?
Interesting! But there are a few problems with this: 1) This gives you the data that is in the item, but what does it give you when there is no data in the item? 2) I am missing a discrete [edit] somewhere indicating where I go to add the data for the fields that are missing from the template I really like the one line aspect - very clean-looking in the edit window! On Fri, Jun 12, 2015 at 8:42 PM, Michael Peel em...@mikepeel.net wrote: Thanks to Wikidata and Module:Wikidata [1], it is now possible [2] to include a basic infobox in an article using a single line, rather than the usual lengthy piece of wikicode (which new users could find off-putting). For a live example, see: https://en.wikipedia.org/wiki/South_Pole_Telescope https://en.wikipedia.org/wiki/South_Pole_Telescope [1] https://en.wikipedia.org/wiki/Module:Wikidata https://en.wikipedia.org/wiki/Module:Wikidata [2] for an example of how to enable this for your favourite infobox, see the source code of https://en.wikipedia.org/wiki/Template:Infobox_telescope https://en.wikipedia.org/wiki/Template:Infobox_telescope Thanks, Mike ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Global North/South
I recently discovered an article on the subject from Norwegian sociocultural anthropologist Thomas Hylland Eriksen that might be of interest here.[1][2] (As a full disclosure about how I came upon it, it was mentioned in the Around the Web Digest of my favorite anthro blog, Savage Minds.[3] :) It explores briefly the history of such terms and how they tend to reduce the diversity of world communities to black and white according to the enculturated values of those in internationally powerful positions—those at the moment being highly nationalistic and neoliberal. The post-Cold War world is not mainly divided into societies that follow different political ideologies such as socialism or liberalism, but by degrees of benefits in a globalized neoliberal capitalist economy. [...] The Global South and the Global North represent an updated perspective on the post-1991 world, which distinguishes not between political systems or degrees of poverty, but between the victims and the benefactors of global capitalism. [2] [...] what is needed are more fine-grained instruments to gauge the quality of life and the economic circumstances of a community, since most of the world's population live mainly in communities and not in states. [2] I would love to see us seek terminology that is more reflective of knowledge accessibility and cultural representation than of global economics but, as Amir mentioned, I find those at WMF to already operate with such mindfulness and distinction. [1] https://en.wikipedia.org/wiki/Thomas_Hylland_Eriksen [2] http://gssc.uni-koeln.de/node/454 [3] http://savageminds.org/2015/05/09/around-the-web-digest-week-of-may-3/ On Thu, Jun 11, 2015 at 5:06 PM, Asaf Bartov abar...@wikimedia.org wrote: I agree with everything Michał said. It's a very flawed distinction, and it is often misleading. We at WMF have certainly been paying much closer attention to contexts at the level of countries and regions than to the binary divide. Conceivably, some time investment could result in a better and more defensible distinction (for example, it would probably not be binary, and it would probably be tied less tightly to socioeconomics, and take into account the actual state of the editing community in a country). It has so far not been deemed enough of a priority to ever be done. A. On Thu, Jun 11, 2015 at 3:19 PM, Michał Buczyński sand...@o2.pl wrote: And they say we, Poles, have a dry sense of humour. Let me guess Milos, you are on purpouse mixing up two definitions of the White Sea (Бело море / Belo More) in Serbian. :P Coming back to the question of Yaroslav: this issue comes up regularily and I find it perfectly valid. Two years ago in Milan we had a quite heated discussion on this topic. The problem is that the global south is a yet another widespread and well-intended but inherently lame euphemism for poor countries also known as the third world, a.k.a. developing countries a.k.a. something different whatever comes handy. Unfortunately, euphemisms bring big problems on their own. One huge problem with this division is its heroic simplicity, mixing up economic differences with social and cultural issues and splitting the world into white and black, no grey. Second thing is its mix of geography with socioeconomic issues which leads to confusions, even in classification by e.g. ITU. Third thing is: it is arbitrary as no firm metric or threshold is given. Contrary to the claim, the Wikimedia list is *not* solely based on ITU list and UN list (what can be actually better, because according to ITU and UN M49 Bosnia and Hercegovina is North, when Hongkong, Macau and South Korea are.. South!). Certainly, everything can be managable when you remember about the questionable definitions and build your strategies upon a more refined thinking. It would be _bad_ if this tag was used as a support more / less flag and financial decisions on particular projects and people were heavily based upon this underexplained and arbitrary list. // Side note: even in case of Wikimania 2015 I am aware of at least one example of a global northerner refused a visa to Mexico, which is allegedly in the Global South. Personally, I would drop this global south / north thinking altogether and in financial decisions move to some more refined analysis, taking into account multiple benchmarks like personal income (which is often distributed far less equal in the developing world). In the global perspective, I would be happy if the Board considered an official change of the strategy to some more detailed perspective, openly communicating which cultural and socioeconomic areas they find particularly interesting and what are their plans to each of them. E.g.: why do we think the Arab world is important and how do we want to build a thriving community sharing our basic values there?) However whatever approach
[Wikimedia-l] Does the European trade secrets law pose a threat to editors?
http://www.euractiv.com/sections/health-consumers/new-law-muzzle-whistleblowers-315357 Wasn't there some time a few years back when the PCI consortium and some ~40 digit hexadecimal number were making Philippe have to do around doing revels or such? Can we vote against that please? ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
Great job. :) Thanks for informing [PS. to members, you may read the WP:VPT https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default discussion too] On 13 June 2015 at 03:05, Habib M'henni habib.mhe...@gmail.com wrote: This is really fantastic. Thanks, Habib Le 12 juin 2015 21:22:26 CET, Juliet Barbara jbarb...@wikimedia.org a écrit : The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/ , Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be complicated. For us, this process began years ago and involved teams from across the Wikimedia Foundation. Our engineering team has been driving this transition, working hard to improve our sites’ HTTPS performance, prepare our infrastructure to handle the transition, and ultimately manage the implementation. Our first steps involved improving our infrastructure and code base so we could support HTTPS. We also significantly expanded and updated our server hardware. Since we don’t employ third party content delivery systems, we had to manage this process for our entire infrastructure stack in-house. HTTPS may also have performance implications for users, particularly our many users accessing Wikimedia sites from countries or networks with poor technical infrastructure. We’ve been carefully calibrating our
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
Congrats, you just made internet shitty for all 3rd world countries and did you people even bother to find out how it will affect users in China or Iran where HTTPS is BANNED?. On 6/13/15, Tito Dutta trulyt...@gmail.com wrote: Great job. :) Thanks for informing [PS. to members, you may read the WP:VPT https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default discussion too] On 13 June 2015 at 03:05, Habib M'henni habib.mhe...@gmail.com wrote: This is really fantastic. Thanks, Habib Le 12 juin 2015 21:22:26 CET, Juliet Barbara jbarb...@wikimedia.org a écrit : The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). This post is available online here: https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ Securing access to Wikimedia sites with HTTPS BY YANA WELINDER https://blog.wikimedia.org/author/ywelinder/, VICTORIA BARANETSKY https://blog.wikimedia.org/author/victoria-baranetsky/ AND BRANDON BLACK https://blog.wikimedia.org/author/brandon-black/ ON JUNE 12TH To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. The HTTPS protocol creates an encrypted connection between your computer and Wikimedia sites to ensure the security and integrity of data you transmit. Encryption makes it more difficult for governments and other third parties to monitor your traffic. It also makes it harder for Internet Service Providers (ISPs) to censor access to specific Wikipedia articles and other information. HTTPS is not new to Wikimedia sites. Since 2011, we have been working on establishing the infrastructure and technical requirements, and understanding the policy and community implications of HTTPS for all Wikimedia traffic, with the ultimate goal of making it available to all users. In fact, for the past four years https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/ , Wikimedia users could access our sites with HTTPS manually, through HTTPS Everywhere https://www.eff.org/https-everywhere, and when directed to our sites from major search engines. Additionally, all logged in users https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/ have been accessing via HTTPS since 2013. Over the last few years, increasing concerns about government surveillance prompted members of the Wikimedia community to push https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ for more broad protection through HTTPS. We agreed, and made this transition a priority for our policy and engineering teams. We believe encryption makes the web stronger for everyone. In a world where mass surveillance has become a serious threat to intellectual freedom, secure connections are essential for protecting users around the world. Without encryption, governments can more easily surveil sensitive information, creating a chilling effect, and deterring participation, or in extreme cases they can isolate or discipline citizens. Accounts may also be hijacked, pages may be censored, other security flaws could expose sensitive user information and communications. Because of these circumstances, we believe that the time for HTTPS for all Wikimedia traffic is now. We encourage others to join us as we move forward with this commitment. The technical challenges of migrating to HTTPS HTTPS migration for one of the world’s most popular websites can be complicated. For us, this process began years ago and involved teams from across the Wikimedia Foundation. Our engineering team has been driving this transition, working hard to improve our sites’ HTTPS performance, prepare our infrastructure to handle the transition, and ultimately manage the implementation. Our first steps involved improving our infrastructure and code base so we could support HTTPS. We also significantly expanded and updated our server hardware. Since we don’t employ third party content delivery systems, we had to manage this process for our entire infrastructure
Re: [Wikimedia-l] What's cool?
1) This gives you the data that is in the item, but what does it give you when there is no data in the item? Ideally, all of the data would be in the wikidata item, and if there's no data then there's nothing to display. ;-) But in practice, you can pass parameter information to the template in the usual way, which will then be shown in the infobox regardless of whether there is information on wikidata about that parameter or not. This infobox template is still in use in other articles in the usual fashion, and it only reverts to wikidata information for empty parameters. 2) I am missing a discrete [edit] somewhere indicating where I go to add the data for the fields that are missing from the template This could probably be handled by an [edit] link in the infobox that points users towards wikidata. However, there's currently no way to show blank fields on wikidata for empty entries that are used in the template, you have to know the right property number or name in order to add it. This is definitely something that needs more technical development, but that doesn't stop it from being cool. ;-) Thanks, Mike ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] What's cool?
Oh I totally agree that it is cool. Thanks for posting this! On Fri, Jun 12, 2015 at 9:40 PM, Michael Peel em...@mikepeel.net wrote: 1) This gives you the data that is in the item, but what does it give you when there is no data in the item? Ideally, all of the data would be in the wikidata item, and if there's no data then there's nothing to display. ;-) But in practice, you can pass parameter information to the template in the usual way, which will then be shown in the infobox regardless of whether there is information on wikidata about that parameter or not. This infobox template is still in use in other articles in the usual fashion, and it only reverts to wikidata information for empty parameters. 2) I am missing a discrete [edit] somewhere indicating where I go to add the data for the fields that are missing from the template This could probably be handled by an [edit] link in the infobox that points users towards wikidata. However, there's currently no way to show blank fields on wikidata for empty entries that are used in the template, you have to know the right property number or name in order to add it. This is definitely something that needs more technical development, but that doesn't stop it from being cool. ;-) Thanks, Mike ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] What's cool?
Thanks to Wikidata and Module:Wikidata [1], it is now possible [2] to include a basic infobox in an article using a single line, rather than the usual lengthy piece of wikicode (which new users could find off-putting). For a live example, see: https://en.wikipedia.org/wiki/South_Pole_Telescope https://en.wikipedia.org/wiki/South_Pole_Telescope [1] https://en.wikipedia.org/wiki/Module:Wikidata https://en.wikipedia.org/wiki/Module:Wikidata [2] for an example of how to enable this for your favourite infobox, see the source code of https://en.wikipedia.org/wiki/Template:Infobox_telescope https://en.wikipedia.org/wiki/Template:Infobox_telescope Thanks, Mike ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] This week on the Wikimedia Blog
Hi folks, Here are some of the stories featured this week on the Wikimedia Blog: • Securing access to Wikimedia sites with HTTPS https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/ * Wikimedia Foundation Board election results are in https://blog.wikimedia.org/2015/06/05/board-election-results/ • How the Wikimedia Foundation Board elections are organized https://blog.wikimedia.org/2015/06/10/how-board-elections-are-organized/ * How to join a Wikipedia meetup near you (VIDEO) https://blog.wikimedia.org/2015/06/05/wikipedia-meetups/ Note: You can also view the meetup video on YouTube: https://www.youtube.com/watch?v=a5uZvTHQuhE • Over 5,000 new articles created with the Content Translation tool https://blog.wikimedia.org/2015/06/09/content-translation-tool/ • Open Badges for editor retention https://blog.wikimedia.org/2015/06/11/open-badges/ • Evaluation helps Wikimedia leaders learn together https://blog.wikimedia.org/2015/06/09/evaluation-helps-leaders-learn-together/ More stories on the Wikimedia Blog: https://blog.wikimedia.org/ Enjoy, Fabrice ___ Fabrice Florin Movement Communications Manager Wikimedia Foundation https://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF) ___ 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: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l ___ WikimediaAnnounce-l mailing list wikimediaannounc...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
On 12 June 2015 at 21:22, Juliet Barbara jbarb...@wikimedia.org wrote: The Wikimedia Foundation is pleased to announce that we have begun the transition of the Wikimedia projects and sites to the secure HTTPS protocol. You may have seen our blog post from this morning; it has also been posted to relevant Village Pumps (Technical). Excellent news! So how are we dealing with the Iran and China issue? - d. ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS
To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS https://en.wikipedia.org/wiki/HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic. With this change, the nearly half a billion people who rely on Wikipedia and its sister projects every month will be able to share in the world’s knowledge more securely. Well this is a great move, and I applaud it (About time :), until such a time as IPSec is fully deployed, isn't that a little misleading as to the actual security afforded by this change? There is quite a lot of evidence that the NSA is slurping up data from unsecured inter data centre links of other people [1], seems unlikely that they are ignoring us. I also think we should have a more balanced position on how much privacy TLS actually provides in the context of Wikipedia, so that users can be properly informed. Sure, TLS is a step in the right direction, probably stops most less well funded adversaries, but its not a panacea. In the case of Wikipedia, the content of every page is not static, but it is totally public, so Wikipedia is probably the ideal target of traffic analysis type attacks against SSL. That sort of thing is almost certainly more expensive than just grepping packets, but surely seems to be within the budget of the NSA to do, even in a bulk manner (Assuming that non-targeted surveillance by a state level adversary is the unspoken threat model we're trying to defend against). -- bawolff [1] https://en.wikipedia.org/wiki/Muscular_%28surveillance_program%29 ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] Wikipedia article per speaker
(adding Analytics, as a relevant group for this discussion.) I think this is next to meaningless, because the differing bot policies and practices on different wikis skew the data into incoherence. The (already existing) metric of active-editors-per-million-speakers is, it seems to me, a far more robust metric. Erik Z.'s stats.wikimedia.org is offering that metric. A. On Sun, Jun 7, 2015 at 3:23 PM, Milos Rancic mill...@gmail.com wrote: When you get data, at some point of time you start thinking about quite fringe comparisons. But that could actually give some useful conclusions, like this time it did [1]. We did the next: * Used the number of primary speakers from Ethnologue. (Erik Zachte is using approximate number of primary + secondary speakers; that could be good for correction of this data.) * Categorized languages according to the logarithmic number of speakers: =10k, =100k, =1M, =10M, =100M. * Took the number of articles of Wikipedia in particular language and created ration (number of articles / number of speakers). * This list is consisted just of languages with Ethnologue status 1 (national), 2 (provincial) or 3 (wider communication). In fact, we have a lot of projects (more than 100) with worse language status; a number of them are actually threatened or even on the edge of extinction. Those are the preliminary results and I will definitely have to pass through all the numbers. I fixed manually some serious errors, like not having English Wikipedia itself inside of data :D Putting the languages into the logarithmic categories proved to be useful, as we are now able to compare the Wikipedias according to their gross capacity (numbers of speakers). I suppose somebody well introduced into statistics could even create the function which could be used to check how good one project stays, no matter of those strict categories. It's obvious that as more speakers one language has, it's harder to the community to follow the ratio. So, the winners per category are: 1) = 1k: Hawaiian, ratio 0.96900 2) = 10k: Mirandese, ratio 0.18073 3) = 100k: Basque, ratio 0.38061 4) = 1M: Swedish, ratio 0.21381 5) = 10M: Dutch, ratio 0.08305 6) = 100M: English, ratio 0.01447 However, keep in mind that we removed languages not inside categories 1, 2 or 3. That affected =10k languages, as, for example, Upper Sorbian stays much better than Mirandese (0.67). (Will fix it while creating the full report. Obviously, in this case logarithmic categories of numbers of speakers are much more important than what's the state of the language.) It's obvious that we could draw the line between 1:1 for 1-10k speakers to 10:1 for =100M speakers. But, again, I would like to get input of somebody more competent. One very important category is missing here and it's about the level of development of the speakers. That could be added: GDP/PPP per capita for spoken country or countries would be useful as measurement. And I suppose somebody with statistical knowledge would be able to give us the number which would have meaning ability to create Wikipedia article. Completed in such way, we'd be able to measure the success of particular Wikimedia groups and organizations. OK. Articles per speaker are not the only way to do so, but we could use other parameters, as well: number of new/active/very active editors etc. And we could put it into time scale. I'll make some other results. And to remind: I'd like to have the formula to count ability to create Wikipedia article and then to produce level of particular community success in creating Wikipedia articles. And, of course, to implement it for editors. [1] https://docs.google.com/spreadsheets/d/1TYyhETevEJ5MhfRheRn-aGc4cs_6k45Gwk_ic14TXY4/edit?usp=sharing ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe -- Asaf Bartov Wikimedia Foundation http://www.wikimediafoundation.org Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us make it a reality! https://donate.wikimedia.org ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] OpenCon conference in Brussels, sign up before 22 June
Hello all, On 14-16 November the OpenCon 2015 conference is organised in Brussels. This conference is about Open Access, Open Education and Open Data, which is practically the same subject as the one of the Wikimedia movement, only from a different perspective. Therefore I think it is good to support this conference and visit it. If you want to attend, sign up before 22 June: http://opencon2015.org/attend Greetings, Romaine ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
Re: [Wikimedia-l] WMF Finance Fellows to develop first-ever movement-wide financial report and metrics
Hoi, For me there is little incentive here. You are doing it for your reasons and that is fine. When primary objectives of chapters and others are omitted it loses its relevance for me. You ask he what to do and for me it is obvious that you are doing something really complicated that takes a whole lot of effort from many many people that produces a result that is really dangerous as it is incomplete in the ways it has been indicated. Dangerous when it is to have consequences. Consider, when admin is painful to the point where people refuse or ignore the results, what is the added value of all that labour? How does it make us more effective in sharing in the sum of all knowledge ? Thanks, GerardM On 11 June 2015 at 23:39, Oluwaseyi Olukoya ooluk...@wikimedia.org wrote: Thank you for your feedback. As a team we are happy to see the necessary conversations and questions being raised and we look forward to working with you to make this better. The report was set out as an experiment with the purpose of consolidating chapters published financial reports to observe what trends may exist. @ GerardM: As you have rightly said the relative value of the report is affected if any principal information is omitted and also how things are done within each chapter’s country needs to be taken into account. If the current outcome of combining 37 financial statements is not optimal - we acknowledge it can be improved - then how can we make it better? If necessary, what variables (e.g. staff/volunteers info) need to be taken in account? … @Ilario: We appreciate that insight. We agree that further steps need to be taken to make the data we gathered more comparable. A first step was allocating all the chapter’s currently used line items to a common revenue and costs category. Now we will need to focus more on refining the first step and, in line with your advice, looking further into: - how can the data we gathered be kept in its original context? - how can the data be used by the chapters in a meaningful and comparable way? During our open discussion presentation at Wikimania, such questions can be explored further. Since this is an experiment towards a consolidated trends report, we can collaboratively observe loopholes/blind spots that may exist and move towards a solution. Thank you. Regards On Thu, Jun 11, 2015 at 3:23 AM, Gerard Meijssen gerard.meijs...@gmail.com wrote: Hoi, Raising revenue is done in one way. We ask people, they give. We tell everybody that the WMF is a charity in the USA.. FINE but it is also a charity in many other countries for instance in the Netherlands. Increasing the amount of money in the Netherlands can be done in many ways. The chapter may help but there are other ways as well. To do this well. you have to be aware about how things are done in a country. Given that it is possible to have gifts to charities fully tax deductible, it is relevant to look after such details.. I know about them and I do not mind to help. Thanks, GerardM On 11 June 2015 at 11:49, Ilario Valdelli valde...@gmail.com wrote: Hi, the idea is interesting, I am a volunteer in same grant committees of WMF and I can only agree to have a more comparable financial sheets (mainly in the use of the currencies). But I have some concerns. a) I hope that this project will produce more comparable financial sheets but without leaving the context were chapters are working. An example is the cost per day of an employee because if there is a standardization of these financial data but out of the context the risk is that the financial statements can generate not realistic data. It means that the total costs of the staff in a country with high salaries cannot be comparable with another having lower salaries without a balanced data. b) I really hope that you will push also the addition of the relevance of the results of the fundraising in each country, because we always think that the cow produces milk, we never think that we have to harvest the cow to produce its milk The financial statements of a chapters out of the context of the WMF fundraising in each country limits a lot the real value of the costs. Regards On Thu, Oct 30, 2014 at 12:15 AM, Michael Guss mg...@wikimedia.org wrote: Hi folks, We are the Finance Fellows, a multicultural team consisting of 4 young professionals. We are happy to introduce a 6-month movement-wide project that focuses on the consistency of how we operate, which is explained further in this announcement. *But here's some information about us*: Arda [User:Melmas_(WMF)] https://meta.wikimedia.org/wiki/User:Melmas_(WMF) is from Turkey. He holds a BA in Economics. Lene [User:Lgillis_(WMF)] https://meta.wikimedia.org/wiki/User:Lgillis_(WMF) is from Belgium. She
