Difference between revisions of "Feedback"

From Kiwix
Jump to navigation Jump to search
m
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
We need more informations about '''why''' our user download kiwix and content. People needs to have a way to give us a feedback and should be advised to use it. Really important: a feedback is only a one way communication from the user to the kiwix project. So we won't answer to feedback, and this is the main difference with bug reports and feature requests.
We need more information about '''why''' our users download Kiwix. People need to have ways to give us feedback and be encouraged to do so. Really important: feedback is one way communication from the user to the Kiwix project. We won't reply to feedback. This is the main difference between bug reports and feature requests.


== Ideas ==
== Ideas ==
Line 5: Line 5:
=== Ongoing feedback on Kiwix / Content ===
=== Ongoing feedback on Kiwix / Content ===


The idea is using something like the [http://input.mozilla.com/en-US/ Mozilla feedback solution]. Feedback is an option at any time, and maybe should be accessible two different places:
The idea is using something like the [http://input.mozilla.com/en-US/ Mozilla feedback solution]. Feedback is an option, and maybe should be accessible two different places:
# in Kiwix
# in Kiwix
## the toolbar (like firefox)
## the toolbar (like firefox)
## in the help menu, "what made you use kiwix" menuitem
## in the help menu, "what brought you to use Kiwix" menu item
# A link to it in every content package's home page.
# A link to it in every content package's home page.
# on the website homepage
# on the website homepage


=== One-time feedback on kiwix / content at the download start ===
=== One-time feedback on Kiwix / content at the download start ===
 
# Something like a "pop-up" box that would come when downloading something from the kiwix library manager. This could just ask a couple of things, like "Why are you downloading this?" and "Where are you planning on using this?" etc. (probably with forced answer choices). Jessie


# Something like a "pop-up" box that would come when downloading something from the Kiwix library manager. This could just ask a couple of things, like "Why did you download Kiwix?" and "Where/how are you planning on using Kiwix?" etc. (probably with multiple choice responses). Jessie
# Very short questionnaire after the user clicks on the Kiwix sourceforge download link
# Very short questionnaire after the user clicks on the Kiwix sourceforge download link
 
# Very short questionnaire on the first start of Kiwix  (if internet connection available)
# Very short questionnaire at kiwix first start (if internet connection available)


== Solution ==
== Solution ==

Latest revision as of 07:06, 29 November 2022

We need more information about why our users download Kiwix. People need to have ways to give us feedback and be encouraged to do so. Really important: feedback is one way communication from the user to the Kiwix project. We won't reply to feedback. This is the main difference between bug reports and feature requests.

Ideas

Ongoing feedback on Kiwix / Content

The idea is using something like the Mozilla feedback solution. Feedback is an option, and maybe should be accessible two different places:

  1. in Kiwix
    1. the toolbar (like firefox)
    2. in the help menu, "what brought you to use Kiwix" menu item
  2. A link to it in every content package's home page.
  3. on the website homepage

One-time feedback on Kiwix / content at the download start

  1. Something like a "pop-up" box that would come when downloading something from the Kiwix library manager. This could just ask a couple of things, like "Why did you download Kiwix?" and "Where/how are you planning on using Kiwix?" etc. (probably with multiple choice responses). Jessie
  2. Very short questionnaire after the user clicks on the Kiwix sourceforge download link
  3. Very short questionnaire on the first start of Kiwix (if internet connection available)

Solution

We can more or less easily:

What is difficult:

  • Add a link in content... as content should be reader agnostic. Kelson 12:11, 26 July 2011 (CEST)

Open questions

  • Open feedback (like on mozilla) vs questionnaire?

See also