User talk:The wub/archive50

Archives

2005: J F M A M J J A S O N D

2006: J F M A M J J A S O N D

2007: J F M A M J J A S O N D

2008: J F M A M J J A S O N D

2009: J F M A M J J A S O N D

2010: J F M A M J J A S O N D

2011: J F M A M J J A S O N D

2012: J F M A M J J A S O N D

2013: J F M A M J J A S O N D

2014: J F M A M J J A S O N D

2015: J F M A M J J A S O N D

VisualEditor News #2—2015

Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:

Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:

After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).

Looking ahead

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.

Let's work together

Share your ideas and ask questions at mw:VisualEditor/Feedback.
Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
The design research team wants to see how real editors work. Please sign up for their research program.
File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite 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. Thank you!

-Whatamidoing (WMF) (talk), 17:50, 3 April 2015 (UTC)[reply]

WikiProject X Newsletter • Issue 3

Greetings! For this month's issue...

We have demos!

After a lengthy research and design process, we decided for WikiProject X to focus on two things:

A WikiProject workflow that focuses on action items: discussions you can participate in and tasks you can perform to improve the encyclopedia; and
An automatically updating WikiProject directory that gives you lists of users participating in the WikiProject and editing in that subject area.

We have a live demonstration of the new WikiProject workflow at WikiProject Women in Technology, a brand new WikiProject that was set up as an adjunct to a related edit-a-thon in Washington, DC. The goal is to surface action items for editors, and we intend on doing that through automatically updated working lists. We are looking into using SuggestBot to generate lists of outstanding tasks, and we are looking into additional options for automatic worklist generation. This takes the burden off of WikiProject editors to generate these worklists, though there is also a "requests" section for Wikipedians to make individual requests. (As of writing, these automated lists are not yet live, so you will see a blank space under "edit articles" on the demo WikiProject. Sorry about that!) I invite you to check out the WikiProject and leave feedback on WikiProject X's talk page.

Once the demo is sufficiently developed, we will be working on a limited deployment on our pilot WikiProjects. We have selected five for the first round of testing based on the highest potential for impact and will scale up from there.

While a re-designed WikiProject experience is much needed, that alone isn't enough. A WikiProject isn't any good if people have no way of discovering it. This is why we are also developing an automatically updated WikiProject directory. This directory will surface project-related metrics, including a count of active WikiProject participants and of active editors in that project's subject area. The purpose of these metrics is to highlight how active the WikiProject is at the given point of time, but also to highlight that project's potential for success. The directory is not yet live but there is a demonstration featuring a sampling of WikiProjects.

Each directory entry will link to a WikiProject description page which automatically list the active WikiProject participants and subject-area article editors. This allows Wikipedians to find each other based on the areas they are interested in, and this information can be used to revive a WikiProject, start a new one, or even for some other purpose. These description pages are not online yet, but they will use this template, if you want to get a feel of what they will look like.

We need volunteers!

WikiProject X is a huge undertaking, and we need volunteers to support our efforts, including testers and coders. Check out our volunteer portal and see what you can do to help us!

As an aside...

Wouldn't it be cool if lists of requested articles could not only be integrated directly with WikiProjects, but also shared between WikiProjects? Well, we got the crazy idea of having experimental software feature Flow deployed (on a totally experimental basis) on the new Article Request Workshop, which seeks to be a place where editors can "workshop" article ideas before they get created. It uses Flow because Flow allows, essentially, section-level categorization, and in the future will allow "sections" (known as "topics" within Flow) to be included across different pages. What this means is that you have a recommendation for a new article tagged by multiple WikiProjects, allowing for the recommendation to appear on lists for each WikiProject. This will facilitate inter-WikiProject collaboration and will help to reduce duplicated work. The Article Request Workshop is not entirely ready yet due to some bugs with Flow, but we hope to integrate it into our pilot WikiProjects at some point.

Harej (talk) 00:57, 19 April 2015 (UTC)[reply]

WikiCup 2015 May newsletter

The second round one has all wrapped up, and round three has now begun! Congratulations to the 34 contestants who have made it through, but well done and thank you to all contestants who took part in our second round. Leading the way overall was Cas Liber (submissions) in Group B with a total of 777 points for a variety of contributions including Good Articles on Corona Borealis and Microscopium - both of which received the maximum bonus.

Special credit must be given to a number of high importance articles improved during the second round.

Coemgenus (submissions) was one of several users who worked on improving Ulysses S. Grant. Remember, you do not need to work on an article on your own - as long as each person has completed significant work on the article during 2015, multiple competitors can claim the same article.
Cwmhiraeth (submissions) took Dragonfly to Good Article for a 3x bonus - and if that wasn't enough, they also took Damselfly there as well for a 2x bonus.
LeftAire (submissions) worked up Alexander Hamilton to Good Article for the maximum bonus. Hamilton was one of the founding fathers of the United States and is a level 4 vital article.

