[Wikimedia-l] Watch your vote in board elections!
Hi everybody, today, board elections have begun. Please think twice on who you vote, because past boards did not bring a lot of innovation (if any???) into Wikimedia... and who else should bring innovation than the top governing entity? Wikimedia suffers from declining editorship... on which the overall quality depends. Vote for better Wikipedia quality with a better board! Good luck in the elections! Regards, Jan Kucera (Kozuch) ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Thanks for all the fish!
Dear Milos, No! But understand. Also now understand why you withdrew your Board candidacy. Thank you for writing so honestly. It touched a chord in me (having gone through similar cycles in other worlds). One of my earliest memories of the wikimedia movement is having a smoky chat with you in wikimania Gdansk about everything from the politics of language to the films of Emir Kusturica. You made me feel at home. :) I hope our paths will continue to cross. Best Bishakha On Sat, Jun 8, 2013 at 10:50 AM, Erik Moeller wrote: > Thanks for everything, Milos. It's been a pleasure and I won't be at > all surprised to run into you again, if not in Wikimedia then in other > free culture circles. There are lots of unfinished projects indeed -- > for me, seeing the movement tackle increasingly hard and complex > challenges successfully has been hugely motivating. I hope that if no > sooner, in a few years you'll check in on where things are and find > things so transformatively different to be re-energized to participate > again. :) > > Erik > > ___ > Wikimedia-l mailing list > Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l > ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Thanks for all the fish!
Am 07.06.2013 19:31, schrieb Milos Rancic: > On Fri, Jun 7, 2013 at 6:32 PM, Milos Rancic wrote: >> == Unfinished projects == > > Oh, and I knew that there were three unfinished projects, but I forgot > the last one. > > Wikimedia movement isn't staying well with formal diplomacy. No of the > Wikimedia organizations participated even in the global events close > to Wikimedia's interests, like, for example, Internet Governance Forum > is. I can at least say that Wikimedia CH and Wikimedia Österreich (Austria) are member of ICANN At-Large and as such will be present at the EuroDIG in Lisbon next week (where we will also have the EURALO General Assembly). /Manuel -- Wikimedia CH - Verein zur Förderung Freien Wissens Lausanne, +41 (21) 34066-22 - www.wikimedia.ch ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Thanks for all the fish!
Hi Milos, thank you is the least we can say at this point. We can be happy to be such a big movement, with so many people like you who further our vision and goals. Some fluctuation is natural and it is totally natural that after serving some time in our community to move on to new and other priorities in live. You have already done much more than most of those benefiting from your work and in fact ten years are a great part of your life-time. Thank you, all the best for your future and I am convinced that one always meets twice in live... Even if you leave you know where and who we are. You are always welcome back, be it only a request for help or collaboration in any other project of your future. /Manuel -- Wikimedia CH - Verein zur Förderung Freien Wissens Lausanne, +41 (21) 34066-22 - www.wikimedia.ch ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Thanks for all the fish!
On Fri, Jun 7, 2013 at 6:32 PM, Milos Rancic wrote: > I am leaving the movement. I thought to leave it quietly, with just a > bit more than a few words to stewards and Wikimedia Serbia, but after > the first question why I am leaving, I realized that I actually owe to > many of you the explanation for leaving the movement after almost 10 > years. > > > It's a pity to hear that Millosh is taking a long WikiBreak. Wikimedia will be more boring now. Thanks for all you've given, I wish you all the best Marco (Cruccone) ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Thanks for all the fish!
Thanks to all of you! It really matters to know that I will be welcome if I back and it matters that people who matters to me think that I made an impact to them and to the movement. I was unprepared on Amir's mail and I reacted on it emotionally. After that I realized which kind of emails I could get :) While reading your emails, I got once more drive to stay. However, that didn't solve my motivation problem and there is no sense to stay without it solved. I am not going to find another movement. When you felt the best one, everything else doesn't have a lot of sense. Besides that, I would have the same kind of lack of motivation, or probably worse one. The problem with my motivation is exclusively my personal issue. Events in the movement influenced that, but the main portion is related to my inner issues and I am now quite confident what the reason is, which corresponds with the second part of 2011. There is another thing produced by your answers. Since this morning I am able to imagine myself back, which I wasn't able for months. I feel freed and able to think that I need a period of time off to be capable to back. I was thinking yesterday that I need serious reconsideration of my inner drives, that I need different life to fix my problems. Now I think that I even have the cure. So, will be back sooner than I was thinking. I suppose that it will be about months rather than years. (And I feel now a bit as a drama queen and attention whore, as nobody would notice even a half of year without my input.) I am professionally connected to MediaWiki. Thus, I won't be able to disappear, even it was about my feelings from yesterday. I am reading news on Portal:Current events and I am occasionally editing English Wikipedia. I noted Sara's and Manuel's emails about what they are doing. Please, connect with others who are doing similar things! Partial efforts are always much less effective. (Sarah, connect with MF-Warburg, he will continue my work in relation to mapping languages. Manuel, connect with Sanja from WM RS.) I am subscribed to so many public Wikimedia lists, that it would require considerable effort to unsubscribe from all of them. Fortunatelly, I am using a separate account for those lists. I will not delete but forget it for the time I will need to remotivate myself. And to repeat: I will always be happy to help to any of you. Feel free to contact me. ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Blocking of HTTPS connection by China
This response seems to miss the fact that, in this particular case, censorship is being accomplished through eavesdropping. On Fri, Jun 7, 2013 at 6:24 PM, Matthew Roth wrote: > Hi all, > I wanted to share a clarifying email from Ryan Lane in WMF Ops. He's > working through the challenges of HTTPS from the Foundation's end. > > Please see below for more details: > > -Matthew > > On Fri, Jun 7, 2013 at 2:31 PM, Ryan Lane wrote: > > > How does it impact people? Short answer: it shouldn't. Long answer: It > may > > make the site slightly slower due to increased network latency, and it is > > slightly more computationally expensive, which may make the site slower > on > > computers that are underpowered. > > > > How does it impact the WMF? It depends. For enabling it for logged-in > > users, or for those that use HTTPS-anywhere? It doesn't affect us, > because > > that's the state we're in right now. For making HTTPS the default for > > anonymous users? We need to change how our infrastructure works. We may > > need to buy additional hardware. We definitely need to do some > engineering > > work. > > > > How does it impact the government's ability to apply censorship? Short > > answer: it doesn't. It affects their ability to eavesdrop on people. Long > > answer: It depends on how sophisticated the government's censorship > program > > is. In some countries the government's censorship program can be totally > > bypassed using HTTPS. China's program is very sophisticated. The best > HTTPS > > is going to help the Chinese is to give them a reasonable amount of > > protection against eavesdropping. It's still possible for China to > > eavesdrop, even when users are using HTTPS, if China has subverted any of > > the Certificate Authorities trusted by our browsers. > > > > Are there negative sides of each choice? Yes. Not providing HTTPS means > > that users will always be subject to eavesdropping, which in very > > authoritative countries could mean they are imprisoned or killed for > > reading or editing Wikipedia, depending on what they are reading or > > editing. Realistically not making HTTPS the default is similar to not > > providing it for all intents and purposes. Search engines will bring > people > > to the HTTP version of the site, not the HTTPS version so the vast > majority > > of users will still be able to be eavesdropped on. Making HTTPS the > default > > also has negatives. A very small minority of users don't have HTTPS > > support, or their computers are so old that it makes the site unusably > > slow. That's a *very* small percentage of users, though. Additionally, it > > makes the site slower for everyone, which may cause a decrease in viewers > > and/or editors. > > > > This is likely the most non-technical way I can explain things. I hope it > > helps! > > > > > On Fri, Jun 7, 2013 at 11:39 AM, Benjamin Chen > wrote: > > > On 8 Jun, 2013, at 12:24 AM, Matthew Roth wrote: > > > > > We have had contact with the authors of the blog and they have said > they > > > will publish our response to their article, though I'm not sure when or > > in > > > what format. > > > > Great. That's really fast response. > > > > On the issue itself, we haven't seen any large scale blocks for years > > (around the time since last time Jimbo visited some Chinese official more > > than 4 or 5 years ago I think). > > > > The secure.wikimedia domain was blocked long ago, but they waited till > now > > to block HTTPS, after 3 years? (I can't remember when it was enabled). I > > wonder how long it took for them to realise. > > > > It is suggested that this could be a long term block similar to how > > secure.wikimedia was blocked - for HTTPS they have no control over > content, > > so they are simply blocking it all. For HTTP they are still performing > deep > > package inspection (means content censoring), so since they can filter > what > > the Chinese people can see, it's likely that they'll leave HTTP alone. > > > > > > Regards, > > > > Benjamin Chen / [[User:Bencmq]] > > ___ > > Wikimedia-l mailing list > > Wikimedia-l@lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l > > > > > > -- > > Matthew Roth > Global Communications Manager > Wikimedia Foundation > +1.415.839.6885 ext 6635 > www.wikimediafoundation.org > *http://blog.wikimedia.org/* > ___ > Wikimedia-l mailing list > Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l > ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Blocking of HTTPS connection by China
What is this "hard-enabled" and "soft-enabled"? If the Chinese volunteer editor community requests that HTTPS be "soft-enabled" for them, and you do so, does that solve anything? On Fri, Jun 7, 2013 at 12:24 PM, Matthew Roth wrote: > We've also hard-enabled HTTPS on all of our > private wikis and have soft-enabled HTTPS on a single wiki (Uzbek > Wikipedia), when it was requested by the volunteer editor community there." ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Blocking of HTTPS connection by China
On Fri, Jun 7, 2013 at 6:24 PM, Matthew Roth wrote: > We have had contact with the authors of the blog and they have said they > will publish our response to their article, though I'm not sure when or in > what format. > > This is the content of our response: > > "The Wikimedia Foundation doesn’t hold any readers of our projects in any > less regard than others. Our mission is to bring the knowledge contained in > the Wikimedia projects to everyone on the planet. There is no strategic > consideration around how we can make one or another language project more > accessible or readable in one part of the world or another. We do not have > control over how a national government operates its censorship system. We > also do not work with any national censorship system to limit access to > project knowledge in any way. > > It is worth noting the blog post makes some incorrect assumptions about > Wikimedia culture - including incorrect titling of some Wikimedia > Foundation staff (e.g. Sue Gardner is the Executive Director of the > Wikimedia Foundation, the non-profit that operates Wikipedia -- Wikipedia > is written by tens of thousands of volunteers and has no director and no > hierarchy of editors). There is also an incorrect assertion that Jimmy > Wales has a direct role in working with our staff in making changes to core > infrastructure. Of course Jimmy plays a role in the conversation, but he is > participating in the conversation along with anyone else from the volunteer > editor community. > > On the larger topic, the implementation of HTTPS by default across all > Wikimedia sites for all readers and users is non-trivial, and a > conversation is ongoing within the Wikimedia Foundation and within the > community about how we might make this possible. We do have plans to > eventually enable HTTPS as the default, but it's difficult and we're taking > steps toward this goal over time. > > Our first step is to force HTTPS for logged-in users. The next step will be > to expand our SSL cluster and to do some testing on a wiki-by-wiki basis > with anonymous HTTPS. At some point later we'll attempt to enable HTTPS for > anons on all projects. Then we'll look at enabling HSTS, so that browsers > know they should always use HTTPS to access our sites. > > We've only had proper native HTTPS for about a year and a half. We > attempted to force HTTPS by default for logged-in users last month and > rolled it back. We'll be attempting this again soon. So, it's something > we're actively working on. We've also hard-enabled HTTPS on all of our > private wikis and have soft-enabled HTTPS on a single wiki (Uzbek > Wikipedia), when it was requested by the volunteer editor community there." > > > Great response, which makes it clear that there is no politically biased motives here, just techinical issues. I hope they will be publishing it in some sort of decent form, though unfortunately the damage is generally never restored, it might go a long way. On a tiny side note: Is calling non logged in users on official communications a good idea? I've always found it to be sounding quite denigrating. > > > > On Fri, Jun 7, 2013 at 6:50 AM, shi zhao wrote: > > > https://upload.wikimedia.org also blocked > > Chinese wikipedia: http://zh.wikipedia.org/ > > My blog: http://shizhao.org > > twitter: https://twitter.com/shizhao > > > > [[zh:User:Shizhao]] > > > > > > 2013/6/7 Benjamin Chen : > > > Hi, > > > > > > Since 31 May, China's Great Firewall has blocked the HTTPS connection > to > > all language versions of Wikipedia, by blocking port 443 on two of our > IPs. > > I was also told that service to Wikimedia Commons may be affected. Other > > projects, such as en.wikisource are not affected by this block (but they > > may still be subjected to keyword censoring on HTTP). > > > > > > Compared to the previous short-lived half-day block, this time the > block > > has been in place for a week and as usual no one knows if it will last > for > > long. > > > > > > Here is an article that has some explanation, some comments, and > (their) > > opinions and suggestions for the Foundation. > > > > > > > > > https://en.greatfire.org/blog/2013/jun/wikipedia-drops-ball-china-not-too-late-make-amends > > > > > > Regards, > > > > > > Benjamin Chen / [[User:Bencmq]] > > > > > > > > > ___ > > > Wikimedia-l mailing list > > > Wikimedia-l@lists.wikimedia.org > > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l > > > > ___ > > Wikimedia-l mailing list > > Wikimedia-l@lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l > > > > > > -- > > Matthew Roth > Global Communications Manager > Wikimedia Foundation > +1.415.839.6885 ext 6635 > www.wikimediafoundation.org > *http://blog.wikimedia.org/* > ___ > Wikimedia-l mailing list > Wikimedia-l@lists.wikimedia.
Re: [Wikimedia-l] Blocking of HTTPS connection by China
On Sat, Jun 8, 2013 at 9:41 AM, Anthony wrote: > > What is this "hard-enabled" and "soft-enabled"? I hope someone will correct me if I'm wrong, but... I believe that "soft-enabled" means that https was set as the protocol in the canonical URLs for uzwiki. So search engines should start linking to the https URLs, and non-relative links generated by MediaWiki on WMF wikis would link to https rather than http. And, eventually, the links that people post to other places would start to be more often https too. But a visitor may still go to the http URL if they want to. Bug 43466[1] seems relevant, and links to other discussion. "Hard-enabled", on the other hand, means that anyone fetching the http URL would be redirected to the corresponding https URL.[2] If this were somehow done now, then people in China would not be able to read Wikipedia at all because the http links would just redirect to https and then China's firewall would block the https request. The blog post mentioned earlier in this thread hopes that that would make China back down and unblock https to Wikipedia. [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=43466 [2]: With an HTTP 301 redirect, most likely. ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Solving the China censorship problem
I have no idea what you are trying to say. Perhaps others are having the same problem and that is why they haven't replied since you posted this yesterday? Who are we asking what? How would transcoding the stoplist stop censorship? On Fri, Jun 7, 2013 at 10:28 PM, James Salsman wrote: > If we transcoded the stoplist would we still trigger censorship in China? > http://en.wikipedia.org/wiki/Wikipedia_talk:Wikipedia_Signpost/Newsroom/Suggestions/Archive_20#Mentioning_Wikipedia_on_Chinese_Skype_triggers_surveillance > > All centralized authorities engage in misguided attempts to impose content > restrictions on what they percieve as threatening. Asking others for their > opinions on how to counteract these mistakes is an integral part of > building reference material in general, not just encyclopedias. > > I see no better solution than to institute such requests. > ___ > Wikimedia-l mailing list > Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Blocking of HTTPS connection by China
On Sat, Jun 8, 2013 at 12:01 PM, Brad Jorsch wrote: > "Hard-enabled", on the other hand, means that anyone fetching the http > URL would be redirected to the corresponding https URL.[2] If this > were somehow done now, then people in China would not be able to read > Wikipedia at all because the http links would just redirect to https > and then China's firewall would block the https request. The blog post > mentioned earlier in this thread hopes that that would make China back > down and unblock https to Wikipedia. That might not even work, if they decide to return the contents of the (proxied) https page rather than the redirect. Bleh, that's depressing. ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
[Wikimedia-l] [Wikimedia Announcements] This Month in GLAM: May 2013
*This Month in GLAM* is a monthly newsletter documenting recent happenings within the GLAM project, such as content donations, residencies, events and more. GLAM is an acronym of *G*alleries, *L*ibraries, *A*rchives and *M*useums. You can find more information on the project at glamwiki.org. *This Month in GLAM – Issue V, Volume III – May 2013* -- Australia and New Zealand report: Australian participation - east and west; urban and outback; at home and away http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Australia_and_New_Zealand_report Belgium report: Belgian cultural institutions interested in Open Data http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Belgium_report Czech Republic report: QRpedia codes in Silesian Museum Opava http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Czech_Republic_report Finland report: Maps; WLPA; Workshop material http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Finland_report France report: Edit-a-thon in Quai Branly http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/France_report Germany report: Being online on air - TV cooperation http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Germany_report Mexico report: Edit-a-thons in Puebla and Mexico City; *Möebius* radio program http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Mexico_report Netherlands report: Europeana Fashion edit-a-thon; First Dutch Wikipedian in Residence; Wikimedia Hackathon; Wiki loves libraries http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Netherlands_report Spain report: Wiki Loves Catalan Public libraries http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Spain_report Sweden report: A month full of art http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Sweden_report Switzerland report: QRpedia Pilot at the Natural History Museum in Bern http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Switzerland_report UK report: Monmouth; Museums; More http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/UK_report USA report: Wikipedian in Residence in the Smithsonian; News in brief http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/USA_report Special story: GLAM and Early Telescopes http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Special_story Open Access report: Bugfixes; over 10,000 files from PLOS; conferences http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Open_Access_report Calendar: June's GLAM events http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Contents/Events -- Single page view http://outreach.wikimedia.org/wiki/GLAM/Newsletter/May_2013/Single Twitter http://twitter.com/ThisMonthinGLAM Work on the next edition http://outreach.wikimedia.org/wiki/GLAM/Newsletter/Newsroom -- The *This Month in GLAM* team http://outreach.wikimedia.org/wiki/GLAM/Newsletter ___ 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 Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Solving the China censorship problem
Nathan wrote: >... > How would transcoding the stoplist stop censorship? The paper Leslie linked to indicates that the Great Firewall operates through automated packet inspection, but its stoplist is regularly exposed in peer-to-peer applications such as TOM-Skype. We could replace its stoplist words with alternate encodings which do not match textually. There are an infinite number of ways to do this, from insertion of tags, to graphical image replacement, to use of javascript which evaluates to the stoplist words, or any other of a literally countably infinite number of steganographic techniques. Most people simply capitulate to the Great Firewall. Shouldn't we be setting the example for others of showing how it's easily defeated? > Who are we asking what? On these any other topics involving activism, we should be asking the community for solutions and discussing them, but the centralization of the WMF is drifting further away from that. For example, the annual plan has apparently been drafted without any community review before going to the Board this year. Last year we had regular fundraising testing updates about once per werk, but we've only had one so far this year. Who approved the tighter restrictions on who can vote in Board elections this year? Nobody has bothered to ask donors whether they would prefer to pay staff market pay rates instead of following the ”peer group” practice of huge raises for the top and uncompetitive salaries for new hires, based on an interpretation of Dan Pink's work which he and the secondary literature both firmly reject. Perhaps the elections and ED replacement will provide leadership who care more about the evidence than suffering through having to admit that they've been misguided. On Fri, Jun 7, 2013 at 10:28 PM, James Salsman wrote: > If we transcoded the stoplist would we still trigger censorship in China? > http://en.wikipedia.org/wiki/Wikipedia_talk:Wikipedia_Signpost/Newsroom/Suggestions/Archive_20#Mentioning_Wikipedia_on_Chinese_Skype_triggers_surveillance > > All centralized authorities engage in misguided attempts to impose content > restrictions on what they percieve as threatening. Asking others for their > opinions on how to counteract these mistakes is an integral part of > building reference material in general, not just encyclopedias. > > I see no better solution than to institute such requests. ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Solving the China censorship problem
On 8 June 2013 23:16, James Salsman wrote: > Who approved the tighter restrictions on who can vote in Board elections > this year? > The requirements for voting are almost identical in 2013 compared to 2011. For editor voters, WMF staff and contractors, and Board/advisory board members, they are exactly the same. A modification was made for developer voters to reflect the change in the way that code is committed. Risker (member of the Election Committee) ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Solving the China censorship problem
Too bad mailing list posts don't count :-P My editing has been highly sporadic, and for the first time in six years, apparently I don't qualify to vote. On Sat, Jun 8, 2013 at 11:45 PM, Risker wrote: > On 8 June 2013 23:16, James Salsman wrote: > > > > >> Who approved the tighter restrictions on who can vote in Board elections >> this year? >> > > The requirements for voting are almost identical in 2013 compared to 2011. > For editor voters, WMF staff and contractors, and Board/advisory board > members, they are exactly the same. A modification was made for developer > voters to reflect the change in the way that code is committed. > > > > Risker (member of the Election Committee) > ___ > Wikimedia-l mailing list > Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
