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

Re: [RFC] Git User's Survey 2008

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 23, 2008, 23:49 UTC
Message-ID
<200807240149.27371.jnareb@gmail.com>
In-Reply-To
<169F15EC-1A58-4C2A-84FC-3D14F7B4F1C5@yahoo.ca>
Dnia środa 23. lipca 2008 17:14, Jean-François Veillette napisał:
Show 18 quoted lines
> Le 08-07-22 à 21:25, Jakub Narebski a écrit :
>
> > First there is a question about the form of survey. Should we use web
> > based survey, as the survey before (http://www.survey.net.nz), sending
> > emails with link to this survey, or perhaps do email based survey,
> > with email Reply-To: address put for this survey alone?  Should we use
> > the same web survey service as before (found by Paolo Ciarrocchi for
> > first, 2006 survey, and used also for 2007 survey), or is there one
> > better (it would better be free, and without limitations on the number
> > of responses; in 2006 there were around 117 responses, in 2007 there
> > were 683 individual responses).
> 
> Consider
> http://www.survs.com
> It is still in beta but already years ahead of the proposed solution.
> I don't know about the specific of the beta (cost, availability,  
> etc.) but I had a live presentation of the product and it is an  
> amazingly great product !

It certainly _looks_ nice, but it lacks one very important feature (or at least I was not able to find it): the ability to download *RAW* data to analyse it off-line using more advanced tools (like for example Perl script to clean-up responses; spreadsheet like Excel or Gnumeric, or some statictics tool like R to analyze data, for example do a correlation between responses to different questions).

http://www.survey.net.nz allows to download raw data in modified
CSV format (modified as it allows for line continuation).  See for
example raw data for Git User's Survey 2007 results:
  http://git.or.cz/gitwiki/GitSurvey2007?action=AttachFile&do=get&target=surveydata.csv
There is another nice thing that http://www.survey.net.nz is supposed
to have (but it doesn't unfortunately work; at least downloading
current layout of survey to tweak off-line doesn't/didn't work),
namely ability to create survey off-line using some specified text
format, and upload it, instead of creating it on-line (which might be
much work for large surveys).
 
-- 
Jakub Narebski
Poland
Previous: Miguel ArrozNext: Sverre Rabbelier
Message 91 of 93 in “[RFC] Git User's Survey 2008”
  1. Jakub NarebskiJul 23, 2008
  2. Junio C HamanoJul 23, 2008
  3. HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008)Miklos Vajna, Jul 23, 2008
  4. Jakub NarebskiJul 23, 2008
  5. Miklos VajnaJul 23, 2008
  6. Jakub NarebskiJul 23, 2008
  7. Marek ZawirskiJul 24, 2008
  8. Mailing lists, was Re: [RFC] Git User's Survey 2008Johannes Schindelin, Jul 24, 2008
  9. Shawn O. PearceJul 25, 2008
  10. Junio C HamanoJul 25, 2008
  11. Jakub NarebskiJul 25, 2008
  12. Shawn O. PearceJul 25, 2008
  13. Junio C HamanoJul 25, 2008
  14. Shawn O. PearceJul 25, 2008
  15. Jakub NarebskiJul 26, 2008
  16. Marek ZawirskiJul 26, 2008
  17. Shawn O. PearceJul 26, 2008
  18. Jean-François VeilletteJul 26, 2008
  19. Petr BaudisJul 25, 2008
  20. Jing XueJul 26, 2008
  21. Jakub NarebskiJul 26, 2008
  22. Shawn O. PearceJul 26, 2008
  23. Jakub NarebskiJul 26, 2008
  24. Johannes SchindelinJul 26, 2008
  25. Scott ChaconJul 26, 2008
  26. Jakub NarebskiJul 24, 2008
  27. Johannes SchindelinJul 23, 2008
  28. Jakub NarebskiJul 23, 2008
  29. Johannes SchindelinJul 23, 2008
  30. Robin RosenbergJul 23, 2008
  31. Johannes SchindelinJul 23, 2008
  32. Jakub NarebskiJul 24, 2008
  33. Jakub NarebskiJul 23, 2008
  34. Johannes SchindelinJul 23, 2008
  35. Stephan BeyerJul 23, 2008
  36. david@lang.hmJul 24, 2008
  37. Stephan BeyerJul 24, 2008
  38. david@lang.hmJul 24, 2008
  39. Jakub NarebskiJul 24, 2008
  40. Jakub NarebskiJul 26, 2008
  41. Nguyen Thai Ngoc DuyJul 27, 2008
  42. Junio C HamanoJul 23, 2008
  43. Jakub NarebskiJul 24, 2008
  44. Dmitry PotapovJul 23, 2008
  45. Johannes SchindelinJul 23, 2008
  46. Stephan BeyerJul 23, 2008
  47. Jakub NarebskiJul 24, 2008
  48. Alex RiesenJul 23, 2008
  49. Jakub NarebskiJul 24, 2008
  50. Stephan BeyerJul 23, 2008
  51. Stephan BeyerJul 24, 2008
  52. Dmitry PotapovJul 23, 2008
  53. Matthias KestenholzJul 23, 2008
  54. Dmitry PotapovJul 23, 2008
  55. Jakub NarebskiJul 23, 2008
  56. Dmitry PotapovJul 24, 2008
  57. Jakub NarebskiJul 24, 2008
  58. Petr BaudisJul 23, 2008
  59. Jakub NarebskiJul 23, 2008
  60. Jon LoeligerJul 24, 2008
  61. Jakub NarebskiJul 24, 2008
  62. Lachele Foley (Lists)Jul 24, 2008
  63. Jakub NarebskiJul 24, 2008
  64. Dmitry PotapovJul 24, 2008
  65. Jakub NarebskiJul 24, 2008
  66. Jakub NarebskiJul 31, 2008
  67. [RFC v2] Git User's Survey 2008Jakub Narebski, Aug 20, 2008
  68. Alex RiesenAug 20, 2008
  69. Petr BaudisAug 20, 2008
  70. Jakub NarebskiAug 20, 2008
  71. Alex RiesenAug 20, 2008
  72. Junio C HamanoAug 20, 2008
  73. Jakub NarebskiAug 21, 2008
  74. Junio C HamanoAug 21, 2008
  75. Jakub NarebskiAug 21, 2008
  76. Stephan BeyerAug 20, 2008
  77. Stephan BeyerAug 20, 2008
  78. Jakub NarebskiAug 21, 2008
  79. Stephan BeyerAug 21, 2008
  80. Jakub NarebskiAug 22, 2008
  81. Mike GantAug 21, 2008
  82. Stephan BeyerAug 24, 2008
  83. Jakub NarebskiAug 25, 2008
  84. Abhijit BhopatkarAug 20, 2008
  85. [RFC v3] Git User's Survey 2008Jakub Narebski, Aug 25, 2008
  86. Stephan BeyerAug 28, 2008
  87. [RFC v4] Git User's Survey 2008 (cover letters)Jakub Narebski, Aug 30, 2008
  88. Garry DolleyAug 30, 2008
  89. Paolo CiarrocchiSep 1, 2008
  90. Miguel ArrozJul 23, 2008
  91. Jakub NarebskiJul 23, 2008
  92. Sverre RabbelierJul 24, 2008
  93. Jakub NarebskiAug 25, 2008

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.