The points varied across groups, with the lowest score required to gain automatic qualification was 68 in Group A - meanwhile the second place score in Group H was 404, which would have been high enough to win all but one of the other Groups! As well as the top two of each group automatically going through to the third round, a minimum score of 55 was required for a wildcard competitor to go through. We had a three-way tie at 55 points and all three have qualified for the next round, in the spirit of fairness. The third round ends on June 28, with the top two in each group progressing automatically while the remaining 16 highest scorers across all four groups go through as wildcards. Good luck to all competitors for the third round! Figureskatingfan (talk · contribs · email), Miyagawa (talk · contribs · email) and Sturmvogel 66 (talk · contribs · email) 16:53, 4 May 2015 (UTC)[reply]

VisualEditor News #3—2015

Did you know?

When you click on a link to an article, you now see more information:

The link tool has been re-designed:

There are separate tabs for linking to internal and external pages.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

Share your ideas and ask questions at mw:VisualEditor/Feedback.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite 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. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)[reply]

WikiProject X Newsletter • Issue 4

Newsletter • May/June 2015

Hello friends! We have been hard at work these past two months. For this report:

The directory is live!

For the first time, we are happy to bring you an exhaustive, comprehensive WikiProject Directory. This directory endeavors to list every single WikiProject on the English Wikipedia, including those that don't participate in article assessment. In constructing the broadest possible definition, we have come up with a list of approximately 2,600 WikiProjects. The directory tracks activity statistics on the WikiProject's pages, and, for where it's available, statistics on the number of articles tracked by the WikiProject and the number of editors active on those articles. Complementing the directory are description pages for each project, listing usernames of people active on the WikiProject pages and the articles in the WikiProject's scope. This will help Wikipedians interested in a subject find each other, whether to seek feedback on an article or to revive an old project. (There is an opt-out option.) We have also come up with listings of related WikiProjects, listing the ten most relevant WikiProjects based on what articles they have in common. We would like to promote WikiProjects as interconnected systems, rather than isolated silos.

A tremendous amount of work went into preparing this directory. WikiProjects do not consistently categorize their pages, meaning we had to develop our own index to match WikiProjects with the articles in their scope. We also had to make some adjustments to how WikiProjects were categorized; indeed, I personally have racked up a few hundred edits re-categorizing WikiProjects. There remains more work to be done to make the WikiProject directory truly useful. In the meantime, take a look and feel free to leave feedback at the WikiProject X talk page.

Stuff in the works!

What have we been working on?

A new design template—This has been in the works for a while, of course. But our goal is to design something that is useful and cleanly presented on all browsers and at all screen resolutions while working within the confines of what MediaWiki has to offer. Additionally, we are working on designs for the sub-components featured on the main project page.
A new WikiProject talk page banner in Lua—Work has begun on implementing the WikiProject banner in Lua. The goal is to create a banner template that can be usable by any WikiProject in lieu of having its own template. Work has slowed down for now to focus on higher priority items, but we are interested in your thoughts on how we could go about creating a more useful project banner. We have a draft module on Test Wikipedia, with a demonstration.
New discussion reports—We have over 4.8 million articles on the English Wikipedia, and almost as many talk pages as well. But what happens when someone posts on a talk page? What if no one is watching that talk page? We are currently testing out a system for an automatically-updating new discussions list, like RFC for WikiProjects. We currently have five test pages up for the WikiProjects on cannabis, cognitive science, evolutionary biology, and Ghana.
SuggestBot for WikiProjects—We have asked the maintainer of SuggestBot to make some minor adjustments to SuggestBot that will allow it to post regular reports to those WikiProjects that ask for them. Stay tuned!
Semi-automated article assessment—Using the new revision scoring service and another system currently under development, WikiProjects will be getting a new tool to facilitate the article assessment process by providing article quality/importance predictions for articles yet to be assessed. Aside from helping WikiProjects get through their backlogs, the goal is to help WikiProjects with collecting metrics and triaging their work. Semi-automation of this process will help achieve consistent results and keep the process running smoothly, as automation does on other parts of Wikipedia.

Want us to work on any other tools? Interested in volunteering? Leave a note on our talk page.

The WikiProject watchers report is back!

The database report which lists WikiProjects according to the number of watchers (i.e., people that have the project on their watchlist), is back! The report stopped being updated a year ago, following the deactivation of the Toolserver, but a replacement report has been generated.

Until next time, Harej (talk) 22:20, 17 June 2015 (UTC)[reply]