git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Announcing Git User's Survey 2016 [was: Working with public-inbox.org]

From
Jakub Narębski <jnareb@gmail.com>
Date
Sep 9, 2016, 18:51 UTC
Message-ID
<feae2490-8d53-ed3a-d9a5-cc8907bc91d6@gmail.com>
In-Reply-To
<alpine.DEB.2.20.1609091503410.129229@virtualbox>
Hello Johannes,
W dniu 09.09.2016 o 15:06, Johannes Schindelin napisał:
Show 13 quoted lines
> On Sun, 28 Aug 2016, Jakub Narębski wrote:
>> W dniu 28.08.2016 o 10:38, Johannes Schindelin pisze:
>>
>>> I would like to strongly caution against putting too much stock into
>>> this users' survey. It is the best we have, granted. Yet I have not
>>> heard from anybody that they participated in the survey, unless they
>>> were also subscribed to the Git mailing list.
>>
>> I tried in past and will try for this year Git User's Survey to be
>> announced more widely than just Git mailing list (git@vger.kernel.org).
> 
> I did not mean to criticise you. I think you are doing the best you can,
> and it is valuable.
[...]
Show 5 quoted lines
> 
> The question is not so much how to advertise the survey. I skip almost all
> surveys I am asked to participate in, because I am just a little bit busy
> all the time. I feel that my colleagues do the same. Unless forced to take
> a survey, they skip it.
Right, that's a problem.  Thanks for reminding me.

I hope that the fact that by default (via the use of cookies) you can return to Survs.com survey at later time (assuming that you do it from the same computer and the same web browser), and continue responding. Taking 30 minutes or more at once may be a problem, taking 10 x 3 minutes may not be.

But I won't have too much hope...
-- 
Jakub Narębski
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 42 of 59 in “Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path]”
  1. Stefan BellerAug 16, 2016
  2. Junio C HamanoAug 16, 2016
  3. Jeff KingAug 16, 2016
  4. Junio C HamanoAug 16, 2016
  5. Stefan BellerAug 16, 2016
  6. Junio C HamanoAug 16, 2016
  7. Eric WongAug 16, 2016
  8. Eric WongAug 16, 2016
  9. Johannes SchindelinAug 18, 2016
  10. Eric WongAug 18, 2016
  11. Junio C HamanoAug 18, 2016
  12. Johannes SchindelinAug 19, 2016
  13. Johannes SchindelinAug 19, 2016
  14. Stefan BellerAug 19, 2016
  15. Eric WongAug 19, 2016
  16. Johannes SchindelinAug 22, 2016
  17. Jeff KingAug 22, 2016
  18. Eric WongAug 19, 2016
  19. Johannes SchindelinAug 22, 2016
  20. Jakub NarębskiAug 22, 2016
  21. Johannes SchindelinAug 25, 2016
  22. Jakub NarębskiAug 28, 2016
  23. Johannes SchindelinAug 29, 2016
  24. Eric WongAug 22, 2016
  25. Johannes SchindelinAug 25, 2016
  26. Jakub NarębskiAug 27, 2016
  27. Johannes SchindelinAug 28, 2016
  28. Jakub NarębskiAug 28, 2016
  29. Johannes SchindelinAug 29, 2016
  30. Jeff KingAug 19, 2016
  31. Jakub NarębskiAug 20, 2016
  32. Johannes SchindelinAug 22, 2016
  33. Duy NguyenAug 22, 2016
  34. Philip OakleyAug 22, 2016
  35. Johannes SchindelinAug 24, 2016
  36. Eric WongAug 24, 2016
  37. Johannes SchindelinAug 25, 2016
  38. Jakub NarębskiAug 27, 2016
  39. Johannes SchindelinAug 28, 2016
  40. Announcing Git User's Survey 2016 [was: Working with public-inbox.org]Jakub Narębski, Aug 28, 2016
  41. Johannes SchindelinSep 9, 2016
  42. Jakub NarębskiSep 9, 2016
  43. Johannes SchindelinAug 24, 2016
  44. Eric WongAug 24, 2016
  45. Jeff KingAug 24, 2016
  46. Eric WongAug 24, 2016
  47. Johannes SchindelinFeb 10, 2017
  48. Arif KhokarFeb 13, 2017
  49. Johannes SchindelinFeb 13, 2017
  50. Arif KhokarFeb 14, 2017
  51. Arif KhokarFeb 14, 2017
  52. Eric WongFeb 14, 2017
  53. Junio C HamanoFeb 13, 2017
  54. Arif KhokarFeb 14, 2017
  55. Junio C HamanoFeb 14, 2017
  56. Arif KhokarFeb 14, 2017
  57. Jeff KingFeb 14, 2017
  58. Johannes SchindelinAug 25, 2016
  59. Johannes SchindelinAug 26, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.