User talk:CAPTAIN RAJU/Archive 16

{| width=100% cellpadding=12pt  Leave a message  Send an Email
 * colspan=3 style="border: 7px solid #FFA4FF; background-color: #C0FFFF; line-height:1.5" |

Tech News: 2016-25
 Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes
 * Notifications were not always marked as read when you followed a link from an email notification. This will now happen.

Changes this week
 * The list of other languages an article is available in will be shorter on small Wikipedias and non-Wikipedia projects. This is to make it easier to find the most relevant languages for each user. You will still be able to see the other languages.
 * Alerts (the red badge) will not be automatically marked as read when you open the Notifications popup.
 * When you get several thanks you can see them as one notification. This is instead of one notification for each thanks.
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 June. It will be on non-Wikipedia wikis and some Wikipedias from 22 June. It will be on all wikis from 23 June (calendar).

Meetings
 * Octicons-tools.svg You can join the next meeting with the Architecture committee. The topic this week is develop Markdown support strategy for MediaWiki. The meeting will be on 22 June at 21:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.  19:14, 20 June 2016 (UTC)

the Peewee ORM edit
Hi, I apologize if I was in violation of any terms of service.

I would like to clarify that the "complaints" are coming from one disgruntled user.

If this is going to not be a one-sided attack on me as a maintainer, then I think it is only fair to also reference that I responded to this one user's comments and questions many times before resorting to removing his comments.

Here are some examples where I gave technical or aesthetic justifications:


 * https://github.com/coleifer/peewee/pull/950
 * https://github.com/coleifer/peewee/issues/964
 * https://github.com/coleifer/peewee/issues/965
 * https://github.com/coleifer/peewee/pull/952#issuecomment-223105675
 * https://github.com/coleifer/peewee/issues/959

The comments I removed were all in later tickets:


 * https://github.com/coleifer/peewee/issues/983
 * https://github.com/coleifer/peewee/isdsues/986
 * https://github.com/coleifer/peewee/issues/980

I've maintained this project for 6+ years and have never had any issue except with this one individual.

The statement as it currently is, does not correctly represent the situation.

The truth is that I removed this one users comments because they were not constructive, and I was tired of having to defend aspects of my project because he felt entitled to a technical discussion because he happened to disagree with it. When I pointed out to him that the things he disagreed with were documented and obviously intentional (via git log), he suggested I was trying to justify, post-hoc, bad design decisions, and was being an irresponsible maintainer. How is that constructive?

Furthermore, how is this anything more than one disgruntled user's opinion? — Preceding unsigned comment added by 198.248.188.137 (talk) 21:40, 22 June 2016 (UTC)

Here are some comments from other users of the project:

arikfr noticed this as well:

> I follow Peewee for a long time now. I read every bug report, pull request, comment, etc. I never seen Charles react before like he has with you. Charles explained what bothered him with the issues you opened. You might not agree, but you shouldn't ignore that.

Here's another user on hackernews:

> Peewee [1] is my tool of choice because of its convenience and flexibility combined. I can create pretty complex queries using its Query API, but also execute arbitrary queries when I know I need something a little more nonstandard. Plus the maintainer (Charles Leifer) is an awesome dude who has always been really helpful to his users.

And another:

> PeeWee and the maintainer Charles Leifer are both very awesome. — Preceding unsigned comment added by 198.248.188.137 (talk) 21:05, 22 June 2016 (UTC)

Welcome to the Hall of Fame!
--Rosiestep (talk) 09:01, 23 June 2016 (UTC) via MassMessage (To subscribe, Women in Red/Invite list. Unsubscribe, Women in Red/Opt-out list)

UNCONSTRUCTIVE EPITHETS
Bit concerned about your edit. I used to work with female rally drivers and part of the competition was putting up with other female rally drivers' insults - at least you can let the victims lick their wounds. — Preceding unsigned comment added by Daniel Norton Smith II (talk • contribs) 16:15, 24 June 2016 (UTC)

fixing link.
Hi I noticed you fixed the second link for the Geoffrey Darby wikipedia, The first link needs fixing, Can you please fix the first link since I do not not how to fix the link.

Persian Gulf
Hi Raju,

the name of "Persian Gulf" is internatinally and legally recognized by all countries and United Nations (refer to UN website). Reference to any name other than "Persian Gulf" to the body of water is illegal. Wikipedia shall also use the legalized name of "Persian Gulf".

Regards — Preceding unsigned comment added by 37.36.212.11 (talk) 05:56, 25 June 2016 (UTC)

Hi 37.36.212.11,

I agree with you, that body of water should be called "Persian Gulf", but you're editing the name of a football league, that was named "Arabian Gulf" after a company called "ARABIAN GULF DEVELOPMENT (L.L.C)" for sponsorship reasons, I hope you come to your senses. Abdelaziz1889 (talk) 13:43, 25 June 2016 (UTC)

Tech News: 2016-26
 Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes
 * The ORES service has now moved to a new location. This should make it easier to use ORES. The ORES review service is now available as a beta feature on Wikidata and Persian Wikipedia. ORES is an artificial intelligence system for Wikimedia wikis to help editors.
 * The order of wikis in collapsed cross-wiki notifications was different than when the list was expanded. This is now fixed.
 * A new category for tracking pages with math errors was added:    :.

Problems
 * The Wikimedia Etherpad crashed on June 23. Some edits done that day have been lost. They can be found at etherpad-restore.wikimedia.org for another few days.

Changes this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 June. It will be on non-Wikipedia wikis and some Wikipedias from 29 June. It will be on all wikis from 30 June (calendar).
 * The way to mark notifications as read or unread will be changed to be more clear.

Meetings
 * Octicons-sync.svg You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 28 June at 19:00 (UTC). See how to join.

Future changes
 * The Collaboration team at the Wikimedia Foundation will look at developing better tools for edit review. This is because research suggests we scare away newcomers who want to help.
 * An e-mail from the Editing Department explains the technical work that is planned and being researched for the future. Items include better wikitext and visual editing, prompts for edits, language improvements, annotations, and meta-data separation.
 * The sorting of Notifications into the two fly-out menus is going to change on July 5 to 7. Bundled notifications should be easier to explore and mark as read individually.
 * Octicons-tools.svg From 29 June git.wikimedia.org (running Gitblit) will redirect all requests to Phabricator. The vast majority of requests should be correctly redirected.
 * Catalan and Polish Wikipedias will have Wikidata descriptions added to articles in the mobile view by default. This is currently a beta option for the mobile versions. This might come to other wikis later.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.  15:42, 27 June 2016 (UTC)

Wikidata weekly summary #215
Here's your quick overview of what has been happening around Wikidata over the last week.  Read the full report &middot; Unsubscribe &middot; Lydia Pintscher (WMDE) 16:48, 27 June 2016 (UTC)
 * Discussions
 * New request for comments: Verifiability and living persons, RfP voting eligibility
 * Events/Blogs/Press
 * Past: Wikimania! The Wikidata-related program parts including slides and notes can be found on the Wikidata Wikimania page.
 * TIB and HsH project approved: The replication of Open-Access images
 * Other Noteworthy Stuff
 * EasyQuery is now a gadget that you can enable in your preferences. It gives you an icon next to each statement value. That gives you a list of other items with the same statement.
 * Stats have been updated and show a significant jump in references.
 * SQID now shows references (example)
 * INSPIRE HEP has been added to Mix'n'match
 * PAWS is now available. It lets you easily run a Jupyter notebook and much more.
 * Did you know?
 * Newest properties: language used, connector, Encyclopedia of Triangle Centers identifier, INSPIRE-HEP author ID, lighthouse range, memory capacity, water as percent of area, InterPro ID, domain of saint or deity
 * Query examples: sandwich ingredients (source), inventors killed by their own invention (source), objects with most mass (source), music genres (source), number of jurisdictions by driving side (source)
 * Development
 * The majority of the Wikidata developers team atteded Wikimania
 * You can now embed query results from query.wikidata.org in other websites (example)
 * Linking MediaInfo entities to media files in the "MediaInfo for Commons" prototype (T134473)
 * Tracking more statistics for the ArticlePlaceholder (T138500)
 * Adding support for quantity values with unknown uncertainty (T115269)
 * Worked on fix for bug where new entities can be created with wrong language (T138725)
 * Monthly Tasks
 * Hack on one of these.
 * Help develop the next summary here!
 * Contribute to a Showcase item
 * Help translate or proofread pages in your own language!
 * Help merge identical items across Wikimedia projects.
 * Add labels, in your own language(s), for the new properties listed above.

Duduk
How is it not constructive? Rather than just making a change, give a reason. I reverted to the instrument's true name. HyeSK (talk) 19:34, 27 June 2016 (UTC)HyeSK

Hi Captain Raju, as you said I accept my mistakes. The problem is Iam new to this, and after doing some mistakes there I couldn't bring it back to normal. Anyway thanks for your advice and I will surely come with a next edit after knowing few more stuffs in sandbox. Thank You ! Regards, Ashwathy Sai — Preceding unsigned comment added by Ashwathysai (talk • contribs) 14:01, 28 June 2016 (UTC)

sock puppet allegation msg
I dont know really what your msg means but this is my first and only wiki account, do not appreciate the unwarranted accusation — Preceding unsigned comment added by W.C. Justice (talk • contribs) 18:59, 28 June 2016 (UTC)

Copyright question
Apologies for bothering you, sir, I'm sure you are terribly busy. I sent copyright verification about book covers for my series (File:THE_TRAVELLER_CHRONICLES_-_cover.pdf and File:Zak_Standridge_-_Traveller_-_Mr_Blue_-_Cover_2ND_EDITION.pdf. Just curious if this copyright release was sufficient as I haven't heard back. I don't want to make anything harder for Wikipedia and I would prefer if my work wasn't deleted. Thank you! ZakStandridge (talk) 21:26, 28 June 2016 (UTC)

The Cooper Associates County Ground
I wonder if you can help - We, as a business, have the naming rights to The County Ground in Taunton and as such the ground now needs to be referred to as 'The Cooper Associates County Ground'. Is this a change that can be done please? — Preceding unsigned comment added by 86.53.213.57 (talk) 08:10, 30 June 2016 (UTC)
 * ✅ – I have renamed the article and added a source for the name change. nyuszika7h (talk) 09:55, 30 June 2016 (UTC)

Editing News #2—2016
Editing News #2—2016 Read this in another language • Subscription list for this multilingual newsletter

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "" menu and click the "" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references.

Finally, click "" in the dialog to insert the. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "" and "" tabs into a single "" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes
The "" button will say "". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.
 * Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor?  Please sign up for the new VisualEditor Community Taskforce.
 * Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

Whatamidoing (WMF) (talk), 21:09, 30 June 2016 (UTC)

2016 GA Cup-Wrap Up
--MediaWiki message delivery (talk) 02:26, 2 July 2016 (UTC)

Help Me
Hello @CAPTIANRAJU, you have kept my page Suntalilai Bhagai Lagyo Jhilkele for Speedy Deletion. Please Remove this Page from Speedy Deletion. I will manage this article and improve it. So, Please Help me. — Preceding unsigned comment added by Dangerous Khiladi 5 (talk • contribs) 11:52, 2 July 2016 (UTC)

Coca-Cola Amatil changes
I added the letters BU to the page on Coca-Cola Amatiland you undid them. What I referred to here was the soft drink BU, from Papua New Guinea. I know exists because I lived in Papua New Guinea and it is verifiable by a web search or looking at Coca-Cola Amatil's website however I have no clue how one would Cite that 14.203.7.151 (talk) 05:08, 3 July 2016 (UTC).

Punjab edit-a-thon: Write for glory
Hello friend, A multilingual national-level edit-a-thon is being conducted at this moment with an aim to create or improve Punjab-related articles. A community that will create or expand the most number of articles during this edit-a-thon contest will be awarded a trophy during WikiConference India 2016. Best contributors' recognition may also be considered. We need your help here. Please join right now as a participant and help your community. Thanks and regards. --WikiConference India (2016) organizing team using MediaWiki message delivery (talk) 15:52, 3 July 2016 (UTC)

Click here to subscribe/unsubscribe.

Wikidata weekly summary #216
Here's your quick overview of what has been happening around Wikidata over the last week.  Read the full report &middot; Unsubscribe &middot; Lydia Pintscher (WMDE) 16:51, 4 July 2016 (UTC)
 * Events/Blogs/Press
 * Europeana280 Art History Challenge has finished
 * Europeana blog post
 * video
 * Wikimedia blog post
 * The life and times of Mr Herbert Ellerby: Linking Llandudno, Lancashire, and Moggill, Australia
 * Wikidata auf der GPN
 * Past: PSESHSF (You can sign up to be notified about more Wikidata workshops in France)
 * Past: Swiss Open Cultural Data Hackathon
 * Upcoming: office hour on IRC
 * Upcoming: State of the Map US in Seattle - http://stateofthemap.us/
 * Upcoming: Wikimedia UK AGM with Wikidata training
 * Other Noteworthy Stuff
 * There is now a 100wikidatadays challenge based on the 100wikidays challenge for Wikipedia. The goal: convert 100 templates to make use of Wikidata over the course of 100 days.
 * Tobias started writing a tutorial on how to write infoboxes that make use of Wikidata's data and could use your help expanding it.
 * Thiemo wrote a user script to pre-fill "date retrieved" in a reference with the current date. Please test and let us know what you think ont he linked page. If you like it it can become a gadget.
 * Did you know?
 * Newest properties: British Book Trade Index ID, Plarr ID, warheroes.ru ID, Dailymotion channel ID, Munk's Roll ID, Catalogus Professorum Rostochensium ID, CageMatch tag team ID, Pleiades place type identifier, parliamentary term
 * Query examples: Ancestors of Guðni Jóhannesson (note the last names), movies with Bud Spencer (source), largest cities per country (source), longest river of each continent (source), rivers in Antarctica (source), continents (source), and some other continents (source), places with continent Antarctica more than 3000 km north of south pole (source), files used as “image” in more than 10 items (source), monuments historiques in Loire-Atlantique (source), music composers by birth place (source), places of whorship (source), teachers with most students (source), buildings in more than one country (source), sandwiches (source), [https://query.wikidata.org/#%23%20Each%20composer%E2%80%99s%20most%20used%20tonality%2C%20with%20number%20of%20works%20in%20that%20tonality.%0A%23%20%28If%20this%20is%20ambiguous%20%E2%80%93%20multiple%20tonalities%20with%20the%20same%20number%20%E2%80%93%20there%20are%20multiple%20results%20for%20one%20composer.%29%0A%23%20%0A%23%20The%20SPARQL%20for%20this%20is%20an%20evil%20perversion%20of%20three%20subqueries%20%28one%20of%20them%20nested%20in%20another%29.%0A%23%20To%20understand%20it%2C%20you%20have%20to%20go%20inside%20out%E2%80%A6%20follow%20the%20numbers.%0A%0ASELECT%20%3FcomposerLabel%20%3FtonalityLabel%20%3Fcount%0AWHERE%0A%7B%0A%20%20%7B%0A%20%20%20%20%23%204.%20Group%20again%2C%20this%20time%20just%20by%20the%20composer.%0A%20%20%20%20%23%20%20%20%20We%20also%20select%20the%20highest%20count%20of%20a%20tonality.%0A%20%20%20%20%23%20%20%20%20Notice%20that%20we%20don%E2%80%99t%20know%20what%20tonality%20this%20count%20is%20associated%20with%20%E2%80%93%20we%E2%80%99ll%20get%20to%20that.%0A%20%20%20%20%23%20%20%20%20So%20now%20we%20have%20each%20composer%2C%20along%20with%20how%20often%20they%20used%20whatever%20tonality%20they%20used%20most.%0A%20%20%20%20SELECT%20%3Fcomposer%20%28MAX%28%3Fcount%29%20AS%20%3Fcount%29%0A%20%20%20%20WHERE%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%23%202.%20Group%20by%20composer%20and%20tonality%2C%20so%20that%20for%20each%20composer%20and%20tonality%2C%20we%20get%20a%20count%20of%20how%20often%20the%20composer%20used%20this%20tonality.%0A%20%20%20%20%20%20%20%20SELECT%20%3Fcomposer%20%3Ftonality%20%28COUNT%28%3Fcomposition%29%20AS%20%3Fcount%29%0A%20%20%20%20%20%20%20%20WHERE%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%23%201.%20Extremely%20straightforward%3A%20the%20%3Fcomposition%20has%20the%20composer%20%3Fcomposer%20and%20the%20tonality%20%3Ftonality.%0A%20%20%20%20%20%20%20%20%20%20%23%20%20%20%20%28I%E2%80%99m%20not%20bothering%20with%20any%20%E2%80%9Cinstance%20of%E2%80%9D%20because%20the%20presence%20of%20these%20two%20properties%20is%20a%20sufficient%20indicator%20of%20%3Fcomposition%20being%20a%20composition.%29%0A%20%20%20%20%20%20%20%20%20%20%3Fcomposition%20wdt%3AP86%20%3Fcomposer%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20wdt%3AP826%20%3Ftonality.%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20GROUP%20BY%20%3Fcomposer%20%3Ftonality%0A%20%20%20%20%20%20%20%20HAVING%28%3Fcount%20%3E%201%29%20%23%203.%20Limit%20that%20to%20counts%20%3E%201%2C%20because%20using%20a%20tonality%20once%20is%20hardly%20%E2%80%9Cmost%20used%E2%80%9D.%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%20%20GROUP%20BY%20%3Fcomposer%0A%20%20%7D%0A%20%20%7B%0A%20%20%20%20%23%206.%20Identical%20to%202.%0A%20%20%20%20SELECT%20%3Fcomposer%20%3Ftonality%20%28COUNT%28%3Fcomposition%29%20AS%20%3Fcount%29%0A%20%20%20%20WHERE%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%23%205.%20Identical%20to%201.%0A%20%20%20%20%20%20%3Fcomposition%20wdt%3AP86%20%3Fcomposer%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20wdt%3AP826%20%3Ftonality.%0A%20%20%20%20%7D%0A%20%20%20%20GROUP%20BY%20%3Fcomposer%20%3Ftonality%0A%20%20%20%20HAVING%28%3Fcount%20%3E%201%29%20%23%207.%20Identical%20to%203.%0A%20%20%7D%0A%20%20%23%208.%20That%E2%80%99s%20it.%20Wait%2C%20what%3F%0A%20%20%23%20%20%20%20From%204%2C%20we%20now%20have%20%3Fcomposer%2C%20any%20composer%2C%20and%20%3Fcount%2C%20the%20count%20of%20how%20often%20they%20used%20whatever%20tonality%20they%20used%20most.%0A%20%20%23%20%20%20%20From%206%2C%20we%20also%20have%20a%20%3Fcomposer%2C%20as%20well%20as%20a%20%3Ftonality%2C%20and%20the%20count%20of%20how%20often%20they%20used%20that%20particular%20tonality.%0A%20%20%23%20%20%20%20The%20trick%20is%20that%20%3Fcomposer%20and%20%3Fcount%20are%20the%20same%20variable%20in%20each%20subquery%2C%20and%20so%20now%2C%20when%20the%20two%20subqueries%20are%20joined%2C%0A%20%20%23%20%20%20%20we%20select%20only%20that%20%3Ftonality%20from%206%20where%20the%20%3Fcomposer%20and%20the%20%3Fcount%20are%20identical%20to%20those%20from%204%20%E2%80%93%0A%20%20%23%20%20%20%20that%20is%2C%20where%20this%20tonality%20was%20used%20as%20often%20as%20the%20composer%E2%80%99s%20most-used%20tonality.%0A%20%20%23%20%20%20%20In%20other%20words%2C%20this%20must%20%2abe%2a%20the%20composer%E2%80%99s%20most-used%20tonality%20%28except%20when%20there%20are%20multiple%20tonalities%20with%20the%20same%20count%29.%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22.%20%7D%0A%7D%0AORDER%20BY%20DESC%28%3Fcount%29%20%23%209.%20Order%20by%20count%20%28highest%20first%29%2C%20because%20the%20result%20isn%E2%80%99t%20very%20meaningful%20for%20low%20counts%20%28many%20compositions%20aren%E2%80%99t%20on%20Wikidata%20or%20don%E2%80%99t%20have%20a%20tonality%20statement%29. composers and their most-used tonality] (source), former capitals (source), list of suicide attacks (source), birthplaces of people named Antoine (source), ||%0A%20%20%20%20%20%20%20%20%20%28%3Fel%20%3C%20%3Fkm*3281%20%26%26%20%3Funit%20%3D%20wd%3AQ3710%29%0A%20%20%20%20%20%20%20||%20%28%3Fel%20%3C%20%3Fkm%20%26%26%20%3Funit%20%3D%20wd%3AQ828224%29%20%29.%20%0A%20%20%3Fp%20wdt%3AP625%20%3Flocation.%0A%20%20optional%20%7B%20%3Fp%20wdt%3AP18%20%3Fimage%20%7D%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20%7D%0A%7D%0A places that are below 10 meters above sea level (source)
 * Newest WikiProjects: Etymology, Knowledge Organization Systems
 * Newest external tools: Navel Gazer (users statement addition counts)
 * Development
 * More groundwork for Commons. We can now save a statement in the new MediaInfo entity type \o/ (Some minor issues still with the demo system but should be solved next week.)
 * Fixed a display issue with description tooltips in recent changes. Thanks Matěj Suchánek! (T89663)
 * Refactored quite some of the sitelinks-related JavaScript code (T127056 and 294687. This may break some existing gadgets and user scripts temporarily.
 * Updated the graphic representing the data model in Wikidata: long, medium, short
 * Fixed problem with editing statements on Wikidata, after last week's deployment (T138974)
 * Started interviews to find user needs and workflows for automated list generation (T139284)
 * Monthly Tasks
 * Hack on one of these.
 * Help develop the next summary here!
 * Contribute to a Showcase item
 * Help translate or proofread pages in your own language!
 * Help merge identical items across Wikimedia projects.
 * Add labels, in your own language(s), for the new properties listed above.

The Signpost: 04 July 2016
 * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 18:47, 4 July 2016 (UTC)

Tech News: 2016-27
 Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes
 * A daily email summary of notifications could be sent even when there were no notifications from the wiki. Now no email will be sent if there is no activity.

Changes this week
 * The "" button in the visual editor's toolbar will move into the "" menu except for Wikipedias, Wikibookses and Wikiversities. This is to make it less prominent on wikis that don't use it as much.
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 July. It will be on non-Wikipedia wikis and some Wikipedias from 6 July. It will be on all wikis from 7 July (calendar).

Meetings
 * You can take part in the next office hour for Wikidata on IRC on July 8 at 16:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.  19:45, 4 July 2016 (UTC)