VisualEditor/Survey 2015/nl

Het Editing team vraagt u hulp voor het verbeteren van de visuele tekstbewerker. Het team heeft een lijst van grote problemen gemaakt, maar zij willen ook op de hoogte zijn van kleine problemen. Deze problemen kunnen het bewerken minder leuk maken, veel te veel tijd van uw tijd vragen, of net zo irritant zijn als het snijden in uw vingers. Kleine problemen kunnen niet belangrijk genoeg lijken om er een bugrapport voor in te dienen, maar zij willen ook de kleine problemen oplossen.

Ze nemen nu contact op met verschillende gebruikers, en vragen u om om deze enquête in te vullen.

De snelle, simpele en anonieme enquête wordt afgenomen via Qualtrics. U mag de enquête in uw eigen taal invullen. Als u deze enquête invult, gaat u ermee akkoord dat uw ingevulde antwoorden gebruikt kunnen worden zoals beschreven in dit document. De enquête wordt afgenomen via Qualtrics, and hoe zij uw informatie gebruiken is bepaald in hun privacybeleid. Als u nog vragen heeft, of liever on-wiki reageert, laat dan alstublieft een bericht achter op de overlegpagina. De inhoud van de gehele enquête is aan het einde van deze pagina beschikbaar.

De gegevens die u deelt zullen worden gebruikt om de visuele tekstbewerker te verbeteren. Een link naar de resultaten van de enquête zal aan het einde op deze pagina worden geplaatst.

Introductie
Deze enquête wordt afgenomen in opdracht van de Wikimedia Foundation om meer te weten te komen over de ervaringen van gebruikers van de visuele tekstbewerker op Wikipedia en andere projecten. De visuele tekstbewerker is een zogenaamde "rich-text editor" waarmee artikelen bewerkt kunnen worden zonder kennis van de wikicode-opmaak.



De schermafbeeldingen komen van het artikel "Galaxy" op de Engelstalige Wikipedia. De eerste schermafbeelding (links) laat de visuele tekstbewerker zien in bewerkmodus. De tweede schermafbeelding (rechts) laat de wikitekstbewerker zien in bewerkmodus (ditmaal ook op het artikel "Galaxy").

''U gaat ermee akkoord dat uw ingevulde gegevens gebruikt kunnen worden in overeenstemming met dit privacybeleid. De enquête wordt mede mogelijk gemaakt door Qualtrics, en zij gebruiken uw informatie in overeenstemming met hun privacybeleid. Voor licenties en naamsvermelding voor de bijbehorende schermafbeeldingen, zie https://en.wikipedia.org/wiki/Galaxy.''

