Wikitech-l June 2018

wikitech-l@lists.wikimedia.org

77 participants
84 discussions

Discovery Weekly Update for the week starting 2018-06-04
by Chris Koerner 11 Jun '18

11 Jun '18

Howdy, Here's the weekly update from the Search Platform team. As always, feedback and questions welcome. == Discussions == === Search === * After lots of talk about stemmers getting committed and plugins getting deployed, the Slovak-language wikis have finally been *reindexed*, and stemming [0] is now happening on the Slovak wikis! [1] === Search—Time Machine Edition === A few things from May that got missed: * Trey wrote up some potential applications of natural language processing (NLP) to on-wiki search [2]. We're still going through them to pick out a couple that we'll turn into projects, probably next quarter. Right now, spelling correction and entity extraction are high on the list, but more questions, comments, and suggestions are welcome. * Erik pulled 90 days worth of regular expression (regex) searches across all wikis, and Trey did a quick survey of the most common patterns. [3] There are a lot more regex searches than we thought—5.6 million in 90 days!—and three apparently automated processes (bots, apps, or tools of some kind) are responsible for more than 90% of the regex searches. [0] https://en.wikipedia.org/wiki/Stemming [1] https://phabricator.wikimedia.org/T190815 [2] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Potential_Applicatio… [3] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Survey_of_Regular_Ex… --- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

Re: [Wikitech-l] Gerrit as a shared community space
by Yaron Koren 11 Jun '18

11 Jun '18

Hi, Moriel Schottlender <mschottlender at wikimedia.org> wrote: > This isn't a personal attack, it's a consequence to your earlier email. > > You stated yourself, that one of the reasons you don't think a COC.md file > should exist in your repository is because not all interactions are covered > by it. While that might be true technically-speaking, it does make a > statement to potential contributors about what they might expect in terms > of feeling safe and secure with a CoC in place. > > For those of us who "bad interaction online" are a norm rather than an edge > case, a statement that the CoC is not fully covering a space means we don't > go to that space if we can help it. > > Saying that one does not intend on touching a space where the maintainer > clearly stated the CoC is only partially in effect is not a personal attack > -- it's a consequence of what you said. > A consequence that is also shared by others who may feel less comfortable > speaking up on public threads, but would avoid going into such spaces all > the same. Not because of who you are personally, but because of what your > statement about how your space is governed means. > > Whatever other claims and discussion is going on in this and the other > thread, let's not try to make it sound like there's a personal attack going > on here. No, I still think it's a personal attack. I think we've already established that the CoC does not cover all interactions, and that the CoC.md file is thus giving false information. Some people have stated that clearly, some have grudgingly admitted it, but no one has really argued against it. Even you note that it's "technically" true, whatever exactly that means. And of course, this file was put in place by a few developers - it wasn't an opt-in choice. (It's still not 100% clear that it's even an "opt-out" choice, though at this point it seems to be.) Given those two things, the presence of a CoC.md file in an extension directory tells a potential contributor nothing - nothing about additional security they're getting, and nothing really about the extension's developers. Actually, it's worse than nothing, because it gives potential contributors false comfort as far as the protections they'll have. If, as you say, some people face a real danger of harassment everywhere not covered by a code of conduct, then it's all the more reason to either remove that file, or reword it, everywhere - so people know what they're actually getting into. So, why should Amir want to avoid dealing with my code specifically? Is it because he would have fewer protections? Clearly, no. It must be something about me personally that would make him treat my code differently from everyone else's. -Yaron

2 5

Escaping wikitext to JSON-valid string in templates
by Tom Schulze 11 Jun '18

11 Jun '18

Hello everyone, I am having trouble escaping and displaying wikitext in a way that is JSON-safe. I did some research but none of the provided MagicWords/ParserFUnctions/etc seem to be suited for this purpose. Please refer to my gitLab snippet <https://gitlab.com/snippets/1723632> to see the sample code of the query, template and widget. My goal is to build up a structure like this using a widget (to load my custom JS), a cargo query and finally a template to display the items row by row: <div class="item" data-item='{"content":"data from a mediawiki form field"}'>Description</div> <div class="item" data-item='{"content":"data from a mediawiki form field"}'>Description</div> The data is taken from a PageForms textarea form field (the user can enter any data she wants). This piece of HTML gets parsed by a custom Java Script on page load for further processing. As soon as characters like single (') or double quotes (") appear, the whole JSON string gets messed up and the JavaScript JSON parser throws errors. Even worse, the DOM structure becomes fragmented when single quotes appear. So client-side fixing w/ JavaScript is impossible/tedious. Any solution is welcome, also restricting the types of characters used. Ideally, I would just need to wrap the parameter passed from the query to the template in some kind of Magic Word which escapes/strips out unwanted characters. What options do I have ? I am open for different approaches... Kind regards, Tom

1 0

Re: [Wikitech-l] Gerrit as a shared community space
by Yaron Koren 11 Jun '18

11 Jun '18

Hi, Amir Ladsgroup <ladsgroup at gmail.com> wrote: > One note particularly about this incident, I personally would be happy if > Yaron thought the wording is wrong, put the file back with a better > wording, like "gerrit part of development of this extension is covered by > the WM CoC". Maybe I'll do that, now that I know it's an option. > For me personally > and after this stuff, I wouldn't touch any code Yaron is developing outside > of gerrit with one-yard stick but I'm fine with making patches in gerrit in > his extensions because I know it's covered by CoC. This looks to me like a violation of the Code of Conduct. I don't want to cause more drama in this discussion, especially since it seems like a sort of consensus has formed and we can all move on, but I do find it disturbing that a member of the Code of Conduct Committee, who is tasked with enforcing the rules, is himself willing to engage in personal attacks. -Yaron

