Start asking Git Rev News interviewees about their mailing list workflows?

[nasamuffin]

Git Rev News developer spotlights follow the same set of questions every week. Can we add a question asking the spotlit developer about the workflow they use to interact with the Git mailing list?

Context: https://lore.kernel.org/git/YbvBvch8JcHED%2BA9%40google.com - seems like some people (not just me! but also me :) ) could use help learning how to interact with the Git mailing list in a more productive way. It can be inspiring to see someone else's workflow and think "I like that but I'd do this thing differently" or "I didn't know you could do that thing, I'll start doing that!". Plus, what developer doesn't love talking about their own workflow? ;)

[sivaraam]

This does sound like a good idea. I'll certainly try including in the upcoming interviews 👍🏼
Thanks for the suggestion!

[sivaraam]

I was thinking about how we could phrase the question for this and came up with this:

How does your mailing list workflow look like?

Does that sound good enough? Or could it be improved? 🤔

[sivaraam]

Alternatively, I happened to notice the following questions was used during one of the initial developer spotlight interviews (I guess Thomas Ferris Nicolaisen handled the interview)._ Let me know if that sounds better.

What is your preferred Git development model?

[nasamuffin]

Hm, I would be happy to see both - but selfishly, I'm much more interested in people's mailing list workflow (for me, "mutt and here are the interesting parts of my .muttrc") than their development workflow (for me, "vim and grep"). I don't think "What is your preferred Git development model?" tends to make someone think of how they read and review patches.

I think "How does your mailing list workflow look like?" is fine - it's open-ended but it's clear that the question is about tooling, rather than "give us life advice about replying to Git emails". I like it :)

[sivaraam]

I think "How does your mailing list workflow look like?" is fine - it's open-ended but it's clear that the question is about tooling, rather than "give us life advice about replying to Git emails". I like it :)

Ok. I'll fix on that then. Thanks for the detailed feedback! 🙂