Vragen

 * 1) Als eerste, aan welk project draagt u het meeste bij?
 * 2) * Wikipedia
 * 3) * Commons
 * 4) * MediaWiki
 * 5) * Wikibooks
 * 6) * Wikidata
 * 7) * Wikinews
 * 8) * Wikiquote
 * 9) * Wikiversity
 * 10) * Wikivoyage
 * 11) * Een ander project gesponsord door de Wikimedia Foundation
 * 12) * Ik draag meestal niet bij aan enig Wikimedia Foundation-project.
 * 13) Hoe vaak gebruikt u de visuele tekstbewerker wanneer u artikelen bewerkt? (on a scale of 0% to 100%)
 * 14) * Never (0%)
 * 15) * (10% to 90%)
 * 16) * Always (100%)
 * 17) Hoe waarschijnlijk is het dat u de visuele tekstbewerker aan een nieuwe bewerker aanraadt? (op een schaal van 0 tot 10)
 * 18) * Ik raad altijd de wikitekstbewerker aan. (0)
 * 19) * (1 to 9)
 * 20) * Ik raad altijd de visuele tekstbewerker aan. (10)
 * 21) Kies wat van toepassing is:
 * 22) * In het verleden heb ik vaak de visuele tekstbewerker gebruikt, maar meestal gebruik ik nu de wikitekstbewerker.
 * 23) * Ik heb geprobeerd om de visuele tekstverwerker te gebruiken, maar meestal heb ik de veranderingen nooit opgeslagen.
 * 24) * Soms begin ik met bewerken in de visuele tekstbewerker, maar daarna gebruik ik de wikitekstbewerker weer.
 * 25) * Ik heb terugkoppelingen over de visuele tekstbewerker op de wiki achtergelaten op pagina's zoals VisualEditor/Feedback.
 * 26) * Ik heb bugs gerapporteerd, of ben geabonneerd op bugs in Bugzilla en Phabricator.
 * 27) * Geen van bovenstaande
 * 28) In de visuele tekstbewerker vind ik het gebied dat de meeste verbeteringen moet krijgen...
 * 29) * Citaten toevoegen of veranderen
 * 30) * Afbeeldingen en andere media
 * 31) * Algemeen
 * 32) * Ondersteuning voor andere talen dan Engels
 * 33) * Sjablonen toevoegen en bewerken
 * 34) * Prestaties en snelheid
 * 35) * Making or editing links to other pages and other websites
 * 36) * Kopiëren en plakken
 * 37) * Having discussions with other editors
 * 38) * Switching back and forth between VisualEditor and wikitext editor
 * 39) * Categorieën plaatsen en aanpassen
 * 40) * Having two edit buttons rather than the software remembering which I like to use
 * 41) * Handling edit conflicts without showing me wikitext
 * 42) * Showing me diffs and the history of articles visually
 * 43) * Formulæ, imagemaps, timelines or other special content types
 * 44) * Stability and reliability
 * 45) * Anders
 * 46) I would like to see improvements to this area (the one selected in the previous question).  If I could make one change to this area, I would change...
 * 47) Hoe bent u de enquête tegengekomen?
 * 48) * Een bericht op mijn overlegpagina
 * 49) * Een bericht op de overlegpagina van iemand anders
 * 50) * From another page on wiki
 * 51) * Email
 * 52) * Anders
 * 53) Optioneel: in het geval dat we nog vragen hebben over uw opmerkingen en suggesties, kunt u uw gebruikersnaam achterlaten, zodat we contact met u kunnen opnemen. Als u dat wenst, kunt u ook nog een link naar uw thuiswiki toevoegen. (Voorbeeld: User:MijnGebruikersnaam at nl.wikipedia.org)

Results
1,639 invitations were sent, including some duplicates due to contacting a few dozen people via e-mail (from Bugzilla accounts, which are not associated with wiki accounts). As of 17 April 2015, 508 surveys had been completed in Qualtrics and two on wiki.

First, to which project do you contribute most often?
There were 501 responses to this question.

How frequently do you use VisualEditor when you are editing articles?
There were 452 responses to this question. The mean was using VisualEditor for 40% of article editing, and the standard deviation was 30%. The answers were mostly evenly distributed, with clusters among people who almost never used VisualEditor and also editors who almost always used it.

How likely are you to recommend VisualEditor to a new editor? (on a scale of 0 to 10)
There were 449 responses to this question. The mean was 60% with a standard deviation of 30%.

This answer correlated very strongly (p=<0.0001) with whether the respondent uses VisualEditor frequently.

Choose all that apply:
There were 453 responses to this question.

In VisualEditor, the area that needs the most improvement is...
There were 433 responses to this question.

The order of the items (except "Other") were randomized, so that different people saw different items at the top of the list. The most popular choice was "Adding and editing templates", followed by "Switching back and forth between VisualEditor and wikitext editor", "Adding or editing citations or references", and "Performance and speed". Responses were correlated with how much the participant uses VisualEditor. People who use VisualEditor for most of their editing were most interested in improved support for citations, such as the automatic reference filler Citoid, rich copying and pasting, and special content types, such as mathematical formulae. People who never or rarely use VisualEditor were more interested in performance and reliability as well as general or non-software issues; they were comparatively uninterested in template or citation support within VisualEditor.

If I could make one change to this area, I would change...
There were 300 responses to this question.

