VisualEditor/Survey 2015/tr

Düzenleme ekibi GörselEditör'ü geliştirmek için yardımınızı istiyor. Ekibin yüksek önem taşıyan sorunlar listesi mevcut, ancak küçük sorunları da bilmek istiyorlar. Bunlar düzenlemenin eğlencesini kaçıran, çok fazla vakit alan veya kağıt kesiği gibi rahatsız eden sorunlar olabilir. Küçük sorunlar hata bildirilecek kadar önemli görünmeyebilir, fakat Düzenleme ekibi bunlar hakkında da bilgilenmeyi ve bunları da düzeltmeyi istiyorlar.

Çeşitli türden kullanıcılarla iletişim kuruyorlar ve sizin de düşüncelerinizi buraya tıklayarak bildirmenizi istiyorlar.

Hızlı, basit ve anonim olan anket, Qualtrics aracılığıyla yapılıyor. Kendi dilinizde de cevaplayabilirsiniz. Eğer ankete katılırsanız, cevaplarınızın bu şartlar altında kullanılabileceğini kabullenmiş olursunuz. Bu anket Qualtrics tarafından düzenlenmiş olup, sizin bilgilerinizin kullanımı kendi gizlilik politikasına göre şekillenir. Eğer sorunuz varsa veya wiki üzerinden cevaplamayı tercih ederseniz, lütfen tartışma sayfasına mesaj yazın. Anketin tamamı aşağıdadır.

Bilgilerin tamamı GörselEditör'ün fonksiyon ve tasarımını geliştirmek için kullanılacaktır. Sonuçların bağlantısı bu sayfada yayınlanacaktır.

Giriş
This survey is being conducted by the Wikimedia Foundation to learn more about community members' experience with VisualEditor on Wikipedia and related projects. VisualEditor is a rich-text editor that makes it possible to edit Wikipedia and other projects without first learning wikitext markup.



These screenshots were taken from the English Wikipedia article, "Galaxy". The first screenshot (on the left) shows the article open for editing in VisualEditor. The second screenshot (on the right) shows the same article open for editing in the wikitext editor.

'' You agree your responses may be used in accordance with these terms. This survey is powered by Qualtrics and their use of your information is governed by their privacy policy. For licensing and attribution of the screenshots, see https://en.wikipedia.org/wiki/Galaxy. ''

Sorular

 * 1) İlk olarak, hangi projeye daha çok katkıda bulunuyorsunuz?
 * 2) * Vikipedi
 * 3) * Commons
 * 4) * MediaWiki
 * 5) * Vikikitap
 * 6) * Wikidata
 * 7) * Wikinews
 * 8) * Wikiquote
 * 9) * Wikiversity
 * 10) * Vikigezgin
 * 11) * Wikimedia Vakfının sponsorluğundaki başka bir projede
 * 12) * Normalde Wikimedia Vakfı projelerine katkıda bulunmuyorum.
 * 13) Maddeleri düzenlerken hangi sıklıkta GörselEditör'ü kullanıyorsunuz? (%0 ile %100 arasında)
 * 14) * Asla (%0)
 * 15) * (%10 - %90)
 * 16) * Her zaman (%100)
 * 17) GörselEditör'ü hangi sıklıkta yeni editörlere tavsiye ediyorsunuz? (0 ile 10 arasında)
 * 18) * Her zaman vikimetin editörünü tavsiye ederim. (0)
 * 19) * (1 - 9)
 * 20) * Her zaman GörselEditör'ü tavsiye ederim. (10)
 * 21) Size uyanların hepsini seçin:
 * 22) * Geçmişte GörselEditör'ü kullandım ancak artık genellikle vikimetin editörünü kullanıyorum.
 * 23) * GörselEditör'ü kullanmaya çalıştım ancak sıklıkla sayfadaki değişiklikleri kaydetmeden sayfayı kapattım.
 * 24) * Bazen GörselEditör ile düzenlemeye başlıyorum ancak sonrasında vikimetin editçrüne geçiş yapıyorum.
 * 25) * GörselEditör hakkında wikideki VisualEditor/Feedback gibi sayfalarda geribildirimlerde bulundum.
 * 26) * Hata raporlamasında bulundum veya Bugzilla ya da Phabricator'daki hatalara aboneyim.
 * 27) * Yukarıdakilerin hiçbiri
 * 28) GörselEditör'ün geliştirmeye en çok ihtiyaç duyulan kısmı...
 * 29) * Alıntı veya kaynakları eklemek veya düzenlemek
 * 30) * Resim ve diğer medyalar
 * 31) * Genel düzenleme
 * 32) * İngilizceden farklı bir dil desteği
 * 33) * Şablon ekleme veya düzenleme
 * 34) * Performans ve hız
 * 35) * Diğer sayfa veya websitelerine bağlantı ekleme veya düzenleme
 * 36) * Kopyalama ve yapıştırma
 * 37) * Diğer editörlerle tartışırken
 * 38) * GörselEditör ve vikimetin arasında gidip gelirken
 * 39) * Kategorileri ayarlama ve değiştirme
 * 40) * Yazılımın benim neyi kullandığımı hatırlaması yerine iki düzenleme butonunun olması
 * 41) * Vikimetinleri görüntülemeden düzenleme sorunlarını çözümlemesi
 * 42) * Maddenin fark ve geçmişini görsel olarak gösterişini
 * 43) * Formül, görsel haritalama, zaman çizelgesi ve diğer özel içerik türleri
 * 44) * Kararlılık ve güvenilebilirlik
 * 45) * Diğer
 * 46) Bu kısımlarda geliştirmeler olmasını isterdim (bir önceki soruda seçilen). Eğer bu kısımlardan birine değişiklik yapabilseydim, şunları değiştirirdim...
 * 47) Bu anketi nereden duydunuz?
 * 48) * Kullanıcı mesaj sayfamdaki mesajda
 * 49) * A message on someone else's talk page
 * 50) * From another page on wiki
 * 51) * Eposta
 * 52) * Diğer
 * 53) Optional:  In case we have questions about your comments or suggestions, you may type your username here, so we can contact you.  If you want, you may add the best wiki to reach you.  (Example:  User:WhatamIdoing at en.wikipedia.org)

Sonuçlar
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.

Kullanıcı arayüzü: 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.

Yerel sorunlar: 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.

Performans:   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 kişi bu soruyu cevapladı. 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.

Diller
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 regularly 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