git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: Eric Wong <e@80x24.org>
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 13:22:21 +0200	[thread overview]
Message-ID: <45245d59-f258-f029-d478-62b3b99e6fdf@gmail.com> (raw)
In-Reply-To: <20160828094946.GA11722@dcvr>

W dniu 28.08.2016 o 11:49, Eric Wong pisze:
> 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?
[..]
>> 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.

All right, I can make Git User's Survey 2016 to be on one page
(at least the anonymous JavaScript-less channel).  It turns out
that there would be 40-42 questions in this year survey.


Though I don't know how resilent Survs.com is for submitting survey
results after connection drop/fail.

*Editing* survey (which requires to be logged in, which is not needed
for submitting survey), times out after inactivity.

-- 
Jakub Narębski


  reply	other threads:[~2016-08-28 11:22 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
2016-08-28 11:22       ` Jakub Narębski [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=45245d59-f258-f029-d478-62b3b99e6fdf@gmail.com \
    --to=jnareb@gmail.com \
    --cc=david.bainbridge@gmail.com \
    --cc=doug@dougrathbone.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).