Overall: Editors who use VisualEditor frequently have different concerns compared to those who use it rarely or never. Among those who commented, VisualEditor was considered superior for writing, copyediting, and editing tables (except for tables generated from templates). Several complex workflows, especially involving templates and citations, were areas of concern for people who use VisualEditor dozens or hundreds of times in a month. Editors who rarely or never use VisualEditor are more interested in the quality of Parsoid's conversion of the HTML that VisualEditor uses into wikitext, in the ability to switch to the wikitext editor, or general performance. Some users would like to see it enabled in talk namespaces or in the project namespace. A couple of respondents used the suggestion field to say that other editors should not be allowed to use VisualEditor, or that using VisualEditor would block the personal growth of new editors.

User interface: Some of the issues reported stem from a lack of familiarity with VisualEditor's features. For example, although a majority of respondents said that they sometimes switch from VisualEditor to the wikitext editor, a few believed that this feature did not exist. A few others believed that it was not possible to insert or edit new templates. These features may not be sufficiently prominent, or editors may benefit from a GuidedTour of the interface to point out the location of these items, such as the one proposed in T89074. Several editors said that making and editing internal and external links is confusing. The Design Research team has also identified this as an area of concern in user testing before the survey started, and improvements are being tested now.

Citations:  Most of the concerns about citations are being or will be resolved by the Citoid system, by better local TemplateData, and/or by improvements to the template system overall. Some changes, such as the ability to name citations, would need to be made in VisualEditor. Some other suggestions, like better support for page numbers and nested citations, may need to be handled through changes to the Cite extension. Requests included support for wikis'   templates. Templates that contain or display references can be inserted and viewed in VisualEditor. However, their contents do not update during an editing session, because this would significantly harm performance. Changes to citations immediately appear if the page is using MediaWiki's faster, simpler, native  tag; however, that tag does not currently support column formatting. Respondents also recommended being able to edit a citation by clicking on the citation in the references list, a planned VisualEditor feature.

Local issues: Some editors said that VisualEditor is less convenient because parameters they commonly use are not present in, or not correctly prioritized in, the TemplateData. The options automatically presented inside the template dialog are controlled on-wiki by the community, rather than in VisualEditor. For example, in a  template, whether the newspaper parameter is added by default depends upon whether that parameter is marked as either " " or " " in that template’s TemplateData on the local wiki.

Performance:  Lost-work bugs and slow performance were significant concerns for some editors, especially editors who have older or slower computers, or who teach editing to people who do. Performance has been improved significantly since the survey started, and more work is planned, which should address these concerns.

Other recurring requests: Except for the last two, most of these are already planned or are being strongly considered. Section editing does not reduce edit conflicts and paradoxically would not improve loading times in VisualEditor. Instead, the team is working on a long-term plan making it possible for editors to modify individual pieces of a page, like a table or a paragraph, rather than whole sections at once. The team is not planning to provide built-in spelling or grammar checking, as it is unlikely that a spell checker inside VisualEditor could work as well as or as quickly as the ones editors already have in their web browsers.
 * Better special character support, especially for inserting pairs (e.g., German-style quotation marks); met since the survey was started.
 * Better support for copying and pasting citations between articles
 * In situ editing of the contents of templates like infoboxes
 * Bi-directional switching between editing environments
 * Support for Internet Explorer 9
 * Fewer "dirty diffs" (awkward changes to wikitext that do not affect the page's appearance)
 * The ability to upload images to Commons, or the local wiki, within VisualEditor
 * Section editing
 * Built-in spell check

How did you hear about this survey?
423 people answered this question. 82% said that they received an invitation on their own talk pages. 9% received an invitation through e-mail. 6% found the link to the survey on someone else's talk page. 2% chose "Other", and about half of them said that they received the message either on wiki or in e-mail, e.g., e-mail messages to the translator's mailing list. One person found the link on another wiki page.

Languages
Almost all invitations were delivered in English. Almost 40% of the survey respondents took the survey in a language other than English. People who took the survey in English, French, or German were more likely to have used VisualEditor reqularly in the past, but not currently. People who took the survey in English or German were more likely to have exited without saving or to switch to the wikitext editor during an edit. Participants taking the survey in English were much more likely to have provided feedback or reported bugs.

Newly tracked bugs

 * T97323: Improve tabbing in template dialog