[Wikimedia-l] Report of grants given out by the Wikimedia Foundation in 2020−2021
Hi folks, I wanted to share the link to a report covering grants given out by the Wikimedia Foundation during the 2020−2021 fiscal year. This is the second annual grantmaking report, inspired last year by the Fundraising reports that fundraising teams have prepared for many years. https://meta.wikimedia.org/wiki/Grantmaking/Reports/2020-2021 I would like to thank Janice Tud for all her help in making sense of our grants database, and Kassia Echavarri-Queen, Jessica Stephenson, and the rest of the Community Resources team for contributing additional context and narrative to the report beyond the charts and numbers. Questions and comments are welcome, preferably on the talk page. Minor edits, typo fixes, etc. are appreciated on the page itself. -- Guillaume Paumier (he/him) ___ Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/KAJXPT62VOJZW7JYT7M36YTJJH6HEKLL/ To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
[Wikimedia-l] Re: About raising money
/Wikipedia:There_is_a_deadline In a nutshell: by all means, let's better assess our impact, instead of just assuming it. And let's discuss accountability mechanisms. But let's also be realistic about the resources required for a mission as broad as ours. And let's understand both the urgency of our endeavor, and the financial demands of our collective promise of Knowledge Equity. Misery is no more virtuous than opulence if wealth is distributed equitably to advance our mission. -- Guillaume Paumier (he/him) ___ Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MBLZ5R6SGOWU53CGTEKYOCHVOZ7YY74B/ To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
[Wikimedia-l] Report of grants given out by the Wikimedia Foundation in 2019−2020
Hi folks, I wanted to share the link to a report covering grants given out by the Wikimedia Foundation during the 2019−2020 fiscal year. This was inspired by the Fundraising reports that fundraising teams have prepared for many years. The intent is to publish similar yearly reports for grantmaking going forward. https://meta.wikimedia.org/wiki/Grantmaking/Reports/2019-2020 Questions and comments are welcome, preferably on the talk page. -- Guillaume Paumier (he/him) ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] The Wikimedia Enterprise API project
Hi, Le mar. 16 mars 2021 à 13:51, Chris Keating a écrit : > Thanks Liam! > > Great to see such clear and thorough documentation of what this project is > about, why we're doing it, and why it's being done in this particular way. > Indeed! Obviously, I'm biased, but I appreciate the level of documentation provided, which makes it easier to have an informed and in-depth discussion (although it's a lot to translate!). >From the Strategic Direction in 2017 ( https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 ), to the WMF revenue strategy in 2018 ( https://meta.wikimedia.org/wiki/2018_Revenue_strategy/Summary ), to the working group on Revenue Streams in 2019 ( https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations/Iteration_1/Revenue_Streams/1 ), to the final recommendations in 2020 ( https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations/Increase_the_Sustainability_of_Our_Movement ), and now to this, it's certainly been a long journey, but it's great to see this coming to life. Taking this idea and shepherding it towards implementation while respecting the ethos of the movement is not an easy feat, and the team really seems to take this to heart, which is a good sign. -- Guillaume Paumier (he/him) ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Next steps on Wikimedia Space
Hi, Le mer. 19 févr. 2020 à 10:31, Todd Allen a écrit : > I don't think anyone had bad intentions. It was just redundant. > > Real time communication is on IRC. Asynchronous communication is either on > the wiki, preferably, or on the mailing list. > > Quit trying to make us TwitFaceTube. The tools we already have work just > fine. That perspective suffers from a lack of empathy. "The tools we already have" may work for the limited sample of the population who are currently using them. Assuming that that sample is representative is flawed and is a classic example of survivorship bias. If we have learned anything from the Space experiment and from years of strategy discussions, it is that the tools we currently have do not, in fact, work just fine for a large number of people, whose voices are missing from our discussions and content. -- Guillaume Paumier (he/him) ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Snøhetta and Wikimedia
Earthfire and rustbuckets, can we please stop calling for people to be fired for doing their job, especially right after admitting that there is obviously more going on that we don't know about yet. No one's going to "start replacing employees" based on mailing list messages, so this kind of peremptory statement only serves as dog-whistling posturing, and only contributes to the denominator part of this list's signal-to-noise ratio. This is literally divisive. Be better than that. On Fri, Jan 17, 2020 at 4:50 PM Pine W wrote: > There are ways that Wikimedia rebranding consultations could be done > collaboratively, politely, and with careful stewardship of donor's money. > This is not one of them. > > I think that it's time for some people in WMF to move on. Without having > access to WMF internal discussions, I don't know exactly who I would > remove, but I've had enough of poor coordination, questionable financial > decisions, and discourtesy, and I hope that the donors and the Board have > too. These problems are not isolated to the rebranding effort, but I think > that this is as good a place as any to start replacing employees who aren't > working out. > > Pine > ( https://meta.wikimedia.org/wiki/User:Pine ) > ___ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] [Strategy] September 28: Strategy update - Final draft of movement direction and endorsement process (#25)
al or social inequity. > But well, the WMF will claim that that is what the „community“ wants - > given the new definition of community, that would even be true. :-( > > Certainly, people can set up a page on Meta to express their concerns > about such an unready draft paper. Is this an announcement that > endorsements of the draft paper will be welcomed at the main gate, while > the concerns will have to use the backyard entrance? > > Kind regards > Ziko > > > > > > > Guillaume Paumier <gpaum...@wikimedia.org> schrieb am Mo. 2. Okt. 2017 um > 22:36: > >> Hello, >> >> If you feel a strong urge to reject the text, there is obviously nothing >> preventing anyone from creating a Meta-Wiki page to that purpose. However, >> I would first ask to reflect on the process, its outcome, and where it's >> going. >> >> Strategy is complicated. Building a movement strategy even more so [ >> https://blog.wikimedia.org/2017/05/19/wikimedia-strategy- >> 2030-discussions/ >> ]. One person's serious issue may be another person's slight preference. >> People's serious issues may be at odds with each other (and I can tell you >> from experience that they are indeed). Balancing all those priorities is a >> difficult exercise, and I certainly don't claim to have done it perfectly. >> But I do think the outcome we've arrived at represents the shared vision >> of >> a large part of the movement. >> >> As I was writing, rewriting and editing the text of the direction, I did >> consider everything that was shared on the talk page, and the last version >> is indeed based on those comments, as well as those shared during multiple >> Wikimania sessions, individual chats, comments from the Drafting group, >> from affiliates, from staff, and so on. >> >> While I did consider all of those, I didn't respond to every single >> comment, and there is little I can do about that except apologize and >> endeavor to do better. I should have set clearer expectations that not >> every comment would be integrated in the text. I ran into an issue all too >> familiar in the Wikiverse where one person had to integrate comments and >> feedback from a large group of people at the same time. >> >> High-level vision and strategy integration isn't really something that can >> be spread across a group of people as easily as writing an encyclopedia >> article, and so I ended up being a bottleneck for responding to comments. >> I >> had to prioritize what I deemed were issues that were shared by a large >> group, and those that seemed to be more individual concerns. >> >> Anyone who knows me knows that I'm not the "everything must be positive, >> fantastic, yeehaw-we-are-number-one" type. If anything, I'm rather the >> opposite, as I think many Wikimedians are. If we had unlimited time, I'd >> probably continue to edit the draft for years, and I'm sure there would be >> other perfectionists to feed my obsession. >> >> However, others in my personal and professional circles have helped me >> realize in the past few weeks that even getting to this stage of the >> process is remarkable. As Wikimedians, we often focus on what's wrong and >> needs fixing. Sometimes, our negativity bias leads us to lose focus of the >> accomplishments. This can clash with the typical American culture, but I >> think somewhere in the middle is where those respective tunnel visions >> widen and meet. >> >> One thing I've learned from Ed Bland, my co-architect during this process, >> is that sometimes things can't be perfect. Sometimes, excellence means >> recognizing when something is "good enough" and getting out of the >> asymptotic editing and decision paralysis loop. It means accepting that a >> few things annoy us so that a larger group of people is excited and >> motivated to participate. >> >> From everything I've heard and read in the past two months, the last >> version of the direction is agreeable to a large part of individuals, >> groups, and organizations that have been involved in the process. Not >> everyone agrees with everything in the document, even within the >> Foundation, and even me. But enough people across the movement agree with >> enough of the document that we can all use it as a starting point for the >> next phase of discussions about roles, resources, and responsibilities. >> >> I do hope that many of you will consider endorsing the direction in a few >> weeks. While I won't claim to know everyone involved, I think I know you >> enough, Ziko and Fæ, from your work an
Re: [Wikimedia-l] September 28: Strategy update - Final draft of movement direction and endorsement process (#25)
/088654.html > > [5] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_headquarters > > > > -- > > Katherine Maher > > Executive Director > > > > *We're moving on October 1, 2017! **Our new address:* > > > > Wikimedia Foundation > > 1 Montgomery Street, Suite 1600 > > San Francisco, CA 94104 > > > > +1 (415) 839-6885 ext. 6635 > > +1 (415) 712 4873 > > kma...@wikimedia.org > > https://annual.wikimedia.org > > _______ > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/ > > wiki/Wikimedia-l > > New messages to: 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/wik > i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> > -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Naive questions: what could do the movement with 1B dollars/euros?
Hello, 2017-05-17 10:08 GMT-07:00 David Cuenca Tudela <dacu...@gmail.com>: > Are there any activities that could have a meaningful impact if we ask > donors for such amount of seed money? Are there reasons to do so? > > Can we offer anything else in this world than truth, free knowledge, and an > open inclusive environment? > "Truth, free knowledge, and an open inclusive environment" is already a pretty big commitment :) From a numbers perspective, USD/EUR 1 billion isn't that much of a stretch. Consider that the combined funds raised by the Wikimedia Foundation [1] and Wikimedia Deutschland [2] last year amount to approximately $85 million [3]. We're currently developing a movement-wide strategy using the 2030 time horizon [4], meaning 13 years from now. If we're very conservative and assume no increase at all in funds raised across the movement during that period, that's still a low estimate of $85 million × 13 years ≈ $1.1 billion. Of course, I'm not advocating against having big dreams. We can certainly do a lot more if we manage to accelerate our efforts and find new ways to finance them. My point is that it's less about the numbers, and more about what we decide to focus on (what we use the money for), and how committed we are to that goal (how quickly we get it). This thread is a useful thought exercise because it helps us think big about what we really care about. The good thing is that now is the perfect time for everyone to share their thoughts on what they care about and what they think we should focus on over the next decade. The goal of the movement strategy discussions is precisely that. [4]. So I encourage everyone to participate in those discussions and make their voice heard. Because if we put our minds to it and agree on what to use it for, getting that $/€ 1 billion isn't unrealistic at all, and we can get it long before 2030. [1] https://annual.wikimedia.org/2016/financials.html [2] https://upload.wikimedia.org/wikipedia/commons/8/8d/Jahr esbericht_Wikimedia_Deutschland_2016.pdf [3] This is a low estimate that doesn't include funds raised by other organizations. WMF and WMDE were the easiest to find. [4] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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 Conference 2017 versus movement strategy
Hello Yaroslav, I'm not sure I understand how including affiliates excludes individual contributors. There are many avenues for people and groups across the movement to participate on wikis, in person, in video conference, in off-wiki online discussions, etc. Anyone is welcome to contribute in multiple tracks (as individual participant, affiliate member, or both) and in multiple channels. There were about 100 participants who attended the whole strategy track at the conference; surely there are more than 100 people across the projects who want to voice their opinion on the future of the movement. Also, the strategy sessions that were held in Berlin only concerned "Cycle 1" of the discussion, which will end soon. That first cycle is very open and exploratory and far from the be-all and end-all of the movement strategy process. I certainly hope that many people contribute to cycles 2 and 3 (where the convergence and prioritization will happen) regardless of whether they were in Berlin. 2017-04-06 13:06 GMT-07:00 Yaroslav Blanter <ymb...@gmail.com>: > The backside seems to be that those who have been to the conference feel no > incentive to participate in the strategy discussions in the projects, and > these discussions show up as major disappointment (like those on the > English Wikipedia or Wikidata) or do not really interest anybody (at the > Russian Wikivoyage, we compiled a large document, which will likely be > translated to English, moved to Meta and forgotten). Which technically > means that this time, the individual contributors are excluded from > building up the strategy, unless they can do it via chapters and thematic > organizations. > > Cheers > Yaroslav > > On Thu, Apr 6, 2017 at 8:35 PM, Tanel Pern <tanel.p...@gmail.com> wrote: > >> Just to add to this as someone who (also) was at the conference and >> participated in a few of the strategy track sessions, it would have been >> basically impossible to provide any more information than the conference >> website already provides about what took place at this session beforehand, >> given the extremely open-ended nature of the discussions. Just as outlined >> in the session overview [1], the participants started from basically >> nothing (other than their ideas of what's going to be important in the next >> 15 years) and ended up formulating a few dozen thematic statements >> regarding the strategic direction of the movement. Frankly, I'm amazed it >> worked as well as it did. At the same time, I'm not at all amazed that it >> would take time to digitize the materials, given how many people >> participated in the session and how much paper they consumed :) And though >> it wouldn't be difficult to publish the final thematic statements, some of >> them unfortunately don't make sense without some background materials. >> >> Just my €0.02, >> >> Tanel >> >> >> [1] >> https://meta.wikimedia.org/wiki/Wikimedia_Conference_ >> 2017/Program#Movement_Strategy >> >> 2017-04-06 16:42 GMT+03:00 Guillaume Paumier <gpaum...@wikimedia.org>: >> >> > Hello Hajdu, >> > >> > As Chris mentioned, there is a lot of documentation coming from the >> > Wikimedia conference in Berlin. In fact, there is so much >> > documentation that it's going to take the team a few days to digitize >> > and publish everything. You can see some of the notes from related >> > discussions, for example: >> > >> > * The notes from a discussion about movement strategy by contributors >> > from Wikimedia Commons: >> > https://meta.wikimedia.org/wiki/Strategy/Wikimedia_ >> > movement/2017/Sources/Commons_in-person_discussion_at_the_ >> > Wikimedia_Conference >> > >> > * The notes from a discussion about movement strategy by the Wikimedia >> > Foundation's Board of Trustees: >> > https://meta.wikimedia.org/wiki/Strategy/Wikimedia_ >> movement/2017/Sources/ >> > Wikimedia_Foundation_Board_of_Trustees_-_Discussion_at_the_ >> > Wikimedia_Conference >> > >> > The rest of the notes, photos, summaries, etc. will be published this >> > week or the next. There was nothing confidential about the sessions, >> > and many participants have shared their work and sessions on Commons ( >> > https://commons.wikimedia.org/wiki/Category:Wikimedia_Conference_2017 >> > ) and on social media ( >> > https://twitter.com/search?q=wmcon%20strategy=typd ). >> > >> > I hope that this reassures you and gives you some materials to look >> > over until we upload everything else. >> > >> > >> > 2
Re: [Wikimedia-l] Wikimedia Conference 2017 versus movement strategy
Hello Hajdu, As Chris mentioned, there is a lot of documentation coming from the Wikimedia conference in Berlin. In fact, there is so much documentation that it's going to take the team a few days to digitize and publish everything. You can see some of the notes from related discussions, for example: * The notes from a discussion about movement strategy by contributors from Wikimedia Commons: https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Sources/Commons_in-person_discussion_at_the_Wikimedia_Conference * The notes from a discussion about movement strategy by the Wikimedia Foundation's Board of Trustees: https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Sources/Wikimedia_Foundation_Board_of_Trustees_-_Discussion_at_the_Wikimedia_Conference The rest of the notes, photos, summaries, etc. will be published this week or the next. There was nothing confidential about the sessions, and many participants have shared their work and sessions on Commons ( https://commons.wikimedia.org/wiki/Category:Wikimedia_Conference_2017 ) and on social media ( https://twitter.com/search?q=wmcon%20strategy=typd ). I hope that this reassures you and gives you some materials to look over until we upload everything else. 2017-04-05 0:12 GMT-07:00 Hajdu Kálmán <kal...@startadsl.hu>: > > Hi, There is a very active campaign for strategic conversation defining the > future role of Wikimedia in the world. In the last weekend has been hold the > Wikimedia Conference 2017 > in Berlin. On this conference was a spacial group organized from > Representatives > for the Movement Strategy Track. I paid great attention the conference > program, but unlike the former practice on the conference page on the meta > was not e bit information about what happened in this section. No Ethernet, > no abstract of presentation, nothing. > > I don't understand the new policy of organizers, that the conference out of > the ordinary way was hold in totally confidential or secret wise. My > question this should bee the new Wikimedia strategy? > > Texaner > -- > Using Opera's mail client: http://www.opera.com/mail/ > > ___ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l@lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe> -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Welcoming 19 long-time Wikimedians as Coordinators for Movement strategy
Hi Lane, 2017-03-10 8:01 GMT-08:00 Lane Rasberry <l...@bluerasberry.com>: > Congratulations to everyone. > > I notice that some of these users do not have their WMF accounts connected > to their user accounts. > > Would it be a problem to ask for user and work accounts to reference each > other? Not a problem at all; it is probably an oversight. The coordinators have had a lot to do this week with onboarding, translations, and preparations, and it may simply be that they didn't get around to completing their user page. I would suggest leaving them a friendly note on their talk page if you notice something missing. -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Welcoming 19 long-time Wikimedians as Coordinators for Movement strategy
Hello Yaroslav, Yes, the Foundation's Community Engagement department, who are the most familiar with Wikimedia communities, reviewed the applications thoroughly. If you have concerns about a specific person, which obviously can't be discussed on a public list, I happy to discuss them with you privately. 2017-03-09 23:48 GMT-08:00 Yaroslav Blanter <ymb...@gmail.com>: > Thanks the coordinators. I do not know everybody on the list, but I > recognize there names of many excellent people. > > I also see there a name which has rung a bell for me, and the sound of the > bell was somewhat alarming. I checked and found indeed that the coordinator > has a sizable block log on the Russian Wikipedia, their home project, for > actions which include trolling and disruptive editing, and at some point > had to be placed under a topic ban. The most recent block is one and half > years ago. Which poses a natural questions whether the candidates were > actually screened. -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Welcoming 19 long-time Wikimedians as Coordinators for Movement strategy
Hello, As most of you are aware, the Wikimedia movement has embarked on an ambitious initiative to discuss our collective future and determine a movement-wide strategic direction. [1] The movement is composed of people in many different roles, notably individual contributors who may not be affiliated with any organized group. It can be challenging to reach individual contributors and involve them in strategy discussions, since they may not monitor the usual communication channels, and they may not think that strategy discussions are relevant to them. For this year’s movement strategy process, the Wikimedia Foundation has decided to hire 19 part-time discussion coordinators to better bridge the gap between the strategy discussions and local communities of contributors. Today, I am thrilled to announce that we have concluded the search and assembled a stellar team of 19 long-time Wikimedians, who have agreed to join the movement strategy efforts in this capacity. As you go through the team’s page on Meta-Wiki, you will see many familiar names. [2] The team is composed of Abbad, Bohdan, Chico, Gereon, Jonatan, Ran, Marco, Nahid, Niccolò, Tomasz, Robin, Samuel, Satdeep, Szymon, Oleg, Takashi, Todd, Tuan, and Venus. Because of the team’s geographic distribution, Jan Eissfeldt, from the Foundation’s Support and Safety team, has agreed to help lead the day-to-day activities of the group of Asian language coordinators. All the coordinators started on Monday for a 3-month contract, and they have already been hard at work, translating materials on Meta and organizing the outreach to their local communities. [3] Some will focus their efforts on specific language communities [4], and others will support an array of smaller communities. If you are interested in working with the coordinators to bridge the gap with your local communities, I invite you to take a look at the description of the coordinator role, and sign up using the form on that page. [5] You can also contact them directly via their talk page. I want to express my deepest gratitude to everyone who was involved in this ultra-fast hiring process, most notably the Foundation’s Talent & Culture team, who handled the recruiting and administrative onboarding masterfully, and the Community Engagement department, who reached out to their contacts, thoroughly reviewed applications, and made this ambitious wave of recruiting ridiculously easy for me. Please join me in welcoming Venus, Tuan, Todd, Takashi, Oleg, Szymon, Satdeep, Samuel, Robin, Tomasz, Niccolò, Nahid, Marco, Ran, Jonatan, Gereon, Chico, Bohdan, and Abbad in their new role. Guillaume Paumier [1] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 [2] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/People/Strategy_coordinators [3] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Track_B/Outreach/Map [4] https://meta.wikimedia.org/wiki/Talk:Strategy/Wikimedia_movement/2017#Language_list_in_development [5] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017/Toolkit/Discussion_Coordinator_Role -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Opening the 2016 Values discussion
Hello, The discussion is now wrapping up. The process and its outcome were presented last week at the Metrics and activities meeting; you're encouraged to watch the segment in this video: https://www.youtube.com/watch?v=-blWUhkm8g4=17m18s You can read the full transcripts of the discussions on Meta: https://meta.wikimedia.org/wiki/Values/2016_discussion/Transcripts as well as browse through the main themes that emerged: https://meta.wikimedia.org/wiki/Values/2016_discussion/Themes and their synthesis: https://meta.wikimedia.org/wiki/Values/2016_discussion/Synthesis The discussion on the talk page of the synthesis is open until March 4 to finalize the language of the descriptions. I want to thank everyone who participated in the discussions, and everyone who helped with the organization. It was truly a joy to see the interest of the participants and the deep, thoughtful discussions that resulted from it. I believe the values that have emerged as part of this process constitute a part of our organizational identity that we had not entirely codified, or even been conscious of, before. As our friend Ray aptly put it in 2007, "The values were already there. Perhaps they might have been poorly codified. Had they not been there, neither you nor I would have stuck around for over five years." https://lists.wikimedia.org/pipermail/wikimedia-l/2007-September/079180.html I hope that this exercise has helped us realize why we're here, and that its outcome resonates with many members of our communities, both present and future. 2016-10-18 11:27 GMT-07:00 Guillaume Paumier <gpaum...@wikimedia.org>: > Greetings, > > As a community, we've talked a lot about values in the past year. The > core values of the Wikimedia Foundation were first formulated in > 2007−2008 and have not really been discussed in depth since then. In > 2013, we also developed Guiding principles, a list of more practical > norms and expected behaviors that guide our day-to-day work at the > Foundation. Combined with our vision and mission statements, those > documents represent the core facets of our organizational identity. > > Both staff and volunteers have expressed concerns that there isn't > currently a shared understanding (among the staff and other > constituents) of what our core values are, and how we express them in > our work. We've also talked about a need to revisit or reinforce them. > > A few months ago, a working group formed to organize a series of new > discussions about the WMF's values. The goal is to reflect on what is > bringing us together, identify the core beliefs that motivate our > vision, refine our list of values, and clarify our organizational > identity. > > Discussions about values in nonprofit organizations are usually done > internally. Given the open and collaborative nature of the Wikimedia > movement, such a closed, internal process wouldn't make sense for the > WMF. The Foundation is part of an integrated ecosystem of individuals > and organizations that contribute to defining its identity. Input > should be collected not just from staff and Board members, but also > from volunteers, affiliates, and partners who wish to participate in > this process. > > On behalf of the Values working group, I would therefore like to > invite you to this discussion on Meta. There, you will find more > information about the process, as well as a page to share your > perspective on the Wikimedia Foundation's values. The framing that > we're using for this discussion is one that considers values as the > core intrinsic beliefs that drive our participation in the movement. > > https://meta.wikimedia.org/wiki/Values/2016_discussion > > The discussion will be open for a month, i.e. until November 20. > Comments added after that date will still be welcome, but may not be > included in the summary process. > > I hope many of you take this opportunity to help define (or refine) > the Foundation's organizational identity. > > -- > Guillaume Paumier > Wikimedia Foundation -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: 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] Fwd: Opening the 2016 Values discussion
Reposting in case it didn't make it to the list (and because more exposure can't hurt an any case.) -- Forwarded message -- From: Guillaume Paumier <gpaum...@wikimedia.org> Date: Tue, Oct 18, 2016 at 11:27 AM Subject: Opening the 2016 Values discussion To: Wikimedia-announce <wikimediaannounc...@lists.wikimedia.org> Greetings, As a community, we've talked a lot about values in the past year. The core values of the Wikimedia Foundation were first formulated in 2007−2008 and have not really been discussed in depth since then. In 2013, we also developed Guiding principles, a list of more practical norms and expected behaviors that guide our day-to-day work at the Foundation. Combined with our vision and mission statements, those documents represent the core facets of our organizational identity. Both staff and volunteers have expressed concerns that there isn't currently a shared understanding (among the staff and other constituents) of what our core values are, and how we express them in our work. We've also talked about a need to revisit or reinforce them. A few months ago, a working group formed to organize a series of new discussions about the WMF's values. The goal is to reflect on what is bringing us together, identify the core beliefs that motivate our vision, refine our list of values, and clarify our organizational identity. Discussions about values in nonprofit organizations are usually done internally. Given the open and collaborative nature of the Wikimedia movement, such a closed, internal process wouldn't make sense for the WMF. The Foundation is part of an integrated ecosystem of individuals and organizations that contribute to defining its identity. Input should be collected not just from staff and Board members, but also from volunteers, affiliates, and partners who wish to participate in this process. On behalf of the Values working group, I would therefore like to invite you to this discussion on Meta. There, you will find more information about the process, as well as a page to share your perspective on the Wikimedia Foundation's values. The framing that we're using for this discussion is one that considers values as the core intrinsic beliefs that drive our participation in the movement. https://meta.wikimedia.org/wiki/Values/2016_discussion The discussion will be open for a month, i.e. until November 20. Comments added after that date will still be welcome, but may not be included in the summary process. I hope many of you take this opportunity to help define (or refine) the Foundation's organizational identity. -- Guillaume Paumier Wikimedia Foundation ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Qualities for the next long-term WMF executive director
Hi, Le lundi 7 mars 2016, 13:40:20 Brion Vibber a écrit : > > Third, what happens when the "unicorn" retires and we transition again? > > I think we're going to need to think harder about structural remedies: > communications channels, reporting infrastructures, "escape valves" for > miscommunications or squashed communications in the reporting chain, etc. I agree. I think it's going to be critical for us to rebuild the organization in a way that is more resilient to the shortcomings of any single individual. This reminds me of this quote: "As a leader, your goal should always be to build structures and processes that don't depend on you and ideally don't need you." It's from an article I shared with Lila and Boryana in December due to the context then: http://firstround.com/review/the-keys-to-scaling-yourself-as-a-technology-leader/ These were my thoughts on the topic back then: I think a key point here is that the key to an efficient and resilient organization is distributed processes and documentation. The article notably mentions Conway's Law, whose application is unusual in the context of the WMF. The law states that organizations model their products after their own structures and processes. Because the WMF was created /after/ its products, the opposite happened: the WMF modeled itself after the open, collaborative wiki model, and stayed that way for a while. During that initial period, there was little conflict between the WMF and our communities. As the WMF grew and professionalized, we started drifting from that model. The risk of alienating our values and identity (and as a consequence our communities) was identified early on. At Sue Gardner's request, the theme of the 2010 all-staff meeting was "How do we grow our organization but stay who we are" (paraphrased). One of the all- staff exercises was to "list the things we cherish"; One prominent item on this list was "The Casey Browns of this world" ( https://commons.wikimedia.org/wiki/File:WMF_All-staff_meeting_2010_-_Things_we_cherish.jpg ), after the name of one of our most engaged volunteers involved in many support functions for the WMF. I found this so insightful that I took that picture :) Despite that early caution, we /have/ more or less abandoned the wiki model gradually (due to many different factors), and I see this reflected in the results of the Engagement survey. I feel that many of the issues the organization is facing right now (both internally, and externally with our communities) are related to this conflict between our original model and the one we've drifted towards. My impression, based on my personal experience and 6 years of being at the WMF, is that the most successful WMF initiatives have been those led by people who followed the wiki model as closely as possible (regardless of whether they were originally hired from the communities). I'm happy to discuss this further and share my experience in this area, if you're interested. -------- -- Guillaume Paumier Wikimedia Foundation ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Siko's message, and the importance of shared values
Hello, On 13 February 2016 at 13:50, Pete Forsyth <petefors...@gmail.com> wrote: > > I am sure Siko chose all her words carefully, and I encourage anyone who > hasn't to read and consider her message carefully.[1] But for now, I'll > limit my comments to the sentence quoted above -- and specifically, the > second of the four values Siko chose to identify. > > Integrity must be a core value for any organization. Any effort of multiple > people to work toward a common goal must protect integrity as a baseline > value. It is so central and obvious, in my view, that we Wikimedians have > managed to neglect adding it to the central expressions of our values we > have produced over the years. On a related note, a few weeks ago I started putting together a set of pages on Meta-Wiki about Values. The pages most relevant to this discussion are: https://meta.wikimedia.org/wiki/Values/History and https://meta.wikimedia.org/wiki/Values/Review/2016 Discussion is much welcome on the talk pages, especially if people are interested in collaborating on a process for the latter. -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Are we too rigid?
Hello,
Le jeudi 25 février 2016, 02:06:38 Yuri Astrakhan a écrit :
> Guillaume, the idea may come from anywhere, shouldn't we post the process
> on meta? Or is this WMF specific, e.g. "I want my favorite cereal in the
> cafeteria" proposal? :)
This is what I wrote in the introduction of the Business case page:
-
A business case is a document that provides the rationale for making a change
or starting a project. It defines an observed problem and argues the merits of
a proposed solution.
A case may be created for a small change ("Every WMF employee must wear green
clothes on the third Friday of the month") or a large project ("The WMF should
create a freely-licensed YouTube"). They provide a useful framework for
organizing one's thinking and convincing others.
-
Putting the Business case documents on the private staff wiki was the first
step
in my effort to rescue the process from the walled Google Docs abyss, where the
documents got lost after senior staff (who initiated the process) left the WMF.
I
like the framework and was hoping to make it used more widely at the
Foundation over time.
I agree that Meta-Wiki would be a better place in principle. I am slightly
worried that moving the process there might lead some employees to revert to
Google Docs for their ideas and drafts*, whereas they could be convinced to use
the process if it was on the staff wiki (which would still be an improvement).
On the other hand, if the upside is that the tool is useful to, and used by,
volunteers, that may be a good enough reason to move the pages to Meta. It
could set an example for staff to follow. I'm happy to move the pages if people
think it's a good idea.
[*] I refuse to use the word "ideation".
--
Guillaume Paumier
Wikimedia Foundation
https://meta.wikimedia.org/wiki/User:Guillaume_(WMF)
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: 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] Are we too rigid?
Le mercredi 24 février 2016 14:52:45, j'ai écrit : > Hey Yuri, > > [Responding offlist because I'm linking to officewiki] Obviously, I failed to change the To: line. My apologies to everyone who can't access those documents. -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Are we too rigid?
Hey Yuri, [Responding offlist because I'm linking to officewiki] Le jeudi 25 février 2016, 01:38:31 Yuri Astrakhan a écrit : > > In a sense, the barrier of entry for the person in the "weakest position" > would not be as high for the "doer" as for the "inspirer". So I think the > real challenge is how do we capture and evaluate those ideas from the > second group? One possible mechanism is the Business case: https://office.wikimedia.org/wiki/Business_case And also from https://office.wikimedia.org/wiki/Rebuilding#Agency : "If we want to start a new project or make a big change, we can make a case for it and argue its merits to the group." -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Better thankspam
Hello, Le vendredi 15 janvier 2016, 06:07:54 Alice Wiegand a écrit : > My experiences with discourse in a non-Wikimedia context is great. Worth a > try. +1. A few weeks ago, I drafted some notes about moving Wikimedia mailing lists to Discourse (I posted them on a private wiki; I should have known better). I've now posted the drafts on Meta: https://meta.wikimedia.org/wiki/Discourse I suggest we expand that page and continue this specific discussion on the talk page.* * Sadly, we don't have Flow on Meta, so it'll be good ol' wikitext. -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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] Origin and status of WMF Values and Guiding principles
Hello folks, I was adding citations to an internal WMF page, and I went down a wiki- archaeology rabbit hole trying to find the origin of the WMF's Values and Guiding principles documents. I'd like to reach out to the collective accumulated experience of this list to sort out a few questions and disambiguate the two concepts. I realize a lot is happening in the movement (and on this list) these days, and this isn't an urgent, important or groundbreaking discussion. This message is more like a message in a bottle, hoping to find knowledgeable people that can help me clear up the ambiguity :) This is what I've got so far (with some help from Tilman Bayer for a few bits): -o-o-o-o- * Florence Devouard (then-Chair of the WMF's Board of Trustees) started a discussion about the Foundation's values on the foundation-l list in 2007: http://thread.gmane.org/gmane.org.wikimedia.foundation/19502 * The list of values was first drafted by the Board and the Advisory Board, and then discussed on Meta-Wiki with the larger communities: https://advisory.wikimedia.org/wiki/Meeting_August_2007/Notes#Values https://meta.wikimedia.org/wiki/Values * The discussion was restarted by Florence in early 2008 on foundation-l. She presented a new, longer draft of six core values with explanations, and proposed "to the board to finalize (-> approve) the values of Wikimedia Foundation.": http://thread.gmane.org/gmane.org.wikimedia.foundation/25147/ * After some feedback from list members, she posted a modified version on the Meta-Wiki page, which is largely identical to today's text: https://meta.wikimedia.org/w/index.php?diff=858927=856985 * It is unclear whether those Values were officially approved by the Board. I couldn't find a resolution or meeting minutes indicating official approval. * In 2013, then-Executive Director Sue Gardner drafted a list of Guiding principles for the WMF, which were presented to, and approved by, the Board in May of that year. https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Guiding_Principles https://wikimediafoundation.org/wiki/Minutes/2013-04-18#Guiding_Principles https://wikimediafoundation.org/wiki/Resolution:Wikimedia_Foundation_Guiding_Principles * That resolution indicates that the guiding principles "may come to replace the previous list of values", but I couldn't find any confirmation that they did replace them. * A conflicting statement from Sue on Meta-Wiki indicates that "This document isn't intended to supersede the Values document. It's actually intended to flesh out the values a little bit further, so it's more explicit how we live them on a day-to-day basis at the staff level.": https://meta.wikimedia.org/w/index.php?diff=5375389=5367067 -o-o-o-o- We're linking to the WMF's Values in a lot of prominent places, and they've also been brought up many times in recent strategy discussions. There seems to be an underlying assumption, in those discussions, that the Values are a document with the same origin and status as the Vision & Mission statements. My impression (and I'd like to hear thoughts from this list about this) is that the Values document was never "officially" approved by the Board, and instead is more the result of a soft consensus. This isn't to say that those Values wouldn't have as much weight, importance or authority as voted-on documents like the Mission & Vision statements, or the WMF Guiding principles. An unchallenged consensus seems like a valid way of validating rules and principles, especially in the context of our movement. I'm trying to get confirmation about whether this is the case, so as to remove the ambiguity and acknowledge the origin story. As I mentioned, this isn't the most important topic of discussion right now. I'll still be grateful if someone can help me understand the backstories :) -- Guillaume Paumier ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: 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 - 3D Logo for printing
Hello Rodrigo, On 29 October 2015 at 13:12, Rodrigo Padula <rodrigopad...@wikimedia.org.br> wrote: > > Where can I find the source files of the 3d logo printed for the WMF offices? > > I'm planning a photo exhibition here in Brasil for WLE and WLM and I would > like to have that logo printed for our exhibition room. There is more information about the 3D logo at https://wikimediafoundation.org/wiki/Visual_identity_guidelines#toc-3dmodel , and what is and isn't allowed. The file itself is at https://wikimediafoundation.org/wiki/File:Wikipedia_puzzle_globe_3D_render.zip , in "Autodesk Maya" format. HTH, -- Guillaume Paumier ___ 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] possible power point or pdf file
Hello Mardetanha, Le jeudi 6 août 2015, 19:52:17 Mardetanha a écrit : within next month I am going to give lecture about wikipedia and sister projects, I would like to know if have already prepared file to describe about wikipedia (and all sister projects), that I can use for this event. even if it is old it would be useful and I will update with current information. There is a repository of presentations about Wikimedia projects at https://meta.wikimedia.org/wiki/Presentations , and another one at https://commons.wikimedia.org/wiki/Category:Wikimedia_presentations . I'm not sure many are up-to-date, but they can be used as inspiration to get you started :) There's also a smaller list at https://wikimediafoundation.org/wiki/Press_room/WMF_Presentations but they seem more outdated. Hope that helps, -- Guillaume Paumier ___ 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] Environmental impact of Wikipedia
Hello Andrea, Le dimanche 5 juillet 2015, 17:45:34 Andrea Zanni a écrit : I tried to find the info myself, with little success: I'm interested to know about the environmental impact of running Wikipedia (carbon emissions, etc.) and what we are doing about it. Sorry if I missed wikimedia-l threads, or other sources. Here are a couple of old threads to get you started: 2007: WMF-projects: Carbon neutral/low/aware website? http://thread.gmane.org/gmane.org.wikimedia.foundation/17517 2009: Wikimedia and Environment http://thread.gmane.org/gmane.org.wikimedia.foundation/43381 The numbers discussed in those threads are undoubtedly out of date, but I imagine some of the arguments still apply. Hope that helps :) -- Guillaume Paumier ___ 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 office location and remodel
Hello, On Tue, Apr 7, 2015 at 10:07 PM, Aleksey Bilogur aleksey.bilo...@gmail.com wrote: A logistical non-starter! They've got 200+ staff members, any gains to recruitment competitiveness will be quickly lost to the drain that losing whatever significant percent of the staff that doesn't make the move incurs on the organization. I don't think it's that clear-cut. A large part of the Product Engineering staff is already working remotely, so they wouldn't be affected by the change. Many SF-based staffers also work remotely some of the time, and there are constant efforts being made to make the organization more remote-friendly; it wouldn't be a stretch to become a remote-first organization, to split to smaller offices, to relocate entirely, or all of the above. Some WMF employees followed the WMF from St Petersburg, FL to San Francisco during the 2007 relocation. I expect that this would also happen to some extent if the WMF were to relocate and/or split to smaller distributed offices. San Francisco isn't just expensive for the WMF; it's expensive for employees as well, and some of them may find it beneficial to move to a less expensive area, especially as they start families. In addition to the insanely high cost of living in the San Francisco area, there are other reasons that make relocation a viable long-term solution. The main that come to mind are geological instability (the bay area /will/ be struck by major earthquakes in the medium term) and ecological conditions (i.e. the multi-year drought and its anticipated socio-ecological consequences). Planning for continuity means taking these concerns into account in any medium- and long-term strategy thinking. As Oliver mentioned, an East-coast office could make sense in this context. Technical staff is somewhat distributed around the globe, but in contrast the head (leadership) and backbone (finance, admin and HR) of the WMF is concentrated in the San Francisco office. In the current situation, it would take months or years to recover from a major disaster. Transitioning to several (2+) smaller, distributed offices would make the organization a lot more resilient, geographically and functionally. All this to say: it is possible, even probably desirable, for the WMF to consider relocating out of the Bay Area in the long term (in whole or in part), so entertaining the idea is a valid train of thought. -- Guillaume Paumier (volunteer capacity) https://guillaumepaumier.com This is a mailing list-only e-mail address. Direct messages may go unnoticed. ___ 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 engineering report, November 2014
Hi, The report covering Wikimedia engineering activities in November 2014 is now available: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/November -- Guillaume Paumier ___ 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] Quarterly reviews of high priority WMF initiatives
Hello again, Minutes and slides from the January 2015 quarterly review of the Foundation's Technical Operations team are now available at https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Tech_Ops/January_2015 -- Guillaume Paumier ___ 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] Quarterly reviews of high priority WMF initiatives
Hello, Minutes and slides from the January 2015 quarterly review of the Foundation's Finance Administration team are now available at https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Finance_%26_Administration/January_2015 -- Guillaume Paumier ___ 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] File metadata cleanup drive: An update and a request
Hi,
A quick follow-up: We now have good numbers for the amount of files
missing machine-readable metadata on Commons (spoiler: it's about
~500,000 files, meaning ~98% of files have machine-readable markers).
Below is a copy of the update I sent to commons-l:
https://lists.wikimedia.org/pipermail/commons-l/2014-December/007431.html
-- Forwarded message --
From: Guillaume Paumier gpaum...@wikimedia.org
Date: Thu, Dec 11, 2014 at 8:16 PM
Subject: File metadata cleanup drive: We now have numbers for Commons
To: Coordination of technology deployments across languages/projects
wikitech-ambassad...@lists.wikimedia.org, Wikimedia Commons
Discussion List common...@lists.wikimedia.org
Greetings,
As many of you are aware, we're currently in the process of
collectively adding machine-readable metadata to many files and
templates that don't have them, both on Commons and on all other
Wikimedia wikis with local uploads [1,2]. This makes it much easier to
see and re-use multimedia files consistently with best practices for
attribution across a variety of channels (offline, PDF exports, mobile
platforms, MediaViewer, WikiWand, etc.)
In October, I created a dashboard to track how many files were missing
the machine-readable markers on each wiki [3]. Unfortunately, due to
the size of Commons, I needed to find another way to count them there.
Yesterday, I finished to implement the script for Commons, and started
to run it. As of today, we have accurate numbers for the quantity of
files missing machine-readable metadata on Commons: ~533,000, out of
~24 million [4]. It may seem like a lot, but I personally think it's a
great testament to the dedication of the Commons community.
Now that we have numbers, we can work on going through those files and
fixing them. Many of them are missing the {{information}} template,
but many of those are also part of a batch: either they were uploaded
by the same user, or they were mass-uploaded by a bot. In either case,
this makes it easier to parse the information and add the
{{information}} template automatically with a bot, thus avoiding
painful manual work.
I invite you to take a look at the list of files at
https://tools.wmflabs.org/mrmetadata/commons/commons/index.html and
see if you can find such groups and patterns.
Once you identify a pattern, you're encouraged to add a section to the
Bot Requests page on Commons, so that a bot owner can fix them:
https://commons.wikimedia.org/wiki/Commons:Bots/Work_requests#Adding_the_Information_template_to_files_that_don.27t_have_it
I believe we can make a lot of progress rapidly if we dive into the
list of files and fix all the groups we can find. The list and
statistics will be updated daily so it'll be easy to see our progress.
Let me know if you'd like to help but are unsure how!
[1] https://meta.wikimedia.org/wiki/File_metadata_cleanup_drive
[2]
https://blog.wikimedia.org/2014/11/07/cleaning-up-file-metadata-for-humans-and-robots/
[3] https://tools.wmflabs.org/mrmetadata/
[4] https://tools.wmflabs.org/mrmetadata/commons/commons/index.html
--
Guillaume Paumier
https://meta.wikimedia.org/wiki/User:Guillaume_(WMF)
___
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 engineering report, October 2014
Hi, The report covering Wikimedia engineering activities in October 2014 is now available: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/October -- Guillaume Paumier ___ 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] File metadata cleanup drive: An update and a request
Greetings, As you may have seen in Tech News, on the Wikimedia blog or at the latest Metrics meeting, I'm currently leading a File metadata cleanup drive, whose goal is to to fix file pages and tweak templates across Wikimedia wikis, to ensure that multimedia files consistently contain machine-readable metadata [1,2]. This initiative is a critical step in improving reuse and following best practices for attribution in PDF prints, offline content like Kiwix and third party tools like WikiWand, among others. Some of you have already started adding the markers to information and licensing templates (Thank you!) and I'm going around wikis to do the same. We're making progress [3], but there's still a lot of work to do because we have so many wikis. I'd like to ask for your help in adding markers to the templates on your wiki, since you probably speak many languages that I have trouble deciphering. You're also more familiar with your wiki's templates, and a distributed effort will be more efficient than just a handful of us going around wikis :) There's a detailed guide in many languages if you're not sure how to proceed: https://meta.wikimedia.org/wiki/Special:MyLanguage/File_metadata_cleanup_drive/How_to_fix_metadata I also recommend that you reach out to other editors on your wiki, template authors, gadget maintainers, etc. since they may be able to help, but may not know about this effort. I'm also happy to help if you have questions. You can ask me off-list, on the tech ambassadors list, on IRC (I'm guillom in #wikimedia on freenode) or on my talk page on Meta. (Carrier pigeons are discouraged.) If you're helping, please consider adding yourself to the list of participants, so others can see which wikis are actively fixing files and templates: https://meta.wikimedia.org/wiki/File_metadata_cleanup_drive/Participants And if you're having difficulties, please do let others know on the talk page so we can try and find a solution, both for your benefit and for the benefit of others who might have the same problem: https://meta.wikimedia.org/wiki/Talk:File_metadata_cleanup_drive . I hope that you'll be able to help fix files and templates on your wiki and give a hand in this distributed effort. [1] https://meta.wikimedia.org/wiki/File_metadata_cleanup_drive [2] https://blog.wikimedia.org/2014/11/07/cleaning-up-file-metadata-for-humans-and-robots/ [3] https://tools.wmflabs.org/mrmetadata/historical_tallies.svg -- Guillaume Paumier https://meta.wikimedia.org/wiki/User:Guillaume_(WMF) ___ 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] Wikimedia engineering report, August 2014
programs https://www.mediawiki.org/wiki/Mentorship_programs* All Google Summer of Code https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014 and FOSS Outreach Program for Women https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8were evaluated by their mentors as PASSED, although many were still waiting for completion, code reviews and merges. We hosted a wrap-up IRC meeting https://meta.wikimedia.org/wiki/GSoC_%26_FOSS_OPW_wrap-up_meeting with the participation of all teams except one. We are still waiting for some final reports from the interns. In the meantime, you can check their weekly reports: - Tools for mass migration of legacy translated wiki content https://www.mediawiki.org/wiki/Extension:Translate/Mass_migration_tools/Project_updates - Wikidata annotation tool https://www.mediawiki.org/wiki/Wikidata_annotation_tool/updates - Email bounce handling to MediaWiki with VERP https://www.mediawiki.org/wiki/VERP/GSOC_Progress_Rerport - Google Books, Internet Archive, Commons upload cycle https://www.mediawiki.org/wiki/Google_Books,_Internet_Archive,_Commons_upload_cycle/Progress - UniversalLanguageSelector fonts for Chinese wikis https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector/Fonts_for_Chinese_wikis#Weekly_Report - MassMessage page input list improvements https://www.mediawiki.org/wiki/Extension:MassMessage/Page_input_list_improvements/Progress_reports - Book management in Wikibooks/Wikisource https://meta.wikimedia.org/wiki/Book_management_2014/Progress - Parsoid-based online-detection of broken wikitext https://www.mediawiki.org/wiki/User:Hardik95/GSoC_2014_Progress_Report - Usability improvements for the Translate extension https://www.mediawiki.org/wiki/User:Kunalgrover05/Progress_Report - A modern, scalable and attractive skin for MediaWiki https://www.mediawiki.org/wiki/User:Jack_Phoenix/GSoC_2014 - Automatic cross-language screenshots for user documentation https://www.mediawiki.org/wiki/Automatic_cross-language_screenshots/progress - Separating skins from core MediaWiki https://www.mediawiki.org/wiki/Separating_skins_from_core_MediaWiki/Progress - Chemical Markup support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In August, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillaume_(WMF) attended the Wikimania conference and the associated hackathon. He gave a talk https://wikimania2014.wikimedia.org/wiki/Submissions/Tech_news about Tech News https://meta.wikimedia.org/wiki/Tech/News (video available on YouTube https://www.youtube.com/watch?v=rqGDTNkVgLIlist=UURXe4cgJPTVHcDH6ZGwOT3A#t=9m15s) and created a poster summarizing the talk. He also continued to write and distribute Tech News every week, and started to contribute to the Structured data https://commons.wikimedia.org/wiki/Commons:Structured_data project. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We ran the Wikimania Hackathon https://wikimania2014.wikimedia.org/wiki/Hackathon in an unconference manner together with the Wikimania organizers. The event went well in a unique venue, and we are compiling a list of lessons learned to be applied in future events. Together with other former organizers of hackathons, we decided that the next Wikimedia Hackathon in Europe will be organized by Wikimedia France (details coming soon). Also at Wikimania, Quim Gil gave a talk about The Wikimedia Open Source Project and You https://wikimania2014.wikimedia.org/wiki/Submissions/The_Wikimedia_open_source_project_and_you (video https://www.youtube.com/watch?v=c5tJdQCnGWQlist
Re: [Wikimedia-l] Invitation to beta-test HHVM
Hello, On Sat, Sep 20, 2014 at 9:32 PM, Rand McRanderson therands...@gmail.com wrote: Here is one idea. A dashboard of top level Wikimedia projects with statuses, estimates, and a key to terms. Or does this exist? There is https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard It doesn't have everything you mentioned, but we can build on it and improve it. -- Guillaume Paumier ___ 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] Invitation to beta-test HHVM
Hi, On Fri, Sep 19, 2014 at 1:15 PM, MF-Warburg mfwarb...@googlemail.com wrote: Why should he give himself credit for your insufficient testing? Insufficient is in the eyes of the beholder :) Beta Features are experimental, and Ori's announcement clearly indicated that this particular feature was for intrepid beta testers. This means that the feature is still being tested, and that people who enable it should expect to find bugs, and should report them so they can be fixed before the feature is deployed more widely. This is precisely what happened in this case, so the testing process worked as expected. Developers can't find All The Bugs alone, which is why they need the help of volunteer testers. -- Guillaume Paumier ___ 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] Wikimedia engineering report, July 2014
/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* https://commons.wikimedia.org/wiki/File:Flesch_reading_ease_chart_for_Tech_News.svg Chart showing historical Flesch reading ease https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests data for Tech News, a measure of the newsletter’s readability https://meta.wikimedia.org/wiki/Tech/News/Readability. Higher scores indicate material that is easier to read. A score of 60–70 corresponds to content easily understood by 13- to 15-year-old students. Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom collaborated with authors of the Education newsletter https://outreach.wikimedia.org/wiki/Education/Newsto set it up https://outreach.wikimedia.org/wiki/Education/Newsletter/Newsroom/Multilingual_message for multilingual delivery, using a script https://meta.wikimedia.org/wiki/Module:Assemble_multilingual_message similar to the one used for Tech News https://meta.wikimedia.org/wiki/Tech/News. He also wrote adetailed how-to https://meta.wikimedia.org/wiki/Newsletters/Translation to accompany the script for people who want to send a multilingual message across wikis. In preparation for the Wikimania session https://wikimania2014.wikimedia.org/wiki/Submissions/Tech_news about Tech News, he updated the readability https://meta.wikimedia.org/wiki/Tech/News/Readability andsubscribers https://meta.wikimedia.org/wiki/Tech/News/Subscribers metrics. He also continued to provide ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, and to prepare and distribute Tech News every week. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We focused on the preparation of the Wikimania Hackathon https://wikimania2014.wikimedia.org/wiki/Hackathon, encouraging all registered participants to propose topics and sign up to interesting sessions. We also organized a QA session https://plus.google.com/events/c0fgci542f8cn58o606gng6avio with potential organizers of the Wikimedia Hackathon 2015. We organized two Tech Talks: *Hadoop and Beyond. An overview of Analytics infrastructure* https://plus.google.com/u/0/b/103470172168784626509/events/c53ho5esd0luccd09a1c30rlrmg and*HHVM in production: what that means for Wikimedia developers* https://plus.google.com/events/cp5mjf6jrihevtdje8lmu5hvm1k. More activities hosted in July can be found at Project:Calendar/2014/07 https://www.mediawiki.org/wiki/Project:Calendar/2014/07. *Architecture and Requests for comment process https://www.mediawiki.org/wiki/Architecture_process* Developers finished the security architecture guidelines https://www.mediawiki.org/wiki/Security_for_developers/Architecture, and discussed several requests for comment https://www.mediawiki.org/wiki/Requests_for_comment in online architecture meetings https://www.mediawiki.org/wiki/Architecture_meetings: - 2014-07-10 — Frontend standardization discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-10 focusing onRequests for comment/Redo skin framework https://www.mediawiki.org/wiki/Requests_for_comment/Redo_skin_framework ; - 2014-07-16 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-16 focusing on Requests for comment/Vertical writing support https://www.mediawiki.org/wiki/Requests_for_comment/Vertical_writing_support ; - 2014-07-23 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-23 focusing on Requests for comment/Composer managed libraries for use on WMF cluster https://www.mediawiki.org/wiki/Requests_for_comment/Composer_managed_libraries_for_use_on_WMF_cluster, in which the architecture committee approved the RfC; - 2014-07-30 — RfC discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-30 focusing on Requests for comment/CentralNotice Caching Overhaul – Frontend Proxy https://www.mediawiki.org/wiki/Requests_for_comment
Re: [Wikimedia-l] Options for the German Wikipedia
Hi, On Tue, Aug 12, 2014 at 8:44 AM, Dan Garry dga...@wikimedia.org wrote: On 12 August 2014 02:39, svetlana svetl...@fastmail.com.au wrote: There needs to be a central place, like the Wikimedia blog, but dedicated to tech things - actively announcing everything WM ENGINEERING are doing, both in products and in core. There is. It's called the monthly report. See here for July's for example: *https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/July Just a small note: The July report is still being drafted; the latest published report is the one for June: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Report/2014/June . My apologies for forgetting to add the draft template when I created the page. To see the latest status update of all current activities* at any given time, see the Wikimedia engineering status dashboard: https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard [*] Except for those documented on other wikis, like the work of the Operations team. -- Guillaume Paumier ___ 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] Wikimedia engineering report, June 2014
support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In addition to ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom focused on information architecture of Wikimedia engineering activities. This notably involved reorganizing the Wikimedia Engineering https://www.mediawiki.org/wiki/Wikimedia_Engineering portal (now linked from mediawiki.org’s sidebar) and creating a status dashboard https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard that lists the status of all current activities hosted on mediawiki.org. The portal is now also cross-linked with the other main tech spaces (like Tech https://meta.wikimedia.org/wiki/Tech and Tech News https://meta.wikimedia.org/wiki/Tech/News) and team hubs. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Volunteers and staff are beginning to add or express interest in topics for the 2014 Wikimania Hackathon in London. The WMUK team is working hard to finalize venue logistics so that we can schedule talks and sessions in specific rooms. Everything is on track for a successful (and very large!) Hackathon. Tech Talks held in June:*How, What, Why of WikiFont* https://plus.google.com/events/chpgv8usjd6dn38on07njjk28hg on June 12 and *A Few Python Tips* https://www.mediawiki.org/wiki/Meetings/2014-06-19 on June 19. A new process has been set up forvolunteers needing to sign an NDA https://wikitech.wikimedia.org/wiki/Volunteer_NDA in order to be granted special permissions in Wikimedia servers. On a similar note, we have started a project to implement a Trusted User Tool http://fab.wmflabs.org/project/view/40/ in Phabricator, in order to register editors of Wikimedia projects that have been granted special permissions after signing a community agreement. *Architecture and Requests for comment process https://www.mediawiki.org/wiki/Architecture_process* Developers had several meetings https://www.mediawiki.org/wiki/Architecture_meetings on IRC about architectural issues or Requests for comment https://www.mediawiki.org/wiki/Requests_for_comment: - 2014-06-02 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-02 of Requests for comment/Grid system https://www.mediawiki.org/wiki/Requests_for_comment/Grid_system; - 2014-06-11 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-11 of several RfCs (lightning round); - 2014-06-13 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/Security_guidelines_discussion_2014-06-13 of security guidelines draft https://www.mediawiki.org/wiki/Security_for_developers/Architecture; - 2014-06-20 — Discussion https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-06-20 of revamping MediaWiki’s skin systems: Trevor Parscal’s “Redo skin framework” https://www.mediawiki.org/wiki/Requests_for_comment/Redo_skin_framework and Bartosz Dziewoński’s “Separating skins from core MediaWiki” work https://bugzilla.wikimedia.org/show_bug.cgi?id=65748; - 2014-06-25 — Discussion http://lists.wikimedia.org/pipermail/wikitech-l/2014-June/077227.html of front-end and UX standardization https://www.mediawiki.org/wiki/UX_standardization. Analytics https://www.mediawiki.org/wiki/Analytics *Wikimetrics https://www.mediawiki.org/wiki/Analytics/Wikimetrics* To support Editor Engagement Vital Signs, the team has implemented a new metric: Newly Registered User. There is also a new backup system to preserve user’s
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, May 2014
,_Commons_upload_cycle/Progress - UniversalLanguageSelector fonts for Chinese wikis https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector/Fonts_for_Chinese_wikis#Weekly_Report - MassMessage page input list improvements https://www.mediawiki.org/wiki/Extension:MassMessage/Page_input_list_improvements/Progress_reports - Book management in Wikibooks/Wikisource https://meta.wikimedia.org/wiki/Book_management_2014/Progress - Parsoid-based online-detection of broken wikitext https://www.mediawiki.org/wiki/User:Hardik95/GSoC_2014_Progress_Report - Usability improvements for the Translate extension https://www.mediawiki.org/wiki/User:Kunalgrover05/Progress_Report - A modern, scalable and attractive skin for MediaWiki https://www.mediawiki.org/wiki/User:Jack_Phoenix/GSoC_2014 - Automatic cross-language screenshots for user documentation https://www.mediawiki.org/wiki/Automatic_cross-language_screenshots/progress - Separating skins from core MediaWiki https://www.mediawiki.org/wiki/Separating_skins_from_core_MediaWiki/Progress - Chemical Markup support for Wikimedia Commons https://www.mediawiki.org/wiki/Chemical_Markup_support_for_Wikimedia_Commons/Internship_Report - Improving URL citations on Wikimedia https://www.mediawiki.org/wiki/User:Mvolz/Weekly_Reports - Historical OpenStreetMap https://www.mediawiki.org/wiki/User:JaimeLyn/Weekly_Reports - Welcoming new contributors to Wikimedia Labs and Tool Labs https://www.mediawiki.org/wiki/Welcome_to_labs/Progress_Reports - Evaluating, documenting, and improving MediaWiki web API client libraries https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports - Feed the Gnomes – Wikidata Outreach https://www.mediawiki.org/wiki/User:Thepwnco/OPW_Reporting - Template Matching for RDFIO https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports - Switching Semantic Forms Autocompletion to Select2 https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Select2_for_autocompletion/Progress_Report - Catalogue for Mediawiki Extensions https://www.mediawiki.org/wiki/User:Adi.iiita/Gsoc2014/Report#Weekly_Report - Generic, efficient localisation update service https://www.mediawiki.org/wiki/Extension:LocalisationUpdate/LUv2/Updates . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In addition to ongoing communications support https://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activity for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom mostly focused on improvements to the system of scripts and templates https://www.mediawiki.org/wiki/Category:Wikimedia_engineering_templates used to document Wikimedia engineering activities on mediawiki.org. Active and inactive projects can now be queried separately, which means that the list of projects that appears in the drop-down of the status helper gadget https://www.mediawiki.org/wiki/MediaWiki:Gadget-WmfProjectStatusHelper.js is much shorter, now only listing active projects. Guillaume also wrote a dedicated Lua module https://www.mediawiki.org/wiki/Module:Wikimedia_engineering to manipulate engineering activities automatically, in particular for theWikimedia Engineering https://www.mediawiki.org/wiki/Wikimedia_Engineering portal. It is now possible to query activities from a given team, and display them on any page in various formats. Using the module, the ever-outdated list of “current” activities on the portal was replaced by an automatically-generated list based on projects listed on team hubs. The module also allows to feature a random engineering activity on the portal. Other additions to the portal include the latest issue of Tech News https://meta.wikimedia.org/wiki/Tech/News(transcluded and automatically updated every week), as well as the first paragraph of the latest monthly engineering report (manually updated for now). Future improvements of the portal are expected to be mostly aesthetic. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* The Wikimedia Hackathon in Zürich https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014 was a success according to ad hoc feedback from the participants. A deeper review is expected to be published in July, after compiling the results of the survey. The main merit goes to Wikimedia CH for an efficient, warm, and flexible organization. We also announced a process to request the organization of Hackathons https://www.mediawiki.org/wiki/Hackathons. We had an intense calendar of events in May https://www.mediawiki.org/wiki/Project:Calendar/2014/05, including a Tech Talk about Elasticsearch https://plus.google.com/b/103470172168784626509/events/cokipb2senmmvkvdjif7aq55kac and a meetup in San Francisco on *Making Wikipedia Fast* https://plus.google.com/events
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, April 2014
and future Wikimedia engineering efforts. -- *This article was written collaboratively by Wikimedia engineers and managers. See revision history https://www.mediawiki.org/w/index.php?title=Wikimedia_engineering_report/2014/Aprilaction=history and associated status pages. A wiki version https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2014/April is also available.* -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ 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
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, March 2014
community members for the gradual release of Media Viewerhttps://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Release_Plan, to be enabled by default on a number of pilot sites next month, then deployed widely to all wikis a few weeks later. For more updates about our multimedia work, we invite you to join the multimedia mailing listhttps://lists.wikimedia.org/mailman/listinfo/multimedia . Engineering Community Teamhttps://www.mediawiki.org/wiki/Engineering_Community_Team *Bug management https://www.mediawiki.org/wiki/Bug_management* Beside working on the Project Management Tools Reviewhttps://www.mediawiki.org/wiki/Project_management_tools/Review#Status, Andre Klapper retriaged many older tickets with high priority set for 2years, older PATCH_TO_REVIEW tickets and older critical tickets and investigated moving the Bugzilla instance on Wikimedia Labs to the Ashburn data center (easier to set up from scratchhttps://bugzilla.wikimedia.org/show_bug.cgi?id=62658#c6). Andre addedhttps://www.mediawiki.org/w/index.php?title=Annoying_little_bugsdiff=922892oldid=915158project-specific sections and Bugzilla queries to Annoying little bugshttps://www.mediawiki.org/wiki/Annoying_little_bugs to help newcomers finding an area of interest for contributing, and blogged about the 4.4 upgradehttps://blog.wikimedia.org/2014/03/28/wikimedias-road-to-bugzilla-4-4/ (which took place in February) and moving Bugzilla to a new server. In Bugzilla’s tickets, all remaining Cortado tickets were closedhttps://bugzilla.wikimedia.org/show_bug.cgi?id=54063#c4 and new Versions for “Wikipedia App” producthttps://bugzilla.wikimedia.org/show_bug.cgi?id=62660 set up. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* Guillaume Paumier and Andre Klapper reached to the teampracticeshttp://lists.wikimedia.org/pipermail/teampractices/2014-March/000270.html and wikitech-lhttp://lists.wikimedia.org/pipermail/wikitech-l/2014-March/074896.html mailing lists in order to shorten the list of optionshttps://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options that can come out of this review process. They also hosted a lively IRC office hourhttps://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-28-17.04.html to give an overview of the current situation, answer questions and discuss the first version of the related RFChttps://www.mediawiki.org/wiki/Requests_for_comment/Project_management_tools_review . *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* The six ongoing FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7 were completed successfully, setting a new benchmarkhttp://lists.wikimedia.org/pipermail/wikitech-l/2014-March/075146.html for success in our outreach programs. Check the results: - Niharika’s compact language links is now a Beta featurehttps://www.mediawiki.org/wiki/Universal_Language_Selector/Design/Interlanguage_links - Anu’s upload wizard with OSM supporthttp://uploadwizard-osm.wmflabs.org/wiki/Special:UploadWizard - Diwanshi’s Wikipedia API courses in Codecademy 1http://www.codecademy.com/courses/web-beginner-en-vj9nh/0/1 and 2 http://www.codecademy.com/courses/web-beginner-en-yd3lp/0/1 - Brena’s prototype of mediawiki.org’s redesigned homepagehttps://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview - Be’s clean up of Parsoid’s round-trip testing UI is mergedhttps://gerrit.wikimedia.org/r/#/q/owner:bebirchall%2540gmail.com,n,z - Maria’s clean up of Parsoid’s tracing/debugging/logging is mergedhttps://gerrit.wikimedia.org/r/#/q/owner:maria.pacana%2540gmail.com,n,z We received 43 Google Summer of Codehttps://www.mediawiki.org/wiki/Google_Summer_of_Code_2014 proposals from 42 candidates, and 18 FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8 proposals from 18 candidates. Dozens of mentors are pushing the selection processhttps://www.mediawiki.org/wiki/Mentorship_programs/Selection_process that will conclude on April 21 with the announcement of selected participants. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In addition to ongoing communications support for the engineering staff, and contributing to the technical newsletterhttps://meta.wikimedia.org/wiki/Tech/News , Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom edited and published a series of essayshttps://blog.wikimedia.org/2014/03/25/seeing-through-the-eyes-of-new-technical-contributors/ on the Wikimedia Tech blog written by Google Code-in students, who shared their impressions, frustrations and surprises as they discovered the Wikimedia and MediaWiki technical community. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* The bulk of work to create community metricshttps://www.mediawiki.org/wiki/Community_metrics around five Key
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, February 2014
, which fixed numerous bugshttps://bugzilla.wikimedia.org/buglist.cgi?bug_id=47013,42850,32504,49250,56183,53199,60727,28796. Daniel Zahn puppetized Bugzillahttps://bugzilla.wikimedia.org/show_bug.cgi?id=51036and (together with Sean Pringle) moved Wikimedia Bugzilla to a new server https://wikitech.wikimedia.org/wiki/Zirconium. Bugzilla now displays useful querieshttps://bugzilla.wikimedia.org/show_bug.cgi?id=22170and personal information on its front page. Its table of duplicates https://bugzilla.wikimedia.org/duplicates.cgi now displays bug resolutions https://bugzilla.wikimedia.org/show_bug.cgi?id=58749 (to identify popular WONTFIXed requests) and prioritieshttps://bugzilla.wikimedia.org/show_bug.cgi?id=56253as columns. The Bugzilla etiquette https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquettewas finalized (read the announcementhttp://lists.wikimedia.org/pipermail/wikitech-l/2014-February/074282.html). In Bugzilla’s taxonomy, the MobileFrontend componentshttps://bugzilla.wikimedia.org/show_bug.cgi?id=61280were restructured and the Windows and MacOS entries in Bugzilla’s “OS” dropdown were reordered to list recent versions first. Andre Klapper refreshed the Annoying little bugshttps://www.mediawiki.org/wiki/Annoying_little_bugspage by adding a sectionhttps://www.mediawiki.org/w/index.php?title=Annoying_little_bugsdiff=909298oldid=909297covering common questions and issues of new contributors, based on Google Code-In https://www.mediawiki.org/wiki/Google_Code-In experience. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* After summarizing community input into consolidated requirementshttps://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements, Andre Klapper and Guillaume Paumier listed the different optionshttps://www.mediawiki.org/wiki/Project_management_tools/Review/Optionsmentioned during the consultation process. Those go from keeping the status quo to changing a single tool, to consolidating most tools into one. They also continued to research the main candidates by reading articles and testing demo sites. Once the list of options has been shortened collaboratively, the community RFC will start. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* The six ongoing FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7projects all made good progress, and are headed to completion by the end of the program on March 10. For more details, check their dedicated reports: - Compacting interlanguage linkshttps://www.mediawiki.org/wiki/User:Niharika/Project_Progress_Report#February_2014 - MediaWiki Homepage Redesignhttps://www.mediawiki.org/wiki/User:Monteirobrena/MediaWiki_Homepage_Redesign/Monthly_Reports#February - Complete the MediaWiki API development course on Codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW_February_Report - Clean up Parsoid round-trip testing UIhttps://www.mediawiki.org/wiki/User:5xbe/OPW_Monthly_Progress_Reports#February - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/OPW_Progress_Report#February_2014 - UploadWizard: OSM Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/OPW_Internship_Report#February Getting Facebook Open Academyhttps://www.mediawiki.org/wiki/Facebook_Open_Academyprojects up to speed is becoming even more complex than expected, but we are getting there slowly. All students and mentors met at the kick-off hackathon at Facebook headquarters on February 7−9 (see Marc-André Pelletier’s reporthttps://blog.wikimedia.org/2014/02/25/facebooks-open-academy-hackathon-was-a-success/ ). Wikimedia applied to Google Summer of Code 2014https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014and we were accepted. We also confirmed our participation in FOSS Outreach Program for Women round 8https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8. We are organizing both programs simultaneously under a common umbrella, as we did last year with great success. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In February, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillomcontinued to provide ongoing communications support for the engineering staff, and contributed to writing, simplifying, publishing and distributing the weekly technical newsletter https://meta.wikimedia.org/wiki/Tech/News. He also edited essays from Google Code-inhttps://www.mediawiki.org/wiki/Google_Code-instudents for publication on the Wikimedia blog. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Wikimedia completed its more ambitious participation in FOSDEMhttps://www.mediawiki.org/wiki/Events/FOSDEM(Brussels) with mild success. The Wikis devroom (co-organized with the XWiki and Tiki projects), the Wikimedia stand, and *The Wikipedia Stack*main track session achieved
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, January 2014
on this!”https://bugzilla.wikimedia.org/show_bug.cgi?id=57648to be more descriptive. The link to the guided bug entry form at the top of the standard bug entry form now sets the already chosen product directlyhttps://bugzilla.wikimedia.org/show_bug.cgi?id=59886, saving you two clicks when you switch to the guided form. Work continued on preparing the Bugzilla 4.4 upgrade: Andre Klapper’s patches for porting custom changes from 4.2 to 4.4 were deployed on the Bugzilla test instance on Zirconium and tested, and Daniel Zahn fixed a problem with Bugzilla’s collectstats.pl https://bugzilla.wikimedia.org/show_bug.cgi?id=29203, so the 4.4 upgrade and server move will take place in February. Bug management documentation related, Andre added a “Situation specific information” section to the Triage guidehttps://www.mediawiki.org/wiki/Bug_management/How_to_triagedocumentation about purging and profiling. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* Andre Klapper reached out to the teampracticeshttps://lists.wikimedia.org/mailman/listinfo/teampracticesmailing list as well as individual stakeholders, asking users to share their workflow and needshttps://www.mediawiki.org/wiki/Talk:Project_management_tools/Reviewregarding project management and tracking tools. Guillaume Paumier summarized all that content into consolidated requirementshttps://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements; those are now in the process of being compared to features offered by available tools, in order to assemble a shortlist of candidates for community discussion. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* [image: Google Code-in 2013, the Wikimedia debut.pdf]https://commons.wikimedia.org/wiki/File:Google_Code-in_2013,_the_Wikimedia_debut.pdf https://commons.wikimedia.org/wiki/File:Google_Code-in_2013,_the_Wikimedia_debut.pdf Wikimedia’s first participation in the Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-Inprogram ended up with great success: 273 tasks completed by 46 students with the help of about 30 mentors. Theo Patt and Mateusz Maćkowski were selected winners for Wikimediahttp://google-opensource.blogspot.com/2014/01/google-code-in-2013-drumroll-please.html, and we sent a special mention to Mayank Madan. Round 7 of the FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7started and all projects are on track so far: - Compacting interlanguage linkshttps://www.mediawiki.org/wiki/User:Niharika/Project_Progress_Report#January_2014 - MediaWiki Homepage Redesignhttps://www.mediawiki.org/wiki/User:Monteirobrena/MediaWiki_Homepage_Redesign/Monthly_Reports#January - Complete the MediaWiki API development course on Codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW_January_Report - Clean up Parsoid round-trip testing UIhttps://www.mediawiki.org/wiki/User:5xbe/OPW_Monthly_Progress_Reports#January - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/OPW_Progress_Report#January_2014 - UploadWizard: OSM Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/OPW_Internship_Report#January Facebook Open Academy https://www.mediawiki.org/wiki/Facebook_Open_Academy‘s warm-up period saw a slow progress in the beginning of the projects. At the end it seemed that everybody was waiting for the official start at the kick-off in Facebook headquarters on February 7−9. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In January, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillomwrapped up work on mentoring Google Code-in https://www.mediawiki.org/wiki/Google_Code-in students and continued to provide ongoing communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityfor the engineering staff. He contributed to writing, simplifying, publishing and distributing the weekly technical newsletterhttps://meta.wikimedia.org/wiki/Tech/News, and published an in-depth articlehttps://blog.wikimedia.org/2014/01/07/tech-news-fighting-technical-information-overload-for-wikimedians/explaining the process by which the newsletter is put together every week. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* We helped organizing the Architecture Summit 2014https://www.mediawiki.org/wiki/Architecture_Summit_2014in San Francisco (January 23−24) and we got everything ready for FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM in Brussels (February 1−2). We continued working with the tech community metricshttps://www.mediawiki.org/wiki/Community_metricsaround two key performance indicators: who contributes codehttp://korma.wmflabs.org/browser/who_contributes_code.html, and the Gerrit review queuehttp://korma.wmflabs.org/browser/gerrit_review_queue.html . Analytics https://www.mediawiki.org/wiki/Analytics
[Wikimedia-l] [Wikimedia Announcements] Fwd: Wikimedia engineering report, December 2013
Bugzilla puppet code into a puppet modulehttps://gerrit.wikimedia.org/r/#/q/project:operations/puppet+topic:bugzilla+owner:dzahn+status:merged,n,zand automatically generating documentation on doc.wikimedia.orghttps://doc.wikimedia.org/puppet/classes/bugzilla/bugzilla.html. As part of this preparation, Daniel and Andre also eliminated nearly all Perl CPAN modules (in Bugzilla’s /lib subfolder) on the new server by using default distribution packages instead. Furthermore, Andre worked on a preliminary patch https://bugzilla.wikimedia.org/show_bug.cgi?id=22170#c27 to display some common queries on the Bugzilla front page. *Project management tools review https://www.mediawiki.org/wiki/Project_management_tools/Review* Andre Klapper and Guillaume Paumier kicked off an evaluation of Wikimedia’s project management toolshttps://www.mediawiki.org/wiki/Project_management_tools/Review. Guillaume prepared a consultation pagehttps://www.mediawiki.org/wiki/Talk:Project_management_tools/Reviewwith topics for stakeholders and improved it together with Andre. It will initially be sent to the teampracticeshttps://lists.wikimedia.org/mailman/listinfo/teampracticesmailing list and individual stakeholders. To facilitate getting input, talking to individual stakeholders via Hangouts and holding an IRC discussion https://meta.wikimedia.org/wiki/IRC_office_hours are also considered. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* Wikimedia’s first participation in the Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-Inprogram required a lot of dedication from the ECT members, and about a dozen of mentors and other contributors helping creating and reviewing tasks. Students completed about 200 tasks. The GCI inertia and the lessons learned will help us organize a better gateway for new contributors, which was a main reason for us to join this program. We also believe that the experience acquired will help us make future editions as successful with less work. Round 7 of the FOSS Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7started and all projects and on track so far: - Compacting interlanguage linkshttps://www.mediawiki.org/wiki/User:Niharika/Project_Progress_Report#December_2013 . - MediaWiki Homepage Redesignhttps://www.mediawiki.org/wiki/User:Monteirobrena/MediaWiki_Homepage_Redesign/Monthly_Reports#December . - Complete mediawiki API development course on codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW_Internship_Report#December_2013 . - Clean up Parsoid round-trip testing UIhttps://www.mediawiki.org/wiki/User:5xbe/OPW_Monthly_Progress_Reports#December_10th_-_31st_.28three_weeks.29 . - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/OPW_Progress_Report#December_2013 . - UploadWizard :OSM Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/OPW_Internship_Report#December We joined Facebook Open Academyhttps://www.mediawiki.org/wiki/Facebook_Open_Academyalmost at the last minute thanks to a reminder from developer Tyler Romeo. Six projects were accepted, which will be developed by teams of university students during the first half of 2014: - Distributed cron replacementhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Distributed_cron_replacement— Coren https://www.mediawiki.org/wiki/User:Coren - Cassandra backend for distributed round-trip test serverhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Cassandra_backend_for_distributed_round-trip_test_server— Gabriel Wicke https://www.mediawiki.org/wiki/User:GWicke, Marc Ordinas i Llopishttps://www.mediawiki.org/wiki/User:Marcoil - Flow Right-To-Left language supporthttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Flow_Right-To-Left_language_support— S Page (WMF) https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and Werdna https://www.mediawiki.org/wiki/User:Werdna - Flow Edit Filter integrationhttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Flow_Edit_Filter_integration— S Page (WMF) https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29 and Werdna https://www.mediawiki.org/wiki/User:Werdna - OpenBadges https://www.mediawiki.org/wiki/OpenBadges and Personahttps://www.mediawiki.org/wiki/Extension:Personasupport for MediaWiki — Parent5446 https://www.mediawiki.org/wiki/User:Parent5446 and Qgilhttps://www.mediawiki.org/wiki/User:Qgil *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In December, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom‘s primary focus was on creating and assigning tasks for the Google Code-inhttps://www.mediawiki.org/wiki/Google_Code-inprogram, mentoring students and reviewing their work. They worked on writing discovery reportshttps://www.mediawiki.org/wiki/Category:Discovery_reports, adding TemplateData https
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, November 2013
in Google Code-In https://www.mediawiki.org/wiki/Google_Code-in. This includes supporting mentors and students by writing documentation and importing tasks. Code-related, Andre cleaned up Wikimedia Bugzilla's custom CSS by removing 16 CSS fileshttps://bugzilla.wikimedia.org/show_bug.cgi?id=54823with 6 lefthttps://git.wikimedia.org/tree/wikimedia%2Fbugzilla%2Fmodifications.git/HEAD/skins%2Fcontrib%2FWikimediato stay, prepared and tested patches for upgrading Wikimedia Bugzilla https://bugzilla.wikimedia.org/show_bug.cgi?id=49597#c5from version 4.2 to 4.4, updated the Greasemonkey triagescriptshttps://git.wikimedia.org/log/wikimedia%2Fbugzilla%2Ftriagescripts(e.g. stock answers to ping assignees), and sync'ed the WeeklyReport Bugzilla extension code https://gerrit.wikimedia.org/r/#/c/96479/ with upstream. WMF's Operations team installed new SSL certificateshttps://rt.wikimedia.org/Ticket/Display.html?id=5011for bugzilla.wikimedia.org. The shellpolicy keyword in Bugzilla was renamedhttps://bugzilla.wikimedia.org/show_bug.cgi?id=49494to community-consensus-needed and the wikidata keyword was removed https://bugzilla.wikimedia.org/show_bug.cgi?id=56417. Furthermore, Andre created a draft for a Bugzilla etiquettehttps://www.mediawiki.org/wiki/Bug_management/Bugzilla_etiquette . *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We started successfully Wikimedia's first participation in Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In. Six candidates were selected as new interns at the FOSS Outreach Program for Women - Round 7https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7: - Anu G Enchackal https://www.mediawiki.org/wiki/User:Inchikutty - UploadWizard:OSM Map Embeddinghttps://www.mediawiki.org/wiki/User:Inchikutty/UploadWizard_OSM_Map_Embedding(mentored by Gergő Tisza https://www.mediawiki.org/wiki/User:Tgr) - Diwanshi Pandey https://www.mediawiki.org/wiki/User:Diwanshipandey - Complete the MediaWiki development course at Codecademyhttps://www.mediawiki.org/wiki/User:Diwanshipandey/OPW(Yuri Astrakhan https://www.mediawiki.org/wiki/User:Yurik) - Brena Monteiro https://www.mediawiki.org/wiki/User:Monteirobrena - mediawiki.org homepage redesign https://www.mediawiki.org/wiki/User:Monteirobrena/OPW(Heather Walls https://www.mediawiki.org/wiki/User:Heatherawalls and Quim Gilhttps://www.mediawiki.org/wiki/User:Qgil) - Be Birchall https://www.mediawiki.org/wiki/User:5xbe - Clean up Parsoid round-trip testing UI, including using a templating systemhttps://www.mediawiki.org/wiki/User:5xbe/Proposal(Marc Ordinas https://www.mediawiki.org/wiki/User:Marcoil and Subramanya Sastry https://www.mediawiki.org/wiki/User:Ssastry) - Maria Pacana https://www.mediawiki.org/wiki/User:Mariapacana - Clean up tracing/debugging/logging inside Parsoidhttps://www.mediawiki.org/wiki/User:Mariapacana/Application(Subramanya Sastry https://www.mediawiki.org/wiki/User:Ssastry and Arlo Breaulthttps://www.mediawiki.org/wiki/User:Arlolra) - Niharika Kohli https://www.mediawiki.org/wiki/User:Niharika - Compact interlanguage links as a beta featurehttps://www.mediawiki.org/wiki/User:Niharika/Compacted_Interlanguage_Links_as_a_beta_feature(Sucheta Ghoshal and Pau Giner) We also confirmed the participation of Wikimedia in the Facebook Open Academy https://www.mediawiki.org/wiki/Facebook_Open_Academy program. *Technical communications https://www.mediawiki.org/wiki/Technical_communications* In November, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom's primary focus was on preparing for the Google Code-inhttps://www.mediawiki.org/wiki/Google_Code-inprogram, and mentoring students once the program started. In 2 weeks, 18 studentshttps://www.mediawiki.org/wiki/Technical_communications/Code-in/2013worked on writing discovery reports https://www.mediawiki.org/wiki/Category:Discovery_reports (candid essays from the perspective of newcomers to the Wikimedia technical community); among them, seven completed their task successfully. Guillaume also assembled and published the weekly technical newsletterhttps://meta.wikimedia.org/wiki/Tech/Newsand provided ongoing communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityfor the engineering staff. *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Erik Moeller's talk The Wikipedia stack was accepted for the main track session at FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM. The call for proposals for the Wikis devroom at FOSDEMhttps://www.mediawiki.org/wiki/Events/FOSDEMwas extended until December 15. Wikimedia applied for a stand. A Request for Proposals for a technical writer contractorhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-November/073077.htmlwas also sent. Last, we helped establishing a routine around Architecture meetings https://www.mediawiki.org/wiki/Architecture_meetings
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, October 2013
for VisualEditor, Flow, gadgets, Language features, MobileFrontend, and more. Engineering community team *Bug management https://www.mediawiki.org/wiki/Bug_management* Bugzilla now offers a new guided bug entry formhttps://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimediacomponent=Bugzillaformat=guidedwhich will make creating good bug reports easier for newcomers. Bugzilla now also displays metadata changeshttps://bugzilla.wikimedia.org/show_bug.cgi?id=47256#c11of a bug report inline for all logged-in users, so they can see in the comments who changed a value of a field (without clicking on History). Daniel Zahn upgraded Wikimedia Bugzilla to latest version 4.2.7http://www.bugzilla.org/releases/4.2.7/release-notes.html. Legoktm mass-imported about 400 Pywikibot ticketshttps://bugzilla.wikimedia.org/show_bug.cgi?id=52692from Sourceforge to Bugzilla. On a related note, Amir ran a PyWikibot Bug Triage https://www.mediawiki.org/wiki/Bug_management/Triage/20131024resulting in nearly 100 tickets receiving updates. Furthermore, Andre Klapper investigated Wikimedia Bugzilla's customizations in CSS and code in order to clean up and sync with the upstream code base, to simplify current maintenance and also make a potential future upgrade of Wikimedia Bugzilla from version 4.2 to 4.4 easier. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We presented the summary of GSoC 2013 and FOSS OPW round 6https://commons.wikimedia.org/wiki/File:GSoC_2013_%26_FOSS_OPW_Round_6.pdfat the Wikimedia Metrics Meeting. The document about lessons learned in mentorship programshttps://www.mediawiki.org/wiki/Mentorship_programs/Lessons_learnedwas updated. Wikimedia applied to Google Code-In https://www.mediawiki.org/wiki/Google_Code-In and was successfully accepted on November 1. We opened the call for candidates for FOSS Outreach Program for Women - Round 7https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women . *Technical communications https://www.mediawiki.org/wiki/Technical_communications* Besides ongoing communications support for the engineering staff, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom published three issues of the Tech newsletter https://meta.wikimedia.org/wiki/Tech/Newsin October, and started a list of open taskshttps://www.mediawiki.org/wiki/Technical_communications/What_you_can_dorelated to technical communications, available for anyone to work on, primarily in preparation for Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In . *Volunteer coordination and outreach https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach* Our proposal for a Wiki devroom at FOSDEMhttps://www.mediawiki.org/wiki/Events/FOSDEMwas accepted and we launched the Call for participationhttps://lists.fosdem.org/pipermail/wikis-devroom/2013-October/00.html. On tech community metrics https://www.mediawiki.org/wiki/Community_metrics, we obtained first results of the *Community metrics: Who contributes code*https://www.mediawiki.org/wiki/Community_metrics#Who_contributes_codekey progress indicator. We facilitated the MediaWiki 1.22 Release Plan tech talkhttps://www.mediawiki.org/wiki/Meetings/2013-10-09and the Flow UX Workshop http://www.meetup.com/wikimedia-tech/events/141845782/meet-up. The list of participants of the Architecture Summit 2014 https://www.mediawiki.org/wiki/Architecture_Summit_2014 was published. We also experimented with a monthly cycle of Engineering Community Team meetingshttps://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings . Multimedia *Multimedia https://www.mediawiki.org/wiki/Multimedia* In October, we continued to expand our multimedia teamhttps://www.mediawiki.org/wiki/Multimediaand hired Gergő Tisza https://meta.wikimedia.org/wiki/User:Tgr as software engineer. Mark Holmquist worked with Gergő to develop a first beta version of the Media Viewer https://www.mediawiki.org/wiki/Multimedia/About_Media_Viewer, which displays images in larger size or full screen; this work was based on designs by Pau Giner, May Tee-Galloway and Jared Zimmerman. We also completed development on the Beta Featureshttps://www.mediawiki.org/wiki/About_Beta_Featuresprogram, which invites users to try out new features before they are released for everyone. A first version of both products is now ready for testing by logged in users on MediaWiki.orghttps://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures(to try new features, click on the small 'Beta' link next to your 'Preferences'). We plan to release the Beta Features program in coming days to Wikimedia Commons and Meta-Wiki, then to all wikis worldwidehttps://www.mediawiki.org/wiki/Beta_Features/Release_Planat the end of November. Fabrice Florin managed the development of both projects, and updated our multimedia plans to prepare for roundtable discussions https://meta.wikimedia.org/wiki/Roundtables with community members next month. Bryan Davis started work on improving
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering report, September 2013
Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_6project (read our announcementhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-September/072081.htmland blog posthttp://blog.wikimedia.org/2013/09/30/foss-outreach-program-for-women-success-and-new-round/). These numbers are unprecedented and we have to ensure that they are not just occasional results but a trend. Wrap-up reports from the projects: - Browser test automation for Visual Editorhttp://bleededge.blogspot.com/2013/09/wrap-up-of-my-outreach-program-for.html - Internationalization and Right-To-Left Support in VisualEditorhttp://moriel.smarterthanthat.com/tips/google-summer-of-code-2013-summary/ - Improve support for book structureshttp://www.mollywhite.net/blog/?p=104 - Section handling in Semantic Formshttp://lists.wikimedia.org/pipermail/wikitech-l/2013-October/072133.html - Prototyping inline comments http://richajain-annotator.blogspot.in/ - jQuery.IME extensions for Firefox and Chromehttp://blog.praveensingh.in/articles/gsoc-wrap-up/ *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom wrapped up work on supporting the deployment of VisualEditor, and resumed regular activities like preparing the Tech newsletterhttps://meta.wikimedia.org/wiki/Tech/Newsand ongoing communications support for the engineering staff. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Together with XWiki http://www.xwiki.org/ and Tiki https://tiki.org/, we submitted a Wiki devroomhttps://www.mediawiki.org/wiki/Events/FOSDEM#Devroom_proposalproposal for FOSDEM http://fosdem.org, the biggest open source source conference in Europe. We are also preparing a proposal for a stand, lead by volunteers at the nascent Wikimedia Belgium chapter. The overall goal is to achieve a good MediaWiki Wikimedia tech gathering in Brussels next February. We are also supporting the organization of the MediaWiki Architecture Summithttps://www.mediawiki.org/wiki/Architecture_guidelines/Meetings/Architecture_Summit_2014in San Francisco on 23-24 January, 2014. Analytics https://www.mediawiki.org/wiki/Analytics The team has been focused on smaller but more important work items this month, including enhancement to Wikimetrics, Grantmaking and Program Developments graphing infrastructure and fixing some long-standing Limn bugs. On the infrastructure side, our collaboration with Ops has the Kafka middleware project moving along nicely. The all-staff meeting and travel schedules definitely impacted our throughput this month.Two notable accomplishments should be called out: our Hadoop environment is now 100% free software, as we swapped out a proprietary JDK for OpenJDK 7. We also spent a lot of time on our engagement processes and planning for our first combined quarterly review in October, and made significant process on our hiring goals. *Research and datahttps://www.mediawiki.org/wiki/Analytics/Research_and_Data * This month, Aaron Halfakerhttps://en.wikipedia.org/wiki/User:Halfak_%28WMF%29joined the research team as a full-time employee. We started to reorganize the team structure and engagement model in coordination with the Analytics developers. We performed a survival analysis of new editorshttps://meta.wikimedia.org/wiki/Research:Newcomer_survival_modelsin preparation for new experiments led by the Growth https://meta.wikimedia.org/wiki/Growth team, and worked with the team to iron out the data collection and experimental design for the fortcoming iterationhttps://meta.wikimedia.org/wiki/Research:Onboarding_new_Wikipedians/OB6of *GettingStarted*. We worked with product owners to determine the initial research strategy for features with key releases scheduled for the next two quarters (Mobile Web https://www.mediawiki.org/wiki/Mobile_web/Team, Beta Featureshttps://www.mediawiki.org/wiki/Beta_Features, Multimedia https://www.mediawiki.org/wiki/Multimedia, Flowhttps://www.mediawiki.org/wiki/Flow, Universal Language Selectorhttps://www.mediawiki.org/wiki/Universal_Language_Selector, Content translation https://www.mediawiki.org/wiki/Content_translation). We started a cohort analysis of conversion rates for mobile vs desktop account registrations; the results will be publishedhttps://meta.wikimedia.org/wiki/R:Mobile_editor_engagementon Meta shortly. We drafted a proposal to host tabular datasetshttps://meta.wikimedia.org/wiki/DataNamespacein a dedicated namespace and solicited feedback from interested parties (particularly the Wikidata community). We also started fleshing out the Labs 2 https://meta.wikimedia.org/wiki/Research:Labs2proposal, an outreach program for academic researchers and community members, launched at Wikimania 2013 in Hong Kong. We co-hosted the second IRC research office hours and prepared for the first Wikimedia research hackathonhttps://meta.wikimedia.org
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering August 2013 report
://www.mediawiki.org/wiki/User:Orsagi/GSoC_2013_proposal#Monthly_Report:_August_2013 - Mobilizing Wikidatahttps://www.mediawiki.org/wiki/User:Pragunbhutani/GSoC_2013_Updates#Monthly_Report:_August_2013 - Improve support for book structureshttps://meta.wikimedia.org/wiki/Book_management/Progress#August - Incremental data dumpshttps://www.mediawiki.org/wiki/User:Svick/Incremental_dumps#August_report - Language Coverage Matrix Dashboardhttps://www.mediawiki.org/wiki/User:Harsh4101991/GSoC_2013#August - Internationalization and Right-To-Left Support in VisualEditorhttps://www.mediawiki.org/wiki/User:Mooeypoo/GSOC_2013_Proposal:_RTL_Support_in_VisualEditor#Monthly_Report:_August_2013 - Browser test automation for Visual Editorhttps://www.mediawiki.org/wiki/User:Rachel99/proposal1#August - VisualEditor plugin for source codehttps://www.mediawiki.org/wiki/User:Beanixster#August - UploadWizard: Book upload customizationhttps://www.mediawiki.org/wiki/User:Rasel160/GSoC2013/Status#2013-08-monthly - Prototyping inline commentshttps://www.mediawiki.org/wiki/User:Rjain/Gsoc2013/Project_Updates#August - Improvement of glossary toolshttps://www.mediawiki.org/wiki/GSOC_2013_Improvement_of_glossary_tools#August - Incremental updates for Kiwixhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993/ZIM_incremental_updates_for_Kiwix#Reports - Pronunciation Recording Toolhttps://www.mediawiki.org/wiki/User:Rahul21/Gsoc2013/Project_Updates#August - Bayesian Spam Filterhttps://www.mediawiki.org/wiki/User:Anubhav_iitr/Bayesan_spam_filter/Project_updates - Wikidata language fallback and conversionhttps://www.mediawiki.org/wiki/User:Liangent/wb-lang/updates#August *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom continued to focus on the VisualEditor deployment effort, working on communications, documentation and liaising with the French Wikipedia. Work on technical communications mostly focused on perennial activities like Tech newshttps://meta.wikimedia.org/wiki/Tech/Newsand ongoing communications support to the engineering staff. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * We had a team presentation at Wikimania: Transparency and collaboration in Wikimedia engineeringhttp://wikimania2013.wikimedia.org/wiki/Talk:Submissions/Transparency_and_collaboration_in_Wikimedia_engineering, explaining how volunteers can make a difference. Following the work on Community metrics https://www.mediawiki.org/wiki/Community_metrics, the five key performance indicatorshttps://www.mediawiki.org/wiki/Community_metrics#Key_performance_indicators(KPIs) were discussed and agreed upon. We are focusing on the first one: who contributes codehttps://www.mediawiki.org/wiki/Community_metrics#Who_contributes_code. A list of Key Wikimedia software projectshttps://wikitech.wikimedia.org/wiki/Key_Wikimedia_software_projectshas been created to define the scope of these KPIs. Recruiting automated browser testers keeps being our top priority. We are organizing the next workshop in San Francisco and online on September 18: Epic fail: figuring out Selenium test resultshttp://www.meetup.com/wikimedia-tech/events/137381022/ . Analytics https://www.mediawiki.org/wiki/Analytics *Analytics infrastructurehttps://www.mediawiki.org/wiki/Analytics/Infrastructure * We continue to pursue the initiatives listed in our planning document. We've had one analyst accept a job offer (welcome Aaronhttps://en.wikipedia.org/wiki/User:EpochFail!) and are in discussions with a software engineer. We continue to have a solid pipeline and are spending a lot of time interviewing. Wikimetrics is on target for an early September release and we've made good progress against our hadoop infrastructure goals. In co-operation with Ops, we've completed our reinstall of the Hadoop cluster and run several days of reliability testing over the labor day weekend. We are currently investigating replacing the Oracle JDK with the Open JDK to be in line with our goals of using open source whenever possible. Our project to replace udp2log with Kafka is making steadily progress. Varnishkafka, which will replace varnishncsa, has been debianizedhttps://gerrit.wikimedia.org/r/#/c/78782/and the first performance tests of compressing the message sets are very encouraging. We created a test environment in Labs to test Kafka failover modes and we have been prototyping with Camushttps://github.com/linkedin/camusto consume the data from a broker and write it to HDFS. We are right now thinking about how to set up Kafka in a multi data-center environment. The Zookeepers have been reinstalled through Puppet as well. *Analytics Visualization, Reporting Applicationshttps://www.mediawiki.org/wiki/Analytics/Visualization,_Reporting_%26_Applications * In close collaboration with Dario, Jaime and Jessie, we have worked on new features
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering July 2013 report
://www.mediawiki.org/wiki/Roadmap#Wikidata_deployment. Coveralls.io support https://coveralls.io/r/wikimedia has been added to most of our components. Since the first deployment of Phase1 to Wikipedia, about 240 million interwikilinks (5GB text) have been removed from articles (2012http://simia.net/languagelinks/index.htmlvs 2013 http://simia.net/languagelinks/2013.html analysis). In other news, the AAAI Feigenbaum Prize for Watson was donated to the Wikimedia Foundation by IBM research to support work, especially on Wikidatahttps://blog.wikimedia.org/2013/07/16/ibm-research-watson-aaai-prize-wikimedia-foundation/ . Denny Vrandečić explainshttp://lists.wikimedia.org/pipermail/wikidata-l/2013-July/002518.htmlwhy Wikidata items are identified with a Q. Future The engineering management team continues to update the *Deploymentshttps://wikitech.wikimedia.org/wiki/Deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. *Annual goals*https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goalsfor the 2013–2014 fiscal year are being drafted by some teams and have been finalized by others. * This article was written collaboratively by Wikimedia engineers and managers, and assembled by Sumana Harihareswara. See revision historyhttps://www.mediawiki.org/w/index.php?title=Wikimedia_engineering_report/2013/Julyaction=historyand associated status pages. A wiki versionhttps://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/Julyis also available. * -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] Tech newsletter #29
and will be added to wikis later. [8]http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070253.html - Wikivoyage https://meta.wikimedia.org/wiki/voy: wikis will start to use Wikidata https://meta.wikimedia.org/wiki/d: for interwiki links on July 22. [9]http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2013-July/000297.html - A new image gallery designhttps://tools.wmflabs.org/bawolff/gallery/index.php?title=Featured_pictures/Non-photographic_mediahas been proposed by Brian Wolff; comments and feedback are welcome. - An IRC discussion https://meta.wikimedia.org/wiki/IRC_office_hoursabout Bugzilla is planned for July 16, at 16:00 (UTC) on the IRC channel #wikimedia-office on Freenode (time conversionhttp://www.timeanddate.com/worldclock/meetingdetails.html?year=2013month=7day=15hour=16min=0sec=0p1=224p2=179p3=195p4=176p5=240). [10]http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070248.html *Tech news https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Newsprepared by tech ambassadorshttps://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Ambassadorsand posted by Global message delivery https://meta.wikimedia.org/wiki/Global_message_delivery• Contributehttps://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News#contribute• Translatehttps://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2013/29• Get help https://meta.wikimedia.org/wiki/Tech • Give feedbackhttps://meta.wikimedia.org/wiki/Talk:Tech/News• Subscribe or unsubscribehttps://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Tech_ambassadors .* -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering June 2013 report
was the deployment of the geocoordinate datatype. This makes it possible, for example, to indicate the location of a city. Geocoordinates that are already in Wikidata can be seen on this maphttps://dl.dropboxusercontent.com/u/172199972/map.png(huge version https://dl.dropboxusercontent.com/u/172199972/map_huge.png, updated daily). In a blog entryhttp://blog.wikimedia.de/2013/06/04/on-truths-and-lies/, Denny Vrandečić explained his understanding of the relation of Wikidata and the truth. In other news, further development of Wikidata has been supported through a large donation by the search engine company Yandexhttp://blog.wikimedia.de/2013/06/05/grosspende-fur-wikidata/ . Future The engineering management team continues to update the * Deployments https://wikitech.wikimedia.org/wiki/Deployments* page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. *Annual goals*https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goalsfor the 2013–2014 fiscal year are currently being drafted. -- This report was reviewed and proofread using VisualEditor. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering May 2013 report
of his investigation, Andre documentedhttp://blogs.gnome.org/aklapper/2013/05/28/understanding-bugzilla-groups-and-admin-rights/the meaning of Bugzilla admin rights. *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* We selected 20 Google Summer of Codehttps://www.mediawiki.org/wiki/Summer_of_Code_2013and 2 Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_6projects that will be mentored by a total of 32 volunteers. This represents more than double the amount of projects we had last year. We received 69 applications from 60 students for Google Summer of Code 2013, from which 9 were also applying to OPW, and 4 OPW-only individual applications. Google allocated the 21 slots we requested, but we decided to give one back in order to keep a standard on project feasibility. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * In May, Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom's major focus was on supporting Tech ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadorsand setting up Tech news https://meta.wikimedia.org/wiki/Tech/News, an initiative aiming to collaboratively monitor recent software changes likely to impact Wikimedians, and distribute a weekly summary, free of technical jargon, to subscribers on their talk page. Two issues of this weekly summary were published this month; starting with the second issue, the content is now distributed in several languages if translations are available. Guillaume also continued to review technical blog posts, and executed the move of the Mobile documentationhttps://www.mediawiki.org/wiki/Technical_communications/Mobile_documentation_consolidationfrom Meta-Wiki to mediawiki.org. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Quim Gil https://www.mediawiki.org/wiki/User:Qgil has been preparing a proposal to get automated community metricshttps://www.mediawiki.org/wiki/Community_metricsbased on vizGrimoire http://vizgrimoire.bitergia.org/ and provided by their maintainers, Bitergia http://bitergia.com/. It is currently being discussed with Sumana Harihareswarahttps://www.mediawiki.org/wiki/User:Sharihareswara_%28WMF%29and Rob Lanphier https://www.mediawiki.org/wiki/User:RobLa-WMF for budget approval. Quim also worked on a user-friendly template for the landing page of the wikitech-announcehttps://lists.wikimedia.org/mailman/listinfo/wikitech-announcemailing list that can be used for other Wikimedia lists (source code https://www.mediawiki.org/wiki/User:Qgil/wikitech-announce). He also created a landing page for organizationshttps://www.mediawiki.org/wiki/Mentorship_programs/Organizationswilling to collaborate with Wikimedia to co-organize technical activities. Kiwix http://www.kiwix.org *The Kiwix project is funded and executed by Wikimedia CHhttps://meta.wikimedia.org/wiki/Wikimedia_CH .* With openZIM http://www.openzim.org, we have finally released the first version of its standard implementation code: the zimlibhttp://www.openzim.org/wiki/Zimlib. Kiwix was introduced in Debian testinghttp://packages.debian.org/search?suite=allarch=anysearchon=nameskeywords=kiwix. A new release of Kiwix for Androidhttps://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile, with a few bug fixes and improvements, was released. Our first GSoC project (ZIM incremental updates for Kiwixhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993/ZIM_incremental_updates_for_Kiwix) was prepared and accepted; work has already started with Kiranhttps://www.mediawiki.org/wiki/User:Kiran_mathew_1993, the Indian student responsible for this project. Wikidatahttps://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The Wikidata team worked on 2 major topics in May: the ability to access data from Wikidata in a Wikipedia article by its label and not just its ID, and the ability to enter points in time into Wikidatahttps://www.wikidata.org/wiki/Wikidata:Project_chat#Time_datatype_available_and_short_overview_of_next_steps, which for example now makes it possible to enter the date of birth of a person. Magnus Manske blogged about the tool ecosystemhttp://blog.wikimedia.de/2013/05/06/the-wikidata-tool-ecosystem/that is building around Wikidata. During the next 3 months, the team will be workinghttp://lists.wikimedia.org/pipermail/wikidata-l/2013-May/002293.htmlwith 3 Google Summer of Code students, and 2 other students will be working with other organizations on Wikidata-related projects. The codebase has been reviewedhttp://lists.wikimedia.org/pipermail/wikidata-tech/2013-May/06.htmlby Qafoo. Wikidata-tech https://lists.wikimedia.org/mailman/listinfo/wikidata-tech, a new mailing list for discussions related to the development around Wikidata, was created. Additionally, the team attended the hackathon
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering April 2013 report
://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * Quim Gil https://www.mediawiki.org/wiki/User:Qgil refactored the radica *Wikitech contributors* proposal into the more gradual Project:New contributorshttps://www.mediawiki.org/wiki/Project:New_contributorsbased on the feedback received. He supported QA and bug management events, organized a tech talk for 3 tech projects receiving Wikimedia grantshttps://www.mediawiki.org/wiki/Meetings/2013-04-18, and completed the survey about best times for volunteeringhttp://www.doodle.com/minqnd6ngz9npfdv(which got 33 answers). He spoke at the Bay Area Linux User Group http://balug.org with Daniel Zahn, Rob Lanphier and Brian Wolff, and requested a proposal from Bitergia http://bitergia.comto automate the generation of Community metrics https://www.mediawiki.org/wiki/Community_metrics. Kiwix http://www.kiwix.org *The Kiwix project is funded and executed by Wikimedia CHhttps://meta.wikimedia.org/wiki/Wikimedia_CH .* In April, we releasedhttps://blog.wikimedia.org/2013/04/17/carry-the-entirety-of-wikipedia-in-your-pocket-with-kiwix-for-android/for the first time Kiwix for Androidhttps://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile. This version doesn't provide as many features as the desktop app, but it works well with all ZIM files. Two Kiwix developers will attend Wikimania and have started preparing http://www.kiwix.org/wiki/Wikimania_2013 for a a small hackathon, two presentations and a permanent booth. Wikidatahttps://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The team hit a big milestone with the deployment of the first iteration of phase 2 of Wikidata on all remaininghttp://blog.wikimedia.de/2013/04/22/and-that-makes-12/ Wikipediashttp://blog.wikimedia.de/2013/04/24/wikidata-all-around-the-world/(it had been enabled on 11 Wikipedias previously). Qualifiershttps://meta.wikimedia.org/wiki/Wikidata/Notes/Data_model_primer#Qualifierswere also enabled on Wikidata, making it possible to add additional information to certain data. Wikipedians are now able to make use of the data available on Wikidata in articles, allowing the data to be collaboratively collected, curated and used by all Wikipedias.The team also fixed a few issues to make it possible to use Wikidata with Internet Explorer 8, and worked on the time datatype. Together with bot owners, they massively improved the time it takes for Wikidata changes to show up in the recent changes and watchlists on Wikipedia sites. The code and architecture got an external professional review; the reviewers were quite happy with the quality of the code base and gave useful tips for improvements. Future The engineering management team continues to update the *Deploymentshttps://wikitech.wikimedia.org/wiki/Deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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] Glossary vs. Glossaries
Hi, On Fri, Mar 22, 2013 at 2:27 PM, Guillaume Paumier gpaum...@wikimedia.org wrote: * Google custom search: Waldir recently used Google Custom Search to created a search tool to find technical information across many pages and sites where information is currently fragmented: http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067450.html . We could set up a similar tool (or a floss alternative) that would include all glossaries. By advertising the tool prominently on existing glossary pages (so that users know it exists), this could allow us to curate more specific glossaries, while keeping them all searchable with one tool. Just a quick note to let people know that this is now up and running: https://www.google.com/cse/home?cx=015296225943515200682:ds3sfewbbrw (Note to Ghostery users: you'll have to enable Google AJAX Search API to see search results.) I'm slightly annoyed that this is a third-party tool and I'd much prefer a floss alternative running on Tool Labs or something, but until that happens, we have a working tool we can use to search a term across scattered Wikimedia-related glossaries. I'd like to find people to help maintain the URL list (right now there's a version at https://meta.wikimedia.org/w/index.php?oldid=5406259 ) so if you'd like to help, contact me offlist and I'll give you access. The next step is to better organize the glossaries, and actually add definitions; I'll start another thread later about this. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] [Wikimedia Announcements] Announcement *please read*
Hi, On Thu, Mar 28, 2013 at 12:38 PM, Dariusz Jemielniak dar...@alk.edu.pl wrote: One piece of thought (without looking much into the technicalities): Perhaps the movement could really benefit from an ex-exec of this caliber getting a new seat on the Board. or more probably the Advisory board :) https://wikimediafoundation.org/wiki/Advisory_Board -- Guillaume Paumier ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
[Wikimedia-l] [Wikimedia Announcements] Lua scripting enabled today on all wikis
pywikipedia, try parsercountfunction.py by Binárishttps://svn.wikimedia.org/svnroot/pywikipedia/trunk/pywikipedia/parserfunctioncount.py, which helps you find wikitext templates that currently parse slowly and thus would be worth converting to Lua. Try fulfilling open requests for conversion on English Wikipediahttps://en.wikipedia.org/wiki/Wikipedia:Lua_requests, possibly using Anomie’s Greasemonkey scripthttps://en.wikipedia.org/wiki/User:Anomie/PP-report-Greasemonkey-scriptto help you see the performance gains. On English Wikipedia, some of the templates have already been convertedhttps://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Lua_talk *—* feel free to reuse them on your wiki. The Lua hub on mediawiki.org https://www.mediawiki.org/wiki/Lua has more information; please add to it. And enjoy your faster, more flexible templates! *Sumana Harihareswara, Engineering Community Manager* = -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering January 2013 report
the MediaWiki Group Bug Squadhttps://www.mediawiki.org/wiki/Groups/Proposals/Bug_Squad. Furthermore, some problems due to data center migrationhttps://blog.wikimedia.org/2013/01/19/wikimedia-sites-move-to-primary-data-center-in-ashburn-virginia/were investigated, and it was discussed how to improve interaction on Bugzilla tickets that need handling by the Operations team (who mostly prefers to use the RT https://rt.wikimedia.org/ bugtracker instead). *Mentorship programs https://www.mediawiki.org/wiki/Mentorship_programs* Six Outreach Program for Womenhttps://www.mediawiki.org/wiki/Outreach_Program_for_Womeninterns started on January 3rd and will work full time until April. Mariya https://www.mediawiki.org/wiki/User:Mitevam is working on a discussion among third-party MediaWiki usershttps://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion. Valerie https://www.mediawiki.org/wiki/User:Valeriej has completed the Bug Squad group proposalhttps://www.mediawiki.org/wiki/Groups/Proposals/Bug_Squadand a first Bug Day. Priyanka https://www.mediawiki.org/wiki/User:Priyanka_Nag created a scripthttps://www.mediawiki.org/wiki/User:Priyanka_Nag/common.jsand plans to move to Git https://www.mediawiki.org/wiki/Git. Suchetahttps://www.mediawiki.org/wiki/User:Sucheta_Ghoshalis on schedule following her project planhttps://www.mediawiki.org/wiki/User:Sucheta_Ghoshal/OPW-EtherEditor#Plans_and_Estimated_Timeline. Kim https://www.mediawiki.org/wiki/User:Isarra is learning about Flowhttps://www.mediawiki.org/wiki/Flowand the basics of interactive design as indicated by her mentor. Teresa https://www.mediawiki.org/wiki/User:Chot has completed a solid basehttps://gerrit.wikimedia.org/r/#/q/owner:tcho708%2540gmail.com,n,zfor her extension and is working on the main functionality. She hit a snag with her work environment this week, but is still on track with her proposed timeline. The Google Summer of Code 2013https://www.mediawiki.org/wiki/Summer_of_Code_2013page was created, a pre-planning discussionhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065771.htmlstarted on wikitech-l, and LevelUp https://www.mediawiki.org/wiki/Mentorship_programs/LevelUpmatchmaking for the first quarter of 2013 is nearly done. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom provided communications supporthttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityto the engineering team, notably around the data center migrationhttps://blog.wikimedia.org/2013/01/19/wikimedia-sites-move-to-primary-data-center-in-ashburn-virginia/and associated bannershttps://meta.wikimedia.org/wiki/CentralNotice/Generic_maintenance_notice, noticeshttps://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Spamoldid=5081391 translationshttp://lists.wikimedia.org/pipermail/translators-l/2013-January/002199.html. He started to organize and clean up the MediaWiki version pages (like MediaWiki 1.21/wmf7 https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf7) to make them more useful for tech ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadors, by highlighting the most important changes, improving translatability and adding navigation. He also prepared and organized translations for the *How to report a bug https://www.mediawiki.org/wiki/How_to_report_a_bug* and *How to contribute https://www.mediawiki.org/wiki/How_to_contribute* pages, to facilitate the involvement of volunteers who don't necessarily communicate in English. Last, he created a Project:Calendarhttps://www.mediawiki.org/wiki/Project:Calendarto consolidate and centralize announcements for all events https://www.mediawiki.org/wiki/Template:Event, to make opportunities for participation more visible. Events around a particular topic (like QA, testing and bugshttps://www.mediawiki.org/wiki/QA/Weekly_goals) can still be selectively transcluded, using Labeled Section Transclusionhttps://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion . *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * The MediaWiki groups https://www.mediawiki.org/wiki/Groups for Promotionhttps://www.mediawiki.org/wiki/Groups/Promotionand San Francisco https://www.mediawiki.org/wiki/Groups/San_Francisco were officially approved by the Wikimedia Affiliations Committeehttps://meta.wikimedia.org/wiki/Affiliations_Committee, and are the first Wikimedia User Groupshttps://meta.wikimedia.org/wiki/Wikimedia_User_Groups#Approved_user_groupscreated. We helped the Editor Engagement https://www.mediawiki.org/wiki/Editor_Engagement team organize a sprint to test Echo https://www.mediawiki.org/wiki/Echo/Testing, but our plans to collaborate further with the Editor Engagement and Mobilehttps://www.mediawiki.org/wiki/Mobileteams were delayed; Quim Gil proposed a different approachhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-January/065758
[Wikimedia-l] [Wikimedia Announcements] Wikimedia sites to move to primary data center in Ashburn, Virginia. Disruption expected.
on donations from readers. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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] adding SM to the Blog Calendar on Meta
Hi, On Fri, Jan 18, 2013 at 2:52 AM, Matthew Roth mr...@wikimedia.org wrote: Do you guys think it makes any sense to use Meta to help handle the workflow for both the blog and social media messages? See the item for tomorrow where I've added proposed social media message for the two blog posts I'm publishing tomorrow: http://meta.wikimedia.org/wiki/Wikimedia_Blog/Calendar#January_2013 I don't know how we can make Meta work for this kind of thing, but it seems to make sense to me to try to consolidate the tool we use for seeking and giving feedback on these. I'm too lazy to dig up the previous conversation about this in my e-mail archives, but I think that's what we wanted to do at some point. I think it's when Stacey started publishing OTD / DYK stuff and we felt it could be scheduled far in advance to avoid being delayed by belated validation of the proposed postings on the socialmedia@ alias. It's also why the blog calendar has the qualifier Blog for each blog post: because at some point we started to add social media stuff there too, so Blog was used to distinguish the blog posts from social media postings. (Oh, and that means I'm totally fine with it, btw :) -- Guillaume Paumier ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering December 2012 report
://www.mediawiki.org/wiki/Outreach_Program_for_Women(OPW). 4 of them are funded by the Wikimedia Foundation and 2 by Google through an agreement with the GNOME Foundation, organizers of the program. They will work as full-time interns under the supervision of MediaWiki mentors between January and March 2013. We got 10 submissions from about 25 people interested. The rather open and participatory selection processhttps://www.mediawiki.org/wiki/Mentorship_programs/Selection_processwe have defined for OPW will be used as a basis for future mentoring programs. We've also started matchmaking for the LevelUphttps://www.mediawiki.org/wiki/Mentorship_programs/LevelUpmentorships for the coming quarter. *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * [edithttps://www.mediawiki.org/w/index.php?title=Technical_communications/statusaction=edit ] Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom published a project plan and timelinehttps://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultationfor the consultation process started in October about how to improve 2-way communication between the technical and editing communities. He summarizedhttps://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultation#Phase_2:_Summary_and_wider_outreachthe results of the first phase and reached out to the wikitech-ambassadors listhttp://lists.wikimedia.org/pipermail/wikitech-ambassadors/2012-December/000105.htmlto widen the consultation process by proxy. After consolidation and prioritization of the results, the most feasible solution appeared to be to grow a network of ambassadorshttps://meta.wikimedia.org/wiki/Tech/Ambassadors, which he started to organize on meta. Unrelatedly, Guillaume made a list of 2012 tech blog postshttps://www.mediawiki.org/wiki/Technical_communications/Tech_blog_activityto map tech blog activity by month subdepartment (with priority activities listed separately). Work on setting up a Volunteer product managerhttps://blog.wikimedia.org/2012/11/21/lead-development-process-product-adviser-manager/program is also underway. Quim Gil https://www.mediawiki.org/wiki/User:Qgil sorted out Social mediahttps://www.mediawiki.org/wiki/Social_mediachannels, and we now have @MediaWiki handles for identi.ca http://identi.ca/mediawiki, Twitterhttps://twitter.com/#%21/MediaWiki, Facebook https://www.facebook.com/MediaWikiProject and Google+https://plus.google.com/u/0/b/103470172168784626509/103470172168784626509/posts. He published the community metrics November reporthttps://www.mediawiki.org/wiki/Community_metrics/November_2012and a blog posthttps://blog.wikimedia.org/2012/12/10/introducing-mediawiki-community-metrics/introducing this new activity. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * [edithttps://www.mediawiki.org/w/index.php?title=Volunteer_coordination_and_outreach/statusaction=edit ] MediaWiki Groups https://www.mediawiki.org/wiki/Groups became official and the first proposals https://www.mediawiki.org/wiki/Groups/Proposalsare going through the approval process. As a side effect, a process for requesting regional mediawiki-themed mailing listshttps://www.mediawiki.org/wiki/Groups#Local_vs_regionalhas been created with mediawiki-indiahttps://lists.wikimedia.org/mailman/listinfo/mediawiki-indiaas the first case. At least three Wikimedia-related talks have been accepted at FOSDEM https://www.mediawiki.org/wiki/Events/FOSDEM. Language engineeringhttps://www.mediawiki.org/wiki/Wikimedia_Language_engineering *Language tools https://www.mediawiki.org/wiki/Language_tools* [edithttps://www.mediawiki.org/w/index.php?title=Language_tools/statusaction=edit ] Development of the new user interface for Translate, as well as the translation editor functionality, continued at full pace throughout the month of December, with iterative feature development and user experience improvements. Santhosh Thottingal and Niklas Laxström are leading development and Pau Giner is focusing on optimizing user experience elements. The team also released the latest version of the MediaWiki Language Extension Bundle. Increased support for language variants, alternate language codes were added to the Universal Language Selector. Alolita Sharma continued to work with Red Hat's localization and internationalization teams to evaluate localization data, translation tools and internationalization tools and technologies. *Milkshake https://www.mediawiki.org/wiki/Milkshake* [edithttps://www.mediawiki.org/w/index.php?title=Milkshake/statusaction=edit ] More language input methods contributed by language communities were added to the jquery.ime library. Other newsPau Giner and Amir Aharoni participated in the Open Tech Chat this month to talk about best practices in multilingual user testing and internationalization. Amir Aharoni also participated in mentoring OPWhttps://www.mediawiki.org/wiki/Outreach_Program_for_Womencandidate
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering November 2012 report
Gilhttps://www.mediawiki.org/wiki/User:Qgil, the new technical contributor coordinator who started working with the Wikimedia foundation in November. They continued to follow up on contacts (such as those gained at October's Grace Hopper Celebration of Women in Computing), recruit new contributors to the Wikimedia tech community, and mentor newer contributors. The weekly online tech chatshttps://www.mediawiki.org/wiki/Meetingscontinued on Thursdays. Sumana and others continued to grant developer access https://www.mediawiki.org/wiki/Developer_access and work on Gerrit project ownership requestshttps://www.mediawiki.org/wiki/Git/Gerrit_project_ownership . Language engineeringhttps://www.mediawiki.org/wiki/Wikimedia_Language_engineering *Language tools https://www.mediawiki.org/wiki/Language_tools* [edithttps://www.mediawiki.org/w/index.php?title=Language_tools/statusaction=edit ] In November 2012, the Language Engineering team travelled to India for 10 days together with the Mobile team for 6 events in total: the two-day Language Summit https://www.mediawiki.org/wiki/Pune_LanguageSummit_November_2012at the Red Hat offices in Pune, a Language Engineering Community Meetup in Punehttps://www.mediawiki.org/wiki/Pune_Language_Engineering_Meetup_November_2012, the three-day DevCamp 2012 Bangalorehttps://www.mediawiki.org/wiki/Bangalore_DevCamp_November_2012, a Language Engineering Community Meetup in Bangalorehttps://www.mediawiki.org/wiki/Bangalore_Language_Engineering_Meetup_November_2012, a presentation by Erik Moellerhttps://www.mediawiki.org/wiki/User:Eloquenceon the current state of tech in the Wikimedia Foundation, and *Coffee with Arky*, a meetup of Mozilla users. The rest of the month, development time was spent on completing the Universal Language Selector, and getting it to a state where it could be put in maintenance mode for a few months. In April 2013, phase two of the ULS will start, will consist of adding content language selection. The Language Engineering designers completed the design for the Translation UX https://www.mediawiki.org/wiki/Translation_UX project, for which development has commenced end of November, and will continue for 8 sprints of a fortnighthttps://mingle.corp.wikimedia.org/projects/internationalization/cards/1962, until mid-March 2013. *Milkshake https://www.mediawiki.org/wiki/Milkshake* [edithttps://www.mediawiki.org/w/index.php?title=Milkshake/statusaction=edit ] The first phase of the Universal Language Selectorhttps://www.mediawiki.org/wiki/Universal_Language_Selector(ULS) was completed in November. The jQuery modules jQuery.ULS https://github.com/wikimedia/jquery.uls, jQuery.IMEhttps://github.com/wikimedia/jquery.uls, jQuery Webfonts https://github.com/wikimedia/jquery.webfonts and jQuery i18n https://github.com/wikimedia/jquery.i18n have had their first stable version. The Universal Language Selectorhttps://www.mediawiki.org/wiki/Extension:UniversalLanguageSelectorMediaWiki extension is now being used on Wikidata https://en.wikidata.org/wiki/. During the DevCamp in Bangalorehttps://www.mediawiki.org/wiki/Bangalore_DevCamp_November_2012, experimentations were done with ULS in Android, a Chrome extension was created to make jQuery.IME usable in the Chrome web browser, and an extension for Firefox implementing the input methods is underway. The first contributions by non-Wikimedia developers have been made, which indicates that the jQuery extensions are getting some attention. The Wikimedia Language Engineering team will now put the modules and MediaWiki extension in maintenance mode until April 2013. Wikidata https://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The repository side of Wikidata has been launchedhttps://en.wikipedia.org/wiki//Wikipedia:Wikipedia_Signpost/2012-10-29/Technology_reporton http://www.wikidata.org. It contains the results of phase 1 (language links) and has already attracted a community to maintain the wiki. Meanwhile, the Wikidata team has continued work on Phase 2 of Wikidata (Infoboxes) to add statements with values to the items in the Wikidata repository. The team improved the propagation of changes from the repository to the client and the messaging in Recent Changes. There is a constant exchange with Wikimedia Foundation engineers about the upcoming deployment cycle. Feedback and questions are welcome on the mailing listhttps://lists.wikimedia.org/mailman/listinfo/wikidata-land on meta https://meta.wikimedia.org/wiki/Talk:Wikidata. Future The engineering management team continues to update the *Software deploymentshttp://wikitech.wikimedia.org/view/Software_deployments * page weekly, providing up-to-date information on the upcoming deployments to Wikimedia sites, as well as the *engineering roadmaphttps://www.mediawiki.org/wiki/Roadmap *, listing ongoing and future Wikimedia engineering efforts. -- Guillaume Paumier
[Wikimedia-l] Help needed to complete and expand the Wikimedia glossary
Hi, The use of jargon, acronyms and other abbreviations throughout the Wikimedia movement is a major source of communication issues, and barriers to comprehension and involvement. The recent thread on this list about What is Product? is an example of this, as are initialisms that have long been known to be a barrier for Wikipedia newcomers. A way to bridge people and communities with different vocabularies is to write and maintain a glossary that explains jargon in plain English terms. We've been lacking a good and up-to-date glossary for Wikimedia stuff (Foundation, chapter, movement, technology, etc.). Therefore, I've started to clean up and expand the outdated Glossary on meta, but it's a lot of work, and I don't have all the answers myself either. I'll continue to work on it, but I'd love to get some help on this and to make it a collaborative effort. If you have a few minutes to spare, please consider helping your (current and future) fellow Wikimedians by writing a few definitions if there are terms that you can explain in plain English. Additions of new terms are much welcome as well: https://meta.wikimedia.org/wiki/Glossary Some caveats: * As part of my work, I'm mostly interested in a glossary from a technical perspective, so the list currently has a technical bias. I'm hoping that by sending this message to a wider audience, people from the whole movement will contribute to the glossary and balance it out. * Also, I've started to clean up the glossary, but it still contains dated terms and definitions from a few years ago (like the FundCom), so boldly edit/remove obsolete content. Thank you, -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering October 2012 report
, and deployed a new banner impression filter. Engineering community team *Bug management https://www.mediawiki.org/wiki/Bug_management* [edithttps://www.mediawiki.org/w/index.php?title=Bug_management/statusaction=edit ] New Bug Wrangler Andre Klapperhttps://www.mediawiki.org/wiki/User:Malyackohad many discussions with different stakeholders to get a better impression of how work is done, how people interact with the bug tracker, what the expectations are and what policies might be needed. He investigated the product/component organization within bugzilla, started triaging incoming and older reports, and did maintenance work (creation and partial cleanup of products and components). bugzilla.wikimedia.org was upgraded to 4.0.8 with the help of Daniel Zahn, and investigations started to determine how urgent an upgrade to 4.2 was with regard to functionality improvements. Plans for the next month include improving documentation on bug management and bug triaging, and describing interactions between the bug wrangler and the different teams. *Summer of Code 2012https://www.mediawiki.org/wiki/Summer_of_Code_2012/management * [edithttps://www.mediawiki.org/w/index.php?title=Summer_of_Code_2012/management/statusaction=edit ] The Wikimedia engineering community continues to help the 2012 GSoC students improve their projects towards the goal of release and deployment. Sumana Harihareswara aims to lead a postmortem discussion in November. Rob Lanphier and Sumana attended a GSoC Mentors' Summit in October, and discussed mentor recruitment http://etherpad.osuosl.org/veFnJ0z05K, community metrics http://gsoc-wiki.osuosl.org/index.php/Community_Metrics, how to be more effective mentors, student selection strategieshttp://gsoc-wiki.osuosl.org/index.php/Ideas_an_techniques_to_improves_student_selection_phase, PHP http://gsoc-wiki.osuosl.org/index.php/PHP and code review tools, and other related topics. As a follow-up to Summer of Code, the MediaWiki community is discussing whether to participate in Google Code-Inhttps://www.mediawiki.org/wiki/Google_Code-In . *Technical communicationshttps://www.mediawiki.org/wiki/Technical_communications * [edithttps://www.mediawiki.org/w/index.php?title=Technical_communications/statusaction=edit ] This activity was revived as its scope was expanded to include not only on-wiki engineering project documentation, but more generally the improvement of communications between Wikimedia contributors and the technical community (MediaWiki developers, Operations engineers, etc.). Guillaume Paumier https://www.mediawiki.org/wiki/User:Guillom prepared and started a wide and open discussion with editors on some local wikis to identify issues and discussion possible solutions. Management is currently reviewing options to determine the direction this activity will follow in future months. *Volunteer coordination and outreachhttps://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach * [edithttps://www.mediawiki.org/w/index.php?title=Volunteer_coordination_and_outreach/statusaction=edit ] Sumana Harihareswara https://www.mediawiki.org/wiki/User:Sumanahcontinued to follow up on contacts (such as those gained at October's Grace Hopper Celebration of Women in Computing), recruit new contributors to the Wikimedia tech community, and mentor newer contributors. She granted developer access https://www.mediawiki.org/wiki/Developer_access and Gerrit project ownership requestshttps://www.mediawiki.org/wiki/Git/Gerrit_project_ownership, and worked on getting more volunteer developers +2https://www.mediawiki.org/wiki/%2B2status in MediaWiki core: 8 volunteers now have MediaWiki core maintainership. Sumana also published a retrospective of the 2012 Berlin Hackathonhttps://www.mediawiki.org/wiki/Berlin_Hackathon_2012/Retrospectiveand updated the list of towards a better understanding of which parts of the codebase are maintained, and by whom. Hiring for a Volunteer Engineering Coordinator to work on volunteer coordination and outreach is almost finished. Wikidata https://meta.wikimedia.org/wiki/Wikidata *The Wikidata project is funded and executed by Wikimedia Deutschlandhttps://meta.wikimedia.org/wiki/Wikimedia_Deutschland/en .* The Wikidata team has worked on initial parts of Phase 2 of Wikidata (Infoboxes) and worked together with the WMF to get Wikidata deployed on http://www.wikidata.org. A big step towards this deployment was the merge of the content handler branchhttps://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-10-15/Technology_reportinto MediaWiki core. This allows MediaWiki to handle other content types besides just wikitext. In addition, the team is looking for help with the initial design of the Main Pagehttp://lists.wikimedia.org/pipermail/wikidata-l/2012-October/001104.htmlof wikidata.org. A draft was also published by the team discussing how the propagation of changes from a repository to the clientshttps://meta.wikimedia.org/wiki/Wikidata/Notes/Change_propagationshould work
Re: [Wikimedia-l] Fwd: [WikiEN-l] Improving dialogue between editors and tech people
Hi, On Fri, Oct 26, 2012 at 4:26 PM, JP Béland lebo.bel...@gmail.com wrote: I`m wondering why this discussion is on the English Wikipedia since it concerns all projects, it should be on Meta in my opinion. To avoid the Not my wiki effect [1], I've chosen to start multiple discussions on local wikis instead of a central one on meta. This week, I'm focusing on all English and French language wikis, and I'm planning to expand to other languages next week. With that in mind, I welcome comments on this list as well, and if you'd like to start the discussion on your wiki now, please feel free to do so; your help will be much appreciated. [1] https://meta.wikimedia.org/wiki/Not_my_wiki -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering August 2012 report
Hi, On Wed, Sep 5, 2012 at 3:05 AM, Federico Leva (Nemo) nemow...@gmail.com wrote: Tilman Bayer, 05/09/2012 02:52: Rupert raises an interesting point. How many people prefer such mailing list announcements of new reports to include a plaintext version of the report itself? Usually I'm very more likely to read something if it's directly in the email, however long; a link means oh, more work, must be something long, of unknown length (I don't see it), requires one more click, and finally the click just sends the reading to the queue together with the other dozens tabs open in the browser. That said, a good compromise is, I found, to just include the HTML from the wiki page. HTML emails are horrible (and I usually fail at sending them) but converting wikitext to a readable email plaintext is horrible too. I'm happy to do that, but do Wikimedia mailing lists support HTML e-mails? -- Guillaume Paumier ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering September 2012 report
Hi, The report covering Wikimedia engineering activities in September 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/September Blog version: https://blog.wikimedia.org/2012/10/03/engineering-september-2012-report/ -- Guillaume Paumier ___ 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
[Wikimedia-l] [Wikimedia Announcements] Wikimedia engineering July 2012 report
Hi, The report covering Wikimedia engineering activities in July 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/July Blog version: https://blog.wikimedia.org/2012/08/02/engineering-july-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ 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] [Wikitech-l] New, lower traffic, announcements only email list for Wikimedia developers
Hi, [cc:ing wikimedia-l because this message is also for Wikimedia users.] I've been asked to weigh in on this topic, because this is going to be an area of focus for me over the coming year. I've been tasked with improving the 2-way communication between users developers, possibly using the wikitech-ambassadors list as a medium. A few people have already explained the scope of the different lists, but here's my understanding: * wikitech-l: A high-traffic, unapologetically technical, discussion list for developers talking to developers * wikitech-announce: A low-traffic, plain English, announce-only list for developers talking to Wikimedia users * wikitech-ambassadors: A (currently) low-traffic, mostly-announce list for developers talking to Wikimedia users * mediawiki-announce: A low-traffic, announce-only list for developers talking to (mostly 3rd-party) MediaWiki users * wikimediaannounce: A low-traffic, plain English, announce-only list for general Wikimedia usues. And the possible change would be for wikitech-ambassadors to become a medium-to-high-traffic, plain English, list for discussion between developers and Wikimedia users, to report issues, share ideas and provide feedback in unapologetically layman terms. The Ambassadors part also means that users who are on that list will have a role in disseminating information to their local communities, and reporting back issues possibly raised on local wikis. FYI, if you're at Wikimania this week, this 2-way communication channel between developers and users will be a main focus of the Transparency discussion with Sumana, Rob and myself on Saturday 14 at 10:30 in Room 310: https://wikimania2012.wikimedia.org/wiki/Submissions/Transparency_and_collaboration_in_Wikimedia_engineering I've also just noticed that there are two other talks related to this topic: * Oliver's Engaging the Community: What We've Tried and Where We're Going (Thursday July 12, 11:40, Room 310) https://wikimania2012.wikimedia.org/wiki/Submissions/Engaging_the_Community:_What_We%27ve_Tried_and_Where_We%27re_Going * Tilman and Max's Movement Broadcasting - 'Stop Spamming' vs. 'Nobody Told Me (Thursday, July 12, 14:00, Room 302) https://wikimania2012.wikimedia.org/wiki/Submissions/Movement_Broadcasting_-_%27Stop_Spamming%27_vs._%27Nobody_Told_Me%27 If you can't attend any of those sessions, but you want to discuss / rant / share ideas about (mis)communication between MediaWiki developers and Wikimedia users, please come to me at any time during the hackathon or the conference (If we don't already know each other, my photo is on https://wikimediafoundation.org/wiki/Staff_and_contractors ) And if you're not at Wikimania, feel free to drop me an e-mail with your thoughts on the subject. -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
