User talk:Ged UK/Archives/2015/August

This is an archive of past discussions about User:Ged UK. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Kibana as non-notable software?

Latest comment: 9 years ago2 comments2 people in discussion

I was rather surprised by this deletion.

I know and understand the premise for deleting web pages documenting non-notable software, but this seems a bit overreaching in the case of Kibana (note: I am not affiliated with Kibana, Elasticsearch, Elastic.co, or any of their partners).

Kibana is a tool that has been around for some time know, which is regularly maintained. It is also deployed in many enterprise environments. It is isn't non-notable, by any means.

Google shouts back at least 427,000 results for Kibana alone (though these include hits for the Japanese station). The Kibana image on the Docker registry as been downloaded 51,695 times (and this is only a minimal indicator of its total download count, as I wouldn't expect the vast majority of Kibana users to deploy it as Docker containers). The entire ELK stack itself is in use at Wikimedia (https://wikitech.wikimedia.org/wiki/Logstash, though granted that doesn't either guarantee "notability" in itself).

While log management and log analysis may not be the most documented field of sofware and sysadmin, it is a recurrent topic, with some dedicated pages on Wikipedia (https://en.wikipedia.org/wiki/Log_management, https://en.wikipedia.org/wiki/Log_analysis). A more productive editing or housekeeping would be to flesh out these pages and update them, rather than deleting the page of one of the actors in this area. — Preceding unsigned comment added by 164.177.29.102 (talk) 15:00, 3 August 2015 (UTC)

The issue is, those aren't the criteria that Wikipedia uses to assess notability. We need independent coverage in reliable, third party sources. These may exist in this case, but there wasn't any indication of it. Ged UK 10:46, 4 August 2015 (UTC)

The Signpost: 05 August 2015

Latest comment: 9 years ago1 comment1 person in discussion

Editorial: Wikipedia better equipped to deal with systemic bias than traditional publishers

Op-ed: Je ne suis pas Google

News and notes: VisualEditor, endowment, science, and news in brief

WikiProject report: Meet the boilerplate makers

In the media: Probe into Nehru edits launched; dangers of the right to be forgotten

Traffic report: Mrityorma amritam gamaya...

Featured content: Maya, Michigan, Medici, Médée, and Moul n'ga

Blog: Get help editing Wikipedia with the new “Co-op” mentorship program

VisualEditor News #4—2015

Latest comment: 9 years ago1 comment1 person in discussion

Read this in another language • Local subscription list • Subscribe to the multilingual edition

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

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

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.

In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

Future changes

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together

Share your ideas and ask questions at Wikipedia:VisualEditor/Feedback.
Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
The design research team wants to see how real editors work. Please sign up for their research program.
The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact Elitre directly, so that she can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 00:01, 8 August 2015 (UTC)

Requested move of Damián Martínez

Latest comment: 9 years ago2 comments2 people in discussion

Please see Talk:Damián Martínez#Requested move 11 August 2015. You imposed move protection last February and I didn't want to perform the technical move until the reason for that can be addressed. Thanks, EdJohnston (talk) 16:47, 11 August 2015 (UTC)

@EdJohnston: Hey there. I've replied on the talk page. I didn't apply the move protection, it was already on when I semi protected the editing rights. Ricky81682 applied the move protection in Dec 2014. Ged UK 18:00, 12 August 2015 (UTC)