3 2

Gerrit as a shared community space
by Brion Vibber 10 Jun '18

10 Jun '18

Recent threads have demonstrated there seems to be some disconnect about what is expected about maintainership and ownership of repositories. This has spilled over into talk about the code of conduct, IMHO specifically because some people are trying to avoid being bound by it or protesting its existence by looking for loopholes to avoid it. Which I think is a shame, but I don't expect much constructive talk to come out of that thread. I think we should though clarify that code repositories on gerrit and diffusion are not owned by any one person, but are technical community spaces held in common for the benefit of the Wikimedia movement. And yes, that means sometimes your favorite project will get documentation commits you personally didn't like. If this has been unclear, it should be made clear. If that means some people host their self-maintained code outside of Wikimedia technical spaces, then that is their decision and I respect it. If some kind of official kerfluffle is needed to decide this, let's talk about how to do that. -- brion

9 14

Article 13 and the "censorship machine" for code
by Federico Leva (Nemo) 10 Jun '18

10 Jun '18

I guess this should be mentioned here at some point: Open Letter to Secure Free and Open Source Software Ecosystem in the EU Copyright Review https://savecodeshare.eu/ «Save Code Share: Current EU Copyright Review threatens Free and Open Source Software. Take action now to preserve the ability to collaboratively build software online!» Context on article 13: * https://saveyourinternet.eu/ * https://blog.wikimedia.org/2017/06/06/european-copyright-directive-proposal/ The next vote on the proposed EU copyright directive is on June 20. More broadly: https://meta.wikimedia.org/wiki/EU_policy/Statement_of_Intent Federico

1 0

(no subject)
by Liza Rustanto 10 Jun '18

10 Jun '18

-- FUSION ENTREPRISES GROUPS PTY LTD 2/14 Bloomfield Avenue MARIBYRNONG VIC 3032 Phone: (+61) 448 86 96 46 Fax: (+61)3 8679 0330 Email: info(a)fusionentreprises.com.co

1 0

?מה עושה אותך מאושר השבוע / What's making you happy this week? (Week of 10 June 2018)
by Pine W 09 Jun '18

09 Jun '18

Here are some highlights: * "Improved geocoding in CiviCRM", by Eileen McNaughton: https://blog.wikimedia.org/2018/06/05/improved-geocoding-in-civicrm/ * "Thank you week-end thread", with posts by hashar ( https://lists.wikimedia.org/pipermail/wikitech-l/2018-June/090126.html) and legoktm ( https://lists.wikimedia.org/pipermail/wikitech-l/2018-June/090142.html) * You may be familiar with the United Nations Sustainable Development Goals. WMF commented on a draft text that is being considered by UNESCO in regards to Sustainable Development Goal 4. You can read about SDG 4 at https://en.unesco.org/education2030-sdg4/targets and https://sustainabledevelopment.un.org/sdg4. Nichole Saad published WMF's comments about the draft document at https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Comment_on_the…. * "Rebuilding Wikimédia France", by Charlotte Matoussowsky: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-June/090413.html * "Stats re new users per gender per year in Hebrew Wikipedia", by Shani Evenstein Sigalov: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-June/090429.html. Asaf Bartov uploaded a screenshot of the data table here that may be easier to read: https://commons.wikimedia.org/wiki/File:User_gender_on_Hebrew_Wikipedia,_by… What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

Thank you week-end thread
by Antoine Musso 09 Jun '18

09 Jun '18

Hello, I had a lot of interactions this week with various people, specially since I have spamed a lot of mediawiki extensions with random patches. So this is my thank you thread to a few people, feel free to reply with your own thanks to others so we all get a nice week-end. Thank you Yaron Koren for starting a conversation about the code of conduct file and specially how it could be rephrased to better fit all use cases. That and other suggestions are going to improve our interactions. https://lists.wikimedia.org/pipermail/wikitech-l/2018-June/090086.html Marco Aurelio, who has been dramatically helping to archive a few outdated/no more working extensions. The workflow is nice, makes sure nothing get missed and he knows authors to contact to get a confirmation. http://phabricator.wikimedia.org/tag/cleanup is great! Stephan "Foxtrott" Gambke, co author of the Lingo extension https://www.mediawiki.org/wiki/Extension:Lingo If you don't know about it check it out, that let you defines a glossary of term quite easily with a mouse over popup on defined terms. He gracefully accepted a few fixes to the extension. Thank you everyone! -- Antoine "hashar" Musso

2 1

Re: [Wikitech-l] Can/should my extensions be deleted from the Wikimedia Git repository?
by Chris Koerner 08 Jun '18

08 Jun '18

> I for one think that requiring a specific filesystem structure or notice in > a git repo is quite far afield from the sorts of things that CoC is > designed to deal with. I agree. I do think that as a community of practice we have many unwritten rules and numerous expectations of how we work together. We don't explicitly define the expectation of a README.MD file in repos either.[0] It's a best practice and cultural expectation in our spaces to include one. The code works the same with or with out it. Yeah, sure a coc.md isn’t “the same”, but both are expected as something we do as a community. If we need to write that down somewhere so there's no repeat confusion on if it's expected or not, that seems like a good compromise. However, I'd like to think we don't have to define everything, but ¯\_(ツ)_/¯ . [0] I'm waiting for someone to contradict me on this risky comparison. :) I could not find anything explicit in https://www.mediawiki.org/wiki/Gerrit/New_repositories or https://www.mediawiki.org/wiki/Manual:Coding_conventions Yours, Chris K.

3 2

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l June 2018