Thanks for helping us with improving Git Rev News by answering the following questions! We hope it will help us provide you a better newsletter starting with edition 101. All these questions are optional, and any constructive feedback is appreciated.
About the different sections, in general
1.
What are the Git Rev News sections you enjoy the most?
2.
Why do you enjoy those Git Rev News sections?
3.
What are the Git Rev News sections you don't enjoy much (you enjoy the least)?
4.
Why do you not enjoy those Git Rev News sections (you selected above)?
5.
Which Git Rev News section(s) would you like to appear at the top and which one(s) at the bottom?
6.
Which section(s) could evolve in a good way and how?
7.
Do you have ideas for new sections or sub-sections?
About the "Discussion" section:
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?
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?
About the "Developer Spotlight" aka "Interview" section:
10.
If there was a way for you to suggest contributors to be interviewed, would it be helpful? Would you consider using it?
11.
If there was a way for you to suggest contributors to be interviewed, what kind of way would be most helpful?
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?
14.
If you wish for more than one contributor to be re-interviewed, please put all their names there, separating names with commas ','.
15.
Do you have any suggestions on the set of interview questions?
16.
Do you have any suggestions on the set of re-interview questions?
About the "Other News" aka "Links" section:
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?
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?
19.
Do you know good ways to classify links that we could use?
About the "Releases" section:
20.
What is missing in the "Releases" section? Which tools could/should we add to this section?
About contributing to Git Rev News:
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)?
23.
If you were about to contribute to Git Rev News, why would you want to contribute to selected sections?
24.
How could we make it easier to contribute to Git Rev News?
25.
How could we recruit new contributors, helpers or internal reviewers to Git Rev News?
General questions:
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?
27.
How do you find about new edition of Git Rev News?
28.
How could Git Rev News get more readers?
30.
How could Git Rev News recruit and help people who would like, or are starting, to contribute to Git?
31.
How do you like the current design / layout of Git Rev News?
32.
Have you noticed any issues with the current design / layout of Git Rev News?
Do you have any suggestions on improving it?
33.
Do you have suggestions about the email version of Git Rev News we send?
34.
How could we get more and better feedback from readers and the community?