Skip to contentSkip to conversation

separate mailing list for patches?

DISCUSSION Eric Levy 3 participants 5 messages Nov 15, 2022 Btrfs file system

lore
Share & tools
lore

Eric Levy

author
#0 lore raw

I have subscribed to the Btrfs development list occasionally, for seeking support and raising issues, though I am not involved in the development effort. Currently, there is no channel of communication more accessible to members of the public, yet, the list is often used for patches sent among the development team. For many of us, it may seem cumbersome to be flooded by so many messages carrying the patches.

Perhaps it would be useful to consider a separate mailing list for patches, or to open a web interface that is friendly to those seeking to interact with the group for more occasional support. Hopefully, it would not much affect those regularly involved to subscribe to two lists, using one for patches and the other for basic correspondence.

#1 lore raw
Quoted 7 lines · On Tue, 15 Nov 2022 13:20:24 -0500 Eric Levy <[email protected]> wrote:

I have subscribed to the Btrfs development list occasionally, for seeking support and raising issues, though I am not involved in the development effort. Currently, there is no channel of communication more accessible to members of the public, yet, the list is often used for patches sent among the development team. For many of us, it may seem cumbersome to be flooded by so many messages carrying the patches.

Quoted 8 lines

Perhaps it would be useful to consider a separate mailing list for patches, or to open a web interface that is friendly to those seeking to interact with the group for more occasional support. Hopefully, it would not much affect those regularly involved to subscribe to two lists, using one for patches and the other for basic correspondence.

By the way: You don't have to be subscribed to the mailing-list at all. You can just send emails to [email protected]. The implied reply-policy on pretty much any mailing list is reply-to-all so if anyone replies to you he will send with To: You and CC:
[email protected] and also CC: anyone else involved in the discussion so far (Thats what the Reply-to-all button in your mail client does). So it just works without being subscribed.

Regards,
Lukas Straub

author
#2 lore raw
Quoted 31 lines · Lukas Straub
Quoted 9 lines · On Tue, 15 Nov 2022 13:20:24 -0500 Eric Levy <[email protected]> wrote:

I have subscribed to the Btrfs development list occasionally, for seeking support and raising issues, though I am not involved in the development effort. Currently, there is no channel of communication more accessible to members of the public, yet, the list is often
used
for patches sent among the development team. For many of us, it may seem cumbersome to be flooded by so many messages carrying the
patches.

Quoted 10 lines

Perhaps it would be useful to consider a separate mailing list for patches, or to open a web interface that is friendly to those
seeking
to interact with the group for more occasional support. Hopefully,
it
would not much affect those regularly involved to subscribe to two lists, using one for patches and the other for basic correspondence.

By the way: You don't have to be subscribed to the mailing-list at all. You can just send emails to [email protected]. The implied reply-policy on pretty much any mailing list is reply-to-all so if anyone replies to you he will send with To: You and CC:
[email protected] and also CC: anyone else involved in the discussion so far (Thats what the Reply-to-all button in your mail client does). So it just works without being subscribed.

Quoted 4 lines

Regards,
Lukas Straub

--

Thank you for the extremely useful information. I have not been following the policy, and also, probably was also carrying an assumption that messages are only accepted from subscribers, as I think is the policy on some lists, perhaps to control spam and trolling.

At any rate, perhaps some subscribers have the preference for not receiving patches, and might appreciate my idea, but I will be happy simply to use the list following in the way you suggest.

#3 lore raw
Quoted 2 lines · Eric Levy

At any rate, perhaps some subscribers have the preference for not receiving patches, and might appreciate my idea

While I cannot speak for the developers, I'd guess they'd want to keep *this* one as the development list, and rather have a separate user list (if at all).

This however has also it's downsides (in particular for the users):
namely likely less attention by the developers ;-)

Cheers,
Chris.

author
#4 lore raw
Quoted 2 lines · Christoph Anton Mitterer

This however has also it's downsides (in particular for the users):
namely likely less attention by the developers ;-)

Yes, if the developers subscribe only to one, and use it for all communication among themselves. As was my intended suggestion, I thought it might be helpful broadly, though perhaps very slightly less convenient for some, to put the patches on a dedicated channel, separate from one for the regular messages, containing written text for any purpose.