Tristan Van Berkom wrote on Wed, Jul 08, 2020 at 23:00:36 +0900: > On Tue, 2020-07-07 at 21:34 +0200, Sander Striker wrote: > > Given the above, I'm inclined to just leave it as-is. But obviously we > > could discuss further if need be. > > While I certainly don't agree with it, it would appear that the ASF has > already taken a project-wide position on this,
The ASF does not have a cross-project position on Reply-To adding. The ASF exists to enable projects to do their thing. Among other things, that means the ASF doesn't tell projects how to run their mailing lists. Project lists are created with Reply-To adding enabled by default, but that's just that: a default, not a mandate. It is [email protected]'s decision whether or not [email protected] should set Reply-To. (Personally, I would have expected the Apache lists to be created by default with the same Reply-To settings as the respective pre-Apache lists. There used to be a checkbox for this in the mailing list creation request form.) --- Another point of view: ASF doesn't choose winners. That's why ASF is happy to host competing projects and is allergic to majority votes. Any sort of "Project dev@ lists MUST be configured to do X" policy would be a choice of winner, and so would need very good reasons. --- Not directly related, but there are at least three options for y'all to choose from: - Add no headers. - Add Reply-To. - Add Mail-Followup-To. > > I remember from my early days in the ASF (2004) that we also had a short > > conversation about Reply-To [4]. The expectation seemed to be that replies > > went to the list. And annoyance was voiced more regarding inconsistency > > than anything else. The result was the inconsistency being fixed. > > So, let's formalize your argument for a minute, Sander: Premise: The Apache HTTP Server developers decided in 2004 to configure their dev@ list in the same way their spun-off sister project's dev@ list was configured. Conclusion: Buildstream should configure its lists the same way today. I don't see how the conclusion follows from the premise. Daniel (please Cc, as I'm not subscribed)
