Activity
|
|
724
Visits
|
15
Responses
|
15
Complete
|
0
Incomplete
|
|
Responses
|
1.
What are the Git Rev News sections you enjoy the most?
|
Discussions (General, Reviews, Support)
|
66.7% |
|
10 |
|
Developer Spotlight (aka Interview)
|
93.3% |
|
14 |
|
Releases
|
26.7% |
|
4 |
|
Other News (aka Links)
|
53.3% |
|
8 |
|
Credits
|
13.3% |
|
2 |
| Total respondents |
15
|
| Respondents who skipped this question |
0 |
2.
Why do you enjoy those Git Rev News sections?
|
Discussions (General, Reviews, Support)
|
64.3% |
|
9 |
|
Developer Spotlight (aka Interview)
|
85.7% |
|
12 |
|
Releases
|
28.6% |
|
4 |
|
Other News (aka Links)
|
57.1% |
|
8 |
|
Credits
|
14.3% |
|
2 |
| Total respondents |
14
|
| Respondents who skipped this question |
1 |
3.
What are the Git Rev News sections you don't enjoy much (you enjoy the least)?
|
Discussions (General, Reviews, Support)
|
33.3% |
|
3 |
|
Developer Spotlight (aka Interview)
|
0% |
|
0 |
|
Releases
|
44.4% |
|
4 |
|
Other News (aka Links)
|
11.1% |
|
1 |
|
Credits
|
44.4% |
|
4 |
| Total respondents |
9
|
| Respondents who skipped this question |
6 |
4.
Why do you not enjoy those Git Rev News sections (you selected above)?
|
Discussions (General, Reviews, Support)
|
33.3% |
|
3 |
|
Developer Spotlight (aka Interview)
|
0% |
|
0 |
|
Releases
|
44.4% |
|
4 |
|
Other News (aka Links)
|
22.2% |
|
2 |
|
Credits
|
44.4% |
|
4 |
| Total respondents |
9
|
| Respondents who skipped this question |
6 |
5.
Which Git Rev News section(s) would you like to appear at the top and which one(s) at the bottom?
|
At top (1) |
Near top (2) |
In the middle (3) |
Near bottom (4) |
At bottom (5) |
Don't matter |
Average |
|
| Discussions (General, Reviews, Support) |
|
|
|
|
|
|
1.79 |
14 |
| Developer Spotlight (aka Interview) |
|
|
|
|
|
|
2.00 |
15 |
| Releases |
|
|
|
|
|
|
3.29 |
14 |
| Other News (aka Links) |
|
|
|
|
|
|
3.00 |
13 |
| Credits |
|
|
|
|
|
|
4.82 |
13 |
| Total respondents |
15
|
| Respondents who skipped this question |
0 |
6.
Which section(s) could evolve in a good way and how?
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
7.
Do you have ideas for new sections or sub-sections?
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
8.
About the discussions or sometimes news we summarize in the "Discussions" section towards the top of Git Rev News, what could we improve? Are the articles too long or too technical?
| Total respondents |
5 |
| Respondents who skipped this question |
10 |
9.
In the "Discussions" section towards the top, is the classification of articles between "General", "Review" and "Support" relevant? How could we improve on that?
| Total respondents |
4 |
| Respondents who skipped this question |
11 |
10.
If there was a way for you to suggest contributors to be interviewed, would it be helpful? Would you consider using it?
|
Yes
|
20% |
|
2 |
|
No
|
10% |
|
1 |
|
Maybe
|
70% |
|
7 |
| Total respondents |
10
|
| Respondents who skipped this question |
5 |
11.
If there was a way for you to suggest contributors to be interviewed, what kind of way would be most helpful?
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
12.
Is there anyone we've missed to interview? Is there anyone who you wish should be interviewed?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
13.
We request for a re-interview of certain contributors who've been interviewed long back. Do you have any suggestions on contributors who you wish to be re-interviewed?
|
Eric Sunshine
|
0% |
|
0 |
|
Luke Diamand
|
0% |
|
0 |
|
Matthieu Moy
|
0% |
|
0 |
|
Stefan Beller
|
0% |
|
0 |
|
Thomas Gummerer
|
0% |
|
0 |
|
Sebastian Schuberth
|
25% |
|
1 |
|
Johannes Sixt
|
0% |
|
0 |
|
David Turner
|
0% |
|
0 |
|
Duy Nguyen
|
0% |
|
0 |
|
Jakub Narębski
|
0% |
|
0 |
|
Lars Schneider
|
0% |
|
0 |
|
Brian M. Carlson
|
0% |
|
0 |
|
Dennis Kaarsemaker
|
0% |
|
0 |
|
Jacob Keller, alias Jake
|
0% |
|
0 |
|
David Aguilar
|
0% |
|
0 |
|
Michael J Gruber
|
0% |
|
0 |
|
René Scharfe
|
0% |
|
0 |
|
Brandon Williams
|
0% |
|
0 |
|
Shawn Pearce(Hidden)
|
0% |
|
0 |
|
Ben Peart
|
0% |
|
0 |
|
Philip Oakley
|
0% |
|
0 |
|
Torsten Bögershausen
|
0% |
|
0 |
|
Michael Haggerty
|
0% |
|
0 |
|
Jiang Xin
|
0% |
|
0 |
|
Johannes Schindelin (alias Dscho)
|
0% |
|
0 |
|
Nicolas Pitre
|
0% |
|
0 |
|
Derrick Stolee
|
0% |
|
0 |
|
Elijah Newren
|
0% |
|
0 |
|
Denton Liu
|
0% |
|
0 |
|
Jeff Hostetler
|
0% |
|
0 |
|
Jean-Noël Avila
|
0% |
|
0 |
|
Emily Shaffer
|
0% |
|
0 |
|
Phillip Wood
|
0% |
|
0 |
|
Chris Webster
|
0% |
|
0 |
|
Christian Couder
|
0% |
|
0 |
|
Eric S. Raymond
|
0% |
|
0 |
|
Jonathan Tan
|
0% |
|
0 |
|
Matheus Tavares Bernardino
|
0% |
|
0 |
|
Philippe Blain
|
0% |
|
0 |
|
Felipe Contreras
|
0% |
|
0 |
|
Sergey Organov
|
0% |
|
0 |
|
Taylor Blau
|
0% |
|
0 |
|
Yann Dirson
|
0% |
|
0 |
|
Patrick Steinhardt
|
0% |
|
0 |
|
Han-Wen Nienhuys
|
0% |
|
0 |
|
Josh Steadmon
|
0% |
|
0 |
|
Randall S. Becker
|
0% |
|
0 |
|
Victoria Dye
|
0% |
|
0 |
|
Carlo Marcelo Arenas Belón
|
0% |
|
0 |
|
Junio C Hamano
|
25% |
|
1 |
|
Glen Choo
|
0% |
|
0 |
|
Jeff King (alias Peff)
|
50% |
|
2 |
|
Bagas Sanjaya
|
0% |
|
0 |
|
ZheNing Hu
|
0% |
|
0 |
|
Teng Long
|
0% |
|
0 |
|
|
0% |
|
0 |
| Total respondents |
4
|
| Respondents who skipped this question |
11 |
14.
If you wish for more than one contributor to be re-interviewed, please put all their names there, separating names with commas ','.
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
15.
Do you have any suggestions on the set of interview questions?
| Total respondents |
4 |
| Respondents who skipped this question |
11 |
16.
Do you have any suggestions on the set of re-interview questions?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
17.
Do you know blogs we should watch, or a good source of links (blog aggregator, newsletter, tech news site, not paywalled publishing service, etc.) we should take advantage of?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
18.
What kind of links do you prefer: tips and tricks, unusual use cases, new tools and workflows, research publications, videos, podcasts? Are there some kinds of links we aren't paying enough attention to?
|
Tips and tricks
|
90% |
|
9 |
|
Unusual use cases
|
80% |
|
8 |
|
New tools and workflows
|
60% |
|
6 |
|
Research publications
|
40% |
|
4 |
|
Videos
|
30% |
|
3 |
|
Podcasts
|
10% |
|
1 |
|
Other, please specify
|
0% |
|
0 |
| Total respondents |
10
|
| Respondents who skipped this question |
5 |
19.
Do you know good ways to classify links that we could use?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
20.
What is missing in the "Releases" section? Which tools could/should we add to this section?
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
21.
How could we get more help with the scripts (in https://github.com/chriscool/getreleases) we use to automate the "Release" section and the publication of Git Rev News?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
22.
If you were about to contribute to Git Rev News, which section or sections would you be interested in contributing to (existing or not)?
|
Discussions (General, Reviews, Support)
|
0% |
|
0 |
|
Developer Spotlight (aka Interview)
|
50% |
|
1 |
|
Releases
|
0% |
|
0 |
|
Other News (aka Links)
|
50% |
|
1 |
|
New section, please specify
|
0% |
|
0 |
| Total respondents |
2
|
| Respondents who skipped this question |
13 |
23.
If you were about to contribute to Git Rev News, why would you want to contribute to selected sections?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
24.
How could we make it easier to contribute to Git Rev News?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
25.
How could we recruit new contributors, helpers or internal reviewers to Git Rev News?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
26.
What kind of information is the most useful and/or enjoyable to the community?
Is it already available through Git Rev News? If not, how should it appear?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
27.
How do you find about new edition of Git Rev News?
|
Newsletter or mailing list
|
90.9% |
|
10 |
|
Announcement in online journal, like LWN.net
|
9.1% |
|
1 |
|
Manually checking https://git.github.io/rev_news/
|
0% |
|
0 |
|
RSS feed or feed aggregator
|
9.1% |
|
1 |
|
Watching GitHub repository or issues for https://github.com/git/git.github.io
|
0% |
|
0 |
|
Other, please specify
|
9.1% |
|
1 |
| Total respondents |
11
|
| Respondents who skipped this question |
4 |
28.
How could Git Rev News get more readers?
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
29.
Do you have suggestions for the Git Developer Pages website (https://git.github.io/), its Git Rev News pages, its Hacking Git page, or its GSoC and Outreachy pages?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
30.
How could Git Rev News recruit and help people who would like, or are starting, to contribute to Git?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
31.
How do you like the current design / layout of Git Rev News?
|
I like it
|
72.7% |
|
8 |
|
I slightly like it
|
27.3% |
|
3 |
|
I neither like it or dislike it
|
0% |
|
0 |
|
I slightly dislike it
|
0% |
|
0 |
|
I don't like it
|
0% |
|
0 |
| Total respondents |
11
|
| Respondents who skipped this question |
4 |
32.
Have you noticed any issues with the current design / layout of Git Rev News?
Do you have any suggestions on improving it?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
33.
Do you have suggestions about the email version of Git Rev News we send?
| Total respondents |
1 |
| Respondents who skipped this question |
14 |
34.
How could we get more and better feedback from readers and the community?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
35.
Any other feedback?
| Total respondents |
2 |
| Respondents who skipped this question |
13 |
36.
Feel free to leave your e-mail, for the editorial team to be able to contact you about your suggestions.
| Total respondents |
3 |
| Respondents who skipped this question |
12 |
