All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git@vger.kernel.org, Doug Rathbone <doug@dougrathbone.com>,
	David Bainbridge <david.bainbridge@gmail.com>,
	Stefan Beller <sbeller@google.com>
Subject: Re: [RFC] Proposed questions for "Git User's Survey 2016"
Date: Sun, 28 Aug 2016 09:49:46 +0000	[thread overview]
Message-ID: <20160828094946.GA11722@dcvr> (raw)
In-Reply-To: <6d171c23-65f6-5f67-7d80-051f2dfe8678@gmail.com>

Jakub Narębski <jnareb@gmail.com> wrote:
> W dniu 26.08.2016 o 08:15, Eric Wong pisze:
> 
> > Not directly-related to the survey questions, but can you ensure
> > it's accessible to folks without JavaScript/graphics, and
> > perhaps also ensure it is on a host that is Tor-friendly?
> 
> I plan on using Survs.com (where we have Premium account for free,
> thanks to Survs admins).  It has good online analysis tools, allows
> to download results in easy parseable format[1], and has support
> for multiple channels.
> 
> [1]: https://github.com/jnareb/GitSurvey-scripts
> 
> 
> It is possible to have a channel without JavaScript and without
> cookies (anonymous), at the cost of having to fill the survey
> in one go (without cookies and JavaScript you cannot go back
> to fill more questions, or change your mind about answers).
> The main page of survey would have a link to JavaScript-free
> version, and all announcements (by me) would include it.

Thanks.

> There would be no graphics that are not purely optional
> (decorative); probably there would be just a logo.
> 
> I'm not sure how Tor-friendly is this host.

I was able to get to Survs.com using Tor (maybe it was just luck
with a new exit).

> > Graphics setups often require non-Free firmware or drivers for
> > acceptable performance; and there are also visually-impaired
> > users who will need screen readers or Braille.
> 
> A question: would it be better to have the whole survey one one
> large page, or have it split into pages (with fever questions
> per page)?

I prefer single. One could get one page, take take time and let the
connection drop/fail, and send it over all in one go.  With multiple
pages, one would have to reconnect for every POST.

(fittingly, my connection failed writing this message a few
 days ago and I only got back around to it)

  parent reply	other threads:[~2016-08-28  9:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 18:56 [RFC] Proposed questions for "Git User's Survey 2016" Jakub Narębski
2016-08-20 21:29 ` Eric Wong
2016-08-25 10:26   ` Jakub Narębski
2016-08-21 23:59 ` Andrew Ardill
2016-08-25 14:53   ` Jakub Narębski
2016-08-26  6:58     ` Andrew Ardill
2016-08-26 11:42       ` Jakub Narębski
2016-08-26  6:15 ` Eric Wong
2016-08-26 11:52   ` Jakub Narębski
     [not found]     ` <CAFO0PHfy_teFFMiuFdjKYohCgRZHNT+Cc8hXOjsPeRTi9gAHPQ@mail.gmail.com>
2016-08-26 23:46       ` Jakub Narębski
2016-08-28  9:49     ` Eric Wong [this message]
2016-08-28 11:22       ` Jakub Narębski
2016-08-27 22:00 ` [RFCv2] Proposed questions for "Git User's Survey 2016", take two Jakub Narębski
2016-09-05 21:27   ` [RFCv3] Proposed questions for "Git User's Survey 2016", take three Jakub Narębski
     [not found]     ` <CAFO0PHc48OmWNcRrh2Wu30L6Oarqyw+co+zNPpsPEWerCiqanw@mail.gmail.com>
     [not found]       ` <CAFO0PHdGppfgSSYW4YB-0LEsuohyzSCkrk48fovppNfDYZx78w@mail.gmail.com>
2016-09-09 20:20         ` Jakub Narębski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160828094946.GA11722@dcvr \
    --to=e@80x24.org \
    --cc=david.bainbridge@gmail.com \
    --cc=doug@dougrathbone.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=sbeller@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.