@@ -259,6 +259,59 @@ and uploaded
259
259
260
260
Pranit passed the GSoC final evaluation.
261
261
262
+ * ** [ Git User's Survey 2016] ( https://survs.com/survey/3cop1kt5eg ) ** is open till ** 20 October 2016**
263
+
264
+ This year we will see the return of Git User's Survey (the last one was
265
+ in 2012). The goal of the survey is mainly to help to understand who is
266
+ using Git, how and why.
267
+
268
+ The results will be published to the Git wiki on the
269
+ [ GitSurvey2016] ( https://git.wiki.kernel.org/index.php/GitSurvey2016 )
270
+ page and discussed on the git mailing list.
271
+
272
+ The survey would be open from ** 12 September** to ** 20 October 2016** .
273
+
274
+ Beside getting information on how people use Git, what are their pain
275
+ points, and what they want from Git (which might be different from what
276
+ Git developers think it is), the [ survey has also educational purpose,
277
+ and includes a bit of advertisement] ( https://public-inbox.org/git/577E6F32.7020007%40gmail.com/ )
278
+ (brief note about this
279
+ was in [ #17 ] ( https://git.github.io/rev_news/2016/07/20/edition-17/ ) ).
280
+ For example question about tools used or one about features used teaches
281
+ what is available (and which might had been not known).
282
+
283
+ The questions were prepared with the help of Eric Wong and Andrew Adrill;
284
+ the
[[ RFC
] Proposed questions for "Git User's Survey 2016"
] ( http://public-inbox.org/git/[email protected] /t/ )
285
+ thread and its subthreads was posted to solicite feedback.
286
+
287
+ The survey was announced first on Git mailing list in
288
+ [[ ANNOUNCE
] Git User's Survey 2016
] ( http://public-inbox.org/git/[email protected] / ) thread.
289
+ At request to survey administrator, Jakub Narębski, (as response to the
290
+ announcement email), one can get a separate channel in survey, with
291
+ a separate survey URL, so that responses from a particular site
292
+ or an organization could be split out. Some companies already
293
+ got their customized survey URLs.
294
+
295
+ It should be noted that the result of the survey need to be taken with
296
+ a bit of caution. As Johannes Schindelin [ reminded us] ( http://public-inbox.org/git/alpine.DEB.2.20.1609091503410.129229@virtualbox/ ) ,
297
+ many professional developers that use Git would be too busy to take the
298
+ survey. Though hopefully the fact that you can fill it bit by bit
299
+ (from the same computer), instead of having to fill it whole at once,
300
+ would help. Taking 30 minutes or more at once may be a problem,
301
+ taking 10 times a 3 minutes at once may not be...
302
+
303
+ There is also alternate version of the survey (alternate channel),
304
+ which does not require cookies or JavaScript, and is fully anonymous,
305
+ but it doesn't allow one to go back to response and edit it:
306
+ https://tinyurl.com/GitSurvey2016-anon
307
+
308
+ *** A bit of history:
*** First "GIT user survey" was
[ announced
] ( http://public-inbox.org/git/[email protected] / )
309
+ and created in 2006; its results can be found at [ GitSurvey2006] ( https://git.wiki.kernel.org/index.php/GitSurvey2006 )
310
+ page on Git Wiki. So this year's survey is 10th anniversary
311
+ of the first one. Since 2008 the Git User's Survey was hosted on
312
+ [ Survs.com] ( https://survs.com ) (then beta), thanks to generocity
313
+ of the site, who provides with recurring premium annual plan.
314
+
262
315
* Thank you Nicola and call for help!
263
316
264
317
From the beginning in March 2015, Nicola Paolucci helped set up the
@@ -278,7 +331,6 @@ There is no need to even know Git well for that. It's possible to
278
331
participate by just proofreading articles for example. Please contact
279
332
us (see our emails at the bottom) if you are interested.
280
333
281
-
282
334
### Reviews
283
335
284
336
* [ Use header data patch ids for rebase to avoid loading file content
] ( http://public-inbox.org/git/[email protected] / )
0 commit comments